​
Errors

The API uses standard HTTP status codes with structured JSON error responses where applicable.
StatusMeaningRecommended action
400The request is not acceptable for the current state.Check the message and request context before retrying.
401Missing, invalid, or expired authentication.Refresh credentials or sign in again.
402Insufficient credit for a billable operation.Fund the wallet and retry with the same idempotency key only for the same operation.
403The authenticated business is not allowed to perform the operation.Confirm approval status, account state, and required headers.
404The requested resource was not found.Verify identifiers and ownership.
409The request conflicts with an existing resource or state.Resolve the duplicate or state conflict before retrying.
422Validation failed.Correct field formats, required fields, or conditional fields.
429Rate limit exceeded.Back off and retry later.
503A dependency or service is temporarily unavailable.Retry with backoff and preserve the same idempotency key for identical requests.

​
Retrying requests

Use exponential backoff for transient failures such as 429 and 503. For account creation and lookup requests, retry the same operation with the same Idempotency-Key. For a new operation, generate a new idempotency key.

​
Correlation IDs

Where available, keep correlation IDs from responses or logs. They make support investigations faster and help connect client-side events to server-side processing.