I am using ExpressCheckout in several shops. Since a couple of weeks there is a problem with the landingpage. Instead of a landingpage with guest payment options or even price-information a stupid login page is shown.
Please take look at the image I made.
It worked before and with my sandbox I still get the old Landingpage. Because there are no price-information many customers cancel the checkout process now.
You can't avoid the new version of the landing page, but if you have all of the parameters set in the request the way you say then you should see a button that says "Pay with Debit or Credit Card" instead of "Create an Account".
Here's a screenshot of what I get. You'll notice the pricing has been moved into a drop-down.
Related
I've been using PayPal Website Payments Standard for many years - I use both IPN and PDT. Recently I discovered that although IPN is still working fine, the customer is no longer returned to my website at the end of a purchase, so the PDT is not called, and the customer never makes it back to my website (this is new - it has been working fine for years).
I do have Auto Return turned on in my PayPal settings. The page it's supposed to go to exists and is working fine. That landing page is never hit in the logs.
This is broken on the live PayPal site and in the PayPal Sandbox. The page that I land on says "Your payment was completed. To continue shopping, please return to the merchant." There is no "Return to Merchant" button. The URL for this page is https://www.sandbox.paypal.com/webapps/hermes?flow=1-P&ulReturn=true&token=2GX255130M045604B&mfid=1540506852194_f375a853a7234&useraction=commit&country.x=US&locale.x=en_US&country.x=US&locale.x=en_US#/checkout/genericError?code=PAYMENT_ALREADY_DONE. This page used to automatically redirect back to my website.
On a related note (not sure if it's the same problem) the "Continue Shopping" button on the PayPal Cart page doesn't work anymore either. I am sending the URL for the page in a hidden field of the form I send to PayPal for my Add to Cart button as shopping_url, but when I click "Continue Shopping" it appears to be taking me Back (like a browser back) to the page that submitted the form rather than going to the page I specified in shopping_url. Again, this has worked for years, but now is no longer working.
Any help will be much appreciated!
[not an answer, but I can't post comments]
This broke a few months ago for us (Paypal button "return" parameter doesn't seem to work). In the new checkout flow, Paypal ignores the "return" value passed in the button/form, it redirects the customer to the URL configured in website settings (https://www.paypal.com/businessmanage/preferences/website).
I'm not sure if Paypal developers read this forum for bug reports or not, but this definitely looks like a regression.
I have integrated Express Checkout with my application it works fine but sometimes paypal payment pages behaves very oddly. When user is directed to payment page, the page it shows is not same all the time. sometimes it shows saying "Login or Checkout as a Guest" and sometimes user see a page saying "Login as paypal or Create an account"
I have attached the image url Please see the following links.
First Layout
http://oi60.tinypic.com/149rpcn.jpg
http://oi60.tinypic.com/2r43ms2.jpg
Second Layout
http://oi58.tinypic.com/vxcl04.jpg
http://oi62.tinypic.com/v3j3hc.jpg
First layout makes sense. but second layout creating confusion when it says "create an account"? is that means creating paypal account or what? when i click on the option it simply shows me credit card details to enter. i dont know if that is related to the payment or asking to create new paypal account?
PayPal has been split testing the old EC pages with the new ones that you're seeing sometimes. In order to work with both sets of pages nicely, you'll need to make sure to add an additional parameter into your SetExpressCheckout request.
It looks like you're already using the following (and if you're not, you need to add them)
SOLUTIONTYPE=Sole
LANDINGPAGE=Billing
You need to also include the following to work well with the new pages.
USERSELECTEDFUNDINGSOURCE=CreditCard
We're developing an application that uses Paypal Express Checkout, and we're finding that we get two different landing pages. We're actually finding a problem that seems superficially similar to Can you force PayPal Payments Standard API to show credit card fields first?, but with a few differences:
Everything is fine with the sandbox, and we get exactly the appearance (credit card first) we want.
On the live site, about 50% of the time we get exactly the appearance (credit card first) we want.
Sometimes, we get a more "mobile-like" landing page, with the credit card stuff totally hidden in a "Check out as a guest" button, as shown.
This feels like a failing A/B test to me. We're sending exactly the variables in the question linked above, and as I said, all works fine with the older landing pages. I know there are also cookie issues, but in this case, we're seeing it even when Paypal is not able to identify an account and when cookies are cleared.
Does anybody know if there is anything we can do to work around this?
I can add code if needed, but the problem appears to be more data than logic.
I had the same question after I started to see users coming in from the 'new style' page.
I found the answer here:
Paypal express "order summary" page
I added the "force_sa=true" parameter to my Paypal URL:
https://www.paypal.com/cgi-bin/webscr?cmd=_express-checkout&force_sa=true&token=…
The new page is definitely weighted to appear more often on mobile devices. Without the parameter I get the new style page on a iPad after about 5 refreshes, with the parameter I can refresh as much as I like and never see the new page.
Obviously, PayPal will roll out the new page to everyone in the end, but this technique allows us a stop gap while we get ready for it ;-)
The screen pictured is PayPal's new checkout. It is only partially deployed at this point, you can think of it as A/B testing.
Regarding whether the customer sees "credit cards first", this mostly depends on whether they have a PayPal email stored in their browser cookie. If they do, the top "Log in to PayPal" section will be expanded, the email filled out, and they just need to type in their password and do about 3 clicks to complete the checkout..
If they do not have a PayPal email stored in their cookies, the bottom Create an Account or Pay as Guest section will be expanded. (If you want guest checkout, pass SOLUTIONTYPE=Sole in your initial SetExpressCheckout request).
The customer can always switch between the two expanded sections, it's just a "smart default" of sorts.
Try doing all your "credit cards first" testing in an incognito / private browsing window.
Had a nice little custom button with a few parameters I was POSTing to PayPal (and getting POSTed back via IPN) a few years ago working fine. Payments were disabled for several years, but now my client wants to resume subscriptions with their new campaign.
I switched back to the sandbox hostname/merchant accounts, did a sandbox transaction with a test Visa card, and all was well.
Switched it to the live hostname/merchant account, went to do another test with a real Visa, but noticed that not only has the real PayPal site been completely rebranded/redesigned, they now seem to be forcing you to create a PayPal account: on the sandbox, there's a blurb with a link that says "continue" which takes you right to the credit card/billing information (this is identical to what the live PayPal site used to look like a few years ago).
NOTE: The merchant account has changed; I'm not sure if that matters or not and/or if there's any settings in there I need to change.
Question: is this the way it is now with PayPal? I can't seem to find any official information that says yes/no. Besides the Express, is there any other IPN method that'll work here or is this a policy thing at PayPal? I'd hate to rewrite my working/tested code, but this isn't going to fly with my client.
Yahel's answer is incorrect: I called PayPal, and they explained that the following conditions must be met in order to accept non-PayPal payments:
The business email address must be confirmed. You can check by going to Profile > Email.
PayPal Account Optional must be checked:
Go to www.paypal.com.au and log in to your Business account.
Click 'Profile icon' near the top right of the page (next to "Log out" button)
Click "Profile & settings"
Click ‘My selling tools.’
Click ‘Update' beside 'Website preferences.’
Select 'On' under 'PayPal Account Optional' near the bottom of the page.
Click 'Save.'
Yes paypal has been forcing users to create an account for a long time now. Before that you could use a credit card up to 10 times and then it would force you to create an account anyway.
The reason you are seeing the old branding in your sandbox is probably because it is you old sandbox on an old paypal server.
Last I tried there was no way around this new policy.
But djechelon is right, they have an excellent customer service, give them a call.
PayPal does force people to create accounts, even when they want to just make a single payment. I was puzzled by this situation too: I was choosing the option to pay without a PayPal account, but still was forced to provide all the private details enough for PayPal to create an account for me against my wishes. Very sneaky of PayPal! Then I found this page and that explained a lot.
This is the message I received in my PayPal Account:
PayPal Account Optional
When this feature is turned on, your customers will go through an optimized checkout experience. This feature is available for Buy Now, Donations, and Shopping Cart buttons, but not for Subscription buttons.
So you cannot provide a regular "Subscribe" experience to non-PayPal customers. I believe you must pay the $19.99 a month "Enhanced Subscription" for this.
PayPal Has a Purchasing Limit of $3,000 for "Guests".
I ran into this issue as well and #gravyface was bang on with setting your account preferences. However, my customers were still having issues paying without a PayPal account.
I called PayPal and it turns out they have a $3,000 (cumulative) purchasing limit for "guests". My customer's invoice was for $7,000 so even though my preferences were set to make the PayPal account optional, it still would not go through.
Hope that helps others.
JP
As I've been integrating with PayPal, I've noticed that their sandbox UI is very different from their real UI.
When I set my button to post to sandbox.paypal.com, I get something like this:
But when I post to paypal.com from a browser that has never visited PayPal before, I get this:
Is there any way to setup the sandbox so its interface will be closer to the "real" PayPal's interface?
I've not seen it, but perhaps that's a New UI? The quote below is about all I've been able to find out about it though.
The Adaptive Payments consumer
experience will be upgraded to the new
PayPal payment flow design being
rolled out across all PayPal products.
The new UI will show the merchant's
business name instead of their email
address and will have a split slider
showing the payment breakdown on the
left and the login/approval on the
right.
David seems to be right — they are rolling out a new UI on the real site, but I guess the sandbox hasn't gotten it yet.
Also, clearing all my *sandbox.paypal.com cookies gives me a "pay with credit card" screen instead of the "log into PayPal" screen.
There is problem with new paypal interface, also mentioned in developer community forum on their website. many of the users are having problem since 1 month, and paypal is still working on it to resolve the issue.
Regards,
Mazhar Karimi