Big 3 API Matrix: Citi vs. J.P. Morgan vs. Bank of America

A practical comparison of how Citi, J.P. Morgan, and Bank of America present treasury and payments APIs in public. The focus is implementer clarity: domestic payments, onboarding, callbacks, market restrictions, and the limits of what public documentation establishes.

Big 3 API matrix Treasury APIs Domestic payments Cross-border Official sources
Start with summary Review official links
Last verified: September 14, 2026
Scope: public bank websites, developer portals, and official bank publications only
Start here Refresh check U.S. domestic Cross-border JPM watchouts Sources
J.P. Morgan Documented payment families

Versioned Global Payments documentation, U.S. instant rails, and explicit product restrictions. Global Payments 2 remains pilot-gated.

Bank of America CashPro APIs and treasury tools

A public CashPro library, ACH and RTP services, FX APIs, disbursement choices, and forecasting or assistant tools.

Citi Global connectivity and public references

Public account, payment, card, and authentication references alongside files, integrations, FX, and tokenized-cash services.

Use this page Fast comparison before deeper diligence

Start with the summary, then use the U.S. domestic and cross-border matrices to see where the three banks diverge in product packaging and implementation posture.

Start here

The short answer

All three banks publish treasury and payments API information. J.P. Morgan documents product versions and U.S. instant rails; Bank of America exposes a CashPro API library and treasury tools; Citi publishes endpoint references, authentication guidance, and multinational connectivity options.

This is a comparison of public evidence, not a performance ranking. Country coverage, payment direction, account eligibility, API version, onboarding, and commercial entitlement must be validated for the intended workflow. A public product page is not proof that every client can use every feature.

Evaluate an eligible workflow, not a universal winner. Public documentation depth, network footprint, and production service quality are different measurements. The comparison below keeps those distinctions explicit.
J.P. Morgan

Versioned payment documentation

Global Payments, Checks, Pay by Bank, and Validation Services expose product-level restrictions. Global Payments 2 documentation does not remove its pilot requirement.

Bank of America

CashPro API and operating tools

CashPro combines a public API library with payment operations, reporting, digital disbursements, FX trading, and treasury-assistance products.

Citi

API and multichannel connectivity

CitiConnect combines public API references with file and SWIFT connectivity, pre-built integrations, and bank-specific account and market coverage.

Refresh check

What was re-checked against official bank sources on September 14, 2026

The full page was reviewed for source accuracy, market scope, API access, catalog measurement, and outdated comparative claims. Original publication dates remain attached to historical announcements; current verification is not a new launch date.

J.P. Morgan

India UPI and Pay by Bank coverage updated

Country scope and version restrictions are product-specific.

  • Global Payments: current documentation lists 45+ countries; Global Payments 2 remains pilot-only, including its ACH and wire expansion.
  • Checks: United States and Canada; new integrations use v2.x. The reviewed overview no longer shows the earlier beta label.
  • Pay by Bank: account information covers the U.S., U.K., and five EU markets; payment initiation covers the U.K. and those EU markets, not the U.S.
  • Request to Pay via QR Code: India UPI is now listed as available alongside Brazil Pix, Singapore PayNow, and Hong Kong FPS. Payment links and bulk scheduled QR generation remain Brazil-specific.
  • Treasury insights: Cash Flow Intelligence and an AI copilot are public treasury tools, not evidence of an unrestricted payment-initiation API.
Citi

Public technical scope is broader than the old comparison implied

Current technical documentation is public for accounts, payments, virtual cards, payment acceptance, and authentication; registration is still required for provisioned access.

  • Platform and Data Services: 11 billion-plus year-to-date API calls, 90+ markets, and 130+ currencies are explicitly dated November 2025.
  • Authentication and onboarding: OAuth client credentials, mutual TLS, certificate approval, and version-specific payload protection are publicly described.
  • Payment acceptance methods: public documentation identifies U.S. USD Request for Pay over RTP; payer approval is required. It does not establish a FedNow integration.
  • Account Services: Single Entity and Wallet virtual-account offerings are publicly listed; registration and bank confirmation still govern access.
  • 2026 Investor Day Services presentation: identifies a CitiDirect AI Assistant and reports Payments Express in 22 markets as of December 2025, excluding Argentina.
Bank of America

Live library and announced cross-border expansion

The live CashPro catalog and current product announcements replace reliance on the retired API setup form.

  • CashPro API library: 78 visible entries in 10 families were recounted. These are catalog entries, not a bank-wide endpoint-operation total.
  • ACH: API payments/reporting and U.S. Account Validation remain public.
  • June 4, 2026 announcement: cross-border real-time payments were planned for the following quarter, with CashPro API, host-to-host, and SWIFT access. This review does not treat the announcement as confirmation of rollout completion.
  • Digital disbursements: U.S. Zelle/Venmo, Canadian Interac, and PayPal in selected markets have different eligibility and delivery conditions.
  • CashPro FX Trading API: spot, forwards, swaps, and non-deliverable forwards are publicly described. Its absence from the visible library is not evidence that the product was withdrawn.
Countability rule Citi solution cards, J.P. Morgan browse entries, Bank of America API entries, OpenAPI specifications, and HTTP operations are not interchangeable units. The current catalog review below preserves the older snapshot without presenting its totals as newly recounted.
API map

