Posted: January 2, 2025 at 2:07 pm
|
Our Authorize account has been working steadily for years and now when switching to Authorize Accept we are getting this error continuously “There was an error initializing the payment form from Authorize.net. Please contact the site administrator.” even with sandbox on |
|
|
Hi there, Can you tell me about how you are testing or setting up your site? Are you using your sandbox or live credentials while testing in sandbox mode? Double-check your credentials to make sure that you are using the API Login ID and Transaction key. Also, make sure that there is no extra spacing before or after the credentials in the payment methods page of Event Espresso. |
|
|
Installed the Authorize Accept add-on at NAAUD.org and while the AIM configuration was working fine we went ahead seeing the deprecation of AIM bought the $99 add-on. and now Authorize doesn’t work no matter how many time I redo the Transaction key, or the client key or the public key or tunr the plugin on and off, dump the cache. Site uses Version 5.0.31, I need help quickly but not sure if this is even a working support ticket system as I getting no reply that I’ve even submitted a ticket. How can I get help with this matter? Thank You |
|
|
Installed the Authorize Accept add-on at NAAUD.org and while the AIM configuration was working fine we went ahead seeing the deprecation of AIM bought the $99 add-on. and now Authorize doesn’t work no matter how many time I redo the Transaction key, or the client key or the public key or tunr the plugin on and off, dump the cache. Site uses Version 5.0.31, I need help quickly but not sure if if the support ticket system is even picking up my support ticket since I get no acknowledgement I’ve even submitted it. |
|
|
Hi there, I’ve merged all your threads on this together to keep the replies in a single place and work through this. What I would do right now, is enable the AIM payment method again so that you have an active, working payment method for users to pay on your site. Note if you’ve regenerated your Auth.net API/Transaction keys in your account you’ll need to update those within the AIM payment method settings for it to work but that gets you back up and running with a working payment method whilst we troubleshoot the above issue. You can leave both AIM and Accept enabled whilst troubleshooting and then disable AIM when Accept is fixed. — Right now I can tell you, this is unlikely to be a cache issue. The error your getting is from a request being sent to Auth.net themselves to create your payment form and they are returning an error which is saying your credentials are invalid. Is Sandbox mode enabled within the Accept payment method? From your reply, I assume your API login and Transaction key are valid, and you’ve double-checked that the values used match those from your account.
AIM and Accept are 2 different integration methods that are independent of each other, they are both a way to connect to your account but one can work another other not (usually they are both fine, but there’s always a possibility something isn’t enabled on your Auth.net account to prevent one/both from working). With getting the authentication error you are getting and if you are 100% certain that your Authorize.net API login ID & Authorize.net Transaction Keys are correct within the Accept payment method and you do NOT have Sandbox Mode enabled (Sandbob uses a totally different account specially for Auth.net Sandbox) then it may be an issue with the account and something needs to be enabled. I can’t say for sure yet as we don’t have enough info, just adding some details as to why AIM can work but Accept not. |
|
|
Thanks for replying quickly, AIM has been working for several years we only traded it for Accept because of the giant deprecation action language at the top of the page. We are launching a new conference and rather than wait till January 15. We decided better to get Accept working than wait and interrupt registration on Jan 15. Downloaded the add-on installed it went to Authorize account copied the login API login key and generated a new Transaction key and pasted that (while AIM was still active) dumped site cache, and promptly got our 1st E00007 error in “live” mode, wasn’t using sandbox at that point. Called Authorize support but they weren’t helpful. Assumed maybe we couldn’t have AIM active as well so turned it off. Once we were in this state I did try sandbox and was getting same error. Tried generating a new T key. No luck tried turning the add-on plugin off and started over again same error. Tried running testing from Authorize on and off nothing. Went through all EE settings, tried various configurations of testing and live and same error. Tried generating a new Public Client Key, but since this doesn’t require a Public Client that was probably a mistake. Tried the Authorize sandbox with a variety of configurations same error. Read and reread all documentation. But there’s enough dead links in EE and Authorize documentation could never locate the “You can correct this issue by enabling the Transaction Reporting API through your Authorize.net account.” From what I could see since we were already using Authorize transaction reporting should have been on, and couldn’t find any thing in Authorize to “turn on” in transactions. All along have been testing over and over and each time same error. Obviously it appears it doesn’t recognize the account within the accept API. But I’ve been through all the authorize options and not seeing any options to use accept vs AIM. Is Accept a whole different Authorize service? What am I missing? We’ve truly had great outcomes for years with this plugin and AIM, and wasn’t sure if there is an actual deprecation of AIM since none of your support doc mention it’s being deprecated. Thank you for your help ahead! |
|
|
Replying to Garth, it’s not spaces this issue, (saw that and made sure there were no spaces) is ongoing no matter with same error E00007 after 50 some attempts both live and in sandbox – put in a support token — but reaching out again to Authorize — either it’s the Accept add-on plugin or something at Authorize not recognizing the Accept status and there’s nothing in the Authorize dashboard of use to why the error |
|
Or is the request being malformed before/as it is being sent. The E00007 error is directly from Auth.net themselves, this isn’t an error from EE that I can give you more details on and the docs from Auth.net don’t give much details (I support they can’t really give many details on this, if the credentials are wrong, they are wrong and that’s what the error is saying… if its a service that needs to be enabled it could do with returning that in the error but we don’t know if it is here). This is the docs for E00007: So using Sandbox credentials when connecting to Live or vice versa. Or the API Login ID or Transaction Key is incorrect, but if AIM worked and you just copied those over, that seems unlikely too (at least in the beginning).
In Auth.net? You won’t fine options specifically for Accept itself in your auth.net account.
Service? Not really, it’s an integration method, so the API is used to connect between EE and Auth.net although it does work differently. It is an Auth.net hosted option rather than your server processing the card details and POSTing them to auth.net like AIM does, part of which is to reduce PCI Compliance requirements on your end.
So far, it sounds like you’ve covered all basis! I can see your support token request so I’ll log in and take a look now.
Yes, its from us (EE) and the notice on your site should link to this support doc: https://support.eventespresso.com/article/612-deprecated-payment-methods-2025 Auth.net themselves have deprecated AIM so we’ve had to follow suit: |
|
|
Just got off phone with Authorize and they don’t see anything wrong with account, it is live is is valid, they did mention whether there was any difference between script delivering http vs https in that Accept plugin — but I haven’t checked source to see if I can track that down pointing me to this https://support.authorize.net/knowledgebase/Knowledgearticle/?code=000001158 |
|
|
The error beign thrown from Auth.net is:
Looks like this is from the comma in your Organization name set within General Settings. I’ve swapped that out for a dash ( |
|
|
Awesome, bizarre since it worked fine with AIM and just threw that error when changing to Accept, and neither are an exact match to the actual Authorize account name. Glad to get this back in order – Thanks, this is definitely resolved 🙂 |
|
You must be logged in to reply to this support post. Sign In or Register for an Account
