Wallet and DApp integration
These guides are for developers building wallet frontends, DApps and payment entry points. Establish the account, asset and payment route before choosing an SDK or merchant API. Product behavior here is not an additional API contract or a promise that every release exposes every control.
Choose an integration layer
| Goal | Documentation | Application responsibility |
|---|---|---|
| Create a hosted merchant checkout | Merchant quickstart | Persist orders and idempotency keys, verify server-side, fulfill once |
| Manage Note inventory and construct transactions | SDK wallet sessions | Unlock, authenticate decryption, persist, authorize and reconcile |
| Handle native IPP payments in a wallet | IPP payment | Validate the fixed Request, follow authenticated links, preserve the operation |
| Query public protocol data | Protocol RPC | Authenticate chain facts; candidate discovery is not a private balance |
| Display public source information | Provenance | Preserve the recognition scope without inferring identity or legal conclusions |
Legacy payment-code parsers, internal App business endpoints and demo pages are not stable third-party integration interfaces. Merchant API decimal amounts in currency units are different from SDK/Core/native IPP amounts in base units.
Integration sequence
- Pin the deployment, network, token address, decimals, protocol and SDK versions.
- Establish account boundaries; separate connection, unlock, viewing and signing capabilities.
- Sync public balances and verified private inventory independently and expose freshness.
- Freeze the asset, recipient, amount, remainder and fees at confirmation.
- Persist an operation before submission and its hash afterward; reconcile it on recovery.
- Test rejected signatures, RPC failures, repeated clicks, restarts, insufficient funds and confirmation rollback.
Read by task
- Accounts, connections and signing: site sessions and authorization boundaries.
- In-app DApp discovery and connection: EIP-6963 discovery, account approval, events and cancellation.
- Dual balances and Note selection: available, reserved, unknown and remainder states.
- Addresses and payment codes: ordinary addresses, privacy addresses and payment requests.
- Transaction states and recovery: broadcast, execution and business completion.
- Valuation, networks and fees: asset identity, missing prices and Gas display.
Example networks, assets and fees in product mockups explain interfaces only. Execution must follow the selected deployment, supported capabilities and final signing terms.