BlockBee Logo

Search BlockBee

Search BlockBee blog posts and documentation.

How to Add Crypto Payments to Your Website: A Step-by-Step Guide
Share
June 19, 2024 • 5 min read

How to Add Crypto Payments to Your Website: A Practical Setup Guide

Guides

A practical guide to accepting crypto on your website: pick Payment Links, a plugin, hosted Checkout or a custom flow, handle webhooks safely and test with a small real payment.

How to add crypto payments to your website: the short answer

Create a BlockBee account, add a receiving address for each coin you want, then pick the path that fits your site: Payment Links for invoices and one-off sales, an official plugin for a supported store platform, hosted Checkout through the API, or a custom payment flow with your own screens. Fulfil an order only once BlockBee reports the payment as confirmed, through a verified webhook, your plugin or the dashboard, never on the customer's redirect. Then test with a small real payment before launch.

Choose your path

Path Good fit Code needed What you handle
Payment Links Invoices, one-off sales, a link on your site None, and no API key Creating and sharing links; tracking payments in the dashboard
E-commerce plugin Stores on WooCommerce, PrestaShop, OpenCart, Magento, Odoo or WHMCS None Installing it, your API key, coins and addresses
Hosted Checkout Custom sites happy to use BlockBee's payment page Server-side Creating payments and processing the webhook
Custom payment flow Sites that need their own payment screen Most Addresses, payment screen, minimums and webhooks

BlockBee's docs estimate about 5 minutes for a basic payment link, 5–10 for Checkout and 30–45 for a custom flow. For Bitcoin specifics, see our Bitcoin payment gateway guide; for the payment screen itself, see our crypto checkout guide.

Set up the account side

  1. Register and add addresses. Create a BlockBee account and set the receiving address for each coin on the Addresses page. Payment Links and Checkout also need a default fiat currency in Payment Settings.
  2. Generate an API key if you use a plugin, Checkout or a custom flow; Payment Links don't need one. Keep the key on your server, never in client-side code.
  3. Verify your domains. Once domain verification applies to your account, BlockBee accepts callback, notification and redirect URLs, including a payment link's redirect, only on domains verified for the profile. That applies from the start to accounts created on or after 20 October 2026, and to existing accounts from 1 February 2027. Add each domain under Profile settings → Domains and publish the TXT record shown, or use the HTTPS file option in the domain verification guide. With a plugin, verify your shop's domain, because the plugin sends its callbacks there.

Plugin or API: who does what

With a plugin, the plugin does the payment work and you don't build payment logic. In WooCommerce, for example, you install the BlockBee plugin, open WooCommerce settings → Payments, paste your API key, select the coins you accept, enter your addresses and save; the plugin then updates order status automatically. Plugins are configured in your store admin, so follow BlockBee's plugin guides.

With the API (Checkout or a custom flow), your server owns the order logic:

  • Map orders server-side. Create each payment from your server with your order ID in the notify_url (Checkout) or callback (custom flow), and store BlockBee's payment_id or, for a custom flow, the payment address plus the coin and crypto amount you requested against the order.
  • Add a secret. Include an unguessable per-payment value in the notification URL, store it, and reject notifications that don't match.
  • Verify signatures. BlockBee signs every webhook; check the x-ca-signature header against its public key, as the signature guide shows.
  • Acknowledge quickly. Respond with HTTP 200 and the body *ok* within 30 seconds, and queue slower work. Any other response counts as a failure, and BlockBee retries at growing intervals until the transaction is 3 days old, as the webhooks guide explains.
  • Fulfil once, on confirmation. In a custom flow, a pending webhook (pending=1) may update the customer's progress but must not fulfil the order. Process the verified confirmed webhook (pending=0) even if you already recorded a pending one with the same uuid: check that its coin and value_coin match the coin and crypto amount you stored, then fulfil once and treat any repeat of that confirmation as handled. Checkout sends one webhook per completed payment; deduplicate it by payment_id.
  • Don't treat the redirect as proof. BlockBee's Checkout docs recommend validating payments with the notify_url rather than the redirect page.

We also recommend logging each notification, its verification result and the order it matched.

Test before you go live

BlockBee has no sandbox or test mode, so test with real funds:

  1. A small real payment. Place a real order above the coin's minimum; the docs use about $2 in Litecoin as an example. Check that the order is marked paid once, the amounts are stored and the funds reach your wallet. Never go below the minimum: those payments are ignored and the funds lost.
  2. A duplicate notification. Confirm a repeated webhook can't fulfil the order twice. One way, on your own test order only: process the confirmation webhook but return an error, then check that your handler recognises BlockBee's retry (the first comes 6 minutes later), doesn't fulfil again and still answers HTTP 200 with *ok*.
  3. An expired or abandoned payment. Give a Checkout payment an expiry (the minimum is 1 hour) or set an expiry date on a payment link, leave it unpaid, and check that your order stays unpaid and follows your own cancellation rules.

Fees in brief

  • Service fee: a percentage of each payment. On 3 November 2026 the fees page showed 1.000% for monthly volume of USD 0–9,999, with rates down to 0.25% depending on 30-day volume and industry risk tier, and no setup or monthly fees. Use the fee calculator for your rate.
  • Network fees: blockchain costs, separate from the service fee, varying by chain and, by default, deducted before the payment is forwarded to you. Forwarding your payment and BlockBee's fee both cost network fees; optional Prepaid BlockBee Fees remove one of those transactions.
  • Swap fees: with Swap Everything enabled, customers on eligible Checkout flows can pay with other supported coins. Swap fees are charged to the customer and add no extra cost for you; your usual service and network fees still apply.

FAQ

Do I need a developer?

Not for Payment Links or an official plugin. Hosted Checkout needs server-side code, and a custom payment flow needs the most development.

What if my platform has no official plugin?

Use Payment Links or hosted Checkout, or contact BlockBee support about a custom integration.

Can I test without spending real money?

No. BlockBee has no sandbox or test mode. Use a small real payment above the coin's minimum.

Do I have to verify my domain?

Yes, once verification applies to your account: from the start for accounts created on or after 20 October 2026, and from 1 February 2027 for existing accounts. You can verify domains ahead of time.

Can customers pay with a coin I don't accept?

With Swap Everything enabled on eligible Checkout flows, customers can pick a supported route with a live quote, and the payment is converted into one of your configured receiving coins. While swap checkout is active for a profile, that profile's Exchanges automation rules pause. If the switch isn't on your account, contact BlockBee to check access.

Crypto payments made simple

Start accepting cryptocurrency payments with BlockBee

Create an account, generate your API key, and accept Bitcoin, USDT, Ethereum, and 100+ cryptocurrencies through hosted checkout, APIs, plugins, or payment links.

Start now

0% fees for 7 days!

BlockBee Logo
Cryptocurrency solutions to
grow your business

Review Us

BlockBee rating on Cryptwerk
TrustPilot Logo
© BlockBee 2026. All Rights reserved.