Developer Programs

Learn

Docs

Data Broker Pipeline Efforts

Data Broker Pipeline Efforts

Account Services

Customers could use the data broker data set of account services to access data related to Accounts, Transactions, Available Balance, Holds, Stop Payments, Stop Payment Settings and Products available within digital banking platform.

Banno Usage Data

Get a clear picture of customer behavior by tracking their movements through your digital banking platform. This dataset includes analytics from all your Banno apps including user paths, product adoption, and feature usage, and can be used for a wide variety of purposes such as informing product decisions, building marketing campaigns, understanding usage trends, and more.

DIGITAL History Events (Banno)

Dive into the details of your customer’s activity from a system standpoint. This dataset encompasses details about various events such as user login attempts, customer devices, high-risk events, and more. Notably, this dataset excludes application-specific navigation and transaction data.

Exception Item Processing

Gain comprehensive insights into your institution’s Exception Item Processing with the EIP dataset. This dataset includes detailed records of exception items, associated fees, and associated notes. Supplementary information from ACH transactions, core Account Details, and NSF occurrences provide a holistic view of the decision making surrounding the exception items. Utilize this dataset to streamline exception handling, monitor transaction anomalies, and enhance compliance reporting.

Finicity

Allow your customers to use your digital banking platform as a central location for all their external fintech data. Finicity—a MasterCard company focused on financial data sharing, security, and standards—aggregates financial information from external applications to give both you and your users a full view of their financial picture.

Payments-Smartsight

The goal of this pipeline is to make the Payments dataset available in Google Big Query where it can be queried using the SQL interface for business purposes and to drive downstream business processes.

The Payments dataset is comprised of a single data file for each Jack Henry Payments solution. The data files are in PARQUET format, sourced from an Amazon S3 bucket on a monthly cadence. Today, the file must be copied to a Google Cloud Storage bucket, imported into Big Query, and exposed as a native table in Big Query to provide a SQL interface for the data.

Topics in this section

Last updated Tue Nov 5 2024