Should we include the configuration id (and PSU-ID header) in the headers of the following requests: POST /consents and POST /payments/sepa-credit-transfer OR should we add it to the body of the re...

When initiating Account Information Service (AIS) or Payment Initiation Service (PIS) flows, the partner configuration ID must be included in the request using the X-Custom-Property-Partner-Id header.

This parameter is required only when initiating a consent or a payment, and does not need to be included in every subsequent request. The value must be provided in the request header, not in the request body. This ensures that the integration is correctly associated with the relevant partner configuration.

If the X-Custom-Property-Partner-Id header is not provided, the request cannot be processed and the following error will be returned:

{
  "code": "SERVICE_BLOCKED",
  "detail": "Redirect Flow is not supported",
  "type": "https://berlingroup.com/error-codes/SERVICE_BLOCKED",
  "title": "This service is not reachable.",
  "status": 403
}

Please note that the legacy Redirect SCA flow was fully decommissioned on 1 March 2026. Integrations must use the Enhanced (Decoupled) SCA Flow. Requests that implicitly rely on the deprecated redirect flow will no longer be supported.

For detailed implementation guidance, please refer to the Decoupled SCA guide and FAQ documentation.