jXchange and SilverLake

Some behaviors are not easily discoverable nor exposed but are pertinent to consumers for understanding not only the contracts but unique behavior from providers. This page begins to document these specifics to ensure a smoother development process for consumers. It is not an inclusive description of all behaviors, but it answers common questions regarding the information.

Additional information about API specific behaviors may be found within Developer Resources page located with each API reference.

Email

SilverLake supports adding two email addresses to a customer record. They must be defined as either primary or secondary, using the exact text in the EmailType element.

<EmailArray>
    <EmailInfo>
        <EmailAddr>primary-email@host.com</EmailAddr>
        <EmailType>Primary E-Mail</EmailType>
    </EmailInfo>
    <EmailInfo>
        <EmailAddr>secondary-email@host.com</EmailAddr>
        <EmailType>Secondary E-Mail</EmailType>
    </EmailInfo>
</EmailArray>

Phone Types

SilverLake supports the following phone number types, up to six entries.

<PhoneArray>
    <PhoneInfo>
        <PhoneNum>8005558888</PhoneNum>
        <PhoneType>HP</PhoneType>
    </PhoneInfo>
</PhoneArray>

Loan Collateral Documents

SilverLake supports up to six item descriptions and six document descriptions for the Loan Collateral services. The CollatDocInfoText and CollatItemDescText elements require exact text for the operation to function correctly.

<CollatDocInfoArray>
    <CollatDocInfoRec>
        <CollatDocInfo>Information</CollatDocInfo>
        <CollatDocInfoText>Doc Description #1</CollatDocInfoText>
    </CollatDocInfoRec>
        <CollatDocInfoRec>
        <CollatDocInfo>Information</CollatDocInfo>
        <CollatDocInfoText>Doc Description #2</CollatDocInfoText>
    </CollatDocInfoRec>
...Through Document Description 6
</CollatDocInfoArray>

<CollatItemInfoArray>
    <CollatItemInfoRec>
        <CollatItemInfo>Information</CollatItemInfo>
        <CollatItemInfoText>Item Description #1</CollatItInfoText>
    </CollatItemInfoRec>
        <CollatItemInfoRec>
        <CollatItemInfo>Information</CollatItemInfo>
        <CollatItemInfoText>Item Description #2</CollatItemInfoText>
    </CollatItemInfoRec>
...Through Item Description 6
</CollatItemInfoArray>

Account Types

SilverLake Account Types

Account Status Codes

Here are the current account statuses used by the SilverLake core broken out by account type.

Deposit - Account Type D / Savings - Account Type S / Club - Account Type X

This code identifies the status of the account. The system uses this code to determine how activity and accruals are handled. Valid codes are:

General Ledger - Account Type G

Loans - Account Type L

The default status code will be obtained from the type code parameter file. In new loan entry, in most cases, this code should be 4 to indicate a new loan today. Other valid codes are:

The status code should be left at 4 for all new loans. The ability to enter status codes 5, 6, 7, and 8 is provided primarily for the purpose of adding charged off loans to the system after conversion. Some servicing companies do not carry charged off loans in their database, and they are not converted to the JH system.

Overdraft Account - Type O

Safe Deposit Box - Type B

Time Deposits - Account Type T

This code identifies active, redeemed, matured but not redeemed, and new accounts. The system uses this code to determine how activity and accruals are to be handled. Valid status codes are:

Optional CIF Field Validation

SilverLake allows each institution to determine certain non-critical customer-level information to be required during the creation or modification of customer-level records. The behavior and error response may vary from site to site. Allowing for this variable will help eliminate future problems. The table below lists the items that a financial institution may flag using one of the three following values. This list may change in newer releases of SilverLake.

• Required – Values have to be provided
• Override – Required but allowed to be overridden
• Not Required – Values do not have to be provided