5 easy steps for implementing PSD2 with

The fastest integration we have done from start to finish has been 2 days. However, understanding that every case is different, we typically work on the assumption of a 2 to 4 week delivery timescale.


Working out the details

The first step of an ASPSP is getting in touch. There is no need for a protracted sales or analysis process, We simply need to know some basics around how you work and what you do. Once we have this information, we can set you up in minutes.

The sort of things we will be asking:

Do you have an existing API available?

If you have an existing mechanism for tell.connect to access data via API, we can utilise this to map and populate TPP requests. If not, we can capture data from your payment processors, or develop a custom integration exclusively for you.

What you currently make available to Consumers?

Once we understand your current and roadmap product set and its features, we can advise on how and what needs to be made available via your PSD2 API gateway. This drives the API endpoints we expose on your implementation, as well as the specification that is automatically generated and published.



When all is agreed the clock starts

We will begin by creating and configuring both your sandbox and production PSD2 API solutions. This include your branded developer portal, TPP management zone and API suite.

This part of the process is remarkably quick and straight forward, typically less than a day. We will need you to provide us with images to be used and domain preference (don’t worry, all of this will be discussed during the consultation). Any special requirements you may have are put into place at this point.



Authenticating Customers & Authorising Consent

Based upon the initial consultation there are 2 main mechanisms for implementing the required Strong Customer Authentication (SCA) and consent authorisation.

You will have undoubtedly already created a comprehensive secure authentication process for your consumers. For this reason, our clients typically choose to handle this aspect of the service themselves. If you choose this option, you will need to provide new authentication screens in order for us to redirect the consumer to you. You simply authenticate the consumer and confirm that they are happy to authorise your TPP to access their data and confirm this with us.

Optinally, we can build these customisable and branded pages for you, or we can build, host, authenticate and authorise your customers for you (subject to your required APIs being available).



Giving your customers control

Your customers will need the ability to view, revoke and manage their consents as part of the PSD2 regulations. tell.connect provides ASPSP consent management APIs which deliver all the information required to make this happen. Simply add a user interface and you’re done.

Much like the authentication and authorisation, we can alternatively provide template pages or host and manage these for you. You decide what’s simpler.



We are ready to integrate and start relaying data.

Everything is now in place apart from relaying the data requested by TPPs from your API requests.

In most instances, you will have an existing mechanism to access data via API, in which case tell.connect will utilise this to map and populate TPP requests. All that is needed is for us to map your API calls to the tell PSD2 specification.

If you don’t have such an interface, or if there are valid reasons for not using it for this purpose, we will employ one of number of alternative approaches, such as;

• Integrating directly with your supplier / payment processors
• Direct data access
• Creation and storage of data repositories within our cloud store
• A custom integration to suit your requirements, capabilities and technology stack

This part tends to be much simpler than you might first think. Every integration is different, but based on our experience and skills in this area, we typically complete full integration in under a week.