Does Settlematic replace our multisig?

No. Sweeps move funds to wallets you configure - including multisig cold storage destinations.

Can we embed checkout in our dapp?

Yes. Gateway supports hosted pages, iframe embeds, and API-driven sessions with signed webhooks.

Is there an API for payment automation?

Yes. REST APIs cover invoices, payment links, gateway sessions, and webhooks - with scoped keys for testnet and mainnet.

Which chains and assets can a Web3 team accept?

USDC, USDT, EURC, ETH, and BTC across Ethereum, Polygon, Base, Arbitrum, Arc, Solana, Tron, and Bitcoin. Stablecoin availability follows the issuer: USDT is not offered on Solana, and EURC is EVM-only. You choose which assets and networks each invoice or checkout accepts.

Is Settlematic custodial at any point in the payment?

No. Deposit addresses are derived for wallets you control and bound to the invoice at issuance. Settlematic holds no private keys or key shards that can move funds; it watches the chain, confirms the payment, and executes the sweep rule you configured.

How does this differ from a crypto payment gateway that forwards to our wallet?

Forwarding gateways receive funds into a processor-controlled address first, then pay out. Settlematic never sits in the path: the payer sends directly to an address bound to your destination. There is no processor balance to freeze, delay, or charge a percentage on.

Can we invoice a DAO or a grant program in USD and receive USDC?

Yes. Quote the invoice in USD (or EUR/GBP), attach line items and any PO or proposal reference, and the payer chooses USDC on the chain they hold it. The fiat amount is locked for the payment window and recorded at receipt for your books.

Industries

Invoicing and checkout with merchant-configured sweeps.

Web3 teams already hold treasury on-chain, so the last thing they need is a payment processor that pools their inbound funds in a custodial balance and pays out on a schedule. What they do need is boring finance plumbing: invoices quoted in USD or EUR that a partner's accounts-payable team will actually approve, checkout that a dapp or API product can embed, and a ledger that reconciles every USDC, USDT, EURC, ETH, or BTC receipt against an invoice or session ID without someone pasting hashes from a block explorer. Settlematic is that plumbing. Every invoice and checkout session gets its own deposit address bound to a wallet you control at the moment it is issued; we watch the chain, confirm the payment, fire a signed webhook, and sweep funds to the multisig, cold wallet, or operating wallet you configured. No pooled balances, no processor custody, no percentage of volume.

Start free trial Try sandbox →

Overview

Web3 payments infrastructure for DAOs, protocols, and crypto-native companies: fiat-quoted partner invoicing, embeddable multi-chain checkout, invoice-scoped addresses bound to your own wallets, signed webhooks, and merchant-configured sweeps — with a full testnet environment before mainnet.

Networks

Ethereum, Polygon, Base, Arbitrum, Arc, Solana, Tron, and Bitcoin

Custody

None

Addresses bound to your wallets at issuance

Testnet

Free

Full platform access before mainnet

Checkout

4 modes

Hosted, embedded, iframe, QR

Definition

What is Web3 teams?

Settlematic for Web3 teams combines Collect (fiat-quoted invoicing paid in stablecoins or native assets) with Gateway (hosted, embedded, iframe, and API-driven checkout for products and platforms). Both share one non-custodial settlement layer: deposit addresses are derived for wallets you control, payments are detected on-chain, and confirmed funds are swept to destinations you set. Settlematic never holds private keys or key shards that can move your funds.

Settlement

Sweeps to wallets you configure — including your multisig

Each invoice or checkout session gets a fresh deposit address derived for a destination you control. When the payment confirms, Settlematic sweeps it to that destination: a Safe multisig, a hardware-wallet cold address, or an operating wallet per business unit. Destinations are fixed at issuance, so nobody — including Settlematic — can redirect a payment after the fact. Sweep rules can differ per asset and network: USDC on Polygon to the ops wallet, ETH to cold storage, BTC left in place.

Merchant-configured sweep destinations per asset and network
Invoice-scoped deposit addresses, never reused across payers
Dual-source on-chain detection before an invoice is marked paid
Signed webhooks (HMAC) with delivery and retry logs

Settlematic sweep destinations settings with destination addresses configured across EVM, Bitcoin, Solana, and Tron chain families

Partners

Invoice ecosystem partners in fiat, settle in stablecoins

