Preference Record

The Preference record contains information about a member’s preferences for interacting with the audio response or home banking system.

This document contains the field name, field description, field number, mnemonic, data type, and default information for each field. Other pertinent information includes:

**Source**  
Indicates where the data in the field comes from:

    **User-entered**  
    The user creates the information in this field.

    **System-entered**  
    A system process populates the value for the field. This value can include data transmitted by the ATM network, when applicable.

    **System-calculated**  
    The system calculates but does not store the value of the field each time the field appears on an inquiry or file maintenance screen.

When you receive a member’s completed application for audio response or home banking, you must create a Preference record for the member’s account. An account can have several Preference records, each with a unique audio access code.

The Preference record includes the following fields, which are defined below:

Fields

Type

This field stores a credit union-defined code identifying this kind of Preference record.

Enter a credit union-defined code (00-99) to identify this kind of Preference record.

Audio Access Code

This field stores the full audio access code if it is in clear text or hashed with an MD5 hashing method. If using advanced hashing, this field stores the first part of the hashed audio access code.

Tip: Symitar audio software must be on level 5.06 or greater to support up to a 15-digit PIN.

This field is used for the audio access code (also known as a Personal Identification Number or PIN). Enter one of the following:

• Type 0 if you want the system to issue an Audio Access PIN.
• Type 1 if you do not want the system to issue a PIN.
• Entries 2–9 are reserved for future use.
• Enter a number (10-9998) to assign a specific PIN.
  • The type of data stored in this field when you enter a PIN depends on the value of the HB/Audio Password Hash Code parameter in the Miscellaneous Parameters:
    • When the HB/Audio Password Hash Code parameter is set to (0) Do Not Hash Passwords, the entered specific PIN is assigned to the account manually. For a PIN shorter than four digits, you must enter leading zeros. The PIN is stored in this field as up to the first 15 characters entered as a numeric string.
    • When the HB/Audio Password Hash Code parameter is set to (1) Use Modified MD5 Hash, the hash of the entered PIN is stored in this field using the first 16 characters of this field. To modify this field using the Account Manager or the FMPERFORM command in a specfile, you must specify the 16 hexadecimal character hash in this field.
    • When the HB/Audio Password Hash Code parameter is set to (2) Use Advance Hash, the first part of the hash of the entered PIN is stored in this field and the other parts are stored in the Audio Access Code 2-4 fields. You cannot retrieve the audio access code because it is masked. If you type 0000 in this field, the system issues a PIN regardless of how the HB/Audio Password Hash Code parameter is set. If you set this field to 0000 in only one Preference record, the first time the member enters an account number to access the audio response or home banking system, the member must enter a PIN. This PIN is then stored in this field in the Preference record and displays as 9999 for security. You can also use theAssign Audio Access Numbers function of the Miscellaneous Processing batch program to assign PINs randomly. Caution: When using SymXchange to create an account, do not include the Audio Access Code field. This field will be set to 0000 by default.

After a PIN is assigned to an account, either automatically or manually, the system displays in this field for security.

Tip: Although this is a 40-character field, the system only uses up to the first 15 characters for the audio ******************** access code unless you are using the hash of the code. The actual number of characters used (4 through 15) depends on the value of the Symitar-maintained host parameter Audio Access Len. Contact Symitar Support to have this parameter changed.

Whenever this field is file maintained, the Last Access Code Change field is updated with the date of the change.

Tip: The MD5HASH and PASSWORDHASH PowerOn commands are used to encrypt codes in specfiles.

Second Audio Access Code

This field stores the full member’s secondary audio access code if it is in clear text or hashed with an MD5 hashing method. If using advanced hashing, this field stores the first part of the hashed secondary audio access code.

This field is used for the audio access code (also known as a Personal Identification Number or PIN). Enter one of the following:

