teletrack uk frequently asked questions€¦ · frequently asked questions . teletrack us faq....

Frequently Asked Questions Teletrack US FAQ

Confidential

Version: 1.22 Last Updated On: Sept 30, 2013 Prepared By: Jonathan Levin

This document contains confidential and proprietary business information belonging to CoreLogic Teletrack, and is only distributed in accordance with a

signed confidentiality agreement. Any use or distribution not expressly allowed by the confidentiality agreement is strictly prohibited.

Teletrack is a registered trademark of CoreLogic.

© 2013 CORELOGIC TELETRACK PROPRIETARY & CONFIDENTIAL

Table of Contents 1. Overview ................................................................................................................. 1 2. Password Expiration ............................................................................................... 1

How frequently will my username’s password expire?................................................... 1 Will I be notified when my username password is set to expire? ................................... 1

3. Data ......................................................................................................................... 4 When should I send a previous Address to Teletrack? .................................................... 4 Do I get charged for each address sent to Teletrack? ...................................................... 4 How do I use Request Types in Teletrack? ..................................................................... 4 If I send a Request Type, will I automatically receive the information requested? ........ 5 Which elements will I receive based upon these request types? ..................................... 6

4. Loan Reporting ....................................................................................................... 9 When should I report a loan to Teletrack? ...................................................................... 9 How do I report a loan to Teletrack? ............................................................................. 10 Should I send the TransactionCode when reporting a loan? ......................................... 10 What is the difference between a status of Active and one of Open? ........................... 10 How does Teletrack determine the original loan amount of a loan? ............................. 11 What elements are necessary for reporting new loans and loan updates? ..................... 11 What is the typical flow of a Payday Loan? .................................................................. 15 What is the typical flow of an Installment, Auto Equity or Simple Interest Loan? ...... 18 How should I handle the Charge Off of a Loan? ........................................................... 19 What is the Difference Between “Void” and “Rescind”? ............................................. 19 What does the message “Disputed Tradeline Deleted” mean? ...................................... 19

5. Authentication Variables ...................................................................................... 19 What are Authentication Variables and how are they used? ......................................... 20 How are the variables and sub-variables related? ......................................................... 20

6. Credit Variables .................................................................................................... 23 What are Credit Variables? ............................................................................................ 23 How are Credit Variables billed? .................................................................................. 31

7. Scoring Changes ................................................................................................... 32 How is scoring now calculated to determine most important factors? .......................... 32 What if there are fewer than four negatively scored variables? .................................... 32 What if there are four or more negatively scored variables? ......................................... 32 What is the score range? ................................................................................................ 32

8. Follow-On Transactions........................................................................................ 33 What is the definition of a follow-on transaction? ........................................................ 33 When would I want to use a follow-on transaction? ..................................................... 33 How do I send a follow-on transaction? ........................................................................ 33 What rules govern the use of follow-on transactions? .................................................. 33

9. Third Party Data .................................................................................................... 34 What is a Third Party Data? .......................................................................................... 34 What information will I need to furnish in order to receive a Third Party Data? ......... 34

10. XML Versioning ................................................................................................... 35 What is XML versioning? ............................................................................................. 35 What is the best approach for me? ................................................................................. 35 Will my existing software continue to work? ................................................................ 35

© 2013 CORELOGIC TELETRACK PROPRIETARY & CONFIDENTIAL

How do I identify the version of XML that I am using? ............................................... 35 11. Connecting with Teletrack .................................................................................... 36

How do I connect to Teletrack using PHP code? .......................................................... 36 How do I connect to Teletrack using Visual Studio 2005? ........................................... 38 How do I connect to Teletrack using Visual Studio 2008? ........................................... 46

Teletrack US FAQ Frequently Asked Questions Version 1.22 09/30/2013

© 2013 CORELOGIC TELETRACK PAGE 1 PROPRIETARY & CONFIDENTIAL

1. Overview This document is intended to provide answers to questions and advice on making your integration with CoreLogic® Teletrack™’s software as productive as possible. It is divided into several areas to identify what you need to provide, the best approaches to providing the most useful data, application design, and interpretation of results.

2. Password Expiration How frequently will my username’s password expire? Will I be notified when my username password is set to expire?

How frequently will my username’s password expire? There are two system settings used for password expiration: one for Teletrack Online usernames and one for system-to-system usernames. These two settings will typically force online users to change their passwords more frequently than system-to-system users. The current settings for these are 45 days for online users and 90 days for system-to-system users.

Will I be notified when my username password is set to expire? If you are a Teletrack Online user, you will not receive a notification. At the point that the password expires, you will be sent to a screen that allows you to change your password. See the Teletrack Online User Manual for details. If you have a system-to-system XMLUser username, an email will be sent identifying that it is time to change the password. The email will appear as:



You will be given a period of fifteen days during which you will need to log onto the Teletrack Online system and modify your password. This is performed as follows:

• Follow the link supplied in the email. You will be taken to the Teletrack Online login screen:

• Enter the User Name and current Password for the XML User for your Subscriber ID and press Login

• You will be taken to the following screen:



This screen identifies your Subscriber ID (34247 shown above) and identifies that you are creating the new password for username x (merchant_34247 shown above).

• Press the Reset Password button to get a new password. • The system will create a new password and display it as:

The new and old password may both be used until the old password expires. This will give you time to institute the changed password in your application.

• When completed, copy the new password and press Log Out.



3. Data When should I send a previous address to Teletrack? Do I get charged for each address sent to Teletrack? How do I use Request Types in Teletrack? If I send a Request Type, will I automatically receive the information requested? Which elements will I receive based upon these request types? What does the message “Disputed Tradeline Deleted” mean?

When should I send a previous Address to Teletrack? An address is one of the primary data elements that let Teletrack identify an individual. A previous address is always useful, but it is especially important if the consumer moved within the last year. Teletrack does not charge additionally for each address, so it is always useful to provide this information.

Do I get charged for each address sent to Teletrack? Teletrack encourages its clients to submit all known addresses for an individual. Teletrack does not charge any additional fee for previous addresses.

How do I use Request Types in Teletrack? A Request Type in Teletrack is equivalent to asking for the information you wish to receive and, in some cases, what form that information should take. There are several Request Types in Teletrack, each with its own meaning: Request Type Meaning "Inquiry" This will perform a Credit Inquiry, returning the information in

the form of raw XML data. "ID Verification" This will perform ID verification, returning a score and warnings.

This is not a standalone request type and must be accompanied by either “Inquiry” or “Text Report”.

"State" Future “Score” Future (currently not standalone, incorporated within Inquiry and

Text Report) “Underwriting” This will utilize a customer’s underwriting model to approve or

deny a loan, identify the amount to be lent and return that together with denial reasons to the merchant.

“OFAC” future (currently incorporated within Inquiry and Text Report)



Request Type Meaning “Text Report” This will perform a Credit Inquiry and return the information in

the form of a text report. “Checking Data” This will validate the account information sent and return that

validation together with historical information for the consumer and the account. This is not a standalone request type and must be accompanied by either “Inquiry” or “Text Report”.

“Third Party Data” This will contact one of several Third Party vendors to obtain additional information on a consumer. More than one Third Party Data request may be made as part of a single transaction or through follow-on transactions. (See additional information below.)

“Variables” This will provide consumer information from specific variables that are part of your contract. This is not a standalone request type and must be accompanied by either “Inquiry” or “Text Report”. The list of available variables may be found in an appendix of the XML Interface Manual.

Although “Score” and “OFAC” are listed for “future” use, you will still receive Score and OFAC results if you have subscribed to them. The “future” use envisions a cafeteria approach that would allow you to request only responses to the specific services that you wish for a particular inquiry. Teletrack recommends that you include these RequestTypes together with the Inquiry or Text Report RequestTypes so that you will seamlessly integrate with the future implementation of this cafeteria approach.

If I send a Request Type, will I automatically receive the information requested? No. You must be configured for the appropriate service, provide the appropriate input and, in some cases, be a contributor of the information you are requesting. The table below shows these requirements: Request Type Requirements "Inquiry" 1. Sign up for Basic Service

2. Request “Inquiry” "ID Verification" (an inquiry must be requested)

1. Sign up for Basic Service and ID Verification 2. Request one or more of:

a. “Inquiry” b. “Text Report” c. “Underwriting”

3. Request “ID Verification” "State" Future “Score” Future (currently not standalone, incorporated within Inquiry and

Text Report)



Request Type Requirements “Underwriting” (an inquiry must be requested)

1. Sign up for Basic Service, Scoring, Underwriting and possibly Extended Underwriting.

2. Have a Scorecard 3. Request “Inquiry” and “Underwriting” 4. Include those attributes from Salary, BankAccounts and

ApplicationCredit that are relevant to your Scorecard 5. Include those attributes from Loan Application that are

relevant to your Scorecard 6. Include Request Option for “Payday” and/or

“AlternativeLoan” “OFAC” future (currently incorporated within Inquiry and Text Report) “Text Report” 1. Sign up for Basic Service

2. Request “Text Report” “Checking Data” (an inquiry must be requested)

1. Sign up for Basic Service and Checking Data 2. Request both “Inquiry” and “Checking Data” or “Text

Report” and “Checking Data” 3. Include RoutingNumber and AccountNumber in

BankAccounts “Third Party Data” (an inquiry must be requested with this transaction or this may be part of a follow-on transaction – see below)

1. Sign up for Basic Service and for the service for the vendor 2. Request one or more of:


3. Add “Third Party Data” either to the initial request or send it as a follow-on request. (See additional information below.)

“Variables” (an inquiry must be requested)

1. Sign up for Basic Service and Variables service 2. Configure with your Sales Representative which variables

will be received 3. Request one or more of:


4. Request “Variables”

Which elements will I receive based upon these request types? The information presented in the table below is cumulative. Namely, if you request both “ID Verification” and “Inquiry”, you will see the elements identified for each. Where these represent the same elements, it is possible that additional attributes will accompany these elements based upon the requests made. Request Type Add-On Elements Returned



Request Type Add-On Elements Returned "Inquiry" Example: <Request RequestType="Inquiry"/> <Request RequestType="Inquiry"/> <Request RequestType="Text Report"/> <Request RequestType="Inquiry"/> <Request RequestType="ID Verification"/> <Request RequestType="Inquiry"/> <Request RequestType="Checking Data"/> <Request RequestType="Inquiry"/> <Request RequestType="Variables"/> <Request RequestType="Inquiry"/> <Request RequestType="Third Party Data"/>

