IP Library Granted Patent US 11,961,065
Granted Patent B2
US 11,961,065 · App. 17/235,566 · Granted Apr 16, 2024

NFC mobile wallet processing systems and methods

Inventor: Kevin Laracey (Natick, MA)
Assignee: PAYPAL, INC.
G06Q20/3278G06Q20/108G06Q20/20G06Q20/322G06Q20/3276G06Q20/36G06Q30/0226G06Q30/0241G06Q30/0253G06Q30/06
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,961,065
App. No.
17/235,566
Granted
Apr 16, 2024
Kind
B2
Abstract

Embodiments of the present invention relate to systems, methods, processes, computer program code, and means for employing the wireless or near field communication (“NFC”) functionality of mobile devices and payment terminals for use in payment, loyalty, and offer and coupon transactions.

Claims (70)

1. A method for authenticating and processing transactions, the method comprising:

receiving, by a transaction management system from a merchant device, a merchant payment authorization request for a transaction between the merchant device and a user device, the merchant payment authorization request issued prior to transaction details of the transaction being finalized;

establishing an active session between the user device and the transaction management system based on the receiving the merchant payment authorization request;

authenticating, during the active session, a user of the user device for conducting transactions with the merchant device;

responsive to determining that the user has been authenticated, formatting a checkout token with a primary account number associated with the user, wherein the primary account number is provided in a message field of a near field communication (NFC) message corresponding to the checkout token;

transmitting the checkout token to the user device;

causing a first screen to be displayed on the merchant device by the transaction management system, wherein the first screen includes a checkout request to read an NFC component of the user device to transmit the checkout token to the merchant device;

updating, by the transaction management system and based on the merchant payment authorization request, a pending transaction in association with at least one customer account associated with the user of the user device;

receiving, by the transaction management system from the merchant device, the checkout token and an updated merchant payment authorization request that includes finalized transaction details with a transaction amount for the transaction;

determining the active session is no longer available based on the checkout token being unable to be matched to the active session;

determining the primary account number from the field of the NFC message corresponding to the checkout token;

determining that the user device was authenticated for conducting the transaction during the active session prior to the active session no longer being available; and

authorizing, independent of establishing a new session to authenticate the user device for conducting the transaction, the transaction based on the updated merchant payment authorization request, the updated pending transaction, and the checkout token received from the merchant device.

2. The method of claim 1 , further comprising:

determining a merchant associated with the merchant device; and

determining whether the checkout token was previously issued to the least one customer account for the user of the user device.

3. The method of claim 1 , further comprising:

providing, by the transaction management system to the user device, information for display at a user interface (UI) of the user device, the information identifying the merchant and the at least one customer account.

4. The method of claim 1 , further comprising:

providing, subsequent to receiving the updated merchant payment authorization request and by the transaction management system to the user device, information for display at a user interface (UI) of the user device, the information comprising at least a portion of the finalized transaction details.

5. The method of claim 1 , wherein said authorizing the transaction comprises causing, by the transaction management system and based on the finalized transaction details, a transfer of funds from the at least one customer account to an account of the merchant.

6. The method of claim 1 , further comprising:

transmitting an indication of the transaction being authorized to at least one of the merchant device or the user device.

7. The method of claim 1 , wherein the transaction management system updates the pending transaction further based on a plurality of customer provided rules that are associated with the at least one customer account.

8. The method of claim 1 , wherein the at least one customer account includes a merchant loyalty account, and wherein the method further comprises:

providing, prior to finalizing the transaction details, a calculated loyalty savings resulting from use, by the user, of the merchant loyalty account.

9. The method of claim 1 , wherein said updating the pending transaction in association with at least one customer account includes:

selecting at least one payment account, for funding a transfer of funds for the transaction, based on an identity of the merchant.

10. A transaction management system, comprising:

a non-transitory memory storing instructions; and

a processor configured to execute the instructions to cause the transaction management system to:

access a merchant payment authorization request, received from a merchant device at a first time, for a transaction between the merchant device and a user device, the merchant payment authorization request issued prior to transaction details of the transaction being finalized;

establish an active session between the user device and the transaction management system;

authenticate, during the active session, a user on the user device;

generate, based on at least one customer account associated with the user and the merchant payment authorization request, a checkout token associated with the user device during the active session responsive to authenticating the user on the user device, wherein the checkout token is transmissible via near field communication (NFC) messaging, and wherein the checkout token is generated to provide at least one account number associated with the at least one customer account in a message field of an NFC message corresponding to the checkout token;

load the checkout token to the user device using the NFC message;

cause a first screen to be displayed on the merchant device, wherein the first screen includes a checkout request to read an NFC component of the user device using the merchant device receive a checkout token;

update, in response to identifying the checkout token and based on the merchant payment authorization request, a pending transaction in association with the at least one customer account associated with the user of the user device;

access an updated merchant payment authorization request, received from the merchant device with the checkout token at a second time after the first time, for the transaction between the merchant device and the user device, the updated merchant payment authorization request including finalized transaction details with a transaction amount for the transaction, wherein the active session has ended with the user device at the second time;

extract the at least one account number from the checkout token;

identify the at least one customer account using the extracted at least one account number; and