• Type 0 if you want the system to issue an Audio Access PIN.
• Type 1 if you do not want the system to issue a PIN.
• Entries 2–9 are reserved for future use.
• Enter a number (10-9998) to assign a specific PIN. The type of data stored in this field when you enter a PIN depends on the value of the HB/Audio Password Hash Code parameter in the Miscellaneous Parameters:
  • When the HB/Audio Password Hash Code parameter is set to (0) Do Not Hash Passwords, the entered specific PIN is assigned to the account manually. For a PIN shorter than four digits, you must enter leading zeros. The PIN is stored in this field as up to the first 15 characters entered as a numeric string.
  • When the HB/Audio Password Hash Code parameter is set to (1) Use Modified MD5 Hash, the hash of the entered PIN is stored in this field using the first 16 characters of this field. To modify this field using the Account Manager or the FMPERFORM command in a specfile, you must specify the 16 hexadecimal character hash in this field.
  • When the HB/Audio Password Hash Code parameter is set to (2) Use Advance Hash, the first part of the hash of the entered PIN is stored in this field and the other parts are stored in the Second Audio Access Code 2-4 fields. You cannot retrieve the audio access code because it is masked.

Language

This field stores a code that indicates the language the member wants the audio response system to use for messages.

Data Type Descriptions

(0) English

Messages should be in English.

(1) Spanish

Messages should be in Spanish.

2–9

Use this credit union-defined code for any other language you have ordered and installed if messages should be in that language.

Reference

This field stores any reference information for this Preference record.

Enter any reference information (up to 40 characters) for this Preference record. You must use uppercase letters.

This credit union-defined field has no effect on the audio response system or the home banking system. You can use this field to help you distinguish between multiple Preference records in the same account. For example, you could use this field to store the member’s name or department. PowerOn specfiles can access this field for reports and displays.

E-Mail Address

This field stores the email address used for online password reset.

Enter the member’s email address (up to 40 characters).

Whenever this field is changed, the E-Mail Address Ch Date and the E-Mail Address Ch Time fields are updated with the current date and time.

The email in the primary Name record is used only for e-Statements. The email in the Preference record is used for identity during password reset and for temporary passwords. If the member already has an email address in their primary Name record, then NetTeller displays that email as the default to the member during password reset enrollment. These email addresses may be the same.

If multiple Preference records in the account have the User Code field set to 0, the E-Mail Address field in each Preference record must be unique. Otherwise, members may experience problems with password reset.

E-Mail Address Ch Date

This field stores the date the credit union received the document.

The system automatically sets this field to the current date every time that the E-Mail Address field is updated, either through the system or home banking.

E-Mail Address Ch Time

This field stores the time (in HHMM format) that the credit union received the document.

The system automatically sets this field to the current time whenever the E-Mail Address field is updated. The default is 12:00 A.M.

Last Access Code Change

This field stores the last date the access code for this Preference record was changed, either by the member (through audio response or home banking) or by the credit union (through account file maintenance).

The system automatically sets this field to the current date every time that the access code for this Preference record was changed.

Last Logon Date

This field stores the most recent date that someone successfully logged on to this account through audio response or home banking with the access code specified in this Preference record.

This field is not automatically updated by third-parties interfaces via SymXchange. It must be updated by the credit union’s system. Only Intervoice audio updates this field automatically.

Last Logon Time

This field stores the most recent time (in HHMM format) someone successfully logged on to this account through audio response or home banking with the access code in this Preference record.

This field is not automatically updated by third-parties interfaces via SymXchange. It must be updated by the credit union’s system. Only Intervoice audio updates this field automatically.

Record Change Date

This field stores the system date in this field when you create, change, or save the Preference record. Sometimes the system updates this field because the record was saved, even though there may not be any actual changes in the record.

Note: The system does not change this field when a calculated field changes.

You cannot perform file maintenance on this field.

Audio Information

These preference fields relate specifically to audio preference information.

List Transactions

This field stores the number of transactions the member can hear in a history inquiry.

• Type 0 to allow the member to specify the number of transactions for each history inquiry.
• Enter a number 1–99 to include that number of transactions in a history inquiry. If you enter any value except 0, the member cannot use the audio response system to change the value of this field to 0.

Interaction Mode

This field stores a code that indicates how the member interacts with the audio response system.

Data Type Descriptions

(0) Expert Mode

The system should prompt the caller to enter a transaction code (also called a service code). The caller can refer to a printed list of transaction codes or press a key to hear a help list of transaction codes.

(1) Menu Mode

The audio response system should read menus to the member.

Audio Enable Code

This field stores a code that indicates the level of access the member has to the audio response system.

