Supported Payment Methods

Supported Gateways

Payment Type	Category	Gateway Type	Payment type	MPGS 3DS	Fraud (Accertify)	Comments
Card	MPGS	Direct charge	Supported	Supported	Supported	1. Only 1 3DS type can be enabled at any one time. 2. If 3DS and Fraud are both enabled, the sequence is: Fraud first, 3DS second
Wallet	PayPal	Direct charge	N/A	N/A	N/A
Wallet	Apple Pay (via MPGS)	Direct charge	N/A	N/A	N/A
Wallet	Google Pay (via MPGS)	Direct charge	N/A	N/A	N/A
Checkouts	Afterpay (v1)	Direct charge	N/A	N/A	N/A	Will be migrated to Wallet flow Afterpay v2 in near future
Checkouts	Zip	Direct charge	N/A	N/A	N/A

Term	Definition
Intent	API call a merchant makes when rendering the Master Widget. The intent specifies what payment methods, payment flows and styling customisation are rendered to the customer. The intent call must also include customer specific information (collected during checkout or from their merchant profile) such as contact and address details.
Configuration template	The template that a merchant creates in the PowerBoard UI that specifies which payment methods and payment flows are presented to the end card holder.
Customisation template	The template that a merchant creates in the PowerBoard UI that specifies which styling is applied to the master widget and all child widgets rendered within the master widget.
Master widget	New PowerBoard widget that includes its own messaging components and also wraps all existing PowerBoard widgets as required (to surface the configured payment methods).