petzo

I've already created a bug report for that: http://forge.prestashop.com/browse/PNM-3410 Copy/paste from the report: Paypal ExpressCheckout API requires some addresses to include state (link to info at the end). If for some reason such state was not defined in a user's address, Paypal module finishes the payment flow with a "Fatal error" screen with no chance to recover. By default most of those (but not ALL) countries in a new Prestashop 1.6.0.14 installation require state. But this is not true when updating from old installation. I was updating from 1.4 and this is how I experienced the bug. Steps to reproduce: 1. Clean Prestashop 1.6.0.14 install 2. Install Paypal module 3. Create an user with an address in Brazil (by default Brazil doesn't have states, but they are required in Paypal) 4. Buy with Paypal 5. Paypal doesn't complain about the wrong address - just ignores it 6. When You complete the steps in Paypal.com and you are taken to your store, Paypal doesn't return correct(any) address (as it was ignored). This results in a "Fatal Error". When debug mode is enabled you can see some kind of debug info. The most reviewing is this: Notice: Undefined index: PAYMENTREQUEST_0_SHIPTOCOUNTRYCODE in .../modules/paypal/express_checkout/payment.php on line 91 I'm attaching the file. List of addresses requiring states: Argentina, Brazil, Canada, China, Indonesia, India, Japan, Mexico, Thailand or USA. Source: https://developer.paypal.com/docs/classic/api/merchant/SetExpressCheckout_API_Operation_NVP/#id09BHCD0707U__id107SHG090HS

I've already created bug report, but no one seems to saw it, so I'm pasting a link here: http://forge.prestashop.com/browse/PSCSX-5398 Copy/paste from my report: Reproducible on a clean 1.6.0.14 installation. Prices not converted in Paypal payment when Paypal currency is different from the user/shop currency. The screenshots explain it very well, but steps to reproduce: admin: 1. Clean Prestashop install 2. Install Paypal module 3. Install USD currency 4. Set Paypal currency to be shop default (EUR) as user: 1. Select USD as currency 2. Buy something 3. Pay with Paypal result: 1. Something that was $27.88 (USD) in the shop becomes €27.88 (EUR) in Paypal!!! 2. Shipping is not affected so $7.51 (USD) becomes €7.00 (EURO) I can't stress this enough but this is MAJOR MAJOR issue!

Just to add the response I've got from Paypal, after finally getting to contact them and asking what was the problem: "I apologize for the inconvenience and frustration that this issue has caused you. The issue was found in one of PayPal's servers and was tracked under restore ticket number RESTR16428699 Unfortunately that is the only information I can release on this internal issue with our PayPal servers." So it seems that they have tracked down the issue. I find that satisfying to know.

I just wanted to contribute to the topic, as we have experienced exactly the same ip block issue from Paypal. It was pretty frustrating - absolutely NO response from their support. The issue was, as others have reported - our server could not connect to "https://api-3t.paypal.com" which was causing our prestashop not to be able to complete Paypal payments. We had to move the site to another server/ip so it could function. When we did this, everything was fine. Now, because I was checking this thread from time to time, I saw that you guys where reporting that ban was lifted form some of you. I decided to check what was going on our previous IP/server. What I have found out is that it was already OK for it too... So ban was lifted... Server can connect to Paypal servers... That is good in a way... right ... What I don't like is that we have absolutely no idea why this happened and could it happen again?! Could it happen on our new server... should be switch back to our previous hosting... Absolutely no explanation from Paypal is not nice... _________ PS Just wanted to add that I have also involved my hosting provider to check how can we resolve this issue. They have told me that they were going to "talk to Paypal" to locate the problem as they have independently, on they own, confirmed that this was the reason causing the problem. I don't know if it was because of them Paypal fixed it ...