选择正确的 Paypal 系统来处理注册和订阅
我们在网站上收集的付款用于在线订阅和会议注册。在这两种情况下，我们都希望自己收集除付款信息之外的所有信息，并且最好将其中一些信息传递给 PayPal（这样用户就不必填写姓名、地址等信息）。两次）。
我知道有一些解决方案，其中信息由服务器本身收集，然后通过网络服务调用重定向到 PayPal，但不幸的是，这不是一个选择。 由于网络政策，收集的所有安全支付信息都必须在服务器外进行。
此外，并非每个表单都需要使用 PayPal 进行处理。有些人将通过支票等方式付款，因此根本不应该将他们发送到付款页面。我看过的大多数解决方案都有一个“Pay with Paypal”按钮，因此我认为需要填写表单才能访问 PayPal 网站，但理想情况下我们希望通过 302 重定向到达那里。这有可能吗？ （我知道我们可以做一些类似由 JavaScript 自动提交的表单之类的事情，但我不想走这条路）。
无论我们实施哪个系统，都需要处理经常性（定期）付款。
The payments we gather on our website are for online subscriptions and registrations for conferences. In both cases, we want to gather absolutely all information other than the payment information ourselves, and ideally pass some of it on to PayPal (so users don't have to fill in name, address, etc. twice).
I know there are solutions where the information is gathered by the server itself and then redirected to PayPal via a web services call but that's not an option, unfortunately. All secure payment information gathered has to happen off-server due to network policy.
In addition, not every form will need to be processed using PayPal. Some people will be paying via check, etc. so they shouldn't be sent to a payment page at all. Most solutions I've looked at have a "Pay with Paypal" button, so I assume a form post is necessary to go to the PayPal site, but ideally we'd want to get there via a 302 redirect. Is that at all possible? (I'm aware we could do something like a form that was auto-submitted by JavaScript but I'd prefer to not go down that route).
Whichever system we implemented would need to handle recurring (periodic) payments also.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Paypal 有一个叫做 Payflow Pro 的东西。几年前他们从 VeriSign 购买了它。
您可以使用它与 paypal api 进行完全集成。这样用户就可以在您的网站上输入他们的付款详细信息，并且您的后端代码会将交易提交到 PayPal 的服务器。然后 Paypal 会返回给您一个交易 ID。保留交易 ID，将其他所有内容（例如卡号）扔到窗外。
我们有几个使用 Payflow Pro 的客户。这是非常好的并且易于使用的api。
Paypal has something called Payflow Pro. They bought it from VeriSign a few years ago.
You can use it to do a full integration with the paypal api. So that the user enters their payment details on your site, and your backend code submits the transaction to paypal's servers. Paypal will then give you a transaction id back. Keep the transaction ID, chuck everything else (like the card number) out the window.
We have several clients that use Payflow Pro. It's very good and easy to use api.
我不完全确定我理解你问题的全部范围，但我想我理解。我已经对这些配置进行了编码。注册（虽然我还没有与 PayPal 交互……而是与 iTransact 和 Plug'NPay 交互），并且在我的应用程序中，我必须通读所使用系统的 API 文档（在本例中为 PayPal）。然后我登录到支付网关，通常他们有一个 html 表单生成器。当然，这一切都会返回一个 html 表单，其中的字段标记为适合其 API（因此帐单名称和地址会从您的系统转移到 PayPal，并且用户无需重新输入其信息），显示您需要什么隐藏字段（如 cutomer_id 等）和表单 POST 路径。
然后我要做的就是让用户注册，在另一个页面上预览他们的订单详细信息（您可以选择将他们的信息放入数据库或等到他们的信用卡处理完毕后），然后在确认后，他们会转到 PayPal，使用信用卡或支票付款（选项始终存在），当他们点击确认时，您放入隐藏变量中的回传 URL 会带您进入自定义感谢页面（并希望处理脚本以捕获成功的交易），该页面可以托管在您服务器上的任何位置。
这非常简单，只是一开始当您尝试找出特定于支付网关 API 的新表单变量时有点费力。
希望这有帮助！
I'm not entirely sure I understand the full scope of your question, but I think I do. I've coded a number these conf. registrations (though I have not interfaced with PayPal...rather iTransact and Plug'NPay) and in my applications, I had to read through the API documentation for the system being used (PayPal in this case). Then I logged into the payment gateway and usually they have an html form generator. All this does, of course, is returns an html form with the fields labeled appropriate to their API (so the billing name and address carry over from your system to PayPal's and the user doesn't have to re-enter their information), shows you what hidden fields you'll need(like cutomer_id, etc) and the form POST path.
Then what I do is I have the user register, preview their order details on another page (where you can choose to drop their info into a DB or wait until AFTER their credit card is processed) and then upon confirmation, they go to PayPal, pay with either credit card OR check (the options always exist) and when they hit confirm, the passback URL you put into a hidden var somewhere, takes you to a custom Thank You page (and hopefully processing script to capture successful transactions) which can be hosted anywhere on your servers.
It's pretty simple, just a bit labor intensive at first as you try and figure out the new form variables specific to a payment gateway API.
Hope this helped!