This page maps what is publicly visible about the Citi® Developer Portal, CitiConnect® APIs, and related documentation signals, and separates those signals from what still requires onboarding validation. It now benchmarks Citi against J.P. Morgan Payments, Bank of America CashPro®, Plaid, and Stripe.
Use this as first-pass discovery and vendor benchmarking before bank engagement.
developer.citi.com publicly presents API catalogs, pre-built integrations that feed real-time Citi data into treasury and finance applications, and an API Explorer for sample transactions, payments, and balance inquiries.
Citi's October 2024 announcement positioned the portal around batch files, real-time APIs, and pre-built connectivity into TMS, accounting, and productivity tools.
A Virtual Cards API reference is published under Commercial Cards on developer.citi.com. Earlier versions of this page tracked no card category; that gap is now closed.
Eligibility, pricing, entitlement rules, and product-by-region availability remain onboarding questions. No named bank in this comparison publishes institutional API pricing.
April to July 2026 changes that matter for Citi API positioning.
This page previously leaned on press releases and the CitiConnect® API Playbook PDF. developer.citi.com now carries stronger signals: API catalogs split by audience, an API Explorer sandbox, and pre-built integration messaging for treasury and finance platforms.
The portal landing page routes developers to consumer-app APIs versus institutional use cases. This page covers the institutional CitiConnect® path; consumer APIs are out of scope here.
The Virtual Cards API reference is publicly indexed under Commercial Cards. Virtual card issuance, lifecycle management, and transaction reporting still require production-scope validation.
Citi's October 2024 release stated ERP capabilities would be added to the platform in 2025. Public materials describe file, API, and pre-built integration approaches, including ERP/TMS routes; validate the current ERP connector list during onboarding.
These categories are described in public Citi materials. Full scope varies by client segment, geography, and entitlements.
| Category | What it typically enables | Public evidence signal | Confidence |
|---|---|---|---|
| Balance reporting and account information retrieval for treasury reporting and forecasting. | Portal and press materials describe account balance inquiry APIs; playbook references camt.052-based responses. | ||
| Payment initiation from ERP/TMS or middleware; often paired with files/H2H for bulk volume. | Portal describes payments capabilities including real-time payments in 30+ countries; playbook references pain.001. | ||
| Status, acknowledgements, and exception visibility for reconciliation. | Playbook references pain.002 responses and push notifications; portal lists status APIs. | ||
| Period statement request and retrieval. | Playbook references camt.053 end-of-day statements and MT940 (setup-dependent). | ||
| Rate retrieval and, where applicable, FX booking tied to payments, including WorldLink® multi-currency flows. | Public materials describe FX rate and booking APIs; the developer marketplace lists WorldLink® at 135+ currencies across 180+ markets, plus dedicated InstantFX and CitiFX Gateway API families (verified July 11, 2026). | ||
| Virtual card data and account reporting; broader card lifecycle capabilities described in Citi commercial-cards publications. | Virtual Cards API reference published under Commercial Cards on developer.citi.com. | ||
| Direct debit initiation where supported. | Playbook notes availability in Australia, Singapore, and Hong Kong; references pain.008. | ||
| Cross-border payment monitoring. | Playbook lists SWIFT gpi monitoring; rail/product-dependent. | ||
| User management, cutoff times, and holiday schedules. | Playbook references admin and reference-data APIs with JSON responses. |
Message-version watch item: playbook examples reference pain.001.001.03, pain.002.001.03, and pain.008.001.02. With the SWIFT CBPR+ structured/hybrid address milestone landing in November 2026, teams should validate current supported message versions and address-field handling for their corridors during onboarding rather than assuming the playbook versions. Label: analyst interpretation. Confidence: Medium.
Evidence-anchored areas where Citi's bank infrastructure matters.
Institutional API access is KYC-gated and entitlement-driven by design; playbook materials describe OAuth 2.0 authentication, and transactions execute on the bank's regulated rails rather than through an intermediary.
Citi describes doing business in more than 180 countries and jurisdictions using local banking licenses, with physical presence in 90+ markets. Services pages cite WorldLink® cross-border payments in 135+ currencies and 24/7 USD clearing reaching 1,500+ financial institutions.
The API layer fronts virtual accounts, liquidity structures, instant payments in 30+ countries, and newer 24/7 capabilities such as Citi Token Services.
One hub spans API, file/batch, and pre-built integrations into third-party TMS, accounting tools, and Excel. Citi publicly cites 10B+ CitiConnect® API calls since inception as an adoption signal.
Developer-experience areas where Plaid and Stripe set expectations for bank API programs.
Stripe issues sandbox keys in minutes with a fully versioned public API; Plaid offers limited production access with a free live-call allowance and self-serve plans in the US and Canada.
Even the fastest bank claims are measured in days-to-weeks for existing clients, versus same-day self-service on fintech platforms. Entitlement mapping, security review, and testing add calendar time on the bank side.
Stripe and Plaid treat documentation, SDKs, changelogs, and sample apps as core product. Among banks, J.P. Morgan has moved furthest publicly with self-service API credential management and open-source sample apps.
Stripe publishes core rates; Plaid publishes pricing models. J.P. Morgan, Stripe, and Plaid each publish MCP or agent-oriented documentation routes. No equivalent public Citi surface was identified at verification time.
financeAI.tech editorial analysis of publicly visible signals as of July 1, 2026. These are not claims about production performance or commercial outcomes.
| Category | Citi (CitiConnect®) | J.P. Morgan Payments | Bank of America (CashPro®) | Plaid | Stripe |
|---|---|---|---|---|---|
| Integration speed | Multi-channel hub plus pre-built connectors aim to compress the typical 2-3 month bank build; API Explorer sandbox is public; production is entitlement-gated. | Public sandbox and self-service credential management reduce friction; production requires a client relationship. | Markets API access for existing CashPro clients "in days"; 28+ TMS/ERP platforms pre-integrated; CashPro Validator supports file onboarding. | Sandbox same day; limited production with free live-call allowance; self-serve plans in the US and Canada. | Sandbox keys in minutes; core payments live quickly; regulated features such as Treasury and Global Payouts are preview or eligibility-gated. |
| Security & controls | Bank-grade, KYC/entitlement-gated; OAuth 2.0 per playbook; regulated bank perimeter. | Bank-grade; documented OAuth with signed JWT, mTLS, and digital-signature certificates. | Bank-grade; access provisioned within the CashPro relationship and compliance review. | OAuth-based consumer-permissioned access; strong ecosystem trust; not a bank. | Mature platform security; US financial accounts FDIC-insurance-eligible via partner banks; not a bank itself. |
| Global reach | Network across 180+ countries and jurisdictions; presence in 90+ markets; 135+ WorldLink currencies; instant payments in 30+ countries. | Serves clients in 100+ countries; cites about $10T processed daily and more than 50% of US e-commerce touching its platform. | 350+ payment types across 38 markets; 7 real-time schemes including Zelle and Pix. | 12,000+ connected institutions across US, Canada, and Europe; data reach, not bank rails. | Payouts marketed to 160 countries; Global Payouts in preview; stablecoin-backed balances in 100+ countries. |
| Developer experience | Marketplace-style portal plus API Explorer; consumer/institutional split; some content registration-gated; playbook partly PDF-based. | Strongest public bank DX signals: self-service credentials, GitHub sample apps, reference MCP server. | CashPro Developer Studio with catalog, sandbox, and Validator; tightly coupled to the CashPro platform. | Reference-grade docs, SDKs, docs assistant, MCP server; consistently cited as a DX benchmark. | Industry-benchmark docs, versioned API, SDKs, sample apps, MCP server. |
| Pricing & onboarding transparency | Relationship-priced; not publicly disclosed. | Relationship-priced; not publicly disclosed. | Relationship-priced; not publicly disclosed. | Pricing models published; enterprise rates negotiated; EU/UK custom-only. | Core payment pricing published; enterprise and preview products custom. |
| Institutional treasury depth | Deep: liquidity structures, virtual accounts, 24/7 USD clearing, token services, trade, behind one connectivity layer. | Deep: full treasury and embedded finance, including blockchain via Kinexys. | Deep in NAM-centered treasury; #1 in Coalition Greenwich digital-channels benchmarking four consecutive years. | Not applicable: data connectivity and account-linked transfers, not treasury rails. | Emerging: Treasury and Treasury for platforms in preview/partner-bank model; strong for platform embedded finance, not corporate treasury. |
How to read this table: for multinational corporate treasury, the realistic comparison set is Citi, J.P. Morgan, and Bank of America. Plaid and Stripe matter because they set developer-experience and onboarding-transparency expectations that corporate developers now bring to every bank engagement.
Captured from developer.citi.com on July 11, 2026. The marketplace organizes 14 business-objective solutions. All 115 OpenAPI specs (306 endpoints) are fetchable, and reference docs are publicly readable for most sections; Accept Payments, FX, and Token Services doc pages sit behind login. Sandbox and production hosts are published in the specs. Per-API endpoint detail lives in the dataset below.
| Solution | Public APIs listed | Notable scope | Reference docs |
|---|---|---|---|
| Account Services | Accounts, Balances, Statements, Account Notifications (webhooks), Statements File, Virtual Accounts (Single Entity, Wallet) | Multibank balances supported | |
| Domestic Payments | Payments API, Payments File, Bulk Payments, Validation Services | ~90 countries; 290+ clearing connections | |
| Instant Payments | Instant Payments API; Payments Express variant (JSON-first) | 30+ countries; Payments Express live in 5 | |
| Cross-Border Payments | WorldLink® (incl. FX rate/booking), CBFT API + File, Bulk Payments, Validation Services | WorldLink: 180+ markets, 135+ currencies; CBFT: send 135 / receive 40 currencies | |
| Payment Acceptance (Spring by Citi) | Online Payments, Direct Debit/eMandates (incl. Australia PayTo, India UPI Request-to-Pay, Brazil Pix QR), Payer ID | Pix acceptance live via API | |
| Commercial Cards | Virtual Cards lifecycle, Reporting, Notifications, Real-Time Authorizations, Disputes, Mobile Virtual Cards | 130M+ merchant acceptance | |
| Citi Token Services for Cash | Five API use-case flows (planned payments, 24/7 liquidity, time-sensitive funding, capital-markets funding and redemptions) | DLT-based 24/7 transfers across Citi network | |
| Custody | Accounts, Safekeeping Transactions, Positions, Cash Balance, Cash Transactions, Tax Reclaims, CSDR Penalties, FX Transactions | Hosted on CitiVelocity; GUID-addressed datasets | |
| ETF Services | Order Approval, Portfolio Listing | ETF lifecycle automation | |
| Transfer Agency | Investor, Accounts, Transactions, Holding; Share Class (coming soon) | Shareholder-register data | |
| Citi InstantFX® | FX Quote Request, FX Order, FX Order Enquiry | CitiFX digital solutions in 120+ countries | |
| CitiFX Gateway | FX Market Order, FX Benchmark Order (BFIX, WMR), Order Enquiry | 100+ markets; 400+ currency pairs |
From Citi’s public Authentication Guide (developer.citi.com/apidocs), verified July 11, 2026. This is the full journey from zero to a production API call.
| Step | What happens | What you need |
|---|---|---|
| 1 · Create an account | Sign-up form, email verification, first sign-in with a one-time password — registration completes only after first login. Unlocks Account Reporting and Payments docs by default. | Work email; a second developer account from your organization (required later to approve certificate uploads) |
| 2 · Request access | Request docs or test-environment access per solution from the Marketplace or doc pages. | Your Citi Representative’s information (email devsupport@citi.com if unknown) |
| 3 · Choose integration | Download per-API SDKs from reference pages, or integrate directly against the OpenAPI specs. | — |
| 4 · Get credentials | Client ID and Client Secret appear on the dashboard’s Credentials & Certificates tab once access is granted. | Granted test/production access |
| 5 · Set up certificates | Upload your public keys; download and install Citi’s certificates. One developer uploads, a second approves by email. | See certificate table below |
| 6–7 · Test, then go live | Implementation manager confirms the account for testing, then for production after successful tests. | Citi implementation manager sign-off |
| Certificate (Auth V1–V3) | Encryption | Purpose |
|---|---|---|
| Client TLS Certificate | TLS v1.2 | Mutual authentication of the encrypted connection |
| Client Encryption Certificate | AES-256-GCM | Citi decrypts your request payload |
| Client Signing Certificate | JOSE | Citi verifies your payload signature |
| Auth V4 (newest) | TLS only | One SSL certificate; no payload signing/encryption; backward compatible with V3 APIs |
Certificate rules: Extended Key Usage must include Client Authentication at the leaf level; wildcard certificates are prohibited; 2048-bit RSA keys; Commercial Cards APIs skip the signing certificate; Citi’s own certificates must also be downloaded and installed for V1–V3.
Base64-encode Client ID and Secret into the request header, build the body per the API reference, then sign and encrypt the payload (V4 skips signing/encryption). OAuth 2.0 over mutual TLS, HTTPS only. Tokens last 1,800 seconds with no refresh token — renew from the expires_in field or on a 401.
The Credentials & Certificates tab handles both directions: upload your public keys, download Citi’s. Security note from Citi: store credentials away from client-side code and public repos.
OAuth 2.0 client-credentials over mutual TLS (Authentication Services V1–V4; V4 drops payload signing and needs only an SSL certificate). Tokens are valid 1,800 seconds with no refresh token. Registration unlocks Account Reporting and Payments testing by default; other solutions are enabled per request.
Specs publish both environments: TTS production at tts.apib2b.citi.com/citiconnect/prod and sandbox at tts.sandbox.apib2b.citi.com/citiconnect/sb; Custody on api.citivelocity.com/markets; Transfer Agency and Gateway Services on b2b.api.icg.citi.com. An official Postman workspace (postman.com/citi-services) is linked from the portal.
The full three-bank catalog captured for this site — Citi marketplace solutions with endpoint samples, J.P. Morgan portal groupings, and Bank of America’s 84-API public catalog — is published as structured data.
Public portal visibility is useful, but it is not the same as contracted implementation scope.
Some portal content is JavaScript-rendered or registration-gated and may not be fully indexable. Where a detail is not publicly visible, treat it as a validation item, not a missing feature.
Client eligibility, required entitlements, and product-by-region availability are not fully described publicly for any bank in this comparison.
Institutional pricing is not disclosed in developer portals. Run procurement and contracting in parallel with technical design.
Certification, operational readiness, and cutover details are handled in implementation engagements. Public testing references are inputs, not the full path.
Connectivity options are described globally, but market-level differences in rails, formats, and direct debit availability are not consolidated on one public page. Validate corridors early.
Items that can change API priority or implementation risk.
Confirm supported pain/camt versions and address handling per corridor against playbook-era examples before the November 2026 structured-address milestone.
Confirm the delivered scope of Citi's 2025 ERP commitment during onboarding.
J.P. Morgan, Stripe, and Plaid have public agent-oriented surfaces. Watch whether bank peers formalize equivalents.
CFPB Section 1033 status remains under review. It is primarily a consumer-data question, but it shapes third-party-access and data-sharing posture across US banks.
Public links for comparing discoverability, onboarding visibility, documentation clarity, and developer experience.
Institutional and consumer catalogs, plus API Explorer.
Docs, sandbox, GitHub samples including Unicorn Finance, and reference MCP server signals.
API catalog, sandbox, and CashPro Validator.
APIs & connectivity comparison · Citi vs JPMorgan visual · Big 3 API Matrix · Client-side requirements
Primary public sources used for this page.
| Organization | Public source signal | Verification note |
|---|---|---|
| Citi | Developer Portal, API Explorer, Virtual Cards API Reference, October 2024 Developer Portal release, CitiConnect® API Playbook, global presence, Services payments/receivables pages, and Citi Token Services euro integration release. | Verified July 1, 2026; some documentation areas remain registration or entitlement-gated. |
| J.P. Morgan | Payments Developer Portal, sandbox and authentication docs, self-service credential management, GitHub samples, scale claims, and MCP reference signals. | Verified July 1, 2026. |
| Bank of America | CashPro Developer Studio, CashPro Payment API release, CashPro platform page, and Coalition Greenwich digital-channels recognition. | Verified July 1, 2026. |
| Plaid | Pricing page and billing documentation. | Verified July 1, 2026. |
| Stripe | Treasury, Global Payouts, Treasury for platforms documentation, and Treasury product page. | Verified July 1, 2026; Treasury and Global Payouts noted as limited public preview where applicable. |
Last verified: July 11, 2026.