EES Integration Phases

Introduction

A commonly asked question by new Fintechs to the Fintech Integration Network (FIN) is “How quickly can we implement our product into a financial institution’s environment?”. We have broken this process into phases for better understanding and project planning.

Phase 1 - Joining the FIN

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

Phase 2 - Paperwork

To become part of the FIN there will be contracts, paperwork and fees to be completed. The amount of time during this phase varies depending on a the turnaround of the FIN paperwork and payment to JH by the Fintech.

Phase 3 - Development and Testing

Once the previous steps are complete, the Fintech development team should review the EES Getting Started page and perform the Project Steps noted.

The Fintech will notify the Developer Relations team once they are ready to test their listener and its processes by submitting an Enterprise Event System Setup Request.

The amount of time during this phase varies substantially, depending on Fintech’s product complexity, and Fintech resources allocated and any testing complications observed.

Phase 4 - Final solution documentation

Once successful communications are noted, the Developer Relations team will request information regarding the product and Fintech contacts to receive credentials/information from the production support teams. This ensures that we have everything documented internally for our operational teams to understand the product’s integration requirements.

Phase 5 - Implementations at Financial Institutions

Once 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 with 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 Valid Consumer Name (ValidConsmName)
  • Fintech Valid Consumer Product (ValidConsmProd)
  • Financial Institution Environment(s) to be used for the implementation
  • Any FI specific special instructions

• Product: JX_JXCHANGE

• Problem Type: Implementations

This phase is repeated for each new financial institution that wishes to implement the Fintech’s product.