Does Citibank India (now Axis Bank-owned) still use its legacy SWIFT code, or has it been retired?

As of 2024, Citibank India’s retail and consumer banking operations—including its domestic remittance infrastructure—have been fully acquired by Axis Bank. Consequently, Citibank India’s legacy SWIFT code (CITIINBB) has been officially retired for all domestic and cross-border remittance purposes.

This transition means that international transfers previously routed to Citibank India accounts must now use Axis Bank’s active SWIFT code: AXISINBB. Remittance businesses and overseas senders must update beneficiary bank details immediately to avoid delays, returns, or processing failures—especially for inward remittances targeting former Citibank India customers.

Axis Bank has integrated the migrated customer base into its core banking and SWIFT network, ensuring seamless continuity in fund receipt. However, outdated SWIFT references remain a top cause of failed transactions in India’s remittance corridor. Verifying the correct bank name, IFSC (for domestic transfers), and SWIFT/BIC (for international) is non-negotiable for compliance and speed.

For remittance service providers, updating internal databases, client-facing portals, and payout instructions with Axis Bank’s current identifiers is critical—not just for regulatory alignment (RBI & FATF), but also to maintain sender trust and reduce operational friction. Always confirm via Axis Bank’s official website or SWIFT’s BIC directory before initiating high-value transfers.

What format does Citibank’s SWIFT code follow — 8-character or 11-character — and why?

Citibank’s SWIFT code follows the standard 11-character format — for example, CITIUS33XXX. While the first 8 characters (CITIUS33) identify the bank (Citibank), country (US), and location (New York), the optional 3-character branch code (XXX) specifies a particular office or function. This full 11-character structure ensures precise routing in international remittances.

For remittance businesses, using the correct 11-character SWIFT code is critical to avoid delays, rejected transfers, or misdirected funds. Many banks — including Citibank — default to their primary U.S. clearing office (CITIUS33XXX), but regional branches may require distinct suffixes. Verifying the exact code with the recipient or Citibank directly prevents costly processing errors.

SWIFT codes are globally standardized by the International Organization for Standardization (ISO 9362). Though 8-character codes are valid for head offices, most cross-border payments—especially high-volume remittances—require the full 11-character version to meet compliance, AML, and correspondent banking requirements.

Always confirm Citibank’s current SWIFT/BIC with official sources or your banking partner before initiating payouts. Accurate SWIFT data boosts settlement speed, reduces fees from intermediary corrections, and strengthens trust with your end recipients — key advantages in today’s competitive remittance market.

Can a Citibank SWIFT code reveal whether the account is held in a specific currency (e.g., EUR, JPY)?

When sending international payments, many remittance businesses and customers wonder: *Can a Citibank SWIFT code reveal the account’s currency—such as EUR or JPY?* The short answer is **no**. A SWIFT/BIC code (e.g., CITIUS33 for Citibank N.A. in New York) identifies only the bank, country, city, and branch—not the currency of an individual account.

SWIFT codes follow a standardized four-part format (bank code, country code, location code, and optional branch code), all designed for routing messages—not specifying account-level details like currency, balance, or account type. Currency information is instead provided separately in payment instructions (e.g., via the MT103 message’s field 32A or ISO 20022’s element).

For remittance providers, this means relying solely on the SWIFT code to infer currency can lead to errors, delays, or rejected transfers. Always confirm the beneficiary’s currency with the sender—and validate it against the recipient bank’s supported currencies and local regulations (e.g., JPY transfers to Japan may require additional details like a bank code and branch number).

At [YourRemitBusiness], we automate currency validation at the point of payout, cross-referencing SWIFT data with real-time FX and compliance rules—ensuring faster, compliant, and cost-efficient cross-border payments to Citibank and 150+ other global banks.

How do SWIFT code requirements differ for Citibank when sending funds via SEPA vs. non-SEPA corridors?

When sending money to Citibank accounts in Europe, understanding SWIFT code requirements for SEPA vs. non-SEPA corridors is essential for fast, low-cost transfers. For SEPA (Single Euro Payments Area) payments—denominated in EUR and sent to eligible EU/EEA countries—you typically do *not* need a SWIFT/BIC code. Instead, only the recipient’s IBAN is required, as SEPA relies on standardized pan-European routing.

In contrast, non-SEPA corridors—such as USD transfers to Citibank U.S., GBP to Citibank UK, or cross-border payments outside the SEPA zone—*always* require a valid SWIFT/BIC code. For Citibank, this varies by entity: e.g., Citibank N.A. New York uses CITIUS33, while Citibank Europe PLC uses CITIIE2X. Using an incorrect or outdated BIC may cause delays or rejection.

