error code 35 : An error occurred during processing - authorize.net

I am using authorize.net to charge credit cards. everything works fine in the sandbox but changing to production gives me the error "An error occurred during processing. Call Merchant Service Provider."
I have verified the production URL, id and key everything is correct.
can anyone help me with this please

Related

Getting 401 token error with Azure Active Directory SSO

I'm trying to setup Azure AD SSO to authorise users to log into AWS. I believe I have things mostly set up, I get the Microsoft login option & after logging in I get the error Invalid request 401 - error getting token.
I've tried everything I can find that might be wrong but to no avail, does anyone have any clue as to what might be misconfigured?

"Missing Authentication Token" trying to perform a Post to AWS api

There have been loads of topics on this error and I've spent hours reading through them. I am getting this error when trying to load the URL of my Post method (it works fine when I test it within the AWS console). When I run the URL created after I deployed it:
https://somehexvalues.execute-api.us-east-1.amazonaws.com/prod/temperature
I get this errror: message "Missing Authentication Token"
I can see the response contained this error: missingAuthenticationTokenException
I've done the exact same thing with a Get and had no problems. Is this something specific to Post?
I deployed the app after every change and took the URL from the method's STAGES tab.
Validation and authentication are set to "None"
Is there anything else I can do to debug this?

Production app: Invalid or unknown client (ID copied from credentials page)

I went through the sandbox testing and graduation procedure. My application got approved (for internal use), but I've been unable to use the new client ID.
The OAuth callback URL contains the error message:
GET /oauth2callback?error=invalid_request&error_description=OAU-230%3AInvalid%20or%20unknown%20client%3A%20xxxxxxxclientIdxxxxx
I copied my client ID several times from the application credentials page, it is correct and complete. The ID is repeated correctly inside the error message as well, so I know it's received on the production server. The production server URL is correct too.
What's going on here?
Apparently, all I had to do is wait. After graduating my application and getting the Approved message, RingCentral took a while longer for the new credentials to start working. I don't know how long it took, as I've waited 28 days to try again.

Issue in redirecting back to our Site from sandbox test authorize net

After processing the payment, control is not directing back to our site(x_relay_url) from https://test.authorize.net/gateway/transact.dll.
The URL mentioned in the x_relay_url cannot be accessed directly it requires session id and other details to access it which was passed to Authorize net page using merchantDefinedData variables.
I checked the following article also but our URL seems to be fine and we checked our code there is nothing wrong in that.
I tried multiple URLs in "x_relay_url" but nothing seems to be working.
Any help is appreciated.
Error Message:
An error occurred while trying to report this transaction to the
merchant. An e-mail has been sent to the merchant informing them of
the error. The following is the result of the attempt to charge your
credit card.
This transaction has been approved.
It is advisable for you to contact the merchant to verify that you will receive the product or service.

Transaction Failure in payment gateway Authorize.net

I have installed authorize.net sdk(PHP) and changed config file. I am running the sample app that comes along with the bundle.
When I proceed with the payment, the transaction fails and responses below error
"We're sorry, but we can't process your order at this time due to the following error:
The merchant login ID or password is invalid or the account is inactive.
response code 3
response reason code 13"
Naturally you need to verify your login credentials are correct. Also, make sure you are using the right server. You can use the production server or development server for testing. If you mix up your credentials that will cause this also.