You never reconcile rails by hand. A customer who subscribes on the web with
Stripe and later reinstalls your iOS app sees the same pro entitlement,
because entitlements are keyed to the customer, not to the store that
happened to take the payment. Read Entitlements for the
model.
Billing overview
Connect the App Store, Google Play, Stripe, and merchant-of-record providers so every rail settles into one entitlement model and one revenue ledger.
A billing backend is a payment rail CashSDK settles through. Your customers might pay through the App Store on their iPhone, Google Play on their Android phone, a Stripe checkout on the web, or a merchant of record like Paddle, and CashSDK maps every one of those to the same entitlement your app already checks, and folds the money into one revenue ledger for MRR, churn, and tax.
Store billing#
The primary rails for mobile revenue. Purchases run through the platform SDK and are validated server-side before any entitlement is granted.
Apple App Store
StoreKit 2 purchases and subscriptions on iOS, iPadOS, and macOS.
Google Play
Play Billing purchases and subscriptions on Android.
Web & merchant-of-record billing#
Sell on the web, or let a merchant of record handle global tax and compliance. Every order maps to a CashSDK entitlement and reconciles alongside your store revenue.
Stripe
Card payments, tax, and billing for web checkouts.
Paddle
Merchant of record for SaaS and digital goods.
Lemon Squeezy
Developer-friendly merchant of record.
Polar
Developer-native MoR with usage billing.
FastSpring
Long-established MoR for desktop and SaaS.
Gumroad
Digital products, memberships, and downloads.
Recurly
Enterprise subscription management and recovery.
Chargebee
Subscription billing and revenue operations at scale.
How a billing backend connects#
Every backend follows the same three steps. The specifics differ per provider, and each guide covers them in detail, but the shape is always this.
1
Connect your account
Add the provider from your CashSDK dashboard under Settings → Billing. Credentials (API keys, service-account files, signing secrets) are stored encrypted at rest and never ship in your app binary.
2
Map your catalog
Match the provider's products and prices to CashSDK products and the entitlements they unlock. A purchase on any rail then resolves to the same entitlement everywhere.
3
Reconcile in one ledger
Charges, renewals, and refunds settle into a single revenue view alongside every other backend: one source of truth for MRR, churn, and tax.
Choosing a backend#
- Shipping a mobile app? Use the App Store and Google Play. The platforms require their own billing for digital goods consumed in-app.
- Selling on the web or cross-platform? Stripe is the default. Reach for a merchant of record (Paddle, Lemon Squeezy, Polar, FastSpring) when you want tax and compliance handled for you across borders.
- Already have a billing engine? Connect Recurly, Chargebee, or Gumroad and keep it. CashSDK reads the entitlement, not the invoice logic.