Filter
Top Products
Using Restaurant Transaction Processing
Restaurant transaction processing is handled in much the same way as normal processing.
The major difference is that there is a second step for some types of restaurant-based
transactions: establishing the actual gratuity amount. This second step ensures that the
correct gratuity amount is transferred from the customer's account to your account.
The different types of restaurant transactions are explained in detail below:
• A Sale (including an estimated gratuity amount) -- This transaction should be used
when the actual gratuity amount is not yet known but the total sale amount is known at
the time of transaction. PCCharge can automatically calculate the Estimated Gratuity
Amount: if the Authorization Expansion Factor is set in the processor's extended
data fields. This Estimated Gratuity Amount: can be overridden simply by typing
over the value displayed in the Estimated Gratuity Amount: field. This transaction
should be followed by a Gratuity transaction.
• A Sale (including a known gratuity amount) -- This transaction should be used when
both the actual gratuity amount and the total sale amount are known at the time of
transaction. PCCharge automatically calculates the Actual Gratuity Amount:. This
amount is based on the Authorization Expansion Factor set in the processor's
extended data fields. This Actual Gratuity Amount: can be overridden simply by
typing over the value displayed in the Estimated Gratuity Amount: field.
• A Pre-auth (including an estimated gratuity amount) -- This transaction should be
used when the actual gratuity amount is not yet known but the total pre-auth amount is
known at the time of transaction. PCCharge automatically calculates the Estimated
Gratuity Amount:. This amount is based on the Authorization Expansion Factor
set in the processor's extended data fields. This Estimated Gratuity Amount: can be
overridden simply by typing over the value displayed in the Estimated Gratuity
Amount: field. This transaction type differs from a Sale (including an estimated
gratuity amount) in that a Pre-Auth sets money aside in anticipation of a Post-Auth
(including a known gratuity amount). A Post-Auth can be for less than the original
Pre-Auth. A Pre-Auth must be followed by a Post-Auth in order for the funds to be
transferred from a customer's account to your account.
• A Post-auth (including a known gratuity amount) -- This transaction should be used
when the actual gratuity amount is known after the original corresponding Pre-Auth
transaction has been processed. PCCharge can automatically calculate the Actual
Gratuity Amount: if the Authorization Expansion Factor is set in the processor's
extended data fields. This Actual Gratuity Amount: can be overridden simply by
typing over the value displayed in the Actual Gratuity Amount: field. A Post-Auth
(and/or Actual Gratuity Amount:) can be for less than the original Pre-Auth (and/or
Estimated Gratuity Amount:). A Pre-Auth must be followed by a Post-Auth in order
for the funds to be transferred from a customer's account to your account.
• A Gratuity (after a Sale including an estimated gratuity amount) -- This transaction
should be used when the actual gratuity amount is known after the original
corresponding Sale (including an estimated gratuity amount) transaction has been
processed. A Gratuity can be less than or greater than the original Estimated
Gratuity Amount:. A Sale (including an estimated gratuity amount) must be followed
by a Gratuity in order for the amount of the gratuity to be transferred from a
customer's account to your account.
129