Method and system for processing a transaction

FIELD OF THE INVENTION

[0001] The present invention relates generally to transaction processing and, more specifically, to processing a transaction between a vendor and a user via an electronic terminal connected by a communication line to a communication network.

BACKGROUND OF THE INVENTION

[0002] An increasing number of vendors are offering goods and/or services which may be purchased via a communication network such as a telecommunication network. For example, a purchaser may conduct a transaction via a subscriber line using a landline telephone or a personal computer via the Internet. Conventionally, credit or debit card details are furnished by the purchaser to the vendor to effect payment for the goods and/or services. As many purchasers are hesitant to supply credit or debit card details over a communication network, an alternate method of payment would be advantageous. However, if an alternate method is used, verification of the payment method should preferably take place prior to concluding the transaction.

SUMMARY OF THE INVENTION

[0003] In accordance with the invention, there is provided a method of processing payment for a transaction, the method including:

[0004] providing a user with an option, via an electronic terminal, to select payment for the transaction from an account associated with a communication line to which the electronic terminal is connected;

[0005] receiving a user request entered into the terminal to process payment from the account;

[0006] investigating data associated with the communication line; and selectively approving the transaction dependent upon an outcome of the investigation.

[0007] Further in accordance with the invention, there is provided a method of modifying a financial instrument record, the method including:

[0008] receiving transaction data entered into an electronic terminal connected via a communication line to a communication network;

[0009] obtaining a unique identifier associated with the communication line; and

[0010] combining the unique identifier and the transaction data to form a financial instrument record.

[0011] Still further in accordance with the invention, there is provided a method of validating a transaction conducted using an electronic terminal connected via a subscriber line to an electronic network, the method including:

[0012] receiving a financial instrument record associated with the transaction;

[0013] extracting a unique identifier from the financial instrument record, the unique identifier being associated with the communication line; and

[0014] interrogating at least one database based on the unique identifier to obtain data associated with the subscriber line and selectively generating a validation status.

[0015] The invention extends to a transaction processing system for processing a transaction between a vendor and an electronic terminal connected via a communication line to a communication network, the system including:

[0016] an application interface for providing a user, via the electronic terminal, with an option to select payment for the transaction from an account associated with the communication line, and receiving a user request entered into the terminal to process payment from the account; and

[0017] a modification module connected to the application interface, the modification module generating a record which includes a unique identifier associated with the communication line and communicating the record to a validation module which validates the transaction based on data associated with the unique identifier.

[0018] The invention also extends to a transaction processor interface for processing payment of a transaction, the interface including:

[0019] an application interface for providing a user with an option, via an electronic terminal, to select payment for the transaction from an account associated with a communication line to which the electronic terminal is connected, and for receiving a user request entered into the electronic terminal to process payment from the account; and

[0020] a modification module for creating a financial instrument record which includes a unique identifier associated with the communication line.

[0021] The invention extends further to a transaction validation module for validating a transaction conducted using an electronic terminal connected via a communication line to an electronic network, the module including:

[0022] an extraction module for extracting a unique identifier from a financial instrument record associated with a transaction, the unique identifier being associated with the communication line ; and

[0023] a processor module for interrogating at least one database based on the unique identifier to obtain data associated with the communication line and selectively generating a validation status.

[0024] Further in accordance with the invention, there is provided a computer program product including a medium readable by a processor, the medium carrying instructions which, when executed by the processor, cause the processor to:

[0025] provide a user with an option, via an electronic terminal, to select payment for a transaction from an account associated with a communication line to which the electronic terminal is connected;

[0026] receive a user request entered into the terminal to process payment from the account;

[0027] investigate data associated with the communication line; and

[0028] selectively approve the transaction dependent upon an outcome of the investigation.

[0029] Still further in accordance with the invention, there is provided a computer program product including a medium readable by a processor, the medium carrying instructions which, when executed by the processor, cause the processor to:

[0030] receive transaction data entered into an electronic terminal connected via a communication line to a communication network;

[0031] obtain a unique identifier associated with the communication line; and

[0032] combine the unique identifier and the transaction data to form a financial instrument record.

[0033] Still further in accordance with the invention, there is provided a computer program product including a medium readable by a processor, the medium carrying instructions which, when executed by the processor, cause the processor to:

[0034] receive a financial instrument record associated with a transaction conducted using an electronic terminal connected via a subscriber line connected to a communication network;

[0035] extract a unique identifier from the financial instrument record, the unique identifier being associated with the communication line; and

[0036] interrogate at least one database based on the unique identifier to obtain data associated with the unique identifier and selectively generate a validation status.

[0037] Other features of the present invention will be apparent from the accompanying drawings and from the detailed description which follows.

BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The invention is now described, by way of non-limiting example, with reference to the accompanying diagrammatic drawings.

[0039] In the drawings,

[0040]
FIG. 1 shows a schematic block diagram of a system, in accordance with the invention, for processing a transaction;

[0041]
FIG. 2 shows a schematic block diagram of a method used in the prior art to process a transaction electronically;

[0042]
FIG. 3 shows a schematic block diagram of a method, in accordance with the invention, for processing a transaction;

[0043]
FIG. 4 shows a schematic block diagram of a billing cycle used in the method of FIG. 3;

[0044]
FIG. 5 shows a schematic block diagram of functional modules, also in accordance with the invention, used by a vendor;

[0045]
FIG. 6 shows a schematic block diagram of transaction validation and processing modules, also in accordance with the invention, used in the system;

[0046]
FIG. 7 shows a schematic representation of a client interface in the form of an electronic terminal used to conduct the transaction;

[0047]
FIG. 8 shows a schematic representation of a screen display or layout provided at the client interface;

[0048]
FIG. 9 shows a schematic representation of a further screen layout provided at the client interface;

[0049]
FIG. 10 shows a schematic representation of a screen display at the client interface for choosing a payment method;

[0050]
FIG. 11 shows a schematic representation of a screen display at the client interface for confirming a billing telephone number (BTN);

[0051]
FIG. 12 shows a schematic representation of a screen display at the client which is displayed whilst validation of the client telephone number takes place;

[0052]
FIG. 13 shows a schematic representation of a flow diagram illustrating the validation process;

[0053]
FIG. 14 shows a schematic flow diagram of a bill cycle transaction event;

[0054]
FIG. 15 shows a more detailed schematic block diagram of the transaction validation and processing modules of FIG. 6;

[0055]
FIG. 16 shows a schematic representation of a sample telephone bill platform or account which the system automatically updates; and

[0056] FIGS. 13-15 show schematic flow charts of the validation method or procedure carried out by the validation module of FIGS. 6 and 15.

DETAILED DESCRIPTION

[0057] Referring to the drawings, reference numeral 20 general indicates a system for processing payment of a transaction. The system 20 includes a merchant or vendor 22, a plurality of client interfaces in the form of electronic terminals 24 (only 1 of which is shown in the drawings), a plurality of telephone companies (Telcos) 26 (only 1 of which is shown in the drawings), and a transaction validation and processing facility 28 including a transaction validation and processing module 30 (see FIG. 6), also in accordance to the invention. The vendor 22 includes a transaction processor interface defined by an application interface and modification module 32 (see FIG. 5) and, as will be described in more detail below, the system 20 with its transaction validation and processing module 30 allows a user to purchase goods and/or services from the vendor 22 via the electronic terminal 24 in such a fashion so that charges for the transaction are included in a telephone account 34 (see FIG. 16) of the user.

[0058] The system 20 is typically configured for use in an Internet environment in which a plurality of vendors 22 offer goods and/or services for sale on the Internet via the electronic terminals 24 which are typically personal computers (PCs). It is important to appreciate that the modules 30, 32 describe functional modules or capabilities which may be implemented by a variety of different hardware and software combinations.

[0059] Conventionally, and as shown in FIG. 2, in order to procure payment for goods and/or services, a user or purchaser using the electronic terminal 24 enters financial card details, e.g., credit card, debit card, or any other financial instrument details, which are then communicated (see line 38 in FIG. 2) to a vendor, as shown at 40, which then communicates with a credit card gateway 42. The credit card gateway 42 may then either accept or reject the transaction. However, many users are unwilling to submit financial card information to vendors, inter alia, for security reasons. Further, many users who have access to the Internet do not in fact possess financial cards (hereinafter referred to as credit cards) and are thus unable to transact via the Internet.

[0060] Referring in particular to FIG. 3 of the drawings, in one embodiment of the invention the system 20 receives transaction data 44 which is then formatted substantially to resemble a conventional credit card transaction 46 which is then converted or modified and payment for the transaction is included in a telephone bill or account as shown at block 48. As will be described in more detail below, each particular transaction or billing event is not immediately included in the telephone account 34 at the Telco 26, but during a billing cycle (see FIG. 4) which occurs periodically, e.g., daily, weekly, monthly or at any other interval. Accordingly, communications 50 take place during billing events between the transaction validation and processing facility 28 and the vendor 22 and a record of each transaction is kept at the facility 28 as shown by block 52 in FIG. 4. The facility 28, with its transaction validation and processing module 30, in an automated fashion at the end of a billing cycle, processes the transactions into the relevant telephone accounts at the relevant Telcos 26 as shown at block 54.

[0061] Referring in particular to FIG. 5 of the drawings, the vendor 22 uses the application interface and modification module 32 to interface to the communication network, typically the Internet, so that the user may communicate with the vendor 22 via the electronic terminal 24. The module 32 includes an application interface (API) 56, a customer management system (CMS) 58, an automatic number identification (ANI) module 60, a modification module 62, and a communication module 64. The communication module 64 is configured to communicate with the transaction validation and processing module 30, which is typically located offsite. In use, the API 56 provides the electronic terminal 24 with a user interface whereby the user can purchase goods and/or services and this may be provided in a conventional fashion. Once the user has selected the goods and/or services he or she wishes to purchase, the API 56 communicates a display screen or form 66 to the electronic terminal 24 as shown in FIG. 8. Typically, the API 56 requests the user to enter into the form 66 name, address, city, state, zip, day time phone number, evening phone number, or the like information. Typically, the evening phone number defines a billing telephone number (BTN) which is associated with the telephone account 34. Thereafter, the various terms and or conditions of the transaction are communicated to the user in the form of a display screen 68 as shown in FIG. 9. The user is then compelled either to accept or decline the terms by activating buttons 70, 72 respectively, typically by means of a mouse or pointing device in a conventional fashion.

[0062] Once the user has accepted the terms, the API 56 then provides the user with a display screen 74 which allows the user to select various different methods of payment for the transaction. For example, the display screen 74 includes a “Visa” button 76, a “MasterCard” button 78, “American Express” button 80, and a “bank account” button 82. However, unlike conventional systems, the system 20 provides the user with a “phone bill” button 84 whereby the user can charge the transaction to the telephone account 34 (see FIG. 16).

[0063] If the user selects the option to pay via the telephone account 34 by activating the “phone bill” button 84, the API 56 then provides the user with a screen display 86 (see FIG. 11) which requests the user to confirm the BTN associated with the telephone account 34. The screen display 86 includes a “yes” button 88 for the user to confirm the telephone number which is shown at 90, and a “no” button 92 which is activated in the event of the telephone number being incorrect. If the telephone number shown at 90 is incorrect, the user then is prompted to re-enter a corrected telephone number. Once the user has activated the “yes” button 88, the API 56 then communicates a display screen 94 to the electronic terminal 24 to advise the user that he or she should wait while the request is authorized. It is to be appreciated however that the description above is merely an example of how a user may be provided with various interfaces to allow the user to select a mode or method of payment associated with the telephone account 34. Those skilled in the art will appreciate that user data may be obtained in a variety of different ways. For example, an application may be downloaded to the electronic terminal 24 which requests and obtains the relevant data from the user and which is then subsequently communicated to the vendor 22.

[0064] The BTN which the user enters into the form 66 should correspond with the subscriber line 96 (see FIG. 1) via which the electronic terminal 24 is connected to the communication network. Accordingly, the ANI module 60 automatically identifies or determines the telephone number of the subscriber line 96 so that a comparison between the two can be made. The BTN thus defines a unique identifier associated with the communication line and with which the telephone account 34 corresponds.

[0065] The user's request, via the electronic terminal 24 and via the subscriber line 96 (which may be any communication line associated with the account 34), is then communicated to the CMS 58 which then formats the request to form a request record with information provided by the user via the electronic terminal 24 (see block 98 in FIG. 13). As shown at decision step 100, the module 32 checks to determine whether or not a credit card number is present in the record and, if so, the record is communicated to a credit card gateway for processing in a conventional fashion and the procedure terminates as shown at step 102. This situation typically arises when the user has not selected the telephone account option by activating the “phone bill” button 84 but, instead, selected one of the other methods of payment, e.g., the “Visa” button 76, the “MasterCard” button 78, the “American Express” button 80, or the “bank account” button 82.

[0066] However, if the “phone bill” button 84 has been activated and a credit card number is not present in the record, the CMS 58, in combination with the modification module 62, modifies the credit card record to include the telephone number identified by the ANI module 60. Accordingly, the credit card or financial record communicated from the vendor 22 to the transaction validation and processing facility 28 substantially resembles a conventional or industry standard credit card record except that, instead of a credit card number, the telephone number associated with the subscriber line 96 is included (see step 104). In the embodiment of the invention in which the credit card number has been replaced with the telephone number, and as the record substantially resembles and industry standard credit card record, existing or conventional customer management systems may be used to process the transaction. Thus, the CMS 58 may be a conventional customer management system.

[0067] The application interface and modification module 32 of the vendor 22, communicates the transaction record to the transaction validation and processing module 30 of the facility 28 via the communication module 64. The module 30 then receives the record as shown at step 106 whereafter it is processed. The transaction validation and processing module 30 (see FIG. 6) includes a line number extraction module 108, a processor module 110, and an OBF exchange interface 112. It is important to appreciate that the application interface and modification module 32 and the transaction validation and processing module 30 may be defined by one or more servers which are programmed appropriately. Thus, the blocks or modules may represent functional components of software running on the server. Typically, each vendor 22 has a server programmed and configured to implement the application interface and modification module 32 and the vendors 22 are connected via a communications network to a central transaction processing and validation facility 28. Accordingly the servers at the facility 28 may receive validation and processing requests from a plurality of different offsite servers provided at different vendors 22.

