Fintech 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.

Pre Development Phases

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 Jack Henry (JH) by the Fintech.

As part of the paperwork and FIN payments process, a Fintech will provide JH the name(s) of the REST providers they wish to integrate into their solution.

Development Phases

Phase 3 - Development

Once the previous phase is completed, access will be granted to the Fintech into our development sandbox. This sandbox is used by all Fintechs in the FIN to complete their initial development efforts.

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

Phase 4 - Integration Readiness Check

After the development efforts are complete, a Fintech’s product must pass a Integration Readiness Check (IRC) before being allowed to implement at a Financial Institution. Complete details on this requirement can be found on our Fintech jXchange REST Requirements and Readiness page.

If you have completed development and are ready to take the IRC, please fill out the Integration Readiness Check Request Form and someone from the Developer Relations team will provide next steps.

Phase 5 - Final solution documentation

At the conclusion of the IRC, the Developer Relations team will request information regarding the product and Fintech contacts to receive credentials. This ensures that we have everything documented internally for our operational teams to understand the product’s integration requirements.

Implementation Phases

The following phases are designed to ensure clear communication between the Fintech and the Financial Institution (FI) during the implementation of the Fintech solution within the FI’s environment(s).

Note: These steps must be repeated for each new FI that the Fintech integrates with.

Phase 6 - Preparing Your FI for Integration

Once all development phases are complete, the Fintech should notify their Financial Institution (FI) contact that they are ready to begin FI implementation.

The FI will need to following information from the Fintech to be able to complete phases 7 and 8.

• Fintech Name
• Fintech Valid Consumer Name (ValidConsmName)
• Fintech Valid Consumer Product (ValidConsmProd)
• OAuth Scopes (provided with your DMZ development credentials)
• JWKS URL

Phase 7 - FI Setup of External Application

Once the FI has been informed (Phase 6) that the Fintech has completed development work and readiness checks, the FI will need to perform the steps to setup an external application in their Jack Henry Identity Users & Groups screens. Instructions for this process may be found:

Phase 8 - Request API Access

Once the external application has been established for the Fintech within Jack Henry Identity, the FI must submit a For Clients Portal case requesting Fintech API access within Service Gateway. The case should include the following information:

• 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 Product Name (ValidConsmProd)
  • Financial Institution Environment(s) to be used for the implementation
  • Client Id created for the Fintech in Jack Henry Identity (Phase 7)
  • Associated User created for the Fintech in Jack Henry Identity (Phase 7)
  • Any FI specific special instructions

• Product: JX_JXCHANGE

• Problem Type: Implementations