Non-Custodial Crypto Payment Processor Guide for Businesses

A crypto payment processor routes stablecoin payments from a customer's wallet to your business wallet. Non-custodial means the funds go directly to a wallet you control — the processor never holds your money. You choose between three architectures: processor-only (you build the checkout UI), gateway (processor + hosted checkout page), or full checkout solution (processor + gateway + invoicing tools). This guide explains how each works, what non-custodial custody means in practice, and which setup fits your business model.

What a crypto payment processor does

A payment processor executes the settlement logic: monitoring a blockchain address for incoming transactions, matching payments to orders, confirming settlement, and triggering webhooks when a payment completes. The processor does not build your checkout page or generate invoices — those are separate layers.

A non-custodial processor monitors an on-chain wallet you own. When a customer sends USDC to that address, the processor detects the transaction, verifies the amount and token match the order, then confirms settlement. The funds never route through an account the processor controls. You hold the private keys; the processor reads the blockchain and reports what it sees.

A custodial processor generates a deposit address it controls, receives the customer's payment into that pooled wallet, then settles to your linked bank account or exchange account on a batch schedule. The processor holds custody between receipt and settlement — typically 24-48 hours for fiat conversion, instant for crypto-to-crypto if you stay on the same network.

Non-custodial vs. custodial: the actual tradeoff

Non-custodial custody means you manage wallet security. You generate the seed phrase, you store the private keys, you handle backup. If you lose the keys, the funds are unrecoverable — no support team can restore access. That is the cost of never giving custody to an intermediary.

Custodial processors remove that burden: they manage the hot wallet infrastructure, handle key rotation, insure the pooled funds. You trade custody for convenience. The processor can freeze your settlement if a compliance flag triggers, or if their bank relationship changes. That is the cost of handing custody to an intermediary.

Which model fits depends on your risk appetite and operational capacity. A SaaS company invoicing $50,000/month in subscription revenue may prefer custodial settlement to a linked bank account — one fewer system to secure. A marketplace routing $2M/month in creator payouts may require non-custodial custody because regulatory exposure or cross-border settlement complexity makes pooled custody untenable. Neither model is universally safer; both shift where the operational risk lands.

Processor vs. gateway vs. checkout solution

These terms describe three layers of the payment stack. Most vendors bundle two or all three; understanding the boundary between them clarifies what you are actually buying.

Processor (settlement layer)

The processor monitors blockchain addresses, matches transactions to orders, confirms settlement. You provide: the order ID, the amount, the token, the destination wallet address. The processor provides: transaction monitoring, settlement confirmation webhooks, a dashboard showing which orders paid and which are pending.

You build the customer-facing UI. You generate the QR code or wallet address display. You handle the "copy address" button, the countdown timer, the post-payment redirect. The processor is an API you call after the customer clicks "Pay with crypto" — not the page the customer sees.

Gateway (processor + hosted checkout)

A gateway adds a hosted payment page on top of the processor. You redirect the customer to the gateway's domain; the gateway displays the wallet address, generates the QR code, shows the payment status live. When settlement completes, the gateway redirects the customer back to your success URL.

You provide: the order amount, a return URL, optionally some branding parameters. The gateway provides: the entire payment UX, the wallet address generation, the settlement monitoring, the post-payment redirect.

Gateways reduce your implementation surface to a single redirect. You do not build a blockchain address display or handle websocket connections for live status updates. The tradeoff: less control over the payment UX, and the customer sees the gateway's domain during checkout.

Checkout solution (processor + gateway + invoicing)

A full checkout solution adds invoice generation, email delivery, and a hosted invoice page on top of the gateway. You call an API to create an invoice; the solution emails the customer a payment link, hosts the invoice page, processes the payment via its gateway layer, confirms settlement via its processor layer.

You provide: the line items, the customer email, optionally some branding. The solution provides: invoice PDF generation, email delivery, a hosted page showing the invoice and a "Pay now" button, the entire payment flow, settlement confirmation.

Checkout solutions fit subscription billing, contractor payouts, or any workflow where you generate invoices before the customer initiates payment. The tradeoff: you depend on the vendor's invoicing logic, email deliverability, and hosted-page uptime — more surface area than a processor-only integration.

How Inzi implements non-custodial processing

Inzi is a non-custodial payment processor. You connect a wallet you control — Inzi monitors that wallet's address on-chain, matches incoming transactions to orders, triggers webhooks when settlement completes. Inzi never holds your funds; the wallet you connect is the wallet that receives customer payments directly.

Inzi charges 0% per transaction on every plan. The only cost is the flat monthly fee: $0/month for Starter (no subscription, for small merchants), $49/month for Growth (batch payouts, for growing businesses), $149/month for Scale (contact sales, for high-volume merchants). No percentage fee means your transaction cost is the blockchain network fee — typically $0.01-$0.50 per USDC payment on Polygon or Base.

