Compare

ZeroSettle vs. StoreKit / Play Billing

If your job is to sell subscriptions and IAPs and keep more of what your users pay, the stores are the default — and they take 30% (15% for small business), act as Merchant of Record, and give you only basic analytics. ZeroSettle adds direct web billing so you keep ~85%+ on that revenue, with full analytics free — and the SDK auto-falls-back to StoreKit and Play Billing wherever direct billing isn't permitted, so your app works everywhere.

Store commission
30%

15% under the Small Business Program — you keep roughly 70%.

With ZeroSettle web billing
~85%+

Kept on web-checkout revenue, after payment processing fees.

Store fallback
Automatic

SDK falls back to StoreKit / Play Billing wherever direct billing isn't permitted.

Side by side

The 30% status quo vs. direct billing

ZeroSettle doesn't replace the stores — it adds a higher-margin path and keeps the stores as automatic fallback. Fees apply only to web-checkout revenue; your App Store and Play sales are never charged a ZeroSettle fee.

StoreKit / Play Billing ZeroSettle direct billing
Your share of revenue ~70% store takes 30% (15% small-business) ~85%+ on web-checkout revenue
Merchant of Record The store Optional stay MoR (BYOS) or we're MoR (Managed)
Subscription analytics
MRR, churn, retention, trials
Basic in App Store Connect Full · free · no MRR cap
Entitlements across iOS, Android & web No cross-platform identity Included free
A/B testing on prices & paywalls Included free
Works where direct billing isn't allowed It's the store Auto-falls-back to the store region-aware, no code changes
Global tax, chargebacks & support The store handles it Managed mode · 190+ countries
Fee on App Store & Play sales 30% (15% small-business) Never charged by ZeroSettle store fees still apply on store sales
Fee on web-checkout revenue n/a 0.5% BYOS / 5% + 50¢ Managed BYOS adds your Stripe fees and keeps you MoR; Managed is all-in with MoR

Comparison reflects publicly listed pricing and capabilities as of May 2026. ZeroSettle fees apply only to web-checkout revenue — App Store and Play sales are never charged a ZeroSettle fee.

Honest take

When to choose which

This isn't either/or. ZeroSettle adds a path; the stores stay as fallback.

Stay on the stores if…

Your volume is low, you already qualify for the 15% small-business rate, and you're happy letting the store be Merchant of Record and own analytics, tax, and support. There's nothing to add and nothing to maintain.

Add ZeroSettle if…

You want to keep ~85%+ on web-checkout revenue instead of ~70%, get full analytics and cross-platform entitlements free, and run paywall A/B tests — while the SDK auto-falls-back to StoreKit and Play Billing wherever direct billing isn't permitted, so your app still works everywhere.

Keep comparing

Other comparisons

See how ZeroSettle stacks up against the other ways to bill.

vs. RevenueCat

Same analytics and entitlements, plus direct billing and free A/B testing on one platform.

ZeroSettle vs. RevenueCat

vs. raw Stripe

Stripe is the rail underneath direct billing. See what you'd build yourself versus one SDK call.

ZeroSettle vs. Stripe

Keep ~85%+ instead of ~70%

Add a higher-margin path without leaving the stores behind — direct billing where it's allowed, automatic store fallback where it isn't. Free analytics & entitlements in 5 minutes; direct billing on iOS & Android in 15.

YC-backed·15-min integration