Public API categories and the scope each bank documents

This table is the practical answer to "what APIs are actually visible?" It combines the current public category signals from the three banks and focuses on what a treasury or platform team can infer before entitlement.

Category Typical use J.P. Morgan public signal Bank of America public signal Citi public signal
Payment initiation Initiate domestic or cross-border payments from ERP, TMS, platform, or app. Global Payments and pilot-gated Global Payments 2 publish payment initiation and status capabilities. Payments V2 publishes POST /cashpro/payments/v2/payment-initiations for U.S. ACH credits, RTP, domestic/foreign wires, and other methods. Payments V2 reference Public Payments references cover ACH, wires, instant payments, and token-service flows; eligibility varies by market and version.
Payment status and notifications Track payment lifecycle, receive async updates, reduce manual reconciliation. Global Payments documents status and callbacks; delivery timing is indicative, not an SLA. The live catalog has a Push Notifications family as well as payment status entries. Public payment status polling, enhanced inquiry, and notification documentation are available.
Balances and account information Cash visibility, balance reporting, and account-level data retrieval. BDA Balances covers eligible Blockchain Deposit Accounts; it is not a universal bank-account reporting API. The live Account Information family contains five catalog entries. Accounts supports linked Citi and non-Citi accounts, balances, and transaction history, subject to setup.
ACH and domestic batch rails Payroll, supplier payments, bulk domestic treasury payments, and lower-cost recurring flows. Current Global Payments lists ACH for Chile only; U.S. ACH is documented in pilot-gated Global Payments 2. The ACH product page explicitly describes CashPro API payments and reporting. ACH is explicitly named in Payments documentation; confirm the U.S. payload, account, and processing arrangements.
Real-time payments Near-instant payouts, urgent disbursements, request to pay, and immediate confirmation. Global Payments real-time capabilities and the FedNow solution page document U.S. instant-payment access. RTP and Request for Payment are public; a FedNow-specific CashPro API was not confirmed in this review. Instant Payments is a public solution; Payment Acceptance explicitly documents U.S. RTP Request for Pay.
Wire and high-value transfers High-value, urgent, and cross-bank settlement flows where certainty matters more than price. Wire is explicitly documented in pilot-gated Global Payments 2. The public Payments V2 reference explicitly documents U.S. domestic and foreign wires from U.S.-domiciled accounts. Payments V2 reference Public Payments documentation explicitly names wires and provides downloadable payment specifications.
FX and cross-border overlays FX pricing, cross-border routing, and multinational treasury execution. Global Payments documents international payment methods and country-specific requirements. CashPro FX Trading API is public product evidence for FX execution, not merely a domestic operating tool. Cross Border Payments, CitiFX Gateway, Instant FX, and WorldLink quote-to-pay examples are public.
Receivables and collections Inbound collection flows, request to pay, reconciliation-ready inbound tracking. QR receivables covers Pix, PayNow, FPS, and now India UPI, with market-specific functionality. Payment requests, validation, checks, and treasury receivables products are visible; product scope varies. Payment Acceptance documents local collection methods; the historical Playbook also describes regional direct-debit and India UPI examples.
Validation, admin, and control APIs Reduce failed payments, manage security, and control access or user roles. Validation Services, User Status Management, and product-specific OAuth guidance are publicly listed. Validation Services includes SEPA payee verification, U.S. account/RTP validation, and Zelle token validation. Public OAuth/certificate guidance is detailed; Account Services includes virtual accounts and the Playbook describes user management.
U.S. market focus

Which API families matter most in the U.S. market

For the U.S. specifically, the meaningful comparison is narrower than the full global catalog. This is the operating view for domestic treasury, payouts, and real-time modernization.

U.S. API area J.P. Morgan Bank of America Citi How Citi fares
RTP Global Payments includes real-time payments; confirm version and entitlement. RTP solution and live payment/request/validation entries provide public evidence. U.S. USD Request for Pay is explicitly documented in Payment Acceptance. RTP requests, payouts, and API provisioning are distinct scopes; compare the intended flow.
FedNow Official FedNow solution page confirms participation alongside TCH RTP. No FedNow-specific CashPro API confirmation found in the reviewed sources. No FedNow-specific CitiConnect API confirmation found in the reviewed sources. Absence of a public API reference is not evidence that a bank lacks the capability.
ACH U.S. ACH is documented in Global Payments 2, which remains pilot-gated. CashPro API ACH payments/reporting are explicitly described. ACH is named in public Payments documentation. Confirm U.S. credits/debits, version, cutoffs, and eligibility rather than relying on catalog labels.
Wire Documented in pilot-gated Global Payments 2. Payments V2 explicitly documents U.S. domestic and foreign wires from U.S.-domiciled accounts. Public wire scope Wires are named in Payments documentation and payment specifications are public. The earlier claim that Citi lacks public endpoint detail is no longer accurate.
Account info and balances BDA Balances is U.S.-available for eligible Blockchain Deposit Accounts. Account Information is a five-entry public family. Accounts includes balances and transactions; published availability is 24x5, with maintenance/cutoff caveats. Match account types and history requirements; BDA coverage is not equivalent to all deposit accounts.
Status, callbacks, webhooks Dedicated callback and status documentation; typical timing is not guaranteed delivery. Payment status and Push Notifications are live catalog families/entries. Payment polling, enhanced status, and notifications are publicly documented. Validate retry, duplicate handling, reconciliation, and service commitments with each bank.
Catalog depth

