A Bitcoin path through checkout
On-chain BTC checkout with a configured fixed address, an exact expiring server quote and a separate backend confirmation boundary.
Content revised · English
- Prepared asset
- BTC
- Confirmations
- 2
- Indicative wait
- ~20 minutes
- Chain monitor
- Not connected
Payment with precise context
The authenticated Bitcoin checkout displays a configured mainnet destination, exact cryptocurrency amount, quote expiry and confirmation threshold. The server obtains the USD rate and calculates the quote. The receiving address is fixed; it is not a newly generated wallet for each order.
Understand visibility
Bitcoin transactions are public. A payment address does not contain a name, but history and information from other services can create links. Treat pseudonymity as a condition to manage, not a guarantee.
Confirm before delivery
Broadcast, observation, sufficient confirmations and fulfilment are separate states. A trusted backend integration must independently validate a transaction and associate it with its order reference. No blockchain monitor is connected, and reaching a paid state would not provision a server.
The invoice should fix the uncertain parts
The server quotes the complete USD order total in the selected asset, with a rate timestamp and an explicit expiry shown in checkout. Read the address, asset, network and exact amount together. The receiving address is fixed rather than generated for each invoice; an order reference must be explicitly associated with a verified transaction. Do not invent a memo or assume that an amount alone uniquely identifies an order. Your wallet estimates its own Bitcoin network fee. A second transfer should never be the automatic response to an uncertain match.
Questions, answered.
How is a payment matched?
The payment request has an order reference, fixed mainnet destination, exact amount and expiry. A trusted server-side observer must explicitly associate that reference with a uniquely verified transaction. Neither the reused address nor an amount alone proves which order was paid.
What does the checkout verify?
It checks the account’s order, supported method and server quote. It does not monitor Bitcoin: transaction verification and confirmation updates require a trusted backend observer, which is not connected.
How many confirmations are proposed?
Two on-chain Bitcoin confirmations, with an indicative wait around 20 minutes. Congestion and wallet fees can change the timing.
What if the BTC rate moves while I prepare the transfer?
The exact expiry is shown in checkout. Use that quote’s amount and expiry. An expired unpaid request can obtain a fresh server quote; an observed transaction needs reconciliation rather than an automatic replacement payment.
Can I use Lightning instead?
No. The prepared BTC route is on-chain. Lightning is explicitly outside the current payment catalogue.
Can one payment cover a year?
The prepared flow uses the selected billing cycle’s full total. An annual term is one 12-month invoice amount, not 12 monthly BTC collections.
How would a Bitcoin refund be valued?
The proposal preserves the initial USD payment value and converts it to BTC at the current refund rate, subject to the product and timing rules. The BTC quantity can differ from the original transfer.
Can I choose another payment asset for the same plan?
The prepared payment selection is separate from the plan. Use only a route listed in checkout and follow the exact asset/network instructions.