> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bleepay.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations

<img width="1500" height="844" alt="109" src="https://github.com/user-attachments/assets/50ce9916-c699-493a-be1e-2b617860a8f3" />

> How Bleepay improves Web3 apps with fiat payments and code-based UX.

Bleepay adds **fiat e-commerce payments**, **seamless wallet connections without browser extensions**, and **code-based transaction approvals** to Web3 applications. One integration, simpler UX, fewer maintenance headaches.

## The problem

Web3 teams spend a large share of engineering time on:

* Wallet integration and connection maintenance
* Brittle SDKs, RPC errors, popup failures, extension conflicts
* User drop-off and endless maintenance cycles
* Every protocol or wallet update risking breakage

Result: more time fixing connections than building the product.

## How Bleepay fixes this

Bleepay replaces unstable wallet connections with a **single six-digit code flow**:

* No extensions to conflict with
* No long-lived sessions to manage
* Web2-style checkout experience in Web3

Bleepay handles protocol updates, infrastructure abstraction, transaction logic, and gas at the protocol level. You integrate once; Bleepay maintains compatibility.

## Two ways to integrate

### Wallet providers

Implement Bleepay in your wallet to give users:

* Web2 payment capabilities (pay at online stores with a code)
* Code-based dApp connections (connect with a code instead of extension/QR)
* Per-transaction authorization (users keep custody, generate a code, approve on their device)

### dApps (decentralized applications)

Accept code-based wallet connections and transaction authorizations:

* Users connect with a six-digit code instead of extensions or QR scans
* No popups, no session management, no conflicts with other wallets
* Works on mobile without workarounds

## Why integrate?

**For wallet providers:**

* Differentiate with Web2 payment capabilities (users can spend crypto at online stores).
* No custody risk; each transaction is authorized individually.
* Add an extra security layer (code + in-wallet confirmation).

**For dApp developers:**

* Simpler onboarding; no extensions required.
* Fewer popup/extension failures and fewer drop-offs at connection.
* Works on mobile without special handling.

## Next steps

* [Wallet providers](/home/integration/wallet-providers) — integrating Bleepay into a wallet.
* [dApps](/home/integration/dapps) — accepting code-based connections in your dApp.
* [Web3 processing](/home/integration/processing) — swaps, DeFi, and complex on-chain actions.