The Big 3 public API catalogs, measured

Reviewed on September 14, 2026 using the live Citi marketplace, J.P. Morgan API home, and Bank of America API library. The dataset retains its July 11, 2026 capture and adds a separately dated current inventory. These portals organize their products differently; their counts are not a like-for-like capability ranking.

MeasureCitiJ.P. MorganBank of America
Current visible catalog15 business solutions: 13 API-tagged and two file-only guides; Open Banking is now included.19 distinct visible product browse entries. This is not the same unit as the July snapshot’s 64 nested API products.10 families and 78 API entries in the live catalog.
Operation/spec evidence and datesJuly 11 capture: 306 operations from 115 specifications; not a current recount.July 11 capture: 373 operations across the recorded references; not a current recount.September 14 recount: 78 OpenAPI specs, 97 operation occurrences, and 92 distinct method/path pairs. Scope is the visible library, not all bank APIs.
Reference access checkedAccounts, Payments, Virtual Cards, Payment Acceptance, and authentication content are publicly readable; some solution actions require sign-up.Public product/reference navigation and capability docs were readable. This does not mean credentials or every feature are ungated.All 78 linked OpenAPI specifications were retrieved publicly; credentials and interactive account functions still require access.
Sandbox evidenceDocumentation describes testing access and a public Postman workspace; API access and certificates still need setup.Mock and client-testing environments are distinct from production; onboarding is product-specific.CashPro describes sandbox use and client testing; confirm the current environment with the selected API specification.
Authentication scopeOAuth client credentials over mutual TLS; V4 omits application payload signing/encryption, not TLS protection.OAuth requirements differ for mock, modern JWT-based client testing/production, and legacy certificate flows.Use the current product specification and onboarding security requirements; do not apply one archived spec’s auth scheme to all families.

Method: count visible business-solution cards at Citi, distinct visible product browse entries at J.P. Morgan, and entries in Bank of America’s live library/catalog JSON. Citi and JPM full HTTP-operation totals were not re-enumerated. BofA’s 78 linked specs were parsed; repeated method/path pairs were deduplicated without assuming they represent unique services. Changes in visibility or grouping do not prove service launches or withdrawals.

Build posture

Endpoints, auth, and setup: how Citi fares against J.P. Morgan and Bank of America

This is the engineering handoff view. It focuses on what is publicly visible about endpoint style, auth, sandbox access, and go-live choreography.

Implementation dimension J.P. Morgan Bank of America Citi FinanceAI read
Public endpoint style Versioned Global Payments references and capability guides are public. Public Payments V2 reference displays POST /cashpro/payments/v2/payment-initiations, supported payment types, and code/specification content. Payments V2 reference Payments has public reference content and downloadable YAML specifications. All three support public technical discovery; documentation access is not production access.
Auth model OAuth guidance distinguishes mock credentials, modern JWT assertions, and legacy certificate arrangements. Security is product-specific; validate OAuth, certificates, and callback authentication against the current CashPro specification. Public OAuth client-credentials and mutual-TLS instructions include certificate upload/approval and version-specific payload requirements. Compare the actual chosen version and environment, not perceived simplicity.
Sandbox or mock Mock testing and client acceptance testing are documented separately. Live catalog plus CashPro sandbox case study; do not infer universal access from published hostnames. Public sandbox/testing documentation and Postman resources; provisioning still requires approved access. Sandbox language does not establish faster onboarding or a broader production entitlement.
Production setup Published stage estimates include onboarding, installation, testing, and activation; estimates are not contractual SLAs. CashPro onboarding is banker-supported and product-specific. The public guide describes access requests, certificates, testing, and production approval through Citi. Obtain a scoped implementation plan and agreed service dates from each bank.
Request and response constraints Callbacks, errors, versions, and payment parameters are documented by capability. Use the selected Payments/Push Notifications reference for formats and response handling. Accounts is documented as 24x5; specified payment initiation/status v3+ and refund v2+ operations support 24x7 subject to downtime. Availability differs by operation. A real-time rail does not make every account or support API 24x7.
Overall implementation read Useful for teams evaluating documented version and market restrictions. Useful for teams integrating payments with CashPro operations. Useful for teams combining public APIs with files, SWIFT, and multibank reporting. These are workflow-fit observations, not measured implementation-speed rankings.
Sources: Citi authentication · Citi Payments · CashPro live library · J.P. Morgan become a client · J.P. Morgan OAuth · J.P. Morgan Global Payments · Bank of America CashPro Developer Studio · Bank of America CashPro API Developer Portal · CitiConnect Developer Portal · Citi API Playbook
Confidence: High for reviewed public disclosures; production eligibility, timing, and service commitments require bank confirmation
U.S. domestic market

Validated U.S. domestic API matrix

This section is the slide-to-public-source reconciliation layer. It covers the U.S. rails and adjacent treasury tooling that matter most for corporate payments, then marks whether the capability is clearly confirmed in current official public sources or whether banker confirmation is still needed.

