Skip to content

🇹🇯 Sending to Tajikistan

TJ · TJK

TJS

National format   SWIFT BIC required

← Back to Country-specific guides

Required information

  • Account number

    20-digit CIS-style account number (Soviet-legacy structure: 5-digit balance class + 3-digit currency + 1 check + 4 branch + 7 personal). Used by all Tajik commercial banks. Tajikistan has not adopted IBAN.

  • SWIFT BIC

    Beneficiary bank BIC (8 or 11 characters).

  • MFO (national bank routing code)

    9-digit MFO code; INN tax-ID (9 digits) also required for cross-border

  • Purpose-of-payment code (mandatory)

    Free-text detailed purpose plus contract/invoice reference

  • Beneficiary address

    Match the address template — partial addresses cause holds.

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.

Last reviewed by GIB compliance on 2026-05-21. Reference material only.

  • Currency

    TJS

  • Typical settlement

    1-2 business days typical; longer for cross-border with FX or compliance review.

  • SWIFT BIC

    Required

  • Local clearing

    RTGS (National Bank of Tajikistan)

Account format

How beneficiary account numbers are structured for Tajikistan. Failure to match this format is the single most common reason wires are rejected at the destination.

Field Value
Format tier National format
Length 20-digit CIS-style account number (Soviet-legacy structure: 5-digit balance class + 3-digit currency + 1 check + 4 branch + 7 personal). Used by all Tajik commercial banks. Tajikistan has not adopted IBAN.
Validation regex ^[0-9]{20}$
Example 20202972000111100000

Routing identifiers

Which routing codes the wire-creation API call must include for Tajikistan.

Field Value
SWIFT BIC Required
MFO (national bank routing code) Required
Format 9-digit MFO code; INN tax-ID (9 digits) also required for cross-border
Directory ↗ Source
Local clearing RTGS (National Bank of Tajikistan)

Address format

How Tajikistan expects the beneficiary address to appear on the wire. Free-form variations frequently trigger compliance holds.

  1. Recipient Full Name
  2. Street + Building
  3. District
  4. City
  5. Postal Code
  6. TAJIKISTAN
Field Value
Postal code Optional — validated against the format below when provided
Postal code regex ^7[3-5][0-9]{4}$
Example Rudaki Ave 38/1, Dushanbe 734003, Tajikistan

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: Mandatory (confirmed) GIB check: a missing or unexpected purpose is reported as a validation warning; the wire is not held.

Non-standard element

For Tajikistan, the purpose is placed in <RmtInf> (remittance info), not the standard <Purp> element.

Field Value
Code format Free-text detailed purpose plus contract/invoice reference
Source ↗ Tajikistan FX Law

Operational notes

Field Value
Currencies accepted TJS
Typical settlement 1-2 business days typical; longer for cross-border with FX or compliance review.
Banking holidays ↗ Calendar

Known issues:

  • No IBAN; relies on 20-digit CIS-format account plus MFO and INN, raising misrouting and STP-failure rates.
  • NBT operates managed-float FX regime with intermittent USD shortages.
  • Heavy correspondent dependency on Russian and Kazakh banks; remittance corridors from Russia are systemically important.
  • Not FATF grey-listed as of 13 February 2026.

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 mismatch (initials, abbreviations, punctuation, or transliteration differences from what the beneficiary bank has on file).
Account number format error (wrong length, wrong check digits, or non-standard characters).
Missing or invalid SWIFT/BIC code.
Insufficient remittance information (unclear economic reason for the payment).
Sanctions or compliance hold (OFAC / EU / UN / local screening).
Missing 9-digit MFO bank code or 9-digit INN tax identifier.
Purpose-of-payment not in Russian or Tajik or missing contract reference.
NBT FX surrender or repatriation rules not followed by exporter.

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.

← Back to Country-specific guides