Bank and PayID
Bank one-off payments and PayID are supported on Hosted Checkout only. They are not available on Payment Links or the REST API, and are considered legacy flows — most real-time bank scenarios now use PayTo.
Bank Payments
Under Construction
This page is on a coffee break. It'll be back shortly.
PayID
Customers can make PayID payments from within their bank account application or online banking portal by using a unique PayID identifier. Customers then enter the PayID (which is an email address) and a PayID description to make a payment to the merchant. Unlike traditional bank transfers, there is instant verification of payment success, or notification of insufficient funds.
Zenith Payments supports three different types of PayID levels. More details about each of the different PayID types can be found below.
Summary of PayID Types
| Comparison | Program PayID | Customer PayID | Merchant PayID |
|---|---|---|---|
| PayID Type Example | Every merchant in the program has the same PayID email address. pay@travelpay.com.au | Every customer in the program has a unique PayID email address. john_12345678@travelpay.com.au | Every merchant in the program has a different PayID email address: @travelpay.com.au |
| Suitable For | Most merchants wanting to quickly implement PayID. | Ongoing payments when customers may be inclined to enter the wrong reference when they pay. | One-off transactions / invoice payments |
| Customer profile and CML required? (Customer-Merchant Link) | Yes | Yes | No |
| PayID Description the customer needs to enter | PayID description the customer needs to enter | The customer can enter whatever reference they like. | Reference provided by the merchant on the invoice, etc. |
| Customer Reference used in reports (reconciliation, etc.) | The customer reference stored in the customer's profile for that merchant. | The customer reference stored in the customer's profile for that merchant. | "Description/Message" field the customer enters in their bank app/site when paying |
| Additional Reference used in reports | "Description/Message" field the customer enters in their bank app/site when paying | "Description/Message" field the customer enters in their bank app/site when paying | "Reference" field the customer enters in their bank app/site when paying |
| Advantages | Easy to implement. | The merchant always receives the stored customer reference even if the customer enters the wrong reference when paying. | Easy to use and easy to implement; merchant adds their PayID to their invoice template. |
Tokenisation
You can tokenise a PayID and then use that token to create a customer via Program Level PayID and Customer Level PayID.
Merchant Level
Merchant Level PayID provides the merchant with a unique PayID email address that they can put on their invoices or send to customers so that their customers can use to make a payment to that merchant.
- One-off transactions
- Ad hoc Invoice payments
- Does not require a Zenith Payments customer profile (CML) to work.
- The PayID reference is generated upon creation and is provided by the merchant
- Customer enters in the correct reference as specified by the merchant to assist the merchant with reconciliation
How does a Merchant create a PayID Email Address?
For this type of integration, PayID is created by the Zenith Support staff for the requested merchant/s.
How does a customer make a PayID payment?
Coming soon...
Customer Level
Coming soon...
Program Level
Coming soon...