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
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 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.
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.
Full List of APIs
Begin working with Jack Henry's public APIs to build financial applications today.
jXchange REST-Legacy Migration announced. Deadline for migration is July 31, 2026.
More info

Developer Resources

API by Reference > Teller System > Teller Currency Transaction Addition > Developer Resources

Details

SoapActionhttp://jackhenry.com/ws/TellerCurrTrnAdd
Input NameTellerCurrTrnAdd
Output NameTellerCurrTrnAddResponse
Input Namespacehttp://jackhenry.com/jxchange/TPG/2008
Group NameTeller
ContainerTPG_TellerMaster.xsd

XML Examples

TellerCurrTrnAdd Request

XML
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <SOAP-ENV:Header>
  </SOAP-ENV:Header>
  <SOAP-ENV:Body>
    <TellerCurrTrnAdd xmlns="http://jackhenry.com/jxchange/TPG/2008">
      <MsgRqHdr>
        <jXchangeHdr>
          <JxVer></JxVer>
          <AuditUsrId>{Insert}</AuditUsrId>
          <AuditWsId>{Insert}</AuditWsId>
          <AuthenUsrId></AuthenUsrId>
          <ConsumerName></ConsumerName>
          <ConsumerProd></ConsumerProd>
          <Ver_1/>
          <jXLogTrackingId>{Insert}</jXLogTrackingId>
          <Ver_2/>
          <InstRtId>011001276</InstRtId>
          <InstEnv>TEST</InstEnv>
          <Ver_3/>
          <BusCorrelId></BusCorrelId>
          <Ver_4/>
          <WorkflowCorrelId></WorkflowCorrelId>
          <Ver_5/>
          <ValidConsmName>{Insert}</ValidConsmName>
          <ValidConsmProd>{Insert}</ValidConsmProd>
          <Ver_6/>
        </jXchangeHdr>
        <Ver_1/>
        <Ver_2/>
        <Ver_3/>
      </MsgRqHdr>
      <ErrOvrRdInfoArray>
        <ErrOvrRd>
          <ErrCode></ErrCode>
          <Ver_1/>
        </ErrOvrRd>
      </ErrOvrRdInfoArray>
      <!-- Id from TellerTrnAdd response -->
      <TrnRcptId>0010000099006120181224181328</TrnRcptId>
      <CTRRptDt>2018-12-24</CTRRptDt>
      <CurrTrnInfo>
        <CurrTrnAcctArray>
          <CurrTrnAcctDetail>
            <AcctId>146118</AcctId>
            <AcctType>S</AcctType>
            <CashIn>9000</CashIn>
            <CashOut>0.0</CashOut>
            <CTRCatType>DepWthdwl</CTRCatType>
            <Custom></Custom>
            <Ver_1/>
          </CurrTrnAcctDetail>
        </CurrTrnAcctArray>
        <Custom></Custom>
        <Ver_1/>
      </CurrTrnInfo>
      <Custom></Custom>
      <Ver_1/>
    </TellerCurrTrnAdd>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Question: Currently we report all the cash transactions to core after we have a successful response to TrnAdd requests from Silverlake Core. Is this correct?

Answer: If you are using the TellerCurrTrnAdd and TrnAdd you can run them in either order. They will not affect each other.

Question: In a fulfillment failure scenario (e.g., cash fails to dispense despite a successful TrnAdd and TellerCurrTrnAdd), we initiate a transaction reversal with Silverlake. Should a corresponding reversal of TellerCurrTrnAdd also be performed within the Vertex core to maintain synchronization?

Answer: To resolve the transaction, you may either execute a TrnMod/TellerCurrTrnMod to delete the entry or submit a reversing TrnAdd/TellerCurrTrnAdd. The appropriate method depends on specific FinCEN regulatory requirements; therefore, the final determination should be guided by the Financial Institution’s Compliance Department.

Question: If we need to perform reversal with Vertex Core which API should be used?

Answer: Use either TellerCurrTrnMod or TellerCurrTrnAdd to create a reversal or delete the entry, depending on the current processing date. Selection of the appropriate method may be governed by FinCEN regulatory requirements; therefore, final implementation should be reviewed and approved by the Financial Institution’s Compliance Department.

TellerCurrTrnAdd FAQ

Question: Our response for TellerCurrTrnAdd gives a fail. What are we doing wrong?

XML
<jXchangeHdr>
  <JxVer>R2014.0.08</JxVer>
  <AuditUsrId>myUserId</AuditUsrId>
  <AuditWsId />
  <AuthenUsrId />
  <ConsumerName></ConsumerName>
  <ConsumerProd />
  <Ver_1 />
  <jXLogTrackingId>1a6a5b42-860e-40fa-9e53-a7f2f5b4fe38</jXLogTrackingId>
  <Ver_2 />
  <InstRtId>011001276</InstRtId>
  <InstEnv>TEST</InstEnv>
  <Ver_3 />
  <BusCorrelId>4e18c0fa-14fe-4e08-9449-ef8cd5f94dd1</BusCorrelId>
  <Ver_4 />
  <WorkflowCorrelId />
  <Ver_5 />
  <ValidConsmName>{removed}</ValidConsmName>
  <ValidConsmProd>{removed}</ValidConsmProd>
  <Ver_6 />
</jXchangeHdr>

Answer: We noticed that in the TellerCurrTrnAdd request you are not passing in valid AuditUsrId/AuditWsId values required by the Teller services.

Have a Question?
Did this page help you?
Last updated Wed Mar 4 2026