Notices
Starting November 16, 2026, the Federal Reserve (FED) will eliminate the ability to populate postal addresses as purely unstructured text across all message types, parties, and agents.
Key Mandate Changes
- Removal of 3-Line Free-Format Addresses: The legacy format of 3 free-format address lines will no longer be supported.
- Mandatory Address Elements: Town Name (TownName) and Country (Ctry) are now mandatory when an address is provided.
- Hybrid Address Model: Addresses can be populated as a hybrid postal address, which allows a maximum combination of up to 2 free-format lines alongside structured address elements. Purely unstructured 3-line addresses will fail validation.
More information may be found on our ISO Hybrid Address page.
This was successfully completed on 7/31/2026.
We are migrating all jXchange REST‑Legacy translation services from Mulesoft to a new, high‑performance architecture running in Google Cloud Platform (GCP). This means that updates will be required to the authentication method, API endpoints and environmental variables.
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.
More information may be found:
Beginning on May 1st, 2025, JH is enhancing jXchange SOAP API security by transitioning to OAuth 2.0 instead of username and password pair. This change ensures alignment with modern cloud security standards.
We have created a landing page with valuable information, dates, questions, and videos to help a consumer prepare for this rollout. Please visit: SOAP Authentication Update
Topics in this section
- Have a how-to question? Seeing a weird error? Get help on StackOverflow.
- Register for the Developer Office Hours where we answer technical Q&A from the audience.