TransactionResponse Subscriber RequestDetails ConsumerCreditReport Uin Name BirthDate AliasList AddressList ChargeOffs PreviousInquiries SkipGuards Accounts (if eligible1 for Positive Data) PublicRecordData Evictions (if subscribed) Bankruptcies (if subscribed) Judgments UINValidation Scores2 Alerts OFAC (if subscribed) ConsumerStatements OnFileSince TransactionNumber CustomerReferenceNumber TransactionErrors TransactionDateTime Teletrack XMLVersion

“Text Report” TextReport3 "ID Verification"

Scores2 IDVResponse (if subscribed)

“Checking Data”

CheckingData (if subscribed)

“Third Party Data”

ThirdPartyData (if subscribed)

“Variables” Variables (if subscribed)



Request Type Add-On Elements Returned “Underwriting” <Request RequestType="Inquiry"/> RequestType="Underwriting"> <tt:RequestOption Name="Payday" /> </Request> (This request must include “Inquiry” in order to return the Score) <Request RequestType="Inquiry"/> RequestType="Underwriting"> <tt:RequestOption Name="Payday" /> RequestType="Third Party Data"/> </Request> <Request RequestType="Inquiry"/> RequestType="Underwriting"> <tt:RequestOption Name="Payday" /> RequestType="Variables"/> </Request>

Scores TeletrackScore FICOScore (if alternative loan & requesting response from Bureau) FACTA Alerts (if alternative loan & requesting response from Bureau) LoanApplicationResponse



“Variables” Variables (if subscribed)

“Text Report” <Request RequestType="Text Report"/> <Request RequestType="Text Report"/> <Request RequestType="ID Verification"/> <Request RequestType="Text Report"/> <Request RequestType="Checking Data"/> <Request RequestType="Text Report"/> <Request RequestType="Third Party Data"/>

TransactionResponse Subscriber RequestDetails ConsumerCreditReport Uin Name BirthDate AliasList AddressList TextReport3 TransactionErrors TransactionDateTime Teletrack XMLVersion

"ID Verification"

TextReport4 (if subscribed)

“Checking Data”

TextReport5 (if subscribed)





Request Type Add-On Elements Returned “Third Party Data” <Request RequestType="Third Party Data" RequestOption name="vendor" value="vendorname"/> where vendorname is the specific name of the vendor appropriate for the Third Party (other options may be needed) (as part of follow-on transaction)

TransactionResponse Subscriber RequestDetails ConsumerCreditReport Uin Name BirthDate AliasList AddressList ThirdPartyData6 TransactionErrors TransactionDateTime Teletrack XMLVersion

1 To be eligible for Positive Data (current loans and loan history), you must report your loan data to Teletrack. See your account representative. 2 The Score RequestType cannot currently be requested in standalone mode. It must be accompanied by either “Inquiry” or “Text Report”. A future release will provide the flexibility to request only the information from Scoring. 3 The Text Report contains either separate reports or a consolidated report (depending on your configuration) for all of the consumer information available under the ConsumerCreditReport for which the merchant is eligible. 4 The Text Report also includes the IDV Report 5 The Text Report also includes the Checking Data Report 6 A separate ThirdPartyData will be included for each vendor.

4. Loan Reporting When should I report a loan to Teletrack? How do I report a loan to Teletrack? Should I send the TransactionCode when reporting a loan? What is the difference between a status of Active and one of Open? How does Teletrack determine the original loan amount of a loan? What elements are necessary for reporting new loans and loan updates? What is the typical flow of a Payday Loan? What is the typical flow of an Installment, Auto Equity or Simple Interest Loan? How should I handle the Charge Off of a Loan? What is the Difference Between “Void” and “Rescind”?

When should I report a loan to Teletrack? Current status of outstanding obligations is both a positive and a negative sign for a consumer. It is an indication that the consumer was trusted for the extension of a loan, but too much outstanding debt could warn a merchant against issuing a loan to the



consumer. Because of this, it is extremely helpful to share accurate current information on consumers’ activities among merchants. As a CRA, Teletrack contractually requires customers to report all loans that are issued at the time that they are issued and that you update their current statuses as these statuses change. Your participation in contributing this information will allow you to become eligible to receive current loan information and history on your consumers and improve the risk assessment that you make. Only those merchants who contribute loan information will be able to see the loan information provided by other merchants. Teletrack offers a positive data service that allows you to see current account information on consumers. Please contact your Sales Representative for additional information.

How do I report a loan to Teletrack? The TeletrackReporting schema should be used to report loan transactions. You will need to furnish both the consumer information and the loan information. The schema identifies several data elements that are required and others that may not be relevant to the type of loan or to the status of the loan. For example, DueDate is a required field, but ClosedDatetime is not required until the loan is Paid or Closed. The combination of three elements determines the uniqueness of a loan – SubscriberID, SSN and AccountNumber. The AccountNumber is the loan number that you, the merchant, have assigned to the loan. All references to a specific loan must include these three elements.

Should I send the TransactionCode when reporting a loan? Yes, if the loan was issued following an inquiry to Teletrack. Any time you have utilized Teletrack information in determining whether to grant a loan, the TransactionCode from that Inquiry should be sent with the loan. This is currently required when submitting a loan. If you previously performed an inquiry on the consumer, even if that was not in conjunction with this loan request, it is possible to submit that TransactionCode and successfully submit the loan. This is particularly appropriate when you are renewing a loan or issuing a consecutive loan and do not need to recertify the consumer’s credit position.

What is the difference between a status of Active and one of Open? When a loan is created, it should be reported as “Active”. This should continue until its DueDate. A merchant may choose to grant its consumers a grace period before reporting the loan as being in default. Sending Teletrack a status update of “Open” indicates that



the merchant has actively reviewed the loan and granted a grace period. He has not extended the DueDate, but he has allowed the consumer to pay the loan without issuing a charge off.

How does Teletrack determine the original loan amount of a loan? When you first submit a loan to Teletrack, Teletrack will take the OriginalBalance (or the CurrentBalance if no OriginalBalance was submitted) and use this as the original amount of the loan. Teletrack allows you to correct an improperly entered OriginalBalance if you update the loan on the same day on which it was initially reported. After that time, this original loan amount will remain constant throughout, although the CurrentBalance will change with each payment or additional service charge.

What elements are necessary for reporting new loans and loan updates? The most relevant elements to furnish as part of Loan Reporting (other than the demographic information) are: Legend State Systems Only Installment Loans, Auto Equity Loans and Simple Interest Loans Only Table 1 Element or Attribute Definition When to Send

Loan LoanType Unless told otherwise,

use either Payday, Installment, Auto Equity or Simple Interest

Always

OpenDatetime The actual date and time that the loan was issued

Always

OriginalBalance The initial amount of the loan including all fees

Must be sent with the first reporting of this loan. May be sent each time.

Fees The fees associated with this loan. If not under state governance, you should send zero.

Must be sent with the first reporting of this loan in a state governance environment. May be sent each time. May be ignored in states that are not governed by a state system.

OtherFeeAmount May be used to indicate an NSF charge

Optional



Element or Attribute Definition When to Send OtherFeeType Free-form description of

the type of fee above Optional

DueDate The Maturity Date of the loan

Must be sent with the first reporting of this loan. May be sent each time.

CurrentBalance The amount outstanding on the loan, including all fees.

Must be sent every time an update is made on the loan. Should be zero when the loan is paid off.

ClosedDatetime The date and time on which the loan is paid in full or written off

Must be sent when the loan is paid. Should not be sent unless the loan is paid or written off

NumberOfPaymentsScheduled The number of scheduled payments for an Installment, Auto Equity or Simple Interest loan

Should only be sent when an Installment, Auto Equity or Simple Interest loan is first reported

PaymentFrequency The frequency of scheduled payments. Must be Daily, Weekly, Biweekly, Semimonthly or Monthly.


PaymentAmount The amount of each payment for an Installment, Auto Equity or Simple Interest loan


AccountStatus The current status of the loan. Must be one of Active, Paid, Chargeoff, Void, Rescinded (state only), NSF (state only), or Open

This must be sent when the loan is reported and every time an update is made on the loan.

TransactionNumber The TransactionNumber returned by Teletrack as part of the Inquiry

Must be sent every time an update is made on the loan.

AccountNumber The account number assigned by you to the account. This is one of the keys to the account and must be furnished always.

Must be sent every time an update is made on the loan.

PastDueAmount Not used LastPaymentDate The date of the last

payment for an Installment, Auto Equity or Simple Interest loan

Should only be sent when an Installment, Auto Equity or Simple Interest loan is updated



Element or Attribute Definition When to Send ActualPaymentAmount The payment made

against an Installment, Auto Equity or Simple Interest loan

Should only be sent when an Installment, Auto Equity or Simple Interest loan is updated

StateCode The two-character abbreviation of the state.

This is only used when the loan is under state governance. If it is, this must be sent with each update of the loan.

ReasonCode Not used TransactionDatetime This is the actual date

and time of the consumer transaction as opposed to the date and time that the transaction is being reported.

This should be sent when the loan is reported and every time an update is made on the loan. It is particularly necessary if the loan status is being reported significantly later than the actual occurrence of the change in status.

PaymentMethod Not used CheckNumber The number of the check

if payment is made by check

Should be sent if payment is made by check

DelinquencyStatus The payment status of the loan. This must be one of Current, 30 Days, 60 Days, 90 Days, 120 Days, 150 Days, >=180 Days.

This must be sent for every submission and status update for an Installment, Auto Equity or Simple Interest loan.

DateOfFirstDelinquency The first date on which the loan entered a status of delinquent and remained that way. If the loan regained a “Current” status, this value is reset and is not used unless the loan re-enters its delinquent state. It then reflects that new date.

This field is required if the DelinquencyStatus above is not “Current”.



Element or Attribute Definition When to Send ECOAIndicator The Equal Credit

Opportunity Act indicator. This must be one of: I = Individual J = Joint Contractual Liability M = Maker T = Association Terminated X = Deceased U = Undesignated Z = Delete Consumer

This is required for any submission of an Installment, Auto Equity or Simple Interest loan

ComplianceConditionCode This is the FCRA compliance code. It may be one of the following: Blank – retains previously reported value or no new compliance condition code applies for this period XA: Account Closed at Consumer Request XB: Account Information disputed by consumer under the FCRA XC: Completed FCRA dispute investigation – consumer disagrees XD: Account closed at the consumer & in dispute under FCRA XE: Account closed at consumer request, dispute investigation completed, consumer disagrees XF – Account in dispute under FCBA XG – FCBA dispute resolved – consumer disagrees XH – Account previously disputed – now resolved XJ – Account closed at consumer request and disputed under FCBA XR – Removes the most recently reported Compliance Condition Code

This is an optional field for an Installment, Auto Equity or Simple Interest loan



