This document is intended to provide a non-technical audience with an understanding of the Canvas Portal and App – make a payment element in the end-user journey. Note: For illustrative purposes the Canvas app has been used to demonstrate the end-user functionality of the SDK.
About the Payment Journey
Payments made from a customer account require SCA (exemptions may apply). Payments made from a customer account, initiated in the portal, can have SCA performed via the Contis app.
Canvas Portal and App – make a payment workflow
Canvas Portal and App – make a payment end-user journey
Step 1 – Customer opens the Canvas Portal
Customer opens the Canvas portal.
Step 4 – Authenticate Login via the Canvas app
Now in the journey, the customer is presented with the Authorise login screen.
Step 5 – Login successfully completed
The login has been successful, and the customer is directed to the Transactions landing screen.
In the Transactions screen, select the Payments option.
Step 6 – Select bank payment type
In the Payments screen, select Bank payment to make an external transfer. For this guide, we will select UK Account as it is the most common use case.
The three available options are:
- Canvas Account
- UK Account
Step 7 – Bank payment screen
In the Bank payment screen, select Pay a person to add the new payee details.
Note: This process remains the same even if the customer has already saved the payee’s details.
Step 8 – Add payment details
Next, add the mandatory Payee details and Payment details.
- Payee name
- Account number
- Type of payments
- 3 Working Day Bank Transfer
- Same Day Faster Payment
- Next Day Faster Payment
- Recipient Email address
Step 9 – Confirm payment
Select Submit bank 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
Recipient Email address
Step 10 – 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 11 – SCA not required.
- Not trusted beneficiary – continue to Step 12 – SCA Required.
- Low value transaction – continue to Step 11 – SCA not required.
Transaction value above agreed threshold continue to Step 12 – SCA Required.
Step 11 – 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 17 – Payment has been sent.
Step 12 – SCA Required
If the payment meets one of the following conditions, SCA will be required and the SDK will be applied:
- Not a trusted beneficiary
- Transaction value above agreed threshold
Step 13 – Cancel/Authorise/Not recognised
Depending on the outcome of SCA, one of the following paths will be taken:
- Cancel (by the customer to return to edit the payment details) – return to Step 8 – Add payment details.
- Authorise / Recognised – continue to Step 17 – Payment has been sent.
- Not recognised – continue to Step 14 – Try again/Maximum attempts exceeded/Cancel
Step 14 – Try again/Fail/Cancel
There are three potential outcomes from this point:
- Try again – return to Step 12 – SCA factor required.
- Other authentication – The customer is presented with alternative SCA action to complete the transaction – continue to Step 16 – Payment has been sent.
- Fail – continue to Step 16 – Fail – Account Access blocked.
- Cancel – return to Step 8 – Add payment details.
Step 15 – Alternative SCA factor/Fail – Account Access blocked
Error screen – continue to Step 16 – Error screen displayed – Account Access blocked.
Step 16 – Error screen displayed – Account Access blocked
The Account blocked screen is displayed after a number of failed attempts and a message is displayed instructing the customer to contact customer services.
Step 17 – Payment has been sent
The Success pop-up will appear on the Canvas Portal with a Your payment request has been successful message.