Embedded Payments

Use Embedded Payments APIs to integrate account management and payout services into your existing platform. The API resources provided are designed as a series of logical components that make it easy for you to build an account and payment ecosystem. For more information, see the Embedded Payments guides.

Versioning

Embedded Payments API supports versioning using a prefix in the endpoint URL. This prefix has the following format: vXX, where XX is the version number.

For example:

https://api-mock.payments.jpmorgan.com/tsapi/v1/ef/clients

Which version to use

Always use the latest version of the Embedded Payments API. 

Note: The transactions resource is always a version ahead of the other endpoints in the Embedded Payments API.

Accounts v2 (Beta)

As of January 2026, we are pleased to release Accounts v2, a new and improved version of the Accounts API. Contact our team to start your integration process.

Access virtual transaction accounts and limited access payment accounts through a single integration with the Accounts v2 API. This new, consolidated API gives you access to multiple payment and real-time virtual sub-ledger capabilities across various money transmission flows through a single endpoint. You benefit from integration that is consistent, clear, and aligned with global standards. 

Key improvements

Accounts v2 introduces several key improvements over the current version: 

• Broader account access: Use virtual transaction accounts and limited access to payment accounts through a single integration.
• Consolidated API: Manage multiple payment types and real-time virtual sub-ledgering across various money transmission flows with one endpoint. 
• Simplified payloads: Reduce development effort and errors, making integration and daily operations smoother. 
• Scalable volumes: Increase transaction volumes without impacting service-level agreements (SLAs). 
• Seamless operations: Our platform handles complex interactions, so you can focus on growing your business. 

Coming soon

Transactions v3 API is planned for a future release, bringing feature and payload updates that complement Accounts v2 API.

Production endpoints

The Embedded Payments API has one production endpoint: https://apigateway.jpmorgan.com/tsapi/v1/ef

For example:

https://apigateway.jpmorgan.com/tsapi/v1/ef/clients

Error reason codes

The Embedded Payments API uses standard HTTP response codes, and provides additional detail through the error response payload. Further details are provided in the Error response codes section.