| European Payments Council

EPC FAQ: #27296 — Verification Of Payee scheme — Last updated: 17/07/2025

The Open API specification prescribes the mandatory "code" attribute in VerificationOfPayeeError with a fixed set of codes (FORMAT_ERROR, CLIENT_INVALID, CLIENT_INCONSISTENT, TIMESTAMP_INVALID).

Note that the provided list of error codes does not cover other situations:

Read more about The Open API specification prescribes the mandatory "code" attribute in VerificationOfPayeeError with a fixed set of codes (FORMAT_ERROR, CLIENT_INVALID, CLIENT_INCONSISTENT, TIMESTAMP_INVALID).

EPC FAQ: #27291 — Verification Of Payee scheme — Last updated: 17/07/2025

The OpenAPI specification defines the service URL as "/vop/v1/payee-verifications". Could the "Inter-PSP" VoP services be differentiated from internal (PSU->PSP) VoP services? For example, it would help to assume URL such as "/vop/fi2fi/v1/payee-verificat

The API “Verification of Payee” is only dedicated to the inter-PSP’s space.

EPC FAQ: #27286 — Verification Of Payee scheme — Last updated: 17/07/2025

Clarifications about the provision of VOP-services for bulk files

Background

Read more about Clarifications about the provision of VOP-services for bulk files

EPC FAQ: #27281 — Verification Of Payee scheme — Last updated: 17/07/2025

Is it mandatory for the scheme participants to support all the VOP request types (i.e., both combinations A and B) described in section 3.2 of the VOP scheme rulebook?

Supporting the combination, A is mandatory, but combination B is optional. The scheme participants do not have to support one (or several) identifier code(s) from the beginning; they can update the EDS whenever they are ready.

EPC FAQ: #27276 — Verification Of Payee scheme — Last updated: 28/08/2025

Bulk VOP requests

The VOP Rulebook states that the maximum execution time for the Requesting PSP to get the VOP Response is 5 seconds, and preferably 1 second or less.

Read more about Bulk VOP requests

EPC FAQ: #27271 — Verification Of Payee scheme — Last updated: 17/07/2025

How should the attribute AT-C007 (‘Possible additional information about AT-C001 sent by the Requester’) be used for sub-accounts / virtual accounts?

Legal background

Read more about How should the attribute AT-C007 (‘Possible additional information about AT-C001 sent by the Requester’) be used for sub-accounts / virtual accounts?

EPC FAQ: #27266 — Verification Of Payee scheme — Last updated: 24/07/2025

Will the EPC propose a standardisation of the bulk process?

In the second half of 2025 the Verification Of Payee Working Group will look into the possibility to give guidance about the bulk process.

EPC FAQ: #27261 — Verification Of Payee scheme — Last updated: 17/07/2025

In case a customer (Requester) wants to execute a payment by discarding the VOP result and the warning message (i.e., in case of no match/verification check not possible/no response) and it has resulted in financial loss, who will be liable?

For liability related questions, please refer to the Regulation (EU) 260/2012 as modified by the Regulation (EU) 886/2024 (Instant Payments Regulation - IPR), and to the Clarification of requirements of the

Read more about In case a customer (Requester) wants to execute a payment by discarding the VOP result and the warning message (i.e., in case of no match/verification check not possible/no response) and it has resulted in financial loss, who will be liable?

EPC FAQ: #27256 — Verification Of Payee scheme — Last updated: 17/07/2025

Should the reason code provided in the VOP Response be displayed back to customer (Requester)?

According to the IPR, the Requesting PSP must notify the Requester about the outcome of the VOP check. It is up to the Requesting PSP to decide how to comply with this requirement.

EPC FAQ: #27251 — Verification Of Payee scheme — Last updated: 17/07/2025

Is it planned to publish standards for ISO20022-messages for the customer-to-bank-sphere related to the VOP scheme?

At the moment, only inter-PSP API specifications were published, and it is not foreseen to publish ISO20022 messages for the customer-to-bank space.