What is a crypto payment gateway, and how does a business start taking payments through one?

A crypto payment gateway is a service that lets customers pay you in crypto almost as easily as they pay by card: they see an amount and an address, send the coins, and your shop learns the order is paid without anyone watching a blockchain by hand. You connect one through a payment link, a button on your site or an API, and it keeps a small percentage of each payment. It earns its place when some of your customers can't pay you by card.

What the gateway does between "Pay" and "Paid"

Without a gateway, taking crypto means publishing your wallet address and matching incoming transfers to orders by hand. That holds up at one sale a week. It falls apart the first time two customers each send 50 USDT within the same minute and you can't tell whose order to ship.

USDT, the coin in that example, is a stablecoin: a crypto dollar designed to stay worth one US dollar. Sellers like it because a price in USDT doesn't drift while the customer is paying.

A gateway takes the matching off your hands. Here is one payment from start to finish, for a customer buying a $50 online course:

1. Your shop creates an order. Your site tells the gateway that order 1042 is waiting for $50.
2. The gateway issues an invoice. The customer sees the amount in the chosen coin, the network to send it on, a payment address for this invoice and a QR code that holds all three. The network is the blockchain the coin travels on: USDT, for example, exists on TRON, Ethereum and several others.
3. The customer sends the coins. They pay 50 USDT from their own wallet or straight from an exchange account, on the network the invoice names, before the invoice expires.
4. The gateway waits for confirmation. It sees the transfer arrive and waits until the network has recorded it for good. For USDT on TRON that takes about a minute; for Bitcoin it takes longer, because a new Bitcoin block appears roughly every ten minutes.
5. The gateway tells your shop. It marks the invoice as paid and sends your server a message, and your site unlocks the course.
6. The money reaches you. Depending on the gateway, it goes straight to your own wallet or onto your balance with the service, from which you withdraw it.

The network in the second step is a choice you make once, when you set up the gateway. Customers hold USDT on particular networks and pay from there, so the networks you accept decide who can pay you without extra steps. Before you tick the boxes, it helps to know which USDT network suits a merchant, as opposed to a sender.

The fourth step hides the biggest difference from cards: once confirmed, a crypto transfer can't be reversed. The customer's bank has no button to pull the money back, so there are no chargebacks. The flip side is that a mistake doesn't undo itself either. A customer who sends the wrong amount or uses the wrong network needs someone on your side to sort it out, which we come back to further down.

The fifth step deserves a developer's full attention, even on a small site. The message the gateway sends your server is called a webhook, and your site should act on it only after checking two things:

• It came from the gateway. A shop that ships on any message saying "paid" can be fooled by a forged one sent to the same address.
• This order hasn't been handled yet. A shop that doesn't check for repeats can ship the same order twice when the gateway resends a message.

The details are in how to process crypto payment confirmations safely.

Who needs a crypto gateway, and who can do without one

Crypto doesn't replace cards for most shops. A gateway earns its place in a handful of situations:

• Your customers are abroad and their cards fail. A buyer whose bank blocks foreign payments, or who lives in a country cut off from international card networks, can still send USDT.
• Card processors won't take you on. If the big online payment providers don't onboard businesses from your country, a crypto gateway may be the way to take online payments at all.
• You sell in chats, not through a site checkout. A payment link works in Telegram, WhatsApp or email, with no checkout page of your own.
• You invoice foreign clients for larger sums. A USDT transfer arrives within minutes, where an international bank wire can take days.
• Chargebacks cost you money. A buyer of digital goods can dispute a card payment after downloading the product; a confirmed crypto payment can't be clawed back that way.

If all your customers pay by card without trouble, a gateway adds an option few of them will use. It can still sit as a second button next to card checkout, for the occasional customer whose card won't go through.

If you're here because payments from abroad keep bouncing, crypto is one route among several, and not always the first one to try. The full set of options is laid out in how to get paid by customers abroad when the money won't come through.

Three ways to connect a gateway

A gateway plugs into a business at one of three depths. Which one you need depends on where you sell, not on how big you are.

A payment link, when you have no checkout of your own

You create an invoice in the gateway's dashboard and send the customer its link, in a chat, an email or a direct message. The customer opens a payment page run by the gateway and pays, and the invoice status changes in your dashboard. There is nothing to install and no code to write.

