Documentation Index
Fetch the complete documentation index at: https://docs.polygon.technology/llms.txt
Use this file to discover all available pages before exploring further.
Interactive Demo
Walk through the key flows of a neobank built on a Polygon embedded wallet.
Supported standards
The embedded wallet stack is fully compliant with the following EIPs:| Standard | Description |
|---|---|
| EIP-712 | Typed structured data signing. Wallets present human-readable data for user approval rather than raw hex. |
| EIP-1271 | Smart contract signature validation. Contracts can verify signatures via isValidSignature, enabling contract wallets to sign onchain messages. |
| EIP-2098 | Compact signature representation. Reduces signature size from 65 to 64 bytes for more efficient onchain verification. |
| EIP-6492 | Signature validation for pre-deploy (counterfactual) contracts. Allows wallets that have not yet been deployed onchain to produce verifiable signatures. |
Use cases
| Use case | Fit |
|---|---|
| Neobank or fintech adding stablecoin wallets | Ideal |
| Payments app with recurring or batch transfers | Ideal |
| Consumer product onboarding non-crypto users | Ideal |
| Multi-step checkout with no approval prompt per step | Ideal |
| Enterprise custody with compliance requirements | Use Custodial Wallets |
| AI agent executing autonomous transactions | Use Agentic Wallets |
Get started
Quickstart
Integrate an embedded wallet into your app in minutes.
Authentication
Configure social login, email OTP, and passkey auth flows.
Smart sessions
Scope transaction permissions so users approve once and your app handles the rest.
Wallet operations
Send transactions, sign messages, and check balances.
Recovery
Passkeys and timed recovery for user wallet access.
Security architecture
How keys are protected and transactions are validated.