Developer Resources

Enterprise SOAP API > API by Reference > Core Services > Transfer Source Destination Search > Developer Resources

Details

SoapAction	http://jackhenry.com/ws/XferSrcDestSrch
Input Name	XferSrcDestSrch
Output Name	XferSrcDestSrchResponse
Input Namespace	http://jackhenry.com/jxchange/TPG/2008
Group Name	Inquiry
Container	TPG_InquiryMaster.xsd

XML Examples

OperationSummary-XferSrcDestSrch

Operation Summary

Transfer Add (XferAdd) provides the ability to transfer funds between accounts, make a loan payment, schedule a future transaction, create recurring transactions and transfer funds to an account held at another institution using ACH which requires the ACHXferRec complex to be included in the request.

The <XferType> element identifies the type of transfer operation. Canonical values are:

Values	Description
Xfer	Intra-Financial Institution transfer
ACH	Inter-Financial Institution transfer
Fut	Future transfer

It designates whether the transfer is between accounts within the financial institution, between separate institutions, or to be performed in the future.

The <AcctIdFrom> and <AcctIdTo> complexes represent the account id and type of the source and destination accounts intended for the transfer.

If the transfer will be moving funds within the financial institution, then the <XferRec> complex will need to be included. This is the complex that details the transfer.

The <XferSrcType> element indicates the source of the transfer request. Canonical values are:

Values	Description
ATM	ATM
InPerson	Teller
Intnet	Internet
Tele	Telephone

Trancodes are parameter driven and can vary institution to institution. To retrieve the list of possible trancodes from a service provider for a given institution, the Parameter Value Search (ParmValSrch) operation should be called with TranCodeCode for the <ParmName> element value.

The FutXferRec complex provides a method for scheduling a transfer to occur between accounts on a semi-monthly basis by utilizing the following elements:

Element Name	Description
SemiDay1	This is the day of month for first semi-monthly payment.
SemiDay2	This is the day of month for second semi-monthly payment.
FutXferFirstDt	This is the first date to start a future transfer request.
FutXferExpDt	This is the expiration date of the transfer request.
FutXferFreqUnits	The units of frequency for the transfer request.

Transfer Add (XferAdd) also provides the ability to transfer funds to an account held at another institution using ACH. The ACHXferRec complex will need to be included in the request. This complex defines a transfer through an ACH transaction.

The XferAdd response will contain an <RsStat> element indicating the result of the operation, with a value of Success when completed normally or the operation will return an HdrFault if the service provider was unable to complete the transfer. It will also return a value in the <XferKey> element, which will be needed to modify or delete the transfer.

Special Considerations

Depending on the transaction behavior indicated by the trancode, certain transaction requests may result in one or more faults. Faults that are categorized as a Fault can be overridden by specifying them in the <ErrOvrRdInfoArray> complex, while those categorized as an Error cannot.

Transfer Source Destination Search (XferSrcDestSrch) provides consumers with a listing of accounts/drafts/loans that may be on the source and/or destination side of a transfer request. The response includes elements that could be of interest to the consumer in establishing the identity of the accounts/drafts/loans in a transfer relationship.

The XferSrcDestType element provides a filter by passing one of the following canonical values:

Values	Description
Src	Source account that is the source of the funds transfer
Dest	Destination account that is to receive the funds transfer
Both	Both source and destination accounts

The core provider will return all Transfer Source Destination Types (XferSrcDestType) when the element is absent from the request.

Transfer Add Validate (XferAddValidate) allows the validation of the information without the creation of the actual transactions within the provider.

Note: XferAdd does not provide support for either the target or source accounts to be a General Ledger Type. If a GL transaction is required by the use case, the TrnAdd operation will need to be used instead.

XferSrcDestSrchXML

