If you are choosing an international money transfer API, the right pick depends on one question most guides skip: are you paying money out to people abroad, or collecting money in from foreign customers and settling it at home? The two jobs run on different rails, carry different compliance, and are rarely done well by the same provider.
For a developer who needs to move cross-border money through an API, the best international money transfer APIs for developers in 2026 are:
- Xflow: the developer-first international payment API for collecting cross-border payments, with clean REST endpoints, webhooks and compliance built into the flow.
- Cashfree Payments: an India-based option with a full RBI cross-border licence and automatic FIRA.
- Payoneer: receiving accounts plus a mass-payout API, strong with freelancers and marketplaces.
- Wise Platform: transparent mid-market FX for embedded payouts and receiving in 40-plus currencies.
- Airwallex: a full-stack accept-and-pay-out API for global platforms and marketplaces.
- Nium: payout infrastructure reaching 190-plus countries, built for banks and platforms.
- Stripe: the developer-experience benchmark for global card acceptance and Connect payouts.
- Currencycloud: a Visa-owned collect, convert and pay engine for fintechs building their own product.
Xflow leads this list on developer experience: a well-documented REST API, receiving accounts you provision in a single call, signed webhooks, a sandbox, and transparent mid-market FX. Where most international money transfer APIs stop at moving money, it also automates the compliance reporting that usually lands on your finance team. This guide compares all eight on what matters to a developer, then shows how the machinery works underneath. Xflow itself ships as Xflow for Platforms, a white-label payment API for developers that lets your users collect international payments in India without leaving your product.
The best international money transfer APIs for developers, in brief
Here is the one-line version, ordered by fit for a developer moving money across borders in code.
- Xflow: the developer-first pick, with a clean REST API, receiving accounts, signed webhooks, transparent mid-market FX, and compliance (eFIRA and purpose codes) handled in the flow.
- Cashfree Payments: the closest India-based peer, with a full Payment Aggregator - Cross Border licence and eFIRA issued within 24 hours.
- Payoneer: multi-currency receiving accounts and a mass-payout API, with downloadable FIRC for Indian exporters.
- Wise Platform: mid-market FX with an explicit fee, embedded receiving in 40-plus currencies, held to strict rate transparency.
- Airwallex: one API for card acceptance and payouts across 180-plus countries, with multi-currency accounts.
- Nium: deep real-time payout reach for banks and marketplaces, plus card issuing, on an enterprise contract.
- Stripe: best-in-class documentation and SDKs for global card checkout and marketplace payouts.
- Currencycloud: modular collect, convert and pay building blocks for fintechs that want to build their own product.
Why developers look for a dedicated cross-border payment API
Moving money across borders is not the same problem as taking a domestic card payment, and a general gateway rarely covers it. Teams usually reach for a dedicated cross-border payment API when a bank portal or a card-only stack starts to hurt.
The recurring reasons developers switch:
- Manual wires do not scale in code: logging into a bank portal to reconcile each transfer is fine for one payment and painful for a thousand. An API turns that into a webhook.
- FX cost hides in the rate, not the fee: a bank quotes a small percentage but converts at a marked-up interbank rate you never see. A transparent API converts at the mid-market rate and states its markup.
- Compliance paperwork is the real tax: for money coming into India, the RBI wants purpose codes and a Foreign Inward Remittance Advice on every credit. Chasing that from a bank by hand costs hours.
- Reconciliation needs structured data: matching a credit to an invoice by reading a bank statement does not work at volume. A good API returns a clean record per credit.
- Card tools stop at the border: a checkout API authorises cards well but was never built to provision multi-currency accounts, convert, and settle in local currency.
The result is a market split between two kinds of product: send-side payout APIs, and receive-side collection APIs. Knowing which one you actually need saves a costly integration.
Comparing the top international money transfer APIs for developers
The table below compares all eight on the dimensions that decide a build: which direction the API is built for, whether it settles into India, how it prices FX, and what it does for RBI compliance. Fees are each provider's published rates as seen in September 2026 and mechanisms differ, so read the fee column as a starting point, not a quote.
| API | Best for | Pay-in / payout | Developer surface | FX basis | India settlement + compliance | Indicative fee |
|---|---|---|---|---|---|---|
| Xflow | Developer-first cross-border collections | Collect-led (imports live too) | REST, webhooks, sandbox | Mid-market rate + markup | INR T+1; auto eFIRA + purpose codes; full RBI PA-CB (exports + imports) | Flat on small invoices, then 0.6% / 0.4% by plan |
| Cashfree | India inbound collections | Collect-led (E and I licence) | REST, Node/Python SDKs, webhooks | INR settlement, markup varies | INR; 24-hour eFIRA; full RBI PA-CB (export + import) | ~2.99% intl cards; ~1-1.5% local-rail collections |
| Payoneer | Freelancers, marketplaces | Both | REST, OAuth2, sandbox, webhooks | Mid-market + markup up to ~2% (India) | INR to bank; downloadable FIRC; PA-CB in-principle only | ~1% receive (ACH); ~2% FX on USD to INR |
| Wise Platform | Transparent embedded FX | Both | REST, sandbox, webhooks (no first-party SDK) | Mid-market, no spread, explicit fee | INR settle; FIRA ~$2.50 each; PA-CB in-principle, inward only | Mid-market + per-transfer fee; Platform pricing on quote |
| Airwallex | Global accept + payout | Both | REST, JS + mobile SDKs, sandbox | Interbank + 0.5% (major), 1% (other) | Via non-India entity; FIRC on request, partner fee | 4.30% + $0.30 intl cards; local payouts free |
| Nium | Global payout infrastructure | Both, payout-led | REST, Postman, sandbox, webhooks | Contract-negotiated | Domestic PA/PPI in-principle; no PA-CB | Quote-only |
| Stripe | Global card checkout | Both, geography-gated | REST, seven official SDKs, test mode | Card networks + conversion surcharge | Invite-only; card-in only; FIRC not automatic | India: 4.3% intl + 2% conversion; Connect payout 0.25% |
| Currencycloud | Fintechs building their own | Both, modular | REST, six official SDKs, demo sandbox | Wholesale/interbank | Via partners only; no PA-CB | Quote-only |
You can read the split straight off the table. Xflow and Cashfree are the only two that hand back eFIRA and purpose codes automatically. The global names (Airwallex, Nium, Stripe, Currencycloud) go wider on payouts but reach India through a foreign entity or a partner, leaving FIRC to you.
What each API costs on a $10,000 cross-border invoice
FX cost is the number most API pages skip, so here is a worked example. Take a $10,000 software-services receipt into India at an illustrative USD/INR mid-market rate of ₹95.00, which is ₹9,50,000 before any cost. Each provider prices differently, and cards, wires and local rails are different mechanisms, so treat this as an illustration of where the money leaks, not a promised figure.
| Route | Rate basis | Indicative cost | INR you keep on $10,000 |
|---|---|---|---|
| Xflow (Growth plan, 0.4%) | Mid-market ₹95.00 | ~₹0.38/USD markup | ~₹9,46,200 |
| Cashfree Global Collections | Local rails, ~1% | ~1% of value | ~₹9,40,500 |
| Wise Platform | Mid-market + fee | ~0.5-0.7% fee | ~₹9,44,000 |
| Payoneer | Mid-market + ~2% FX | ~2% of value | ~₹9,31,000 |
| Bank SWIFT wire | Hidden interbank rate | ~2% markup + flat fees | ~₹9,26,000 |
| Stripe (international card) | Card + conversion | ~4.3% + ~2% conversion | ~₹8,90,000 |
Your actual rate depends on the live mid-market rate and your plan. The real difference is visibility: a transparent API shows the rate before you settle, while a bank card rate or a SWIFT wire buries it inside the interbank rate. Xflow's published pricing is a flat fee on smaller invoices, then a percentage on FX above a threshold: Starter, then 0.6%; Growth, then 0.4%; Scale is custom, all converted at the mid-market rate.
What separates a good cross-border payment API from a bad one
This is a developer list, so the order reflects how each API feels to build on and run, not how big the brand is. In practice, four things decide whether an integration is a good week or a bad quarter.
The first is direction: does the API actually do your job, collecting or paying out, instead of claiming both and doing one well? The second is compliance: does it hand back eFIRA and the rbi purpose code for inward remittance automatically, or leave you chasing a bank? The third is FX transparency, whether the rate sits in a quote you can audit or hides in a spread you cannot. The fourth is plain developer experience: clear docs, a working sandbox, and signed, retried webhooks that hold up in production.
Xflow sits at the top because it scores on all four for the collect side and automates the compliance step the others leave to you. Every option below still gets an honest read on where it wins and where it does not.
The best APIs for collecting cross-border payments
If your product needs to receive foreign money and land INR at home, these three are built for that direction and carry the RBI reporting that a global payout API never touches.
1. Xflow
Best for: developers who need to collect cross-border payments through a clean, compliant API, from freelancer tools and SaaS products to marketplaces and exporters.
Xflow is a cross-border payments platform whose developer product, Xflow for Platforms, gives you white-label receiving accounts and webhooks so your users get paid inside your app. What sets it apart as an international payment API is that it handles the step other APIs skip, the RBI reporting, rather than leaving it on your finance team. It holds a final Payment Aggregator - Cross Border (PA-CB) authorisation from the Reserve Bank of India (RBI) for both exports and imports, as of February 2026.
How quickly can you integrate Xflow?
The receive flow is three steps, and most teams have a sandbox integration working in a day rather than a quarter. You provision a receiving account for a customer in one call, and Xflow returns account details a foreign payer can send to:
POST /v1/receiving-accounts
Authorization: Bearer sk_live_xxx
Content-Type: application/json
{
"customer_id": "cus_8842",
"currency": "USD",
"purpose_code": "P0802"
}When the money arrives, a single signed webhook fires, and it already carries the eFIRA status, so you never make a separate call to fetch compliance proof:
{
"event": "payment.credited",
"receiving_account": "racc_01H9",
"amount": 10000.00,
"currency": "USD",
"sender_ref": "INV-2043",
"purpose_code": "P0802",
"efira_status": "issued"
}Your service verifies the webhook signature, matches sender_ref to the invoice, and marks it paid. There is no bank portal to log into and no FIRA to request by hand, which is the part that usually turns a payment integration into a support ticket.
Key features:
- Multi-currency receiving accounts issued through the banking partner, with account details a foreign customer can pay into.
- Signed webhooks that fire the moment a credit lands, carrying amount, currency, sender reference and purpose code.
- Auto-issued eFIRA and RBI purpose codes on every credit, so GST refunds and export records stay clean.
- Next-business-day (T+1) INR settlement to a pre-registered Indian bank account.
- Mid-market-rate conversion with a stated markup, plus an FX AI Analyst that lets you set a target rate.
- ISO 27001 and SOC 2 certification, with JP Morgan Chase as banking partner.
Pros:
- Developer experience is the point: clean REST endpoints, receiving accounts you provision in a call, signed and retried webhooks, and a real sandbox mean a working integration in days.
- Compliance ships with the API: the auto eFIRA and purpose codes are records exporters usually chase by hand, so you remove operational work instead of adding it.
- The FX rate is visible: conversion runs on the mid-market rate with a stated markup, easier to reconcile and audit than a hidden bank spread.
- Regulatory footing is current: the full PA-CB authorisation for exports and imports, plus ISO 27001 and SOC 2, answers the fund-safety questions that stall finance sign-off.
Cons:
- Collections are the core strength: imports are live, but the depth sits on the receiving side, so a team whose main need is high-volume outbound payouts should check corridor coverage first.
- Not a 190-country payout network: for mass disbursement to beneficiaries worldwide, a payout-led provider such as Nium or Airwallex reaches further.
- Younger, smaller review base: Xflow holds a strong 4.8 out of 5 on G2, but across 25 reviews, so some buyers will want references at their own volume.
Verdict: if you want a clean international payment API that also handles the compliance in code, Xflow is where we would start.
Collect international payments into India with compliance built in
2. Cashfree Payments
Best for: Indian businesses that want one provider for domestic and international collections, with automatic FIRA.
Cashfree is an India-based payments company whose International Payment Gateway and Global Collections products let Indian businesses receive cross-border payments and settle INR. It was among the first non-bank entities to receive a full PA-CB licence covering both export and import flows, announced in July 2024, which puts it in the same regulated bracket as Xflow for inbound collections.
Key features:
- Acceptance from 180-plus countries, with settlement in INR and around two dozen settlement currencies.
- Global Collections local-rail virtual accounts for USD, GBP, EUR, CAD and AUD, which avoid slower SWIFT wires.
- Monthly FIRC reporting and an eFIRA auto-issued within 24 hours.
- REST API with Node.js and Python SDKs, sandbox test mode, webhooks and a Postman collection.
- A separate domestic INR payouts product for businesses that also disburse.
Pros:
- Automatic 24-hour FIRA: like Xflow, it removes the manual bank chase, which is decisive for exporters filing GST and EDPMS records.
- Local-rail collections are cheaper than cards: Global Collections at roughly 1 to 1.5% beats the ~2.99% international-card rate for larger invoices.
- One stack for India and abroad: teams already using Cashfree for domestic UPI and cards get international collection under the same integration.
Cons:
- Support coordination draws complaints: Capterra reviewers describe overlapping contact from multiple staff on a single issue and note internal communication could improve.
- Webhook depth is thinner: reviewers call the webhooks "bare minimum" versus a benchmark like Stripe, and report occasional overseas card-transaction failures.
- Dashboard and holds friction: some reviews mention settlement holds and a learning curve on reporting filters.
Verdict: the strongest India-based alternative for inbound collections, and the peer most developers will shortlist alongside Xflow.
3. Payoneer
Best for: freelancers, marketplace sellers and platforms that need to both receive foreign payments and pay out at scale.
Payoneer gives an Indian business two things a developer cares about: multi-currency receiving accounts that collect from clients and marketplaces as if local, and a Mass Payout API for platforms that disburse to a large payee base. It is a widely used route for Indian freelancers and exporters, with marketplace integrations that pay in directly.
Key features:
- Receiving accounts in 13-plus currencies, including USD, EUR, GBP, SGD and AED.
- Mass Payout API with payee onboarding links, KYC approval and payouts to multiple methods at scale.
- OAuth2 auth, a sandbox, webhooks for payout status and a Postman collection.
- Downloadable digital FIRC, FIRA and NOC from the portal for Indian exporters, with purpose codes captured on inward remittances.
- Physical and virtual card for spend, plus balances you can hold and convert.
Pros:
- Two-way rails in one account: a platform can onboard and pay a global supplier base while suppliers also receive, from the same provider.
- Low friction for solo exporters: receiving accounts remove the need to open foreign bank accounts, and marketplace integrations are mature.
- Compliance docs are self-serve: the downloadable FIRC and captured purpose codes cover the paperwork Indian exporters need.
Cons:
- Account holds are a recurring theme: Trustpilot carries a high volume of reports of frozen accounts and payments stuck pending, one of the most-cited complaint categories.
- FX markup is the real cost: the conversion spread on USD to INR is commonly cited around 2%, baked into the rate rather than shown as a fee.
- Fees stack at low volume: an annual charge applies to accounts under a receiving threshold, and support responsiveness draws consistent criticism.
- PA-CB is in-principle only: Payoneer received in-principle PA-CB authorisation in January 2026 and was not yet on the fully authorised list, so its cross-border operating scope in India is still maturing.
Verdict: a practical receiving-plus-payout option, strongest for freelancers and marketplaces that can live with the FX markup and hold risk. For a deeper look, see the Payoneer review.
The best global money transfer and payout APIs
If your job is to pay people abroad, or to collect across many countries without an India-first requirement, these five compete on payout breadth and developer experience. They are strong tools, and each is honest here about its India limits.
4. Wise Platform
Best for: platforms and financial institutions that want mid-market-rate payouts and receiving embedded under Wise's own compliance.
Wise Platform is Wise's business arm, a REST API that lets banks, fintechs and platforms plug Wise's cross-border rails into their own product. Its defining feature is FX honesty: it converts at the mid-market rate with no spread on the rate and adds an explicit, itemised fee instead.
Key features:
- Receiving in 40-plus currencies with local account details, and payouts across a similar set.
- Mid-market rate with a stated fee, backed by around 80 licences globally.
- REST and JSON API covering profiles, balances, quotes, recipients, transfers and webhooks.
- A full sandbox for end-to-end testing, plus a separate comparison API for rate benchmarking.
Pros:
- Predictable, auditable cost: the mid-market rate with a stated fee is easy to reconcile in the quote response, with no hidden spread.
- Real local receiving details: you can offer collect-like-a-local in 40-plus currencies without building bank relationships.
- Heavy regulatory footprint: around 80 licences means Wise carries the compliance load in many markets.
Cons:
- No first-party SDKs: integration is REST-only, so teams hand-roll clients or use community libraries, more lift than an SDK-first rival.
- Support is the weak spot: Wise Business scores about 7.1 out of 10 on support on G2, below its feature scores, and account freezes during KYC sweeps are a recurring review theme.
- India is inward only, and in-principle: Wise holds in-principle PA-CB approval for exports (inward) as of mid-2025, outbound is not yet authorised, and India-registered accounts auto-convert to INR without holding foreign currency.
Verdict: an excellent choice where transparent FX and embedded receiving matter, with the caveat that India support is lighter than an India-first specialist.
5. Airwallex
Best for: global platforms and marketplaces that need to both accept payments and pay out across many countries from one API.
Airwallex is an API-first financial platform that unifies payment acceptance, multi-currency accounts, FX, global payouts and card issuing. It is a fuller accept-hold-convert-pay stack than most, which is its main draw for a scaling platform.
Key features:
- Payment acceptance in 130-plus currencies and 160-plus methods across 180-plus countries.
- Local payouts to 120-plus countries plus SWIFT to 200-plus.
- Transactional FX at interbank plus 0.5% on major currencies and 1% on others, with quote validity from one minute to 24 hours and forward locks.
- Payment Elements and mobile SDKs, a sandbox and webhooks.
Pros:
- One API for acquiring and payouts: you avoid stitching a separate collect provider to a separate payout provider.
- Transparent, programmable FX: interbank plus 0.5% with quotes and forward locks suits currency-risk logic.
- SDK-first checkout: Payment Elements and mobile SDKs speed integration versus REST-only rivals.
Cons:
- Account holds during compliance review: freezes with slow "wait until further notice" responses are a recurring theme across Trustpilot, G2 and Capterra.
- Sandbox and SDK gaps: developer reviews note the sandbox is limited versus production, and server-side SDKs are still in beta and Node-focused.
- India runs through a foreign entity: Airwallex serves Indian businesses via a non-India entity, does not issue FIRC directly (you request it, and the banking partner may charge a fee), and is built as a global platform rather than around RBI reporting.
Verdict: a powerful full-stack option for global flows, less suited to an Indian business whose core need is compliant INR collection.
6. Nium
Best for: banks, marketplaces and platforms building global payout flows at enterprise scale.
Nium is embedded cross-border payments infrastructure exposed through one API, covering payouts, collections, FX and card issuing. Its strength is payout reach, and it is aimed at platforms that can commit to an enterprise integration rather than a self-serve signup.
Key features:
- Payouts to 190-plus countries and 100-plus currencies, with 100-plus real-time corridors to bank, card, wallet or cash pickup.
- Collections in 35-plus markets via virtual account numbers.
- Card issuing in 30-plus countries on Visa and Mastercard, backed by 40-plus licences.
- REST API with a Postman collection, sandbox and webhooks.
Pros:
- Genuine one-API breadth: payout, pay-in, card issuing and FX in one integration, which consolidates several providers.
- Deep real-time payout reach: 100-plus real-time corridors is more than most rivals, useful for gig and marketplace disbursement.
- Owns regulated rails: 40-plus licences reduce the downstream banking relationships a platform must manage.
Cons:
- Quote-only pricing, no self-serve: there is no public price list or signup, which blocks small teams and makes cost modelling hard.
- Integration friction: reviews on G2 and elsewhere cite long onboarding, documentation gaps and sandbox-versus-production inconsistencies, and its G2 score sits at 3.4 out of 5 across a thin review base.
- Wrong direction for Indian exporters: Nium India holds in-principle domestic PA and PPI approvals but no PA-CB, and its India collection product runs the opposite way, letting foreign businesses collect INR from Indian buyers.
Verdict: a serious payout infrastructure choice for platforms, not a fit for an Indian business collecting foreign proceeds.
7. Stripe
Best for: global SaaS and marketplaces that primarily charge international customers with the best developer experience available.
Stripe is the developer-experience benchmark for card acceptance, and Stripe Connect is its layer for onboarding sub-merchants, splitting payments and paying them out. For an Indian entity, though, the cross-border story comes with real limits.
Key features:
- Card acceptance in 135-plus presentment currencies.
- Connect connected accounts, split payments and cross-border payouts within supported regions.
- Official SDKs across seven languages (Node, Python, Ruby, PHP, Java, Go, .NET), a full test mode and a mature webhook system.
- Money-transmitter coverage under Connect that shifts compliance to Stripe in supported regions.
Pros:
- Best-in-class developer experience: documentation, SDK breadth and sandbox are repeatedly cited as the benchmark, giving the fastest ramp on this list.
- Broad card acceptance and Connect primitives: strong for marketplaces charging global customers.
- Compliance offload in supported regions: the money-transmitter licence handles a lot for US and European platforms.
Cons:
- Account freezes and rolling reserves: merchant reports of held funds under review, with rolling reserves and extended holds, are widely documented.
- India is invite-only and card-only: there is no self-serve signup, no SWIFT or bank-transfer collection, and the international option requires an Importer-Exporter Code and purpose codes.
- FIRC is not automatic: Stripe provides a payment advice, not a bank-issued FIRC, so the formal certificate still comes from your bank on request.
- Cross-border Connect payouts exclude India-based platforms: these require a platform based in the US, UK, EEA, Canada or Switzerland, so a foreign entity is the practical route.
Verdict: superb for global card checkout, but a poor match for an Indian business that needs compliant INR collection. See the wider Stripe alternatives for India-fit options.
8. Currencycloud
Best for: fintechs, banks and FX brokers building their own multi-currency product on top of a ready-made engine.
Currencycloud is a Visa-owned embedded API that provides cross-border money movement as three composable modules: Collect, Convert and Pay. It is business-to-business-to-customer infrastructure, meant to sit under someone else's brand rather than face an end merchant.
Key features:
- Collect, Convert, Pay and Manage across 33-plus currencies to 180-plus countries.
- Named multi-currency virtual collection accounts in the US, UK, Canada and Europe.
- Wholesale, interbank FX across hundreds of pairs.
- REST API version 2 with official SDKs in JavaScript, Python, Ruby, PHP, Java and .NET, plus a demo sandbox.
Pros:
- One API to collect, convert and pay: strong primitives for a fintech embedding cross-border money movement.
- Visa backing and multi-region licences: regulatory coverage across the UK, EU, US, Canada, Australia and Singapore.
- Good SDK coverage: six official languages ease the build versus REST-only options.
Cons:
- Quote-only pricing: no published rates, so evaluation needs a sales process.
- Not for direct merchants: you consume it through a partner or by building your own product, a point of confusion in reviews, and its public review base is thin and skewed to partner end-users.
- No direct India service: it serves Indian businesses only through licensed partners, for example powering Skydo, and holds no RBI PA-CB licence.
Verdict: a capable engine for builders, not a product an Indian business collects on directly.
Payouts versus collections: which API for which job
The quickest way to choose is to name the direction you are moving money, then match it to the tool.
- You collect foreign payments into India and settle INR: start with Xflow or Cashfree for full RBI PA-CB coverage and automatic eFIRA, or Payoneer if a receiving account plus payout in one is enough and you accept the FX markup.
- You pay out to beneficiaries across many countries: Nium and Airwallex have the deepest payout reach, and Wise Platform leads on transparent FX. For emerging-market payouts to mobile wallets, Thunes, Rapyd and Tipalti go deeper still.
- You mainly charge global customers by card: Stripe is the developer-experience benchmark, with the India limits noted above.
- You are building your own cross-border product to resell: Currencycloud and Xflow for Platforms both offer white-label building blocks, so weigh direction and India compliance.
If your product needs both directions, treat them as two integrations with different compliance surfaces. The inward leg into India carries the RBI reporting; the outward leg carries different rules. There is also a guide on monetizing cross border payments via api as a platform, by adding your own fee model on top.
Collections and payouts are not the same integration
Receiving money into India triggers RBI reporting, purpose codes and eFIRA that a payout API never touches. If a provider is built for the send side, expect to carry the India paperwork yourself.
How an international payment API works
An international payment API turns a bank workflow into a request and a response. You authenticate once, create an account object, then listen for events as money arrives. Most cross-border payment APIs on the receive side follow the same four stages.
- Authenticate: you call the API with a key or OAuth token over HTTPS, and each request is signed so the provider knows the call is yours.
- Provision a receiving account: the API returns account details, for example a USD account number and routing number or an IBAN, that a foreign payer can send to.
- Get notified by webhook: an event fires when a credit hits that account, carrying the amount, currency, sender reference and purpose code.
- Settle and reconcile: the provider converts the foreign currency and settles INR to your registered Indian bank account, with a data record you match against your ledger.
The idea is that your code never touches the correspondent-banking plumbing. You work with clean JSON while the payment API for developers handles FX conversion, banking partners and regulatory reporting underneath. The Xflow integration example above shows this lifecycle end to end, and the event-driven pattern behind those callbacks is covered in the guide on an api first payment platform.
How currency conversion and compliance work for India
This is where India-inward APIs differ sharply from generic global-payout tools. Receiving foreign money into India triggers RBI reporting that a payout API never touches, and a compliant receiving API bakes that paperwork into the flow.
- Purpose codes: each credit is tagged with an RBI purpose code, for example P0802 for software services, which classifies why the money came in.
- eFIRA: a Foreign Inward Remittance Advice is auto-issued as proof of receipt, so GST refunds and export records stay clean.
- KYB and screening: sender and beneficiary checks run before funds settle.
- FIRC continuity: the downstream certificate workflow through your AD-1 bank is unchanged, and you can read how firc works with vostro payments.
The receiving account your customer pays into is a ring-fenced routing account issued through the banking partner, not a foreign account your business owns abroad. It exists only to book the FX and route funds to your pre-registered Indian bank account. Handled this way, compliance becomes relief rather than a checklist you carry alone.
"Xflow has supported us not just when we qualified for it, but when we needed it. That's rare to find."
Neeraj Krishnamoorthy, Director & Co-Founder, TeachEdison
How to evaluate a cross-border payment API
A smooth payment API integration comes down to more than the feature list; the day-to-day experience decides how fast you ship and how little breaks in production. Weigh these before committing.
| Criterion | What to check | Why it matters |
|---|---|---|
| Direction fit | Collect, payout, or both, done well | Avoids a costly re-integration |
| Docs quality | Clear reference, examples, error codes | Cuts integration time |
| Sandbox | Full test environment with fake credits | Lets you test webhooks safely |
| SDKs | Libraries in your stack's languages | Fewer wrappers to maintain |
| Webhooks | Signed, retried, idempotent | Reliable event handling |
| Compliance in flow | Purpose code, eFIRA, KYB | Less manual paperwork |
| Settlement speed | T+1 or slower | Cash-flow predictability |
| Pricing transparency | Rate basis stated, mid-market versus interbank | No hidden FX leak |
For a marketplace, the ability to open sub-accounts per seller and monetise with your own fee model matters as much as raw uptime. That white-label and revenue-share angle sits in the guide on how to add global payments capabilities to your platform business. If you are still comparing categories, the international payment gateways roundup and the wider payment APIs guide cover more options.
The bottom line
The best international money transfer API depends on the direction you are moving money. For global payouts, the reach of Nium, Airwallex and Wise Platform is hard to beat. For a developer who needs to collect cross-border payments and have the compliance handled in code, Xflow is the pick we would start with: a clean REST API, receiving accounts and webhooks, transparent mid-market FX, and a full PA-CB licence with auto eFIRA and next-business-day settlement.
Frequently asked questions
There is no single best. For paying out globally, Nium, Airwallex and Wise Platform lead. For collecting into India with RBI compliance in the flow, Xflow and Cashfree lead, because they hold full PA-CB authorisation and auto-issue eFIRA.
Xflow and Cashfree are built for it, both with full RBI PA-CB licences, automatic eFIRA and INR settlement. Payoneer works for freelancers who accept a roughly 2% FX markup and can download FIRC themselves.
Only by card, and only by invite. Stripe does not offer SWIFT or bank-transfer collection into India, requires an IEC and purpose codes, and does not auto-issue a bank FIRC, so many Indian businesses use an India-native API instead.
A gateway typically authorises card checkouts. A cross-border payment API provisions multi-currency accounts, receives funds, settles across currencies and returns reconciliation data, a broader job than card authorisation alone.
Yes, with a compliant receiving API. It auto-issues eFIRA and tags purpose codes, and the downstream FIRC workflow through your AD-1 bank is unchanged, so your export and GST records stay intact.
No. It is a ring-fenced routing account issued through the banking partner, used only to book FX and route funds to your pre-registered Indian bank account. It does not earn interest and money cannot move elsewhere.
A transparent API converts at the live mid-market rate and states its markup, unlike banks that mark up a hidden interbank rate. You can verify the rate against public FX references before you settle.
Both hold full PA-CB licences and auto-issue FIRA. Xflow settles at the mid-market rate with plan-based pricing and imports live; Cashfree pairs international collection with its domestic stack. Test both sandboxes against your corridor and ticket size.
