Traitement en cours

Veuillez attendre...

Paramétrages

Paramétrages

Aller à Demande

1. WO2003025824 - PROCEDE ET SYSTEME DE TRAITEMENT DE TRANSACTIONS

Note: Texte fondé sur des processus automatiques de reconnaissance optique de caractères. Seule la version PDF a une valeur juridique

[ EN ]

CLAIMS:

What we claim is:

1. A method of processing payment for a transaction, the method including: 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;
receiving a user request entered into the terminal to process payment from the account;
investigating data associated with the communication line; and
selectively approving the transaction dependent upon an outcome of the investigation.

2. A method as claimed in Claim 1 , in which the communication line is a subscriber line and the account is a telephone account associated with the subscriber line.

3. A method as claimed in Claim 2, which includes identifying a telephone number of the subscriber line using automatic number identification (ANI) techniques.

4. A method as claimed in Claim 3, which includes combining the telephone number and transaction data to form a financial instrument record.

5. A method as claimed in Claim 4, in which the financial instrument record is an industry standard credit card record.

6. A method as claimed in Claim 3, in which investigating data associated with the communication line includes performing a validation process in which data associated with the telephone number is investigated.

7. A method as claimed in Claim 6, which includes obtaining a user entered telephone number from the electronic terminal and comparing the user entered telephone number with the telephone number obtained using ANI techniques.

8. A method as claimed in Claim 6, in which the validation process includes retrieving information form a line identification database (LIDB).

9. A method as claimed in Claim 6, which includes:
communicating a validating message on approval of the transaction if the validation process validates the subscriber line; and
routing processing of the transaction to a financial instrument gateway in the event of the validation process not validating the subscriber line.

10. A method of modifying a financial instrument record, the method including:
receiving transaction data entered into an electronic terminal connected via a communication line to a communication network;
obtaining a unique identifier associated with the communication line; and
combining the unique identifier and the transaction data to form a financial instrument record.

11. A method as claimed in Claim 10, in which the financial instrument record is selected from the group including a credit card record and a debit card record.

12. A method as claimed in Claim 11 , in which the financial instrument record is receivable by a Customer Management System.

13. A method as claimed in Claim 12, in which the communication line is a subscriber line and the unique identifier is a telephone number associated with the subscriber line.

14. A method as claimed in Claim 13, in which the telephone number replaces a financial instrument number in the financial instrument record.

15. A method of validating a transaction conducted using an electronic terminal connected via a communication line to an electronic network, the method including:
receiving a financial instrument record associated with the transaction;
extracting a unique identifier from the financial instrument record, the unique identifier being associated with the communication line; and
interrogating at least one database based on the unique identifier to obtain data associated with the communication line and selectively generating a validation status.

16. A method as claimed in Claim 15, in which the unique identifier is a telephone number of a subscriber line and processor module retrieves information from a line identification database (LIDB).

17. A method as claimed in Claim 16, in which charges for the transaction are included in an account associated with the subscriber line.

18. A method as claimed in Claim 16, which communicates a validating message on approval the transaction if the subscriber line is validated, and routes processing of the transaction to a financial card gateway in the event of the subscriber line is not validated.

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

20. A system as claimed in Claim 19, in which payment is routed to financial card gateway if the validation module invalidates the transaction.

21. A system as claimed in Claim 19, in which the communication line is a subscriber line and the unique identifier is a telephone number associated with the subscriber line.

22. A system as claimed in Claim 21 , which includes an automatic line identification (ANI) module automatically to identify the telephone number.

23. A system as claimed in Claim 22, in which the validation module includes: a telephone number extraction module for extracting a telephone number from the record, the telephone number defining the unique identifier; and a processor module which interrogates at least one reference data base to obtain data associated with the telephone number and, in response thereto, generates a validation status.

24. A system as claimed in Claim 22, in which the processor module interrogates a line identification database (LIDB).

25. A system as claimed in Claim 22, in which the processor module validates the transaction if charges can be included in the account associated with the subscriber line, and invalidates the transaction if the charges cannot be included in the account.

26. A system as claimed in Claim 23, which includes an exchange interface for interfacing the validation module to an accounting facility of a
telecommunications company at which the account is held thereby automatically to include the charges for the transaction in the account.

27. A system as claimed in Claim 19, in which the record is an industry standard financial instrument record.

28. A system as claimed in Claim 27, in which the record is selected from the group including a credit card record and a debit card record.

