Wealth DeskplusEnterprise Wealth Tech
Comparison

Airwallex vs Nium vs Rapyd: Which Cross-Border Platform Fits Your Payment Flows?

Airwallex, Nium and Rapyd all move money across borders, but they're built for different flows. Here's how licensing, collection accounts, FX markup and API depth decide which one fits your volume.

By the Wealth Deskplus editorial team · November 2026 · 11 min read

Three Platforms, Three Different Centers of Gravity

If you're shortlisting cross-border infrastructure in 2026, Airwallex, Nium and Rapyd will probably all make the list. All three expose a cross-border payment API, all three claim payout reach across a large number of countries, and all three say they serve platforms, enterprises and financial institutions. The overlap on paper hides real differences. Picking the wrong one tends to surface months after go-live as FX leakage, failed payouts in a corridor you assumed was covered, or a compliance review that stalls a new market launch.

The short version of Airwallex vs Nium: Airwallex started from the business account and grew outward into payouts, cards, spend management and acquiring. Nium started as a payout and card-issuing rail sold mostly to other businesses and banks, which build their own customer-facing products on top. Rapyd is different again. It's strongest at collecting money through local payment methods (bank transfers, e-wallets, cash vouchers, local cards) and then disbursing it, which is why it appears so often in marketplace and gig-economy evaluations.

Advertisement

This isn't a ranking. The comparison covers the five things that separate these vendors in procurement: licensing footprint, corridor coverage, local collection accounts, FX markup structure and API maturity. It ends with separate verdicts for marketplaces, payroll and expense platforms, and banks that want a white-label payout rail.

One caveat applies throughout. Licenses, corridors and product availability change often, and what a vendor can offer depends on where your entity is incorporated and where your end customers sit. Treat what follows as a due-diligence framework and get current, written confirmation from each vendor.

Licensing Footprint: Who Actually Holds Your Funds, and Where

Licensing determines three things buyers underweight: which entity contracts with you, how customer funds are safeguarded, and how fast you can open a new market. A platform with its own license in a country can usually onboard local customers and hold local funds without a sponsor bank in the middle. Where it relies on partners, expect longer onboarding, more compliance questionnaires and less control when something breaks.

All three vendors operate under regulatory permissions in major financial centers such as the UK, the EU and Singapore, and hold US money transmission coverage in at least some states. Beyond that core, the footprints diverge, and they change over time, so verify each item below directly.

DimensionAirwallexNiumRapyd
Historical home marketsAustralia, Hong Kong, SingaporeSingapore, with deep APAC and India rootsIsrael and UK, strong in Europe and LATAM
Licensing approachOwn licenses across APAC, UK, EU and North America; confirm current status in China and JapanSays it holds licenses or registrations across dozens of jurisdictions, built to support B2B2X clientsEU/UK e-money permissions plus acquiring capability; leans on local partner networks for many payment methods
Typical contracting entityRegional Airwallex entity matched to your incorporationRegional Nium entity; confirm which one for your use caseRegional Rapyd entity, often EU or UK for international merchants
What to verifyWhether your entity type and country are supported for Global AccountsWhich corridors run on Nium's own licenses versus partner banksWhich local methods are processed directly versus through third-party aggregators

Safeguarding questions should differ by region. In the UK and EU, ask which safeguarding method the e-money entity uses (segregated accounts or insurance) and at which credit institutions. In Singapore, ask how funds are protected under the Payment Services Act framework. In Australia, Hong Kong and North America, ask the same question in local terms. In India, cross-border flows run through RBI frameworks with purpose codes and documentation requirements, so ask which Indian entity or bank partner handles inward and outward remittances. In the Gulf and Africa, coverage often depends on local bank partners, and payout speed varies widely by country.

Red flag: a sales team that says "yes, we cover that market" but can't name the licensed entity or partner bank that will settle the payment. Get it in writing before contract.

Corridor Coverage and Multi-Currency Accounts for Business

Headline country counts tell you little. What matters is how many corridors pay out through local rails (domestic clearing like Faster Payments, SEPA, NPP, FAST, IMPS, PIX, SPEI) versus how many fall back to SWIFT. Local payouts usually settle the same day or the next, cost a fraction of a wire, and avoid surprise intermediary deductions. SWIFT fallback is slower, pricier and harder to reconcile.

Payout reach

