|
KIROS
|
April 25, 2018 at 4:50 pm
Hi there, done quite a bit of searching and PayPal show we are not sending the State through the gateway and therefore don’t qualify for seller protection. When we review transactions in PayPal Pro, we only see XX as a value for state. Is this a bug? Do I need to add code to get this to go through? Or something else entirely. 🙂
|
|
Tony
|
April 26, 2018 at 5:33 am
Hi there,
I just checked a couple of PayPal Pro payments and the state field is sending over fine for me, are your users logged into the site when making a payment?
When you have XX do you literally mean ‘XX’ or is it a 2 digit number?
|
|
KIROS
|
May 2, 2018 at 5:51 pm
Literal XX. User would not be signed into PayPal at all, but should be logged into the site, but I can’t verify that. There is a good chance they are not logged in.
|
|
Josh
|
May 2, 2018 at 8:33 pm
Hi there,
You can check the PayPal response that gets logged by Event Espresso by going to Event Espresso → Payment Methods → Logs. Each PayPal Pro transaction should have about 3 log items and one of them will contain the PayPal Response. That part of the log entry will look like this:
https://slack-files.com/T02SY781D-FAJBTCTK8-1b0c629d6e
If the State field is showing XX there, but an actual State name was input, then there may be something filtering what’s being input and changing it to an XX.
|
|
KIROS
|
May 15, 2018 at 10:15 am
Thanks, it appears that the state is being sent to PayPal Payments pro as the full text ‘Washington’ vs. two letter code of ‘WA’. Log shows only ‘Washington’ and not returning error codes, but PayPal documentation shows that it would be expecting two letter state code here: https://developer.paypal.com/docs/classic/api/state_codes/.
How do I proceed?
|
|
Josh
|
May 15, 2018 at 12:52 pm
You can go to Event Espresso → General Settings → Countries and check the Code field in the Washington state row. The field should have WA input there.
|
|
KIROS
|
May 15, 2018 at 4:06 pm
Codes are correct there, but the log shows that it’s sending Washington instead of WA. Is this possibly a bug or am I missing another setting?
|
|
Josh
|
May 15, 2018 at 4:14 pm
That’s probably a bug where something was changed and it’s no longer sending the correctly formatted code for State. I’ll open an issue on Github so they can investigate further and fix.
|
|
KIROS
|
May 16, 2018 at 8:43 am
Thank you!
|
