API - Direct Debits

Improved Direct Debit reconciliation with new webhook field

Effective March 2nd, 2026, we will be adding the collectionScheduleId(often known as the 'Q' ID) to the DD Collection Status webhook payload for Direct Debit Collections

Why are we changing this?

Currently, status update notifications (webhooks) only provide the Mandate Reference. Adding the collectionScheduleIdallows partners to quickly map records directly to their internal data, for example to update when a Direct Debit payment is successful or failed, without making resource-heavy API calls (like GET /mandates) to cross-reference data.

How it will work

From the release date, the JSON payload for DDCOLLECTIONSTATUS will automatically include the new field collectionScheduleId.

Action Required

Check your integration logic:

Strict Parsing: If your system validates the collection update webhook schema strictly (i.e., errors on unknown fields), you **must **update your schema to accept the new **collectionScheduleId **before March 2nd to prevent failures.

**Lenient Parsing: **If your system ignores unknown fields, no action is required to maintain current functionality.

To Use the Feature: update handlers to use the collectionScheduleIdfor easier direct debit collection reconciliation.

Consider if you want to improve your Direct Debit Collections reconciliation process using this new field. Also consider if your system parses webhooks leniently (ignores new fields) if you don’t want to change your current process.

API - Payment Initiation Services (PIS)

Santander Open Banking v4 migration

As PSPs update to the latest Open Banking standards (v4) there is an upcoming change to the Santander Open Banking API that may affect Payment Initiation Services (PIS) with long-lived consents for Santander.

Santander will decommission its existing v3 endpoints and any existing consents will be cancelled on 31 March 2026.

Santander will introduce three new distinct brands for their v4 endpoints: Santander Personal, Santander Business, and Santander Corporate. These will replace the v3 endpoint, and any PIS payments using the v3 endpoints will be deprecated and no longer be accessible after 31 March 2026.

🔄 What’s changing?

Santander is introducing three different brands and we have mapped them to new unique id in the responses in our APIs:

Santander Personal – H2100000G5

Santander Business – H2100000G6

Santander Corporate – H2100000G7

These new IDs are already available via Modulr’s /getaspspproviders endpoint and should be used for all new PIS payments going forward.

📅** Important dates**

✅ Now You can start using the new v4 endpoints and Santander ASPSP IDs immediately.

⏳ Until 31 March 2026 We will support parallel compatibility until the decommission date - both the existing Santander ID (H210000035) and the new brand-specific IDs will work.

🚫 After 31 March 2026

The existing Santander ASPSP ID will be fully decommissioned

All existing consents will be revoked

Any PIS payments using the old ID will fail

There is no backward compatibility after this 31 March 2026.

🛠 What you need to do

If you store the ASPSP id in your application, update your integration now to use the new Santander ASPSP IDs for all future PIS payments.
Ensure you select the correct Santander brand from the ASPSPs returned by the GET ASPSP endpoint
If you have any long-lived consents that cross the migration date - obtain a new consent from your payer against the correct Santander brand either ahead of time or post changeover.

We strongly recommend completing this update well ahead of the 31 March 2026 deadline to ensure uninterrupted PIS functionality.

If you have any questions or need support during the transition, please get in touch with us as usual.