Skip to main content

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​

GoalDocumentationApplication responsibility
Create a hosted merchant checkoutMerchant quickstartPersist orders and idempotency keys, verify server-side, fulfill once
Manage Note inventory and construct transactionsSDK wallet sessionsUnlock, authenticate decryption, persist, authorize and reconcile
Handle native IPP payments in a walletIPP paymentValidate the fixed Request, follow authenticated links, preserve the operation
Query public protocol dataProtocol RPCAuthenticate chain facts; candidate discovery is not a private balance
Display public source informationProvenancePreserve 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​

  1. Pin the deployment, network, token address, decimals, protocol and SDK versions.
  2. Establish account boundaries; separate connection, unlock, viewing and signing capabilities.
  3. Sync public balances and verified private inventory independently and expose freshness.
  4. Freeze the asset, recipient, amount, remainder and fees at confirmation.
  5. Persist an operation before submission and its hash afterward; reconcile it on recovery.
  6. Test rejected signatures, RPC failures, repeated clicks, restarts, insufficient funds and confirmation rollback.

Read by task​

Example networks, assets and fees in product mockups explain interfaces only. Execution must follow the selected deployment, supported capabilities and final signing terms.