teletrack uk frequently asked questions - corelogic · frequently asked questions teletrack us faq...

Frequently Asked Questions

Teletrack US FAQ

Confidential

Version: 1.25 Last Updated On: July 22, 2016 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.

© 2016 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 What is a Security Freeze and how is it lifted? ............................................................... 9

4. Loan Reporting ....................................................................................................... 9 When should I report a loan to Teletrack? .................................................................... 10

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? ........................... 11 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? .................................................................. 16

What is the typical flow of an Installment, Auto Equity or Simple Interest Loan? ...... 19 How should I handle the Charge Off of a Loan? ........................................................... 19 What is the Difference Between “Void” and “Rescind”? ............................................. 20

What does the message “Disputed Tradeline Deleted” mean? ...................................... 20 5. Authentication Variables ...................................................................................... 20

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

6. Credit Variables .................................................................................................... 23 What are Credit Variables? ............................................................................................ 24

7. Scoring Changes ................................................................................................... 24 How is scoring now calculated to determine most important factors? .......................... 24

What if there are fewer than four negatively scored variables? .................................... 24 What if there are four or more negatively scored variables? ......................................... 24 What is the score range? ................................................................................................ 25

8. Follow-On Transactions........................................................................................ 25 What is the definition of a follow-on transaction? ........................................................ 25

When would I want to use a follow-on transaction? ..................................................... 25

How do I send a follow-on transaction? ........................................................................ 25

What rules govern the use of follow-on transactions? .................................................. 26 9. Third Party Data .................................................................................................... 26

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

10. XML Versioning ................................................................................................... 27

What is XML versioning? ............................................................................................. 27 What is the best approach for me? ................................................................................. 27 Will my existing software continue to work? ................................................................ 28

© 2016 CORELOGIC TELETRACK PROPRIETARY & CONFIDENTIAL

How do I identify the version of XML that I am using? ............................................... 28

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

How do I connect to Teletrack using Visual Studio 2008? ........................................... 38

Teletrack US FAQ Frequently Asked Questions

Version 1.25 07/22/2016

© 2016 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:


Version 1.25 07/22/2016


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:


Version 1.25 07/22/2016


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.


Version 1.25 07/22/2016


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?

What is a Security Freeze and how is it lifted?

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.


Version 1.25 07/22/2016


Request Type Meaning

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

“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)


Version 1.25 07/22/2016


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”

“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


a. “Inquiry”



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


a. “Inquiry”



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


Version 1.25 07/22/2016



"Inquiry"

Example: <Request

RequestType="Inquiry"/>

<Request


<Request RequestType="Text

Report"/>

<Request


<Request RequestType="ID

Verification"/>

<Request


<Request

RequestType="Checking

Data"/>

<Request


<Request

RequestType="Variables"/>

<Request


<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)


Version 1.25 07/22/2016



“Underwriting” <Request


RequestType="Underwriting">

<tt:RequestOption

Name="Payday" />

</Request>

(This request must include

“Inquiry” in order to return

the Score)

<Request



<tt:RequestOption

Name="Payday" />

RequestType="Third Party

Data"/>

</Request>

<Request



<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

“Third Party

Data”


“Variables” Variables (if subscribed)

“Text Report”


Report"/>


Report"/>

<Request RequestType="ID

Verification"/>


Report"/>

<Request

RequestType="Checking

Data"/>


Report"/>


Party Data"/>

TransactionResponse

Subscriber

RequestDetails


Uin

Name

BirthDate

AliasList

AddressList

TextReport3

TransactionErrors

TransactionDateTime


"ID

Verification"

TextReport4 (if subscribed)

“Checking

Data”

TextReport5 (if subscribed)

“Third Party

Data”



Version 1.25 07/22/2016



“Third Party Data”


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


Uin

Name

BirthDate

AliasList

AddressList

ThirdPartyData6

TransactionErrors

TransactionDateTime


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.

What is a Security Freeze and how is it lifted?

A consumer may contact Teletrack to request a security freeze be placed on his data.

Once the security freeze has been placed on the consumer’s data, inquiring merchants

will not receive a Credit Report from Teletrack or any Third Party vendors. Teletrack will

reply to the merchant with an error indicating:

<Error ErrorCode="0147">Consumer Security Freeze</Error>

No credit information will be present as part of the response. In order to actually receive

credit information, it will be necessary for the consumer to personally contact Teletrack

to have the freeze temporarily lifted. Once he has completed his application, he will then

need to reinstate the security freeze if he so desires.

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?


Version 1.25 07/22/2016


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


Version 1.25 07/22/2016


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


Version 1.25 07/22/2016


Element or Attribute Definition When to Send

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.


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

OtherFeeType Free-form description of

the type of fee above

Optional

DueDate The Maturity Date of the

loan


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.

Should only be sent




reported

PaymentAmount The amount of each

payment for an

Installment, Auto Equity

or Simple Interest loan

Should only be sent




reported

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.


Version 1.25 07/22/2016



TransactionNumber The TransactionNumber

returned by Teletrack as

part of the Inquiry



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.



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



Interest loan is updated

