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.
Important Notice. JH Datacenter Change announced
More info

JH Datacenter Change FAQ

JH Datacenter Change > JH Datacenter Change FAQ

3PX Client Questions FAQ (Updated October 2025)

Technical Migration Overview

What is changing with Symitar connectivity?

Jack Henry is migrating resources from the Lenexa, KS and Branson, MO datacenters to Allen, TX. All network devices must be removed from Lenexa and Branson by December 31, 2025. Fintechs must update their connection endpoints to new URLs and may need to adjust firewall rules for new IP addresses.

Is the deadline for Fintechs to change their configurations really December 15th of this year?

Yes, the deadline to make changes is 12/15/2025. We understand this is aggressive and appreciate your help.

Fintech Responsibilities

What exactly do Fintechs need to change

  • Update endpoint URLs.
  • Add host entries for port 443.
  • Complete testing and configuration changes by the deadline.
  • Adjust firewall rules for new IP addresses as needed.

Can Fintechs test the new URLs before the cutover date?

Yes, testing is encouraged. Fintechs should confirm when the new endpoints will be live for testing.

What if a Fintech doesn’t respond or complete the changes?

Jack Henry will notify the credit union so they can follow up with the Fintech directly. Credit unions may be asked to help with Fintech outreach if contacts are missing or Fintechs are unresponsive.

What if a Fintech has a change freeze during the migration window?

Fintechs unable to meet the migration timeline due to change freezes should escalate to Jack Henry leadership for assistance. A list of at-risk Fintechs is maintained for weekly review.

Do these changes need to happen for all mutual customers using this service?

This change impacts credit unions hosted in our Outlink EASE datacenter who have Fintechs that connect to them directly through our EASE 3PX router.

Does the Fintech need to make an integration change to resolve to the new URL names?

The URLs should be publicly resolvable however, if you experience an issue, the Fintech may need to add the URL to their DNS table. The Fintech application should now point to these unique URLs for each of their customers instead of the IP or URL they had been using.

Does the Fintech need to update their network to allow the new URL or is this just for the Jack Henry Credit Unions using the persistent endpoints?

This change isn’t related to the persistent endpoint. Rather, this is a change for where the Fintech should point their application to communicate with our shared customers.

Is the “wild card” certificate information only for the Fintech, or is it a certificate file that the Fintech will have to send on each request?

The certificates are public certs so the Fintech does not have to install any certificates or maintain any certificates with the URL. It is a Digicert externally trusted certificate.

Will the static IP’s be migrated to ease.jackhenry.com automatically, or do Fintechs need to provide that information againIPs will be migrated to this new environment, so the Fintech does not need to provide them again.

IPs will be migrated to this new environment, so the Fintech does not need to provide them again.

Credit Union Concerns

Do credit unions need to take any action?

Generally, no. Jack Henry is contacting Fintechs directly. However, credit unions may need to assist if Fintechs are unresponsive or for testing should the Fintech require that.

How can credit unions confirm which Fintechs were contacted?

A Fintech contact list is being maintained and reconciled. Any instances for which we do not have a Fintech contact may require credit union assistance.

Communication & Coordination

Is there a playbook or guide for Fintechs?

Yes. A playbook with detailed configuration instructions and troubleshooting guidance is attached to Fintech communication emails.

How is Fintech outreach being managed?

The Jack Henry Fintech Management team is contacting each impacted Fintech directly with the required changes and deadlines.

What if a Fintech contact is missing or incorrect?

Jack Henry will contact credit unions to get Fintech details for those unknown or unresponsive.

How do Fintechs get support during migration?

A dedicated support email address will be provided in Fintech communications. Fintechs should use this for migration-related issues to ensure prompt assistance.

Why are there multiple communications about migration?

Jack Henry is consolidating messaging to ensure Fintechs and clients receive clear, unified instructions.

Troubleshooting & Edge Cases

Are all clients affected equally?

No. Some clients use different configurations (e.g., jConnect vs. Fintech 3PX routers), which may affect their exposure to the migration. Each configuration requires different mitigation. Fintechs are receiving communication for each scenario.

What about Fintechs still on SymConnect?

SymConnect exemptions are separate from the SymXchange migration. These paths have different timelines and requirements. Fintechs using SymConnect may be impacted by the Data Center move and are receiving additional communication for the required steps and dependencies.

How is testing coordinated before migration? Fintechs are responsible for testing and coordination with credit unions.

Did this page help you?
Last updated Mon Dec 1 2025