Incremental Authorization (75)

Incremental Authorization (Type 75) is used to secure additional authorization for an on-going, previously authorized transaction. Type 75 is limited to certain card types.

Transactions Types (01) and (75) are very similar and are treated as such by the Elavon Gateway applications. If Type 75 is submitted and the application determines that the card type, industry, and processor require an Authorization Only (Type 01) be used, it is automatically changed. Otherwise, the application will process the transactions as an incremental authorization.

Restaurant industry, for tipping:

  • Authorization Tolerance Value is set to 100%
  • Elavon software application disables checking for both Incremental Authorization and Authorization Reversals
  • These transactions are not generated automatically

The Auto Authorize Difference field on the Configuration, Card Types screen (Fusebox Boarding) also influences how an Incremental Authorization operates:

  • If the Auto Authorize Difference field is selected, when a Prior Auth (Type 07) is run and the final amount is greater than the total authorized amount by more than the Auth Tolerance percentage (except 100 %), the application automatically creates an Incremental Authorization
  • If the Auto Authorize Difference field is not selected, the user receives an error message: -16 Final Amt Too Large, if the amount is greater than the total authorized amount by more than the Auth Tolerance percentage (except 100 %)
  • If an Incremental Authorization (Type 75) is run without an Authorization Only (Type 01) to reference, it changes the Incremental Authorization to an Authorization Only

Incremental Authorizations (Type 75) and Authorization Reversals (Type 76) are both reflected in the transactions total amount authorized (Field 130). CPS field data is automatically maintained by the Elavon Gateway software and should never be passed by your POS application.

error_outline
note

The incremental authorization does not require the cardholder account number because the Elavon token or unique ID tracks the transaction from the original authorization.