This page summarizes what Citi publicly discloses about CitiConnect® connectivity, the current Citi Developer Portal, APIs, host-to-host, files, SWIFT, pre-built integrations, and related channels, plus practical implementation implications. It is intentionally neutral and evidence-led.
What is most useful to know first.
Citi describes CitiConnect® for Files and APIs on its Platform and Data Services page, with SWIFT connectivity documented in regional pages and its November 2025 SAP whitepaper. The Developer Portal covers APIs and pre-built integrations.
Use the sources below to compare account reporting, payment initiation and status, payment acceptance, Virtual Cards, Token Services, and file-based ERP workflows. The onboarding checklist is this site's analysis, not a Citi delivery commitment.
Accounts is documented as 24×5; 24×7 payments availability depends on endpoint version and remains subject to downtime. Eligibility, markets, currencies, entitlements, and commercial terms require Citi confirmation.
Open the API page, CitiConnect® page, or Citi vs JPMorgan comparison based on your specific question.
Citi-disclosed channel roles, with an analytical onboarding checklist. Source links and limitations appear below.
| Connectivity path | What it is | Where it fits | What to validate early |
|---|---|---|---|
| Account details, balances and transactions; payment initiation, status inquiries and notifications; Virtual Card lifecycle and reporting APIs. | Embedded treasury and payment workflows. Availability and data freshness depend on the API, endpoint version, market, and branch. | Authentication and entitlements; endpoint versions; payload formats; webhook security; branch cutoffs; reconciliation and downtime handling. | |
| CitiConnect® for Files exchanges payments, receivables and information between client ERP/TMS systems and Citi. | Bulk payment-file submission and reporting, including ISO 20022 XML. Regional documentation lists SFTP, FTPS, HTTPS and AS2 transport options. | Supported formats and secure transport for the client's setup; acknowledgements, cutoffs, retries, resilience, and file-testing access. | |
| CitiConnect® for SWIFT provides bank connectivity through the SWIFT network; Citi's Argentina page describes FIN and FileAct routes. | Corporate treasury messaging and file exchange. Regional descriptions do not establish today's global message or market coverage. | Current SWIFT service and message versions, BIC setup, ISO 20022 mapping, address requirements, and exception handling. | |
| Pre-built integrations and Citi's ERP Integrator support connected workflows; the SAP whitepaper describes payment-file templates and selected Citi-rule validation. | Reducing custom file-development work and supporting ERP migration, payment validation, and reconciliation. | Supported ERP/TMS version and integration package, mapping ownership, validation coverage, testing, and change control. | |
| CitiDirect® supports account, payment, receivables, liquidity, trade, FX and reporting workflows alongside CitiConnect®. | Online treasury operations and approvals, with separate digital onboarding and signer-management services. | User roles, entitlements, audit trails, country-specific onboarding, and how portal approvals align with API/H2H instructions. |
Related pages: CitiDirect® · APIs & connectivity · ERP integrator · Client requirements
These sources inform the page and are good starting points for client and banker conversations.
Citi’s main public page for CitiConnect® positioning, footprint signals, and channel framing.
Citi's current Platform and Data Services page describes CitiDirect®, CitiConnect® for Files and APIs, ISO 20022 XML support, digital onboarding, and treasury data tools. Its scale figures are explicitly as of November 2025: 11 billion+ API calls processed year-to-date, 90+ markets and 130+ currencies. These are dated platform-level figures, not a current coverage promise for every API.
The regional sources add channel detail: Hungary lists file formats and transport options; Argentina describes SWIFT FIN and FileAct connectivity. Both pages are undated and must be read as regional descriptions, not a global implementation specification.
Public account, payment and card documentation, with endpoint-specific availability and production-scope limitations.
Current disclosure context: Citi’s 2026 Investor Day Services presentation identifies a CitiDirect AI Assistant and reports Payments Express in 22 markets as of December 2025, excluding Argentina. These are dated product disclosures, not current endpoint entitlements.
Account reporting: The Accounts API documents company-linked Citi and non-Citi account details, balances and transactions, JSON/XML responses, and 13 months of transaction history. It lists 24×5 availability, with weekend maintenance and local branch processing constraints. Balance endpoint v4 returns current balances; v5 supports current and historical balances. Confirm account eligibility and local cutoffs with Citi. The Account Services marketplace also lists Single Entity and Wallet virtual-account offerings; access requires registration and bank confirmation.
Outgoing payments: Citi documents ACH, wires, instant payments and Citi Token Services, plus status inquiries and webhook notifications. The 24×7 statement applies to Payment Initiation and Payment Status Inquiry GET/POST v3.0.0 or higher, and Payment Refund v2.0.0 or higher, subject to downtime. Refund requests are limited to Singapore and India; a stop-payment request is an attempt, not a guaranteed cancellation. Formats, clearing times and available methods vary.
Payment acceptance: Public payment-method documentation distinguishes U.S. USD Request for Pay over RTP, U.K. GBP Pay by Bank, and Brazilian BRL Pix. A request for payment requires payer approval and is not itself a funds transfer; this does not establish a CitiConnect FedNow API.
Virtual Cards: Public JSON APIs cover creation, modification, cancellation, controls, reporting and notifications. Mastercard and Visa support differs by endpoint and market; the reporting windows shown are 36 months for Mastercard and 180 days for Visa. Do not assume identical notification coverage across both networks.
Token Services: Citi's product page describes near-real-time, 24×7 cash transfers between participating Citi branches, subject to transaction limits, initiated through CitiDirect® or APIs without clients holding tokens or wallets. The Payments API page specifically documents USD in the US, UK, Singapore and Hong Kong. That documented API scope is not proof of availability for every product-announced currency or corridor. Separately, Citi’s September 2, 2026 Swift-ledger announcement describes live FAB/OCBC transactions in a controlled July–December 2026 proof of concept, not general API availability.
The October 28, 2024 release establishes the portal's file, API and pre-built integration framing; the January 18, 2025 video page describes documentation and sandbox access. These historical disclosures do not establish a current implementation SLA, unrestricted sandbox access, or production entitlement.
Public onboarding and testing resources, with limits on the currency of reported implementation figures.
Citi describes implementation support for cash management, trade and commercial cards, with digital onboarding and CitiConnect® testing resources. The undated page includes 2019 project figures, so its staffing, footprint, API-count and satisfaction figures are not treated here as current operating metrics. Confirm delivery milestones, responsibilities, service levels and test access during onboarding.
Dated guidance on ERP file integration, sandbox resources and the CitiConnect® Testing Portal.
Pages 10–11 describe interoperable CitiDirect® and CitiConnect® Files/SWIFT/API channels, direct ERP-to-Citi host-to-host connectivity, downloadable file specifications, and a dummy-account sandbox kit. Citi's ERP Integrator provides ISO XML templates, selected Citi payment-rule validations, and reconciliation support; it does not remove client-specific mapping and onboarding work.
The whitepaper says payment files can be tested through H2H or CitiDirect®, with reports returned in minutes. Its Testing Portal availability is 24 hours a day, Monday–Friday, subject to planned or unplanned maintenance and downtime. These November 2025 descriptions are implementation guidance, not a new 2026 service-level commitment.
Use these when your question is more specific than "tell me about Citi".
Platform scope, onboarding/login resources, and official Citi short links gathered into one page.
What CitiConnect® means, how Files and SWIFT differ from host-to-host patterns, and what to validate in onboarding.
Public API categories, ERP/TMS signals, scenario mapping, and a careful limitations view based on official Citi material.
Side-by-side scorecard across platform positioning, APIs, payments, reconciliation, and public documentation clarity.
E-commerce, fintech, manufacturing, mining, industrial: when to use APIs vs host-to-host (often both).