This looks like the charge is happening too fast after the
authorization, so the system can’t find the transaction yet, which
causes Error 16. It mostly affects saved cards like Visa and MasterCard.
We’ve seen similar issues when things run almost in...
Yeah, using a 2013 SDK might be holding things back, especially with COF
changes.The newer Authorize.net SDK should have better support for those
requirements.Probably a good time to update and move away from older
methods like createCustomerProfileT...
It sounds like the form isn’t fully resetting those sensitive fields on
resubmit. Try clearing and repopulating the CVV and AVS fields each
time, and make sure a fresh payment token is generated with each
attempt.
That sounds super frustrating, sorry you are dealing with that. It
definitely seems like something might be off with how the forms or
merchant accounts are tied to each subdomain. Hope you’re able to get to
the bottom of it soon!
