Skip to main content
The Yabetoo API uses conventional HTTP response codes to indicate the success or failure of an API request.

​
HTTP Status Codes

CodeStatusDescription
200OKRequest succeeded
201CreatedResource created successfully
400Bad RequestInvalid request parameters
401UnauthorizedInvalid or missing API key
403ForbiddenInsufficient permissions
404Not FoundResource does not exist
429Too Many RequestsRate limit exceeded
500Internal Server ErrorServer-side error

​
Payment Error Codes

When a payment fails, the API returns specific error codes to help you understand what went wrong:
CodeDescription
LOW_BALANCE_OR_PAYEE_LIMIT_REACHED_OR_NOT_ALLOWEDThe customer has insufficient funds, has reached their transaction limit, or the transaction is not allowed by the operator
TIMEOUTThe customer did not confirm the payment in time (did not enter their PIN)

​
Example Error Response

{
  "error": {
    "message": "LOW_BALANCE_OR_PAYEE_LIMIT_REACHED_OR_NOT_ALLOWED",
    "code": "LOW_BALANCE_OR_PAYEE_LIMIT_REACHED_OR_NOT_ALLOWED"
  }
}

​
Best Practices

  1. Always handle errors gracefully - Never expose raw error messages to end users
  2. Log errors for debugging - Store error details for troubleshooting
  3. Implement retry logic - For rate limits and temporary failures
  4. Validate before sending - Check parameters client-side to reduce errors
If you encounter persistent errors, contact [email protected] with the error details.