IP Library Granted Patent US 10,360,561
Granted Patent B2
US 10,360,561 · App. 15/055,040 · Granted Jul 23, 2019

System and method for secured communications between a mobile device and a server

Inventors: Dennis Poon (Toronto, CA); Simon Law (Toronto, CA); Richard Burnison (Toronto, CA)
Assignee: Lime Light RM, Inc.
G06Q20/40145G06Q20/027G06Q20/20G06Q20/32G06Q20/322G06Q20/3229G06Q20/389G06Q20/3825G06Q20/3827G06Q20/40G06Q20/407G06Q20/4016G06Q20/4097H04L63/0861H04W4/24H04W12/10H04W12/12G06Q2220/00H04L63/0869H04L2463/101H04W8/26H04W60/00H04W88/16
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,360,561
App. No.
15/055,040
Granted
Jul 23, 2019
Kind
B2
Abstract

The present systems and methods provide for secured communication between a mobile device and a server/gateway. The systems and methods can be used, for example, as a way to confirm whether or not a transaction was actually authorized by the user, thereby settling a chargeback dispute for a previously executed transaction. The method comprises receiving the dispute regarding the transaction including associated transaction data, and retrieving a digital signature associated with the transaction data, the digital signature computed by signing the transaction data. The digital signature is then verified using a public key, wherein the public key corresponds to a private key stored on a mobile device. It is then determined whether or not the transaction is fraudulent based on a verification result of the digital signature.

Claims (53)

1. A method for secured communication between a mobile device and a server, the mobile device having stored thereon a mobile device ID, the method performed on the mobile device comprising:

the mobile device capturing biometric data comprising at least one of fingerprint data, iris data, retina data, and voice data;

the mobile device deriving a supplemental ID from the biometric data, the supplemental ID for verifying a payment ID;

the mobile device sending the supplemental ID and the mobile device ID to the server, the server configured to act as a payment gateway, the server having stored thereon the payment ID and the mobile device ID in association with each other; and

the mobile device receiving from the server a confirmation that a transaction is complete, the confirmation generated at the server based on a verification of a combination of the supplemental ID and the payment ID.

2. The method of claim 1 wherein the supplemental ID comprises encoded data derived from a fingerprint captured by a fingerprint scanner of the mobile device.

3. The method of claim 1 wherein the supplemental ID comprises an image of a fingerprint captured by a fingerprint scanner of the mobile device.

4. The method of claim 1 wherein deriving the supplemental ID comprises receiving the biometric data, obtaining a cryptographic hash using the biometric data, locally verifying the cryptographic hash on the mobile device, and at least one of using the cryptographic hash as the supplemental ID and using the cryptographic hash to derive the supplemental ID.

5. A non-transitory computer readable medium for enabling secured communication between a mobile device and a server, the mobile device having stored thereon a mobile device ID, the computer readable medium comprising computer executable instructions for execution on the mobile device, the computer executable instructions comprising:

the mobile device capturing biometric data comprising at least one of fingerprint data, iris data, retina data, and voice data;

the mobile device deriving a supplemental ID from the biometric data, the supplemental ID for verifying a payment ID;

the mobile device sending the supplemental ID and the mobile device ID to the server, the server configured to act as a payment gateway, the server having stored thereon the payment ID and the mobile device ID in association with each other; and

the mobile device receiving from the server a confirmation that a transaction is complete, the confirmation generated at the server based on a verification of a combination of the supplemental ID and the payment ID.

6. The non-transitory computer readable medium of claim 5 wherein the supplemental ID comprises encoded data derived from a fingerprint captured by a fingerprint scanner of the mobile device.

7. The non-transitory computer readable medium of claim 5 wherein the supplemental ID comprises an image of a fingerprint captured by a fingerprint scanner of the mobile device.

8. The non-transitory computer readable medium of claim 5 wherein deriving the supplemental ID comprises receiving the biometric data, obtaining a cryptographic hash using the biometric data, locally verifying the cryptographic hash on the mobile device, and at least one of using the cryptographic hash as the supplemental ID and using the cryptographic hash to derive the supplemental ID.

9. A method for secured communication between a mobile device and a server, the mobile device having stored thereon a mobile device ID, the method performed on the mobile device comprising:

the mobile device capturing , through a transaction GUI, biometric data comprising at least one of fingerprint data, iris data, retina data, and voice data;

the mobile device deriving a supplemental ID from the biometric data, the supplemental ID for verifying a payment ID;

the mobile device sending the supplemental ID and the mobile device ID to the server, the server configured to act as a payment gateway, the server having stored thereon the payment ID and the mobile device ID in association with each other; and

the mobile device receiving from the server a confirmation that a transaction is complete, the confirmation generated at the server based on a verification of a combination of the supplemental ID and the payment ID.

10. The method of claim 9 wherein the mobile device sends at least one of the supplemental ID and the payment ID without storing the supplemental ID and the payment ID on the mobile device.

11. The method of claim 9 further comprising a registration process for storing the mobile device ID on the mobile device, the method further comprising:

the mobile device receiving from a registration GUI at least the payment ID of a payment account and the supplemental ID, and transmitting the payment ID and the supplemental ID to the server without storing the payment ID and the supplemental ID on the mobile device;

the mobile device receiving from the server a confirmation that the payment ID and the supplemental ID are successfully verified; and,

the mobile device obtaining data for generating the mobile device ID, the mobile device ID stored on the mobile device.

12. The method of claim 11 wherein the mobile device obtains the data for the mobile device ID by at least one of generating and receiving the data.

13. The method of claim 9 wherein the payment ID is comprised of at least one of: a credit card number, an expiry date, a bank card number, a banking number, and a points account number.

14. The method of claim 9 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.

