​

API Reference

Use the backend origin configured for the application by NEXT_PUBLIC_API_URL. Paths below are relative to that origin; do not assume that a separate service’s hostname or API belongs to WizPay Core. Availability is determined by GET /capabilities and operation-specific readiness. Account-scoped endpoints require the wallet session issued by the authentication flow. Execution-intent endpoints also validate the intent’s access key and, where required, its active lease.

​

Health and Capabilities

Feature names include send, sameTokenPayroll, invoice, paymentLink, bridge, swap, and crossTokenPayroll. Only enabled, ready routes may be used.

​

Wallet Authentication

Use Authorization: Bearer <session-token> where wallet-session authentication is required. Never send a private key to these endpoints.

​

Execution Intents

These operations preserve the same intent identity. /verify supports direct Send; it is not a generic verifier for every payment type.

​

Payroll

Initialization is preparation, not backend payment submission. Use the payload returned by the current planning flow rather than inventing token addresses or approval amounts.

​

Invoices and Payment Links

Payment links use the invoice model’s settlement kind. Merchant operations require a wallet session; public checkout routes use their own validation and rate limits.

​

Activity

​

Conditional Swap and Bridge Routes

Only use these routes when the corresponding runtime capability and readiness checks pass. Bridge continuation uses the intent’s approval, source, attestation, and destination lifecycle endpoints. A successful source transaction does not complete the destination transfer. Legacy generic task submission, worker-signed payroll/swap, standalone FX, liquidity execution, hosted-wallet onboarding, and paid preparation APIs from other repositories are not documented as production application integrations.