Capability J.P. Morgan Bank of America Citi Current read
ACH payment initiation Documented in Global Payments 2, which is still pilot-only; confirm eligibility.
ACH overview · How to initiate		 Confirmed by the current ACH page, which describes CashPro API payments and reporting.
Live API library · ACH page		 Public Payments documentation explicitly names ACH. Confirm U.S. credit/debit scope, version, and processing arrangements. Payments documentation Separate documented capability from production eligibility, especially for JPM Global Payments 2.
ACH debit, collections, and account validation GP2 documents ACH debit; Validation Services has feature-specific account checks.
ACH debit parameters · Validation Services		 The current ACH page describes Account Validation for U.S. credits and debits; the live library also lists U.S. Account Validation.
ACH + Account Validation · Funds Check Service		 The April 7, 2021 Present and Pay release is a dated U.S. biller/account-verification example, not a universal collections API entitlement.
Present and Pay · Direct Debit in the API Playbook		 Validation reduces specific risks; it does not guarantee settlement or authorize a debit.
RTP Public Global Payments RTP capability; GP2 remains pilot-gated.
RTP overview · GP2 RTP		 RTP product page, payment-request entries, and U.S. RTP validation provide public evidence.
Live API library · RTP page · Love's case study		 Current Payment Acceptance docs identify U.S. USD Request for Pay over RTP with payer approval. Payment methods An RTP request is a non-payment message; distinguish requesting funds from sending an RTP payout.
FedNow Official FedNow page confirms access to the FedNow Service alongside TCH RTP.
FedNow page		 No FedNow-specific CashPro API confirmation identified in the official sources reviewed September 14, 2026. Citi’s 2025 insurance article projected participation in both U.S. schemes by Q2 2025, subject to change. That forward-looking statement does not verify completed rollout or a current FedNow-specific CitiConnect API; confirm the intended flow with Citi.
Citi instant-payments article, page 3		 This is a public-evidence limit, not a statement that either bank cannot support FedNow.
Explicit U.S. instant-rail API endpoints Public versioned references and rail-specific examples; production access is separate.
GP2 RTP · GP2 ACH · GP2 Push to Card		 The live Payments family exposes reference routes for JSON/XML initiation, status, cancellation, and payment requests.
Live API library · CashPro API portal		 Public payment YAML specifications exist; U.S. rail-specific entitlement still requires validation. Payments API reference The earlier blanket claims that BofA and Citi lack public endpoint detail are removed.
Zelle and digital disbursements Dedicated Zelle docs; GP2 availability remains pilot-gated and delivery depends on recipient eligibility/bank.
Global Payments comparison · GP2 Zelle overview · Initiate a Zelle payment		 Digital Disbursements identifies Zelle and Venmo in the U.S.; eligibility and delivery windows vary.
Live API library · Digital disbursements		 No current CitiConnect Zelle API confirmed in the reviewed sources. Compare the recipient journey and delivery conditions; a 24x7 product is not a guarantee of immediate receipt.
Push to Card and alternative payout rails Push to Card is documented. GP2 Push to Wallet parameters specify USD, U.S. creditors, and PayPal/Venmo.
Push to Card · GP2 Push to Wallet · Push to Wallet parameters		 The Payments V2 reference describes Recipient Select, including Pay to Card, bank transfer (RTP/ACH), Zelle, PayPal, and checks for U.S. payees. Recipient Select scope
Digital disbursements · Real-time payments		 The October 10, 2024 WorldLink/Mastercard announcement explicitly includes U.S. domestic transfers and 14 receiving markets. This is not a dedicated U.S.-only API reference.
Citi + Mastercard		 Citi has public U.S. card-delivery evidence; product reach and endpoint-level access remain distinct.
Status updates, push notifications, and webhooks Payment status and callbacks are documented; typical callback timing is not an SLA.
Global Payments docs · Callbacks		 The live library includes Push Notifications and payment-status entries.
Live API library		 Current Payments documentation covers status polling and notifications. Payments overview Agree duplicate handling, retries, reconciliation, and failure recovery with each implementation team.
Treasury-adjacent forecasting and AI assist Cash Flow Intelligence and an AI copilot are publicly described. Treasury insights CashPro Forecasting and Chat with Erica are public treasury products.
Liquidity management · CashPro + Erica · CashPro Forecasting		 The 2026 Investor Day Services presentation identifies a CitiDirect AI Assistant. Investor Day, slide 8 All three have public treasury AI evidence. These tools are not equivalent to callable payment APIs or autonomous payment authority.
Sandbox and onboarding signal Public mock, testing, and onboarding guidance.
Become a client		 Public developer library and a named sandbox implementation case study.
CashPro portal · Love's case study		 Public sandbox, certificate, and testing guidance. Authentication and setup No comparative onboarding-speed claim is supported by the reviewed evidence.
International market

Cross-border and international API matrix

International comparisons must distinguish payment origination, destination, currency, local collection methods, and API entitlement. The dated network statistics below describe different products and should not be treated as directly comparable API coverage counts.

