Failed transactions and recharge attempts not showing as expected

Hey guys,

I got a prepaid Mastercard to test our Past Due email and reattempt functionality. There are a couple issues:

1) There is no record of a "declined" transaction in our payment gateway (Authorize.net). If foxycart is attempting to charge, why is there no record of it? (We have a reattempt schedule of 1, 2, 3, and 4 days after the failure)

2) The card has insufficient funds, but FC is reporting "There was an error processing your payment: Card Code is required. (Response Reason Code: 33)" but the error should be saying something about "insufficient funds", etc. Any idea why FC is incorrectly reporting?

image

Thanks!
Comments
  • fc_adamfc_adam FoxyCart Team
    @Epotratz,
    1) There is no record of a "declined" transaction in our payment gateway (Authorize.net). If foxycart is attempting to charge, why is there no record of it? (We have a reattempt schedule of 1, 2, 3, and 4 days after the failure)
    That'd be a question best put to Authorize.Net. Looking at the logs for your store - I do see the payment request being sent to Authorize.Net, and their response with the error.
    2) The card has insufficient funds, but FC is reporting "There was an error processing your payment: Card Code is required. (Response Reason Code: 33)" but the error should be saying something about "insufficient funds", etc. Any idea why FC is incorrectly reporting?
    That error is coming back from your gateway directly, rather than something we're generating the error message for ourselves. It's possible that Authorize.Net require prepaid cards always have the CVV2 present.
  • @fc_adam

    Hmm... well its alot harder to test the reattempt feature than I thought!

    It is strange that Authorize.net wouldn't have the CSC code since we entered that code during our first transaction. Do you guys not store the CSC code for recurring transactions?
  • fc_adamfc_adam FoxyCart Team
    edited February 2
    @Epotratz,

    It's not possible to store the CSC code, as it's not allowed under PCI DSS - so as a compliant provider we don't store the CSC anywhere. We just securely pass it through if provided from the checkout.

    That said though - this error is still a valid error you can use to trigger the dunning functionality. It's a hard error for the sub, and from looking at the logs it appears that it's being re-attempted at the schedule you have it set to. Based on your current settings after 5 days you should receive the reminder email.
Sign In or Register to comment.