Page History
...
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. |