Register on the J.P. Morgan Payments Developer Portal and complete the OAuth application setup to obtain client credentials; J.P. Morgan uses OAuth 2.0 client credentials flow for machine-to-machine API access in the production environment
Request access to the specific API products required — balance reporting and payment origination are separate product scopes; work with your J.P. Morgan relationship manager to enable production access as the developer portal sandbox may have different scope limitations
Retrieve current account balances by calling the account balance endpoint with the account identifier; the response includes ledger balance, available balance, and one-day float, with timestamps indicating the as-of time for the balance snapshot
Originate a domestic wire or ACH payment by constructing the payment request body with debtor account, creditor account details, amount, currency, payment method indicator, and your unique payment reference; submit the request and capture the J.P. Morgan transaction reference returned in the response
Poll the payment status endpoint using the returned transaction reference to track the payment through accepted, processing, and settled states; alternatively, configure webhook notifications if available for your product tier to receive push updates on status changes
Integrate the transaction history endpoint into your daily reconciliation workflow to retrieve all posted transactions for a given account and date range, mapping J.P. Morgan transaction codes to your internal ledger categories
Known gotchas
J.P. Morgan's Payments Developer Portal sandbox environment does not replicate all production API behaviors — payment submission that succeeds in sandbox may encounter additional validation rules or field requirements in production that are only documented in the production-specific integration guide
Balance snapshots from the balance reporting API reflect the position as of the last intraday update cycle, not true real-time position; intraday payments originated or received within the same cycle may not appear in the balance until the next cycle, creating a stale-balance risk for high-velocity payment orchestration
J.P. Morgan enforces account-level and instruction-level payment limits that are negotiated during onboarding; exceeding these limits results in payment rejection with a limit-breach error code that is distinct from insufficient funds and requires a limit increase request rather than a funding top-up
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp