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.

Consumer Table and View Naming Convention

Consumer Connectivity > Consumer Table and View Naming Convention

Consumer Table and View Naming Convention

Table and Views exist to group data in logical relations within a Data Broker dataset.

Table / View Variables

Entity A data entity is an object in a data model. Data is typically designed by breaking items down into smaller parts for data representation of data relationships. For example, a customer may include a list of contacts. Each contact may contain an address.

Data Classification (Optional) Data classification is the process of analyzing structured or unstructured data and organizing it into categories based on file type, contents, or other metadata. This helps groups quickly identify their data.

  • Data Classification examples:

    • fct = Fact data is information about a thing that has happened. It is an immutable event at a specific point in time.

    • cdc = Change data capture indicates this table / view contains all instances of a specific thing and receives all changes to those things.

    • cmd = Command data represents operations that occur against the system. This data is typically found as the request-response pattern, where you have a verb and a statement. Examples might include UpdateUser and UserUpdated.

    • sys - System data are used for internal topics within a single service. They are operational data that does not contain any relevant information outside of the owning system. This data is not meant for public consumption.

    • map - Internal processing table for Data Broker Adapter Service

    • raw - Producer source system raw extract without transformations

    • deref - Producer source system lookup table for dereferencing raw data key values to translated values

Last updated Tue Nov 5 2024