Element or Attribute Definition When to Send DateReported This is the report date for

this transaction. If this is a snapshot, this will be the date of the snapshot. If this is left blank, the system will assume today’s date.

This should be sent for an Installment, Auto Equity or Simple Interest loan whenever the date is other than today’s date.

BankAccount Statement Not used in transaction

reporting. This is part of the BankAccount node.

StatementDate Not used in transaction reporting. This is part of the BankAccount node.

NumberOfTransactions Not used in transaction reporting. This is part of the BankAccount node.

NumberOfNSFs Not used in transaction reporting. This is part of the BankAccount node.

Balance Not used in transaction reporting. This is part of the BankAccount node.

BankName The name of the Financial Institution on the check


BankPhoneNumber The phone number of the Financial Institution on the check


RoutingNumber The routing number of the Financial Institution on the check


AccountNumber The account number on the check


AccountType The type of account – Checking, Savings, Money Market or Other


Ownership Single or Joint Should be sent if payment is made by check

What is the typical flow of a Payday Loan? The typical flow of a Payday loan that does not encounter a charge off or NSF issue is the following:

1. Inquire on the Consumer The consumer should have been verified through an earlier inquiry. This inquiry need not take place immediately prior to the issuance of the loan. This



is particularly true when the consumer is well known to the subscriber and has a satisfactory payment history with the subscriber. The most recent inquiry on the consumer will have returned a TransactionCode, which should be stored and used in the issuance of the loan.

2. Issue the Loan Open the loan with the consumer and send the following information to Teletrack together with the consumer information:

• LoanType = “Payday” • OpenDatetime = timestamp at the actual issue of the loan (even if

that was several days earlier) • OriginalBalance = 325.50 or the actual balance including all fees • Fees = 15.50 (Only if this is a state system) • DueDate = date on which loan should be paid • CurrentBalance = 325.50 • AccountStatus = “Active” • TransactionNumber = “TZ10S3”. This should be the

TransactionNumber from the most recent inquiry. • AccountNumber = “J12389-55498”. This should be the account

number that you have assigned to the loan. • State = “AL”. This should only be sent for a state system.

3. Accept a Partial Payment If it is your policy to accept partial payment, you should update the loan at the time that the partial payment is made. Using the example above, consider a partial payment of $150. The following information should be sent to Teletrack. CurrentBalance changes to reflect the new amount and TransactionDatetime reflects the date and time of the payment:


that was several days earlier) • OriginalBalance = 325.50 or the actual balance including all fees • Fees = 15.50 (Only if this is a state system) • DueDate = date on which loan should be paid • CurrentBalance = 275.50 • AccountStatus = “Active” • TransactionNumber = “TZ10S3”. This should be the


number that you have assigned to the loan. • State = “AL”. This should only be sent for a state system. • TransactionDatetime = timestamp of the actual payment against the

loan 4. Payment of the Loan

The following information should be sent to Teletrack. CurrentBalance changes to zero (full payment), AccountStatus is changed to “Paid” and ClosedDatetime reflects the date and time that the loan is paid off:




that was several days earlier) • OriginalBalance = 325.50 or the actual balance including all fees • Fees = 15.50 (Only if this is a state system) • DueDate = date on which loan should be paid • CurrentBalance = 0 • ClosedDatetime = timestamp of the actual date and time that the

consumer paid the loan • AccountStatus = “Paid” • TransactionNumber = “TZ10S3”. This should be the



loan 5. Possible Rollover of the Loan

In some cases, a loan is rolled over into a new loan. The consumer may pay a fee to effectively close the existing loan and a new loan is issued. This is accomplished through Teletrack by closing the initial loan and opening a new loan with a new DueDate and OriginalBalance. The following information should be sent to Teletrack to close the existing loan. CurrentBalance changes to zero (full payment), AccountStatus is changed to “Paid” and ClosedDatetime reflects the date and time that the loan is paid off:


that was several days earlier) • OriginalBalance = 325.50 or the actual balance including all fees • Fees = 15.50 (Only if this is a state system) • DueDate = date on which loan should be paid • CurrentBalance = 0 • ClosedDatetime = timestamp of the actual date and time that the

consumer paid the loan • AccountStatus = “Paid” • TransactionNumber = “TZ10S3”. This should be the



loan The new loan is then sent to Teletrack with the new information. The following information should be sent to Teletrack to open the new loan. A



new account number must be issued for the rollover loan rather than just changing the due date:

• LoanType = “Payday” • OpenDatetime = timestamp at the actual issue of the loan (this is the

same as the ClosedDatetime of the initial loan) • OriginalBalance = 285.50 or the actual balance including all fees for

the amount rolled over • Fees = 15.50 (Only if this is a state system) • DueDate = new date on which the rolled over loan should be paid • CurrentBalance = 285.50 • AccountStatus = “Active” • TransactionNumber = “TZ10S3”. This may be the same

TransactionNumber used with the opening of the original loan • AccountNumber = “J12389-61884”. This should be the new

account number that you have assigned to the rollover loan. • State = “AL”. This should only be sent for a state system.

This loan is then treated like a new loan with its own due date and payment history.

What is the typical flow of an Installment, Auto Equity or Simple Interest Loan? The typical flow of an Installment, Auto Equity or Simple Interest loan is identical to that of the Payday example shown above except for the addition of the following fields. Please follow the guidelines in the “Definition” and “When to Send” columns of Table 1 above.

• LoanType = “Installment” or “Auto Equity” or “Simple Interest” • NumberofPaymentsScheduled = this is a number that remains

constant throughout the process of the loan • PaymentFrequency = “Monthly” or whatever frequency at which the

payments are scheduled • PaymentAmount = 55.10 or the amount of each scheduled payment • LastPaymentDate = the date on which the most recent payment was

made. This is not sent when the loan is initially issued. • ActualPaymentAmount = the amount of the most recent payment.

This is not sent when the loan is initially issued • DelinquencyStatus = the payment status of the loan, such as

“Current” or “60 Days”. • DateOfFirstDelinquency = the first date that a loan entered into a

state of delinquency and remained there. If the loan retained a “Current” DelinquencyStatus, this date is erased. If the loan subsequently became delinquent again, this should be the new date on which it first became delinquent.



• ECOAIndicator = the Equal Credit Opportunity Act indicator. • ComplianceConditionCode = a code identifying FCRA dispute

status • DateReported = the snapshot date of the loan being reported.

How should I handle the Charge Off of a Loan? In some cases, the consumer fails to meet their financial obligation and it is desirable to issue a charge off against the loan. This is currently a two step process. In the example shown above for either a Payday or Installment loan, the most current information is sent with the following change:

• AccountStatus = “Chargeoff” The second step in the process is to send this account together with other charged off accounts in a batch file (see Automated Reporting Format ARF User Manual). This will identify the loan as a charge off even to those subscribers who do not issue loans, such as Rent-to-Own subscribers.

What is the Difference Between “Void” and “Rescind”? The status of “Rescind” connotes a circumstance in which the consumer returns the loan immediately and effectively rejects the loan after it has been issued. This is a policy issue on the part of the subscriber and may be internally limited to a grace period. Teletrack places no restrictions on the ability to do this as it is at the discretion of the subscriber. The status of “Void” connotes a loan that the subscriber issued in error. Voiding the loan will mean that Teletrack will not consider this loan as having taken place. It will not be shown to other subscribers nor to the consumer and it will not be used in any Scoring or calculations.

What does the message “Disputed Tradeline Deleted” mean? When you send in tradeline information (loan, charge off, paid charge off), the item may be disputed by the consumer. Teletrack will then investigate the tradeline in question and may reach an agreement to remove this tradeline from the system. If the tradeline is resubmitted after the disputed item is deleted, you will receive the error message “Disputed Tradeline Deleted”. This means that you may no longer submit this tradeline for updates.

5. Authentication Variables



What are Authentication Variables and how are they used? How are the variables and sub-variables related?

What are Authentication Variables and how are they used? Authentication variables examine the information presented by the consumer in the current request against previous instances of this same information presented by this or another consumer during the previous year. For example, the consumer presented their current address. The Teletrack database may contain other references to this address both for this consumer and for other consumers over the past year. It is quite feasible that another consumer lived or lives at this address and the presenting consumer may or may not have lived at this address during previous searches. The system will identify the number of instances and their timeframes both for this consumer and for other consumers. The view of how much information correlates to recent activity with the presenting consumer or other consumers can give the subscriber a picture of the potential instance of Authentication in this consumer’s presented information. It is important to realize that the information that is provided should be real and accurate. The use of a phone number that is “1111111111” or an email address of [email protected] will skew the results that you receive and may actually be masked by the system as invalid data. Email address and phone numbers are not required fields so they should not be entered at all if no valid information can be supplied.

How are the variables and sub-variables related? Each variable represents the initial element in the correlation. All the searches that were performed referencing this element in the previous year are identified. These instances are then used to correlate each sub-variable to the use of the variable. For example, the consumer indicates that they live at 123 Chase Blvd, Baton Rouge, LA and that their email address is [email protected]. The system would then identify how many times when a consumer used 123 Chase Blvd, Baton Rouge, LA as their address did they also identify their email address as [email protected] and how many times did they identify that their email address was some other value other than blanks or nulls. It is this correlation that represents the crux of the Authentication variables. The table below shows the variables in the main header and the sub-variables below each variable. It also shows the time frames that are examined.

AUTHENTICATION VARIABLES

Number of Occurrences Past

Minute Past 5

Minutes Past Hour

Past 12

Hours

Past Day

Past Week

Past Month

Past Quarter

Past Year

Social Security Number:

mailto:[email protected]







Minute Past 5

Minutes Past Hour

Past 12

Hours

Past Day

Past Week

Past Month

Past Quarter

Past Year

Same Person Different Person/Different Lastname Different Person/Same Lastname Same Current Address Different Current Address Same Phone Different Phone Same Employer Phone Different Employer Phone

Same Routing Number Different Routing Number Same Bank Account Number Different Bank Account Number Same Email Address Different Email Address Current Address: Same Person Different Person/Different Lastname Different Person/Same Lastname Same Phone Different Phone Same Employer Phone Different Employer Phone Same Routing Number Different Routing Number Same Bank Account Number Different Bank Account Number Same Email Address Different Email Address Home Telephone: Same Person Different Person/Different Lastname Different Person/Same Lastname Same Current Address Different Current Address Same Email Address Different Email Address





Minute Past 5

Minutes Past Hour

Past 12

Hours

Past Day

Past Week

Past Month

Past Quarter

Past Year

