Dock Protect allows the issuer to connect to the Falcon®, owned by FICO®, the leading global fraud management system for fraud prevention in the payments industry.

The innovative business model that unites Falcon® with Dock's expertise is accessible to companies of all sizes. The anti-fraud solution shows significant results confirming its effectiveness.

For a better understanding of fraud prevention with Falcon® and its applicability in daily life, Dock prepared the following video:



Advantages of Falcon®

In addition to preventing fraudulent transactions, Falcon® identifies and allows healthy transactions to happen, establishing rapid communication with issuers from any suspicious transaction. Among the main technological characteristics of the system are:

  • Rapid deployment: within three or four weeks the platform will be fully implemented and working, charged according to the number of transactions analyzed.

  • Technological intelligence: the evolutionary characteristic of the technology, once implemented, allows for constant review as the database grows. The model continues to be improved by the mechanisms of Artificial Intelligence and can also undergo changes from the issuers' feedbacks .

  • Platform robustness: it allows a large volume of operations to be analyzed quickly, reliably and accurately, delivering detailed analysis of movements.

  • Reduced response time: the best anti-fraud solution is the one that can quickly identify any suspicious behavior and make automated decisions about it. The response time of Falcon® corresponds to milliseconds in the step of analyzing the authorization of the transactions themselves.

Some data that proves the credibility of Falcon® as the greatest global player overall number and transaction history are:

  • Its mathematical and Artificial Intelligence models are in more than 9,000 financial institutions and in 17 from 20 largest global card issuers;
  • It protects 3 billion accounts and 65% of cards globally;
  • It has 100 patents for machine learning innovations specific to fraud.


Falcon® modules

Falcon modules Card and Falcon Banking follow the traditional transactional flow then get at the Falcon® system, where the transaction will be scored with a score risk and after that it will go through the defined rules portfolio, carrying out the parameterized actions and indicating whether that transaction should be approved or denied according to the rules.


Falcon Card (CRTRANCRTRAN - Transactions made on credit. and DBTRANDBTRAN - Transactions made in debit.)

Corresponds to the protection of all credit, debit, prepaid, voucher and private label transactions. The flow of its operation is shown below.

FIG: Transactional flow of the Falcon CardFIG: Transactional flow of the Falcon Card

FIG: Transactional flow of the Falcon Card

1 - A person makes a transaction on credit or debit;
2 - The merchant forwards transaction information to the acquirer;
3 - The acquirer combines the transaction information into an authorization request message and passes it to the card brand;
4 - The card brand forwards the request to the authorizer;
5 - The authorizer receives it and makes initial validations for the transaction. They identify it must be forwarded to the Falcon system for fraud analysis;
6 - The Fraud Prevention API makes the communication link between the authorizer and Falcon;
7 - Falcon reviews the request and (8) sends a validation response to the authorizer;
9 - The Fraud Prevention API makes the communication link between Falcon and the authorizer;
10 - The authorizer responds about authorization to the card brand;
11 - The card brand forwards the authorization response to the acquirer;
12 - The acquirer passes the result of the authorization request to the merchant;
13 - The merchant passes the result of the authorization request to the person;
14 - The person receives follow-up on their transaction authorization.


📘

Note

The issuer that does not process the authorization with Dock will have to send the transactions in a layout (CRTRAN and DBTRAN), through APIs integrated with the fraud prevention API.


Falcon Banking (RBTRANRBTRAN - Transactions made in retail banking or retail bank, which is a commercial bank that carries out transactions directly with consumers.)

Corresponds to the protection of all banking operations such as transfers (TED, DOC, P2P and PIX), payments, recharges and deposits.

The flow of its operation is presented below, in which the API retail represents the set of APIs related to retail banking it's the middleware the issuer software that intermediates the relationship between the transaction by retail banking and the Falcon environment on the Dock platform.

FIG: Transactional flow of Falcon BankingFIG: Transactional flow of Falcon Banking

