Notes on the Use of Authorization Reversal Transactions

This section provides additional information concerning the requirements of and exceptions to the use of Authorization Reversal transactions.

  • Worldpay supports Authorization Reversal transactions for the following methods of payment: PayPal, Mastercard, Visa, Discover, Diners Club, and JC and American Express, but American Express and PayPal only support reversals of the entire Authorized amount (no partial reversals).

  • All transactional data, including associated Authorizations, Captures, and Refunds, must use cnpAPI format.

  • Worldpay recommends that you send the Authorization Reversal transaction using the same submission method (Batch or Online) as used for the Capture transaction. This is to eliminate a possible race condition that may occur if you submit an Online Authorization Reversal prior to the processing of a Batch containing the associate Capture transaction.

  • For Batch transactions, send Authorization Reversal transactions in a session separate from the both the associated Authorization and the associated Capture transactions.

  • For Online transactions, when following an Authorization with an Auth Reversal, allow a minimum of one minute between the transactions.

  • For Visa and Mastercard transactions, Worldpay automatically performs a partial Authorization Reversal, if the Capture amount is less than the associated Authorization amount.

  • If you do not specify an amount (<amount> element) in the Authorization Reversal, Worldpay reverses the total amount of the associated Authorization.

  • Do not send an Authorization Reversal against an expired Authorization. This results in a 306 - Auth expired, so amount does not need to be reversed error. When an Authorization expires, the hold amount is automatically reversed.

  • Do not send an Authorization Reversal against an Authorization that does not exist in our system. For example, if you sends a reversal against an Authorization that failed or an Authorization that was declined, the Authorization Reversal returns a 360 - No transaction found with specified transaction Id error.

  • Do not send an Authorization Reversal against a payment type that does not support Authorization Reversals. This results in a 335 - This method of payment does not support reversals error.

  • Do not send an Authorization Reversal for a fully depleted Authorization. This results in a 111 - Authorization amount has already been depleted error.

  • Do not use an Authorization Reversal to reverse an Authorization on a (Closed Loop) Gift Card. Use a Gift Card Auth Reversal instead (see Gift Card Auth Reversal Transactions).