ODI Integration Phases

Introduction

One of the most common questions new Fintechs ask the Fintech Integration Network (FIN) is, “How quickly can we implement our product in a financial institution’s environment?” This guide breaks the process into phases to make planning and timelines easier to understand.

Phase 1 - Joining the FIN

Before a Fintech is able to begin using our Enterprise Integration software, they will need to join the Fintech Integration Network (FIN). This process may be started by submitting a FIN Interest Form.

Phase 2 - Paperwork

To become part of the FIN, contracts, paperwork, and fees must be completed. The duration of this phase varies depending on the turnaround time for FIN documentation and payment processing by the Fintech.

Phase 3 - Getting Started

Once the previous steps are complete, the Fintech development team should review the ODI Getting Started page and decide what ODI extracts and data parts they wish to consume.

The Fintech will notify the Developer Relations team once they are ready to receive the extracts for development and testing by submitting an Operational Data Integration Interest Form.

The amount of time during this phase varies substantially depending on your product’s data needs and complexity.

Phase 4 - Setup of ODI extracts

Fill out and return the appropriate ODI Element Mapping Spreadsheets to the Developer Relations team. We will configure the chosen items within the DMZ development institutions and request access to retrieve files.

Phase 5 - Development

By this point the Fintech has received multiple rounds of extracts examples from the development and test institutions. Development may occur and changes to the extracts, if any, may be requested until the final selection is determined by the Fintech.

The amount of time spent during this phase can also vary substantially.

Phase 6 - Solution Documentation

Once initial development is complete, you will notify the Developer Relations team that you are ready to move into production. Dev Rel will make a copy of the data template (called a transform), and gather information regarding the product, support contacts, etc., to be published in our internal documentation repository. This ensures that we have everything documented internally for our operational teams to understand the product’s integration requirements.

The Developer Relations team will notify you once the documentation is complete and you are ready to proceed to Phase 7.

Phase 7 - Implementations at Financial Institutions

When the previous steps are completed, the Fintech will need to inform their contact at the financial institution that a For Clients Portal case will need to be created.

Each case will need to contain the following:

• Problem Summary: Request to implement {Fintech’s Name and Fintech’s Product} solution

• Description: Please route this case to the jXchange Implementations team to implement the following

  • Fintech Name
  • Fintech Product Name
  • Financial Institution Environment(s) to be used for the implementation
  • Any FI specific special instructions

• Product: JX_JXCHANGE

• Problem Type: Implementations

Phase 8 - Maintenance and Revision

After the new integration is set up in production, you may find the need to raise a support case. Support cases for any issue in the FI’s environment must be opened by an appropriate contact at the FI.

If you need to add or modify data for an existing install, you can send Developer Relations an updated ODI Element Mapping Spreadsheet, and we will iterate through the process above, starting at Phase 4. The institution(s) will need to open new cases to have the production integration updated.