[0068] The processor module 110 first checks, at step 114, if all the information required for validation has been furnished by the vendor 22 and, if not, the request is returned to vendor 22 as shown in step 116. If, however, all the information required by the module 30 is present in the record, the credit card record received is then parsed and the billing telephone number (BTN) is extracted from the credit card record and formatted into a validation request as shown at step 118. Thereafter, as described more detail in FIGS. 13 and 14, the module 30 performs various checks during which the subscriber line 96 is validated (see step 120). If the BTN progresses to a LIDB interrogation step (as described in more detail below with reference to steps 264 to 286 in FIG. 17), the request is then reformatted into a LIDB request to obtain LIDB response information (see step 122). The LIDB database 124 (see FIG. 13) is then interrogated and the LIDB response is received and parsed for relevant information whereafter it is reformatted into a BTN validation request as shown at step 126. Thereafter, and as described in more detail below with reference to FIGS. 18 and 19, the processor module 110 performs further validation checks (see step 128 in FIG. 13 and steps 296 to 338 in FIGS. 18 and 19). Once the request has been investigated, the various databases have been interrogated, and the results retrieved therefrom processed, the processor module 110 then translates the validation response in to a credit card authorization response format, which is typically a conventional or industry standard format so that an industry standard or conventional CMS 58 can process the response. The response is then communicated from the facility 28 to the vendor 22 (see step 130). The CMS 58 then receives the reformatted response, updates purchase data, and creates an account for the user as shown in step 132. Thereafter, the API 56 communicates a display screen 134 to the electronic terminal 24 which thanks the user for ordering the good and/or services. Each transaction defines a billing event which is recorded at the vendor 22 and, together with other billing events, is communicated to the facility 28 at the end of a billing cycle (see block 136). Typically, this marks the end of the BTN validation procedure from the credit card authorization record translation as shown at block 138.

[0069] The method described above broadly translates a record requiring validation from an existing financial instrument form, e.g., a credit card form, to a form that is suitable to be validated based on a unique identifier associated with the subscriber line 96. Although the description above, and the more detailed description below, describe the translation from a credit card record to an appropriate record to validate a ANI/BTN, it is to be appreciated that any data associated with a financial instrument may be translated into a BTN format and, in response to validation of the BTN, the transaction may be processed. Further, the validation of the BTN may take place one or more times during the life cycle of a transaction. For example, the validation process may be executed when the user or customer request the transaction to be included in the telephone account 34 as described above and, when the facility 28 receives a plurality of billing events or transactions at the end of a bill cycle, the facility 28 may once again validate the transaction.

[0070] In certain embodiments, the user or purchaser drives an authorization event in order to establish whether or not the transaction can be billed to the telephone account 34. In this case, the Billing Telephone Number (BTN) defines the credit instrument requiring authorization for billing. The CMS 58 may then drive the request to the facility 28 in the same format as it would to a Credit Card Authorization System. An example of the conversion of a credit card billing request to a BTN validation record is described in more detail below.

[0071] 1. Credit Card Authorization Request to Billing Telephone Number Validation Request

1Credit Card Authorization Request Record99m999999123456.........2022269329Ebillittestregistration 12345 Main Streetapt 12Any CityCA950510789202226932930155919920002695Billing Telephone Number Validation Request Record99m999999999999202226932912345Main StreetCA 9505107892022269329Billing Telephone Number ValidationCredit Card Authorization RecordRecordPositionFieldExamplePositonFieldExample 1-15Tracking99m999999123456 1-15Tracking99m999999123456IDID16-35CREDIT #202226932916-25ANI*202226932936-65NAMEEbillittestregistration 66-105ADDRESS112345 Main Street26-56ADDRESS112345 Main Street106-125ADDRESS2Apt 12126-155CITYAny City156-157STATECA57-58STATECA158-163ZIP9505159-63ZIP95051164-168Zip + 4078964-67Zip + 40789169-178BTN202226932968-77BTN2022269329179-188EVENING #3015591992189-195AMOUNT0002695

[0072] 2. Billing Telephone Number Validation to a LIDB Request Record

[0073] If the Phone number passes a series of validation checks, it will then be checked against the LIDB database. In order to do that, the record must be translated in to a format specific for the LIDB process.

2Billing Telephone Number Validation Request Record99m999999123456202226932912345Main StreetCA 9505107892022269392LIDB Request RecordDR1100333333330200021234561010914132401;;102022269329Billing Telephone Number Validation RecordLIDB Request RecordPositonFieldFieldPositonFieldExample 1-15Tracking ID99m9999991234561-2MESSAGE IDDR16-25ANI*20222693293-6FIELD BIT MAP1100 7-14CUST ID3333333326-56ADDRESS112345 Main Street15-18MESSAGE TYPE020019-20LTRANS TYPE0221-26SEQ #12345657-58STATECA27-27DATA INDICATOR159-63ZIP9505128-33DATE01091464-67Zip + 4078934-39TIME13240168-77BTN202226932940-42END OF HEADER;;43-45ACCT # LENGTH1046-55ACCT #2022269329

[0074] 3. LIDB Response Record to a BTN Validation Record

[0075] Once the information is received from LIDB, the record must be translated back into a format that the Phone Number Validation System can read so the process can continue with additional checks to the phone number.

3LIDB Response RecordDR0210333333330200021234561010914132416;;20222693292019417998Billing Telephone Number Validation Request Record99m999999123456202226932912345Main StreetCA 95051078920222693292019417998LIDB Response RecordBilling Telephone Number Validation RecordPositonFieldExamplePositonFieldExample1-2MESSAGE IDDR 1-15Tracking ID99m9999991234563-6FIELD BIT MAP021016-25ANI*2022269329 7-14CUST ID3333333315-18MESSAGE TYPE020026-56ADDRESS112345 Main Street19-20TRANS TYPE0221-26SEQ #12345627-27DATA INDICATOR157-58STATECA28-33DATE01091459-63ZIP9505134-39TIME13241664-67Zip + 4078940-42END OF HEADER;;68-77BTN202226939243-52ACCT #202226932953-55RESPONSE CDOE20178-80RESPONSE CDOE20156-59PHONE COMPANY941781-84PHONE COMPANY9417##60-62PHONE COMPANY99885-87PHONE COMPANY998##

[0076] 4. BTN Validation Response Record to a Credit Card Authorization Response Record

[0077] At the conclusion of the Phone Number Validation Process, the results must be sent back to the CM System so the results can be returned to the purchaser and updated in the CM System. The BTN Validation response must be converted to a format that the CM can interpret. The BTN Validation Response Record is translated to the Credit Card Authorization Response Record for this phase of the purchase.

4Billing Telephone Number Validation Response Record99m9999991234562022269329180201N2Y5552269329YYCredit Card Authorization Response Record99m999999123456..........2022269329201N25552269329YYBilling Telephone Number ValidationRecordCredit Card Authorization RecordPositonFieldExamplePositonFieldExample 1-15Tracking ID99m99999912 1-15Tracking ID99m999999123456345616-25BTN202226932916-35CREDIT #202226932926-28BTN VAL18036-41RESPONSE CODE201N2RESPONSECODE28-32CC RESPONSE201N242-51NEW PHONE #5552269329CODE35-35AREA CODEY52-52BUSINESS LINEYCHANGE36-45NEW PHONE #555226932953-53ACCT < 90 DAYSY46-46BUSINESS LINEY47-47ACCT < 90YDAYS

[0078] Referring in particular to FIG. 14 of the drawings, at the end of a bill cycle during which a plurality of transactions or billing events or transactions have been recorded by the CMS 58, the CMS 58 communicates a billing transaction file in a credit card bill event format to the facility 28 (see step 140 in FIG. 14). Each event in the transaction file includes an indicator to indicate that the event is a phone billing transaction for inclusion in the telephone account 34. The module 30 of the facility 28 then receives the billing request file as shown at step 142, whereafter the request file is parsed, as shown at step 144, and the processor module 110 checks to see whether or not all the required information is present in the file (see step 146). If not, a code is appended to the record as show at step 148. If all the information is present in the file, the process then proceeds to step 150 where the credit card authorization to BTN validation steps 118-130, as described above, are executed. Once the validation procedure has been completed, the BTN billing response is formatted into a industry standard credit card billing response with a response code appended to the end of each record and, the records are then returned to the CMS 58 (see step 152).

[0079] At the same time, transactions or billing events which have been validated as billable and thus capable of being included in the relevant telephone account 34, are translated into an electronic message interface (EMI) format appropriate for the Telco with which the telephone account 34 is associated (see step 154). The EMI formatted file is then transferred to the Telco for billing as shown in step 156 whereafter the Telco call places each billing event on telephone account 34 associated with the subscriber line 96. Typically, the Telco returns any records that can not be billed to the telephone account 34 or that have already been billed and credited, or written off because of non payment to the facility 28 as shown at step 160. The records received by the facility 28 are in the EMI format and the facility 28 translates the record to a credit card return record including a reason code appended to the record, as shown at step 162, whereafter record is returned to the CMS 58 at the vendor 22.

[0080] An example of the billing event record conversion in which a credit card billing request is translated into a BTN billing request is set out below.

[0081] 1. Credit Card Billing Request to a BTN Billing Request

[0082] Once the purchase event has been slotted for billing, it enters the billing stream for that bill cycle. In certain embodiments, daily bill cycle records are sent to the appropriate processors. As described above, the transaction validation and processing module 30 may receive the record in the same format required by a conventional credit card processing facility.

[0083] In certain embodiments, the first step in the bill cycle is to re-validate the billable status of the BTN. This is done by following the same steps in the BTN Validation process set out above. The first step is to convert the record to a BTN Validation event record.

5Credit Card Billing Request RecordS749499M4N0000107252E100BP2623775174 0000 0004500ABPAT*MOOREH2624444444A2888 NW 87th REGENCY CIRCLED2623775174A3CEADARBURG, WI 53012-0505Billing Telephone Number Validation Request Record749499M4N0000107252E10020222693290004500888WI531020505BCredit Card Authorization RecordBilling Telephone Number Validation RecordPositonFieldExamplePositonFieldExample1-1Bill EventS 1-15Tracking ID749499M4N0000107252E1002-7Merchant ID74949916-25BTN26237751748YEARS INM (13th26-33AMOUNT0004500BUSINESSyear) 9-10MONTH,4N (April34-43ADDRESS1888.......DAY14th)11-20ACCT #0000107244-45STATEWI5221-24E10046-50ZIP5310225-25RECORDB51-54ZIP + 40505TYPE26-26BILL TYPEP55-55RECORD TYPEB27-46BTN262377517447-54AMOUNT0000045001-2ACCT INFOAB 3-32NAMEPAT MOORE33-43HOME #H262444444444-45ADDRESSA2INDICATOR46-65STREET888 NW 87thREGENCY CIRCLE66-76DAYTIME #D262377517477-78ADDRESS3A3 79-108CITY,CEADARBURG, WISTATE, ZIP530120505

[0084] 2. Phone Bill Billing Record to Credit Card Billing Response Record

[0085] At the conclusion of the revalidation during the billing process, a different response record may be written to a file. That record is typically in a format according to the Credit Card Billing Response format.

6Billing Telephone Number Billing Validation Response Record749499M4N0000107252E1002623775174180201N2N0000000000NN0004500BCredit Card Billing Response RecordS749499M4N0000107252E100BP2623775174201N2N0000000000NNBTN Billing Validation Response RecordCredit Card Billing Response RecordPositonFieldExamplePositonFieldExample 1-15Tracking ID749499M4N000010721-1BILLINGS52E100EVENT16-25BTN2623775174 2-24Tracking ID749499M4N0000107252E10026-28BTN VAL18025-34BTN262377517RESPONSE4CODE29-33CC RESPONE201N235-39RESPONSE CODE201N2CODE34-34AREA CODEN40-40AREA CODENCHANGECHANGE35-44NEW PHONE #000000000041-50NEW #000000000045-45BUSINESS LINEN51-51BIZ LINEN46-46ACCT < 90N52-52ACCT < 90 DAYSNDAYS47-53AMOUNT000450054-54RECORD TYPEB

[0086] 3. BTN Billing Validation Record to a Phone Company Deposit Record

[0087] At the same time the Billing Response is returned, all accounts that were validated as positive may be formatted into a record that is acceptable at the Telephone Company for processing.

7Billing Telephone Number Billing Validation Response Record749499M4N0000107252E1002623775174180201N2N0000000000NN0004500BPhone Company Deposit Record4250010114000000000074420000000000073640045000000000000000000000000000000000000000910200000000000000090300000002623775174000....000BTN Billing Validation Response RecordPhone Company Deposit RecordPositonFieldExamplePositonFieldExample 1-15Tracking749499M4N0001-6RECORD425001ID0107252E100TYPE16-25BTN2623775174 7-11DATE10140026-28BTN VAL RESPONSE18012-19Zero fill00000000CODE29-33CC201N220-23PROCESSOR7442RESPONSE#CODE34-34AREA CODEN24-34Zero fill00000000CHANGE000035-44NEW PHONE000000000035-38SUBCIC #7364#45-45BUSINESSN39-44AMT004500LINE46-46ACCT < 90N45-81Zero fill000...00DAYS47-53AMOUNT000450082-85OCN910254-54RECORDB 86-100Zero fill00000000TYPE0000000101-103CIC #903104-112Zero fill00..000113-122BTN2623775174123-175Zero fill000...000

[0088] 4. Negative Billing Event Records to Credit Card Negative Event Records

[0089] These BTN Billing Records are deposited at a Telephone Company for processing on to the bill page. If a charge is unable to be placed on the bill page, the event must be converted in to the Credit Card Negative Billing Event format for processing. In addition, any other negative information, such as a credit of a charge or the write-off of bad debt, must be converted to the appropriate Credit Card formats for processing by the CM. Thus, if inclusion into the telephone account 34 fails for some reason, the transaction then gets charged to the financial instrument or credit card and an industry standard credit card record is created by the module 30.

[0090] The CMS 58 typically knows how to handle the negative event by the file name that contains the records and the response code within the returned records. The file name and response codes are in the industry standard credit card processing convention.

8Phone Company Return Record42500101140000000000744200000000000736400450000000000000000000000000000MO000000000910214100000000000090300000002623775174000....000Credit Card Negative Event RecordS749499M4N0000107252E1002623775174201091501Phone Company Deposit RecordCredit Card Chargeback RecordPositonFieldExamplePositonFieldExample1-6RECORD4250011-1BILLINGSTYPEEVENT 7-11DATE101400 2-24Tracking ID749499M4N0000107252E10012-19Zero fill0000000025-34BTN262377517420-23PROCESSOR744235-37RESPONSE201#CODE24-34Zero fill00000000000038-43RETURN DATE09150135-38SUBCIC #736439-44AMT00450045-69Zero fill000...0070-71REASONMOCODE72-81Zero fill000.00082-85OCN910286-89NEW OCN1410 90-100Zero fill000...000101-103CIC #903104-112Zero fill00..000113-122BTN2623775174123-175Zero fill000...000

[0091] As mentioned above, the transaction validation and processing module 30 carries out a validation process on the telephone number associated with subscriber line 96 (see FIG. 15) and periodically processes transactions directly into subscriber telephone accounts 34.

[0092] Referring in particular to FIG. 15 of the drawings, reference numeral 200 generally indicates a more detailed schematic block diagram of an embodiment of the module 30. In the module 200, the line number extraction module 108 and the OBF exchange interface 112 are integrated into the processor module 110 which is in the form of a server.

