Hosted checkout
Localized payment page with asset, network and exact transfer instructions.
Accept USDT, USDC, BTC, LTC, DOT, TRX, BNB, ETH, TON and USDT on TON with hosted checkout, invoices, payment links, API and webhooks.
Qvard is built for stablecoins and major crypto assets used by international customers.
Create a test invoice and see the payment page the way your customer sees it: the invoice comes first, then the buyer picks asset and network on checkout.
Create invoice by API or dashboard
Customer chooses asset and network
Qvard locks the exchange rate and shows payment address
Blockchain payment is detected automatically
Webhook updates your order status
Funds appear in merchant balances for withdrawal
Localized payment page with asset, network and exact transfer instructions.
Create payment intents with amount, currency, lifetime and order mapping.
Share a ready-to-pay URL in chats, invoices or support conversations.
Show merchant logo, store name and visual styling on the payment page.
Lock the quoted amount for the invoice lifetime so customers know exactly what to send.
Create payments from your backend and send customers to paymentUrl.
Redirect customers to the hosted payment page returned by the API.
Send customers back to the right merchant page after success, failure or manual return.
Final status delivery for order reconciliation and backend automation.
Retry failed delivery attempts so temporary merchant outages do not lose status updates.
Override status delivery per invoice when one integration needs a separate endpoint.
Test payment creation, redirects and webhook handling before production traffic.
Track available funds by asset and network before withdrawal or reconciliation.
Move funds out by rule when thresholds, schedules or asset policies are met.
Let finance teams review and initiate withdrawals when extra control is needed.
Show the customer the missing amount instead of losing the order.
Credit funds even if the invoice has already expired.
Export operational data for finance, support and reconciliation workflows.
Send confirmations to customers or internal teams after important payment events.
Notify operators about payment events without requiring them to watch the dashboard.
Add a second layer of protection for account access and sensitive actions.
Limit API access by product area and reduce operational risk.
Restrict API usage to approved merchant infrastructure.
Make sensitive actions visible for owners and support teams.
Separate permissions for owners, developers, support and finance users.
Give teams a clear view of incidents, availability and integration status.
Show availability of scanners and supported blockchain networks.
Show fee economics before the sales conversation.
Blockchain network fee is paid by the customer on the selected network.
Generate payments, redirect users to checkout, receive final webhook statuses and reconcile merchant balances.
const payment = await qvard.payments.create({
externalId: "order_1024",
amount: 149.99,
currency: "USD",
successUrl: "https://shop.com/success",
failUrl: "https://shop.com/fail",
webhookUrl: "https://shop.com/qvard/webhook"
});
return payment.paymentUrl;Qvard answers the questions businesses ask before they trust a crypto payment processor: where the money goes, how statuses are delivered, how withdrawals work and how keys are protected.
Protect owner and finance actions with a second confirmation layer before sensitive changes.
Issue narrow keys for payments, balances or reporting instead of one all-powerful token.
Limit API traffic to approved servers so leaked credentials are harder to abuse.
Show who changed settings, keys, withdrawal rules or team access, and when it happened.
Trace delivery attempts, payloads and retries when an order status needs debugging.
Give teams a quick view of platform availability, incidents and integration health.
Track scanner and blockchain-network availability before it affects payment support.
Define how merchant balances move out, with manual review or automatic thresholds.
Separate operational balances by coin and network for clearer reconciliation.
A quick overview of how Qvard handles payments, integration and merchant operations.
Qvard is a custodial crypto payment gateway for businesses that need hosted checkout, invoices, API payments and merchant balances.
You can accept USDT, USDC, BTC, LTC, DOT, TRX, BNB, ETH, TON and USDT on TON. USDT is available on several networks, so customers can pay through the route they already use.
Yes. The integration is built around creating a payment, redirecting the customer to paymentUrl and receiving a final webhook status, so orders in your system update automatically.
Yes. You can set the shop name, logo, button color, return URLs and localized texts so the payment page feels like part of your product.
Create a merchant account, complete business verification and get access to the sandbox. After testing an invoice, connect hosted checkout, payment links or the API and start accepting real payments.
Funds are tracked in merchant balances separated by asset and network. You can withdraw manually or set up withdrawal rules for automatic payouts.
Guides for merchants and developers: accepting USDT, choosing networks, integrating the API and running day-to-day payment operations.
What is a crypto payment gateway? Plain-language guide to how crypto payment gateways work for online businesses.
Gateway basicsHow a custodial crypto payment gateway works. Plain-language guide to how crypto payment gateways work for online businesses.
Gateway basicsCrypto payment gateway for businesses. Plain-language guide to how crypto payment gateways work for online businesses.
Gateway basicsCrypto acquiring vs crypto payment gateway. Plain-language guide to how crypto payment gateways work for online businesses.
Gateway basicsHow to choose a crypto payment provider. Plain-language guide to how crypto payment gateways work for online businesses.
Accept cryptoHow to accept crypto payments on a website. Practical steps to start accepting crypto payments, from first invoice to go-live.