Say a designer bills a client in Germany 800 USDT for a logo. She creates the invoice, pastes the link into her email and sees it marked paid a few minutes after the client sends the money.

The limit is that every payment stays manual on your side. You create each invoice, check each status and deliver each order yourself, which is fine at a few dozen orders a month and tiring at a few hundred. A link also works as a QR code printed on a counter or placed inside a PDF, one of the ways to accept USDT through payment links and QR invoices without a full integration.

A button on your site

You add the gateway's script to your page, and a "Pay with crypto" button appears. When the customer clicks it, the gateway's checkout opens in a window over your page, so they pay without leaving your site and you don't have to build a payment page of your own.

It suits any site whose page code you are allowed to edit. It is still a job for someone who can insert a script and tell your site what to do when the payment completes: the button reports the result, and your page has to act on it, from unlocking a download to updating stock.

Before you plan around a button, ask the gateway two things:

• Which domains it works on. Some buttons run only on a domain you have registered with the gateway.
• Whether a fixed price needs a server. A button that charges an exact order amount may need your server to create the order first.

Compared with a full integration, a button takes far less developer time and leaves the design of the checkout to the gateway. Where that trade pays off, and where it doesn't, is the subject of when an HTML payment widget beats an API or a plugin.

An API, when crypto becomes part of your own system

An API is a set of commands your server sends the gateway. The basic ones are:

• Create an invoice. Your server asks for an invoice for a specific order and amount.
• Check the status. Your server asks whether that invoice has been paid.
• Send a payout. Your server tells the gateway to send money to an address.

Your developer wires those commands into your checkout, so crypto appears as one more payment method and orders mark themselves paid. No one on your side touches individual payments.

It is the most work and gives the most control. Through an API you can also send money out, for example paying affiliates or suppliers in USDT, and keep every payment tied to a customer record in your own database. A marketplace, for instance, can take a buyer's payment through the API and later pay the seller's share out the same way.

Before a developer commits time to one provider, check how its API handles four things, because each is cheaper to check now than to fix after launch:

• Test payments. A test mode lets you run the whole flow without real money.
• Errors. Clear error messages tell your developer what went wrong with a request.
• Repeated notifications. The gateway may send the same notice twice, and your system has to recognise it.
• Payouts. If you plan to send money out, check that the API can do it, and how.

A fuller version of this list is the checklist for vetting a crypto payment API before you integrate it.

A Telegram bot, when you sell inside the messenger

A Telegram bot that sells access or goods runs on the same API. The customer taps "Buy" in the chat, the bot asks the gateway for an invoice and sends back the payment link, and once the gateway reports the payment, the bot hands over what was bought.

For sellers of courses, subscriptions and private channels, the appeal is that the customer never leaves the chat and nobody on your side has to check payments at night. A coach selling a monthly plan in a private channel, for example, can let the bot add each paying subscriber to the channel and remove them when the month runs out.

Setting it up takes three things:

• A developer, or your own time if you write code.
• The gateway's API keys, which you get in its dashboard.
• An address for notifications, where the gateway tells the bot that a payment has arrived.

The whole sequence is in how to connect a crypto payment gateway to your Telegram bot.

Which one to start with

Start where your sales already happen:

• You sell in chats or by invoice. Payment links are enough.
• You have a site you can edit. The button takes the least work.
• Payments must feed your own order system or a bot. That calls for the API.

These are three ways of using one gateway, not three different products. Moving from links to the API later doesn't mean switching services, as long as the gateway you pick offers all three.

CryptumPay, for example, works all three ways:

• Payment links. You create an invoice in the console and send the link anywhere, with no site integration and no code. A website that shows what you do or sell is still needed for the project review before live payments are enabled.
• A checkout widget. One button on your site opens the full checkout in a window. It works on domains added to your project; for a fixed order amount the order is created from your server, and without a server the customer enters the amount themselves.
• An API. It covers orders, deposits and payouts.

How to connect a gateway to your website, step by step

Whichever gateway you choose, a website setup goes in roughly this order:

