Skip to content
This repository has been archived by the owner on Mar 22, 2024. It is now read-only.

Update account-management.md #187

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

mshmoustafa
Copy link
Contributor

This section was outdated, it said we can't transfer projects between accounts. Instead I wrote up two strategies for transferring projects, changing the email and reaching out to support.

Motivation / Description

Changes introduced

Jira ticket (if any)

Additional comments

This section was outdated, it said we can't transfer projects between accounts. Instead I wrote up two strategies for transferring projects, changing the email and reaching out to support.
@mshmoustafa mshmoustafa requested a review from a team July 13, 2023 18:16
@mshmoustafa mshmoustafa self-assigned this Jul 13, 2023
Copy link
Contributor

@HaleyRevcat HaleyRevcat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice Sharif, Cody and I were just discussing adding something here. Should we also add a tidbit regarding the multiple Stripe account thing, or just address that in the ticket?

@mshmoustafa
Copy link
Contributor Author

@HaleyRevcat thanks for the review! How does that look?

@RCGitBot
Copy link
Contributor

Previews

temp/account-management.md

See contents

Account Security & 2FA

Read more about account security and two-factor authentication in our Account Security guide.

Update your email or name

You can change your account email and name from your account settings in the dashboard.

Transfer account ownership

Projects can be transferred between RevenueCat accounts by following one of two processes:

  1. If you are transferring all of the projects in your account, it is recommended that you change the email of the account to the new owner's email to give the new owner control over the account. If that's the case, use a new email. Please follow the instructions above for changing your account email.
  2. If you want to transfer some but not all projects from your RevenueCat account to another RevenueCat account, contact RevenueCat Support for assistance. Please note the following restrictions:
    • If your app uses Stripe and the receiving account also has Stripe apps, you need to transfer your Stripe account to them as well. RevenueCat supports only one Stripe account per developer account.
    • If your app uses the Apple Ad Services integration, the receiving developer needs to update the public key in App Store Connect.
    • The receiving developer account must have a RevenueCat plan that has an equal or greater level of service than your account to ensure that all integrations continue working.

How does billing work?

RevenueCat bills based on Monthly Tracked Revenue, or MTR, for each plan. MTR is different than Monthly Recurring Revenue, or MRR, and includes the revenue from all purchases and renewals including non-subscription products. You can see your account's current MTR here.

Read more on our Pricing page.

Tax & VAT details

Please reach out to RevenueCat Support if you need Tax IDs or VAT information added to your invoices.

📘 VAT updates apply to future invoices only

RevenueCat Support cannot add tax IDs and VAT information to invoices that have already been sent, and any added tax IDs and VAT information will only apply to future invoices.

Address details

If needed, you can add additional address information to your invoices by clicking 'Update payment method' and expanding the 'Invoice Details' section:

update payment method button invoice details expanded

Delete your account

❗️

To delete your RevenueCat account, you'll first need to delete all of your Projects. Note that deleting any active Projects will prevent users from accessing their purchases via the RevenueCat SDK but will not cancel any of your customer's active subscriptions.

Once your projects have been deleted, reach out to RevenueCat Support via the dashboard Contact Us form in your account settings and request your account to be deleted.

temp/paywalls.md

See contents

RevenueCat's Paywalls allow you to remotely configure your entire paywall view without any code changes or app updates. Whether you’re building a new app, exploring new paywall concepts, or diving into experimentation; RevenueCat’s Paywalls make it easy to get started.

Paywalls are supported in the following SDK versions:

RevenueCat SDK Version required for Offering Metadata
purchases-ios 4.26.0 and up
purchases-android 7.1.0 and up
react-native-purchases 7.4.0-beta.2
purchases-flutter 6.3.0-beta.1

❗️

Within the SDKs, Paywalls are available on the following platforms:

  • iOS 15.0+
  • visionOS 1.0+
  • Mac Catalyst 15.0+
  • watchOS 8.0+
  • Android 7.0 (API level 24)

Support for more platforms is coming soon: macOS, tvOS, and others!

