Accepting Crypto Payments Without Heavy Onboarding: BTCPay, Hosted Gateways and Zitto Checkout Compared

Quick answer: You have three options. Self-host (BTCPay Server: no gateway account, you hold the keys, you run the server). Use a hosted gateway (Coinbase Commerce, NOWPayments, BitPay and others: quick setup, onboarding rules vary). Or use Zitto Checkout. Choose based on who holds the keys, the onboarding requirements, settlement currency and setup time.

Disclosure: Zitto offers a crypto checkout product. Competitor details link to their own pages and were last checked on the date at the top.

The thesis

Card processors make merchants go through heavy underwriting because chargebacks put the processor at risk. Crypto payments can't be reversed by the payer, so a lot of that risk logic goes away. Gateways that still ask for heavy onboarding usually do it because they convert to fiat or hold funds, both of which bring regulation. The less a gateway touches fiat and custody, the less onboarding it needs. That's the core trade-off.

Option 1: Self-hosted (BTCPay Server)

BTCPay Server is free, open-source software you run yourself. Payments go straight to your wallet.

Strengths: no processing fee, no middleman, your keys, plugins for WooCommerce and other platforms, Lightning support. Costs: server hosting, updates, backups, and your time. If you run the server badly, it can go down or lose funds. Best for: technical merchants, Bitcoin-focused shops, anyone who values sovereignty over convenience.

Option 2: Hosted gateways

Examples include Coinbase Commerce, NOWPayments and BitPay. Each sets its own onboarding, fees and supported coins, and these change over time.

Strengths: set up in minutes, hosted invoices, plugins, sometimes fiat settlement. Costs: percentage fees, possible verification requirements, account freezes under their terms. Best for: non-technical merchants who want a plugin and a dashboard.

Option 3: Zitto Checkout

Fill in from verified docs:

• Onboarding: no KYC
• Custody:
• Coins/networks:
• Fees:
• Integrations:
• Settlement:

Comparison table

A decision framework

1. Do you need fiat in a bank account? Then you'll need a regulated off-ramp somewhere along the way. Plan for it.
2. Can you run a server reliably? If yes, BTCPay is hard to beat on cost.
3. Do you need it live today, with no account? That's the gap Zitto aims to fill.
4. Monthly volume: at roughly $X/month, a 0.5–1% fee costs more than a VPS. Work out your own break-even point.

Operational must-dos (any option)

• Price in stablecoins or lock quotes so volatility doesn't eat your margin.
• Underpayment/overpayment handling: decide your policy and show it on the invoice.
• Refunds: crypto refunds go to an address the customer gives you. Get it in writing.
• Accounting: record the fiat value at receipt time for taxes.
• Legal: depending on where you are and what you sell, you may still have licensing, consumer-protection and tax obligations even with no gateway KYC. Get advice.

Who this is not for

Merchants selling regulated goods without the required licences, or anyone hoping crypto will hide revenue from tax authorities. It won't, and you shouldn't try.

Total cost of ownership: a worked model

Headline fees are only one part of the cost. Model 12 months at your real volume:

Illustrative figures only. Put in your own volume and hourly rate. The pattern stays the same: below a few thousand dollars a month, convenience wins. Above that, self-hosting or a low-fee gateway saves real money.

Custody models in plain language

1. Direct-to-wallet (non-custodial): each invoice gets an address from your extended public key (xpub). The gateway never touches funds. This is what BTCPay does.
2. Custodial balance: the gateway receives funds into its own wallets and pays you out later. You get convenience, plus counterparty risk and possible freezes.
3. Hybrid / auto-forwarding: funds pass through a gateway address and are swept to yours automatically. This is safer than holding a balance but still involves a brief custody window.

Ask any provider, Zitto included, which of these it uses. Put the answer in writing on the pricing page.

Stablecoins vs Bitcoin vs Lightning

Practical default: accept USDT/USDC on a cheap network plus BTC on-chain and Lightning. That covers most crypto-paying customers.

Invoice design that reduces support tickets

• Lock the quote for 15–30 minutes and show a countdown.
• Show the exact network ("USDT – TRC-20") in large type. Wrong-network deposits cause most of the support load.
• Underpayment rule: e.g. accept within 1% and ask for a top-up beyond that. Show this on the invoice.
• Overpayment rule: refund on request to an address the customer gives you.
• Confirmation policy: say how many confirmations you wait for before delivery.
• Receipt: email or downloadable PDF with the transaction hash, fiat value and timestamp.

