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

jXchange REST-Legacy Migration

jXchange REST-Legacy Migration

Overview

We are migrating all jXchange REST‑Legacy translation services from Mulesoft to a new, high‑performance architecture running in Google Cloud Platform (GCP).

Notable Items

  • Items to Update: This transition requires updates to both the authentication method (moving from Client Id/Secret to OAuth 2.0/Signed JWT), environmental variables and the API endpoints.

  • API Formatting: API formatting in JSON DOES NOT change with this migration. No need to modify the body of the API calls.

Migration Timeline

Work on your Jack Henry DMZ Sandbox institution should begin immediately.

All existing jXchange REST‑Legacy clients are expected to migrate no later than July 31, 2026.

Performing The Migration

Fintech Integration Phases
The following steps are simplified from our documented Fintech Integration Phases:New Solution. Please refer to that page for more detailed information about the phases of implementing within a bank environment.

Step 1: Development using DMZ Bank 100

To begin testing in the DMZ Bank 100 environment, complete the following steps:

API Formatting
This change does not affect the formatting of the APIs, only the access method.

Step 2: Production Readiness (Fintechs Only)

Once you complete and validate your testing:

Have a Question?
Did this page help you?
Last updated Tue Mar 31 2026