User taps buy
Checkout starts from your paywall — your native UI, unchanged.
Billing routing
One route
One route
per purchase.
One SDK call routes every purchase down the optimal path — direct web billing where it's allowed, the app stores' own billing as an automatic, compliant fallback. From tap to access in seconds, both stores, one integration.
One purchase call, no separate code path. ZeroSettle fees apply only to web-checkout revenue — never to native store sales.
How it works
Tap to access, step by step.
Every purchase follows the same five beats, whatever payment surface the SDK selects. Your paywall and native UI never change.
SDK routes
Region, configuration, and product eligibility decide the path — direct web billing or the app stores.
Payment sheet
Apple Pay, Google Pay, or card — a native sheet, an in-app browser, or the store's own sheet. One tap, no redirect.
Confirmation
The SDK fires a callback the moment payment succeeds — no polling.
Access
Entitlement updates instantly across iOS, Android, and web. One identity.
Checkout modes
One SDK call, the right path every time.
The SDK picks the checkout surface per purchase — a native payment sheet or in-app browser where direct billing is permitted, and the app stores' billing as the automatic fallback everywhere else.
Routing rule
"Send the purchase down the payment path with the highest take-home revenue that's compliant for the buyer's region — and fall back to the app stores automatically when direct billing isn't allowed."
Checkout surfacesSDK-selected, per eligibility
Native payment sheetWhere direct billing is eligible
Apple Pay + card · no redirect
In-app browserWhere direct billing is eligible
Stripe checkout · fast, integrated
Store billingAutomatic fallback everywhere else
The app stores · at the store's rate
Eligibility & fallback
Where direct billing applies — and where the store takes over.
Direct web billing is subject to each store's rules. Where it's permitted you keep far more of every sale; everywhere else the same SDK call falls back to the app stores at the store's rate — no lost sales, no separate code path.
| Purchase context | Path taken | Effective fee | Merchant of record |
|---|---|---|---|
| External purchase permittede.g. Apple’s US external-purchase entitlement, eligible regions | Direct web billing | Managed 5% + 50¢, or BYOS 0.5% + your Stripe (~2.9% + 30¢)Up to 34% more than the app stores’ 30% cut — and the effective fee shrinks as price rises | ZeroSettle (Managed)or you, on BYOS |
| Standard App Storeno external-purchase entitlement | StoreKit — automatic fallback | 30% standard · 15% under the Small Business Program (<$1M/yr) | Apple |
| Google Playwith program enrollment | Direct where enrolled, else Play Billing | Direct: your fees + Google’s service fee, where levied · Play Billing: store rate | You (direct) · Google (Play Billing) |
ZeroSettle only charges on web-checkout transactions; native store purchases pay the store’s rate. Direct billing depends on store eligibility — Apple’s external-purchase entitlement varies by app store, and Google requires program enrollment and may levy a service fee. However a purchase is routed, the customer’s entitlement is identical — access stays unified across web, StoreKit, and Play.
One identity
Every path lands
Every path lands
in the same place.
However a purchase is routed, the customer's entitlement is identical. There's one record of what a customer owns — read from a single call, kept in sync across every surface.
- Unified entitlements across web, iOS, and Android — one source of truth.
- Instant updates the moment payment succeeds, with no polling.
- Refunds & chargebacks revoke access automatically, wherever the sale routed.
Two milestones
Integrate in a day. Launch when your store config is ready.
Wiring up the SDK and going live in production are separate steps — the code lands fast; the store configuration moves at the store’s pace.
SDK integration
Add the SDK, wire one purchase call, and read a single unified entitlement. Your paywall and native UI stay exactly as they are — no separate code path for web vs store.
- Drop-in SDK, one purchase call
- Unified entitlements across web, StoreKit, and Play
- Test the full flow end-to-end in sandbox
Production launch
Go live once your store configuration is in place — App Store review, the external-purchase entitlement or Play program enrollment, and entitlement setup. On your timeline; we guide the compliance steps.
- Store review & external-purchase entitlement / program enrollment
- Entitlement & catalog setup
- Flip to live once approved
Handled for you
We handle the complexity.
From the payment rails to the edge cases, the platform takes care of what you'd otherwise build and maintain.
Subscriptions & consumables
Recurring billing, grace periods, and one-time items — power-ups, credits, unlocks — set up in the quickstart.
Refunds & disputes
Access is revoked automatically on a refund or chargeback. On Managed mode, ZeroSettle is the Merchant of Record.
Apple Pay & Google Pay
One-tap checkout on web, no extra integration — payouts land on your schedule.
Regional checkout, priced right
Purchasing-power price ladders across 175 markets, matched to the checkout mode for that region.
Instant receipts
Email receipts for every purchase — and the margin story behind why direct billing pays more.
A/B test pricing and checkout
Test price and checkout changes on real traffic before committing the whole audience.
Questions
Billing routing, precisely.
One rail sits alongside the other rather than pretending it doesn't exist. Here are the operational details developers usually ask first.
It checks region, your configuration, and product eligibility, then picks the payment path with the highest take-home revenue that's compliant for that buyer — falling back to the app stores' own billing automatically when direct billing isn't allowed.
No. One SDK call handles it — the native payment sheet, in-app browser, and store fallback are all triggered from the same purchase call.
It processes as a normal store purchase — the app stores keep the full transaction, and it is never charged a ZeroSettle fee.
The SDK fires a confirmation callback the moment payment succeeds, and entitlement state updates instantly across iOS, Android, and web — no polling required.
Yes — auto-renewable and non-renewing subscriptions, plus consumable and non-consumable one-time items, all route through the same flow.
Start with one product
A calmer way to grow app revenue.
Connect your catalog, unify customer access, and launch your first pricing experiment — then turn on Autopilot when you're ready to scale.