
🔥 Get your first Bleepay payment flow running in minutes.
This guide walks through the payee (merchant/dApp) side of a Bleepay voucher payment. The payer uses a Bleepay-compatible wallet — you don’t implement that side.
Prerequisites
- A Bleepay account with API credentials
- A Bleepay-compatible wallet (e.g. Bleepay Wallet) for the payer
- cURL or any HTTP client
Flow overview
Your responsibility is the payee side (right column). The payer side happens in their wallet.Payer opens a context in their wallet
The payer uses a Bleepay-compatible wallet to authenticate and open a payment context. The wallet returns a context code — a short alphanumeric string the payer shares with you.This step happens entirely inside the payer’s wallet. You just need to provide a way for the payer to give you the context code (QR scan, text input, deeplink, etc.).
Authenticate as the payee
Use the context code to authenticate. This links your session to the payer’s context.Response:
{ "authorization": { "token": "<payee_token>" } }Reserve a voucher
Reserve a voucher within the payer’s context. This generates a 6-digit voucher code.Response:
Redeem the voucher
Specify what you expect to receive — currency, amount, network, and destination address. The Response:
expectedPayment parameter tells Bleepay to create a SIMPLE voucher with automatic network selection.Payer signs and resolves
The payer reviews the transaction in their wallet, signs it, and the wallet submits the receipt. This happens on the payer’s side — no action needed from you.Poll the voucher to track its status until it reaches The voucher moves through states:
RESOLVED:RESERVED → REDEEMED → RESOLVED. Poll every 2–5 seconds until the final state is reached. For production, register a webhook endpoint instead of polling.Complete payee-side example
Next steps
- Integration overview — full parameter reference and Web2 vs Web3 modes.
- Simple Payments — SIMPLE vouchers, FX, and negotiation.
- Webhooks — event-driven settlement tracking.
