Home › Blog › Two vendor price drifts and a broken cost table

Two Vendor Price Drifts and a Broken Cost Table — This Week's Audit Pass

13 November 2026 · Site Methodology & Corrections · 5 min read

We run a standing audit that works through every page on this site, one at a time, re-checking numbers against the vendor's own current pricing instead of trusting whatever we wrote down last time. This week's batch turned up four real mistakes on pages most people never think twice about: a payment processor, an exchange, and our own token calculator.

Adyen: a fee that was 15% too low

Our Adyen page quoted the interchange++ processing fee at roughly €0.11 per transaction. Adyen's own pricing page, cross-checked against a MerchantMaverick review of the same plan, puts the current fee at €0.13. That's not a rounding difference — it's the actual markup Adyen charges on top of interchange and scheme fees, and we had it 15% low.

月間ボリュームOld number (€0.11)Real number (€0.13)違い
10,000 txns€1,100€1,300€200
100,000 txns€11,000€13,000€2,000
1,000,000 txns€110,000€130,000€20,000

That table is just the fixed processing fee — it doesn't include interchange or scheme fees, which Adyen passes through separately. But at real Adyen-scale volume (this is a processor built for businesses doing six-figure-plus transaction counts, not side projects), a 15% miss on the one number we control compounds into real money.

Binance: the futures taker fee was 20% too low

の Binance API page listed the USDⓈ-M futures taker fee at 0.04%. Binance's own fee schedule and a third-party tracker (cryptowisser.com) both show the base VIP0 taker rate is 0.05% — a fifth higher than what we had. We re-verified the rate-limit figures on the same page live against api.binance.com/exchangeInfo (6,000 request-weight/minute, 100 orders/10s, 200,000 orders/day) and those matched exactly, so only the fee line needed a fix. Spot trading fees on the page (0.1%) were already correct.

Our own bug: a sweep table that didn't sweep

の words-to-tokens calculator has a "cost at different volumes" table meant to show your monthly bill at 0.1x through 10x your typical word count — useful for seeing what happens if traffic grows. Every row showed the exact same number as the 1x row. 75 words a month and 7,500 words a month both priced out to the same monthly figure, which is obviously wrong the moment you think about it for two seconds.

The cause was a scoping mistake: the sweep loop reused a variable that had already been scaled for the main calculation above it, instead of recomputing the word count fresh for each multiplier. The fix scales the word count inside the loop itself before pricing it. Rows now spread correctly from a fraction of a cent at 0.1x to a proportionally larger number at 10x.

A smaller one: a count that disagreed with itself

私たちの API pricing overview page said "387 models tracked" in the title, meta description and the JSON-LD block, but the Coverage section of the page body still said 395 — a stale number left over from before we trimmed five retired OpenAI models out of the dataset in an earlier pass. No vendor was wrong here, just us: one part of the page updated and another didn't. Fixed to 387 everywhere.

What this is, and isn't

None of these four are dramatic. Nobody lost a production bill over a word-count sweep table. But a 15-20% miss on a vendor's actual fee is exactly the kind of error that erodes trust quietly — close enough to look right, wrong enough to matter if someone budgets off it. The fix in every case is the same unglamorous thing: go re-read the source instead of assuming the number on file is still the number that's true.

Check your own Adyen or Binance costs on the APIコスト計算ツール, estimate a token-heavy workload on the words-to-tokens calculator, or browse the full payment API そして crypto exchange API categories. New to usage-based pricing in general? Start with the 無料の API コストガイド.

Adyen and Binance figures checked against each provider's own pricing/fee-schedule pages plus one independent third-party source each, 13 November 2026. Rate limits verified live against Binance's API. Figures change — confirm current pricing on the provider's own page before budgeting high-volume workloads.