A paid subscription is acquired. Fires once, at first activation.

When this fires

On the first successful payment for a subscription, across every payment provider: Stripe, PayPal, Paystack, Razorpay, Skrill, CeyPay, and CoinPayments. It covers both recurring subscriptions and one-time (non-recurring) passes.

It fires once per subscription, at acquisition. It is not a general "became active" signal:

A Stripe subscription that begins in a trial still emits subscription.activated at acquisition, because the provider creates the subscription at that moment. The later trial-to-paid transition emits member.converted only.

This is the paid-acquisition event. If you only subscribe to one subscription event for a paying audience, subscribe to this one, not subscription.created, which never fires for paid checkouts.

data.provider is never access_code on this event; code redemptions emit subscription.created instead.

Caveats

• Once per subscription. Stripe and PayPal de-duplicate with a persistent guard key; the remaining providers emit only on the non-renewal branch of their payment handler. Renewals never re-emit it.
• To capture every acquisition path (paid, comped code, and cardless trial) subscribe to both subscription.activated and subscription.created, then de-duplicate on data.subscription_id.
• Paid acquisitions do not emit member.joined. That event is access-code-only. Use subscription.activated as the paid-audience join signal.
• payment.succeeded fires for the same charge and carries the amount, currency, and external payment id, which this event does not.
• The POST /v1/webhook-endpoints/{endpoint}/test endpoint sends a synthetic subscription.created payload, never subscription.activated. Testing an endpoint does not exercise this event.

Related events

• subscription.created: the zero-payment acquisition equivalent.
• payment.succeeded: the charge behind this activation.
• subscription.renewed: every subsequent cycle.
• member.converted: trial-to-paying transition.