Loomal Index vs Paddle agent transactions vs SaaS billing.
Paddle is a merchant of record running global subscription billing, tax, and compliance for SaaS companies selling to humans. Loomal settles cent-scale, per-call payments from autonomous agents over x402. The transaction shapes are so different that 'versus' mostly means 'and'.
Paddle exists because selling software subscriptions globally is operationally brutal — tax registrations, currency handling, invoicing, renewals, dunning. As merchant of record, it absorbs that so SaaS companies can just ship.
Loomal exists because a new buyer showed up that subscription machinery was never designed for: AI agents that need one API call or one tool invocation, will pay a few cents for it right now, and will never sign up, store a card, or renew anything. This page maps where each belongs.
What Paddle does well
Paddle acts as merchant of record for SaaS and software companies selling subscriptions worldwide. That's the maximal version of 'handling payments': Paddle is the legal seller, so global sales tax, compliance, invoicing, and recurring billing land on its books rather than yours. For a software business with human customers in many jurisdictions, that offload is the entire value proposition, and it's substantial.
If your revenue is plans bought by people, Paddle-class infrastructure is the standard answer for a reason.
Where recurring billing meets agents
Now run an agent through that machinery. It has no legal identity to put on an invoice, no card to store, no inclination to subscribe — it has a task that needs your endpoint four times, today only. Checkout pages and recurring plans simply don't parse for that buyer.
The unit economics fail independently: card-rail transactions carry fixed costs that make a $0.03 charge absurd, which is why human-facing billing aggregates usage into monthly invoices. Aggregation requires the standing account relationship that agents, by nature, don't form. Whole categories of agent demand are unbillable on this infrastructure — not poorly billed, unbillable.
What Loomal adds
Loomal settles the transaction shape Paddle doesn't: single calls, paid by machines, at cent scale. Over x402, the agent's request gets an HTTP 402 carrying your price; it pays in USDC, settlement finalizes on Base in about two seconds, and your handler executes only after the money clears. No invoices, no renewals, no dunning — and no chargebacks, since settlement is final and every payment carries an Ed25519-signed receipt.
Prices start at $0.01 per call and reprice in one field. Loomal's fee is 5% on settled transactions, currently waived. The compliance surface is correspondingly different — these are per-call digital settlements, not card-network subscription commerce.
Side by side
Buyer: human account holders versus autonomous agents. Revenue shape: monthly and annual recurring versus per-call, settled instantly. Rails: card networks with merchant-of-record structure versus USDC on Base over x402. Failure modes: involuntary churn and chargebacks versus a payment that either clears in seconds or the call doesn't run. Minimum viable transaction: practically dollars on card rails; $0.01 on Loomal.
Each column is a poor fit for the other's buyer — which is exactly why this isn't a migration decision.
Both, in the same business
The realistic architecture for a 2026 API or tool business: Paddle (or a peer) bills your human-facing plans, and a Loomal listing exposes the same capability to agents at a per-call price. The agent revenue is incremental — traffic that could never convert through a checkout — and it requires no change to your existing billing stack. List the endpoint, set the price, and the buyer type your MoR can't see starts paying you.
FAQ
Is Loomal a replacement for Paddle?
No. Paddle is merchant-of-record infrastructure for human-facing SaaS subscriptions with full tax and compliance handling; Loomal settles per-call x402 payments from AI agents. They serve different buyers and transaction sizes, and a software business with both audiences would sensibly run both.
Does Paddle support x402 payments?
Paddle's platform is built around card-based subscription billing as merchant of record. As of mid-2026 we're not aware of x402 or per-call stablecoin settlement in its offering — check Paddle's own documentation for the latest.
Can a billing platform just add agent payments?
The hard part isn't will, it's architecture: merchant-of-record billing presumes accounts, invoices, and card rails with fixed per-transaction costs, none of which fit anonymous machine buyers paying cents per call. x402 starts from the opposite premises — HTTP-native, per-call, final settlement in USDC on Base.
How does tax work on Loomal transactions?
Loomal is not a merchant of record — sellers remain responsible for their own tax treatment of x402 revenue, and each settled call has an Ed25519-signed receipt to support records. If MoR handling matters for your human-facing sales, keep a platform like Paddle for that channel.
Bill the buyer your MoR can't.
List your API or MCP server and collect per-call USDC from agents.