Payment Gateway Rails: How does Cross Border Checkout from USA to India Work?

TL;DR

Selling from the US into India is a licensing question before it is a technical one. Since the RBI's October 2023 circular, any entity aggregating cross-border online payments for Indian import or export is regulated directly by the RBI as a Payment Aggregator Cross Border, and roughly 19 to 25 entities held authorisation by early 2026. Once that is settled, the checkout question is straightforward because UPI dominates. Two constraints catch teams out: a per-unit value cap of INR 25 lakh, and RBI tokenisation rules that break stored-card flows built for other markets. Paying Indian suppliers is a separate problem with separate treatment.

Two Directions, Two Different Problems

‍

The US to India corridor is really two corridors, and conflating them is the most common planning error.

‍

Inbound to India means a US business collecting from Indian customers, whether consumers buying from a D2C brand or businesses buying software and services. From India's regulatory perspective the Indian buyer is importing, and the collection is governed by the cross-border payment aggregation framework.

Outbound means a US business paying Indian entities: development firms, outsourcing providers, agencies, contractors, distributors and suppliers. India is a major services exporter, so for a large share of US companies this direction carries real volume.

‍

Different regulation, different rails, different providers, different failure modes.

‍

The Inbound Gate: PA-CB Authorisation

‍

Since the RBI's October 2023 circular on the regulation of Payment Aggregators for cross-border transactions, all entities facilitating cross-border payments for Indian import or export are regulated directly by the Reserve Bank of India as PA-CBs [1]. Before that, the activity sat with Authorised Dealer banks under the older and narrower OPGSP arrangement.

The framework opened the activity to non-bank entities, which is why the provider landscape looks the way it does. It also brought those entities under direct RBI governance with compliance obligations equivalent to and in places heavier than a domestic payment aggregator [2].

For a US business, the translation is short: collecting from Indian customers requires an RBI-authorised PA-CB partner or a bank [3].

‍

Three authorisation categories exist [3]:

PA-CB-E covers export transactions, meaning inward flow into India
PA-CB-I covers import transactions, meaning outward flow from India
PA-CB-E&I covers both

‍

A US merchant collecting from Indian buyers needs a provider with import-capable authorisation.

The entry bar is deliberately high. Non-bank PA-CBs require minimum net worth of INR 15 crore at application, rising to INR 25 crore by 31 March 2026, with FIU-India registration as a prerequisite [2][4]. Import-only PA-CBs must maintain an Import Collection Account with an AD Category-1 scheduled commercial bank, and funds pass through a defined account structure before reaching the foreign merchant [2].

By early 2026 the RBI had authorised roughly 19 to 25 entities, with approvals arriving in waves since mid-2024 [3][5]. Named holders include Cashfree Payments, Amazon Pay India, Adyen India, BillDesk, Razorpay, PayU and Worldline [3][5].

Two due-diligence points. The RBI publishes a regularly updated list of domestic online payment aggregators but, as of early 2026, does not maintain a single always-current public page dedicated to PA-CB authorisations [3]. And in-principle approval is not a final licence [5]. The two get reported interchangeably and they are not the same thing.

‍

What Indian Customers Actually Pay With

‍

Once licensing is settled, the checkout question is comparatively simple because the market is concentrated.

‍

UPI carries around 85% of India's digital payments and processed 23.2 billion transactions in May 2026 alone [6]. For consumer and D2C checkout it is the default, and everything else is a supplement. Our blog on how UPI works covers the mechanics and app landscape.

The failure mode worth naming: a card-first checkout imported from US or European markets underperforms in India for structural reasons unrelated to your product. Card penetration is low relative to UPI adoption and the consumer reflex is to select UPI.

‍

Cards matter for higher-value purchases, corporate card programmes and self-serve software licences where a business user transacts without procurement involvement. RuPay is the domestic network alongside Visa and Mastercard, and RuPay credit cards can now link to UPI.

‍

Net banking persists for higher-value e-commerce and among buyers who prefer a bank-authorised flow.

‍

For invoiced B2B, bank transfer is the normal instrument, for the same reason it is in most markets: values exceed card comfort levels and the buyer's finance function controls the payment.

‍

The Constraints That Change Your Build

‍

Three features of this corridor change what your checkout can do, and all three surprise teams that have only built for US or European markets.

‍

Constraint

What It Says

Impact on D2C

Impact on B2B

Authorisation

Only authorised PA-CBs or banks may aggregate.

Provider choice narrows to roughly 19 to 25 entities.

Same, plus verify the category covers your direction.

Value cap

Maximum INR 25,00,000 per unit of goods or services.

Rarely binds on consumer order values.

Binds on enterprise contracts and annual engagements.

Tokenisation

RBI restricts merchant storage of card credentials.

Returning-customer flows need redesigning.

Repeat purchase by the same buyer is affected.

Merchant KYC

Tightened by the September 2025 Directions.

Longer onboarding than a domestic US integration.

Longer again for group structures. Build it into the timeline.

Summary only, not legal advice. Confirm current requirements with your provider and counsel. Sources: [2], [3], [7], [8].

‍

The tokenisation constraint catches product teams hardest. RBI rules restricting merchant storage of card credentials apply to PA-CBs as they do to domestic aggregators [7]. A returning-customer flow assuming a stored card behaves differently in India, and the design work belongs before launch rather than after.

The value cap tends to surface after launch rather than before. INR 25,00,000 is roughly where enterprise contracts and larger service engagements sit, so a corridor validated on mid-market values can fail on the deals that matter most.

‍

The Other Direction: Paying Into India

‍

For many US businesses this is the larger flow. India exports software development, IT services and outsourced business functions at enormous scale.

Outbound payments run over correspondent banking, or over domestic INR rails through a provider holding the relevant banking relationships. The operational questions are corridor coverage, settlement timing, and the quality of payment data arriving with the funds.

Within India the receiving rails are the bank ones. NEFT carries routine business transfers in batches, RTGS handles high-value settlement individually, and IMPS provides continuous availability at lower values. UPI, despite its dominance of digital payments by volume, is structurally a consumer retail rail with an average ticket near Rs 1,348 [6]. It is not where business value moves.

One dependency becomes non-optional shortly. From 14 November 2026, SWIFT will reject cross-border payment messages carrying fully unstructured postal addresses, and the requirement flows upstream into payment initiation files. For anyone running volume payouts into India over SWIFT, beneficiary address data quality becomes an operational prerequisite. Our ISO 20022 November 2026 guide covers the scope.

‍

What to Verify Before You Build

‍

Confirm your provider holds a final PA-CB licence, not in-principle approval [5].

Confirm the authorisation category matches your direction. Export-only does not enable import flows [3].

Build for UPI first if you sell to consumers. Card-first design imported from other markets underperforms here [6].

Test the value cap against your largest expected transaction, not your average. INR 25,00,000 per unit is where enterprise B2B hits the ceiling [7].

Design for tokenisation constraints from the start. Retrofitting a repeat-purchase flow costs more than building it correctly [7].

Scope inbound and outbound separately. Different regulation, different rails, frequently different providers.

‍

For businesses paying Indian suppliers, contractors and sellers, corridor coverage and payment data quality determine whether payments arrive cleanly or generate exceptions.

‍

Where Tazapay Fits

‍

The two directions of the US-India corridor need different infrastructure, and Tazapay covers both. Its payment gateway supports UPI and card acceptance for collecting from Indian buyers under the PA-CB framework, while its payout coverage moves business value to Indian counterparties through NEFT, RTGS and IMPS with the structured data that keeps SWIFT payments clean ahead of the November 2026 change.

‍