Same Employer Phone Different Employer Phone Same Routing Number Different Routing Number Same Bank Account Number Different Bank Account Number Work Telephone: Same Person Different Person/Different Lastname Different Person/Same Lastname Same Current Address Different Current Address Same Email Address Different Email Address Same Home Phone Different Home Phone Same Routing Number Different Routing Number Same Bank Account Number Different Bank Account Number Bank Account: Same Person Different Person/Different Lastname Different Person/Same Lastname Same Email Address Different Email Address Same Home Phone Different Home Phone Same Employer Phone Different Employer Phone EMail Address: Same First name/Last name Same Last name Different First name/Last name Same Home Phone Different Home Phone Same Employer Phone





Minute Past 5

Minutes Past Hour

Past 12

Hours

Past Day

Past Week

Past Month

Past Quarter

Past Year

Different Employer Phone Date of Birth: Name Match - Same Birthdate Name Match - Different Birthdate

6. Credit Variables What are Credit Variables? How are Credit Variables billed?

What are Credit Variables? Credit variables are established by configuration for each merchant who has contracted for Credit Variables. A maximum of fifty (50) variables may be engaged at a single time, but the specific variables returned may be modified at any point through a merchant’s configuration. The following variables are available for configuration: # Name Variable Description Charge Offs 001 TT_OCALL00 Total Open Chargeoffs 002 TT_OCRS00 Open Chargeoffs - Rent to Own Industry 003 TT_OCCA00 Open Chargeoffs - Check Advance Industry 004 TT_OCCB00 Open Chargeoffs - Cable TV Industry 005 TT_OCAF00 Open Chargeoffs - Auto Finance Industry 006 TT_OCOT00 Open Chargeoffs - Other Industries 007 TT_OCALL03 Open Chargeoffs - Past 3 months 008 TT_OCRS03 Open Chargeoffs - Rent to Own Industry - Past 3 months 009 TT_OCCA03 Open Chargeoffs - Check Advance Industry - Past 3 months 010 TT_OCCB03 Open Chargeoffs - Cable TV Industry - Past 3 months 011 TT_OCAF03 Open Chargeoffs - Auto Finance Industry - Past 3 months 012 TT_OCOT03 Open Chargeoffs - Other Industries - Past 3 months 013 TT_OCALL06 Open Chargeoffs - Past 6 months 014 TT_OCRS06 Open Chargeoffs - Rent to Own Industry - Past 6 months 015 TT_OCCA06 Open Chargeoffs - Check Advance Industry - Past 6 months 016 TT_OCCB06 Open Chargeoffs - Cable TV Industry - Past 6 months 017 TT_OCAF06 Open Chargeoffs - Auto Finance Industry - Past 6 months 018 TT_OCOT06 Open Chargeoffs - Other Industries - Past 6 months 019 TT_OCALL09 Open Chargeoffs - Past 9 months 020 TT_OCRS09 Open Chargeoffs - Rent to Own Industry - Past 9 months



# Name Variable Description 021 TT_OCCA09 Open Chargeoffs - Check Advance Industry - Past 9 months 022 TT_OCCB09 Open Chargeoffs - Cable TV Industry - Past 9 months 023 TT_OCAF09 Open Chargeoffs - Auto Finance Industry - Past 9 months 024 TT_OCOT09 Open Chargeoffs - Other Industries - Past 9 months 025 TT_OCALL12 Open Chargeoffs - Past 12 months 026 TT_OCRS12 Open Chargeoffs - Rent to Own Industry - Past 12 months 027 TT_OCCA12 Open Chargeoffs - Check Advance Industry - Past 12 months 028 TT_OCCB12 Open Chargeoffs - Cable TV Industry - Past 12 months 029 TT_OCAF12 Open Chargeoffs - Auto Finance Industry - Past 12 months 030 TT_OCOT12 Open Chargeoffs - Other Industries - Past 12 months 031 TT_OCALL24 Open Chargeoffs - Past 24 months 032 TT_OCRS24 Open Chargeoffs - Rent to Own Industry - Past 24 months 033 TT_OCCA24 Open Chargeoffs - Check Advance Industry - Past 24 months 034 TT_OCCB24 Open Chargeoffs - Cable TV Industry - Past 24 months 035 TT_OCAF24 Open Chargeoffs - Auto Finance Industry - Past 24 months 036 TT_OCOT24 Open Chargeoffs - Other Industries - Past 24 months 037 TT_INQALL00 Total Inquiries 038 TT_INQRS00 Inquiries - Rent to Own Industry 039 TT_INQCA00 Inquiries - Check Advance Industry 040 TT_INQCB00 Inquiries - Cable TV Industry 041 TT_INQAF00 Inquiries - Auto Finance Industry 042 TT_INQOT00 Inquiries - Other Industries 043 TT_INQALL03 Inquiries - Past 3 months 044 TT_INQRS03 Inquiries - Rent to Own Industry - Past 3 months 045 TT_INQCA03 Inquiries - Check Advance Industry - Past 3 months 046 TT_INQCB03 Inquiries - Cable TV Industry - Past 3 months 047 TT_INQAF03 Inquiries - Auto Finance Industry - Past 3 months 048 TT_INQOT03 Inquiries - Other Industries - Past 3 months 049 TT_INQALL06 Inquiries - Past 6 months 050 TT_INQRS06 Inquiries - Rent to Own Industry - Past 6 months 051 TT_INQCA06 Inquiries - Check Advance Industry - Past 6 months 052 TT_INQCB06 Inquiries - Cable TV Industry - Past 6 months 053 TT_INQAF06 Inquiries - Auto Finance Industry - Past 6 months 054 TT_INQOT06 Inquiries - Other Industries - Past 6 months 055 TT_INQALL09 Inquiries - Past 9 months 056 TT_INQRS09 Inquiries - Rent to Own Industry - Past 9 months 057 TT_INQCA09 Inquiries - Check Advance Industry - Past 9 months 058 TT_INQCB09 Inquiries - Cable TV Industry - Past 9 months 059 TT_INQAF09 Inquiries - Auto Finance Industry - Past 9 months 060 TT_INQOT09 Inquiries - Other Industries - Past 9 months 061 TT_INQALL12 Inquiries - Past 12 months 062 TT_INQRS12 Inquiries - Rent to Own Industry - Past 12 months 063 TT_INQCA12 Inquiries - Check Advance Industry - Past 12 months 064 TT_INQCB12 Inquiries - Cable TV Industry - Past 12 months 065 TT_INQAF12 Inquiries - Auto Finance Industry - Past 12 months 066 TT_INQOT12 Inquiries - Other Industries - Past 12 months



# Name Variable Description 067 TT_INQALL24 Inquiries - Past 24 months 068 TT_INQRS24 Inquiries - Rent to Own Industry - Past 24 months 069 TT_INQCA24 Inquiries - Check Advance Industry - Past 24 months 070 TT_INQCB24 Inquiries - Cable TV Industry - Past 24 months 071 TT_INQAF24 Inquiries - Auto Finance Industry - Past 24 months 072 TT_INQOT24 Inquiries - Other Industries - Past 24 months Paid Charge Offs 073 TT_PCALL00 Total Paid Chargeoffs 074 TT_PCRS00 Paid Chargeoffs - Rent to Own Industry 075 TT_PCCA00 Paid Chargeoffs - Check Advance Industry 076 TT_PCCB00 Paid Chargeoffs - Cable TV Industry 077 TT_PCAF00 Paid Chargeoffs - Auto Finance Industry 078 TT_PCOT00 Paid Chargeoffs - Other Industries 079 TT_PCALL03 Paid Chargeoffs - Past 3 months 080 TT_PCRS03 Paid Chargeoffs - Rent to Own Industry - Past 3 months 081 TT_PCCA03 Paid Chargeoffs - Check Advance Industry - Past 3 months 082 TT_PCCB03 Paid Chargeoffs - Cable TV Industry - Past 3 months 083 TT_PCAF03 Paid Chargeoffs - Auto Finance Industry - Past 3 months 084 TT_PCOT03 Paid Chargeoffs - Other Industries - Past 3 months 085 TT_PCALL06 Paid Chargeoffs - Past 6 months 086 TT_PCRS06 Paid Chargeoffs - Rent to Own Industry - Past 6 months 087 TT_PCCA06 Paid Chargeoffs - Check Advance Industry - Past 6 months 088 TT_PCCB06 Paid Chargeoffs - Cable TV Industry - Past 6 months 089 TT_PCAF06 Paid Chargeoffs - Auto Finance Industry - Past 6 months 090 TT_PCOT06 Paid Chargeoffs - Other Industries - Past 6 months 091 TT_PCALL09 Paid Chargeoffs - Past 9 months 092 TT_PCRS09 Paid Chargeoffs - Rent to Own Industry - Past 9 months 093 TT_PCCA09 Paid Chargeoffs - Check Advance Industry - Past 9 months 094 TT_PCCB09 Paid Chargeoffs - Cable TV Industry - Past 9 months 095 TT_PCAF09 Paid Chargeoffs - Auto Finance Industry - Past 9 months 096 TT_PCOT09 Paid Chargeoffs - Other Industries - Past 9 months 097 TT_PCALL12 Paid Chargeoffs - Past 12 months 098 TT_PCRS12 Paid Chargeoffs - Rent to Own Industry - Past 12 months 099 TT_PCCA12 Paid Chargeoffs - Check Advance Industry - Past 12 months 100 TT_PCCB12 Paid Chargeoffs - Cable TV Industry - Past 12 months 101 TT_PCAF12 Paid Chargeoffs - Auto Finance Industry - Past 12 months 102 TT_PCOT12 Paid Chargeoffs - Other Industries - Past 12 months 103 TT_PCALL24 Paid Chargeoffs - Past 24 months 104 TT_PCRS24 Paid Chargeoffs - Rent to Own Industry - Past 24 months 105 TT_PCCA24 Paid Chargeoffs - Check Advance Industry - Past 24 months 106 TT_PCCB24 Paid Chargeoffs - Cable TV Industry - Past 24 months 107 TT_PCAF24 Paid Chargeoffs - Auto Finance Industry - Past 24 months 108 TT_PCOT24 Paid Chargeoffs - Other Industries - Past 24 months Public Record Data 109 TT_NLT Occurrence of Negative Landlord/Tenant Court Records 110 TT_BKALL Occurrence of Bankruptcies



