BucksBox Developer DocsBucksBox Developer Docs
Getting Started
Merchant API
Partner API
SDK
GitHub
Getting Started
Merchant API
Partner API
SDK
GitHub
  • Introduction
  • Error Handling
  • Commission Model

Error Handling

HTTP Status Codes

CodeMeaning
200Request processed (check status field for business result)
400Bad request — validation error, missing fields
401Unauthorised — missing or expired JWT
403Forbidden — insufficient permissions
404Resource not found
409Conflict — duplicate request (same X-Request-Id)
500Internal server error

Business Status Codes

Returned in the status field of the response body:

StatusMeaning
00Success
01Pending / In-progress
03Failed / Rejected

For DMT account verification (NSDL), the data.status field uses a different scale:

NSDL StatusMeaningAction
1Success — account verifiedProceed
0Failure — account invalidNotify customer
-1AmbiguousRequery in 30 s
91Unknown / timeoutRequery in 30 s

Error Response Shape

{
  "status": "error",
  "message": "Invalid IFSC code",
  "errors": [
    { "field": "receiverIfscCode", "message": "Must be 11 characters" }
  ]
}

SDK Error Handling

The SDK surfaces Axios errors with the server response attached:

try {
  const result = await client.dmt.instantTransfer({ ... });
} catch (err) {
  if (err.response) {
    // Server replied with a non-2xx
    console.error(err.response.status, err.response.data);
  } else {
    // Network error or timeout
    console.error(err.message);
  }
}
Prev
Introduction
Next
Commission Model