Stripe Webhooks

Pay listens to Stripe's webhooks to keep the local payments data in sync.

For development, we use the Stripe CLI to forward webhooks to our local server. In production, webhooks are sent directly to our app's domain.

Development webhooks with the Stripe CLI

You can use the Stripe CLI to test and forward webhooks in development.

stripe login
stripe listen --forward-to localhost:3000/pay/webhooks/stripe

Production webhooks for Stripe

1. Visit https://dashboard.stripe.com/webhooks/create.
2. Use the default "Add an endpoint" form.
3. Set "endpoint URL" to https://example.org/pay/webhooks/stripe (Replace example.org with your domain)
4. Under "select events to listen to" choose "Select all events" and click "Add events". Or if you want to listen to specific events, check out events we listen to.
5. Finalize the creation of the endpoint by clicking "Add endpoint".
6. After creating the webhook endpoint, click "Reveal" under the heading "Signing secret". Copy the whsec_... value to wherever you have configured your keys for Stripe as instructed in Credentials section under Configurations doc.

Events

Pay requires the following webhooks to properly sync charges and subscriptions as they happen.

charge.succeeded
charge.refunded
charge.updated

payment_intent.succeeded

invoice.upcoming
invoice.payment_action_required
invoice.payment_failed

customer.subscription.created
customer.subscription.updated
customer.subscription.deleted
customer.subscription.trial_will_end
customer.updated
customer.deleted

payment_method.attached
payment_method.updated
payment_method.automatically_updated
payment_method.detached

account.updated

checkout.session.completed
checkout.session.async_payment_succeeded

Next

See Metered Billing