-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WEB-2015] Rename "RevenueCat Billing" to "Web Billing" #618
Conversation
Preview this PR here: https://dev-docs.revenuecat.com/pr-618/ |
|
||
RevenueCat provides a backend and a mobile and web SDKs to to make implementing in-app and web purchases and subscriptions easy. With our SDK, you can build and manage your app business on any platform without having to maintain your own backend infrastructure. You can read more about [how RevenueCat fits into your app](https://www.revenuecat.com/blog/growth/where-does-revenuecat-fit-in-your-app/) or you can [sign up free](https://app.revenuecat.com/signup) to start building. | ||
|
||
With the RevenueCat Web SDK and our billing engine RevenueCat Billiing, you can easily implement subscriptions in your web app or build a web subscription page for your mobile app. RevenueCat handles the recurring billing logic, manages what entitlements customers have access to, and automatically recovers payments in the case of billing issues. RevenueCat Billing uses Stripe as a trusted payment gateway and supports all payment methods supported by Stripe. | ||
With the RevenueCat Web SDK and our Web Billing (formerly known as RevenueCat Billing) engine, you can easily implement subscriptions in your web app or build a web subscription page for your mobile app. RevenueCat handles the recurring billing logic, manages what entitlements customers have access to, and automatically recovers payments in the case of billing issues. Web Billing uses Stripe as a trusted payment gateway and supports all payment methods supported by Stripe. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added "formerly known as RevenueCat Billing". Not sure how often we want to add this. Should it be done in all pages, just in the main page?
6ecfaf3
to
42e1769
Compare
6a70e87
to
451c340
Compare
451c340
to
ca6249d
Compare
@@ -128,7 +128,7 @@ try { | |||
const offerings = await Purchases.getSharedInstance().getOfferings({currency: "USD"}); | |||
if (offerings.current && offerings.current.monthly) { | |||
const product = offerings.current.monthly.rcBillingProduct; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed that this property will be marked as deprecated and replaced by webBillingProduct
.
We plan to change this once a new version of the SDK is released, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep, there's a task for it. But we would also need to update the purchases-js
version used in the docs (currently 0.7.0, and latest is 0.15.1)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LG!
I guess that API V2 specs will be updated once the renaming is done in the endpoints, right?
They're part of a khepri PR. To clarify, the endpoints won't be renamed, just some strings in the spec. |
Motivation / Description
Rename "RevenueCat Billing" to "Web Billing"
Changes introduced
Linear ticket (if any)
Additional comments