Inzi supports six networks: Polygon (USDC, USDT), Base (USDC, EURC), Ethereum (USDC, USDT, EURC), Tron (USDT), TON (USDT), and Solana (USDC). You choose which networks to accept; the customer selects their preferred network at checkout. Settlement happens on the network the customer chose — a Polygon USDC payment settles as Polygon USDC in your wallet, not converted to another chain or token unless you separately move it.

Inzi provides a hosted checkout page (gateway layer) and API webhooks (processor layer). You can use the hosted page for a low-code integration, or call the API directly and build your own checkout UI. Batch payouts (Growth plan and above) let you queue multiple recipient addresses and settle them in a single on-chain transaction — useful for creator payouts, affiliate commissions, or contractor payments. See Inzi's pricing for plan differences.

Network and token considerations

Each network has different transaction finality, fee structure, and ecosystem liquidity. Your choice of network affects the customer's experience (wallet compatibility, gas cost) and your own settlement speed.

Network	Supported Tokens	Typical Gas Cost	Finality Time	Wallet Ecosystem
Polygon	USDC, USDT	$0.01-$0.05	2-5 seconds	MetaMask, Trust Wallet, WalletConnect-compatible
Base	USDC, EURC	$0.01-$0.03	2-4 seconds	Coinbase Wallet, MetaMask, Rainbow
Ethereum	USDC, USDT, EURC	$1-$15	12-15 seconds	MetaMask, Ledger, all major wallets
Tron	USDT	$1-$3	3 seconds	TronLink, Trust Wallet
TON	USDT	$0.01-$0.10	5 seconds	Tonkeeper, TON Wallet
Solana	USDC	$0.0001-$0.001	0.4 seconds	Phantom, Solflare

Polygon and Base offer the lowest fees while maintaining EVM compatibility — most customers already have a MetaMask or Coinbase Wallet that works with these chains. Ethereum has the highest liquidity and the widest wallet support, but gas costs make it impractical for payments under $100. Tron dominates stablecoin volume in some regions (Asia, Eastern Europe) due to TronLink's distribution. Solana offers sub-cent fees and sub-second finality, but wallet adoption lags EVM chains outside crypto-native users.

If your customer base skews toward existing crypto holders (marketplace sellers, freelancers paid in stablecoins), support all six networks and let the customer choose. If your customer base is new to crypto payments (subscription buyers, one-time purchasers), default to Polygon or Base — the wallet setup friction is lowest, and the fee cost stays under $0.05 even for small purchases.

Custody and wallet security in practice

Non-custodial custody means you are responsible for the wallet's private keys. Generate the wallet using a hardware wallet (Ledger, Trezor) or a secure key-management service. Do not generate keys in a browser extension or on a server without hardware-backed encryption.

Store the seed phrase offline — paper backup in a safe, metal backup in a bank vault, or multi-signature custody split across geographic locations. If you lose the seed phrase and the hardware wallet fails, the funds are unrecoverable. No support team at Inzi or anywhere else can restore access; blockchain wallets have no password-reset mechanism.

For high-volume merchants, consider multi-signature custody: require two of three keyholders to approve withdrawals. Gnosis Safe supports multi-sig on Ethereum, Polygon, and Base; you set a threshold (2-of-3, 3-of-5) and each withdrawal requires that many signatures. This protects against single-keyholder compromise or loss.

Integration workflow for a non-custodial processor

Integrating Inzi (or any non-custodial processor) follows this sequence:

1. Generate a wallet. Use a hardware wallet or custody service. Record the seed phrase offline. Derive the receiving address for each supported network — Polygon address, Base address, Ethereum address, etc. One wallet can have addresses on multiple chains; the seed phrase is the same, the addresses differ.

2. Connect the wallet to Inzi. Provide the wallet addresses (not the private keys) via the Inzi dashboard. Inzi monitors these addresses on-chain; you retain full custody of the keys.

3. Integrate the API or hosted checkout. For API integration: call the create-payment endpoint with the order amount, currency (USDC/USDT/EURC), and network preference. Inzi returns a unique payment ID and the wallet address to display. For hosted checkout: redirect the customer to Inzi's payment page; Inzi handles the address display, QR code, and live status updates.

4. Handle the webhook. When the customer's transaction confirms on-chain, Inzi sends a webhook to your server with the payment ID, transaction hash, and settlement status. Mark the order as paid in your database. Do not rely solely on the customer's browser redirect — webhooks are the authoritative settlement signal.

