Page History
...
Parameter info | Description | |
Payment info (Payment ID) | ||
Date | Payment date in SOFI | |
External system | Name of the external system which provided the payment data | |
Merchant | Merchant name | |
Order number | Number of order | |
Bill number | Bill number | |
Payment ID | ID of the payment in the external system | |
Amount | Original payment amount | |
Currency | Original payment currency | |
Payment result | Status of the payment in the external system | |
Risk | Percentage of fraud suspicion (description is below) | |
Test mode | Yes/No | |
Recurring indicator | Yes/No | |
Two-step schema | Yes/No | |
Mean info (6 first and 4 last digits of the card number) | ||
Type | Visa, for example | |
Subtype | Electron, for example | |
Exp. date | Expiration date | |
Card holder | Card holder (full name) | |
Country | Country of the issuer bank | |
Bank | Issuer bank name | |
CSC provided | Did the CSC were entered (yes/no) | |
3DSsecure authorization result | The 3DSecure authorization results (Y - success, N – not success, A - Attempt, U – unknown) | |
3DSsecure involvement check result | The result of 3DSsecure involvement check (1 – involved, 0 – not involved, -1 – unknown, null – error appear during the involvement check) | |
Corporate card | Yes/No | |
Client info (last and first name of payer) | ||
Payer E-mail provided in order | ||
Phone | Payer phone number | |
Mob. phone | Payer mobile phone number | |
IP | IP-address of the payer | |
Country of IP | Country determined by IP | |
Country | Payer country specified during order payment | |
State/Region | Payer state/region specified during order payment | |
City | Payer city specified during order payment | |
Address | The address specified during order payment | |
Additional info | ||
The data on the user's system environment | ||
Processing data | ||
Approval code | Operation execution code (from processing center). Each processing center uses its own codes. | |
Process date | Date of a payment transaction execution in processing center. UTC data (GMT-0) or GMT+ hour-offset. | |
Response code | The result code of payment from processing center. | |
Response comment: | Explanation of the result code from the payment processing center. | |
RRN or STAN: | · Retrieval Reference Number (formed by processing center by its own algorithm) for processing centers which transmitting RRN (currently: BPC, BPCBel, RAIF, SviazBank, MBank, AmexPOA and MULT-family) or · another possible transaction number. | |
Product data | ||
Billing number | Abonent's id number, according to the type of billing, for payment of goods and services. | |
Billing type | The type of subscription contract for the provision of telecommunications services, etc. | |
Air data (additional flight data, details in a special document) | ||
Passengers | ||
Route | ||
Time of departure | ||
PNR | ||
Application and device data | ||
Mobile device ID | Unique number of the user device (UDID, IMEI, MEID, ESN or IMSI). | |
Device | Description of the user device, which is used for payment. | |
Application | Name of the application, which is used for payment. | |
Application version | Version of the application, which is used for payment. | |
MAC-address | MAC address of the user device. | |
Android ID | ID of Android device. | |
Latitude (deg.) | Geographic latitude coordinates defining the position of the payer on the Earth's surface. Specified in degrees. For example, 55.755831. | |
Longitude (deg.) | Geographic longitude coordinates defining the position of the payer to the Earth's surface. Specified in degrees. For example, 37.617673. | |
Suspicious | ||
Testing was not performed due to lack of payment details. | If not enough data was been transferred for analysis. | |
Fraud checking is disabled for the merchant | If the payments are verified by the expert | |
Statistical analysis has revealed <the mathematical model score percentage>% fraud, neural network analysis has revealed <the mathematical model score percentage>% fraud. The analysis by constructing CART (Classification and Regression Tree) found <the mathematical model score percentage>% fraud. | If the payment has passed the check by mathematical models. | |
Expert set payment fraud suspicious as <score percent that were set by expert> | If the payment has evaluated by expert. | |
There are dangerous signs of the payment: | Suspicious data are displayed | |
Can’t resolve the client IP | ||
Card is in the 'Black list' of cards | ||
Email is in the 'Black list' of e-mails | ||
Cookie is in the 'Black list' of cookies | ||
Cookie support is switched off | ||
JavaScript support is switched off | ||
Payer conducted fraudulent payments (number of payments) | ||
There are similar fraudulent payments (number of payments) | ||
Payer country and country of IP mismatch | ||
Payer country and card country mismatch | ||
Country of IP and card country mismatch | ||
No CSC were provided during the payment | ||
Mismatch of the payment parameters repeatability | ||
Card holder and payer name mismatch | ||
Address without any digit | ||
The total score of the payment fraud: <Status> | Possible values of status - Neat, Suspicious, Fraud. | |
...