A member can inquire about all Share and Loan records in his or her account, but the system controls transfers and withdrawals according to the service code assigned to each Share and Loan record (see Setting Up the Audio Response System). As long as the Audio Enable Code allows only inquiries, you can set all service codes in advance. Then when a member signs up to use the audio response system, you need to change only the Audio Enable Code to activate the service.

Data Type Descriptions

(0) Inquiries Only

Allow the member to perform inquiries only.

(1) Transfers

Allow the member to perform inquiries and transfers.

(2) Withdrawals and Transfers

Allow the member to perform inquiries, withdrawals, and transfers.

Audio Call Count

This field stores the number of times the member called since the last time the Daily Posting batch program cleared this field.

• Each time a member calls the audio response system and successfully enters the account number and access code for this Preference record, the system increments this field by 1. The system does not increment this field if the system is off line or the account is in use when the member calls.
• You can reset this field to 0000 by entering the account type of the member’s Account record at the Clear Audio Call Count Account Types prompt in the Daily Posting batch program.

Audio Call Minutes

This field stores the number of minutes (rounded to the nearest minute) the member used the audio response system since you last cleared the call minutes log.

When a member calls the audio response system and successfully enters the account number and access code for this Preference record, the system increments this counter by 1 whenever the current system time increases by 60 seconds. The system does not increment this field if the system is off line or the account is in use when the member calls.

Tran Codes

This field can store the transaction code (also called a service code) for the member’s preferred transaction.

Optional entry: The audio response system performs this transaction immediately after the member enters an account number and access code. The system prompts the caller if necessary.

This option is best suited for account inquiries. Members should usually avoid automatically performing transactions such as withdrawals and transfers each time they call the audio response system. Certain transactions (such as transfers) do not take the ID from this field. If this field contains an ID after specifying such a transaction, the system ignores the ID.

This field can contain the following sets of characters:

• Type T followed by the two-digit transaction code defined in the MemberConnect Parameters. These characters indicate a specific transaction. Always enter this transaction code first. For more information, see Audio Response Transactions in the Audio Response book.

• Type S followed by the two-digit share ID. These characters indicate that information for a share of this ID in the current account is requested. Enter these characters after the transaction code. Example:

  Assume that transaction code 06 performs an account balance inquiry, and you type T06S01 in this field. Whenever the member calls the audio response system, the system automatically provides the balance for Share ID 01.

• Type L followed by the two-digit loan ID. These characters indicate that information for a loan of this ID in the current account is requested. Enter these characters after the transaction code.

• Type B followed by the two-digit bill payment number. These characters indicate that information for a bill payment of this number in the current account is requested.

• Type R followed by the two-digit specfile number defined in the MemberConnect Parameters. These characters indicate that a PowerOn specfile of this number is to run automatically whenever the member calls. Enter these characters after the transaction code. For more information, see Audio Response Transactions in the Audio Response book. Example:

  To run specfile 2 whenever the member enters the account and access code (assuming the transaction code for Miscellaneous Inquiry is 69), type T69R02. The specfile must be installed for demand use and must be identified in the appropriate Custom Specfile parameter in the MemberConnect Parameters. A Miscellaneous Inquiry specfile can function like a sales tracking specfile. The specfile can review a caller’s account, see if the caller has a specific credit union product or service, and tell the caller about the product or service if he or she does not already have it.

Home Fax

This field stores the member’s home fax number.

Optional entry: Enter the member’s home fax number (up to 12 characters).

Business Fax

This field stores the member’s business fax number.

Optional entry: Enter the member’s business fax number (up to 12 characters).

Last Audio Logon Date

This field stores the most recent date a member successfully logged on to an account through the audio response system with the access code specified in the Preference record.

This field is not automatically updated by third-parties interfaces via SymXchange. It must be updated by the credit union’s system. Only Intervoice audio updates this field automatically.

Last Audio Logon Time

This field stores the most recent time (in HHMM format) a member successfully logged on to an account through the audio response system with the access code in the Preference record.

This field is not automatically updated by third-party interfaces via SymXchange. It must be updated by the credit union’s system. Only Intervoice audio updates this field automatically.

Home Banking Information

These preference fields relate specifically to home banking preference information.

User Code

This field stores a code you can use to uniquely identify a particular Preference record when many members have access to a single account, such as a corporate account. This field is used only for home banking.

