IP Library Granted Patent US 12,205,116
Granted Patent B1
US 12,205,116 · App. 18/492,924 · Granted Jan 21, 2025

Systems and methods for executing an authenticated service

Inventors: Ashleigh D. DePopas (Denver, CO); Ian Hillis (Denver, CO); Richard Scheffrin (Georgetown, TX); Steven Walchek (Denver, CO)
Assignee: SKIPIFY, INC.
G06Q20/401G06Q20/3674G06Q20/3825
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 12,205,116
App. No.
18/492,924
Granted
Jan 21, 2025
Kind
B1
Abstract

Systems and methods are disclosed for executing an electronic transaction using a digital wallet. One method includes receiving a guest checkout request and electronic transaction data from an electronic transaction browser. Whether a user is enrolled in the digital wallet system may be determined by the digital wallet system. The digital wallet system may authorize an electronic transaction based on the electronic transaction data upon determining the user is not enrolled in the digital wallet system. The digital wallet system may initiate a digital wallet enrollment upon authorizing the electronic transaction. The digital wallet system may store the user data in the digital wallet system and transmit a verification request to the electronic transaction browser. The digital wallet system may receive a verification response from the electronic transaction browser and may generate a digital wallet enrollment status message based on the verification response.

Claims (65)

1. A computer-implemented method comprising:

receiving, by a first sub-system, a request from a device associated with a user, wherein the request is for a service comprising a digital wallet service and provided by the first subsystem, and the first sub-system includes one or more servers and an interface associated with the service;

determining, by the first sub-system, registration status of the user;

initiating, by the first sub-system, a registration process of the user upon determining the user is not registered with the service, wherein the initiating the registration process further comprises:

checking, by the first sub-system, the registration status of the user upon receiving a one-time password or a two-factor authentication code;

determining, by the first sub-system, pendency of the registration has exceeded a pre-determined time threshold;

generating, by the first sub-system, a first notification in the user interface of the device for displaying the one-time password authentication request or the two-factor authentication request; and

validating, by the first sub-system, the one-time password or the two-factor authentication code for approving the registration of the user;

generating, by the first sub-system, a first token based upon user information; and

exchanging, by the first sub-system, the first token with a second token associated with a second sub-system for processing the request for the service, wherein the second subsystem is registered with the first sub-system.

2. The computer-implemented method of claim 1 , further comprising:

determining, by the first sub-system, an authorization of the request for the service is unsuccessful; and

generating, by the first sub-system, an error notification in a user interface of the device, wherein the error notification includes a review screen for the user to re-confirm entered information.

3. The computer-implemented method of claim 1 , further comprising:

determining, by the first sub-system, an authorization of the request for the service is successful; and

generating, by the first sub-system, a success notification in a user interface of the device.

4. The computer-implemented method of claim 1 , wherein determining the registration status of the user, further comprises:

processing, by the first sub-system, the request for the service; and

generating, by the first sub-system, a second notification in a user interface that is integrated by the second sub-system for displaying a one-time password authentication request or a two-factor authentication request in the device.

5. The computer-implemented method of claim 4 , wherein the user interface is integrated into the second sub-system by utilizing a software development kit of the first sub-system.

6. The computer-implemented method of claim 1 , further comprising

generating, by the first sub-system, response objects based on the user information and/or service information; and

generating, by the first sub-system, a display of an order review screen with the response objects in the user interface of the device.

7. The computer-implemented method of claim 6 , further comprising:

providing an auto-populating service that populates data fields in the order review screen with saved user information.

8. The computer-implemented method of claim 1 , wherein the first token is a low-value token, a high-value token, a randomly generated number, a pseudorandom number, or a character sequence.

9. The computer-implemented method of claim 1 , wherein the first token is encrypted and unique for each of the request, the user, or the second sub-system.

10. A system comprising:

one or more processors of a first sub-system;

a data storage storing instructions which, when executed by the one or more processors, cause the one or more processors to perform operations comprising:

receiving a request from a device associated with a user, wherein the request is for a service comprising a digital wallet service and provided by the first sub-system, and the first sub-system includes one or more servers and an interface associated with the service;

determining registration status of the user;

initiating a registration process of the user upon determining the user is not registered with the service, wherein the initiating the registration process further comprises:

checking, by the first sub-system, the registration status of the user upon receiving a one-time password or a two-factor authentication code;

determining, by the first sub-system, pendency of the registration has exceeded a pre-determined time threshold;

generating, by the first sub-system, a first notification in the user interface of the device for displaying the one-time password authentication request or the two-factor authentication request; and

validating, by the first sub-system, the one-time password or the two-factor authentication code for approving the registration of the user;

generating a first token based upon user information; and

exchanging the first token with a second token associated with a second sub-system for processing the request for the service, wherein the second sub-system is registered with the first sub-system.

11. The system of claim 10 , further comprising:

determining an authorization of the request for the service is unsuccessful; and

generating an error notification in a user interface of the device, wherein the error notification includes a review screen for the user to re-confirm entered information.

12. The system of claim 10 , further comprising:

determining an authorization of the request for the service is successful; and

generating a success notification in a user interface of the device.

13. The system of claim 10 , wherein determining the registration status of the user, further comprises:

processing the request for the service; and