Capability J.P. Morgan Bank of America Citi Current read
Unified cross-border payment API Current Global Payments documentation lists 45+ countries with payment-method restrictions.
Global Payments		 The October 2022 announcement described 350+ payment types in 38 markets; this is historical product reach, not today’s catalog count.
CashPro Payment API		 WorldLink’s October 2024 release cites 135+ currencies; Platform and Data Services cites 90+ markets/130+ currencies as of November 2025.
WorldLink + Mastercard · Platforms and Data Services · Cross Border Payments solution		 Do not rank breadth using different dates, products, or origination/destination units.
FX quote to payment execution Global Payments documents cross-currency payment requirements; absence of a dedicated card in this review is not evidence that treasury FX APIs do not exist. CashPro FX Trading API publicly describes spot, forwards, swaps, and NDFs with 24x5 access, subject to product terms. FX Trading API The Playbook demonstrates WorldLink rate inquiry followed by payment initiation; current CitiFX Gateway and Instant FX solution pages are public.
WorldLink quote-to-pay · CitiFX Gateway solution · Instant FX solution		 All FX workflows need quote validity, execution, settlement, and entitlement checks.
India UPI and request-to-pay collections India UPI is now listed as available for Request to Pay via QR Code, alongside Pix, PayNow, and FPS.
JPM QR receivables overview		 June 4, 2026 announcement planned cross-border payouts to India UPI in the following quarter; this is not a domestic UPI-collection API or confirmed completed rollout. Announced expansion The undated API Playbook documents an India UPI collection case study. Confirm current scheme rules, consent, and implementation.
UPI request-to-pay · UPI in glossary		 JPM’s “coming soon” claim is removed. BofA’s announced payout scope is different from Citi/JPM collection flows.
Direct debit outside the U.S. Direct-debit support is method- and market-specific; use the selected API’s parameters.
ACH direct debits		 Do not infer an Asia-wide direct-debit API footprint from Pay by Bank or digital-disbursement product pages.
Pay by Bank · Digital disbursements		 The Playbook glossary lists Australia, Singapore, and Hong Kong direct-debit initiation; it is a historical/undated example, not a current availability matrix.
Direct Debit glossary		 Validate local mandates, cutoffs, currencies, and debit authorizations before comparing coverage.
Reference data APIs: cutoffs and holidays No comparable dedicated cutoff/holiday reference-data API confirmed in this review. No comparable dedicated cutoff/holiday reference-data API confirmed in this review. The Playbook glossary describes cutoff-time and branch-holiday APIs; confirm current versions and supported data.
Cutoff + holiday APIs		 A public-documentation gap does not establish a capability gap.
Virtual cards API No directly comparable treasury virtual-card API reference established by this review; request product-specific evidence. Virtual payables is public product evidence; confirm API access and market scope separately.
Virtual payables		 Public Virtual Cards documentation covers card controls, notifications, and network-specific reporting. The 46-country/30+ currency statistic belongs to the October 17, 2022 release. Virtual Cards documentation Do not convert a dated issuance statistic into a current universal API footprint.
Tokenized or blockchain-based liquidity rails Kinexys Digital Payments is documented in Global Payments with participating-location restrictions.
Kinexys Digital Payments		 No equivalent programmable-settlement API established by this reviewed source set. Citi Token Services and 24/7 USD Clearing have branch/account constraints. Separately, Citi’s September 2, 2026 release reports live Swift-ledger transactions with FAB/OCBC within a controlled July–December proof of concept, not an unrestricted production API. Swift-ledger pilot
Citi Token Services · Citi Token Services for Cash solution		 The two tokenized-liquidity offerings are not interchangeable and are not open cryptocurrency networks.
Cross-border instant destinations, wallets, and cards Global Payments includes wallet, card, Interac, and local real-time methods with version/market restrictions.
Global Payments comparison		 Digital Disbursements includes U.S. Zelle/Venmo, Canadian Interac, and PayPal in selected markets; the June 2026 cross-border RTP rollout is announced separately.
Digital disbursements · Real-time payments		 WorldLink’s October 2024 Mastercard announcement includes 14 receiving markets and U.S. domestic transfers; subsequent destinations require current corridor confirmation.
WorldLink + Mastercard · Citi + Dandelion		 Recipient eligibility, full-value delivery, currency conversion, and settlement timing need corridor-level checks.
User and admin APIs User Status Management is a visible public catalog entry; obtain its precise operational scope. User Status Management No comparable treasury user-admin API confirmed in the selected public sources; CashPro role controls are not automatically an API. The Playbook describes creating/enabling/disabling CitiDirect BE users. Verify the current product and entitlement.
User Management		 JPM is no longer described as having no public user-administration entry.
Cards / Trade / Digital Assets

What is established publicly beyond core payment rails

The attached slides also pushed into cards, trade finance, and digital-asset-linked flows. The official public record is uneven here, so this section separates what is clearly documented from what still needs banker confirmation.

Confirmed

Kinexys is a documented restricted-access payment rail

Kinexys Digital Payments is documented through Global Payments for participating accounts and locations. GP2 integration remains inside the broader pilot scope.

Partly confirmed

Separate BofA products from API entitlement

Virtual payables, digital disbursements, and CashPro treasury tools are public. Market-specific product support should not be inferred from a catalog count or treated as identical to a card API entitlement.

Public-confirmation watchlist As of September 14, 2026, Citi virtual accounts are publicly listed and are no longer an unconfirmed product claim. Exact virtual-account API access, BG/SBLC lifecycle endpoints, and BofA/Citi FedNow-specific API scope still require bank confirmation.
Infrastructure layer

U.S. dual rail means two instant-payment rails, not a complete treasury stack

