#ichidyakin-varicent-subscriptions
1 messages · Page 1 of 1 (latest)
Hi there!
Can you share the request ID (req_xxx) that created the subsciption? Here's how you can find it: https://support.stripe.com/questions/finding-the-id-for-an-api-request
Hi @zinc stump , here it is: req_UtKmqXWyUCCA1d
Thank you, soma had to step out but I am checking in to that request
Appreciate it!
So this is actually expected behavior,
- Pass
payment_behavior=default_incompletewhen creating a subscription. If your subscription requires payment, it’s created with statusincomplete, otherwise your subscription immediately becomesactive.
https://stripe.com/docs/billing/subscriptions/overview#how-payments-work-subscriptions
@fossil loom , I need pay_immediately flag set to false (there's an invoice tax integration that needs time to update the invoice).
And these two settings (pay_immediately and payment_behavior) cannot be set together: req_DWSPjgkwQeQVQw
Ah, I did not look at your code closely enough and missed pay_immediately, checking in to that flag but I believe that that is expected behavior for that call. And the underlying question is how to tell if you should provision your service?
Yes, you're absolutely right. I'd like to refer to Stripe Subscription object, relying on webhook events seems a bit fragile and resolving invoice status each time also does not seem like a good solution for that purpose
Sorry I am still having trouble figuring this out. I will reach out to my colleagues and get back to you on what we can find
Thank you, really looking forward to reading your answer 🙂
So at the moment it looks like you will need to do some form of either checking the latest invoice status or listening for webhooks about invoices getting paid.
To clarify, are you not using webhooks at all here at the moment?
I am using them (invoice.payment_succeded and failed, customer.subscription_deleted (or removed?))
I'd apprecieate if you shared why it was implemented this way on the Stripe side and whether we should expect any changes soon
I would like to understand the logic behind it, if you're in liberty to share it
This behavior will not change soon so you are good there. That behavior is a combination of our legacy subscription behaviors and a change to that flow that has stayed around for Avalara specifically. I understand that it can be less intuitive than the default_incomplete flow but unfortunately that is where the flow is at the moment