Understand the asset
Bitcoin payments use a public transaction ledger. Fees and confirmation times vary with network conditions and the fee selected by the sender.
Before you send
Wait for the invoice’s required confirmations. Do not interpret a broadcast transaction as a verified payment.
What privacy means here
Bitcoin transfers are publicly visible. A hosting account without identity documents does not make the transaction private.
After payment
Payment should be confirmed only after the invoice has been reconciled under its confirmation policy. If a payment is delayed, provide the transaction identifier and invoice number through a verified support channel. Never provide a wallet recovery phrase or private key.
Bitcoin mainnet only
The configured BTC route uses an on-chain Bitcoin address. It does not issue a Lightning invoice. Transaction fees and the time before inclusion depend on the network and wallet policy. Check the required confirmations on the actual payment request rather than assuming a ten-minute promise.
Keep the payment record useful
Retain the order reference, quoted asset and network, expiry and transaction identifier. Contact support through a verified channel if reconciliation is needed. A support enquiry should never include a wallet seed, private key or signing credential.
A little more clarity.
Can I use a Lightning invoice for this BTC order?
No. This checkout accepts on-chain Bitcoin mainnet for BTC. A Lightning guide does not enable a Lightning payment route.