Remittance businesses benefit significantly from this distinction: SEPA transfers settle within 1 business day, cost less, and reduce compliance friction. Non-SEPA routes involve intermediary banks, higher fees, and stricter SWIFT validation. Always verify the correct Citibank entity and corresponding BIC via official sources before initiating non-SEPA payments.

Optimizing corridor selection—leveraging SEPA where possible and validating SWIFT codes rigorously elsewhere—enhances speed, transparency, and customer trust in your remittance service.

Where can I download Citibank’s official SWIFT code directory (e.g., PDF or API-accessible list)?

Citibank does not publicly publish or distribute an official, downloadable SWIFT code directory (e.g., as a PDF or Excel file) for general use. This is standard industry practice—major banks like Citibank treat branch-level SWIFT/BIC codes as operational data, not open resources, to mitigate fraud and ensure accuracy.

For remittance businesses requiring Citibank’s SWIFT codes, the safest and most reliable method is to obtain them directly from Citibank via official channels: through your dedicated relationship manager, Citibank’s corporate banking portal (if you’re an enrolled client), or verified documentation accompanying your account onboarding. Some Citibank branches may also list their BIC on local websites—but always verify with Citibank directly before initiating high-value transfers.

While third-party SWIFT code databases exist online, they’re often outdated or unverified. Relying on unofficial sources risks transaction delays, returns, or compliance flags—especially under AML/KYC scrutiny. Remittance providers must prioritize data integrity; using incorrect or deprecated SWIFT codes can trigger regulatory alerts or failed settlements.

For API-based integration, Citibank offers secure, authenticated APIs (e.g., via CitiConnect®) to enterprise clients—but access requires formal agreement and certification. No public, self-serve SWIFT code API is available. Always consult Citibank’s official support or your account officer for authoritative, up-to-date routing information tailored to your remittance workflow.

Do Citibank’s SWIFT codes comply with ISO 9362 standards—and how is that enforced?

When sending international remittances, accuracy and compliance are non-negotiable—especially regarding SWIFT/BIC codes. Citibank’s SWIFT codes fully comply with ISO 9362 standards, the globally recognized framework governing bank identifier formats. Each Citibank SWIFT code is precisely 8 or 11 characters long, follows strict alphanumeric rules (no special characters), and includes the correct institution code (CITI), country code (e.g., US), location code, and optional branch code—ensuring seamless interoperability across global payment networks.

Compliance isn’t voluntary—it’s enforced through multiple layers: SWIFT’s own registration and validation system audits all active BICs; central banks (like the Fed and ECB) require ISO-aligned identifiers for cross-border settlement; and Citibank’s internal controls undergo regular regulatory reviews under frameworks like FFIEC and Basel III. Any deviation would risk transaction rejection, delays, or fines.

For remittance businesses, using Citibank’s verified, ISO-compliant SWIFT codes minimizes failed transfers, enhances traceability, and strengthens AML/KYC adherence. Always source codes directly from Citibank’s official website or SWIFT’s BIC directory—not third-party lists—to avoid fraud or misrouting. Trusting standardized identifiers means faster settlements, lower operational risk, and greater customer confidence in every cross-border payout.

What alternative identifiers (e.g., IBAN, sort code, BSB) should accompany Citibank’s SWIFT code for successful cross-border payments?

When sending cross-border payments to Citibank accounts, providing the correct SWIFT/BIC code alone isn’t enough—additional local identifiers are essential for accuracy and speed. Citibank operates globally with country-specific clearing systems, so pairing its SWIFT code (CITIUS33 for the U.S., CITIUS22 for legacy NY operations, or regional variants like CITIHKHX for Hong Kong) with the right local account details prevents delays or returns.

For payments to Citibank UK, include the 6-digit sort code and 8-digit account number. To Citibank Australia, supply the 6-digit BSB code alongside the account number. For Citibank EU branches (e.g., Germany or France), the IBAN is mandatory—SWIFT plus IBAN ensures SEPA-compliant processing. Always verify the exact SWIFT variant and required identifiers via Citibank’s official website or your recipient’s bank statement.

Remittance businesses benefit from automating identifier validation using real-time APIs that cross-check SWIFT codes with local standards (e.g., IBAN formatting rules or BSB checksums). This reduces manual errors, lowers rejection rates, and enhances customer trust. Partnering with banks or fintechs offering embedded compliance tools further streamlines high-volume international payouts to Citibank beneficiaries.

 

 

About Panda Remit

Panda Remit is committed to providing global users with more convenient, safe, reliable, and affordable online cross-border remittance services。
International remittance services from more than 30 countries/regions around the world are now available: including Japan, Hong Kong, Europe, the United States, Australia, and other markets, and are recognized and trusted by millions of users around the world.
Visit Panda Remit Official Website or Download PandaRemit App, to learn more about remittance info.