Real-time and Triggered Gateways
FatZebra Hosted Iframe (Real-Time)
Supports processing real time credit card or debit card transactions during Checkout and Invoice payment.
FatZebra Hosted Iframe Triggered without Authorisation
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.
Example Customer with option to 'Charge Card':
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.
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.
NOTE: If the same credit card or debit card is used during checkout, then the existing Customer record is updated as required.
Example Authorisation before 'Capture':
Example Authorisation after 'Capture':
After 'Capture' a Repeat Purchase can be used to charge additional funds to the credit card or debit card used for the original transaction, or a Refund can be used to refund the entire amount or a partial amount to the credit card or debit card, see example transaction below:
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.