1
Consent
2
Authorize
3
Complete
Delegated SCA - User Experience v2.1
Before a customer authorises a Delegated SCA payment consent through Open Finance, you must present a Consent Page that clearly explains that you are seeking permission to initiate payments on their behalf, but that the customer will be required to authenticate and approve each individual payment before it is executed — no payment will be taken automatically. This page must accurately reflect the payee and the nature of the delegated consent being granted. No payment amounts or schedule are shown at this stage as each payment will require separate customer authorisation. The examples and interactive wireframes below define the expected structure, content, and behaviour of the Consent Page and must be followed.
While you may adapt visual elements such as colour palette, fonts, and styling, you must not alter the meaning, clarity, or completeness of the payment information shown, and the representation of AlTareq (including logos, naming, and action buttons) must be preserved. The customer must always be able to clearly understand what payment they are consenting to and that it is part of the AlTareq ecosystem. Your Consent Page must be submitted as part of CX certification prior to production, and any material changes to a production Consent Page must be re-submitted for review and approval.
Interactive Demo
Customise the request body fields below and watch the Consent and Authorisation page previews update live.
Configure the mock accounts the authenticated user holds at their bank. The Authorisation Page will offer these accounts when the user picks a debtor account, or validate the Initiation.DebtorAccount against them when one is pre-selected by the TPP.
Simulated User AccountsAccounts the authenticated user holds at their bank
Live UI Preview
Changes made above are immediately reflected in both panels.
TPP · Consent Page
LFI · Authorisation Page
LFI
Consent
Authorize
Complete
Flexi-Pay Setup
[TPP trading name] needs your permission to make payments from your account.
Before each payment is made, [TPP trading name] will ask you to authenticate, inform you of the beneficiary, and confirm that you are happy to proceed with the payment.
Before each payment is made, [TPP trading name] will ask you to authenticate, inform you of the beneficiary, and confirm that you are happy to proceed with the payment.
Payment Details
Payment Reference
Payment Purpose
Unknown code
Permission to make payments from this account will last until
Invalid Date
Please select the account to pay from
Current Account
AE07 0331 2345 6789 0123 456
Balance
5000
Overdraft
1500
Savings
AE07 0331 2345 6789 0123 457
Balance
25000
UI Behaviour Driven by API Fields
Debtor Account Selection
The presence or absence of Initiation.DebtorAccount in domestic_payment_pii determines whether the user selects their account at the LFI or if it is pre-selected by the TPP.
TIP
Passing a DebtorAccount reduces friction for users who have already selected their account within the TPP's own interface, but removes the user's ability to choose a different account at the LFI.
Creditor Configuration
The presence or absence of creditors in Initiation.Creditor in domestic_payment_pii determines how the LFI presents payment recipient information to the user.
Initiation.Creditor | LFI Authorisation Page Behaviour |
|---|---|
| 1 creditor | The single payee's name and account details are displayed under "Who you're paying". (See Example 1) |
| 2–10 defined creditors | All specified payees are listed under "Who you're paying". (See Examples 2, 3 & 4) |
| Undefined (absent or empty) | A general message informs the user that the TPP is responsible for selecting beneficiaries at payment time. (See Example 5) |
Permissions and Data Access
The table below describes the text shown to users on the Consent Page.
| Permissions | Text shown to user on Consent Page |
|---|---|
ReadAccountsBasic | You also grant us permission to access your account details before making the payment. |
ReadAccountsDetail | You also grant us permission to access your account details before making the payment. |
ReadRefundAccount | You also grant us permission to access your account details in order to process a refund. |
ReadAccountsBasicReadAccountsDetail | You also grant us permission to access your account details before making the payment. |
ReadAccountsBasicReadBalances | You also grant us permission to access your account details and balance before making the payment. |
ReadAccountsBasicReadRefundAccount | You also grant us permission to access your account details before making the payment, as well as to process refunds. |
ReadAccountsDetailReadBalances | You also grant us permission to access your account details and balance before making the payment. |
ReadAccountsDetailReadRefundAccount | You also grant us permission to access your account details before making the payment, as well as to process refunds. |
ReadAccountsBasicReadAccountsDetailReadBalances | You also grant us permission to access your account details and balance before making the payment. |
ReadAccountsBasicReadAccountsDetailReadRefundAccount | You also grant us permission to access your account details before making the payment, as well as to process refunds. |
ReadAccountsBasicReadBalancesReadRefundAccount | You also grant us permission to access your account details and balance before making the payment, as well as to process refunds. |
ReadAccountsDetailReadBalancesReadRefundAccount | You also grant us permission to access your account details and balance before making the payment, as well as to process refunds. |
ReadAccountsBasicReadAccountsDetailReadBalancesReadRefundAccount | You also grant us permission to access your account details and balance before making the payment, as well as to process refunds. |
Example User Journeys
Example 1 - Account Selected at TPP
Click to expand
Example 2 - Account Selected at LFI
Click to expand
Example 3 - Three Creditors
Click to expand
Example 4 - Undefined Creditors
Click to expand