# Name Variable Description 111 TT_BK07 Occurrence of Bankruptcies - Chapter 7 112 TT_BK13 Occurrence of Bankruptcies - Chapter 13 Other 113 TT_MOL Occurrence of Multiple Outstanding Loans 114 TT_OL Open Loans 115 TT_RECINQM Months Since Most Recent Inquiry 116 TT_DSSN Deceased SSN 117 TT_ISSN Invalid SSN 118 TT_RSSN Recent Issue SSN Inquiries (Credit Card Industry) 119 TT_INQCR00 Inquiries – Credit Card Industry 120 TT_INQCR03 Inquiries – Credit Card Industry – Past 3 months 121 TT_INQCR06 Inquiries – Credit Card Industry – Past 6 months 122 TT_INQCR09 Inquiries – Credit Card Industry – Past 9 months 123 TT_INQCR12 Inquiries – Credit Card Industry – Past 12 months 124 TT_INQCR24 Inquiries – Credit Card Industry – Past 24 months Other 125 TT_PL Paid Loans

126 TT_RECINQM_XCR Months Since Most Recent Inquiry (No Credit Card Inquiries)

Open Charge Offs 127 TT_OCALL007 Total number of open charge offs - Past 7 days 128 TT_OCALL014 Total number of open charge offs - Past 14 days 129 TT_OCALL030 Total number of open charge offs - Past 30 days 130 TT_OCALL060 Total number of open charge offs - Past 60 days 131 TT_OCSF000 Total number of Check Advance Storefront Charge offs 132 TT_OCSF007 Total number of Check Advance Storefront Charge offs - Past 7 Days 133 TT_OCSF014 Total number of Check Advance Storefront Charge offs - Past 14 Days 134 TT_OCSF030 Total number of Check Advance Storefront Charge offs - Past 30 Days 135 TT_OCSF060 Total number of Check Advance Storefront Charge offs - Past 60 Days 136 TT_OCSF090 Total number of Check Advance Storefront Charge offs - Past 90 Days 137 TT_OCSF180 Total number of Check Advance Storefront Charge offs - Past 180 Days 138 TT_OCSF270 Total number of Check Advance Storefront Charge offs - Past 270 Days 139 TT_OCSF365 Total number of Check Advance Storefront Charge offs - Past 365 Days 140 TT_OCSF730 Total number of Check Advance Storefront Charge offs - Past 730 Days 141 TT_OCIN000 Total number of Check Advance Internet Charge offs 142 TT_OCIN007 Total number of Check Advance Internet Charge offs - Past 7 Days 143 TT_OCIN014 Total number of Check Advance Internet Charge offs - Past 14 Days 144 TT_OCIN030 Total number of Check Advance Internet Charge offs - Past 30 Days 145 TT_OCIN060 Total number of Check Advance Internet Charge offs - Past 60 Days 146 TT_OCIN090 Total number of Check Advance Internet Charge offs - Past 90 Days 147 TT_OCIN180 Total number of Check Advance Internet Charge offs - Past 180 Days 148 TT_OCIN270 Total number of Check Advance Internet Charge offs - Past 270 Days 149 TT_OCIN365 Total number of Check Advance Internet Charge offs - Past 365 Days 150 TT_OCIN730 Total number of Check Advance Internet Charge offs - Past 730 Days Inquiries



# Name Variable Description 151 TT_INQALL007 Total number of Inquiries - Past 7 days 152 TT_INQALL014 Total number of Inquiries - Past 14 days 153 TT_INQALL060 Total number of Inquiries - Past 30 days 154 TT_INQALL030 Total number of Inquiries - Past 60 days 155 TT_INQSF000 Total number of Check Advance Storefront Inquiries 156 TT_INQSF007 Total number of Check Advance Storefront Inquiries - Past 7 Days 157 TT_INQSF014 Total number of Check Advance Storefront Inquiries - Past 14 Days 158 TT_INQSF030 Total number of Check Advance Storefront Inquiries - Past 30 Days 159 TT_INQSF060 Total number of Check Advance Storefront Inquiries - Past 60 Days 160 TT_INQSF090 Total number of Check Advance Storefront Inquiries - Past 90 Days 161 TT_INQSF180 Total number of Check Advance Storefront Inquiries - Past 180 Days 162 TT_INQSF270 Total number of Check Advance Storefront Inquiries - Past 270 Days 163 TT_INQSF365 Total number of Check Advance Storefront Inquiries - Past 365 Days 164 TT_INQSF730 Total number of Check Advance Storefront Inquiries - Past 730 Days 165 TT_INQIN000 Total number of Check Advance Internet Inquiries 166 TT_INQIN007 Total number of Check Advance Internet Inquiries - Past 7 Days 167 TT_INQIN014 Total number of Check Advance Internet Inquiries - Past 14 Days 168 TT_INQIN030 Total number of Check Advance Internet Inquiries - Past 30 Days 169 TT_INQIN060 Total number of Check Advance Internet Inquiries - Past 60 Days 170 TT_INQIN090 Total number of Check Advance Internet Inquiries - Past 90 Days 171 TT_INQIN180 Total number of Check Advance Internet Inquiries - Past 180 Days 172 TT_INQIN270 Total number of Check Advance Internet Inquiries - Past 270 Days 173 TT_INQIN365 Total number of Check Advance Internet Inquiries - Past 365 Days 174 TT_INQIN730 Total number of Check Advance Internet Inquiries - Past 730 Days Paid Charge Offs 175 TT_PCOA007 Total number of Paid charge offs - Past 7 days 176 TT_PCOA014 Total number of Paid charge offs - Past 14 days 177 TT_PCOA030 Total number of Paid charge offs - Past 30 days 178 TT_PCOA060 Total number of Paid charge offs - Past 60 days 179 TT_PCOSF000 Total number of Check Advance Storefront Paid Charge offs 180 TT_PCOSF007 Total number of Check Advance Storefront Paid Charge offs - Past 7 Days 181 TT_PCOSF014 Total number of Check Advance Storefront Paid Charge offs - Past 14 Days 182 TT_PCOSF030 Total number of Check Advance Storefront Paid Charge offs - Past 30 Days 183 TT_PCOSF060 Total number of Check Advance Storefront Paid Charge offs - Past 60 Days 184 TT_PCOSF090 Total number of Check Advance Storefront Paid Charge offs - Past 90 Days 185 TT_PCOSF180 Total number of Check Advance Storefront Paid Charge offs - Past 180 Days 186 TT_PCOSF270 Total number of Check Advance Storefront Paid Charge offs - Past 270 Days 187 TT_PCOSF365 Total number of Check Advance Storefront Paid Charge offs - Past 365 Days 188 TT_PCOSF730 Total number of Check Advance Storefront Paid Charge offs - Past 730 Days 189 TT_PCOIN000 Total number of Check Advance Internet Paid Charge offs 190 TT_PCOIN007 Total number of Check Advance Internet Paid Charge offs - Past 7 Days 191 TT_PCOIN014 Total number of Check Advance Internet Paid Charge offs - Past 14 Days 192 TT_PCOIN030 Total number of Check Advance Internet Paid Charge offs - Past 30 Days 193 TT_PCOIN060 Total number of Check Advance Internet Paid Charge offs - Past 60 Days 194 TT_PCOIN090 Total number of Check Advance Internet Paid Charge offs - Past 90 Days 195 TT_PCOIN180 Total number of Check Advance Internet Paid Charge offs - Past 180 Days



# Name Variable Description 196 TT_PCOIN270 Total number of Check Advance Internet Paid Charge offs - Past 270 Days 197 TT_PCOIN365 Total number of Check Advance Internet Paid Charge offs - Past 365 Days 198 TT_PCOIN730 Total number of Check Advance Internet Paid Charge offs - Past 730 Days Loans Opened 199 TT_LALL000 Total number of Loans Opened 200 TT_LALL007 Total number of Loans Opened - Past 7 Days 201 TT_LALL014 Total number of Loans Opened - Past 14 Days 202 TT_LALL030 Total number of Loans Opened - Past 30 Days 203 TT_LALL060 Total number of Loans Opened - Past 60 Days 204 TT_LALL090 Total number of Loans Opened - Past 90 Days 205 TT_LALL180 Total number of Loans Opened - Past 180 Days 206 TT_LALL270 Total number of Loans Opened - Past 270 Days 207 TT_LALL365 Total number of Loans Opened - Past 365 Days 208 TT_LALL730 Total number of Loans Opened - Past 730 Days 209 TT_LSF000 Total number of Check Advance Storefront Loans Opened 210 TT_LSF007 Total number of Check Advance Storefront Loans Opened - Past 7 Days 211 TT_LSF014 Total number of Check Advance Storefront Loans Opened - Past 14 Days 212 TT_LSF030 Total number of Check Advance Storefront Loans Opened - Past 30 Days 213 TT_LSF060 Total number of Check Advance Storefront Loans Opened - Past 60 Days 214 TT_LSF090 Total number of Check Advance Storefront Loans Opened - Past 90 Days 215 TT_LSF180 Total number of Check Advance Storefront Loans Opened - Past 180 Days 216 TT_LSF270 Total number of Check Advance Storefront Loans Opened - Past 270 Days 217 TT_LSF365 Total number of Check Advance Storefront Loans Opened - Past 365 Days 218 TT_LSF730 Total number of Check Advance Storefront Loans Opened - Past 730 Days 219 TT_LIN000 Total number of Check Advance Internet Loans Opened for all Industries 220 TT_LIN007 Total number of Check Advance Internet Loans Opened - Past 7 Days 221 TT_LIN014 Total number of Check Advance Internet Loans Opened - Past 14 Days 222 TT_LIN030 Total number of Check Advance Internet Loans Opened - Past 30 Days 223 TT_LIN060 Total number of Check Advance Internet Loans Opened - Past 60 Days 224 TT_LIN090 Total number of Check Advance Internet Loans Opened - Past 90 Days 225 TT_LIN180 Total number of Check Advance Internet Loans Opened - Past 180 Days 226 TT_LIN270 Total number of Check Advance Internet Loans Opened - Past 270 Days 227 TT_LIN365 Total number of Check Advance Internet Loans Opened - Past 365 Days 228 TT_LIN730 Total number of Check Advance Internet Loans Opened - Past 730 Days 229 TT_LRS000 Total of Loans Opened for Rent to Own 230 TT_LRS090 Total number of Loans Opened for Rent to Own Industry - Past 90 Days 231 TT_LRS180 Total number of Loans Opened for Rent to Own Industry - Past 180 Days 232 TT_LRS270 Total number of Loans Opened for Rent to Own Industry - Past 270 Days 233 TT_LRS365 Total number of Loans Opened for Rent to Own Industry - Past 365 Days 234 TT_LRS730 Total number of Loans Opened for Rent to Own Industry - Past 730 Days 229 TT_LCA000 Total of Loans Opened for Cash Advance 230 TT_LCA090 Total number of Loans Opened for Cash Advance Industry - Past 90 Days 231 TT_LCA180 Total number of Loans Opened for Cash Advance Industry - Past 180 Days 232 TT_LCA270 Total number of Loans Opened for Cash Advance Industry - Past 270 Days 233 TT_LCA365 Total number of Loans Opened for Cash Advance Industry - Past 365 Days 234 TT_LCA730 Total number of Loans Opened for Cash Advance Industry - Past 730 Days



