#CarlosEspino-subscription
little vector
Hi river, yes, this is one example sub_1L3U8eFz5jdfdaAC1JvgmFUA
The invoice it's been in draft since yesterday at 00:01:16 😅
shut salmon
Taking a look now!
shut salmon
The reason why the invoice is not finalized is because not all the webhook endpoints returned 200 for invoice.created event. If not all webhook endpoints responded with 200, invoice will only be finalized after 72 hours:
https://stripe.com/docs/invoicing/integration/workflow-transitions#finalized
This is the invoice.created event for this specific invoice: https://dashboard.stripe.com/test/events/evt_1L3U8eFz5jdfdaACBpflapww
You can remove those webhook endpoints that is not in use or try using test clock to advance the time for such scenario: https://stripe.com/docs/billing/testing/test-clocks
little vector
Thank you very much for the info, I'll test it right away, however... I am not completely sure that's the problem 😅
The doc states We wait an hour after receiving a successful response to the invoice.created event before attempting payment So far I understand that if any of the webhooks responds, it keeps going.
And this is what is happening with this subscription (sub_1L0E3IE4Ypfrto6a5xRzG8vI), in there the invoice.created received one successfull response (and there many webhooks configured), and in this case it works.
To add a little more of concepts, we are using this in production, the thing is that now we are trying implement something new that uses application_fee_percentage to move money from the Connected Account to the Platform on
shut salmon
The word in the doc is a bit confusing, but we require all webhook endpoints to acknowledge (200) to finalize the invoice. We will pass the feedback to the team
In sub_1L0E3IE4Ypfrto6a5xRzG8vI, the invoice is finalized 72 hours later (which is expected)
invoice.created was sent on 2022-05-17 00:14 and the invoice was only finalized on 2022-05-20 00:15
little vector
That's true!