PayPal not taking payments.

[sally01]

We are getting a message when going from our website over to PayPal saying

'Things don't appear to be working at the moment. Please try again later.'



Any ideas please.

[Mike Hughes]

Just tried mine and it's working OK.

maybe intermittent, or solved?

[sally01]

all four of our websites are getting the same message. Has been like that all weekend.

[Mike Hughes]

Who is your webhost?

There were some new technical requirements for Paypal due in 2016 that were then postponed to 2017 but from what I remember these aren't due until the end of June. See http://community.sellerdeck.com/showthread.php?t=56703

I've checked and the paypal security roadmap doesn't show anything due at the end of March with the next deadline being the end of June so that side should be OK. https://www.paypal.com/au/webapps/mp...curity-roadmap

All I can think of is to try to compact the database and refresh the site just in case something has got corrupted somewhere.

Mike

PS. There's no sign of any relevant errors in your error log. It might be worth talking to PayPal in case there's something they can identify from their end.

[MattSMR]

Hi Sally,

Same for us here, running 16.0.2.

I've spoke to Dean James & Oliver in support who are insistent it's not an Actinic issue.

I'm convinced it's related to the March 29th PayPal update - https://www.paypal-knowledge.com/inf...ewlocale=en_US

3 sites are affected by this, heatedtowelrails4u.co.uk, showerrails4u.co.uk, radiatorvalves4u.co.uk

I have had to temporarily disable PayPal standard payments on site.

I've got an open ticket with PayPal on the matter since Friday, nothing yet.

Interestingly, our V11 sites standard PayPal integrations are working fine.

[MattSMR]

Also, for what it's worth, I've just tested your site in Chrome, not working for me either.

Dean James managed to get through to PayPal on our sites from his machine, however Oliver in support was not able to.

[Mike Hughes]

Interesting. So it appears to be a new paypal validation action on their new streamlined checkout.

The most common problems are given as:

Passing currency symbols ("$", "£", etc.) or values other than integers (1, 2, 3, etc.) and decimal points (“.”) in the amount field. For example, "1234.50" is correct, but "$1,234.50" isn't allowed.
Passing country code values greater than two letters. For example, "FR" is correct, but "France" or "fr_FR" isn't allowed.
Passing more than 127 characters in the item_number field. For example, don't use the item_number field for "Note to Buyer" information.
Passing more than 64 characters in the option fields (on0, on1, etc.).
Passing duplicate empty parameters.
Passing address_override=1 without passing an address.

Mike

[Mike Hughes]

I believe sellerdeck changed it's PayPal integration from IPN to PDT from version 14.0.2. See http://community.sellerdeck.com/showthread.php?t=56694

This might explain why the problem isn't being seen on V11 sites such as my own.

Mike

[sally01]

Interesting. So it appears to be a new paypal validation action on their new streamlined checkout.

The most common problems are given as:
Passing currency symbols ("$", "£", etc.) or values other than integers (1, 2, 3, etc.) and decimal points (“.”) in the amount field. For example, "1234.50" is correct, but "$1,234.50" isn't allowed.
Passing country code values greater than two letters. For example, "FR" is correct, but "France" or "fr_FR" isn't allowed.
Passing more than 127 characters in the item_number field. For example, don't use the item_number field for "Note to Buyer" information.
Passing more than 64 characters in the option fields (on0, on1, etc.).
Passing duplicate empty parameters.
Passing address_override=1 without passing an address.



Mike

Looks like this might be our problem as we use 3 letter country code to distinguish between UK Mainland/Highlands/Northern Ireland

Put an order through for France and it took me to my PayPal account.

[MattSMR]

Hi Sally,

We use "UK" as our country code, so while I think yours might be related to that, it could be a more widespread issue.

Can you try changing your codes to UK and giving it a try? UK is technically correct as a country code, however I understand why you've done what you have to distinguish.

[Mike Hughes]

I think the correct country code for the UK is 'GB'.

You could try that and see if it fixes the problem.

[MattSMR]

I think the correct country code for the UK is 'GB'.

You could try that and see if it fixes the problem.

Hi Mike,

Would this be the field "ZoneID" in BandDefinition of ShipControl?

Happy to give it a shot on one of our sites later.

[Mike Hughes]

I think it's the two letter code next to the country in Settings > Locations.

I think Sellerdeck introduced some code that would change 'UK' to 'GB' for compatibility with paypal pro but I've no idea if that is still in place or not.

Mike

This is a previous thread on problems with the country codes and how it was fixed. That problems was using 3 letter codes, but it shows the way to fix it (which might be helpful to Sally) and also shows the 'UK' => 'GB' fix that's already in place. http://community.sellerdeck.com/showthread.php?t=54745

[Mike Hughes]

It seems to be a bit more convoluted than I thought.

1. The previous discussion about the scripts changing 'UK' to 'GB' for ISO compatibility seems to be in the PROTX scripts only.

2. The paypal Pro scripts seems to have this back to front.

# we have to translate GB to UK to be ISO compatible.
#
$$hResponse{"SHIPTOCOUNTRY"} =~ s/^GB$/UK/;

Which I guess is where Martin (Feemish) got it from in some of the previous discussions where he finds the code is back to front.

3. It looks like the paypal script has it correct, but it seems to have been thrown in as an additional thought with no clear commenting or explanation about what it's doing.

$sCountry =~ s/^UK$/GB/;

[sally01]

Hi Mike,

following on from your last post. For our Northern Ireland orders where we use a code of UKNI could we use something like below?

$sCountry =~ s/^UK$/GB/;
$sCountry =~ s/^UKNI$/GB/;