🇹🇬 Sending to Togo¶
TG · TGO · +228 · WAEMU
IBAN optional SWIFT BIC required
← Back to Country-specific guides
Required information¶
For your end users
WAEMU country: payments > 5M XOF must be deposited at a local authorized intermediary. Payments > 100M XOF require BCEAO central-bank approval - expect documentation delays.
Last reviewed by GIB compliance on 2026-05-20. Reference material only.
-
Currency
-
Typical settlement
1-2 business days under 5M XOF; 5+ days for amounts requiring BCEAO approval (>100M XOF).
-
SWIFT BIC
Required
-
Local clearing
STAR-UEMOA / SICA-UEMOA (BCEAO)
Account format¶
How beneficiary account numbers are structured for Togo. 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 | 24 characters (TG + 22); IBAN form is 28 alphanumeric |
| Validation regex | ^TG[0-9A-Za-z]{8}[0-9]{14}$ |
| Example | TG1234567890123456789012 |
IBAN Composition
| Component | Length | Example |
|---|---|---|
| Country Code | 2 | TG |
| Check Digits | 2 | 12 |
| Bank Code | 5 | TG345 |
| Branch Code | 5 | 67891 |
| Account Number | 12 | 234567891234 |
| National Code | 2 | 56 |
Routing identifiers¶
Which routing codes the wire-creation API call must include for Togo.
| Field | Value |
|---|---|
| SWIFT BIC | Required |
| Branch identifier | Required |
| None | Optional |
| Local clearing | STAR-UEMOA / SICA-UEMOA (BCEAO) |
Address format¶
How Togo expects the beneficiary address to appear on the wire. Free-form variations frequently trigger compliance holds.
- Recipient Full Name
- Street name and building number
- City or town
- Country (all caps)
| Field | Value |
|---|---|
| Postal code | Optional — this country has no postal code format |
| Example | John Doe Avenue De Ln 5 Lomé TGO |
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.
Recommended:
- Beneficiary phone number (
Cdtr/CtctDtls/PhneNb)
Purpose of payment¶
Put the purpose in the remittance information (<RmtInf><Ustrd>) of the ISO 20022 wire-creation request, as the code format below describes.
Requirement: Highly recommended
GIB check: a missing or unexpected purpose is reported as a validation warning; the wire is not held.
Not yet confirmed
We have not yet confirmed this country's purpose-of-payment requirement against a central-bank or correspondent-bank source. Including a purpose is recommended. We update these guides as we confirm each country.
Non-standard element
For Togo, the purpose is placed in <RmtInf> (remittance info), not the standard <Purp> element.
| Field | Value |
|---|---|
| Code format | Free-text purpose in words (no code list) |
| Authoritative source | ↗ View source |
Remittance info¶
Extra content the regulator requires inside the free-text remittance field, beyond the purpose-of-payment code.
Beneficiary name match must be exact; initials trigger return.
Compliance triggers¶
Beneficiary tax-ID requirements and rules that activate at certain payment amounts.
| Trigger | Requirement |
|---|---|
| Residency restrictions | Beneficiary must be an onshore resident. |
Operational notes¶
| Field | Value |
|---|---|
| FX minimum (USD) | $100 |
| Currencies accepted | XOF |
| Typical settlement | 1-2 business days under 5M XOF; 5+ days for amounts requiring BCEAO approval (>100M XOF). |
| Banking holidays | ↗ Calendar |
Known issues:
- Not registered in the SWIFT IBAN Registry. The 'TG + 22-char' format is a national BBAN with a country prefix, not a true IBAN - MOD-97 IBAN check-digit validation will not apply.
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 supporting documentation for payments > 100M XOF - BCEAO central-bank approval required and not obtained.
Beneficiary not declared at a local authorized intermediary for payments > 5M XOF.
Missing economic-reason purpose statement.
Beneficiary not an onshore resident.
Beneficiary name mismatch.
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: ^TG[0-9A-Za-z]{8}[0-9]{14}$ · 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.