🇹🇷 Sending to Türkiye¶
TR · TUR · +90 · Western Asia
IBAN required SWIFT BIC required
← Back to Country-specific guides
Required information¶
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
FAST (TCMB)
Last reviewed by GIB compliance on 2026-05-20. 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
EFT (TCMB)
Account format¶
How beneficiary account numbers are structured for Türkiye. Failure to match this format is the single most common reason wires are rejected at the destination.
| Field | Value |
|---|---|
| Format tier | IBAN required |
| Length | 26 alphanumeric characters |
| Validation regex | ^TR[0-9]{2}[0-9]{5}[0-9][0-9A-Za-z]{16}$ |
| Example | TR330006100519786457841326 |
IBAN Composition
| Component | Length | Example |
|---|---|---|
| Country Code | 2 | TR |
| Check Digits | 2 | 98 |
| Bank Code | 5 | 71234 |
| National Code | 1 | 5 |
| Bank Account Number | 16 | 6789123456789123 |
Routing identifiers¶
Which routing codes the wire-creation API call must include for Türkiye.
| Field | Value |
|---|---|
| SWIFT BIC | Required |
| None | Optional |
| Local clearing | EFT (TCMB) |
Address format¶
How Türkiye expects the beneficiary address to appear on the wire. Free-form variations frequently trigger compliance holds.
- Full Name
- Neighborhood (Mahalle)
- Street Name + Building Number + Apartment (optional)
- Postal Code + City/Province
- TURKEY
| Field | Value |
|---|---|
| Postal code | Optional — this country has no postal code format |
| Example | Ahmet Yilmaz Çankaya Mahallesi Istiklal Caddesi No: 45 D: 3 06540 Ankara TURKEY |
Purpose of payment¶
Put the country's own code in <Purp><Prtry> (purpose_code_proprietary).
Requirement: Mandatory (confirmed)
GIB check: a missing or unexpected purpose is reported as a validation warning; the wire is not held.
| Field | Value |
|---|---|
| Code format | Turkish purpose-of-payment codes administered by TCMB (Türkiye Cumhuriyet Merkez Bankası - Central Bank of Turkey). |
| Source | ↗ TCMB Capital Movements Circular |
Available codes:
Turkish purpose-of-payment codes administered by TCMB (Central Bank of Turkey).
Remittance info¶
Extra content the regulator requires inside the free-text remittance field, beyond the purpose-of-payment code.
Standard remittance-info field - clearly identify the economic reason for the payment.
Compliance triggers¶
Beneficiary tax-ID requirements and rules that activate at certain payment amounts.
| Trigger | Requirement |
|---|---|
| Residency restrictions | Recipient full name must have no initials. |
Operational notes¶
| Field | Value |
|---|---|
| Currencies accepted | TRY |
| Typical settlement | 1-2 business days typical; longer for cross-border with FX or compliance review. |
| 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.
Beneficiary name with initials.
Missing TCMB PoP code (mandatory for FX).
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: ^TR[0-9]{2}[0-9]{5}[0-9][0-9A-Za-z]{16}$ · 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.