🇬🇭 Sending to Ghana¶
GH · GHA · +233 · West Africa
National format SWIFT BIC required
← Back to Country-specific guides
Required information¶
For your end users
Ghana: Wires are typically routed in USD by US-side providers - sending in GHS may be rejected as a routing matter even though Bank of Ghana doesn't formally require USD.
Real-Time Alternative
GhIPSS Instant Pay (GIP)
Last reviewed by GIB compliance on 2026-05-21. Reference material only.
-
Currency
-
Typical settlement
1-2 business days typical; longer for cross-border with FX or compliance review.
-
SWIFT BIC
Required
-
Local clearing
GIS / GhIPSS
Account format¶
How beneficiary account numbers are structured for Ghana. Failure to match this format is the single most common reason wires are rejected at the destination.
| Field | Value |
|---|---|
| Format tier | National format |
| Length | 8-10 digits typical; no IBAN |
Routing identifiers¶
Which routing codes the wire-creation API call must include for Ghana.
| Field | Value |
|---|---|
| SWIFT BIC | Required |
| Branch Code | Optional |
| Directory | ↗ Source |
| Local clearing | GIS / GhIPSS |
Address format¶
How Ghana expects the beneficiary address to appear on the wire. Free-form variations frequently trigger compliance holds.
- Full name of addressee
- Street name + house or apt number
- City/locality + postal code
- District
- Region (all caps)
- Country (all caps)
- Phone number
| Field | Value |
|---|---|
| Postal code | Optional — this country has no postal code format |
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 Ghana, 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.
Providing an economic reason for the payment helps avoid delays.
Operational notes¶
| Field | Value |
|---|---|
| Currencies accepted | GHS, USD |
| Typical settlement | 1-2 business days typical; longer for cross-border with FX or compliance review. |
| Banking holidays | ↗ Calendar |
Known issues:
- Branch code is recommended to prevent payment delays.
- USD is a market convention for incoming wires (it's how most US-side providers route them) - not a Bank of Ghana FX requirement. Beneficiary banks will typically convert to GHS on receipt.
Common rejection reasons¶
Documented patterns that cause this country's banks to return wires. Universal reasons (sanctions holds, missing BIC) aren't repeated here.
Wire sent in GHS rather than USD - most US-side providers route only USD into Ghana as a routing convention (not a Bank of Ghana FX rule).
Missing branch code (recommended to prevent delays).
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.
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.