10/18/2011

More Suspended Batches? Discover the Solution

Back in July, we discussed suspended batches and gave you the two most common reasons batches suspend: 1) missing or invalid data included in the batch or 2) a communication failure somewhere between you and your processor.
Today, we’d like to add a third reason that has become common enough that we feel it deserves your attention. That reason stems from Discover’s buyouts of Diner’s, Carte Blanche, and JCB. (A move many of you may be unaware of because Discovery has yet to rebrand the cards with their own name and logos.)

Basically, what happens is you accept a card number that references what was once a Diners, Carte Blanche, or JCB card. It’s a valid card and the card number is within Discover’s acceptable range, so the authorization comes back fine. However, upon settlement, when this card is to be sent to the processor, there is no indication as to which processor should handle it.

This is due to an oversight on the part of MSPs (your bank). To properly deal with this re-branded cards, MSPs need to bridge the old Diners/Carte Blanche/ JCB card ranges to their Discover setup.

If you’re seeing lots of suspended batches, and especially if there are Discover cards in the mix, take the time to call your MSP and make sure you are properly set up to handle all Discover cards (even the ones that used to be something else). If you don’t, you may end up having to void these transactions – which will cost you hard-earned revenue.

As always, if you need more information, feel free to contact us at support@shift4.com.