# Name Variable Description 229 TT_LAF000 Total of Loans Opened for Auto Finance 230 TT_LAF090 Total number of Loans Opened for Auto Finance Industry - Past 90 Days 231 TT_LAF180 Total number of Loans Opened for Auto Finance Industry - Past 180 Days 232 TT_LAF270 Total number of Loans Opened for Auto Finance Industry - Past 270 Days 233 TT_LAF365 Total number of Loans Opened for Auto Finance Industry - Past 365 Days 234 TT_LAF730 Total number of Loans Opened for Auto Finance Industry - Past 730 Days 229 TT_LOT000 Total of Loans Opened for Rent to Own 230 TT_LOT090 Total number of Loans Opened for Other Industries - Past 90 Days 231 TT_LOT180 Total number of Loans Opened for Other Industries - Past 180 Days 232 TT_LOT270 Total number of Loans Opened for Other Industries - Past 270 Days 233 TT_LOT365 Total number of Loans Opened for Other Industries - Past 365 Days 234 TT_LOT730 Total number of Loans Opened for Other Industries - Past 730 Days Loans Paid 235 TT_PLALL000 Total number of Paid Loans 237 TT_PLALL007 Total number of Paid Loans - Past 7 Days 238 TT_PLALL014 Total number of Paid Loans - Past 14 Days 239 TT_PLALL030 Total number of Paid Loans - Past 30 Days 240 TT_PLALL060 Total number of Paid Loans - Past 60 Days 241 TT_PLALL090 Total number of Paid Loans - Past 90 Days 242 TT_PLALL180 Total number of Paid Loans - Past 180 Days 243 TT_PLALL270 Total number of Paid Loans - Past 270 Days 244 TT_PLALL365 Total number of Paid Loans - Past 365 Days 245 TT_PLALL730 Total number of Paid Loans - Past 730 Days 246 TT_PLSF000 Total number of Paid Loans 247 TT_PLSF007 Total number of Cash Advance Storefront Paid Loans - Past 7 Days 248 TT_PLSF014 Total number of Cash Advance Storefront Paid Loans - Past 14 Days 249 TT_PLSF030 Total number of Cash Advance Storefront Paid Loans - Past 30 Days 250 TT_PLSF060 Total number of Cash Advance Storefront Paid Loans - Past 60 Days 251 TT_PLSF090 Total number of Cash Advance Storefront Paid Loans - Past 90 Days 252 TT_PLSF180 Total number of Cash Advance Storefront Paid Loans - Past 180 Days 253 TT_PLSF270 Total number of Cash Advance Storefront Paid Loans - Past 270 Days 254 TT_PLSF365 Total number of Cash Advance Storefront Paid Loans - Past 365 Days 255 TT_PLSF730 Total number of Cash Advance Storefront Paid Loans - Past 730 Days 256 TT_PLIN000 Total number of Cash Advance Internet Paid Loans 257 TT_PLIN007 Total number of Cash Advance Internet Paid Loans - Past 7 Days 258 TT_PLIN014 Total number of Cash Advance Internet Paid Loans - Past 14 Days 259 TT_PLIN030 Total number of Cash Advance Internet Paid Loans - Past 30 Days 260 TT_PLIN060 Total number of Cash Advance Internet Paid Loans - Past 60 Days 261 TT_PLIN090 Total number of Cash Advance Internet Paid Loans - Past 90 Days 262 TT_PLIN180 Total number of Cash Advance Internet Paid Loans - Past 180 Days 263 TT_PLIN270 Total number of Cash Advance Internet Paid Loans - Past 270 Days 264 TT_PLIN365 Total number of Cash Advance Internet Paid Loans - Past 365 Days 265 TT_PLIN730 Total number of Cash Advance Internet Paid Loans - Past 730 Days 266 TT_PLRS000 Total number of Paid Loans for Rent to Own Industry 267 TT_PLRS090 Total number of Paid Loans for Rent to Own Industry - Past 90 Days 268 TT_PLRS180 Total number of Paid Loans for Rent to Own Industry - Past 180 Days



# Name Variable Description 269 TT_PLRS270 Total number of Paid Loans for Rent to Own Industry - Past 270 Days 270 TT_PLRS365 Total number of Paid Loans for Rent to Own Industry - Past 365 Days 271 TT_PLRS730 Total number of Paid Loans for Rent to Own Industry - Past 730 Days 272 TT_PLCA000 Total number of Paid Loans for Cash Advance Industry 273 TT_PLCA090 Total number of Paid Loans for Cash Advance Industry - Past 90 Days 274 TT_PLCA180 Total number of Paid Loans for Cash Advance Industry - Past 180 Days 275 TT_PLCA270 Total number of Paid Loans for Cash Advance Industry - Past 270 Days 276 TT_PLCA365 Total number of Paid Loans for Cash Advance Industry - Past 365 Days 277 TT_PLCA730 Total number of Paid Loans for Cash Advance Industry - Past 730 Days 278 TT_PLAF000 Total number of Paid Loans for Auto Finance Industry 279 TT_PLAF090 Total number of Paid Loans for Auto Finance Industry - Past 90 Days 280 TT_PLAF180 Total number of Paid Loans for Auto Finance Industry - Past 180 Days 281 TT_PLAF270 Total number of Paid Loans for Auto Finance Industry - Past 270 Days 282 TT_PLAF365 Total number of Paid Loans for Auto Finance Industry - Past 365 Days 283 TT_PLAF730 Total number of Paid Loans for Auto Finance Industry - Past 730 Days 284 TT_PLOT000 Total number of Paid Loans for Other Industries 285 TT_PLOT090 Total number of Paid Loans for Other Industries - Past 90 Days 286 TT_PLOT180 Total number of Paid Loans for Other Industries - Past 180 Days 287 TT_PLOT270 Total number of Paid Loans for Other Industries - Past 270 Days 288 TT_PLOT365 Total number of Paid Loans for Other Industries - Past 365 Days 289 TT_PLOT730 Total number of Paid Loans for Other Industries - Past 730 Days Active Loans 290 TT_ALALL000 Total number of Active Loans 291 TT_ALALL007 Total number of Active Loans - Past 7 Days 292 TT_ALALL014 Total number of Active Loans - Past 14 Days 293 TT_ALALL030 Total number of Active Loans - Past 30 Days 294 TT_ALALL060 Total number of Active Loans - Past 60 Days 295 TT_ALALL090 Total number of Active Loans - Past 90 Days 296 TT_ALALL180 Total number of Active Loans - Past 180 Days 297 TT_ALALL270 Total number of Active Loans - Past 270 Days 298 TT_ALALL365 Total number of Active Loans - Past 365 Days 299 TT_ALALL730 Total number of Active Loans - Past 730 Days 300 TT_ALSF000 Total number of Active Loans 301 TT_ALSF007 Total number of Cash Advance Storefront Active Loans - Past 7 Days 302 TT_ALSF014 Total number of Cash Advance Storefront Active Loans - Past 14 Days 303 TT_ALSF030 Total number of Cash Advance Storefront Active Loans - Past 30 Days 304 TT_ALSF060 Total number of Cash Advance Storefront Active Loans - Past 60 Days 305 TT_ALSF090 Total number of Cash Advance Storefront Active Loans - Past 90 Days 306 TT_ALSF180 Total number of Cash Advance Storefront Active Loans - Past 180 Days 307 TT_ALSF270 Total number of Cash Advance Storefront Active Loans - Past 270 Days 308 TT_ALSF365 Total number of Cash Advance Storefront Active Loans - Past 365 Days 309 TT_ALSF730 Total number of Cash Advance Storefront Active Loans - Past 730 Days 310 TT_ALIN000 Total number of Cash Advance Internet Active Loans 311 TT_ALIN007 Total number of Cash Advance Internet Active Loans - Past 7 Days 312 TT_ALIN014 Total number of Cash Advance Internet Active Loans - Past 14 Days 313 TT_ALIN030 Total number of Cash Advance Internet Active Loans - Past 30 Days



# Name Variable Description 314 TT_ALIN060 Total number of Cash Advance Internet Active Loans - Past 60 Days 315 TT_ALIN090 Total number of Cash Advance Internet Active Loans - Past 90 Days 316 TT_ALIN180 Total number of Cash Advance Internet Active Loans - Past 180 Days 317 TT_ALIN270 Total number of Cash Advance Internet Active Loans - Past 270 Days 318 TT_ALIN365 Total number of Cash Advance Internet Active Loans - Past 365 Days 319 TT_ALIN730 Total number of Cash Advance Internet Active Loans - Past 730 Days 320 TT_ALRS000 Total number of Active Loans for Rent to Own Industry 321 TT_ALRS090 Total number of Active Loans for Rent to Own Industry - Past 90 Days 322 TT_ALRS180 Total number of Active Loans for Rent to Own Industry - Past 180 Days 323 TT_ALRS270 Total number of Active Loans for Rent to Own Industry - Past 270 Days 324 TT_ALRS365 Total number of Active Loans for Rent to Own Industry - Past 365 Days 325 TT_ALRS730 Total number of Active Loans for Rent to Own Industry - Past 730 Days 326 TT_ALCA000 Total number of Active Loans for Cash Advance Industry 327 TT_ALCA090 Total number of Active Loans for Cash Advance Industry - Past 90 Days 328 TT_ALCA180 Total number of Active Loans for Cash Advance Industry - Past 180 Days 329 TT_ALCA270 Total number of Active Loans for Cash Advance Industry - Past 270 Days 330 TT_ALCA365 Total number of Active Loans for Cash Advance Industry - Past 365 Days 331 TT_ALCA730 Total number of Active Loans for Cash Advance Industry - Past 730 Days 332 TT_ALAF000 Total number of Active Loans for Auto Finance Industry 333 TT_ALAF090 Total number of Active Loans for Auto Finance Industry - Past 90 Days 334 TT_ALAF180 Total number of Active Loans for Auto Finance Industry - Past 180 Days 335 TT_ALAF270 Total number of Active Loans for Auto Finance Industry - Past 270 Days 336 TT_ALAF365 Total number of Active Loans for Auto Finance Industry - Past 365 Days 337 TT_ALAF730 Total number of Active Loans for Auto Finance Industry - Past 730 Days 338 TT_ALOT000 Total number of Active Loans for Other Industries 339 TT_ALOT090 Total number of Active Loans for Other Industries - Past 90 Days 340 TT_ALOT180 Total number of Active Loans for Other Industries - Past 180 Days 341 TT_ALOT270 Total number of Active Loans for Other Industries - Past 270 Days 342 TT_ALOT365 Total number of Active Loans for Other Industries - Past 365 Days 343 TT_ALOT730 Total number of Active Loans for Other Industries - Past 730 Days Other 344 TT_NIICO Total number of Related Non Internet Inquiries and Charge offs 345 TT_TOTINQN Total Number of Non internet Inquiries Ever 346 TT_DSGD Total Number of Days from Reported Skipguard Alert 347 TT_CNLT Total number of Negative Landlord Court records 348 TT_INQNCINCO Total number of Check Advance Storefront Inquiries and no charge offs ever 349 TT_INQNCO Total number of All inquiries with no charge offs on file