Integration paths

• Payment links: no code, good for invoices and social sellers.
• Hosted checkout redirect: the simplest website integration.
• Plugins: WooCommerce, Shopify (where allowed), WHMCS and others.
• API + webhooks: for SaaS. Always check webhook signatures and make your handlers idempotent so a repeated webhook doesn't deliver an order twice.

invoice.created → invoice.paid (0-conf, optional) → invoice.confirmed → fulfil order

Gotcha: never fulfil on the redirect back to your site. Fulfil on the signed confirmed webhook only.

Accounting and records

Record the fiat value at receipt for every payment. Export monthly: invoice ID, coin, network, amount, fiat value, rate source, transaction hash. If you convert to stablecoins or fiat later, the difference may be a separate gain or loss in many places. Ask your accountant. Good records turn crypto revenue from a worry into a routine monthly task.

Questions to ask any gateway before signing up

1. Who holds the keys between payment and payout?
2. Under what conditions can you freeze or hold my funds?
3. Which networks do you support for each stablecoin?
4. What is the fee including payout and conversion?
5. How do refunds work?
6. Is there an uptime history or status page?

A gateway that answers all six clearly on its website is showing you it's trustworthy. That's the bar Zitto should meet publicly. [ACTION]

<!-- deepened -->

A 30-day rollout plan for merchants

Week 1: Decide

• Choose your custody model and coins (see the tables above)
• Write your underpayment, overpayment and refund policy
• Check tax and licensing obligations with an adviser

Week 2: Build

• Set up the gateway or BTCPay instance
• Connect the plugin or API. Implement signed webhooks and idempotent fulfilment
• Create a test product priced at $1

Week 3: Test

• Pay with each coin and network you support
• Test underpayment, overpayment, expired invoice and refund flows
• Check that accounting exports match the blockchain

Week 4: Launch

• Add the crypto option to checkout with a short "How it works" link
• Watch the first 50 payments closely
• Collect support questions and update the FAQ

Customer-facing copy that converts

Crypto payers want three things at checkout: speed, clarity and safety. Effective microcopy:

• "Pay with USDT (TRC-20), BTC or Lightning. Your order confirms automatically."
• "Price locked for 20:00 minutes."
• "Send the exact amount on the network shown. Other networks can't be recovered."
• "Need a refund? We'll send it to an address you provide."

Avoid jargon like "UTXO" or "mempool" on checkout pages, and save the technical details for a help article.

Risk management without KYC

No onboarding KYC doesn't mean no risk management. Merchants still decide who they sell to and how:

1. Fraud is different: crypto payments can't be charged back, so card-style "friendly fraud" disappears. Fulfilment errors and wrong-network deposits become the main problems.
2. Sanctioned addresses: many merchants screen incoming addresses against public sanctions lists, as their legal obligations require.
3. Stablecoin freezes: issuers can freeze addresses. Sweep stablecoins to wallets you control promptly.
4. Price exposure: convert to stablecoins on receipt if you don't want to hold volatile assets.

Case study template (fill with real data)

[MERCHANT NAME], a [category] store, added Zitto Checkout in [month]. In the first 90 days, crypto made up [X]% of orders, average order value was [Y]% higher than card orders, and support tickets per crypto order were [Z]. **

Real case studies are among the strongest trust and conversion assets you can put on a comparison page, so it's worth collecting two or three.

Migrating from another gateway

1. Run both gateways side by side for 2–4 weeks
2. Keep the old gateway's webhooks active until all open invoices expire
3. Export historical transactions for your records
4. Update refund procedures for orders paid through the old gateway
5. Announce the change to repeat crypto customers (new addresses, same experience)

<!-- deepened2 -->

Bottom line

Accepting crypto doesn't have to mean a two-week underwriting process. BTCPay gives full control in exchange for running it yourself. Hosted gateways trade some control for convenience. Zitto's pitch, once the docs back it up, is the convenience of a hosted gateway with no KYC, connected to the same wallet you use for its other services.

FAQ

Do I need KYC to accept Bitcoin? Not with self-hosted tools. Hosted gateways set their own rules. Cheapest way? Self-hosting at higher volumes; hosted gateways at low volume or when you lack the skills. Stablecoins or Bitcoin? Ideally both.