DEV Community: Shieldz

Best crypto payment gateways in 2026 (non-custodial vs custodial)

Shieldz — Tue, 30 Jun 2026 22:02:26 +0000

If you searched "best crypto payment gateways 2026," you have already seen ten listicles that rank whoever pays them the most. This one ranks on the only axis that actually changes your risk: who holds your money. Everything else, fees, payout delays, account freezes, follows from that single decision.

The one question that sorts every gateway

Custodial gateways receive the customer's coins into their wallet, hold a balance for you, and pay you out on their schedule. Convenient, and the source of every percentage fee, payout delay, and "your account is under review" email.
Non-custodial gateways never hold your money. You give a public receiving key, the customer pays an address that belongs to you, and the gateway only watches the chain and tells you it landed. No balance to skim, nothing to freeze.

Sort the 2026 field by that first, then look at fees.

The comparison

Gateway	Custody	Platform fee	KYC to start	Coins
Shieldz	Non-custodial	$0 (network gas only)	No	BTC, shielded Zcash, USDC/USDT on 5 chains
BTCPay Server	Non-custodial (self-hosted)	$0 (you host it)	No	BTC, Lightning, some altcoins
Coinbase Commerce	Custodial flows	~1%	Business verification	Major coins
BitPay	Custodial	~1% + settlement	Yes	Major coins
NOWPayments	Processor-custody	~0.5%+	Varies	300+ coins
CryptAPI	Non-custodial router	~1% per tx	No	Many

(Honest note: BTCPay Server is excellent and genuinely non-custodial, but you run the servers, nodes, and uptime yourself. Shieldz is the hosted, $0-fee, non-custodial option for people who do not want to operate infrastructure.)

How to read it

Custody first. If a provider holds a balance, you have inherited their fraud risk, their payout schedule, and their right to freeze you. Prefer non-custodial. With Shieldz you can verify the non-custodial claim yourself.
Real cost, not headline rate. "1%" usually hides withdrawal fees and float. A non-custodial model charges $0 and you pay only the blockchain's network gas. See the full fee breakdown.
KYC and privacy. Decide up front whether you want to route customers through identity checks. Some gateways gate signup behind business documents; Shieldz has no KYC to start and supports shielded Zcash.
Coins your customers actually pay with. You rarely need 300 long-tail coins. You need stablecoins, Bitcoin, and the chains your buyers use, with single-token settlement so you are not left holding volatility.

The honest pick for 2026

If you want zero infrastructure, $0 platform fees, and to never hand custody to anyone: Shieldz. If you are happy running your own server: BTCPay Server. Everything else asks you to trade custody (and a percentage) for convenience.

Read the practical version: how to accept crypto payments, or start free.

Crypto payment API: a 10-minute quickstart

Shieldz — Tue, 30 Jun 2026 17:01:56 +0000

If you want to accept crypto from your own backend, you want a crypto payment API that is small, predictable, and does not take custody of your money. This is a 10-minute quickstart for the Shieldz API: create an invoice, send your customer to the hosted checkout, and verify the webhook that tells you it was paid. JSON in, JSON out, $0 platform fees.

The full reference lives in the docs; this is the shortest path to a working integration.

1. Get a key

Create a secret key in your dashboard under Developers. Keys are sk_live_… (real funds) or sk_test_… (test mode). The key is shown once, so store it safely.

Authorization: Bearer sk_live_xxxxxxxxxxxxxxxxxxxx

2. Create an invoice

One required field, amount_usd_cents. Everything else is optional.

curl https://shieldz.cash/api/v1/invoices \
  -H "Authorization: Bearer sk_live_…" \
  -H "Content-Type: application/json" \
  -d '{
    "amount_usd_cents": 5000,
    "memo": "Order #1234",
    "idempotency_key": "ord_1234",
    "metadata": { "order_id": "1234" }
  }'

The response is an invoice object with a pay_url. Send your customer there, it is the hosted checkout with a QR code and a pay link. The customer can pay BTC, ETH, USDC, USDT, Zcash and more; you settle to the one token you chose, and the funds go straight to your wallet. Shieldz never holds them.

