Recurring Payment Mandate (TS12)
The Recurring Payment Mandate extension enables an organisation to obtain consent for recurring or merchant-initiated payments using an e-mandate SCA Attestation presented from the customer's EUDI Wallet. The flow uses the urn:eudi:sca:emandate:1 transaction data type defined in the TS12 Electronic Payments SCA Implementation with Wallet specification.
How it works
- The organisation enables the Recurring Payment Mandate extension from the dashboard.
- An administrator configures the mandate details (creditor identity, purpose, validity window, recurrence).
- When a customer sets up a recurring payment, a presentation request with an
urn:eudi:sca:emandate:1transaction data payload is triggered using the configured presentation definition. - The customer reviews the mandate in their EUDI Wallet and presents an SCA Attestation to grant consent.
- The system verifies the presentation, stores the signed mandate and returns the PSD2 Authentication Code that anchors subsequent recurring charges.
Configuration
Mandate details
Configure the fields that describe the mandate shown to the customer:
| Field | Description |
|---|---|
| Creditor name | Name of the creditor / payee |
| Creditor identifier | SEPA Creditor Identifier or equivalent reference |
| Purpose | Short description of what the mandate covers |
| Start date | First date the mandate is valid |
| End date | Last date the mandate is valid (optional for open-ended) |
| Maximum amount | Upper bound per charge |
| Currency | ISO 4217 currency code |
| Frequency | daily, weekly, monthly, yearly, or on_demand |
Mandate type
| Type | Description |
|---|---|
| Recurring | Fixed-schedule charges (e.g. subscriptions) |
| Merchant-initiated | Charges triggered by the merchant within the agreed limits |
Integration
Once configured, the system automatically generates a Presentation Definition bound to the urn:eudi:sca:emandate:1 transaction data type. This presentation definition can be viewed from the extension configuration page and is used when initiating mandate requests via the API.
API endpoints:
- GET
/v3/config/extension/recurring-payment-mandate- Retrieve current configuration - PUT
/v3/config/extension/recurring-payment-mandate- Update mandate settings
Caution: Disabling the Recurring Payment Mandate extension deletes its configuration. Mandates already signed remain valid at the receiving ASPSP but cannot be renewed or replaced from this extension. This action is not reversible.