Two invoices grabbed the same number
A retry. Both customers were understanding and I still did not enjoy the mail. The sequence is locked now. Posting because billing bugs feel private and they should not be.
Comments (4)
I have been adjacent to this. The sentence I would not skip is "Posting because billing bugs feel private and they should not be". Finding who it is for mattered more than adding another feature.
One change, then stop. Address "Both customers were understanding and I still did not enjoy the mail" and leave the rest of the product alone for a week.
Did the conversation in "Both customers were understanding and I still did not enjoy the mail" happen before the build, or only after it launched?
Respectfully, "The sequence is locked now" is an observation, not yet a decision. What number would make you reverse it?
Related discussions
View more- Did you outgrow the first payment provider?
The first integration was fast. Invoices, taxes, and a customer who needs a PO are now the work. I am trying to tell a real limit from ordinary boredom with the dashboard.
Luca MorettiQuestion7 votes7 comments
- Checkout works and the tax note does not
European customers are asking for a VAT line I do not show cleanly. The payment succeeds. The PDF is what they forward to finance, and finance is the one who stalls the renewal.
Tomasz KowalskiDiscussion6 votes4 comments
- A missed webhook marked a paid team as past due
I replayed a Stripe event during a deploy and the handler was not idempotent. A healthy subscription got a past-due email. The fix is in. I am still embarrassed about the note we sent.
Peter NovakDiscussion6 votes4 comments
- The failed-payment email sounds like a scolding
It is accurate and it reads like we are disappointed in them. A card failed. I want the mail to sound like a person who can fix it, not a ledger.