When a customer receives a payment request, they will experience it as a URL that they follow to view a page showing the amount requested and options to make the payment. Merchants can configure this page via settings in a request template on the web UI (applied to all payment requests using the template), or via settings applied in each individual payment request sent via API.
Example page:
Header
The payment page header supports two logos (both optional); the image on the left is the “merchant” logo, while the image on the right is a “co-brand” logo.
Logos must first be loaded to the Merchant’s logo library, and then referenced via API using the logo image’s unique ID.
Example:
Footer
The payment page footer allows a number of data fields to be presented, all are optional. Note that emails must be valid email addresses, URLs must be valid URLs, and phone numbers must be valid Australian phone numbers. Address, ABN and business name are not validated.
Example:
Custom fields
Merchants can add custom fields to the payment page to be displayed to Customers, and/or to request information from Customers as part of the payment process.
Example:
Redirections
Merchants can configure payment pages to present options to Customers to direct them to specific URLs after successful payments or if a pay-later application fails.
Example:
