What a payment gateway is
A payment gateway is the layer that turns "this customer owes this amount" into a completed, verified payment the merchant can rely on. In the card world it captures the buyer's details, routes the authorisation request to the acquiring and issuing banks, and returns an approved-or-declined answer. The merchant integrates once, against the gateway, and the gateway absorbs the protocol details of moving money. The defining property is that it stands between the act of paying and the merchant's back office, so the merchant never has to speak the payment network's raw protocol directly.
A crypto payment gateway plays the same role for blockchain payments, but the underlying mechanics are different. There is no bank to authorise and no card to charge. Instead the gateway issues a deposit address on the network the customer is paying with, presents the amount to send, and monitors that address for an incoming transaction. When the transaction is included in a block and confirmed, the gateway treats the payment as settled and notifies the merchant. The shared idea is constant — accept a payment, verify it, report it — even though the rails underneath are an open blockchain rather than the card networks.
Most gateways bundle more than just acceptance. A typical gateway also handles a hosted payment page or checkout, a record of each transaction, a way to pay money back out, and an event or callback mechanism so the merchant's systems learn about each result without polling. The point of the whole layer is to let a merchant accept and reconcile payments through one integration rather than wiring up each payment method by hand.
Why it matters for a merchant
For a merchant, the gateway is the difference between accepting payments and building a payment system. Without it, accepting crypto would mean generating addresses, running blockchain nodes or RPC connections for every network, deciding how many confirmations are safe on each chain, handling reorganizations that briefly undo a transaction, and matching incoming funds back to the right order — a substantial, error-prone amount of infrastructure. The gateway does that work once, for every merchant, and exposes the result as a simple, verifiable answer: this invoice was paid, this address received a deposit, this payout completed.
A crypto-specific gateway also has to handle the things that make blockchain payments unlike card payments. Amounts can arrive a little short or a little over, so the gateway has to recognise underpayment and overpayment rather than just pass or fail. Confirmation requirements differ per chain, so settlement is not a single uniform moment. And because a confirmed on-chain payment cannot be reversed by a third party, there are no chargebacks — but returning money to a customer becomes a deliberate outbound payout rather than a reversal. A good gateway encodes all of this so the merchant gets a consistent result regardless of which chain the customer paid on.
halfin as a crypto payment gateway
halfin is a crypto payment gateway: it is the infrastructure a merchant integrates once to accept digital-asset payments. The acceptance side is built around invoices — a merchant creates an invoice anchored to a fiat amount, halfin locks a rate and presents the crypto amount and a deposit address, and the customer can pay through halfin's hosted checkout or a self-hosted checkout the merchant renders against the same API. halfin issues the deposit address, monitors the network, applies a per-chain confirmation threshold with reorg-aware crediting, and recognises underpaid and overpaid deposits rather than only an exact match.
Acceptance is only half of a gateway. halfin also covers the outbound and operational pieces: static deposit addresses for funding a balance, single and mass payouts for paying money back out, balance conversion between assets for treasury rebalancing, and refunds. Results are delivered as HMAC-signed webhooks — events such as invoice.confirming, invoice.paid, invoice.overpaid, invoice.underpaid, invoice.expired, balance.credited, payout.completed and payout.failed — so a merchant's systems learn the outcome of each payment and act on it once the signature is verified. The whole surface is a spec-first REST API with scoped API keys and idempotency keys, plus a dashboard for operators, so a merchant accepts and reconciles crypto payments through one integration instead of building chain-by-chain plumbing.