1
8 Comments

I built a no-OAuth Stripe fee auditor from Balance CSVs

Hey IH,

I got tired of the Stripe 2.9% myth.

Like a lot of small SaaS founders, I assumed Stripe was eating roughly 2.9% + $0.30 per transaction. Then I exported my Stripe Balance CSV and did the math.

Between international cards, small transactions, refunds, and other fee lines, my real blended rate was meaningfully higher than the headline number.

Stripe’s dashboard is excellent, but it is not really designed to answer one simple question:

“Why is my actual fee rate higher than I expected?”

So I built Stripe Fee Auditor.

It analyzes an itemized Stripe Balance CSV and shows:

- your processing fee rate vs all-in Stripe cost rate

- which transactions are driving fees up

- refund fee leakage

- unusual high-fee charges

- month-over-month changes

- directional savings opportunities like ACH, local payment methods, or bundling small charges

The privacy angle is important to me, so the product does not use Stripe OAuth and does not ask for API keys. You export the CSV yourself from Stripe and upload it.

Important update from the original prototype: this is no longer a completely offline/browser-only tool. CSVs are sent over HTTPS to the server for analysis so reports can be reopened, emailed, and unlocked after payment. Raw CSV files are not stored; the app stores a temporary derived analysis report, and free-text descriptions are stripped where possible.

So the current promise is:

No Stripe OAuth.

No API keys.

Raw CSV files are not stored.

Temporary derived reports only.

I’m especially curious whether other SaaS founders are surprised by their real effective fee rate. My guess is many are sitting in the 4-6% range and don’t realize it.

Would love feedback, especially from anyone who has international customers, lots of small payments, or frequent refunds.

-Ksantor

posted toAvatar for product Stripe Fee Auditor
Stripe Fee Auditor
  1. 1

    Update: the original prototype was fully browser-only/offline. The current product has changed: CSVs are now sent over HTTPS to the server for analysis so reports can be reopened, emailed, and unlocked after payment.

    Raw CSV files are not stored; the app stores a temporary derived analysis report, and free-text descriptions are stripped where possible.

    Still no Stripe OAuth and no API keys.

  2. 1

    The 2.9% myth is real — I did the same math on a project and got a similar shock. The $0.30 fixed fee on micro-transactions is brutal and nobody talks about it.
    I built a tool that gives AI-powered UX feedback on landing pages. Ran it on feeauditor.com out of curiosity — happy to share what came up if useful. pagepulse.page

    1. 1

      Yes please share! Always curious what AI feedback surfaces on landing pages. And glad the 2.9% frustration resonates — you're one of the first people to actually run it on a real case.

      1. 1

        I can't share screenshots here but this is the main results:
        Overall score 72 (Good)
        Stripe Fee Auditor is a focused, single-purpose landing page with a compelling contrarian hook and clear privacy differentiator (CSV vs OAuth). The value proposition is sharp and relevant, but conversion is hampered by a weak primary CTA label, insufficient visual hierarchy between competing action buttons, and sparse trust signals for a tool asking users to upload financial data. The page tells a coherent story but buries its strongest trust argument (no Stripe access, file processed in memory) in a comparison table rather than the hero.

        Quick Wins

        • 1.

          Move the 4-bullet reassurance strip ('No Stripe API access · Raw CSV never stored · No account required · Results in 30 seconds') to a larger, bolder treatment directly below the CTA — it addresses the #1 objection for a financial data upload tool

        • 2.

          Add one specific social proof metric near the hero (number of businesses analyzed or average savings discovered) — requires no design change, just a single line of copy

        • 3.

          Reframe the beta pricing as time-limited urgency: 'Full report is free during beta' → 'Full report is free right now — locks to paid after launch' to convert fence-sitters

        Critical Issues

        • Zero named testimonials or social proof for a tool asking users to upload Stripe financial data — this is a trust level 3 ask (personal/financial data) with only level 1-2 trust signals present

        • Primary CTA button color (green) is reused in the navigation bar, violating button uniqueness principle — users cannot instantly identify the conversion action by visual style alone

        • No retention or re-engagement mechanism — the entire AARRR funnel terminates at activation with no email capture, account creation, or return path

        1. 1

          This is incredibly detailed — thank you. The trust signal placement point is exactly right, fixing that today.

          Would you be willing to give a one-liner quote I can use as a testimonial? Something like what you wrote: "focused single-purpose tool with a compelling privacy differentiator." Happy to mention your tool in return — just let me know the best way to connect.

          1. 1

            I'm glad to hear that.
            I'll be happy to do it. Please connect me on contact@pagepulse.page

            1. 2

              Perfect, thank you! I’ll reach out at contact@pagepulse.page. Your teardown was honestly super useful - the trust signal placement and CTA hierarchy points were exactly the kind of outside perspective I needed. I already started applying those changes. Happy to use a short quote with attribution, and I’ll gladly mention PagePulse when I post the before/after updates.

              1. 1

                Thank you! I'm glad to hear that you find PagePulse.page useful.
                I can't wait to see how your conversion rate has been changed by the recommendation of PagePulse. I will appreciate it if you will share it.