#DuckHunter-email-invoices
plain compass
Is there any way this could be added to the backlog? This is a fairly major feature that would benefit our business. We plan on using Stripe for all of our payment processing/invoicing... Being able to proactively identify bounced emails instead of making phone calls after the invoice is past due would save us money.
wispy dust
That's totally valid feedback. I would recommend opening a thread with Support and mentioning that you want to put in a feature request. They have workflows for getting these to the product team: https://support.stripe.com/contact/email
plain compass
Awesome. Thanks! I put in a ticket
I appreciate your help!
I see Rubeus popped into the thread 👀
azure nova
Hello! I'm taking over for @wispy dust and joined all the active threads. 🙂
I think the approach above is a good one, but I'm curious about something... do you have an Invoice where the email bounced so I can take a look?
plain compass
I think the approach above is a good one, but I'm curious about something... do ...
I'm not 100% certain if this bounced or not, but as you can see the email where the invoice was sent had a typo in it. I'm assuming that the email doesn't exist, but it is @gmail.com so who knows if it does or not. in_1KoZb2IwAB4IGzVxre81IFRU
We ultimately voided this invoice and sent a different one: in_1KtEutIwAB4IGzVx44jdgHVL
Here is another example of an email typo: in_1Krq9JIwAB4IGzVxZXPBRRlh
old acorn
👋 Rubeus isn't available at the moment but I'm taking a look for whether anything will indicate it bounced
plain compass
Awesome! I appreciate it
visual shard
@plain compass Unfortunately that's not really something we can investigate on our end. I'd recommend working directly with our support team for help: https://support.stripe.com/contact
We don't surface "email bounces" and it