The EPC is an international non-profit association (AISBL), located in Brussels, Belgium. Its members are Payment Service Providers (PSP) or national or European PSP associations. The EPC payment-related schemes developed by the EPC – SPAA, SRTP and VOP – mandate the use of APIs for the exchange of data and for payment transaction initiation. To learn more about this API, see EPC Directory Service (EDS) API Overview. In this section, you will find information on how to integrate, test and go live with EPC Directory Service (EDS) API.
Refer to the EPC Directory Service (EDS) VOP API Reference or EPC Directory Service (EDS) SRTP API Reference and the Technical Specification on the EPC website to help you integrate with the EPC Directory Service.
If you are interested in using the automated download service where you can download EDS files in various formats through an API call, refer to Technical Specification for onboarding and integration information.
We recommend that you test your integration with EPC Directory Service (EDS) APIs in the sandbox before going Live. The EPC Directory Service (EDS) API sandbox behaves the same as the live environment, and you can use it to fully test your application. Follow the steps below to start testing in the API sandbox.
Access to EDS API sandbox is exclusive to Verification of Payee (VOP) scheme participants who have completed the documental adherence process.
Access to EDS API sandbox is exclusive to SEPA Request-to-pay (SRTP) scheme participants who have completed the documental adherence process.
This service is exclusive to participants of the EPC Directory Service (EDS). Follow steps below once the "documental" adherence to the VOP scheme or the SRTP is completed.
To consume the EPC Directory Service (EDS) APIs, you need a registered swift.com account. Refer to Section 4 in the EPC Directory Service (EDS) Onboarding & Registration guidelines.
Log in to swift.com using the user account created in the previous step and submit the e-order to obtain the EPC Directory Service (EDS) contract.
After creating the EPC Directory Service (EDS) contract, follow these steps to create license ID and license secret pair used for authentication and authorisation to the API.
If you have tested the API in the sandbox, swap out the sandbox URL with live URL api.swift.com, and swap out sandbox credentials with live credentials you created in Step 3 and Step 4, then start using the EPC Directory Service (EDS) API in the live environment!
If you have any questions about your integration, refer to the following resources: