IP Library Granted Patent US 12,541,754
Granted Patent B2
US 12,541,754 · App. 18/646,180 · Granted Feb 3, 2026

Context-aware peer-to-peer transfers of items

Inventors: Aaron Y. Ng (San Francisco, CA); Ayokunle Omojola (San Francisco, CA); Jesse Wilson (Waterloo, CA)
Assignee: Block, Inc.
G06Q20/327G06Q20/102G06Q20/223G06Q20/29G06Q20/322
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,541,754
App. No.
18/646,180
Granted
Feb 3, 2026
Kind
B2
Abstract

A payment service system may receive a request to complete a first purchase of at least one ticket for an event, wherein the at least one ticket is offered for sale by an event organizer to a customer. The payment service system may send the at least one ticket to the application on a first mobile device of the customer, receive a request via the application to transfer ownership of the at least one ticket to a new customer, and receive an indication, from a corresponding application on a second mobile device of the new customer, to acquire the ownership of the at least one ticket. Based on the indication, the payment service system may process an electronic payment for the transfer of the ownership and transfer the at least one ticket from the application on the first mobile device to the corresponding application on the second mobile device.

Claims (74)

1 . A method comprising:

receiving a request, at a payment service system, to complete a first purchase of at least one ticket for an event, wherein

the at least one ticket is offered for sale by an event organizer to a customer, and

the payment service system is communicatively coupled to a merchant application executed on a computing device of the event organizer and an application executed on a first mobile device of the customer;

sending, by the payment service system, the at least one ticket to the application on the first mobile device of the customer;

receiving, at the payment service system, a request via the application on the first mobile device to transfer ownership of the at least one ticket to a new customer;

receiving an indication, at the payment service system from a corresponding application on a second mobile device of the new customer, to acquire the ownership of the at least one ticket; and

processing, at the payment service system, an electronic payment for the transfer of the ownership using a first account of the customer and a second account of the new customer at the payment service system; and

transferring, by the payment service system, the at least one ticket from the application on the first mobile device to the corresponding application on the second mobile device.

2 . The method of claim 1 , wherein the first account and the second account are pre-registered with the payment service system.

3 . The method of claim 1 , wherein

the at least one ticket includes two or more tickets,

the indication received from the second mobile device is for acquiring the ownership of a first one of the two or more tickets, and

a second indication is received from a third mobile device of a second new customer to acquire a second one of the two or more tickets.

4 . The method of claim 1 , further comprising:

responsive to completion of transferring the at least one ticket, transmitting, by the payment service system, a confirmation of the completion to the merchant application and the application executed on the first mobile device of the customer.

5 . The method of claim 1 , wherein

the at least one ticket includes two tickets having different values, and

separate electronic payments are processed for each of the two tickets.

6 . The method of claim 5 , wherein the request identifies two different customers each receiving one of the two tickets.

7 . The method of claim 6 , further comprising:

determining that at least one of the two different customers does not have an account with the payment service system;

sending a registration request to a corresponding mobile device of the at least one of the two different customers that does not have an account with the payment service system;

receiving a response to the registration request from the corresponding mobile device of the at least one of the two different customers to register the account for the at least one of the two different customers; and

processing a corresponding payment for one of the two tickets using the account registered for the at least one of the two different customers.

8 . A payment service system comprising:

one or more memories having computer-readable instructions stored therein; and

one or more processors configured to execute the computer-readable instructions to:

receive a request to complete a first purchase of at least one ticket for an event, wherein the at least one ticket is offered for sale by an event organizer to a customer, and

the payment service system is communicatively coupled to a merchant application executed on a computing device of the event organizer and an application executed on a first mobile device of the customer;

send the at least one ticket to the application on the first mobile device of the customer;

receive a request via the application on the first mobile device to transfer ownership of the at least one ticket to a new customer;

receive an indication, from a corresponding application on a second mobile device of the new customer, to acquire the ownership of the at least one ticket; and

process an electronic payment for the transfer of the ownership using a first account of the customer and a second account of the new customer at the payment service system; and

transfer the at least one ticket from the application on the first mobile device to the corresponding application on the second mobile device.

9 . The payment service system of claim 8 , wherein the first account and the second account are pre-registered with the payment service system.

10 . The payment service system of claim 8 , wherein

the at least one ticket includes two or more tickets,

the indication received from the second mobile device is for acquiring the ownership of a first one of the two or more tickets, and

a second indication is received from a third mobile device of a second new customer to acquire a second one of the two or more tickets.

11 . The payment service system of claim 8 , wherein the one or more processors are further configured to execute the computer-readable instructions to:

transmit, responsive to completion of transferring the at least one ticket, a confirmation of the completion to the merchant application and the application executed on the first mobile device of the customer.

12 . The payment service system of claim 8 , wherein

the at least one ticket includes two tickets having different values, and

separate electronic payments are processed for each of the two tickets.

13 . The payment service system of claim 12 , wherein the request identifies two different customers each receiving one of the two tickets.

14 . The payment service system of claim 13 , wherein the one or more processors are further configured to execute the computer-readable instructions to:

determine that at least one of the two different customers does not have an account with the payment service system;

send a registration request to a corresponding mobile device of the at least one of the two different customers that does not have an account with the payment service system;

receive a response to the registration request from the corresponding mobile device of the at least one of the two different customers to register the account for the at least one of the two different customers; and

process a corresponding payment for one of the two tickets using the account registered for the at least one of the two different customers.

15 . One or more non-transitory computer-readable media comprising computer-readable instructions, which when executed by one or more processors of a payment service system, cause the payment service system to:

receive a request to complete a first purchase of at least one ticket for an event, wherein the at least one ticket is offered for sale by an event organizer to a customer, and

the payment service system is communicatively coupled to a merchant application executed on a computing device of the event organizer and an application executed on a first mobile device of the customer;

send the at least one ticket to the application on the first mobile device of the customer;

receive a request via the application on the first mobile device to transfer ownership of the at least one ticket to a new customer;

receive an indication, from a corresponding application on a second mobile device of the new customer, to acquire the ownership of the at least one ticket; and

process an electronic payment for the transfer of the ownership using a first account of the customer and a second account of the new customer at the payment service system; and

transfer the at least one ticket from the application on the first mobile device to the corresponding application on the second mobile device.

16 . The one or more non-transitory computer-readable media of claim 15 , wherein

the at least one ticket includes two or more tickets,

the indication received from the second mobile device is for acquiring the ownership of a first one of the two or more tickets, and

a second indication is received from a third mobile device of a second new customer to acquire a second one of the two or more tickets.

17 . The one or more non-transitory computer-readable media of claim 15 , wherein execution of the computer-readable instructions, further cause the payment service system to:

transmit, responsive to completion of transferring the at least one ticket, a confirmation of the completion to the merchant application and the application executed on the first mobile device of the customer.

18 . The one or more non-transitory computer-readable media of claim 15 , wherein

the at least one ticket includes two tickets having different values, and

separate electronic payments are processed for each of the two tickets.

19 . The one or more non-transitory computer-readable media of claim 18 , wherein the request identifies two different customers each receiving one of the two tickets.

20 . The one or more non-transitory computer-readable media of claim 19 , wherein execution of the computer-readable instructions, further cause the payment service system to:

determine that at least one of the two different customers does not have an account with the payment service system;

send a registration request to a corresponding mobile device of the at least one of the two different customers that does not have an account with the payment service system;

receive a response to the registration request from the corresponding mobile device of the at least one of the two different customers to register the account for the at least one of the two different customers; and

