RevenueCat
In-app purchases & subscriptions — the single source of truth for entitlements across the App Store and Google Play.
Why we need this
RevenueCat is the service that powers in-app purchases and subscriptions in your app. It's the single source of truth for what a customer has paid for and which entitlements they should have, across both the App Store and Google Play. Calda connects to it through the RevenueCat SDK and REST API so the app can sell subscriptions, restore purchases, and unlock features reliably on every platform.
Like all other accounts, this one should be owned by you. Your revenue data, billing, and the store credentials wired into it are tied to the account, so keeping it under your company means that data belongs to you, not us.
Do I need a credit card?
No. RevenueCat accounts are free to set up and free to run until you cross their monthly tracked revenue threshold — more than enough to get started and run early beta. All collaborator roles are available on every plan, so inviting us as a team member needs no paid plan and no card.
A paid plan is only relevant much later, once your revenue grows past the free tier.
Only you can manage billing
On RevenueCat, billing can only ever be managed by the project owner — that's you. When we're invited as collaborators we can configure and manage everything else, but we can't see or change your billing details. That stays with you by design.
A note on organizations vs. projects
This is the important part to get right. RevenueCat does not have an organization-wide team — there's no single place to add someone once and have them on everything. Instead, collaborators are invited per Project.
A Project is the container that holds the platform Apps for your App Store and Google Play listings, plus your entitlements, offerings, and products. We need to be added as a collaborator on the Project itself. If separate Projects are ever created (for example, a separate staging and production project), we'll need to be invited to each one individually.
Project-level, not account-level
Adding us under your personal account or expecting an organization-level invite won't work outside of RevenueCat's Enterprise SSO. Make sure the invite happens from inside the Project's settings so we actually get access.
Step-by-step setup
Create your RevenueCat account
Sign up at revenuecat.com using the company email that should own the account. This creates your account, which can own and be invited to multiple projects.
Create a project
From the dashboard, create a new Project and name it after your company or app. The project is the container for your App Store and Google Play apps, your entitlements, offerings, and products — everything we'll configure lives here.
Invite Calda as a collaborator
Open Project settings → Collaborators, click to invite a collaborator, enter the Calda email we share with you, and assign the Administrator role. Then send the invite — we'll get an email to accept it.
Administrator is the role we need: it lets us manage everything in the project (apps, integrations, entitlements, and API keys) except your billing.
Why Administrator and not a lower role
The lower roles fall short for our setup: Developer can't generate the Secret API keys we need, and Growth can't edit app settings like bundle ID or package name. Administrator covers all of it while still keeping billing with you. Remember collaborators are per-project — if there's more than one project, repeat this invite for each.
Confirm in Slack
Don't forget to notify us in Slack so we can accept the invitation and confirm that we can sign in.
Conclusion
That is it — with a project in place and Administrator access granted, we can wire up in-app purchases and subscriptions on both platforms. Once you've added us as a collaborator and confirmed in Slack, we'll handle the rest of the integration on our side.
How is this guide?