mkato_best-practices | Stripe Developers | Page 1

spare mesaBOT Feb 21, 2025, 2:24 AM

#

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

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

#

blazing berry Feb 21, 2025, 2:44 AM

#

Hi, we have a Send Invoice API: https://docs.stripe.com/api/invoices/send?lang=go

Stripe API Reference

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

tardy fjord Feb 21, 2025, 3:33 AM

#

Thank you for pointing out the Send Invoice API. However, our understanding is that this API does not allow specifying an alternative email address—it always sends the invoice to the customer’s registered email.
Could you please confirm if this is correct? If so, is there an alternative approach or best practice for implementing a dry-run test for invoice emails?

#mkato_best-practices