Hosted Checkout

Overview

Why Hosted Checkout matters

Building a secure crypto checkout requires asset selection, address display, invoice expiration, wallet-friendly payment instructions and payment monitoring. A hosted page can package these functions so a merchant integrates a redirect or link instead of implementing every screen and state update. It also makes the provider's reliability and branding important to the customer's experience.

How it works

A merchant's server creates a payment request with amount, currency, order reference, permitted assets and supported networks. The provider returns a checkout URL, and the merchant directs the customer to it. The customer chooses a supported rail and sends a transfer according to the displayed details. The provider monitors network events and updates its checkout state. Separately, the merchant's backend should consume authenticated server-to-server notifications or query a trusted API to decide whether to fulfill the order. Browser redirects and "success" pages are helpful for user experience, but they can be closed, spoofed or reached before all business checks have completed. The provider may or may not convert or custody funds depending on the product arrangement.

A redirect is not a settlement receipt

Hosted checkouts normally rely on two different communication channels. The browser channel redirects the customer to and from the provider's page and supports user-facing status messages. The server channel uses signed webhooks or authenticated API lookups to tell the merchant backend what the provider has actually verified. If the customer closes the browser, the server channel must still be able to update the order. If an attacker forges a success URL, the merchant backend must not treat that redirect as authenticated payment proof. Developers should test duplicate webhook delivery, out-of-order events, temporary API outages and changes in invoice status after initial detection. Security and reliability depend on correct integration as well as the hosted page itself.

A real-world payment example

An online store receives an order for $120 and opens a hosted crypto checkout. The customer pays, then closes the browser before returning to the store. If the store relies only on the return URL, it may never fulfill a legitimate payment. A safer integration reconciles the order using verified payment events and status lookups independently of the customer's browser.

Limits and common misunderstandings

Hosted pages create dependencies on provider uptime, phishing resistance, domain trust and the provider's supported networks. Merchants should use HTTPS, clear branding, correct payment amounts and expiration rules, and carefully check signed webhook or API responses. A checkout URL should not include secret merchant API keys.

How it differs from related concepts

Hosted checkout is an externally hosted user interface. Embedded checkout appears within a merchant-controlled page. A crypto gateway may offer either while settlement and custody remain separate design decisions.

Explore further

Official background: technical documentation.

Related glossary terms: Crypto Checkout, Crypto Invoice, Webhook.