Fraud monitoring and reporting

Raise, read and report fraud against a card or a transaction.

Operations0DomainFraudStatedocumentedAPIs0

Every authorisation is scored before it is answered. The card platform hands a fraud service sixty-five facts about the transaction and waits for a decision; what you read as an approval or a decline already has that answer in it.

Fraud service · get-fraud-response-for-everestThe service is the platform's own and sits on the authorisation path. It is not a call a bank makes and no address for it is published, because there is nothing a reader could do with one.

What the decision is made from 65

Message and routing 11

What the message is and how it is identified downstream.

module	number
transactionMessageId	number
mti	string
stan	string
rrn	string
refID	string
orderId	string
source	string
psqn	string
transactionDate	date-time
localTransactionDate	date-time

Card 15

The largest group, and the one worth reading closely: the card number arrives in five forms at once — masked, reference, shadow, hashed and encrypted — beside the BIN. Which one a rule keys on is a decision, not a detail.

maskedCardNo	string
referenceCardNo	string
shadowCardNo	string
hashedCardNo	string
encryptedCardNo	string
bin	string
cardType	string
cardDomain	string
cardEmbossDate	date-time
cardExpireDate	date-time
cardCountryCode	string
isDigitalCard	boolean
isVirtualCard	boolean
productNumber	string
customerNo	string

Merchant and acquirer 7

Who accepted the card, and where.

acquirerId	string
merchantId	string
merchantName	string
merchantCity	string
bkmMerchantId	string
merchantCountryCode	string
mcc	string

Cardholder verification 9

How, and whether, the cardholder was proved to be present. Nine of the sixty-five, which is the weight this decision gives the question.

isEmvTransaction	boolean
isPinEntered	boolean
pinStatus	string
pinEntryCode	string
hasCvv	boolean
hasCvv2	boolean
cvmType	string
cvmResult	string
securityLevelIndicator	string

Transaction classification 8

What kind of transaction this is, and whether it undoes an earlier one.

tranCode	string
tranCodeDetail	string
tranCodeSpecial	string
tranCodeMatrixId	string
tranProcessType	string
isReversal	boolean
isVoid	boolean
isClearing	boolean

Amounts 6

Three amounts, each with its own currency: what the cardholder was quoted, what the card is billed, and what the local leg was. They differ under currency conversion, and a rule that reads the wrong one is reading a different transaction.

originalAmount	number
originalCurrencyCode	string
billingAmount	number
billingCurrencyCode	string
localAmount	number
localCurrencyCode	string

Terminal and channel 5

The device and the route the transaction arrived on.

terminalId	string
terminalType	string
posEntryMode	string
catLevel	string
channelType	string

Prior outcome 4

What has already been answered about this transaction, so the decision is not made twice from a blank slate.

authorizationCode	string
hasPendingLastResponse	boolean
lastResponseCode	string
issuerResponseCode	string

Four fraud and risk series are published beside the rest of the platform's metrics — see Dashboards and metrics.