5. Reconcile daily. Compare Inzi's transaction log against your wallet's on-chain history. Every payment Inzi reports as settled should have a corresponding transaction in your wallet. This catches configuration errors (wrong address connected) or webhook delivery failures.

For batch payouts (Growth plan and above): upload a CSV of recipient addresses and amounts, or call the batch-payout API. Inzi queues the payments and submits them in a single on-chain transaction. One transaction fee covers all recipients — cheaper than sending individually.

Regulatory and tax implications

Receiving stablecoin payments creates a taxable event in most jurisdictions. The payment counts as revenue at the fair market value of the stablecoin on the settlement date. If you receive USDC, the value is approximately $1 per token; if you receive USDT, the value fluctuates within $0.99-$1.01. Record the USD-equivalent amount and the settlement timestamp for each payment.

Non-custodial custody means you hold the stablecoins on-chain until you convert them to fiat or spend them. That holding period may create additional tax events if the stablecoin's value changes. USDC and EURC track their fiat equivalents closely (within 0.1%), so the holding-period gain/loss is minimal.

When non-custodial processing makes sense

Non-custodial processing fits businesses that:

• Process enough volume that a percentage fee would exceed the cost of wallet management ($10,000+/month puts you near the breakeven point against typical custodial fees).
• Require instant settlement without waiting for a processor's batch schedule (funds arrive in your wallet the moment the transaction confirms on-chain, not 24-48 hours later).
• Need to avoid pooled-custody risk (regulatory exposure, bank relationship changes, processor insolvency).
• Already manage crypto wallets for other purposes (treasury, payroll) and have the operational capacity to secure one more wallet.
• Operate in jurisdictions where custodial processors require KYC/KYB you cannot or prefer not to complete.

Non-custodial processing does NOT fit businesses that:

• Have no prior experience managing crypto wallets and no one on the team who can own wallet security (the learning curve is real; a lost seed phrase is unrecoverable).
• Process under $5,000/month and would pay more for a flat subscription than a percentage fee.
• Require fiat settlement same-day (non-custodial means you hold stablecoins; converting to fiat is a separate step).
• Depend on chargeback protection (blockchain transactions are irreversible; once settled, the payment cannot be clawed back).

Choosing a non-custodial crypto payment processor

Evaluate processors on these dimensions:

1. Network support. Does the processor monitor the chains your customers use? If your customer base is global, you need at least Polygon, Base, and Ethereum. If your customer base concentrates in Asia or Eastern Europe, add Tron. If your customer base is crypto-native, add Solana.

2. Token support per network. Does the processor support USDC and USDT on the networks you selected? EURC if you invoice in euros? Verify the per-network token list before signing up; not every processor supports every token on every chain.

3. Fee structure. Flat monthly fee or percentage per transaction? Calculate your breakeven: if you process $X/month, a Y% fee costs $X × Y. Compare that to the processor's flat fee.

4. Custody model. Does the processor hold your funds at any point, or do payments go directly to your wallet? Read the terms carefully — some processors advertise "non-custodial" but actually use a custodial intermediary step before settling to your wallet. True non-custodial means the customer sends funds to an address you control, not an address the processor controls.

5. Webhook reliability. Does the processor guarantee webhook delivery, or do you need to poll an API for settlement status? Webhooks are the authoritative settlement signal; if webhook delivery fails, you may mark an order as unpaid when the customer actually paid. Look for processors that support webhook retries, idempotency keys, and a dashboard showing webhook delivery history.

6. Batch payout support. If you pay out to multiple recipients (creator marketplaces, affiliate programs, contractor payroll), does the processor let you batch those payments into one transaction? Batch payouts reduce the per-recipient gas cost from $0.05-$0.50 to $0.001-$0.01 by consolidating multiple sends into a single on-chain transaction.

Next steps

If you are evaluating crypto payment processors:

1. Calculate your monthly processed volume. Multiply by a typical custodial fee percentage and compare to non-custodial flat fees. If the percentage toll exceeds $50-$150/month, a non-custodial processor is cheaper.

2. Audit your wallet management capacity. Do you have someone on the team who can securely generate a wallet, store the seed phrase offline, and handle key rotation if needed? If not, factor in the time to learn wallet security or hire someone who knows it.

3. Map your customer's network preferences. If most customers already hold crypto, support all six networks (Polygon, Base, Ethereum, Tron, TON, Solana) and let them choose. If most customers are new to crypto, default to Polygon or Base for the lowest friction.

4. Test the integration workflow. Inzi's Starter plan costs $0/month — no subscription fee, no per-transaction fee, just the network gas cost. Generate a test wallet, connect it to Inzi, create a test payment, send $1 USDC from your own wallet, confirm the webhook fires and your wallet receives the payment. Register for free to start testing.