简体   繁体   English

使用PayPal与Amazon FPS修改订阅

[英]Modify Subscriptions using PayPal vs Amazon FPS

I have been looking at setting up web applications that rely heavily on the ability for users to frequently and substantially modify subscriptions. 我一直在寻找设置Web应用程序,这些应用程序在很大程度上依赖于用户经常和大幅修改订阅的能力。 I may be using marketplace features as well, and I need a system that supports both seamlessly. 我也可能正在使用市场功能,我需要一个无缝支持的系统。

I have seen multiple horror stories about the complexity of modifying subscriptions, including double billing, or cutting users off at the wrong time. 我看过很多关于修改订阅的复杂性的恐怖故事,包括双重计费,或者在错误的时间关闭用户。

I sincerely hope, for instance, that this article http://talklikeaduck.denhaven2.com/2007/09/02/how-to-cure-the-paypal-subscription-blues 我真诚地希望,例如,这篇文章http://talklikeaduck.denhaven2.com/2007/09/02/how-to-cure-the-paypal-subscription-blues

is out of date. 已过期。 The use cases that I have in mind are even more complex than the ones that he mentioned. 我想到的用例比他提到的用例更复杂。 For a sampling of what I would like to do: 对于我想要做的事情的抽样:

  • Support multiple subscriptions and subscription types/levels. 支持多种订阅和订阅类型/级别。 For instance one user might have 1 Plan A billed monthly at $10 and 10 plan C billed at $50 per month and 1 Plan D billed at $100 per year. 例如,一个用户可能有1个计划A每月收费10美元,10个计划C每月收费50美元,1个计划D收费为每年100美元。
  • Support changing of arbitrary payment amounts. 支持更改任意付款金额。 For instance, user was on the $40 per month plan, but then changes that to a $100 per month plan. 例如,用户每月40美元的计划,但随后将其更改为每月100美元的计划。 Then cancels, then signs up again at $50 per month before the $100 period was up. 然后取消,然后在100美元的期限之前再以每月50美元的价格再次报名。 The user should still get $100 of service for the month that he paid $100 for, and then should change to the $40 per month plan. 用户应该在他支付100美元的月份获得100美元的服务,然后应该更改为每月40美元的计划。
  • Allow for payments of subscription amounts between my users. 允许在我的用户之间支付订阅金额。 So one user might initiate a payment of 50% of whatever amount he has paid into the system so far. 因此,到目前为止,一个用户可能会支付他已支付给系统的任何金额的50%。 My application will be handling these types of marketplace style operations and these payments should work in the context of subscriptions... 我的应用程序将处理这些类型的市场风格操作,这些付款应该在订阅的上下文中工作...

It does not appear that there is an Open Source PHP library that does what I need either with Amazon or Paypal. 似乎没有一个开源PHP库可以用亚马逊或Paypal做我需要的东西。 So I am looking forward to coding this myself. 所以我很期待自己编码。 (be glad to be proved wrong here, perhaps a Freemium for PHP?). (很高兴在这里被证明是错误的,也许是PHP的Freemium ?)。 I cannot use the various subscription services that are available . 我无法使用可用各种订阅服务 Because they generally do not support the features above, and because I need to have direct access to the PayPal or Amazon FPS API for later cleverness via marketplace issues. 因为他们通常不支持上述功能,因为我需要直接访问PayPal或Amazon FPS API,以便以后通过市场问题获得聪明才智。

Which brings me to my question. 这让我想到了我的问题。 Which payment platform should I choose for ease of managing subscriptions? 我应该选择哪种支付平台以便于管理订阅? Please send me in the right direction, I only have so much time. 请把我送往正确的方向,我只有这么多时间。 But I also do not have time to make the wrong decision. 但我也没有时间做出错误的决定。 Please provide evidence for your preferences, and if possible detail your work comparing the two systems. 请提供您的偏好的证据,如果可能的话,请详细说明您比较两个系统的工作。 Google has the only other payment platform and currently their subscription system is in beta.. If you propose some other better system, please provider tons of good reasons, because I need a popular payment engine that people will feel comfortable with! 谷歌拥有唯一的其他支付平台,目前他们的订阅系统处于测试阶段。如果你提出一些其他更好的系统,请提供大量的理由,因为我需要一个人们会觉得舒服的流行支付引擎!

-FT -FT

I see you asked this question back in December... if you haven't found an answer yet, I have some suggestions based on my experience with a business problem almost identical to yours. 我看到你在十二月回答了这个问题...如果你还没有找到答案,我会根据我与你的业务问题几乎相同的经验提出一些建议。

Which PayPal API are you thinking of using? 您正在考虑使用哪种PayPal API? In using the PayFlow XML API, I found it was thousands of times easier to just roll my own subscription service. 在使用PayFlow XML API时,我发现滚动我自己的订阅服务要容易几千倍。 If the API you're using supports creating 'reference transactions' based on the previous successful transaction ID, you may save yourself a headache by keeping track of users' subscription amounts, keeping track of what's been paid, and creating a billing script that runs on a daily cronjob, checking each user to see if they need to pay (and how much), and then creating a reference sale for each of them. 如果您使用的API支持基于之前成功的事务ID创建“引用事务”,则可以通过跟踪用户的订阅量,跟踪已支付的内容以及创建运行的计费脚本来避免您的头痛。在每日cronjob上,检查每个用户是否需要支付(以及多少),然后为每个用户创建参考销售。

Of course, don't forget that you have to explicitly ask for users' permission before you start billing them on a recurring basis, and there should be a good recurring billing and privacy policy. 当然,不要忘记在定期开始计费之前必须明确要求用户许可,并且应该有一个良好的定期计费和隐私政策。 One trouble with this setup is that you pretty much need to create your own scripts to manage people's subscriptions and payments -- fortunately, I was tacking PayPal recurring billing onto a web app that already had subscriptions and accounting built-in. 这种设置的一个问题是你几乎需要创建自己的脚本来管理人们的订阅和付款 - 幸运的是,我正在将PayPal定期计费发布到已经内置订阅和会计的Web应用程序上。

Let me know if you need any suggestions on how to go about this! 如果您需要任何有关如何解决此问题的建议,请与我们联系!

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM