SEPA Request to Pay (SRTP) is a framework that lets a payee send a structured request for payment to a payer, who can then accept and pay it from their bank app. It is a powerful alternative to cards and direct debit for everything from e-commerce to recurring bills. But a request to pay raises an obvious question for the payer: is this request really from who it claims to be?
Two layers, two jobs
It helps to separate what each piece does:
- Request to Pay handles the conversation — who is asking, for how much, and by when.
- Verification of Payee handles the identity — does this account belong to the named party?
- The credit transfer that follows handles the money movement itself.
Why they belong together
A request to pay that the payer cannot trust is just a more convenient phishing vector. Pairing it with payee verification means the convenience comes with a confirmation step.
- 1 A payee issues a Request to Pay for an invoice or bill.
- 2 Before the payer settles, a VoP check confirms the destination account matches the requesting party.
- 3 The payer accepts with confidence, and the transfer is initiated.
Convenience needs a trust anchor
The faster and smoother account-to-account payments become, the more they need an identity check behind them. VoP is that anchor for Request to Pay.
RoxPay's Verification of Payee fits naturally alongside Request to Pay flows, confirming the payee so a streamlined request does not become an easy fraud channel.