HeritagePay API

Wallet, onboarding, money movement, developer, and operator APIs.

HeritagePay 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.