[0093] The module 200 includes an application program interface (API) 214 which is connected to the vendor 22 or service provider (see also FIG. 5) of goods and/or services which require validation of a subscriber account. The vendor 22, which could for example be an Internet Service Provider, may request the validation of the subscriber line 96 prior to concluding an electronic transaction with a subscriber via the subscriber line 96. It is, however, to be appreciated that the API 214 may be connected to a variety of different hosts or clients which require validation of a subscriber line 96 via which the vendor 22 may carry out transactions for goods and/or services.

[0094] The vendor 22 typically communicates a request to the module 200 and forwards the subscriber line number, determined by the ANI service, to the module 200 via its API 214. The module 200 then processes the information received from the vendor 22 and provides a validation status, e.g. a code indicating a valid billable number or a code indicating that the line number is not a valid billable number (unbillable or non-billable). In particular, a plurality of codes associated with various statuses of the subscriber line 96 are communicated to the vendor 22 as described in more detail below.

[0095] The module 200 includes hardware and software to implement the invention. In particular, the module 200 includes a comparator module 218, a threshold database 220, an OFFNET database 222, an ONNET database 224, a competitive local exchange carrier (CLEC) database 226, a 42 BLOCK database 228, a block and cancel database 230, an unbilled and/or unpaid bills database 232, line identification database (LIDB) short term cache 234, a validity check module 236, a regional account office (RAO) database 238, an operating company number (OCN) database 240, an ONNET database 242, an address verification database 244, customer account record exchange (CARE) results database 246, an ANI watch database 248, and an NPA (Numbering Plan Area) exchange database 250. It is to be appreciated that, in less sophisticated embodiments of the invention, all of the above databases need not be included. However, for enhanced accuracy, all of the above databases are preferably included. Further databases may also be included further to increase the reliability of the validation process.

[0096] In addition to any one or more of the above databases, the module 200 is in communication via a conventional communication channel with an offsite or, in some embodiments, on-site line identification database (LIDB) host 252. The LIDB host 252 may include a line number portability (LNP) database. Typically, the LNP database may front end access to a plurality of industry standard LIDBs (e.g. 13 different LIDBs). The LNP database may however be a separate database. As described in more detail below, the module 200 communicates the subscriber line number to the LIDB host 252 which, in turn, communicates reference subscriber data in the form of industry standard LIDB codes back to the module 200 for processing. The module 200 then processes the LIDB codes to provide the vendor 22 with validation data relating to the subscriber line 96. Unlike conventional LIDB applications which use a LIDB to make decisions regarding destination subscriber lines or call completion decisions, e.g. decisions for calling cards, collect and third party toll services or the like, the module 200 is used to identify telephone numbers of originating subscriber lines.

[0097] Broadly, the module 200 includes a communication module formed by the application program interface (API) 214 which communicates with the communication module 64 (see FIG. 5) of the vendor 22, a processor module 110 which includes the various databases 220 to 232 as well as the comparator module 218 and the validity check module 236, and an interrogation module 256 for interrogating the LIDB host 252. It is to be appreciated that the modules may be defined by one or more servers with associated databases. Further, in the example illustrated, the LIDB host 252 is shown as a single database but may comprise many different LIDB databases maintained by various LECs and, accordingly, may be located at various different geographic locations.

[0098] Referring in particular to FIGS. 16 to 19 of the drawings, various sections of a flow chart describing the method of operation of the module 200 are shown. As described above, the vendor 22 initiates a request to the module 200 to validate a transaction to be included in the account 34 associated with the subscriber line 96. As shown at step 260, the module 200 first checks to see if the BTN number is present in the request from the vendor 22 and, if no number is present, a return code 121 is generated and communicated to the vendor as shown at step 262. The code 121 indicates to the vendor 22 that the module 200 is unable to process the request. If, however, the number is present in the request from the vendor 22, the module 200 then checks if the line number captured (hereinafter also referred to as the ANI) by the ANI module 60, and the BTN entered on the form 66 (see FIG. 8) match, as shown at step 264 (see also the comparator module 218 in FIG. 15). If, however, the ANI and the BTN do not match, then the processor module 110 generates a code 120 (see step 66) to indicate that the caller and the owner of the line number are not the same person (e.g. the user enters his or her BTN in the form 66 and uses an electronic terminal connected to a different subscriber line and is thus calling from a different ANI) and the relevant modified code is then returned to the vendor 22.

[0099] If the ANI and the BTN do match, the processor module 110 interrogates the threshold database 220 (see step 268) to ascertain whether or not the line number has reached its threshold (e.g., a predefined client threshold parameter such as an account threshold). If the line number has reached its threshold, the processor module 110 then generates a code 60, as shown at step 270, which is then communicated to the vendor 22 to indicate that the line number may not be granted service. In other words, the subscriber account cannot be billed for the goods and/or services requested by the user from the vendor 22.

[0100] If the threshold has not been reached, the module 200 then interrogates its OFFNET database 22 (see step 271) to check if the industry standard NPA/NXX and operating company number (OCN) of the subscriber line 96 is present in the OFFNET database 22. The OFFNET database 22 includes NPA/NXX and OCN combinations of operating companies with which the proprietor or user of the module 200 does not have billing and collections agreements to bill into the Telco's bill page associated with the subscriber line 96. Accordingly, the facility 20 is unable to include a charge in the account associated with the subscriber line 96 on behalf of the vendor 22 for the transaction.

[0101] If the line number is in the OFFNET database 222, then the processor module 110 generates codes 130 to 133 (see step 272) and communicates these codes to the vendor 22. The codes 130 to 133 indicate that the NPA/NXX and OCN for the particular line number 96 are not billable and, accordingly, charges for goods and/or services requested by the user cannot be included in the monthly telephone account 34 by the module 200. As shown in Table 2 below, the codes 130 to 133 provide an indication to the vendor 22 why the subscriber line 96 is not billable or deliverable. If the subscriber line number is not included in the OFFNET database 222, a check is conducted to see whether or not the subscriber line number is included in the ONNET database 224. This check is however optional in the embodiment depicted in the drawings, but may be mandatory if the module 200 does not include the OFFNET database 222.

[0102] Thereafter, as shown in step 278, the processor module 110 checks to see if the line number is found in a known CLEC table in the CLEC database 226. CLEC numbers are those line numbers that are known to have ported to a CLEC and, accordingly, the proprietor of the module 200 is thus unable to route these line numbers to the correct billing entities. If the line number is found in the CLEC database 226, then the processor module 110 generates a code 140 (see step 276) which is communicated to the vendor 22. The code 140 indicates that the BTN provided by the user is not billable for the CLEC and the module 200 can thus not charge the transaction to the subscriber account associated with the subscriber line 96.

[0103] If the line number is not found in the CLEC database 226, then the module 200 checks to see if the subscriber of the subscriber line 96 has requested a 4250 billing block as shown at step 278. In particular, the processor module 110 interrogates the 42 BLOCK database 228 and, if the number is located in the database 228, which indicates that monthly recurring charges (4250) charges are prevented from being billed to that line number, the processor module 110 generates a code 150 (see step 280) which is communicated to the vendor 22 to indicate that billing to the particular subscriber line 96 has been blocked.

[0104] If, however, the subscriber line 96 has not been blocked, the module 200 then checks at step 282 if the line number is located in the block and cancel database 230 and, if so, the processor module 110 generates codes 160 and 161 which are then communicated to the vendor as shown at step 284. The block and cancel database 230 includes requests from owners of subscriber lines, agencies, businesses, or the like that a service be canceled or blocked from further billing. Thereafter, the module 200 interrogates the unbilled and/or unpaid bills database 232, as shown at step 286, to check if there is a history of any unpaid bills and/or unbillable bills associated with the subscriber line 96. Unbillable bills relate to those subscriber line numbers where previous attempts have been made to bill charges to the subscriber account associated with the line number, and which have been returned as unbillable. If the processor module 110 locates the line number in the unbillable and/or unpaid bills database 232 then, as shown at step 288, a code 170 is generated and communicated to the vendor 22 to indicate that the line number was previously found to be unbillable and is still considered to be unbillable.

[0105] The processing described above conducts a preliminary investigation into the subscriber line number or ANI/BTN to provide an initial indication of whether or not the ANI/BTN corresponds with a billable subscriber line. Once the initial investigation has been conducted, the module 200 then uses the ANI to obtain reference subscriber line data in the form of LIDB codes from one or more industry standard databases in the form of the LIDB host or database 252. Examples of the LIDB codes used in the module 200 are shown in Table 3 below.

[0106] As shown at step 290, if the ANI is not found in the LIDB database 252, the module 200 cannot provide any validation data to the vendor 22 on this subscriber line and an appropriate code is then communicated to the vendor 22 as shown at block 292.

[0107] Once the LIDB database or host 252 has been interrogated, it returns industry standard LIDB codes and line number portability (LNP) data to the module 200 as shown in step 294 (see FIG. 18). The LIDB codes are then mapped or translated by the processor module 110 into modified validation codes (see Table 3) which provide relevant validation information to the vendor 22. As can be seen from Table 3, the same modified validation code can be generated from a plurality of different LIDB codes. Once the LIDB information codes have been returned to the processor module 110, the LIDB codes, including OCN and RAO response codes, are fed into the validity check module 236 (see FIG. 15) as shown at step 96.

[0108] As mentioned above, the LIDB host 252 may also provide LNP data to the module 200. The LNP data is used to identify subscriber line numbers that have ported to a CLEC. If a subscriber line has been ported to a CLEC, the billing ONNET status of the CLEC is verified in the CLEC database 226. The LNP identifies the facilities based CLECs which are CLECs that have been assigned all the line numbers for an NPA/NXX in a specific geographic territory. This type of CLEC would be in control of the cable, dial tone and billing envelope for that number. Typically, the LNP cannot be used to identify CLEC sellers which have resold the subscriber line under their brand, but still lease the cable and tone from an incumbent local exchange carrier (ILEC). Accordingly the facility 28 may be unable to process transaction data onto a bill page or telephone account 34 of the CLEC reseller bill page. In order to identify reseller CLECs, the module 200 compares RAO and OCN information, returned from the LIDB host 252, to data in the ONNET database 224. The OCN is the local Telco that owns the subscriber line number and the RAO is the office of the Telco that is responsible from a billing standpoint for the subscriber line number.

[0109] If the validity check module 236 determines that the response codes are invalid, the module 200 generates modified codes 180 to 999 (see step 298 and Table 2) which are communicated to the requester or vendor 22 to indicate that the mapping of the LIDB codes to the modified codes concluded that the line is an unbillable subscriber line.

[0110] If the validity check module 236 confirms the validity of the LIDB codes and, in the event of the line number being a billable line number, the processor module 110 then checks the RAO database 238 to ascertain whether or not the RAO is billable, as shown at step 300. If the RAO is not billable, then the processor module 110 generates and communicates a return code 143 (see step 302) to indicate to the vendor 22 that the line number belongs to a CLEC which is not billable by the module 200.

[0111] In a similar fashion, at step 304 the processor module 110 checks to see if the OCN returned from the LIDB host 252 corresponds with a known CLEC or if the OCN corresponds with an OFFNET OCN and is therefore also unbillable. If the line number corresponds to an OCN that is not billable, a return code 142 is generated by the processor module 110 and communicated to the vendor 22 (see step 306).

[0112] If the subscriber line number has passed the RAO and OCN checks and, accordingly, it appears that the number is billable, the processor module 110 then checks to see if a new NPA /NXX and OCN combination for this line number is guidable to the correct local Telco for billing (see step 308). If the line number is not guidable, then the module 200 generates a code 141 at step 310 which is communicated to the vendor 22 to indicate that, even though the line number is billable, the facility 28 is unable to guide the billing information to the new Telco for billing. Accordingly, the telephone number is in fact non-billable insofar as the facility 28 is concerned and a decline status is therefore communicated to the vendor 22.

[0113] The abovementioned steps are carried out to ascertain whether or not the subscriber line 96 can be billed for the goods and/or services requested. However, to enhance the accuracy or reliability of the module 200, further checks or verification are conducted as described below.

[0114] In the event that the subscriber line number has passed or complied with the abovementioned checks, and has thus not yet been rejected, the module 200 performs address verification procedures at step 312. The module 200 then interrogates an address verification database 244 to compare the address or location data (e.g. a ZIP code) supplied by the user via the form 66 (see FIG. 8) with reference address data as shown at step 312. If, however, the address supplied by the user does not match with the address in the verification database 244 or, the addresses are not within a predefined range or area, the processor module 110, as shown at step 314, generates codes 10 to 39 which are then communicated to the vendor 22 to indicate the level of likelihood that the caller (ANI) and the account owner are the same person.

[0115] During the address verification step 312, the module 200 interrogates a customer account record exchange (CARE) database (which can be an on-site database which is regularly updated), to provide enhanced reliability. In particular, the CARE database or information site is typically one or more industry standard offsite databases which allow consumers to select or change their long distance service provider. Local Telcos forward specific customer information to the LEC associated with the subscriber. The information communicated typically includes a new phone number, billing address, installation date, the person or organization responsible for the account, or the like.

[0116] As shown at step 316, the module 200 interrogates the CARE database or information site and CARE data is then loaded into CLEC and new line databases to perform certain fraud and billing checks. The CARE information investigation occurs after a successful validation event. Once the module 200 has validated the subscriber line 96, the subscriber line number data is sent to a CARE database provider hosting the CARE database 246 to obtain the BNA and age of the account. The information is typically returned within 48 hours and then processed. Care records that are returned without BNA and CLEC ACCOUNT codes are inserted into the CLEC database 226 for future reference. Accordingly, if the BTN is presented again at a later date, it will fail the CLEC check step (see step 274 in FIG. 17).

[0117] The ANI watch database 248, which includes historical and adjusted information, is used by the module 200 to determine if the account has previously been adjusted (see step 316). Typically, this step includes ascertaining previous requests by the subscriber for credit, obtaining data on any written off amounts for charges that were billed to a bill page, or the like.

[0118] If adjustments have previously been made to the account associated with the subscriber line 96, the processor module 110 generates codes 1 to 5 (see step 318) to indicate to the vendor 22 that the adjustments have been made. If no adjustments have been made, the processor module 110 checks to see whether or not the line number has a business line indicator as shown at step 320. If the business line indicator is active, the module 200 generates a code 70 (see step 322) which is communicated to the vendor 22 to advise that the line is a business line. Thereafter, as shown in step 324, the processor module 110 checks to see if the subscriber line number has been in service for less than about 90 days and, if so, a return code 80 (see step 326) is generated to advise the vendor 22 who may then selectively decide whether or not to conclude the transaction. A database of new numbers may be updated with the new number.

[0119] Thereafter, the module 200 interrogates the ANI watch database 248 (see step 328) to ascertain whether or not the area code of the line number has been changed or is scheduled to change. This interrogation is typically for billing purposes only and is not used to decide upon the validity of the request. In this step, the vendor 22 requesting the validation typically updates the billing file with the new area code number, and the processor module 110 generates a code 110 (see step 330) to advise the vendor 22 of the scheduled change to the area code.

