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_pledge_cdc

Pipelined Data Sets > Symitar > ssdb_pledge_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
pledgekeyInternal use only; SSDB fieldNULLABLEINTEGER
deleteidThis field stores a soft delete flag where 0=not deleted, 1=deletedNULLABLEINTEGER
accountkeyInternal use only; SSDB fieldNULLABLEINTEGER
sortrankInternal use only; SSDB fieldNULLABLEINTEGER
typeThis field identifies the purpose of the Pledge recordNULLABLEINTEGER
accountnumberThis field identifies the account pledging security for a loan. This field is not used if the Pledge Type field is set to (5) CollateralNULLABLESTRING
idThis optional field identifies a share or portfolio pledging security for a loan. This field is not used if the Pledge Type is (5) CollateralNULLABLESTRING
collateralcodeThis field contains a user-defined code used to identify the collateral pledged for a loan. You can use this field to categorize types of collateral for reports and displays. This field is not used if the Pledge Type is (5) CollateralNULLABLEINTEGER
percentUse this field to specify the percentage of a loan secured by a pledge; alternatively, you can use the Pledge Amount field to specify a dollar amount secured by a pledgeNULLABLEINTEGER
amountUse this field to specify the dollar amount of a loan secured by a pledge; alternatively, you can use the Pledge Rate field to specify the percentage secured by a pledgeNULLABLEINTEGER
locatorThe system stores a unique number within each member account in this field that can be used as a unique identification of this recordNULLABLEINTEGER
collateralnumberThis field references the Collateral record associated with this Account Pledge recordNULLABLESTRING
priorityThis field indicates the priority of the collateral associated with this Pledge record. This field is used only if the Pledge Type is set to (5) CollateralNULLABLEINTEGER
effectivedateThis field stores the creation date of the Pledge record or, if entered manually, the date this Pledge record can be usedNULLABLEDATE
expirationdateThis field stores the date this Pledge record should expireNULLABLEDATE
recordchangedateThe system stores the system date in this field when you create, change, or save the Pledge recordNULLABLEDATE

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