<?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>
    <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
      xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
      <wsse:UsernameToken xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
        <wsse:Username>{Insert}</wsse:Username>
        <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">{Insert}</wsse:Password>
        <wsu:Created xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">2018-11-28T21:14:39Z</wsu:Created>
      </wsse:UsernameToken>
    </wsse:Security>
  </SOAP-ENV:Header>
  <SOAP-ENV:Body>
    <XferSrcDestSrch xmlns="http://jackhenry.com/jxchange/TPG/2008">
      <SrchMsgRqHdr>
        <jXchangeHdr>
          <JxVer/>
          <AuditUsrId></AuditUsrId>
          <AuditWsId></AuditWsId>
          <AuthenUsrId/>
          <ConsumerName/>
          <ConsumerProd/>
          <Ver_1/>
          <jXLogTrackingId>{Insert}</jXLogTrackingId>
          <Ver_2/>
          <InstRtId>011001276</InstRtId>
          <InstEnv>TEST</InstEnv>
          <Ver_3/>
          <BusCorrelId/>
          <Ver_4/>
          <WorkflowCorrelId/>
          <Ver_5/>
          <ValidConsmName>{Insert}</ValidConsmName>
          <ValidConsmProd>{Insert}</ValidConsmProd>
          <Ver_6/>
        </jXchangeHdr>
        <MaxRec>50</MaxRec>
        <Cursor/>
        <Ver_1/>
        <Ver_2/>
        <Ver_3/>
      </SrchMsgRqHdr>
      <AccountId Rstr="">
        <AcctId>8318033</AcctId>
        <AcctType>D</AcctType>
        <Ver_1/>
      </AccountId>
      <CustId/>
      <XferSrcDestType/>
      <Custom/>
      <Ver_1/>
      <XferSrcDestSrchRqArray>
        <XferSrcDestSrchRqInfo>
          <RstrExcType/>
          <Ver_1/>
        </XferSrcDestSrchRqInfo>
      </XferSrcDestSrchRqArray>
      <Ver_2/>
      <IncXtendElemArray>
        <IncXtendElemInfo>
          <XtendElem/>
          <Ver_1/>
        </IncXtendElemInfo>
      </IncXtendElemArray>
      <Ver_3/>
    </XferSrcDestSrch>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

XferSrcDestSrchXMLResponse

<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
  <s:Header>
    <o:Security s:mustUnderstand="1"
      xmlns:o="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
      <u:Timestamp u:Id="_0">
        <u:Created>2018-11-28T21:14:39.498Z</u:Created>
        <u:Expires>2018-11-28T21:19:39.498Z</u:Expires>
      </u:Timestamp>
    </o:Security>
  </s:Header>
  <s:Body>
    <XferSrcDestSrchResponse xmlns="http://jackhenry.com/jxchange/TPG/2008"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <SrchMsgRsHdr>
      <!-- Removed -->
        <SentRec>28</SentRec>
        <MoreRec>false</MoreRec>
        <Cursor>0</Cursor>
        <TotRec>28</TotRec>
        <Ver_1></Ver_1>
      </SrchMsgRsHdr>
      <AccountId>
        <AcctId>8318033</AcctId>
        <AcctType>D</AcctType>
        <Ver_1></Ver_1>
      </AccountId>
      <CustId>A000003</CustId>
      <XferSrcDestType>Both</XferSrcDestType>
      <PersonName>
        <ComName>A &amp; B TV Sales &amp; Serv</ComName>
        <Ver_1></Ver_1>
      </PersonName>
      <ProdCode>CN</ProdCode>
      <ProdDesc>Commercial NOW</ProdDesc>
      <XferSrcDestSrchArray>
        <XferSrcDestSrchInfo>
          <AccountId>
            <AcctId>1234</AcctId>
            <AcctType>D</AcctType>
            <Ver_1></Ver_1>
          </AccountId>
          <CustId>S000001</CustId>
          <PersonName>
            <ComName>Marla Smith</ComName>
            <FirstName>Marla</FirstName>
            <MiddleName>D</MiddleName>
            <LastName>Smith</LastName>
            <Ver_1></Ver_1>
          </PersonName>
          <ProdCode>NC</ProdCode>
          <ProdDesc>NOW Checking</ProdDesc>
          <XferSrcDestType>Both</XferSrcDestType>
          <SvcPrvdInfo>
            <JHAConsumer>
              <CurBal>813363784.20</CurBal>
              <AvlBal calculated="CurBal HoldAmt Float">813363709.20</AvlBal>
              <CurPayOff>.00</CurPayOff>
              <PmtAmt>.00</PmtAmt>
              <PmtAmtDue>.00</PmtAmtDue>
              <AcctStat>5</AcctStat>
              <AcctStatDesc>Pending Closed</AcctStatDesc>
              <Ver_1></Ver_1>
              <BrCode>1</BrCode>
              <BrDesc>Monett Office</BrDesc>
              <AcctRelCode>J</AcctRelCode>
              <AcctRelDesc>Joint</AcctRelDesc>
              <Ver_2></Ver_2>
            </JHAConsumer>
          </SvcPrvdInfo>
          <Ver_1></Ver_1>
          <Ver_2></Ver_2>
        </XferSrcDestSrchInfo>
        <!-- Removed additional records -->
      </XferSrcDestSrchArray>
      <Ver_1></Ver_1>
      <Ver_2></Ver_2>
    </XferSrcDestSrchResponse>
  </s:Body>
</s:Envelope>

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 Tue Oct 18 2022