OpenEdge - Transaction Decline Minimizer
A customer's wine club purchase processed successfully, but the card on file is different than the card that was actually charged. Why does the order show the charge going through the "card on file" when the actual card on file is different than what is charged?
OpenEdge has a service called, Decline Minimizer that allows Credit Cards to be automatically updated. The process is that for expired/replaced credit cards, whenever a payment is attempted in OrderPort, we attempt to pull cc updates (e.g card number, expire date, etc).
If we get a response that the card details changed, then we update the COF in OrderPort. The issue is that this process does not work for orders placed from the wine club (it is a limitation in OrderPort).
So, transactions are still approved but the COF is not updated in OrderPort and such orders will still show the old CC no / exp date even though in OpenEdge the transaction will display the actual cc details. When this happens, clients can go to admin => Customers => Card on File and lookup address.
By doing this, the COF will be automatically updated, and updates will apply for orders going forward. (But not for the wine club order already placed). Alternatively, placing orders from the admin cart/pos/web store will automatically trigger the COF update too.
**AMEX** does not participate in the Decline Minimizer program and their cards will not update there, AMEX does not send updates out like Visa and Mastercard do. They have their own 'Trusted Merchant' program where they will simply not decline card on file transactions with expired cards if the updated card has been activated and the merchant themselves has some sort of trusted status with AMEX.