DEV Community

Keshav Sharma
Keshav Sharma

Posted on Originally published at settlematic.com

SaaS crypto invoicing: usage meters still need an address per invoice

SaaS billing is a state machine: trial, usage, invoice, dunning, tax. Crypto does not remove that. It adds finality and chain IDs.

Do not bolt a wallet onto Stripe’s mental model

Stripe can reverse. Chains do not. Your “refund” is a new outbound you sign, or a credit on the next invoice. If a vendor offers “crypto with chargebacks,” they are sitting in the middle (custodial) or lying.

Usage → invoice

Meter in your app. Emit an invoice in USD. Lock a USDC rate for a window. Bind an address. Webhook invoice.paid into entitlements. Do not wait for a human to paste a tx hash into Metabase.

Recurring is just that loop on a schedule. Recurring does not require the vendor to hold a balance of your customers’ USDC.

Settlematic Collect covers the invoice object and matching. Gateway is sandbox — do not design production checkout on it. Wire webhooks properly or do not bother (we already wrote that one).

Canonical: best crypto invoicing for SaaS. settlematic.com

Top comments (0)