Legal claims defining the scope of protection, as filed with the USPTO.
1. A method for authenticating a transaction on a payment gateway, the payment gateway having stored thereon a mobile device ID in association with a payment ID, the payment ID identifying a payment account, the method performed on the payment gateway comprising: the payment gateway receiving from a mobile device a supplemental ID and the mobile device ID, the supplemental ID for verifying the payment ID, and the mobile device having stored thereon the mobile device ID; the payment gateway retrieving the payment ID associated with the mobile device ID and sending the payment ID and the supplemental ID to a verification module for verification; and, upon the payment gateway receiving a verification result from the verification module that the supplemental ID and the payment ID are successfully verified, the payment gateway executing the transaction.
2. The method of claim 1 further comprising a registration process for storing the mobile device ID and the payment ID on the payment gateway, the method further comprising: the payment gateway receiving from the mobile device at least the payment ID and the supplemental ID, and transmitting the payment ID and supplemental ID to the verification module; and, upon the payment gateway receiving an initial verification result from the verification module that the payment ID and the supplemental ID are successfully verified, the payment gateway obtains a component for a mobile device ID, the mobile device ID associated with the payment ID and stored at the payment gateway, and the mobile device ID stored on the mobile device.
3. The method of claim 2 wherein the payment gateway obtains the component for the mobile device ID by at least one of generating and receiving the component.
4. The method of claim 1 wherein the payment gateway executes the transaction via a payment server, the payment server in communication with at least one of the payment gateway and the verification module.
5. A method for authentication a transaction, the method comprising: a payment gateway receiving a mobile device ID and a supplemental ID, the supplemental ID for verifying a payment ID, the payment ID identifying a payment account; the payment gateway retrieving the payment ID associated with the mobile device ID, the payment ID and the mobile device ID being stored on the payment gateway in association with each other, and sending the payment ID and the supplemental ID to a verification module; upon the verification module successfully verifying the payment ID and supplemental ID, a payment server executing the transaction, the payment server in communication with at least one of the payment gateway and the verification module.
6. The method of claim 5 wherein a mobile device sends the mobile device ID and the supplemental ID to the payment gateway.
7. The method of claim 5 wherein the payment server is in communication with both the payment gateway and the verification module, and the payment gateway sends the supplemental ID and payment ID to the verification module via the payment server.
8. The method of claim 5 wherein a successful verification result is sent from the verification module to at least one of the payment server and the payment gateway.
9. The method of claim 5 wherein operations of at least two of the payment gateway, the payment server and verification module are combined into a unified server.
10. The method of claim 5 wherein the payment gateway sends the supplemental ID without storing the supplemental ID on the payment gateway.
11. The method of claim 5 wherein the payment ID is comprised of at least one of: a credit card number an expire date, a bank card number, a banking number, and a points account number.
12. The method of claim 5 wherein the supplemental ID is comprised of at least one of: a Card Security Value (CSV), a Card Security Code (CSC), a Card Verification Value (CVV or CVV2), a Card Verification Value Code (CVVC), a Card Verification Code (CVC or CVC2), a Verification Code (V-Code or V Code), a Card Code Verification (CCV), a PIN, a password, biometric data, and voice data.
13. The method of claim 5 wherein the mobile device ID includes at least one of subscriber identity information stored on a SIM card or IMEI of the mobile device, networking information, an IP address, a phone carrier identification, a port address, a DNS name, a GPS coordinate of the mobile device, the battery temperature of the mobile device, a geographical location of the mobile device, an accelerometer reading of the mobile device, a cookie, a user agent, and a header; wherein the cookie, the user agent and the header are provided by a browser on the mobile device or a DOM storage on the mobile device.
14. The method of claim 5 wherein the mobile device ID is randomly generated.
15. The method of claim 5 wherein the mobile device ID is replaced by a new mobile device ID and is associated with the payment ID for each subsequent execution of the transaction process.
16. The method of claim 5 further comprising, during the transaction process, the payment gateway comparing the received mobile device ID to the mobile device ID previously stored thereon to determine if they are similar, and if so, enabling the transaction to be executed.
17. The method of claim 16 wherein the received mobile device ID in the transaction process must be equal to the mobile device ID previously stored on the payment gateway for the transaction to be executed.
18. A non-transitory computer readable medium for authenticating a transaction on a payment gateway, the computer readable medium comprising computer executable instructions for execution on the payment gateway, wherein the payment gateway having stored thereon a mobile device ID in association with a payment ID, the payment ID identifying a payment account, the computer executable instructions comprising: the payment gateway receiving from a mobile device a supplemental ID and the mobile device ID, the supplemental ID for verifying the payment ID, and the mobile device having stored thereon the mobile device ID; the payment gateway retrieving the payment ID associated with the mobile device ID and sending the payment ID and the supplemental ID to a verification module for verification; and, after the payment gateway receiving a verification result from the verification module that the supplemental ID and the payment ID are successfully verified, the payment gateway executing the transaction.
19. The non-transitory computer readable medium of claim 18 further a registration process for storing the mobile device ID and the payment ID on the payment gateway, the non-transitory computer readable medium further comprising: the payment gateway receiving from the mobile device at least the payment ID and the supplemental ID, and transmitting the payment ID and supplemental ID to the verification module; and, upon the payment gateway receiving an initial verification result from the verification module that the payment ID and the supplemental ID are successfully verified, the payment gateway obtains a component for a mobile device ID, the mobile device ID associated with the payment ID and stored at the payment gateway, and the mobile device ID stored on the mobile device.
20. The non-transitory computer readable medium of claim 19 wherein the payment gateway obtains the component for the mobile device ID by at least one of generating and receiving the component.
21. The non-transitory computer readable medium of claim 18 wherein the payment gateway executes the transaction via a payment server, the payment server in communication with at least one of the payment gateway and the verification module.
Unknown
February 18, 2014
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.