[0120] Once the line number has passed all the aforementioned checks, the module 200 then concludes that the subscriber line 96 obtained using ANI techniques is in fact a billable line and, accordingly, the transaction may be charged directly to the account of the subscriber. Accordingly, the module 200 then generates a code 000 (see step 334) which is communicated to the vendor 22. The code 000 defines an approved status following both a billable line number inquiry as well as several fraud checks which are carried out by the fraud control module 332. If the line number has passed the abovementioned checks and the return code 000 is generated, the process terminates at block step 336. Thus, step 336 defines the end of the process during which the various checks have been conducted on the subscriber line 96 to assess whether or not it is a billable subscriber line that charges may be billed to. Step 338 defines the last step to which the process jumps when, at any point during the abovementioned process, the line number is found not to be billable (e.g., a creditworthy decision was requested by the vendor 22) and the inquiry is accordingly terminated and the relevant code is communicated to the vendor 22.

[0121] The abovementioned steps are typically executed in real time. However, information sources that do not allow checks on the line number in real time may be are carried out subsequently on the line number. Typically, once the real time evaluation is carried out and the return code 000 is communicated to the vendor, and the vendor 22 decide to proceed with the transaction, transaction data is then periodically returned to the module 200 by the vendor 22 for a pre-billing validation check or actual billing. During actual billing the module 200 accesses an account folder of the subscriber line at the Telco 26 and inserts the charges due to the vendor 22 into the telephone account 34. As shown at step 340, line numbers are sent to the CARE database 246 to determine if the BNA is available at the local Telco 26. If the folder or telephone account 34 is not available, the local Telco 26 typically sends the BNA and codes as to why the number is unavailable to the facility 28. If the BNA is found in the CARE database 246, the processor module 110 then checks to see whether or not the account was created within the last 90 days as shown at step 342. If the account was not created within the last 90 days, then the business indicator is checked as shown at step 344 and the process ends as previously shown at step 346. If, however, the number was found in the CARE database 246, the account was created within the last 90 days, or has an active business indicator then the module 200 generates the appropriate codes which are communicated to vendor 22 and the process terminates as shown at step 348.

[0122] The above process has been described in terms of modified codes set out in Table 2 but, it is to be appreciated, that the mapping or translation of the LIDB codes may produce any other defined set of corresponding codes so long as the codes are mapped onto, or generated in response to, any one or more of the industry standard LIDB codes.

[0123] A summary of the codes generated by the module 200 during execution of the validation process is provided in Table 1 below.

9TABLE 1Modified codes generated during the BTN Validation Process.Code Generated and ref to flow chartsDescription of codeReturn Code 121Indicates inability to proceed with validation; returned torequestorSee step 264Checks if ANI captured and BTN provided match (notrequired in all scenarios)Return Code 120Indicates caller and # (line number) owner are not thesame person; returned to requestorSee step 268A defined Threshold limits the number of attempts on that# within a certain timeframeReturn Code 60Indicates # may not be granted service; returned torequestor.See step 271Checks the NPA/NXX and OCN to those in the OFFNET.OFFNET = NPA/NXX and OCN combinations whereproprietor of the module 200 does not have a Billing andCollections agreement to bill into the Telco's' bill page.Return Code 130-Indicates that NPA/NXX & OCN for that Number are not133billable; returned to requestorSee step 274Checks the line number to see if found in known CLECtable. These are numbers that are known to have portedto a CLEC. Proprietor is unable to route these # to thecorrect billing entities.Return code 140Indicates # not billable for CLEC; returned to requestor.See step 278Checks line # to see if owner has requested a 4250Billing block. This block prevents monthly recurring(4250) charges from being billed to that line #.Return Code 150Indicates that requested a block of billing; returned torequestor.See step 282Checks line number for inclusion in the Block and Canceldatabase. This database includes requests from line #owners, agencies, businesses etc that have requestedthat service be cancelled and or blocked from furtherbilling.Return Code 160-Indicates number found in Block and Cancel and is not161billable; returned to requestor.See step 286Checks line # for unbillable history. Unbillables are #swhere tried to bill charges previously and have beenreturned as unbillable.Return Code 960Indicates # has unbilled before and is still consideredunbillable; returned to requestor.See step 290If # not found in Unbillable, then routed to LIDB for info.ITEMDescriptionSee step 294Identifies info returned from LIDB re. that line #; ResponseCode = status about that # as a call termination point. OCN =Operating Company # = the local Telco that owns that #. RAO= Regional Accounting Office = the office of the Telco that isresponsible from a $ flow standpoint for that #.See step 296Checks the validity of the LIDB code returned for the numberas a Billable #. This is where the mapping of the LIDB codesto the proprietor validation codes happens.Return Code 180-999Indicates the mappings of the LIDB codes to the proprietor Valreply codes. Each of these indicate a non-billable #; returnedto requestor.See step 300Checks if RAO returned is an RAO that is not billable.Return CodeIndicates that the # belongs to a CLEC and is unbillable;143returned to requestor.See step 304Checks if OCN returned from LIDB is a known CLEC orOFFNET OCN and therefore unbillable.Return codeIndicates that the new OCN is not billable; returned to142requestor.See step 308Checks to see if new NPA/NXX & OCN combination for # isguidable to the correct local Telco for billing.Return codeIndicates that even though the # is billable, eBillit is unable to141guide to the new Telco for billing; unguidable = unbillable; #returned to requestor.The steps to indicate if # is billable have been completed.The next steps provide additional information about the # for the requestore.g. to decide if and how much credit to extend for services. They alsoprovide additional billing information.See step 312Provides address verification (if required). Matches # toaddress to determine likelihood of person dialing to the personthat owns the acct at local Telco.Return CodeIndicates the level likelihood that the caller (ANI) and acct10-39owner are the same. Returned to requestor.See step 316Checks to see if # has had adjustment activity previously.This includes request for credit, written off for charges thatbilled to a bill page. Requestor makes credit decision basedon #s history of credits, adjustments, write offs.Return CodeIndicates the type and source of adjustment to charges to that1-5#. Returned to requestor.See step 320Checks to see if the # has a business line indicator.Requestor decides if would like to extend service or not.Return CodeIndicates that the # is identified as a business.70See step 324Checks to see if the # has been in service less than 90 days.Requestor makes a decision about how much service to offer# without much payment history.Return CodeIndicates that the # has been in service less than 90 days.80See step 328Checks if the Area Code of the # has been scheduled tochange. This is for billing information purposes only.Requestor updates billing filed with new number.Return CodeIndicates Area Code has been scheduled to change. New110number is appended to end of record.See step 334If the number passes all the previous checks, then 000 code isreturned to requestor. The Validation is complete for thisrequest.See step 338End of validation for numbers that did no pass or were foundin other checks.END OF REAL TIME VALIDATION EVENTInformation sources that do not allow checks on the # in Real-time (r-t),happen on # that was returned as 000 after the r-t validation event hascompleted. The #s are loaded into the appropriate databases. Thisinformation will be provided once the # is returned for billing.Steps 340, 342, 344Indicates path for those #s returned with a000 code.See step 340#s are sent to CARE source to determine ifBNA (billing Name and Address) availableat local Telco. Telco sends BNA andcodes as to why unavailable.CLEC#s that are returned with codes thatindicate the # has moved to a CLEC fromthe local Telco are loaded into the CLECtable.See step 342#s are sent to the CARE source todetermine if the account has been crestedwithin the last 90 days. The responsecodes indicate this condition.New within 90#s that are returned with codes thatindicate this condition are loaded into theNEW table.See step 344#s are sent to a Business source. Thissource identifies which numbers belong tobusinesses.Biz tableNumbers that are indicated as being line#s that belong to businesses are loaded inthis table.

[0124] Table 2 below provides the various actions which are executed in response to a modified validity code. The table provides a description and explanation of each code. Return codes 001 to 969 relate to failure codes which are generated by the module 200 prior to investigation of the LIDB host 252. Return codes 180 to 451 are generated during the LIDB code checks. In the event of the subscriber line 96 failing the checks carried out on it, the module 200 provides optional use of a credit card and, accordingly, Table 2 sets out codes which the module 200 generates in response to executing a standard credit card enquiry for a particular transaction. If the module 200, which is typically defined by a server and associated databases, is down, codes 994 to 999 are generated and communicated to the vendor.

