Payment gateway vs crypto wallet for merchants

What a plain wallet does

With a wallet you publish an address, the customer sends funds to it and the money arrives on a blockchain you control. That has real advantages: no intermediary, no account to open, and funds reach you directly.

What it does not do is anything about your orders. A wallet knows that some coins arrived at an address; it does not know which order they were for.

Where a plain wallet becomes hard

As volume grows, five jobs appear that the wallet does not do for you:

1. Matching a payment to an order. If every customer pays the same address, you must tell payments apart by hand, by amount or by a note. Two orders with the same amount become a guessing game.
2. Exact amounts. Someone has to calculate the crypto amount for a dollar price and hold it still while the customer pays.
3. Watching the blockchain. You need to know when a payment arrived, whether it is complete and which network it came by.
4. Short, late and wrong-network payments. Each is a separate case with no status attached.
5. Records. You build the accounting trail yourself, from addresses and transaction hashes.

You can build all of this. It is a project, and it carries the risk of getting the money logic wrong.

What a gateway adds

A gateway takes the order-shaped jobs off you. With Qvard:

• You create a payment for each order with one POST to https://api.qvard.com/api/v1/payment, using your own order number as the id and the amount in US dollars as the price.
• The customer pays on a hosted page, choosing an asset and network and seeing the exact amount and the address. The rate is fixed for one hour.
• The payment has a status: wait, partial, completed or rejected. A short payment is a status, not a surprise.
• You learn the result by webhook, sent when the payment is completed, with your order number in it. See how to accept crypto payments on a website.
• Your funds sit on your Qvard balance and you withdraw them to your own wallet for the network fee. Withdrawal to a bank account in fiat is not available.

The gateway does not remove the need to think about refunds, accounting or support; it gives them a structure.

Cost and control

A fair comparison includes what each approach costs you.

• A wallet has no commission and no gateway. Its cost is your time, the risk of mistakes and the need to look after the keys yourself: a lost or leaked key means lost money.
• A gateway costs a commission. With Qvard there is no subscription fee; the commission is individual to your project and, per the pricing page, starts at 1% and can go down to 0.1%. In return you do not build or run the order-matching and monitoring layer.

Control is a trade. With a wallet you hold the funds from the first moment. With a gateway your funds first sit on the gateway's balance until you withdraw them, so consider how much you are comfortable leaving there and how often you withdraw.

How to choose

• A plain wallet is enough for a handful of payments, for donations where nothing has to be matched to an order, or for a first experiment.
• Use a gateway once you have regular orders, when customers pay at different times, when you need statuses and automatic confirmation, or when someone else needs to understand your books.
• You can start simple and move. Nothing stops you from using a wallet while you test the idea and a gateway when volume justifies it.

Whichever you choose, state the accepted coins and networks clearly, since sending on the wrong network loses money in both cases (see TRC20, ERC20 and BEP20 for payments). For the day-to-day routine of a gateway, see merchant operations checklist for crypto payments, and for the API itself crypto payment API for developers.

FAQ