Issue

An authorization was declined and reversed later on. 

Resolution

This issue is rare but can happen when using collaborative authorization. In a typical collaborative authorization flow, the following processes occur:

1. The cardholder initiates a transaction and a pre-authorization event is sent to Highnote.
2. During pre-authorization, Highnote verifies available funds, ensures spend and velocity rules pass, and the cardholder's funds are put on hold. 
3. If everything passes, Highnote approves the pre-authorization and sends an authorization request to your collaborative authorization endpoint for approval.
4. Your collaborative authorization endpoint approves or declines the authorization event. 

If there is a communication error with your collaborative authorization endpoint and Highnote can't send the authorization request, Highnote has to reverse the pre-authorization. This results in two separate events, with a reversal: 

• Approved pre-authorization event
• Declined authorization event
• Reversal for the approved pre-authorization event, which releases the funds that were placed on hold