Hold and Review authorizations, AVS, and ResStatus using XML and payment processing
If a Site is using AuthorizeNet as a payment gateway and they have the The Authnet Fraud Detection Suite enabled to Hold and Review, then the developer needs to know what can happen.
The basic response codes we get from a credit card attempted transaction from AuthNet are
1 = Approved
2 = Declined
3 = Error
4 = Held for Review
While Approved, Declined, and Error are handled logically, we have to be smart about what happens with a Hold and Review because the merchant will make a decision later, in AuthNet, and no one will know what that decision is at the time the booking is being saved.
Thus, the XML will respond to an authnet message 4 by saving the booking in 'unconfirmed' status and in the xml message ResStatus=Hold.
Also the text the XML returns will say 'Payment held for verification'. What the XML developer does with this knowledge is for their use alone, as the customer will need to cancel the booking if their decision, after Hold and Review, is to reject the booking.