Browser Post Validation Response Fields
This chapter describes the data that is returned from validation events that can occur when processing using the Browser Post API.
BP_FIELD_ERRORS
The BP_FIELD_ERRORS field will contain a pipe/caret-delimited list of the fields that failed and the reason code for the failure, during a request to the Browser Post API. In the example below, the ACCOUNT_NBR and EXP_DATE fields were missing and the FIRST_NAME field failed the regular expression validation. All other POSTed fields were accepted by the Browser Post system. The possible field error reason codes are listed in the following table.
Example:
BP_FIELD Error Codes
| Code | Description |
|---|---|
| FE_001 | Required Field Missing |
| FE_002 | Field failed RegEx Validation |
| FE_003 | ACCOUNT_NBR failed MOD-10 check |
BP_RESP_CODE and BP_RESP_TEXT
The BP_RESP_CODE field contains a code value that corresponds with one of the specific validation events that can occur when processing using the Browser Post API. The table below outlines the possible codes that may be received. Contact the EPX Integration team for assistance in troubleshooting error messages received while implementing the Browser Post API.
BP_RESP_CODE
| BP_RESP_CODE | BP_RESP_TEXT |
|---|---|
| BP_000 | Success |
Merchant Configuration Errors
These errors are a result of instances where the Merchant configuration file cannot be loaded. Without this file we cannot access the merchant’s stored value for INVALID_REDIRECT_URL, so the client browser will be redirected to a generic EPX error page.
|
NOTE: Due to the nature of the issue, these errors cannot be returned; however, they will be logged and for assistance in troubleshooting contact the Integration team at EPX. |
Merchant Configuration Errors
| BP_RESP_CODE | BP_RESP_TEXT |
|---|---|
| BP_100 | Missing TAC |
| BP_101 | TAC decryption error |
| BP_102 | Invalid TAC parameter |
| BP_103 | TAC validation – 4-part key mismatch |
| BP_104 | Merchant configuration not found |
| BP_105 | Merchant configuration decryption error |
| BP_106 | Merchant configuration parse error |
| BP_110 | Merchant REDIRECT_URL not configured |
REDIRECT_URL Validation Errors
These errors are a result of instances where the REDIRECT_URL cannot be validated. If a merchant provides a value for INVALID_REDIRECT_URL, the browser will be redirected there with error codes, response variables, etc. If INVALID_REDIRECT_URL is not configured, the browser will be redirected to the EPX generic error page.
REDIRECT_URL Validation Errors
| BP_RESP_CODE | BP_RESP_TEXT | Additional Detail |
|---|---|---|
| BP_111 | TAC validation – REDIRECT_URL missing | This response occurs when a redirect URL was not sent. |
| BP_112 | TAC validation – Invalid REDIRECT_URL | If this error occurs the system will append the value for REDIRECT_URL contained in the TAC to the response output, using the tag: REDIRECT_URL |
| BP_113 | Merchant REDIRECT_URL mismatch | If this error occurs the RTBP system will append the value for REDIRECT_URL contained in the TAC to the response output, using the tag: REDIRECT_URL. In addition, the system will also echo back the stored (configured URL, sans query string) value for REDIRECT_URL, using the tag: MERCH_REDIRECT_URL |
Basic Validation Errors
These errors are a result of instances where the REDIRECT_URL has been validated, but there is an additional validation issue. The code will be returned to the REDIRECT_URL address if they occur. The BP_140 code is used for any field mismatch validation failures.
Basic Validation Errors
| BP_RESP_CODE | BP_RESP_TEXT |
|---|---|
| BP_120 | Multiple TAC use |
| BP_121 | Expired TAC |
| BP_122 | TAC validation - TRAN_NBR missing |
| BP_123 | TAC validation - TRAN_GROUP missing |
| BP_124 | TAC validation - AMOUNT missing |
| BP_125 | TAC validation - POST value mismatch |
| BP_126 | TAC validation - Invalid merchant validation code (MVC) |
| BP_127 | TAC validation - Invalid RESPONSE_URL |
| BP_128 | TAC validation - TRAN_GROUP mismatch |
| BP_129 | TAC validation - Unknown TRAN_GROUP |
| BP_130 | Unknown tran_code |
| BP_131 | System Error |
| BP_132 | 3-D Secure authentication failure |
| BP_133 | 3-D Secure system error |
| BP_140 | Field error |