Documentation
What Sign in with SizWallet is
SizWallet is an OpenID Provider. Your site is a relying party. The person signs in (DID or passkey) on our origin. We send you an authorization code. You exchange it on your server. That is the only supported flow — no implicit tokens, no seed phrases on your page, no Chrome-extension bridge from your domain.
You receive
- An
id_tokensigned RS256 - An access token for UserInfo
subthat starts withpw:- Standard claims: iss, aud, exp, iat, nonce, auth_time
Tokens never include
- DID, username, email, phone, or legal name
- Wallet addresses or KYC fields
- The wallet
ownership_token - A query-string display name you invent — the consent screen uses our registry
Client types
Confidential — server app. Keep client_secret on the server. Use client_secret_post or HTTP Basic.
Public — SPA or native. No secret. PKCE S256 is still required for every client.
Scope today
Only openid. Asking for profile, email, or wallets is rejected. If you later need a public address, the user must consent through a separate wallet API call — never from the ID token.
Live endpoints
| Use | Method | URL | Notes |
|---|---|---|---|
| Discovery | GET | https://wallet.siz.land/.well-known/openid-configuration | OIDC metadata. Also at /api/wallet/oauth/openid-configuration. |
| Authorize | GET | https://wallet.siz.land/oauth/authorize | User-facing consent on wallet.siz.land. Authorization-code + PKCE only. |
| Token | POST | https://wallet.siz.land/api/wallet/oauth/token | Exchange the one-time code. PKCE verifier required. |
| UserInfo | GET | https://wallet.siz.land/api/wallet/oauth/userinfo | Bearer access token. Returns pairwise sub only. |
| JWKS | GET | https://wallet.siz.land/api/wallet/oauth/jwks | RSA public keys to verify id_token (RS256). |