Stripe

With the Stripe integration, you can:

Attribute web purchases and subscriptions collected through Stripe back to the install and ad campaign that drove them.
See Stripe revenue alongside your app-store revenue in Appstack.

To successfully connect Stripe, you must:

Have Stripe enabled for your organization (currently in pilot). If you see Coming soon, contact support@appstack.tech.
Have editor access to the project, and no pre-launch apps in it.
Have the Appstack SDK integrated, and a server that creates your Stripe Checkout Sessions.

Connect to Stripe

Install the Appstack app in Stripe

In Appstack, go to Integrations > Stripe and click Continue. Install the Appstack app in Stripe, then click Continue setup to return to Appstack.

Choose the account and products

Select the Stripe account for this project and at least one product. A single connection covers both your iOS and Android apps.

Each project uses one Stripe account, and the account can’t be replaced yet.
An organization can register several Stripe accounts, and one account can serve several projects in that organization.
A Stripe account belongs to one Appstack organization only.
Each product maps to one project. Use Add products on the integration page to add more later; at least one must stay mapped.

Send the metadata with every purchase

Read the Appstack ID in your app and send it to your server, together with the app’s app_id, in the request that creates the checkout:

Key	Value
`app_id`	iOS: the numeric App Store ID. Android: the package name.
`appstack_id`	The Appstack ID returned by the SDK.

Always send the app_id of the app where the purchase started. If your project has both an iOS and an Android app and you always send the same app_id, every subscription and purchase is attributed to that one app. Set app_id per platform, never as a single hardcoded value on your server.

let appstackId = AppstackAttributionSdk.shared.getAppstackId()

val appstackId = AppstackAttributionSdk.getAppstackId()

const appstackId = await AppstackSDK.getAppstackId();

final appstackId = await AppstackPlugin.getAppstackId();

using Appstack;

string appstackId = AppstackSDK.GetAppstackId();

Then add both keys when you create the Checkout Session.Subscriptions: use subscription_data.metadata.

curl https://api.stripe.com/v1/checkout/sessions \
  -u "sk_live_...:" \
  -d mode=subscription \
  -d "line_items[0][price]={{PRICE_ID}}" \
  -d "line_items[0][quantity]=1" \
  -d "success_url=https://example.com/success" \
  -d "subscription_data[metadata][app_id]={{APP_ID}}" \
  -d "subscription_data[metadata][appstack_id]={{APPSTACK_ID}}"

const session = await stripe.checkout.sessions.create({
  mode: "subscription",
  line_items: [{ price: priceId, quantity: 1 }],
  success_url: "https://example.com/success",
  subscription_data: {
    metadata: { app_id: appId, appstack_id: appstackId },
  },
});

session = stripe.checkout.Session.create(
    mode="subscription",
    line_items=[{"price": price_id, "quantity": 1}],
    success_url="https://example.com/success",
    subscription_data={"metadata": {"app_id": app_id, "appstack_id": appstack_id}},
)

One-time payments: use payment_intent_data.metadata.

curl https://api.stripe.com/v1/checkout/sessions \
  -u "sk_live_...:" \
  -d mode=payment \
  -d "line_items[0][price]={{PRICE_ID}}" \
  -d "line_items[0][quantity]=1" \
  -d "success_url=https://example.com/success" \
  -d "payment_intent_data[metadata][app_id]={{APP_ID}}" \
  -d "payment_intent_data[metadata][appstack_id]={{APPSTACK_ID}}"

const session = await stripe.checkout.sessions.create({
  mode: "payment",
  line_items: [{ price: priceId, quantity: 1 }],
  success_url: "https://example.com/success",
  payment_intent_data: {
    metadata: { app_id: appId, appstack_id: appstackId },
  },
});

session = stripe.checkout.Session.create(
    mode="payment",
    line_items=[{"price": price_id, "quantity": 1}],
    success_url="https://example.com/success",
    payment_intent_data={"metadata": {"app_id": app_id, "appstack_id": appstack_id}},
)

The Checkout Session’s top-level metadata, and metadata on the Customer or Product, is not enough. Use the nested parameters above.

Payment Links: a static Payment Link can’t carry a different appstack_id per install, and Appstack doesn’t read client_reference_id. Create Checkout Sessions from your server instead.

The integration activates once at least 50% of new live-mode subscriptions over the last 24 hours include a valid app_id and appstack_id. One-time payments alone don’t activate the integration yet.

List of events

Name	Definition
`st_trial_started`	Free trial begins.
`st_subscription_started`	Paid subscription starts, with no trial.
`st_trial_converted`	Trial becomes paid.
`st_subscription_renewed`	Subscription renews.
`st_in_app_purchase`	One-time purchase.

Troubleshooting

Problem	Solution
Status stays on Waiting for events	Check that new live-mode subscriptions for the selected products include both keys in `subscription_data.metadata`.
Alert about `app_id`	Send the App Store ID (iOS) or package name (Android) of an app in this project, not the bundle ID.
Alert about `appstack_id`	Make sure the app reads the Appstack ID with the SDK and your server forwards it on every checkout.
Events coverage stays low after a fix	Older subscriptions keep their original metadata. Fixes only apply to new purchases.

To disconnect, click Disconnect on the Stripe integration page. This removes the project’s connection and product mappings; the Stripe account stays registered to your organization. For issues, contact support@appstack.tech.

Getting started

Mobile SDKs

Integrations

Products

Developer tools

Connect to Stripe

List of events

Troubleshooting

​Connect to Stripe

​List of events

​Troubleshooting

Connect to Stripe

List of events

Troubleshooting