RS Intelliedge Blog

Shared authority between bank and branch

Most fraud and risk management products are built with a single-layer enterprise in mind. For example, it could be for all wire transfers for a bank, or for all payments made through the mobile app of a bank, etc. However, a bank is not a flat organization. It can have different branches across the country or even outside of the country. The branches may be catering to a specific type of demographics, businesses, etc. They aim to provide a holistic solution. Hence, the rule parameter values may need to be different for each of these branches while the rule structure may remain the same for all the branches.

One of the smart ways to cater to such needs is having a federated architecture for the rules of the fraud and risk management product that is deployed, while the workflow systems, portals, reporting systems, identity, and security management are done in a syndicated manner.

This lets the bank have a set of global rules and then have overrides on the rules for some of its branches; while the different workflows, case/alert management portals, analytic reporting, etc. are maintained centrally. Rather than building a complete set of new rules for every branch, building a “flavour” of the same rule but with a slight variation of the parameter values in the rule that works for the branch helps in better management of the rules.

RS IntelliEdge™ is built with a core design principle that supports federated architecture for rules and syndicated architecture for the rest of the functionalities. Thus, it can have a relatively small set of distinct rules and a very large set of override rules specific to each of the branches.

Read more on this –



Leave a Reply

Your email address will not be published. Required fields are marked *

Comment moderation is enabled. Your comment may take some time to appear.