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
Related
I use IPN in my website. The request is sent to https://www.paypal.com/cgi-bin/webscr . It works fine before.
Few weeks ago I notice that even the user choose to pay without paypal account, they are forced to create an account. As it is showed in the first picture. At the bottom of that page, it asks the user to create an account. They can not skip it.
But if I change the country to China (in the first picture, I change the country to China), then the page layout is changed to the old version. As it is show in the second picture. In this page, the user do not need to create an account to make the payment.
My question is how can I go to the old page layout directly?
I called paypal, this is their issue and they said they are aware of it, no ETA. They said they have not emailed clients affected by this at all. I ran into the same issue with my clients, this blows...
-Quentin
I have the following variables defined in my SetExpressCheckout API code:
SOLUTIONTYPE=Sole
LANDINGPAGE=Billing
USERSELECTEDFUNDINGSOURCE=CreditCard
Previously, this worked so that the shopper is first shown a form where he can enter his credit card details, followed by an option to log into his existing PayPal account. Since about a week however, everyone gets this screen:
Yes, I tested it from several machines, several countries, with cookies cleared, etc. And the sandbox is giving me the same issue.
Unfortunately, not all of our users are tech savvy and we've heard from several of them that they found no way to pay with credit card, even though the PayPal button to pay with a card is there - just not very visible because it's grey.
Is anyone experiencing the same thing lately? Have you found a way around it to display the credit card form first?
Unfortunately, there's nothing you can do about this.
PayPal is split testing those checkout pages. I've seen 3 different versions pop up lately. The old/original one where the full form is displayed by default, this new page design/style with the button only, and I've also seen another new page design that does display the full form as well by default.
They are letting their split tests run their course, though, and in theory will choose the one that performs the best over all.
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.
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.
I need to implement Paypal express checkout and client needs the Paypal checkout to have their own theme (at least the header). Paypal facilitates that by providing an option to upload banner image and a logo. That works fine for me, but I have a different scenario here.
Paypal checkout has 3 (abstract) steps, first where Paypal asks for login, second where it asks you to review shipping address and final the payment confirmation page. I need Paypal checkout to have three different banner images for three different steps. The reason I want to do this is because I want to give a feel of navigation to the user, each banner image will have a tab selected for each step. It might sound confusing, look at the screenshot attached and you'll understand. Its a shot from a checkout on Etsy.com
Is this possible at all? If not, how have the guys at Etsy.com done this? Is there any other way to implement tab/navigation like the header in Paypal Checkout? Any suggestions?
Etsy uses a fixed header as well, specifically https://www.etsy.com/images/paypal/paypal-checkout-steps.png
However, the same header is used when you're returned to Etsy's website for order review and order completion.
To answer your question directly; in PayPal itself, you can't set up three different 'headers' for each step in the process.