Not every counterparty is on-chain native, and even the ones that are usually have a finance team that thinks in dollars. Collect issues invoices quoted in USD, EUR, or GBP with line items, tax buckets, PO references, and payment terms, then lets the payer choose USDC, USDT, EURC, ETH, or BTC on the chain they hold it. The fiat amount is locked for the payment window, so a partner paying a $25,000 integration fee sends exactly the stablecoin amount due, and your ledger records the fiat value at the time of payment for tax purposes.

USD, EUR, and GBP quotes with locked exchange rates
Line items, tax fields, PO numbers, and due dates on every invoice
Partial payments and early-payment discounts as invoice terms
Recurring invoices for retainers, grants, and service agreements

Settlematic invoice INV-1042 for Alex Chen with consulting line items, $80 balance due, and sent timeline in the Collect dashboard

Product checkout

Embed checkout in your dapp, API, or marketplace

Gateway creates checkout sessions from your backend and renders them as a hosted page, an embedded component, an iframe, or a QR flow — the same detection and settlement rails as Collect. Platforms that onboard their own merchants get multi-merchant operations: per-merchant API keys, allowed assets, KYB workflows, refunds, and audit logs, with each merchant's funds settling to that merchant's own wallet rather than a platform-controlled pool.

REST API for sessions, invoices, and payment links
Multi-merchant onboarding with scoped keys per environment
Sandbox merchants on testnet that mirror production behavior
Customer portal for payment status and receipts

Settlematic hosted crypto checkout for invoice INV-1042 with ETH, USDC, and BTC tabs, partial payment progress, and wallet pay controls

Automation

Webhooks and agents, not dashboards

Crypto-native teams automate. Every payment lifecycle event — created, detected, confirmed, swept, underpaid, wrong-chain — is delivered as a signed webhook you can verify and replay. Teams operating from Claude or other assistants can use the Settlematic MCP server to query receivables, draft invoices, and check settlement status from conversation, with confirmation gates before anything client-facing is sent.

payment.confirmed, invoice.paid, and sweep.completed events
Idempotent delivery with replay from the dashboard
MCP server for Claude-driven AR workflows
Wrong-chain and underpayment detection with recovery flows

Settlematic webhook endpoint setup subscribing to invoice and payment events for automation

Reporting

Reports your accountant and your DAO can both read

Each payment is recorded with the invoice ID, payer, asset, network, transaction hash, block confirmation, fiat value at receipt, and sweep destination. Export CSV or JSON by period for QuickBooks, Xero, or a governance report; every row carries the on-chain reference so a treasury committee can verify it independently. Tax buckets on line items carry through, so VAT, GST, or sales-tax reporting starts from the invoice, not from a wallet export.

Fiat value at time of receipt on every record
Transaction hash and confirmation height per payment
CSV and JSON exports for accounting and governance
Tax buckets carried from line item to report

Settlematic Tax & compliance report for Settlematic Demo LLC showing gross receipts, taxable sales, rate breakdown, and filing readiness checks

Workflow

How web3 teams teams use Settlematic

1
Receive
Partner or client pays via Collect or Gateway checkout
2
Confirm
On-chain detection updates invoice or session status
3
Sweep
Configured rules move funds to your wallets
4
Automate
Webhooks drive internal ops and provisioning
5
Audit
Export payment reports with on-chain references

Problems we solve

Teams in web3 teams often hit the same operational walls before adopting unified crypto finance infrastructure.

Partner billing that AP teams reject

A wallet address in a Notion doc is not an invoice. Ecosystem partners, grant programs, and enterprise integrators need a numbered, fiat-denominated invoice with line items, tax fields, and a due date before their finance team will release funds — even when they intend to pay in USDC.

Fragmented payment tooling

Partner invoices live in one tool, product checkout in another, and grant disbursements in a spreadsheet. Nothing shares a ledger, so month-end means reconciling three sources against the chain by hand.

Manual wallet ops

Without invoice-scoped addresses and webhooks, every inbound payment is a block-explorer investigation: which sender, which invoice, which chain, was the amount short, did they pay USDT on Tron when the invoice asked for Polygon?

Custodial off-ramps for on-chain teams

Most crypto payment gateways forward funds from a pooled processor balance on a settlement schedule. For a team that already runs a multisig, that is a step backwards: added counterparty risk, delayed finality, and a percentage fee on volume you could have received directly.