Chase

Chase is the merchant acquiring and payment processing business of JP Morgan Chase — its developer portal and documentation use the name JP Morgan Chase. Data reaches Athia three ways: Athia polls the Global Payments and Reporting APIs for payment status and reports, receives pushes on the webhook you register in the JPMC portal, and picks up SFTP batch files where the integration is form-based. The provider-side prerequisites — API access on the JP Morgan Chase Payments Developer Portal, and any DFR form that has to go to your JPMC Relationship Manager — are arranged with your Athia team. Once you hold the credentials, you complete the connection yourself.

What you get

Payments — status and real-time payment information.
Transactions — transaction detail and balances.
Reports — sales, refunds, deposits and fees, pre-funded and post-funded.
Notifications — events and recommendations.

Custom reports are defined through API parameters, or through a DFR form where the report you need is not one the APIs return.

Before you start

You need access to the JP Morgan Chase Payments Developer Portal with permission to generate certificates, OAuth credentials or API keys.

In the portal:

Request or configure access to the Global Payments and Reporting APIs.
Enable the features you need — for example real-time payments and notifications.
Generate the credential Athia will use.

Choose a credential type

Either works:

OAuth — generate a client ID and secret, and set the scopes payments:read and reports:read. Both scopes are read-only: this credential cannot move money.
Certificate-based — download the .pem / .crt files from the portal and upload them to Athia.

Associate the credential with your entity type — Company or Business Unit.

The DFR form

Additional reports require a DFR (Delimited File Reporting) form. It asks for Business Name and Entity Number, and you email the completed form to your JPMC Relationship Manager. Contact your Athia account team if you want help with DFR forms or with initial setup.

Credentials Athia asks for

Field	Required	What it is / where to find it
Name	Yes	Your label for this connection — identify the Chase entity it covers
Schedule	Yes	How often Athia polls Chase — daily or hourly
OAuth Client Id	OAuth only	From the OAuth credential you generated in the JPMC portal
OAuth Client Secret	OAuth only	The matching secret for that client ID
Certificate upload	Certificate only	The `.pem` / `.crt` files downloaded from the portal — use these instead of the OAuth pair
Entity Number	Yes	Your JPMC entity identifier, the same number used on the DFR form

Setting up the connection

In the JPMC portal, confirm API access, enable the features you need, and generate either the OAuth pair with payments:read and reports:read or the certificate files.
In Athia, go to Settings → Connections → + Add Connection and select Chase.
On Configure Connector, enter a Name and pick a Schedule.
On Enter Credentials, enter the OAuth Client Id and OAuth Client Secret, or upload the .pem / .crt files, then enter your Entity Number.
Define the network and operation — select or create a group and add the operations this connection covers.
Choose Verify Connection. Athia runs a lightweight payment-status ping against the API.
Copy the Athia Webhook Destination URL from the wizard and register it in the JPMC portal — see below.

The connection then shows as ACTIVE and the first sync starts. For several entities, generate a separate certificate or use sub-IDs, and create one connection per entity.

Webhook

Register Athia as a notification destination so payment status changes arrive as they happen rather than at the next poll.

Copy the Athia Webhook Destination URL from the connection wizard.
In the JP Morgan Chase Payments Developer Portal, open the notifications / webhook configuration.
Paste the Athia URL and select the events you want — payment status changes, plus payment updates and recommendations if you use them.
Enable the webhook, then test the configuration from the portal.

Skip this and Athia sees only what the scheduled poll returns.

Sync cadence

Daily or hourly. Where your integration is form-based rather than API-based, the same data arrives as SFTP batch files instead of API polls.

Limits and things to know

Entity Number is required. Without it the connection cannot be scoped to the right JPMC entity.
One credential per entity. Separate certificates or sub-IDs, and a separate Athia connection for each.
DFR forms route through your Relationship Manager. Allow lead time before the reports they unlock appear.
Production and test environments are separate. Use production credentials on the connection you expect production data in.
Card data is minimized. Field-level detail on what Athia stores is in Athia Data Dictionary.

Troubleshooting

What you see	Likely cause	What to do
Verification fails on a certificate upload	Wrong file exported, or the certificate is not the one associated with this entity	Re-download the `.pem` / `.crt` from the JPMC portal and upload again
Verification fails on OAuth	Scopes missing from the client	Add `payments:read` and `reports:read` in the portal, then verify again
Payments arrive but reports are empty	Reporting API access not granted, or the report needs a DFR form	Request Reporting API access in the portal; for additional reports, email the DFR form to your Relationship Manager
Connection is `ACTIVE` but data belongs to another entity	Wrong Entity Number on the connection	Correct the Entity Number and verify again
Nothing arrives between polls	Webhook not registered or not enabled in the portal	Re-add the Athia Webhook Destination URL, select payment status change events, and enable it
No data at all after the first sync	Test-environment credentials on a production connection	Reissue credentials in the environment you process in, then reconnect

Athia Connectors — the full connector catalog
Athia Data Dictionary — field definitions
Integrating Athia — file drops, warehouse shares and the other integration paths