|
Skye
|
July 31, 2019 at 4:25 pm
Hello, we’ve a situation where an e-mail address won’t always get passed through Event Espresso and show up on the receipts we generate through “PayJunction.” Any clues?
|
|
Josh
|
July 31, 2019 at 5:13 pm
Hi,
What you could do is contact PayJunction support. PayJunction actually developed and supports the PayJunction gateway. It’s not supported by Event Espresso.
https://support.payjunction.com/hc/en-us
|
|
Skye
|
August 1, 2019 at 9:14 am
Good morning, and thanks for the note back. I started with PayJunction of course, and they were able to duplicate the error, but suggested it was not being passed through to their system. Other data is (name, address, amounts, etc.), it’s just that on occasion it drops e-mail and not all the time. We haven’t been able to isolate why that is. Any other suggestions? Thank you.
|
|
Tony
|
August 1, 2019 at 1:48 pm
Hi there,
If you look in the registration itself, can you see an email linked to the contact for that registration?
Meaning if you go to Event Espresso -> Registrations, find the registration this happen on and click on the name. Now look ‘Contact details’ section to the right – https://monosnap.com/file/Ee5qqGRMYc5OMjCPrFokGIqSnVDD0p
Does it show the email there?
With Event Espresso the payment method takes over sending all of the details to the payment provider, so when a 3rd party creates their own custom payment method, it’s down to the code used within that 3rd party payment method as to what details are send over. Why only sometimes it would fail, I’m not sure, as I don’t know any of the code for that payment method, but if you see an email address in the section I mentioned above EE has done everything it should be doing and the issue is most likely with the payment method.
If the payment method is logging the requests sent to/from your site and the payment merchant you can check those logs to confirm what details are being sent over, maybes its an encoding issue with the request they are using (blind guess!) and thats one way to narrow it down. If the payment method isn’t logging thew requests, then you can request they add logging, or use something like Log HTTP Requests and see if the requests to the merchant show up there. Then wait for a failed email and check over the logs.
In short, the payment method has all of the control on what it sends over so you’ll need to start digging into what that is doing rather than EE.
|
|
Skye
|
August 7, 2019 at 12:24 pm
Good morning. After a back and forth with PayJunction, the determination was made that its the QuickLink API that doesn’t support the ability to transmit an e-mail address. Just FYI the work around we settled on was to customize the event registration notification to include address and email
|
|
Tony
|
August 8, 2019 at 8:14 am
That’s still a little strange if it only happened on a few of the requests and not all, but I don’t know all of the details 🙂
Either way, I’m glad you found a solution and thanks for keeping us updated.
|
