Destination coverage

Where payouts can go, and which payment methods get them there.

Jeeves payouts reach 190+ countries. Every corridor is defined by the beneficiary — their bankCountry, bankCurrency, and attached payment methods — and falls into one of two method families:

Payment method	What it means
`local_bank_transfer`	Delivery over the destination country's own clearing rail (SPEI, PIX, SEPA, ACH, Faster Payments, …) — typically faster and cheaper.
`wire`	International wire — the broad-reach fallback, available to the large majority of destinations.

All payment methods

A beneficiary's paymentMethods[].paymentMethod is one of the values below — bank rails and crypto networks alike. The crypto networks pay out to a wallet address on that network.

Group	`paymentMethod`	What it means
Bank rails	`ach`	United States ACH.
	`wire`	International wire.
	`swift`	SWIFT international transfer.
	`sepa`	SEPA, in the Eurozone.
	`faster-payments`	Faster Payments, in the United Kingdom.
	`pix`	PIX, in Brazil.
	`spei`	SPEI, in Mexico.
	`ted`	TED, in Brazil.
	`boleto`	Boleto, in Brazil.
	`rtgs`	Real-time gross settlement.
	`bank-transfer`	A generic bank transfer.
	`local-clearing`	A country-specific domestic clearing system with no dedicated value of its own.
Crypto networks	`ethereum`	Ethereum.
	`base`	Base.
	`solana`	Solana.
	`tron`	Tron.
	`polygon`	Polygon.
Other	`other`	A rail with no dedicated value.

Which of these a corridor offers is live configuration — check the beneficiary's attached methods, or ask GET /v1/beneficiary-schemas what a corridor accepts.

The same flow also makes domestic payments — same currency and country on both sides, e.g. paying a Mexican business in MXN via SPEI from your Mexican Jeeves account.

Coverage is live configuration, not a fixed list — corridors are added continuously, and the authoritative answer for any beneficiary is the paymentMethods attached to them (see Beneficiaries). Treat the tables below as a snapshot of flagship corridors, not the ceiling; to confirm a specific corridor, check the beneficiary's methods or ask your Jeeves contact.

Flagship local rails

Destination	Currency	Local rail
🇺🇸 United States	USD	ACH · Fedwire
🇲🇽 Mexico	MXN	SPEI
🇧🇷 Brazil	BRL	PIX · TED · Boleto
🇨🇴 Colombia	COP	Local bank transfer
🇨🇱 Chile	CLP	Local bank transfer
🇵🇪 Peru	PEN	Local bank transfer
🇦🇷 Argentina	ARS	Local bank transfer
🇪🇺 Eurozone	EUR	SEPA · SEPA Instant
🇬🇧 United Kingdom	GBP	Faster Payments
🇸🇬 Singapore	SGD	FAST · GIRO · MEPS
🇭🇰 Hong Kong	HKD	FPS · RTGS
🇸🇪 Sweden	SEK	RIX
🇩🇰 Denmark	DKK	Intraday clearing
🇨🇿 Czech Republic	CZK	CERTIS
🇦🇺 Australia	AUD	Local bank transfer

Local bank transfer — available destinations

Beyond the flagship rails, local_bank_transfer is live in roughly 50 countries, including:

Canada · Bolivia · Uruguay · Switzerland · Norway · Iceland · Israel · Türkiye · Morocco · South Africa · India · China · Japan · South Korea · Malaysia · Thailand · Philippines · Sri Lanka · Nepal · New Zealand — plus the Eurozone members individually (Austria, Belgium, Croatia, Cyprus, Estonia, Finland, France, Germany, Ireland, Latvia, Malta, Monaco, Netherlands, San Marino, Slovenia, Spain).

Wire — the broad-reach fallback

International wire reaches well over 100 countries across every region — Western and Eastern Europe, the GCC (UAE, Saudi Arabia, Qatar, Kuwait, Bahrain, Oman), Asia, Africa, and Latin America & the Caribbean — and is how most of the long tail of the 190+ destinations is served.

How to think about it as an integrator

Don't hardcode a coverage list. paymentMethod is intentionally an open string in the API, and corridors change without an API version bump.
The beneficiary is the source of truth. A beneficiary's attached paymentMethods are exactly what that corridor supports today.
Purpose codes vary by corridor — see the table in Send a payment.
Opening a new corridor (a country or method you don't see on your beneficiaries) is an onboarding conversation, not an API call — talk to your Jeeves contact.