SECURE NETWORKED TRANSACTION SYSTEM

• US 20090125430A1
• Filed: 01/21/2009
• Published: 05/14/2009
• Est. Priority Date: 12/16/1999
• Status: Active Grant

• Current Assignee: Kioba Processing, LLC (IP Investments Group LLC)
• Original Assignee: Ucetrans KG LLC (Intellectual Ventures LLC)
• Inventors: Krueger, Scott, Goodman, Daniel
• Granted Patent: US 7,853,523 B2
• Time in Patent Office: Days
• US Class Current: 705/35
• 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/04 Payment circuits
• 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/12 specially adapted for electronic shopping systems
• CPC Class Codes: G06Q 20/24 Credit schemes, i.e. "pay after"
• CPC Class Codes: G06Q 20/3674 involving authentication
• CPC Class Codes: G06Q 20/382 insuring higher security of transaction
• CPC Class Codes: G06Q 20/383 Anonymous user system
• 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/401 Transaction verification
• CPC Class Codes: G06Q 20/4012 Verifying personal identification numbers [PIN]
• CPC Class Codes: G06Q 20/403 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

Abstract

A method and system for approving a transaction between a customer and a merchant including the steps of transmitting a transaction request from a customer to a merchant; transmitting a verification request from the merchant to a verification entity, the verification request comprising first data; the customer device transmitting second data to the verification entity; and the verification entity performing a verification step by using the first data and the second data to verify if the transaction should be approved.

Claims

1. A method of approving a transaction between a customer and a merchant comprising:

transmitting a transaction request from a customer to a merchant;

transmitting a verification request from the merchant to a verification entity, the verification request comprising first data;

the customer transmitting second data to the verification entity; and

the verification entity performing a verification step by using the first data and the second data to verify if the transaction should be approved.

114. The method of claim 1 wherein transmitting a transaction request from a customer to a merchant and the customer transmitting second data to the verification entity are performed with wireless communications.

115. The method of claim 1 wherein transmitting a transaction request from a customer to a merchant, transmitting a verification request from the merchant to a verification entity, the verification request comprising first data, and the customer transmitting second data to the verification entity are executed over a computer network.

116. The method of claim 1 wherein the first data comprises at least part of a debit card account number and the second data comprises at least part of a PIN number associated with the debit card account number.

117. The method of claim 116 further comprising the customer swiping a debit card through a magnetic stripe reading device in order to obtain information from a magnetic stripe on the debit card.

118. The method of claim 117 wherein the magnetic stripe reading device is associated with the merchant.

119. The method of claim 117 wherein the magnetic stripe reading device is associated with the customer.

120. The method of claim 117 further comprising the customer entering the PIN number onto a device in communication with the verification entity.

121. The method of claim 1 wherein the first data comprises at least part of a credit card account number and the second data comprises at least part of a card security code associated with the credit card account number.

122. The method of claim 1 further comprising the merchant causing the customer to transmit the second data to the verification entity.

123. The method of claim 122 further wherein the merchant causing the customer to transmit the second data to the verification entity comprises the merchant sending a command to a web browser executing on a device operated by the customer, the command causing the web browser to connect to the verification entity and transmit the second data to the verification entity.

124. The method of claim 123 wherein the command sent to the web browser comprises a redirect command.

2-113. -113. (canceled)

125. A system for approving a transaction between a customer and a merchant comprising:

a customer device;

a merchant device; and

a verification device;

wherein

said customer device is adapted to transmit a transaction request to the merchant device and second data to the verification device;

said merchant device is adapted to transmit a verification request comprising first data to the verification device; and

said verification device is adapted to performing a verification step by using the first data and the second data to verify if the transaction should be approved.

126. The system of claim 125 wherein the customer device is a wireless device.

127. The system of claim 125 further comprising a magnetic stripe reading device for reading a debit card in order to obtain information from a magnetic stripe on the debit card, at least part of the information from the magnetic stripe being at least part of the first data.

128. The system of claim 127 wherein the magnetic stripe reading device is associated with the merchant device.

129. The system of claim 127 wherein the magnetic stripe reading device is associated with the customer device.

130. A verification device for approving a transaction between a customer and a merchant comprising:

means for receiving from a merchant device a verification request comprising first data;

means for receiving second data from a customer device; and

means for using the first data and the second data to verify if the transaction should be approved.