• Type 0 if you do not want to identify Preference records by this field. Multiple Preference records associated with an account can have an undefined User Code field. If all the Preference records in an account have a value in the User Code field of 0, this field does not affect the member’s use of the home banking system. If any of the member’s Preference records has a value in this field of 0, the members must type 0 at the User Code prompt.
• Enter a credit union-defined code (1-999) to uniquely identify this Preference record. Each credit union-defined code must be unique in an account. For example, an account can have only one Preference record with a value in this field of 1, and only one Preference record with a value in this field of 777, but any or all the Preference records in an account can have a value in this field of 0. If at least one Preference record in an account has a defined value in this field (1-999), when the member accesses the home banking system and enters an account number and access code, the home banking system prompts the member to enter the User Code.

Note: Instead of waiting for the User Code prompt, the member can prefix the user code to his or her four-digit access code at the Access Code prompt. If the access code has fewer than four digits, the member must enter leading zeros. For example, a member with an access code of 77 and a user code of 21 can type 210077 at the Access Code prompt to bypass the User Code prompt.

Whenever a member who has a Preference record with a defined value in the User Code field (1-999) accesses home banking, that value is stored in the transaction record’s User Override field for withdrawal and transfer transactions.

• If a member requests a draft copy or asks to stop a draft, the system appends the value in the User Code field to the request in the DRAFT.COPY.AUTH.LIST or DRAFT.STOP.AUTH.LIST letter file. If the authorization is faxed, the sample RD.FAX.DRAFT.COPY.AUTH and RD.FAX.DRAFT.STOP.AUTH specfiles include the User Code field value.
• When a member who has a Preference record with an undefined value in the User Code field (0) accesses home banking, the system posts transactions and makes entries in the DRAFT.COPY.AUTH.LIST and DRAFT.STOP.AUTH.LIST files without including a User Code field value.

HB Username

This field stores a home banking username that is used with the home banking password to let members access their accounts through the home banking system.

This field is not case-sensitive and must be unique in the database. It must start with an alphabetic character and contain only numbers or letters. In the Miscellaneous Parameters, set the HB Username Minimum Length and HB Username Maximum Length parameters to control the minimum and maximum length of this field.

Note: The system uses a cross-reference key file to ensure that the home banking username is unique in the database.

HB Mode

This field stores a code that controls the member’s access to NetTeller and, if using SymConnect, access to the audio response system.

Note: As of Symitar Release 2025.00, the SymConnect API is fully decommissioned. All clients and vendors are required to transition to SymXchange.

Data Type Descriptions

(0) No Home Banking

Prevent the member from accessing the home banking or audio response system.

(1) Standard Home Banking

Allow the member to access the home banking or audio response system.

HB Enable Code

This field stores a code that control the member’s level of access to NetTeller and, if using SymConnect, the level of access to the audio response system.

Data Type Descriptions

(0) Inquiries Only

Allow the member to perform account inquiries only through the home banking or audio response system.

(1) Transfers

Allow the member to perform account inquiries and transfers through the home banking or audio response system.

(2) Withdrawals and Transfers

Allow the member to perform account inquiries, transfers, and withdrawals through the home banking or audio response system.

Initially all accounts have this field set to 0. As members apply for home banking services, set this field to 1 or 2, depending on the level of access requested.

Note: If you create a Preference record for a member who does not already have a Preference record for audio response, be sure to assign an audio access code, which serves as an access code for both home banking and audio response.

HB Password

This field stores the full home banking password if it is in clear text or hashed with an MD5 hashing method. If using advanced hashing, this field stores the first part of the hashed home banking password.

Enter an optional home banking password that can be used instead of an audio access code to gain access to a member’s account through the home banking system.

This field must be set to a value of 8 or greater. The maximum number of characters you can enter in this field is 20. Additionally, you cannot choose a home banking password that contains the value in the HB Username field.

The value in the HB Password Mode parameter in the Miscellaneous Parameters must be set to (0) Use HB Password and the value in the Use HB Password? parameter in the SymConnect Client-Specific Parameters must be set to Yes for this field to be used.

In Miscellaneous Parameters, set the HB Password Mode, HB Password Minimum Length, and HB Password Maximum Length parameters to control whether the home banking system uses passwords and the minimum and maximum lengths of those passwords, if used.

