Payment transaction types
The pilot’s transaction catalogue, per Annex 1 (src-call-annex-1-pilot-payment-services) and detailed in src-end-to-end-process-flows §3.
Full step-by-step detail for every flow below — flow IDs, actor sequences, the shared pre-settlement/settlement/post-settlement-waterfall backbone, wireframes, minimum UX requirements — is in transaction-management-flows.
Person-to-person (P2P)
- NFC (offline), payer-initiated — see offline-payments.
- Via alias, payer-initiated (online).
- Via DEAN, payer-initiated, same PSP (online).
Person-to-business (P2B) / e-commerce / m-commerce
- E-commerce payment with alias or DEAN.
- M-commerce payment via mobile app — including SEAR (seamless embedded authentication redirect) and app-to-app redirection flows — see authentication.
- Point-of-sale: NFC-based online payment via SoftPOS, same pilot PSP.
Refunds
- Refund for e-commerce payment (P2B → payer, and B2P for acquiring-side).
Balance & history
- Balance enquiry (online or offline balance).
- Transaction history (online only).
Sub-flows underpinning all of the above
Online integrity check, balance pre-check (payer/payee side), pre-settlement, pilot PSP processing, post-settlement holding limit check (“waterfall”), SoftPOS defunding of offline digital euro — full step tables in transaction-management-flows §3.6.
Related
offline-payments · funding-and-defunding · transaction-management-flows · dean · alias · authentication · spec-sepi · spec-queries