Add Paddle Billing and Stripe sync methods #943
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The goal of this PR is to introduce a simple interface for syncing one-time or subscription transactions. For Stripe, this is syncing Checkout Sessions and determining the Charge or Subscription to sync. For Paddle Billing, this retrieves a Transaction and determines if it is a charge or subscription.
We can also take this a step further and provide a method that takes a hash (like
params
) and determines whether to sync from Stripe, Paddle Billing, etc.The end goal is to provide integrations a single method to call for syncing after checkout.