3. Verify the webhook

When the payment confirms on-chain, Shieldz sends a signed invoice.paid webhook. Always verify the signature before you act on it. The header is X-Shieldz-Signature: t=<unix>,v1=<hex>, where the hex is HMAC_SHA256(secret, "<t>.<rawBody>").

import crypto from "node:crypto";

function verify(rawBody, header, secret) {
  const parts = Object.fromEntries(header.split(",").map((p) => p.split("=")));
  const expected = crypto
    .createHmac("sha256", secret)
    .update(`${parts.t}.${rawBody}`)
    .digest("hex");
  return crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(parts.v1));
}

// Express handler (use the RAW body, not the parsed one)
app.post("/webhooks/shieldz", express.raw({ type: "*/*" }), (req, res) => {
  const ok = verify(req.body.toString(), req.headers["x-shieldz-signature"], process.env.SHIELDZ_WEBHOOK_SECRET);
  if (!ok) return res.sendStatus(401);
  const event = JSON.parse(req.body.toString());
  if (event.type === "invoice.paid") {
    // fulfil the order — webhooks are idempotent and delivered at least once
  }
  res.sendStatus(200);
});

That is the whole integration: create, redirect, verify. Test the entire flow with a sk_test_ key and the dashboard's simulate-payment tool before you touch real funds.

Why a non-custodial API matters for developers

A custodial API quietly makes you responsible for someone else holding your customers' money. A non-custodial one does not: you only ever pass a public receiving key, payments land in your wallet, and there is no balance for anyone to freeze. If you are weighing the two paths, the pay-any-coin trust tradeoff post covers exactly what happens to custody when a buyer pays a different coin than you settle in.

SDKs

If you would rather not hand-roll HTTP, there are official SDKs for Node, Python, Rust and PHP, plus an MCP server so AI agents can create payment links with no API key at all.

Ready? Read the full API reference or start free. For the non-technical version, see how to accept crypto payments.

What is a crypto payment gateway, and how to choose one

Shieldz — Tue, 30 Jun 2026 16:54:43 +0000

A crypto payment gateway is the piece of infrastructure that lets a business accept cryptocurrency and turn it into a clean, confirmed payment: a checkout for the customer, address handling and conversion under the hood, and a notification to your app when the money arrives. Think of it as the crypto equivalent of a card payment gateway, minus the card networks taking a cut.

That is the simple definition. The part that actually matters is who holds the money, because every other difference between providers follows from it.

Custodial vs non-custodial crypto payment processing

There are two models, and they are not close.

Custodial. The gateway receives the customer's coins into its own wallet, holds a balance for you, and pays you out on its schedule. This is how most "crypto payment platforms" work. It is convenient, and it is exactly where the problems come from: a percentage fee on every payment, payout delays "for security," and the standing ability to freeze or offboard your account. You did the work; they decide when you get paid.

Non-custodial. The gateway never holds your money. You give it a public receiving key, the customer pays an address that belongs to you, and the gateway only watches the blockchain and tells you it landed. There is no balance to skim, no payout to delay, no account to freeze, because the funds were never in the middle. This is the model Shieldz is built on, with $0 platform fees.

If you only remember one thing about choosing a crypto payment gateway: non-custodial removes the entire risk category, not just the fee. You can verify the non-custodial claim yourself.

What a good gateway does for you

Hosted checkout. A drop-in payment page so you do not build crypto UI yourself.
Multi-coin acceptance with single-token settlement. Customers pay BTC, ETH, USDC, USDT, Zcash and more; you receive the one token you chose. Volatile coins get routed through a swap so you are not left holding price risk.
Signed webhooks. A verifiable, idempotent notification the instant a payment confirms on-chain, so fulfilment is automatic.
An API and SDKs. So the gateway fits your stack instead of the other way around. See the crypto payment API quickstart.

How to choose one: a short checklist

