IP Library Granted Patent US 12,211,024
Granted Patent B2
US 12,211,024 · App. 17/825,338 · Granted Jan 28, 2025

Payment by use of identifier

Inventors: Brian Grassadonia (San Francisco, CA); Ajit Kalidindi Varma (San Francisco, CA); Mark Jen (San Francisco, CA)
Assignee: Block, Inc.
G06Q20/204G06Q20/10G06Q20/385G06Q20/42
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 12,211,024
App. No.
17/825,338
Granted
Jan 28, 2025
Kind
B2
Abstract

Described is a technology that enables a customer, who uses a payment card in a transaction and further provides an identifier in the same transaction, to use the identifier as a payment mechanism in future transactions. In some embodiments, the technology involves communication between a customer's user device, a payment service system (PSS), and one or more merchant point-of-sale (POS) systems. A merchant POS system collects information in a transaction between the merchant POS system and the customer, including the customer's contact information (e.g., telephone number), and forwards this information to the PSS. The PSS stores the information as an identifier, and the identifier is stored in association with the payment card. In a second transaction, the PSS sends a verification request to the user device based on the identifier (e.g., a text message), and processes the transaction upon confirmation from the customer.

Claims (44)

1. A system comprising:

one or more processors; and

one or more computer-readable media storing executable instructions that, when executed by the one or more processors, cause the one or more processors to:

receive, by one or more servers of a payment service system (PSS) and from a point-of-sale (POS) device associated with a merchant, a request for payment for a transaction between the merchant and a customer of the merchant, wherein the request for payment includes transaction data associated with the transaction and a customer identifier of the customer, wherein the customer identifier comprises at least one of a driver's license number of the customer, a social security number of the customer, an employee identification number of the customer, a device identifier of a customer device of the customer, a mobile application identifier of the customer, an IP address of the customer, a personal identification number (PIN) of the customer, a card verification value (CVV) of the customer, a security access code of the customer, a messaging identifier of the customer, an email address of the customer, or a biometric identifier of the customer;

based on receiving the request for payment, identify, by the one or more servers of the PSS, a financial instrument and the customer device, wherein an association between the customer identifier, the financial instrument, and the device identifier is stored in a database associated with the PSS;

based at least in part on the association, send, by the one or more servers of the PSS, a message to the customer device via a user interface, wherein the user interface comprises a first actuation mechanism to approve the transaction and a second actuation mechanism to cancel the transaction, and wherein the message lacks a financial instrument number of the financial instrument;

receive, by the one or more servers of the PSS and from the customer device, an indication of selection of the first actuation mechanism;

determine, by the one or more servers of the PSS and based on the indication of the selection of the first actuation mechanism, to approve the request for payment; and

initiate, by the one or more servers of the PSS, a transfer of a payment amount associated with the request for payment to pay for the transaction, wherein the transfer is from a financial account associated with the financial instrument to a financial account associated with the merchant.

2. The system of claim 1 , wherein the biometric identifier comprises input associated with a voice of the customer, a face of the customer, a fingerprint of the customer, a heartbeat of the customer, or an iris of the customer.

3. The system of claim 1 , wherein the POS device comprises a first POS device, wherein the transaction comprises a first transaction, wherein the association between the customer identifier, the financial instrument, and the device identifier corresponds to a second transaction conducted at a second POS device, and wherein the first POS device and the second POS device are different POS devices.

4. The system of claim 1 , wherein the database stores one or more financials instruments associated with customer identifiers.

5. A method comprising:

receiving, by one or more servers of a payment service system (PSS) and from a point-of-sale (POS) device associated with a merchant of a plurality of merchants, a request for payment associated with a transaction between the merchant and a customer of the merchant, wherein the request for payment includes transaction data associated with the transaction and a customer identifier of the customer;

based on receiving the request for payment, identifying, by the one or more servers of the PSS, a financial instrument and a customer device of the customer, wherein an association between the customer identifier, the financial instrument, and a device identifier of the customer device is stored in a database associated with the PSS;

based at least in part on the association, sending, by the one or more servers of the PSS, a message to the customer device via a user interface, wherein the user interface comprises a first actuation mechanism to approve the transaction and a second actuation mechanism to cancel the transaction, and wherein the message lacks a financial instrument number of the financial instrument;

receiving, by the one or more servers of the PSS and from the customer device, indication of selection of the first actuation mechanism; and

determining, by the one or more servers of the PSS and based on the indication of the selection of the first actuation mechanism, to approve the request for payment.

6. The method of claim 5 , further comprising:

sending, by the one or more servers of the PSS and to the POS device, an approval message for the request for payment to be output by the POS device; and

