FAQ

Frequently Asked Questions

Does Jack Henry plan to retire jXchange SOAP APIs?

No. This is intended to make the jXchange SOAP APIs more secure.

Are there functional or structural changes to the APIs themselves?

No. Jack Henry is committed to continued support of backwards compatibility with our APIs. This change does not affect that initiative.

Will all Jack Henry Hosted APIs require this new security model?

All APIs accessible over the internet will implement the new security model.

Does this change impact SymXchange APIs?

This update only applies to the Hosted jXchange environments so this excludes all SymXchange instances.

Will Jack Henry provision production credentials?

Institutions will be responsible for provisioning credentials, though there may be exceptions. Configurations on the jXchange product will still require a Jack Henry work effort regardless if an institution or Jack Henry provisions the API credentials.

Does this impact my on-premise (jXchange hosted within an institution’s network) jXchange implementation?

No. This only applies to Jack Henry hosted JX environments

If I have already provided my public and private key to an institution, do I need an additional client?

If you’re currently using the Digital Toolkit Admin API, you may use the existing client configuration to access jXchange API’s, but additional setup is still needed on the jXchange side to authorize that client to the jXchange operations.

Are third parties required to migrate all their bank partners at once?

No. Third party consumers can migrate each bank partner individually, using the old and new security models concurrently before the deadlines.

We currently pass in the wsse security information (username and password) within the SOAP ENV header. Will consumers still need to provide that information within the request?

No. The wsse:security section of the older SOAP APIs, i.e. usernames and passwords, will no longer be used with the OAuth security model. Please remove those from your request. More information may be obtained on our Getting Started Development Using SOAP page.