JPMorgan Chase Checkout Intent 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 Checkout Intent. 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 38 schemas.
It is described by OpenAPI 3.2.0, at version 1.9.2.
Requests are made against 3 base URLs: https://merchant-api.checkout.merchant.jpmorgan.com/v1, https://merchant-api.checkout-cat.merchant.jpmorgan.com/v1, https://api-mock.payments.jpmorgan.com/v1.
1 operations1 paths38 schemas1 POST
Metadata
The identity and technical contract details declared by the specification.
JPMorgan Chase Checkout Intent 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.
Checkout Intent 1
Operations related to setting up and managing checkout sessions.
POST
/checkout/intent
Set up checkout intent
4 paramsbody→ 200400401404408500
Schemas 38
The contract defines 38 schemas that model the data the API accepts and returns. The most detailed are lineItem (17 properties), cart (13 properties), cardholderAccountHistory (12 properties), softMerchant (11 properties). Each schema is shown below with its type and property counts.
recurringPaymentDetails
object
Information required for recurring payments.
1 property
paymentMethodOptions
object
Defines payment method options.
2 properties
fraudCheckOptions
object
Fraud Check Options
2 properties
installmentPaymentDetails
object
Information required for installment payments.
1 property
cart
object
Consumer Shopping Cart
13 properties
validationMessage
object
Information about errors occurred in transaction validation
3 properties
capture
object
Capture Option
1 property
subMerchantSupplementalData
object
Additionsl data provided by merchant for reference purposes.
1 property
klarnaOptions
object
Codifies consumer choices and industry data provided by merchant to complete the payment with Klarna payment provider.
1 property
paymentCardAuthenticationRequest
object
paymentCardAuthenticationRequest models SCA request data which will be sent to 3DS provider if the Shopper is using a payment card as a payment method. This me…
7 properties
purchaseInfo
object
Purchase information.
4 properties
requestorPriorTransactionAuthenticationInfo
object
Information about how the 3DS Requestor authenticated the cardholder as part of a previous 3DS transaction.
4 properties
requestorAuthenticationInfo
object
Information about how the 3DS Requestor authenticated the Cardholder before or during the transaction.
4 properties
consumerProfileOptions
object
Shopper Profile Option
1 property
messages
object
A list of errors and warnings
4 properties
checkoutOptions
object
Defines checkout session options.
7 properties
address
object
Specifies an address.
7 properties
transactionalCharge
object
Additional charges applied by the merchant to the entire cart.
7 properties
cardOnFile
object
Card On File Option
3 properties
cardholderAccountHistory
object
Additional information about the Cardholder’s Account provided by the 3DS Requestor.
12 properties
merchantFraudRiskAssessment
object
Merchant's assessment of the level of fraud risk for the specific authentication for both the Cardholder and the authentication being conducted.
7 properties
lineItem
object
Specifies the detail about individual cart item.
17 properties
checkoutIntentResponse
object
Defines a response for the SetupCheckoutIntent endpoint.
2 properties1 required
merchantIdentification
object
Sub Merchannt Identification Information
3 properties
responseCode
string
Short explanation of response Code
authorization
object
Auth Options
5 properties
checkoutIntentRequest
object
Request for SetupCheckoutIntent
6 properties1 required
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…
tax
object
Tax Rate information
6 properties
shippingMethod
object
Shipping Method Information
4 properties
responseStatus
string
The label given to the state of a response to a request submitted by a consumer through the Firm's Application Program Interface (API) that matches a test case…
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…
discount
object
A monetary value to which the merchant applied a reduction (e.g., percentage or fixed amount) to a single line item of the purchase, the total purchase amount,…
8 properties
responseMessage
string
Long explanation of response Message
softMerchant
object
Soft merchant information is passed to the card association along with the transaction. This soft merchant information may also be used for cases where smaller…
11 properties
merchantProduct
object
Merchant Product Information
8 properties
paymentMethodType
string
Codifies the method of payment accepted for the checkout session.
consumer
object
Profile information of the consumer whom the transaction will be billed to
4 properties
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 Checkout Intent 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.
