IP Library Granted Patent US 10,699,268
Granted Patent B2
US 10,699,268 · App. 14/984,804 · Granted Jun 30, 2020

Method, server and system for authorizing a transaction

Inventor: Didier Hugot (Austin, TX)
Assignee: THALES DIS FRANCE SA
G06Q20/3821G06Q20/12G06Q20/20G06Q20/325G06Q20/401G06Q20/4014G06Q20/4018G06Q20/40145G06Q20/425
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,699,268
App. No.
14/984,804
Granted
Jun 30, 2020
Kind
B2
Abstract

To authorize a transaction, a first device sends to a first server a transaction-authorization request accompanied with an Id-PAN relating to a user account, and including an identifier of a second device. The first server sends to a second server a user-authorization request accompanied with the Id-PAN and transaction data. The second server sends to the second device a request for user approval including the transaction data and the user account data. The second device requests whether the device user approves a requested transaction. The second device sends to the second server a request for authorizing the transaction and data relating to user approval. The second server verifies whether the requested transaction is approved by the user. The second server sends to a server a verification result including a transaction authorization or refusal.

Claims (50)

1. A method for authorizing a transaction, comprising:

generating, by or through a first device, an Id-PAN, the Id-PAN including a bank issuer identifier and at least in part a second device identifier, the second device identifier allowing to address the second device;

sending, by the first device to a first server, a first message including a request for authorizing a transaction accompanied with the Id-PAN;

sending, by the first server to a payment network, a message including a request for getting at least one identifier relating to a second server accompanied with the Id-PAN, the at least one second server identifier allowing to address the second server;

extracting, by the payment network, the bank issuer identifier from the Id-PAN;

getting, by the payment network, based upon the bank issuer identifier, at least one second server identifier;

sending, by the payment network, to the first server, the at least one second server identifier;

sending, by the first server to the second server, a second message including a request for a user authorization for the transaction accompanied with the Id-PAN and transaction data;

retrieving, by the second server, based upon the Id-PAN, the second device identifier and user account data;

sending, by the second server, based upon the second device identifier, to the second device a third message including a request for getting a user approval relating to the transaction accompanied with the transaction data and the user account data;

requesting a user, by the second device, whether the second device user does or does not approve a requested transaction authorization;

sending, by the second device to the second server, a fourth message including a request for authorizing the transaction accompanied with user approval data;

determining, by the second server, based upon the user approval data, a user approval result, and sending to the first server a fifth message including a response for authorizing the transaction accompanied with the user approval result and the Id-PAN;

sending, by the first server, to the second server a sixth message including a request for authorizing the transaction accompanied with the Id-PAN;

verifying by the second server, based upon the Id-PAN, whether the requested transaction is or is not approved by the user; and

sending by the second server to a server a seventh message including a verification result.

2. The method according to claim 1 , wherein the user of the second device approves the requested transaction authorization by depressing at least one predetermined key at the second device side.

3. The method according to claim 1 , wherein the second device user approves the requested transaction authorization by providing user authentication data to be successfully verified by or through the second device.

4. The method according to claim 3 , wherein the user authentication data includes at least one element of a group comprising:

a Personal Identity Number;

at least one biometric print;

user credentials;

a user name; and

a password.

5. The method according to claim 3 , wherein the second device generates a cryptogram, as user approval data, by using a predetermined cryptogram generation algorithm and the second server generates an expected cryptogram by using the cryptogram generation algorithm, the second server verifies whether the expected cryptogram does or does not match the cryptogram, the second server stores a cryptogram verification result, the user account identifier and the transaction data.

6. The method according to claim 5 , wherein, after having received the sixth message, the second server retrieves, based upon the Id-PAN, the transaction data, the user account identifier and the cryptogram verification result.

7. The method according to claim 6 , wherein the second server verifies whether the cryptogram verification result is a positive cryptogram verification or a negative cryptogram verification.

8. A system for authorizing a transaction,

wherein, the system comprising a payment network, a first device, a second device, a first server and a second sever, the first device is configured to:

generate an Id-PAN, the Id-PAN including a bank issuer identifier and at least in part a second device identifier, the second device identifier allowing to address the second device; and

send, to a first server, a first message including a request for authorizing a transaction accompanied with the Id-PAN;

wherein the first server is configured to send, to the payment network, a message including a request for getting at least one identifier relating to a second server accompanied with the Id-PAN, the at least one second server identifier allowing to address the second server;

wherein the payment network is configured to:

extract the bank issuer identifier from the Id-PAN;

get, based upon the bank issuer identifier, at least one second server identifier; and

send, to the first server, the at least one second server identifier;

wherein the first server is configured to send, to the second server, a second message including a request for a user authorization for the transaction accompanied with the Id-PAN and transaction data;

wherein the second server is configured to:

retrieve, based upon the Id-PAN, the second device identifier and user account data; and

send, based upon the second device identifier, to the second device, a third message including a request for getting a user approval relating to the transaction accompanied with the transaction data and the user account data;

wherein the second device is configured to:

request a user whether the second device user does or does not approve a requested transaction authorization; and

send, to the second server, a fourth message including a request for authorizing the requested transaction accompanied with user approval data;

wherein the second server is configured to:

determine, based upon the user approval data, a user approval result; and

send, to the first server, a fifth message including a response for authorizing the transaction accompanied with the user approval result and the Id-PAN;

wherein the first server is configured to send, to the second server, a sixth message including a request for authorizing a requested transaction accompanied with the Id-PAN; and

wherein the second server is configured to:

verify, based upon the Id-PAN, whether the requested transaction is or is not approved by the user; and

send, to a server, a seventh message including a verification result.

Assignments (4)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 28, 2023
From: THALES DIS FRANCE SA
To: THALES DIS FRANCE SAS
Reel/Frame 064730/0238 →
CHANGE OF NAME Recorded May 1, 2020
From: GEMALTO SA
To: THALES DIS FRANCE SA
Reel/Frame 052548/0653 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 11, 2016
From: GEMALTO, INC.
To: GEMALTO SA
Reel/Frame 038542/0218 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 30, 2016
From: HUGOT, DIDIER
To: GEMALTO INC.
Reel/Frame 038136/0411 →