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

Validate Transaction Before Posting

Enterprise SOAP API > Tutorials > Transaction > Validate Transaction Before Posting

The bank or other transaction performing process needs to validate a transaction’s data before actually posting the transaction to an account. The TrnAddValidate operation will allow the requestor to perform the transaction to the system and get a response to determine if the transaction will be successful. When this operation is used, no posting to the account ledger occurs and no direct action against the account is taken.

Steps

  1. The requestor provides the information about the requested transaction. (i.e. Account number, type of account, transaction amount, type of transaction)
  2. The performing application collects the information from the request and parses it into the TrnAddValidate operation passing in the correct TranCode, ProdCode and applicable information.
  3. The banking core responds with relevant information about the TrnAdd action without actually updating the account.

*TranCode and ProdCode values can be obtained using the ParmValSrch operation.

Referenced and Associated Operations

Operation NameDescriptionXSD/WSDL Container
TrnAddCreate a new monetary transaction recordTransaction
ParmValSrchRetrieve default canonical values for a parameterCustomer
TrnAddValidateValidate a transaction prior to creationCustomer
TrnModModify a previously entered transactionTransaction
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 Thu Jul 14 2022