#jayswebay-areahello_api

1 messages ¡ Page 1 of 1 (latest)

oblique wrenBOT
#

👋 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/1371915097513136138

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

shy holly
#

hello! i am not aware of a way to do that, but let me look into it

lethal hinge
#

Thank you!

shy holly
lethal hinge
#

maybe with customer emails enabled? Will this automatically send the customer invoice that they need to pay to their email every month/year?

#

yes i believe so, or we set collection_method to charge_automatiically but allow a way for the user to pay by invoice

#

i'm pretty sure this isn't supported in checkout so using the subscription API directly might be the best option for now

  • is there a way to indicate this on the UI? Currently when the user clicks on "subscribe now" to one of our product, we just create a stripe checkout with the product + price id and collect the payment information there. However, with the stripe subscription API, i am not sure how to display such information (price, etc.) to the user on the UI
shy holly
#

when using the subscription API you have to display all of that info yourself

#

there are a bunch of ways you can handle it when using the API - you can just collect the customer's info (email etc), then create the subscription and send the invoice. or you can collect payment info via our elements

#

but as for displaying the price, products etc, all of that would need to be handled by your integration

lethal hinge
#

i see, but what happens when we set collection_method = send_invoice? Does the customer get their invoice emailed every month/year (depending on the price duration)?

Also what happens if they fail to pay on time or their payment fails, is there a way for us to know that and stop them from using their subscription?

shy holly
#

ok, i'm thinking through other options here - one would be to create your checkout session, collect the intial payment, then update the subscription to have collection_method: "send_invoice"

#

with that you would collect the initial payment and then future payments would be handled via invoice

shy holly
# lethal hinge i see, but what happens when we set collection_method = send_invoice? Does the c...

from our docs on subscription status:

If subscription collection_method=send_invoice it becomes past_due when its invoice is not paid by the due date, and canceled or unpaid if it is still not paid by an additional deadline after that. Note that when a subscription has a status of unpaid, no subsequent invoices will be attempted (invoices will be created, but then immediately automatically closed). After receiving updated payment information from a customer, you may choose to reopen and pay their closed invoices.

lethal hinge
shy holly
#

with that option you would do exactly what you're currently doing - creating the checkout session, which collects payment and charges, and then after the subscription is created and paid for you would update it to send invoices. so no, the original payment would be charged automatically and not via invoice.

#

if you want the whole subscription to be invoices from end to end you'd probably be better off using the API

#

which unfortunately removes the benefit of us displaying price + products.

oblique wrenBOT
lethal hinge
#

Ah I see, what about invoice_creation.enabled option in the stripe checkout, would that allow for the initial payment (one time) to be payid by invoice then we can switch to this method afterwards ?
then update the subscription to have collection_method: "send_invoice"

shy holly
#

nope - that just sends a "paid" invoice after the fact - the initial payment is still charged automatically

lethal hinge
#

ah okay sounds good

#

Thank you for the help

shy holly
#

yep of course! i also think this makes sense as a use case to flag with our product team to see if maybe we can get it built out in the future, so i'll go ahead and do that for ya

lethal hinge
#

thank you, please let me know if this will be something that will be implemented in the future, that'd be amazing!