IP Library Granted Patent US 9,940,614
Granted Patent B2
US 9,940,614 · App. 13/986,228 · Granted Apr 10, 2018

Syncing two separate authentication channels to the same account or data using a token or the like

Inventor: Ryan Caldwell (Provo, UT)
Assignee: MX TECHNOLOGIES, INC.
G06Q20/322G06Q20/425H04L9/3215H04L9/3226H04L63/18G06Q20/3221H04L2209/56
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 9,940,614
App. No.
13/986,228
Granted
Apr 10, 2018
Kind
B2
Abstract

Syncing two separate authentication channels to the same account or data using a token or the like is performed. Two authentication channels could be an online login and a mobile device login. Login for one channel creates a unique authentication code. When login from the second channel is desired, the login information is passed to the first channel device to obtain the appropriate authentication code. Then login at a service layer and data access are accomplished.

Claims (46)

1. A method for syncing account authentication from an online banking provider (“OLBP”) with a mobile electronics device (“MED”) comprising:

accessing a device communicatively coupled to an OLBP;

receiving login credentials for the OLBP, the login credentials comprising a username and a password;

logging into the OLBP at the device using the username and password;

generating, at the OLBP, a unique user key for the user based on the username and password;

providing, from the OLBP, the unique user key to a personal financial management (“PFM”) software service layer;

creating, at the PFM software service layer, an account for the user based on the unique user key;

generating, at the PFM software service layer, a globally unique identifier (“GUID”);

associating, at the PFM software service layer, the GUID with the user;

accessing a MED comprising a PFM application;

receiving the login credentials for the OLBP at the MED, the login credentials comprising the username and the password;

logging into the MED PFM application using the username and the password;

providing the username and the password to the PFM software service layer from the MED PFM application via a first authentication channel, the PFM software service layer executing on a device remote from the MED and the OLBP, the first authentication channel comprising a communication channel between the MED PFM application and the PFM software service layer;

logging into the OLBP via the PFM software service layer using the username and the password;

determining the unique user key associated with the username and password at the OLBP in response to successfully logging into the OLBP;

providing the unique user key from the OLBP to the PFM software service layer via a second authentication channel, the second authentication channel comprising a communication channel between the PFM software service layer and the OLBP;

determining, at the PFM software service layer, the globally unique identifier (“GUID”) associated with the user based on the unique user key;

accessing, at the PFM service layer, account data for the user, the account data being accessible using the GUID associated with the user;

associating, by the remote device executing the PFM software service layer, the account data uniquely identified by the user key with the username and password based on the GUID; and

providing the account data to the MED PFM application for display on the MED within the MED PFM application.

2. A method as recited in claim 1 , further comprising permitting the user to conduct banking transactions using the account data through the MED PFM application.

3. A method as recited in claim 1 , further comprising permitting the user to manipulate and change the account data through the MED PFM application.

4. A method as recited in claim 1 , further comprising accessing a database where the account data is stored.

5. A method as recited in claim 4 , wherein accessing a database is performed by the PFM service layer.

6. A computer program product comprising a non-transitory computer readable storage medium storing code executable by a processor to perform operations, the operations comprising:

receiving login credentials at a first device for a banking platform, the login credentials comprising a username and a password, the banking platform in communication with a software service layer via a first authentication channel between the banking platform and the software service layer, the software service layer executing on a device remote from the first device;

logging into the banking platform via the first device using the username and the password;

generating a user key, via the banking platform, based on the username and the password in response to logging into the banking platform;

providing the user key to the software service layer from the banking platform via the first authentication channel;

creating, at the software service layer, an account for the user based on the unique user key;

generating, at the software service layer, a globally unique identifier (“GUID”);

associating, at the software service layer, the GUID with the user;

receiving the username and the password at a second device for a banking application executing on the second device, the second device different than the first device, the banking application in communication with the software service layer via a second authentication channel;

logging into the banking application on the second device using the username and the password;

providing the username and the password to the software service layer via the second authentication channel;

logging into the banking platform via the software service layer using the username and the password;

determining the user key associated with the username and password at the banking platform in response to successfully logging into the banking platform;

providing the user key from the banking platform to the software service layer via the first authentication channel;

determining, at the software service layer, the globally unique identifier (“GUID”) associated with the user based on the user key;

accessing, at the software service layer, account data for the user, the account data being accessible using the GUID associated with the user;

associating, by the remote device executing the software service layer, the account data uniquely identified by the user key with the username and password based on the GUID; and

providing the account data to the banking application for display on the second device within the banking application.

7. A computer program product as recited in claim 6 , the operations further comprising permitting the user to conduct transactions on the account data.

8. A computer program product as recited in claim 6 , the operations further comprising permitting the user to manipulate and change the account data.

9. A computer program product as recited in claim 6 , the operations further comprising accessing a database where the account data is stored.

10. A computer program product as recited in claim 6 , further the operations further comprising running a software application on the second device to manipulate the account data.

Assignments (2)
CHANGE OF NAME Recorded Oct 23, 2015
From: MONEYDESKTOP, INC.
To: MX TECHNOLOGIES, INC.
Reel/Frame 036872/0066 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 3, 2014
From: CALDWELL, RYAN
To: MONEYDESKTOP, INC.
Reel/Frame 033660/0616 →
Continuity (1)
Related Publication 20140310173A1 · Oct 16, 2014