IP Library Granted Patent US 10,984,406
Granted Patent B2
US 10,984,406 · App. 16/424,123 · Granted Apr 20, 2021

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 10,984,406
App. No.
16/424,123
Granted
Apr 20, 2021
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 (53)

1. A method for performing a transaction, comprising:

receiving, by a transaction management system from a merchant Point Of Sale (POS) device, a first merchant transaction authorization request that does not include a transaction amount and that identifies a merchant and a first checkout token that was previously issued to a customer account;

creating, by the transaction management system, a pending transaction in association with at least one customer payment account associated with the customer account;

providing, by the transaction management system for display on a customer mobile device that is linked with the customer account, a first pending transaction screen that identifies the merchant, at least one offer that is based on information in the customer account, and the at least one customer payment account;

receiving, by the transaction management system from the merchant POS device and subsequent to providing the first pending transaction screen for display on the customer mobile device, a second merchant transaction authorization request that includes a transaction amount due;

providing, by the transaction management system for display on the customer mobile device subsequent to providing the first pending transaction screen for display on the customer mobile device, a second pending transaction screen that identifies the merchant, the at least one customer payment account, and the transaction amount due; and

causing, by the transaction management system subsequent to providing the second pending transaction screen for display on the customer mobile device, funds to be transferred from the at least one customer payment account to the merchant.

2. The method of claim 1 , wherein the at least one customer payment account includes a plurality of customer payment accounts, and the method further comprises:

receiving, by the transaction management system, a selection of a first customer payment account from the plurality of customer payment accounts, wherein the transaction management system causes the funds to be transferred from the first customer payment account to the merchant.

3. The method of claim 2 , wherein the transaction management system identifies the plurality of customer payment accounts using a plurality of customer provided rules that are associated with the customer account.

4. The method of claim 1 , wherein the

at least one offer that is based on information in the customer account includes at least one of a coupon, a loyalty incentive, or an advertisement.

5. The method of claim 1 , wherein the first pending transaction screen includes:

an indication that the transaction management system is waiting on the transaction amount due from the merchant.

6. The method of claim 1 , further comprising:

issuing, by the transaction management system prior to receiving the first merchant transaction authorization request, a plurality of checkout tokens that include the first checkout token.

7. The method of claim 1 , wherein the at least one customer payment account includes a merchant loyalty account, and wherein the second pending transaction screen includes:

a calculated loyalty savings resulting from the use of the merchant loyalty account.

8. The method of claim 1 , wherein the creating the pending transaction in association with the at least one customer payment account includes:

selecting the at least one customer payment account based on the transaction amount due.

9. The method of claim 8 , wherein the at least one customer payment account is designated as a default account for the transaction amount due.

10. The method of claim 1 , wherein the creating the pending transaction in association with the at least one customer payment account includes:

selecting the at least one customer payment account based on an identity of the merchant.

11. A transaction management system, comprising:

a non-transitory memory; and

at least one hardware processor coupled to the non-transitory memory and configured to read instructions from the non-transitory memory to cause the system to perform operations comprising:

receiving, from a merchant Point Of Sale (POS) device, a pending merchant transaction authorization request that does not include a transaction amount and that identifies a merchant and a checkout token that was previously issued to a customer account;

creating a pending transaction in association with at least one customer payment account associated with the customer account;

providing, for display on a computing device that is linked with the customer account, a pending transaction screen that identifies the merchant, at least one offer that is based on information in the customer account, and the at least one customer payment account;

receiving, from the merchant POS device and subsequent to providing the pending transaction screen for display on the computing device, an updated merchant transaction authorization request that includes a transaction amount due;

providing, for display on the computing device subsequent to providing the pending transaction screen for display on the computing device, an updated transaction screen that identifies the merchant, the at least one customer payment account, and the transaction amount due; and

causing, subsequent to providing the updated transaction screen for display on the computing device, funds to be transferred from the at least one customer payment account to the merchant.

12. The transaction management system of claim 11 , wherein the at least one customer payment account includes a plurality of customer payment accounts, and the operations further comprise:

receiving a selection of a first customer payment account from the plurality of customer payment accounts and, in response, causing the funds to be transferred from the first customer payment account to the merchant.

13. The transaction management system of claim 12 , wherein the plurality of customer payment accounts are identified using a plurality of customer provided rules that are associated with the customer account.

14. The transaction management system of claim 11 , wherein the at least one offer that is based on information in the customer account includes at least one of a coupon, a loyalty incentive, or an advertisement.

15. The transaction management system of claim 11 , wherein the operations further comprise:

issuing, prior to receiving the pending merchant transaction authorization request, a plurality of checkout tokens that include the checkout token that was previously issued to the customer account.

16. The transaction management system of claim 11 , wherein the at least one customer payment account includes a merchant loyalty account, and wherein the updated transaction screen includes:

a calculated loyalty savings resulting from a use of the merchant loyalty account.

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

receiving, from a merchant Point Of Sale (POS) device, a pending transaction authorization request that does not include a transaction amount;

creating a pending transaction in association with at least one customer payment account that is associated with a customer identified in the pending transaction authorization request;

providing, for display on a device that is linked with the customer, a pending transaction screen that identifies a merchant identified in the pending transaction authorization request, at least one offer that is based on information in a customer account, and the at least one customer payment account;

receiving, from the merchant POS device and subsequent to providing the pending transaction screen for display on the device, an updated transaction authorization request that includes a transaction amount due;

providing, for display on the device subsequent to providing the pending transaction screen for display on the device, an updated transaction screen that identifies the transaction amount due; and

causing, subsequent to providing the updated transaction screen for display on the device and in order to complete the pending transaction, funds to be transferred from the at least one customer payment account to the merchant; and

completing the pending transaction after the funds have been transferred from the at least one customer payment account to the merchant.

18. The non-transitory, machine-readable medium of claim 17 , wherein the creating the pending transaction in association with at least one customer payment account includes:

selecting the at least one customer payment account based on the transaction amount due.

19. The non-transitory, machine-readable medium of claim 18 , wherein the at least one customer payment account is designated as a default account for the transaction amount due.

20. The non-transitory, machine-readable medium of claim 17 , wherein the creating the pending transaction in association with at least one customer payment account includes:

selecting the at least one customer payment account based on an identity of the merchant.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 7, 2021
From: PAYDIANT, LLC
To: PAYPAL, INC.
Reel/Frame 054839/0157 →
CHANGE OF NAME Recorded Jan 7, 2021
From: PAYDIANT, INC.
To: PAYDIANT, LLC
Reel/Frame 054914/0198 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 6, 2021
From: LARACEY, KEVIN
To: PAYDIANT, INC.
Reel/Frame 054830/0794 →
Continuity (19)
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 61582010 · Dec 30, 2011
Provisional Application 61426731 · Dec 23, 2010
Provisional Application 61362567 · Jul 8, 2010
Provisional Application 61322477 · Apr 9, 2010
Related Publication 20190347646A1 · Nov 14, 2019
Cited By (2)
US 12,349,141 US 12,417,447