Every month, a significant portion of revenue was disappearing before it ever reached the treasury. Not to fraud. Not to intentional churn. To billing infrastructure fees — a silent tax on every successful payment.

At $400,000 in monthly recurring revenue, a standard custodial billing fee of 3% costs over $12,000 per month. That is $144,000 per year paid to infrastructure that adds no product value and introduces counterparty custody risk on top of the fee.

This is the economic reality of custodial billing for Web3 SaaS products whose users hold USDC. You are running a crypto-native product through fiat-era infrastructure — and paying fiat-era margins for it.

The Problem With Custodial Billing for Crypto-Native Teams

When you use custodial payment infrastructure to bill crypto users, you introduce a structural mismatch. Your users hold USDC in self-custodied wallets. But collecting a recurring payment forces them through a processor's custody layer — one that charges a percentage, introduces settlement delays, and requires trusting a third party with your revenue flow every billing cycle.

The custodian takes a cut. Every month. On every transaction. Without exception. And that fee is baked into your unit economics in a way that is easy to normalize and very difficult to see clearly until you do the annual math.

$12,400
Monthly custodial fees at $400K MRR
$2,000
AuthOnce fees at same MRR
$124,800
Annual saving returned to treasury

Fee Comparison Across MRR Levels

The math scales linearly. Here is the comparison at four common MRR levels, using a 3% custodial fee and AuthOnce's hardcoded 0.5% protocol fee plus 0.5% application fee:

Monthly MRRCustodial (3%)AuthOnce (1% total)Monthly SavingAnnual Saving
$10,000$300$100$200$2,400
$50,000$1,500$500$1,000$12,000
$100,000$3,000$1,000$2,000$24,000
$400,000$12,000$4,000$8,000$96,000

These figures use a conservative 3% custodial rate. Many processors charge additional per-transaction fees, which push the effective rate higher on smaller ticket sizes.

Protocol Transparency

AuthOnce's 0.5% protocol fee is hardcoded and immutable in executePull(). It cannot be changed by governance, operations, or any admin function. Every fee collection is recorded on-chain and independently verifiable.

Non-Custodial Billing: How It Works

AuthOnce is a non-custodial USDC subscription billing protocol built on Base Network. When a subscriber authorizes a subscription, they sign an EIP-2612 permit — a cryptographic authorization that requires no gas and no pre-approval transaction. No funds move at authorization. No custodian holds anything.

On each billing cycle, the Keeper executes a pull payment directly from the subscriber's wallet to the merchant's wallet. The full settlement flow runs on-chain. The merchant receives USDC directly. Nothing passes through a third-party custodian.

For a full technical breakdown of the authorization model, see our article on EIP-2612 gasless subscriptions.

The Churn Problem That Gets Solved Automatically

Fee reduction was the primary goal. What many merchants do not anticipate is how much the programmable grace period changes subscriber retention.

In custodial billing, a failed payment is often binary. The charge fails. The subscription cancels. The subscriber churns — frequently involuntarily, because of a wallet balance timing issue rather than genuine intent to cancel.

AuthOnce implements a 1–30 day programmable grace period, configurable per merchant. If a pull payment fails, the subscriber retains access during the grace window. The protocol retries automatically. Most subscribers top up their wallet and continue without ever noticing the issue.

Involuntary churn from failed payments drops significantly after migration. Revenue that would have been permanently lost is recovered automatically, on-chain, without manual intervention.

Integration Timeline

The WooCommerce plugin connects in under two hours. Merchant dashboard setup takes minutes. Vanity pay links at pay.authonce.io/yourhandle go live immediately after merchant registration. For custom integrations, the protocol contracts are open source and available via the AuthOnce developer portal.

What This Means at Scale

If your users hold USDC, you should be billing in USDC. The infrastructure now exists to do it non-custodially, at a fraction of the cost, with better subscriber retention built directly into the protocol.

The economics of subscription billing have shifted. For Web3 SaaS products, DAOs, and digital-native subscription businesses, the question is no longer whether to move to non-custodial USDC billing — it is whether to do it before or after competitors do.

For the compliance posture that makes this possible without regulatory exposure, see our article on USDC billing compliance and the software-only legal stance.

Run the numbers for your MRR

AuthOnce is live on Base Sepolia. Mainnet launches Q3 2026. Integration takes under two hours.

Start with AuthOnce Full Cost Framework →