Developer Programs
Getting Started
Get started working with Jack Henry's developer programs today.
Fintech Integration Network (FIN)
Jack Henry's Integration Program for Fintechs.
Technical Account Manager (TAM)
Get technical integration help from a single point of contact.
Developer Account
Create a developer acccount to access resources that help you integrate with Jack Henry.
Learn
Shared Responsibility
Learn about shared roles and responsibilities of customers and Jack Henry in open banking.
Developer Use Cases
Find a use case that fits your development needs.
Developer Video Gallery
Watch the latest demos, webinars, and more.
Developer Conference
Connect with industry leaders, gain insights from expert speakers, and explore our latest innovations.
Docs
Admin API
Create solutions for an institution's back office support tools.
Authentication Framework
Map customer identities to your existing system IDs.
Consumer API
Access financial data for user accounts, transactions, and more.
Data Hub
Get deeper access to financial institution data.
Digital Core
Modernize with cloud-native core banking technology.
Enterprise Event System
Respond to events in real-time using this powerful pub/sub-based solution.
jXchange - REST API
Translate business information between Jack Henry and 3rd-party apps using a REST-based API.
jXchange - SOAP API
Translate business information between Jack Henry and 3rd-party apps using a SOAP-based API.
Operational Data Integration (ODI)
Get customized queries for bulk data needs.
Payments
Embed check deposits, ACH, bill pay, cards, and real-time payments.
Plugin Framework
Embed the best of the fintech world directly into your user's dashboard.
SymXchange
Query Symitar core member accounts, post transactions, run PowerOn scripts, and more.
Full List of APIs
Begin working with Jack Henry's public APIs to build financial applications today.
jXchange REST-Legacy Migration announced. Deadline for migration is July 31, 2026.
More info

Jack Henry Identity External Application Configuration Guide

Getting Started > Post Development > Jack Henry Identity External Application Configuration Guide

Overview

This guide is designed for API consumers to provide to a financial institution’s back office administrator. It outlines the necessary steps and information required to establish a new external application for service-to-service integration. Completing this process correctly is essential for authorizing your integration with the Jack Henry platform. Feel free to add your specific Fintech name and product name, along with JWKs URL when providing these instructions to customers.

Pre-Requisite

The institution must be onboarded to Jack Henry Identity

Customers who are not currently utilizing Banno or Jack Henry Identity must first complete an onboarding process. This involves opening a case with the jXchange Support team to request Jack Henry Identity onboarding for a new Fintech jXchange integration.

During this request, the customer must provide the email address for the initial administrator. This administrator will have the ability to invite other team members as additional administrators later.

After the Jack Henry Identity onboarding is complete, the customer can then proceed with the remaining configuration steps independently.

Establishing the Associated User

Before creating the external application, the the bank’s back office administrator should establish a dedicated “Associated User” via the Banno Admin Users & Groups section. We recommend the following steps for this:

Create a Service Group

  • Navigate to Groups and create a new group (e.g., “JX OAuth Consumer”). Do not assign any permissions to this group.
Step 1

Create the Placeholder User

  1. Invite a new user using a “dummy” email (e.g., fintechname@yourbank.com).
Associated User Note

This ‘Associated User’ acts as a system account and is used when configuring the external application.

We strongly recommend using a non-existent or administrative (non-employee) email to prevent the service account from being tied to a specific employee’s lifecycle (e.g., the service won’t break if an employee leaves the bank).

  1. Assign this user to the group created in Step 1.
Step 2

External Application Creation Steps

Setup New External Application

  1. The bank’s back office administrator will need to navigate to the external application creation function and provide the following five pieces of information:
FieldRequired Value/SelectionDescription
NameRelevant name for the product being installed (e.g., MyFintech-MyProduct)This is a freeform field used primarily for easy identification within the Jack Henry Identity portal. We recommend a format combining your Fintech name and Product name.
Application TypeService AccountThis is the required type for all service-to-service integrations.
Public key in PEM format or a JWKs URLA valid, internet accessible JWKs URLRecommendation: Always use a JWKs URL. While PEM format is supported, it requires manual updates for every key rotation, which is not recommended.
Associated UserSelect the pre-established userThis must be the user account created in the pre-requisite steps. This is a dropdown selection.
ScopesFor JX-SOAP use: https://jackhenry.com/jx/service-gateway.write
For JX-REST-Legacy (JX-RL) use: https://jackhenry.com/jx/service-gateway.write and https://jackhenry.com/platform/translations/jx-rl.write		Click the “Add scopes” button, search for jxchange, and select this specific scope value from the pop-up list.
External App 1
  1. Once all fields are populated, the administrator should click Save.

Retrieve Client Id

  1. The newly created external application will appear in the list of external applications.
  2. The administrator must select the new application to view its details.
  3. The system will have generated a unique Client ID. The administrator must retrieve this value.
External App 2
Multiple Environment Setups
If the bank intends to configure the Fintech in multiple environments (e.g., UAT, QA, PROD), the External Application Creation steps must be repeated, as each environment requires a unique Client ID. However, the JWKS/PEM public key may be reused across different External Applications.

jXchange Environment Setup Request

The bank’s back office administrator must submit the following information to Jack Henry by opening a case in the For Clients Portal and assigning it to the jXchange Support team:

  • Summary: jXchange OAuth for FintechName-FintechProductName
  • Description:
    • The generated Client ID for the external application.
    • The Fintech Name (e.g., FintechName).
    • The Product Name (e.g., FintechProductName).
    • Bank Routing ID
    • Bank Environment (PROD, UAT)

Upon receiving the request, the jXchange Support Team will schedule the setup of the bank’s jXchange environment. Any additional steps or requests for information will be managed within the case.

Have a Question?
Did this page help you?
Last updated Fri Dec 19 2025