Falcon services
Overview
Falcon services provide a comprehensive suite of fraud detection capabilities focused on monitoring and protecting payment card transactions and account activities. The system handles both monetary and nonmonetary data streams, combining account, customer, and transaction-level information to maintain a robust fraud detection framework.
Real-Time Authorization Engine
Instant transaction validation and decision-making for both credit and debit card purchases at point of sale.
Multi-Level Data Intelligence
Unified processing of account, customer, and card information for comprehensive fraud detection.
Dynamic Profile Management
Real-time updates and monitoring of customer profiles, travel notifications, and account changes.
Secure Card Data Handling
Robust PAN management system with secure mapping between cards and accounts.
Transaction Monitoring System
End-to-end tracking of retail banking transactions, payments, and fund movements.
Flexible Update Framework
Seamless integration of monetary and non-monetary data updates across all service levels.
PAN Information Summary
Status:
Production
Version:
V2
Product:
FalconServices
Overview
This record provides contains Primary Account Number (PAN)-level nonmonetary information. For Falcon Fraud Manager debit or credit usage, there are one or more PIS records for each account indicated by an Account Information Summary (AIS) record.
PAN Information Summary
Status:
Production
Version:
V2
Product:
FalconServices
Node | Child Node | Type | Length | Description |
---|---|---|---|---|
Authorization | Bearer xxxx | string | Authorization Header (Bearer Token) | |
Content-Type | application/json | string | Content Type |
Node Type | Type | Length | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|
NISrvRequest | request_PIS | header | msg_id | string | 12 | Message ID, this field should be unique id for each Api call. This will be generated from client side. If the same message ID is used the system will decline the API call with Error Description “Duplicate Message ID” | ||||
msg_type | string | 12 | Message Type – This can have either “TRANSACTION” or “ENQUIRY” As for this API the value expected is “TRANSACTION” | |||||||
msg_function | string | 50 | Message functions: Should be “REP_FALCON_PIS” | |||||||
src_application | string | 10 | Source Application: This is a free Text and the client can populate the source system from where the API is Initiated Example: TIBCO, IB, MB No Validations of these are kept at Network Systems | |||||||
target_application | string | 10 | The target_application can hold any value from FI side, this can be used by FI to check the target system of the API call | |||||||
timestamp | string | 30 | Timestamp of the request - Format YYYY-MM-DDtHH:MM:SS.SS +04:00 | |||||||
bank_id | string | 4 | Bank Id is Unique Id 4 digit code for each client and the same will be provided once the client setup is completed in our core system. For sandbox testing – Please use “NIC” | |||||||
body | tranCode | string | 3 | The action code. Note tranCode values must be greater or equal to 100. | ||||||
source | string | 10 | Name of source application.Note A header accompanies both a message from a sender to a recipient, and a response from the recipient to the sender. In the response, the source and dest values are reversed. | |||||||
dest | string | 10 | Name of destination application. Note A header accompanies both a message from a sender to a recipient, and a response from the recipient to the sender. In the response, the source and dest values are reversed. | |||||||
extendedHeader | string | 1024 | Extended header. Contains data used by, and returned unaltered to, the requesting system. | |||||||
workflow | string | 16 | Contains the name of the workflow to be executed by Falcon Fraud Manager. | |||||||
recordType | string | 8 | PIS20. | |||||||
dataSpecificationVersion | string | 5 | the value 2 should be added | |||||||
clientIdFromHeader | string | 16 | Unique identifier for the client or subclient. The value of this field is determined jointly by the client and FICO. | |||||||
recordCreationDate | string | 8 | format yyyymmdd Date that this record was created. Time zone must be GMT. | |||||||
recordCreationTime | string | 6 | format hhmmss Time that this record was created. Time zone must be GMT. | |||||||
recordCreationMilliseconds | string | 3 | format sss Milliseconds portion of the time that this record was created. | |||||||
gmtOffset | string | 6 | Filled with blanks. | |||||||
customerIdFromHeader | string | 20 | Primary Customer Identifier. Financial institution's unique identifier for the primary customer for the account. | |||||||
customerAcctNumber | string | 40 | Unique identifier for the account associated with the transaction/record. | |||||||
externalTransactionId | string | 32 | Client-generated unique transaction ID that is unique across all data feeds for a specific installation of Falcon Fraud Manager. | |||||||
pan | string | 19 | Primary Account Number (PAN) of the payment instrument. This is the number encoded or embossed on the payment instrument. | |||||||
type | string | 1 | Type of the card: C = Credit card, D = Debit card, M = Multi-card (combined credit and debit), P = Pre-paid (stored value) | |||||||
subType | string | 2 | Card subtype: B = Commercial, corporate, business, purchasing, fleet, and so on. | |||||||
category | string | 1 | Card category: P = Platinum, G = Gold, S = Standard | |||||||
association | string | 1 | Credit card association under which the card was issued: A = AMEX, D = Discover, J = JCB, M = MasterCard, N = Diners Club, O = Other, P = Proprietary, V = Visa | |||||||
panOpenDate | string | 8 | Date on which a card was first provided on the account. | |||||||
memberSinceDate | string | 8 | Card member since date, as printed on the card. | |||||||
issuingCountry | string | 3 | ISO numeric country code for the country from which the card was issued. | |||||||
cardholderCity | string | 40 | PAN primary address: city | |||||||
cardholderStateProvince | string | 5 | PAN primary address: state or province. | |||||||
cardholderPostalCode | string | 10 | PAN primary address: postal code. | |||||||
cardholderCountryCode | string | 3 | PAN primary address: ISO numeric country code. | |||||||
numberOfPaymentIds | string | 3 | Number of activated payment instruments for this Primary Account Number (PAN). | |||||||
paymentInstrumentId | string | 30 | Filled with blanks for initial PIS record for each PAN. For token provisioning, populated with most recent token or virtual card number. | |||||||
status | string | 2 | "Current card status: 00 = Open, non-statused, active 11 = Open, inactive 20 = Closed 21 = Closed, cardholder request 22 = Closed, bankruptcy or filing for bankruptcy 23 = Closed, bank action (revoked) 24 = Closed, charged-off 25 = Closed, fraud 26 = Closed, stolen 27 = Closed, lost 28 = Closed, deceased 29 = Closed, other 30 = Closed, due to inactivity 31 = Closed, non-fraud, transacted at point of compromise (POC) 32 = Closed, bank-initiated upgrade of card technology 33 = Closed, customer verified attempted fraud 40 = Statused, other (blocked)" | |||||||
statusDate | string | 8 | Effective date of current status. | |||||||
pinLength | string | 2 | Length of PIN. | |||||||
pinSetDate | string | 8 | Date on which the PIN was last set. | |||||||
pinType | string | 1 | Type of PIN: I = Issuer selected, C = Customer selected, Blank = Unknown | |||||||
activeIndicator | string | 1 | PAN activation indicator: Y = Yes, N = No | |||||||
nameOnInstrument | string | 40 | Name that appears on the payment instrument(s). Fill with blanks if the name is not the same for all payment instruments with the specified PAN. | |||||||
expirationDate | string | 8 | PAN expiration date. | |||||||
lastIssueDate | string | 8 | PAN issue date. | |||||||
plasticIssueType | string | 1 | Card issue type for most recently issued payment instrument: F = Force emboss, I = Initial issue, R = Normal reissue, S = Special reissue, T = Token or virtual card issue, Blank = Unknown/other | |||||||
incentive | string | 1 | Incentive program associated with the PAN, if any. Valid values: A = Auto discount, C = Cash back, F = Frequent-flier miles, G = Gas discount, H = Charity contribution, I = Internet discount, L = Telephone discount, M = Merchandise rebate, O = Other, R = General purpose points/rewards, N = None | |||||||
currencyCode | string | 3 | ISO numeric currency code. This is the currency unit used for all currency-based fields. | |||||||
currencyConversionRate | string | 13 | The multiplicative currency conversion rate that is used to convert the currency specified in currencyCode to US dollars. | |||||||
creditLimit | string | 10 | Credit limit for the PAN. Expressed in full units of the currency specified in currencyCode. | |||||||
overdraftLimit | string | 10 | Overdraft limit for the PAN. Expressed in full units of the currency specified in currencyCode. | |||||||
dailyPosLimit | string | 10 | Daily limit for POS transactions for the PAN. Expressed in full units of the currency specified in currencyCode. | |||||||
dailyCashLimit | string | 10 | Daily limit for cash (ATM) transactions for the PAN. Expressed in full units of the currency specified in currencyCode. | |||||||
cashbackLimitMode | string | 1 | Indicates which daily limit cashback counts towards: 0 = No daily limits, 1 = Cashback debited from POS limit, 2 = Cashback debited from CASH limit, 3 = Cashback debited from POS limit and CASH limit, 4 = Cashback not debited from POS limit or CASH limit | |||||||
mediaType | string | 1 | Medium carrying the payment information: C = Chip card, D = Contactless-capable chip card, M = Magnetic-stripe card, N = Contactless | |||||||
aipStatic | string | 1 | Indicates the ability of a chip card to support Static Data Authentication (SDA) as part of the Application Interchange Profile: Y = SDA is supported, N = SDA is not supported, Blank = Unknown/not provided. | |||||||
aipDynamic | string | 1 | Indicates the ability of a chip card to support Dynamic Data Authentication (DDA) as part of the Application Interchange Profile: Y = DDA is supported, N = DDA is not supported, Blank = Unknown/not provided. | |||||||
aipVerify | string | 1 | Indicates the ability of a chip card to support Cardholder Verification as part of the Application Interchange Profile: Y = Cardholder Verification is supported, N = Cardholder Verification is not supported, Blank = Unknown/not provided. | |||||||
aipRisk | string | 1 | Indicates the ability of a chip card to perform Terminal Risk Management as part of the Application Interchange Profile: Y = Terminal Risk Management is to be performed, N = Terminal Risk Management is not to be performed, Blank = Unknown/not provided. | |||||||
aipIssuerAuthentication | string | 1 | Indicates the ability of a chip card to support Issuer Authentication as part of the Application Interchange Profile: Y = Issuer Authentication is supported, N = Issuer Authentication is not supported, Blank = Unknown/not provided. | |||||||
aipCombined | string | 1 | Indicates the ability of a chip card to support DDA/AC Generation (CDA) as part of the Application Interchange Profile: Y = CDA is supported, N = CDA is not supported, Blank = Unknown/not provided. | |||||||
chipSpecification | string | 1 | Chip specification: V = VIS, C = CCD, M = M/Chip, Blank = Unknown/not provided. | |||||||
chipSpecVersion | string | 3 | Chip specification version. Examples: 140 = Version 1.4, 210 = Version 2.1, 400 = Version 4.0. | |||||||
offlineLowerLimit | string | 2 | Lower consecutive off-line limit for card. Blank = Unknown/not provided. | |||||||
offlineUpperLimit | string | 2 | Upper consecutive off-line limit for card. Blank = Unknown/not provided. | |||||||
userIndicator01 | string | 1 | User-defined information. Editable in Falcon Expert rules | |||||||
userIndicator02 | string | 1 | User-defined information. Editable in Falcon Expert rules | |||||||
userIndicator03 | string | 1 | User-defined information. Editable in Falcon Expert rules | |||||||
userIndicator04 | string | 1 | User-defined information. Editable in Falcon Expert rules | |||||||
userIndicator05 | string | 1 | User-defined information. Editable in Falcon Expert rules | |||||||
userCode1 | string | 6 | User-defined information. | |||||||
userCode2 | string | 6 | User-defined information. | |||||||
userCode3 | string | 6 | User-defined information. | |||||||
userCode4 | string | 8 | User-defined information. | |||||||
userCode5 | string | 8 | User-defined information. | |||||||
userData01 | string | 6 | User-defined information.Editable in Falcon Expert rules. | |||||||
userData02 | string | 6 | User-defined information.Editable in Falcon Expert rules. | |||||||
userData03 | string | 6 | User-defined information.Editable in Falcon Expert rules. | |||||||
userData04 | string | 8 | User-defined information. Editable in Falcon Expert rules. | |||||||
userData05 | string | 8 | User-defined information.Editable in Falcon Expert rules. | |||||||
userData06 | string | 8 | User-defined information.Editable in Falcon Expert rules. | |||||||
userData07 | string | 10 | User-defined information.Editable in Falcon Expert rules. |
{
"NISrvRequest": {
"request_PIS": {
"header": {
"msg_id": "236001",
"msg_type": "TRANSACTION",
"msg_function": "REP_FALCON_PIS",
"src_application": "TIBCO",
"target_application": "FALCON",
"timestamp": "2020-07-20T10:49:02.366+04:00",
"bank_id": "default"
},
"body": {
"tranCode": "102",
"source": "TIBCO",
"dest": "FALCON",
"extendedHeader": "EXTENDEDHEADER120001",
"workflow": "modelSTUB",
"recordType": "PIS20",
"dataSpecificationVersion": "2.0",
"clientIdFromHeader": "D360",
"recordCreationDate": "20230912",
"recordCreationTime": "160912",
"recordCreationMilliseconds": "234",
"gmtOffset": "+03.00",
"customerIdFromHeader": "12345000000001",
"customerAcctNumber": "0009991110000000001",
"externalTransactionId": "D360PIS000000000001",
"pan": "1234567890123456789",
"type": "C",
"subType": "B",
"category": "P",
"association": "M",
"panOpenDate": "20220101",
"memberSinceDate": "20190101",
"issuingCountry": "840",
"cardholderCity": "New York",
"cardholderStateProvince": "NY",
"cardholderPostalCode": "10001",
"cardholderCountryCode": "840",
"numberOfPaymentIds": "3",
"paymentInstrumentId": "123456789012345678901234567890",
"status": "00",
"statusDate": "20220101",
"pinLength": "4",
"pinSetDate": "20220101",
"pinType": "I",
"activeIndicator": "Y",
"nameOnInstrument": "John Doe",
"expirationDate": "20251231",
"lastIssueDate": "20220101",
"plasticIssueType": "F",
"incentive": "A",
"currencyCode": "840",
"currencyConversionRate": "1.234567",
"creditLimit": "10000",
"overdraftLimit": "5000",
"dailyPosLimit": "2000",
"dailyCashLimit": "1000",
"cashbackLimitMode": "1",
"mediaType": "D",
"aipStatic": "Y",
"aipDynamic": "Y",
"aipVerify": "Y",
"aipRisk": "Y",
"aipIssuerAuthentication": "Y",
"aipCombined": "Y",
"chipSpecification": "V",
"chipSpecVersion": "140",
"offlineLowerLimit": "05",
"offlineUpperLimit": "15",
"userIndicator01": "A",
"userIndicator02": "B",
"userIndicator03": "C",
"userIndicator04": "D",
"userIndicator05": "E",
"userCode1": "UC1",
"userCode2": "UC2",
"userCode3": "UC3",
"userCode4": "UC4",
"userCode5": "UC5",
"userData01": "U DAT1",
"userData02": "U DAT2",
"userData03": "U DAT3",
"userData04": "USR DAT4",
"userData05": "USR DAT5",
"userData06": "USR DAT6",
"userData07": "USER DAT07"
}
}
}
}
Node | Child Node | Type | Length | Description | |
---|---|---|---|---|---|
Content-Type | application/json | string | Content Type |
Node Type | Type | Length | Description | |||||||
---|---|---|---|---|---|---|---|---|---|---|
NISrvResponse | response_PIS | header | msg_id | string | 12 | Message ID, this field should be unique id for each Api call. This will be generated from client side. If the same message ID is used the system will decline the API call with Error Description “Duplicate Message ID” | ||||
msg_type | string | 12 | Message Type – This can have either “TRANSACTION” or “ENQUIRY” As for this API the value expected is “TRANSACTION” | |||||||
msg_function | string | 50 | Message functions: Should be “REP_PIS” | |||||||
src_application | string | 10 | Source Application: This is a free Text and the client can populate the source system from where the API is Initiated Example: TIBCO, IB, MB No Validations of these are kept at Network Systems | |||||||
target_application | string | 10 | The target_application can hold any value from FI side, this can be used by FI to check the target system of the API call | |||||||
timestamp | string | 15 | Timestamp of the response - Format YYYY-MM-DDtHH:MM:SS.SSS+04:00 | |||||||
bank_id | string | 4 | Bank Id is Unique Id 4 digit code for each client and the same will be provided once the client setup is completed in our core system. For sandbox testing – Please use “NIC” | |||||||
exception_details | application_name | string | 20 | Application Name | ||||||
date_time | string | 30 | Timestamp of the response Format “YYYY-MM-DD HH:MM:SS” | |||||||
status | string | 1 | Status of the request (S/F) | |||||||
error_code | string | 4 | EAI Internal Error Code (Check error codes section for the complete list of error codes and error code descriptions) | |||||||
error_description | string | 100 | Error Description (Check error codes section for the complete list of error codes and error code descriptions) | |||||||
transaction_ref_id | string | 20 | The tracking_id sent in the request will be sent back in response in this field. | |||||||
body | tran_code | number | 3 | The transaction code. 101 for auth, 102 for advice, 108 for profile maturation. | ||||||
source | string | 10 | Name of source application. Note: A header accompanies both a message from a sender to a recipient, and a response from the recipient to the sender. In the response, the source and destination values are reversed. | |||||||
destination | string | 10 | Name of destination application. | |||||||
extended_header | string | 1024 | Extended header. Contains data used by, and returned/unaltered to, the requesting system. For example: Tracking identifier used by requesting system. | |||||||
responseRecordVersion | string | 1 | The response_record_version specifies the version of the scoring response layout. This field is included to support building libraries that support reading multiple versions of scoring response messages. | |||||||
scoreCount | string | 2 | This field specifies the number of scores in the response message and has values from 0 to 8. | |||||||
decisionCount | string | 2 | This field specifies the number of decisions in the response message and has values from 0 to 10. |
{
"NISrvResponse": {
"response_PIS": {
"header": {
"msg_id": "236001",
"msg_type": "TRANSACTION",
"msg_function": "REP_FALCON_PIS",
"src_application": "TIBCO",
"target_application": "FALCON",
"timestamp": "2020-07-20T06:49:02.366Z",
"bank_id": "default"
},
"exception_details": {
"application_name": "TCC-ADP",
"date_time": "2023-02-01T16:39:47.314+04:00",
"status": "S",
"error_code": "000",
"error_description": "Success",
"transaction_ref_id": "236001"
},
"body": {
"tran_code": 101,
"source": "PMAX",
"destination": "TIBCO",
"extended_header": "EXTENDEDHEADER120001",
"responseRecordVersion": "4",
"scoreCount": "00",
"decisionCount": "0"
}
}
}
}
Code | Description |
---|---|
200 | Sample Description |
400 | Bad Request |
401 | Unauthorized |
403 | Forbidden |
500 | Internal Server Error |
502 | Bad gateway |
503 | Scheduled Maintenance |
504 | Gateway Timeout |
596 | Service Not Found |