What Makes Settlematic Different for Crypto Invoicing

Why crypto invoicing became a custody problem

Crypto invoicing sounds simple: send an invoice, receive a payment, mark it paid. The hard part is reconciliation. On most blockchains, a plain wallet transfer carries no reliable invoice reference. Your customer sends 5,000 USDC from Coinbase; your treasury wallet receives 5,000 USDC. Which open invoice did they mean?

The industry default fix is operational custody. Generate a fresh deposit wallet per invoice, watch it, sweep to the merchant when confirmed. Reconciliation works. You also become a custodian for every second between deposit and sweep — regardless of what the marketing page says.

Settlematic was built around a different constraint: reconcile without ever controlling funds. That single design choice ripples through architecture, pricing, compliance posture, and what happens when the platform has an outage. If you are evaluating vendors, start with the question of who can sign a transaction that moves your customer's payment. Everything else — UI polish, chain count, webhook schemas — is secondary to that answer.

Non-custodial is not a footer disclaimer

Regulators and bankruptcy courts treat custody as control, not as marketing language. If your provider can move funds, stop you from moving them, or hold information without which funds are unreachable, you have dependency risk — even when nobody stores a full private key.

Settlematic applies a three-question test to every settlement design:

Invoice-scoped addresses in Settlematic are address-bound at issuance: the deposit address is derived from your settlement configuration (BIP-84 watch-only derivation on Bitcoin; CREATE2 counterfactual addresses on EVM chains) such that incoming value is cryptographically routed to wallets you control. Settlematic indexes confirmations and updates invoice state. It does not sit in the settlement path.

For a deeper regulatory framing, see our guide on custodial vs non-custodial crypto invoicing.

Invoice-scoped addresses without temporary wallets

Unique addresses per invoice are table stakes for automated reconciliation. The difference is who holds the keys to those addresses.

Custodial invoicing: deposit keys belong to the platform. Non-custodial address binding: deposit addresses are derived from your extended public key or factory configuration; the platform never possesses signing material.

On Bitcoin, Settlematic uses BIP-84 hierarchical derivation from a merchant-provided account-level xpub. Each invoice receives the next child index — allocated transactionally, never reused. On EVM networks, CREATE2 counterfactual deployment computes the deposit address from a factory and invoice salt, with the merchant treasury baked into init code.

Read the mechanics in invoice-scoped wallet addresses explained. The pattern matters because it is the technical reason Settlematic can offer automated matching without operating as a payment intermediary.

Flat subscription pricing vs percentage take-rates

Payment processors often charge 0.5%–1.5% of volume plus network passthrough. That model aligns the vendor with your growth — and penalizes high-ticket B2B invoices.

Settlematic charges a flat monthly subscription with no percentage of settled volume. A $50,000 USDC invoice and a $500 invoice cost the same in platform fees. For agencies, SaaS vendors, and consultancies billing five- and six-figure statements, that difference compounds quickly.

Compare plans on pricing or walk through a live invoice on demo.

Fiat-quoted invoices, crypto settlement

B2B buyers think in dollars, euros, or dirhams — not in "how many USDC at this second." Settlematic invoices can be denominated in fiat while settlement occurs in USDC, USDT, EURC, ETH, or BTC across Ethereum, Polygon, BSC, Solana, Tron, and Bitcoin.

Exchange rates lock for a configurable payment window. Webhooks deliver both the target fiat amount and the settled crypto amount, supporting gain/loss accounting without manual spreadsheet work. Finance teams can keep AR in functional currency while treasury receives stablecoins — a common pattern for international contractors and SaaS companies billing globally.

Multi-chain support without becoming a custodian

Supporting six networks multiplies reconciliation complexity. Custodial stacks pool liquidity and internal ledgers. Settlematic instead runs watch-only indexers per chain, applies per-chain finality thresholds, and matches transfers to invoice-scoped addresses.

Customers paying from centralized exchanges send plain transfers — no contract calls required — which matters because a large share of real-world B2B crypto payments originate on exchanges. Your pay page can restrict assets and chains per invoice so treasury ops stay predictable.

Webhooks, audit trails, and finance-team ergonomics

Crypto-native founders sometimes underestimate how much finance teams need deterministic records. Settlematic fires signed webhooks on confirmation, partial payment, overpayment, and expiry events. Each event ties an on-chain transaction hash to an invoice ID, payer address, token, chain, and amounts in both crypto and quoted fiat.

