Send a verification code
POST/otp/challenges
Machine token. Called by your backend, using your client_credentials token.
We resolve the destination from the customer's registered contact channel and deliver the code there — you never see it, and you cannot redirect it. That is what makes a returned code evidence about the person rather than about the caller. Render your code-entry screen from the returned masked destination.
Request
Responses
- 201
- 400
- 401
- 403
- 404
- 409
- 422
- 500
Created
Malformed request — validation failure, or a header such as Idempotency-Key is missing or not a UUID.
Missing, expired, or untrusted bearer token.
Authenticated but not permitted — the caller's role or scope does not grant this operation, or the resource belongs to another tenant.
The referenced wallet, transaction, user, or tenant does not exist within the caller's tenant.
Idempotency conflict — a request with this Idempotency-Key is still in flight. Retry once it settles. A key belonging to an already-completed request is NOT an error: the original response is replayed with its original status.
The request is well-formed but violates a business rule — for example a posting that would breach a wallet fund's balance floor, a transaction type not enabled for the tenant, a per-transaction or daily issuance cap, or an operation on a frozen wallet.
Unexpected server error.