New Solutions

Introduction

A common question from new Fintechs joining the Fintech Integration Network (FIN) is:

“How quickly can we implement our product into a financial institution’s environment?”

To provide clarity and assist with project planning, we’ve broken the implementation process into distinct phases. These phases outline the steps required for successful integration and help set realistic timelines.

Pre Development Phases

The following phases must be completed to successfully onboard into the FIN program and gain access to Jack Henry (JH) development environments.

Phase 1 - Joining the FIN

Before a Fintech can begin using our Enterprise Integration software, they must first join the FIN. To start this process, submit a FIN Interest Form.

Phase 2 - Contracts, Paperwork, and Fees

To become part of the FIN, Fintechs must complete all required contracts, paperwork, and associated fees. The duration of this phase varies based on the turnaround time for completing FIN documentation and payment to JH.

As part of this process, the Fintech will need to provide a PEM public key or JWKS URL.

Development Phases

Phase 3 - Development Environment Access

Once the previous phases are complete, the Fintech will be granted access to our development institution sandbox, commonly referred to as the DMZ.These shared institutions are used by all Fintechs in the FIN program to complete initial development efforts.

Phase 4 - Solution Development

During this time the Fintech develops their solution against the JH SOAP APIs.

The duration of this phase can vary significantly based on two key factors:

• Product complexity
• Resources allocated by the Fintech

These variables influence how quickly development and integration tasks can be completed.

Phase 5 - Integration Readiness Check

After the development efforts are complete, a Fintech’s product must pass an Integration Readiness Check (IRC) before being allowed to implement at a Financial Institution. Complete details on this requirement can be found on our Fintech Requirements and Readiness page. Jack Henry limits your integration’s API authorization in live customer environments to only the APIs you used during the Integration Readiness Check. For any future enhancements that require additional APIs or support for a new product (like CIF20/20 or Core Director), you must complete another Integration Readiness Check. This ensures the new functionality works correctly within the Jack Henry sandbox.

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 6 - JH Internal Solution Documentation

After the IRC is completed, the Developer Relations team will collect details about the product and designated Fintech contacts who will receive credentials. This process ensures all information is properly documented internally, enabling our operational teams to clearly 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 7 - 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 8 and 9.

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

Phase 8 - FI Setup of External Application

Once the FI has been informed that the Fintech has completed development work and readiness checks (Phase 7), 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 9 - 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 8)
  • Any FI specific special instructions

• Product: JX_JXCHANGE

• Problem Type: Implementations