The RevenueCat Android SDK Handbook

In-app subscriptions without the boilerplate — the same problems as raw Google Play Billing, solved with RevenueCat SDK.

Start reading Download PDF

Foundations

Chapter 1

Understanding RevenueCat

One SDK replaces three separate systems: BillingClient, Google Play Developer API, and RTDNs.

Chapter 2

Setting Up RevenueCat

Dashboard configuration, service account setup, and SDK dependency — everything in just 8 steps.

Products

Chapter 3

One-Time Products with RevenueCat

Three method calls are all you need: fetch offerings, launch a purchase, and check the result.

Chapter 4

Subscriptions with RevenueCat

Offerings → Packages → SubscriptionOptions. The complete product hierarchy, clearly simplified.

Client-side integration

Chapter 5

Configuring the SDK

A single configure() call replaces the entire connection lifecycle, reconnection, and sync logic.

Chapter 6

The Purchase Flow

awaitPurchase() handles the complete billing flow, verification, and acknowledgement internally.

Chapter 7

Subscription Upgrades and Downgrades

Same replacement modes, one PurchaseParams builder, and no manual token chain code to maintain.

Chapter 8

Error Handling

PurchasesErrorCode replaces BillingResponseCode. The SDK handles all retry logic automatically.

Server-side

Chapter 9

Backend Architecture

You don't need to build a verification server. RevenueCat already is your verification server.

Chapter 10

Webhooks

One endpoint with normalized JSON events. No Cloud Pub/Sub configuration, no base64 decoding.

Subscription lifecycle

Chapter 11

Subscription States

Seven complex subscription states are resolved to just one simple boolean check: isActive.

Chapter 12

Payment Recovery

In-app messages are shown automatically by default. Just two lines needed to detect grace period.

Chapter 13

Cancellations, Pauses, and Winback

Read unsubscribeDetectedAt and expirationDate. That's your entire cancellation handler, done.

Chapter 14

Price Changes

Nothing to implement on your side. RevenueCat processes RTDNs, and CustomerInfo stays correct.

Production readiness

Chapter 15

Security

Trusted Entitlements with built-in response signature verification. Choose from three modes.

Chapter 16

Testing

Test Store provides fully deterministic outcomes without needing Google Play sandbox accounts.

Chapter 17

Catalog Management

Import your products and update Offerings directly from the dashboard. No code changes needed.

Advanced

Chapter 18

Alternative Billing Programs

Web billing available via webCheckoutURL. Google programs still require raw PBL integration too.

Reference

Appendix A

RevenueCat API Quick Reference

All SDK methods, data structures, and error codes are fully documented on just a single page.

Appendix B

What RevenueCat Replaces

A complete side-by-side comparison: your responsibility vs. everything handled by RevenueCat.

What RevenueCat replaces

A side-by-side look at what the SDK handles and what stays your responsibility.

ConcernRaw Google Play BillingWith RevenueCat

BillingClient connection lifecycle
You writeHandled internally
Receipt verification
You build serverAutomatic
Purchase acknowledgement
You writeAutomatic
RTDN / Cloud Pub/Sub
You set upNot needed
Subscription state machine
You buildisActive computed by RC
Retry logic for transient errors
You writeHandled internally
linkedPurchaseToken chain
You buildRC backend

View full comparison table in Appendix B

Related resources

RevenueCat Docs
Full SDK reference, platform guides, and integration walkthroughs for every feature.
Learn more
Sub Club Podcast
Insights on subscription app growth, pricing strategies, and retention from industry experts.
Learn more
Сat-paywall-compose
Open-source Jetpack Compose paywall example with production-ready code.
Learn more