[block:embed]
{
"html": "<iframe class="embedly-embed" src="//cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FxSc9ICeyJpk%3Ffeature%3Doembed&display_name=YouTube&url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DxSc9ICeyJpk&image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FxSc9ICeyJpk%2Fhqdefault.jpg&key=7788cb384c9f4d5dbbdbeffd9fe4b92f&type=text%2Fhtml&schema=youtube" width="854" height="480" scrolling="no" title="YouTube embed" frameborder="0" allow="autoplay; fullscreen; encrypted-media; picture-in-picture;" allowfullscreen="true"></iframe>",
"url": "https://www.youtube.com/watch?v=xSc9ICeyJpk",
"title": "Introducing RevenueCat Paywalls",
"favicon": "https://www.google.com/favicon.ico",
"image": "https://i.ytimg.com/vi/xSc9ICeyJpk/hqdefault.jpg",
"provider": "https://www.youtube.com/",
"href": "https://www.youtube.com/watch?v=xSc9ICeyJpk",
"typeOfEmbed": "youtube"
}
[/block]

How Paywalls work

iOS Installation

Using SPM:

If you already have RevenueCat in your project:

  1. Open your project settings and select "Package Dependencies":
Change version
  1. Double-click and make sure version is at least 4.26.0:
Configure version
  1. Open your target settings and find "Frameworks, Libraries, and Embedded Content":
Find frameworks in your target
  1. Add RevenueCatUI:
Add RevenueCatUI dependency

First time integrating the RevenueCat SDK:

  1. Click File -> Add Packages...

  2. Search for git@github.com:RevenueCat/purchases-ios.git and make sure version is at least 4.26.0:

Adding purchases-ios dependency
  1. Add RevenueCat and RevenueCatUI SPM dependency to your project:
Add paywall

Using CocoaPods:

Add the following to your Podfile:

pod 'RevenueCat'
pod 'RevenueCatUI'

Android Installation

  1. Add RevenueCatUI:
implementation 'com.revenuecat.purchases:purchases:7.1.0'
implementation 'com.revenuecat.purchases:purchases-ui:7.1.0'

❗️

Android paywalls is currently behind an experimental flag (ExperimentalPreviewRevenueCatUIPurchasesAPI).
It is safe to release app updates with it. We guarantee that paywalls will continue to work and any changes will always be backwards compatible.
They are stable, but migration steps may be required in the future. We'll do our best to minimize any changes you have to make.

React Native (Beta) Installation

See 7.4.0-beta-.2 release notes

Flutter (Beta) Installation

See 6.3.0-beta.1 release notes

Overview

Our paywall templates use native code to deliver smooth, intuitive experiences to your customers when you’re ready to deliver them an Offering; and you can use our Dashboard to pick the right template and configuration to meet your needs.

To use RevenueCat Paywalls, simply:

  1. Create a Paywall on the Dashboard for the Offering you intend to serve to your customers

  2. See displaying paywalls for how to display it into your app.

Offerings and Paywalls

You can think of a Paywall as an optional feature of your Offering. An Offering is the collection of Products which are organized into Packages to be displayed to your customers as a single "offer" across platforms. Now, with Paywalls, you can control the actual view that is used to display that "offer" in addition to controlling the products that are offered.

Therefore, you can create a unique Paywall for each of your Offerings, and can create an unlimited number of Offerings & Paywalls for each variation you want to test with Experiments.

Limitations

Platforms (support for more coming)

  • ✅ iOS 15.0 and higher
  • ✅ visionOS 1.0 and higher
  • ✅ Mac Catalyst 15.0 and higher
  • ✅ watchOS 8.0 and higher
  • ✅ Android 7.0 (API level 24)
  • ❌ macOS
  • ❌ tvOS

Android's Google Play developer determined offers

Paywalls in Android will use the default subscription option which, in case you use developer determined offers, will always be available, providing these types of offers always to your users. If you want to avoid this behavior when using paywalls, add the rc-ignore-offer tag to the developer determined offer from your product.

Next Steps

  • Now that you know how our paywalls work, read about creating paywalls
  • Once you're ready to see your paywalls in action, you can follow our guides on displaying paywalls
  • If you need inspiration with some paywall examples, you can try our Paywalls Tester app

- If your app uses Stripe and the receiving account also has Stripe apps, you need to transfer your Stripe account to them as well. RevenueCat supports only one Stripe account per developer account.
- If your app uses the Apple Ad Services integration, the receiving developer needs to [update the public key](doc:apple-search-ads#advanced) in App Store Connect.
- The receiving developer account must have a RevenueCat plan that has an equal or greater level of service than your account to ensure that all integrations continue working.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mshmoustafa just merged main in this branch and noticed the section got deleted in main. Do you still want to add this text? Or should we close this PR.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants