Connecting RevenueCat for subscriptions

RevenueCat handles subscriptions and one time purchases of digital things inside your app: a monthly plan, a premium routine, an unlocked feature. Apple requires digital goods to be sold through in app purchase, and RevenueCat is how Quiny does that without you touching receipts.

If you sell physical products or services that are delivered outside the app, you do not need RevenueCat. Use Stripe. Quiny chooses the right one from your answers and tells you which.

Before you start

• Your Apple Developer account is connected, so the app exists in App Store Connect.
• The Paid Apps agreement is accepted under Business, then Agreements, with bank and tax details filled in. Apple will not let purchases work without it.

Step 1. Create the products in App Store Connect

1. Open your app in App Store Connect, then Subscriptions or In App Purchases.
2. Create each product with a plain identifier, for example glowhaus_monthly or glowhaus_routine_pro. Set the price and, for subscriptions, the duration.
3. Fill in the display name and description Apple asks for. Products must be at least in the Ready to Submit state.

Step 2. Create a RevenueCat project

1. Sign up at app.revenuecat.com and create a Project named after your app.
2. Add an app to the project and choose App Store. Enter the bundle identifier, which Quiny shows under Workspace, then App details.
3. Under App Store Connect API in that app, upload an In App Purchase key. Create it in App Store Connect under Users and Access, then Integrations, then In App Purchase: press the plus button, name it RevenueCat, download the .p8, and paste the Key ID and Issuer ID into RevenueCat.

Step 3. Set up entitlements and an offering

1. In RevenueCat open Entitlements and create one for what people unlock, for example pro.
2. Open Products and import the products from App Store Connect, then attach each one to the entitlement.
3. Open Offerings. Create a default offering with a package for each product, for example monthly and yearly. This is what the paywall shows.

Step 4. Connect it in Quiny

1. In RevenueCat open API keys and copy the public app specific key for your App Store app. It starts with appl_.
2. In the console open Settings, then Connections, then RevenueCat. Paste the key and choose the entitlement Quiny should check.
3. Press Connect. Quiny adds the paywall screen using your offering, adds restore purchases to the account screen, and gates the right parts of the app on the entitlement. The screens arrive for approval like any other.

Step 5. Test before you submit

1. In App Store Connect open Users and Access, then Sandbox Testers, and add a test Apple ID.
2. Ask Quiny for a test build. Install it through TestFlight, sign in on the device with the sandbox account, and buy the subscription. Sandbox purchases do not charge real money and renew quickly so you can watch them.
3. Check the purchase appears in RevenueCat under Customers. If it does, you are ready to submit.

What Quiny never does

Quiny never sees your customers' payment details and never holds your money. Apple collects payment, RevenueCat records the entitlement, and payouts go from Apple to your bank.

Common problems

• "No offerings found" means the offering is not marked current or has no packages.
• Purchases work in sandbox but the paywall shows no prices: the products are not yet approved or the Paid Apps agreement is incomplete.
• "Entitlement not active after purchase": the product is not attached to the entitlement in RevenueCat.