Payment Authorisation (For Merchants)

The Payment Authorisation (For Merchants) extension enables a merchant or a Payment Initiation Service Provider (PISP) to authorise a payment using an SCA Attestation presented from the customer's EUDI Wallet. This is the third-party-requested flow defined in the TS12 Electronic Payments SCA Implementation with Wallet specification.

How it works

1. The organisation enables the Payment Authorisation (For Merchants) extension from the dashboard.
2. An administrator configures the merchant/PISP identity shown in the authorisation request and the transaction fields bound to authentication (dynamic linking).
3. When a customer checks out at the merchant or via a PISP, a presentation request with an urn:eudi:sca:payment:1 transaction data payload is triggered using the configured presentation definition.
4. The customer reviews the payment details in their EUDI Wallet and presents the SCA Attestation previously issued by their ASPSP.
5. The system verifies the presentation, validates the Key Binding JWT and forwards the PSD2 Authentication Code to the ASPSP to complete the payment.

Configuration

Relying party identity

Configure how the merchant or PISP is identified to the customer during authorisation:

Field	Description
Legal name	Registered name of the merchant or PISP
Trade name	Optional trade name shown in the wallet UI
Relying party type	merchant or pisp

Payment authorisation request

Configure the transaction fields cryptographically bound to the authentication:

Field	Description
Payee account	IBAN or account identifier of the recipient
Amount	Transaction amount
Currency	ISO 4217 currency code
Execution date	Requested execution date
Remittance information	Optional reference shown to the payer

Accepted issuers

Select which ASPSPs (issuers) are trusted to issue the SCA Attestation for this flow. Only attestations signed by the selected issuers are accepted.

Integration

Once configured, the system automatically generates a Presentation Definition bound to the urn:eudi:sca:payment:1 transaction data type. This presentation definition can be viewed from the extension configuration page and is used when initiating payment authorisation requests via the API.

API endpoints:

• GET/v3/config/extension/payment-authorisation-merchant - Retrieve current configuration
• PUT/v3/config/extension/payment-authorisation-merchant - Update payment authorisation settings

Caution: Disabling the Payment Authorisation (For Merchants) extension deletes its configuration. This action is not reversible.