IP Library Granted Patent US 11,526,866
Granted Patent B1
US 11,526,866 · App. 17/068,186 · Granted Dec 13, 2022

Systems and methods for secure wireless payment transactions when a wireless network is unavailable

Inventor: William O. White (Kirkland, WA)
Assignee: STRIPE, INC.
G06Q20/3226G06Q20/20G06Q20/327G06Q20/3672G06Q20/382G06Q20/385G06Q20/401G06Q20/325G06Q20/3278G06Q2220/00
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 11,526,866
App. No.
17/068,186
Granted
Dec 13, 2022
Kind
B1
Abstract

Systems, methods, and devices are disclosed which allow a mobile device user to complete financial transactions even when the mobile device is not connected to a wireless network. The systems, methods, and devices of the present disclosure may utilize a combination of an encrypted lockbox containing out of network payment codes on the mobile device and a matching set of out of network payment codes stored on a server of a payment authority.

Claims (49)

1. A method for authorizing a transaction, the method comprising:

generating, by a payment authority server, a payment code for use by a mobile device when the mobile device is located in areas associated with a risk of disconnection of the mobile device from a communications network, wherein the payment code is associated with a period of validity during which the payment code may be used;

transmitting, by the payment authority server, the payment code to the mobile device;

updating, by the payment authority server, the payment code by extending the period of validity in response to a determination that the mobile device is located in an area associated with the risk of disconnection between the mobile device and the communications network;

receiving at a payment authority server, from a point of sale terminal, the payment code associated with a state of disconnection between the mobile device and the communications network;

authorizing the transaction associated with the point of sale terminal in response to a determination that a set of payment codes stored by the payment authority server contains the payment code received from the point of sale terminal and the payment code is received within the period of validity of the payment code, wherein the set of payment codes stored by the payment authority server is associated with the state of network disconnection between the mobile device and the communications network; and

invalidating the received payment code at the payment authority server for future transactions.

2. The method of claim 1 , further comprising:

marking the payment code, received from the point of sale terminal, as used in the set of payment codes stored by the payment authority server.

3. The method of claim 1 , further comprising:

transmitting a replacement payment code to the mobile device in response to the mobile device connecting to a wireless network.

4. The method of claim 1 , further comprising:

rendering the payment code, received from the point of sale terminal, unusable for a predetermined period of time.

5. The method of claim 1 , further comprising:

associating the set of payment codes stored by the payment authority server with a user of the mobile device.

6. The method of claim 1 , wherein the payment code, received from the point of sale terminal, comprises: a first portion provided to the mobile device by the payment authority server; and a second portion known to a user of the mobile device.

7. The method of claim 1 , wherein a length of the payment code, received from the point of sale terminal, and each stored payment code in the set of payment codes stored by the payment authority server is variable.

8. The method of claim 1 , wherein at least one stored payment code in the set of payment codes stored by the payment authority server is valid indefinitely.

9. A payment authority server, comprising:

at least one processor; and

at least one memory communicatively coupled with the at least one processor, the at least one memory comprising executable code that, when executed by the at least one processor, causes the at least one processor to:

generate a payment code for use by a mobile device when the mobile device is located in areas associated with a risk of disconnection of the mobile device from a communications network, wherein the payment code is associated with a period of validity during which the payment code may be used;

transmit the payment code to the mobile device;

update the payment code by extending the period of validity in response to a determination that the mobile device is located in an area associated with the risk of disconnection between the mobile device and the communications network;

receive at the payment authority server, from a point of sale terminal, the payment code associated with a state of disconnection between the at a mobile device and the communications network;

authorize a transaction associated with the point of sale terminal in response to a determination that a set of payment codes stored by the payment authority server contains the payment code received from the point of sale terminal and the payment code is received within the period of validity of the payment code, wherein the set of payment codes stored by the payment authority server is associated with the state of network disconnection between the mobile device and the communications network; and

invalidate the received payment code at the payment authority server for future transactions.

10. The payment authority server of claim 9 , wherein the executable code is further configured to cause the at least one processor to:

mark the payment code, received from the point of sale device, as used in the set of payment codes stored by the payment authority server.

11. The payment authority server of claim 9 , wherein the executable code is further configured to cause the at least one processor to:

transmit a replacement payment code to the mobile device in response to the mobile device connecting to a wireless network.

12. The payment authority server of claim 9 , wherein the executable code is further configured to cause the at least one processor to:

render the payment code, received from the point of sale device, unusable for a predetermined period of time.

13. The payment authority server of claim 9 , wherein at least one stored payment code in the set of payment codes stored by the payment authority server is valid indefinitely.

14. A non-transitory computer readable storage medium, having one or more instructions stored thereon, which when executed by a processing system of a payment authority server, causes the payment authority server to perform operations, comprising:

generating, by the payment authority server, a payment code for use by a mobile device when the mobile device is located in areas associated with a risk of disconnection of the mobile device from a communications network, wherein the payment code is associated with a period of validity during which the payment code may be used;

transmitting, by the payment authority server, the payment code to the mobile device;

updating, by the payment authority server, the payment code by extending the period of validity in response to a determination that the mobile device is located in an area associated with the risk of disconnection between the mobile device and the communications network;

receiving at a payment authority server, from a point of sale terminal, the payment code associated with a state of disconnection between the mobile device and the communications network;

authorizing the transaction associated with the point of sale terminal in response to a determination that a set of payment codes stored by the payment authority server contains the payment code received from the point of sale terminal and the payment code is received within the period of validity of the payment code, wherein the set of payment codes stored by the payment authority server is associated with the state of network disconnection between the mobile device and the communications network; and

invalidating the received payment code at the payment authority server for future transactions.

15. The non-transitory computer readable storage medium of claim 14 , wherein the operations further comprise:

marking the payment code, received from the point of sale terminal, as used in the set of payment codes stored by the payment authority server.

16. The non-transitory computer readable storage medium of claim 14 , wherein the operations further comprise: transmitting a replacement payment code to the mobile device in response to the mobile device connecting to a wireless network.

17. The non-transitory computer readable storage medium of claim 14 , wherein the operations further comprise:

rendering the payment code, received from the point of sale terminal, unusable for a predetermined period of time.

18. The non-transitory computer readable storage medium of claim 14 , wherein the payment code, received from the point of sale terminal, comprises: a first portion provided to the mobile device by the payment authority server; and a second portion known to a user of the mobile device.

19. The non-transitory computer readable storage medium of claim 14 , wherein a length of the payment code, received from the point of sale terminal, and each stored payment code in the set of payment codes stored by the payment authority server is variable.

20. The non-transitory computer readable storage medium of claim 14 , wherein at least one stored payment code in the set of payment codes stored by the payment authority server is valid indefinitely.

Assignments (2)
CHANGE OF NAME Recorded Mar 6, 2026
From: STRIPE, INC.
To: STRIPE, LLC
Reel/Frame 075020/0639 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 2, 2021
From: CRIA, INC.
To: STRIPE, INC.
Reel/Frame 057044/0753 →
Continuity (5)
Continuation 15667471 · Aug 2, 2017
Continuation 15599327 · May 18, 2017
Continuation 14257437 · Apr 21, 2014
Continuation 13417868 · Mar 12, 2012
Provisional Application 61452102 · Mar 12, 2011