Receiving an error when initiating a test check out with Authorize.net. support told me that I need to add: Sandbox API Endpoint: https://apitest.authorize.net/xml/v1/request.api
to the code of my site.
when I went into WP and looked at my site health there was an error for: The server port value is unexpected. Try adding the following to your wp-config.php file: define( ‘JETPACK_SIGNATURE__HTTP_PORT’, 10004 )
I was thinking this may be the issue why my Authorize cart checkout is receiving “User authentication failed due to invalid authentication values.”
I logged into the database of .local and can see database files, but nervous on where to actually update and put said snippets.
Can anyone here help me?
What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc I have received API errors and suggestions form Authoirize.net.
Security Reminder
Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed. local-logs.zip (92.4 KB)
I’m having a little trouble following here. What exactly do you need help with inputting? Do you need instructions on how to update your wp-config.php or something in your database? Did the people you talk to provide any documentation?
Hey there Nick!
Yeah, Authorize support was vague, I am going a little blind here. I did see an error in my database log. I guess I am just trying to figure out why Authorize will not successfully complete a transaction in testing (using flywheel).
I cant really find a good way to add the snippets in DIVI builder, so I guess I am wondering if anyone else has had this issue and how they resolved it.
I found an old thread here with users doing similar testing and running into issues because of the basic auth prompting in Live Links. The TLDR is that it seems like these sorts of things are better tested on a live site.
One user came up with a pretty hacky workaround here but this might be outside of your comfort level to try:
It seems like Jetpack testing requires a site to be live as well. They have some steps on how to set up “Offline Mode” but a lot of features will still not be available: Offline Mode