If a vendor can sign a move of your client’s payment before it hits a key you control, you are in a custodial invoicing flow. Marketing copy about “non-custodial” does not change that.
Two stacks that look the same in a screenshot
Both show a QR, an amount, and a countdown. The difference is who holds keys between “paid” and “in your treasury.”
Custodial invoicing: payer sends to a vendor-controlled deposit address. Vendor credits an internal ledger. Later, a payout, net of fees, maybe in a different asset. You have a balance in their UI. Chargebacks are rare in crypto, but freezes, delayed withdrawals, and “we’re reviewing this tx” are not.
Non-custodial invoicing: the invoice address is derived or deployed such that the intended recipient is you (or a contract you control) from the first confirmation. The vendor watches. They do not sweep. They do not have a withdrawal queue.
Why invoicing is stricter than a checkout widget
Invoicing is B2B, often 30-day terms, often auditors. “We got paid into a processor and we’ll wire you Friday” is a working-capital product. If that is what you bought, say so. Do not call it non-custodial.
Temp-wallet-plus-sweep is still custody. The sweep is the tell: if they must move funds to deliver them, they held them.
What to ask a vendor
- Who can sign the first outbound from the deposit address?
- Is the address unique per invoice and bound at issuance?
- Do you ever batch, convert, or hold to cover gas?
- If your company disappears at block N, is my money already on an address I control?
If answers 1 and 4 are “us, and no,” you have a custodian with invoices.
Settlematic’s Collect product is built for the second stack: invoice-scoped addresses, watch-only verification, settlement to you. Gateway remains sandbox. No SOC 2 claim here — that work is in progress, not done.
Canonical: custodial vs non-custodial crypto invoicing. settlematic.com
Top comments (0)