Skip to main content
182
Integrate Bleepay into your wallet for Web2 payments and code-based dApp connections.
If you build a wallet (mobile, desktop, or web), you can integrate Bleepay to give your users Web2 payment capabilities and code-based dApp connections without relying on browser extensions.

​
What you implement

  • Voucher generation — When the user wants to pay or connect, your wallet requests a short-lived voucher (6-digit code) from Bleepay and displays it to the user.
  • Secure channel — Communication with Bleepay’s backend must be authenticated (e.g. signed by the user’s key or session token) so only the rightful payer can generate and redeem vouchers.
  • Transaction retrieval and signing — When a payee (merchant or dApp) redeems the code, Bleepay notifies your wallet with a pending transaction. Your wallet fetches the transaction object, shows it to the user, and signs/broadcasts it.

​
User flow

  1. User chooses “Pay with Bleepay” or “Connect with code” in your wallet.
  2. Wallet requests a voucher from Bleepay (signed request).
  3. User sees the 6-digit code and enters it at the merchant/dApp (or the other side submits it).
  4. When the code is redeemed, the wallet receives a pending transaction; user reviews and approves.
  5. Wallet signs and broadcasts; settlement proceeds (on-chain and/or off-ramp).

​
Benefits for your users

  • Web2 payments: Pay at online stores with a code; no need to connect the store to the wallet.
  • Custody: Each transaction is authorized individually; no standing permissions or deposits.
  • dApp connections: Connect to dApps with a code instead of extension/QR, reducing friction and conflicts.

​
Technical notes

  • Voucher lifecycle (generation, TTL, redemption, single-use) is defined by the Bleepay protocol; your wallet must comply with the API and signing requirements.
  • Transaction objects are chain-native (e.g. EIP-1193, Solana Web3 format) so your existing signing and broadcast logic can be reused.
  • See Protocol flow and Terminology for details.

​
Next steps