ActualPaymentAmount The payment made

against an Installment,


Interest loan

Should only be sent



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


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.


Version 1.25 07/22/2016



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”.

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


Version 1.25 07/22/2016



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

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




Version 1.25 07/22/2016



NumberOfTransactions Not used in transaction



NumberOfNSFs Not used in transaction



Balance Not used in transaction



BankName The name of the

Financial Institution on

the check

Should be sent if

payment is made by

check

BankPhoneNumber The phone number of

the Financial Institution

on the check

Should be sent if

payment is made by

check

RoutingNumber The routing number of

the Financial Institution

on the check

Should be sent if

payment is made by

check

AccountNumber The account number on

the check

Should be sent if

payment is made by

check

AccountType The type of account –

Checking, Savings,

Money Market or Other

Should be sent if

payment is made by

check

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


Version 1.25 07/22/2016


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:














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:







CurrentBalance = 0

ClosedDatetime = timestamp of the actual date and time that the

consumer paid the loan

AccountStatus = “Paid”


Version 1.25 07/22/2016








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:







CurrentBalance = 0

ClosedDatetime = timestamp of the actual date and time that the

consumer paid the loan

AccountStatus = “Paid”







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:


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


DueDate = new date on which the rolled over loan should be paid




Version 1.25 07/22/2016


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.


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


Version 1.25 07/22/2016


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


Version 1.25 07/22/2016


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:

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

mailto:[email protected]




Version 1.25 07/22/2016




Past Minute

Past 5 Minutes

Past Hour

Past 12

Hours

Past Day

Past Week

Past Month

Past Quarter

Past Year

Same Routing Number

Different Routing Number

Same Bank Account Number

Different Bank Account Number

Same Email Address

Different Email Address

Current Address:

Same Person



Same Phone

Different Phone

Same Employer Phone


Same Routing Number




Same Email Address


Home Telephone:

Same Person





Same Email Address


Same Employer Phone


Same Routing Number




Work Telephone:

Same Person



Version 1.25 07/22/2016




Past Minute

Past 5 Minutes

Past Hour

Past 12

Hours

Past Day

Past Week

Past Month

Past Quarter

Past Year




Same Email Address


Same Home Phone

Different Home Phone

Same Routing Number




Bank Account:

Same Person



Same Email Address


Same Home Phone


Same Employer Phone


EMail Address:

Same First name/Last name

Same Last name

Different First name/Last name

Same Home Phone


Same Employer Phone


Date of Birth:

Name Match - Same Birthdate

Name Match - Different Birthdate

6. Credit Variables

What are Credit Variables?


Version 1.25 07/22/2016


What are Credit Variables?

Credit variables are established by configuration for each merchant who has contracted

for Credit Variables. The variables that are available for configuration may be found in

Appendix L of the XML Interface Manual. Note that the number of variables you request

will have a definite impact on the amount of time that will be required to return the

results to you. If you are building your own scoring model, credit variables may be used

to determine which of these are predictive. Once you have determined those variables

that are most predictive, you would be well served to then only return those variables to

you for scoring. When the time comes to re-evaluate your scoring model, it would then

be appropriate again to choose a broader range of variables to re-evaluate which ones are

most predictive.

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?


Version 1.25 07/22/2016


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?


Version 1.25 07/22/2016


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:


Version 1.25 07/22/2016


<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.


Version 1.25 07/22/2016


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 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


Version 1.25 07/22/2016


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>


Version 1.25 07/22/2016


<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

}

?>



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



Version 1.25 07/22/2016


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".


Version 1.25 07/22/2016


Enable the project for web service enhancements.


Version 1.25 07/22/2016


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


Version 1.25 07/22/2016


The type of policy Teletrack is expecting is simply the username and

password to be secured over the transport layer.


Version 1.25 07/22/2016



Version 1.25 07/22/2016


If you need to do any debugging of the messages going back and forth, you

can "Enable Message Trace" under the "Diagnostics" tab.


Version 1.25 07/22/2016


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


Version 1.25 07/22/2016


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).



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


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.


Version 1.25 07/22/2016


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

below.


Version 1.25 07/22/2016


2. Next we need to add a Service Reference by choosing “Add Service

Reference” from the “Project” menu.


Version 1.25 07/22/2016


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”.


Version 1.25 07/22/2016


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

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


Version 1.25 07/22/2016


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.


Version 1.25 07/22/2016


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


Version 1.25 07/22/2016


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:");


xmlInput.Serialize(Console.Out, transactionRequest);


inqCT.ClientCredentials.UserName.UserName = username;

inqCT.ClientCredentials.UserName.Password = password;

TransactionResponseEntity response = inqCT.GetData(transactionRequest);

XmlSerializer xmlOutput = new XmlSerializer(response.GetType());


Console.WriteLine("Inquiry Response:");

xmlOutput.Serialize(Console.Out, response);


}

catch(Exception ex)

{


Console.WriteLine(ex.Message);

Console.WriteLine(ex.StackTrace);

}


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();


Version 1.25 07/22/2016


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 - corelogic · frequently asked questions teletrack us faq...

Documents