JPM Payments Developer Portal — Full API Catalog
Source: Screenshots of the JPM Payments Developer Portal "Browse our APIs / All products" view (2026-05-11). Use this as the master checklist before doing any OAS-hunt or planning new spec sections — to ensure we haven't missed a product that's already available.
Working principle: Every JPM product card is a potential OAS to evaluate. For UTA's integration spec, walk this list top-to-bottom and ask: "Does our spec cover this? If not, is it in scope? If yes, do we have the OAS?" The catalog is the structural floor; ad-hoc discovery is the structural ceiling.
How to read this catalog
| Column | Meaning |
|---|---|
| Product | Name as it appears on the JPM "All products" page |
| One-line purpose | JPM's published description (verbatim) |
| UTA scope | In-scope (covered in spec) · Evaluate (potentially useful, not yet decided) · Out-of-scope (clearly not for UTA's Klutch operating-account use case) · Future-state (deferred) |
| OAS status | Downloaded (in Playbook/) · Available — not downloaded · No separate OAS (inside a parent product) · Unknown |
| Spec § | Section where covered |
| Notes | Open items, gotchas, or relationship to other products |
Treasury Reporting
| Product | Purpose | UTA scope | OAS status | Spec § | Notes |
|---|---|---|---|---|---|
| Account Balances | Real-time and historical account balances by flexible queries | In-scope | Downloaded (v1.0.5) | §6.2 | EOD anchor for §9 Three-Way Match |
| Transaction Details | Comprehensive incoming/outgoing transactions with date ranges, pagination, lockbox detail | In-scope | Downloaded (v3.1.8) | §6.1 | CNB BAI2 replacement; tier: LEGACY |
| Onboarded Accounts | Retrieve list of all onboarded accounts including account numbers, names, currencies, types, bank identifiers | Evaluate | Available — not downloaded | (TBD) | Could be useful for verifying Klutch entitlement once CAT lands |
| Reporting | Transaction-level payment reports with flexible options for report types, scheduling, file formats | Evaluate | Available — not downloaded | (TBD) | May overlap with Transaction Details; investigate scope |
| Payment Inquiry | Retrieve detailed information about a payment investigation or inquiry | Evaluate | Available — not downloaded | (TBD) | For exception research; lower priority |
| Virtual Account Balances | Intraday and EOD balance details for J.P. Morgan virtual accounts | Out-of-scope | — | — | UTA's Klutch is a single operating account, not a virtual-account program |
| Virtual Account Postings | Transaction postings for virtual accounts | Out-of-scope | — | — | Same reasoning as above |
Treasury Payments — Outbound
| Product | Purpose | UTA scope | OAS status | Spec § | Notes |
|---|---|---|---|---|---|
| Global Payments 2 | Initiate, track, and manage a wide range of payment types and returns across multiple currencies and geographies through a single, consistent interface | In-scope | Downloaded (v2.4.7) | §7.2 RTP · §7.3 ACH Credit · §7.4 ACH Debit · §7.5 Wire · §6.6 Callbacks · §7.6 FX | THE core outbound product — RTP/ACH/Wire/etc. all live here |
| Global Payments (v1) | Initiate, track, and manage various payment types across international markets | Out-of-scope | — | — | DEPRECATED — Jessica Jin 2026-03-03: "GPV1 will be deprecated eventually, I would not recommend building to GPV1 as a fallback" |
| Wire Payments | Allows financial institutions with J.P. Morgan accounts to securely initiate high-value wire credit transfers, including cover payments | Out-of-scope | Downloaded (v2.0.5) | §7.5 (distinction note only) | RESOLVED 2026-05-11. OAS confirms this is the FI-to-FI (correspondent banking) wire product, not a corporate wire product. OAS requires initiatingParty.id.organizationId.other.id: "BANK" and all 3 OAS examples are labeled "US FI to FI." UTA is a corporate (talent agency), not a financial institution, so UTA's wires belong in GP2 (§7.5). Earlier-session claim "no separate Wire OAS exists" was technically wrong (a separate Wire OAS does exist), but the underlying conclusion (UTA uses GP2 for wires) was correct. |
| Faster Payments - U.S. RTP | Initiate, track, and retrieve details for real-time payments, including support for payment status queries, return of funds requests, and information retrieval across supported clearing systems | Evaluate | Unknown | §7.2 (potentially) | May be a US-RTP-specific surface or a doc page pointing back to GP2 RTP. Investigate before relying solely on GP2 RTP |
| Low Value and ACH Payments | Initiate and manage low value ACH credit transfer payments | Out-of-scope (likely overlap with GP2) | Unknown | — | Likely GP1-era surface superseded by GP2 ACH Credit (§7.3). Verify with Jessica before treating as authoritative |
| Low Value and ACH Direct Debits | Initiate and manage low-value direct debit payments | Out-of-scope (likely overlap with GP2) | Unknown | — | Same — likely superseded by GP2 ACH Debit (§7.4) |
| Push to Card | Send near real-time payments from your account directly to a recipient's eligible Visa or Mastercard debit or prepaid card | Out-of-scope | — | §7.10 (mentioned only) | Already covered as out-of-scope GP2 rail |
| Corporate Quick Pay | Send payments to individuals or businesses using Zelle, ACH, RTP, or check, leveraging email address or bank account information | Out-of-scope (likely overlap with GP2 + Zelle) | — | — | Looks like consumer-style payments; UTA's flow is corporate AR/AP, not P2P-style |
| Global Mass Pay | Streamline global payment operations by securely initiating and tracking high-volume cross-border payments | Out-of-scope (volume profile) | — | — | UTA's wire volume to Klutch doesn't fit "high-volume cross-border" use case |
| Request for Payment | Initiate payment requests, track real-time status, and receive automatic notifications upon completion to streamline receivables and reduce manual follow-up | Evaluate | Unknown | (TBD) | Could be a Receivables product for UTA's AR side — different from CNB. Worth investigating |
| Request to Pay via QR Code | Create, manage, and track digital payment requests, generating shareable payment links and QR codes | Out-of-scope (Brazil PIX use case) | — | — | Brazil-focused product |
Treasury Payments — FX
| Product | Purpose | UTA scope | OAS status | Spec § | Notes |
|---|---|---|---|---|---|
| FX Rate Sheet | Real-time foreign exchange rate sheets for a specific account, with optional filtering by business department | In-scope | Downloaded (v1.0.2) | §7.6.6 | Replaces CNB §5.6 Exchange Rate File |
| Request for Quote | Request executable or indicative FX quotes for currency conversion and then book or cancel trades | In-scope | Downloaded (v1.0.1) | §7.6.2 / §7.6.3 / §7.6.5 | The upstream RFQ flow that produces Rate ID + Contract ID for the wire body |
| Xpedite Remit FX Rate Sheet | Request and retrieve FX rate sheets for cross-currency remittance transactions | Out-of-scope | Downloaded (v1.0.1) | §7.6.7 (mentioned only) | Consumer remittance product, not corporate treasury |
Treasury Payments — Status & Tracking
| Product | Purpose | UTA scope | OAS status | Spec § | Notes |
|---|---|---|---|---|---|
| Payment Status Track and Trace | Query and retrieve real-time status and detailed tracking information for cross-border and domestic payments using various reference identifiers | Evaluate | Unknown | §8 (potentially) | May overlap with GP2 Callbacks (§6.6) or GET /payment/v2/payments/{paymentId}. If separate, could be a polling alternative |
| Payment Status Track-n-Trace with GPI | Real-time visibility with GPI tracking | Evaluate | Unknown | (TBD) | SWIFT GPI for wire tracking; relevant for §7.6 FX wires |
| Platform Availability | Real-time online/offline status of US Real-Time Payments participants and receive outage notifications | In-scope | Downloaded (v1.1.0) | §10 | THIS IS PACMan — the catalog name is "Platform Availability"; we've been calling it PACMan informally. Same product. OAS endpoints: GET /participants (with optional status=ONLINE|OFFLINE filter) and GET /participants/{id}. Production hosts: openbanking.jpmorgan.com/tsapi/v1 (OAuth) and apigateway.jpmorgan.com/tsapi/v1 (mTLS); CAT analogs openbankinguat, apigatewayqaf. GAP: OAS description mentions "subscribe to outage alerts" but no webhook/subscription endpoint is defined — outage notification is via polling only or via a separate (undocumented) webhook product. |
| Notifications | Subscribe to and receive real-time notifications for events like payments, disputes, refunds, account updates as webhooks and emails | Evaluate | Unknown | (TBD) | Generic notification subscription — may be a meta-product or a Commerce-tier product. Investigate if relevant for our webhook delivery |
Treasury Payments — Inbound
| Product | Purpose | UTA scope | OAS status | Spec § | Notes |
|---|---|---|---|---|---|
| Payment Receipts | Notify clients of incoming credit confirmations with a webhook solution that provides timely alerts about payments or returns | In-scope | Downloaded (v1.2.0) | §6.5 | RESOLVED 2026-05-11. OAS verified — webhook envelope creditConfirmation with structured + unstructured remittance, relatedParties.debtor/creditor with full postal addresses, relatedAgents, taxInformation.debtorTaxInformation (Mexico). OAS examples: Singapore IRCT and UK FPS Agency Banking (no US RTP example, but schema is rail-agnostic). Webhook path /webhook/credit-confirmation; receiver {YOUR-SERVER-DOMAIN}/creditConfirmation. |
Fraud Solutions
| Product | Purpose | UTA scope | OAS status | Spec § | Notes |
|---|---|---|---|---|---|
| Validation Services | Verify the identity of individuals, organizations, and bank accounts by submitting detailed entity or account information and receiving validation results from trusted data providers | In-scope | Downloaded (v2.2.3) | §7.1 | Pre-Flight gating; needed before §7.2-§7.5 outbound payments. OAS confirms two endpoints: POST /validations/entities (entity/individual/organization) and POST /validations/accounts. Production host apigateway.jpmorgan.com/tsapi/v2; CAT apigatewaycat.jpmorgan.com/tsapi/v2; mock api-mock.payments.jpmorgan.com/tsapi/v2. Required headers: x-client-id, x-program-id (assigned during onboarding). |
Checks
| Product | Purpose | UTA scope | OAS status | Spec § | Notes |
|---|---|---|---|---|---|
| Checks | Retrieve detailed check information and images using flexible search criteria | In-scope | Downloaded (v2.1.1) | §6.4 · §7.7 · §7.8 | Base URL confirmed by Jessica 2026-03-03 and reconfirmed by OAS: production api.payments.jpmorgan.com/payable/v2, mock api-mock.payments.jpmorgan.com/payable/v2. Endpoints: /checks/search, /checks/images/search, /checks/issuances, /checks/cancellations, /checks/stops, /checks/stops/revoke, /checks/prints, /checks/prints/{id}, /checks/health. OAS examples cover US & CA. |
Liquidity & Account Solutions
| Product | Purpose | UTA scope | OAS status | Spec § | Notes |
|---|---|---|---|---|---|
| Blockchain Deposit Account Balances | Retrieve current and historical balances for BDA accounts | Out-of-scope | — | — | BDA = Kinexys / blockchain accounts; not UTA's case |
| Sweep Amendment and Execution | Update key sweep parameters and execute sweep instructions on demand | Evaluate | Unknown | (TBD) | Could be relevant if UTA wants automated end-of-day sweeps between Klutch accounts |
| Sweeps Visibility | Consolidate balances from various accounts into one main account for control and visibility | Evaluate | Unknown | (TBD) | Companion to Sweep Amendment |
Commerce (consumer card processing — NOT UTA's use case)
| Product | Purpose | UTA scope | Notes |
|---|---|---|---|
| 3-D Secure | Consumer card authentication | Out-of-scope | UTA is not a merchant processing card payments |
| Account Updater | Card credential updater | Out-of-scope | Consumer cards |
| Checkout | Checkout sessions / payment links | Out-of-scope | E-commerce |
| Consumer Profile | Manage consumer profiles | Out-of-scope | E-commerce |
| Embedded Payments | Embedded payment account management | Out-of-scope | Platform product |
| Online Payments | Card-not-present transactions | Out-of-scope | Commerce |
| Tokenization | Card data tokenization | Out-of-scope | Commerce |
| Wallet Decryption | Decrypt digital-wallet payment data | Out-of-scope | Commerce |
| Boleto | Brazil consumer payment slips | Out-of-scope | Brazil-specific consumer |
Pay by Bank (consumer open banking)
| Product | Purpose | UTA scope | Notes |
|---|---|---|---|
| Pay by Bank | Open banking consumer payments | Out-of-scope | Consumer-tier OBP |
| Pay by Bank - US | Consumer account access consent for bank-based payments | Out-of-scope | Same — consumer-tier |
JPM Wallet / Prepaid Card
| Product | Purpose | UTA scope | Notes |
|---|---|---|---|
| J.P. Morgan Wallet™ | Virtual/physical prepaid Visa debit card accounts | Out-of-scope | Klutch is a corporate operating account, not a Wallet program |
| J.P. Morgan Prepaid Card | Prepaid Visa debit card accounts | Out-of-scope | Same |
| J.P. Morgan Concourse™ | Multi-currency transactions, counterparties, users, external accounts, invoices, payables | Evaluate (low priority) | Concourse may overlap with multiple capabilities; investigate only if other products fall short |
| Push to Card | Near real-time payments to Visa/Mastercard | Out-of-scope | Already in §7.10 |
Administrative / Meta
| Product | Purpose | UTA scope | Notes |
|---|---|---|---|
| User Status Management | Manage user access across applications | Out-of-scope (admin) | UTA's IT admin, not in the integration scope |
Total counts
| Bucket | Count | Status |
|---|---|---|
| In-scope and OAS downloaded | 9 products | Transaction Details (v3.1.8), Account Balances (v1.0.5), Global Payments 2 (v2.4.7), FX Rate Sheet (v1.0.2), Request for Quote (v1.0.1), Payment Receipts (v1.2.0), Validation Services (v2.2.3), Checks (v2.1.1), Platform Availability (v1.1.0) |
| In-scope and OAS NOT YET downloaded | 0 products | All in-scope OAS now in Playbook/ |
| Evaluate (potentially useful, need triage) | 8 products | Onboarded Accounts, Reporting, Payment Inquiry, Faster Payments US RTP, Request for Payment, Payment Status Track and Trace, Payment Status Track-n-Trace with GPI, Notifications, Sweep Amendment, Sweeps Visibility, J.P. Morgan Concourse |
| Out-of-scope (OAS downloaded for confirmation) | 2 products | Wire Payments 2 (v2.0.5 — FI-to-FI, §7.5), Xpedite Remit FX Rate Sheet (v1.0.1 — consumer remittance) |
| Out-of-scope | ~24 products | Commerce, consumer wallet, Pay by Bank, virtual accounts, etc. |
| Deprecated | 1 product | Global Payments v1 (per Jessica 2026-03-03) |
| Future-state | 1 product | Business Direct Connect (v6.2.16 — FDX migration target; OAS downloaded) |
High-priority next moves
In priority order based on this catalog:
Hunt for Payment Receipts OAS— ✅ Resolved 2026-05-11 (v1.2.0 downloaded, §6.5 rewritten with full schema)Investigate Wire Payments vs GP2 wires— ✅ Resolved 2026-05-11 (v2.0.5 downloaded; confirmed FI-to-FI, out-of-scope; GP2 §7.5 remains UTA's wire path)Hunt for Validation Services OAS— ✅ Resolved 2026-05-11 (v2.2.3 downloaded; two endpoints/validations/entities+/validations/accounts)Hunt for Checks API OAS— ✅ Resolved 2026-05-11 (v2.1.1 downloaded; full surface — inquiry, image, issuance, cancellation, stop, revoke, print, health)Hunt for Platform Availability / PACMan OAS— ✅ Resolved 2026-05-11 (v1.1.0 downloaded;GET /participantspolling; webhook surface absent)- Deep-scan §7.1 Validation Services with OAS v2.2.3 — entity vs account flows, screening flag, ACS scoring, x-program-id values
- Deep-scan §6.4 + §7.7 + §7.8 Checks with OAS v2.1.1 — Cancel verb/path (closes §12 #6), search criteria, escheatment fields, image retrieval shape
- Deep-scan §10 PACMan with OAS v1.1.0 —
partnerBankresponse schema, partner-bank ID conventions, polling cadence (closes §12 #21) - Triage Faster Payments - U.S. RTP — is this additional to GP2 RTP or just a doc surface?
- Triage Payment Status Track and Trace — is this a polling alternative to GP2 Callbacks?
- Triage Request for Payment — is this UTA's Receivables / AR API?
- Triage Onboarded Accounts — useful for verifying Klutch entitlement post-CAT
- Triage Reporting — may overlap with Transaction Details, but separate product card suggests distinct surface
Catalog discipline going forward
Update this catalog whenever:
- A new OAS is downloaded (update OAS status column)
- A spec section is rewritten to reference a new product (update Spec § column)
- A product is reclassified (e.g., moved from "Evaluate" to "In-scope" after deep-scan)
- JPM publishes a new product on the developer portal (re-screenshot All Products, diff vs this catalog, add new rows)
For BofA: the very first artifact to produce is the BofA equivalent of this file — a full catalog of every product BofA publishes on its developer portal. Without it, we'll miss products the same way we missed Wire Payments here.