Strong customer authentication when an agent initiates the payment
PSD2 and the UK regulations require strong authentication with dynamic linking for remote payments, including through initiation services. Where an agent fits in that.
Strong customer authentication (SCA) is not optional because software started the payment.
The rule. PSD2 Article 97 requires a payment service provider to apply SCA when the payer initiates an electronic payment transaction, accesses the account online, or acts through a remote channel with fraud risk. For remote payments, SCA must include elements that dynamically link the transaction to a specific amount and a specific payee. These requirements also apply when payments are initiated through a payment initiation service provider. The UK's Payment Services Regulations 2017, regulation 100, sets out the same structure.
Dynamic linking in detail. The regulatory technical standards (RTS) require that the payer is made aware of the amount and the payee, that the authentication code is specific to that amount and payee, and that a code accepted by the provider corresponds to them.
What this means for agents. The agent cannot authenticate as the customer: the customer's credentials are personalised to them, and providers must protect their confidentiality. So the agent must route the customer to authenticate, for example in the bank's app or on a trusted surface showing the amount and payee, or use a permitted exemption.
Designs that fit: an agent prepares the payment; the bank shows the amount and payee and authenticates the customer; the agent receives the result. Protocols point the same way: AP2 renders mandates on a non-agent trusted surface, and Visa uses a passkey to authenticate payment instructions.
This is general information, not legal advice.
Sources: Directive (EU) 2015/2366, PSD2 (EUR-Lex, archived), Delegated Regulation (EU) 2018/389, RTS on strong customer authentication (EUR-Lex, archived), Payment Services Regulations 2017, regulation 100 (legislation.gov.uk)