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
Authentication Framework
Map customer identities to your existing system IDs.
Banno SDK
Create exceptional banking experiences.
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.
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.

ssdb_wire_receiver_fi_info_cdc

Pipelined Data Sets > Symitar > ssdb_wire_receiver_fi_info_cdc

Column nameDescriptionModeTypeLength
institutionidThis field stores the JH Platform institution identifierREQUIREDSTRING
sourceeventtimeThe timestamp of the change event from the source system (e.g., Debezium's ts_ms field).NULLABLEINTEGER
sourceeventdateThe UTC date of the change event, derived from sourceeventtime.NULLABLEDATE
operationThe type of operation that caused the change event (e.g., 'c' for create/insert, 'u' for update, 'd' for delete, 'r' for read). This corresponds to Debezium's 'op' field.NULLABLESTRING
wirereceiverfiinfokeyInternal use only; SSDB fieldNULLABLEINTEGER
deleteidThis field stores a soft delete flag where 0=not deleted, 1=deletedNULLABLEINTEGER
wirekeyInternal use only; SSDB fieldNULLABLEINTEGER
sortrankInternal use only; SSDB fieldNULLABLEINTEGER
text_1These fields contain information intended specifically for the financial institution receiving a wireNULLABLESTRING
text_2These fields contain information intended specifically for the financial institution receiving a wireNULLABLESTRING
text_3These fields contain information intended specifically for the financial institution receiving a wireNULLABLESTRING
text_4These fields contain information intended specifically for the financial institution receiving a wireNULLABLESTRING
text_5These fields contain information intended specifically for the financial institution receiving a wireNULLABLESTRING
text_6These fields contain information intended specifically for the financial institution receiving a wireNULLABLESTRING
text_7These fields contain information intended specifically for the financial institution receiving a wireNULLABLESTRING
text_8These fields contain information intended specifically for the financial institution receiving a wireNULLABLESTRING
text_9These fields contain information intended specifically for the financial institution receiving a wireNULLABLESTRING
text_10These fields contain information intended specifically for the financial institution receiving a wireNULLABLESTRING
text_11These fields contain information intended specifically for the financial institution receiving a wireNULLABLESTRING
text_12These fields contain information intended specifically for the financial institution receiving a wireNULLABLESTRING
text_13These fields contain information intended specifically for the financial institution receiving a wireNULLABLESTRING
text_14These fields contain information intended specifically for the financial institution receiving a wireNULLABLESTRING
text_15These fields contain information intended specifically for the financial institution receiving a wireNULLABLESTRING
text_16These fields contain information intended specifically for the financial institution receiving a wireNULLABLESTRING
text_17These fields contain information intended specifically for the financial institution receiving a wireNULLABLESTRING
text_18These fields contain information intended specifically for the financial institution receiving a wireNULLABLESTRING
text_19These fields contain information intended specifically for the financial institution receiving a wireNULLABLESTRING
text_20These fields contain information intended specifically for the financial institution receiving a wireNULLABLESTRING
locatorThis field value in each record is unique for each member accountNULLABLEINTEGER

Have a Question?
  • Have a how-to question? Seeing a weird error? Get help on our collaborative Discourse page.
  • Register for the Developer Office Hours where we answer technical Q&A, in real time, from the audience.
Did this page help you?
Last updated Tue Sep 15 2026