How are Credit Variables billed? Credit Variables are billed on a subscription basis. You may configure up to 126 variables to be collected any time you use the Request Type of “Variables”, but the amount you may be charged makes it advantageous for you to be selective in the



variables that you use. Please talk with your Account Representative both to subscribe for Credit Variables and to select those variables that will best meet your needs.

7. Scoring Changes How is scoring now calculated to determine most important factors? What if there are fewer than four negatively scored variables? What if there are four or more negatively scored variables? What is the score range?

How is scoring now calculated to determine most important factors? Earlier releases of Teletrack scoring software returned up to four factors that most affected a consumer’s score. Teletrack will now return up to five factors that most negatively affect a consumer’s score. The difference in the calculation will not affect the consumer’s score, but it may impact both the number of factors returned and which ones are returned. The distinction between the previous reporting and that which will now be reported is the difference between variance and value. Previously, variance was used. This meant that a scored variable would be compared to the greatest number of points that could be awarded for the variable and the variance between those values was ranked across all scoring variables. The new calculation looks only at the value awarded to the variable and the scoring variables are then ranked by the values that most reduce the consumer’s score (have the greatest number of negative points awarded the variable),

What if there are fewer than four negatively scored variables? If there are fewer than four negatively scored variables, then only those factors will be reported back to the merchant.

What if there are four or more negatively scored variables? If there are at least four negatively scored variables, the four with the greatest negative impact on the consumer’s score will be reported first. If there are five or more negatively scored variables, then the system will report a fifth factor that will either be the highest-impact inquiry-related factor or the highest-impact non-inquiry-related factor when there are no additional inquiry-related factors that were not reported as part of the first four factors.

What is the score range?



The score range displays the lowest and highest score available for a consumer. It should be used to gauge the relative position of the consumer’s score within the total distribution of scores available.

8. Follow-On Transactions What is the definition of a follow-on transaction? When would I want to use a follow-on transaction? How do I send a follow-on transaction? What rules govern the use of follow-on transactions?

What is the definition of a follow-on transaction? A follow-on transaction is a transaction that is closely linked to a previous transaction. Data supplied with the follow-on transaction is matched against the previous transaction to confirm that this is the same merchant and consumer. The data will come from the Subscriber and Applicant nodes. Specifically, the SubscriberID, the Uin, and the LastName should be the same as those from the TransactionCode. The system will treat the initial transaction and the follow-on transaction as if they had been performed concurrently.

When would I want to use a follow-on transaction? A follow-on transaction would be particularly useful if the information gathered from the initial transaction would reduce the number of applicants who would qualify and, for whom, additional information would be needed. This is especially true when the additional information is billed separately and warrants reducing the qualified entries seeking this information. In addition, the follow-on transaction will not show as a previous inquiry or be billed as an inquiry.

How do I send a follow-on transaction? The TransactionCode attribute in the TransactionRequest is an optional attribute. If it is blank or missing, this is not a follow-on transaction. If it is non-blank, then the attribute must contain a previous TransactionCode returned to the merchant from the initial transaction for this consumer. The TransactionCode is tied to the SubscriberID and the SSN.

What rules govern the use of follow-on transactions? There are several rules that govern the use of follow-on transactions:



1. Currently, the only acceptable RequestType within a follow-on transaction is “Third Party Data”. Several of these RequestTypes may be sent as part of a single follow-on transaction.

2. There is a time limit of 24 clock hours from the moment that the initial transaction is received for the merchant to submit a follow-on transaction.

3. A merchant may issue as many follow-on transactions to the initial transaction as they wish as long as the last transaction falls within 24 clock hours of the initial transaction.

4. A follow-on transaction will not be billed as a separate inquiry. 5. A follow-on transaction will not show as a previous inquiry or count in Scoring

and Underwriting as a previous inquiry.

9. Third Party Data What is Third Party Data? What information will I need to furnish in order to receive Third Party Data?

What is a Third Party Data? Teletrack has contracted with several external partners to provide its customers with a one-stop approach to information. A single call to Teletrack can pull in additional information from a variety of sources all of which will be returned to the customer bundled together in a single XML response. Each vendor’s data is separated by the source of the information so that the customer knows all of the information on the consumer and from whom he received it. Please reference the individual vendor’s FAQ for additional information.

What information will I need to furnish in order to receive a Third Party Data? The Third Party Data request typically requires at least two options. These are supplied as the vendor and product. These would appear as follows:

<Request RequestType="Third Party Data"> <tt:RequestOption Name="Vendor" Value="vendor name" /> <tt:RequestOption Name="Product" Value="product name" />

</Request> Each individual vendor may have other parameters that may be furnished when making the request. Individual vendor information will be sent to you when you contract with Teletrack for that vendor’s service. Reference specific FAQs



10. XML Versioning What is XML versioning? What is the best approach for me? Will my existing software continue to work? How do I identify the version of XML that I am using?

What is XML versioning? Teletrack supports the ability for different subscribers to be on different compatible or incompatible versions of Teletrack’s XML. Teletrack will maintain access for all subscribers. Some changes in the XML schema may be breaking changes, though, such as the renaming of an attribute, the need to make an element or attribute required instead of optional or inclusion of additional data being returned for the same service. Whenever Teletrack issues a schema with a “breaking change”, all previous schemas will be considered to be in maintenance mode. Teletrack will ensure that subscribers will continue to be able to function as they have without making changes to their software. However, all new services that may be offered will be offered against the latest version of the schema only. This will mean two things to you. As a subscriber, you will always be able to function as you do today with no changes to your software. However, if you wish to take advantage of new features and services being offered by Teletrack, you will need to move to the latest version of the schema.

What is the best approach for me? Teletrack recommends that even if there are no features that you wish to take advantage of immediately, that you schedule upgrading to the latest version of the XML schema at a time that is convenient to you. This will eliminate the additional effort that might be required at the time that you wish to integrate to a new feature or service.

Will my existing software continue to work? Yes. Teletrack is equally concerned that your existing software continue to work as coded. Teletrack tests the support of all pre-existing software prior to installation of a new version. In addition, Teletrack makes available its Customer Test system to all subscribers prior to installation of new software so that you may test this as well.

How do I identify the version of XML that I am using? In the schemas that you have been sent, you will see a line that looks like the lines below:



<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://xml.teletrack.com/transaction" xmlns:tt="http://xml.teletrack.com/globals" targetNamespace="http://xml.teletrack.com/transaction" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.2.0"> This identifies version 1.2.0 of the XML. When sending a TransactionRequest of a TransactionReport, you would include the TeletrackXMLVersion with a value of “1.2.0”. This identifies to Teletrack that this is the version number of the software you are using and this is what Teletrack should use in its communication of the TransactionResponse or TransactionReportResponse. If you send no TeletrackXMLVersion, then Teletrack will default to the lowest level of schemas. Inclusion of the TeletrackXMLVersion is mandatory for any schema that is equal to or later than 1.2.0.

11. Connecting with Teletrack How do I connect to Teletrack using PHP code? How do I connect to Teletrack using Visual Studio 2005? How do I connect to Teletrack using Visual Studio 2008?

How do I connect to Teletrack using PHP code? The following code samples are intended to be an indicative example of how you could integrate from the PHP code platform. They are provided without obligation on an ‘as is’ basis. Teletrack does not support this code nor does it guarantee that it will function on this or any future releases of our xml transaction processing platform. We recommend that whatever code you use that you follow your full SDLC including regression testing before using any code in a production environment. If you can make changes to php.ini, it might be worth adding or adjusting the following lines: max_execution_time = 300 ; Maximum execution time of each script, in seconds max_input_time = 60 ; Maximum amount of time each script may spend parsing request data memory_limit = 8M ; Maximum amount of memory a script may consume (8MB) Then, proceed with the following code: set_time_limit(300); $soap_user = 'REPLACE-ME'; $soap_pass = 'REPLACE-ME'; $Subscriber= 'REPLACE-ME'; $url="https://xmltest.teletrack.com/inquiry.asmx ";



$additional_headers = array( 'Content-Type: text/xml; charset=utf-8', "SOAPAction: \"http://xml.teletrack.com /transaction/GetData\"" ); //Each merchant will want to use functions to build this string as best suited to their needs. $reqPayloadString = ' <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Header> <wsse:Security soapenv:mustUnderstand="1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"> <wsse:UsernameToken wsu:Id="SecurityToken-ea4855e0-675b-4ac5-a1c1-e170bac5f1eb"> <wsse:Username>USERNAME</wsse:Username> <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">PASSWORD</wsse:Password> </wsse:UsernameToken> </wsse:Security> </soapenv:Header> <soapenv:Body> <tns:GetData xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:s0="http://xml.teletrack.com/globals" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://xml.teletrack.com/transaction"> <tns:TransactionRequest> <tns:Subscriber SubscriberID="44073" UserName="USERNAME" Password="PASSWORD" /> <tns:RequestDetails> <tns:Request RequestType="Inquiry" /> </tns:RequestDetails> <tns:Applicant> <tns:Uin Type="SSN" Uin="042202487" /> <tns:Name FirstName="Caldwell" LastName="Stubbins" /> <tns:BirthDate>1956-08-07</tns:BirthDate> <tns:DriversLicense State="OH" Number="123456789" /> <tns:Address Country="America"> <s0:ParsedAddress StreetNumber="3570" StreetName="Gorsuch" StreetType="Rd" City="Nashport" State="OH" PostalCode="43830" /> </tns:Address> <tns:Phones> <tns:Phone Number="4043256987" Type="Home" /> </tns:Phones> </tns:Applicant> </tns:TransactionRequest> </tns:GetData> </soapenv:Body> </soapenv:Envelope> '; $reqPayloadString = mb_convert_encoding($reqPayloadString,"UTF-8"); //make sure that php.ini has the following line UNcommented: //extension=php_curl.dll //Note: Note to Win32 Users In order to enable this module on a Windows environment, libeay32.dll and ssleay32.dll must be present in your PATH. You don't need libcurl.dll from the cURL site.



