GuidesRecipesAPI ReferenceChangelog
Guides

B2B App Payout Corridors

Which currencies, countries, and rails does the B2B Payments App support?

Overview

A corridor is the combination of a currency and a country the platform can deliver money to. This page lists every supported corridor, the bank network ("rail") used for each, and any extra information that corridor requires.

ℹ️

When to use this page

Use this page to answer: "Can I pay someone in country X using currency Y from this app?"

Where corridors apply

The currencies and rails listed here determine what is available in:

  • The Add Payment Method form when adding a bank account on a Contact
  • The Send flow when picking the send currency
  • The Receive page when sharing bank deposit details

Supported corridors

ℹ️

Corridor-specific guides

Mexico, Colombia, the Dominican Republic, Kenya, and Nigeria each have detailed payout guides. See Related resources for links.

CurrencyCountryRail(s)Routing identifier
USD — US DollarUnited StatesACH, RTP, Wire9-digit ABA Routing Number
CAD — Canadian DollarCanadaEFT, Interac e-Transfer8 digits (5-digit transit + 3-digit institution)
MXN — Mexican PesoMexicoSPEI18-digit CLABE (replaces the account number)
COP — Colombian PesoColombiaPSE3-digit PSE bank code
DOP — Dominican PesoDominican RepublicLBTRSWIFT/BIC code, for example BPDODOSX
KES — Kenyan ShillingKenyaKEBANK, MPESASWIFT/BIC + account number; or MPESA phone number (E.164)
NGN — Nigerian NairaNigeriaNGBANK3-digit CBN bank code (preferred) or SWIFT/BIC + 10-digit NUBAN account number

Unavailable corridors

The following corridors are recognized by the platform but not currently enabled for payouts. The Add Payment Method form does not offer them.

CurrencyCountryStatus
INR — Indian RupeeIndiaNot currently available for payouts

Ask your administrator about when the corridor may be re-enabled.

Rail descriptions

  • ACH — standard US bank-to-bank, 1–3 business days. Lower cost, slower delivery.
  • RTP — US real-time payments, instant 24/7. Supported by fewer banks.
  • Wire — international bank wire. Faster than ACH but more expensive.
  • EFT — Canadian Electronic Funds Transfer (the Canadian equivalent of ACH).
  • Interac e-Transfer — Canadian email-based instant transfer.
  • SPEI — Mexican Sistema de Pagos Electrónicos Interbancarios. Real-time, settles in about 5 minutes.
  • PSE — Colombian Pagos Seguros en Línea.
  • LBTR — Dominican Liquidación Bruta en Tiempo Real (real-time gross settlement).
  • KEBANK — Kenyan interbank settlement network. Routes via SWIFT/BIC code.
  • MPESA — Kenyan mobile money network (M-Pesa). Routes via E.164 phone number.
  • NGBANK — Nigerian interbank settlement network. Routes via CBN bank code or SWIFT/BIC with a 10-digit NUBAN account number.

Corridor-specific requirements

Most corridors require only the standard fields (Currency, Rail, Nickname, Account Number, Routing identifier). A few corridors require additional inputs that the form prompts for.

Colombia (COP)

A Colombian Contact requires:

  • Email Address — required for COP payouts
  • Identification Number:
    • Individuals — Passport or Cédula de Ciudadanía
    • Businesses — NIT (tax identification number)
  • Account Type — Checking or Savings (required by the PSE rail)

Dominican Republic (DOP)

A Dominican Republic Contact requires:

  • Identification Number:
    • Individuals — Cédula (national identification number)
    • Businesses — RNC (tax identification number)
  • Account Type — Checking or Savings (required by the LBTR rail)

Mexico (MXN)

The CLABE is an 18-digit identifier that encodes bank, branch, and account in one number. The form does not prompt for a separate account number for MXN.

Kenya (KES)

Kenya payouts support two routes:

  • Bank account (KEBANK rail) — SWIFT/BIC code + bank account number
  • Mobile wallet (MPESA rail) — phone number in E.164 format (for example, +254712345678)

purpose_of_transaction is required for all KES payouts.

Nigeria (NGN)

Nigeria uses the NGBANK rail with NUBAN account numbers. Two routing formats are supported:

  • CBN bank code (preferred) — 3-digit Central Bank of Nigeria code + 10-digit NUBAN account number
  • SWIFT/BIC — standard SWIFT/BIC code + 10-digit NUBAN account number

When both routing details exist on the same account, the system prefers CBN routing. Configure only one routing method per account to avoid relying on this implicit preference.

Stablecoins

Stablecoins are not a corridor in the same sense — no countries are involved. The stablecoin assets the workspace can pay out and receive are set by platform configuration. Supported stablecoins include USDC, USDT, and others.

To check the stablecoins enabled for the workspace, open the Cryptocurrency dropdown in the Add Payment Method → Crypto Wallet form, or check the Wallets tab on the Receive page.

Notes

  • Workspace settings can be narrower than the full list above. The administrator controls which currencies and countries are enabled for the workspace. The list in the Add Payment Method form may be shorter than this table.
  • The form displays only valid combinations. Pairing a currency with an unsupported rail is not possible.
  • The wrong rail for the destination causes payment failure. Confirm the rail with the recipient if uncertain.
  • Some corridors enforce minimum and maximum amounts. Limits vary by rail and are not shown in the form. Contact your administrator if a payment is rejected for size.
  • For stablecoins, network matters as much as asset. Sending the correct stablecoin on the wrong network can lose funds permanently. Always copy the wallet address and confirm the network with the recipient.
  • A missing expected corridor is either not enabled on the workspace (ask your administrator) or not supported by the platform (check the table above).

Related resources