Environments

The PSD2 APIs are available in two environments:

  • Sandbox: A mocked environment allowing TPPs easy access to APIs to test integration with business functionality of APIs. Sandbox follows same security model, enrollment and SCA-flows as seen in the production APIs. Hence, once tested in sandbox, it usually only requires a change of endpoints and certificates to migrate to production.
  • Production: Real production APIs working on live production data. Access to production APIs is strictly limited to authorized TPPs with proper license to operate as a AISP, PISP or CBPII under PSD2 in Denmark. A (one time automated) onboarding step is required for TPP to register certificates and validate license to operate as an AISP, PISP or CBPII

On top of the Sandbox And Production environments, BEC's PSD2 solution provides separate environments for all banks under the BEC umbrella. Hence, when integrating to the APIs, the TPP must both consider the environment (sandbox vs production) as well as which specific bank to integrate with.

As of August 30, all portals, sandbox- and production endpoints are provided per bank. See list in above link for a fulllist of banks and endpoints.

Since all banks reside under separate URLs, E.g. to use PSD2 solution from Vestjysk Bank use endpoints under https://psd2api19.prod.bec.dk/eidas/1.0/v1 while e.g. https://psd2api369.prod.bec.dk/eidas/1.0/v1 would use PSD2 solution from Spar Nord Bank A/S.

The sandbox and production environments are elaborated below.

 

Production environment

Production is a live environment working on real production data. Access to production APIs is strictly enforced and limited to authorized TPPs with proper license to operate as a AISP, PISP or CBPII under PSD2 in Denmark. An onboarding must have been completed as a prerequisite for consuming the PSD2 API's. The onboarding includes register of certificates and validate license to operate as an AISP, PISP or CBPII.

On top of TPP validation - e.g. validation that TPP is properly

Sandbox environment

Note: As of September 2019, the isolated, purely mocked sandbox environment has been replaced by a new environment with support for security solution, consents and SCA flows. The new sandbox still works on mocked data, but the infrastructure now much more resembles the production environment and it allows a TPP to test full E2E integration - including onboarding using EiDAS certificates - prior to moving to production. The old sandbox will be decommisioned. TPPs that have previoously signed