|
mkreik
|
March 28, 2023 at 8:47 am
We notice that periodically transactions are passed to Square without the event name (ticket name). In those cases we see the following message in the transaction’s payment detail in Event Espresso: Unable to read the response body. The amount is processed, but then staff have to open the website dashboard to find the transaction to code it correctly in our accounting systems. In this most recent case, the transactions before and after the one with the error were for the same event and the ticket name was passed over correctly. Is there something we can do to pass the event name over to Square after the transaction has been processed? Is there something we can do to prevent this error from happening in the future?
|
|
Garth
|
March 28, 2023 at 9:43 am
Hi there,
So, to clarify, the affected transactions have two problems:
1) The Transaction Details in Event Espresso state “unable to read the response body”?
2) The transaction details in Square are missing the ticket name?
Do you have any screenshots you can share to help clarify what you’re seeing?
|
|
mkreik
|
March 28, 2023 at 12:43 pm
Yes. I will send the links to you in a private reply
|
|
mkreik
|
March 28, 2023 at 12:54 pm
This reply has been marked as private.
|
|
mkreik
|
April 3, 2023 at 8:34 am
Any solution to the issue?
|
|
Garth
|
April 11, 2023 at 2:10 pm
Sorry for the delay. Those screens are not loading for me.
The transaction in Square should show the ticket name.
|
|
mkreik
|
April 11, 2023 at 4:24 pm
All of the screen shots are still loading for me. The transaction in Square does not show the ticket name because the ticket name was not captured within EE. Is there another way I can sent you the screenshots so you can see the error in EE>transactions?
|
|
mkreik
|
April 17, 2023 at 12:01 pm
Can you see the screen shots from 3/28? I’m still able to open them. I’d like to get this issue resolved so we don’t have situations where the EE transaction does not include the ticket name.
|
|
Garth
|
April 21, 2023 at 10:32 am
This is what I see (or don’t see) when I look at your screenshot links: https://www.screencast.com/t/kgG3mo3rN
Here are examples of the ticket name included in Square:
– Transaction details: https://www.screencast.com/t/k87wzpMNuv
– Order details: https://www.screencast.com/t/bNiaaDo2
|
|
mkreik
|
April 24, 2023 at 3:08 pm
I cannot explain why you cannot see the screenshots since I can in an incognito window without being logged into the screenshot provider. I don’t want to sign up for another screenshot service. Is there another way I can share the screenshots with you like via a Dropbox link?
|
|
mkreik
|
April 24, 2023 at 3:18 pm
This reply has been marked as private.
|
|
mkreik
|
April 24, 2023 at 3:19 pm
This reply has been marked as private.
|
|
mkreik
|
April 24, 2023 at 3:19 pm
This reply has been marked as private.
|
|
Garth
|
April 25, 2023 at 3:04 pm
I can see the dropbox link.
So, do you see a pattern with this issue when you see a failed payment attempt in Event Espresso, then a successful payment attempt in Event Espresso, but the ticket details in Square do not show the ticket name?
Is that what you’re seeing?
|
|
mkreik
|
May 8, 2023 at 10:29 am
That’s a great question. I will have to go through hundreds of transactions to find the ones that do not pass the ticket name to see if they all have an initial failure like and then success.
|
|
Garth
|
May 8, 2023 at 2:33 pm
okay. Let us know.
|
|
mkreik
|
May 17, 2023 at 11:07 am
This reply has been marked as private.
|