process a corresponding payment for one of the two tickets using the account registered for the at least one of the two different customers.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 26, 2024
From: NG, AARON Y.; OMOJOLA, AYOKUNLE; WILSON, JESSE
To: BLOCK, INC.
Reel/Frame 067232/0812 →
Continuity (4)
Continuation 18190020 · Mar 24, 2023
Continuation 17512618 · Oct 27, 2021
Continuation In Part 14664781 · Mar 20, 2015
Related Publication 20240273507A1 · Aug 15, 2024
References Cited (82)
US 5093787A · Simmons · 1992 [cited by applicant]
US 5687968A · Tarantino · 1997 [cited by examiner]
US 6098051A · Lupien · 2000 [cited by examiner]
US 6272474B1 · Garcia · 2001 [cited by examiner]
US 6278982B1 · Korhammer · 2001 [cited by examiner]
US 6356911B1 · Shibuya · 2002 [cited by examiner]
US 6721715B2 · Nemzow · 2004 [cited by examiner]
US 7062361B1 · Lane · 2006 [cited by examiner]
US 7130789B2 · Glodjo · 2006 [cited by examiner]
US 7182253B1 · Long · 2007 [cited by applicant]
US 7315840B1 · Keith · 2008 [cited by examiner]
US 7392213B2 · Merkoulovitch · 2008 [cited by examiner]
US 7693784B2 · Rivest et al. · 2010 [cited by applicant]
US 7792717B1 · Hankins et al. · 2010 [cited by applicant]
US 7822655B1 · LaQuinta · 2010 [cited by examiner]
US 7831494B2 · Sloan · 2010 [cited by examiner]
US 7865435B1 · Medina, III · 2011 [cited by applicant]
US 7958050B2 · Finch · 2011 [cited by applicant]
US 8073763B1 · Merrin · 2011 [cited by examiner]
US 8126794B2 · Lange · 2012 [cited by examiner]
US 8359260B2 · Merrin · 2013 [cited by examiner]
US 8417618B2 · Milne · 2013 [cited by examiner]
US 8755943B2 · Wenzel · 2014 [cited by examiner]
US 9665858B1 · Kumar · 2017 [cited by applicant]
US 11636462B2 · Ng et al. · 2023 [cited by applicant]
US 20020147671A1 · Sloan · 2002 [cited by examiner]
US 20020147675A1 · Das · 2002 [cited by examiner]
US 20020194099A1 · Weiss · 2002 [cited by examiner]
US 20030182224A1 · Horrigan · 2003 [cited by examiner]
US 20040024692A1 · Turbeville · 2004 [cited by examiner]
US 20050021447A1 · Lawrence · 2005 [cited by examiner]
US 20050080703A1 · Chiesa · 2005 [cited by examiner]
US 20050124408A1 · Vlazny · 2005 [cited by examiner]
US 20060085321A1 · Staib · 2006 [cited by examiner]
US 20060293983A1 · Rosenblatt et al. · 2006 [cited by applicant]
US 20070106558A1 · Mitchell et al. · 2007 [cited by applicant]
US 20080015871A1 · Eder · 2008 [cited by examiner]
US 20090106140A1 · De La Motte · 2009 [cited by examiner]
US 20090198528A1 · Kahn · 2009 [cited by applicant]
US 20090307149A1 · Markov · 2009 [cited by examiner]
US 20090327123A1 · Wolfson · 2009 [cited by applicant]
US 20100088210A1 · Gardner · 2010 [cited by examiner]
US 20100306103A1 · Hankins et al. · 2010 [cited by applicant]
US 20110119166A1 · Steinberg · 2011 [cited by examiner]
US 20110125652A1 · Sato · 2011 [cited by examiner]
US 20110145049A1 · Hertel et al. · 2011 [cited by applicant]
US 20110191241A1 · Blain et al. · 2011 [cited by applicant]
US 20120078784A1 · Anthony et al. · 2012 [cited by applicant]
US 20120158443A1 · Kim · 2012 [cited by applicant]
US 20120166332A1 · Naaman · 2012 [cited by applicant]
US 20120239453A1 · Osogami · 2012 [cited by examiner]
US 20120323753A1 · Norman · 2012 [cited by examiner]
US 20130080351A1 · Schneider · 2013 [cited by examiner]
US 20130185187A1 · Vasinkevich · 2013 [cited by examiner]
US 20130275334A1 · Andersen · 2013 [cited by examiner]
US 20130317893A1 · Nelson et al. · 2013 [cited by applicant]
US 20140156517A1 · Argue · 2014 [cited by examiner]
US 20140201110A1 · Sato · 2014 [cited by examiner]
US 20140297533A1 · Mittal · 2014 [cited by applicant]
US 20140351118A1 · Zhao · 2014 [cited by applicant]
US 20150058261A1 · Parikh · 2015 [cited by examiner]
US 20150127392A1 · Shivakumar et al. · 2015 [cited by applicant]
US 20150170132A1 · Patel · 2015 [cited by applicant]
US 20150287006A1 · Hunter et al. · 2015 [cited by applicant]
US 20150310461A1 · Lee · 2015 [cited by examiner]
US 20150363866A1 · Depew · 2015 [cited by examiner]
US 20160055474A1 · Syed · 2016 [cited by applicant]
US 20160117784A1 · Hwang · 2016 [cited by examiner]
US 20160148164A1 · Luk · 2016 [cited by examiner]
US 20160196521A1 · Wada · 2016 [cited by examiner]
US 20180074523A1 · Cantrell · 2018 [cited by examiner]
US 20180285970A1 · Snow · 2018 [cited by examiner]
US 20190132350A1 · Smith · 2019 [cited by examiner]
US 20190311443A1 · Blades · 2019 [cited by examiner]
US 20190340689A1 · Gordon, III · 2019 [cited by examiner]
US 20200118068A1 · Turetsky · 2020 [cited by examiner]
US 20200151709A1 · Bryan · 2020 [cited by examiner]
US 20200193752A1 · Burris · 2020 [cited by examiner]
US 20200302468A1 · Karuppan · 2020 [cited by examiner]
US 20210142302A1 · Anderson · 2021 [cited by examiner]
US 20220261925A1 · Kurczodyna · 2022 [cited by examiner]
US 20230237462A1 · Ng et al. · 2023 [cited by applicant]