Error Response Codes

APIs return a standard code. Branch on code — do not rely on message text alone.

Standard response codes

code	Meaning	What to do
00	Success	Update local order; notify user; audit log
01	In progress	Poll with inquiry; set a timeout
10	Bad request	Fix required fields, types, request shape
11	Not found	Check endpoint, orderNo / tradeNo, API version
12	Unauthorized	Check signature, keys, payment method → Signature Rules
13	Too many requests	Reduce rate; exponential backoff
14	Forbidden	Check account / method status; contact BD
15	Timeout	Check network; retry with increasing delay
16	Insufficient balance	Validate balance before pay-out; clear user message
99	System / channel error	Log full response + requestId; short retry, then support

Example response body

{
  "code": "10",
  "message": "Bad Request",
  "details": "Missing required parameter: merchantId",
  "timestamp": "2020-12-17T10:55:00-05:00",
  "requestId": "req_123456789"
}

Implementation notes

1. Branch on code — copy may change; codes stay stable.
2. Retry only when safe — 01 / 15 / some 99; fix 10–14 and 16 first.
3. Logging — at least code, requestId, and your order id.
4. Idempotent updates — retries and callbacks must not double-credit.

Support playbook for code + responseCode: Customer RAG.