The type of data stored in this field depends on the value of the HB/Audio Password Hash Code parameter in the Miscellaneous Parameters:

• When the HB/Audio Password Hash Code parameter is set to (0) Do Not Hash Passwords, this field contains the left-justified password.
• When the HB/Audio Password Hash Code parameter is set to (1) Use Modified MD5 Hash, the hash of the home banking password is stored using the first 16 characters of this field. To modify this field using the Account Manager or the FMPERFORM command in a specfile, you must specify the 16 hexadecimal character hash in this field.
• When the HB/Audio Password Hash Code parameter is set to (2) Use Advance Hash, the first part of the hash of the home banking password is stored in this field and the other parts are stored in the HB Password 2-4 fields. You cannot retrieve the home banking password because it is masked.

A blank value in this field means that the member cannot use the home banking password in the Preference record to gain access to the account, regardless of how the HB/Audio Password Hash Code parameter is set in the Miscellaneous Parameters.

You can also use the Assign Audio Access Numbers option of the Miscellaneous Processing batch program to assign the same PINs randomly generated for the Audio Access Code field to each HB Password field.

The PASSWORDHASH PowerOn command is used to apply an MD5 hash method to clear text passwords or audio access codes in specfiles. See PASSWORDHASH for details.

Note: The Audio PIN & HB Pwd Access parameter in Miscellaneous Parameters must be set to (2) Allow FM & Mask or (3) Allow FM & Unmask to update this field through file maintenance outside of the Miscellaneous Processing batch program or the FMPERFORM command in a specfile.

Second HB Password

This field stores the full member’s secondary home banking password if it is in clear text or hashed with an MD5 hashing method. If using advanced hashing, this field stores the first part of the hashed secondary home banking password.

This field is used when the Second Password Verification parameter is set to (1) Second Password on the Preference Record in the SymConnect Client Specific parameters. You can use this option when you want a password other than the member’s Social Security Number.

For the advance password hashing option, this field stores the first part of the second home banking password and the other password parts are stored in the Second HB Password 2–4 fields.

Using this option gives you the ability to use the Second Password Eff Date parameter to specify the date when the secondary password becomes mandatory.

Last HB Password Change

This field stores the date of the last change to the home banking password, if used.

The system automatically sets this field to the current date every time that the home banking password for this Preference record was changed.

HB Call Count

This field stores the number of times the member used home banking since the last time you cleared the count.

This field can be useful in assessing home banking fees.

HB Call Minutes

For credit unions using the older dial-up MemberConnect PC software, this field stores the total number of minutes the member used home banking since the last time you cleared the log.

Last HB Logon Date

This field stores the most recent date that a member successfully logged on to an account through NetTeller online banking or goDough mobile banking solutions with the access code specified in the Preference record.

Last HB Logon Time

This field stores the most recent time a member successfully logged on to an account through NetTeller online banking or goDough mobile banking solutions with the access code specified in the Preference record.

HB Password Reset Info

These preference fields relate specifically to home banking password reset information.

Security Question

This field stores the security question used to validate the member’s identity for a password reset feature.

Enter a security question (up to 40 characters).

If the member does not want to enroll in online password reset, type Member Opts Out in this field.

Security Answer

This field stores the security answer for a password reset feature.

Enter a security answer (up to 40 characters). After entered, this field is masked.

Lock Count

This field stores the number of times the member has entered an incorrect security answer during password reset.

The system increments this field every time the member submits an invalid security answer during an online password reset. When a user reaches the maximum attempts, as defined by the Inv Attempts Before Frozen parameter in MemberConnect and SymConnect Client-Specific parameters, the system sets the value in the Locked field to (1) Yes and the value in the Audio/HB Frozen Mode field in the Account record to (2) Audio/HB is permanently frozen.

The system automatically resets this field to 0 when you set the Locked field to (0) No.

Locked

This field stores a code indicates whether the Preference record is locked.

Data Type Descriptions

(0) No

The Preference record is not locked. To unlock the member’s Preference record, select this option.

(1) Yes

The Preference record is locked.

When the Preference record is locked, the member cannot access an applicable home banking system or use a password reset feature.

The system locks the Preference record when the value in the Lock Count field reaches the number set by the Inv Attempts Before Frozen parameter.