Custody: non-custodial, or are they holding your balance? (This is the whole game.)
Real cost: is it $0 + network gas, or a percentage plus withdrawal fees plus float? Here is the fee comparison.
KYC: can you start without uploading business documents? Shieldz has no KYC to start.
Coins and chains: does it cover what your customers actually pay with, across the chains you care about? See supported coins.
Developer experience: real docs, signed webhooks, and SDKs.
Chargebacks: on crypto they do not exist; a confirmed payment is final.

It is also worth comparing specific providers directly, for example Shieldz vs Coinbase Commerce, vs BitPay and vs BTCPay Server.

The bottom line

A crypto payment gateway should make accepting crypto boring in the best way: customers pay, the right token lands in your wallet, your app gets told, and nobody in the middle takes a cut or holds the money. If a provider cannot say "non-custodial" plainly, that is your answer.

Want the practical version? Read how to accept crypto payments, or start free.

How to accept crypto payments (a practical 2026 guide)

Shieldz — Tue, 30 Jun 2026 16:54:42 +0000

If you sell anything online, "how do I accept crypto payments?" has a longer answer than it should. Most guides quietly assume you will hand your money to a company that holds it, takes a cut, and decides when you can withdraw. You do not have to. This is the short, honest version of how to accept crypto payments in 2026, and how to do it without giving up custody of a single cent.

What "accept crypto payments" actually means

There are three separate things people lump together:

Receiving the coins a customer sends.
Settling into the asset you actually want (say, a stablecoin instead of a volatile coin).
Knowing a payment happened so your app can ship the order.

A good setup does all three without ever taking custody of your funds. A custodial processor does all three by holding your money in the middle, which is where the fees, the payout delays, and the account freezes come from.

Your options, briefly and honestly

A custodial gateway (the BitPay / Coinbase Commerce model). Easy to start, but they hold a balance, charge a percentage, and can freeze or offboard you. See the fee comparison and why custody is the real cost.
Run your own node (BTCPay Server and friends). Fully self-hosted and non-custodial, but you maintain servers, nodes, and uptime yourself.
A non-custodial gateway (what Shieldz is). You give a public receiving key, customers pay that address directly, and the service only watches the chain and notifies you. No balance to hold, nothing to freeze, $0 platform fees.

If you want the definition and the trade-offs in one place, the crypto payment gateway explainer goes deeper.

How to accept crypto payments with Shieldz, in five minutes

Sign in with a wallet, Google, or Telegram. No business documents, no KYC to start.
Add a receiving address (or an extended public key / Zcash viewing key). Shieldz derives a fresh address per invoice from it; it never sees a spending key.
Create an invoice from the dashboard or the API. You get a hosted checkout link and a QR code.
Send the customer to that link. They pay BTC, ETH, USDC, USDT, Zcash or others from any wallet; you settle to the one token you chose.
Get a signed webhook the moment it confirms on-chain, so your app can fulfil the order automatically.

That is the whole loop. The money goes from the buyer's wallet to yours. We never touch it.

Which coins should you accept?

Start with what people actually pay in: USDC and USDT (stable, no volatility risk), Bitcoin, and shielded Zcash for privacy. You can read the per-coin guides for Bitcoin, USDC, USDT and Zcash. If a customer pays in a coin you do not settle in, an independent swap routes it and you still receive your chosen token.

What to watch for

Custody. If a provider holds a balance for you, every other risk follows from that. Prefer non-custodial. Verify it yourself.
Real cost. "Low fee" often hides a percentage plus a withdrawal fee plus float. With a non-custodial model you pay only network gas.
Chargebacks. They do not exist on crypto. A confirmed payment is final, which removes a whole category of fraud for digital goods.
Privacy and KYC. Decide up front whether you want to route customers through identity checks. Shieldz does not gate signup behind paperwork.

The one-line summary

To accept crypto payments well: take the coins directly to your own wallet, settle to a stablecoin if you want predictability, and use signed webhooks to automate fulfilment. That is exactly what Shieldz is built to do, for $0. Start free or read the API docs.