Developer documentation

How it works

End-to-end flow from provider.request() to hosted wallet UI and back to your dApp.

request() path

  1. Your dApp calls provider.request({ method, params }).
  2. Read-only methods (eth_chainId, eth_accounts) resolve from cached session state.
  3. eth_requestAccounts opens SessionConnect overlay if no valid session exists.
  4. Signing methods build a WallCard RPC intent and open /onetime-connect (iframe or popup).
  5. WallCard API creates a signing request; user approves in hosted wallet UI.
  6. Wallet UI posts noderails-card:success back to your page; SDK resolves the promise.

Hosted wallet routes

RouteWhen it opens
/session-connecteth_requestAccounts, first connect per dApp origin
/onetime-connectpersonal_sign, eth_sendTransaction, Solana sign methods, and other signing RPCs
/authOptional App login only (wallet settings flows, not required for standard dApp signing)

Custody boundary

Your site never receives PIN, CVV, or private key material. The SDK only returns addresses, signatures, and transaction results after user approval in WallCard UI.