在结帐步骤中选择PayPal，然后在下一步之前在下一步中查看订单详细信息
我正在寻找文档的指示或其他具有相同情况的网站的指示：
- 步骤A：选择付款 - 用户可以在结帐
- 步骤B中选择PayPal 并可以在与PayPal下订单之前查看订单详细信息。
问题：
- 可以选择不导致PayPal登录的PayPal付款方式的选择？
- 还是一旦签署到PayPal，步骤A必须成为PayPal的标志
- ，PayPal API是否允许用户返回站点允许审查（步骤B）？
- 启动PayPal是否必须以订单的安置结束？即，它无法返回步骤B进行审查，然后完成订单？
I'm looking for direction on documentation or others who have sites with the same scenario:
- step a: Select Payment - The user can selecting Paypal in checkout
- step b: Review Order details - The user has selected paypal in step 2
and can review the order detail before placing the order with PayPal.
Questions:
- Can step a just be a selection of the paypal payment method not leading to paypal sign in?
- Or does step a have to be a sign into paypal
- Once Signed into paypal, does the paypal api allow the user back to the site to allow to review (step b)?
- Does initiating Paypal have to end with the placement of the order? i.e. it can not return to the step b to review , then complete the order?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
“选择”贝宝（Paypal）而不签名无需做任何事情，什么也没做。除了正常的付款选择地点外，还应尽早使用PayPal Checkout/登录快捷方式按钮（理想情况下在“查看购物车”页面上）。这允许付款人迅速登录，而无需输入任何速度的地址信息。 PayPal付款人几乎总是已经在PayPal保存了地址。该过程中的摩擦越少，付款人实际单击并完成结帐的可能性就越大。这可以衡量地增加销售额。
如果您在捕获前需要审核后的审核步骤，则可以在捕获之前（在“ Onapprove”功能）后显示一项。如果您不会立即捕获，则应将PayPal的最后一个操作的按钮文本从默认的“立即付款”更改为“继续”。为此，创建订单时，设置顶级（不在购买单元内）
application_context带有user_action键>继续的对象。这只会更改按钮的文本，在批准匹配之后取决于您的行为（必须匹配）。要在捕获之前更改PayPal订单的详细信息，请使用更新订单详细信息/a> API调用，它是HTTP修补程序操作（不是发布），除了204代码以外，没有任何成功响应。
对于付款人的批准，使用此流量;它具有v2/Checkout/订单捕获响应的必要客户端错误处理（如果可回收的资金失败，重新启动）
"Selecting" PayPal without signing in doesn't do anything, and accomplishes nothing. You should have a PayPal checkout/sign-in shortcut button as early as possible in your flow (ideally on a "view cart" page), in addition to the normal payment selection location. This allows payers to sign in quickly without having to type in any address information, which speeds the process. PayPal payers almost always already have their address saved at PayPal. The less friction there is in the process, the more likely a payer is to actually click through and complete the checkout. This increases sales measurably.
If you need a review step after PayPal before capturing, then you can show one after approval (in the 'onApprove' function) before doing the capture. If you are not going to be capturing immediately, the button text of the last action at PayPal should be changed from the default 'Pay Now' to say 'Continue'. To do so, when creating the order set a top level (not inside purchase units)
application_contextobject with auser_actionkey ofCONTINUE. This only changes the text of the button, it is up to you to make the behavior after approval match (and it must match).To change the details of the PayPal order before capture, use an Update Order Details API call, which is an HTTP patch operation (not post) that gives no success response other than a 204 code.
For payer approval, use this flow; it has the necessary client-side error handling of a v2/checkout/orders capture response (restarting in case of a recoverable funding failure)