Page History
...
Parameter name | Icon | Comment |
Order |
| The parameters of the order, which was paid: · BillNumber - bill number in the external system; · OrderNumber - number of order in the external system; · Merchant ID - merchant identity number (external merchant ID); · Merchant - merchant name. Clicking on the icon takes you to the detail of this order (section 3.3). |
Date | Payment date in format DD.MM.YYYY HH:MM. | |
Payment | Payment parameters: · Payment ID in the external system; · Status of the payment in the external system. | |
Amount |
| Original payment amount, the icon corresponds to the currency of payment. |
Payment mean |
| Payment mean parameters: · Payment mean number (masked); · Payment mean holder; · Expiration date; · Issuer bank name; · Country of the issuer bank. The icon corresponds to the group and type of payment mean. |
Payer | Payer parameters: · Last and first name of payer; · E-mail address; · Merchant's internal customer identification; · Phone number. | |
Risk |
| Risk parameters: Fraud percentage; Reasons for the fraud-status determination. Each reason for the fraud-status has its own icon: · fraud-status was determined by the mathematical modeling methods; · corresponds to the 'clear' fraud-status but no checks were performed by mathematical modeling methods as insufficient data were provided for the payment; · corresponds to the 'clear' fraud-status but no checks were performed; · fraud-status was determined by expert; · according to 'Black list' of payment attributes; · according to trust 'white-list' of payment attributes; · according to allowing white list, when payment attributes are out of that list; · by corresponding to the filter on card number; · by corresponding to the filter on E-mail; · by corresponding to the filter on unique payer identity values under application/service of external system; · payment was successfully checked by mathematical methods and passed all filters but some characteristics of payment look like payments that were considered as fraudulent; · by corresponding to the filter on customer country (country is determined by customer IP-address); · by corresponding to the filter on issuer-bank country; · by corresponding to the filter on IP-address; · due to the card belonging to list of trusted cards; · due to the IP belonging to list of trusted IP-address; · due to fraud-lists from bank; · by corresponding to the filter on customer phone number; · in accordance with the limit (based on aggregated payments for a certain period) for the merchant, external system or the payment application. |
Device |
| Description of the user device, which is used for payment. Each type of device its own icon: · computer; · phone. |
...
| Configures number of rows to be shown on the page (select the value from the drop-down box), in the result will be shown not more than specified number of payments on each page. |
| You can go to the last page by pressing “»»»»” button or return to the first page by pressing “««««”.The next page of the payments is available by pressing “»” button and you can go on previous page by button “«”. |
| Anchor | ||||
|---|---|---|---|---|
|
Payment details
Clicking on detail icon (
) on some payment opens a new window with detailed information about the payment.
The following parameters are displayed in this window:
Parameter name | Comment |
Payment ID (payment identity) | |
Processing | |
CODE: | Operation execution code (from processing center). Each processing center uses its own codes. |
DATE | Date of a payment transaction execution in processing center. UTC data (GMT-0) or GMT+ hour-offset. |
RESPONSE | The result code of payment from processing center. |
RRN/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. |
Card | |
Type (subtype) of card | Type (Visa, for example), subtype (Electron, for example) of card. |
Country | Country of the issuer bank |
Card number | Bank card number (first 6 and last 4 digits only). |
Card holder | Card holder (full name). |
VALID THRU: | Expiration date |
Bank | Issuer bank name |
| Did the CSC were entered: · yes; · no. |
| The 3DSecure authorization results: · success; · not success; · attempt; · unknown. |
| The result of 3DSsecure involvement check: · involved; · not involved; · unknown; · error appears during the involvement check. |
Suspicious | |
Statistical analysis | Statistical analysis has revealed <the mathematical model score percentage>% fraud. |
Neural network analysis | Neural network analysis has revealed <the mathematical model score percentage>% fraud. |
Method of constructing CART | The analysis by constructing CART (Classification and Regression Tree) found <the mathematical model score percentage>% fraud. |
Expert mark | Expert set payment fraud suspicious as <score percent that were set by expert>. |
The total score: | Possible values of status - Neat, Suspicious, Fraud. |
Ad parameter into list: | |
Card number | Add the payment mean of current payment to the list. |
Add E-mail address of current payment’s payer to the list. | |
User ID | Add user ID of current payment’s payer to the list. |
Reason | The reason for adding the parameter(s) to the list. |
The result of pressing one of the buttons displayed at the top of the payment details window:: | · Blocked – the number of mean of payment and E-mail address are being added to the "black" lists, and if these values were presented in the corresponding "white" lists, they are become inactive there; the user ID is added to the domain filter. ID пользователя добавляется в доменный фильтр. · Checked - the number of mean of payment and E-mail address are being added to the "grey" lists, and if these values were presented in the corresponding "white" or "black" lists, they are become inactive there; the user ID is become inactive in the domain filter, if this value was presented there. · Trusted - the number of mean of payment and E-mail address are being added to the "white" lists, and if these values were presented in the corresponding «grey» or "black" lists, they are become inactive there. |
| Device info | |
| Client_Browser_Platform | Browser platform name. |
| Client_COOKIES | Unique identity of the payment service user in an external system. |
| Client_JAVA | Java script support enabled indicator. |
| CLIENT_JS_BROWSER_NAME | Customer browser name. |
| CLIENT_JS_VER | Java script interpretator version. |
| CLIENT_LOCAL_TIME | Customer local time. |
| See more | Button for getting more information about payment. |
By choosing of «See more» option the additional window is opened to show the extended details of the payment. It contains several sections, which can be expanded by click on theirs headers:
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. | |
In the field ‘Fraud Suspiciousness’ is shown the SOFI conclusion about the payment suspicion (final scoring) is derived based on estimates of the mathematical models, expert conclusions and other reasons. The reason, by which the final scoring was set, is displayed in brackets.
| Warning |
|---|
The evaluations of mathematical models and expert are varies in range from 0 to 100% while the value displayed in the column 'Fraud probability' can take only three values - 0%, 50%, 100%, which means respectively - 'Neat', 'Suspicious', 'Fraud' payment. |
Additional user settings and export to csv
For comfortable work with SOFI software interface, the user can also choose the display language:
| Warning |
|---|
If you change the display language you should re-login into the system to download the necessary data in the selected language. |
Thus, the user does not need to reconfigure the language when he/she changed the browser or cleared cookies; the language setting for user is stored in a database for later use.
For export of all displayed payments press the icon in the upper-right corner:
A Zip file will be created with a name like AFSPayments_YYYYMMDDhhmmss (where YYYY – year, MM – month, DD – day, hh – hour, mm – minutes, ss – seconds of the moment of the file export in GMT time zone).
Archive contains two file - export.csv and README.
README file is a standard text file. It contains the information about creation date, character encoding:
| Code Block | ||
|---|---|---|
| ||
generated: 2013.01.09 15:10:26 GMT
encoding: UTF-8
format: CSV
ESCAPE_CHARACTER: "
QUOTE_CHARACTER: "
SEPARATOR: ,
Filters:
Period: 2013.01.09 00:00:00 - 2013.01.09 00:00:00 |
File export.csv format and about filters which were used to select the payments. File export.csv is a standard CSV file which can be opened in the MS Excel or OpenOffice Calc. To open file export.csv in MS Excel you should:
- open empty book and select from menu Data -> From Text-> Import data from a text file;
- select the file export.csv to import;
- using the Import wizard:
- on step 1: set that it is file with delimiters, select appropriate encoding (UTF-8 is recommended);
- on step 2: Select semicolon (';') as delimiter;
- on step 3: Select the data type 'Text' for the first column;
- on the last step: you should specify the list of the book that will be used for import.
| Warning |
|---|
File contains all the payments that fit the filter parameters, but not only those that displayed on one page. |