Skip to content

🇰🇿 Sending to Kazakhstan

KZ · KAZ · +7 · Central Asia

KZT

IBAN required   SWIFT BIC required

← Back to Country-specific guides

Required information

  • IBAN

    20 characters (KZ + 18), e.g. KZ86125KZT5004100100.

  • SWIFT BIC

    Beneficiary bank BIC (8 or 11 characters).

  • Purpose-of-payment code (mandatory)

    10-character EKNP purpose code

  • Beneficiary full name

    Spelled out exactly as registered at the bank. No initials or abbreviations.

  • Regulator-mandated fields

    Whether the beneficiary is a company or a person + others

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-19. Reference material only.

  • Currency

    KZT

  • Typical settlement

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

  • SWIFT BIC

    Required

  • Local clearing

    ISMT (NBK)

Account format

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

Field Value
Format tier IBAN required
Length 20 characters (KZ + 18)
Validation regex ^KZ[0-9]{2}[0-9]{3}[0-9A-Za-z]{13}$
Example KZ86125KZT5004100100

Routing identifiers

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

Field Value
SWIFT BIC Required
None Optional
Local clearing ISMT (NBK)

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.

Mandatory:

  • Whether the beneficiary is a company or a person (Cdtr/Id/OrgId or Cdtr/Id/PrvtId)
  • Beneficiary identifier, such as a tax or registration number (Cdtr/Id/OrgId/Othr/Id or Cdtr/Id/PrvtId/Othr/Id, with SchmeNm) — 12-digit Business Identification Number (BIN) or Individual Identification Number (IIN) Scope: FX only

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 10-character EKNP purpose code
Source ↗ NBK Resolution 203

Available codes:

10-character EKNP (Единый код назначения платежа - Unified Payment Purpose Code) administered by the National Bank of Kazakhstan. Format combines transaction type, operation type, and economic sector.

Remittance info

Extra content the regulator requires inside the free-text remittance field, beyond the purpose-of-payment code.

Payment purpose must be clearly identified.

Operational notes

Field Value
Currencies accepted KZT, USD
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.

Missing 10-character EKNP PoP code (mandatory for FX).
Missing legal_type or legal_id (12-digit BIN/IIN, required by regulator for FX wires).
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: ^KZ[0-9]{2}[0-9]{3}[0-9A-Za-z]{13}$ · 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.

← Back to Country-specific guides