Reviewing Available Projects
Most projects are transactional data feeds, which are identified with numbers, such as 20 and 25, to indicate corresponding version numbers, 2.0 and 2.5.
Because each type of transaction has its own data feed, you can write rules in the appropriate ruleset. For example, to find fraudulent credit authorizations, write rules in a Credit Authorization-Posting project. To write a debit rule for excessive deposits, write this rule in the Debit Deposit project. Depending on your implementation of Falcon, you will have some but not all of the projects listed below.
 | Note: The Debit 2.4 and Credit 2.4 data feeds share a common Nonmonetary 11 project.
|
| Project Category | Project Definitions and Data Feeds |
|---|---|
| Alerts |
The Block and Reissue data feed includes cards in which a Card Alert Services block and reissue alert has been created. The Suspect Accounts data feed includes alerts for accounts. If your institution has subscribed to these services, you can create rules based on the data. For more information, see
Card Alert.
|
| Authentication | A data feed containing authentication data sent from an authentication service. |
| Credit |
Credit data feeds include:
|
| Crossfeed | A data feed where you can set up rules that are executed on all projects available to you. |
| Debit |
Debit data feeds include:
|
| Demographic Information |
|
| External Message | A data feed originating in a third-party product or system, which contains information about the account, customer or service which may be useful. |
| Ledger | Contains information about a customer's accounts with a financial institution, such as account balances, payments and outstanding loans. |
| Retail Banking |
The Retail Banking Transactions data feed contains information about a payment or deposit. A transaction occurs when funds are moved out of, or into a retail banking account. |
| Tools and Management |
|