Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
developer:api_specification:special_fields_and_parameters [2019/06/04 14:16] vinayh [Nuvei Fraud Solution Fields] |
developer:api_specification:special_fields_and_parameters [2022/03/31 08:32] lezlieh update with secure token |
||
|---|---|---|---|
| Line 45: | Line 45: | ||
| <code java> | <code java> | ||
| - | 5B39821025C33A3C37560196F36AF68668E46E82AFC4017434D72E62DBC4C06781AFC6364E992D5594656FB185C901ECE65ADF85E8822832B8985F602E533EBA | + | 5b39821025c33a3c37560196f36af68668e46e82afc4017434d72e62dbc4c06781afc6364e992d5594656fb185c901ece65adf85e8822832b8985f602e533eba |
| </code> | </code> | ||
| Line 182: | Line 182: | ||
| To use a custom field with a request, first verify if the request you want to use allows the custom fields. If it allows, all you have to do is to add to the request as many custom field tags as you need, using its original NAME at the NAME tag attribute, inform the value you desire, then send the request. | To use a custom field with a request, first verify if the request you want to use allows the custom fields. If it allows, all you have to do is to add to the request as many custom field tags as you need, using its original NAME at the NAME tag attribute, inform the value you desire, then send the request. | ||
| - | Example: registering a Secure Card with custom fields to inform the client's loyalty system id (custom field ClientLSID) and the current amount of accumulated points (custom field ClientLSCP). | + | Example: registering a Secure Token with custom fields to inform the client's loyalty system id (custom field ClientLSID) and the current amount of accumulated points (custom field ClientLSCP). |
| <code xml> | <code xml> | ||
| Line 306: | Line 306: | ||
| The terminal returned with **REVIEW**, when using Fraud Solution, needs to be manual reviewed by the Merchants. A new report feature on Selfcare System allows Merchant to manually accept transaction marked as **REVIEW** by Fraud Solution and the XML gateway allows the use of the status update service to change a transaction to **APPROVE** or **REJECT** depending on the merchant's needs. | The terminal returned with **REVIEW**, when using Fraud Solution, needs to be manual reviewed by the Merchants. A new report feature on Selfcare System allows Merchant to manually accept transaction marked as **REVIEW** by Fraud Solution and the XML gateway allows the use of the status update service to change a transaction to **APPROVE** or **REJECT** depending on the merchant's needs. | ||
| - | |||
| Be aware transaction with REVIEW status are not going to be settled until it is rejected or approved by the merchant. | Be aware transaction with REVIEW status are not going to be settled until it is rejected or approved by the merchant. | ||
| + | |||
| + | |||
| + | **SAMPLE RESPONSE CODE:** | ||
| + | |||
| + | **APPROVED:** | ||
| + | |||
| + | * **UNIQUEREF:** JZUBX2INT8 | ||
| + | * **RESPONSECODE:** A | ||
| + | * **RESPONSETEXT:** APPROVAL | ||
| + | * **APPROVALCODE:** UVUVUM | ||
| + | * **FRAUDREVIEWRESPONSE:** | ||
| + | * **FRAUDREVIEWSTATUS:** PASS | ||
| + | * **FRAUDREVIEWRISKRATING:** LOW | ||
| + | * **FRAUDREVIEWSCORE:** -20 | ||
| + | * **FRAUDREVIEWREASONCODE:** NO DEVICE ID | ||
| + | * **DATETIME:** 2019-06-28T18:41:02 | ||
| + | * **AVSRESPONSE:** U | ||
| + | * **CVVRESPONSE:** M | ||
| + | * **HASH:** 135ef96ed3c28ef5f92a0919d9c9e73e6d855a9701ccf37911578f372265407f1a43ae2fc18119884d3ee73483c904a930112875ac90722e1e0347e93b4cf1a5 | ||
| + | |||
| + | **REJECT:** | ||
| + | |||
| + | * **UNIQUEREF:** BKMDDH6DM0 | ||
| + | * **RESPONSECODE:** D | ||
| + | * **RESPONSETEXT:** RISK REJECTION | ||
| + | * **APPROVALCODE:** UVUVUM | ||
| + | * **FRAUDREVIEWRESPONSE:** | ||
| + | * **FRAUDREVIEWSTATUS:** REJECT | ||
| + | * **FRAUDREVIEWRISKRATING:** LOW | ||
| + | * **FRAUDREVIEWSCORE:** -20 | ||
| + | * **FRAUDREVIEWREASONCODE:** NO DEVICE ID | ||
| + | * **DATETIME:** 2019-06-28T18:50:50 | ||
| + | * **AVSRESPONSE:** U | ||
| + | * **CVVRESPONSE:** M | ||
| + | * **HASH:** df1dccbcb360688c4d56f5197cda8ff1c7f80a0d8bcf12570681064b2d3568deac354f6e46e1c72bb8f6a4aea99bb52dc5dd301522643e24d96d313c2034c420 | ||
| + | |||
| + | |||
| + | **REVIEW:** | ||
| + | |||
| + | * **UNIQUEREF:** BK8C9KCC03 | ||
| + | * **RESPONSECODE:** A | ||
| + | * **RESPONSETEXT:** APPROVAL | ||
| + | * **APPROVALCODE:** UVUVUM | ||
| + | * **FRAUDREVIEWRESPONSE:** | ||
| + | * **FRAUDREVIEWSTATUS:** REVIEW | ||
| + | * **FRAUDREVIEWRISKRATING:** LOW | ||
| + | * **FRAUDREVIEWSCORE:** -20 | ||
| + | * **FRAUDREVIEWREASONCODE:** NO DEVICE ID | ||
| + | * **DATETIME:** 2019-06-28T18:52:53 | ||
| + | * **AVSRESPONSE:** U | ||
| + | * **CVVRESPONSE:** M | ||
| + | * **HASH:** 446345d95b9f5296ced5367e515260237409c5677531485b1da774ea1713b32df9ae3ab3fbe8ad249302d6453697a38e57b6af62077271040771713e66e05981 | ||
| + | |||
| + | |||