Bitcoin Betting Casino Setup
Bitcoin in iGaming is not just another payment method. There are specifics here: high-frequency transactions of small amounts, requirement for instant crediting for bets, BTC volatility against casino fiat balance, and strict provably fair requirements. Standard on-chain transactions with 10-minute confirmation wait for bets don't work — Lightning Network or custodial model with internal balances is needed.
Architectural approaches: three models
Model 1: Custodial wallet with internal balances
Most common in the industry. Bitcoin is accepted on-chain, converted to internal credits, bets go through internal system:
BTC on-chain deposit → Internal credit balance → Bets (no blockchain) → Withdraw to BTC
Pros: instant bets, no per-bet fees, simple rollback on error. Cons: casino holds user keys, custody risk, requires trust.
Model 2: Lightning Network for bets
Bets via LN channels — instant and without custody of large sums. Architecture described below.
Model 3: Hybrid (recommended)
Deposit/withdrawal — on-chain BTC (for large amounts) + Lightning (for small). Game balance — custodial. Balance between UX, security, and operational complexity.
On-chain integration: BTCPay Server
For production — don't reinvent the wheel with Bitcoin node directly. BTCPay Server — open-source, self-hosted, proven solution:
# Docker deployment BTCPay Server
git clone https://github.com/btcpayserver/btcpayserver-docker
cd btcpayserver-docker
export BTCPAY_HOST="pay.yourcasino.com"
export NBITCOIN_NETWORK="mainnet"
export BTCPAYGEN_CRYPTO1="btc"
export BTCPAYGEN_LIGHTNING="lnd" # Lightning built-in
. btcpay-setup.sh -i
API for creating deposit invoice:
import httpx
BTCPAY_URL = "https://pay.yourcasino.com"
BTCPAY_API_KEY = "your_api_key"
STORE_ID = "your_store_id"
async def create_deposit_invoice(user_id: str, amount_usd: float) -> dict:
async with httpx.AsyncClient() as client:
response = await client.post(
f"{BTCPAY_URL}/api/v1/stores/{STORE_ID}/invoices",
headers={"Authorization": f"token {BTCPAY_API_KEY}"},
json={
"amount": amount_usd,
"currency": "USD",
"metadata": {"userId": user_id},
"checkout": {
"expirationMinutes": 60,
"redirectURL": f"https://casino.com/deposit/success?user={user_id}"
}
}
)
invoice = response.json()
return {
"invoice_id": invoice["id"],
"payment_url": invoice["checkoutLink"],
"btc_address": invoice["addresses"]["BTC"],
"btc_amount": invoice["cryptoInfo"][0]["due"]
}
Webhook from BTCPay
@app.post("/btcpay/webhook")
async def btcpay_webhook(request: Request):
body = await request.body()
signature = request.headers.get("BTCPay-Sig")
# Verify HMAC-SHA256
expected = "sha256=" + hmac.new(
WEBHOOK_SECRET.encode(), body, hashlib.sha256
).hexdigest()
if not hmac.compare_digest(expected, signature):
raise HTTPException(status_code=401)
event = json.loads(body)
if event["type"] == "InvoiceSettled":
invoice_id = event["invoiceId"]
invoice = await get_invoice_details(invoice_id)
user_id = invoice["metadata"]["userId"]
usd_amount = float(invoice["amount"])
await credit_user_balance(user_id, usd_amount)
await notify_user_deposit_confirmed(user_id, usd_amount)
Dealing with volatility
BTC/USD can move 5–10% in hours. For casino with fiat accounting need a strategy:
Option 1: Immediate conversion — received BTC is converted to USDT/USDC via exchange API (Binance, Kraken) at confirmation moment. Player balance in USD, exchange risk minimal.
async def convert_btc_to_usd(btc_amount: float) -> float:
binance = ccxt.binance({'apiKey': KEY, 'secret': SECRET})
order = await binance.create_order(
symbol='BTC/USDT',
type='market',
side='sell',
amount=btc_amount
)
return float(order['cost']) # USD received
Option 2: Holding BTC — casino accepts volatility risk. Justified only if owner intentionally accumulates BTC.
Option 3: BTC-denominated balance — bets in satoshis, withdrawals in satoshis. Player bears exchange risk. Popular in Bitcoin-oriented casinos.
Lightning Network for instant payments
For small-amount bets (0.0001–0.01 BTC) — Lightning allows instant bets without on-chain fees:
# LND gRPC client for creating invoice
import grpc, codecs
from lnd_grpc_pb2 import Invoice
stub = create_lnd_stub(LND_HOST, MACAROON, TLS_CERT)
def create_lightning_invoice(amount_sats: int, memo: str) -> dict:
invoice = Invoice(
value=amount_sats,
memo=memo,
expiry=3600 # 1 hour
)
response = stub.AddInvoice(invoice)
return {
"payment_hash": codecs.encode(response.r_hash, 'hex').decode(),
"payment_request": response.payment_request # BOLT11 invoice
}
def check_invoice_paid(payment_hash: str) -> bool:
lookup = stub.LookupInvoice(PaymentHash(r_hash=codecs.decode(payment_hash, 'hex')))
return lookup.state == Invoice.SETTLED
Managing Lightning channel liquidity — separate operational task: channels need to be kept open, inbound liquidity provided via loop-out or LSP.
Provably Fair
Honest casinos publish result verification algorithm. Standard scheme:
import hashlib, hmac
def generate_game_result(server_seed: str, client_seed: str, nonce: int) -> float:
"""Returns number [0, 1) to determine outcome"""
message = f"{client_seed}-{nonce}"
h = hmac.new(server_seed.encode(), message.encode(), hashlib.sha256).hexdigest()
# First 8 hex chars → float
return int(h[:8], 16) / 0xFFFFFFFF
# Player can verify: server publishes server_seed_hash before game,
# after game reveals server_seed — player checks hash match
Limits and AML
Main regulatory requirements for crypto casinos:
- Identification threshold: usually 2000 EUR/day requires KYC
- Keep transaction history minimum 5 years
- Screen addresses against sanctions (OFAC list) before crediting
- Suspicious activity (structuring, fast deposit/withdrawal) — SAR report
Complete BTC integration setup with BTCPay Server, webhook handler, USD conversion, and Lightning support: 2–4 weeks including testnet testing.