Payer experience

Why is payer experience so important?

Payer experience (also known as customer experience or user experience) is the quality of the customer’s experience when using an open banking payment.

A poor payer experience can lead to your customer not choosing or abandoning the payment.

For customers to choose open banking payments over other available payment methods, your provider needs to take into account four key factors that affect your customers’ perception of an open banking payment:

  1. Convenience: will this take long?

  2. Clarity: what exactly do I need to do? Is it going to be difficult?

  3. Familiarity: have I done this before? Do I recognise it?

  4. Security: is this safe? Do I trust it?

Buyers guide chapter checklist
Understanding open banking payments adoption

They then need to navigate the open banking payment flow successfully. A completion of a started payment flow constitutes a conversion. Good UX practices can also increase the likelihood of a user completing the payment. Best practices for this include:

  • 💡 avoid ambiguity

  • 👀 be transparent

  • ☝️ use common patterns and shortcuts

  • ✏️ simplify complexities

buyers guide conversion
Best practices for increasing open banking payment conversion

It’s important to note that part of every open banking payment journey — the authorisation step — is dictated by the banks, rather than the provider you choose, and that standards set by governing bodies across Europe can lead to inconsistent user journeys.

buyers guide payment flow
Who controls each stage of an open banking payment flow?

But your provider should be able to advise you on how to build a high-performing payment journey, taking into account the nuances of different banks and different market standards across Europe, as well as the needs of your business. Your chosen provider should be able to help you with:

Tried-and-tested bank selection and consent screens

The two parts of the open banking payment flow that your provider will control are the bank selection and consent screens.

  • Bank selection screen: the user chooses from a list of available banks (at which point they are redirected to that bank to authorise the payment).

  • Consent screen: the user is informed of the information required of them to complete the payment process, and they give their consent.

Your provider should have tested and optimised screens for both of these parts of the payment flow, which meet regulatory requirements, and they should give you recommendations for your business and use case.

Ask your provider

How do you ensure bank selection screens and consent screens are compliant and optimised for conversion?

Expert advice on authentication flows across Europe

As we mentioned in Coverage, payment flows will differ across Europe, as banks apply different standards for UX during the authentication part of the flow. While your open banking payment provider can’t control these parts of the journey, they can advise you on what markets and banks have particular UX quirks, such as if a specific bank requires IBANs or specific error messages to be aware of. They should also advise on how to build your flows to account for these differences.

Your provider should also be in constant communication with banks and regulators, feeding back to them and lobbying for improvements.

Ask your provider

What is your relationship with the banks you’re connected to? How often do you feed back to them?

High performing end-to-end payment or deposit flows

The parts of the payment flow controlled by your provider, the parts controlled by the bank and the parts controlled by your business (eg payment selection screens and success screens), combine to make the end-to-end payment or deposit flow.

While distinct, they naturally all work together to drive a user to complete a payment. Your provider should be able to advise on how to build a full flow that works effectively, removing ambiguity and complexity that would increase the chance of a payer dropping out of the flow.

Ask your provider

What is a typical conversion rate for use cases like mine in [country]?

buyers guide example payment flow
Open banking payment flow example

Best practices for driving open banking adoption

Adding open banking payments to your payment page isn’t simply about what happens when a payer has chosen open banking. It’s equally important to ensure your customers understand what it is and what it offers them compared to other available payment methods.

A provider should be able to advise you on the language to use (ie what to call your payment method) and how to structure the hierarchy of your payment options to increase the share of checkout (the percentage of all a business’ payments transacted through open banking). This is particularly important if further open banking adoption drives down your costs and operational inefficiencies.

Ask your provider

How can I maximise adoption of my new payment method?

buyers guide improving clarity
8.0 How to drive open banking adoption by increasing clarity
How does TrueLayer compare?

TrueLayer offers both direct API integrations that allow for customised payment flows as well as hosted payment pages (HPPs) and mobile software developer kits (SDKs) with some customisable elements and developer libraries.

Plus, our new QR code authentication feature lets you authorise desktop payments faster by handing off the payment session to the customer's mobile banking app via a QR code.

Our Integration Support team will work with you during the sales and integration process to guide you through the best payment flow for your use case while taking into account available development time.

Through extensive testing, research and experience of previous integrations, our UX experts have built payment flows that are fully optimised for conversion, with continuous testing always ongoing to find further optimisations.

"Take up of TrueLayer has been very positive. We now see around 25% of eligible payments going through bank transfer via TrueLayer."


Sitong Wei,

Product Manager