Restaurant

A typical restaurant transaction is processed using the CreditAuth transaction type to hold the initial amount. This transaction can be followed by a CreditAddToBatch transaction, which finalizes the total amount, may also adjust the transaction for the tip (if necessary), and adds the transaction to the current batch.

An alternative to using CreditAuth and CreditAddToBatch for tip handling is to use CreditTxnEdit to adjust the transaction, prior to using CreditAddToBatch to finalize the amount and add the transaction to the batch.

CreditAuth+CreditAddToBatch has the advantage of ensuring that no unadjusted transactions are inadvertently settled if the merchant is wanting to use auto-settlement.

NOTE: Merchants hosted on the Exchange Authorization host may use a CreditSale transaction followed by CreditTxnEdit , but this is not recommended. All new Restaurant integrations should use the CreditAuth transaction type.

Portico supports CreditIncrementalAuth for bars and restaurants. The original transaction must be an open CreditAuth that has not yet been added to the batch.

NOTE: For new integrations, Portico no longer supports the CreditAdditionalAuth service for the handling of bar tabs. This service has been deprecated. Please use CreditIncrementalAuth.

Remove this

Tip adjustments are not allowed on partial authorizations. If adjustments are made through the CreditTxnEdit or CreditAddToBatch on a CreditSale or CreditAuth that received a partial authorization, an error is returned.