Qvard vs 0xProcessing: fees, KYC, webhooks and testing compared
TL;DR: The biggest practical difference is how you get started and what you can see up front. Qvard publishes a 1% base rate (individually down to 0.1%) and lets a merchant register without KYC. 0xProcessing publishes no percentage: the fee depends on the merchant's business model and monthly turnover and is set in an individual agreement, and its Terms reserve the right to verify identity and freeze accounts. In return, 0xProcessing offers things Qvard does not have today: no-code invoices and payment links, signed webhooks (HMAC-SHA256) and a documented test mode. Neither is objectively better; it depends on whether you want a transparent starting price or a richer feature set negotiated with a manager.
Qvard vs 0xProcessing
Published price versus an individual agreement
Qvard shows its base rate: 1% per payment, set individually down to 0.1% as volume grows. 0xProcessing does not publish a percentage. Its documentation says the processing fee depends on the merchant's business model and monthly turnover, is deducted automatically from each payment credited to the merchant's balance, and is always covered by the merchant. The Terms add that fees are disclosed in the Merchant's Agreement. So you cannot compare the two numbers before talking to 0xProcessing; ask both for a quote against your own expected volume.
Payment links and invoices
This is a real difference in 0xProcessing's favour. Its docs describe invoices created in the dashboard (up to 20 positions, link active for 14 days) and payment links. Qvard has no no-code payment links: a payment is created through the API and the customer is sent to a hosted checkout page.
Webhooks: X-Qvard-Signature versus X-Webhook-Signature
Qvard sends a final-status webhook with retry and an X-Qvard-Signature header (HMAC-SHA256 over the raw body). 0xProcessing signs webhooks with HMAC-SHA256 in the X-Webhook-Signature header (format v1=<hex>), retries up to 31 times and expects 200 OK within 3 seconds. If you want signature verification out of the box, that is a point for 0xProcessing.
Network fees and withdrawals
By default the network fee on an incoming payment is included in the client's payment, and a merchant can choose to cover it instead. For withdrawals 0xProcessing charges no processing fee, only the network fee; its fee table is not consistent with itself for USDT TRC20 (two different values on the same page), so check the current number in your dashboard. Qvard supports manual and automatic withdrawals to a wallet; neither service describes a fiat payout in the sources we checked.
Coins and networks
Qvard offers USDT on TRC20, ERC20 and BEP20 plus BTC, LTC, ETH, BNB and TRX; TON is not offered. 0xProcessing's site lists a much longer set of coins and networks, including TON and Solana, though the number of coins it claims does not match the list on the same page. If you need a coin outside Qvard's list, 0xProcessing is the wider option.
Plugins
Qvard has no ready-made plugins; integration is through the REST API. We did not find ready-made plugins in 0xProcessing's official documentation either, whose integration options are API-based, so do not assume either service has a one-click WooCommerce or Shopify module.
When 0xProcessing is the better choice
Pick 0xProcessing if you need no-code invoices and payment links, signed webhooks, a documented Test=true mode, or a coin or network that Qvard does not list, and you are comfortable agreeing the fee individually with a manager.
When Qvard is the better choice
Pick Qvard if you want a stated starting rate (1%, down to 0.1% with volume), self-registration without merchant KYC, and a simple API-first flow around USDT on TRON, Ethereum and BNB Smart Chain, with support through a Telegram bot.
FAQ
What is 0xProcessing's fee?
No percentage is published. The documentation says it depends on the merchant's business model and monthly turnover and is set in an individual Merchant's Agreement. Qvard's base rate is 1% per payment, individually down to 0.1%.
Does 0xProcessing require KYC?
There is no explicit KYC requirement in the docs, but the Terms reserve the right to verify identity, require due diligence cooperation and freeze accounts on suspicion. Some marketing material calls the service "no-KYC"; we did not treat that as a fact. Qvard requires no KYC for merchants.
Is there a 0xProcessing sandbox or test mode?
Yes. Set Test=true when creating a payment form. Test payments only simulate statuses, must not be funded with real crypto, and webhooks for them carry a Test flag, so you should not credit funds on them. The docs do not clearly say which other features (invoices, withdrawals, static wallets) can be tested.
Are 0xProcessing webhooks signed?
Yes: an HMAC-SHA256 signature in the X-Webhook-Signature header, format v1=<hex>. It retries 31 times and expects 200 OK within 3 seconds. Qvard's webhook is signed with an X-Qvard-Signature header (HMAC-SHA256).
Is 0xProcessing custodial like Qvard?
The site does not use the word custodial or non-custodial and the Terms do not describe how funds are held. The docs describe a merchant balance that payments are credited to and withdrawn from. Qvard is custodial: it tracks a merchant balance per asset until withdrawal.
Can I accept payments without code on both?
On 0xProcessing, yes: invoices and payment links can be created in the dashboard. On Qvard, no: payments are created through the API and the customer is sent to a hosted checkout page.
More comparisons
Data on 0xProcessing verified 2026-10-28 from official sources. Fees, features and policies can change after this check — confirm current details directly with the provider before deciding.
Sources checked: https://0xprocessing.com/terms/ · https://0xprocessing.com/commissions/ · https://0xprocessing.com/supported-coins/ · https://0xprocessing.com/contacts/ · https://docs.0xprocessing.com/basic/general/transaction-fees.md · https://docs.0xprocessing.com/faq · https://docs.0xprocessing.com/quick-start/account-registration.md · https://docs.0xprocessing.com/quick-start/invoices.md · https://docs.0xprocessing.com/0xprocessing-api-v1/webhooks.md · https://docs.0xprocessing.com/basic/introduction-guide/payment-form.md