A Bitcoin transaction that appears in the mempool has been broadcast, but it has not yet been confirmed in a block. For most merchants, that means the payment should remain pending rather than trigger irreversible fulfillment. A payment processor can supply invoice, status, and notification workflows; direct wallet acceptance leaves payment detection and risk decisions to the merchant. BTCPay Server offers a middle path: checkout and invoice software with payments sent to wallets the merchant controls.
What “unconfirmed” means at checkout
When a customer broadcasts an on-chain Bitcoin transaction, it may become visible to nodes before miners include it in a block. Seeing it is evidence of broadcast, not proof of settlement. Until confirmation, the transaction remains exposed to double-spend risk: a conflicting transaction may be broadcast, or the payment may fail to confirm.
Confirmation depth is the number of blocks added after the block containing the transaction. More confirmations generally provide stronger protection, but a merchant should not treat one specific count as universally right for every order. Bitcoin.org’s Payment Processing guide says high-value or fraud-sensitive payments should wait for at least six confirmations and identifies accepting unconfirmed payments as a case requiring double-spend risk analysis.
How processors and direct acceptance differ
| Approach | What the merchant gets | What the merchant must decide or operate |
|---|---|---|
| Managed payment processor | Hosted checkout or invoices, transaction monitoring, payment states, and notifications that can connect to order systems. | Understand the provider’s status definitions and security guidance; set fulfillment rules and verify authoritative invoice status. |
| Direct wallet acceptance | Payments observed by the merchant’s own wallet or payment infrastructure. | Associate transactions with orders, distinguish mempool activity from confirmations, monitor delays and conflicts, and implement fulfillment logic. |
| Self-hosted processor such as BTCPay Server | Invoice and checkout workflows while payments go to merchant-controlled wallets. | Operate and monitor the server, node and integration, and choose a confirmation policy and fulfillment response. |
A processor can reduce the amount of payment-detection software a merchant has to build, but its status notifications are workflow signals, not a guarantee that a transaction cannot be challenged. The available sources do not establish which party bears losses from conflicting spends under a particular provider’s terms; merchants should not assume a processor eliminates that risk.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems#1 Best Overall
- BITCOIN EXCLUSIVE, PHONE VERIFICATION: Bitkey is designed from the ground up exclusively for bitcoin — a dedicated hardware wallet for secure bitcoin storage. Approve transactions with a tap using your phone and NFC. No device screen is required.
- SELF-CUSTODY, NO EXCHANGE OR CUSTODIAN REQUIRED: You hold two of the three keys in the Bitkey system – one on your phone and one on your Bitkey device. The third is stored on Bitkey’s server and cannot move your bitcoin on its own.
- NO SEED PHRASE: Set up and use Bitkey without creating or storing a seed phrase.
- 2-of-3 MULTISIG: Three keys are stored separately across your phone, Bitkey device, and Bitkey’s server. Any two keys are required to move your bitcoin.
- BUILT-IN RECOVERY: Encrypted backup and recovery tools can help you regain access if you lose your phone or Bitkey device. You can also designate a Recovery Contact.
When a processor is useful—and what to verify
A managed processor is useful when a merchant needs checkout, invoice creation, payment tracking, and integration events without building those pieces from scratch. The merchant still needs to connect invoice states to order states deliberately.
BitPay’s support article, “How do I prevent fraud on unconfirmed payments?” (updated August 16, 2026), recommends fulfilling only when an invoice is “Confirmed” or “Complete.” It also says to fetch the invoice status after an IPN (Instant Payment Notification), because IPNs are not secure. In other words, use the notification to know when to check; retrieve and validate the invoice’s status before fulfillment. BitPay’s developer documentation describes its invoice confirmation states and notification timing.
Rank #2
- Unparalleled Security: Protect your assets NDA-free EAL 6+ Secure Element, offering robust defense and complete transparency
- Simple & Secure Interface: Manage your digital assets easily with a clear OLED screen for secure on-device confirmations
- Supports 1000s of Coins & Tokens: Securely handle thousands of assets, including Bitcoin, Ethereum, and more, all in one wallet
- Effortless Asset Management: Monitor and transact seamlessly with Trezor Suite, our intuitive desktop and mobile app
- Enhanced Backup Solution: Rest assured with Multi-share Backup, eliminating single points of failure for secure cold wallet recovery
- Check the provider’s exact meanings for pending, paid, confirmed, and complete; labels are provider-specific.
- Verify the current invoice status through the provider’s documented method instead of trusting a webhook or IPN alone.
- Make order fulfillment conditional on the status and risk policy you intend to use.
- Do not infer that a provider’s invoice state promises a particular loss allocation; review the provider’s applicable terms.
What direct unconfirmed acceptance requires
Accepting an on-chain payment directly while it is unconfirmed puts the risk decision in the merchant’s hands. The merchant needs to match the transaction to the correct order, detect whether it is only in the mempool or has entered a block, and decide what to do if it conflicts, remains unconfirmed, or confirms later than expected. Bitcoin.org notes that nodes and applications can provide confirmation information, but accepting before confirmation merits risk analysis.
This can be a conscious business choice when the amount is small and the fulfillment is reversible or low-cost. It is a poor default for high-value orders or goods that cannot be recovered once handed over. The core question is not simply “Did the wallet see a transaction?” but “What is the cost to the business if this transaction does not become confirmed?”
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
- Unparalleled Security: Protect your assets with EAL 6+ Secure Element, offering robust defense and complete transparency
- Simple & Secure Interface: Manage your digital assets easily with a clear OLED screen for secure on-device confirmations
- Supports 1000s of Coins & Tokens: Securely handle thousands of assets, including Bitcoin, Ethereum, and more, all in one wallet
- Effortless Asset Management: Monitor and transact seamlessly with Trezor Suite, our intuitive desktop and mobile app
- Enhanced Backup Solution: Multi-share Backup eliminates single points of failure for secure cold wallet recovery
BTCPay Server: workflow with merchant-controlled wallets
BTCPay Server supplies invoice and checkout functionality while recording payment to wallets controlled by the merchant. Its User Guide describes on-chain settlement according to the store’s configured confirmation policy, and its eCommerce Integration Guide distinguishes InvoiceProcessing—a full payment observed in the mempool—from InvoiceSettled, which follows the configured confirmation policy. An integration should preserve that distinction rather than mapping both events to “paid and fulfill.”
This model avoids handing wallet control to a hosted processor, but it is not operationally hands-off: the merchant is responsible for server, node, integration, and monitoring reliability. BTCPay’s Wallet FAQ discusses mempool full-RBF configuration and double-spend detection behavior; those details matter to operators configuring how they observe transactions. The broader BTCPay documentation covers its self-hosted payment-acceptance setup.
Rank #4
- Dual-chip architecture for maximum protection: The next-gen, fully auditable TROPIC01 chip works alongside a certified EAL6+ Secure Element—completely NDA-free—to deliver radically transparent, industry-leading defense against physical attacks.
- Quantum-ready security: Get protection against future threats with the first-ever hardware wallet designed with quantum-ready architecture.
- See every detail with confidence: Our largest high-resolution color touchscreen makes it easy to navigate your assets, review transactions and manage your coins with clarity.
- Wireless freedom with encrypted Bluetooth control: Manage, buy, swap and stake securely using Trezor Suite on desktop or mobile. Qi2-compatible wireless charging keeps your Trezor powered up. No cables required—security meets convenience.
- Works seamlessly with Android, iOS and desktop: Connect wirelessly or via USB-C to your phone or computer. Manage your crypto anywhere with our companion Trezor Suite app.
Choose a policy based on the order, not a universal count
A sound fulfillment policy takes account of what is being sold, what the merchant could lose, and how the payment route works. Bitcoin.org’s six-confirmation guidance applies to high-value or fraud-sensitive cases; it is not a universal instruction for every transaction. Separately, BitPay says it requires six BTC confirmations before funds are credited to a BitPay merchant account. That is BitPay’s crediting policy, not a general Bitcoin rule. BitPay notes that confirmation timing is determined by the network, so no exact wait time is guaranteed.
- Low-value, reversible fulfillment: A merchant may choose to release access earlier, but should explicitly accept the residual double-spend and non-confirmation risk.
- Irreversible or high-value fulfillment: Keep the order pending until the confirmation policy selected for that risk is met; Bitcoin.org advises at least six confirmations for high-value or fraud-sensitive payments.
- Delayed confirmation: Keep the order in a pending state, communicate that the transaction has not settled, and avoid treating elapsed time or a processor notification as confirmation.
- Conflicting or dropped transaction: Follow the payment provider’s documented status and recovery process, or, for a direct setup, your own monitoring and exception workflow. Do not fulfill solely because the original transaction was once visible.
Lightning is a separate payment route
Lightning should not be described as an on-chain transaction with zero confirmations. BTCPay says Lightning payments settle without on-chain confirmations. Its settlement mechanics differ from an on-chain payment waiting for block confirmations, so apply the payment status and risk rules for the route actually used.
Quick Recap
Best Value
- Effortlessly build your crypto portfolio via the all in one Ledger Wallet app: buy, sell, send, receive, swap, stake and more across popular blockchains. 15,000+ coins & tokens in a single dashboard. Keep a close eye on the market. Compare service providers. Track performance. Get timely alerts. Build your portfolio with confidence.
- Effortlessly build your crypto portfolio via the all in one Ledger Wallet app: buy, sell, send, receive, swap, stake and more across popular blockchains. 15,000+ coins & tokens in a single dashboard. Keep a close eye on the market. Compare service providers. Track performance. Get timely alerts. Build your portfolio with confidence.
- Enjoy Bluetooth connectivity, iOS access, and hours of battery use with this mobile-first, secure backup signer. Freedom you can depend on.
- Genuine Check: confirm your signer is authentic during setup with the Ledger Wallet app.
- Protect your signer: keep it in mint condition at all times with a bespoke Pod or Case to avoid scratches and everyday wear and tear.
Practical implementation checklist
- Define order states. Keep “broadcast or mempool-seen,” “confirmed,” and “fulfilled” distinct in your checkout and commerce system.
- Set a risk-based fulfillment rule. Consider order value, fraud incentives, and whether goods or services can be revoked or recovered.
- Validate processor events. For BitPay, retrieve invoice status after an IPN and use the authoritative status when deciding whether to fulfill, following its fraud-prevention guidance.
- For BTCPay integrations, preserve event semantics. Treat
InvoiceProcessingas mempool-observed and wait forInvoiceSettledaccording to the configured policy when that is your fulfillment threshold. - Plan for exceptions. Decide how staff and software will handle slow confirmation, underpayment, conflicting spends, and customer questions such as “When will my payment confirm?”
- Separate routes. Handle on-chain confirmation policy separately from Lightning settlement.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