10TABLE 2Validation & BNA Reply CodesCodeActionDescriptionExplanationBILLABLE CODES000ApprovedBillable; was not found duringPassed all billing and fraud control checksfraud control checksFRAUD CONTROL CODESANI WATCH (adjustments to bill)001VerifyBillable; found in ANI WATCH -Passed all billable checks; but ANI hadCLIENT source allbeen adjusted previously at vendor's,Client's or telco's request for your Client #002VerifyBillable; ANI WATCH - CLIENTPassed all billable checks; but ANI hadsource Clientbeen adjusted previously at Client'srequest for your Client #003VerifyBillable; ANI WATCH - CLIENTPassed all billable checks; but ANI hadsource Telco or Vendorbeen adjusted previously at vendor's ortelco's request for your Client #004VerifyBillable; found in ANI WATCH -Passed all billable checks; ANI had beenGLOBALadjusted previously at vendor's, Client's ortelco's request for all Client ids005VerifyBillable; found in ANI WATCH -Passed all billable checks; ANI had beenPRODUCTadjusted previously at vendor's, Client's ortelco's request for same product typeZIP VERIFICATION010VerifyBillable; Unable to match ZIPPassed all billable checks; unable to findinvalidthis Zip code for this NPA/NXX -011VerifyBillable; ZIP does not matchPassed all billable checks; Zip code doesnot match this NPA/NXX012VerifyBillable; ZIP matches to samePassed all billable checks; Zip codeMetropolitan areamatches to same Metropolitan area asNPA NXX.ADDRESS VERIFICATIONNote: The result of an AVS check does not mean that the transaction is declined. Thisinformation is advice only. The system compares the AVS data with billing informationfor the buyer and passes the results of the comparison to the merchant.020VerifyBillable; BNA match not foundPassed all billable checks; no BNA matchfound for ANI021VerifyBillable; Unable to verify BNAPassed all billable checks; unable to verifyinvalidBNA to ANI info sent022VerifyBillable; with zip-Match, plus4-Passed all billable checks; BNA Zip code +Match, locale-Match4 & locale (street address) matches infosent for ANI, Name does not match023VerifyBillable; with zip-Match, plus4-Passed all billable checks; BNA Zip code +Match, NoMatch-locale.4 matches info sent for ANI but locale(street address) does not match024VerifyBillable; zip-Match, NoMatch-Passed all billable checks; BNA Zip code &plus4, locale-Match.locale (street address) matches info sentfor ANI but + 4 does not match025VerifyBillable; zip-Match, NoMatch-Passed all billable checks; BNA Zip codeplus4, NoMatch-locale.matches info sent for ANI but locale(street address) & + 4 does not match026VerifyBillable; NoMatch-zip, plus4-Passed all billable checks; BNA +4 andMatch, locale-Match.locale (street address) matches info sentfor ANI but Zip does not match027VerifyBillable; NoMatch-zip, plus4-Passed all billable checks; BNA +4Match, NoMatch-locale.matches info sent for ANI but locale(street address) and Zip does not match028VerifyBillable; NoMatch-zip, NoMatch-Passed all billable checks; BNA localeplus4, locale-Match.(street address) matches info sent for ANIbut ZIP and +4 does not match029VerifyBillable; NoMatch-zip, NoMatch-Passed all billable checks; BNA does notplus4, NoMatch-locale.match zip, + 4 or locale (street address)sent for ANI030GoodAddress & Zip Match031VerifyAddress Match, Zip No Match032VerifyAddress Match, Zip ServiceUnavailable033VerifyAddress No Match, Zip Match034VerifyAddress No Match, Zip No Match035VerifyAddress No Match, Zip ServiceUnavailable036VerifyAddress Service Unavailable, ZipMatch037VerifyAddress Service Unavailable, ZipNo Match038VerifyAddress Service Unavailable, ZipService UnavailableAREA CODE CHANGE INDICATOR110UpdateIndicates there has been an areaCode is sent in addition to the validationcode change for this NPA/NXXresponse codes. New phone number isappended to record. Provided to updatethe account with the correct BTN.MISC120VerifyBTN and AMI do not matchFor use where BTN and ANI are passedand do not match.121VerifyBTN or ANI are missing fromFor use where BTN and ANI is missingrecordfrom recordUNBILLABLE CODESOFFNET130UnbillableNPA/NXX found in OFFNET -Area code/exchange (NPA/Nxx)GLOBALcombination resides in OFFNET DB.OFFNET is a territory where the LEC(Local Exchange Carrier) is unable toprovide 3rd party presentation in to it'senvelope.131UnbillableNPA/NXX found in OFFNET -Area code/exchange (NPA/Nxx)CLIENT SPECIFICcombination resides in OFFNET DBspecific for this Client id.132UnbillableNPA/NXX found in OFFNET -Area code/exchange (NPA/Nxx)PRODUCTcombination resides in OFFNET DBspecific for this product type.133UnbillableNPA/NXX NOT VALIDArea code/exchange is not a valid areacode exchangeCLEC (CLECs are unable to provide 3rd party bill presentation in their envelopes.)140UnbillableLine number (NPA/Nxx-xxxx) inBTN has been ported to a CLECCLEC Territory(competitive local exchange carrier).141UnbillableNPA/Nxx not ON NETBTN has been ported to a CLEC(competitive local exchange carrier) and isnot billable.142UnbillableLine number OCN in CLEC OCNOperating Company number for this BTNtablewas found on CLEC OCN table. Thenumber is not billable.143UnbillableLine number RAO in CLEC RAORegional Accounting Office number for thistableBTN was found on CLEC RAO table. ThisBTN is not billable.42 BLOCK (4250s Only)150UnbillableLine Number has a block for 4250Consumer has requested a block for allrecordsMRCs (monthly recurring charges) frombeing billed to this phone number.BLOCK & CANCEL160UnbillableGLOBAL — Line number has beenConsumer requested block to stop allblocked to stop all charges.charges from being billed to this number.161UnbillableCLIENT — Line number has aConsumer requested a block to stopblock to stop all charges from thischarges from being billed or to cancelClient id.service for this phone number from thisClient id.UNBILLS960UnbillableLine number is Unbillable.Line number has been returned from theLocal Telephone companies within th last 6months as unable to be billed.LIDB FAILURE180UnbillableLine number failed LIDB check -Line Number has been returned from LIDBGENERALas unbillable.181UnbillableVacant NPA NXXNo working line #s in NPA NXX182UnbillableNo Incoming CallsLine # cannot accept incoming calls183UnbillableDenied ANIAuto decline of all attempts from this ANI184UnbillableCalling Card blockAuto decline of Calling Card number185UnbillableCollect Call BlockAuto decline of Collect calls to this number186UnbillableThird Party Call BlockAuto decline all Third Party billed calls tothis number187UnbillableCredit Card BlockAuto decline of charges billed to CreditCard188UnbillableGroup Number BlockAuto decline of attempts from this group.189UnbillableAudiotext BockNumber does not allow audiotext calls.190UnbillableExcessive Calling Card PIN hitsThreshold for calling card attempts hasbeen exceeded.191UnbillableLine Number BlockAuto decline of all charges to this number200UnbillableExcessive Use - BTNBTN has exceeded threshold201UnbillableExcessive Use DNDN has exceeded threshold202UnbillableExcessive Use - ANIANI has exceeded threshold203UnbillableExcessive USE - Calling Card PinCalling Card Pin has exceeded threshold220UnbillableFeature Group ALocal telephone switch is Feature Group A221UnbillablePBX lineLine # is a PBX line222UnbillableWATS lineLine # is a WATS line223UnbillableHotel/Motel Auto Quote w/ taxHotel/Motel Auto Quote w/ tax224UnbillableHotel/Motel Auto quote w/o taxHotel/Motel Auto quote w/o tax225UnbillableDormitory lineLine # belongs to a dorm226UnbillableHospital lineLine number belongs to a hospital227UnbillableCentrex lineLine number belongs to CENTREX228UnbillableAlternate Service ProviderLine # belongs to an alternate serviceprovider229UnbillablePOTS line (collect or third partyLine # is plain old telephone service linescalls)for business or residential230UnbillablePager #Line number belongs to pager231UnbillablePCS/Mobile/Cellular #Line number belongs to a wireless provider240UnbillableLine was disconnected w/oLine # was disconnected w/o a referralreferralnumber241UnbillableLine Number changingLine is not connected yet.242Unbillablenot used243UnbillableDISCO w/o referralLine number has been removed fromservice w/o referral244UnbillableTemp DISCOLine number has been removed fromservice temporarily245UnbillableDISCO with referralLine number has been disconnected w/referral or Operator takes calls246UnbillableTemp DISCO w/ referralLine number has been removed fromservice temporarily w/ referral250UnbillablePOTS line rating on rate planPOTS line is on a rate plan for business orresidential message rate 1 or 2 or flat rate300UnbillablePublic - Incompatible interfacePublic phone with incompatible interface301UnbillableLEC Public Standard PreP OTLEC Public phone standard interface;prepay overtime302UnbillableLEC Public AlternateLEC Public phone alternate interface;functions controlled by set303UnbillableLEC Public Standard PP OTLEC Public phone standard interface;postpay overtime304UnbillableIC PublicIC Public Phone - Alternate Interface305UnbillableIC Public StandardIC Public Phone - Standard Interface306UnbillableLEC Public Special - PP OTLEC Public Phone - Special billing postpaid OT307UnbillableLEC Public Special - PreP OTLEC Public Phone - Special Billing; Prepay OT308UnbillableLEC Semi PublicLEC Semi Public Phone309UnbillableLEC Semi Public Phone (noLEC Semi Public Phone does not allowcollect or 3rd Party calls)collect or 3rd party calls to this number310UnbillableLEC Prepaid CardLEC Prepaid Card Telecommunicationsstation311UnbillableIPP (fka COCOT) StandardPayphone Standardinterface312UnbillableIPP (fka COCOT) AlternatePayphone - Alternateinterface313UnbillableCoinless (non IPP fka COCOT)Coinless Pay phone314UnbillableCoinless (IPP fka COCOT)Coinless payphone315UnbillablePrison (non IPP fka COCOT)Prison payphone316UnbillablePrison (IPP fka COCOT)Prison Payphone450UnbillableBNS: Voice Quote - without taxCharge quotes without tax451UnbillableBNS: Voice Quote - with taxCharge quotes with taxCREDIT CARD RESPONSE CODES000ApprovedCredit card approved501Decline/ErrorUser authentication Failed502Decline/ErrorInvalid tenderYour merchant bank account does notsupport the following credit card type thatwas submitted503Decline/ErrorInvalid transaction typeTransaction type is not appropriate for thistrans-action. For example, you cannotcredit an authorization-only transaction.504Decline/ErrorInvalid amount505Decline/ErrorInvalid merchant informationProcessor does not recognize yourmerchant account information. Contactyour bank account acquirer to resolve thisproblem.512Decline/ErrorDeclinedPlease check the credit card number andtransaction information to make sure theywere entered correctly. If this does notresolve the problem, have the customercall the credit card issuer to resolve.513Decline/ErrorReferralTransaction was declined but could beapproved with a verbal authorization fromthe bank that issued the card. Submit amanual Voice Authorization transactionand enter the verbal auth code519Decline/ErrorOriginal transaction ID not foundThe transaction ID you entered for thistransaction is not valid.520Decline/ErrorCannot find the customerreference number522Decline/ErrorInvalid ABA number523Decline/ErrorInvalid account numberPlease check credit card number and re-submit.530Decline/ErrorAccount Lookup informationAccount provided found in system,Mismatchhowever, unique key provided does notmatch unique key in system.531Decline/ErrorAccount does not existAccount provided not found in system1102Decline/ErrorInvalid expiration datePlease check and re-submit525Decline/ErrorTransaction type not mapped tothis host526Decline/ErrorInvalid vendor account527Decline/ErrorInsufficient partner permissions528Decline/ErrorInsufficient user permissions550Decline/ErrorInsufficient funds available551Decline/ErrorInvalid transaction returned fromhost552Decline/ErrorProcessor not available553Decline/ErrorCredit errorPlease make sure you have not alreadycredited this transaction, or that thistransaction ID is for a creditabletransaction. (For example, you cannotcredit an authorization.)5110Decline/ErrorVoid errorPlease make sure the transaction IDentered has not already been voided. Ifnot, then look at the Transaction Detailscreen for this transaction to see if it hassettled. (The Batch field will be set to anumber greater than zero if the transactionhas been settled). If the transaction hasalready settled, your only recourse is areversal (credit a payment or submit apayment for a credit).555Decline/ErrorCapture errorOnly authorization transactions can becaptured556Decline/ErrorFailed AVS checkAddress and Zip code do not match557Decline/ErrorCannot exceed sales capFor ACH transactions only558Decline/ErrorCVV2 Mismatch800UnbillableLNP Only Look-Up, number wasLNP Only Look-Up, number was found in thefoundLNP GTT database as ported.801UnbillableLNP Only Look-Up, number was notLNP Only Look-Up, number was not found infoundthe LNP GTT database, not ported.802UnbillableLNP Only Look-Up, the NPANXX isLNP Only Look-Up, the NPANXX is not anot a portable range.portable range.SYSTEM DOWN994ResubmitMessage Format ErrorMessage received in invalid orunrecognized format.995ResubmitTime outSession timed out.996ResubmitConnection FailureUnable to connect.997ResubmitSubsystem FailureSubsystem, such as LIDB, Credit Card,etc, not available.998ResubmitNetwork FailureNetwork Not Available999ResubmitSystem DownSystem Unavailable

[0125] As mentioned above, the module 200 translates the LIDB codes into modified verification codes as shown in Table 2. These modified validity codes are then mapped or translated. Table 3 below provides a list of the modified validity codes which are generated following the mapping carried out by the processor module 110 to translate LIDB codes to the modified verification codes set out in Table 1.

