Redirect Crypto Invoice

Overview

A redirect crypto invoice is a checkout flow in which the merchant sends the customer from its website or application to another payment page to complete a cryptocurrency payment. The destination may be hosted by a payment provider, wallet service, or separate merchant payment domain.

The merchant creates the invoice server-side, receives a redirect URL, sends the customer to that URL, and later receives payment status through authenticated callbacks or API queries. Related operational concepts include Hosted Crypto Invoice, White-Label Crypto Invoice, and Crypto Payment Phishing. They should remain connected through identifiers and evidence without being treated as the same payment state, control, or financial result.

A robust implementation of Redirect Crypto Invoice treats the invoice, on-chain transaction, payment record, commercial order, and settlement entry as separate but connected objects. Controls include allowlisting redirect domains, preventing open redirects, binding the URL to an immutable invoice, using HTTPS, validating state or session data, expiring links, authenticating webhooks, and showing the payer the merchant, amount, asset, network, and destination clearly.

Those details prevent the term from becoming a vague label and allow merchants, developers, finance teams, and risk teams to apply the same meaning. Testing should cover duplicated and out-of-order events, incorrect asset or network data, late transactions, provider outages, retries after uncertain responses, and manual intervention after one subsystem has already changed state. Specific scope: a checkout flow in which the merchant sends the customer complete a cryptocurrency payment.

Governance should connect Redirect Crypto Invoice to the original obligation, payment instructions, observed transaction, internal state, financial posting, and any fulfillment or refund. The decisive principle remains that a redirect flow must secure both the outbound destination and the return path while relying on server-side payment confirmation rather than browser navigation.