initiating, by the one or more servers of the PSS, a transfer of a payment amount associated with the request for payment from a financial account associated with the financial instrument to a financial account associated with the merchant to pay for the transaction.

7. The method of claim 5 , wherein the customer identifier comprises at least one of a driver's license number of the customer, a social security number of the customer, an employee identification number of the customer, the device identifier, a mobile application identifier of the customer, an IP address of the customer, a personal identification number (PIN) of the customer, a card verification value (CVV) of the customer, a security access code of the customer, a messaging identifier of the customer, an email address of the customer, or a biometric identifier of the customer.

8. The method of claim 7 , wherein the biometric identifier comprises input associated with a voice of the customer, a face of the customer, a fingerprint of the customer, a heartbeat of the customer, or an iris of the customer.

9. The method of claim 5 , wherein the POS device comprises a first POS device, wherein the merchant comprises a first merchant, wherein the user interface comprises a first user interface, and wherein the customer identifier was previously provided by the customer via a second user interface presented by a second POS device associated with a second merchant of the plurality of merchants.

10. The method of claim 5 , wherein the POS device is a physical POS device or an online POS device.

11. The method of claim 5 , wherein the financial instrument is a credit card, a debit card, a pre-paid card, a smartcard, a biometrically identifiable instrument, or a virtual wallet.

12. The method of claim 5 , further comprising:

receiving, by the one or more servers of the PSS and prior to receiving the transaction data and from at least one alternate POS device associated with at least one alternate merchant of the plurality of merchants, different transaction data, the different transaction data including the customer identifier and the financial instrument; and

storing, by the one or more servers of the PSS and based at least in part on verifying that the customer identifier is associated with the customer, the customer identifier associated with the financial instrument in the database such that the customer identifier is configured to be utilized at the plurality of merchants to initiate payments for a merchant transaction.

13. The method of claim 5 , wherein the POS device comprises a first POS device, wherein the transaction comprises a first transaction, wherein the association between the customer identifier and the financial instrument corresponds to a second transaction conducted at a second POS device, and wherein the first POS device and the second POS device are different POS devices.

14. One or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, program the one or more processors to perform acts comprising:

receiving, by one or more servers of a payment service system (PSS) and from a point-of-sale (POS) device associated with a merchant, a request for payment including transaction data associated with a transaction and a customer identifier of a customer of the merchant;

based on receiving the request for payment, identifying, by the one or more servers of the PSS, a financial instrument and a customer device of the customer, wherein an association between the customer identifier, the financial instrument, and a device identifier of the customer device is stored in a database associated with the PSS;

based at least in part on the association, sending, by the one or more servers of the PSS, a message to the customer device via a user interface, wherein the user interface comprises a first actuation mechanism to approve the transaction and a second actuation mechanism to cancel the transaction, and wherein the message lacks a financial instrument number of the financial instrument;

receiving, by the one or more servers of the PSS and from the customer device, an indication of selection of the first actuation mechanism; and

determining, by the one or more servers of the PSS and based on the indication of the selection of the first actuation mechanism, to approve the request for payment.

15. The one or more non-transitory computer-readable media of claim 14 , the acts further comprising:

sending, by the one or more servers of the PSS and to the POS device, an approval message for the request for payment to be output by the POS device; and

initiating, by the one or more servers of the PSS, a transfer of a payment amount associated with the request for payment from a financial account associated with the financial instrument to a financial account associated with the merchant to pay for the transaction.

16. The one or more non-transitory computer-readable media of claim 14 , wherein the customer identifier of the customer comprises at least one of a driver's license number of the customer, a social security number of the customer, an employee identification number of the customer, the device identifier, a mobile application identifier of the customer, an IP address of the customer, a personal identification number (PIN) of the customer, a card verification value (CVV) of the customer, a security access code of the customer, a messaging identifier of the customer, an email address of the customer, or a biometric identifier of the customer.

17. The one or more non-transitory computer-readable media of claim 14 , wherein the POS device is a first POS device, wherein the user interface is a first user interface, wherein the customer identifier was previously provided by the customer via a second user interface presented by a second POS device associated with a second merchant.

18. The one or more non-transitory computer-readable media of claim 14 , wherein the message comprises an email.

19. The one or more non-transitory computer-readable media of claim 14 , wherein the message comprises a text message or SMS message.

20. The one or more non-transitory computer-readable media of claim 14 , wherein the message comprises a push notification.

