METHOD AND SYSTEM FOR FACILITATING PAYMENT TRANSACTIONS USING ACCESS DEVICES

• US 20080103985A1
• Filed: 10/30/2007
• Published: 05/01/2008
• Est. Priority Date: 08/27/2002
• Status: Active Grant

• Current Assignee: Eric Redmond, Jean Huang, Pete Heisinger
• Original Assignee: Eric Redmond, Jean Huang, Pete Heisinger
• Inventors: Huang, Jean, Redmond, Eric, Heisinger, Pete
• Granted Patent: US 7,711,621 B2
• Time in Patent Office: Days
• US Class Current: 705/76
• CPC Class Codes: G06Q 20/02 involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
• CPC Class Codes: G06Q 20/027 involving a payment switch or gateway
• CPC Class Codes: G06Q 20/04 Payment circuits
• CPC Class Codes: G06Q 20/045 using payment protocols involving tickets
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/223 based on the use of peer-to-peer networks
• CPC Class Codes: G06Q 20/26 Debit schemes, e.g. "pay now"
• CPC Class Codes: G06Q 20/3821 Electronic credentials
• CPC Class Codes: G06Q 20/385 using an alias or single-use codes
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/403 Solvency checks
• CPC Class Codes: G06Q 20/4037 Remote solvency checks
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/03 Credit; Loans; Processing thereof
• CPC Class Codes: G06Q 40/12 Accounting
• CPC Class Codes: G07F 7/08 by coded identity card or credit card or other personal identification means without personal verification means G07F7/02

Abstract

A payment system for facilitating a payment transaction between a payer and a payee is disclosed. The payment system includes a payer access device, a payee access device, and a services hub. The services hub is configured to communicate with the payer device and the payee device; maintain information relating to a payer account and access device information associated with the payer account, the payer account being linked to the access device; generate a tracer ticket in response to a request issued by the payer using either the payer device or the payee device, the tracer ticket containing information relating to the payment transaction; validate the access devices; and authorize the payment transaction against the payer account through conventional payment processing systems. Upon receiving the request from the payee device for the tracer ticket, the services hub generates the tracer ticket and forwards a copy thereof to the payer via the payee device. Upon receiving the copy of the tracer ticket, the payer uses the payer device to communicate with the services hub and forward the received copy of the tracer ticket to the services hub. The services hub then validates the payer device based on the access device information. Upon validation of the payer device, the services hub checks the copy of the tracer ticket forwarded by the access device against the previously generated tracer ticket. If the copy of the tracer ticket forwarded by the access device corresponds to the previously generated tracer ticket, the services hub authorizes the payment transaction against the payer account.

Claims

1-55. -55. (canceled)

56. A telephone for facilitating a payment transaction between a payer and a payee, the telephone configured to:

establish a transactional dialog with a services hub to communicate tracer ticket information with the services hub, wherein the tracer ticket information comprises a tracer ticket number associated with a tracer ticket;

transmit at least two levels of authentication information to the services hub, wherein the authentication information identifies the payer associated with the telephone; and

receive an approval response from the services hub, wherein the approval is associated with the successful completion of the payment transaction.

57. The telephone of claim 56 comprising a cellular mobile telephone.

58. The telephone of claim 56, wherein a first level of authentication information comprises a number associated with the telephone.

59. The telephone of claim 56, wherein a second level of authentication information further comprises a password, login ID, or biometric information.

60. The telephone of claim 56 further configured to receive instructions from the services hub to output a prompt requesting the payer to input a tracer ticket number.

61. The telephone of claim 56 further configured to receive instructions from the services hub to output the tracer ticket information to the payer.

62. The telephone of claim 56 further configured to output the approval response to the payer.

63. The telephone of claim 56 further configured to receive a tracer ticket, the tracer ticket containing encrypted tracer ticket information relating to the payment transaction.

64. The telephone of claim 56, wherein the tracer ticket information further comprises a payment amount.

65. The telephone of claim 56, wherein the tracer ticket information further comprises payment terms.

66. The telephone of claim 56, wherein the tracer ticket information further comprises an expiration time.

67. The telephone of claim 56, wherein the tracer ticket information further comprises payee information.

68. The telephone of claim 56, wherein the tracer ticket information further comprises at least one account from which payment will be made.

69. The telephone of claim 68, wherein the at least one account comprises a credit card account.

70. The telephone of claim 56, wherein the tracer ticket is encrypted.

71. A method for facilitating a payment transaction between a payer and a payee, the method comprising:

establishing a transactional dialog with a services hub to communicate tracer ticket information with the services hub, wherein the tracer ticket information comprises a tracer ticket number associated with a tracer ticket;

providing at least two levels of authentication information to the services hub, wherein the authentication information identifies the payer; and

receiving an approval response from the services hub, wherein the approval is associated with the successful completion of the payment transaction.

72. The method of claim 71, wherein the tracer ticket is encrypted.

73. The method of claim 71 further comprising outputting the tracer ticket information to the payer.

74. The method of claim 71, wherein a first level of authentication information comprises a number associated with the telephone.

75. The method of claim 71, wherein a second level of authentication information comprises a password, login ID, smart card, or biometric information.