As an Account Servicing Payment Service Provider (ASPSP) Wirepayer is using Open Banking to provide access to Third Party Providers (TPPs) to account information and payment initiation services in accordance with the PSD2 Regulations.
Account Information Services & Payment Initiation APIs
Both the Account Information interface and the Payment Initiation interface are being provided using v3.1 of the Open Banking Read/Write Data API Specifications - click here for details.
A browser based Redirect method will be used for client authentication, both during the consent process and during any subsequent authentication. The user experience for the client authentication process will be exactly the same as for clients that are logging in to the dedicated interface, with the addition of Open Banking-mandated consent journey elements at the end. Following the completion of the authentication process, there will be the playback of the consent request for the client to verify, along with account selection.
All Third Party Providers must be registered by the relevant National Competent Authority (NCA) and enrolled on the Open Banking Directory. Open Banking Independent Entity (OBIE) will provide TPP’s with an SSA (a JSON Web Token (JWT) containing client metadata about TPP client software signed by the OpenBanking Directory). To register to use Wirepayer's APIs a TPP should email us at email@example.com and provide their SSA.
A sandbox environment is available for testing purposes prior to consuming our production APIs. To request access to our sandbox please email us at firstname.lastname@example.org
If you have any technical queries or require technical support in regard to Wirepayer’s Open Banking APIs please email us at email@example.com