Skip to main content
PayNext Billing APIs use standard HTTP status codes to indicate the outcome of each request:
  • 2xx — Success
  • 4xx — Client errors (missing parameters, invalid input, authentication issues)
  • 5xx — Server errors (rare)

​
HTTP Status Codes

CodeMeaningDescription
200OKReturned when the request succeeds.
400Bad RequestReturned when the request contains invalid parameters or malformed data.
401UnauthorizedReturned when no valid API key is provided or the key is invalid.
404Not FoundReturned when the requested resource does not exist.
429Too Many RequestsReturned when the request rate limit is exceeded (reserved for future use).
500Server ErrorReturned when something goes wrong on PayNext’s side (rare).
Always check the HTTP status code and handle errors gracefully in your application.

​
Error Response Format

All error responses share a consistent structure: 
{
  "error": {
    "message": "A human-readable description of the error."
  }
}
Fields may expand in the future (for example, error codes or subfields for validation errors).
Your integration should always parse the error.message field at a minimum.