APIs and connectivity: public portal comparison
This page compares major banks using what is publicly visible in developer portals and official product/implementation pages. It focuses on discoverability, onboarding visibility, documentation clarity, and public limitations (what is not visible publicly). It now includes a requested 10-bank API cohort for J.P. Morgan, Citi, HSBC, Bank of America, Barclays, Goldman Sachs, BNP Paribas, UBS, RBC, and TD.
Confidence: Medium (portal content can change; private onboarding can add scope)
Legal/compliance review: Recommended before publication
Citi vs JPMorgan: API visibility comparison
A careful, factual view based on public disclosures and public portal documentation.
| Dimension | Citi (public view) | JPMorgan (public view) | Client implication | Confidence |
|---|---|---|---|---|
| API categories publicly visible | CitiConnect® public materials describe balances, payment status, and FX-related examples; full category inventory may vary by segment/region. | Public portal provides a navigable documentation index and onboarding narrative; category detail is easier to traverse publicly. | Use portal visibility to plan discovery. Confirm scope and eligibility early with the bank. | |
| Documentation clarity | Public disclosures are clear at a high level; technical detail may require portal navigation and client context. | Public portal documentation reads like a guided path, including onboarding steps and timing signals. | If your team includes non-developers, stronger narrative docs can reduce translation work. | |
| Onboarding visibility | Implementations and testing portals are referenced publicly; end-to-end steps often shift into engagement. | Public portal describes a phased onboarding timeline and testing-to-production journey. | Clear public onboarding steps can reduce early ambiguity; validate timelines with your bank team. | |
| Sandbox / test environment visibility | Public materials reference a testing portal; details may require access. | Public onboarding documentation references a mock environment and testing stages. | Early access to test environments helps with parallel build and data mapping. | |
| Region / market visibility | Connectivity routes are described publicly (API, files, SWIFT, ERP integration), but region differences can be dispersed across pages. | Portal is global in orientation; region-specific product differences may still require confirmation. | Build market-specific plans (NAM/U.S./Canada) and confirm eligibility per region. | |
| Public commercial/pricing visibility | Pricing and commercial terms are typically not publicly disclosed in developer portals. | Same common pattern: commercial terms are handled via client engagement. | Plan procurement/legal work in parallel with technical design. |
JPM sources: J.P. Morgan llms.txt (undated) · Become a client (undated)
Last verified: April 6, 2026
Publicly visible API considerations and limitations
Neutral, factual guidance focused on what is visible publicly and what typically must be confirmed during onboarding.
Public portals are not complete inventories
Developer portals typically show a curated subset of capabilities. Full scope can depend on client segment, geography, and entitlements.
Confidence: High
Region and eligibility differences are common
APIs and connectivity options can differ by country, entity, currency, and product. Treat public pages as starting points, not definitive eligibility statements.
Implementation steps often move into engagement
Some banks publish onboarding steps publicly; others reference implementations teams and testing portals. Even with public steps, certification and operating model readiness are usually engagement-led.
Confidence: Medium
Commercial terms are usually not public
Pricing, SLAs, and eligibility terms are typically handled through relationship and contracting. Avoid publishing claims about latency/uptime unless officially disclosed.
Related: Legal page
Client operating model matters
APIs change ownership boundaries: entitlement admin, exception handling, reconciliation mapping, and control models. Use a client-side checklist before kickoff.
Hybrid connectivity is normal
APIs often coexist with host-to-host and files (especially for high volume). Design for both: initiation, status, and reconciliation flows.
Public API category map and entitlement paths
Requested API comparison cohort: J.P. Morgan, Citi, HSBC, Bank of America, Barclays, Goldman Sachs, BNP Paribas, UBS, RBC, and TD.
Authorized-access rule: financeAI.tech does not attempt to bypass gated portals. If a bank does not publish a numeric technical constraint publicly, the limitation is recorded as Not disclosed in public portal; requires entitlement.
How to read this matrix
The first table maps which API families are visible publicly and how a treasury team legitimately gets access. The second table gives one representative API limitation per bank, with hard limits only where the bank publishes them.
| Bank | Public API categories visible | Legitimate entitlement path | Public portal link | Last verified |
|---|---|---|---|---|
| J.P. Morgan |
Global Payments
Pay by Bank
Receivables
Checks
Liquidity & Account Solutions
Validation Services
Embedded Finance
Blockchain Deposit Account Balances
|
Create a developer account, align to the J.P. Morgan client journey, stand up a project, test in the published environment, and then request production credentials through the bank's onboarding flow. | J.P. Morgan API catalog Become a client |
Apr 6, 2026 |
| Citi |
Balances
Statements
Payments
Payment Status
FX / WorldLink
Notifications
Direct Debit
Authentication
User Management
|
Public playbooks and implementation pages show the use cases, but detailed testing access and production scope move into Citi onboarding and client engagement. | developer.citi.com Citi API Playbook |
Apr 6, 2026 |
| HSBC |
Open Banking
Corporate APIs
Banking as a Service
Securities Services
Account Information
Payments
Merchant Services
|
Register on the public developer portal, choose the API family, and complete the consent or client-entitlement flow required for that product and market. HSBCnet-linked corporate flows add separate bank-side entitlements. | develop.hsbc.com | Apr 6, 2026 |
| Bank of America |
US RTP
Payment Initiation
Global Digital Disbursements
US ACH Credit Transfers
Account Information
Funds Check Service
Check Image Retrieval
Push Notifications
|
Bank of America's public access form asks for client context, source IP or IP range, and capacity planning details before credentials are issued through the bank's API operations process. | developer.bankofamerica.com Public developer portal |
Apr 6, 2026 |
| Barclays |
Payment APIs
Open Banking
US Cards
|
Use the Barclays API Exchange catalogue and sandbox first, then register for a live account and follow the production connection guides for the selected API family. | Barclays API Exchange Support and help guides |
Apr 6, 2026 |
| Goldman Sachs |
Payments
Reporting
Foreign Exchange
Entity Management
Account Management
Webhooks
|
Create an application in the developer portal, subscribe to Transaction Banking APIs, and complete implementation-led production onboarding for the required services. | Goldman Sachs TxB docs | Apr 6, 2026 |
| BNP Paribas |
Account Information
Funds Confirmations
Supply Chain
Cash Account Information
Fund Access
Corporate Actions
Securities APIs
|
Register on the BNPP CIB API portal, create an application, and subscribe to the required APIs. Sandbox and production access are controlled through the bank's authorization flow. | BNP Paribas CIB API portal | Apr 6, 2026 |
| UBS |
QR Portal API
key4 Mortgage Offer
bLink Account
bLink Payment
PSD2 Account
PSD2 Payment
Funds Confirmation
Securities Settlement Status
|
Register or log in, choose the product, and request the subscription or API reference path published for that product. Availability depends on client consent and jurisdiction. | UBS API products | Apr 6, 2026 |
| RBC |
Move Money
Pay
Balance & Transactions
Tracking
Validation
Integration APIs
|
RBC routes API access through a relationship manager or APISupport@rbc.com; live access is not a public self-serve workflow. | RBC Business Banking APIs | Apr 6, 2026 |
| TD |
Data APIs
Transactions
Statements
Bills
Rewards
Images
Token APIs
Apps Management
Notifications
Consent
|
Join the network through the TD developer portal, create a test app, generate credentials, and manage subscriptions through the published management and notification workflows. | TD developer portal guide | Apr 6, 2026 |
Public API limitations database
Representative treasury-relevant API rows only. Hard limits are shown only when the bank publishes them in public documentation.
| Bank Name | API Category | API Name | Use Case | Technical Capability & Specific Limitation | Documentation Link |
|---|---|---|---|---|---|
| J.P. Morgan | Payments | Zelle Disbursements | Initiate near-real-time U.S. reimbursements or claim payouts from a treasury workflow. | Public documentation states a maximum of $100,000 per transaction; production use still requires project setup and issued credentials. | J.P. Morgan Zelle docs |
| Citi | Payments / Reporting | Payment Status Inquiry API | Track the state of an outbound payment from ERP or TMS exception queues. | Public playbook states a status inquiry can be made for one payment per request; implementation moves through Citi onboarding and entitlement. | Citi API Playbook |
| HSBC | Accounts | Account Information API | Pull balances and recent transactions for liquidity visibility and automated reconciliation. | Public implementation guidance limits transactions to the last 90 days; restricted-access sessions last 60 minutes, or 180 minutes for HSBCnet-linked access. | HSBC developer portal |
| Bank of America | Payments | US RTP API | Initiate U.S. real-time payments directly from treasury operations or ERP workflows. | Not disclosed in public portal; requires entitlement. Public access materials ask for client context, source IP or range, and capacity planning before credentials are provisioned. | BofA public portal |
| Barclays | Payments | Payment APIs | Support payment initiation and orchestration from a connected treasury or finance stack. | Not disclosed in public portal; requires entitlement. Official guidance points teams to sandbox usage first, then live-account registration and production connection steps. | Barclays API Exchange |
| Goldman Sachs | Payments | Payments API | Submit batched supplier, customer, or intercompany payment instructions from treasury systems. | Public Transaction Banking docs state a request can include up to 500 individual payments or collections. | Goldman Sachs Payments docs |
| BNP Paribas | Accounts | Cash Account Information API | Retrieve balances and transaction history across cash accounts for treasury reporting. | Public portal guidance describes access to up to 3 years of historical data. | BNP Paribas CIB API portal |
| UBS | Payments | bLink: Payment API | Submit Swiss payments from the account of a consenting corporate client. | Not disclosed in public portal; requires entitlement. The public product page shows subscription and API reference access flowing through the product enrollment path. | UBS API products |
| RBC | Accounts | RBC Balance and Transactions API | Feed real-time balances and transactions into ERP or TMS cash-position reporting. | Not disclosed in public portal; requires entitlement. RBC publicly routes access through a relationship manager or APISupport@rbc.com. | RBC Business Banking APIs |
| TD | Accounts / Transactions | Search for Account Transactions API | Pull account activity into finance systems for reconciliation and cash visibility. | Public implementation docs state a maximum page limit of 200 records; checking history is 3 months, savings history is 13 months, and some card endpoints cap at the last 3000 transactions. | TD implementation guide |
Last verified: April 6, 2026
Peer portals and official links (starting points)
A short list of major bank developer portals for cross-checking. Portal visibility varies and can change.
| Bank | Public portal / official link | Notes (public-evidence view) | Last verified |
|---|---|---|---|
| Citi | developer.citi.com | Public CitiConnect® API disclosures and implementation pages provide additional context. | Apr 6, 2026 |
| JPMorgan | developer.payments.jpmorgan.com | Public onboarding timeline and documentation index visible. | Apr 6, 2026 |
| Bank of America | developer.bankofamerica.com | Portal visibility varies by product family; validate for treasury use cases. | Apr 6, 2026 |
| HSBC | develop.hsbc.com | Public documentation visibility for account and payments-related APIs. | Apr 6, 2026 |
| Barclays | developer.barclays.com | Public catalogue, sandbox, and production-connection help guides are visible. | Apr 6, 2026 |
| Goldman Sachs | developer.gs.com | Public Transaction Banking documentation is visible for payments, reporting, FX, and webhooks. | Apr 6, 2026 |
| BNP Paribas | BNP Paribas API portal | Public portal exists; detail varies by API family. | Apr 6, 2026 |
| UBS | developer.ubs.com | Public product catalogue is visible; access depth depends on subscription and jurisdiction. | Apr 6, 2026 |
| RBC | RBC Business Banking APIs | Public API page exists; live access is relationship-managed rather than self-serve. | Apr 6, 2026 |
| TD | TD developer portal | Public getting-started and implementation docs are visible for the commercial and consumer API network. | Apr 6, 2026 |