Developer Programs
Vendor Integration Program (VIP)
Direct access to Jack Henry's technical integration resources.
Technical Account Manager (TAM)
Get technical integration help from a single point of contact.
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 Broker
Get deeper access to financial institution data.
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 third-party applications using a REST-based API.
jXchange - SOAP API
Translate business information between Jack Henry and third-party applications 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.
Xperience
Modern UI that provides consistent visual integration across Jack Henry products.
Important notification about upcoming changes to the DMZ environment. Please read.
More info

Entity Match Search

Enterprise SOAP API > API by Reference > Fraud Services > Entity Match Search

Entity Match Search

Entity Match Search is a jXchange service designed to allow consumers to submit entity values for verification with government agencies' entity registers.

Message Flow

In jXchange, the Entity Match Search service uses a typical exchange of MType messages to allow consumers to submit entity values for verification with government agencies' entity registers.

Primary Request

The consumer forwards the EntityMatchSrchRq_MType message to the service provider. The message contains the following simple elements:

  • BirthDt
  • BirthDtTolr
  • City
  • Cntry
  • CntryType
  • CustId
  • EntityConfdScore
  • EntityName
  • EntityType
  • PostalCode
  • StateCode
  • StreetAddr1
  • StreetAddr2

Primary Response

The service provider returns the EntityMatchSrchRs_MType message to the consumer. The message contains the following simple elements:

  • BirthDt
  • BirthDtTolr
  • City
  • CntryType
  • CustId
  • EntityConfdScore
  • EntityMatchListType
  • EntityName
  • EntityType
  • PostalCode
  • StateCode
  • StreetAddr1
  • StreetAddr2
  • TrnRcptId
Have a Question?
Have a how-to question? Seeing a weird error? Get help on StackOverflow.
Register for the Digital Toolkit Meetup where we answer technical Q&A from the audience.
Last updated Wed Feb 2 2022