Skip to main content

Overview

When you create a payment account (POST /v1/payment-accounts), the required bank-account fields depend on the destination currency and rail. This page is the field-by-field reference for every supported currency/rail so you know exactly what to send.
This page is a companion to Offramps with Transfers. Use it to build the externalFiatAccount object; the transfers guide covers the end-to-end quote → transfer flow.
Rail values are case-insensitive, but this reference uses the canonical lowercase form. Field requirements are validated end-to-end at account creation — a 400 response names the specific missing field, which is always the authority if this page and the API ever disagree.

Fields required for every rail

These apply to all currencies and rails unless noted otherwise: Use the tables below to find the rail-specific fields you must send in addition to the universal fields above.

Third-party accounts

Set thirdParty: true when you pay out to someone other than the account holder. On most rails this changes nothing — you send the same fields as a first-party account. Only the five rails below ask for extra beneficiary identification, and only the fields named on that row are required. Every other field in this section stays optional.

Rails with extra requirements

For an individual beneficiary, send these in addition to the rail’s normal fields from the tables further down: For a business beneficiary, the ID fields do not apply — only co_bre_b requires anything extra, and that is beneficiaryMsisdn alone.
These are additional to the rail’s own identifier, not a replacement for it. On co_mobile_wallet and co_bre_b, phoneNumber identifies the wallet you are paying, while beneficiaryMsisdn is the beneficiary’s own contact number — two separate fields that may hold different values. On ar_transfers_3 you still send taxNumber and accountNumber.

Field definitions

Definitions only — see the table above for which rails actually require these.
Send national identifiers digits-only, without separators — a Brazilian CPF goes as 31038403812, not 310.384.038-12.

North America

United States (USD)

Mexico (MXN)

Canada (CAD)

South America

Brazil (BRL)

Colombia (COP)

For co_bre_b, supply one of phoneNumber, email, or accountHandle.

Argentina (ARS)

Europe

Eurozone (EUR)

United Kingdom (GBP)

Africa

Egypt (EGP)

Kenya (KES)

Nigeria (NGN)

South Africa (ZAR)

Middle East

Saudi Arabia (SAR)

Asia-Pacific

India (INR)

Philippines (PHP)

Additional fields may be required depending on the transfer amount or specific compliance requirements. When in doubt, submit the request — a 400 response names any missing field. Contact your Rain representative for corridor-specific requirements.

Error Handling

Supported Fiat Currencies (Upon Request)

The following additional currencies are supported and available upon request:
Contact your Rain representative to enable the above rails for your tenant.