birdy247

[frozen vigil]

Hello 👋
Let's chat here

[nocturne matrix]

I note customer is optional, but in this use case, can we assume that its somewhat mandatory

https://stripe.com/docs/api/subscription_schedules/create

[frozen vigil]

Yeah, IMO I'd create a customer object prior to creating the schedule. I've not seen them done any other way before
https://stripe.com/docs/billing/subscriptions/subscription-schedules/use-cases#installment-plans

[nocturne matrix]

so create customer

[frozen vigil]

yup

[nocturne matrix]

attach to subscription_schedule

then how do we attach the payment method?

In a more typical subscription, we take the first invoice items payment intent I think

[frozen vigil]

yup on a schedule, you'd still find a subscription object where you can locate the latest_invoice.payment_intent

https://stripe.com/docs/api/subscription_schedules/object#subscription_schedule_object-subscription

[nocturne matrix]

ok cool

So as soon as thats paid, then the schedule starts?

[frozen vigil]

I believe so, would recommend testing it out to be 100% certain

[nocturne matrix]

ok cool

and do these generate invoice likes subscriptions?

So we can expect invoice.xx webhooks?

[frozen vigil]

you mean renewal invoices?

yes

[nocturne matrix]

Yea, so lets say the schedule has 6 iterations

presumably we would get webhooks each time an iterative payment is made

[frozen vigil]

that's correct, yes.

[nocturne matrix]

Great

will we be able to different these webhooks from "regular" subscription

[frozen vigil]

sorry missed your question, do you mean if you receive invoice.paid you want to know if they came from a scheduled subscription?

[nocturne matrix]

yes

[frozen vigil]

I don't think there's direct way but you can expand subscription object on invoice.paid event payload and look at schedule property of the subscription
https://stripe.com/docs/api/subscriptions/object#subscription_object-schedule

regular subscription wouldn't have a value ther