This document is intended to provide a non-technical audience with an understanding of the Make a Payment end-user journey.
Note: For illustrative purposes the Canvas app has been used to demonstrate the end user-functionality of the SDK.
About the Payments end-user journey
Payments made from a customer account require SCA (exemptions may apply).
The Payments end-user journey
Step 1 – SCA applied at login
The customer has already registered and performs a login using 2FA SCA.
Step 2 – Transactions screen
After successfully logging in, the customer is directed to the Transactions screen.
In the Transactions screen, select the Payments option.
Step 3 – Select bank payment type
In the Payments screen, select Bank payment to make an external transfer. For this guide, we will select Domestic Account as it is the most common use case.
The three available options are:
- Canvas Account
- Domestic Account
Step 4 – Bank payment screen
In the Bank payment screen, select the + icon to add the new payment details.
Note: This process remains the same even if the customer has already saved the payee’s details.
Before the next step, a Fraud Alert pop-up will appear. Click OK to access the next screen to add the payee and payment details.
Step 5 – Add payment details
Next, add the mandatory Payee details and Payment details.
- Payee name
- Account number
- Type of payments
- 3 Working Day BankTransfer
- Amount Same DayFaster Payment
Step 6 – Confirm payment
Select Confirm Payment. Available options before the payment is confirmed include:
- Type of payment – Same Day Faster Payment or Next Day Faster Payment
- Reference – an optional description of the transaction
- Send the recipient a receipt? – Optional addition of the recipient’s email address
Step 7 – Confirm payment (exemptions)
When Confirm Payment is selected, one of the four following exemptions determine the next steps of the journey.
- Trusted beneficiary – continue to Step 8 – SCA not required.
- Not trusted beneficiary – continue to Step 9 – SCA required (SDK).
- Low value transaction – continue to Step 8 – SCA not required.
- Low value transaction threshold – continue to Step 9 – SCA required (SDK).
Step 8 – SCA not required
If the payment meets one of the following conditions, the SCA will not be applied.
- Trusted beneficiary.
- Low value transaction.
Continue to Step 15 – Payment has been sent.
Step 9 – SCA required (SDK)
If the payment meets one of the following conditions, SCA will be required and the SDK will be applied:
- Not a trusted beneficiary
- Low value transaction – threshold exceeded
Step 10 – Cancel/Authorise/Not recognised
Depending on the outcome of the SCA, one of the following paths will be taken:
- Cancel (by the customer to return to edit the payment details) – return to Step 5 – Add
- Authorise/Recognised – continue to Step 15 – Payment has been sent.
- Not recognised – continue to Step 11 – Try again/Fail/Cancel.
Step 11 – Try again/Fail/Cancel
There are three potential outcomes from this point:
- Try again – return to Step 9 – SCA factor required.
- Fail – continue to Step 12 – Alternative SCA factor/Fail – Account blocked.
- Cancel – return to Step 5 – Add payment details.
Step 12 – Alternative SCA factor/Fail – Account blocked
There are two potential outcomes from this point:
- Alternative SCA factor – continue to Step 14 – Alternative SCA factor.
- Error screen – continue to Step 13 – Error screen displayed – Account blocked.
Step 13 – Error screen displayed – Account blocked
An Error screen is displayed after a maximum number of failed attempts is exceeded and a message is displayed instructing the customer to contact customer services.
Step 14 – Alternative SCA factor
The customer can choose an alternative SCA action to complete transaction – continue to Step 15 – Payment has been sent.