Build vs Buy: Cross-border payments for Indian platforms
If you run an Indian SaaS company, a marketplace, or a platform business, cross-border payments eventually become unavoidable. You either pay international vendors, receive money from global users, or do both. At some point, your team faces the question: should we build this ourselves, or integrate with an existing provider?
The answer seems simple until you scope the work. Most platforms that choose to build discover, after 18 months and several crores of rupees, realise that the problem is far larger than it appeared. This article breaks down what building involves, what it costs, and when integration is the smarter call.
What does "building" actually mean?
Most founders assume building a cross-border payment layer means writing some API code and connecting to a bank. The reality covers a much larger surface area than that.
Building in-house means creating an end-to-end system that handles currency conversion, settlement, compliance reporting, and bank reconciliation. It also means obtaining regulatory approvals, managing banking partnerships, and continuously updating the system as regulations change.
The scope typically breaks into four distinct areas. First, you need a formal banking relationship. To move foreign currency legally on behalf of your users, your platform needs a tie-up with an Authorised Dealer Category I (AD Cat-I) bank in India. These partnerships take time to establish and require a track record that early-stage platforms rarely have.
Second, if your platform facilitates cross-border payments on behalf of other businesses or individuals, you very likely need a Payment Aggregator for Cross-Border (PA-CB) licence from the Reserve Bank of India. This is a licensed activity governed by specific RBI guidelines. In most practical structures, you either need your own RBI approval or must operate fully under a licensed entity's umbrella.
Third, you need a compliance infrastructure. Every cross-border transaction requires purpose codes, FEMA documentation, and, in certain cases, Form 15CA or 15CB certificates. Your systems must accurately generate, store, and transmit this data on time for every transaction.
Fourth, you need an FX engine. Currency conversion is not simply multiplying by a mid-market rate. You need live interbank rates, spread management, settlement timing controls, and multi-currency support.
Building all four of these layers at once is a serious undertaking. Most engineering teams underestimate both the complexity and the duration involved.
The compliance burden is heavier than it looks
The RBI has steadily tightened its framework for cross-border payments. Through multiple circulars in recent years, the RBI has issued detailed requirements for entities operating as payment aggregators in the cross-border space. The PA-CB framework sets out several requirements for any entity seeking approval.
Current RBI guidelines for payment aggregators require a minimum net worth of Rs. 15 crore at the time of application, rising to Rs. 25 crore by the end of the third financial year. PA-CB applicants are expected to meet similar thresholds. Directors and key management personnel must pass fit-and-proper checks. The entity must submit a board-approved policy covering risk, fraud management, and compliance before processing a single live transaction.
After receiving in-principle approval, ongoing obligations include regular reporting to the RBI, maintaining full transaction records, and ensuring all payments flow through proper banking channels.
FEMA adds a separate compliance layer. The Foreign Exchange Management Act governs every foreign currency transaction in India. Platforms must categorise each payment under the correct RBI purpose code, ensure outflows fall within permissible limits, and credit inflows in the prescribed form and within the prescribed timeline.
Getting FEMA documentation wrong is not a minor issue. Violations attract penalties of up to three times the contravention amount or Rs. 2 lakh, whichever is higher, where the sum cannot be quantified. For platforms with high transaction volumes, this exposure grows quickly. Understanding your full cross-border tax compliance obligations as an Indian exporter is a useful starting point before committing to a build decision.
How long does building actually take?
A realistic timeline for building a compliant cross-border payment infrastructure in India is longer than most teams expect.
In the first three months, your team is in discovery and planning mode: scoping requirements, engaging legal counsel, identifying banking partners, and starting the RBI application process—no code ships in this phase.
From months four to nine, engineering work begins. This phase covers building core payment rails, integrating with banking APIs, and constructing compliance modules. This is where the real complexity surfaces, because payment systems interact with regulatory rules in ways that are hard to anticipate during planning.
Months 10 to 14 involve internal testing, regulatory correspondence, and a limited soft launch to meet RBI requirements. Full commercial launch is not yet possible at this stage.
Between months fifteen and twenty-four, the team works on scaling, handling edge cases, and stabilising the system for production volumes. Bugs that only appear at scale take time to surface and fix.
That is 18 to 24 months before your platform has a production-ready, compliant cross-border payment system. During this period, competitors who chose to integrate with an existing provider are already processing real transactions and iterating on the product.
By contrast, integrating with an established cross-border payment provider typically takes four to twelve weeks, depending on the complexity of your use case and the quality of the provider's documentation.
The real cost of building
Engineering time is the most visible cost. A team of six engineers working for eighteen months at a total team cost of Rs. 12 lakh per month represents a direct investment of over Rs. 2 crore, before accounting for management overhead, QA, or infrastructure.
Legal and compliance counsel is essential from day one. Drafting internal policies, preparing the RBI application, engaging with banking partners, and managing ongoing regulatory correspondence requires specialised legal support. This typically costs between Rs. 20 lakh and Rs. 50 lakh for the initial phase alone.
Banking partnership costs are often overlooked at the planning stage. AD Cat-I banks charge setup fees and minimum balance requirements, and transaction fees are negotiated based on volume. You do not yet have meaningful volume when you are starting, so terms tend to be unfavourable.
Ongoing maintenance is consistently underestimated. Payment regulations change. Banking APIs release new versions. FX market conditions shift in ways that affect settlement logic. You need at least two to three engineers dedicated to payments infrastructure continuously, even after the initial build is complete and in production.
Opportunity cost is the hardest item to put a number on. Every engineer working on payment rails is an engineer not shipping features that drive growth or retention.
When you add everything up, most platforms land somewhere between Rs. 3 crore and Rs. 6 crore in the first year, before ongoing costs. Many of these costs are invisible during initial planning, much like the payment aggregator structures in India carry layers of cost that only surface at scale.
What integration with a provider actually looks like
When you integrate with a cross-border payment provider, you outsource the infrastructure layer while keeping control of the user experience your customers see.
A capable provider handles regulatory compliance and licensing, banking relationships and settlement, FX conversion, transaction monitoring and reporting, and FEMA documentation on your behalf. Your engineering team integrates via an API. The provider manages everything underneath.
The cost structure changes fundamentally. Instead of a large upfront capital commitment and a permanent headcount addition, you pay a per-transaction fee or a small FX markup on each payment. For early-stage and growth-stage platforms, costs scale with revenue rather than preceding it.
The speed advantage matters even more than the cost advantage. Going live with a provider can take weeks, allowing your team to test whether cross-border payments deliver the outcomes you expect before committing to a multi-crore build.
When building might make sense
Building in-house is not always the wrong answer. There are specific situations where it becomes the right one.
At very high transaction volumes, often above tens of millions of dollars processed monthly, the economics of owning your payment infrastructure can improve. At that scale, even a small reduction in per-transaction cost compounds significantly.
If your payment flows are genuinely unique and no existing provider can adequately serve them, building becomes necessary. This applies to specialised verticals where payment logic is deeply embedded in the product itself.
The third scenario is when payments are your core product and competitive differentiation depends on owning the stack. A company building a fintech product centred on cross-border FX, for example, may have no practical choice but to build from the start.
For the large majority of Indian SaaS companies and marketplace operators, none of these conditions applies in the early or growth stages.
The maintenance problem no one talks about
Even after you build and launch, the operational work does not stop. Cross-border payment infrastructure demands continuous attention.
The RBI updates its guidelines regularly. Banking partners push API version changes that require engineering effort to absorb. New compliance requirements emerge at both the Indian and international ends of each transaction. FX settlement rules can vary by currency pair and banking arrangements.
Each change must be assessed, implemented, tested, and deployed within the applicable timeline. If a regulatory change takes effect in sixty days, your team must be ready, regardless of what else is on the roadmap.
With an established provider, these changes happen on their side. You receive a notice, update a few configurations, and continue processing. The compliance burden stays with the provider, not your team.
For most Indian platforms, the integration path wins
The build vs buy question in cross-border payments is not a close call for most Indian platform businesses. Regulatory complexity, upfront capital requirements, and time-to-market make building impractical in the early and growth stages.
The smarter path is to integrate with a provider that gets your platform live quickly, keeps your engineering team on the product, and manages the compliance burden as regulations evolve.
Winvesta offers Indian platforms exactly this through its GCA product. Businesses can receive and manage foreign-currency payments through structured, FEMA-compliant flows without building or maintaining the underlying banking and compliance rails. The setup is API-driven, onboarding takes weeks rather than months, the documentation is compliant by default, and the FX rates are competitive from day one.
As your transaction volumes grow, you can revisit the build decision with real operational data. Most platforms that do this find integration continues to make sense even at meaningful scale, because the compliance and maintenance overhead of owning the stack remains significant regardless of size. If your platform needs to move on to cross-border payments now, Winvesta is a practical starting point. Get started at winvesta.in
Disclaimer: The information provided in this blog is for general informational purposes only and does not constitute financial or legal advice. Winvesta makes no representations or warranties about the accuracy or suitability of the content and recommends consulting a professional before making any financial decisions.
Get paid globally. Keep more of it.
No FX markups. No GST. Funds in 1 day.
Table of Contents
If you run an Indian SaaS company, a marketplace, or a platform business, cross-border payments eventually become unavoidable. You either pay international vendors, receive money from global users, or do both. At some point, your team faces the question: should we build this ourselves, or integrate with an existing provider?
The answer seems simple until you scope the work. Most platforms that choose to build discover, after 18 months and several crores of rupees, realise that the problem is far larger than it appeared. This article breaks down what building involves, what it costs, and when integration is the smarter call.
What does "building" actually mean?
Most founders assume building a cross-border payment layer means writing some API code and connecting to a bank. The reality covers a much larger surface area than that.
Building in-house means creating an end-to-end system that handles currency conversion, settlement, compliance reporting, and bank reconciliation. It also means obtaining regulatory approvals, managing banking partnerships, and continuously updating the system as regulations change.
The scope typically breaks into four distinct areas. First, you need a formal banking relationship. To move foreign currency legally on behalf of your users, your platform needs a tie-up with an Authorised Dealer Category I (AD Cat-I) bank in India. These partnerships take time to establish and require a track record that early-stage platforms rarely have.
Second, if your platform facilitates cross-border payments on behalf of other businesses or individuals, you very likely need a Payment Aggregator for Cross-Border (PA-CB) licence from the Reserve Bank of India. This is a licensed activity governed by specific RBI guidelines. In most practical structures, you either need your own RBI approval or must operate fully under a licensed entity's umbrella.
Third, you need a compliance infrastructure. Every cross-border transaction requires purpose codes, FEMA documentation, and, in certain cases, Form 15CA or 15CB certificates. Your systems must accurately generate, store, and transmit this data on time for every transaction.
Fourth, you need an FX engine. Currency conversion is not simply multiplying by a mid-market rate. You need live interbank rates, spread management, settlement timing controls, and multi-currency support.
Building all four of these layers at once is a serious undertaking. Most engineering teams underestimate both the complexity and the duration involved.
The compliance burden is heavier than it looks
The RBI has steadily tightened its framework for cross-border payments. Through multiple circulars in recent years, the RBI has issued detailed requirements for entities operating as payment aggregators in the cross-border space. The PA-CB framework sets out several requirements for any entity seeking approval.
Current RBI guidelines for payment aggregators require a minimum net worth of Rs. 15 crore at the time of application, rising to Rs. 25 crore by the end of the third financial year. PA-CB applicants are expected to meet similar thresholds. Directors and key management personnel must pass fit-and-proper checks. The entity must submit a board-approved policy covering risk, fraud management, and compliance before processing a single live transaction.
After receiving in-principle approval, ongoing obligations include regular reporting to the RBI, maintaining full transaction records, and ensuring all payments flow through proper banking channels.
FEMA adds a separate compliance layer. The Foreign Exchange Management Act governs every foreign currency transaction in India. Platforms must categorise each payment under the correct RBI purpose code, ensure outflows fall within permissible limits, and credit inflows in the prescribed form and within the prescribed timeline.
Getting FEMA documentation wrong is not a minor issue. Violations attract penalties of up to three times the contravention amount or Rs. 2 lakh, whichever is higher, where the sum cannot be quantified. For platforms with high transaction volumes, this exposure grows quickly. Understanding your full cross-border tax compliance obligations as an Indian exporter is a useful starting point before committing to a build decision.
How long does building actually take?
A realistic timeline for building a compliant cross-border payment infrastructure in India is longer than most teams expect.
In the first three months, your team is in discovery and planning mode: scoping requirements, engaging legal counsel, identifying banking partners, and starting the RBI application process—no code ships in this phase.
From months four to nine, engineering work begins. This phase covers building core payment rails, integrating with banking APIs, and constructing compliance modules. This is where the real complexity surfaces, because payment systems interact with regulatory rules in ways that are hard to anticipate during planning.
Months 10 to 14 involve internal testing, regulatory correspondence, and a limited soft launch to meet RBI requirements. Full commercial launch is not yet possible at this stage.
Between months fifteen and twenty-four, the team works on scaling, handling edge cases, and stabilising the system for production volumes. Bugs that only appear at scale take time to surface and fix.
That is 18 to 24 months before your platform has a production-ready, compliant cross-border payment system. During this period, competitors who chose to integrate with an existing provider are already processing real transactions and iterating on the product.
By contrast, integrating with an established cross-border payment provider typically takes four to twelve weeks, depending on the complexity of your use case and the quality of the provider's documentation.
The real cost of building
Engineering time is the most visible cost. A team of six engineers working for eighteen months at a total team cost of Rs. 12 lakh per month represents a direct investment of over Rs. 2 crore, before accounting for management overhead, QA, or infrastructure.
Legal and compliance counsel is essential from day one. Drafting internal policies, preparing the RBI application, engaging with banking partners, and managing ongoing regulatory correspondence requires specialised legal support. This typically costs between Rs. 20 lakh and Rs. 50 lakh for the initial phase alone.
Banking partnership costs are often overlooked at the planning stage. AD Cat-I banks charge setup fees and minimum balance requirements, and transaction fees are negotiated based on volume. You do not yet have meaningful volume when you are starting, so terms tend to be unfavourable.
Ongoing maintenance is consistently underestimated. Payment regulations change. Banking APIs release new versions. FX market conditions shift in ways that affect settlement logic. You need at least two to three engineers dedicated to payments infrastructure continuously, even after the initial build is complete and in production.
Opportunity cost is the hardest item to put a number on. Every engineer working on payment rails is an engineer not shipping features that drive growth or retention.
When you add everything up, most platforms land somewhere between Rs. 3 crore and Rs. 6 crore in the first year, before ongoing costs. Many of these costs are invisible during initial planning, much like the payment aggregator structures in India carry layers of cost that only surface at scale.
What integration with a provider actually looks like
When you integrate with a cross-border payment provider, you outsource the infrastructure layer while keeping control of the user experience your customers see.
A capable provider handles regulatory compliance and licensing, banking relationships and settlement, FX conversion, transaction monitoring and reporting, and FEMA documentation on your behalf. Your engineering team integrates via an API. The provider manages everything underneath.
The cost structure changes fundamentally. Instead of a large upfront capital commitment and a permanent headcount addition, you pay a per-transaction fee or a small FX markup on each payment. For early-stage and growth-stage platforms, costs scale with revenue rather than preceding it.
The speed advantage matters even more than the cost advantage. Going live with a provider can take weeks, allowing your team to test whether cross-border payments deliver the outcomes you expect before committing to a multi-crore build.
When building might make sense
Building in-house is not always the wrong answer. There are specific situations where it becomes the right one.
At very high transaction volumes, often above tens of millions of dollars processed monthly, the economics of owning your payment infrastructure can improve. At that scale, even a small reduction in per-transaction cost compounds significantly.
If your payment flows are genuinely unique and no existing provider can adequately serve them, building becomes necessary. This applies to specialised verticals where payment logic is deeply embedded in the product itself.
The third scenario is when payments are your core product and competitive differentiation depends on owning the stack. A company building a fintech product centred on cross-border FX, for example, may have no practical choice but to build from the start.
For the large majority of Indian SaaS companies and marketplace operators, none of these conditions applies in the early or growth stages.
The maintenance problem no one talks about
Even after you build and launch, the operational work does not stop. Cross-border payment infrastructure demands continuous attention.
The RBI updates its guidelines regularly. Banking partners push API version changes that require engineering effort to absorb. New compliance requirements emerge at both the Indian and international ends of each transaction. FX settlement rules can vary by currency pair and banking arrangements.
Each change must be assessed, implemented, tested, and deployed within the applicable timeline. If a regulatory change takes effect in sixty days, your team must be ready, regardless of what else is on the roadmap.
With an established provider, these changes happen on their side. You receive a notice, update a few configurations, and continue processing. The compliance burden stays with the provider, not your team.
For most Indian platforms, the integration path wins
The build vs buy question in cross-border payments is not a close call for most Indian platform businesses. Regulatory complexity, upfront capital requirements, and time-to-market make building impractical in the early and growth stages.
The smarter path is to integrate with a provider that gets your platform live quickly, keeps your engineering team on the product, and manages the compliance burden as regulations evolve.
Winvesta offers Indian platforms exactly this through its GCA product. Businesses can receive and manage foreign-currency payments through structured, FEMA-compliant flows without building or maintaining the underlying banking and compliance rails. The setup is API-driven, onboarding takes weeks rather than months, the documentation is compliant by default, and the FX rates are competitive from day one.
As your transaction volumes grow, you can revisit the build decision with real operational data. Most platforms that do this find integration continues to make sense even at meaningful scale, because the compliance and maintenance overhead of owning the stack remains significant regardless of size. If your platform needs to move on to cross-border payments now, Winvesta is a practical starting point. Get started at winvesta.in
Disclaimer: The information provided in this blog is for general informational purposes only and does not constitute financial or legal advice. Winvesta makes no representations or warranties about the accuracy or suitability of the content and recommends consulting a professional before making any financial decisions.
Get paid globally. Keep more of it.
No FX markups. No GST. Funds in 1 day.
