Back to results
US 9,792,600 B1Granted
Payment without account creation
AssigneeSquare, Inc.
InventorBrian Grassadonia
Life of this patent
Estimating the term…
Abstract
Technology is disclosed for a convenient money transfer without requiring any account login and/or creation activities. The disclosed technology enables a sender to transfer a specified amount of currency to one or more recipients through a payment application. In response to a request from the sender, the technology provides a user interface to collect a numerical value corresponding to the specified amount of currency, accesses a list of contacts in a database of the sender's mobile device, and then provides the list of contacts to the sender. The technology enables the sender to manually select recipients from the provided list of contacts and can accordingly initiate a payment process based on statuses of selected recipients.
Claims30
A computer-implemented method for providing a user interface to facilitate implementing a payment application, the method comprising:
- identifying, by the payment application executing as a background process and without presenting a payment application user interface, a payment request by monitoring and identifying a payment identifier in text characters of a message in a conversation between the sender and a recipient;
- upon identifying the payment request, presenting, by the payment application, at the mobile device of the sender, the payment application user interface to enable the sender to input a numerical value;
- while presenting the payment application user interface, accessing, by the payment application, a list of contacts previously stored in a database of the mobile device, wherein accessing the list of contacts includes locating the list of contacts by a contact-list search module, identifying a type of the list of contacts by a contact-list identification module, and analyzing the list of contacts by a contact-list analysis module;
- presenting, by the payment application, the list of contacts to the sender through the payment application user interface, wherein a first contact in the list of contacts is presented to the sender in a first section of the payment application user interface and a second contact is presented to the sender in a second section of the payment application user interface, and wherein the first contact is associated with a first electronic device at which the payment application is installed, and wherein the second contact is associated with a second electronic device at which the payment application is not installed, and wherein the first section is positioned adjacent to the second section, and wherein the numerical value inputted by the sender is presented in the first section for review by the sender;
- receiving, by the payment application, a portion of the list of contacts selected by the sender through the payment application user interface, so as to identify at least one recipient;
- in an event that the recipient has a recipient service account associated with the payment application, presenting, by the payment application, in the payment application user interface, a first indication associated with information from the recipient service account;
- in an event that the recipient does not have the recipient service account associated with the payment application, presenting, by the payment application, in the payment application user interface, a second indication associated with a first linking invitation requesting the recipient to register a new service account associated with the payment application, wherein the first linking invitation is generated by a first link-generation module;
- and
- in an event that the sender does not have a sender service account associated with the payment application, presenting, by the payment application, in the payment application user interface, a third indication associated with a second linking invitation requesting the sender to register a new service account associated with the payment application, wherein the second linking invitation is generated by a second link-generation module.
6 more elements
A computer-implemented method for proving a user interface to facilitate implementing a payment application, the method comprising:
- in response to monitoring and identifying, by the payment application executing as a background process and without presenting a payment application user interface, a payment identifier in text of a message between a sender and a recipient, presenting, by the payment application, at a mobile device of the sender, the payment application user interface to enable the sender to input a numerical value;
- receiving, by the payment application, from the payment application user interface, a request to initiate the payment application;
- in response to receiving the request, enabling the sender to access, through the payment application user interface, a list of contacts previously stored in a database of the mobile device, wherein accessing the list of contacts includes locating the list of contacts by a contact-list search module, identifying a type of the list of contacts by a contact-list identification module, and analyzing the list of contacts by a contact-list analysis module;
- providing, by the payment application, the list of contacts to the sender through the payment application user interface, wherein a first contact in the list of contacts is presented to the sender in a first section of the payment application user interface and a second contact is presented to the sender in a second section of the payment application user interface, and wherein the first contact is associated with a first electronic device at which the payment application is installed, and wherein the second contact is associated with a second electronic device at which the payment application is not installed, and wherein the first section is positioned adjacent to the second section, and wherein the numerical value inputted by the sender is presented in the first section for review by the sender;
- and
- receiving, by the payment application, a portion of the list of contacts selected by the sender through the payment application user interface, so as to identify at least one recipient.
3 more elements
A system, comprising:
- a client computing device having:
- a processor and memory;
- a client database configured to store a set of contact information, wherein the set of contact information includes multiple contacts and multiple corresponding email addresses;
- an identifying component configured to monitor and identify, a request to initiate a payment application, without presenting a user interface associated with a payment application;
- a display component configured to provide a user interface associated with the payment application to enable the sender to input a numerical value;
- and
- a retrieving component configured to retrieve a list of contacts by accessing the set of contact information stored in the client database, wherein accessing the set of contacts includes locating the set of contacts by a contact-list search module, identifying a type of the list of contacts by a contact-list identification module, and analyzing the set of contacts by a contact-list analysis module;
- wherein the list of contacts is provided to the sender through the user interface associated with the payment application, wherein a first contact in the list of contacts is presented to the sender in a first section of the user interface associated with the payment application and a second contact is presented to the sender in a second section of the user interface associated with the payment application, and wherein the first contact is associated with a first electronic device at which the payment application is installed, and wherein the second contact is associated with a second electronic device at which the payment application is not installed, and wherein the first section is positioned adjacent to the second section, and wherein the numerical value inputted by the sender is presented in the first section for review by the sender;
- and
- wherein a portion of the list of contacts is selected by the sender, through the user interface associated with the payment application.
7 more elements
Dependencies are inferred from the claim text.