#Siva_K-invoices
1 messages ยท Page 1 of 1 (latest)
Thank you @topaz parrot
why does a zero invoice an issue for your use case?
We have a usage-based subscription, but the client does not want to store the usage information in Stripe. As the usage information will be downloaded from another system every night into Salesforce, businesses wish to have one or two days to finalize the usage information. Then generate the custom invoice by creating the Invoice item through APIs with Quantity and Unit Amount.
So, the subscription invoice will be always ZERO
Can we void the Zero invoice of Subscription?
Hi ๐ jumping in as my teammate needs to step away soon.
Thank you @chrome coyote
If you're not planning to pass the usage information to us, and are not planning to use the invoices that are generated each billing period, then what functionality of our Subscriptions are hoping to leverage? It sounds like they may not be a good fit for what you're trying to accomplish.
Their customers want to subscribe their products with trail days
As they have the trail product and subscription functionality
as simple checkout does not have the option to pass the trail days, we thought Subscription is the option
Can you elaborate? The main point of our Trials is to postpone the issuing of the first invoice, but if you're not planning to use the invoices that we generate for the Subscription, then that doesn't seem too beneficial. My impression so far is that it'd be better if you modeled the flow you're looking for on your end, and when it comes time to make a payment then you use Stripe for that.
Can we VOID the ZERO amount invoice?
of Subscription
as we are not able to delete it
Yes you can void invoices, the function to do so is here:
https://stripe.com/docs/api/invoices/void
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
but as the subscription invoice is Zero as soon as it finalized the status changes to Pain
Paid
we can't void the paid invoice right?
Stripe will immediately change the customer, once the Invoice Finalized, right?
I will need to double check that.
as its zero amount it automatically changing the status to paid
Can we use the regular checkout without charging the customer?
Yes, Checkout Session have the mode option of setup where they will just collect customer payment information to be used later:
https://stripe.com/docs/payments/save-and-reuse?platform=checkout
We can create the Invoices for this customer without subscription right?
but we can't pass the trial days here, right?
Correct, you can create the Invoices directly, but if you do there is no concept of a trial.
but in our case, we need to pass the trial days. so what would be the best option? kindly suggest
We need the option to Void the ZERO subscription invoice or way to pass the trail days without Subscription
I'm working on running a test to confirm something.
Ok thank you
My testing is showing that the recurring $0 invoices for a Subscription don't automatically finalize, so you can void them during the hour when they're in the draft state.
So I can call /v1/invoices/in_1LFcXmSBqc4wAjJc4T3ls9te/void API to VOID the Invoice during the draft status
I can Void the DRAFT invoice directly without finalization, right
Apologies, I was mistaken. You can't void an invoice that is still in a draft state, nor can you delete invoices associated with a Subscription. I don't think there is a good way with our objects to model what you're looking for. Can you track the trial days on your end?
Do you mean we can't VOID the invoice in DRAFT status?
Yes, apologies, editing my previous message
So, since the monthly Subscription invoice value is ZERO, Stripe will automatically mark the status as PAID as soon as its Finalized. Correct?
Correct
No problem
๐ , Did you see this kind of scenarios earlier?
What shall I do now?๐ which is the best way?
It sounds like it'd be best to track the timing of payments (including the trial period) on your end. The model that you want to achieve doesn't align well with the flow of our objects, so you would need to try to suppress a lot of our default behavior, and then build a bunch of your own logic to map between our structure and yours. At that point it sounds like it would be simpler to model the timing on your end and then use us when it comes time to generate an invoice that you want a customer to pay.
Ok, thank you so much for your time and suggestion. I need to be more practice before I propose the solution.
in Stripe.
๐ ๐
Happy to help!