That is the difference between "we think they paid" and "our ERP auto-closed the receivable." Hash-chained audit logs give compliance and security reviewers a tamper-evident trail without asking you to trust a black-box ledger inside the vendor's database.

KYB without turning invoicing into a bank

Merchant KYB/KYC workflows help B2B teams present a professional compliance posture to enterprise buyers. Settlematic supports optional verification flows without converting the product into a custodial money transmitter. You remain the merchant of record; settlement still lands in wallets you control.

KYB is about who you are as a counterparty, not about the platform holding float on your behalf. That distinction keeps procurement conversations focused on your business credentials rather than on whether your invoicing vendor is also your custodian.

Smart invoices: discounts, late fees, and payment terms

Traditional invoicing tools encode payment terms in PDF footers. Settlematic smart invoices encode terms in the payment object: early-payment discounts, late fees, due dates, and partial-payment rules surface on the hosted pay page and in webhook payloads.

See smart invoices: early payment discounts and late fees for worked examples. Terms that live only in email prose do not survive month-end close; terms bound to the invoice object do.

Who Settlematic is built for

Strong fit:

• B2B teams billing internationally in stablecoins — see how to bill international clients in crypto
• SaaS companies adding crypto settlement without custody risk (SaaS guide)
• Agencies on retainers needing per-invoice reconciliation (agency guide)
• Merchants who already hold USDC/USDT in self-custody treasuries

Consider alternatives if:

• You require automatic fiat payout to a local bank on T+1 — Settlematic settles on-chain; off-ramp is yours
• You need exotic altcoin support beyond USDC, USDT, EURC, ETH, and BTC
• You prefer a custodial float model for operational simplicity and accept the creditor risk

For a neutral comparison of vendors, read best crypto invoicing platforms in 2026.

Getting started with Collect

Settlematic Collect is the invoicing surface: create clients, issue fiat-quoted invoices, share hosted pay links, and reconcile automatically. Connect your settlement wallets once; every subsequent invoice inherits address binding.

• Complete organization setup and optional KYB
• Configure settlement destinations per asset and chain
• Issue your first invoice and share the pay link
• Receive webhooks on confirmation; export for accounting

Book demo if you want a guided walkthrough of address binding and webhook payloads. Explore pricing when you are ready to pick a tier.

The bottom line

Settlematic is different because it treats non-custodial settlement as a prerequisite, not a feature bullet. Invoice-scoped addresses, address-bound derivation, flat pricing, multi-chain watch-only reconciliation, and finance-grade webhooks are all consequences of that constraint — not separate upsells.

If your evaluation criteria include "what happens when the provider disappears," the architecture answer matters more than the UI skin. Settlematic Collect | pricing | demo

Competitive evaluation scorecard

Use a weighted scorecard when comparing Settlematic to alternatives — prevents demo-driven decisions that ignore custody:

Score each vendor 1–5 with evidence (documentation links, test invoice results), not sales claims. Weight non-custodial and address binding highest if invoice amounts exceed $10,000 regularly — custody tail risk dominates fee differences at scale.

Implementation timeline: first 30 days

Typical Settlematic rollout for B2B teams:

Accelerate week 1–2 if team already operates crypto treasury. Extend week 3 if enterprise clients require security questionnaire responses referencing /security.

Objections from finance teams and responses

Finance objections often reflect 2021 BTC invoice trauma — address stablecoin fiat-quoted pattern explicitly when presenting to CFO.

Extended analysis: operational depth (1)

Frequently Asked Questions

Is Settlematic non-custodial?

Yes. Settlematic never holds private keys or interim balances. Deposit addresses are derived and bound to merchant-controlled settlement wallets at invoice issuance; the platform detects on-chain confirmations and reconciles invoices without signing transactions.

What chains and assets does Settlematic support?

USDC, USDT, EURC, ETH, and BTC across Ethereum, Polygon, BSC, Solana, Tron, and Bitcoin. Each invoice can restrict which assets and networks a payer may use.

How does Settlematic price its product?

Flat monthly subscription tiers on pricing with no percentage fee on settled volume.

Can I invoice in USD but accept USDC?

Yes. Invoices can be fiat-denominated with crypto settlement. Exchange rates lock for a configurable validity window.

Does Settlematic replace my accounting system?

No. Settlematic handles invoice issuance, pay pages, on-chain detection, and webhooks. You export or integrate into QuickBooks, Xero, or your ERP.

How is this different from a crypto payment gateway?

Collect is invoicing-first: client records, payment terms, discounts, and receivables workflows. Gateway checkout is better for cart-style ecommerce. Both share the same non-custodial settlement core.