Purpose: Use the Work with Credit Card Cancellations function to cancel orders whose credit cards have been declined by the authorization service.
In this chapter:
You can define different actions to take for each vendor response code you receive from an authorization service. For example, if the service declines an authorization because the card is over its credit limit, you could set up the system to put the order on hold for five days and reattempt authorization after that time. You have the option of setting up a vendor response so that the system will flag the order for cancellation, either when the credit card is first declined or after a given number of attempts.
Determining when to flag for cancellation: The system determines that an order should be flagged for cancellation based on the number of declines received from the authorization service. You can set up the maximum number of declines in two ways:
• vendor response code: Specify the maximum number of attempts for an individual vendor response code. For example, a vendor response code that indicates credit card fraud might trigger cancellation after one authorization attempt; a code that indicates insufficient credit limit might trigger order cancellation after four or more attempts. Some response codes might be set up to attempt authorization an unlimited number of times, and never trigger a cancellation.
• system control value: The system control value specifies the number of times to attempt reauthorization across all vendor responses. This value overrides the limits you set up for individual response codes; in other words, if you specify you will attempt authorization 15 times for a vendor response code, but the system control value is set to 10, the system will not exceed 10 attempts.
The counter for authorization attempts is reset when you receive an authorization.
Example: An order:
• fails authorization three times
• is authorized
• you make a partial shipment
• the order fails authorization again
This last decline counts as response number one.
What happens when an order is flagged for cancellation? The system creates a record in the Backorder Cancellation Pending file (BOCANP). These records are assigned a type of C, to distinguish them from orders flagged for cancellation due to a backorder. In addition, the system writes:
If an order is flagged for cancellation but is not on hold, it will still be submitted for authorization.
Once an order is flagged for cancellation, you cannot exclude it when you cancel credit cards. Deleting the cancel date on the order detail line will not prevent the order from being canceled by this function. The system cancels every order flagged with a C in the Backorder Cancellation Pending file, and there is no visibility into this file through a CWDirect menu option.
What happens when you cancel orders? You can use the Work with Credit Card Cancellations menu option to cancel all orders flagged for cancellation due to credit card decline, or you can select all orders within a given range of cancel dates. The system produces the and cancels each flagged order, using the cancel reason specified for the vendor response code that triggered the cancellation. If the order is cancelled because it exceeded the maximum number of declines defined in the System Control file, the system uses the cancel reason code for the most recent vendor response that has a cancel reason code assigned. If none of the responses in the order's authorization history is assigned a cancel reason code, the system uses the default cancel reason defined in the system control value.
At this time the system also writes an order line history message for all canceled items (available by entering 24 next to the item in order inquiry) specifying the quantity canceled and the cancel reason code.
Note: If the cancel reason code set up to reduce demand, the order status after cancellation will be X; otherwise, the order status after cancellation will be C.
Stored value card authorization reversal: If a stored value card payment with an open, unused authorization amount exists on the order, the system also generates a stored value card authorization reversal; see .
Periodic function: You can also set up credit card cancellations to run as part of your periodic processing, using function BOR0029. In this case, you would not be able to specify a range of dates; all flagged orders would be canceled.
For more information:
How to display this screen: Enter WCCC in the Fast path field at the top of any menu or by selecting Work with Credit Card Cancellations from a menu.
AAR0144 ENTER Cancel Credit Card Order Cancellation 7/17/97 15:13:00
EZK Mail Order
If no dates are entered, all orders flagged for cancellation will be cancelled
F3=Exit F9=Accept F12=Cancel
The earliest cancel date to include when selecting credit card orders for cancellation. You cannot enter a beginning date without also entering an ending date.
Numeric, 6 positions (MMDDYY format); optional.
The latest cancel date to include when selecting credit card orders for cancellation. You cannot enter an ending date without also entering a beginning date.
Numeric, 6 positions (MMDDYY format); optional.
1. Optionally, complete the beginning and ending dates.
2. Press Enter. The system validates your entries and highlights any field you need to correct. Correct any fields and press Enter again.
3. Press F9. If you have entered a range of dates, the system submits the job CC_CANCELS and displays a message such as:
Job 356966/ELISE_K/CC_CANCELS submitted to job queue QBATCH in library QGPL.
4. If you have not entered a range of dates, a pop-up window displays:
Confirm Cancellation of Orders
Are you sure you want to cancel ALL credit card orders
flagged for cancellation?
Press enter to cancel all orders