在我们的应用程序中，用户在结帐期间使用一年的使用费，然后一年后，我们凝视着收费。
假设用户是通过电子邮件识别的。那么，如何验证用户现在有活动的订阅呢？
我已经看过几个帖子建议构建Webhook并收听PayPal事件。
在我们的流程中，初始购买将在WordPress网站上使用其中一个订阅插件，然后我需要在应用程序中“激活”订阅。
“ Webhook”是PayPal唯一可能的选项吗？
我已经在Braintree SDK中看到了与订阅有关的东西，这可以工作吗？
在我看来，它太复杂了，无法构建整个系统以验证订阅。例如，在Stripe中，您可以主动询问用户是否有订阅。
In our app user is paying for one year of use during checkout and then after a year we are staring to charge subscription.
Let's say that users are identified by email. So, how can I verify that user have now an active subscription ?
I have seen a few posts that suggest to build webhook and listen to PayPal events.
In our flow the initial purchase will be on WordPress website with one of the subscriptions Plugins and then I need to "activate" subscription in the App.
Is the "webhook" the only possible option with PayPal?
I have seen something in Braintree SDK related to subscription, can this work?
Seems to me too complicated to build the whole system only to verify subscription. In Stripe, for example, you can proactively ask if the user has subscription.
发布评论
评论（1）
webhook付款。使用此信息不断更新您的记录，以了解用户是否具有付费订阅。
如果您需要元数据来对帐，哪些订阅对应于哪个用户（但是在PayPal中识别出它们可能与您相关，但是您可以识别它们），则可以在创建订阅时，以下设置参数
code> cody> code_id最多127个字符的值。如果您需要下载以前付款的事务历史记录，则可以从帐户接口，通常在活动下 - ＆gt;所有报告 - ＆gt;活动下载。然后，可以将其导入到数据库中，以在您没有Webhook事件的记录中进行任何差距。
The webhook PAYMENT.SALE.COMPLETED informs of every completed subscription payment. Use this information to continuously update your records of whether a user has a paid-for subscription.
If you need metadata for reconciliation of which subscription corresponds to which user (since however they are identified at PayPal may not correspond to however you identify them), you can set the parameter
custom_idwhen creating the subscription, to any value of up to 127 characters.If you need to download a transaction history of previous payments, you can get a report in CSV format from the https://www.paypal.com account interface, typically under Activity -> All Reports -> Activity Download. This can then be imported to a database to backfill any gap in your records that you don't have webhook events for.