$curl_handle = curl_init($url); curl_setopt($curl_handle, CURLOPT_TIMEOUT, 300); //how long CURL will run before it gives up curl_setopt($curl_handle, CURLOPT_CONNECTTIMEOUT, 5); //how long CURL will wait to even connect to the site you want to pull data from curl_setopt($curl_handle, CURLOPT_VERBOSE, 1); curl_setopt($curl_handle, CURLOPT_SSL_VERIFYPEER , 0); curl_setopt($curl_handle, CURLOPT_POST , 1); curl_setopt($curl_handle, CURLOPT_POSTFIELDS , $reqPayloadString); curl_setopt($curl_handle, CURLOPT_RETURNTRANSFER, 1); curl_setopt($curl_handle, CURLOPT_HEADER , 0); curl_setopt($curl_handle, CURLOPT_HTTPHEADER , $additional_headers); try { $buffer = curl_exec($curl_handle); curl_close($curl_handle); } catch (Exception $e) { printf("Message = %s\n",$e->__toString()); print_r(curl_getinfo($curl_session)); } if (empty($buffer)) { print "Sorry, no data returned.<p>"; } else { print htmlspecialchars($buffer); //i am using a browser to debug } ?>

How do I connect to Teletrack using Visual Studio 2005? The following code samples are intended to be an indicative example of how you could integrate from the Visual Studio 2005 platform. They are provided without obligation on an ‘as is’ basis. Teletrack does not support this code nor does it guarantee that it will function on this or any future releases of our xml transaction processing platform. We recommend that whatever code you use that you follow your full SDLC including regression testing before using any code in a production environment.

• Install WSE 3.0. • Be sure to install the developer version of WSE. • Once you have completed the installation, you will be able to specify WSE

setting for a project with Visual Studio. • You can right click on your project and there should be an option "WSE

Setting 3.0".



• Enable the project for web service enhancements.



• Add a new policy under the policy tab called "ClientPolicy".



• The type of policy Teletrack is expecting is simply the username and password to be secured over the transport layer.



• If you need to do any debugging of the messages going back and forth, you can "Enable Message Trace" under the "Diagnostics" tab.



• To add references to TeleTrack's webservices, simply add a webreference to the project for the test and development webservices.

• Once you have added the webreference, you should be able to access the methods you need to setup your message.

• There are two versions of the "Inquiry" proxy class generated. One is simply the "Inquiry" proxy class and the other is called "InquiryWse".

• You want to use the "InquiryWse" proxy class in setting up your message. • Before you setup your message, you need to be sure and set the client

credentials via the "SetClientCredential(UsernameToken)" method as part of the "InquiryWse" instance you create.

• You have to create a "UsernameToken" instance which is part of one of the "Microsoft.Web.Services3" libraries.

• You should also call the "SetPolicy" method on your instance of "InquiryWse", set it to the name of the policy you created, "ClientPolicy".

• Now you should be ready to setup your message. • Be sure to ask for an example message for the type of transaction you wish to

perform. • Once Teletrack gets you that, after enabling message tracing, Visual Studio

will create files within your project which contain the message contents and you can use those files to make sure the information you are sending and



receiving is correct. (Be sure to not leave the trace messages enabled when you go to production, you can disable the tracing via your configuration file)

NOTE: One thing to note about the output files from visual studio is that they are named unusually. InputTrace should mean that this is the file to look in to see what data is being sent to the server (being input to the server) and the OutputTrace would be the data that is being received from the server (output from the server). However, it is the opposite. The OutputTrace.webinfo is the file that shows the data being sent to the server, and the InputTrace.webinfo is the file that shows the data being received from the server. Another thing to note is that SOAP does not allow for null data types other than strings. This is why when the FromDate and ToDate are described as being optional in the WSDL, the Web service proxy that is created in Visual Studio creates additional properties named [optionalFieldname]+Specified to tell the XML serializer that something has been specified, so serialize it. Hence, our documentation makes no reference to FromDateSpecified (a Boolean that Visual Studio Creates).

How do I connect to Teletrack using Visual Studio 2008? The following code samples are intended to be an indicative example of how you could integrate from the Visual Studio 2008 platform. They are provided without obligation on an ‘as is’ basis. Teletrack does not support this code nor does it guarantee that it will function on this or any future releases of our xml transaction processing platform. We recommend that whatever code you use that you follow your full SDLC including regression testing before using any code in a production environment. To keep this example simple, we will be creating a console application to connect to Teletrack’s XML Interface. The developer should weigh the needs of their organization to determine what type of application makes the most sense for their environment. The actual steps needed to connect to Teletrack would be the same for whichever choice was made.



1. First, we will create a new console application as seen in the screenshot below.



2. Next we need to add a Service Reference by choosing “Add Service Reference” from the “Project” menu.



3. When the following dialog appears, enter the URL for the Teletrack customer

test environment. (The URL can be changed to the production environment in the configuration file later once your application is ready to deploy.) You will also want to enter a Namespace such as CT_Inquiry. However, it can be whatever name you choose. When you are finished click on the button labeled “Go”.

4. At this point, Visual Studio will connect to the URL and inspect the WSDL found there. It should populate the dialog box similar to the next screenshot. Choose “InquirySoap”, set your namespace appropriately, and choose “Okay”.



5. The new Service Reference should now appear in the project explorer. Notice

that references to other .Net framework assemblies have also been added.



6. In addition, the following section has now been added to the application configuration file. Note that the client node now has a section called client. This endpoint URL is what you will later change to the production value instead of customer test.

Add the “using statements” needed for the Service Reference as determined by the namespace that you choose earlier. Also, ensure that there is a “using statement” for the “System.ServiceModel” namespace.



7. Now we need to modify the configuration file to make it compatible with Teletrack’s chosen security model. (The following configuration changes can be done using the Microsoft provided Service Configuration Tool in the Windows SDK. Since there is no guarantee that the reader has the SDK installed we will edit the configuration file manually). In the application configuration, look for the following section:

Change it to the following:

8. All of the setup is now complete. Now the code needs to be written to create an instance of the SOAP client and call the GetData method. The GetData method requires that a TransactionRequestEntity is passed into it and (if successful) it will return a TransactionResponseEntity. This method is when the client actually connects to Teletrack. An example of this code is provided below (note that your namespace for the SOAP client may differ):

using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.Configuration; using System.ServiceModel; using WCF_Sample.CT_Inquiry; using System.Xml.Serialization;

http://msdn.microsoft.com/en-us/library/ms732009.aspx



namespace WCF_Sample { class WCF_CustomerTest { static void Main(string[] args) { string username = ConfigurationSettings.AppSettings["UserName"]; string password = ConfigurationSettings.AppSettings["Password"]; string subscriberID = ConfigurationSettings.AppSettings["SubscriberID"]; Console.WriteLine("Calling Inquiry in CT"); Console.WriteLine(); InquirySoapClient inqCT = new InquirySoapClient("InquirySoap"); TransactionRequestEntity transactionRequest = CreateRequest(username, password, subscriberID); try { XmlSerializer xmlInput = new XmlSerializer(transactionRequest.GetType()); Console.WriteLine("Inquiry Request:"); Console.WriteLine(); xmlInput.Serialize(Console.Out, transactionRequest); Console.WriteLine(); inqCT.ClientCredentials.UserName.UserName = username; inqCT.ClientCredentials.UserName.Password = password; TransactionResponseEntity response = inqCT.GetData(transactionRequest); XmlSerializer xmlOutput = new XmlSerializer(response.GetType()); Console.WriteLine(); Console.WriteLine("Inquiry Response:"); xmlOutput.Serialize(Console.Out, response); Console.WriteLine(); } catch(Exception ex) { Console.WriteLine(); Console.WriteLine(ex.Message); Console.WriteLine(ex.StackTrace); } Console.WriteLine(); Console.WriteLine("Press any key to continue ...."); Console.ReadKey(); } internal static TransactionRequestEntity CreateRequest(string username, string password, string subscriberID) { TransactionRequestEntity transactionRequest = new TransactionRequestEntity(); transactionRequest.Applicant = new ConsumerEntity(); transactionRequest.Applicant.Address = new AddressEntity(); transactionRequest.Applicant.Address.Country = "United States"; transactionRequest.Applicant.Address.SimpleAddress = new SimpleAddressEntity(); transactionRequest.Applicant.Address.SimpleAddress.City = "Anchorage"; transactionRequest.Applicant.Address.SimpleAddress.Line1 = "802 S Townsend"; transactionRequest.Applicant.Address.SimpleAddress.Line2 = ""; transactionRequest.Applicant.Address.SimpleAddress.PostalCode = "99510"; transactionRequest.Applicant.Address.SimpleAddress.State = "AK"; transactionRequest.Applicant.BirthDate = new DateTime(1935, 01, 14); transactionRequest.Applicant.DriversLicense = new DriversLicenseEntity();



transactionRequest.Applicant.DriversLicense.Number = "492929750"; transactionRequest.Applicant.Uin = new UINEntity(); transactionRequest.Applicant.Uin.Uin = "125326910"; transactionRequest.Applicant.Uin.Type = "SSN"; RequestEntity requestEntity = new RequestEntity(); requestEntity.RequestType = RequestEntityRequestType.Inquiry; transactionRequest.RequestDetails = new RequestEntity[1]; transactionRequest.RequestDetails[0] = requestEntity; transactionRequest.Subscriber = new SubscriberEntity(); transactionRequest.Subscriber.Password = password; transactionRequest.Subscriber.UserName = username; transactionRequest.Subscriber.SubscriberID = subscriberID; return transactionRequest; } } }

In this example you need to include your Username, Password, and SubscriberID in the configuration file.

NOTE: During development and testing it is often helpful to enable trace logging. This will capture all of the request and response data sent to and from Teletrack. Trace logging can be enabled as indicated in this Microsoft reference page. Another thing to note is that SOAP does not allow for null data types other than strings. This is why when the FromDate and ToDate are described as being optional in the WSDL, the Web service proxy that is created in Visual Studio creates additional properties named [optionalFieldname]+Specified to tell the XML serializer that something has been specified, so serialize it. Hence, your documentation makes no reference to FromDateSpecified (a Boolean that Visual Studio Creates). This could lead to some confusion.

http://msdn.microsoft.com/en-us/library/ms733025.aspx

teletrack uk frequently asked questions€¦ · frequently asked questions . teletrack us faq....

Documents