End User Payment Flow

Making a payment with PayTo

User is presented with the Pay by Bank landing page and is prompted to provide their PayID (their PayID can be in the form of a mobile phone number or email address)
Azupay performs pre-requisite checks to ensure the user is eligible to continue with the payment
If the user is eligible, a PayTo agreement is generated and the details are sent to the user's online banking platform
User reviews these details and approves the agreement in their mobile banking app or online banking
Payment is initiated and the transaction is completed
User is shown success screen (in iFrame) or redirected back to merchant success confirmation page (full frame version)

Making a payment with PayID

If user clicks on button 'Pay to our PayID', then they will be shown the PayID fallback option screen to make a payment to the merchant's generated PayID unique to the specific payment request
User clicks on copy button to copy PayID or scans QR code to transfer PayID details to a mobile device to make payment through mobile banking or online banking
Upon successful payment, user is shown success screen (in iFrame) or redirected back to merchant success confirmation page (full frame version)

Key Configurations / Variants

The payment experience can be configured to suit the needs of your use case. In the table below configurations may be set by URL parameters, values in the API calls or set in your specific client configuration.

Experience	Configuration	Comments
Duration allowed for payment	Payment agreement expiry time	Once a payment agreement has expired the payer is unable to approve the agreement in order for a payment to be taken from the account. Use a short expiry time if payment must be confirmed quickly, e.g. a travel booking must be paid before reserved tickets are released or repriced. If no Expiry Time is set the payment agreement can continue to receive payment initiations against the agreement indefinitely.
Maximum agreement amount	Client configuration	The default configurations of the PayTo agreement (created when using the Pay by Bank UX solution) is now defaulted to: - $200 maximum amount - Ad-hoc frequency - Variable agreement - End date set to T+2 years
Redirect	redirectURL	When the payer journey has completed (either following success or terminating at some unhappy path ending) the payer will be returned to this URL
Cancel	cancelRedirectURL	If a cancelRedirectURL is provided the payer sees a cancel button. Hitting the cancel button will send the payer to the specified URL and will deregister the PayID preventing anyone accidentally paying to this PayID

Example:
https://pay-stg.azupay.com.au/v3/checkout/QVpVUEFZRGVtb0NsaWVudC8xODBmNGE5ZGYwZGRmOTNiZTA0ZTQ0ODc5NTE3ZjczYi9BenVwYXkgRGVtbyBDbGllbnQvMUNsaWNrL2FIUjBjSE02THk5d1lYa3RjM1JuTG1GNmRYQmhlUzVqYjIwdVlYVXZZWE56WlhSekwyUTJaak5tTlRsaE9XTTVaamcxWkRZMk56SmhOMlEzTldZMVpEVm1Oekl6TG5CdVp3PT0=?token=fd511dd497a0e225bb0e45cca784838f9a38ee7d2426ee50abed7c3f4358b6960a2d24d0f&redirectURL=https%3A%2F%2Fwww.bing.com%3Fmyparam%3Dsomething&cancelRedirectURL=https%3A%2F%2Fwww.google.com

This URL is provided by the CheckoutURL response in the Payment Request API. In this example, a redirectURL has been added to take you to bing.com upon successful payment or to google.com upon cancellation by customer.

Exception Handling

The Pay by Bank UX solution includes exception handling so that merchants do not need to manage these complexities.

Should merchants want to simulate exception scenarios, they are detailed here for the UAT environment. There are particular PayIDs which trigger exception scenarios such as insufficient funds.