Troubleshooting
Problem
Consider an order having multiple payment methods - Gift card and credit card. The charge sequence is 1 for gift card and 2 for credit card. Gift card has reverse excess for authorizations and credit card has "Do not reverse authorizations". When there is a cancellation on the order, the charges are not opened against corresponding authorizations for gift card and credit card.
Symptom
For example, consider the following scenario :
1. Create an order with one line and quantity 3 .
2. Let the line total be $207 and unit price be $69.
3. Add the two payment types Gift Card and Credit Card to the order and authorize it for $185 and $22 respectively.
4. Schedule and release the order. Cancel quantity 1 (So order total is now 207-69=138),run the APIs requestCollection, executeCollection and requestCollection for the order.
A new entry for reversal of authorization -$69 for Gift Card is created and checked
Create and confirm the shipment then invoice it.
5. Run requestCollection on the order.
When charge requests for settlements are created, a charge request for $116 (with auth ID) is created against Gift card and an another charge request for amount $22 is created for Gift card without auth ID (blank auth ID).
The expectation is that the charge request for settlement is a charge request for $116 (with corresponding auth ID) should be created against Gift card and a charge request for amount $22 should be created for Credit card.
Cause
This is working as designed
Diagnosing The Problem
Based on the charge sequence system is designed to utilize the high priority payment method first (that is either authorize or charge till the max charge limit is exhausted).
In this case , the application will not charge the credit card until the gift card is utilized to its max charge limit .
Resolving The Problem
This can be resolved in two ways -
Reduce the max charge limit for the gift card once there is a price change in the order.
or
Reduce the max charge limit by the amount that is reversed/processed in the User Exit.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg22002068