...
FatZebra Hosted Iframe Triggered without Authorisation
NOTE: Triggered transactions require:
The configuration of the Gateway Hash field, see example image below:
Credit card fingerprint matching turned off on the Gateway so that a new ‘Customer’ record is created for each order processed (request change with support@fatzebra.com.au).
Supports storing a new Customer and the respective card details during Checkout which requires a subsequent 'Charge Card' of the full value of the transaction via the Merchant Login.
...
If the same credit card or debit card is used during checkout, then a new Customer record is created for each transaction, and
Invoice payments are processed in Real-Time.
FatZebra Hosted Iframe Triggered (with Authorisation)
NOTECONFIGURATION NOTES: Triggered transactions require:
The configuration of the Gateway Hash field, see example image below:
Credit card fingerprint matching turned off on the Gateway so that a new ‘Customer’ record is created for each order processed (request change with support@fatzebra.com.au)..
FatZebra Hosted Iframe Triggered (with Authorisation)
Supports processing an authorisation for the full value of the transaction against the credit card or debit card transactions and storing a new Customer and the respective card details during Checkout which requires subsequent 'Capture' of the full value of the transaction via the Merchant Login.
...
A Customer is also created to group transactions by Credit Card, and enable re-Charge of stored Credit Card details, see example below:
...
NOTE:
If the same credit card or debit card is used during checkout, then a new Customer record is created for each transaction, and
Invoice payments are processed in Real-Time.
CONFIGURATION NOTES: Triggered transactions require:
The configuration of the Gateway Hash field, see example image below:
Credit card fingerprint matching turned off on the Gateway so that a new ‘Customer’ record is created for each order processed.