In-App Payments vs. Payment Processors vs. Rolling Your Own: What I Learned Building PetSafe

I spent months exploring how to integrate payments. StoreKit for PetSafe's subscription model made the most sense given time constraints. Then I found our Amazon team debate Stripe vs. Adyen in Slack channels. We ended u

The Three Paths StoreKit/Google Play Billing: Apple and Google own the rails. You pay 15-30%, they handle everything. Stripe/Adyen: Payment processors. You pay 2.9% + $0.30 (roughly), you control more. Roll your own: You pay interchange + processor fees (1.5-2%), you control everything, you also maintain everything.

When StoreKit Makes Sense StoreKit isn't a choice if you're doing iOS subscriptions or consumables—it's the only option per App Store guidelines. But even when you have a choice (reader apps, some B2B scenarios), here's what you get: Pros:

- Subscription management is handled. Upgrades, downgrades, grace periods, billing retry—all built-in. - Users trust the blue payment sheet. No card form UI to build. - Family Sharing works out of the box. - TestFlight sandbox testing is straightforward.

Cons:

- 30% cut is brutal (15% for small business program, but that caps at $1M revenue). - Receipt validation is arcane. Server-to-server notifications help, but you're still dealing with base64-encoded blobs. - No direct customer email. You can't email users about failed payments. - Refunds go through Apple. You have zero control.

For PetSafe, the 30% hurt, but the alternative was building web-based subscriptions and driving users out of the app. Conversion would've tanked. Sometimes the tax is worth it.

When Stripe/Adyen Work Better If you're on web or Android (with alternative billing), processors give you control without building infrastructure. Stripe wins on:

- Speed to integrate. Checkout, Billing, and Payment Links get you live in days. - Documentation. Their docs are legitimately good. - Ecosystem. Extensions, plugins, and integrations exist for everything. - Startup-friendly pricing. 2.9% + $0.30 is standard, but negotiable as you scale.

Adyen wins on:

Global payment methods. Ideal, Klarna, Boleto—they're native, not bolted on. Enterprise pricing. At scale, you'll pay less than Stripe (1.5-2% range). Platform features. If you're running a marketplace, their split payment logic is battle-tested.

Both handle:

- PCI compliance (you never touch card data). - Fraud detection (machine learning models you didn't have to train). - Failed payment recovery (dunning management that actually works).

The trade-off is you're paying for convenience. Stripe's 2.9% is significantly better than Apple's 30%, but it's still a margin hit. For most startups, this is the right path. You're buying time and reliability.

Why You Shouldn't Roll Your Own (Probably) I've seen the "just integrate with a payment gateway" pitch. Use Braintree's SDK, talk directly to card networks, save on fees. Here's what that actually means:

You're responsible for:

- PCI DSS compliance (annual audits, quarterly scans, documentation). - Tokenization and encryption (do this wrong once and you're done). - 3D Secure implementation (required in Europe, painful everywhere). - Fraud detection (or you'll bleed money to chargebacks). - Failed payment retry logic (subscriptions die without this). - Reconciliation (matching payments to orders at scale is harder than it sounds).

You save:

~1% in processing fees at volume (Stripe's 2.9% vs. interchange at ~1.8% + gateway fees).

The math only works if you're processing serious volume. Shopify, Netflix, Uber—they have payment teams. You probably don't. And even they use processors for some markets. The exception: if you're in a regulated or high-risk industry (crypto, gaming, nutraceuticals), you might not have a choice. Processors will reject you or charge punitive rates. Then you're building payment infrastructure whether you want to or not. What I'd Choose Today For a new startup: -Mobile app with subscriptions? StoreKit. Eat the 30%, optimize conversion. -Web or cross-platform SaaS? Stripe. Ship fast, iterate on pricing. Global product with localized payment methods? Adyen. Conversion rates in APAC and Europe will justify the integration effort. High volume B2C (>$10M ARR)? Talk to Adyen or Braintree, negotiate rates. -Venture-scale with payment complexity (marketplace, escrow, etc.)? Still Stripe or Adyen. Build features, not infrastructure.

The only time I'd build custom payment infrastructure is if I was in a restricted industry or processing massive volume where 1% margins matter. Payment rails are boring infrastructure. Pick the boring option that lets you ship features your customers care about.

In-App Payments vs. Payment Processors vs. Rolling Your Own: What I Learned Building PetSafe

Share Post