11TABLE 3LIDB/LNP SOURCE TRANSLATIONS for ISP:LIDBResp.Resp.ADMINrtfcType InCode InACTION?DescriptiontypeEBI Code OutAPP000ApprovedCalling card has an Unrestricted PIN.G1000APP001ApprovedCalling card has a Restricted PIN. The switch mustg1000verify that the DNI matches the first 10 digits of thecalling card before placing the call.APP004ApprovedCollect call - No verification is required.G1000APP005ApprovedThird-party call - No verification is required.G1000APP006ApprovedThere is a system error.S999APP008ApprovedCommunications Link Tests “Good.”S999APP010ApprovedCommercial credit card is approved and the zip codeG1000matches, if the zip code was sent.APP011ApprovedYBill-to number has an Admin. Override to automaticallyG1000approve the transaction. (Admin. Reply)APP012ApprovedOriginating number (ANI) has an Admin. Override toG1000automatically approve the transaction. (Admin. Reply)APP013ApprovedDialed number (DNI) has an Admn Override toG1000automatically approve the transaction. (Admin. Reply)APP014ApprovedGroup number has an Admin. Override to automaticallyG1000approve the transaction. (Admin. Reply)APP015ApprovedCommercial credit card is approved but the zip codeCC500check is unavailable.APP016ApprovedCommercial credit card is approved but the zip codeCC501check is unavailable. Retry later.APP096ApprovedCommercial credit card is approved but the zip codeCC502check is not supported.APP018ApprovedCommercial credit card is approved and the addressCC503matches but the zip code does not match.APP019ApprovedCommercial credit card is approved and the addressCC504and the zip code match.APP020SuccessLNP Only Look-Up, number was found in the LNP GTTLNP800database as ported.APP021SuccessLNP Only Look-Up, number was not found in the LNPLNP801GTT database, not ported.CON050VerifyCollect call number has no block. Verify acceptance ofo1000the charge.CON051VerifyThird-party call number has no block. VerifyO1000acceptance of the charge.CON053DeniedUnable to authorize, Automatic Code Gapping is inS999effect at the LIDB. Every third query is dropped by theLIDB.CON0110DeniedYExcessive Use - The bill-to number exceeded the highG3000limit threshold in the Admin. fraud control system.(Admin. Reply)CON055DeniedYExcessive Bad PIN Attempts - The threshold for bad PINO2000attempts for the calling card was exceeded in theAdmin. fraud control system. (Admin. Reply) This is thesame as reply code 309.CON060ConditionalYLow Limit Warning - The bill-to number exceeded theG3000low limit threshold in the Admin. Fraud control system.(Admin. Reply)CON061ConditionalYLow Limit Warning - The dialed number exceeded theG3000low limit threshold in the Admin. fraud control system.(Admin. Reply)CON062DeniedYExcessive Use Dialed - The dialed number exceededG3000the high limit threshold in the Admin. fraud controlsystem. (Admin. Reply)CON063ConditionalYNo Host Still Billable - There is no LIDB check available,G2180but the Customer has a billing agreement with this LEC.(Admin. Reply)CON064ApprovedYCommercial credit card is approved but the zip codeCC505and the address do not match.CON065ConditionalYLow Limit Warning - The ANI exceeded the low limitG3000threshold in the Admin. fraud control system. (Admin.Reply)CON066DeniedYExcessive Use ANI - The ANI exceeded the highG3000threshold in the Admin. fraud control system. (Admin.Reply)CON070ApprovedCalling card has no service denial in the Card ServiceG1000Denial Indicator field. Calling card calls may be billed tothis card number.CON071ApprovedCalling card has no service denial in the Pin ServiceG1000Denial Indicator field. Calling card calls may be billed tothis card number.CON080VerifyCollect calls - Accept intralata, Reject interlata collectO1000calls. Recommend verify acceptance of the charge.CON081VerifyThird-party calls - Accept intralata, reject interlata third-O1000party calls. Recommend verify acceptance of thecharge.CON082VerifyCollect calls - Accept intralata, verify interlata collectO1000calls. Recommend verify acceptance of the charge.CON083VerifyThird-party calls - Verify intralata, reject interlata third-O1000party calls. Recommend Verify acceptance of thecharge.CON084VerifyCollect call - Verify acceptance of the charge by anO1000Operator.CON085VerifyThird-party call - Verify acceptance of the charge by anO1000Operator.CON086VerifyCollect call - Accept intralata charge, verify interlataO1000charge with Operator.CON087VerifyThird-party calls - Verify intralata charge with operator,O1000reject interlata charge with Operator.CON088VerifyCollect Calls: POTS Line (Business/Residential)G5000CON089VerifyThird-Party Calls: POTS Line (Business/Residential)G5000CON090VerifyBNS: Centrex Line, Collect calls - Some LECs allowG4000billing to this type of line, others do not. VerifyAcceptance.CON091VerifyBNS: POTS Line - Residential - Message rate 1G9000CON092VerifyBNS: POTS Line - Residential - Message rate 2G9000CON093VerifyBNS: POTS Line - Business - flat rateG9000CON094VerifyBNS: POTs Line - Business - message rate 1G9000CON095VerifyBNS: POTS Line - Business - message rate 2G9000CON096VerifyBNS: POTS Line - Residential - flat rateG9000DENY100DeniedMessage Format Error MessageS994DENY100DeniedMessage Format Error - Date formatS994DENY100DeniedMessage Format Error - Header Message ErrorS994DENY100DeniedMessage Format Error - Merchant ID ErrorS994DENY100DeniedMessage Format Error - No End of Header IndicatorS994DENY100DeniedMessage Format Error - Header Data Indicator, did notS994contain data in each field of the message That wasrepresented by the message text map fieldDENY100DeniedMessage Format Error - PIN not numericS994DENY100DeniedMessage Format Error - Terminating Error (commercialS994credit card onlyDENY100DeniedMessage Format Error - Terminating Number notS994numericDENY100DeniedMessage Format Error - Originating Number not NumericS994DENY100DeniedMessage Format Error - Charge Number not NumericS994DENY100DeniedMessage Format Error - No End Header IndicatorS994DENY101DeniedMessage Format Error Invalid Customer/Terminal IDS994NumberDENY102DeniedMessage Format Error Invalid Message TypeS994DENY103DeniedMessage Format Error Invalid Transaction TypeS994DENY104DeniedMessage Format Error Invalid Sequence NumberS994DENY105DeniedMessage Format Error Invalid Data IndicatorS994DENY105DeniedMessage Format Error - Header Data IndicatorS994DENY107DeniedBad PIN format. PINs must be equal to or higher thanS9942000.DENY200DeniedCalling card blocked, missing customer record - ThereS994is no record of that calling card number in the database.DENY201DeniedBNS, missing customer record - There is no record ofS994that line number in the database.DENY202DeniedMissing BNG - There is no record of that NPANXX inS994the database.DENY203DeniedNon billable NXX - DPC table failure. The NPANXXG2180does not have routing or allow billing, e.g. cellular.(LIDB or Admin. Reply)DENY204DeniedCalling card blocked, screened data - A screeningO2000mechanism is in place at the LIDB that does not allowcharges to this calling card.DENY205DeniedProtocol converter problem - There is a problem withS999the SS7 protocol converter.DENY206DeniedBNS & No Calling Card Calls - No Host,o2180Nonparticipating Group. This NPANXX exists but thereis no LIDB host. (LIDB or Admin. Reply)DENY207DeniedLIDB Access Denied because no queries should beS999sent to this LIDB destination. (Admin. Reply)DENY208DeniedCalling card blocked, Screened Data on PIN (PinO2000Service Denial Indicator) - A screening mechanism is inplace at the LIDB that does not allow charges to thisPIN.DENY209DeniedExternal SS7 Problem - There is a format problem inS999the SS7 networkDENY210DeniedCalling card blocked, screened data - A screeningO2000mechanism is in place at the LIDB that does not allowcharges to this calling card.DENY211DeniedCalling card is blocked because it has a bad PIN or theO2000PIN does not match database information.DENY211DeniedUnexpected Data Value, Calling card blocked, Bad PIN -O2000This means a bad PIN was used or there is no PIN onfile.DENY212DeniedCalling card blocked, PIN Excessive Use at LIDBG3000Owner. - The PIN exceeded the high threshold in theLIDB fraud control systemDENY213DeniedVacant BNG - There are no working lines in theG2181NPANXX.DENY214DeniedNo Collect calls - Collect calls are not allowed to thisO2000line number.DENY215DeniedNo Third-party calls - Third-party calls are not allowedO2000to this line numberDENY216DeniedBNS: LEC Public - Standard Interface (functionsG10303controlled by the network) - Postpay OvertimeDENY296DeniedBNS: Coinless (non IPP fka COCOT)G10313DENY218DeniedBNS: semi-public phone - No Collect or Third-party callsG10309are allowed to this line number.DENY219DeniedSpare - This LIDB response is not in use at this time.AV180DENY220DeniedTime-out, No response from Host - A response was notS180received from the host database within 4 seconds for aTelco query or 12 seconds for a Bank card query.(LIDB or Admin. Reply)DENY221DeniedBNS Data unavailable, Error Message, No Host - NoS180collect or third-party calls should be allowed to this linenumber.DENY222DeniedCalling card Data unavailable, Error Message, No Host -S180No calling card calls should be allowed to this linenumber.DENY223DeniedBNS & Calling card, screened response LIDB - AO2000screening mechanism is in place at the LIDB that doesnot allow charges to this account number.DENY224DeniedLIDB Misroute - The query was routed to the wrongS999LIDB.DENY225DeniedReject, Reroute - The LIDB could not read the format ofS994the query.DENY226DeniedUnexpected Component - The LIDB cannot interpret theS994format of the query.DENY227DeniedUDTS, SS7 Network problem - There is an SS7S999network problem.DENY228DeniedBNS: Personal Communication Service (PCS)G8231DENY229DeniedBNS: MobileG8231DENY230DeniedNot Billable - The Customer does not have a billingG2180arrangement with the LEC for this NPANXX (OCN On-Net Screening).DENY231DeniedBNS: LEC Prepaid Telecommunications Card StationG10310DENY232DeniedFeature Group A (FGA)G4000DENY233DeniedBNS: LEC Public - Alternate Interface (functionsG10302controlled by set)DENY234DeniedBNS: LEC Public - Special Billing - Postpay OvertimeG10306(functions controlled by the network)DENY235DeniedBNS: LEC Public - Special Billing - Prepay OvertimeG10307(functions controlled by the network)DENY236DeniedBNS: Public - Incompatible Network Interface (interfaceG10300other than standard or alternate)DENY237DeniedBNS: IC Public - Alternate InterfaceG10304DENY238DeniedBNS: IPP (fka COCOT) - Standard Interface311DENY239DeniedBNS: PagerG8230DENY241DeniedGeneral, Reject - The LIDB could not read the format ofS994the query.DENY242DeniedInvoke, Reject - The LIDB could not read the format ofS994the query.DENY243DeniedReturn Result, Reject - The LIDB could not read theS994format of the query.DENY244DeniedReturn Error, Reject - The LIDB could not read theS994format of the query.DENY245DeniedTransaction Portion, Reject - The LIDB could not readS994the format of the query.DENY246DeniedBNS: Vacant Number - There is no line numberG2180assigned.DENY247DeniedBNS: Disconnected without referral - The line numberG6240was disconnected with no referral to a new line number.DENY248DeniedBNS: Changed to non-published number - The lineo5000number was changed to a non-published number.DENY250DeniedNo Collect Calls, Screened Data - A screeningO2000mechanism is in place at the LIDB that does not allowcharges to this line number.DENY251DeniedNo Third-party calls, Screened Data - A screeningO2000mechanism is in place at the LIDB that does not allowcharges to this line number.DENY252DeniedBNS: Screened Data - A screening mechanism is inG7191place at the LIDB that does not allow charges to thisline number.DENY253DeniedBNS: Screened Data - A screening mechanism is inG7191place at the LIDB that does not allow charges to thisline number.DENY2110DeniedBNS & No Calling Card, Unavailable network resource -O2411This line or card number is not in the database.DENY255DeniedBNS: Screened Data - A screening mechanism is inG7191place at the LIDB that does not allow charges to thisline number.DENY256DeniedBNS: Being changed - The line number is beingG6241changed, it may not yet be connected.DENY257DeniedBNS: May not yet be connected - The line number mayG6243be new, it may not yet be connected.DENY258DeniedBNS: Temporarily disconnected - The line number isG6244temporarily disconnected.DENY259DeniedBNS: Disconnected, calls being taken by operator - TheG6245iine number is temporarily disconnected, the operator istaking calls.DENY260DeniedBNS: Temporarily removed from service - The lineG6244number is temporally removed from service.DENY261DeniedBNS: Not in service for incoming calls - This lineG2182number cannot accept incoming calls.DENY262DeniedBNS: Temporarily disconnected at customer requestG6245without referral - The line number is temporarilydisconnected at the request of the customer withoutreferral.DENY263DeniedBNS: Temporarily disconnected at customer requestG6246with referral - The line number is temporarilydisconnected at the request of the customer withreferral.DENY264DeniedBNS: Changed with referral to new number - The lineo5000number was changed. A referral to another line numberis in place.DENY265DeniedCalling card blocked, PIN Nonpayment - The callingO2000card is blocked because of nonpayment.DENY266DeniedCalling card blocked, Service Restriction on PIN - ThereO2000is a service restriction on this PIN.DENY267DeniedCalling card blocked, no PINs assigned. There is noO2000PIN assigned to this calling card/line number.DENY268DeniedCalling card blocked, service denial - There is a serviceO2000restriction on this calling card.DENY269DeniedCalling Card - The calling card is a CIID (proprietaryO2000card) for which there is no host.DENY270DeniedBNS: Unexpected Data Value - No Collect or Third-S994Party Calls are allowed.DENY272DeniedLIDB/CCC Response Time-out - A response was notS180received from the host database within 4 seconds for aTelco query and 12 seconds for a Bank query.DENY273DeniedNo Collect Calls at Customer Request - The end userO2000customer requested the block for collect calls to this linenumber.DENY274DeniedBNS & No Calling Card Calls: Screened data.O2000DENY275DeniedBNS: Hotel/Motel Auto Quote - with taxG4000DENY276DeniedBNS: Dormitory LineG4225DENY277DeniedBNS: Hotel/Motel Auto Quote - without taxG4000DENY278DeniedBNS: PBX LineG4221DENY279DeniedBNS: Prison (IPP fka COCOT)G10316DENY280DeniedBNS: WATS LineG4222DENY281DeniedNo Third-party calls at Customer Request - The endO2000user customer requested the block for third-party callsto this line number.DENY282DeniedBNS: LEC Public - Standard interface - PrepayG10301OvertimeDENY283DeniedBNS: Coinless (IPP fka COCOT)G10314DENY284DeniedBNS: IC Public - Standard InterfaceG10305DENY285DeniedBNS: Voice Quote - without taxo6450DENY286DeniedBNS: Voice Quote - with taxo6451DENY287DeniedBNS: IPP (fka COCOT) - Alternate InterfaceG10312DENY288DeniedBNS: HospitalG4226DENY289DeniedBNS: Prison (non-IPP fka COCOT)G10315DENY290DeniedBNS: LEC Semi-PublicG10308DENY291DeniedBNS: Subsystem CongestionS180DENY292DeniedBNS: Subsystem FailureS180DENY293DeniedBNS: No translation for address of such natureS180DENY294DeniedBNS: Unequipped UserS999DENY295DeniedBNS: Network FailureS180DENY296DeniedBNS: Network congestionS999DENY297DeniedBNS: Cellular (cellular is distinct from mobile)G8231DENY298DeniedBNS and Calling Card - Although the NPANXX belongsG4228to SWBT the end-user account number is no longer is aSWBT customer. The line number now belongs toanother local service provider.DENY299FailureLNP Only Look-Up, the NPANXX is not a portableLNP000range.DENY301DeniedYDenied Originating Number (ANI) - The ANI has anG2183Admin. block to automatically decline all attempts fromthis line number. (Admin. Reply)DENY302DeniedYTerminating Number (DNI) has an Admin. block toG2182automatically decline all attempts to this line number.(Admin. Reply)DENY303DeniedYCalling card has an Admin. block to automaticallyG2000decline all attempts to this line number. (Admin. Reply)DENY304DeniedYCollect Number has an Admin. block to automaticallyG2000decline all attempts to this line number. (Admin. Reply)DENY305DeniedYThird Party Number has an Admin. block toG2000automatically decline all attempts to this line number.(Admin. Reply)DENY306DeniedYCommercial credit card has an Admin. block toG2000automatically decline all attempts to this line number.(Admin. Reply)DENY307DeniedYGroup Number has an Admin. block to automaticallyG2000decline all attempts from this group. (Admin. Reply)DENY308DeniedYGlobal Negative Database Block - There is an Admin.G2000block in the Global Negative Database to this linenumber for the Audiotext Industry. (Admin. Reply)DENY309DeniedYExcessive calling card PIN hits - The threshold for badG2000PIN attempts for a calling card was exceeded in theAdmin. fraud control system (Admin. Reply). This is thesame as reply code 055.DENY400DeniedCommercial credit card, Invalid Commercial credit card -506This is not a valid commercial credit card accountnumber. It failed the MOD 10 check. Also an invalidamount, invalid date or a format error may cause thisresponse. (Host or Admin. Reply)DENY401DeniedCommercial credit card, Call issuer - The authorization507attempt triggered a flag in the fraud control system ofthe issuing bank, Banknet or VISAnet.DENY402DeniedCommercial credit card, Confiscate card - No billing is508allowed to this account number. If possible confiscatethis card.DENY403DeniedCommercial credit card, Authorization Declined - No509billing is allowed to this account number.DENY404DeniedCommercial credit card, Unable to Validate Account510Number - There is problem in authorizing this accountnumber.DENY405DeniedCommercial credit card, Card expired - No billing is511allowed to this account number because the card hasexpiredDENY406DeniedCommercial credit card - Invalid Merchant ID512DENY408DeniedCommercial credit card, Invalid card and Address (zip513code) - Both the account number and the address or zipcode are invalid. Do not allow billing to this accountnumber.DENY409DeniedCommercial credit card, System Problem - There is a514technical problem with the authorization system of theissuing bank, Banknet or VISAnet.DENY420DeniedCommercial credit card, Over withdrawal limit - This515account has exceeded the withdrawal threshold in theauthorization system of the issuing bankDENY421DeniedCommercial credit card, Over credit limit - This account516has exceeded the credit threshold in the authorizationsystem of the issuing bankDENY422DeniedCommercial credit card, Lost card, Confiscate - - This596account number was reported lost. No billing is allowedto this account number. If possible confiscate this card.DENY423DeniedCommercial credit card, Stolen card, Confiscate card -518This card was reported stolen. No billing is allowed tothis account number. If possible confiscate this card.DENY424DeniedCommercial credit card, Invalid Pin - This means a bad519PIN was used.DENY425DeniedCommercial credit card, Allowable Number of PIN Tries520Exceeded - The threshold for bad PIN attempts for acalling card was exceeded in the authorization systemof the issuing bank, Banknet or VISAnet.DENY426DeniedDuplicate transaction. The Authorization host considers521this a duplicate transaction.

[0126] In the embodiment of the invention depicted in the drawings, regardless of the type of service provider or the type of validation request, all clients or vendors 22 typically need a profile so that the process or method carried out by the module 200 knows how to treat the request. The client or vendor profile is set up in a database which includes the indicators that are set for the type and tests for each request which will be subsequently received from the vendor.

12Client or Vendor Profile TableFieldsData TypeKeyNameChar (10)ClientChar (4)PrimaryProductChar (3)TranstypeChar (3)BTN_vs_AMINull or notGlobal_OffnetNull or notClient_OffnetNull or notProduct_OffnetNull or notCalling_Card_OffnetNull or notPlan_OffnetNull or notONNETNull or notCLECNull or notBlock42Null or notUnbillNull or notCancelNull or notSmart_LIDBNull or notArea_Code_SplitNull or notZipNull or notBNANull or notBNA_AVAILNull or notThresholdNull or notClient_Bad_ANINull or notGlobal_Bad_ANINull or notProduct_Bad_ANINull or notNON-PAYNull or notGoodwillNull or notReturn_To_SenderNull or notCredit_CheckNull or notNote: Some tests are required for certain validation types.

[0127] In certain embodiments, the client or vendor profile is used to determine which validation request type to convert from or to, which validation checks should be performed on the ANI/BTN for the particular purchase event, which checks are to be performed for the pre-billing validation event at the time of billing, and the billing record conversion specifics for that client or vendor. Thus, the facility 28 may customize is validation procedures to suit a specific client or vendor.

[0128] For the both the validation events, the client profile check is typically performed in facility 28 prior to carrying out the validity checks. For example, the customer profile check may be included in step 98 (see FIG. 13) and step 142 (see FIG. 14). The customer profile includes client specific information which may determine the nature and extent of the validation process. Accordingly, the profile may be checked as soon as the record is received from a registration module or the customer management system 58. In use, a profile table is queried to identify the validation checks to be performed by the module 30 and the checks may differ between an initial purchase event or transaction and an associated subsequent billing event at the end of a bill cycle. These checks may, dependent on the client profile, include checking if the ANI is the same as the BTN, if the subscriber line is listed in OFFNET database 222, in the UNBILLS database 232, in the Blocking databases 228,230, in the CLEC database 226, in the LIDB database 252, in the address verification database 244, or in databases including data on previous credits, new lines, business lines area codes, area code changes, or the like.

[0129] Additionally, the client profile is typically checked to see which billing record should be written for inclusion on the phone bill for that particular purchase. This may occur as the first part of step 218 in FIG. 15 and step 260 in FIG. 17.

[0130] The client profile can also be used to determine the type of billing record to convert from and the type to convert to for inclusion the telephone account 34 for the purchase or transaction. For example, the types of billing records may include a 425001 record for a monthly recurring charge; 010101, 010105, 010102, 010116 type records for detailed, usage-based events; and 415001, 410101, 410105, 410102, 410116 records for the credit records.

[0131] An example of software tables for implementing the steps in the method set out in the flow diagrams shown in FIGS. 17 to 19 are shown below.

[0132] The first table shows the steps in the BTN test descriptions process. Typically, a set of core tests is run for each client. Additionally, clients may have some configuration options to identify the tests that best fit their program.

13PROCESSTESTsPURPOSEBILLABLE BTN TESTsVAL/Pre-billClient profileClient profile for each id for BTN validation process test flags.VAL onlyANI = BTNDetermines if originating number = BTN input by caller.VAL/Pre-billInvalid # OFFNETIds Invalid NPAs & NXXsVAL/Pre-billGlobal OFFNETIds (NPA)NXX & OCN combinations where there is not a B&C agreementVAL/Pre-billProduct OFFNETIds (NPA)NXX & OCN combinations where the traffic type is not approved tobill (Jul. 24, 2001: MRC only for NECA and Illuminet Only)VAL/Pre-billClient OFFNETIds (NPA)NXX & OCN combinations where there the Client id (7###) is notapproved to billVAL/Pre-billSpecial Calling CardIds (NPA)NXX & OCN combinations of special calling card #s for non-callingOFFNETcard traffic that are unable to be billedVAL/Pre-billPlan OFFNETIds (NPA)NXX & OCN combinations where a Client Plan is not approved tobillVAL/Pre-billONNETIds (NPA)NXX & OCN combinations where there are B&C agreementsVAL/Pre-billCLECIds (NPA)NXX-xxxx's are not billable due to CLEC for all Clients.VAL/Pre-bill4250 BLOCKIds (NPA)NXX-xxxx's that have a 4250 billing block(for MRC only)VAL/Pre-billUNBILLIds (NPA)NXX-xxxx's that have unbilled previously for all ClientsVAL/Pre-billBlock & Cancel -Ids (NPA)NXX-xxxx's that requested a Block and/or Cancel; usuallyGLOBALinstitutionalVAL/Pre-billBlock & Cancel -Ids (NPA)NXX-xxxx's that requested a Block and/or Cancel for a particularClient SpecificClient idVAL/1st + nVal Code CacheIds (NPA)NXX-xxxx & Return Code combinations for previous requestPre-billVAL/1st Pre-LIDB Validity TestTo determine the billable status of the return code from the LIDB dipbillVAL/1st Pre-LIDB CLEC RAOIds RAOs that belong to CLECsbillVAL/1st Pre-LIDB CLEC OCNIds known CLEC OCNsbillVAL/1st Pre-LIDB State SpecificTo determine if the returned LIDB code is a state specific code and then abillConversionconversion to the billable OCN for the ONNET checkVAL/1st Pre-LIDB ONNETIds billable (NPA)NXX & returned OCN combinationsbillALLVAL Trans LogLog of each validation request and response by Client IDBTN CREDIT SCORINGVAL/Pre-billAREA CODE ChangeProvides the new area code for the line number while in permissive dialingindicatorperiod.ValZIP MATCHZIP matches zip codes for (NPA) NXX (not in production as of June 2001)VAL/Pre-billANI WATCH - CLIENT(NPA)NXX-xxxx's where there a refund/chargeback has been issued(SOURCE: all)previously for this Client IDVAL/Pre-billANI WATCH - CLIENT(NPA)NXX-xxxx's where there a refund has been issued previously for this(SOURCE: client)Client IDVAL/Pre-billANI WATCH - CLIENT(NPA)NXX-xxxx's where there a chargeback/bad debt has been issued(SOURCE: ebi/telco)previously for this Client IDVAL/Pre-billANI WATCH - GLOBAL(NPA)NXX-xxxx's where there a refund/chargeback/bad debt has been(SOURCE: all)issued previously from CLIENT, ebi or telcoVAL/Pre-billANI WATCH -(NPA)NXX-xxxx's where there a refund/chargeback/bad debt has beenPRODUCTissued previously for the same product(SOURCE: all)VALAddress VerificationNot AvailableTEST BEFORE FIRST BTN BILLINGVAL/Pre-billLEC CARE FEEDDetermines if the ILEC owns the Acct. for billingVAL/Pre-billBiz vs ResDetermines the commercial or consumer status for credit scoreExample TESTsVAL/Pre-billThreshold by ClientDetermines whether the BTN has met a Client specific thresholdVAL/Pre-billLEC PROV feedTo determine if LEC owns AcctVAL/Pre-billCredit CheckCredit header files check from Credit sourceVAL/Pre-billNew within 90 daysDetermines if BTN is less than 90 days old; affects credit score

[0133] The OFFNET table family contains OCN & NPA_NXX combinations where billing is not approved. If found, the BTN does not continue on the validation path.

14FieldsData TypeKeyInvalid # OFFNET TableNPA_NXXNumeric(6)PrimaryOFFNET Global TableNPA_NXXNumeric(6)PrimaryOFFNET Product TableOCNInt(4)NPA_NXXNumeric(6)PrimaryNSP_ProductVarchar(10)PrimaryOFFNET Client TableOCNInt(4)PrimaryClient IDChar(4)SecondarySpecial Calling Card OFFNET TableOCNInt(4)NPA_NXX_xxxxNumeric(10)PrimaryPlan OFFNET TableClient idChar(4)PrimaryOCNInt(4)PrimaryNPA_NXXNumeric(6)PrimaryNSP_PlanChar(3)Primary

[0134] The ONNET table determines if an NPA_NXX & OCN combination can be found among the billable combinations. In this case a match, allows the BTN to move further on the validation path. A no match will return a failure.

15ONNET TableFieldsData TypeKeyOCNNumeric(4)NPA_NXXNumeric(6)Primary

[0135] The CLEC table consists of CLECs that the proprietor, or user of the module 200, does not have billing contracts with. This table is specific to the line number. Sources dictate the fields that will be present for the record. A match here is considered a fail and does not continue.

16CLEC TableFieldsData TypeKeyBTNNumeric(10)PrimaryJulianChar(3)YearChar(2)DateDateTimeOCNInt(4)

[0136] The 4250 Block table consists of specific line numbers that cannot be billed for 4250-01 record types. A match in this table stops the validation movement.

174250 Block TableFieldsData TypeKeyBTNNumeric(10)PrimaryJulianChar(3)YearChar(2)DateDateTime

[0137] Bill Control Family Tables

[0138] The Unbills or unbillable table holds all the BTNs that have been sent to a subscribers bill page but could not be placed on the bill page for various reasons. A match here halts the validation sequence for the subject BTN.

18Unbill TableFieldsData TypeKeyBTNNumeric(10)PrimaryClient idInt(4)SecondaryProductVarChar(3)TertiaryDateDateTimeReason CodeAlphaN(2)

[0139] Block and cancel tables identify BTNs that have requested a permanent or a Client specific block for billing. A match sends a failed response.

19FieldsData TypeKeyBlock & Cancel - Global TableBTNNumeric(10)PrimaryDateDateTimeBlock & Cancel - Client Specific TableBTNNumeric(10)PrimaryDateDateTimeClient idNumeric(4)Secondary

[0140] Validation Cache is a table that holds responses in order not to process duplicates (e.g., Submit pressed 10 times). A match here will return the code stored from a previous request.

20Validation Cache TableFieldsData TypeKeyBTNNumeric(10)PrimaryResponseChar(3)DateDateTime

[0141] LIDB Family Tables

[0142] LIDB is a third party that supplies information to the phone line number level. The module 30 typically tests and stores as many relevant fields as can be requested in a transaction.

21LIDB Codes TableFieldsData TypeKeyLIDBChar(3)PrimaryDescriptionChar(100)RFCChar(3)ISPChar(3)OSPChar(3)CCCChar(3)LDDChar(3)CRCChar(3)

[0143] The LIDB Validity Table translates the LIDB code into a billable or non-billable response according to predefined business rules. A fail here will halt the validation for the request.

22LIDB Validity Translation TableFieldsData TypeKeyBTNNumeric(10)PrimaryDateDateTimeLIDB_CodeChar(3)OCNChar(4)TransTypeChar(3)UpdatedbitRAOChar(3)

[0144] The State specific table is a conversion from a true OCN to a known State Specific OCN that is billable. A match here will trigger the conversion, the

[0145] BTN Continues in the Validation Process.

23LIDB State Specific OCN TableFieldsData TypeKeyST_OCNNumeric(4)PrimaryBillable_OCNNumeric(4)

[0146] The transaction log is the history of each transaction request and response that is processed through the validation system.

24VAL Transaction Log TableFieldsData TypeKeyCLIENT IDInt(3)ANINumeric(10)LidbCodeChar(3)DateDateTimePrimary

[0147] The TPM indicates that an NPA is in the permissive dialing period. A match here appends the record with the updated number for a record update.

25FieldsData TypeKeyTPM Change TableNPA_NXXNumeric(6)PrimaryDATEDateTimeTPM Delete TableNPA_NXXNumeric(6)NoneDATEDateTimeNone* See Exhibit A

Validation Table Maintenance

[0148]

26

TABLE LOAD

TABLE
SCHEDULE
SOURCE
HOW

Client profile
Adds & changes
CSA
Manual

ANI = BTN
NA
NA
NA

Invalid # OFFNET
Adds & changes
Rejects/Unbills*
Manual

Global OFFNET
2× weekly
CYCLE OFFNET
Full Replace

Thurs for Mon cycle
P:/WC30/FILES/ONOFF

Tues for Thurs cycle
CIC: 903

Product OFFNET
Fridays
Client Directory
Full Replace

Cust7000 Directory

Client OFFNET
Fridays
Client Directory
Full Replace

CYCLE files

Load for each client id.

Special Calling Card
Fridays
CYCLE OFFNET
Full Replace

OFFNET

P:/WC30/FILES/ONOFF

CIC: 903

Plan OFFNET
Adds & changes
NA
Manual

ONNET
2× weekly
CYCLE ONNET
Full Replace

Thurs for Mon cycle
P:/WC30/FILES/ONOFF

Tues for Thurs cycle
CIC: 903

CLEC1
Mondays
CLEC MASTER*
Incremental adds

CLEC2
as process LIDB
Fails for LIDB OCN/RAO tests
Insert with source

responses

CLEC3
as process BNA
TCSI 2618s, 2619s codes that fail
Insert with source

responses
for BNA

4250 BLOCK
Mondays
Block42 Master
Incremental adds

UNBILL
Mondays
Unbill Master from UB1s
Incremental adds

Block & Cancel -
Mondays
INQ file
Incremental adds

GLOBAL

Block & Cancel - Client
Mondays
INQ files for Clients
Incremental adds

Specific

Val CACHE
as process LIDB
LIDB requests
Insert new

requests

LIDB Validity Test
NA
NA
NA

LIDB CLEC RAO
as process LIDB
Code 998 only (new Telcordia
TBD

requests
source)

LIDB CLEC OCN
As process LIDB
P:OCN.dat
Full replace

requests

LIDB State Specific
Adds & changes
NA
manual

VAL Trans Log
Adds
NA
All adds

AREA CODE Change
Adds
TPM
All adds

indicator

*See Exhibit B for Billing rejects and Unbills codes that are loaded into tables.

TABLE PURGE

TABLE
SCHEDULE
TRIGGER
HOW

Client profile
changes
NA
manual

ANI = BTN
NA

Invalid # OFFNET
changes
NA
manual

Global OFFNET
See load
See load
Full replace

Product OFFNET
See load
See load
Full replace

Client OFFNET
See load
See load
Full replace

Special Calling Card
See load
See load
Full replace

OFFNET

Plan OFFNET
See load
See load
Full replace

ONNET
See load
See load
Full replace

CLEC
90 days
Insert date
Delete from table

4250 BLOCK
180 days

Delete from table

UNBILL
OCN Moratorium
Insert date and
Delete from table

elapsed time

Block & Cancel -
No purge

Delete from table

GLOBAL

Block & Cancel -
Every 6 months
From insert date
Delete from table

Client Specific

VAL CACHE
>2 < 30 days;
From insert date
Delete from table

>180 days

LIDB Validity Test
As changes
NA
Manual

LIDB CLEC RAO
See load
NA
Full replace

LIDB CLEC OCN
See load
NA
Full replace

VAL Trans Log
No purge

AREA CODE Change
Monthly
Completion of
TPM deletions

indicator

Permissive Dialing

period

*See Exhibit C OCN Moratorium schedule.

[0149] Exhibit A

[0150] Example Tables

[0151] Zip to NPA_NXX source allows for best 3 zips for an NPA_NXX combination. Tests show a 70% match rate. This rate has been improved by matching to position 1-3 of the Zip. The low match rate combined with the fact that a BTN is not a portable instrument, this test is not recommended for BTN validation.

27Zip Match TableFieldsData typeKeyNPA_NXXNumeric(6)PrimaryZIP1Numeric(5)NoneZIP3Numeric(5)NoneZIP3Numeric(5)None

[0152] The following tests are optionally carried out in other embodiments of the invention.

28ANI WATCH TableFieldsData TypeKeyBTNNumeric(10)PrimaryNSP_ProductChar(5)NoneClient idNumeric(3)NoneDATETIMENumeric(4)NoneSOURCENumeric(6)None

[0153] The ANI Watch has BTNs that have been given an adjustment for charges by the Client, proprietor or user of the module 200 or the Telco. This is to help the client determine the credit score for the BTN.

29FieldsData TypeKeyBilling Name and Address TableNameVarchar(30)NoneAddress1Varchar(30)NoneAddress2Varchar(30)NoneAddress3Varchar(30)NoneCityVarchar(20)NoneStateCHAR(2)NoneZip + 4Numeric(10)NoneBTNNumeric(10)NoneDATEDateTimeNoneSourceVarchar(20)NoneBTN Thresholding TableBTNNumeric(10)NoneDATEDateTimeNoneClient IDNumeric(3)NoneeBi RESPONSE CODEChar(3)NoneNSP ProductChar(10)NoneTotalInt(4)NoneExhibit BLoaded Reject and Unbill CodesRejectReject CodeLOADCodesDescriptionin DB?DB?PURGE?15ORIGINATING NXXYInvalidNINVALID (NXX =OFFNET555 OR 976)44BILLING NXXYINVALIDNINVALID (NXX =555 OR 976)48REFUSE TO PAY/ENDYB&CNORMALUSER REJECT74LEC REQUESTEDYB&CNORMALBLOCK93REGULATORY BLOCKYB&CNORMAL94INTRASTATE LECYB&CNORMALBLOCK95ANI BLOCKYB&CNORMAL98NON-LOCALYB&CNORMALINTRASTATE BLOCKM0SHARED NPA-NXXYCLEC90 DAYS(CLEC)12ORIG NPA/NXX NOTYInvalidNEVERON TPMOFFNET15ORIG NXX INVALIDYInvalidNEVER(NXX = 555OFFNETOR 976)16ORIG NPA INVALIDYInvalidNEVEROFFNET30TERM NPA = 800YInvalidNEVEROFFNET44BILLING NXXYInvalidNEVERINVALID (NXX =OFFNET555 OR 976)ASINVALID NPA CODEYInvalidNEVEROFFNET18ORIG NUM INVALIDYUNBILLOCN34TERMINATINGYUNBILLOCNNUMBER INVALID36SPECIAL BILLINGYUNBILLOCNNBR - AT&T ONLY37SPECIAL BILLINGYUNBILLOCNNBR - CINCINNATIBELL ONLY38SPECIAL BILLINGYUNBILLOCNNUMBER INVALID41BILLING NPA/NXXYUNBILLOCNIN SPECIAL BILLNBR NVALID59SUSPECTED FRAUDYUNBILLOCNA1SUSPECTED FRAUDYUNBILLOCNNUMBERA7INVALID BILLYUNBILLOCNTO COIN ACCOUNTA8NO ACCOUNTYUNBILLOCNB0NO ACCOUNT AFTERYUNBILLOCNINVESTIGATIOND6INVALID BILLINGYUNBILLOCNNUMBERE6CALLS OVERYUNBILLOCN$999.99F1BILLED TOYUNBILLOCNCELLULAR/MOBILENUMBERG1ACCOUNT INYUNBILLOCNWRITE-OFF STATUSH8REBILL - NOYUNBILLOCNLONGER BILLABLEBY PBK2TOLL BILLINGYUNBILLOCNRESTRICTIONU0DENY ALL KNOWLEDGEYUNBILLOCN(DAK)U6END-USER ACCOUNTYUNBILLOCNIN FINAL STATUSK4LEC INITIATED BILLYUNBILLOCNBLOCKL6DENIAL STATUSYUNBILLOCNRESTRICTION(891/CIID)L7DISCONNECTEDYUNBILLOCNACCOUNT DUE TONONPAYMENTV7RESTRICTED ACCOUNTYUNBILLOCNA9EC DOES NOT HAVEYUNBILLOCNBILLING ARRANGEMENTWITH ICExhibit COCN PURGE SCHDEULEDaysNAMESOCNS90Ameritech, Pac Bell, Nevada Bell,9321, 9323, 9325, 9327,SNET, SWBT, Bell Atlantic, Nynex,9329, 9740, 9742, 9147,Bell South9102, 9104, 9206, 9208,9210, 9211, 9212, 9213,9214, 9496120Sprint United0341, 0470, 832, 9993180CBT, GTE, NECA, Illuminet, Alltel,All othersCitizens, Qwest, default

[0154] Unlike conventional use of the LIDB database that uses the LIDB data to obtain information on a destination/termination or recipient location or subscriber unit, the module 200, in accordance with the invention, uses the industry standard LIDB database to obtain relevant information on the initiating subscriber line 96. The subscriber line reference data obtained from the LIDB database is then processed to generate modified validity codes, which provide a vendor with data to facilitate deciding whether or not a transaction should be processed. The LIDB/LNP database is queried as if a collect call event is occurring and a call is thus mimicked. The processing of the transaction typically involves communicating the relevant transaction data to a folder of the subscriber's account with a relevant Telco. The method of, and module 200 for, validating the billing account associated with the subscriber line allows, for example, a subscriber line to be used to validate and conclude a transaction instead of using a conventional payment techniques such as a credit card, debit card, bank account details or the like.

[0155] A current industry-wide problem is the lack of ability of a service provider to identify when a line subscriber has switched his service to a CLEC since the service provider may not have an existing billing arrangement with such a CLEC and may also not have a source for the BNA to allow for a direct billing solution. LNP databases were originally established for the purpose of directing call routing activities among facilities-based carriers and most telephone numbers ported to a CLEC do not involve a facility change (the CLEC may be simply reselling the incumbent LEC's facilities). This means that, for billing decision purposes, LNP queries usually provide an incorrect response.

[0156] The LNP queries are enhanced by analyzing and interpreting other field elements included within the query response. Specifically, certain values or, in some cases, the absence of certain values, in the Operating Company Number (“OCN”) and/or the Regional Accounting Office (“RAO”) fields, allows further accuracy in the validation response. While the definitions of the OCN and RAO field elements can be obtained from industry sources, their interpreted use in the validation process is unique to the present invention. Use of these additional data elements can improve the reliability of the validation event.

[0157] LNP results may be supplemented with CARE queries in LEC regions where LNP results are inadequate and CARE costs are not otherwise prohibitive based on the retail price of the underlying service. CARE provides a reliable result on CLEC-ported numbers since its basic purpose is to provide subscriber account information (such as billing name and address). Once a number is ported to a CLEC, the incumbent LEC no longer has subscriber responsibility and will, therefore, return an “unavailable” response, even if the LEC's dial-tone facility is still being utilized. This negative response is then used to generate a “deny” status on the subscriber based on the current lack of CLEC billing support.

[0158] The validation process is also supplemented through the use of internal databases built from information gathered throughout the billing and collection process.

[0159] It is important to appreciate that all of the steps in the method executed by the module 200 need not be executed in real time. Typically, after the approval code 000 has been generated by the module 200 at step 334 the module 200 terminates its pre-validation check routine as shown at step 336. At this point the module 200 may merely provide pre-validation data or verification data to indicate to the vendor 22 if the subscriber line 96 is billable. Thus the module 200 may, in a first interaction with the vendor 22 provide pre-validation data, and in a second interaction process billing information. During the processing of billing information the validation process may once again be executed. In certain embodiments, the first interaction may be in the form of a registration process during which the validation procedure is carried out to register a subscriber line 96. The vendor 22 may then conduct numerous transactions with subscriber and subsequent validation checks on the subscriber line may then only be carried out on a periodic basis as described above.

[0160] After the validation code has been sent to the vendor 22, and the pre-validation procedure has been complete, the module 200 then carries out the fraud checks on a non-real time basis (usually during the next 48 to 72 hours) as shown in steps 340 to 344. The information obtained during the fraud control checks, if necessary, is used to update the various databases. In particular, after a BTN has been successfully validated but before a billing event takes place, the CARE investigation steps 340 to 344 are executed. The module 200 is typically arranged to interrogate offsite CARE databases and the results of the enquiry are stored in the CARE database 246. Checks on the data received from the CARE databases are then performed whereafter one or more of the other databases may be updated with the results. For example, the CARE database 246 may be updated, new within 90 days information, business indicator information, or the like. CARE codes 2618 and 2619 typically indicate that the BNA is not available and that the LEC no longer owns the account.

[0161] The updating of the databases following the CARE investigation allows enhanced future checks by the module 200 in a subsequent pre-validation procedure or subsequent registration event validation event. The updated information may be provided to the vendor 22. However, if the BTN information returned from the CARE database 246 does not meet predefined criteria, the other databases of the module 200 are not updated.

[0162] When a purchase validation event or billing event is declined, fails, unbillable or is negative event for any reason, the purchaser is preferably apprised. The manner in which the failure is treated depends upon the point in time and the reason the transaction validation or billing event fails.

[0163] In certain embodiments, a business rule table drives the treatment method and course based on when the failed event occurred during the validation process and the reason for the failure. With a purchase validation event, the option may be provided to interact with the purchaser at the time of requesting the purchase. For example, the option to change failed information for a revalidation or to change to another payment option may be provided. An example of customer failure may be as follows:

30If a purchasevalidation eventfails:Then the customer treatment may be:ANI = BTNScreen pop requesting new number and or to callfrom the matching number.Missing orScreen pop requesting correct cust code.incorrectcust codeTHRESHOLDScreen pop explaining this and a request for anotherpayment method.OFFNETScreen pop explaining this and a request for anotherpayment method.CLECScreen pop explaining this and a link to changecarrier to ILEC. Or request another payment option.42 BlockScreen pop explaining this and a link to ILEC tounblock 4250. Or request another payment option.BLOCK andScreen pop explaining this and a request for anotherCANCELpayment method. Also include explanation as tohow to unblock.UNBILLsScreen pop explaining this and a request for anotherpayment method.LIDB Code FailScreen pop explaining this and a request for anotherpayment method.LIDB RAO/OCNScreen pop explaining this and a link to changefailcarrier to ILEC. Or request another payment option.ADDRESSScreen pop requesting correct information.VERIFICATIONPreviousScreen pop explaining this and a link to inquiryAdjustmentchat or inquiry call information.Unpaid BalanceSee above.

[0164] At the time of a pre-billing validation event or a failed billing event, the interaction with the purchaser will be after the fact and is typically in a screen pop at the next sign-on and in email form. In certain embodiments, there is a preset length of time to correct the failed information for a revalidation or change to a new payment method.

31If a pre-billvalidation eventfails:Then the customer treatment may be:OFFNETScreen pop at next id sign-on explaining this andrequesting change of payment method. Emailcontaining the same information and link toupdate payment information.CLECScreen pop at next id sign-on explaining this andinstructions how to solve or update payment methodinformation. Email containing the same informationand a link to change carrier to ILEC and link toupdate payment method.42 BlockScreen pop at next id sign-on explaining this andinstructions how to solve or update payment methodinformation. Email containing the same informationand link to unblock at ILEC or link to updatepayment information.BLOCK andScreen pop at next id sign-on explaining this andCANCELinstructions hot to solve or update payment methodinformation request for another payment method.Email requesting the same information and a link tochange carrier to ILEC and link to updatepayment methodUNBILLsScreen pop at next id sign-on explaining this andrequesting change of payment method. Emailcontaining the same information and link to updatepayment information.LIDB Code FailScreen pop at next id sign-on explaining this andrequesting change of payment method. Emailcontaining the same information and link to updatepayment information.LIDB RAO/OCNScreen pop at next id sign-on explaining this andfailinstructions how to solve or update payment methodinformation. Email containing the same informationand a link to change carrier to ILEC and link toupdate payment methodPreviousScreen pop at next sign-on explaining this and a linkAdjustmentto inquiry chat or inquiry call information.Unpaid BalanceSee above.If a billingevent fails:Then the customer treatment may be:UnbillsScreen pop at next id sign-on explaining this,requesting payment of unbilled charge andsuggestions of ways to solve including a link toswitch back to the ILEC and a way to update newphone number. It will also include a requestfor a change of payment method.Email containing the same information, link tochange back to ILEC, to update with a new phonenumber, update to update payment information alsocontains link to inquiry chat or inquiry call.ChargebackScreen pop at next sign-on explaining this and alink to inquiry chat or inquiry call information.Bad DebtScreen pop at next sign-on explaining this and aWrite-offlink to inquiry chat or inquiry call information.

[0165] Once the treatment period passes, the account access is typically denied and more traditional ways of saving, winning back, and reactivation or collections activities would take place.

[0166] In the embodiment described above, information on the subscriber line 96 is forwarded by the service provider or vendor 22 to the module 200 for validation. However, in other embodiments of the invention, the consumer or user may call the module 200 directly, as shown by line 350 in FIG. 1, and the ANI may then be obtained by the module 200 directly from the terminal 24 and not indirectly from the vendor 22. Further subscriber line data, e.g. BTN, address of the user and so on, may then also be obtained directly from the user. For example, the user may have appropriate software installed on his/her PC which allows the user to dial into the module 200 in an automated fashion should he/she wish to charge any requested goods or services to his/her subscriber account. The module 200 would then validate the subscriber line 96 using the method describer above. The module 200 then typically communicates a validation code (e.g. corresponding to approval or non-approval) to the vendor 22 as shown by line 352. The vendor 22 would then conclude the transaction with the user if the subscriber line has been validated.

[0167] In the first iteration of the validation process in which a validation request is received from the vendor 22, the ANI of the subscriber line 96 is captured to identify the subscriber line to which the terminal 24 is connected so that the validation process can be executed and the transaction or purchase can be approved and the billing process can be effected. It is to be appreciated however that the validation process and further prosecution of the transaction may take place based on the BTN which the user enters but that the capturing of the ANI may reduce the likelihood of fraud. Thus, if the ANI is captured, it may be done during an initial enquiry, purchase event, or at any other time during the process.

[0168] In other embodiments of the invention, in addition to or instead of capturing the ANI, the system 20 may request a user to enter the unique number associated with every phone billing account that Telcos currently issue. These additional digits are typically found at the end of the account number on a conventional telephone bill. These digits, sometimes called customer codes, identify the account associated with that particular assignment of the phone number. These codes provide a way to avoid capturing the ANI because typically only the account holder has access to this number thereby reducing the chance of fraud. Thus, the display screen 86 of FIG. 11 optionally includes the field 364 in which a user can enter the customer codes. An appropriate database would then be interrogated to validate the subscriber line. In one embodiment of the invention, the interrogation is included in the LIDB step, and includes details on the account to the customer code level.

[0169] The customer codes may thus eliminate the need to capture the ANI by the module 60 (see FIG. 5) and, customer code data may be compared by the comparator module 218 (see FIG. 15) and as shown in step 264 in FIG. 17. As described above, the display screen 86 then includes the field 264 to accommodate this facility. Likewise, if the phone number is not confirmed, then the input screen would be provided with the customer code field.

[0170] When the customer code is used to validate the subscriber line 96, a step to interrogate the information is included in which additional information is sent to the LIDB database 252 (see FIG. 15) in step 124 of FIG. 13, and step 290 in FIG. 17. Additionally, steps relating to the return of LIDB data are updated to include the results of the interrogation of this piece of information.

[0171] The facility 28 may function as a type of clearing house. In particular, the facility 28 may be responsible or accountable for payment of the goods or services for each transaction to the service provider or vendor 22 and, in turn, receive payment from the Telco. As mentioned above, the module 200 updates the telephone bill or account 34 of the subscriber in an automated fashion (see line) and the bill 356 that the user receives (see FIG. 1) includes the charges for the goods and/or services provided by the vendor 22. The user pays the Telco 26 (see line 358), the Telco 26 pays the facility 28 (see line 360), and the facility 28 pays the vendor 22 (see line 362). It is important to appreciate that these payments need not take place at the same time. Typically, the payments between the Telco 26 and the facility 28, and the facility 28 and vendor 22, take place periodically in a batch fashion the PC 24, and modules 30, 32 are exemplary forms of computer systems or machines within which a set of instructions, for causing the machine to perform any one of the methodologies discussed above, may be executed. In alternative embodiments, the machine may comprise a network router, a network switch, a network bridge, Personal Digital Assistant (PDA), a cellular telephone, a web appliance or any machine capable of executing a sequence of instructions that specify actions to be taken by that machine.

[0172] Each machines includes a processor, a main memory and a static memory, which communicate with each other via a bus. The machines may further include a video display unit (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). The machine also includes an alpha-numeric input device (e.g. a keyboard), a cursor control device (e.g. a mouse), a disk drive unit, a signal generation device (e.g. a speaker) and a network interface device.

[0173] The disk drive unit includes a machine-readable medium on which is stored a set of instructions (i.e., software) embodying any one, or all, of the methodologies described above. The software is also shown to reside, completely or at least partially, within the main memory and/or within the processor. The software may further be transmitted or received via the network interface device. For the purposes of this specification, the term “machine-readable medium” shall be taken to include any medium which is capable of storing or encoding a sequence of instructions for execution by the machine and that cause the machine to perform any one of the methodologies of the present invention. The term “machine-readable medium” shall accordingly be taken to included, but not be limited to, solid-state memories, optical and magnetic disks, and carrier wave signals.

Method and system for processing a transaction

Information

Publication Number

Date Filed

Date Published

Inventors

CPC

US Classifications

International Classifications

Abstract

Description

Claims