US-20260127572-A1 - CONTEXT-AWARE PEER-TO-PEER TRANSFERS OF ITEMS

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.

Inventors

• Aaron Y. Ng
• Ayokunle Omojola
• Jesse Wilson

Assignees

• BLOCK, INC.

Dates

Publication Date

20260507

Application Date

20251230

Claims (1)

1. 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.

Description

PRIORITY This application is a continuation under 35 U.S.C. § 120 of U.S. patent application Ser. No. 18/646,180, entitled “CONTEXT-AWARE PEER-TO-PEER TRANSFERS OF ITEMS”, filed Mar. 25, 2024, which is a continuation under 35 U.S.C. § 120 of U.S. patent application Ser. No. 18/190,020, entitled “CONTEXT-AWARE PEER-TO-PEER TRANSFERS OF ITEMS”, filed Mar. 24, 2023, now U.S. Pat. No. 11,989,718, which is a continuation of U.S. patent application Ser. No. 17/512,618, entitled “CONTEXT-AWARE PEER-TO-PEER TRANSFERS OF ITEMS”, filed Oct. 27, 2021, now U.S. Pat. No. 11,636,462, which is a continuation-in-part of U.S. patent application Ser. No. 14/664,781, entitled “MERCHANT APPLICATION PROGRAMMING INTERFACE FOR TRANSFERRING PURCHASE UNITS”, filed Mar. 20, 2015, the contents of which are incorporated herein by reference in their entireties. TECHNICAL FIELD This disclosure generally relates to databases, data management, and discovery within network environments, and in particular relates to hardware and software for transfer systems. BACKGROUND Peer-to-peer transfers using transfer systems enable transfers of items between user accounts, thereby facilitating the transfer of ownership of such items between users. In conventional transfer systems for transferring items from one user to another user (i.e., “peers”), the transferring user enters a user identifier for the receiving user such as a username, phone number, or email address into a user interface of the transfer system. To initiate the transfer of the item from the transferring user to the correct receiving user, the transferring user first obtains the correct user identifier of the receiving user and then carefully enters the user identifier to the user interface. The transfer system can disassociate the item from the transferring user and associate the item with the receiving user, based on the provided user identifier. This process can be time consuming, prone to user error, and require significant computational resources in presenting appropriate user interfaces to share relevant user identifiers and receive input from transferring users. A transferring user who enters an incorrect user identifier may request the item back from the incorrect recipient, further using computational resources and taking further time, but return is not guaranteed. BRIEF DESCRIPTION OF THE DRAWINGS Application programming interface (API) based technologies for integrating merchant applications and/or systems with a payment service system to enable split bill payment and purchase transfer introduced here may be better understood by referring to the following Detailed Description in conjunction with the accompanying drawings, in which like reference numerals indicate identical or functionally similar elements. FIG. 1 is a block diagram illustrating a network-based environment in which the disclosed technologies can operate. FIG. 2 is a user interface diagram illustrating an example checkout interface of a merchant application executing on a merchant system. FIG. 3 is a block diagram illustrating an example user interface for splitting a bill among bill payers. FIG. 4A is a block diagram illustrating an example split bill payment flow involving a merchant system, multiple client devices and a payment service system in accordance with a first embodiment. FIG. 4B is a block diagram illustrating an example split bill payment flow involving a merchant system, multiple client devices and a payment service system in accordance with a second embodiment. FIG. 5A is a user interface diagram illustrating an example checkout interface of a merchant including an option to transfer purchase units. FIG. 5B is a user interface diagram illustrating an example interface of a payment application associated with a payment service system for transfer of purchase units to another. FIG. 6 is a block diagram illustrating a purchase transfer flow involving a merchant system, multiple client devices and a payment service system in accordance with a third embodiment. FIG. 7 is a block diagram illustrating example components of a merchant system implementing the disclosed technologies. FIG. 8 is a block diagram illustrating example components of a client device implementing the disclosed technologies. FIG. 9 is a block diagram illustrating example components of a payment service system implementing the disclosed technologies. FIG. 10 is a logic flow diagram illustrating an example method of requesting and processing a split bill payment. FIG. 11 is a logic flow diagram illustrating an example method of transferring purchase units. FIG. 12 is a block diagram of an example of a computing system in which at least some operations related to the disclosed technologies can be implemented. DETAILED DESCRIPTION An application programming interface (API) is described for integrating merchant applications and/or systems with a payment service system to enable split bill payment and purchase transfer. In some embodi