Fraud Login Event - Field Descriptions

The following page details each of the fields that can be used in the request and received in the response when using the Fraud Login Event endpoint.

Request

The following table describes fields that can be included in the body of the request when using the Fraud Login Event endpoint.

FieldDescriptionTypeMandatory
channelChannel through which the login was made. Recommended values are "online" or "mobile". Further free text examples can be added to fit the use case.StringNo
customerEnrollmentDateThe date in which the customer signed up to use mobile/online banking.date-timeNo
customerFlagUsed for specific customer flags that can determine treatment strategies, for example if a customer is a VIP or classified as vulnerable. This is an array that can include free text values.StringNo
customerIdThe unique identifier for the customer.StringYes
customerTypeThe customer type. For example, Retail or Commercial.StringNo
deviceObject that contains details of the device used for the login attempt.
anonymizerInUseFlagIf true, indicates if the anonymizer was in use during the session.BooleanNo
areaCodeThe device area code captured during the customer session.StringNo
browserTypeThe device browser type captured during the customer session.StringNo
browserVersionThe device browser version captured during the customer session.StringNo
cityThe device city name captured during the customer session.StringNo
clientTimezoneThe client time zone captured during the customer session.StringNo
continentCodeThe device continent code captured during the customer session.StringNo
cookieIdThe cookie ID used during the customer session.StringNo
countryCodeThe device country code captured during the customer session.StringNo
countryNameThe device country name captured during the customer session.StringNo
deviceFingerprintThe device fingerprint captured during the customer session by a third party.StringNo
deviceIMEIThe IMEI of the device used during the customer session.StringNo
deviceNameThe device name given at point of registration.StringNo
flashPluginPresentThe Flash Plugin captured during the customer session.StringNo
httpHeaderThe HTTPHeader captured during the customer session.StringNo
ipAddressV4The IP address v4 captured during the customer session.StringNo
ipAddressV6The IP address v6 captured during the customer sessionStringNo
metroCodeThe device metropolitan code captured during the customer session.StringNo
mimeTypesPresentThe Mime-Types captured during the customer session.StringNo
mobileNumberDeviceLinkA concatenated string of the mobile number and device ID to establish the link.StringNo
networkCarrierThe network carrier captured during the customer session.StringNo
oSThe device Operating System captured during the customer session.StringNo
postalCodeThe device postal code captured during the customer session.StringNo
proxyDescriptionThe proxy type description captured during the customer session.StringNo
proxyTypeThe proxy type captured during the customer session.StringNo
regionThe device region code captured during the customer session.StringNo
screenResolutionThe screen resolution captured during the customer session.StringNo
sessionLatitudeThe latitude captured during the customer session.NumberNo
sessionLongitudeThe longitude captured during the customer session.NumberNo
timestampThe timestamp of the login captured during the customer session.Date-TimeNo
typeThe device type captured during the customer session.StringNo
userAgentStringThe user agent string captured during the customer session.StringNo
deviceEnd of the device object.
deviceIdA unique identifier of the device performing the event, such as the mobile/cell phone used for a transaction (For example, Google or Apple Pay transactions).StringNo
eventTimeDate and time that the login occurred.Date-TimeYes
initiatingPartyIdIdentifier of the initiating party, where this is not the account ID. This is mandatory for commercial use cases.StringNo
initiatingPartyNameA human readable string identifying the initiator as indentified in the intiatiatingPartyId attribute.StringNo
initiatingPartyTypeThis field describes how the initiating party is being used. Represents an individual user in the commercial banking setting. However it can also be used to represent the Open Banking entity that initiates the action. This field describes how the initiating party is being used. For example, "User" or "Open Banking".StringNo
productIdThe unique product identifier.StringNo
programManagerCodeThe unique code for the program manager.StringYes
sessionObject that contains details for the login.
sessionIdPersistent identifer for a single session.StringNo
sessionStartTimeStart time and date of the session.Date-TimeNo
sessionEnd of the session object.
traceIdCustomer provided ID for tracking events.StringNo
thirdPartyDetailsObject that contains details sent by the third party provider.
authenticationFailedReasonIndicates the reason for failure, such as "user cancel" or "challenge response failed".StringNo
authenticationMethodThe authentication method used by the third party.StringNo
authenticationServiceTypeIndicates the authentication service being registered. This field is only populated if the registration event is for an authentication service.StringNo
authenticationStatusIndicates the status of the authentication. For example, auth_success.StringNo
browserAnomalyReturns a value of 'yes' if an anomaly is detected with the various browser attributes collected during profiling, including Flash, JavaScript and User Agent.StringNo
browserCrawlerIdentificationThe agent, parsed from the http user agent/ browser string, which indicates if the client is not a real browser, e.g. crawler.StringNo
browserHTTPInfoThe user agent/browser string presented in the HTTP header.StringNo
browserHTTPInfoAnomalyIndicates if there is an anomaly in the browser string content.StringNo
browserInfoThe browser information, determined using a combination of Flash, JavaScript and User Agent. If browser detection was unsuccessful this will be set to Unknown. If a browser is detected that is not recognised, it will be set to Other.StringNo
browserLanguageThe code for the language that the browser is configured to accept.StringNo
browserLanguageAnomalyIndicates if there is an anomaly between the browser_language and flash_lang values. This happens when both appear, and none of the browser's preferred languages is the same as the flash_lang.StringNo
browserStringMismatchIndicates if there is a mismatch between the javascript user agent string and the HTTP user agent string.StringNo
browserVersionIdThe version of the browser installed.StringNo
deviceFingerprintThe device fingerprint as calculated by the third party.StringNo
deviceFingerprintFirstSeenThe date that this entity was first encountered by the third party.StringNo
deviceFingerprintResultDefines the result of third-party identification. If this field is set to not found, it indicates this is the first time the third party has seen this entity involved in a transaction. If the field is set to success, indicates that the third party has intelligence on this entity.StringNo
deviceFingerprintScoreThe risk score calculated by the third party.IntegerNo
deviceFirstSeenDateThe date that this entity was first encountered by the third party, in yyyy-mm-dd format.StringNo
deviceIdConfidenceThe probability of this being the same device.IntegerNo
deviceMatchResultIndicates a new device, whether it was encountered before, and if not enough attributes were gathered to create a device identity.StringNo
deviceRootJailBreakIndicates whether a mobile device has Root privileges on Android, or a Jailbroken iOS device. This stores a numerical value that indicates the number of jailbreak/root elements on a device. 0 indicates that there are no jailbreak/root elements detected.IntegerNo
deviceRootJailBreakReasonA comma separated string containing additional information that describes the elements on the device that triggered the Jailbreak or Root detection.StringNo
deviceScoreThe risk score calculated by the third party.IntegerNo
deviceScoreReasonThe risk score reason code. For example, InAuth.StringNo
digitalIdThe digital identifier assigned by the third party.StringNo
digitalIdConfidenceIndicates the level of confidence that the event appears to be matching the behaviour from the returned digitalId.IntegerNo
digitalIdTrustScoreRatingThe trust score rating associated with the ThirdParty ID. For example, very_high.StringNo
digitalIdTrustScoreReasonCodeThe reason codes describing the Trust Score rating (multiple values). There can be up to 64 characters per entry and there may be an unlimited number of entries.StringNo
loginVerificationResultIndicates the result of the login verification. not found indicates this is the first time the third party has seen this entity involved in a transaction. success indicates that the third party has intelligence on this entity.StringNo
loginVerificationScoreThe login verification risk score calculated by the third party.IntegerNo
nameVerificationScoreThe name verification risk score calculated by the third party.IntegerNo
nameVerificationResultIndicates the result of the name verification. not found indicates this is the first time the third party has seen this entity involved in a transaction. success indicates that the third party has intelligence on this entity.StringNo
overallAssessmentThe overall assessment of the verification. For example, FAIL.StringNo
overallAssessmentReasonIndicates the reason for failure, such as user cancel or challenge response failed.StringNo
phoneVerificationResultIndicates the result of the phone verification. not found indicates this is the first time the third party has seen this entity involved in a transaction. success indicates that the third party has intelligence on this entity.StringNo
phoneVerificationScoreThe phone verification risk score calculated by the third party.IntegerNo
profiledDeviceTypeIndicates the type of device that was profiled, including mobile app, desktop app, or web browser on a desktop or mobile platform.StringNo
providerNameThe name of the third party provider used to capture and assess session and behaviour biometric use.StringNo
refNumberThe third party provider reference number assigned when the third party assesses session risk and returns results to the customer.StringNo
virtualDeviceIdentificationIndicates whether a mobile device is running in an Emulator on Android, or a Simulator on iOS. This stores a numerical value that indicates the number of emulator/simulator elements on a device.IntegerNo
wiFIAccuracyThe accuracy of the estimated location, in meters. This represents the radius of a circle around the given location.IntegerNo
wiFiLatitudeThe Latitude of the WiFi connection based on BSSID.IntegerNo
wiFiLongitudeThe Longitude of the WiFi connection based on BSSID.IntegerNo
thirdPartyDetailsEnd of the thirdPartyDetails object.
verificationResultThe final result of the verification. This indicates whether the customer was successful in verifying themselves. The verificationType determines whether any specific verifications were failed or were successful. If the customer is successfully verified, then it is set to SUCC.StringNo
verificationTypeObject that enables you to track multiple verifications required to perform the designated events. For each verification that took place, SUCC indicates successful verification, and FAIL indicates verification failed.
aaIndicates whether the Account holder Authentication Value (AAV) was successful.StringNo
accountDigitalSignatureIndicates whether the Account-based digital signature authentication was successful.StringNo
avsIndicates whether the Address Verification Service (AVS) was successful.StringNo
biometryIndicates whether the biometric authentication of the cardholder was successful.StringNo
cardholderIdentificationDataIndicates whether the cardholder data provided for verification was successful.StringNo
cryptogramVerificationIndicates whether the verification of a cryptogram generated by a chip card or another device was successful.StringNo
cscVerificationIndicates whether the verification of the Card Security Code (CSC) was successful.StringNo
cvvIndicates whether the Card Verification Value (CVV) was successful.StringNo
offlinePINIndicates whether the offline PIN authentication was successful.StringNo
oneTimePasswordIndicates whether the verification of a One-Time Password (OTP) provided by the issuer was successful.StringNo
onlinePINIndicates whether the online PIN authentication was successful.StringNo
otherIndicates whether the other type of verification was successful.StringNo
paperSignatureIndicates whether the handwritten paper signature was successful.StringNo
passiveAuthenticationIndicates whether the authentication based on statistical cardholder behaviour was successful.StringNo
passwordIndicates whether the authentication by a password was successful.StringNo
threeDSIndicates whether the authentication performed during a secure electronic commerce transaction was successful.StringNo
tokenAuthenticationIndicates whether the cryptogram generated by the token request or a customer device to validate the authorised use of a token was successful.StringNo
verificationTypeEnd of the verificationType object.

Response

If successful, a 204 No Content response is returned.