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.
Payments Orchestrator
Embed multiple payment rails and virtual accounts into your solution.
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.

Login

Jack Henry Identity > UX Flows > Login

When a user needs to login to a product that is integrated with Jack Henry Identity, they begin by navigating to that product’s URL.

Imagine a user who’s already been invited to the financial institution through Users & Groups, and has accepted the invitation to finalize their profile. Now they’re ready to authenticate and begin using your amazing product!

  1. User navigates to Your Product URL.
  2. User supplies their email address (username).
  3. Your Product initiates the OAuth redirect to https://login.jackhenry.com/login using the Institution Zero institutionId.
  4. User authenticates through Jack Henry Identity.
  5. Jack Henry Identity redirects the user back to Your Product URL, and the access token is for Institution Zero’s institutionId.
  6. Your Product presents the user with a method of selecting which institution they’re trying to access (or applies logic to make a default selection).
  7. Your Product initiates the OAuth redirect to https://login.jackhenry.com/login again using the selected institutionId.
  8. User is already authenticated and is redirected back to Your Product’s URL, and the access token is for the selected institutionId.
Note about Step 4

Each user’s authentication flow will vary depending on factors including:

  • whether their previous session is still active,
  • whether they’re currently enrolled in 2FA (and which methods), and
  • whether or not they utilize the “remember me” feature.

Create a login page for your product that includes a place for users to key in their email address (username) before being redirected to the Jack Henry Identity login page. Then begin the OAuth flow and include a login_hint=username query parameter (which your Backend for Frontend will need to support.)

This helps prompt users to bookmark your product’s URL rather than https://login.jackhenry.com. This matters because if they begin the login flow on the Jack Henry Identity page they will get to Account Settings pages for profile and security rather than your product.

The query parameter will pre-fill the value the user keyed as the email address (username) into the correct field on the Jack Henry Identity login screen so they don’t have to re-enter it.

Example

Imagine a user navigates to your product’s login page and keys in their email address (i.e. username) of rfredericksen+777@jackhenry.com. Your product would then initiate the OAuth flow, including the login_hint=username query parameter.

The user is taken to the Jack Henry Identity login page, with their email address pre-filled in.

Login Username Filled

The user selects Continue, and next sees the password entry field.

Login Password

If the user is already enrolled with one or more 2-factor authentication methods, they’ll be required to complete 2FA unless they previously selected the checkbox “Dont ask for codes again while using this browswer.”

2FA Remember Me

If the user is not enrolled in 2FA (e.g. they got a new phone number and had to remove their old number), they’ll be required to enroll.

2FA Start

The supported methods include passkeys, FIDO security keys, authenticator apps, SMS, and phone call.

Choose Method

After the user has successfully enrolled in 2FA, they’ll see the confirmation screen.

2FA Done

After selecting “Done” the user will be redirected back to your product’s URL.

Have a Question?
Did this page help you?
Last updated Fri Apr 3 2026