Accept and send stablecoins. Keep control of your funds.
Get paid, prepare contractor payouts with your team, and track every payment. Funds stay in wallets you control.
Who can move your money? →Get paid
Create or connect a wallet, send a payment link or show a QR code, and watch the payment arrive.
Pay contractors
Prepare a payout list in USDC or USDT, review fees and route before you sign, follow each recipient and keep the records.
Delegate the work. Keep control of the money.
Your team prepares. You authorize.
Teammates draft payouts and send them for signature. Money leaves only when the wallet’s owner signs: preparing a payout and the right to send funds are separate.
Check before you sign. Track after you send.
Before your wallet asks for a signature you see each recipient, the amount and the network fee. After sending, each status comes from the network: an outcome we cannot confirm is shown as unknown, never as paid.
Know your way out.
For every type of wallet the trust model explains how to reach your funds without inzi and what to prepare in advance — for a wallet created in inzi, a backup file.
Several approvals for larger sums.
A shared treasury on Base: for example, 2 of 3 owners approve each payment. A Ledger or another hardware wallet can be one of the keys. The Safe contract on the network checks the approvals, not our server, and inzi is not an owner. A treasury with several approvals is available on Base only for now.
How the treasury works →
Get paid in stablecoins for your work.
Create a payment request, send the link or show the QR code. Follow the payment as it arrives in inzi.
- A link with the amount and description. The customer pays on a network the request accepts.
- A QR code for the same request, on a screen or printed.
- Partial payments add up against the same request, and you see what is left.
- Each payment keeps the payer, the rate at receipt and the transaction hash.
inzi does not send money to a bank account. Funds arrive as stablecoins in your wallet.
Open an accountFrom what you owe to what was paid
- 01
Prepare the payouts
Pick saved recipients or paste a list of addresses and amounts — up to 500 recipients in one payout from your own wallet. Every address is checked against the network and asset before anything is signed.
In the pilotLinking each payout to the invoice or obligation behind it.
- 02
Review and sign
Before your wallet asks for a signature you see who gets what, the network fee and the route. The payout is simulated first: a recipient that would fail is left out, or stops the whole payout — your choice.
- 03
Follow the result
Each payout shows its status on the network, what still needs your action and the transaction hash for your records. An outcome we cannot confirm is shown as unknown, never as paid.
In the pilotClosing a period with one evidence pack for your accountant.
See it in action
Start from your spreadsheet. Rows that would fail are caught before anything is signed. Sample data.
Money, upcoming payouts and the decisions that need you — on one screen.
The first screen after you sign in. Every figure says which wallets and networks it covers.
- Balances
- Per asset and per connected wallet, in token units and estimated in euro or dollars. A network we could not read is named, not counted as zero.
- Movement
- Customer payments in and payouts out over the last 30 days.
- In progress
- Payments still confirming and payouts on their way to recipients.
- Needs you
- A request paid only in part, a payout that failed or whose outcome is unknown, notifications to your system that stopped arriving.
It shows the wallets you connected to inzi, not your company's whole financial position. No profit, runway or free-cash figures without the data behind them.
Payout to 4 recipients, confirming
- Payout outcome unknown — do not send it again
- inv-2041 paid in part: 60.00 of 100.00
Where the money is at each step.
Sometimes we pay the network fee or submit a transaction you have already signed. Neither gives us access to your funds: a signed transaction cannot be changed or redirected.
If a route ever goes through a partner that holds funds — a conversion to a bank account, for example — it will be marked as such before you use it.
- Receiving
- Customers pay to an address that can only forward to your wallet. There is no inzi balance in between.
- Paying out
- inzi prepares the transaction, your wallet signs it. Without your signature nothing leaves.
- A wallet created in inzi
- The key is split into three parts and inzi can read only one, so it cannot sign for you. Lose both your passkey and your device, and nobody can restore access — including us.
- If inzi stops
- Your balance is untouched. You would lose the links and the records, not the money. For a wallet created in inzi, download its backup in advance: without inzi, that file is how you reach the key.
Assets and networks, by what you can do with them
Not every asset is on every network, and not every route does everything. Here is each route as it works today.
Open USD
In the pilot- What it is
- A US-dollar stablecoin issued by Open Standard, on Base and Tempo. It shares the OUSD ticker with an unrelated asset, Origin Dollar — inzi tells them apart by contract, not by name.
- Why it matters for a business
- When a client or partner pays you in Open USD, you need a wallet that can receive it and a way to pass it on — without a detour through an exchange.
- What you can do in inzi
- Receive it into your inzi wallet on Base or Tempo, see the balance, and send it to a contractor or supplier with your own signature, one transfer at a time.
Not yet: payment requests in Open USD, conversion to other assets, or a euro value for the balance — it shows in token units until there is a price source we trust. On Base the network fee is paid in ETH from the same wallet.
One request, one webhook
Keys are on every plan, including the free one. A test key fires a mock webhook five seconds after the checkout is created, so the integration can be finished before a real payment exists.
POST https://api.inzilink.com/api/v1/checkouts
Authorization: Bearer sk_live_…
Content-Type: application/json
{
"amount": "1200.00",
"currency": "USD",
"description": "Brand system, phase 2",
"order_ref": "inv-2041"
}POST your webhook_url
X-Inzi-Event: checkout.completed
X-Inzi-Signature: sha256=…
X-Inzi-Timestamp: 1757030400
{
"event": "checkout.completed",
"checkout_id": "chk_live_K3bs4EA2OJJXGOhT",
"data": {
"status": "completed",
"amount": "1200.00",
"payment": {
"network": "tron",
"crypto_currency": "USDT",
"tx_hash": "…",
"confirmed_at": "2026-08-04T09:12:44Z"
}
}
}Questions
- Do I need a new wallet?
- No. Connect the one you already use — MetaMask, Phantom, Trust and others, or a Ledger through MetaMask. If you do not have one, create a wallet in inzi with a passkey and no seed phrase. You can export the key and leave at any time.
- Who controls the funds and signs payouts?
- You do. Funds stay in your wallet, and every payout needs your signature in that wallet. inzi prepares the transaction and records the result; it has no key that can move your money.
- Which assets and networks are available?
- Receiving: USDC, USDT and EURC on Polygon, Base, Ethereum, Solana, Tron and TON — the exact assets differ by network. Batch payouts: USDC on Ethereum, Polygon, Base and Solana; USDT on Polygon. USDT on Tron (TRC20) is in the pilot: one tap in the signing window for every transfer in the list, a status for every recipient, network fee in TRX shown before you sign. Open USD: receive and send on Base and Tempo.
- Who pays the fees?
- Your subscription includes the monthly usage listed on our pricing page. Additional usage is billed separately only after the owner agrees to the terms and a spending cap. It is off by default. We never deduct our software fee from your customer’s payment. Contact sales to discuss additional usage; network costs are separate. The gas budget applies only where inzi pays the network fee. On Tron (TRC-20), merchants always pay their network costs and see an estimate before signing. Starter sweeps are self-funded; eligible sweeps on paid plans share the plan’s gas budget. On supported payout routes, sponsorship is available for a wallet created in inzi or a connected wallet with none of the network’s coin, within the plan’s gas budget.
- What data do I get for accounting?
- For every payment received: the payer, the amount, the euro rate at the moment of receipt with its source, and the transaction hash — as CSV, or a ZIP with a PDF per payment. Payouts appear in the transactions export with amount, network and transaction hash. Closing a period with one pack for your accountant is part of the pilot.
- Can I take payments by link and QR?
- Yes. Every payment request has a link and a QR code. The customer pays from their own wallet on a network the request accepts, and you see the payment arrive in inzi.
Latest guides
All guides →- What MiCA Means for a Business Accepting Stablecoin PaymentsWhat MiCA means for a business accepting stablecoin payments: which tokens, who holds the funds, and what stays the same for bookkeeping and tax
- Stablecoin Mass Payouts: How Batch Payouts Work for BusinessMass payouts in stablecoins: how batch runs work, which chains carry USDC, USDT and EURC, who pays gas, and where inzi's guided batch payout pilot fits
- Crypto Payment API: Accept Stablecoins Without CustodyHow a crypto payment API accepts USDC, USDT, and EURC without holding customer funds: the payment flow, per-chain token support, and the tradeoffs
Pick the way in that fits you.
Getting paid works on your own: open an account and send your first request. Payouts start as a guided pilot: tell us who you pay and how often, and we set up the first cycle with you. Either way you keep the keys.