Assignments (2)
CHANGE OF NAME Recorded Sep 18, 2024
From: SQUARE, INC.
To: BLOCK, INC.
Reel/Frame 068989/0310 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 2, 2022
From: GRASSADONIA, BRIAN; VARMA, AJIT KALIDINDI; JEN, MARK
To: SQUARE INC.
Reel/Frame 060975/0337 →
Continuity (3)
Continuation 15675099 · Aug 11, 2017
Continuation 14502703 · Sep 30, 2014
Related Publication 20220398556A1 · Dec 15, 2022
References Cited (79)
US 5870723A · Pare, Jr. et al. · 1999 [cited by applicant]
US 6167517A · Gilchrist et al. · 2000 [cited by applicant]
US 6192142B1 · Pare, Jr. et al. · 2001 [cited by applicant]
US 6243689B1 · Norton · 2001 [cited by applicant]
US 6310966B1 · Dulude et al. · 2001 [cited by applicant]
US 6532541B1 · Chang et al. · 2003 [cited by applicant]
US 6760841B1 · Fernandez · 2004 [cited by applicant]
US 7020778B1 · Miettinen et al. · 2006 [cited by applicant]
US 7949609B2 · Colella · 2011 [cited by applicant]
US 8583496B2 · Yoo · 2013 [cited by examiner]
US 8769556B2 · Guo et al. · 2014 [cited by applicant]
US 9256878B2 · Light et al. · 2016 [cited by applicant]
US 9519901B1 · Dorogusker · 2016 [cited by applicant]
US 9741026B1 · Grassadonia et al. · 2017 [cited by applicant]
US 9754255B1 · Ma et al. · 2017 [cited by applicant]
US 9852418B2 · Mardikar · 2017 [cited by applicant]
US 11348083B1 · Grassadonia et al. · 2022 [cited by applicant]
US 20030061167A1 · Mann et al. · 2003 [cited by applicant]
US 20040059924A1 · Soto et al. · 2004 [cited by applicant]
US 20040107170A1 · Labrou et al. · 2004 [cited by applicant]
US 20060265602A1 · Robinson · 2006 [cited by applicant]
US 20080114699A1 · Yuan et al. · 2008 [cited by applicant]
US 20080189214A1 · Mueller et al. · 2008 [cited by applicant]
US 20080319869A1 · Carlson et al. · 2008 [cited by applicant]
US 20100191652A1 · Eckert · 2010 [cited by examiner]
US 20120197743A1 · Grigg et al. · 2012 [cited by applicant]
US 20130173475A1 · Lund · 2013 [cited by applicant]
US 20130232073A1 · Sheets et al. · 2013 [cited by applicant]
US 20130267200A1 · Weiner et al. · 2013 [cited by applicant]
US 20140058862A1 · Celkonas · 2014 [cited by applicant]
US 20140058865A1 · Yang et al. · 2014 [cited by applicant]
US 20140122267A1 · Tayebi · 2014 [cited by applicant]
US 20140222596A1 · S · 2014 [cited by applicant]
US 20150088750A1 · Dua · 2015 [cited by examiner]
US 20150088755A1 · Sobel et al. · 2015 [cited by applicant]
US 20150120557A1 · Zhang · 2015 [cited by applicant]
US 20150310419A1 · Kadaster et al. · 2015 [cited by applicant]
US 20150317638A1 · Donaldson · 2015 [cited by applicant]
US 20150348018A1 · Campos et al. · 2015 [cited by applicant]
US 20160048821A1 · Sprecher · 2016 [cited by applicant]
US 20160125415A1 · Mardikar et al. · 2016 [cited by applicant]
US 20160125416A1 · Spencer et al. · 2016 [cited by applicant]
US 20160217279A1 · Scully-Power et al. · 2016 [cited by applicant]
US 20160364730A1 · Rans et al. · 2016 [cited by applicant]
US 20170053275A1 · Hogl et al. · 2017 [cited by applicant]
US 20170208464A1 · Guertler et al. · 2017 [cited by applicant]
US 20200410500A1 · Dorogusker · 2020 [cited by applicant]
US 20220366424A1 · Dorogusker et al. · 2022 [cited by applicant]
WO 9809227A1 · 2013 [cited by applicant]
WO 2013123438A1 · 2013 [cited by applicant]
Schneier, B., “Protocol Building Blocks,” in Applied Cryptography—Second Edition—Protocols, Algorithms and Source Code in C, Chapter-2, pp. 37-38, Phil Sutherland, Katherine Schowalter (1996). [cited by applicant]
Non-Final Office Action mailed Jun. 16, 2016, for U.S. Appl. No. 14/502,703, of Grassadonia, B., et al., filed Sep. 30, 2014. [cited by applicant]
Notice of Allowance mailed Aug. 18, 2016, for U.S. Appl. No. 14/985,130, of Dorogusker, J., filed Dec. 30, 2015. [cited by applicant]
Final Office Action mailed Dec. 29, 2016, for U.S. Appl. No. 14/502,703, of Grassadonia, B., et al., filed Sep. 30, 2014. [cited by applicant]
Non Final Office Action mailed Mar. 9, 2017, for U.S. Appl. No. 15/339,744, of Dorogusker, J., filed Oct. 31, 2016. [cited by applicant]
Notice of Allowance mailed Apr. 20, 2017, for U.S. Appl. No. 14/502,703, of Grassadonia, B., et al., filed Sep. 30, 2014. [cited by applicant]
Final Office Action mailed Aug. 17, 2017, for U.S. Appl. No. 15/339,744, of Dorogusker, J., filed Oct. 31, 2016. [cited by applicant]
Advisory Action mailed Oct. 31, 2017, for U.S. Appl. No. 15/339,744, of Dorogusker, J., filed Oct. 31, 2016. [cited by applicant]
Non Final Office Action mailed Jun. 1, 2018, for U.S. Appl. No. 15/339,744, of Dorogusker, J., filed Oct. 31, 2016. [cited by applicant]
Non-Final Office Action mailed Aug. 13, 2018, for U.S. Appl. No. 14/984,931, of Dorogusker, J., filed Dec. 30, 2015. [cited by applicant]
Final Office Action mailed Dec. 14, 2018, for U.S. Appl. No. 14/984,931, of Dorogusker, J., filed Dec. 30, 2015. [cited by applicant]
Final Office Action mailed Mar. 7, 2019, for U.S. Appl. No. 15/339,744, of Dorogusker, J., filed Oct. 31, 2016. [cited by applicant]
Advisory Action mailed Mar. 21, 2019, for U.S. Appl. No. 14/984,931, of Dorogusker, J., filed Dec. 30, 2015. [cited by applicant]
Non-Final Office Action mailed Jun. 3, 2019, for U.S. Appl. No. 14/984,931, of Dorogusker, J., filed Dec. 30, 2015. [cited by applicant]
Non-Final Office Action mailed Jun. 27, 2019, for U.S. Appl. No. 15/675,099, of Grassadonia, B., filed Aug. 11, 2017. [cited by applicant]
Final Office Action mailed Sep. 9, 2019, for U.S. Appl. No. 14/984,931, of Dorogusker, J., filed Dec. 30, 2015. [cited by applicant]
Non-Final Office Action mailed Jan. 8, 2020, for U.S. Appl. No. 15/339,744, of Dorogusker, J., filed Oct. 31, 2016. [cited by applicant]
Non-Final Office Action mailed Jan. 16, 2020, for U.S. Appl. No. 14/984,931, of Dorogusker, J., filed Dec. 30, 2015. [cited by applicant]
Non-Final Office Action mailed Feb. 14, 2020, for U.S. Appl. No. 15/675,099, of Grassadonia, B., et al., filed Aug. 11, 2017. [cited by applicant]
Final Office Action mailed Jul. 24, 2020, for U.S. Appl. No. 15/339,744, of Dorogusker, J., filed Oct. 31, 2016. [cited by applicant]
Final Office Action mailed Aug. 19, 2020, for U.S. Appl. No. 14/984,931, of Dorogusker, J., filed Dec. 30, 2015. [cited by applicant]
Final Office Action mailed Aug. 21, 2020, for U.S. Appl. No. 15/675,099, of Grassadonia, B., et al., filed Aug. 11, 2017. [cited by applicant]
Advisory Action mailed Oct. 9, 2020, for U.S. Appl. No. 15/339,744, of Dorogusker, J., filed Oct. 31, 2016. [cited by applicant]
Notice of Allowance mailed Oct. 25, 2021, for U.S. Appl. No. 15/339,744, of Dorogusker, J., filed Oct. 31, 2016. [cited by applicant]
Advisory Action mailed Dec. 17, 2020, for U.S. Appl. No. 15/675,099, of Grassadonia, B., et al., filed Aug. 11, 2017. [cited by applicant]
Non-Final Action mailed May 13, 2021, for U.S. Appl. No. 15/675,099, of Grassadonia, B., et al., filed Aug. 11, 2017. [cited by applicant]
Final Action mailed Aug. 30, 2021, for U.S. Appl. No. 15/675,099, of Grassadonia, B., et al., filed Aug. 11, 2017. [cited by applicant]
Advisory Action mailed Nov. 17, 2021, for U.S. Appl. No. 15/675,099, of Grassadonia, B., et al., filed Aug. 11, 2017. [cited by applicant]
Notice of Allowance mailed Feb. 2, 2022, for U.S. Appl. No. 15/675,099, of Grassadonia, B., et al., filed Aug. 11, 2017. [cited by applicant]