Core Integrations Overview

core integration is the process of connecting the Narmi platform to the Financial Institutions' (FIs) core banking system ("Core"). A core banking system is a back-end system of record that processes daily banking transactions and posts updates to accounts and other financial records. Narmi's integration layer standardizes how information is processed for all core types. Core type impacts data type needed in conversion files for existing users. 

Cores can be hosted onsite at the FI, offsite at the core provider, or with a third-party IT vendor. Location determines who needs to give Narmi connectivity. Narmi will work with the appropriate party at your FI, core provider, and/or third-party vendor to complete the connectivity process. 

Go to About Core Banking Systems for more details. To learn about other methods of integration, go to Integrations Overview.

Connecting to a Core Banking System

There are three methods to connect to a core:

• Direct connection via public internet (optionally restricted to Narmi's egress IP addresses). 

  • UAT and Production requests can originate from 34.203.54.204 and 44.209.24.210.

• Direct connection via virtual private network (VPN)

• Connection via Enterprise Service Bus (ESB)—such as ModusBox or Mulesoft—that maps Narmi to the core banking system. We are not responsible for this integration and instead define a specification for the financial institution or ESB vendor to implement. For more information, go to Enterprise Service Bus.

During implementation, we will work closely to connect to two instances of your financial institution’s core banking system—a test core and a production core. Once we establish a connection to the core, we gather additional configuration information to complete the implementation. 

What Is Needed to Connect?

Please note that the standard information listed below will be required for every core integration, regardless of the core provider. However, every core is different, and there are information and data fields specific to each core that are required to connect. At the start of the implementation, Narmi will share a "Core Connectivity Workbook" for your institution to complete. This workbook contains information that is specific to your core and your institution. This information will enable Narmi to connect to your core provider.  

Narmi has existing integrations with several core providers. If you use a core that Narmi has not integrated with, Narmi may be able to establish a new integration with your core; however, this depends on many different variables, and the Narmi team would require additional scoping. Regardless of whether or not Narmi has an existing integration with your core provider, you could elect to integrate via an ESB, as no direct integration with the core is performed. 

Standard Information Required for Internet Connectivity 

The following information is required from your institution:

1. Gateway URL for Test core

2. Gateway URL for Production core

3. Port Number(s)

Standard Information Required for VPN Connectivity 

Narmi will generate and send the following to your institution:

1. Public IP Address

2. Narmi Classless Inter-Domain Routing (CIDR) 

3. Shared Secret

Then, your institution sends Narmi the following:

1. VPN Public IP Address

2. Financial institution-specific CIDR

Narmi utilizes Libreswan to create our site-to-site tunnels. We prefer to have two live tunnels to the core if the Primary tunnel is having issues or we need to failover during scheduled maintenance (on either side). We do not currently support automated failover of the DR tunnel.

We will provide the PSK, our Public IPs, and our CIDR after confirming the number of VPNs needed.

If your financial institution will connect via ESB, please visit the ESB section for additional information.

Additional Information to Complete Implementation

Once Narmi establishes connection to the core, there are generally five categories of information needed from your institution to complete the implementation:

1. Core System Info – Unique (or related) to the financial institution's core and Narmi accessing the core

2. Configuration Info – Unique to the financial institution's selected banking features through Narmi 

3. Third-Party Vendor Info – Unique to the financial institution's selected banking features & third-party vendors selected for that feature

4. Banking Product Constructs – Defined by the financial institution's existing products

5. Banking Segment Definitions – Defined by the financial institution's desired segment capabilities. Learn more here.