15. The method of claim 9 wherein the mobile device ID is randomly generated.

16. The method of claim 9 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.

17. The method of claim 9 wherein the supplemental ID comprises encoded data derived from a fingerprint captured by a fingerprint scanner of the mobile device.

18. The method of claim 9 wherein the supplemental ID comprises an image of a fingerprint captured by a fingerprint scanner of the mobile device.

19. The method of claim 9 wherein deriving the supplemental ID comprises receiving the biometric data, obtaining a cryptographic hash using the biometric data, locally verifying the cryptographic hash on the mobile device, and at least one of using the cryptographic hash as the supplemental ID and using the cryptographic hash to derive the supplemental ID.

20. A non-transitory computer readable medium for enabling secured communication between a mobile device and a server, the mobile device having stored thereon a mobile device ID, the computer readable medium comprising computer executable instructions for execution on the mobile device, the computer executable instructions comprising:

the mobile device capturing through a transaction GUI, biometric data comprising at least one of fingerprint data, retina data, and voice data;

the mobile device deriving a supplemental ID from the biometric data, the supplemental ID for verifying a payment ID;

the mobile device sending the supplemental ID and the mobile device ID to the server, the server configured to act as a payment gateway, the server having stored thereon the payment ID and the mobile device ID in association with each other; and

the mobile device receiving from the server a confirmation that a transaction is complete, the confirmation generated at the server based on a verification of a combination of the supplemental ID and the payment ID.

21. The non-transitory computer readable medium of claim 20 wherein the mobile device sends at least one of the supplemental ID and the payment ID without storing the supplemental ID and the payment ID on the mobile device.

22. The non-transitory computer readable medium of claim 20 wherein the instructions further comprise a registration process for storing the mobile device ID on the mobile device, the instructions further comprising:

the mobile device receiving from a registration GUI at least the payment ID of a payment account and the supplemental ID, and transmitting the payment ID and the supplemental ID to the server without storing the payment ID and the supplemental ID on the mobile device;

the mobile device receiving from the server a confirmation that the payment ID and the supplemental ID are successfully verified; and,

the mobile device obtaining data for generating the mobile device ID, the mobile device ID stored on the mobile device.

23. The non-transitory computer readable medium of claim 22 wherein the mobile device obtains the data for the mobile device ID by at least one of generating and receiving the data.

24. The non-transitory computer readable medium of claim 20 wherein the payment ID is comprised of at least one of: a credit card number, an expiry date, a bank card number, a banking number, and a points account number.

25. The non-transitory computer readable medium of claim 20 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.

26. The non-transitory computer readable medium of claim 20 wherein the mobile device ID is randomly generated.

27. The non-transitory computer readable medium of claim 20 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.

28. The non-transitory computer readable medium of claim 20 wherein the supplemental ID comprises encoded data derived from a fingerprint captured by a fingerprint scanner of the mobile device.

29. The non-transitory computer readable medium of claim 20 wherein the supplemental ID comprises an image of a fingerprint captured by a fingerprint scanner of the mobile device.

30. The non-transitory computer readable medium of claim 20 wherein deriving the supplemental ID comprises receiving the biometric data, obtaining a cryptographic hash using the biometric data, locally verifying the cryptographic hash on the mobile device, and at least one of using the cryptographic hash as the supplemental ID and using the cryptographic hash to derive the supplemental ID.

Assignments (8)
SECURITY INTEREST Recorded Sep 7, 2021
From: STICKY.IO, INC.
To: GOLDMAN SACHS SPECIALTY LENDING GROUP, L.P.
Reel/Frame 057396/0542 →
RELEASE OF SECURITY INTEREST Recorded Sep 7, 2021
From: CVC CALIFORNIA IV, LLC
To: STICKY.IO, INC.
Reel/Frame 057396/0877 →
CHANGE OF NAME Recorded Sep 13, 2020
From: LIME LIGHT CRM, INC.
To: STICKY.IO, INC.
Reel/Frame 053761/0625 →
CHANGE OF NAME Recorded Mar 16, 2020
From: LIME LIGHT CRM, INC.
To: STICKY.IO, INC.
Reel/Frame 052167/0414 →
SECURITY INTEREST Recorded Sep 30, 2019
From: LIME LIGHT CRM, INC.
To: CVC CALIFORNIA IV, LLC
Reel/Frame 050567/0751 →
SECURITY INTEREST Recorded May 30, 2019
From: SALT TECHNOLOGY INC.
To: 8538824 CANADA CORP.
Reel/Frame 049317/0582 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 30, 2019
From: 8538824 CANADA CORP.
To: SALT PAYMENTS INC.
Reel/Frame 049317/0805 →
CHANGE OF NAME Recorded May 30, 2019
From: SALT PAYMENTS INC.
To: LIME LIGHT CRM, INC.
Reel/Frame 049317/0926 →
Priority Claims (3)
CA 2724297 · Dec 14, 2010 · national
CA 2743035 · Jun 14, 2011 · national
CA 2748481 · Aug 11, 2011 · national
Continuity (10)
Continuation In Part 14173089 · Feb 5, 2014
Continuation In Part 13162324 · Jun 16, 2011
Continuation In Part 15055040
Continuation In Part 13324905 · Dec 13, 2011
Continuation In Part 13162324 · Jun 16, 2011
Continuation In Part 15055040
Continuation In Part 13324888 · Dec 13, 2011
Continuation In Part 13162324 · Jun 16, 2011
Provisional Application 61522862 · Aug 12, 2011
Related Publication 20160180343A1 · Jun 23, 2016
Cited By (6)
US 12,277,537 US 12,301,704 US 12,381,887 US 12,462,245 US 12,563,098 US 12,597,017