#Sedhu
1 messages · Page 1 of 1 (latest)
I'm not sure that's possible automatically with subscriptions/billing. We'll attempt to take payment ~immediately once the invoice is finalised around the billing date (e.g. 1st)
okay. Thanks!
@true cloak I tried to create a subscription now with billing_cycle_anchor: 1676313000 I'm getting an error billing_cycle_anchor cannot be later than next natural billing date (1675519151) for plan
Hello 👋
Taking over as ynnoj needs to step away soon
As my colleague suggested, your usecase isn't supported with subscriptions.
Like the error suggested, you can't move the billing cycle anchor past its natural cycle
Hi @covert flicker
You may need to introduce a trial for the time in between the natural billing date and the anchor you want to set on
Okay, Is that possible, we can charge at the trial Period?
We don't charge customers anything during the trial period, no.
okay. Lemme explain my scenarios, please suggest a way forward for my requirement
The only option that I can think of (which I havent' tested personally) is that you disable automatic collection by setting auto_advance: false when an invoice is generated on the 1st of the month
and then finalize it on 14th manually by calling the API
- We are offering 14 days of trails, but user want to pay the amount while subscribe.
- Every month 1st we have to send the invoice and 14th of month we have to charge them.
EX: If I'm subscribing today(4th Jan), I have to pay full amount today and while next month 1st I receive email of invoice and 14th of FEB amount should debit from my account.
So you mean I have to disable automatic collection to false and I have to update to true on every 14th of every month, am I correct?
Yes you can either set it to true or just call the API to finalize the invoice and pay
https://stripe.com/docs/api/invoices/finalize
https://stripe.com/docs/api/invoices/pay
okay lemme check this
@covert flicker Here the Invoice ID should be old one or upcoming invoice ID?
As long as you're not re-creating invoice, it should be the same as the one that was generated initially
I'd recommend giving it a try in test mode using test clocks
okay.