Skip to main content
A single reference for when a bitcoin payment is safe to credit, and which events tell you about it. For the flow that produces them, see Issue addresses and Lightning invoices.

​
Confirmation thresholds

Bitnob waits for the confirmations above, then sends deposit.success. Credit the user when it arrives, and treat earlier signals on a block explorer as pending. Lightning payments settle off-chain and require no block confirmations, so an invoice marked paid is final. That is what makes Lightning suited to tipping and micropayments, where waiting for blocks is not acceptable. To check a deposit later, use Get transaction by id or reference. It returns the transaction state, not a confirmation count.

​
Webhook events

Deliveries are HTTPS POSTs signed with the x-bitnob-signature header. Verify the signature on every event before acting on it, and make handlers idempotent, de-duplicating on event_id. The full verification walkthrough and source IP list are on the Addresses webhooks reference.

​
deposit.success payload fields

​
Address reuse

Generate a new address for each receipt. Bitnob still fires deposit.success for a payment to a previously used address, so reuse does not break delivery, but it lets third parties link payments together through chain analysis and makes reconciliation ambiguous when several payments share one address. See Address and privacy practices for the fuller treatment.