Stripe VS purchases-ios

Stripe iOS SDK: iOS SDK versions 22.8.1-22.8.3 contain updates to PaymentSheet, CardScan, and Identity, as well as bug fixes for Financial Connections and the Card Scan UI.

Stripe iOS SDK: iOS SDK versions 22.6.0 - 22.8.0 were released this month. These updates contain fixes and updates for PaymentSheet and Apple Pay.

Stripe iOS SDK v22.6.0: The stripe-ios v22.6.0 release includes support for Link payment method on payment sheets, adds the ability to capture selfie images in the native component flow for Identity, and fixes several bugs related to Identity.

Stripe iOS SDK v22.5.1: In iOS SDK version 22.5.1, you can now use PaymentSheet.ApplePayConfiguration.paymentSummaryItems to directly configure the payment summary items displayed in the Apple Pay sheet. This is useful for recurring payments.

Stripe iOS SDK version 21.11.0 and 21.10.0: iOS SDK version 21.11.0 introduces several payment methods in the PaymentSheet including Afterpay/Clearpay, EPS, Giropay, Klarna, P24, and more. Version 21.10.0 introduces the StripeCardScan beta.

Stripe iOS SDK version 21.9.0: iOS SDK version 21.9.0 introduces several new features to PaymentSheet, including support for more payment methods like SEPA Direct Debit, Bancontact, iDEAL, and Sofort as well as support for setting up future usage for cards, Apple Pay, and Google Pay.

Stripe iOS SDK version 21.8.0: This new iOS SDK release adds support for Stripe Identity on iOS. Read more in the docs.

RevenueCat — Hosted backend for in-app purchases and subscriptions (iOS and Android). Free up to $2.5k/mo in tracked revenue.

You got it! Yea, I can't promise everything will work perfectly with all those other platforms, but I will promise that I believe we have the best handling out there. We have 10+ engineers fielding issues from 1000s of developers every month and incrementally improving.

We try to collect as little data as possible, but we use RevenueCat for handling the IAP. We currently use it with anonymous (randomly generated) IDs and don't save additional attribution metadata, so we try to be as privacy-friendly as is possible with this setup.

For IAPs, RevenueCat is one of the simplest setup that exists for React Native. And they have an expo plugin. But having this expo management workflow is the first thing you want to do. https://www.revenuecat.com/

Alternatively you could use RevenueCat which would handle receipt validation for you. I haven’t used it personally but everyone seems to sing its praises.

There are services out there like revenuecat (disclaimer: I have no connection with them, other than being a satisfied customer) that help make these things easier. I recommend looking into them if you’re struggling to wrap your head around it on your own, apple’s documentation can be pretty hard to decipher at times.

I'm Josh Holtz, the author of this article. You might now me from my lead maintainer role of fastlane, creator of Indie Dev Monday, and founder of the new Deep Dish Swift conference ☺️ But I also work at RevenueCat to help developers make more money by making in-app purchases and subscriptions easier!

I have integrated RevenueCat in my previous Startup Fitenium to manage subscriptions, and it was one of the best decisions. Instead of having to integrate both Apple and Google play SDK for subscriptions, with RevenueCat I simply integrated their SDK, which is well documented and much easier to work with. Everything else is magically managed by RevenueCat behind the scenes, to properly handle the payments, users, and analytics.

RevenueCat — Hosted backend for in-app purchases and subscriptions (iOS and Android). Free up to $10k/mo in tracked revenue.