I seem to have everything setup correctly, however my transactions are not being placed and I get an error saying “There was an error processing your order, please contact us or try again later", when I hit the “PLACE ORDER” button.
I had double checked that the merchant email. partner id, user, vendor and the password are provided correctly and the test mode is enabled.
My payflow pro account is not activated, so its a test account. Is that the reason for my problem ? Any help would be greatly appreciated.
This is a normal process then, I would contact PayPal as they are declining the payment, due to a rule on their side, over max limit, etc.
Other option would be is that you could change the request sent to increase the verbosity of the error but it would only shed further light and would help in troubleshooting.
The request string needs to appended with Verbosity=Medium to increase the output. I believe this can be done via class Mage_Paypal_Model_Payflowpro:_buildBasicRequest() and modify the setVerbosity()
Refer to PayPal Documentation for information.
Related
I really need your help guys. Since two hours I'm facing with a very strange problem related to Paypal Sandbox. I read lot of answers here on stack overflow but none of them helps me.
I'll try the explain my problem: when I create a new sandbox account (respecting all rules like password strength, load balance etc.) I receive the "success" message, the account is created and visible in the list, but when I open it using "Profile" button I receive this error message (and is really a problem because I need to get the username, password and signature to work in sandbox mode):
Account Details
Your request is still processing, please wait...
No difference between "Buyer" or "Seller" account, it always fail.
I've tried in many ways (using notes, changing email address, using custom numbers into email) but nothing is work for me.
Someone can suggest me what can I do?
Thank you very much.
I think I've found a temporary solution to works with PayPal sandbox.
Instead of create an account using "Create Account" button you have to register a new account using sandbox website.
In details:
Go To: https://sandbox.paypal.com
Register a Business Account
Go To: https://developer.paypal.com/developer/accounts/ and click con "Click Here". This link is placed in the Second paragraph of the page:
Want to link existing Sandbox Account with your developer account? Click Here and provide credentials of your sandbox account
You will be redirect to sandbox paypal web site, if you don't do anything it will recognize your previous register account (anyway, if not, you have to login with the new created account), procede with linking process and after you will have, in the list of accounts, a new one with "Profile" button ready to show you informations necessary to works.
I don't understand way paypal release an important tool like this with a lot of bugs. No response received from no one.
BugPal your are luky because we needs you but please, improve your development process! :#
Looks like a general problem on Paypal side. We see same issues with two of our accounts. It was working last friday.
been trying to wrap my head around an issue I have with the IPN tester, not 100% sure if its my hosting company's problem or Paypal Developer 'beta' to be honest but my IPN's have worked fine on a few sites I have for atleast a year and now it doesn't on any of them. I've not changed anything and now im getting
IPN Delivery Failed:I/O error: www.mywebsitesname.co.uk; nested exception is java.net.UnknownHostException: www.mywebsitesname.co.uk
and none of my NotifyUrl.ashx handlers are working.
any ideas what this actually means in english? any more info. from me required to help you diagnose my issue?
#
AS AN UPDATE (27-08-2013), I thought I would try out the original C# SDK sample code from Paypal that I used to set up my IPN's with about a year or three ago (ie. it worked great with the IPN simulator). I have put it onto two different hosting companies servers to check its not an issue with a particular hosting server and my results using the IPN Simulator show "error 500: internal server error" for one and "IPN Delivery Failed:I/O error: www.ang##########.co.uk; nested exception is java.net.UnknownHostException: www.ang############.co.uk".
In short, I have the same identical sample file from Paypal (that used to work) in the root of each hosting companies servers and im using the same IPN simulator settings, with the exception of the IPN handler URL has the webaddress of the server followed by '/Handler.ashx' (which is the handler file) but i'm getting different errors.
Also to make this a bit more interesting, today I correctly received an IPN from Paypal to one of the same hosting server webaddress, with a 'transaction_subject : PayPal money request from xxxxxxxx' which was received and processed by my existing IPN handler (not the sample one from Paypal) and returned the correct info. to receive 'IPN Response: VERIFIED DateTime: 27-08-2013 19:05' so this got through and worked fine.
So in conclusion, I wonder if Paypal have either changed something and not informed the community or have an issue with their IPN simulator / CART IPN. If anyone can help or if a Paypal support engineer would like to work with me to try out some code, etc, please get back to me as I will keep trying to solve this but to be honest I see not what else I can do from my end as I've seen working IPN and a non working IPN simulator.
As extra info. here is an IPN Message as from my sandbox seller test account, that can't get through to my IPN handler on one of the same hosting servers (returns error 500) yet this used to get through and nothing has changed.
'mc_gross=2.75&protection_eligibility=Ineligible&address_status=confirmed&item_number1=BabyGrow2&payer_id=KHJGBQZNAFB7L&tax=0.00&address_street=1 Main St&payment_date=14:34:07 Aug 27, 2013 PDT&payment_status=Pending&charset=windows-1252&address_zip=95131&mc_shipping=0.00&mc_handling=0.00&first_name=Test&mc_fee=0.28&address_country_code=US&address_name=Test Buyer¬ify_version=3.7&custom=1csi4t45gy4gkz45r5r4t0ey&payer_status=verified&business=wow####gmail.com&address_country=United States&num_cart_items=1&mc_handling1=0.00&address_city=San Jose&verify_sign=AFcWxV21C7fd0v3bYYYRCpSSRl31A1fBAmiE5lcDRsQKQNaqoyQI7ucQ&payer_email=wow#######gmail.com&mc_shipping1=0.00&tax1=0.00&txn_id=8SG98957G0030294Y&payment_type=instant&last_name=Buyer&address_state=CA&item_name1=Baby Grow Age 0 - 1&receiver_email=wow#########gmail.com&payment_fee=&quantity1=1&receiver_id=8QRMB3QFHCL56&pending_reason=paymentreview&txn_type=cart&mc_gross_1=2.75&mc_currency=GBP&residence_country=US&test_ipn=1&transaction_subject=1csi4t45gy4gkz45r5r4t0ey&payment_gross=&ipn_track_id=7b4507c8c4313'
Still hoping we can resolve this soon.
Many Thanks.
Trev.
Asp.net / C# / HTML / CSS3
I am facing the same problem as seen in this http://forge.prestashop.com/browse/PNM-1165
It says this following message after I click on 'pay with paypal'
Error occurred:
Please try to contact the merchant:
PayPal response:
->
I don't know what to do T^T
Im using prestashop 1.5.4 and paypal module 3.5
There is one reply suggestion from Francois Gaillard added a comment - 29/Mar/13 9:29 AM
He said that
This issue occurs when your server IP has been blocked by the PayPal's API. If you are running share hosting environment the server can be banned blacklisted by PayPal.
Please, try to contact PayPal support they should be able to help you.
Let us know when you have more details please.
Thank you,
Kind regards.
That answer is incorrect in as much that we do not block IP addresses to our API endpoints without making the merchant aware.
It is correct, from our experience, that the above error occurs in PrestaShop when your server is unable to establish a successful HTTPS connection with our API endpoint.
I suggest you take a look at General troubleshooting - API timeout and run the tests provided in it.
Pay special attention to the AT&T block we mention in there, as we've seen a large number of API callers getting blocked at that level.
Unfortunately that block is beyond our control - but we've heard good reports of merchants getting in touch with AT&T and getting that block lifted (if confirmed to be blocked there).
I'm using the callback API to prevent someone selecting a non-UK shipping address. I've supplied a callback url, I've set CALLBACKVERSION to 61.0.
When I go into the sandbox and choose an address I know the callback page is being called as I've added code to email me the values submitted to it and the value returned to PayPal. For anything with a SHIPTOCOUNTRY that isn't GB the response is
METHOD=CallbackResponse&NO_SHIPPING_OPTION_DETAILS=1
I've also tried setting a fuller response in case it doesn't like some required field to be missing
METHOD=CallbackResponse&CURRENCYCODE=GBP&L_SHIPPINGOPTIONNAME0=Standard&L_SHIPPINGALABEL0=Standard&L_SHIPPINGAMOUNT0=2.95&L_SHIPPINGOPTIONISDEFAULT0=true&L_SHIPPINGOPTIONNAME1=Express&L_SHIPPINGALABEL1=Express&L_SHIPPINGAMOUNT1=5.95&L_SHIPPINGOPTIONISDEFAULT1=false&NO_SHIPPING_OPTION_DETAILS=1
But it's still allowing non-UK addresses and just using the shipping options set during the initial set up request.
Any suggestions on where I'm going wrong?
After opening a ticket as suggested by PayPal_Patrick the problem was that I was adding the callbackversion in the wrong place. The full response to reject a shipping address on callback is:
METHOD=CallbackResponse&NO_SHIPPING_OPTION_DETAILS=1&CALLBACKVERSION=61
There are different transaction ID's for Buyer and Seller accounts.
I think this might be an issue caused by the country associated with the buyer account being used. I'm going to reach out to the product team for Express Checkout and see if it is intended functionality or not - I don't believe it would be.
If you want to stay updated on the issue I would recommend creating a ticket to PayPal.com/mts, give me the ticket number, I'll grab it and keep you involved.
After spending several hours trying to get django-paypal (originally dcramer's fork) to get a 200 OK response from PayPal IPN, I pinpointed the error to PayPal adding an empty, spurious &cmd= argument when using the IPN Simulator. If I leave the &cmd= in, I get a 400 Bad Request response when I try to postback; if I take it out I get a 200 OK but, of course, the postback is invalid because it's not what PayPal sent my server.
Of course, I'd be absolutely happy to do away with the IPN Simulator entirely and simply use Sandbox accounts, but those are broken too: the ones I create through the developer interface can't login (login failed errors); the ones I created through the "regular" interface on the sandbox site don't send any IPN whatsoever no matter what.
So, actually there's two questions here:
is there a way to work around the IPN Simulator &cmd= bug?
is there a way to make the sandbox accounts work?
A reply to either one would make me very very happy.
Many of the issues you've experienced are now cleared up. The IPN issue and some developer/sandbox log in issues have been cleared up as of Monday evening. If you are still experiencing any issues please let me know and I'll be more than willing to look into this further.