Password Reset Date

This field stores the system date when the member resets their password in an applicable home banking system.

The member is allowed to reset their password only once per calendar day, as determined by this field.

Password Reset Time

This field stores the time (in HHMM format) when the member resets their password in an applicable home banking system.

Password Reset Notice

This field stores a code indicates when the member successfully resets their password in an applicable home banking system.

Data Type Descriptions

(0) No

The Preference record is not locked.

(1) Yes

The member has successfully reset their password in an applicable home banking system.

In the Daily Posting batch program, if you answer Yes at the HB Password Reset Notice(s) prompt and this field is set to (1) Yes, the system generates a Notice of Online Password Reset for this member and sets this field to (0) No. Otherwise, you can ignore this field.

Last Scsful Pw Reset Dt

This field stores the system date when the member successfully logs on to an applicable home banking system using the temporary password and changes it.

Last Scsful Pw Reset Tm

This field stores the time (in HHMM format) when the member successfully logs in to an applicable home banking system using the temporary password and changes it.

Pw Reset Probation

This field stores a code indicates the account probation status.

The home banking applications (Audio Response or NetTeller) use this status with their password reset feature to require a member to provide a new password.

Data Type Descriptions

(0) No

The account is not in probation.

If the member logs on and changes the temporary password successfully, the system sets this field back to No.

(1) Yes

The account is in probation.

The system sets this field to Yes when the member resets their home banking password and receives a temporary one via email. You can also set this field to Yes manually, if you want to force the user to update their password the next time they log on to the home banking application.

Note: If the member reaches the maximum number of invalid logon attempts with the temporary password, as defined by the Inv Attempts Before Frozen field in the SymConnect Client-Specific and MemberConnect parameters, the system freezes the account. The system sets the value in the Audio/HB Frozen Mode field in the Account record to (2) Audio/HB is permanently frozen.

Invalid Password Attempts

This field stores the number of times a member enters an invalid password.

Each time the member enters an invalid password, the system adds 1 to this field. When a member enters a valid password, the system resets the value in this field to zero (0). After each invalid attempt, the system checks if the value in this field equals the value specified at the Inv Attempts Before Frozen parameter. If it does, the system sets the value in the Audio/HB Frozen Mode field in the Account record to (2) Audio/HB is permanently frozen and this field is reset back to zero.

Transaction Limit Info

These preference fields relate specifically to transaction limit information.

Last Transaction Date

This field stores the date of the last successful transaction that was subjected to limiting. For the limits to be enforced, the SymXchange Parameters must be using home banking credentials.

The system updates this field when SymConnect transactions are posted.

Maximum Cash W/D

This field stores the maximum amount allowed in a single cash withdrawal.

Enter the maximum positive amount allowed in a single cash withdrawal.

Cash W/D Limit

This field stores the daily cash withdrawal limit.

Enter the positive daily cash withdrawal limit.

Cash W/D Count Limit

This field stores the maximum number of cash withdrawals allowed per day.

Enter the maximum number of cash withdrawals (0-9999) allowed per day.

Cash W/D Amount

This field stores the total cash withdrawal amount on the date in the Last Transaction Date field.

The system updates this field with a positive amount when SymConnect transactions are posted.

Cash W/D Count

This field stores the number of cash withdrawals performed on the date in the Last Transaction Date field.

The system updates this field with a positive value when SymConnect transactions are posted.

Maximum Check W/D

This field stores the maximum amount allowed in a single withdrawal by check.

Enter the maximum positive amount allowed in a single withdrawal by check.

Check W/D Limit

This field stores the daily amount that can be withdrawn each day by check.

Enter the positive daily amount that can be withdrawn each day by check.

Check W/D Count Limit

This field stores the maximum number of withdrawals by check allowed per day.

Enter the maximum number of withdrawals by check (0-9999) allowed per day.

Check W/D Amount

This field stores the total cash withdrawals by check on the date in the Last Transaction Date field.

The system updates this field with a positive amount when SymConnect transactions are posted.

Check W/D Count

This field stores the number of check withdrawals performed on the date in the Last Transaction Date field.

The system updates this field with a positive value when SymConnect transactions are posted.

Maximum Transfer

This field stores the maximum amount allowed in a single transfer.

Enter the maximum positive amount allowed in a single transfer.