Nium has built its brand on payout reach and speed, and its pitch to payroll providers, remittance companies and banks rests on fast local payouts across many countries, including hard-to-reach Asian corridors. Airwallex's payout network is also broad, especially across APAC, the UK, Europe and North America. Rapyd's disbursement product covers bank accounts, cards and e-wallets, and it's strongest where recipients prefer non-bank methods. That matters in parts of Latin America, Southeast Asia and Africa, where many gig workers and sellers would rather be paid to a wallet than a bank account.

Local collection accounts

This is where the three differ most. Airwallex is the strongest of the three on multi-currency accounts for business. Its Global Accounts give you local account details in a range of currencies, so a customer in the UK, euro area, Australia, Singapore, Hong Kong or elsewhere can pay you by domestic transfer. For a SaaS company or exporter collecting B2B invoices in several currencies, that's often the deciding feature.

Nium offers virtual accounts for collection, generally in a narrower set of major currencies. That's fine when collection supports payouts (funding a payroll run, say), but thin if collection is your main use case. Rapyd approaches collection differently: instead of named account details for B2B transfers, it gives you access to hundreds of local payment methods so consumers or small merchants can pay the way they normally do. That's stronger for checkout-style collection and weaker for invoice-based B2B receivables.

Practical test: list your top 10 pay-in and top 10 pay-out corridors by volume, then ask each vendor to mark every one as local rail, SWIFT or partner-routed, with typical settlement time and cut-off. Two vendors that look identical on the brochure often differ on several of your top corridors.

FX Markup Structure and What a Payment Really Costs

On cross-border volume, FX margin usually costs more than per-transaction fees, yet buyers negotiate it least. All three vendors price FX as a markup over a reference or interbank rate. They differ in how the markup is set and shown to you.

Airwallex publishes standard pricing for its business account in many markets, with a stated FX markup on major currencies and tiered plans in some regions; platform and enterprise deals are negotiated. Nium and Rapyd mostly sell on custom contracts, so the markup depends on your volume, corridor mix and share of exotic currencies. These are typical 2026 market ranges. They vary by contract, so confirm with each vendor:

  • FX markup, major currency pairs: around 0.2% to 0.6% above mid-market for platforms with meaningful volume; 0.5% to 1.0% or more on standard self-serve pricing.
  • FX markup, emerging or restricted currencies: often 1% to 3%, sometimes more where liquidity is thin or capital controls apply.
  • Local payout fees: roughly $0.20 to $3 per payout, depending on rail and volume tier.
  • SWIFT payouts: roughly $8 to $30 per wire, plus possible intermediary deductions unless you pay for full-amount delivery.
  • Platform minimums: enterprise and white-label contracts commonly carry monthly minimums from a few thousand dollars to $25,000 or more.

Worked example (hypothetical)

Say a marketplace pays 6,000 sellers a month, $5 million in total, with half requiring conversion out of USD. On $2.5 million converted, a 0.35% markup costs $8,750 a month. At 0.8% it's $20,000. That $11,250 monthly gap is $135,000 a year, far more than any difference in per-payout fees. If 5,500 payouts go via local rails at $0.60 and 500 via SWIFT at $15, payout fees total about $10,800. Same order of magnitude as the FX line, but it's the markup that moves the total.

Three structural questions matter more than the headline rate:

  1. Is the markup fixed, tiered or dynamic? A fixed basis-point markup over a named reference rate is auditable. A "competitive rate" quoted at the time of the trade isn't.
  2. Can you lock rates? Marketplaces that quote sellers in local currency need a rate-lock or quote-validity window. Ask for the duration and any fee.
  3. Who absorbs FX on refunds and reversals? Round-trip conversion on refunds can quietly double your FX cost on that flow.

API Maturity, Onboarding Effort and Integration Red Flags

All three are API-first, with sandboxes, webhooks and SDKs. The differences show up in data model design and in how much compliance burden the platform carries for you.

Airwallex offers a documented REST API, and its platform product (connected accounts for your end customers) suits software companies that want to embed accounts, cards and payouts under their own brand. Because the business account came first, some platform capabilities can feel layered onto that core model, particularly around sub-account structures. Test those edge cases in the sandbox before committing.

Nium is built for B2B2X. Its APIs center on onboarding your end users (KYC/KYB), wallets, payouts and card issuing, and its model expects you to be a regulated or semi-regulated platform serving your own customers. That suits banks and payroll providers. Integration work is real, though, and you'll need engineering and compliance capacity to run it well.

