Banking · Service Initiation · Delegated SCA · UX

Delegated SCA — User Experience 4 min read

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.

01 Interactive Demo

Edit the consent and watch the previews respond

TPPConsent page
LFIAuthorisation page
LFI
Consent
2
Authorize
3
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.
Permission to make payments from this account will last until
Invalid Date
Please select the account to pay from
Authorize using AlTareq
Cancel

Customise the request body fields below and watch the Consent and Authorisation page previews update live.

domestic_payment_piiPAR request body (AEDomesticPaymentPII)
AEBankServiceInitiationRichAuthorizationRequests.AEDomesticPaymentPIIView PAR endpoint ↗
1 lines0 charsEdits commit on blur — invalid JSON reverts.
authorization_detailsPAR request body field
AEBankServiceInitiationRichAuthorizationRequestsV21.AEBankServiceInitiationAuthorizationDetailsPropertiesView PAR endpoint ↗
1 lines0 charsEdits commit on blur — invalid JSON reverts.

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 accounts Accounts the authenticated user holds at their bank
2 / 5
02 Field-Driven UI

How API request fields change what the user sees

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.CreditorLFI Authorisation Page Behaviour
1 creditorThe single payee's name and account details are displayed under "Who you're paying". (See Example 1)
2–10 defined creditorsAll 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.

PermissionsText shown to user on Consent Page
ReadAccountsBasicYou also grant us permission to access your account details before making the payment.
ReadAccountsDetailYou also grant us permission to access your account details before making the payment.
ReadRefundAccountYou also grant us permission to access your account details in order to process a refund.
ReadAccountsBasicReadAccountsDetailYou also grant us permission to access your account details before making the payment.
ReadAccountsBasicReadBalancesYou also grant us permission to access your account details and balance before making the payment.
ReadAccountsBasicReadRefundAccountYou also grant us permission to access your account details before making the payment, as well as to process refunds.
ReadAccountsDetailReadBalancesYou also grant us permission to access your account details and balance before making the payment.
ReadAccountsDetailReadRefundAccountYou also grant us permission to access your account details before making the payment, as well as to process refunds.
ReadAccountsBasicReadAccountsDetailReadBalancesYou also grant us permission to access your account details and balance before making the payment.
ReadAccountsBasicReadAccountsDetailReadRefundAccountYou also grant us permission to access your account details before making the payment, as well as to process refunds.
ReadAccountsBasicReadBalancesReadRefundAccountYou also grant us permission to access your account details and balance before making the payment, as well as to process refunds.
ReadAccountsDetailReadBalancesReadRefundAccountYou also grant us permission to access your account details and balance before making the payment, as well as to process refunds.
ReadAccountsBasicReadAccountsDetailReadBalancesReadRefundAccountYou also grant us permission to access your account details and balance before making the payment, as well as to process refunds.
03 Examples

Sample user journeys

Example 1 — Account Selected at TPP

delegated-sca
delegated-sca

Example 2 — Account Selected at LFI

delegated-sca
delegated-sca

Example 3 — Three Creditors

delegated-sca
delegated-sca

Example 4 — Undefined Creditors

delegated-sca
delegated-sca