Transfer Limit

This field stores the maximum amount that can be transferred daily.

Enter the positive maximum amount that can be transferred daily.

Transfer Count Limit

This field stores the maximum number of transfers allowed per day.

Enter the maximum number of transfers (0-9999) allowed per day.

Transfer Amount

This field stores the total transfer amount on the date in the Last Transaction Date field.

The system updates this field with a positive amount when SymConnect transactions are posted.

Transfer Count

This field stores the number of transfers performed on the date in the Last Transaction Date field.

The system updates this field with a positive value when SymConnect transactions are posted.

Maximum Bill Pmt

This field stores the maximum allowable amount for a single bill payment.

Enter the maximum positive allowable amount for a single bill payment.

Bill Pmt Limit

This field stores the daily bill payment limit.

Enter the positive the daily bill payment limit.

Bill Pmt Count Limit

This field stores the maximum number of bill payments allowed per day.

Enter the maximum number of bill payments (0-9999) allowed per day.

Bill Pmt Amount

This field stores the total amount of bill payments on the date in the Last Transaction Date field.

The system updates this field with a positive amount when SymConnect transactions are posted.

Bill Pmt Count

This field stores the number of bill payments performed on the date in the Last Transaction Date field.

The system updates this field with a positive value when SymConnect transactions are posted.

Maximum Deposit

This field stores the maximum amount allowed in a single deposit.

Enter the maximum positive amount allowed in a single deposit.

Deposit Limit

This field stores the maximum amount of total deposits allowed per day.

Enter the maximum positive amount of total deposits allowed per day.

Deposit Count Limit

This field stores the maximum number of deposits allowed per day.

Enter the maximum number of deposits (0-9999) allowed per day.

Deposit Amount

This field stores the total deposit amount on the date in the Last Transaction Date field.

The system updates this field with a positive amount when SymConnect transactions are posted.

Deposit Count

This field stores the number of deposits performed on the date in the Last Transaction Date field.

The system updates this field with a positive value when SymConnect transactions are posted.

Non-Displayed Fields

This preference field does not appear in the system and is only accessed by PowerOn specfiles or SymConnect.

Audio Access Code 2-4

These fields store the second, third, and fourth hash parts of a member’s audio access code if you use the advance password hashing option.

When the HB/Audio Password Hash Code parameter in the Miscellaneous Parameters is set to (2) Use Advance Hash, the first part of the hash of the entered code is stored in the Audio Access Code field and the other parts are stored in these fields.

You cannot read or update these fields.

HB Password 2-4

These fields store the second, third, and fourth hash parts of a member’s home banking password if you use the advance password hashing option.

When the HB/Audio Password Hash Code parameter in the Miscellaneous Parameters is set to (2) Use Advance Hash, the first part of the hash of the entered password is stored in the HB Password field and the other parts are stored in these fields.

You cannot read or update these fields.

Locator

This field stores a unique number within each Preference record set that can be used as a unique identification of this record.

The system automatically assigns the value in this field when the record is created, and you cannot change it. The value is a positive number greater than zero and up to about two billion.

This field can be used during PowerOn file maintenance (both on demand and batch) to uniquely identify a record. Using this field is recommended since a record’s ordinal sequence number may change if someone else inserts or deletes a record with a lower ordinal sequence number just before you post your file maintenance.

Second HB Password 2-4

These fields store the second, third, and fourth hash parts of a member’s second home banking password if you use the advance password hashing option.

When the HB/Audio Password Hash Code parameter in the Miscellaneous Parameters is set to (2) Use Advance Hash, the first part of the hash of the entered password is stored in the Second HB Password field and the other parts are stored in these fields.

You cannot read or update these fields.

Second Audio Access Code 2-4

These fields store the second, third, and fourth hash parts of a member’s second audio access code if you use the advance password hashing option.

When the HB/Audio Password Hash Code parameter in the Miscellaneous Parameters is set to (2) Use Advance Hash, the first part of the hash of the entered code is stored in the Second Audio Access Code field and the other parts are stored in these fields.

You cannot read or update these fields.

Previous HB Password 01 - Previous HB Password 24

These fields store the past 24 HB Password and Second HB Password field values. Each field stores the full password if it is in clear text or hashed with an MD5 hashing method.

