Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.chipipay.com/llms.txt

Use this file to discover all available pages before exploring further.

​
What you get

  • Zero gas for end-users — Chipi’s paymaster covers transaction fees, paid in your service wallet’s USDC balance.
  • Non-custodial — private keys are encrypted client-side with a user-chosen PIN (or passkey). Chipi never sees the unencrypted key.
  • Production-grade auth — works with Clerk, Supabase, Better Auth, Firebase, or your own JWKS endpoint.
  • Multiple wallet types — CHIPI v29 (default), v33 (with spending policies), or READY (Argent X).

​
Where this fits in the dashboard

In the Chipi Dashboard, this is the Gasless Wallets service. Once you’ve completed the 5 onboarding milestones (API keys → auth → first wallet → first transfer → webhook), you can monitor wallets and transfers from /services/gasless.

Open the Gasless service

Dashboard → Services → Gasless Wallets

​
Pick your stack

Node.js / Server-side

@chipi-stack/backend — create wallets and execute transfers from your server.
Python (chipi-stack on PyPI), React (@chipi-stack/chipi-react), and Expo (@chipi-stack/chipi-expo) guides land in follow-up PRs. The underlying API and chipi-stack@2.0.0 package are already shipped — until those guides arrive, see the language-specific reference under the SDK dropdown.

​
Operations covered

OperationEndpointSmoke test
Create walletPOST /v1/chipi-walletsstaging-smoke.test.ts
Get wallet by externalUserIdGET /v1/chipi-wallets/{externalUserId}staging-smoke.test.ts
Transfer ERC-20 (gasless)POST /transferstaging-smoke.test.ts
Read token balanceGET /v1/chipi-wallets/{address}/balancestaging-reads.test.ts
Rotate PIN / passkeyPATCH /chipi-wallets/update-encryption-detailsstaging-update-encryption.test.ts
Session keys (create / register / execute / revoke)variousstaging-sessions.test.ts, staging-session-execute.test.ts
Every code sample on the per-language pages is lifted from one of these tests, which run against live staging on every release.

​
Prerequisites

  1. A Chipi org and DEV instance (created at sign-up).
  2. CHIPI_PUBLIC_KEY and CHIPI_SECRET_KEY from /configure/credentials.
  3. A configured auth provider (/configure/credentials → JWKS section). Required to call any wallet endpoint.
If those are in place, head to the Node.js guide.