🇺🇸 Sending to United States of America¶
US · USA · +1 · North America
National format SWIFT BIC required
← Back to Country-specific guides
Required information¶
-
Account number
-
SWIFT BIC
-
ABA Routing Number
-
Purpose-of-payment code (strongly advised)
-
Beneficiary address
For your end users
Double-check the beneficiary's full name (no initials), account number, and bank SWIFT/BIC against what their bank has on file. International wires can take 1-5 business days and may be delayed by sanctions screening.
Real-Time Alternative
FedNow (Federal Reserve) / RTP (The Clearing House)
Last reviewed by GIB compliance on 2026-05-20. Reference material only.
-
Currency
-
Typical settlement
Same day (Fedwire) for USD; 1-2 days for international.
-
SWIFT BIC
Required
-
Local clearing
Fedwire (FedNow for instant) / CHIPS
Account format¶
How beneficiary account numbers are structured for United States of America. Failure to match this format is the single most common reason wires are rejected at the destination.
| Field | Value |
|---|---|
| Format tier | National format |
| Length | 6-17 digits depending on bank; no IBAN. |
Routing identifiers¶
Which routing codes the wire-creation API call must include for United States of America.
| Field | Value |
|---|---|
| SWIFT BIC | Required |
| ABA Routing Number | Required |
| Format | 9 digits (or 4-digit CHIPS participant code as alternative) |
| Directory | ↗ Source |
| Local clearing | Fedwire (FedNow for instant) / CHIPS |
Address format¶
How United States of America expects the beneficiary address to appear on the wire. Free-form variations frequently trigger compliance holds.
- Recipient's full name
- Building number and street address
- City, state, and ZIP Code
- Country
| Field | Value |
|---|---|
| Postal code | Optional — validated against the format below when provided |
| Postal code regex | ^\d{5}([\-]?\d{4})?$ |
| Postal example | 90210 |
| Example | John Doe 969 Cox Rd Gastonia, NC 28054-3455 USA |
Purpose of payment¶
Put a code from the ISO 20022 list in <Purp><Cd> (purpose_code).
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.
Remittance info¶
Extra content the regulator requires inside the free-text remittance field, beyond the purpose-of-payment code.
Use account number OR CHIPS Universal Identifier (UID) - 6 digits.
Operational notes¶
| Field | Value |
|---|---|
| Currencies accepted | USD |
| Typical settlement | Same day (Fedwire) for USD; 1-2 days for international. |
| Banking holidays | ↗ Calendar |
Known issues:
- Non-residents can hold in-country accounts.
- Beneficiary bank requires either ABA Routing Number (9 digits) or CHIPS participant code (4 digits).
Common rejection reasons¶
Documented patterns that cause this country's banks to return wires. Universal reasons (sanctions holds, missing BIC) aren't repeated here.
Wrong ABA Routing Number or CHIPS UID.
Beneficiary name truncated or mismatched.
Missing intermediary-bank instruction for non-USD wires.
Sanctions or compliance hold (OFAC).
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.