Interac allows for a pre-authorization on debit cards to place a temporary hold on funds before the final purchase amount is determined, for example, to allow a vending machine or kiosk to dispense multiple items within a single sale.

 A DebitAuth places a hold on the cardholder’s account for the funds specified. A DebitAddToBatch is then used to complete the sale; this is also called "capturing" the authorization.  The DebitAddToBatch places the completed authorization in the batch.

The POS Sequence Number must be incremented for the DebitAuth and for the DebitAddtoBatch.

The following rules apply:

• AccountType must be CHECKING or SAVINGS
• The amount on the DebitAddToBatch cannot exceed the DebitAuth amount
• Cashback is not allowed on debit pre-authorizations or completions
• DebitAuth cannot be voided once approved    
• If the cardholder cancels the DebitAuth, a DebitAddToBatch must be sent to Portico with an Amount of $0.00
  • NOTE: Portico also allows the POS to send a DebitReversal, as this message is formatted to the GSAP Host as a Capture for $0.00; the POS Sequence Number must be incremented and sent in the DebitReversal request
• In the event a DebitAuth request times out, a DebitReversal or Debit AddtoBatch for $0.00 should be sent
  • NOTE: When acting on a DebitAuth, both a DebitAddToBatch and a DebitReversal are formatted to the GSAP Host as a Debit Capture for $0.00
  • This notifies Interac to release the funds held by the authorization
• Once a Debit preauthorization has been completed with a DebitAddToBatch, the transaction cannot be reversed           
• If the cardholder cancels the DebitAuth after it has been completed by a DebitAddToBatch, a DebitReturn is required to return the funds to the cardholder
• TagData is required in DebitAuth and DebitAddtoBatch transaction requests
• DebitAddToBatch must be submitted within 2 hours after approval of the DebitAuth