authorize, independent of establishing a new session to authenticate the user device for conducting the transaction, the transaction based on the updated merchant payment authorization request, the updated pending transaction, and the identified at least one customer account.

11. The transaction management system of claim 10 , wherein authorizing the transaction comprises causing, by the transaction management system and based on the finalized transaction details, a transfer of funds from at least one customer payment account associated with the least one customer account to an account of the merchant.

12. The transaction management system of claim 10 , wherein executing the instructions further causes the transaction management system to:

provide, subsequent to receiving the updated merchant payment authorization request and by the transaction management system to the user device, information for display at a user interface (UI) of the user device, the information comprising at least a portion of the finalized transaction details.

13. The transaction management system of claim 10 , wherein executing the instructions further causes the transaction management system to:

provide, by the transaction management system to the user device, information for display at a user interface (UI) of the user device, the information identifying the merchant and the at least one customer account, the information further identifying at least one offer that is based on information in the least one customer account.

14. The transaction management system of claim 10 , wherein the at least one customer account is identified using a plurality of customer provided rules that are associated with the user.

15. A non-transitory machine-readable medium having stored thereon machine-readable instructions executable to cause a machine to perform operations comprising:

receiving, by a transaction management system from a merchant device, a merchant payment authorization request for a transaction between the merchant device and a user device, the merchant payment authorization request issued prior to transaction details of the transaction being finalized;

establishing an active session between the user device and the transaction management system based on the receiving the merchant payment authorization request;

authenticating, during the active session, a user of the user device for conducting transactions with the merchant device;

responsive to determining that the user has been authenticated, formatting a checkout token with a primary account number associated with the user, wherein the primary account number is provided in a message field of a near field communication (NFC) message corresponding to the checkout token;

transmitting the checkout token to the user device;

causing a first screen to be displayed on the merchant device by the transaction management system, wherein the first screen includes a checkout request to read an NFC component of the user device to transmit the checkout token to the merchant device;

updating, by the transaction management system and based on the merchant payment authorization request, a pending transaction in association with at least one customer account associated with the user of the user device;

receiving, by the transaction management system from the merchant device, the checkout token and an updated merchant payment authorization request that includes finalized transaction details with a transaction amount for the transaction;

determining an absence of the active session based on the checkout token being unable to be matched to the active session;

determining the primary account number from the field of the NFC message corresponding to the checkout token;

determining that the user device was authenticated for conducting the transaction during the active session prior to the absence of the active session; and

authorizing, independent of establishing a new session to authenticate the user device for conducting the transaction, the transaction based on the updated merchant payment authorization request, the updated pending transaction, and the checkout token received from the merchant device.

16. The non-transitory machine-readable medium of claim 15 , wherein the operations further comprise:

determining a merchant associated with the merchant device; and

determining whether the checkout token was previously issued to the least one customer account.

17. The non-transitory machine-readable medium of claim 15 , wherein the operations further comprise:

providing, subsequent to receiving the updated merchant payment authorization request and by the transaction management system to the user device, information for display at a user interface (UI) of the user device, the information comprising at least a portion of the finalized transaction details.

18. The non-transitory machine-readable medium of claim 15 , wherein said authorizing the transaction comprises causing, by the transaction management system and based on the finalized transaction details, a transfer of funds from a customer payment account associated with the least one customer account to an account of the merchant.

19. The non-transitory machine-readable medium of claim 15 , wherein said updating the pending transaction is based on a plurality of customer provided rules that are associated with the at least one customer account.

20. The non-transitory machine-readable medium of claim 15 , wherein the at least one customer account includes a merchant loyalty account, and wherein the operations further comprise:

providing, prior to finalizing the transaction details, a calculated loyalty savings resulting from use, by the user, of the merchant loyalty account.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 17, 2022
From: LARACEY, KEVIN
To: PAYDIANT, INC.
Reel/Frame 060240/0484 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 17, 2022
From: PAYDIANT, LLC
To: PAYPAL, INC.
Reel/Frame 060240/0598 →
CHANGE OF NAME Recorded Jun 17, 2022
From: PAYDIANT, INC.
To: PAYDIANT, LLC
Reel/Frame 060528/0853 →
Continuity (20)
Continuation 16424123 · May 28, 2019
Continuation 14632949 · Feb 26, 2015
Continuation In Part 14169067 · Jan 30, 2014
Continuation In Part 14140165 · Dec 24, 2013
Continuation In Part 13893978 · May 14, 2013
Continuation In Part 13768156 · Feb 15, 2013
Continuation In Part 13731348 · Dec 31, 2012
Continuation 13336574 · Dec 23, 2011
Continuation In Part 12846911 · Jul 30, 2010
Continuation 12846911 · Jul 30, 2010
Continuation In Part 12846911 · Jul 30, 2010
Provisional Application 61944987 · Feb 26, 2014
Provisional Application 61758543 · Jan 30, 2013
Provisional Application 61651177 · May 24, 2012
Provisional Application 61646523 · May 14, 2012
Provisional Application 61362567 · Jul 8, 2010
Provisional Application 61582010 · Dec 30, 2011
Provisional Application 61322477 · Apr 9, 2010
Provisional Application 61426731 · Dec 23, 2010
Related Publication 20210312425A1 · Oct 7, 2021