If your subscription app manages web subscriptions with Stripe, you can plug Stripe with Purchasely. The configuration of Stripe with Purchase is performed in 4 steps

I. Installing the Stripe App

Go to the Purchasely's app listing on Stripe apps marketplace

If you have more than one Stripe account (for each application) then connect the account you want to associate with the application.

🚧
One Stripe Account for One Purchasely Application
A Stripe application combines a Stripe account with only one Purchasely Application. If your Stripe account works with more than one Purchasely Application, please contact our support team via Intercom.
Read below on how to handle Stripe "test", "sandbox", and "production" environments.

Click on install app.
The list of authorizations required for the proper functioning of our application is then displayed.

📘
Question?
If you have a question about the use of an authorization, contact our support team via Intercom.

Validate the authorizations requested

The installation is complete, you can proceed with the configuration.

II. Configuration of the Stripe app

Once the Stripe Purchasely app is installed you need to configure it.
Go to the Stripe console in Settings > installed apps > Purchasely.

Associate with Purchasely

Once on the app configuration you need to associate it with your Purchasely account and app. To do this, start by clicking on "SIGN IN".

Select the Purchasely app you wish to link your Stripe account to.

Click on "NEXT".

📘
Configuration for Test and Production
Once the app is installed, it needs to be configured both in the "test" and "production" Stripe environments for purchases to be tracked in those environments accordingly.
The following configurations are supported :

2 Purchasely applications

My Purchasely App (staging) <-> Stripe Account (test mode)

My Purchasely App (production) <-> Stripe Account (production mode)

1 Purchasely application

My Purchasely App <-> Stripe Account (test + production mode)

📘
Sandbox support
Since version 0.0.22 of the Purchasely Stripe App, you can also install Purchasely in a Stripe sandbox environment.
The installation flow is identical to test and production modes: install Purchasely from the marketplace while your Stripe dashboard is switched to your sandbox, then follow the setup wizard. Purchasely automatically detects that you are in a sandbox and links the account accordingly.
🚧
Switching from test mode to sandbox on the same Purchasely application
Sandbox and test mode are separate Stripe environments with distinct account identifiers. A Purchasely application can only be linked to one of them at a time.
If your Purchasely application is already linked to a Stripe account in test mode and you want to switch to sandbox, you must first unlink the test mode connection before installing the app in your sandbox:

In your Stripe dashboard, open the Purchasely app settings in test mode and click "Disconnect" (or uninstall the app).

Switch to your sandbox in the Stripe dashboard.

Install the Purchasely app from the marketplace and follow the setup wizard.

Your historical test mode data (subscriptions, receipts) remains attached to the previous test mode link but will no longer receive new events.

Confirm Stripe app link with your mobile application

Once you have selected the application, you will be redirected to Stripe to finalise the configuration by clicking on "CONFIRM".

The app will appear as below when properly configured in Purchasely and Stripe.

III. Configuration of plans

In order for Purchasely to associate Stripe products, they must be defined in the plans. Also you must associate each Pricing Stripe to a Purchasely Plan otherwise the purchase will not be taken into account by Purchasely.

From the Stripe console, copy the API ID (price) ...

Then paste this ID into the corresponding plan:

Purchasely allows you to associate more than one Stripe Price to one given Purchasely plan, to handle cases where there exists several Stripe Prices tied to the same "plan" but with a different currency.

🚧
Different Stripe Price
Do not associate more than one Stripe Price to one given Purchasely plan if the Stripe Prices have different periodicity, or different level of entitlement.
For such use cases, create another plan.

IV. Associating Stripe subscriptions to Purchasely

This last step allows Purchasely to retrieve and associate a purchase with a user.

❗️
This step is mandatory, otherwise we won't track the subscription
We need to know the association between the Stripe Subscription and your User ID
Otherwise we would track the subscription but wouldn't know to which user in your app to associate it with

The principle is the same as for the migration of an existing subscriber

To send us this information, simply call our API and provide it with

stripe_object_id: the Stripe subscription ID
stripe_price_id: the Stripe Price Id for this subscription (ON STRIPE)
user_id: the user_id associated with the purchase, the same as you enter in the SDK during configuration.
stripe_object_type: the type of Stripe object sent, currently we only accept subscription

curl \
  --request POST \
  -i \
  -H "Content-Type: application/json" \
  -H "X-API-KEY:{{YOUR_API_KEY}}" \
  -H "X-PLATFORM-TYPE:STRIPE" \
  --data '{"stripe_object_id":"{{STRIPE_SUBSCRIPTION_ID}}","stripe_price_id":"{{STRIPE_PRICE_ID_FOR_THIS_SUBSCRIPTION}}", "user_id":"{{SAME_ID_AS_IN_SDK_CONFIGURATION}}", "stripe_object_type":"subscription"}' \
  https://s2s.purchasely.io/receipts

Example request:

