#changpet_payment-links-vs-invoicing

1 messages · Page 1 of 1 (latest)

small cloudBOT
#

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

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

versed swan
wind hazel
#

req_NthJG8btCX5RUB

versed swan
#

You're possibly on an older API version that doesn't support passing in price_data on line_items param

small cloudBOT
versed swan
#

Yeah you're on 2022-11-15 and I think support for this was added in Basil

wind hazel
#

What date was Basil released?

versed swan
#

Ad hoc pricing for Payment Links: You can now specify a Price while creating a Payment Link in just one API request.

wind hazel
#

With my current API version, is there an alternative we could do to achieve the same functionality?

grand bloom
#

👋 Hanzo had to head out so I'll be taking over

#

Prior to basil the only option was to pass an existing price.

#

Do you have any concerns regarding upgrading to a newer API version?

wind hazel
#

Yeah I'm looking into this now and checking the breaking changes from each version from our current one leading up to basil. Also, I see there is an even more recent version called Clover? Would you recommend just upgrading to Basil for now?

#

And yes, have some concerns when upgrading. What would be the best aproach to making sure there are no breaking changes that would affect our stripe integration? We use subscriptions, payments, webhooks, etc

#

Also, do you have to upgrade to the latest version available? On the workbench I see I can only upgrade to Clover.

Screenshot_2025-11-11_at_4.01.54_PM.png
grand bloom
#

I think it might make the most sense to read through the breaking changes from each major release, and if nothing stands out as worrying, create a sandbox using the next major release to test that all continues to work as desired.

#

The most common rough edge with basil would be the change to partial invoice payments.
https://docs.stripe.com/changelog/basil/2025-05-28/partial-payments

The many to one relationship replacing the one to one relationship means it's not as simple as looking at an invoice property on a Payment Intent to determine what invoice it was assocaited. Same in the other direction.

wind hazel
#

Thanks, is there anything else in the api that would allow us to send a one time payment sheet to a user so they can pay the amount? We're looking into allowing our connect account users to add funds to their account. Our original plan was to use the payment links api, create a payment that they would pay using the payment link url, which would send that amount to our platform account, and then we would transfer that amount to the connect account using the transfer api. If we didn't upgrade our version right now, is there any other part of the api that would allow us to achieve this functionality? Maybe the invoices api?

grand bloom
wind hazel
#

Okay, yeah was taking a look at the invoices api, seems like we could create the invoice through api, and also send the invoice url for manual payment. Wondering what the differences between invoices and payment links are exactly? Also, how do fees apply for invoices and payment links, are they the same for both? Is there any negatives you can see in using the invoices over payment links

grand bloom
#

Payment Links are re-useable and can be sent to many people. In my mind stands out as the biggest difference.

small cloudBOT
wind hazel
#

Thanks, will try the invoices api out and will reopen this if other questions come up

grand bloom
#

Excellent, we're always here : )

wind hazel
#

Appreciate it. A question that just came up. My previous explanation of what we plan to do to handle adding funds to a connect account. Was going to transfer the paid invoice to the connect account after the invoice is paid. Is there a way to handle that directly within the invoice api? Can we have the invoice be paid and tranferred to the connect account in one step?

proper steppe
#

Hi there,
taking over for my colleague who had to step away.
If you want to transfer funds automatically to the connected account when the invoice gets paid, you can use the transfer_data parameter when creating a Payment Intent or Invoice

wind hazel
#

If the invoice is set to send_invoice instead of charge_automatically, and we set the days_until_due. If the invoice is not paid within those days, I'd like to have the invoice be closed and not try to retry sending the invoice to the customer. Do you know where that can be configured? Is there somewhere that can be changed on the dashboard or set via the api call?

proper steppe
#

For one-off invoices, you can set Invoice reminders and set retries in the dashboard under Settings->Billing->Invoices at the very bottom