A payment processor is optimized for checkout conversion. An invoicing stack is optimized for reconciliation. Both can be custodial or not. Mixing the two in a vendor comparison is how you buy the wrong thing.
Processor job
Accept a payment in 15 seconds, emit payment_intent.succeeded, maybe settle to fiat. Shared deposit pools, aggressive fee take, KYC on the merchant, sometimes on the payer. Fine for SaaS self-serve. Terrible if your AP team needs invoice #1847 matched to a USDC transfer on Polygon with a PO number.
Invoicing job
Issue a receivable, survive a 14-day wait, accept partials or not, export to QuickBooks, survive an auditor asking why 12 clients paid “the same wallet.” Unique addresses matter more than a pretty pay modal.
Custody still dominates the risk
A non-custodial processor (rare) still has to solve gas, finality, and refunds without holding keys. Most processors do not try. They take custody, because refunds and FX are easier when they sit in the middle.
A non-custodial invoicer can refuse to be in the middle: unique address, watch-only, you settle yourself. Refunds are a new invoice or an outbound you sign. That is operationally heavier and legally cleaner.
How to shop without a feature matrix lie
Do not rank “supports USDC” as a differentiator. Everyone does. Rank:
- Custody model (keys, sweep, float)
- Per-invoice address vs pooled
- Fiat quote + rate lock
- Webhook authenticity (HMAC, not a guessable URL)
- Whether gateway and invoicing are the same product or two SKUs
Settlematic is invoicing first (Collect, live) and a payment gateway second (sandbox). We are not a custodial acquirer. If you need card + crypto + instant fiat, that is a different vendor class.
Canonical: custodial vs non-custodial crypto payment processors. settlematic.com
Top comments (0)