The other side of the scheme

Answer VoP requests, not just send them

Under the Instant Payments Regulation every PSP must also respond to incoming Verification of Payee requests about its own account holders — accurately and within tight time limits.

Requesting vs responding

Verification of Payee has two roles. As a requesting PSP you check a payee before sending a payment. As a responding PSP you receive checks from other providers about your own customers and must answer whether the submitted name matches the account holder.

The regulation makes the responding role mandatory too. If your institution holds accounts, you need a responder that returns accurate results fast — or you risk both non-compliance and a poor experience for the people paying your customers.

What a responder must do

  1. 1

    Receive the request

    Expose a scheme-compliant endpoint reachable through the EPC Directory Service and routing mechanism.

  2. 2

    Match the name

    Compare the submitted name against the account holder using robust, tolerant matching that handles abbreviations, ordering and legal forms.

  3. 3

    Return the outcome

    Respond with match, close match (with the registered name where allowed) or no match — within the scheme's response-time limits.

  4. 4

    Log for audit

    Record requests and outcomes for dispute handling, reporting and regulatory evidence.

How RoxPay helps responders

Low-latency matching

A matching engine tuned to answer well within scheme time limits, at scale.

Tolerant name matching

Handles diacritics, name order, abbreviations and legal-entity suffixes to reduce false no-matches.

Compliant by design

Aligned to the EPC VoP rulebook and IPR obligations for responding PSPs.

Audit & reporting

Structured logs and metrics for disputes and supervisory reporting.

FAQ

Yes. The Instant Payments Regulation requires PSPs to both send and answer Verification of Payee requests for accounts they hold.

The EPC scheme sets strict response-time limits so the payer experiences a near-instant result. A responder must be engineered for low latency at scale.

Where the rules allow, a close match can return the registered name (or a hint) so the payer can confirm — balancing fraud prevention with data protection.

Stand up a compliant responder

We help PSPs answer Verification of Payee requests accurately and on time.