TS12 SCA Workflows
Strong Customer Authentication (SCA) for payments is mandated under PSD2 Article 97 (1) for electronic payment initiation, as well as for accessing a payment account online or other actions that carry a risk of fraud. The EUDI Wallet supports all three authentication factor categories (knowledge, possession, inherence) to enable SCA, as well as Dynamic Linking.
This specification defines four SCA workflows using SUA Attestations (SCA Attestations) issued into the user's Wallet Unit by their Account Servicing Payment Service Provider (ASPSP).
SCA Attestation Types
| Attestation Type | Claims | Purpose |
|---|---|---|
| Payment Service User | Login and risk-based step-up authentication | |
| Payment Card | pan_last_four, scheme, scheme_logo | Payment Authorisation and Recurring Payment Mandate |
| Payment Account | iban, bic, currency | Payment Authorisation, Recurring Payment Mandate, and Account information access |
Transaction Types
| Transaction Type | Type Identifier | Attestation Used | Description |
|---|---|---|---|
| Risk-based Authentication | urn:eudi:sca:login_risk_transaction:1 | Payment Service User | Step-up SCA for sensitive actions (e.g. login from new device) |
| Payment Authorisation | urn:eudi:sca:payment:1 | Payment Account, Payment Card | Authorize a payment via PISP or directly |
| Recurring Payment Mandate | urn:eudi:sca:emandate:1 | Payment Account, Payment Card | Authorize recurring e-mandate for regular payments |
| Account Information Access | urn:eudi:sca:account_access:1 | Payment Account | Authorize AISP to access account data |
Each workflow follows the same 5-step developer pattern: obtain an API key, create a credential definition, issue a credential, create a presentation definition, and send a verification request with transaction data.