Projects stay separated
Give every integration its own contracts, credentials, users, webhook destination, and operational history.
BitPay brings projects, payment activity, on-chain verification, and signed settlement events into one deliberate operating layer.
Keep project access, on-chain activity, operational review, and merchant notifications in one consistent workflow.
Give every integration its own contracts, credentials, users, webhook destination, and operational history.
Validate payment receipts against configured project contracts before activity enters your operational record.
Signed payment events, delivery history, and retry controls make downstream reconciliation easier to operate.
Use a purpose-built console to review transactions, user attribution, balances, delivery attempts, and activity history.
BitPay gives technical and operations teams a shared, traceable workflow without putting secret credentials in the browser.
Read the integration docsDefine its contract, access, payment rules, and merchant webhook destination.
Use a project-scoped API key from your backend and keep it out of client code.
Submit or observe the transaction, then consume the signed confirmation event.
# Authenticate a project
curl \
-H "Authorization: Bearer $BITPAY_API_KEY" \
https://api.bitpay.live/api/client/v1/me
# Signed webhook event
X-BitPay-Signature: t=...,v1=...
X-BitPay-Event: deposit.confirmed
The BitPay API now runs independently from the BitVault exchange API. Its stable, versioned client surface is designed for server-side integrations.
Configure projects, monitor activity, and manage integrations from the BitPay operations console.