For most of the last decade, cross border payments in India were solved in fragments. If you were an exporter collecting revenue from overseas customers, you used one provider. If you were an importer or a company paying overseas vendors, you went to your bank - along with the paperwork delays that came with it. Money moving into India and money moving out of India were treated as two fundamentally different problems, run on separate infrastructure, by separate intermediaries.
That split was never intentional. It was an inevitable artifact of how regulation and infrastructure evolved. But in 2026, it is finally being dismantled. India's cross border payments infrastructure is being rebuilt around a single principle: one authorised stack that handles both inward and outward flows seamlessly. We call this the two-way rail, and I believe it represents the most significant structural shift in Indian cross border payments since UPI transformed domestic flows.
Here's why it matters - and what it changes for any business whose operations span international borders.
Consider a real example: a mid-sized Indian SaaS company. It collects payments from customers in the US and Europe (inbound flows), pays for cloud infrastructure and tools hosted overseas (outbound flows), and increasingly hires contractors across borders (more outbound).
Under the traditional model, this single company needed to stitch together a patchwork solution:
The cost of this fragmentation wasn't visible on a single invoice - which is precisely why it was so damaging. Currency markups leaked in both directions. Finance teams spent entire days reconciling export collections against international payouts that lived in completely different systems. Compliance trails (Foreign Inward Remittance Advice, purpose codes, audit documentation) had to be assembled manually from multiple sources. For a business trying to scale internationally, the payments layer became a tax on growth.
The catalyst was regulatory. In late 2023, the Reserve Bank of India introduced the Payment Aggregator – Cross Border (PA-CB) framework, establishing formal standards for who can move money across India's borders and under what conditions. It set meaningful requirements: net worth mandates rising to ₹25 crore, PCI-DSS compliance, CERT-In-approved audits, per-transaction ceilings, and rigorous KYC processes on both ends of every transaction.
The framework recognised three authorisation types:
Most early entrants pursued inbound-only licences - export collections were the obvious, established market. The dual authorisation - one entity licensed to move money both into and out of India on a single regulated stack - is the harder mandate to secure, and it's also the more valuable one to hold.
When PayGlocal received its RBI PA-CB-I&O authorisation, it enabled us to build the two-way rail from theory into practice. Now, an Indian business can collect from a customer in London and pay a vendor in Singapore through the same authorised infrastructure, with one compliance spine, one reconciliation view, and one relationship - instead of patching two systems together itself.
It's tempting to frame "inbound and outbound on one platform" as a mere procurement efficiency - one vendor instead of two. That understates what's actually happening. Unifying cross border flows restructures the economics and intelligence of the entire process. Here’s how:
When inbound and outbound flows sit on the same stack, currency can be netted and timed rather than blindly converted in both directions. A company earning USD and spending USD no longer has to round-trip through the rupee twice, paying a markup each way. That's not a marginal saving - it's a structural shift in how FX costs behave.
In international card acceptance, the gap between a mediocre setup and an optimised one is enormous. The difference between ~85% and ~96% payment success rate is revenue that either lands in your account or disappears silently at an overseas card issuer. A unified stack that sees both directions of a customer relationship can route, retry, and localise intelligently. Every failed transaction on the inbound side represents a customer you've already won and then lost at the critical moment.
When both flows run through one authorised aggregator such as PayGlocal, documentation, purpose codes, and audit trails are generated automatically and consistently. The finance team stops being a reconciliation department and starts being a strategic function.
This is the real promise of the two-way cross border payments model: it turns international payments from a cost centre you manage into foundational infrastructure you build on.
None of this works without a modern technical architecture, and this is where the current rebuild diverges sharply from the legacy bank-led model.
The two-way rail is API-first. Payout creation, mid-market currency conversion, fee calculation, and reconciliation are exposed as endpoints embedded directly into a product's workflows—the same architecture SaaS platforms and marketplaces already expect from their entire stack. It's built on ISO 20022, the structured-data standard quietly rewiring global payment infrastructure and enabling richer, machine-readable compliance. And it treats fraud as an AI problem, because in 2026 it is: the volume and sophistication of AI-powered identity fraud has risen sharply, and static rule sets no longer hold.
Layer in the direction the entire industry is moving - real-time settlement corridors (the UPI-PayNow link between India and Singapore being the clearest signal), early institutional use of stable-coins for B2B settlement, and coverage across 180+ countries and local alternate payment methods - and you can see the shape of the next decade. The rail is not just two-way. It's programmable, real-time, and intelligent.
I spent years working in global payments before co-founding PayGlocal, and one lesson shaped everything we've built: you cannot bolt local trust onto a global product. Global platforms are engineering achievements, but they were architected for the world in general and then retrofitted to India. India's regulatory reality - RBI frameworks, purpose codes, repatriation rules, the specific texture of how Indian businesses actually get paid and pay out - isn't an edge case to patch later. It's the core of the problem.
If you export services or goods, the question is no longer just "how do I collect faster?" It's "can my export collections and my international payouts live on the same intelligent stack?"
If you import, subscribe to overseas services, or pay international talent, you can finally stop treating outbound payments as a banking chore.
If you're a fintech, marketplace, or platform, the two-way rail is something you can build directly into your product through APIs, rather than sending your users off to solve payments themselves.
The halves are being put back together. For the first time, the way cross border payments work across India's borders is starting to match how real businesses actually operate - in both directions, at once.
What is a two-way cross border payments rail?
It's a single, regulated payments stack that handles both inward flows (money coming into India, like export collections) and outbound flows (money leaving India, like vendor and subscription payments), rather than requiring separate providers for each direction.
What is the RBI PA-CB-I&O authorisation?
PA-CB-I&O is the Reserve Bank of India's authorisation for Payment Aggregators operating in Cross border payments for both Inward and Outward flows. It permits a single authorised entity to facilitate cross border payments in both directions under one regulatory framework, subject to net-worth, compliance, audit, and transaction-limit requirements.
Why does unifying inward and outbound cross border payments matter?
It reduces FX leakage by netting currency across directions, improves payment success rates through intelligent routing, and turns compliance and reconciliation into automatic processes rather than manual, time-consuming tasks. It also simplifies your payments stack from multiple vendors to one integrated partner.
How is this different from using global providers like Payoneer or PingPong?
Global providers adapt an international product to India's market. A two-way cross border rail designed for India is engineered around India's regulatory framework—RBI rules, purpose codes, repatriation guidelines, local payment methods—from the ground up. Then it adds global reach on top. The architecture itself is fundamentally different.
Can smaller exporters and importers benefit from a two-way cross-border payments setup?
Yes. Whether you're a freelancer collecting from international platforms, a small goods exporter, or a service company paying overseas contractors, a unified cross border payments stack reduces friction and costs. Explore PayGlocal's solutions for exporters to see what's available for your use case.
What is a two-way cross border payments rail?
It's a single, regulated payments stack that handles both inward flows (money coming into India, like export collections) and outbound flows (money leaving India, like vendor and subscription payments), rather than requiring separate providers for each direction.
What is the RBI PA-CB-I&O authorisation?
PA-CB-I&O is the Reserve Bank of India's authorisation for Payment Aggregators operating in Cross border payments for both Inward and Outward flows. It permits a single authorised entity to facilitate cross border payments in both directions under one regulatory framework, subject to net-worth, compliance, audit, and transaction-limit requirements.
Why does unifying inward and outbound cross border payments matter?
It reduces FX leakage by netting currency across directions, improves payment success rates through intelligent routing, and turns compliance and reconciliation into automatic processes rather than manual, time-consuming tasks. It also simplifies your payments stack from multiple vendors to one integrated partner.
How is this different from using global providers like Payoneer or PingPong?
Global providers adapt an international product to India's market. A two-way cross border rail designed for India is engineered around India's regulatory framework — RBI rules, purpose codes, repatriation guidelines, local payment methods — from the ground up. Then it adds global reach on top. The architecture itself is fundamentally different.
Can smaller exporters and importers benefit from a two-way cross-border payments setup?
Yes. Whether you're a freelancer collecting from international platforms, a small goods exporter, or a service company paying overseas contractors, a unified cross border payments stack reduces friction and costs. Explore PayGlocal's solutions for exporters to see what's available for your use case.
PayGlocal operates international and domestic payments on one RBI-authorised stack, with cross border acceptance across 180+ countries and payment success rates up to 96%. Whether you're managing export collections, outbound vendor payments, or both, discover how the two-way rail works for your business.
Explore our international payments platform or talk to our team about building your cross border workflow on unified infrastructure.
That split was never intentional. It was an inevitable artifact of how regulation and infrastructure evolved. But in 2026, it is finally being dismantled. India's cross border payments infrastructure is being rebuilt around a single principle: one authorised stack that handles both inward and outward flows seamlessly. We call this the two-way rail, and I believe it represents the most significant structural shift in Indian cross border payments since UPI transformed domestic flows.
Here's why it matters - and what it changes for any business whose operations span international borders.
The Old Model: Two Separate Systems, One Fragmented Workflow
Consider a real example: a mid-sized Indian SaaS company. It collects payments from customers in the US and Europe (inbound flows), pays for cloud infrastructure and tools hosted overseas (outbound flows), and increasingly hires contractors across borders (more outbound).
Under the traditional model, this single company needed to stitch together a patchwork solution:
- A collections provider to handle export receivables
- Banking relationships to manage vendor and contractor payouts
- Separate FX conversion processes for each direction, each with its own margin and its own compliance trail
The cost of this fragmentation wasn't visible on a single invoice - which is precisely why it was so damaging. Currency markups leaked in both directions. Finance teams spent entire days reconciling export collections against international payouts that lived in completely different systems. Compliance trails (Foreign Inward Remittance Advice, purpose codes, audit documentation) had to be assembled manually from multiple sources. For a business trying to scale internationally, the payments layer became a tax on growth.
What Changed: India's Regulatory Turning Point
The catalyst was regulatory. In late 2023, the Reserve Bank of India introduced the Payment Aggregator – Cross Border (PA-CB) framework, establishing formal standards for who can move money across India's borders and under what conditions. It set meaningful requirements: net worth mandates rising to ₹25 crore, PCI-DSS compliance, CERT-In-approved audits, per-transaction ceilings, and rigorous KYC processes on both ends of every transaction.
The framework recognised three authorisation types:
- PA-CB-I: Inbound collections only
- PA-CB-O: Outbound payments only
- PA-CB-I&O: Both directions unified under one licence
Most early entrants pursued inbound-only licences - export collections were the obvious, established market. The dual authorisation - one entity licensed to move money both into and out of India on a single regulated stack - is the harder mandate to secure, and it's also the more valuable one to hold.
When PayGlocal received its RBI PA-CB-I&O authorisation, it enabled us to build the two-way rail from theory into practice. Now, an Indian business can collect from a customer in London and pay a vendor in Singapore through the same authorised infrastructure, with one compliance spine, one reconciliation view, and one relationship - instead of patching two systems together itself.
How Unified Cross Border Payments Change the Economics
It's tempting to frame "inbound and outbound on one platform" as a mere procurement efficiency - one vendor instead of two. That understates what's actually happening. Unifying cross border flows restructures the economics and intelligence of the entire process. Here’s how:
FX Becomes Managed, Not Accidental
When inbound and outbound flows sit on the same stack, currency can be netted and timed rather than blindly converted in both directions. A company earning USD and spending USD no longer has to round-trip through the rupee twice, paying a markup each way. That's not a marginal saving - it's a structural shift in how FX costs behave.
Payment Success Rates Stop Being Invisible
In international card acceptance, the gap between a mediocre setup and an optimised one is enormous. The difference between ~85% and ~96% payment success rate is revenue that either lands in your account or disappears silently at an overseas card issuer. A unified stack that sees both directions of a customer relationship can route, retry, and localise intelligently. Every failed transaction on the inbound side represents a customer you've already won and then lost at the critical moment.
Compliance Becomes Automatic, Not Manual
When both flows run through one authorised aggregator such as PayGlocal, documentation, purpose codes, and audit trails are generated automatically and consistently. The finance team stops being a reconciliation department and starts being a strategic function.
This is the real promise of the two-way cross border payments model: it turns international payments from a cost centre you manage into foundational infrastructure you build on.
The Technology Foundation Underneath
None of this works without a modern technical architecture, and this is where the current rebuild diverges sharply from the legacy bank-led model.
The two-way rail is API-first. Payout creation, mid-market currency conversion, fee calculation, and reconciliation are exposed as endpoints embedded directly into a product's workflows—the same architecture SaaS platforms and marketplaces already expect from their entire stack. It's built on ISO 20022, the structured-data standard quietly rewiring global payment infrastructure and enabling richer, machine-readable compliance. And it treats fraud as an AI problem, because in 2026 it is: the volume and sophistication of AI-powered identity fraud has risen sharply, and static rule sets no longer hold.
Layer in the direction the entire industry is moving - real-time settlement corridors (the UPI-PayNow link between India and Singapore being the clearest signal), early institutional use of stable-coins for B2B settlement, and coverage across 180+ countries and local alternate payment methods - and you can see the shape of the next decade. The rail is not just two-way. It's programmable, real-time, and intelligent.
Building for India's Complexity, Not Despite It
I spent years working in global payments before co-founding PayGlocal, and one lesson shaped everything we've built: you cannot bolt local trust onto a global product. Global platforms are engineering achievements, but they were architected for the world in general and then retrofitted to India. India's regulatory reality - RBI frameworks, purpose codes, repatriation rules, the specific texture of how Indian businesses actually get paid and pay out - isn't an edge case to patch later. It's the core of the problem.
That's why we chose to build domestically first: to design for India's rails and rules from the first line of code, letting global reach be the layer on top rather than the other way around. The two-way rail is the clearest expression of that principle. It's only possible because we held the harder, two-directional regulatory mandate and treated India's complexity as the foundation, not the friction.
What This Means for Your Business
If you export services or goods, the question is no longer just "how do I collect faster?" It's "can my export collections and my international payouts live on the same intelligent stack?"
If you import, subscribe to overseas services, or pay international talent, you can finally stop treating outbound payments as a banking chore.
If you're a fintech, marketplace, or platform, the two-way rail is something you can build directly into your product through APIs, rather than sending your users off to solve payments themselves.
The halves are being put back together. For the first time, the way cross border payments work across India's borders is starting to match how real businesses actually operate - in both directions, at once.
Frequently Asked Questions
What is a two-way cross border payments rail?
It's a single, regulated payments stack that handles both inward flows (money coming into India, like export collections) and outbound flows (money leaving India, like vendor and subscription payments), rather than requiring separate providers for each direction.
What is the RBI PA-CB-I&O authorisation?
PA-CB-I&O is the Reserve Bank of India's authorisation for Payment Aggregators operating in Cross border payments for both Inward and Outward flows. It permits a single authorised entity to facilitate cross border payments in both directions under one regulatory framework, subject to net-worth, compliance, audit, and transaction-limit requirements.
Why does unifying inward and outbound cross border payments matter?
It reduces FX leakage by netting currency across directions, improves payment success rates through intelligent routing, and turns compliance and reconciliation into automatic processes rather than manual, time-consuming tasks. It also simplifies your payments stack from multiple vendors to one integrated partner.
How is this different from using global providers like Payoneer or PingPong?
Global providers adapt an international product to India's market. A two-way cross border rail designed for India is engineered around India's regulatory framework—RBI rules, purpose codes, repatriation guidelines, local payment methods—from the ground up. Then it adds global reach on top. The architecture itself is fundamentally different.
Can smaller exporters and importers benefit from a two-way cross-border payments setup?
Yes. Whether you're a freelancer collecting from international platforms, a small goods exporter, or a service company paying overseas contractors, a unified cross border payments stack reduces friction and costs. Explore PayGlocal's solutions for exporters to see what's available for your use case.
What is a two-way cross border payments rail?
It's a single, regulated payments stack that handles both inward flows (money coming into India, like export collections) and outbound flows (money leaving India, like vendor and subscription payments), rather than requiring separate providers for each direction.
What is the RBI PA-CB-I&O authorisation?
PA-CB-I&O is the Reserve Bank of India's authorisation for Payment Aggregators operating in Cross border payments for both Inward and Outward flows. It permits a single authorised entity to facilitate cross border payments in both directions under one regulatory framework, subject to net-worth, compliance, audit, and transaction-limit requirements.
Why does unifying inward and outbound cross border payments matter?
It reduces FX leakage by netting currency across directions, improves payment success rates through intelligent routing, and turns compliance and reconciliation into automatic processes rather than manual, time-consuming tasks. It also simplifies your payments stack from multiple vendors to one integrated partner.
How is this different from using global providers like Payoneer or PingPong?
Global providers adapt an international product to India's market. A two-way cross border rail designed for India is engineered around India's regulatory framework — RBI rules, purpose codes, repatriation guidelines, local payment methods — from the ground up. Then it adds global reach on top. The architecture itself is fundamentally different.
Can smaller exporters and importers benefit from a two-way cross-border payments setup?
Yes. Whether you're a freelancer collecting from international platforms, a small goods exporter, or a service company paying overseas contractors, a unified cross border payments stack reduces friction and costs. Explore PayGlocal's solutions for exporters to see what's available for your use case.
Ready to Unify Your Cross Border Payments?
PayGlocal operates international and domestic payments on one RBI-authorised stack, with cross border acceptance across 180+ countries and payment success rates up to 96%. Whether you're managing export collections, outbound vendor payments, or both, discover how the two-way rail works for your business.
Explore our international payments platform or talk to our team about building your cross border workflow on unified infrastructure.