问题描述
过去，通过将LANDINGPAGE参数(以及SOLUTIONTYPE设置为"Sole")作为SetExpressCheckout请求的一部分，可以指定用户将经历的Express Checkout流(登录或访客).如果将其设置为计费"，则结帐体验将默认为访客结帐，而如果将其设置为登录"，则将要求用户使用其PayPal帐户进行身份验证.
In the past, it was possible to specify which Express Checkout flow (login or guest) a user would experience by passing the LANDINGPAGE parameter (along with SOLUTIONTYPE set to "Sole") as part of the SetExpressCheckout request. If set to "Billing", the checkout experience would default to guest checkout, whereas if set to "Login", the user would be asked to authenticate with their PayPal account.
PayPal似乎正在尝试使用新的Express Checkout UI，该UI不支持LANDINGPAGE参数.即使通过了Billing，登录流程也会在界面中分派.
PayPal appears to be experimenting with a new Express Checkout UI, which does not honor the LANDINGPAGE parameter; even if Billing is passed, the login flow is dispatched in the interface.
是否有一种方法可以在重定向时在新的Express Checkout UI中强制显示来宾结帐?
Is there a way to force display guest checkout in the new Express Checkout UI on redirect?
推荐答案
我们正在解决此问题.此后，LANDINGPAGE将继续为您工作.
We're fixing that as we speak. LANDINGPAGE will continue to work for you after this.
这篇关于PayPal ExpressCheckout LANDINGPAGE参数已弃用?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！