arsenijblokov

[vapid latch]

hey there, there are many events related to subscriptions: https://stripe.com/docs/billing/subscriptions/webhooks#events

Only you can determing which ones are relevant to your business/operations

1. is customer.subscription.created but its not specific to payment links, its any subscription creation

2. could be customer.subscription.update to check the new period for example, or if you need payment details you could look at invoice.paid or even the payment events

3. would be invoice.payment_failed then looking at the details

4. customer.subscription.deleted

5. is also customer.subscription.update and look at status

[strange vine]

Thank you so much, it's really helps me to figure out with subscription-related events.
I researched this page https://stripe.com/docs/billing/subscriptions/webhooks#events, but amount of information is enormous, so above extraction is really helpful

[strange vine]

As i understand this event have subscription id in detail information?

[strange vine]

Like this one? Does this event triggered when subscription charges failed on only when customer cannot initiate subscription his first payment?

Also i would to know how much tries of charges and with what time interval between them will be initiated within subscription after failed charge?

[vapid latch]

Yes, any customer.subscription.* events have a subscription object as the payload, which has the id

[vapid latch]

Both, any invoice related payment failure

So you'd need to inspect those details

Since those invoice.* events include the invoice object, that include the billing_reason field you can look at:
https://stripe.com/docs/api/invoices/object#invoice_object-billing_reason

billing_reason
string
Indicates the reason why the invoice was created.

manual: Unrelated to a subscription, for example, created via the invoice editor.
subscription: No longer in use. Applies to subscriptions from before May 2018 where no distinction was made between updates, cycles, and thresholds.
subscription_create: A new subscription was created.
subscription_cycle: A subscription advanced into a new period.
subscription_threshold: A subscription reached a billing threshold.
subscription_update: A subscription was updated.
upcoming: Reserved for simulated invoices, per the upcoming invoice endpoint.

So you can use that to differentiate new subscription invoice from renewals or upgrade etc

(subscription_cycle is renewal)

[strange vine]

Good, i understand

[strange vine]

May i get answer to this question? It's crucial in our financial scheme

[vapid latch]

This depends on your settings. Take a look here about smart retries: https://stripe.com/docs/billing/revenue-recovery/smart-retries#smart-retries
But you can also configure retry timing in your Dashboard settings: https://dashboard.stripe.com/settings/billing/automatic (under "manage failed payments")

Or look at our Beta for automations: https://stripe.com/docs/billing/revenue-recovery/automations

[strange vine]

Good, i research this. But in nutshell - this behavior is available (i mean retries of charges from customer for subscription) and much customizeable?

[vapid latch]

Yes, automatic retries are available and customizable (with some exception included in docs)

[strange vine]

Really glad to hear that. Thank you so much again for you help!

Did you know how long our thread will be available so i didn't have to copy this information in any other place?