Breaking Change Announced for PSD2 APIs - UPDATED

23 Mar 2026

Mandatory Endpoint Migration for Third Party Providers; Enhanced Security with JWS Signing

Update on 14 October 2026:

The current signing mechanisms of the PSD2 API will be updated. This change was initially scheduled for 1 September 2026.

The implementation would impact ING customers, to mitigate the impact we have to extended the deadline to 1 March 2027 and we will stop with creating new HTTP signed OAUTH2 refresh tokens as of 20 January 2027.

Introduction

ING is introducing new endpoints for the Account Information Services (AIS) API, Payment Initiation API (PIS), Confirmation on Availability of Funds (CAF) API and the Real-Time Reporting API affecting all PSD2 licensed Third Party Providers (TPPs) and all users of the Real-Time Reporting API.

The current endpoints will be decommissioned. Their decommissioning requires all users all users to migrate from the existing endpoints to new ones that offer advanced security features.

Why are we implementing this breaking change?

The new endpoints support JSON Web Signature (JWS) headers, delivering a higher standard of message integrity and aligning with Open Banking Europe’s specifications.

We have introduced new fields in the Payment Initiation Service that are compliant with changes to the SEPA Rules and NextGen messaging standards.

What do you need to do before 1 March 2027?

We hereby request you to migrate your connection to the new endpoints as per the steps below.

To maintain connectivity, we ask you to review the updated API References of the PSD2 APIs and Real-Time Reporting API and our Get Started Guide on implementing JWS:

  • Account Information Service
  • Payment Initiation Service
  • Confirmation on Availability of Funds Service
  • Real-Time Reporting API
  • Get Started JSON Web Signatures (JWS)

Steps to perform:

  1. Enable access to the new endpoints by using the PUT /oauth2/applications/{id} - to update the registered application's metadata to ensure that your application is correctly registered in ING's administration for operational purposes
  2. Implement changes related to JWS signing and the new endpoints that you consume.
  3. Creation and renewal of OAuth2 tokens must be performed using JWS signatures.
  4. Call the PSD2 APIs on the new endpoints with JWS signature and OAuth2 tokens created with JWS.

Take your time to familiarize yourself with the changes and reach out to us if you have any questions or concerns.

What do you need to do before 21 January 2027?

HTTP-signature-based creation and renewal of OAuth 2.0 tokens will be supported until and including 20 January 2027. From 21 January 2027, new tokens must be created using JWS.

Current endpoints will be deprecated

Both the current and new endpoints are working in parallel.

After 1 March 2027 the current PSD2 APIs and Real-Time Reporting API endpoints supporting HTTP signing will be decommissioned and the breaking change will be enforced.

In order to maintain connectivity, please take action as described above.

Is there any impact on existing consents that ING customers have granted for the Account Information Service (AIS), Check Availability of Funds (CAF) and Real-Time Reporting API?

Yes, existing OAuth 2.0 tokens effectively become unusable for the new JWS-enabled endpoints. Tokens issued under the HTTP-signing model cannot be used when calling endpoints that require JWS.

The customer consent itself remains valid. However, because the existing OAuth 2.0 tokens are not compatible with the new JWS-enabled endpoints, end users will need to perform a new Strong Customer Authentication (SCA). This allows new OAuth 2.0 tokens to be issued that can be used with the JWS-enabled endpoints.

The capability to create new OAUTH2 tokens with HTTP signatures will be discontinued as of 21 January 2027.

Details of Endpoint Changes

To ensure a smooth transition, below is a table listing the current (old) endpoints and their new replacements:

