How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Transactions API

Create, track, and manage payments, such as ACH, wire, and real-time transfers, while easily filtering and retrieving transaction details by type, status, account, or date. This lets you automate fund movement and gain real-time visibility into your payment activity, all through a secure and flexible interface.

Transactions API is one of 65 APIs that JPMorgan Chase publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transaction. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 4 operations across 3 paths, and defines 57 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 6 base URLs: https://api.payments.jpmorgan.com/embedded/v2, https://api-mock.payments.jpmorgan.com/embedded/v2, https://api-sandbox.payments.jpmorgan.com/embedded/v2, https://api-ms.payments.jpmorgan.com/api/v2, https://cat-api.merchant.jpmorgan.com/api/v2, https://api-mock.payments.jpmorgan.com/api/v2.

4 operations 3 paths 57 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.payments.jpmorgan.com/embedded/v2
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Transactions API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth).

Paths & Operations 4

Across 3 paths, the API surfaces 4 operations — 2 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Transactions 4

Initiate and track the movement of funds, including payments.

GET
/transactions
List transactions
listTransactionsV2 15 params → 200400401403404500503
POST
/transactions
Create transaction
createTransactionV2 1 param body → 201400401403404500503
GET
/transactions/{id}
Get transaction
getTransactionV2 2 params → 200400401403404500503
POST
/wallet-decryptions
Decrypt a Paze, Google Pay, or Apple Pay encrypted wallet bundle
2 params body → 200400401403404408500

Schemas 57

The contract defines 57 schemas that model the data the API accepts and returns. The most detailed are TransactionGetResponseBase (25 properties), TransactionRequestResponseBase (15 properties), PostTransactionRequestBase (13 properties), cryptogramDetail (12 properties). Each schema is shown below with its type and property counts.

TransactionGetResponse
object
2 properties
ApiErrorReasonV2
object
Schema representing detailed reasons for an API error, including code, location, and message.
4 properties 1 required
PostTransactionV2FxInformation
object
Foreign exchange information for cross-border transactions.
3 properties
TransactionGetResponseV2
object
6 required
TransactionsSearchResponseV2
RoutingCodeType
string
Type of routing code.
RecipientAddress
object
Address details for the recipient. Mandatory for payments using the RTP payment type.
9 properties 3 required
CountryCode
string
Two letter country code based on ISO 3166 standard
ListTransactionsSearchResponseV2
object
2 properties 2 required
AccountNumber
string
Demand Deposit Account number or International Account Number (IBAN).
RecipientContact
object
3 properties 2 required
RoutingNumber
string
Routing number corresponding to the routing code type
TransactionResponseV2
object
4 required
TransactionGetResponseBase
object
25 properties 5 required
TransactionStatus
string
The current status of the transaction as it is processed: PENDING - The transaction is still being processed. CANCELED - The transaction has been canceled. COM…
PaymentType
string
The type of transaction being initiated. Valid values are: | Value | Description | |-------|-------------| | RTP | Realtime Transactions | | ACH | ACH Transact…
RecipientType
string
RecipientAccount
object
Bank account details of the recipient.
5 properties 2 required
RequestTransactionTypeV2
string
The types of transaction that the client is allowed to search by.
FeeType
string
The type of the fee transaction. Use this to differentiate between the fee transactions that were charged and those that were reversed. CHARGE - the fee that w…
PaymentTypeResponse
string
The transaction type indicates the nature of the transaction. Valid values are: | Value | Description | |-------|-------------| | RTP | Realtime Transactions |…
TargetCurrency
string
The creditor account / recipient currency for a foreign exchange transaction
PageMetaData
object
3 properties
PartyType
string
RecipientIdentity
object
2 properties 2 required
PostTransactionRequestV2
object
2 required
RequestTransactionStatus
string
The statuses of the transaction that the client is allowed to search by.
TransactionGetResponseV2FxInformation
object
Foreign exchange information for cross-border transactions.
4 properties
ApiErrorV2
object
Schema representing a version 2 API error, including title, HTTP status, and additional context.
5 properties 1 required
CurrencyCode
string
Three letter currency code based on ISO 4217 standard
PostTransactionRequestBase
object
13 properties 3 required
TransactionRecipientDetailsV2
object
Payment recipient, either recipient or recipient id must be provided for Payouts
3 properties
TransactionRequestResponseBase
object
15 properties
OriginatingTransactionType
string
The transaction type of the originating transaction that incurred a 'FEE' or 'RETURN' transaction. This is only available for transactions of type 'FEE' or 'RE…
RoutingInformation
object
3 properties 3 required
AccountType
string
Type of bank account.
RecipientPartyDetails
object
8 properties 1 required
RoutingInformationTransactionType
string
Type of transaction.
multiTokenAuthenticationResponse
object
This is used for specifying an attribute used on a model for object that will contain one or more attributes
3 properties
validationMessage
object
Object containing information in the file
3 properties
expiry
object
Expiration for the account number
2 properties
messages
object
A list of errors and warnings
4 properties
cardArt
object
Card art information of a payment card.
3 properties
walletCardData
object
additional card information received from digital wallet provider.
3 properties
address
object
Address Information
7 properties
walletTransactionId
string
Value provided by the wallet provider.
cryptogramDetail
object
Cryptogram Detail Information
12 properties
responseCode
string
Short explanation of the response code
consumerInfo
object
Consumer Information
7 properties
code
string
Codifies a raised exception encountered by an internal or external system, sub-system, interface, job, module, system component with which the web service appl…
responseStatus
string
Status for the request. Valid Values: ERROR,SUCCESS, DENIED
message
string
Provides textual description of a problem that has occurred and is preventing the system from completing a task. Messages can be a confirmation, warning or not…
walletResponse
object
Wallet response object
6 properties
responseMessage
string
Long explanation of the response code
walletRequest
object
Wallet request object
9 properties 1 required
accountHolder
object
Card owner properties
10 properties
cardMetadata
object
Card Metadata information
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jp-morgan-chase-transactions-api-openapi.yml Raw ↑

Other APIs JPMorgan Chase publishes across the network.

Notifications API
Accounts API
Recipients API
Webhooks API
Documents API
JPMorgan Chase Account Information API
JPMorgan Chase Account Restrictions API
JPMorgan Chase Account Services API
JPMorgan Chase Account Statements API
JPMorgan Chase Account Transactions API
JPMorgan Chase Account Updates API
JPMorgan Chase Account Validation API
Where this information came from

This is an independent, third-party profile of Transactions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.