How it works
Both the buyer and the vendor independently compute the same nonce from the same invoice metadata. No external registry is required to coordinate payment. The nonce is derived deterministically:Settlement flow
- Invoice issued — the vendor creates an invoice with a unique number, amount, and due date.
- Nonce computed — both parties independently derive the same nonce from the invoice metadata.
- Buyer signs — the buyer signs an ERC-3009 authorization off-chain using the deterministic nonce. The
validBeforefield can be set to the due date plus a grace period. - Settlement — the buyer or vendor submits
transferWithAuthorizationon-chain. Settlement confirms in under a second. - Reconciliation — the emitted
AuthorizationUsedevent contains the nonce, linking the on-chain settlement to the exact invoice. TheTransferevent in the same transaction verifies sender, recipient, and amount.
Double-payment prevention
The nonce is consumed on-chain upon payment. The same invoice cannot be settled twice — resubmitting an authorization with an already-used nonce reverts.What makes it different
Traditional B2B invoicing involves bank wires (1–5 business days), manual reconciliation, and no cryptographic proof of payment tied to the invoice itself. With deterministic nonces, the on-chain payment is self-documenting: the nonce links the settlement to the exact invoice, and the blockchain event log provides an immutable audit trail.| Aspect | Traditional (bank wire) | Stable (ERC-3009) |
|---|---|---|
| Settlement | 1–5 business days | Under 1 second |
| Reconciliation | Manual matching against bank statements | AuthorizationUsed event links payment to invoice nonce |
| Payment proof | Bank confirmation letter | On-chain transaction, cryptographically linked to invoice |
| Intermediaries | Correspondent banks | None |
| Fees | Wire fees ($15–45) + FX spread | ~0.00021 USDT0 (or 0 with Gas Waiver) |