Depending on your use case for the Data or Payments API, you may wish not to show TrueLayer’s name or branding when users are connecting their bank accounts. This stage is called the consent flow, and you can redesign the consent flow, provided you meet certain requirements.
This is also known as whitelisting or skipping TrueLayer's consent page.
Where is TrueLayer branding shown?
- When giving consent and reviewing shared information with the Data API.
- When selecting banks. (Either requesting Account Data or initiating Payments)
Why do we show TrueLayer branding?
We are regulated by the FCA under PSD2 as an Account Information Services Provider (AISP) & Payments Initiation Services Provider (PISP).
Our consent flow needs to be clear that TrueLayer is seeking consent for access as TrueLayer is the Third Party Provider (TPP) providing the regulated service.
You can only remove TrueLayer branding if you are independently regulated by the FCA as an AISP or PISP, in which case we act only as a Technical Service Provider.
- You need to be regulated by the FCA under PSD2 as an Account Information Services Provider or Payment Initiation Service Provider, depending on your use case.
- You need to be on TrueLayer’s Developer Pricing Plan.
- You will need to design a replacement User Consent & Bank Selection dialogue which builds the appropriate Auth Link with the required provider_id.
- You will need to include a consent_id parameter in your Auth Link (e.g. add `&consent_id=1234567` where the consent_id is a randomly generated unique number, which is stored in your database, matched to the user)
How To Get Started:
Get in touch with our Sales team here or your dedicated CSM who will provide you with more details.