Accepting payments from customers without cards

Who pays without a card

Three groups account for most of them:

• Customers whose cards do not work for you. Their bank declines foreign or online purchases, a card network or your processor does not serve their country, or they have no card in their own name.
• Customers who prefer not to use a card. They want to keep card details off the internet, avoid card limits, or simply keep their money in dollar stablecoins already.
• Businesses paying invoices. A company that pays suppliers by transfer finds a stablecoin payment faster and cheaper than an international bank transfer.

None of them needs a bank's permission to send a stablecoin. They need a wallet or an exchange account that holds one.

What they need to pay

A customer needs three things, and it helps to say so on your checkout:

1. A dollar stablecoin, such as USDT or USDC, in a wallet or on an exchange. Qvard accepts several assets; see the supported coins.
2. Enough to cover the network fee of the transfer, paid by the sender on top of the amount, usually in the network's own coin or resources.
3. The right network. The same coin exists on several networks, and funds sent on the wrong one do not arrive. The payment page shows the network next to the address.

The price is in US dollars, so the customer knows what a dollar-pegged coin is worth. The amount on the payment page is fixed for one hour, so it does not change while the customer prepares the transfer.

Make the first payment easy

Someone new to crypto will hesitate at the first transfer. A few things remove most of the friction:

• Say what happens, in four lines: you choose the coin and the network, the page shows an address and an exact amount, you send it from your wallet, and the order is confirmed automatically when the payment is complete.
• Tell them to copy, not type. The amount and the address on the payment page are meant to be copied.
• Warn about exchange fees. If the customer pays from an exchange, the amount that must arrive is the one shown, and the exchange may take a withdrawal fee on top. If less arrives, the payment gets the partial status and the order stays open until the rest comes.
• Show the status. An order page that says "waiting for payment", "received, X missing" or "paid" stops people from paying twice or writing to support.

A demo invoice lets you see, and show, exactly what the customer will see.

What to prepare on your side

Accepting payments without cards changes a few habits.

• Mark an order paid only from the webhook. Qvard sends it when the payment is completed; your endpoint must answer exactly HTTP 200 and be safe to run twice.
• Decide your rule for a short payment. Ask for the difference or refund, and write it down. See how to handle USDT underpayments.
• Write a refund rule. A crypto payment cannot be reversed by the sender or pulled back by you; a refund is a transfer you send to an address the customer gives you, on the network they confirm.
• Keep a support contact visible on the payment path. Wrong-network mistakes need a human.
• Plan how you take the money out. You withdraw to your own crypto wallet for the network fee; withdrawal to a bank account in fiat is not available.

Integration and what is ready

Qvard works through the API: your server creates a payment and receives a webhook. There is no ready-made plugin for store platforms yet, and payment links and a separate sandbox are in development, so the integration takes a developer. Start with how to accept crypto payments on a website, and see crypto payments vs card payments for how the two compare.

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%. Check the tax and legal treatment of crypto receipts for your country and your customers' countries with your own advisers before you launch.

FAQ