🇧🇷 Sending to Brazil¶
BR · BRA · +55 · South America
IBAN optional SWIFT BIC required
← Back to Country-specific guides
Required information¶
For your end users
Brazil: An 11-digit CPF (individual) or 14-digit CNPJ (corporate) is mandatory for FX wires, plus phone and email on the counterparty record.
Real-Time Alternative
PIX (Banco Central)
Last reviewed by GIB compliance on 2026-05-19. Reference material only.
-
Currency
-
Typical settlement
1-2 business days; FX-control reporting can extend by 1 day.
-
SWIFT BIC
Required
-
Local clearing
STR / SPI / SITRAF
Account format¶
How beneficiary account numbers are structured for Brazil. Failure to match this format is the single most common reason wires are rejected at the destination.
| Field | Value |
|---|---|
| Format tier | IBAN optional (recommended) |
| Length | 29 characters (BR + 27) |
| Validation regex | ^BR[0-9]{2}[0-9]{8}[0-9]{5}[0-9]{10}[A-Z][0-9A-Za-z]$ |
| Example | BR1800360305000010009795493C1 |
Routing identifiers¶
Which routing codes the wire-creation API call must include for Brazil.
| Field | Value |
|---|---|
| SWIFT BIC | Required |
| None | Optional |
| Local clearing | STR / SPI / SITRAF |
Counterparty fields¶
Party details the destination expects on the beneficiary. Mandatory fields are required by the destination; recommended fields reduce the chance of a delay or return.
Mandatory:
- Beneficiary phone number (
Cdtr/CtctDtls/PhneNb) - Beneficiary email address (
Cdtr/CtctDtls/EmailAdr) - Whether the beneficiary is a company or a person (
Cdtr/Id/OrgIdorCdtr/Id/PrvtId) - Beneficiary identifier, such as a tax or registration number (
Cdtr/Id/OrgId/Othr/IdorCdtr/Id/PrvtId/Othr/Id, withSchmeNm) — 11-digit CPF (individual) or 14-digit CNPJ (corporate/NGO/org) Scope: FX only
Purpose of payment¶
Put a code from the ISO 20022 list in <Purp><Cd> (purpose_code).
Requirement: ISO 20022 code required (confirmed)
GIB check: a missing or unexpected purpose is reported as a validation warning; the wire is not held.
Standard list applies
Brazil doesn't publish a country-specific PoP scheme. Use the ISO 20022 standard purpose codes.
| Field | Value |
|---|---|
| Source | ↗ BCB Resolution 277 |
Remittance info¶
Extra content the regulator requires inside the free-text remittance field, beyond the purpose-of-payment code.
Payment purpose must be clearly identified.
Operational notes¶
| Field | Value |
|---|---|
| FX minimum (USD) | $25 |
| Currencies accepted | BRL |
| Typical settlement | 1-2 business days; FX-control reporting can extend by 1 day. |
| Banking holidays | ↗ Calendar |
Common rejection reasons¶
Documented patterns that cause this country's banks to return wires. Universal reasons (sanctions holds, missing BIC) aren't repeated here.
Missing legal_id (11-digit CPF or 14-digit CNPJ).
Missing phone or email on counterparty record (required by regulator for FX wires).
Missing or unclear payment purpose.
Beneficiary name mismatch.
Sanctions or compliance hold.
Validate before you send¶
Check identifiers before you submit. The IBAN check runs in your browser (format plus the ISO 13616 MOD-97 check digit). GIB's API checks the IBAN format for countries where an IBAN is required. The BIC lookup searches GIB's BIC directory and needs a dashboard login.
IBAN check
Format: ^BR[0-9]{2}[0-9]{8}[0-9]{5}[0-9]{10}[A-Z][0-9A-Za-z]$ · MOD-97 (ISO 13616) check digit verified locally.
BIC lookup
Loading…
References¶
First-party sources — central banks, FX regulators, ISO registries. Always re-verify against these before pushing volume to a new corridor.
Disclaimer
These country guides aggregate information from central banks, regulators, and industry-standard references. Global Innovations Bank reviews them on a rolling cadence and notes the verification date on each page. Payment-corridor rules change between releases, so we cannot guarantee continued accuracy.
Always verify against the primary sources linked in the References section before going live in a new corridor. Re-check applicable sanctions lists (OFAC, EU, UK, UN consolidated, and any state-level requirements) at the time of payment, since designations shift between our refreshes.
For fintech partners on GIB's sponsor-bank rails, these guides do not replace your BSA/AML, KYC, sanctions-screening, or transaction-monitoring obligations under your program agreement with GIB.
Nothing in this material constitutes legal, tax, or regulatory advice, and wire-acceptance decisions remain at the discretion of GIB Compliance and the destination bank.