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

Memo Posted Transactions

Enterprise SOAP API > Tutorials > Transaction > Memo Posted Transactions

Standard behavior

In the JH cores (SilverLake, CIF 2020 and Core Director) all transactions are handed as memo posted until the end of day (EOD) processing occurs. This is not considered a real-time process, though the transaction is recorded in the temporary tables and can affect the available balance of an account depending on how an FI decides to calculate available balance.

Transactions that are in the memo posted state may be modified with the TrnMod API. This means that during the time-period from when the TrnAdd request is received until the EOD processing occurs the transaction can be modified or cancelled.

Modification After Hard Posting
Once the transaction is hard posted after EOD processing the only method to modify the transaction is to perform a second TrnAdd to reverse the transaction.

MemoPostOnly Behavior

Within the TrnAdd API there is an element named MemoPostOnly. Passing in a value of “Y” within the MemoPostOnly element allows the consumer to notate that the transaction is only to be considered a memo posted transaction and tells the system to not hard post the transaction at the EOD process. Transactions that are marked as MemoPostOnly, will disappear from the systems tables and not post when the EOD processing occurs.

Remove MemoPostOnly Flag
To remove the MemoPostOnly flag to allow it to hard post at the end of the day, a TrnMod API with the MemoPostOnly element changed to a value of “N” and must be received by the system before EOD processing occurs.

MemoPostHldOvr Behavior

Note
MemoPostOnly is only supported by SilverLake and CIF2020.

In some use cases, there may be a need to hold a memo posted transaction over to the next day due to a waiting period or other action. This can be accomplished by using the MemoPostHldOvr element in conjunction with the MemoPostOnly element. Passing in MemoPostOnly and MemoPostHldOvr elements with a value of “Y” will tell the system to mark the transaction as a memo posted item and to retain it during the next EOD processing.

The MemoPostHldOvr flag is only activated for one EOD processing. After the transaction has been carried over to the next processing period, the transaction will be marked as a MemoPostOnly transaction and will be discarded at the next EOD processing.

Multiple MemoPostHldOvr
If a transaction needs to be held over a second time, a TrnMod API will need to be used passing the TrnRcptId of the held over transaction, along with MemoPostHldOvr element with a value of “Y”. This can be performed two times before the system will no longer accept the MemoPostHldOver request.

Transaction Flow

SilverLake and CIF2020

Transaction flow diagram

Core Director

Transaction flow diagram
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 Mon Oct 21 2024