29. A transaction processor interface for processing payment of a transaction, the interface including:
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
a modification module for creating a financial instrument record which includes a unique identifier associated with the communication line.

30. A transaction processor interface as claimed in Claim 29, in which the communication line is a subscriber line and the account is a telephone account associated with the subscriber line.

31. A transaction processor interface as claimed in Claim 30, which includes an automatic number identification (ANI) module to obtain a unique identifier in the form of a telephone number of the subscriber line.

32. A transaction processor interface as claimed in Claim 29, which includes a communications module for communicating the financial instrument record to a validation module for validating the transaction based on data associated with the unique identifier.

33. A transaction processing interface as claimed in Claim 29, in which the financial instrument record is selected from the group including a credit card record and a debit card record.

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

35. A transaction validation module as claimed in Claim 34, in which the unique identifier is a telephone number and the processor module retrieves the data form a line identification database (LIDB).

36. A transaction validation module as claimed in Claim 35, in which charges for the transaction are included in an account associated with the communication line.

37. A transaction validation module as claimed in Claim 34, which
communicates a validating message on approval the transaction if the
communication line is validated, and routes processing of the transaction to a financial card gateway if the communication line is not validated.

38. 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:
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;
receive a user request entered into the terminal to process payment from the account;
investigate data associated with the communication line; and
selectively approve the transaction dependent upon an outcome of the investigation.

39. A product as claimed in Claim 38, in which the communication line is a subscriber line and the account is a telephone account associated with the subscriber line.

40. A product as claimed in Claim 39, which includes identifying a telephone number of the subscriber line using automatic number identification (ANI) techniques.

41. A product as claimed in Claim 39, which includes combining the
telephone number and transaction data to form a financial instrument record.

42. 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:
receive transaction data entered into an electronic terminal connected via a communication line to a communication network;
obtain a unique identifier associated with the communication line; and combine the unique identifier and the transaction data to form a financial instrument record.

43. A product as claimed in Claim 42, in which the financial instrument record is selected from the group including a credit card record and a debit card record.

44. A product as claimed in Claim 42, in which the financial instrument record is receivable by an Internet-based Customer Management System.

45. 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:
receive a financial instrument record associated with a transaction conducted using an electronic terminal connected via a subscriber line
connected to a communication network;
extract a unique identifier from the financial instrument record, the unique identifier being associated with the communication line; and
interrogate at least one database based on the unique identifier to obtain data associated with the unique identifier and selectively generate a validation status.

46. A product as claimed in Claim 45, in which the unique identifier is a telephone number and the processor retrieves information form a line
identification database (LIDB).

47. A method as claimed in Claim 45, in which charges for the transaction are included in an account associated with the communication line.

48. A method of providing validation data associated with a subscriber line of a telecommunication network, the method including:
obtaining line data of the subscriber line, the line data being suitable for interrogating a line identification database (LIDB);
interrogating the LIDB with the line data to obtain reference subscriber data associated with the line data; and
processing the reference subscriber data to obtain validation data associated with the subscriber line.

49. The method of claim 48, wherein the LIDB is a conventional LIDB used by a service provider.

50. The method of claim 49, which includes:
analyzing the reference subscriber data to determine if the line data is associated with a billing telephone number (BTN); and
generating one of an approval and a decline status in response to the analysis.

51 The method of claim 48, wherein the line data is an automatic number identification (ANI).

52. The method of claim 51 , which includes interrogating the LIDB with the ANI to obtain the reference subscriber data associated with the line data.

53. The method of claim 52, which includes processing the validation data to determine whether the subscriber line is a billable line having an associated account to which goods or services can be billed.

54. The method of claim 52, which includes processing the reference subscriber data received from the LIDB selectively to approve a transaction requested via the subscriber line.

55. The method of claim 52, wherein the reference subscriber data is in the form of LIDB codes.

56. The method of claim 55, wherein the processing of the reference subscriber data includes generating a modified code from at least one LIDB code from a plurality of LIDB codes.

57. The method of claim 56, which includes generating a common modified code from the plurality of LIDB codes.

58. The method of claim 57, which includes arranging the modified codes into a billable group and a non-billable group.

59. The method of claim 51 , which includes conducting fraud control checks on the account associated with the subscriber line.

