Accept code-based wallet connections and transaction authorizations in your dApp.dApps can use Bleepay to accept code-based wallet connections and transaction authorizations. Users connect with a six-digit code instead of browser extensions or QR scans—no popups, no session management, no conflicts with other wallets.
Use cases
- Onboarding: User opens your dApp, selects “Connect with code,” and enters the code from their wallet. No extension required.
- Transactions: For sensitive or high-value actions, require a fresh code + in-wallet confirmation (e.g. swap, transfer, governance).
- Mobile: Same flow on mobile; no extension workarounds.
How it works
- User generates a code in their Bleepay-compatible wallet (session or one-time, depending on your flow).
- Your dApp provides an input for the code and sends it to Bleepay (via your backend or Bleepay’s API) to associate the session with the user’s wallet.
- Bleepay links the code to the payer’s identity and, when you request a transaction (e.g. “approve spending” or “execute swap”), returns an unsigned transaction to the wallet.
- User sees the transaction in their wallet, approves it, and the wallet signs and broadcasts.
- Your dApp can track the transaction via Bleepay or on-chain.
Benefits
- Simpler onboarding: No extension install or connect popup.
- Fewer failures: No popup/extension conflicts; fewer drop-offs at connection.
- Mobile-friendly: Works on mobile without special handling.
- Per-action authorization: Optional extra step (code + confirm) for sensitive operations.
Implementation
Integrate with Bleepay’s API (or SDK) to:- Start a “connection” or “session” and receive a code (or accept a code from the user and resolve it to a session).
- Request transaction objects for the actions you need (e.g. token approval, swap, transfer).
Next steps
- Wallet providers — how wallets implement Bleepay.
- Web3 processing — complex actions (swaps, DeFi) via Bleepay.