| Country | Currency | Account ID Format | Routing Code | Extra Required Fields |
|---|---|---|---|---|
| India | INR | 10–18 digit account number | IFSC code (11 chars, e.g. HDFC0001234) | Account holder name, bank branch name |
| Nigeria | NGN | 10-digit NUBAN account number | Bank code (3 digits) or SWIFT/BIC | Account holder name must match BVN exactly |
| Mexico | MXN | 18-digit CLABE number | CLABE encodes bank + branch (no separate code needed) | Full legal name, RFC tax ID optional |
| Philippines | PHP | Account number (varies by bank) | SWIFT/BIC code | Bank branch address for SWIFT; InstaPay alias for local |
| Europe (SEPA zone) | EUR | IBAN (15–34 chars, starts with country code) | BIC/SWIFT (8 or 11 chars) | Full name, billing address for some banks |
| United Kingdom | GBP | 8-digit account number | 6-digit sort code (e.g. 20-00-00) | Full legal name, bank name |
| Ghana | GHS | 13-digit account number | SWIFT/BIC code | Bank branch name, account holder name |
| Kenya | KES | M-Pesa: phone number / Bank: account number | SWIFT/BIC for bank; none for M-Pesa | For M-Pesa: registered phone number and full name |
| Colombia | COP | Account number (varies) | NIT (tax ID) + SWIFT/BIC | Account type (savings/checking), bank name |
| Brazil | BRL | Agency number + account number | CPF (individual tax ID, 11 digits) | Bank code (3 digits, e.g. 001 for Banco do Brasil), PIX key optional |
| Indonesia | IDR | 10–16 digit account number | Bank code or SWIFT/BIC | Account holder name, bank branch |
| South Africa | ZAR | Account number (varies) | 6-digit branch code or SWIFT/BIC | Account type (cheque/savings), bank name |
| United Arab Emirates | AED | IBAN (23 chars, starts with AE) | SWIFT/BIC code | Full name, bank name, branch address |
30% — of failed international transfers are caused by incorrect account details
| Transfer Method | Recipient Details Needed | Risk of Detail Error |
|---|---|---|
| Bank wire (SWIFT) | Full name, SWIFT/BIC, account number, bank address, branch code | High — errors trigger returns with fees |
| Wise | Full name, local routing code (IFSC/sort code/routing number), account number | Medium — Wise validates format before sending |
| Remitly / WorldRemit | Full name, account number, bank name, routing code | Medium — platform validates at entry |
| USDC via crypto off-ramp | Recipient's verified exchange account (email/username) + their bank linked to exchange | Low — off-ramp exchange handles final deposit |
| M-Pesa (Kenya) | Safaricom phone number + registered full name | Low — phone number format is validated instantly |
You need: recipient's full legal name (as on their bank account), their bank account number (10–18 digits), the bank's IFSC code (11-character code found on cheque books and bank statements, e.g. HDFC0001234), and the bank name. For transfers via Wise, these four fields are sufficient. For SWIFT bank wires, you also need the bank's SWIFT/BIC code and branch address.
A CLABE (Clave Bancaria Estandarizada) is an 18-digit standardized bank account number used for all electronic transfers in Mexico. It encodes the bank, city, and account — no separate routing code is needed. Your recipient can find their CLABE in their mobile banking app under account details, on a bank statement, or by asking their bank. Entering even one wrong digit will cause the transfer to fail or go to the wrong account.
Yes, for several corridors. In Kenya, recipients can receive via M-Pesa using just their phone number. In the Philippines, recipients can receive via GCash or PayMaya with a registered mobile number. In Mexico, OXXO cash pickup via Remitly or Western Union requires only a national ID. For crypto corridors, recipients need a verified account on a local exchange (Quidax for Nigeria, CoinDCX for India) to off-ramp to cash or mobile money — but not a traditional bank account.
The outcome depends on the error type. A wrong account number or IBAN causes the transfer to be rejected and returned — typically within 1–5 business days, with a return fee of $15–35 deducted. A name mismatch may cause a compliance hold requiring manual review (1–3 business days). In rare cases where wrong-but-valid details route to a real account, recovering the funds requires a formal recall process that can take weeks. Always verify details with your recipient before sending.
Usually no, for personal transfers. Exceptions: Brazil requires the recipient's CPF (11-digit tax ID) for bank deposits above certain amounts — your recipient can find this on their CPF card or government app. Colombia requires NIT for business recipients. Mexico's RFC is optional for personal transfers. For most other corridors (India, Nigeria, Philippines, UK, Europe), no tax ID is required from the recipient.
Compare live rates across 370+ corridors on RemitRoutes · methodology.