Hello all,
I'm dealing with a strange issue in our production environment wherein I'm able to post to accept.authorize.net/payment/payment and display the hosted form properly, but when I hit "Pay" within the hosted form, I end up with the E00007 "User authentication failed due to invalid authentication values" error. I don't understand how I could get the hosted form for the production environment, yet receive this error after trying to pay. Does anybody have any ideas?
Best,
Jonathan Rasmussen
Software Developer I
College of Southern Idaho
Application & Data Architecture
jrasmussen@csi.edu
208-732-6846
Solved! Go to Solution.
04-01-2019 10:42 AM
04-01-2019 01:18 PM
It's also worth noting that the actual payment went through to the payment gateway, but the iframeResponseHandler is what failed with this error. We need to redirect the user to the custom receipt page and do some database work, which relies on the transactionResponse.
Best,
Jonathan Rasmussen.
04-01-2019 12:43 PM
04-01-2019 01:18 PM
Yes, I've definitely changed the environment to production. As much as I would love to use webhooks for the db related work, that isn't an option here, as we have other systems using the same merchant account for payment management. I don't have this issue on production, and it seems strange to me that I would receive an authentication-related issue due to server performance. The way I have the iframe response handler set up, the database work won't even begin until there's a successful response, so it has nothing to do with that. I do appreciate the advice though. I'll try a bit more debugging and see if there's something going wrong in my internal API for my web app.
Best,
Jonathan Rasmussen
04-01-2019 01:27 PM
04-01-2019 05:53 PM
I've figured out the problem. I totally spaced out and forgot that I'm making a second call to the API during this process to get the transaction details. This means that I also had to set that API controller to production.
Regarding your question about the webhooks - we would receive notifications about payments from another system that we actually don't want going to the system I've been working on. In addition, the custom email receipts we're sending out are being generated using information from the payment session, so webhooks wouldn't fit this exact use case. I could potentially develop a different architecture to allow for that, but that's a time investment that we can't afford right now. Thanks for all the help anyways; I really do appreciate it.
Best,
Jonathan Rasmussen
Software Developer I
College of Southern Idaho
jrasmussen@csi.edu
208-732-6846
04-02-2019 02:19 PM