Reliability & Stability

Error Codes

The STSPoint API uses standard HTTP response codes to indicate the success or failure of an API request. In general, codes in the 2xx range indicate success, codes in the 4xx range indicate an error from the client-side, and codes in the 5xx range indicate an error with our servers.

Common Status Codes

Below is a summary of the most common error codes you might encounter while integrating with our infrastructure.

Status	Title	Message / Reason	Description
400	Bad Request	"Missing required fields"	The request body is malformed or missing parameters.
401	Unauthorized	"Authentication failed"	Invalid `secret_key` or `merchant_id`.
403	Forbidden	"Service not initialized"	The service or subscription is not active for your account.
404	Not Found	"Transaction not found"	The requested resource (transaction/product) does not exist.
429	Too Many Requests	"Rate limit exceeded"	You have exceeded your allocated RPM (Requests Per Minute).
500	Server Error	"Internal Server Error"	Something went wrong on STSPoint's end.

Error Payload Structure

When an error occurs, the API returns a JSON object containing a success: false flag and a descriptive message.

Error Response Example

{
  "success": false,
  "message": "Authentication failed: Invalid secret_key provided.",
  "error_code": "AUTH_INVALID_KEY",
  "request_id": "req_8329482938"
}

Error Handling Tips

Wait for Retries: For 429 errors, implement an exponential backoff strategy.
Log Request IDs: Always include the request_id when contacting support for faster resolution.
Sanitize Logs: Ensure your application logs do not store raw secret_key values when errors occur.

STSPoint Global API • Error Reference v1.2

Reliability & Stability

Error Codes

Common Status Codes

Below is a summary of the most common error codes you might encounter while integrating with our infrastructure.

Status	Title	Message / Reason	Description
400	Bad Request	"Missing required fields"	The request body is malformed or missing parameters.
401	Unauthorized	"Authentication failed"	Invalid `secret_key` or `merchant_id`.
403	Forbidden	"Service not initialized"	The service or subscription is not active for your account.
404	Not Found	"Transaction not found"	The requested resource (transaction/product) does not exist.
429	Too Many Requests	"Rate limit exceeded"	You have exceeded your allocated RPM (Requests Per Minute).
500	Server Error	"Internal Server Error"	Something went wrong on STSPoint's end.

Error Payload Structure

When an error occurs, the API returns a JSON object containing a success: false flag and a descriptive message.

Error Response Example

{
  "success": false,
  "message": "Authentication failed: Invalid secret_key provided.",
  "error_code": "AUTH_INVALID_KEY",
  "request_id": "req_8329482938"
}

Error Handling Tips

Wait for Retries: For 429 errors, implement an exponential backoff strategy.
Log Request IDs: Always include the request_id when contacting support for faster resolution.
Sanitize Logs: Ensure your application logs do not store raw secret_key values when errors occur.

STSPoint Global API • Error Reference v1.2

Core

Payments

Services

Integration

Error Codes

Common Status Codes

Error Payload Structure

Core

Payments

Services

Integration

Error Codes

Common Status Codes

Error Payload Structure