Verification Of Payee Responder Service
The IPF Verification of Payee (VoP) Responder Service represents an implementation of the Verification of Payee service for Responding PSPs required by SEPA Instant Payment Regulation. The Responder Service processes VoP requests received through a Routing and Verification Mechanism (RVM). Essentially, the Responder Service allows the payee name provided in a request to be compared to the name/s actually held for a specific account on the Account Management System (AMS). The output is a match result which is returned via an API response. IPF have their own VoP Requester service which can be used alongside this Responder Service, but they can also be used as two separate standalone services.
The IPF Verification of Payee (VoP) Responder currently supports FPAD as a Routing and Verification Mechanism (RVM).
Responder Flow
The below diagram depicts the flow of a VoP request through the VoP Responder to the RVM:
| 1 | A request from the RVM is received by the VoP Responder service with a Name and IBAN in the message |
| 2 | The request is mapped and forwarded to the Processing Entity Account Management system |
| 3 | The Account Management system sends the account details using the IBAN |
| 4 | The VoP Responder system uses the account details and Name from the request and determines if this is a Match/No Match/Close Match and forwards the response to the RVM |
Further Reading
See Concepts for a high level overview of Responder Service core components and error handling.
The Concepts section also looks at the Account Management Service, with information about Joint Accounts, Account Type and Name Type.
Lower level information can be found under Features as follows:
Link |
Content |
Deployment options with detail on Database logging, Configuration, Runtime and Start Up Errors |
|
How Name Matching works, with detail about Defaults and Configuration |
|
This feature provides protection against potential phishing attempts. Contains detail on how it works, Configuration, Metrics and Error Handling |
|
An archive message contains the data used to determine match results. This section includes Configuration and Data Sourcing details |
|
The Responder Service provides a number of Message Logs. Describes message content and provides detail on Configuration and Error Handling |
|
Explains how to propagate request messages Request ID into Application Log statements |
The Verification Of Payee Responder API provides an overview on the FPAD Response API and the Account Management API. Detail is provided on data requirements:
-
What FPAD will send and receive
-
What is sent to the Account Management system and what is returned