IP Library Granted Patent US 9,544,143
Granted Patent B2
US 9,544,143 · App. 13/039,209 · Granted Jan 10, 2017

System and method of notifying mobile devices to complete transactions

Inventors: Jon Oberheide (Ann Arbor, MI); Douglas Song (Ann Arbor, MI); Adam Goodman (Ann Arbor, MI)
Assignee: Duo Security, Inc.
H04L9/32G06F21/305G06F21/31H04L9/321H04W12/06H04W12/08
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,544,143
App. No.
13/039,209
Granted
Jan 10, 2017
Kind
B2
Abstract

A method including registering an authority device for an account on an auth platform; receiving transaction request from an initiator to the auth platform; messaging the authority device with the transaction request; receiving an authority agent response from the authority device to the auth platform; if the authority agent response confirms the transaction, communicating a confirmed transaction to the initiator; and if the authority agent response denies the transaction, communicating a denied transaction to the initiator.

Claims (34)

1. A method of completing a transaction comprising the steps of:

registering an authority device for a first account on an auth platform;

at a website, receiving a login request, the login request comprising a username and password, for a second account; the second account linked to a user identity;

after verifying the username and password as associated with the second account, transmitting both a login transaction request and a descriptor of the user identity, the descriptor retrieved from the second account, from the website to the auth platform;

at the auth platform, receiving the login transaction request and the descriptor of the user identity;

at the auth platform, identifying the first account from the descriptor of the user identity, and identifying the authority device registered for the first account from the first account; messaging the authority device with the login transaction request;

at the auth platform, receiving an authority agent response from the authority device;

verifying the authority agent response is from the authority device registered for the account;

if the authority agent response confirms the transaction in a transaction approval response, communicating a confirmed login transaction response to the website; and

if the authority agent response denies the login transaction in a transaction rejection response, communicating a denied login transaction response to the website; and

wherein a plurality of authority devices are registered, and messaging the authority device includes messaging at least two authority devices and wherein a authority agent response is received from at least one of the two authority devices.

2. The method of claim 1 , wherein messaging the authority device includes pushing a notification to a mobile application; wherein pushing a notification is performed over a channel with real-time alerts through an application on the authority device.

3. The method of claim 2 , wherein pushing a notification includes sending an SMS message to the authority device, the SMS message including a link to a full transaction information and options retrievable through an application.

4. The method of claim 2 , wherein messaging the authority device includes messaging a size limited message to the authority device with a unique identifier of a full message and wherein a response is received through an application providing the full message.

5. The method of claim 1 , wherein the authority device is a mobile computing device for authentication of a user and wherein the authority agent response confirms or denies the identity of an agent of the login transaction request.

6. The method of claim 1 , wherein the authority device is a mobile computing device for authorization of a transaction and wherein the authority agent response confirms or denies a login transaction by an agent; wherein a plurality of authority devices are registered, and messaging the authority device includes messaging at least two authority devices and wherein a received authority agent response is received from at least one of the two authority devices.

7. The method of claim 1 , wherein there is at least one authority device registered for authentication and a second authority device registered for authorization; wherein the received authority agent response from the device for authentication is used in confirming or denying the identity of a first agent of the transaction request; and wherein the received authority agent response from the device for authorization is used in confirming or denying an action of the first agent in a transaction; wherein the device for authorization receives authorization from a second agent; wherein the first agent corresponds to a first user and the second agent corresponds to a second user; wherein the first person is distinct from the second person.

8. The method of claim 1 , wherein messaging the authority device includes tracking state and communication channels of the authority device; wherein the authority device is a single electronic device.

9. The method of claim 8 , wherein a persistent TCP/IP connection is used as a communication channel and messaging the authority device includes initiating a new persistent connection upon network changes of the authority device.

10. The method of claim 1 , further comprising cryptographically authenticating the authority agent response from the authority device.

11. The method of claim 1 , wherein the login transaction request includes information on claimed identity of the agent of the transaction and an action associated with the login transaction.

12. The method of claim 1 , further comprising at the authority device, cryptographically authenticating the authority agent response is from the authority device.

13. The method of claim 1 , wherein receiving an authority agent response comprises receiving an authority agent response denying the login transaction in a transaction rejection response; wherein the transaction rejection response is one of a transaction cancelation response and a transaction fraud response; wherein communicating the denied login transaction response to the website comprises:

if the transaction rejection response is a transaction cancelation response, communicating a cancelled login transaction response to the website, and

if the transaction rejection response is a transaction fraud response, communicating a fraudulent login transaction response to the website;

wherein the transaction cancelation response is distinct from the transaction fraud response.

14. The method of claim 1 , further comprising;

at the website, encrypting the login transaction request using an encryption key;

at the authority device, decrypting the login transaction request using a decryption key;

wherein the auth platform does not possess the decryption key and cannot decrypt the login transaction request.

15. The method of claim 1 , further comprising:

at the authority device, encrypting the authority agent response, using an encryption key, prior to transmitting the authority agent response to the auth platform;

at the website, decrypting the authority agent response using a decryption key;

wherein the auth platform does not possess the decryption key and cannot decrypt the authority agent response.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 11, 2021
From: DUO SECURITY LLC
To: CISCO TECHNOLOGY, INC.
Reel/Frame 056208/0504 →
CHANGE OF NAME Recorded May 11, 2021
From: DUO SECURITY, INC.
To: DUO SECURITY LLC
Reel/Frame 056210/0008 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 25, 2011
From: OBERHEIDE, JON; SONG, DOUGLAS; GOODMAN, ADAM
To: DUO SECURITY, INC.
Reel/Frame 026025/0663 →
Continuity (2)
Provisional Application 61309885 · Mar 3, 2010
Related Publication 20110219230A1 · Sep 8, 2011