The U.S. instant-payments market is now structurally dual rail: The Clearing House RTP network and the Federal Reserve's FedNow Service operate side by side. But enterprise treasury buyers still need more than rail access. They need initiation, status, exceptions, approvals, reporting, entitlement mapping, and fallback paths into ACH and wire.

Rail 1

RTP

RTP remains the earlier U.S. instant rail and is often the clearest shorthand for business-triggered real-time payments, request for payment, and immediate confirmation.

Always on Business messaging Request for payment
Rail 2

FedNow

FedNow extends instant settlement through the Federal Reserve system and makes the domestic real-time conversation impossible to frame around a single network.

Federal Reserve 24x7x365 Domestic liquidity speed
Operating reality

APIs still sit above ACH and wire

For large corporates, instant payments complement rather than replace ACH, wires, and controls. The winning bank surface is the one that explains how those pieces fit together.

ACH adjacency Wire fallback Control plane
Sources: Federal Reserve FedNow overview · The Clearing House RTP network · J.P. Morgan Global Payments docs
Confidence: High for market structure; Medium-High for strategy interpretation
J.P. Morgan watchouts

J.P. Morgan APIs with beta status, pilot gating, or market restrictions

Looking holistically across the J.P. Morgan URLs shared for this review, the portal is strong precisely because it publishes the constraints as well as the capabilities. The important distinction is that some limits are beta or pilot-stage, some are country or market-specific, and some are account-entitlement restrictions.

J.P. Morgan API / product Public status Official restriction or availability signal Why it matters
Global Payments 2 Pilot-gated. Global Payments documentation continues to limit GP2 live integration to pilot clients, even though capability references are public.
Global Payments docs · API overview · GP2 ACH · GP2 RTP · GP2 Zelle · GP2 Push to Card · GP2 Push to Wallet · GP2 Callbacks		 Treat public documentation as design evidence, not general availability.
Global Payments current version Current product; entitlement required. The comparison table restricts current-version ACH to Chile. Broad Global Payments coverage does not mean every rail is available in every country.
Global Payments docs		 Check the capability table and API version.
Checks API U.S./Canada; v2.x for new integrations. The reviewed Checks overview does not show the earlier beta label. Version and country requirements remain explicit.
Checks docs · Checks API overview · Checks resources		 Do not carry forward a beta label without current evidence.
GP2 Zelle Disbursements Within GP2 pilot scope. Zelle is a documented U.S. disbursement flow; recipient eligibility and recipient-bank processing affect delivery.
Zelle overview · Initiate a Zelle payment		 Confirm limits and recipient conditions from the selected current parameters rather than an unverified universal cap.
GP2 Push to Wallet Within GP2 pilot scope. Published parameters specify USD, U.S. creditor country, PayPal/Venmo, and amounts from 0.01 to 60,000; beta parameters can change.
Push to Wallet overview · Payment parameters		 This is a scoped U.S. wallet profile, not global wallet availability.
Validation Services Feature- and geography-specific. The overview anchors API service availability in the U.S.; Account Validation documents U.S. and Ireland-related coverage, and Entity Validation covers customers in 50+ countries.
Validation Services docs · API overview · Account Validation · Entity Validation countries		 Service location, account jurisdiction, and entity coverage are different dimensions.
BDA Balances Eligible Blockchain Deposit Accounts. The current Balances capability identifies U.S. availability and current/historical balances for eligible accounts.
BDA Balances docs · Balances capability · API overview		 Do not equate Kinexys’s broader location list with BDA Balances API country coverage.
Embedded Payments Version and eligibility require confirmation. The reviewed overview no longer supports the blanket claim that Accounts v2 and Transactions v3 are beta. Use the selected product reference and commercial onboarding conditions.
Embedded Payments docs · Embedded Payments index · Core concepts		 Avoid stale version-status labels and confirm the intended jurisdiction.
Pay by Bank AIS and PIS have different coverage. AIS: U.S., U.K., Germany, Italy, Spain, Netherlands, Austria. PIS: U.K. and those five EU countries. New integrations use V2. The U.K. recurring-payment summary and “coming soon” capability label should be clarified with the bank.
Pay by Bank · Core concepts · Initiate a payment		 U.S. account-information availability does not mean U.S. payment initiation is supported.
Receivables / Request to Pay via QR India UPI now listed as available. The overview lists Brazil Pix, Singapore PayNow, Hong Kong FPS, and India UPI. Payment links, bulk scheduled QR generation, and update functionality have Brazil-specific limits; the reviewed overview does not show the earlier beta label.
Receivables · QR overview · Get payment request details		 Carry market-specific features into the implementation plan.
Kinexys Digital Payments Current Global Payments; GP2 pilot restrictions apply. Published locations include the U.S.; Luxembourg, London, Frankfurt, Dublin, Amsterdam; and Hong Kong, Singapore, Sydney. Eligible accounts and integration arrangements still apply.
Kinexys in Global Payments · Kinexys in Global Payments 2		 Location coverage is not unrestricted global availability.
Read status labels at the product and version level. A removed beta label is not proof of unrestricted general availability; a visible reference does not override pilot gating, eligible-account rules, or a country table.
Reference bank

J.P. Morgan: versioned payments documentation and explicit restrictions

J.P. Morgan publishes an API catalog plus capability guides, authentication, response codes, and versioning. Its Global Payments comparison is useful because it distinguishes the current product from pilot-gated Global Payments 2.

