Posted: December 6, 2024 at 9:26 am
We recently updated EE and are now seeing a payment method error: It appears that the event you were about to make a payment for is now accepting payments at this time. Please contact the event administrator if you believe this is an error. We have not updated our Authorize.net payment method and expected some time before a final cutoff for Authorize.net AIM Please advise! |
|
Can you confirm which payment method(s) are acitve and have proper credentials? Can you provide a link to where we can replicate this happening? |
|
I wasn’t expecting Authorize.net AIM to not work all of a sudden so I switched the payment method to Authorize.net Accept. I’m now able to accept payments again. Do you know why Authorize.net AIM stopped working with the latest EE update? I was delayed on updating EE because we also seem to have an issue where something breaks after an update. |
|
Are you sure the only change you made between this working and not was switching to Auth.net Accept? This notice:
Isn’t directly related to payment methods, that’s based on the event being open for payments to then load payment methods, its part of the Single Page CheckOut process which loads before payment methods (SPCO is what actually loads the payment methods themselves). Which means if your getting that notice you’d get it regardless of the payment method used unless something on the event itself changed. Were you tested the same registration using the same method to get to the payment options before and after switching payment methods? |
|
Side note regarding the deprecated Payment methods. AIM has been deprecated (with a few others) for a while now but as of now, nothing has changed with how AIM functions. EE will still load and use the Auth.net AIM payment method as is but we display a notice in the admin stating that it will be deprecated and that you need to switch to a newer payment method. The current deadline before EE will ‘officially’ deprecate the payment methods and take action is Jan 2025 |
|
Yes, that error message went away when I switched to Auth.net Accept. |
|
You must be logged in to reply to this support post. Sign In or Register for an Account