Posted: June 5, 2019 at 6:15 am
|
|
Hi, here’s the link to the original forum post on event espresso: And here’s the email trail between me, my credit card processor, and my developer. Please let me know how you can fix, thanks: ———- Forwarded message ——— This is what my credit card processor said when I told them that event espresso said it was up to my cc processor to fix the error: Dear CHRISTOPHER SABIDO This is the transcript of our discussion. 00:00:02 system : Welcome to Authorize.Net Chat Support. Please do not send any password, bank, credit card, or SSN information. For further help, please visit our Support Center at http://support.authorize.net. Based on the above, I reached out to my developer. This is what my developer said when I forwarded them the transcript you just read: Hi Chris, We have read through the chat and understand that this is something the developer can change. In this case, it is something that Event Espresso would need to change since they are the developers of the integration. Authorize.net integration is included by default with Event Espresso. https://eventespresso.com/features/payment-options/ We would recommend reaching back out to Event Espresso and providing them with the same information you provided us. Since we are not the original developers for the integration, if we were to customize the integration then the next time Event Espresso pushes an update it would overwrite any changes we make. For reference, our only part in the Authorize.net setup was configuring the settings through the WP Admin dashboard with the API info you provided and making adjusts to the settings Event Espresso includes in the integration (such as the fields it collects). You can see the available options you can configure by going to Event Espresso -> Payment Methods -> Authorize.net AIM in your WP Admin dashboard. As you will see there is no option to suppress the code 523. Let us know if you have any questions. Thanks! Jaylynn Boone 2K Web Group Apalachicola, Florida 32320 *** thanks, WordPress Version: 4.9.10 PHP Version: 7.3.5 MySQL Version: 5.5.5 Event Espresso Version: 4.9.79.p WordPress Address (URL): https://awakenedlifeschoolofyoga.com Site address (URL): https://awakenedlifeschoolofyoga.com |
|
Hi Chris, There are a few points above that are incorrect and imo the term ‘security risk’ does not belong in the above conversation as that’s a serious accusation being made against EE. There’s no more risk in displaying the response code itself than there is in displaying the text from auth.net themselves. To explain, all of the Auth.net response codes (with their additional text/info) is public information and can be found on the link included by the support agent, or download all of them HERE. Displaying the response code is no different from displaying text/additional information they also include in the response as it takes seconds to search the above for the response text to find the code itself, so the code itself being a security risk makes no sense. Before going into detail on the above can I take a quick look over the payment logs on the site? I’d like to confirm exactly what response EE is receiving from Auth.net. You can send temp login details using this form: https://eventespresso.com/send-login-details/ What looks like is happening is Auth.net is returning an error response with code 253 but is actually processing the request. As EE is receiving an error response it’s displaying the message to the user (as its an error) and we include the response code there so that the user has more details to provide to the admin. Meaning rather you getting an email with ‘the payment said it didn’t work with a messaging saying it failed’, you can get something like ‘the payment failed with an error and had code 253’, which gives you more info to work from. The response code can be removed, without having to edit EE’s files, meaning it won’t be lost on update but we’ll get to that shortly. I’d like to confirm exactly what is being received from the auth.net first. |
|
|
|
Hi Tony, Saying it was a security risk didn’t make any sense to me either, especially since I can just google authorize.net error codes and find out what they all are! At any rate, you’re correct: authorize.net is flagging certain charges for review, but not declining them. Once I go in and approve them, authorize.net is then processing them. So ideally, you guys would just remove the response code, as it’s confusing for our clients. Just yesterday someone reached out to us again, concerned that their payment didn’t do through. Can you do that? thanks, |
|
With the registrations this is happening to, are they being set to Approved and the payment shows as Accepted within EE without you doing anything? The reason I want to see the logs, is with a ‘success’ response there’s no message shown on the screen, the payment goes through and they go through to the thank you page showing their registration and payment status. So the reason people are contacting you is likely because that isn’t happening and the reasons that would happen is if the response from auth.net was not success but something else and depend on what it is we may be able to process it differently, meaning the user may still go through to the thank you page in the above situation. Removing the reason code from the message isn’t really the right solution here and I don’t recommend it, but to do it you need to translate this text `’%1$s (Reason Code: %2$s)’ You can do that using a snippet like this: https://gist.github.com/Pebblo/8ca7e0ada54d6b615eff8b76ded48461 Only within the https://gist.github.com/Pebblo/8ca7e0ada54d6b615eff8b76ded48461
So your strings array would be: You can add that to a custom functions plugin on your site, we have some documentation on creating one here: https://eventespresso.com/wiki/create-site-specific-plugin-wordpress-site/ Although again, the better solution here is for me to take a look over the logs and see what is actually happening. |
|
|
|
This reply has been marked as private. |
|
Thank you for the login details, however for me to view anything you’ll need to upgrade that account to an administrator account as right now I only have subscriber access. |
|
|
|
This reply has been marked as private. |
|
Thank you. So looking over the response I can confirm that the AIM payment method doesn’t handle the payments that are held as if they were complete or even pending. Auth.net is not responding with an ‘approved’ payment response, they are responding with a ‘held’ response and with the AIM payment method you are using, anything other than Approved is currently considered ‘failed’ (Not that the payment actually failed, but the payment status will be failed). That’s why the error message is shown and your users will be contacting you at that point as the registration/payment will not be shown as complete and the ‘error’ message shown, meaning removing the response code isn’t really going to help. The first thing to note is Auth.net have deprecated the AIM integration method in favour of their Accept integration methods, which we use with the Auth.net Accept Payment Method. The fact that AIM has been deprecated means they will eventually stop support for it altogether (although granted that will likely be a while from now) so we recommend switching payment methods. I can see the code used in that Accept payment method should handle ‘held’ payments by setting their status to ‘Pending’, this would direct your users to the thank you even if their payment is held. Currently, with the AIM payment method, you (the site owner) take full responsibility of PCI compliance for your site and that payment method requires the highest level of compliance. The Auth.net Accept payment method requires the lowest level to comply, which imo is another reason to switch to that integration. |
|
|
|
Thanks Tony, appreciate it. I’ll have my developer make the switch. Chris |
The support post ‘Error code 523 – payment processor says event espresso needs to fix it’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.
