Skip to Content
Core ConceptsSupported Corridors & Currencies

Supported Corridors & Currencies

A corridor is a country plus a currency plus a direction: COP payins in Colombia, BOB payouts in Bolivia, MXN in both directions in Mexico. Each corridor runs over a specific local rail, and the rail is what determines how fast funds settle and which fields an order needs.

This page is the coverage reference. For how to actually build against a corridor, see Accepting Payments for payins and Paying Providers for payouts.


Coverage by Country

CountryCurrencyDirectionLocal railNotes
🇦🇷 ArgentinaARSPAYIN · PAYOUTNamed CVU (virtual account)Named accounts only, in both directions.
🇧🇴 BoliviaBOBPAYINQRWire payin in development.
🇧🇴 BoliviaBOBPAYOUTBank transferAll banks supported. If a destination bank is missing from our catalogue we add it.
🇧🇷 BrazilBRLPAYIN · PAYOUTPIXSettles in seconds.
🇨🇱 ChileCLPPAYINInstant bank transferPer-merchant virtual accounts in development.
🇨🇱 ChileCLPPAYOUTBulk payment fileEffectively instant. Batched, and split into parts for transactions above CLP 7,000,000.
🇨🇴 ColombiaCOPPAYINPSE
🇨🇴 ColombiaCOPPAYOUTACH Colombia, Bre-B, A2AACH is cycle-based; Bre-B settles in seconds. A2A in development (instant to some banks).
🇲🇽 MexicoMXNPAYIN · PAYOUTSPEI via virtual accounts
🇵🇪 PeruPENPAYINVirtual CCI for deposits; wire transfer or recaudo
🇵🇪 PeruUSDPAYINWire transfer or recaudo
🇵🇪 PeruPEN · USDPAYOUTWire transfer
🇺🇸 United StatesUSDPAYIN · PAYOUTNamed accounts; payouts by wire or ACHRequires separate KYB/KYC onboarding.
🇻🇪 VenezuelaVESPAYIN · PAYOUTBank transferRequires additional compliance checks.
🌐 Cross-borderMultiplePAYOUTCircle Payments Network / Tether T-0 — stablecoin settlement between institutions, local fiat delivered at destinationLive in Hong Kong, Singapore, the Philippines, India, Thailand, Japan and European markets.

Coverage as of the last update to this page. The live list of payin methods per country and currency is served by GET /api/v1/payment-method.

Direction uses the same vocabulary as the API: PAYIN is money coming in from a payer, PAYOUT is money going out to a bank account. See Orders & Order Types.


Coverage by Currency

The same coverage, framed by currency. These symbols are what you pass to originCurrencySymbol, destinationCurrencySymbol and currencySymbol in the API.

CurrencyNameCorridors
ARSArgentine peso🇦🇷 Argentina (PAYIN · PAYOUT)
BOBBoliviano🇧🇴 Bolivia (PAYIN · PAYOUT)
BRLBrazilian real🇧🇷 Brazil (PAYIN · PAYOUT)
CLPChilean peso🇨🇱 Chile (PAYIN · PAYOUT)
COPColombian peso🇨🇴 Colombia (PAYIN · PAYOUT)
MXNMexican peso🇲🇽 Mexico (PAYIN · PAYOUT)
PENPeruvian sol🇵🇪 Peru (PAYIN · PAYOUT)
USDUS dollar🇵🇪 Peru (PAYIN · PAYOUT) · 🇺🇸 United States (PAYIN · PAYOUT)
VESVenezuelan bolívar🇻🇪 Venezuela (PAYIN · PAYOUT)

Coverage as of the last update to this page. The live list of payin methods per country and currency is served by GET /api/v1/payment-method.

Crypto currencies are documented separately, since support there is defined by symbol and network — see Supported Networks for the valid pairs.


Checking Coverage at Runtime

The table above is the commercial view and is updated by hand. The API is the live source for which payin methods a corridor exposes right now, including per-method amount limits:

curl -X GET 'https://api-sandbox.koywe.com/api/v1/payment-method?countrySymbol=CO&currencySymbol=COP'

This endpoint is public — no authentication required. With the CLI:

koywe payment-methods list --country-symbol CO --currency-symbol COP

Each method comes back with its method code, responseType (QR, PAYMENT_LINK, PUSH_NOTIFICATION or BANK_TRANSFER), requiredFields and minAmount / maxAmount. Build your checkout from that response rather than hardcoding a method list — new rails appear without an API change.

Payment method details by country →


Reading the Table

Named accounts

In Argentina and the United States, funds move through accounts held in the payer’s or beneficiary’s own name. The account holder’s identity has to match, in both directions — an unnamed or third-party account is rejected by the rail, not by Koywe.

Virtual accounts

Argentina (CVU), Mexico (SPEI) and Peru (CCI) issue an account number per merchant that payers deposit into, so a payin arrives already attributed. See Virtual Accounts and Deposit Accounts.

Batched rails

Two corridors are not one-transfer-per-order:

  • Chile payouts go out in a bulk payment file. Settlement is effectively instant, but a single transaction above CLP 7,000,000 is split into parts.
  • Colombia ACH runs on settlement cycles rather than continuously. Bre-B, on the same corridor, settles in seconds.

Cross-border settlement

Payouts outside Latin America settle between institutions in stablecoin over the Circle Payments Network or Tether T-0, with local fiat delivered at the destination. Live markets are listed in the table above. This is an institutional corridor — talk to your Koywe contact before designing against it.

In development

Rails marked in development in the table are not callable yet. Do not build against them until they appear in the GET /payment-method response for that corridor.


Compliance Notes

United States requires a separate KYB/KYC onboarding from your Latin American merchants, and Venezuela requires additional compliance checks before a corridor is enabled. Neither is available by default — contact Koywe to have them enabled on your organization.

See Onboarding & KYB for what the process needs.


Next Steps

Last updated on