The current Global Payments documentation lists more than five methods across 45+ countries, with initiation, status, and callbacks. That product-level reach is not a promise that every listed rail works in every market.

Checks, Validation Services, BDA Balances, Embedded Payments, and Pay by Bank have their own country, account, version, or feature restrictions. The current visible browse inventory is recorded separately from the July nested-API snapshot.

Current version

Global Payments

Current Global Payments covers multiple methods and countries subject to the published capability table, account eligibility, and onboarding.

Next step

Global Payments 2

Global Payments 2 documents ACH, wire, idempotency, and granular errors; live integration remains limited to pilot clients.

Selected official feature signals Global Payments Global Payments 2 Why it matters here
Real-time payments Documented Documented; pilot scope Confirm rail and market availability per version.
ACH Chile only in the current comparison Documented; pilot scope Do not advertise U.S. ACH in the current version from the overall product name.
Wire Not listed as supported in the current comparison Documented; pilot scope Wire capability in GP2 is not evidence of general rollout.
Business duplicate checks Documented Documented Use bank-prescribed duplicate controls and reconciliation.
Idempotency and granular error handling Compare selected reference version Explicitly described Implementation requirements are more useful than an unmeasured maturity ranking.
Global Payments

Multi-method payment family

The docs say the current Global Payments API lets clients initiate payments across multiple payment methods and countries with a single API.

  • Multiple methods with distinct market restrictions
  • Status and payment-detail retrieval in the product family
Global Payments 2

Pilot-gated product evolution

Global Payments 2 is already public in documentation and adds ACH, wire, idempotency, and granular error codes for pilot clients.

  • Public roadmap is separate from rollout completion
  • Validate error handling against the selected API version
RTP + FedNow

Published U.S. dual-rail participation

The official FedNow page identifies participation in both FedNow and TCH RTP. Confirm eligible flows, routing, and API version during onboarding.

  • FedNow and TCH RTP are explicitly named
  • Confirm routing and eligible sending/receiving flows
Portal design

Public reference navigation

The portal supports product discovery and technical review. Public reference navigation does not grant credentials, testing access, or production entitlement.

  • Visible catalog entries are not endpoint-operation totals
  • Credentials and production access require setup
Sources: J.P. Morgan API reference home · Quick start · Global Payments documentation · Global Payments API overview · GP2 Callbacks · GP2 Zelle · Zelle initiation guide · Push to Wallet parameters · Receivables QR overview · Receivables payment-request details · Pay by Bank · Pay by Bank core concepts · Pay by Bank initiate payment · Checks docs · Checks API overview · Validation Services docs · BDA Balances · Embedded Payments · FedNow solution page · Balances capability
Confidence: High
Domestic operator

Bank of America reads like a CashPro operating stack with API leverage

Bank of America combines CashPro operations with a live public API library. Its September 14 inventory contains 78 entries across 10 families; separate FX and treasury-tool product pages show why library counts are not a complete inventory of every offering.

CashPro API

Treasury-first API story

The current library includes Account Information, Payments, Push Notifications, Validation Services, Check Services, Brazil, Supply Chain Finance, and Global Markets-related families.

  • Assess fit with existing CashPro operations
  • Public library includes product families and reference routes
ACH + RTP

Strong domestic breadth

ACH payments/reporting and RTP are public. The June 4, 2026 announcement planned cross-border real-time payments through API, host-to-host, and SWIFT for the following quarter; rollout completion was not confirmed in this review. Announcement

  • ACH and RTP serve different timing and control needs
  • Announced cross-border expansion is not confirmed completed rollout
Sandbox proof

Operational credibility

The Love’s Financial case study documents a specific CashPro API/RTP sandbox implementation. It is evidence of that deployment, not a universal onboarding schedule.

  • Named implementation example, not a general SLA
  • Sandbox access requires the relevant onboarding arrangement
CashPro control plane

Approvals, reporting, and mobile oversight

CashPro includes approvals, reporting, mobile oversight, forecasting, and Chat with Erica. The separate CashPro FX Trading API page describes spot and derivative FX workflows; Merchant Services APIs should not be treated as identical to CashPro. FX Trading API

  • Treasury tools and payment APIs are different layers
  • Verify product-specific security and market entitlement
Sources: CashPro Developer Studio · CashPro API Developer Portal · ACH payments · Global real-time payments · Love's Financial RTP case study · CashPro app · Healthcare Reporting API
Confidence: High for product and case-study signals; Medium-High for comparative interpretation
Strategic read

Citi: public API references within a multichannel treasury network

Citi publishes technical references for payments, accounts, virtual cards, payment acceptance, and authentication. Its wider proposition includes file/SWIFT connectivity, ERP/TMS integrations, WorldLink, and tokenized cash. Public U.S. RTP request evidence should not be converted into an unverified FedNow claim.

Developer portal

Public documentation and sandbox resources

The current marketplace has 15 business-solution cards, including Open Banking. Public references and sandbox material coexist with sign-up and banker-led access requirements.

  • Technical discovery is publicly possible
  • Approved credentials are still needed
Payments and Receivables

Dated Payments Express coverage

The 2026 Investor Day Services presentation reports Payments Express in 22 markets as of December 2025, excluding Argentina. This dated platform measure differs from the older five-country card still visible in the developer solution page. Investor Day, slides 7 and 15

  • Separate platform footprint from bank-network reach
  • Preserve the date attached to published statistics
