Hosted payments page

The hosted payment page (HPP) collects all payment information required from your users and guides them through the payment authorisation journey. We will add any new banks supported by TrueLayer to the HPP, so you don't need to make any updates.

HPP features

The HPP includes a variety of features:

• A bank selection screen
• A scheme selection screen for EUR payments, if the bank supports multiple payment schemes
• A consent screen
• Collecting any additional inputs needed from your user
• A QR code that allows desktop users to continue the payment on their mobile phone
• Functionality that enables users to authorise payments, such as:
  • Redirecting the user to their bank to authorise the payment
  • Using embedded payment authorisation for banks that need it
• A built-in payment result screen to advise of payment success, or to help users with failed payments.

A benefit of the HPP over a direct API integration is that if any new features are added, you can take advantage of them with minimal or no integration needed.

Supported countries

The hosted payment page is currently optimised for the UK, Ireland, France, Germany, Spain, the Netherlands, and Lithuania.

Beta testers can also use the HPP for banks in Austria, Belgium, Finland, Poland and Portugal.

The user interface can be displayed in English, Spanish, French, Italian, German, Dutch, Portuguese, Polish, Finnish and Lithuanian.

Supported browsers

We've built the hosted payment page to work best on:

• Chrome
• Edge
• Firefox
• Safari

HPP payment and mandate journey

When a customer makes a payment or creates a mandate through the hosted payment page, it follows this flow:

1. The user selects the Pay by bank option or equivalent in your app or website.
2. Your integration creates a payment with TrueLayer and gets a payment id and resource_token in response.
   If you include signup_plus in related_products at payment creation, the authorisation flow changes to reflect this.
3. Your system uses the ID and token to build the HPP URL and then displays it to your user.
4. Your user selects their bank on the screen.
   • If a bank is unavailable it's greyed out on the provider selection screen, so the user can attempt to use a different bank.
   • If your user is paying internationally from certain French or Finnish banks, a screen displays that explains how to enable international payments.
5. Your user enters any additional information that the bank requires, and confirms.
   If the user is making a EUR payment through a provider that supports multiple payment schemes, they select a scheme at this point.
6. If their bank supports app-to-app authentication, desktop users see a QR code. Scanning the code enables them to continue the payment using the banking app on their phone. They can also continue on desktop.
7. The HPP redirects your user to their bank's website or app.
8. Your user authorises the payment in their bank's website or app.
9. Once the authorisation is complete, the bank redirects the user to the HPP's payment result screen.
10. After the user acknowledges the result screen, they are redirected to the return URI that you set in Console.

This is an example of the user experience when a user authorises the payment using their mobile from step 6.