If you are not regulated for payment initiation services under PSD2 in the UK or EU, then you must display some additional information in your payment journey. This document sets out what you need to include in your flow.
Before getting into the detail, here are some things to bear in mind.
- All mandatory information is clearly identified by the term must.
- The wording can be added in your choice of formats but must remain clear and visible to your customers.
- Your payment journeys require approval by TrueLayer before you can test in production and go live. Simply create a ticket to reach our Client Operations team, including a copy of your customer’s payment journey, ensuring it covers the end user’s consent as well as the payment confirmation.
- Your payment journeys must not be changed without TrueLayer’s prior approval. Again, create a ticket to contact us about any changes you make to your payment journey.
- We’d love to work with you to create the best experience for your customers, so don’t hesitate to ask us for assistance if you need it.
Example Payment Journey
We’ve provided here an example of a payment journey that meets the requirements whilst providing a great user experience. We’d recommend a similar approach for your payment journey, though it is possible to meet the requirements using alternative designs.
In this example, the Confirm payment screen fulfils the Payment Consent Requirements, while the Payment submitted screen meets the Payment Initiated Requirements.
Payment Consent Requirements
Before creating a payment with their bank, the end user must consent to TrueLayer initiating payment on their behalf.
- For a Redirect Authorisation Flow, these requirements must be met before the user is redirected to their bank’s app or website.
- For an Embedded Authorisation Flow, these requirements must be met before asking the user for any of the bank’s additional inputs.
|
1. Payee account name
The Payee to be credited must always be clearly stated.
Our suggested wording:
|
|
2. Amount and currency
The amount and currency of the payment must always be clearly stated.
|
|
3. Confirm button
You must only allow the user to proceed with the payment if they provide active confirmation that they want to pay the amount shown to the payee account name shown.
|
|
4. End-user terms of service and privacy policy
You must include the following wording on your payment user interface:
The Terms of Service and Privacy Policy page links change depending on the language and regulatory area. whether you're in the UK or the EU.
|
In our example payment journey above, these requirements are all satisfied by the Confirm payment screen.
Payment Initiated Requirements
|
1. Confirmation
At a minimum, you must confirm that the payment has been successfully initiated with the end user’s provider.
As the payment completes, you should further communicate that the payment has either succeeded or failed.
|
|
2. Amount and currency
The amount and currency of the payment must always be clearly stated.
|
|
3. Payment reference
A payment reference must be stated, enabling the payer to identify the payment transaction and, where appropriate, information relating to the payee.
|
In our example payment journey above, these requirements are all satisfied by the Payment submitted screen. However, for your payment journey, you may prefer to consider other approaches, such as:
- emailing or texting this information to the end user;
- providing a link to allow an end user to download a PDF of the information;
- having the information accessible for the end user to view on your app.
Note that whichever approach you take to meeting these requirements, we’ll need visibility of the payment journey before you test in production. Simply create a ticket to reach our Client Operations team, including a copy of your customer’s payment journey. This forms a part of our regulatory compliance approval process.