How to Judge Crypto Payment Gateway Reliability and Uptime

What makes a crypto payment gateway reliable?

A reliable crypto payment gateway is one whose reliability you can check for yourself. Look for five things: uptime published for each blockchain, not just one overall figure; a status page that keeps a history; webhooks that retry when your server misses them; settlement that sends payments to your own wallet rather than a balance you must withdraw; and a small live payment you run yourself before launch. Below is how to check each one, using BlockBee as the example.

Why does uptime differ by blockchain?

A gateway has to watch every blockchain it supports, and each chain can have its own problems. BlockBee's status page, status.blockbee.io, tracks eight monitors: the Service API and seven network APIs. Checked on 26 October 2026, all eight were up, with these figures for the last 90 days:

Overall uptime was 100.000% for the last 24 hours and the last 7 days, 99.995% for the last 30 days and 99.991% for the last 90 days. The page showed no status updates in the last 30 days and links to a status update history. These figures update continuously; check the page on the day you decide.

The spread matters more than the average. Over 90 days, 99.999% is about 1 minute of downtime; the EVMs monitor's 99.963% is about 48 minutes. If most of your customers pay on one network, read that network's line.

Uptime is not speed. BlockBee's troubleshooting docs say a transaction that stays unconfirmed, for example because of network congestion, can take 1 to 24 hours to confirm, depending on the network.

What happens to a payment if the gateway or your server is down?

A customer's payment is recorded on the blockchain, so an outage does not undo it. What it delays depends on whose outage it is. If your server is down, you miss the notice that the payment arrived. If the gateway is down, it may also be late detecting the payment and sending it on. Ask the provider how it detects and forwards payments during its own outage.

At BlockBee, that notice is a webhook: a POST request to the URL you registered. Your endpoint must reply with status 200 and the body *ok* within 30 seconds; any other response counts as a failure. BlockBee then retries after 6 minutes, then 12, then 24, doubling each time. Retries stop when the transaction is 3 days old, counted from the payment, not from when your endpoint went down. By the schedule, the last retry comes about 51 hours after the payment, so plan to fix an outage well within two days.

Retries mean duplicates, so make your handler idempotent: store each webhook's uuid and skip any you have already processed.

If you miss every retry, BlockBee's docs describe a logs endpoint you can poll "as a backup method" to check payment status. The webhooks guide lists the retry rules and troubleshooting steps, and our guide to crypto payment webhooks covers the handler pattern.

Why does the settlement model matter for reliability?

If a gateway holds your money as a balance, getting paid depends on it processing your withdrawal. Our guide to custodial vs non-custodial gateways notes that access to custodial funds "can depend on provider approvals, limits, maintenance windows, or account reviews".

BlockBee forwards instead. Each on-chain payment goes to your address once it confirms. Bitcoin Lightning payments, available through Checkout and the Point of Sale (PoS) only, settle once a day at 00:00 UTC. Forwarding removes the withdrawal step, but BlockBee still has to detect each payment and send it on, so the checks above still apply. BlockBee's Terms also say it may suspend or delay the processing or forwarding of a transaction where it finds potential concerns.

How do you test reliability before you commit?

BlockBee has no sandbox or test mode. Its docs suggest a small real payment above the coin's minimum: about $1 in Litecoin in the quickstart, or about $2 in the e-commerce guide. On 26 October 2026, BlockBee's API listed Litecoin's minimum as 0.002 LTC, about $0.11 at the API's price that day; payments below the minimum are ignored and the funds are lost. At BlockBee's published 1% starting rate, the fee on a $2 test is $0.02, plus the network fee.

Test failure as well as success:

• Check that the pending and confirmed webhooks arrive and the funds reach your wallet.
• Take your endpoint offline, send a second payment, bring the endpoint back, and watch the retry arrive.
• Send your handler the same webhook twice and check the order is paid once.

What should you ask a provider about uptime?

Ask every provider the same questions, and get the answers in writing:

• Is there a public status page with history? BlockBee's shows 90-day uptime for each monitor and links to a status update history.
• Is each network monitored separately? One overall figure can hide a weak chain.
• What is the webhook retry policy? Ask for the intervals and when retries stop.
• Can you check payments without webhooks? For example, by polling a logs endpoint.
• How is maintenance announced? BlockBee's contacts page says its official social media channels post maintenance notices, and its Terms say it may need to suspend the Service temporarily for repairs, planned maintenance or upgrades.
• Is there an SLA? Ask whether one is offered, what it covers (the API, each network, webhooks), how downtime is measured and what you get if it is missed.
• What do developers report? Read recent reviews on independent sites for missed webhooks or outages, and see how the company replies.

Frequently asked questions

What uptime should a crypto payment gateway have?

No single figure suits every business. Compare the networks you need over the same window. Over 90 days, 99.99% uptime is about 13 minutes of downtime, and 99.9% is about 2 hours 10 minutes.

Where can I see BlockBee's uptime?

On status.blockbee.io. On 26 October 2026 its 90-day figures ranged from 99.963% (EVMs) to 100.000% (Service API).

Does a crypto payment API need an uptime SLA?

If downtime would cost you sales, ask each provider whether it offers an SLA and what it covers, and get the answer in writing. A status page shows past uptime; an SLA, where one is offered, sets out what the provider commits to.

What happens if my webhook endpoint is down?

BlockBee retries after 6, 12 and 24 minutes, doubling each time, until the transaction is 3 days old; by the schedule, the last retry comes about 51 hours after the payment. After that, check the payment through the logs endpoint.

Is a non-custodial gateway more reliable?

It removes one dependency: you don't wait for the provider to process a withdrawal. You still depend on it to detect payments and send webhooks, so check its uptime and retry policy too.

To run these checks yourself, create a BlockBee account and start with a small Litecoin payment.