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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
JPMorgan Chase

JPMorgan Chase Merchant Notification API

Operations related to merchant notifications.

Documentation Provider Profile APIs.io OpenAPI GitHub

JPMorgan Chase Merchant Notification 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 Merchant Notification. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 3 operations across 3 paths, and defines 48 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.

3 operations 3 paths 48 schemas 2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.9.2
Base URL
https://api.payments.jpmorgan.com/onboarding/v1
Authentication
HTTP Bearer
Contact
Checkout API Support
Resource Areas
1

Authentication & Security 1

JPMorgan Chase Merchant Notification API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). By default, every request must be authenticated.

Paths & Operations 3

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

Merchant Notification 3

Operations related to merchant notifications.

GET
/checkout/notifications
List all notifications for a given time period
10 params → 200400401403500503
POST
/checkout/notifications/ackdeprecated
Acknowledge notifications
2 params body → 200400401404408500
GET
/checkout/notifications/receivedeprecated
Receive notifications for customer transactions
5 params → 200400401403500503

Schemas 48

The contract defines 48 schemas that model the data the API accepts and returns. The most detailed are orderNotification (23 properties), threeDomainSecureTransaction (14 properties), paymentMethod (12 properties), tokenNotification (9 properties). Each schema is shown below with its type and property counts.

validationMessage
object
Information about errors occurred in transaction validation
3 properties
paymentMethod
object
Provides information about the payment method used.
12 properties
expiry
object
Provides information about the expiry information for payment instrument
2 properties
listMessagesResponse
object
Messages Responses
2 properties
profileNotification
object
Specifies shopper profile information.
9 properties
applePay
object
Use is for encrypted bundles for web or Internet acceptance of digital device wallets such as Apple Pay
7 properties
threeDomainSecureExemption
object
EEA/UK Supported SCA exemptions
2 properties
requestId
string
Value provided by the merchant to uniquely identify the checkout session. Alphanumerics only; max 22 chars. This will be used as the orderId/orderNumber in und…
googlePay
object
Use is for encrypted bundles for web or Internet acceptance of digital wallets such as Google Pay
7 properties
wechatpay
object
Wechatpay payment method is linked to consumer bank accounts and/or payment network cards.
1 property
messages
object
A list of errors and warnings
4 properties
electronicCheck
object
Object for ACH (Automated Clearing House) payment method which occurs whenever someone instructs the ACH network to “push” money from their account to someone…
3 properties
tokenAuthenticationValue
string
Contains authentication value received from Payment Networks for network token transactions
sepa
object
Object for SEPA (Single Euro Payments Area) payment method is a regulatory initiative to facilitate cross border cashless payments across euro-using countries.…
2 properties
receiveMessagesResponse
object
Receive Messages Response
2 properties
payByBank
object
Pay by Bank payment method information.
2 properties
address
object
Specifies an address.
7 properties
consent
object
Consent for consumer profile
4 properties
paymentMethodTypeCode
string
Codifies the method the Applicant has used to Pay the good faith deposit or other fee paid at application.
messageInfo
object
Message Info
2 properties 1 required
threeDomainSecureTransaction
object
Three Domain Secure Transaction Information
14 properties
orderNotification
object
Specifies order information.
23 properties
networkResponse
object
Provides response information from the payment network.
2 properties
last4CardNumber
string
Identifies the last four digits of the primary account number of a credit, debit or pre-paid card.
authentication
object
Indicates Strong Customer Authentication (SCA) requirements.
1 property
electronicCommerceIndicator
string
Describes the Electronic Commerce Indicator used in cardholder authentication on a network token
cardTypeName
string
Provides name of the payment network
responseCode
string
Short explanation of response Code
money
object
Represents a monetary amount with currency.
2 properties
tokenNotification
object
Specifies card token information.
9 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…
paze
object
Use is for encrypted bundles for web or Internet acceptance of digital device wallets PAZE
7 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…
checkoutReference
string
This attribute is deprecated. Please use merchantOrderNumber or requestId based on the use case.
ackMessagesResponse
object
Since ack can result in a combination of successful and unsuccessful result, client should always check if there is any ack failed messages.
1 property
responseMessage
string
Long explanation of response Message
cardTypeIndicators
object
Card type indicators.
7 properties
paymentAccountReference
string
A unique identifier associated with a specific cardholder primary account number (PAN) used to link a payment account represented by that PAN to affiliated pay…
card
object
Provides information about the card instrument
7 properties
accountHolder
object
Captures details of the account owner
1 property
consumerAcknowledgement
object
Consumer acknowledgement information
2 properties
ideal
object
Ideal is Netherland based payment method that allows customers to buy on the Internet using direct online transfers from their bank account.
2 properties
ackMessagesRequest
object
Ack Messages Request
1 property 1 required
mandate
object
Demand deposit mandate information
5 properties
messagesResponse
object
List of messages, if any
7 properties
merchantOrderNumber
string
A unique identifier assigned by the merchant or on behalf of the merchant for the intention to purchase goods and/or services. The merchant order provides the…
ackFailedMessage
object
ack failed messages information
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jp-morgan-chase-merchant-notification-api-openapi.yml Raw ↑

Other APIs JPMorgan Chase publishes across the network.

Notifications API
AE Profile APIs.io
Accounts API
AE Profile APIs.io
Recipients API
AE Profile APIs.io
Webhooks API
AE Profile APIs.io
Transactions API
AE Profile APIs.io
Documents API
AE Profile APIs.io
JPMorgan Chase Account Information API
AE Profile APIs.io
JPMorgan Chase Account Restrictions API
AE Profile APIs.io
JPMorgan Chase Account Services API
AE Profile APIs.io
JPMorgan Chase Account Statements API
AE Profile APIs.io
JPMorgan Chase Account Transactions API
AE Profile APIs.io
JPMorgan Chase Account Updates API
AE Profile APIs.io
#Merchant Notification
← Back to J APIs
API Details
ID
jp-morgan-chase:jp-morgan-chase-merchant-notification-api
Base URL
https://api.payments.jpmorgan.com/onboarding/v1
Docs
https://developer.payments.jpmorgan.com/api
Provider
JPMorgan Chase
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

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.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=jp-morgan-chase-merchant-notification-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/jp-morgan-chase-merchant-notification-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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 Merchant Notification 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.