Developer Programs

Learn

Docs
jXchange REST-Legacy Migration announced. Deadline for migration is July 31, 2026.

Developer Resources

API by Reference > Core Services > Internet Financial Institution Identification Add > Developer Resources

Details

SoapActionhttp://jackhenry.com/ws/IntnetFinInstIdAdd
Input NameIntnetFinInstIdAdd
Output NameIntnetFinInstIdAddResponse
Input Namespacehttp://jackhenry.com/jxchange/TPG/2008
Group NameCustomer
ContainerTPG_CustomerMaster.xsd

XML Examples

IntnetFinInstIdAdd 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>
    <IntnetFinInstIdAdd xmlns="http://jackhenry.com/jxchange/TPG/2008">
      <MsgRqHdr>
        <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>
        <Ver_1/>
        <Ver_2/>
        <Ver_3/>
      </MsgRqHdr>
      <ErrOvrRdInfoArray>
        <ErrOvrRd>
          <ErrCode/>
          <Ver_1/>
        </ErrOvrRd>
      </ErrOvrRdInfoArray>
      <CustId>NAA0317</CustId>
      <IntnetFinInstIdInfo>
        <AllowIntnetIdDup>true</AllowIntnetIdDup>
        <IntnetFinInstPswdId>David445886</IntnetFinInstPswdId>
        <IntnetFinInstAcctIdArray>
          <IntnetFinInstAcctId>
            <AcctId>143453</AcctId>
            <AcctType>D</AcctType>
            <Ver_1/>
          </IntnetFinInstAcctId>
        </IntnetFinInstAcctIdArray>
        <Ver_1/>
        <IntnetFinInstACHXferArray>
          <IntnetFinInstXferInfo>
            <ACHDrName>Cassidy Norris</ACHDrName>
            <ACHDrRtNum>123456789</ACHDrRtNum>
            <FinInstDrName>Community First</FinInstDrName>
            <ACHDrAcctId>146118</ACHDrAcctId>
            <ACHDrAcctType>S</ACHDrAcctType>
            <Ver_1/>
            <AccessAlw>true</AccessAlw>
            <Ver_2/>
            <AliasAcctName/>
            <Ver_3/>
          </IntnetFinInstXferInfo>
        </IntnetFinInstACHXferArray>
        <Ver_2/>
      </IntnetFinInstIdInfo>
      <Custom/>
      <Ver_1/>
    </IntnetFinInstIdAdd>
  </SOAP-ENV:Body>
</SOAP-ENV:Envelope>

IntnetFinInstIdAdd FAQ

Does this API call create a new Online Banking (OLB) user for the specified CustId?

Yes, the API call establishes a new OLB user for the provided CustId.


How does the process of creating a new OLB user work? What steps must the user follow after the IntnetFinInstIdAdd API call completes?

The IntnetFinInstIdAdd service registers new users for NetTeller. Please note that this process is not real-time. NetTeller IDs created through this service become available after an automatic nightly sync or a manual update performed by the financial institution (FI) via the back-office tool. We are working toward automating this update for near real-time availability.

Once the ID is active, the customer logs into the NetTeller application and completes the first-time login process. This process varies by FI based on installed products and configured disclosures. At minimum, the user will need their NetTeller ID and PIN. Additional requirements may apply—for example, if the FI uses Electronic Statements Interactive (ESI), an email address may be required for enrollment.


How does setting AllowIntnetIdDup to false affect the API call? Will an error occur if the CustId already has an associated IntnetFinInstId?

Yes. If AllowIntnetIdDup is set to false and the CustId already has a NetTeller ID, the API returns error 5008. To allow duplicates, set AllowIntnetIdDup to true and include an override for error code 5066 (“NetTeller ID already exists for customer”).


Core Director what does error code ErrCode = 1, “System error encountered” mean?

This is a generic error indicating an unexpected issue in the business service. Verify that you are passing the required AllowIntnetIdDup field. Valid values are:

  • true: Allows multiple NetTeller IDs for a CIF
  • false: Prevents multiple NetTeller IDs for a CIF

What is the use case for allowing duplicate Internet IDs?

Allowing duplicates should be limited to FI-controlled overrides to reduce fraud risk. Common scenarios include:

  • Disabling an existing ID and issuing a new one due to fraud
  • Customers managing numerous accounts under separate IDs (e.g., a business with hundreds of tenant-specific accounts)

For an existing SilverLake customer, is checking CustSrchResponse.CustSrchRecArray.CustSrchRec.IntnetFinInstIdArray.IntnetFinInstArrayInfo.IntnetFinInstId sufficient to confirm OLB access?

Yes. You can also check for an existing IntnetFinInstId in the CustInq response.


What does IntnetFinInstIdAdd.IntnetFinInstIdInfo.IntnetFinInstPswdId contain? Is it an ID or the actual password?

This field contains the actual password—a numeric PIN, typically 4 characters long. It is used for first-time login and was historically used for password resets. Current password recovery methods no longer rely on this PIN. It is not a long-term password and does not follow standard password complexity rules.


What is IntnetFinInstIdAdd.IntnetFinInstIdInfo.IntnetFinInstAcctIdArray used for?

This array lists the accounts linked to the new NetTeller ID. If no accounts are provided during creation, they can be added later using the IntnetFinInstAcctIdAdd service.


If a customer without OLB access already has accounts, do those accounts need to be added to the new NetTeller ID?

It depends on the FI’s configuration. Use the IntnetFinInstIdInq service to confirm which accounts are linked to the NetTeller ID.


What is IntnetFinInstIdAdd.IntnetFinInstIdInfo.IntnetFinInstACHXferArray used for?

This array sets up ACH transfer arrangements with other financial institutions and makes them available in OLB.


What does IntnetFinInstIdAdd.IntnetFinInstIdInfo.IntnetFinInstPswdId in the response contain?

If no password was specified in the request, the service provider generates a random PIN and returns it in this field. The customer must use this PIN for their initial NetTeller login.


If the IntnetFinInstIdAdd response includes error code 5008, is there another way to retrieve the existing NetTeller ID?

Yes. Use the CustInq service to retrieve the associated NetTeller ID at: CustRec.IntnetFinInstIdArray.IntnetFinInstIdArrayInfo.IntnetFinInstId


Can a NetTeller ID be deleted using a jXchange API?

No. The jXchange API does not provide functionality to delete a NetTeller ID.


Is it possible to create a Cash Management NetTeller ID via the IntnetFinInstIdAdd API?

No. IntnetFinInstIdAdd can be used to create standard NetTeller IDs, but it does not support creating Cash Management IDs.


Have a Question?

Did this page help you?

Last updated Wed Mar 4 2026