Overview

Every API response tells you whether the request succeeded. When it fails, the response includes an error code or message that explains what went wrong. Use this page to understand the response format, then open the error page for the API you're using.

Response Fields

Merchant API

Field	Description
`error_no`	Result of the request. `S00` means success; any other value is an error code (for example `E05` or `D09`).
`error_code`	Standard response code for the transaction (for example `00` = Approved).
`msg`	Short result message (for example `APPROVED` or `INVALID AMOUNT`).
`desc`	More detail about the result.

Success example

{
  "error_no": "S00",
  "error_code": "00",
  "msg": "APPROVED",
  "desc": "APPROVAL TAS163",
  "txnid": "11254314"
}

Vault API

Field	Description
`code`	HTTP status code. `400` means the request failed.
`status`	`FAILED` when the request is not processed.
`errors`	Error message explaining what went wrong.

Error example

{
  "code": 400,
  "status": "FAILED",
  "errors": "Card number is invalid"
}

Merchant CRM API

Field	Description
`code`	HTTP status code. `400` means the request failed.
`status`	`false`, `Failed` or `FAILED` when the request is not processed.
`message` or `errors`	Error message explaining what went wrong. Depending on the endpoint, the message is returned in `message` or `errors`.

Error example

{
  "code": 400,
  "status": "FAILED",
  "errors": "Invalid value for key card_type"
}

Processor Response Codes

When a card transaction reaches the processor, the processor returns its own response code. The gateway maps it to a standard Response Code, so the same result looks the same no matter which processor handled it.

Use the Response Code in your integration logic.
Use the Processor Response Code and message when troubleshooting with support.

Handling Errors

Check the result first:
- Merchant API: error_no is S00.
- Merchant CRM API and Vault API: code is not 400, and status is not false or FAILED.
Find the error: look up the code or message on the matching error page below.
Fix and retry: follow the resolution for that error, then send the request again.
Timeouts: if a transaction times out, check its status with the Transaction Fetch API before retrying, to avoid duplicate charges.
Still failing: contact Valor support with the request time, EPI and error details. Never share full card numbers, tokens or API keys.

Error Code Pages

Page	What it covers
Merchant API Errors	Validation and processing errors from the Merchant APIs (codes such as E01, D09, A01, SUB01).
Vault API Errors	Errors from the Vault APIs for customers, cards, tokens and ACH profiles.
Merchant CRM API Errors	Errors from the Merchant CRM APIs for merchant boarding, stores, EPIs, operators and settings.
Processor Response Codes	Response codes from each card processor and their standard Response Code.