Rapyd exposes a large surface area: collection across many local methods, disbursements, wallets, issuing and checkout. That breadth is its advantage, but it also means more integration paths to choose from, and behavior can vary across payment methods sourced through different local partners. Budget time for method-by-method testing in your priority markets.

Due-diligence checklist

  • Idempotency on payout creation, so retries can't double-pay.
  • Webhook delivery guarantees, retry policy and event ordering.
  • Payout status granularity: can you tell "sent to rail" from "credited to beneficiary"?
  • Beneficiary validation before submission (account name matching, IBAN checks, local format rules).
  • Reconciliation reporting: per-payout FX rate, fees and reference IDs in a machine-readable export.
  • Who owns end-customer KYC/KYB, and what happens to your users' accounts if the vendor tightens its risk appetite.

Red flags: sandbox behavior that doesn't match production in your key corridors; no named technical contact for platform contracts; a vague answer on which risk categories (crypto-adjacent, adult, gaming, high-risk MCCs) can trigger offboarding; and status codes that lump "returned" and "failed" together.

Verdicts for Marketplaces, Payroll and Expense Platforms, and Banks

Marketplaces and platforms paying sellers or creators

Start with Rapyd vs Airwallex, and let the shape of your pay-ins decide. If buyers pay through local methods (wallets, bank transfer apps, cash vouchers, local cards) across Latin America, Southeast Asia, the Middle East or Africa, and sellers want wallet payouts, Rapyd's breadth of local methods is hard to match. If your marketplace is mostly B2B, collects by bank transfer or card in major currencies, and needs sellers to hold multi-currency balances, Airwallex is usually the better fit because its collection accounts and embedded account model do more of the work. If pay-ins are already handled by your existing acquirer and you need a payouts platform, add Nium to the evaluation; its payout reach may beat both in your top corridors.

Payroll, EOR and expense management platforms

For most payroll and employer-of-record providers, Nium is the first platform to evaluate. The work is high-volume, deadline-critical payouts to individual bank accounts in many countries, and Nium's B2B2X design, payout focus and card issuing line up with that job. Expense and spend-management platforms are a closer call on Airwallex vs Nium. If you need multi-currency accounts for business customers, virtual and physical cards, and reimbursements in one embedded stack, Airwallex covers more of the product surface out of the box. If cards and payouts matter most and your customers already bank elsewhere, Nium is the leaner choice. Rapyd is a credible third option for payroll where workers expect wallet payouts.

Banks and regulated institutions wanting a white-label payout rail

Banks, credit unions, building societies and remittance operators that want to offer international payments under their own brand usually fit Nium best. Its model assumes you own the customer relationship and front end, while it supplies the licensed payout network, FX and compliance tooling underneath. Airwallex can serve institutional and embedded use cases, but its product and brand lean toward businesses using it directly or through software platforms. Rapyd fits banks mainly when the goal is acquiring or local collection rather than outbound remittance.

Decision rule

Classify your flow before you talk to sales. If more than half your value is collection through local methods, lead with Rapyd. If it's B2B receivables plus multi-currency balances, lead with Airwallex. If it's outbound payouts under your own brand, lead with Nium. Then request a corridor-by-corridor quote on your top 10 flows, run it through the FX worked example above, and sign with the vendor that wins on effective all-in cost, not headline country count. Have legal and compliance advisers in each operating jurisdiction review the contracting entity and safeguarding terms before you commit.

Quick answers

Can we use more than one of these platforms at the same time?

Yes, and many larger platforms do, routing each corridor to whichever vendor offers the best local rail and FX. The trade-off is engineering effort: you'll need an abstraction layer, separate reconciliation and multiple compliance relationships. For volumes under a few million dollars a month, a single primary provider with a backup contract is usually simpler.

How much can we realistically negotiate the FX markup down?

It depends mainly on monthly converted volume, corridor mix and how predictable your flows are. Platforms converting several million dollars a month in major currencies commonly negotiate toward the lower end of the 0.2% to 0.6% range, while exotic currencies stay higher. These are typical 2026 market ranges that vary by contract, so get quotes from every vendor on your actual corridor mix.

Do these platforms handle KYC on our end customers, or do we?

It varies by product and contract. With embedded or connected-account products, the vendor typically runs or supervises KYC/KYB on your users, sometimes with you collecting the data. In white-label bank arrangements, the institution often keeps more of that responsibility. Agree on the split in writing and have compliance counsel in your jurisdictions review it, because the split determines your regulatory exposure.

Written by the Wealth Deskplus editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.