Menu
DocsKO

Digital asset wallets for your app

Connect an app-specific wallet with a sign-in button. Pouchi handles user-approved payments and lost-device recovery.

QuickstartTry the demo

Available on Maroo Testnet with app registration. Final signup and payment checks are in progress.

Payment requestReview the amount and recipient.

Payment flow illustration · Maroo Testnet

User approvalApprove with a PIN or passkey. The app covers gas.

Key shares and wallet recovery

In the documented 2-of-3 design, an owner signature requires two key shares. The Pouchi server share cannot sign on its own.

Owner signature

Two of the three key shares sign together.

  • Your deviceStored
  • Pouchi serverStored
  • Recovery shareStored
Owner signature

Cannot sign

The server share alone cannot produce an owner signature.
Example wallet0x96d0…65e3Same address

An illustration of the documented 2-of-3 design, not verification of every demo’s key configuration.

  • Keys kept outside app code

    Key shares stay in the Pouchi vault, served from a separate origin. Your app code cannot access key material.

  • Separate wallets for each app

    Each app gets a separate wallet by default. Users sign in with one Pouchi account, while wallet addresses and balances stay app-specific.

  • The same address after recovery

    Recover on a new device with a previously configured passkey or recovery code. New signing keys are created; the wallet address and assets remain unchanged.

  • Set up recovery in advance

    Set up and keep a passkey or recovery code. If both your device and recovery method are lost, email sign-in alone cannot restore the wallet.

Pouchi has not yet undergone an external security audit. The security design and current scope are documented publicly. Security docs

Spending limits for agents

Users approve an amount, count, period and destination once. The wallet checks those limits on chain for each agent payment. Users can revoke permission.

Limit approval docs
Maroo blockchain Inside the limit Coffee shop Electronicsstore Spending limit9,900 OKRW eachUp to 3 · Coffee shop Approve once No permission 9,900 OKRW9,900 OKRW paid 9,900 OKRWRefused: store not allowed 15,000 OKRWRefused: over 9,900 OKRW Maroo blockchain Inside the limit Coffee shop Electronicsstore Spending limit9,900 OKRW eachUp to 3 · Coffee shop Approve once No permission 9,900 OKRW9,900 OKRW paid 9,900 OKRWRefused: store not allowed 15,000 OKRWRefused: over 9,900 OKRW
The limits of 9,900 OKRW per payment and up to 3 payments come from a local approval demo. Shops and payment attempts are illustrative.

Pouchi demos

Demos built with the Pouchi SDK. Explore sign-in and payment flows using OKRW, a test asset on Maroo Testnet.

Hermes agent connection

The connection flow was tested locally without real payments. The setup is documented.

Agent connection docs

Developers

Quickstart

Add one script to your website to create a Pouchi login button. Users authenticate in a separate Pouchi window, then return to your app with their wallet connected.

Web script illustration · proposed button design

index.htmlApp ID and domain registered
<main>  <h1>App-specific wallet</h1></main><script defer src="https://pouchi-wallet.vercel.app/sdk/v1/pouchi.js" data-app-id="tenant_your_app"></script><footer></footer>
Replace the example with your issued app ID. The script adds a login button; payment requests require separate integration.

Integration setup

Register your app ID and allowed domains, then add the official script. No React setup is required. Connect payment requests separately through the browser API.

Web script
Load the official URL without npm
App settings
App ID and allowed domains
Current environment
Maroo Testnet

Email us about app registration and pricing. Pricing

business@pouchi.app

Integrations currently run on Maroo Testnet. Public documentation covers supported features and configuration.

  • Web script and payment API

    Add the button, read login state and connect payment requests.

    Browser SDK docs

  • React SDK

    Use the provider and hooks in an existing React application.

    React SDK reference

  • Wallet MCP

    Agents request payments through MCP clients such as Claude. The wallet executes them only within approved limits.

    Agent docs

  • Migrate from Privy

    Compare supported APIs and provider settings to assess the changes your app needs.

    Migration guide

See the app wallet integration guides and payment API.

Read the docs

Currently running on Maroo testnet.