从 WPS 切换到 Express Checkout？
我目前有一个网站付款标准结账流程，用于购买年度订阅和订阅。独立的虚拟产品，其最简单的形式；
- 收集有关客户和客户的一些基本详细信息在我的网站上的数据库中记录新的购买
- 使用准备 Web 表单的技巧，该表单会在客户端自动提交到 PayPal，并使用
custom字段来跟踪和记录。使用 IPN 验证购买
据我所知，通过 Express，我可以
- 剪掉表格技术和表格。收紧我的应用程序，启动服务器端请求然后将用户直接发送到 PayPal
- 在客户返回时立即处理付款（无需等待可能的 IPN 延迟 - 尽管我知道我可以通过自动返回 PDT 来应对这一点）
- 现场管理订阅（不是必需的，但确认为好处）
但是，我知道涉及的额外工作，特别是定期付款。
您认为为了收益而这样做值得吗？或者考虑到要求，我正在做的事情是否可以接受*？
*我一直担心在标准 PayPal 网络表单中公开交易，这就是我喜欢 Express 想法的原因，但我正在严格验证 IPN 调用；我有真正的理由担心吗？
I currently have a Website Payments Standard checkout process for purchasing annual subscriptions & standalone virtual products, which in its simplest form;
- Collects a few basic details about the customer & logs a new purchase in a database on my site
- Uses the trick of preparing a webform that auto-submits to PayPal on the client-side, using the
customfield to track & verify the purchase with IPN
As I understand, with Express I could
- Cut out the form technique & tighten my application, initiating the request server-side & then send the user straight to PayPal
- Process the payment instantly when the customer is returned (no waiting on possible IPN delays - though I know I can counter for this with auto-return PDT)
- Manage subscriptions on-site (not required, but acknowledged as a benefit)
However, I am aware of the additional work involved, particularly with recurring payments.
Would you argue it's worth it for the gains? Or is what I'm doing acceptable*, given the requirements?
*I've always been concerned about exposing the transaction in a standard PayPal webform, which is why I like the idea of Express, but I'm rigorously validating IPN calls; do I have any genuine reason to worry?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
是的！一定要，加油。
也许我有偏见，但我喜欢快速结账而不是网站支付标准。
除了能够通过 ManageRecurringPaymentsProfileStatus 控制定期付款配置文件之外，您还可以控制 Express Checkout PayPal 登陆页面的登陆页面（“计费”或“登录”）。
您可以使用 CreateRecurringPaymentsProfile 和/或 DoExpressCheckoutPayment API 响应（如果您收取初始金额）来检查 PAYMENTSTATUS。
另外，如果您想升级到 Website Payments Pro 直接定期付款（通过您自己网站的信用卡表单设置定期付款，无需前往 PayPal 网站），您只需将所需的附加参数添加到相同的 CreateRecurringPaymentsProfile API 响应。
最后，如果您决定开始使用 PayPal 数字商品进行快速结帐（包括定期付款），只需在 SetExpressCheckout 中更改一些参数，然后加载 dg.js 文件即可。
使用 Express Checkout 定期付款的唯一缺点是没有对应的增强型定期付款/高级服务（允许您在美国、英国、加拿大和澳大利亚接受基于客人的定期付款）。唯一的替代方案是 Website Payments Pro Direct Recurring Payments，这在产品提供方面略有进步。
Yes! Definitely, go for it.
Perhaps I'm biased, but I love Express Checkout as opposed to Website Payments Standard.
In addition to being able to control the recurring payment profiles via ManageRecurringPaymentsProfileStatus, you can also control the LANDINGPAGE for the Express Checkout PayPal landing page ('Billing' or 'Login').
You can use the CreateRecurringPaymentsProfile and/or DoExpressCheckoutPayment API response (in case you charge an initial amount) to check for the PAYMENTSTATUS.
Plus, if you ever want to upgrade to Website Payments Pro Direct Recurring Payments (setting up a recurring payment via your own site's credit card form, without leaving to go to the PayPal website), you can simply add in the required additional parameters to the same CreateRecurringPaymentsProfile API response.
Lastly, if you ever decide to start using PayPal Digital Goods for Express Checkout including Recurring Payments, all it takes is a few parameter changes in SetExpressCheckout, and for you to load the dg.js file.
The only downside of using Express Checkout Recurring Payments is that there is no equivalent for Enhanced Recurring Payments / Premium Services (allowing you to accept guest-based recurring payments in the US, UK, CA and AU). The only alternative for this would be Website Payments Pro Direct Recurring Payments, which is a slight step up in terms of product offering.