Our company builds website for credit card transactions. Our clients are large organizations that allow their member to pay their monthly dues online. We build Tests Cases for all possible Transactions that can occur. Moreover, our test cases include not only successful payments, but failures/declines. Hence, it would be extremely helpful if Authorize.Net could provide the ability to test payment methods that decline and/or fail for any and all reasons (i.e. expired cards, Address Zipcode mismatch, etc.).
We provide our clients with Training, User Manuals with screen shots and instructions. However, at this time, we are unable to test or train our clients for transaction failures/declines. To demonstrate how our software operates when a payment is declined we have no other choice but to run the transaction in the production system on our clients sites using real credit cards. This puts our own Credit Cards in jeopardy and has caused some to be placed on hold. This is less than an ideal situation. It would be great if Authorize.Net could allow us to do real live testing that would cause a credit transaction to decline in our testing environment.
We called Authorize.Net regarding this, but we thought we'd post this in case someone has some ideas that would help us and/or how you are testing declined transactions. thank you
01-11-2020 07:54 AM
Authorize.Net has a testing guide (which includes triggering declines) here:
01-15-2020 08:40 AM
It appears that it isn't possible to test expired cards. Is that true?
04-17-2023 10:52 AM