FIG: Transactional flow of Falcon Banking

1 - A person makes a transaction by retail banking;
2 - The middleware of the issuer receives it and makes initial validations for the transaction. They identify it must be forwarded to the Falcon® system for fraud analysis;
3 - The API retail makes the communication link between the issuer's middleware and the fraud prevention API;
4 - The fraud prevention API makes the communication link between the API retail and Falcon;
5 - Falcon® reviews the request and (6) sends a validation response to the issuer's middleware;
7 - The fraud prevention API makes the communication link between Falcon® and the API retail;
8 - The API retail makes the communication link between fraud prevention API and the issuer's middleware;
9 - The issuer's middleware responds about authorization to the person;
10 - The person receives follow-up on their transaction authorization.


CCS - Customer Communication Service

CCS allows case handling to be done automatically via notifications by email , voice, text and application ( push notification ) focused on a scalable operation and is already integrated in the Falcon® platform.

It works with a customizable decision tree, which allows a higher rate of contact with the end customer, and consecutively increases the operational efficiency of the operations team.

This decision tree can be divided into high, medium and low risk so that different contact strategies are carried out in each row, according to the effectiveness of each rule implemented in Falcon®. Here are some examples of strategies:

High risk

  • Preventive blocking made in the card;
  • Sending the first SMS;
  • Sending the second SMS;
  • Attempted contact by cell phone;
  • Attempted residential contact;
  • Attempted commercial contact.
    If the contact does not succeed, after two hours, the following actions will be taken:
  • Sending another SMS;
  • Another attempt at cell phone contact.

Medium risk

  • Sending the first SMS;
  • Preventive blocking included in the card;
  • Sending the second SMS;
  • Attempted contact by cell phone;
  • Attempted residential contact;
  • Attempted commercial contact.

Low risk

  • Sending the first SMS;
  • Sending the second SMS;


Falcon® flows (Card and Banking)

Falcon® is an application multitenantmultitenant - Multitenancy or "software multi-tenancy" refers to a software architecture in which a single instance of software runs on a server and serves multiple tenants. Systems designed in this way are often referred to as shared., which allows management to be done by several issuers, each one with their access to the tenant. Dock offers two options for managing the tool:


Full management by the issuer

This type of management allows the issuer to be responsible for all its strategy and operation against fraud.

FIG: Full management of the fraud prevention by the issuerFIG: Full management of the fraud prevention by the issuer

FIG: Full management of the fraud prevention by the issuer


🚧

Attention

The full issuer management allows the use of the CCS platform, however this tool will be handled by FICO® upon request from Dock.


Shared management

This type of management allows the issuer to be responsible for all its strategy and operation against fraud, and Dock acts to create and setup rules on the system related to the strategy, making available the hiring of the CCS tool to handle alerts automatically.

FIG: Shared management of fraud preventionFIG: Shared management of fraud prevention

FIG: Shared management of fraud prevention



Falcon® Layouts (Card and Banking)

Dock Protect makes the Falcon platform available through APIs for consumption via SaaS, where registration and transactional integrations are required. They are presented below.

Registration layouts

Falcon® has layouts which are necessary for the operation of the application, performing integrations through the following endpoints:

  • CIS ( Customer Information Summary ): summary of non-monetary information at the cardholder level. Through endpoint Natural person information registration information for natural person is sent to the platform (eg. name, documents, address).

  • BIS ( Business Information Summary ): summary of non-monetary commercial information about a company. Through endpoint Legal person information, the registration information for legal person (eg. corporate name, CNPJ, address) is sent to the platform.

  • AIS ( Account Information Summary ): summary of non-monetary information at the account level. Through endpoint Account information the account information of the cardholder is sent to the platform (eg. account number, opening date).

  • PIS (PAN - Primary Account Number ): summary of non-monetary information at the level of the primary account number (PAN / PIS), which is used only in Falcon Card . Through endpoint Card information registration information for cards issued to the cardholder is sent to the platform (eg. date of issue, limit, expiration).

  • LEDGER: through the endpoint Confirmation of operations account input and output information is sent to the platform (eg. C / C, payment account, digital account).

  • FRD ( Fraud Dispositions ): contain information about status fraud, and associated details for an entity, such as account, person / cardholder. Through endpoint Reported fraud data, the transaction information contested by the cardholders and which were closed as fraudulent is sent to the platform.

  • HOTLIST ( Hotlist Update Data ): contain requests to add, delete or update table entries hotlist. Through the endpoints Submit a hotlist information entry and Send several entries of hotlist information, the information for registration of lists in the application is sent to the platform (eg. blacklist , whitelist , VIP customers, travel notice).

