RevenueCat webhook to sync subscriptions #547
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-code-scanning[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| @@ -0,0 +1,24 @@ | |||
| module Webhooks | |||
| class RevenueCatController < ApplicationController | |||
| skip_before_action :verify_authenticity_token, only: :create | |||
Check failure
Code scanning / CodeQL
CSRF protection weakened or disabled High
joemasilotti
force-pushed
the
revenue-cat-webhooks
branch
2 times, most recently
from
e48cdbd
to
b7e645c
Compare
joemasilotti
force-pushed
the
revenue-cat-webhooks
branch
from
b7e645c
to
bb57a1b
Compare
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR exposes a new endpoint,
/webhooks/revenue_cat, for RevenueCat to POST webhooks to. The user ID is extracted from the payload and a generic "sync" workflow is kicked off. Each webhook is handled the same way, regardless of the type of event that is sent, from RevenueCat's recommendation.The syncing workflow uses Tarpon to interact with RevenueCat's REST API. The user's subscription status is requested and then written to a fake payment processor via the Pay gem. This aligns with Stripe subscriptions so existing infrastructure can be used to verify permissions for paying customers.
In the future, a full-blown RevenueCat payment processor could be implemented. But for now, I think this should get us what we need!
Pull request checklist
bin/checkI added significant changes and product updates to the changelog