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

JPMorgan Chase Merchant API

Merchant entity information

JPMorgan Chase Merchant 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. 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 25 schemas. It is described by OpenAPI 3.2.0, at version 1.0.3.

Requests are made against 3 base URLs: https://api.payments.jpmorgan.com/commerce/configuration/v1, https://api-cat.payments.jpmorgan.com/commerce/configuration/v1, https://api-mock.payments.jpmorgan.com/commerce/configuration/v1.

1 operations 1 paths 25 schemas 1 GET

Metadata

The identity and technical contract details declared by the specification.

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

Authentication & Security 1

JPMorgan Chase Merchant 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 GET. Each is listed below with its method, path, parameters, and response codes.

Merchant 1

Merchant entity information

GET
/merchant-accounts/{merchantAccountId}
Retrieve merchant details
getMerchantAccount 1 param → 200400401403404503

Schemas 25

The contract defines 25 schemas that model the data the API accepts and returns. The most detailed are merchantResponse (17 properties), locationAddress (7 properties), payoutAccount (6 properties), Error (5 properties). Each schema is shown below with its type and property counts.

phoneNumber
string
A locator whose value identifies the formatted numeric address for routing voice or data communications via telephony, to reach a party. NOTE: Telephone number…
digitalSales
object
This is used for specifying an attribute used on a model for object that will contain one or more attributes
2 properties
merchantResponse
object
This is used for specifying an attribute used on a model for object that will contain one or more attributes
17 properties
ProcessingTemplate
string
The alternate label for a pre-defined format for a processing entity configuration.
ErrorContext
object
Error Context model
4 properties 1 required
businessProfile
object
This is used for specifying an attribute used on a model for object that will contain one or more attributes
3 properties
countryCode
string
The telephone dialing prefix for a member country in the International Telecommunication Union (ITU) that is defined by the ITU-T E.164 standard. The code is a…
merchantManualKeyedTransactionsPercentage
integer
Percentage of transactions which will be keyed into the terminal with the card not present (i.e. Mail or Phone Order). User can manually type in the credit car…
clientId
string
A unique internal identifier created by the Firm's small medium business (SMB) unit for referencing a merchant.
Error
object
Common Error Model matching the api-template schema
5 properties 1 required
deviceLanguageCode
string
Indicates the method of communication, either spoken or written, consisting of the use of words in a structured and conventional way. The master set of values…
accountAlias
string
The alias chosen by the customer to identify the account.
merchantMetadataList
array
This is used for specifying an attribute used on a model for collection object that will contain one or more attributes
accountName
string
The alias name given to a Merchant Account, labeled as D.B.A., that is different from the legal name.
LocationType
string
Location where the error occurred in the request
projectedSalesInfo
object
This is used for specifying an attribute used on a model for object that will contain one or more attributes
4 properties
website
string
Provides textual information about data for the protocol for specifying addresses on the Internet (Universal Resource Locator - URL) for the merchant's organiz…
enterprisePlatformIdentifier
string
A unique identifier representing the profile (configuration) for an external client or internal service of the Firm that facilitates how it interacts with the…
payoutAccount
object
This is used for specifying an attribute used on a model for object that will contain one or more attributes
6 properties
merchantMetadata
object
This is used for specifying an attribute used on a model for object that will contain one or more attributes
2 properties
pricingTemplate
string
The alternate label for a pre-defined format for a pricing configuration.
payoutTemplate
string
The label given to the Funds Transfer Instructions (FTI) provided on reports to the merchant.
contactInfo
object
This is used for specifying an attribute used on a model for object that will contain one or more attributes
2 properties
terminalSales
object
This is used for specifying an attribute used on a model for object that will contain one or more attributes
3 properties
locationAddress
object
This is used for specifying an attribute used on a model for object that will contain one or more attributes
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs JPMorgan Chase publishes across the network.

Notifications API
Accounts API
Recipients API
Webhooks API
Transactions 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
Where this information came from

This is an independent, third-party profile of JPMorgan Chase Merchant 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.