Always-on network

Eligible always-on clearing and liquidity

Citi’s 24/7 USD Clearing and Token Services materials describe always-on bank connectivity for eligible accounts and participating branches. Receiving-bank processing and product limits still matter.

  • Validate participating branches and receiving-bank behavior
  • Confirm currencies, eligibility, and service conditions
Citi Payments Express

A consistent API with market-specific scope

Payments Express is a globally consistent integration proposition, but market availability and API entitlement must be confirmed separately. Do not substitute broad bank-network statistics for supported endpoint coverage.

  • Use market-specific reference and onboarding evidence
  • No overall bank ranking is implied
Global network abstraction
Lower U.S. rail explicitness Higher U.S. rail explicitness

Documented evaluation strengths

Multichannel connectivity, public account/payment references, regional integrations, and cross-border liquidity are documented considerations for multinational treasury teams.

Public-evidence limits

A dedicated CitiConnect FedNow API was not confirmed. Some marketplace products need sign-up, and older publications are not current country-by-country API availability matrices.

Implementation takeaway

Evaluate Citi’s documented APIs and connectivity against the required accounts, corridors, currencies, and controls; obtain explicit confirmation for any U.S. rail or product not covered by the public references.

Sources: Citi Account Services · Citi Domestic Payments · Citi Instant Payments · Citi Cross Border Payments · Citi Payment Acceptance · Citi Commercial Cards · Citi Custody · Citi ETF Services · CitiFX Gateway · Citi Instant FX · Citi ISO · Citi Token Services for Cash · CitiConnect Developer Portal · Payments and Receivables · 24/7 USD Clearing · Instant payments in insurance · Citi Token Services + 24/7 USD Clearing
Confidence: High for portal and network facts; Medium-High for the positioning conclusion
Strategic implications

What the market divide means by client segment

These are financeAI workflow-fit inferences from the official sources, not bank performance rankings or recommendations to buy a product.

Corp — Multinational

Multinational treasury: compare corridors and integration requirements

Citi’s multichannel integration, WorldLink, and regional collection examples are relevant to global payment factories. Compare them with JPM’s method/country tables and BofA’s CashPro/FX offering against actual corridors and accounts.

Corp — U.S. Domestic

U.S. treasury: compare rails, controls, and eligibility

JPM documents U.S. instant rails and pilot-gated GP2 expansion; BofA combines ACH/RTP with CashPro operations; Citi has public ACH/wire and RTP request evidence. All three now have public treasury AI-tool disclosures.

FI — Cross-Border Corridors

Financial institutions: compare participating accounts and networks

Citi Token Services/24x7 clearing and JPM Kinexys have different participating-account, currency, and network constraints. Neither should be represented as unrestricted global programmable settlement.

Public Sector / Mass Disbursements

Mass disbursements: compare recipient methods and restrictions

JPM documents Zelle/card/wallet flows; BofA describes U.S. Zelle/Venmo, Canadian Interac, and selected PayPal markets; Citi’s WorldLink Mastercard release includes U.S. domestic transfers. Compare delivery conditions and recipient eligibility.

Comparison summary

Quick comparison guide

How to frame the three-bank story in one screen This is the piece to use when you need an internal answer fast.
Dimension J.P. Morgan Bank of America Citi What it means
Public U.S. instant-rail clarity FedNow and TCH RTP explicitly named. RTP public; FedNow-specific API not confirmed. U.S. RTP Request for Pay public; FedNow-specific API not confirmed. Public evidence is not a complete bank capability inventory.
ACH and wire adjacency U.S. ACH/wire documented in pilot-gated GP2. ACH payments/reporting and CashPro Payments are public. ACH and wires named in public Payments references. Confirm country, direction, version, and onboarding.
Sandbox and onboarding signal Mock and client-testing guidance. Public library and sandbox case study. Public sandbox, certificates, and testing guidance. No verified comparative onboarding-speed ranking.
Status, servicing, and control signal Status and callback documentation. Payment status, Push Notifications, and CashPro controls. Payment polling/notifications and account references. Match retry, reconciliation, approval, and support requirements.
Global operating-model fit Country- and method-specific payment capabilities. CashPro, FX trading, and announced cross-border RTP expansion. Multichannel connectivity, WorldLink, and eligible token/clearing services. Compare the same corridor and operating requirements.
Best-fit pitch Evaluate versions, restrictions, and rail documentation. Evaluate CashPro integration and operating tools. Evaluate multichannel and cross-border integration. Select by verified requirements, not a universal winner.
If the brief is domestic instant-payments API leadership Check J.P. Morgan’s documented rails and pilot restrictions, then validate each bank against the required U.S. flow.
If the brief is U.S. treasury execution with strong ACH and approvals context Evaluate CashPro’s APIs and approval model alongside the competing implementations.
If the brief is a multinational treasury or FI platform story Evaluate Citi’s corridor and account coverage alongside JPM and BofA using consistent requirements.
Source register

Source notes

Official sources were reviewed on September 14, 2026. Dated releases and the July catalog snapshot remain historical evidence, not current rollout certifications. Source-map interpretations are financeAI analysis; availability still requires bank confirmation.

Citi

Network reach, portal discovery, and TMS / payments proof points