Merchants evaluating crypto payments usually frame the decision as "use a gateway" versus "do it ourselves." That framing hides the actual question. Both approaches must perform the same three jobs — generating payment addresses, watching the blockchain for incoming funds, and reconciling payments against orders — and the real difference is who performs each job, who carries each risk, and what it costs in money and attention.
This article breaks the comparison down to architecture and operations rather than marketing claims. Whether you run your own wallet stack or plug into a gateway, you will finish with a clear picture of which responsibilities move, which stay with you, and where the security boundary sits in each model.
The Three Jobs Every Crypto Checkout Must Do
Job 1: Address Generation
Every order needs a unique receiving address (or a unique amount) so that incoming payments can be attributed to orders. A self-hosted stack derives addresses from your own HD wallet — you hold the seed, and address generation happens on your infrastructure. A gateway derives addresses from its infrastructure; in a non-custodial model those addresses are derived from your extended public key or are swept automatically to a wallet you control, while in a custodial model they belong to the gateway's omnibus wallets.
Job 2: Chain Monitoring
Someone must watch the mempool and confirmed blocks for every outstanding invoice, detect underpayments and wrong-asset transfers, handle chain reorganizations, and decide when a payment is final. Self-hosted means running or renting reliable node access and writing the monitoring logic yourself. A gateway operates this as shared infrastructure, typically confirming TRC20 payments within about a minute and ERC20 payments within a few minutes depending on confirmation policy.
Job 3: Reconciliation
Finally, payments must land in your order system and your books: webhook or polling into the store, order status updates, and exportable records for accounting. Self-hosted means building and maintaining this pipeline. A gateway provides webhooks, dashboards, and CSV or API exports out of the box — though your finance team still owns the bookkeeping logic, as our reconciliation guide explains.
What a Self-Hosted Wallet Stack Really Involves
The appeal of self-hosting is total independence: no intermediary in the payment path, no per-transaction percentage, and custody that never leaves your control. The costs are real and recurring:
- Infrastructure. Reliable node access for each chain you accept — self-run nodes with monitoring and failover, or paid node API services with rate limits you must design around.
- Key management. Seed generation, encrypted storage, signing procedures, and a hot/cold split so that the wallet watching for payments cannot be drained through your server.
- Edge-case engineering. Reorgs, stuck transactions, partial payments, duplicate callbacks, wrong-chain deposits, and the monitoring that detects each of them.
- Ongoing operations. Chain upgrades, node resyncs, and the pager duty that comes with being your own payment processor.
Teams that have run this in production generally describe it as a permanent part-time engineering commitment. That cost is worth paying when you have the expertise in-house, process enough volume that percentage fees exceed the engineering cost, or have compliance reasons to minimize third parties. It is a poor trade for a merchant who wants to start accepting crypto this month.
What a Gateway Does Instead
A gateway absorbs jobs one and two as a service and standardizes job three. Integration is a plugin or a few API calls; monitoring, confirmation logic, and callbacks are operated for you; and you receive structured payment events rather than raw chain data. Fees are typically a per-transaction percentage, and terms vary by provider and volume, so check official sites for current rates.
The critical distinction within gateways is custody. A custodial gateway collects payments into its own wallets and pays you out on a schedule — reintroducing the counterparty risk and settlement delays familiar from card acquiring. A non-custodial gateway never takes possession of funds: payments land in, or are forwarded immediately to, addresses under your control. USDTGate operates on the non-custodial model, which means the gateway can suffer downtime or even disappear and your received funds remain untouched on-chain. The broader build-versus-buy framing is covered in our comparison of USDT integration methods.
Cost and Responsibility Comparison
| Dimension | Self-hosted wallet stack | Non-custodial gateway | Custodial gateway |
|---|---|---|---|
| Address generation | Your HD wallet, your infrastructure | Gateway infra, derived toward your wallet | Gateway's own wallets |
| Chain monitoring | You build and operate it | Provider operates it | Provider operates it |
| Who can move funds | Only you | Only you | Provider, until payout |
| Custody risk | Your key security | Your key security | Provider solvency and behavior |
| Upfront effort | Weeks of engineering | Hours | Days including KYB |
| Ongoing cost | Infrastructure plus engineering time | Per-transaction fee | Fee plus settlement terms |
| Reconciliation tooling | You build it | Provided, you own the books | Provided, usually fiat-denominated |
Security Boundaries: Who Owns What Risk
Mapping responsibility explicitly prevents the most common misunderstanding — the assumption that a gateway makes your security problems disappear, or that self-hosting makes you immune to operational failure:
- Self-hosted: you own key custody, server security, monitoring correctness, and incident response. A compromised server is a compromised payment flow.
- Non-custodial gateway: the provider owns monitoring uptime and detection correctness; you own your withdrawal wallet's keys and your store's webhook endpoint validation. Funds already received are outside the provider's reach.
- Custodial gateway: the provider owns everything up to payout, including the risk that funds are frozen, delayed, or lost while in their wallets.
Note what stays constant across all three: your own operational security — admin credentials, server patching, webhook signature verification — is yours in every model. And a subtle point in the non-custodial case: because received funds are already in your wallet, an incident at the provider interrupts new payments, not your existing balance.
Conclusion
The gateway-versus-self-hosted decision reduces to three questions: does your team have the engineering capacity to run payment infrastructure permanently, do you require zero third parties in the payment path, and does the per-transaction fee exceed what your own operations would cost? If you answer yes to the first two, self-hosting is defensible. Most merchants answer otherwise, and for them a non-custodial gateway captures nearly all of the independence with a fraction of the operational load. To see the architecture in practice, the USDTGate documentation describes the payment flow and webhook model, and you can register to inspect a live integration before committing to anything.