1. Open an account. If the gateway asks for identity documents, send them at the start rather than when the first payment is already waiting.
2. Choose the coins and networks you accept. Starting with USDT on one or two inexpensive networks keeps the checkout simple for customers.
3. Add the button or connect the API. The button goes into your page code; the API needs a developer and the keys from your gateway dashboard.
4. Point the notifications at your site. Give the gateway the address on your server where it should send payment updates, so orders mark themselves paid.
5. Make a small real payment yourself. Send a few dollars from your own wallet and watch the order move to "paid".
6. Withdraw once. Before real customers pay, check that the money comes out the way you expect, to the address you expect.

Most of the difference between website platforms sits in the third step: where the code goes in a site builder, and what a store engine lets you change. The platform side is covered in how to accept crypto payments on your own website.

What a crypto payment gateway costs

The cost of a crypto payment has three layers, and only the first is the gateway's fee:

• The gateway's fee. A percentage of each successful payment. Among well-known hosted gateways in 2026, published fees run from zero to about two percent, some with a small fixed amount on top; self-hosted software charges no fee at all, but you run the server yourself.
• The network fee. Every transfer pays the blockchain for recording it. The customer's wallet or exchange pays it when they send, so it doesn't come out of your price.
• Getting the money out. Withdrawing from the gateway, converting one coin into another and selling crypto for bank money can each cost a fee or an exchange-rate margin.

On a $200 order, a 1% gateway fee is $2. It is tempting to stop at that number, yet a withdrawal fee or a poor conversion rate can cost more than the fee itself. Compare gateways on the whole path of a typical order, from the customer's payment to money you can spend, using how network fees, gateway fees and checkout costs add up.

At CryptumPay, the fee is 1% per successful payment, dropping to 0.5% at higher volumes. On the $200 order above, that is $2, and you can pass it on to your customer instead of paying it yourself.

The network fee doesn't touch your margin, but it shapes what your customers do. On a $20 purchase, a fee of a few dollars feels like a surcharge, and a customer who sees one in their wallet may abandon the payment. On TRON there is a second catch: the fee is paid in TRX, the network's own coin, so a customer who holds only USDT in a personal wallet may be unable to send it until they buy some TRX. A customer paying straight from an exchange account doesn't hit this, because the exchange sends the transfer and charges its own withdrawal fee instead. What all this means for a shop that takes USDT is set out in how to accept TRON payments on your website and what they really cost.

The third layer is the easiest to overlook, because it only shows up after the sale, when the first payout arrives smaller than the dashboard promised. Find out each of those costs before you sign up, and run them on your usual order size: a fixed withdrawal fee hurts a seller of $10 items far more than one who sells at $1,000.

What happens to the money after it arrives

If you accept bitcoin or another coin whose price moves, the money you were paid can shrink before you withdraw it. A 5% dip between payment and withdrawal turns a $1,000 day of sales into $950. A gateway gives you two defences:

• Price in a stablecoin. Ask customers to pay in USDT, and what you receive keeps its dollar value.
• Convert on arrival. Let customers pay in any coin and have the gateway turn each payment into a stablecoin as soon as it lands.

How far to take that protection, and what it costs, is a question of its own, answered in how to protect crypto funds from market volatility when accepting payments.

Whatever gateway you choose, find out where your money sits between payment and withdrawal. A balance held by the service is convenient, but until you withdraw, you are trusting the service with your money. A gateway that pays straight into your own wallet leaves the money with you, and the responsibility for keeping it safe with you too.

CryptumPay converts incoming payments to USDT as soon as they are credited, so your balance never sits in a coin whose price swings. You can withdraw at any time, with no minimum amount, by hand or automatically, to any address you set: your own wallet, an exchange account or a supplier you are paying. CryptumPay requires every merchant, without exception, to pass KYC, an identity check; without it, withdrawals are not possible.

USDT on a balance is not yet money in a bank account. To pay rent or salaries in dollars or euros, you sell the USDT through an exchange or a broker and send the proceeds to your bank, a step known as an off-ramp. The routes, and what each asks of a business, are set out in how crypto payments become money your business can use.

What goes wrong with crypto payments, and who sorts it out

Because a confirmed transfer can't be reversed, a customer's mistake stays put until someone fixes it by hand. Four cases are worth planning for before the first one arrives:

• Wrong network. USDT exists on several networks, and a customer can send it on one the invoice didn't ask for. The gateway won't see that transfer, and whether the money can be recovered depends on the gateway.
• Wrong amount. Some exchanges subtract their withdrawal fee from the amount sent, so 99 USDT arrives on a 100 USDT invoice. To the gateway, that is an underpayment.
• Too late. The customer pays after the invoice has expired, and the money lands on a closed invoice whose exchange rate no longer holds.
• Money from a flagged address. Some gateways check incoming transfers against lists of addresses linked to theft, fraud or sanctions, and may hold a payment that comes from one.

Each of these ends up with your support team, so ask a gateway how it treats them before you sign up. Does an underpaid invoice wait for the customer to top it up, or get marked as partly paid? Is a late payment credited at the new rate, or returned? The seller's side starts with the invoice itself: what a crypto invoice must say and what to do when the amount is off.

The flagged case is the hardest to plan for, because the decision isn't yours. Screening exists to protect you: money traced to a theft can be frozen later, when you try to sell it, and then the loss is yours. Ask whether a gateway screens incoming payments, who decides what happens to a held one and whether the customer can get it back.

Many wrong-network and wrong-amount cases can be prevented on the payment page itself. An invoice that names the network in large letters, shows the exact amount to send and warns that exchanges may deduct a fee leaves the customer far fewer ways to slip.

No chargebacks also means refunds are your job. A refund is a new transfer from you to the customer, to an address they give you, and you pay the network fee for sending it. It is final too, so check the address twice. Before the first case reaches you, settle how your business will handle crypto refunds, overpayments and mistaken transfers.

What to ask any gateway before you sign up

Gateways look alike on their home pages. These questions tell them apart:

• Which coins and networks does it accept? The networks your customers already use should be on the list; the rest matters less.
• What happens to an underpaid, overpaid or late invoice? The answer decides how many support emails you will write.
• How does your site learn about a payment? Look for signed notifications and a test mode you can try before going live.
• Does it convert incoming payments to a stablecoin? Automatic conversion saves you from watching prices.
• When can you withdraw, and what is the minimum? A high minimum or a fixed payout schedule keeps your money with the service longer.
• What verification does it ask for, and when? Documents sent at sign-up are better than documents demanded at the first withdrawal.
• What does a typical order cost you in total? Add the gateway fee, the withdrawal fee and the conversion margin on your usual order size.

If you'd rather see that arithmetic done for you, here are ten crypto payment processors compared by total cost.

The short version

A crypto payment gateway turns a blockchain transfer into an ordinary "paid" on your order: it issues the invoice, watches the network and tells your shop. Three decisions shape how well it works for you:

• How to connect. Choose links, a button or the API by where you sell, not by how big you are.
• What it costs. Compare the whole path of a payment, not the headline fee.
• What happens afterwards. Decide in advance where the money goes once it arrives and who handles the payments that go wrong.

Frequently asked questions

Is a crypto payment processor something different from a gateway?

Mostly not: the two names describe the same kind of service, and providers use them interchangeably. Some reserve "processor" for a company that also holds and converts the money, and "gateway" for the part that shows the invoice and watches the network. When you compare services, the label matters less than what each one does with your money after the payment confirms.

Is there a crypto payment gateway that works without KYC?

Some services advertise accounts without identity checks. The catch is timing rather than principle: a service that skips the check at sign-up can still ask for documents later, for example after it flags a payment, and until then your money waits. Why gateways check merchants and the funds their customers send is explained in how AML, KYC and wallet screening protect crypto payments.

How do you create your own crypto payment gateway?

The shortest route is open-source payment software you install on your own server, after which payments land straight in your own wallet with no company in between taking a cut. In exchange, every job a hosted service would do for you becomes yours, including the unglamorous ones that only show up after a payment goes wrong. The software is free; the hours your developer spends keeping it running are not. It makes sense for a team with a developer to spare and a reason to hold the money directly; for most sellers a hosted gateway is the shorter road.

Does a crypto payment gateway work in my country?

The blockchain doesn't care where you are, but two things are local. The gateway decides which countries' businesses it takes on, so check its list of supported countries before you sign up. Your country's law decides whether, and on what terms, a business may accept crypto at all. Before the first payment, check the rules in force where your business is registered, starting with whether a business may legally accept crypto payments.

This article is general information, not legal or tax advice.