curl \
  --request POST \
  -i \
  -H "Content-Type: application/json" \
  -H "X-API-KEY:AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE" \
  -H "X-PLATFORM-TYPE:STRIPE" \
  --data '{"stripe_object_id":"sub_1MluxqJaEiB9UwXB34gmtzCB","stripe_price_id":"price_1MbKJHJaEiB9UwXBPt0fFq4O", "user_id":"jdo-cus_Msq9YfCiFkFzVx", "stripe_object_type":"subscription"}' \
  https://s2s.purchasely.io/receipts

curl \
  --request POST \
  -i \
  -H "Content-Type: application/json" \
  -H "X-API-KEY:{{YOUR_API_KEY}}" \
  -H "X-PLATFORM-TYPE:STRIPE" \
  --data '{"stripe_object_id":"{{STRIPE_SUBSCRIPTION_ID}}","stripe_price_id":"{{STRIPE_PRICE_ID_FOR_THIS_SUBSCRIPTION}}", "user_id":"{{SAME_ID_AS_IN_SDK_CONFIGURATION}}", "stripe_object_type":"subscription"}' \
  https://s2s.purchasely.io/receipts

Example request:

curl \
  --request POST \
  -i \
  -H "Content-Type: application/json" \
  -H "X-API-KEY:AAAAAAAA-BBBB-CCCC-DDDD-EEEEEEEEEEEE" \
  -H "X-PLATFORM-TYPE:STRIPE" \
  --data '{"stripe_object_id":"sub_1MluxqJaEiB9UwXB34gmtzCB","stripe_price_id":"price_1MbKJHJaEiB9UwXBPt0fFq4O", "user_id":"jdo-cus_Msq9YfCiFkFzVx", "stripe_object_type":"subscription"}' \
  https://s2s.purchasely.io/receipts

🚧
Cross-platform subscriptions are not deduplicated
Sending a Stripe receipt for a user_id that already has an active App Store / Play Store subscription does not deactivate the existing subscription. Both will coexist as active in Purchasely (each emitting its own events), and the user will be billed by each store.
If you want to prevent this, check the user's current subscription status (via webhooks or the SDK) before triggering a Stripe checkout, and ask the user to cancel their existing store subscription first.

Passing integration attributes (optional)

You can include integration_* fields in the JSON body so that Purchasely associates the subscriber with your analytics and engagement platforms (Amplitude, Mixpanel, Airship, Adjust, etc.). This lets those platforms receive subscription lifecycle events automatically.

curl \
  --request POST \
  -i \
  -H "Content-Type: application/json" \
  -H "X-API-KEY:{{YOUR_API_KEY}}" \
  -H "X-PLATFORM-TYPE:STRIPE" \
  --data '{
    "stripe_object_id":"sub_1MluxqJaEiB9UwXB34gmtzCB",
    "stripe_price_id":"price_1MbKJHJaEiB9UwXBPt0fFq4O",
    "user_id":"jdo-cus_Msq9YfCiFkFzVx",
    "stripe_object_type":"subscription",
    "integration_amplitude_user_id":"amp-12345",
    "integration_adjust_id":"adj-67890",
    "integration_mixpanel_distinct_id":"mx-abcde"
  }' \
  https://s2s.purchasely.io/receipts

All fields are optional. Include only the ones for the platforms you use.

Platform	Field(s)
Adjust	`integration_adjust_id`
Airship	`integration_airship_channel_id`, `integration_airship_user_id`
Amplitude	`integration_amplitude_user_id`, `integration_amplitude_device_id`, `integration_amplitude_session_id`
Appsflyer	`integration_appsflyer_id`
AT Internet	`integration_at_internet_id_client`
Batch	`integration_batch_installation_id`, `integration_batch_custom_user_id`
Branch	`integration_branch_user_developer_identity`
CleverTap	`integration_clevertap_id`
Customer.io	`integration_customerio_user_id`, `integration_customerio_user_email`
Firebase / Google Analytics	`integration_firebase_app_instance_id`
Iterable	`integration_iterable_user_email`, `integration_iterable_user_id`
Mixpanel	`integration_mixpanel_distinct_id`
MoEngage	`integration_moengage_unique_id`
mParticle	`integration_mparticle_user_id`
OneSignal	`integration_one_signal_player_id`, `integration_one_signal_user_id`, `integration_one_signal_external_id`, `integration_one_signal_external_user_id`
Sendinblue (Brevo)	`integration_sendinblue_user_email`

👍
Real-Time Events
Purchasely relies on Stripe webhooks to get the information about a known subscription in real time. This information is processed by our system to create Purchasely events and then sent to your webhook, if configured.

📘
Export
You can export a list of your Stripe's subscriptions with their associated prices from your Stripe Stripe dashboard.
On Stripe go under:
Billing > Subscription > Export
Select: Custom and keep only "ID" and "Plan"