PayPM Platform API
Wallet, onboarding, money movement, developer, and operator APIs.
PayPM exposes two API planes.
Plane A is the end-user mobile API. It uses phone + OTP + PIN login and
JWT bearer tokens. Plane A requests include X-Deployment-Scope: end-user.
Plane B is the operator/developer API. It uses institution API keys and HMAC-signed requests for internal automation, API keys, audit, webhooks, contract vault operations, and portal bootstrap work.
Sandbox simulates money movement. Staging is configured for live money-flow checks and should be handled as sensitive.
Merchant is an optional acquirer slice on the same wallet host. Human Merchant routes require a ZITADEL OIDC bearer token, not a Plane A wallet JWT. The public pay-instrument resolver is unauthenticated. Merchant routes do not authorize a wallet debit.
Standalone Marketplace Contract Vault reads live on the Marketplace product API, not on this wallet host. They require a Marketplace SPA OIDC bearer token, not a Plane A wallet JWT and not a Plane B API key. Missing Identity wallet link or store fails closed to unavailable + empty. Create, sign, pay, and evidence writes remain on wallet-backend.