Marie

[drifting rock]

Hi
Do you have an example eventId and a webhook Id ?

[cunning swallow]

The last one was yesterday : "evt_1MXR1eK9OerefZqGTFPrQ2w2" and "req_MdsfMfPujiO207"

[drifting rock]

thanks for sharing let me check

[drifting rock]

According to the eventId you shared, your endpoint responded with The condition for the workflow payment-subscription_success is not met. Workflow won't run

You need to debug your endpoint and see why it's not responding 2xx

[cunning swallow]

Alright, thanks for that information. On every event, the status is "trialing" instead of active as I expected, what does it mean exactly ?

[vital kestrel]

You passed trial_end when you created the Subscription: https://dashboard.stripe.com/logs/req_MdsfMfPujiO207

So the status field will reflect that until the end of the trial period: https://stripe.com/docs/billing/subscriptions/overview#subscription-statuses

[cunning swallow]

Thank you for this, it's true we've implemented a trial period. Can you confirm that after that period, each payment of a subscription triggers the event "customer.subscription.updated" ? The webhook should be triggered by the event customer.subscription.updated and customer.subscription.created but I only see the last one

[vital kestrel]

This doc details how webhooks work with Subscriptions: https://stripe.com/docs/billing/subscriptions/webhooks

Generally you'd get customer.subscription.updated events when there's a change to the Subscription, like status transitions from trialing -> active, or at the end of a billing cycle

[cunning swallow]

Alright thanks a lot, according to what I see I should use incoive.paid instead of customer.subscription.updated to see if a subscription's monthly payment is made

[vital kestrel]

Yes, that's our general recommendation. The 2 will be sent ~simultaneously