JPMorgan Chase Cryptograms Request 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 Cryptograms Request. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.
This API exposes
1 operation
across 1 path,
and defines 40 schemas.
It is described by OpenAPI 3.2.0, at version 1.5.0.
Requests are made against 3 base URLs: https://api.merchant.jpmorgan.com/payments/v1/, https://api-test.merchant.jpmorgan.com/payments/v1/, https://api-mock.payments.jpmorgan.com/payments/v1.
1 operations1 paths40 schemas1 POST
Metadata
The identity and technical contract details declared by the specification.
JPMorgan Chase Cryptograms Request API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (BearerAuth).
By default, every request must be authenticated.
Paths & Operations 1
Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.
The contract defines 40 schemas that model the data the API accepts and returns. The most detailed are paymentInstrument (21 properties), device (11 properties), tokenCryptogramResponse (9 properties), tokenCryptogramPaymentInstrument (7 properties). Each schema is shown below with its type and property counts.
transactionAmount
integer
Specifies the monetary value of the transaction performed.
validationMessage
object
Object containing information about transaction validation.
3 properties2 required
expiry
object
A number in the form of Month/Year that is displayed on a card (Debit/Credit). Provided in format MM/YY.
2 properties2 required
adfsError
object
Object containing information about the active directory file system error.
3 properties3 required
messages
object
A list of errors and warnings.
4 properties2 required
tokenAuthenticationValue
string
Contains authentication value received from the payment networks for network token transactions.
tokenLifecycleMercant
object
Manage the lifecycle of a token on file
2 properties1 required
address
object
Address Object
6 properties
identifier
string
It is the resource identifier for a given merchant request, provided/generated by JPMC.
merchantDoingBusinessAs
string
Alternate name for the merchant if it exists (trading name).
tokenCryptogramType
string
Type of cryptogram to be requested from Token service.
tokenReferenceIdentifier
string
Identifier given to a token at the time of provisioning. Can be used as a reference to the token number.
cardExpiry
object
A number in the form of Month/Year. Provided in format MM/YY.
2 properties2 required
merchant
object
Contains information about the Merchant.
5 properties1 required
paymentInstrument
object
Payment Instrument
21 properties
tokenRequestorIdentifier
string
Identifier for the merchant given by payment networks or token provider.
device
object
Contains additional information related to the consumer device.
11 properties
trackTwo
string
Contains track 2 equivalent data for the token.
electronicCommerceIndicator
string
Codifies the authentication results of the cardholder's credit card and tokenization interaction. Also known as ECI.
tokenCryptogramResponse
object
Response to token cryptogram request.
9 properties
cardLast4Digits
string
Identifies the final 4 digits card number.
responseCode
string
Short explanation of the response code.
timestamp
string
Designates the date, hour, minute and second when response was provided for a request. Using ISO 8601 date-time format.
tokenCryptogramRequest
object
Request Cryptogram for a token, which can be used in token payment processing.
5 properties
tokenNumber
string
The token number is a SECURE surrogate value for the account number utilized in payment. A token is created at enrollment into programs or when consumer creden…
year
integer
The year of the expiration date
transactionCurrencyCode
string
Monetary unit that was associated with transaction using ISO 4217 format.
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…
tokenCryptogramPaymentInstrument
object
Manage the lifecycle of a token on file
7 properties
responseStatus
string
Request result status.
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…
responseMessage
string
Long explanation of the response message.
requestIdentifier
string
Merchant identifier for the request. The value must be unique.
ipAddress
string
IP address of the consumer's device used in token transactions. Supports both IPv4 and IPv6. When processing American Express - IP Address is required in IPv4…
accountholderName
string
Consumer name that includes the first, middle, and last name.
paymentAccountReference
string
Payment Account Reference (PAR) acts as a linkage mechanism for processing transactions when full PAN is unavailable. PAR is not intended to be a PAN replaceme…
paymentOrder
object
Information about the order related to the transaction.
4 properties
paymentAmounts
object
Information about the amount and currency related to a transaction.
2 properties
merchantName
string
Merchant legal name.
month
integer
The month of the expiration date
Specification
The full machine-readable OpenAPI contract behind this narrative.
Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.
Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.
MCP tools for apis
4 tools reach this content
search_api_evangelistSearch every content type across the network at once.
find_relatedThe shared-tag relevance graph — what else covers this.
get_tagEverything one tag labels, across all content types.
guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
A second provider on the same verified email joins the account you already have.
Your account
ⓘWhere this information came from
This is an independent, third-party profile of JPMorgan Chase Cryptograms Request 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.
