Empower your solutions with banking
Payment Services Directive (PSD 2) is a Directive of the European Parliament of 25 November 2015 on payment services within the internal market.
In accordance with the requirements of PSD 2, Papaya Ltd. offers the API (Application Programming Interface) Sandbox solution for Open Banking.
The Sandbox is a safe environment in which Third Party Providers can test ideas and innovations to build the next generation of digital services and products in the field of financial services.
The solution provided by Papaya Ltd. allows both Account Information Service Providers and Payment Initiation Service Providers to enter the market. It is suitable for both large companies and independent developers.
This API intends to provide an interface between:
- • Account Servicing Payment Service Providers (ASPSP)
- • Third Party (Payment Service) Providers (TPP)
TPP may act with different roles as described below:
- • Account Information Service Providers (AISP) (available in Production and SandBox)
- • Payment Initiation Service Providers (PISP) (available in Production and SandBox)
- • Payment Instrument Issuer Service Providers (PIISP) (available in Production and SandBox)
The Payment Service User (PSU) is the owner of the accounts held by the ASPSP and gives accreditations to the TPP in order to access his accounts information or initiates payment from these accounts
The API is designed on a REST model using JSON structures.
Before starting the registration process your organisation must meet several prerequisites in order to be successfully onboarded as a TPP for the Open Banking APIs.
• You must have a valid licence to use Open Banking API issued by NCA in any EU countries.
• You must obtain a valid PSD2 compliant client certificate to authenticate your application to the PSD2 APIs and play with production data.
Overall XS2A API statistic
We propose an API metrics that provide a view of the availability of our services in real time. This is imperative for compliance reasons based the Article 33 (RTS on CSA&CSC), and in order to achieve the required transparency regarding the uptime of the proposed API services.
XS2A API Services overall Uptime
XS2A Average response time
average per month
XS2A API Services overall Downtime
average per month