EDS Local File

The EPC Directory Service (EDS) Local File is the representation of the EDS in a form of file in XML, JSON, and CSV format to be used locally by scheme participants and their technical providers (e.g. Routing and/or Verification Mechanisms (RVM) for the Verification Of Payee (VOP) scheme). 

Its content is generated daily in the EDS platform and contains:

• Participant identification data (participant BIC, account Holding BICs, PSD2 National Authorisation Numbers- NANs);
• Adherence data (schemes the participant adheres to and the readiness date, roles and options);
• API-endpoints related information (URI, environment, priority, version, effective dates and time).

The EDS Local File can be downloaded from the EDS via Web GUI access after user authentication or obtained from the EDS via an EDS API.  It can be parsed and imported in the IT system of the participants for an optimised access. 

EDS usage for VOP

The participants in the VOP Scheme, or their RVMs, are expected to perform the following validations using the file’s content as part of the VOP API flows as specified in the VOP API specifications (link):

• VOP requesting side:
  • Using the IBAN of the beneficiary, the VOP Requesting PSP shall look-up the Account Holding BIC of the beneficiary PSP using one of the commercially available IBAN/BIC directory services. Note: the EDS does not provide this service.
  • Using the Account Holding BIC of the beneficiary, the VOP Requesting PSP shall use the local copy of the EDS to look-up the API endpoint (URI) of the VOP Responding PSP.
• VOP responding side
  • The VOP Responding PSP shall verify that the combination of the Requesting PSP BIC (that is received in the API payload) and the PSD2 NAN  (that can be retrieved from the PSD2 QWAC certificate of the VOP Requesting PSP), corresponds to a valid entry in the EDS Local File. This means the VOP Requesting party is a valid VOP scheme participant.
     
• Specifications (Updated 24 July 2025)
• Examples