Crypto Payment Gateway

Overview

The basic problem a gateway solves

Imagine a shop that sells a $40 digital product. Its shopping cart knows the order number, customer and amount, but a blockchain does not know what an order is. It records transfers between addresses. If the shop merely displays a wallet address, someone must still discover the correct transfer, check its network, compare its amount and decide which order it belongs to. A payment gateway automates much of that connection. It turns the commercial instruction “collect $40 for order A102” into payment instructions and converts observed transfers into useful order information. This connection, not the QR code itself, is the key service.

How the underlying system works

A gateway connects a commercial order to an observable blockchain payment. The merchant creates a payment request with an amount, currency, supported network and order reference; the gateway presents payment instructions and records incoming transfers. Confirmation and status rules translate blockchain events into information that a commerce application can use. The merchant still needs to decide when to fulfill the order and how to handle exceptions.

Providers vary materially. One gateway may send funds to a merchant-controlled address; another may receive assets in its own accounts and credit an internal balance. Conversion, refunds, supported coins, network matching, settlement timing and fee allocation can therefore be separate services. Evaluate these responsibilities in the agreement and actual funds flow, not from the label 'gateway' alone.

Follow one payment from click to fulfillment

A buyer chooses to pay in crypto. First, the store creates a payment request and saves the request identifier beside its own order number. The gateway displays the supported asset, exact network, destination and any amount or expiry rules. Next, the buyer submits a blockchain transfer. The gateway detects the transfer and checks whether it matches the request. It may wait for a confirmation policy before reporting an accepted payment. Finally, the store checks the authenticated notification or status endpoint and changes the order state. The store—not the blockchain—decides whether to deliver the product. If the invoice expires while a transaction is pending, an exception rule matters more than the payment screen's appearance.

What a gateway cannot promise by its name alone

A gateway may be custodial, non-custodial or part of a wider provider arrangement. “Payment received” does not tell you whether an external merchant wallet already holds the assets, whether the balance is withdrawable, or whether a conversion occurred. Nor does an address appearing on a page prove that it supports the buyer's chosen chain. Ask where the funds go, who controls the keys, what confirmation conditions apply, and how missing or duplicate notifications are handled. In a responsible integration, a browser “payment completed” page is informational; a verified server-side state triggers fulfillment.

Further reading and related concepts

Reference documents: OxaPay — Generate Invoice, OxaPay — Payment Status Table.

Related glossary topics: Crypto Payment Processor, Crypto Payment Service Provider, Crypto Settlement.