60. The method of claim 59, wherein the fraud control checks include at least one of the operations selected from the group consisting of checking if adjustments have been made to the account associated with the line data, verifying a user entered ZIP code with ZIP data from a ZIP data source, verifying user entered address data with address data from an address data source, checking if an area code associated with the line data has changed, checking if the line data and a BTN match, and checking if one of the BTN and ANI are missing from the record.

61. The method of claim 48, which includes interrogating a network database with the ANI to determine if the subscriber line is a billable subscriber line and, if so, generating one of a decline status and an approved status in response to the interrogation.

62. The method of claim 61 , which includes interrogating with the line data at least one of a competitive local exchange carrier (CLEC) database, a 42 BLOCK database, a Block and Cancel database, an unpaid bills database, an off network database, an on network database, an address verification database, a regional account office (RAO) database, an operating company number (OCN) database, and a customer account record exchange (CARE) database.

63. The method of claim 48, which includes:
receiving the line data from a vendor of goods or services; and
communicating one of a decline status and an approval status to the vendor in response to receiving the line data from the vendor.

64. The method of claim 63, which includes billing charges raised by the vendor to an account submitted by an exchange carrier to a subscriber for use of the subscriber line.

65. A machine-readable medium for storing a set of instructions that, when executed by a machine, cause the machine to:
obtain line data of a subscriber line, the line data being suitable for interrogating a line identification database (LIDB);
interrogate the LIDB with the line data to obtain reference subscriber data associated with the line data; and
process the reference subscriber data to obtain validation data associated with the subscriber line.

66. A subscriber line validation system to validate a subscriber line of a communication network, the system including
a communication module to receive line data of the subscriber line, the line data being suitable for interrogating a line identification database (LIDB);
an interrogation module for interrogating the LIDB with the line data to obtain reference subscriber data associated with the line data; and
a processor module for processing the reference subscriber data to obtain validation data associated with the subscriber line.

67. The system of claim 66, wherein the LIDB is at least one conventional LIDB used by at least one service provider to investigate a destination line to which the subscriber line requests a connection.

68. The system of claim 67, wherein the processor module is configured to analyze the reference subscriber data to determine if the data is associated with a billing telephone number (BTN) and to generate one of an approval and a decline status in response to the analysis.

69. The system of claim 66, wherein the line data is an automatic number identification (ANI).

70. The system of claim 69, wherein the interrogation module is configured to interrogate the LIDB with the ANI to obtain the reference subscriber data associated with the line data.

71. The system of claim 70, wherein the validation data is processed to determine whether the subscriber line is a billable line having an associated account to which goods or services can be billed.

72. The system of claim 70, wherein the reference subscriber data is received from the LIDB and is processed selectively to approve a transaction requested via the subscriber line.

73. The system of claim 70, wherein the reference subscriber data is in the form of conventional LIDB codes and the processor module generates a modified code from at least one LIDB code.

74. The system of claim 73, wherein a common modified code is generated from a plurality of different LIDB codes.

75. The system of claim 74, wherein a plurality of modified codes are generated and arranged in a billable group and a non-billable group.

76. The system of claim 69, wherein the processor module is configured to conduct at least one fraud control check selected from the group consisting of checking if adjustments have been made to the account associated with the line data, verifying a user entered ZIP code with a ZIP data source, verifying user entered address data with an address data source, checking if the area code associated with the ANI has changed, checking if the ANI and the BTN match, and checking if at least one of the BTN and ANI is missing from the record.

77. The system of claim 66, wherein the processor module is configured to interrogate a network database with the ANI to determine if the subscriber line is a billable subscriber line and, if so, generate one of a decline status and an approved status in response to the interrogation.

78. The system of claim 77, wherein the network database includes at least one of a competitive local exchange carrier (CLEC) database, a 42 BLOCK database, a Block and Cancel database, an unpaid bills database, an off network database, an on network database, an address verification database, a regional account office (RAO) database, an operating company number (OCN) database, and a customer account record exchange (CARE) database.

79. The system of claim 66, wherein the communication module receives the line data from a vendor of goods or services and communicates at least a decline status to the vendor.

80. The system of claim 79, wherein charges raised by the vendor are included in an account submitted by an exchange carrier to a subscriber for use of the subscriber line.

81. A system to provide validation data associated with a subscriber line of a telecommunication network, the system including
means for obtaining line data of the subscriber line, the line data being suitable for interrogating a line identification database (LIDB);
means for interrogating the LIDB with the line data to obtain reference subscriber data associated with the line data; and
means for processing the reference subscriber data to obtain validation data associated with the subscriber line.