Adapty supports tracking web payments and subscriptions made through Stripe. If you're already offering your product on the web or thinking about doing it, there are two scenarios where it can be helpful:
- automatically providing access to paid features for users who purchased on the web but later installed the app and logged in to their account
- having all the subscription analytics in a single Adapty dashboard (including cohorts, predictions and the rest of our analytics toolbox)
Even though purchases on the web are becoming increasingly popular for apps, you must remember that it is against Apple's App Store terms to provide a different system than in-app purchases for digital goods. Make sure you don't promote your web subscriptions from inside your app. Otherwise your app may get rejected or banned.
This integration is currently in Beta and comes with a few limitations. However, it's still possible to complete the most popular scenarios. Follow the steps below to configure the integration with Stripe.
This integration mainly relies on Adapty pulling subscription data from Stripe via the webhook. So it is essential to connect your Adapty account to your Stripe account by doing 2 things: providing API Keys and using Adapty's webhook URL in Stripe.
The steps below are the same for Production and Sandbox (or Test mode in Stripe). You can do them simultaneously for both environments.
Go to Developers → API Keys in Stripe:
Press "Reveal live (test) key" on the Secret key, then copy it and go to Adapty's App Settings → Stripe. Paste the key here:
Next, copy the Webhook URL from the bottom of the same page in Adapty. Go to Developers → Webhooks in Stripe and press "+ Add endpoint":
Paste the webhook URL from Adapty into "Endpoint URL" field. Then choose the Latest API version in webhook version. Then select the following events:
Press "Add endpoint" and then press "Reveal" under the "Signing secret". This is the key that is used to decode the webhook data on the Adapty's side, copy it after revealing:
Finally, paste this key into Adapty's App Settings → Stripe under "Stripe Webhook Secret":
You're all set! Next, create your products on Stripe and add them to Adapty.
If you're configuring Sandbox, make sure to switch to Test mode in Stripe, before proceeding with this step.
Go to Stripe's Product catalog and create the products you would like to sell as well as their pricing plans. Note that Stripe allows you to have multiple pricing plans per product, which is useful for tailoring your offering without the need to create additional products.
At the moment Adapty only supports Flat rate ($9.99/month) or Package pricing ($9.99/10 units), as those behave similar to app stores. Tiered pricing, Usage-based fee and Customer chooses price options are not supported
We treat Stripe the same way as App Store and Google Play: it is just another store where you sell your digital products. So it is configured similarly: simply add Stripe products (namely their
price_id) to the Products section of Adapty:
Product IDs in Stripe look like
prod_... and price IDs look like
price_.... They are pretty easy to find for each product in Stripe's Product Catalog, once you open any Product:
After you've added all the necessary products, the next step is to let Stripe know about which user is making the purchase, so it could get picked up by Adapty!
Adapty relies on the webhooks from Stripe to provide and update access levels for users as the only source of information. But you have to provide additional info from your end when working with Stripe for this integration to work properly.
For access levels to be consistent across platforms (web or mobile), you have to make sure that there is a single user ID to rely on which Adapty can recognize from the webhooks as well. This could be user's email, phone number or any other ID from the authorization system you're utilizing.
Figure out which ID you would like to use to identify your users. Then, access the part of your code that's initiatilizing the payment through Stripe — and add this user ID to the
metadata object of either Stripe Subscription (
sub_...) or Checkout Session object (
customer_user_id like so:
This one simple addition is the only thing that you have to do in your code. After that, Adapty will parse all the webhooks it receives from Stripe, extract this
metadata and correctly associate subscriptions with your customers.
User ID is required
Otherwise, we have no way to match this user and provide him the access level on the mobile.
If you don't supply
metadata, you will have the option to make Adapty look for
customer_user_idin other places: either
client_reference_idfrom Stripe's Session.
Learn more about configuring profile creation behavior below
Customer in Stripe is also required
If you are using Checkout Sessions, make sure you're creating a Stripe Customer by setting
To make sure your mobile users arriving from web can access the paid features, just call
Adapty.identify() with the same
customer_user_id you've provided on the previous step (see Identifying users for more).
Make sure you've completed the steps above for Sandbox as well as for Production. Transactions that you make from Stripe's Test mode will be considered Sandbox in Adapty.
Your users can now complete purchases on the web and access paid features in your app. And you can also see all your subscription analytics in a single place.
Adapty has to tie a purchase to a customer profile for it to be available on the mobile — so by default it creates profiles upon receiving webhooks from Stripe. You can choose what to use as customer user ID in Adapty:
- Default and recommended:
customer_user_idyou supplied in metadata in step 4 above
client_reference_idin Stripe's Session object (see Stripe's docs)
You can configure which ID you would like to use in App Settings → Stripe.
Note: if a particular transaction from Stripe does not contain the specified ID, we will not create a profile at all. This transaction will remain anonymous until it gets picked up by some profile (for example, if you use S2S validate afterwards and tell us about this transaction manually).
It will show up in Analytics but not in the sections that rely on counting profiles (LTV, Cohorts, Conversions, etc) and you won't be able to see it in Event feed.
You also have a fourth option to not create profiles at all but this is not recommended due to the above.
While in Beta, we don't send out integrations for purchases coming from Stripe. This will certainly be a part of the release version.
Subscription changes such as upgrading or downgrading can result in prorated charges. Adapty will not account for these charges in revenue calculations. It would be best to disable these options manually via the Stripe dashboard. You can also disable them by setting the
proration_behaviour attribute value to
none via the Stripe API.
Stripe has two subscription cancellation options:
- Immediate cancellation: subscription cancels immediately with or without any proration option
- Cancellation at the end of the period: The subscription cancels at the end of the current billing period (similar to in-app subscriptions on the app stores).
Adapty supports both options, but the revenue calculation for immediate cancellation will disregard the proration option.
When a customer encounters an issue with their payment, Adapty will generate a billing issue event and access will be revoked. We don't support Stripe's Grace Period while in Beta, but it will be available on Release.
Adapty tracks only full refunds. Proration or partial refunds are not supported currently.
Updated 14 days ago