#pl_api

1 messages · Page 1 of 1 (latest)

modest crestBOT
#

đź‘‹ 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/1277828586732261438

📝 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.

stray flower
#

What is "overage"? Do you mean extra charge? If so, there can be multiple ways to do it - using Payment Intent for off session payment, one-time invoice, or bill the one-time invoice item into next subscription

rich pike
#

I understand at least one way to do "one time billing".
Is there a proper way to set the “description” of the invoice to be generated there with stripe (instead of specifying it in the create invoice parameter)?

Is it a good practice to make product, price a temporary payment to set this “description” ? I am asking.
Is it appropriate to use a parameter to specify the description on these invoices in the first place?

stray flower
#

Which description are you referring to here? There are invoice description, invoice item description... etc. Where do you want this description to be shown?

rich pike
stray flower
#

For one-time invoice, the custom description can only be set at the creation request

rich pike
#

Yes, that's right.
What about a policy of creating a dedicated product, price, for this purpose? Would you recommend it?

stray flower
#

As mentioned earlier, it's possible to create a adhoc price with price_data if the price isn't for permanent usage

rich pike
stray flower
#

No. It's temporary

rich pike
stray flower
modest crestBOT