Revenge of the double billing
As I’m sure you’re aware, Monday morning’s billing batch processed twice. As soon as we realized this we ran a batch to void the duplicate transactions. We thought this solved…
As I’m sure you’re aware, Monday morning’s billing batch processed twice. As soon as we realized this we ran a batch to void the duplicate transactions. We thought this solved the issue, but we were wrong.
Today I got a report that a user’s card was in fact billed twice. Upon further investigation it appears our void batch missed a small handful of users. Specifically, users whose card had declined in a previous batch and were being retried did not have the duplicate charge voided. I have gone through each of these customers by hand and refunded the duplicate transactions.
I’d like to urge everyone who received receipt emails on Monday to double-check with your bank that only one charge has processed through. If the duplicate did post, please don’t hesitate to contact support so I can ensure that a refund has been issued.
I can’t apologize enough for this, we’re really sorry folks.
Written by
Related posts
GitHub for Nonprofits: Drive social impact one commit at a time
Now, it’s easier than ever for nonprofits to receive GitHub product discounts.
Career growth, learning, and fun, oh my! Your guide to GitHub Universe 2024
Dive into a whirlwind of insights, inspiring sessions, and mingle with industry leaders at this year’s Universe. Get your tickets now before they’re gone!
GitHub Availability Report: September 2024
In September, we experienced three incidents that resulted in degraded performance across GitHub services.