#mathieu_api
1 messages · Page 1 of 1 (latest)
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1218127897206853652
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- mathieu_api, 18 hours ago, 6 messages
hi! well in general, the only purpose of backdate_start_date is to generate proration, so if you also pass proration_behavior:"none" it ends up not doing anything.
I guess what do you intend to happen here? What amount do you want the customer to pay today on 15 March when signing up to this subscription?
Hey @subtle summit
If I don't pass the backdate_start_date and set proration_behaviour to none, it doesn't generate an invoice as well
(I can retry that)
My intention is to have the user pay the full, normal price of the pricing for the first period, whatever its duration.
And I also what to have it anchored to 01/01
(I wanted to backdate it for accounting purposes, in order to clarify on the invoice that it goes from 01//01 to 01/01 but I can find another way to fit that need)
yep, because what you're saying it, create this subscription but the billing anchor is next Janurary. What we'd do by default is charge the prorated amount from 15 March->1 Jan, but you disable that, so there's nothing to invoice.
to be honest what I would just do is use add_invoice_items to add an ad-hoc one-time Price that is the same amount as one year of the plan, that's easiest
Ok, yes that makes sense
I thought I could, after subscribing the user, create a one off invoice but I didn't like the fact that the subscription would be validated even if the payment failed for this one off invoice.
If I add the invoice item to the subscription, then the behaviour of the status of the subscription will be the same as if I were doing a "normal" subscription (meaning it would depend on the status of the first invoice generated)?
I would say yes. It just creates an Invoice like normal and if that invoice fails/requires 3D Secure and you're using default_incomplete per docs, you get an incomplete subscription as normal
Ok then, it sounds perfect!
Thx for your help @subtle summit , it seemed easy with you but that the 3rd time I try to contact support with this issue, and the first I get a satisfying answer 🙂
Hello @subtle summit , may I know which API in the Stripe-ACH payment process includes the user's bank card name?(https://docs.stripe.com/payments/ach-debit) Because we require users to make deposits under the same name.
Could you please advise on how to proceed?