For the advance password hashing option, each field stores the first part of the password and the other password parts are stored in HB Previous Password Hash 2(24)–HB Previous Password Hash 4(24) fields.

You cannot read or update these fields.

HB Password Mode

This field stores a code that indicates the format the system uses to store a member’s password.

Data Type Descriptions

(0) Do Not Hash Passwords

The system assumes that the value stored in the HB Password field is the home banking password.

(1) Use Modified MD5 Hash

The system hashes the new value stored in the HB Password field with a modified MD5 hash.

(2) Use Advance Hash

The system hashes the new value stored in the HB Password field with an advanced hash.

SymConnect or SymXchange applications and PowerOn specfiles cannot read passwords that are stored with advanced password hashing. As a result, the system displays only the masking characters when you use SymConnect or SymXchange applications or PowerOn specfiles to read the field.

Second HB Password Mode

This field stores a code that indicates the format the system uses to store a member’s second password.

Data Type Descriptions

(0) Do Not Hash Passwords

The system assumes that the value stored in the Second HB Password field is the home banking password.

(1) Use Modified MD5 Hash

The system hashes the new value stored in the Second HB Password field with a modified MD5 hash.

(2) Use Advance Hash

The system hashes the new value stored in the Second HB Password field with an advanced hash.

SymConnect or SymXchange applications and PowerOn specfiles cannot read passwords that are stored with advanced password hashing. As a result, the system displays only the masking characters when you use SymConnect or SymXchange applications or PowerOn specfiles to read the field.

Audio Access Code Mode

This field stores a code that indicates the format the system uses to store a member’s audio access code.

Data Type Descriptions

(0) Do Not Hash Passwords

The system assumes that the value stored in the Audio Access Code field is the audio access code.

(1) Use Modified MD5 Hash

The system hashes the new value stored in the Audio Access Code field with a modified MD5 hash.

(2) Use Advance Hash

The system hashes the new value stored in the Audio Access Code field with an advanced hash.

SymConnect or SymXchange applications and PowerOn specfiles cannot read passwords that are stored with advanced password hashing. As a result, the system displays only the masking characters when you use SymConnect or SymXchange applications or PowerOn specfiles to read the field.

Second Audio Access Code Mode

This field stores a code that indicates the format the system uses to store a member’s second audio access code.

Data Type Descriptions

(0) Do Not Hash Passwords

The system assumes that the value stored in the Second Audio Access Code field is the audio access code.

(1) Use Modified MD5 Hash

The system hashes the new value stored in the Second Audio Access Code field with a modified MD5 hash.

(2) Use Advance Hash

The system hashes the new value stored in the Second Audio Access Code field with an advanced hash.

SymConnect or SymXchange applications and PowerOn specfiles cannot read passwords that are stored with advanced password hashing. As a result, the system displays only the masking characters when you use SymConnect or SymXchange applications or PowerOn specfiles to read the field.

HB Previous Password Mode 01 - HB Previous Password Mode 24

These fields store a code for the past 24 HB Password Mode and Second HB Password Mode field values that indicate the format the system used to store each past home banking password.

Data Type Descriptions

(0) Do Not Hash Passwords

The system assumes that the values stored in the HB Password or Second HB Password field is the home banking password.

(1) Use Modified MD5 Hash

The system hashes the new values stored in the HB Password or Second HB Password field with a modified MD5 hash.

(2) Use Advance Hash

The system hashes the new values stored in the HB Password or Second HB Password field with an advanced hash.

SymConnect or SymXchange applications and PowerOn specfiles cannot read passwords that are stored with advanced password hashing. As a result, the system displays only the masking characters when you use SymConnect or SymXchange applications or PowerOn specfiles to read the field.

You cannot update these fields.

HB Previous Password Hash 2(24)–HB Previous Password Hash 4(24)

These fields store the second, third, and fourth hash parts of the past 24 HB Password and Second HB Password field values if you use the advance password hashing option.

When the HB/Audio Password Hash Code parameter in the Miscellaneous Parameters is set to (2) Use Advance Hash, the first part of the hash of each previous password is stored in the HB Password or Second HB Password field and the other parts are stored in these fields.

Since there are 24 previous passwords for each of these three fields, there are a total of 72 fields represented here.

You cannot read or update these fields.