APIOld endpointsNewStatus
PIS APISingle Payment:
 POST /v1/payments/{payment-product}POST /v2/payments/{payment-product}Live
 GET /v1/payments/{payment-product}/{paymentId}GET /v2/payments/{payment-product}/{paymentId}Live
 DELETE /v1/payments/{payment-product}/{paymentId}DELETE /v2/payments/{payment-product}/{paymentId}Live
 GET /v1/payments/{payment-product}/{paymentId}/statusGET /v2/payments/{payment-product}/{paymentId}/statusLive
 POST /v1/payments/pain.001-{payment-product}POST /v3/payments/pain.001-{payment-product}Expected in Q4 2026
 GET /v1/payments/pain.001-{payment-product}/{paymentId}/statusGET /v3/payments/pain.001-{payment-product}/{paymentId}/statusExpected in Q4 2026
 GET /v2/payments/pain.001-{payment-product}/{paymentId}/statusGET /v3/payments/pain.001-{payment-product}/{paymentId}/statusExpected in Q4 2026
 
PIS APIPeriodic Payments:
 POST /v1/periodic-payments/{payment-product}POST /v2/periodic-payments/{payment-product}Live
 GET /v1/periodic-payments/{payment-product}/{paymentId}GET /v2/periodic-payments/{payment-product}/{paymentId}Live
 DELETE /v1/periodic-payments/{payment-product}/{paymentId}DELETE /v2/periodic-payments/{payment-product}/{paymentId}Live
 GET /v1/periodic-payments/{payment-product}/{paymentId}/statusGET /v2/periodic-payments/{payment-product}/{paymentId}/statusLive
 POST /v1/periodic-payments/pain.001-{payment-product}POST /v3/periodic-payments/pain.001-{payment-product}Expected in Q4 2026
 GET /v1/periodic-payments/pain.001-{payment-product}/{paymentId}GET /v3/periodic-payments/pain.001-{payment-product}/{paymentId}Expected in Q4 2026
 
PIS APIBulk Payments:
 POST /v1/bulk-payments/{payment-product}
POST /v2/bulk-payments/{payment-product}
POST /v3/bulk-payments/{payment-product}Live
 GET /v1/bulk-payments/{payment-product}/{paymentId}
GET /v2/bulk-payments/{payment-product}/{paymentId}
GET /v3/bulk-payments/{payment-product}/{paymentId}Live
 DELETE /v1/bulk-payments/{payment-product}/{paymentId}DELETE /v3/bulk-payments/{payment-product}/{paymentId}Live
 GET /v1/bulk-payments/{payment-product}/{paymentId}/statusGET /v3/bulk-payments/{payment-product}/{paymentId}/statusLive
  New: GET /v1/bulk-payments/{payment-product}/{paymentId}/extended-statusLive


APIOld endpointsNewStatus
AIS APIAccount Information Service:
 GET /v3/accountsGET /v4/accountsLive
 GET /v3/accounts/{account-id}/balancesGET /v4/accounts/{account-id}/balancesLive
 GET /v3/accounts/{account-id}/transactionsGET /v4/accounts/{account-id}/transactionsLive
 GET /v1/card-accounts/{account-id}/transactionsGET /v2/card-accounts/{account-id}/transactionsLive


APIOld endpointsNewStatus
CAF APIConfirmation Availability of Funds:
 POST /v2/funds-confirmationsPOST /v3/funds-confirmationsLive
 POST /v2/funds-confirmations/accountsPOST /v3/funds-confirmations/accountsLive


APIOld endpointsNewStatus
Real-Time Reporting APIReal-Time Reporting:
 GET /v1/openbanking/accountsGET /v2/openbanking/accountsLive
 GET /v1/openbanking/accounts/{account-id}/balancesGET /v2/openbanking/accounts/{account-id}/balancesLive
 GET /v1/openbanking/accounts/{account-id}/transactionsGET /v3/openbanking/accounts/{account-id}/transactions_standardLive
 GET /v1/openbanking/accounts/{account-id}/transactionsGET /v3/openbanking/accounts/{account-id}/transactions_extendedLive
 GET /v1/openbanking/card-accounts/{account-id}/transactionsGET /v2/openbanking/card-accounts/{account-id}/transactionsLive