Tried to follow magento's own paypal integration for payment pro. and everything seemed to work fine untill I tried to process an order . The I get an error (in the log file) saying:
"PayPal response hasn't required fields."
and since I followed the magento paypal integration thingy to the letter. I hope someone else have bumped into this problem before and could point me in the right direction.
Well solved it myself.. found out that this error is magentos way of saying: paypal says, that the api information is wrong. So if you bump into this one go check your api credentials. :)
Related
I'm getting this error when I go live in my PayPal account, it was working and now it stopped working suddenly, can you please help me, it's Codeigniter website.
The problem is that it works in sandbox and I don't understand what is going on, I already set off Block non-encrypted website payment,
Thanks.
UPDATE:
You can test it:
https://www.paypal.com/cgi-bin/webscr?business=KPEG34H4RENJA&cmd=_cart&production=1&custom=&invoice=57089&upload=1¤cy_code=CAD&disp_tot=Y&cpp_cart_border_color=&no_note=1&return=https://www.lesjeuxdiamant.com&cancel_return=https://www.lesjeuxdiamant.com/panier¬ify_url=https://www.lesjeuxdiamant.com/panier/ipn&rm=2&lc=EN&shipping=&shipping2=&handling=&tax=&discount_amount_cart=&discount_rate_cart=&first_name=&last_name=&address1=&address2=&city=&state=&zip=&email=&night_phone_a=&night_phone_b=&night_phone_c=&item_name_1=jeuxvideo&amount_1=54.95&quantity_1=1&item_name_2=expedition&amount_2=0&quantity_2=1&item_name_3=TPS-TVQ&amount_3=8.23&quantity_3=1
if you switch this to sandbox it works:
https://sandbox.paypal.com/cgi-bin/webscr?business=9H3GUGRW23D3W&cmd=_cart&production=1&custom=&invoice=57089&upload=1¤cy_code=CAD&disp_tot=Y&cpp_cart_border_color=&no_note=1&return=https://www.lesjeuxdiamant.com&cancel_return=https://www.lesjeuxdiamant.com/panier¬ify_url=https://www.lesjeuxdiamant.com/panier/ipn&rm=2&lc=EN&shipping=&shipping2=&handling=&tax=&discount_amount_cart=&discount_rate_cart=&first_name=&last_name=&address1=&address2=&city=&state=&zip=&email=&night_phone_a=&night_phone_b=&night_phone_c=&item_name_1=jeuxvideo&amount_1=54.95&quantity_1=1&item_name_2=expedition&amount_2=0&quantity_2=1&item_name_3=TPS-TVQ&amount_3=8.23&quantity_3=1
It appears the account in the live environment is restricted, and cannot accept any PayPal payments.
Tell the the account owner to log into https://www.paypal.com to review the restriction and the business steps needed to resolve it.
If necessary, they can reach out to PayPal's support via https://www.paypal.com/smarthelp/contact-us to resolve the issue.
Fix Paypal Things don't appear to be working at the moment. Please try again later
Click image to fix bug --->
https://i.stack.imgur.com/iVS3q.png
OR
Add this code to form <input type="hidden" name="upload" value="1">
#HKimhab
I had a similar problem. That paypal page wasn't giving me any help as to what the problem might be. I found that the value of my form's hidden field sometimes exceeded the 200-character limit imposed by PayPal's policy.
We have magento CE 1.9 which we are trying to get some analytics on and I have seen many posts on the internet about setting up paypal with magento. I believe we have everything setup correctly for paypal standard checkout except for the return URL.
Some of the sources I found on the internet say to use
http://www.storename.com/checkout/onepage/success/
Where others say to use
http://www.storename.com/paypal/standard/success/
which one is actually correct?
An order finally reached analytics via:
http://www.storename.com/paypal/standard/success/
Other orders were completed but did not reach alalytics, I can only speculate on the reason for this. One possible cause I have read about, is premature closing of the browser window. This could prevent our sites success page from loading the analytics javascript.
I recently started to have the following error when trying to proceed a paypal payment on my magento store:
Cannot retrieve payment method instance.
I have read about it on various websites, and it seems to happened when you create/modify a payment method. However, in my case, it really started happening with no reason at all, as I have not made any changes to my website recently.
I have tried to manually force paypal_standard as method in the sales_flat_order_payment and sales_flat_quote_payment tables, but it did not work.
Paypal express checkout doesn't work anymore neither.
Does anyone have an idea of how to reinstall/reset or something the paypal payment module?
Or to further debug the issue?
(I am not a programmer so I would need quite detailed information)
For anyone having this issue, I have solved it by deleting the /app/code/core folder and replacing it with a vanilla magento one. Most likely the paypal payement system module got corrupted for no reason and replacing it with vanilla version solved the problem.
I am setting up a megento shop but while testing I get the following error when paying by card using ebizmarts Sage Pay module:
Payment has failed, please reload checkout page and try again. Your card has not been charged.
Does anyone know the solution to this problem?
Regards,
Daniel
There is a support forum for the free plugin here http://ebizmarts.com/forums and if you are using the PRO module, you can just use the contact form here http://ebizmarts.com/contact-us
Also, the problem you mention is described on the Wiki here http://wiki.ebizmarts.com/sage-pay-common-problems
FIXED
From what I can see and for whatever reason, Magento was loading the "info.phtml" file from the theme/default/checkout/onepage/review folder, rather than the one in the sagepaysuite folder.
I copied in the above code to the relevant position to the default info.html file, and it's working now.
The staging server was loading the sagepaysuite/checkout/review/info.phtml file correctly, hence it was working.
Every order placed from the frontend of our Magento store logs a "Wrong order ID" exception even though all orders seem to be going through with no problems. Orders also seem to take a lot longer to complete than they should. If I place an order from the admin, it's virtually instantaneous and does not log any errors. What's different between frontend and backend orders? Why are these errors being logged every time even though no error really occurred? Any suggestions?
Thanks!
Per the change log for Magento 1.7.0.0 (which came out in April), they think they've fixed the problem:
Fixed: “Wrong order ID” exception in PayPal Express module under heavy load
Can anyone confirm that upgrading to Magento 1.7 does indeed fix the problem? Every time I've looked at it, it does seem to be a PayPal Express issue (our payments normally go through PayPal Pro and that doesn't seem to have errors).
So... we finally found a permanent solution to this for Magento 1.6. And we can confirm that this has been fixed in Magento 1.7.
Full explanation and code here:
Magento Paypal IPN Wrong Order ID – SOLVED
We had this same exception in Magento 1.6.1 showing up in exception.log. The problem for us was that the Order Number and Invoice Numbers were out of sync.
For some reason, when using PayPal Express, it causes the order to not be fully processed and logs the exception: “Wrong Order ID”. The worst part was that it was erratic… sometimes it would fail, other times it was fine.
THE SOLUTION:
http://www.magentocommerce.com/magento-connect/fooman-sameorderinvoicenumber.html
Thanks for a great extension from Fooman! Just install their “SameOrderInvoiceNumber” extension, remember to enable it in “Configuration | Sales | Order Numbers” and you’re all set!
Solved the problem for us on Magento 1.6.1… don’t mess with core code!
Ok... So my other solution didn't soIve the problem for us either. Spoke too soon. Although this helped it didn't get rid of the error completely.
We did however find a definite clear link between server load and this IPN error. Detailed analysis here:
http://www.bigdune.net/geek-blog/magento/60-magento-paypal-ipn-wrong-order-id.html
Sorry, but it doesn't seem like there's a quick "code fix" for this one.. not that we could find yet.