The basis-point figure on a stablecoin provider's pricing page rarely matches the invoice, because mint fees, burn fees, spread, and issuer fees usually live below the line the marketing page shows.
A mint fee of zero looks generous until the redemption fee shows up three lines down the same schedule. Zero Hash's own fee schedule is the clearest public example of why a headline rate and the actual invoice rarely match.
A 2026 comparison of major providers, a support-article listicle rather than an industry report or any single company's own pricing page, groups stablecoin API pricing into three shapes: volume-tiered take rate, per-transaction-plus-gas, and flat enterprise contract.
BlindPay publishes itemized quotes per corridor instead of a blended rate or a sales-only contract; see the pricing page for the current numbers.
Volume-tiered take rate is what most consumer-facing platforms use: a percentage per transaction that compresses as monthly volume grows. This shape rewards scale and punishes small integrations, since a low-volume developer pays near the top of a provider's published range while a large one negotiates down.
Circle prices closer to a flat per-call fee, with network gas passed through separately as its own line, a shape usually called per-transaction-plus-gas. The effective rate depends on network congestion as much as on the provider's own pricing sheet, and it can swing week to week for reasons that have nothing to do with the integration itself.
Flat enterprise contract is the shape Eco, BVNK, and Fireblocks lean toward for larger customers: a negotiated monthly or annual fee independent of transaction count, with the number only surfacing after a sales conversation, which makes it the least useful shape for a developer trying to compare options early.
None of these is objectively cheaper. A high-volume payments company probably wants the tiered rate because it compresses with scale. A team running unpredictable, spiky volume through a handful of chains might prefer the gas-plus-fee model because it doesn't punish quiet months. What matters is knowing which shape is being quoted before comparing it to anything else: a 0.3 percent take rate and a "$0.02 per call plus gas" quote aren't the same kind of number, and they don't compress the same way as volume grows.
Zero Hash's documentation lists 0 basis points to mint across seven supported stablecoins: DAI, TUSD, USDC, USDT, USDP, PYUSD, and RLUSD. Minting, in plain terms, is depositing fiat and receiving stablecoin back. It's free at the issuer level across the board.
Burning is the reverse: converting the stablecoin back into fiat, and that's where the fee shows up. Zero Hash charges 5 basis points specifically on USDC redemption, across every network it supports. The platform sitting on top of Zero Hash can then layer its own spread on top of that issuer fee, the docs' own worked examples run anywhere from 10 to 50 basis points depending on the scenario, and can choose whether to pass the issuer fee to the end customer or absorb it.
An issuer wants stablecoin supply to grow, so there's no reason to tax the deposit side. Redemption is the step that actually costs money to process on the issuer's end, since it means converting the token back to fiat and moving real dollars, so that's where the fee sits. Comparing only the mint-side rate a provider quotes means comparing the free half of the transaction and ignoring the half that actually costs something. This is the same asymmetry that makes stablecoin API pricing pages harder to read than they look: the number on the landing page is usually the cheap half of the flow.
Zero Hash's quote response returns issuer_fee_rate, issuer_fee_amount, spread_notional, and spread_bps as four separate fields. That's the standard worth asking every provider to match: it's the only way to tell what's actually changing when a rate moves. If a provider raises its take rate next quarter, an itemized quote shows whether that's the issuer fee moving (out of the platform's control) or the platform's own spread widening (very much in its control).
One blended rate doesn't automatically mean overcharging. It might be cheaper. But that's not verifiable from the API response alone, and there's no way to build alerting or reconciliation against a number that can't be decomposed. Zero Hash's docs also note that the only supported settlement_type is "STANDARD," described as instant settlement, so at least on that provider there's no separate tier to price against: the itemization is about fees more than settlement speed.
Almost nobody publishes a dated, reproducible quote for a specific corridor and a specific amount. Pricing pages show ranges, sales calls produce numbers that expire the moment the call ends, and aggregator comparisons average across providers in ways that erase exactly the detail that matters for a given integration. Conduit's FX pricing is sometimes cited around 10 basis points in industry writeups, and even that number comes through a third-party aggregator rather than a dated quote that could be reproduced directly. That figure could not be independently verified against Conduit's own current pricing documentation, which is itself the point: transparent, reproducible pricing is rare enough in this space that even finding a citable number takes real digging.
A real comparison holds the same notional amount, the same day (FX and spread both move daily), the same network the transfer settles on (gas depends on chain and congestion), and itemized fees rather than a blended total. Without holding all four constant, the comparison is really between marketing copy from different months. The best stablecoin APIs comparison applies this same standard across providers side by side.
A BlindPay quote splits the FX spread from the payout fee into two numbers, showing what the conversion costs and what the transfer costs separately, and which one moved when a rate changes. There's no pre-funding requirement sitting underneath any of it, either: no capital needs to sit parked in a destination account before a payout clears, which erases trapped capital as a cost, something a lot of pricing comparisons skip because it never shows up as a line item at all.
For a corridor like USDC to BRL, or for payin and payout flows more broadly, the getting started guide walks through what a live quote actually returns, field by field. Pull a same-day quote against the real volume and corridor before trusting any published rate, including this one, and to get the fees broken out against a real amount, talk to us.
Ten stablecoin APIs compared for 2026: BlindPay, Circle, Bridge, BVNK, Fireblocks, Crossmint, Zero Hash, Conduit, Sphere, and Borderless, across rails, custody, pricing, and compliance.
XRP is not a stablecoin: its price floats freely with the market. Ripple's actual stablecoin is RLUSD. Here is how the two differ and why it matters.
USDC offers stronger reserve transparency and US regulatory posture; USDT offers deeper liquidity in emerging markets. Most payment flows should support both.