#birdy247
1 messages · Page 1 of 1 (latest)
What's the use case
Total item price = £500
item is delivered on a given day in the future, no matter when you buy it
User is asked to pay £200 when they signup
And then £300 3 months before the item is delivered OR when they choose, but it cannot be any closer to the date that 3 months
I am guessing we can use subscription schedules and set the start,end dates ourselves
And then if the customer wants to pay earlier, we can just finalise the invoice sooner
Why would you use a schedule when this isn't really a recurring payment?
Think I helped you the other day, and I advised the same
Right
Got it
We already use subscription schedules, so thought we could re-use that logic
You're kind of trying to bend a schedule to fit your will, which is probably why you're encountering issues
But you think instead save the card?
Its just a bigger piece of work to store customers against entities that are not on subscriptions
Yes, you'd need to save the card against a Customer object to charge it off-session for the remaining amount
You could use a schedule as I also suggested in that thread, but it will likely result in unintentional side effects (e.g. zero-amount invoices)
Yea, but what about setting our own start/end date
rather than using an interval of week/month etc..
How do you then account for the final payment?
the inital payment scheule has an end-date of when the final balance is then due
There'd need to be X amount of phases where there's no payment between that initial down payment and the final amount. How do you account for that?
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
Guess that could work. Try it out with clocks!