Interaction between the SOFI and external system is organized via XML-interfaces by HTTPS protocol. The external system provides the data of transaction that currently processed to SOFI and receives results of this transaction check on fraud.
The SOFI returns to the external system the payment status and the reasons for the status determination as a result of checking. All possible fraud-statuses of the payment are presented in the table below.
Payment fraud-statuses, which SOFI determines
Name | Code | Description |
Clear | 0 | Fraud is not detected. |
Suspicious | 50 | Transaction passes all filters but data analysis shows that this payment can be considered both (50/50) as fraudulent and as clear. |
Fraud | 100 | Transaction didn't pass some filters or data analysis shows that this payment has all features of fraud . |
All possible reasons for the fraud-status determination are presented in the table below.
Reasons for the fraud-status determination
Name | Code | Description |
Math model | 1 | Fraud-status was determined by the mathematical modeling methods. |
Insufficient data | 2 | Corresponds to the 'clear' fraud-status but no checks were performed by mathematical modeling methods as insufficient data were provided for the payment. |
Not validate | 3 | Corresponds to the 'clear' fraud-status but no checks were performed. |
Expert | 4 | Fraud-status was determined by expert. |
Payment is in black list* | 7 | Fraud-status determined according to black list of payment attributes. |
Payment is in trust white list* | 8 | Fraud-status determined according to trust white-list of payment attributes. |
Payment is out of allowing white list* | 9 | Fraud-status determined according to allowing white list, when payment attributes are out of that list. |
Blocked card | 10 | Fraud-status was determined by corresponding to the filter on card number. |
Blocked e-mail | 11 | Fraud-status was determined by corresponding to the filter on E-mail. |
Blocked unique payer identity | 12 | Fraud-status was determined by corresponding to the filter on unique payer identity values under application/service of external system. |
Blocked customer country | 14 | Fraud-status was determined by corresponding to the filter on customer country (country is determined by customer IP-address). |
Blocked bank county | 15 | Fraud-status was determined by corresponding to the filter on issuer-bank country. |
Blocked IP | 16 | Fraud-status was determined by corresponding to the filter on IP-address. |
Trust card | 17 | Corresponds to the 'Clear' fraud-status due to the card belonging to list of trusted cards. |
Trust IP | 18 | Corresponds to the 'Clear' fraud-status due to the IP belonging to list of trusted IP-address. |
Fraud chain | 13 | Corresponds to the 'Suspicious' fraud-status. This payment was successfully checked by mathematical methods and passed all filters but some characteristics of payment look like payments that were considered as fraudulent. |
Fraud-list from bank | 20 | Payment is considered as fraudulent due to fraud-lists from bank. |
Blocked phone | 19 | Fraud-status was determined by corresponding to the filter on customer phone number. |
Limit restrictions | 21 | Fraud-status is set in accordance with the limit (based on aggregated payments for a certain period) for the merchant, external system or the payment application. |
* these reasons can be specified when there is not more specific reason for the fraud-status determination, for example, blocked card. | ||