← Back to brand directory

PSP / aggregator

Razorpay payment acceptance

Razorpay is treated as a PSP or aggregator. It may help merchants access multiple payment methods, but each method still has its own market rules and risk controls.

0Market entriesExisting channel URLs kept
3MarketsFrom public channel data
1Provider recordsPublic provider library
5Contact leadsPublic PSP contact feed

What this brand represents in LocalPayMap

Razorpay is treated as a PSP or aggregator. It may help merchants access multiple payment methods, but each method still has its own market rules and risk controls.

This is a brand-level overview, not a live quote, official pricing page, endorsement, or onboarding guarantee. Country pages explain local payment habits; PSP contact records explain who may be able to connect your business.

Merchant brand notes

Razorpay is treated on LocalPayMap as an India PSP brand, not as a recommendation or availability promise. Use this page to understand the brand's usual payment role, then place it beside PSPs, local methods, wallet, bank, or BNPL routes for the target market. Frame questions about gateway, subscriptions, and payment operations discovery, and verify details with the provider before build work.

How merchants should read this brand

Read Razorpay as an India PSP brand. Treat brand recognition as context for discovery, then confirm the exact merchant use case through official material.

Where it fits in a shortlist

Place Razorpay beside local PSPs, direct methods, and bank or wallet routes when reviewing gateway, subscriptions, and payment operations discovery. Keep another route in scope while facts are checked.

What to verify with the provider

Ask the official provider or partner to confirm eligible merchant profiles, countries, methods, integration steps, support ownership, refunds, disputes, reporting, and terms.

Record-specific caution

Verify the merchant entity, business category, target country route, enabled payment methods, KYB documents, refunds, disputes, settlement currency, reserves, and support owner before choosing this PSP path.

Merchant usage and connection route

Razorpay in the payment stack

Razorpay is relevant for merchants evaluating Indian payment acceptance and related business payment workflows, including cards, UPI, net banking, wallets, subscriptions, payment links, and platform integrations. The merchant decision should focus on onboarding fit, product scope, reconciliation, refunds, disputes, and whether alternatives are needed.

Connection route

A merchant may connect directly to Razorpay, through ecommerce plugins, platforms, marketplaces, or an orchestration layer, or compare it with bank-direct acquiring and other Indian PSPs. Confirm the contracting entity, merchant category, payment methods, acquiring or aggregation role, settlement reporting, and support path.

Verification questions

  • Which Indian entity, customer geography, payment methods, currencies, and checkout channels are required?
  • Is the merchant integrating directly with Razorpay or through a platform, plugin, marketplace, or orchestration layer?
  • Which UPI, card, net banking, wallet, payment link, subscription, refund, dispute, and reconciliation flows are in scope?
  • What onboarding, documentation, category, risk-review, reserve, and support expectations must be confirmed?
  • Who handles failed payments, bank or UPI disputes, chargebacks, account reviews, and operational incidents?

Merchant caveats

  • Razorpay product scope depends on entity, merchant category, payment method, and risk review.
  • A plugin can simplify integration but may not expose every payment or reporting feature.
  • UPI, card, refund, and dispute workflows should be validated separately.
  • Provider examples are discovery examples only, not recommendations or support evidence.

Provider examples to verify

RazorpayCurlec (Razorpay Curlec)

Related markets

IndiaMalaysiaSouth Asia

Keep researching

This explanation separates payment methods, PSPs/aggregators, acquirers/banks, wallets, and networks/schemes. It does not publish coverage, eligibility, pricing, settlement timing, or onboarding guarantees.

Sources

Why merchants ask about it

Merchants ask about Razorpay because it may bundle local payment methods, onboarding, risk review, checkout, settlement, and support into one provider relationship.

Role clarification

Brand type
PSP / aggregator
Payment types
To be confirmed by market
Related countries
India, Malaysia, South Asia
Country URLs
Market-specific entries remain available for country research.

Related market links

Market-specific entries

Each row below is a country or payment-scenario record. It is kept because the same brand can behave differently by market, entity requirement, settlement route, and provider coverage.

Related PSP contact leads

These public contact routes are prioritized toward official forms, contact pages, and direct public routes when available. Confirm market scope, merchant eligibility, pricing, settlement, and support coverage directly before relying on any listing.

India · PSP / aggregator

Cashfree Payments

CardsUPINet bankingWallets

Cashfree Payments is an RBI-licensed payment aggregator in India offering an online payment gateway, payouts, virtual accounts and split settlement tools for businesses of all sizes.

Malaysia · PSP / aggregator

Curlec (Razorpay Curlec)

CardsFPXDuitNowE-wallets

Malaysian businesses wanting a modern gateway with recurring and payout features.

Malaysia · PSP / aggregator

Curlec (Razorpay Curlec Sdn. Bhd.)

Curlec is a Malaysia-only gateway regulated by Bank Negara Malaysia and settles in ringgit. Foreign-issued cards are priced separately, but this is a domestic merchant solution rather than a cross-border one.

Next actions for merchants

Use this brand page as a navigation layer. Before outreach, narrow the target market, decide whether you need a PSP, gateway, acquirer, wallet operator, or platform route, then confirm eligibility directly with the provider.

Questions merchants ask

Is Razorpay enough to make a provider decision?

No. Use the brand page to shape discovery, then compare it with market pages, PSP contacts, and written answers from the provider.

Can LocalPayMap confirm Razorpay availability for my business?

No. Availability can depend on country, entity, product category, risk review, currency, and integration model. Confirm it officially.

What should I ask before adding Razorpay to checkout work?

Ask about supported markets and methods, onboarding documents, fees, settlement setup, refunds, disputes, reporting, and production support.

FAQ for first-time merchants

Can a cross-border merchant accept Razorpay?

Possibly, but acceptance depends on account location, supported industries, risk review, settlement currency, and the specific country. Ask the provider whether it onboards merchants from your company location.

Do I need a local company or local bank account?

It depends on the country, industry, transaction model, and provider route. Some psp / aggregator records can be reached by cross-border merchants; others require a local entity, local bank account, local tax registration, or extra licensing.

Are fees and settlement terms fixed?

Published pricing is suitable for initial screening only. Actual pricing can vary by country, industry, volume, settlement currency, integration model, and contract terms. Confirm the official pricing page or a provider quote before going live.

What should I ask before integration?

Ask who signs the merchant agreement, which countries and currencies are covered, whether your industry is allowed, how refunds and disputes work, whether reserves apply, what settlement timing is available, and which official contact route handles onboarding.

Is this page the same as a country payment-channel page?

No. This page aggregates brand context. Country payment-channel pages keep the local market, checkout, entity, pricing, and settlement questions visible.

Pricing note

Published pricing is suitable for initial screening only. Actual pricing can vary by country, industry, volume, settlement currency, integration model, and contract terms. Confirm the official pricing page or a provider quote before going live.