Error Handling
Servinux V2 uses standard HTTP response codes to indicate the success or failure of an API request. Codes in the 2xx range indicate success, 4xx range indicate an error from the provided information (e.g., authentication failure or missing parameters), and 5xx range indicate an error with our servers or banking upstream.
HTTP Status Codes
| Code | Meaning | Description |
|---|---|---|
| 200 | OK | Everything worked as expected. |
| 400 | Bad Request | The request was invalid (Missing parameters or Auth failure). |
| 401 | Unauthorized | API key is missing, incorrect, or merchant ID resolution failed. |
| 402 | Request Failed | Valid parameters but the action failed (e.g. Insufficient balance). |
| 500, 503 | Server Errors | Something went wrong on our end or with the NIP network. |
V2 Error Response Body
JSON Error Payload
{
"success": false,
"message": "Unauthorized: Merchant API Key not recognized."
}V2 Troubleshooting Pillar
V2 returns an explicit message string. If you encounter a 1452 Cannot add child row error, ensure your Merchant Profile has been verified through the **KYC Master** system. Our engine automatically provisions account IDs upon successful KYC submission.