Free, Standardized Webhooks for iOS, Android, and Stripe

One consistent webhook format and real-time subscription events across every store, with no meter on your data. Stop writing glue code for three event shapes — Superwall delivers one standardized webhook feed across the App Store, Google Play, and Stripe, free as you scale.

Why it matters

Most subscription stacks hand you three different event shapes: one for the App Store, one for Google Play, one for Stripe. You write glue code to normalize them, then rewrite it whenever a store changes its payload. And many tools meter the revenue they track or gate integrations behind higher plans, so the data you need to react to renewals, cancellations, and refunds gets more expensive as you grow.

Superwall takes the opposite approach. Webhooks deliver real-time notifications about your app's subscription and payment events in one standardized format, and they're free on the Indie plan ($0/month up to $10k Monthly Attributed Revenue). You pay only on the revenue your paywall experiments drive, not on users, total app revenue, or webhook volume.

What you can do with Superwall

• Receive every subscription event in one format. Superwall webhooks cover 9 event types: initial purchase, renewal, cancellation, uncancellation, expiration, billing issue, product change, subscription pause, and non-renewing purchase, with a consistent payload across the App Store, Google Play, and Stripe.

• Unify web and app revenue. An iOS app can receive Stripe events through Superwall's web checkout, so purchases made online and in-app land in the same feed. Web checkout revenue tracking is automatic with Stripe.

• Trust the data. Every request is signed so you can verify it came from Superwall (Svix / HMAC-SHA256), with timestamp validation to reject replays and unique event IDs for idempotency.

• Forward events anywhere. Pipe the same standardized events into your own endpoint or connect built-in integrations like Mixpanel, Amplitude, Slack, and Discord.

• Get revenue math for free. Per the webhook docs, summing proceeds or price across all events (without filtering) accurately represents total revenue net of refunds.

How it works

• Add a webhook endpoint. Configure your URL in the Superwall dashboard under Integrations. Each endpoint gets a unique signing secret.
• Receive standardized events. Superwall sends each subscription event as JSON with root-level metadata (event type, project/application IDs, timestamp) and a data object carrying 30+ fields, including product IDs, user info, and revenue figures. Custom user attributes you set via the SDK attach automatically.
• Verify each request. Use the signing secret and the included svix-id, svix-timestamp, and svix-signature headers to confirm authenticity. Use the Svix library or a manual HMAC check.
• Act on the events. Build win-back and recovery flows on billing issues and cancellations, sync entitlements, or forward events to analytics, all from one consistent stream covering iOS, Android, and Stripe.

Proof from customers

Superwall's customers consistently ask for one place to understand what's working across their main paywalls, discounts, web, and app, rather than fragmented data across surfaces. Standardized webhooks are how that single feed gets built: the same event format whether revenue comes from the App Store, Google Play, or Stripe.

Teams also rank promotions, win-back, offers, and abandoned-transaction recovery among their highest-priority, highest-converting opportunities. Real-time cancellation, billing-issue, and expiration events are the trigger layer that makes those recovery flows possible without turning every experiment into engineering work.

Because pricing is based on Monthly Attributed Revenue, the data layer never becomes the thing you're rationing. Webhooks stay free as you scale.

Use cases

• Win-back and recovery: trigger save offers when a billing_issue or cancellation event fires.

• Revenue dashboards: sum proceeds across events for revenue net of refunds, across all three stores.

• Web + app unification: route Stripe web checkout purchases into the same pipeline as App Store and Play purchases.

• Migration with low friction: events closely mirror App Store and revenue-provider structures, so moving onto Superwall's webhooks means less normalization code to rewrite.

• Entitlement sync: keep your backend's access state current on every renewal, expiration, and uncancellation.

Get started

• Set up your first webhook with the Webhooks docs and secure it using the verification guide.

• See what's free, including Webhooks, Integrations, Charts, and the IAP SDK, on the Superwall pricing page.

• Sign up for Superwall and start receiving standardized iOS, Android, and Stripe events today.