I had one of those moments that makes you question not only your software stack, but also reality itself.
I was setting up a Stripe product and wanted to charge different fixed amounts for different currencies. Nothing fancy. Just normal regional pricing. For example, one amount in GBP and another amount in USD.
I typed in US$43.50.
Then I looked again.
Stripe was apparently showing US$4.00.
At that point, several theories presented themselves.
- Maybe Stripe had decided that manual pricing was illegal.
- Maybe there was some hidden anti-FX-arbitrage feature.
- Maybe global finance had collapsed and nobody told me.
- Maybe I had discovered a new kind of SaaS business model: accidental charity.
Naturally, I started doubting Stripe.
Then I started doubting the browser.
Then I started doubting myself.
The actual problem was much dumber, which is usually how these things go.
It was Dark Reader.
Dark Reader had changed the background color of the Stripe dashboard in a way that made part of the number visually blend into the background. So the value looked wrong even though it was actually fine. I switched browsers, looked again, and there it was: the number had been correct the whole time.
So the problem was not:
- Stripe rejecting my pricing
- Stripe auto-correcting for FX
- some secret pricing policy
- my inability to understand numbers
It was just a browser extension doing creative reinterpretation of a payment interface.
There is something very humbling about spending time investigating a financial configuration issue only to discover that the real root cause is “my dark mode plugin made the text camouflage itself.”
The lesson
The lesson is straightforward:
If you are doing anything serious in a dashboard involving money, taxes, infrastructure, domains, or production settings, use a clean browser profile first.
Not because extensions are bad. Extensions are useful. But some of them are apparently bold enough to become co-founders of your debugging session.
Dark Reader is excellent in many places. Stripe’s dashboard, on that particular day, was not one of them.
So if a payment system ever appears to turn $43.50 into $4.00, before writing a long internal memo about broken fintech UX, try this first:
Open the page in another browser.
It may save you from investigating the collapse of modern commerce when the real issue is just CSS in a trench coat.