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 [2018/12/03 10:26] 127.0.0.1 external edit |
developer:api_specification:special_fields_and_parameters [2019/06/04 14:13] vinayh [Nuvei Fraud Solution Fields] |
||
|---|---|---|---|
| Line 290: | Line 290: | ||
| </WRAP> | </WRAP> | ||
| - | ===== The Threat Metrix Fields ===== | + | ===== Nuvei Fraud Solution Fields ===== |
| - | This feature is also a complementary service to other features in HP and XML integration methods. | + | This feature is also an additional service to existing features in HPP and XML integration methods. |
| - | ThreatMetrix provides software as a service (SaaS) technology that profiles online transactions and activities to determine whether they initiate from fraudsters or legitimate customers. | + | Fraud Solution provides software as a service (SaaS) technology that profiles online transactions and activities to determine whether they initiate from fraudsters or legitimate customers. |
| - | The Payment Gateway accepts or rejects transactions based on the ThreatMetrix Fraud analysis, enhancing the fraud prevention and threat detection for payment transactions on the Nuvei platform. | + | The Payment Gateway accepts or rejects transactions based on the Fraud Solution analysis, enhancing the fraud prevention and threat detection for payment transactions on the Nuvei platform. |
| Each feature of each integration method is going to present details on how to use it, if available, and all you have to do is make sure the terminal in use has this feature settings enabled at its Security & Fraud section, and that your integration is providing the data necessary for the verification. | Each feature of each integration method is going to present details on how to use it, if available, and all you have to do is make sure the terminal in use has this feature settings enabled at its Security & Fraud section, and that your integration is providing the data necessary for the verification. | ||
| + | |||
| + | <WRAP center important 100%> | ||
| + | **TERMINAL CONFIGURATION**\\ | ||
| + | The terminal used to process the tranaction must have the Fraud Solution feature enabled and configured if you want it used on tha transaction or any transaction processed by that terminal. | ||
| + | </WRAP> | ||
| + | |||
| + | The terminal returned with **REVIEW**, when using Fraud Solution, needs to be manuall 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 teh 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. | ||
| + | |||