Non-Custodial Crypto Payment Gateway: Complete Guide for Merchants in 2026

A custodial processor takes the payment, holds the coins, and later lets you withdraw. A non-custodial crypto payment gateway does the opposite: the customer pays an address you control, and the software’s job is invoices, monitoring, and status — not holding funds.

That difference is the whole product. TheyPaid is built as a non-custodial gateway: payments go directly to your wallet, there is no KYC wall to start, and setup is meant to be immediate.

This guide covers how the model works in 2026, what you still have to get right as a merchant, and how a TheyPaid invoice actually gets paid.

Custodial vs non-custodial, in one checkout

Custodial gateways feel familiar if you have used a hosted checkout that “receives crypto for you.” The processor controls the deposit address. You wait on their ledger, their withdrawal queue, and their risk policy. Frozen accounts and delayed payouts are failure modes of custody, not of Bitcoin.

Non-custodial checkout flips the ownership:

1. You (or your integration) create an invoice with an amount and the networks you accept.
2. The customer picks a coin and sees a unique payment address plus the exact amount.
3. They send from their own wallet.
4. The gateway watches public chain data. When the payment is detected, the invoice is marked paid — and the coins are already in your wallet.

TheyPaid’s positioning is explicit: it never stores, accesses, or controls your funds. Because settlement is on-chain to you, there is no platform balance to freeze and no withdrawal limit to wait out.

What a TheyPaid invoice actually does

Think of TheyPaid as invoicing and monitoring software, not as a bank. The terms of use describe the service as creating invoices, displaying payment information, monitoring public blockchain activity, and sending status notifications.

That has practical consequences:

• You own the address. Wrong network or a mistyped destination is a merchant error, not something TheyPaid can reverse.
• The chain is the source of truth. Confirmations, mempool delays, and underpayments behave like any other crypto transfer.
• Status is derived from public data. The dashboard tells you what the network already shows.

For a store, the useful part is the glue: a stable invoice ID, a payment URI or QR, a paid/expired/insufficient state, and (if you use the API) a callback when that state changes.

How your customer pays

The public checkout story on theypaid.io is three steps, and it is the same flow you should design your UX around.

Select cryptocurrency. At checkout the buyer chooses from the assets you enabled. Showing logos and network names (Bitcoin vs Bitcoin Cash, USDT vs native coins) reduces “I sent it on the wrong chain” tickets.

Send payment. TheyPaid generates a unique payment address and the exact amount. The customer pays from a wallet they already have. There is no TheyPaid customer account and no hosted wallet for the buyer.

Confirmation. Once the transaction is visible on the network, the invoice updates and the merchant wallet already holds the coins. Your customer can see an instant payment notification on the checkout side while confirmations continue in the background depending on the asset.

If you are integrating by API rather than a plugin, the same sequence applies — you create the invoice, render the address, then poll or wait for the webhook. The official SDK maps that to invoices.create(), invoices.get(), and invoices.poll().

Coins, networks, and what to enable

TheyPaid markets multi-asset checkout. The live marketing site highlights BTC, BCH, LTC, BSV, XRP, DOGE, USDT, and GRAM (TON). Enable only what you are willing to operate: every extra network is another address book, another underpayment pattern, and another “wrong chain” support case.

A practical 2026 default for many shops:

• BTC if your audience expects it.
• USDT if you want a unit that matches your list prices more closely than a volatile coin.
• One additional chain you actually use (LTC, BCH, XRP, DOGE, or TON) rather than turning everything on on day one.

Store-level asset lists come from the merchant dashboard (store.assets in the API). Do not hard-code coin IDs in your app without reading what the account currently allows.

Fees: amount-based, no monthly plan

TheyPaid’s pricing page publishes processing fees as a percentage of invoice amount. There is no fixed monthly subscription in that model. The live schedule is:

New accounts are offered a starting balance (currently $10 on the marketing site) so you can run real invoices before you pay for volume.

Separately, blockchain network fees are paid by the sender on-chain. TheyPaid does not replace miner fees, gas, or wallet fees. Price your goods in a unit you understand, and remember that a $50 invoice and a $50,000 invoice are different fee percentages — but both settle to your wallet, not a TheyPaid omnibus account.

What “no KYC” does and does not mean

TheyPaid does not put a lengthy identity check in front of creating a gateway. That is a product choice: faster activation, no custodial onboarding queue.

It is not a waiver of your obligations. You still decide who you sell to, how you invoice, how you handle refunds, and which laws apply to your business. The terms put tax, consumer rules, sanctions, and AML duties on the merchant. Non-custodial software does not make a restricted business legal.

If you needed a processor that underwrites the buyer and holds funds through disputes, this is the wrong category of product. If you needed coins in a wallet you already control, it is the right one.

A sensible go-live checklist

Before you send a customer to pay:

1. Confirm the receiving addresses and networks in the dashboard — test with a tiny invoice first.
2. Decide which coins you actually support, then hide the rest.
3. Match invoice currency and displayed price so the “exact amount” the customer sends is the amount you expect.
4. Wire status handling: paid, insufficient, expired. Do not fulfil on “seen in mempool” unless you accept that risk.
5. If you use callbacks, verify the invoice ID and amounts against your own database. Do not trust a webhook body alone.
6. Document refunds as a separate on-chain send from your wallet. There is no chargeback rail.

When you want the storefront path rather than the architecture, read how to accept Bitcoin and crypto on an online store. When you want the operator view after go-live, read how invoice status works in the TheyPaid dashboard.

Start with a real invoice, not a slide deck

Create an account, take the starting balance, and issue one invoice to a wallet you control. Watch the status flip when the chain sees the payment. That single loop — invoice, address, on-chain credit, dashboard update — is the entire non-custodial model.

Create your TheyPaid account and run that test before you wire it to production checkout.