Layouts for updates

Endpoints for non-monetary changes that convey information about dozens of different types of events.

  • NMON CIS ( No Monetary Customer Information Summary ): summary of cardholder information, is responsible for updating non-monetary information at the level of the natural person. Through endpoint Update natural person data, updates to the registration information of natural person cardholders are sent to the platform (eg. name, documents, address).

  • NMON BIS ( No Monetary Business Information Summary ): summary of commercial information, is responsible for updating non-monetary information about a company. Through endpoint Update legal person data, updates to the registration information of corporate cardholders are sent to the platform (eg. corporate name, CNPJ, address).

  • NMON AIS ( No Monetary Account Information Summary ): summary of account information, is responsible for updating non-monetary information at the account level. Through endpoint Update account data, updates to the account information of the cardholder are sent to the platform (eg. account number, opening date).

  • NMON PIS (No Monetary PAN - Primary Account Number): responsible for updating non-monetary information at the level of the primary account number (PAN). Through endpoint Update card data updates to the registration information of cards issued to the cardholder are sent to the platform (eg. date of issue, limit, expiration).

Transactionals layouts

Falcon® has transactionals layouts that are needed for the operation of the application, with the sending of transactions in real time, performing integrations through the following endpoints:

  • CRTRAN: through endpoint Credit transactions transaction card information is sent to the platform credit (ISO 8583 standard).

  • DBTRAN: through endpoint Debit transactions transaction card information is sent to the platform debit (ISO 8583 standard).

  • RBTRAN: through endpoint Retail Banking transactions transactional information is sent to the platform Retail Banking ( cash in and cash out in the account of the holder. Eg. TED, DOC, P2P, PIX, payments).



Setup of Falcon® (Card and Banking)

The issuer that is willing to use Falcon® must align with its commercial account manager about the interest in enabling it to provide the setup, where all the necessary parameterizations and tests will be done.

The settings made on the setup involve:

1- Creation of the Issuer ID in Dock's base;
2- Creation of pipelinespipelines - Instructional segmentation is a hardware technique that allows the CPU to search for one or more instructions in addition to the next one to be executed. loads of demographic data;
3- Creation of token on the Pier and link to the fraud prevention APIAPI - Application Programming Interface are instructions and programming standards for accessing an application or software. (API and CAMCAM - Computer Aided Manufacturing is the use of computer-controlled software and machinery to automate a manufacturing process.);
4- Creation of token of the issuer in the fraud prevention API;
5- Creation of tenant at the ADAD - Active Directory is a database and set of services that connect users to the network resources they need to do their jobs. The database (or directory) contains critical information about your environment, including which users and computers exist and who is allowed to do what.;
6- Creation of tenant on Falcon®;
7- Creation of VPNVPN - Virtual Private Network, is a private communications network built on a public communications network. (if not);
8- Release of firewallfirewall - Firewall is a security solution based on hardware or software (most common) that, based on a set of rules or instructions, analyzes network traffic to determine which data transmission or reception operations can be performed. to access the tool;
9- Creation of users to access the platform;
10- Definition of rules with issuer;
11- Activation of the parameter to start receiving transactions on Falcon®;
12- Activation of the parameter to consider the Falcon® response in the authorizer.


Did this page help you?