generating a second notification in a user interface that is integrated by the second subsystem for displaying a one-time password authentication request or a two-factor authentication request in the device.

14. The system of claim 13 , wherein the user interface is integrated into the second sub-system by utilizing a software development kit of the first sub-system.

15. The system of claim 10 , further comprising:

generating response objects based on the user information and/or service information; and

generating a display of an order review screen with the response objects in the user interface of the device.

16. A non-transitory computer readable medium, the non-transitory computer readable medium storing instructions which, when executed by one or more processors of a first sub-system, cause the one or more processors to perform operations, comprising:

receiving a request from a device associated with a user, wherein the request is for a service comprising a digital wallet service and provided by the first sub-system, and the first sub-system includes one or more servers and an interface associated with the service;

determining registration status of the user;

initiating a registration process of the user upon determining the user is not registered with the service, wherein the initiating the registration process further comprises:

checking, by the first sub-system, the registration status of the user upon receiving a one-time password or a two-factor authentication code;

determining, by the first sub-system, pendency of the registration has exceeded a pre-determined time threshold;

generating, by the first sub-system, a first notification in the user interface of the device for displaying the one-time password authentication request or the two-factor authentication request; and

validating, by the first sub-system, the one-time password or the two-factor authentication code for approving the registration of the user;

generating a first token based upon user information; and

exchanging the first token with a second token associated with a second sub-system for processing the request for the service, wherein the second sub-system is registered with the first sub-system.

17. The non-transitory computer readable medium of claim 16 , wherein determining the registration status of the user, further comprises:

processing the request for the service; and

generating a first notification in a user interface that is integrated by the second sub-system for displaying a one-time password authentication request or a two-factor authentication request in the device, wherein the user interface is integrated into the second sub-system by utilizing a software development kit of the first sub-system.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 6, 2024
From: WORLDPAY LLC
To: SKIPIFY, INC.
Reel/Frame 067663/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 24, 2023
From: DEPOPAS, ASHLEIGH D.; HILLIS, IAN; SCHEFFRIN, RICHARD; WALCHEK, STEVEN
To: WORLDPAY, LLC
Reel/Frame 065319/0978 →
Continuity (3)
Continuation 17889261 · Aug 16, 2022
Continuation 17106654 · Nov 30, 2020
Provisional Application 62705037 · Jun 8, 2020
References Cited (34)
US 10686600B1 · Vo et al. · 2020 [cited by applicant]
US 11232433B1 · Kurani et al. · 2022 [cited by applicant]
US 20010039535A1 · Tsiounis et al. · 2001 [cited by applicant]
US 20060200735A1 · Ormond · 2006 [cited by examiner]
US 20080243702A1 · Hart · 2008 [cited by examiner]
US 20120166333A1 · Behren et al. · 2012 [cited by applicant]
US 20120290376A1 · Dryer et al. · 2012 [cited by applicant]
US 20120316992A1 · Oborne · 2012 [cited by examiner]
US 20130212387A1 · Oberheide · 2013 [cited by examiner]
US 20130317928A1 · Laracey · 2013 [cited by applicant]
US 20140344153A1 · Raj · 2014 [cited by examiner]
US 20140351126A1 · Priebatsch · 2014 [cited by applicant]
US 20150121496A1 · Andrada et al. · 2015 [cited by applicant]
US 20150165319A1 · Bono · 2015 [cited by examiner]
US 20150254672A1 · Huesch et al. · 2015 [cited by applicant]
US 20150339666A1 · Wilson et al. · 2015 [cited by applicant]
US 20160127356A1 · Fukuda et al. · 2016 [cited by applicant]
US 20160321663A1 · Batlle · 2016 [cited by applicant]
US 20170099597A1 · Choi · 2017 [cited by examiner]
US 20170357976A1 · Malik et al. · 2017 [cited by applicant]
US 20170364918A1 · Malhotra et al. · 2017 [cited by applicant]
US 20180047016A1 · Sarin · 2018 [cited by applicant]
US 20190080312A1 · Yeager · 2019 [cited by examiner]
US 20190333055A1 · Mohammed et al. · 2019 [cited by applicant]
US 20190347431A1 · Nair · 2019 [cited by applicant]
US 20190386984A1 · Thakkar et al. · 2019 [cited by applicant]
US 20200160323A1 · Ledwell · 2020 [cited by examiner]
US 20200264766A1 · Hameed · 2020 [cited by examiner]
US 20210224789A1 · Jones · 2021 [cited by applicant]
US 20210233200A1 · Meltzer et al. · 2021 [cited by applicant]
Secure and reliabe routing protocol for transmission data in wireless sensor mesh networks Bany Muhammad, Nooh Adel. ProQuest Dissertations and ThesesProQuest Dissertations & Theses. (2015) (Year: 2015). [cited by examiner]
Microsoft Alters Azure Active Directory Refresh Token Settings ICT Monitor WorldwideAmman: Disco Digital Media, Inc. (Sep. 1, 2017) (Year: 2015). [cited by examiner]
International Search Report and Written Opinion in PCT Application No. PCT/US2021/059371, dated Mar. 4, 2022, (12 pages). [cited by applicant]
IP.com NPL Search Strategy (Year: 2022). [cited by applicant]