# JPMC-PDP Documentation from https://developer.payments.jpmorgan.com

# Changelog

This page includes updates introduced in J.P. Morgan Business Direct Connect.

### Version 6.5.1 | July 23, 2026

> Updated to FDX API v6.5; pagination on the payment-networks endpoint is deprecated while maintaining backward compatibility for v6.2 implementations.
> 

**New**

 
**New**

| Summary | Description | 
| --- | --- | 
| Added FDX headers | The API has been updated to comply with FDX API v6.5 by supporting the following request headers (as applicable per endpoint): FDX-API-Client-Public-Key, FDX-API-Data-Provider-Id, and FDX-API-Data-Recipient-Id. | 
| Added pageKey | Added pageKey for pagination object. | 

**New attributes by endpoint**

 
**New attributes by endpoint**

| Endpoint | Change type | Attribute name | 
| --- | --- | --- | 
| /accounts | Header | FDX-API-Client-Public-Key | 
| /accounts | Header | FDX-API-Data-Provider-Id | 
| /accounts | Header | FDX-API-Data-Recipient-Id | 
| /accounts | Pagination | pagekey | 
| /accounts/{accountId} | Header | FDX-API-Client-Public-Key | 
| /accounts/{accountId} | Header | FDX-API-Data-Provider-Id | 
| /accounts/{accountId} | Header | FDX-API-Data-Recipient-Id | 
| /accounts/{accountId}/transactions | Header | FDX-API-Client-Public-Key | 
| /accounts/{accountId}/transactions | Header | FDX-API-Data-Provider-Id | 
| /accounts/{accountId}/transactions | Header | FDX-API-Data-Recipient-Id | 
| /accounts/{accountId}/transactions | Pagination | pagekey | 
| /accounts/{accountId}/payment-networks | Header | FDX-API-Client-Public-Key | 
| /accounts/{accountId}/payment-networks | Header | FDX-API-Data-Provider-Id | 
| /accounts/{accountId}/payment-networks | Header | FDX-API-Data-Recipient-Id | 
| /accounts/{accountId}/statements | Header | FDX-API-Data-Provider-Id | 
| /accounts/{accountId}/statements | Header | FDX-API-Data-Recipient-Id | 
| /accounts/{accountId}/statements | Pagination | pagekey | 
| /accounts/{accountId}/statements/{statementId} | Header | FDX-API-Client-Public-Key | 
| /accounts/{accountId}/statements/{statementId} | Header | FDX-API-Data-Provider-Id | 
| /accounts/{accountId}/statements/{statementId} | Header | FDX-API-Data-Recipient-Id | 
| /accounts/{accountId}/contact | Header | FDX-API-Client-Public-Key | 
| /accounts/{accountId}/contact | Header | FDX-API-Data-Provider-Id | 
| /accounts/{accountId}/contact | Header | FDX-API-Data-Recipient-Id | 

**Deprecated**

 
**Deprecated**

| Summary | Description | 
| --- | --- | 
| Deprecated pagination on the payment-networks endpoint | Pagination for the payment-networks API is deprecated per FDX API v6.5, while preserving backward compatibility for v6.2 implementations. | 
| Deprecated offSet-based pagination on paginated endpoints | The offSet pagination parameter is deprecated on endpoints where v6.5 pageKey-based pagination is supported. | 

**Deprecated attributes by endpoint**

 
**Deprecated attributes by endpoint**

| Endpoint | Deprecated Item | Notes | 
| --- | --- | --- | 
| /accounts | offset | Deprecated in favor of pageKey | 
| /accounts/{accountId}/transactions | offset | Deprecated in favor of pageKey | 
| /accounts/{accountId}/statements | offset | Deprecated in favor of pageKey | 
| /accounts/{accountId}/payment-networks | pagination | Pagination deprecated for this endpoint. Pagination has backward compatability (v6.2). | 

### Version 6.2.19 | June 11, 2026

**Added**

The following features are included in this release. 

 
**6.2.19**

| Summary | Description | 
| --- | --- | 
| Correction to balances response | Known issue: Business Direct Connect may return a value of 0 for closingLedgerBalance, which is incorrect, since by default only current and opening balances are meaningful for current-day balances. | 
| Account open date | Accounts list and details calls now return the account open date. Known issues (to be fixed in a future release): - Business Direct Connect will return a date with a timestamp, which may fail field validation if you expect a date-only value. Starting with the July release, the product will send only the date. - In certain cases, you may notice a mismatch between this date and what is displayed in Online Banking. - Although this is implemented, the published spec does not document this field. The spec will be updated with the July release. The value is returned in the accountOpenDate attribute per FDX API 6.2. | 
| JWKS URI | Partner onboarding now supports JWKS URI-based authentication in addition to certificate-based authentication. If a JWKS URI is provided, a certificate is no longer required. | 
| App message optional | The application message is now optional in the application onboarding template. If provided, it will be displayed as a message from the application to the user within the consent flow. If omitted, no message is shown to the user. | 
| Partner and application templates version change to 4.0 | With the inclusion of jwksUri in the partner template, and by making appMessage optional in the application template, the template version is updated to 4.0 and must be specified as such after Jun 11. | 
| Payment network type | As of the April release, the Payment Networks call returns the payment network type. | 
| Support for USER actor type | As of the April release, Business Direct Connect also supports the USER actor type, which should be used when the call is made in the context of a user being present. | 

### Version 6.2.16 | April 15, 2026

**Added**

The following features are included in this release. 

 
**version 6.2.16**

| Summary | Description | 
| --- | --- | 
| Account information | Use the account information capability to retrieve details for accounts a user has consented to share through J.P. Morgan Business Direct Connect. | 
| Account transactions | Retrieve transactions from the consented accounts to aid use cases such as accounts reconciliation, and cash flow reporting. Transactions contain the Bank Administration Institute codes (BAI) codes to permit easy categorization. | 
| Account statements | Retrieve statements for accounts a user has consented to share, supporting use cases such as month-end account reconciliation. | 
| Full account number | Retrieve the full account number for a given account. Use it for verification or to set up money movement use cases. | 
| Account owner information | Retrieve account owner name and contact information such as address, email or phone for a given account to use for verification of account ownership. |