Contact us to schedule a demo or ask a question to learn how AdvantageCS can help you.

What action do you want Advantage to take in the case of a credit card decline? Do you want the action to be different, based on the number of attempts, the type of card, or the amount of the transaction?

You can control all of these scenarios through the use of a powerful Advantage feature, credit card response rules. The feature works similarly to direct debit responses. You filter the response code returned by your credit card vendor through a set of parameters that you determine, and then direct Advantage to take an action or set of actions---such as suspending a CIR subscription, retrying the card, or sending a customer service response.

Set up your response rules at ARPTBL/CCR.   You can vary such elements as the amount of the charge, the billing organization, whether the card is recurring use (i.e., auto-renewal or installment billing), and so on.

credit card response rules

You then use the ‘Actions’ tab to define what the system should do when these parameters are satisfied.  You can assign any number of actions to the same response rule---for example, you can bill-suspend a subscription, and simultaneously generate an email or letter to send to the customer.

Valid actions you can take with your credit card responses including the following:

  • Add the customer to a Telesales list
  • Suspend a subscription/BCL participation/AMB agreement/conference participation
  • Cancel a subscription/BCL participation/AMB agreement/conference participation (after ‘n’ days, or on the ‘nth’ day of the month)
  • Reset a subscription/AMB agreement/conference participation
  • Delay the next retry of the card ‘n’ number of days
  • Reset the subscription flag to ‘Y’ (i.e., remove from auto-renew)
  • Send the customer an email or letter response
  • Increment (or blank out) the expire date
  • Try a different credit card for the customer

You use a separate process, ARP372, to process credit card "events."  The process handles the main (parent) event for the transaction---accepting the transaction, creating a reversal, etc.--as well as the actions associated with the parent event.

Credit card event rules may be used regardless of how you are authorizing the purchase---online or batch.  In either case, the rules are applied when the vendor returns the response code for the transaction involved (combined authorization/settlement, or settlement only).



Filed under: Software