# US 2019/0378099 A1 · Communication device interface for monetary transfers through a displayable contact list

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0378099 A1
- Document ID: US20190378099A1
- Status: Published application
- Kind: A1
- Application number: 16/505,616
- Filed: 2019-07-08
- Published: 2019-12-12
- Earliest claimed: 2013-10-09
- Assignees: Paypal, Inc.
- Applicants: Paypal, Inc.
- Inventors: Hyunju Lee
- Web page: https://patentgrep.com/patent/US20190378099A1

## CPC

- G06Q 20/10: specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q 10/40: Business processes related to social networking or social networking services
- G06Q 20/322: {Aspects of commerce using mobile devices [M-devices]}
- G06Q 20/3278: {RFID or NFC payments by means of M-devices}
- G06Q 20/363: {with the personal data of a user}
- G06Q 20/384: {using social networks}
- G06Q 20/386: {using messaging services or messaging apps (using mobile network messaging services for payment, e.g. SMS G06Q20/3255)}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

There is provided systems and method for a communication device interface for monetary transfers through a displayable contact list. A user may import contacts from a contact list application, a social networking service, a user account with a payment provider, and/or another contact source into a communication device, such as a mobile phone. The mobile phone may then execute a monetary transfer module that allows the user to transmit requests for monetary transfers with the contacts. When the user selects a contact in a contact list, the module may retrieve payment account information and initiate a monetary transfer with the selected contact. The monetary transfer may correspond to receiving money or sending money to the contact. Additionally, the user may communicate messages with the request as well as a monetary amount. In order to facilitate completion of the monetary transfer, a payment provider may be utilized.

## Claims

### Claim at position 1

1-7. (canceled)

### Claim 8

A non-transitory machine-readable medium having instructions stored thereon, the instructions executable to cause performance of operations comprising:
accessing, by a transfer application executing on a user device of a first user, contact information of a contact application of the user device, wherein the contact information is accessed from an application programming interface (API) of the contact application;
determining, by the transfer application using the contact information, that a second user has a second user payment account with a transaction processor;
causing to be displayed, a selectable icon for an option in a contact list interface of the contact application, the option for initiating a transfer from a first account of the first user to a second account of the second user using the transfer application, the option displayed with a second user contact information for the second user in the contact list interface, the option identifying the second user as using the transaction processor for transfers;
in response to receiving selection of the icon by the first user, populating a transfer interface in the transfer application with the second user contact information; and
in response to receiving a request to process the transfer, communicating a transfer form to the transaction processor for processing the transfer.

### Claim 9 (depends on 8)

The non-transitory machine-readable medium of claim 8, wherein the operations further comprise determining, by the transfer application, identifier for the second user in the contact information, wherein said determining that the second user has the second user payment account is performed with a transfer processor service of the transaction processor using the identifier.

### Claim 10 (depends on 8)

The non-transitory machine-readable medium of claim 8, wherein the operations further comprise receiving, by the transfer application from the first user, a request to view the contact list interface for the contact application, wherein the contact list interface comprising the contact information is displayed within a graphical user interface (GUI) for the user device.

### Claim 11 (depends on 8)

The non-transitory machine-readable medium of claim 8, wherein the operations further comprise displaying, by the transfer application in the contact list interface for the contact application through the API, a first icon corresponding to the second user payment account and a second icon designating a first verification status for the second user payment account, wherein the first icon identifies the second user as a user of the transaction processor.

### Claim 12 (depends on 11)

The non-transitory machine-readable medium of claim 11, wherein the first verification status is determined by the transaction processor based on a past transaction history of the second user with the transaction processor and indicates that the second user payment account has been authenticated with the transaction processor.

### Claim 13 (depends on 8)

The non-transitory machine-readable medium of claim 8, wherein the operations further comprise receiving an input for a payment transfer from the first user via the transfer interface within the contact application.

### Claim 14 (depends on 8)

The non-transitory machine-readable medium of claim 8, wherein the contact information comprises an account identifier for the first user that uniquely identifies the first user and verifies that the first user is requesting the transfer.

### Claim 15 (depends on 8)

The non-transitory machine-readable medium of claim 8, wherein the contact information is received through a social networking application associated.

### Claim 16 (depends on 8)

The non-transitory machine-readable medium of claim 8, wherein the contact list interface comprising the contact information is displayed within a graphical user interface (GUI) for the user device.

### Claim 17

A method for initiating transactions from contact lists, the method comprising:
instructions executable to cause performance of operations comprising:
accessing, by a transfer application executing on a user device, contact information of a contact application of the user device of a first user, wherein the contact information is accessed from an application programming interface (API) of the contact application;
determining, by the transfer application using the contact information, that a second user has a second user payment account with a transaction processor;
causing to be displayed, a selectable icon for an option in a contact list interface of the contact application, the option for initiating a transfer from a first account of the first user to a second account of the second user using the transfer application, the option displayed with a second user contact information for the second user in the contact list interface, the option identifying the second user as using the transaction processor for transfers;
in response to receiving selection of the icon by the first user, populating a transfer interface in the transfer application with the second user contact information; and
in response to receiving a request to process the transfer, communicating a transfer form to the transaction processor for processing the transfer.

### Claim 18 (depends on 17)

The method of claim 17, further comprising receiving, by the transfer application from the first user, a request to view the contact list interface for the contact application, wherein the contact list interface comprising the contact information is displayed within a graphical user interface (GUI) for the user device.

### Claim 19 (depends on 17)

The method of claim 17, further comprising displaying, by the transfer application in the contact list interface for the contact application through the API, a first icon corresponding to the second user payment account and a second icon designating a first verification status for the second user payment account, wherein the first icon identifies the second user as a user of the transaction processor.

### Claim 20 (depends on 19)

The method of claim 19, wherein the first verification status is determined by the transaction processor based on a past transaction history of the second user with the transaction processor and indicates that the second user payment account has been authenticated with the transaction processor.

### Claim 21 (depends on 17)

The method of claim 17, wherein the operations further comprise receiving an input for the transfer from the first user via the transfer interface within the contact application.

### Claim 22 (depends on 17)

The method of claim 17, wherein the contact information comprises an account identifier for the first user that uniquely identifies the first user and verifies that the first user is requesting the transfer.

### Claim 23

A user device comprising:
a non-transitory memory storing instructions; and
a processor configured to execute the instructions to cause the user device to:
access, by a transfer application executing on the user device of a first user, contact information of a contact application of the user device, wherein the contact information is accessed from an application programming interface (API) of the contact application;
determine, by the transfer application using the contact information, that a second user has a second user payment account with a transaction processor;
causing to display, a selectable icon for an option in a contact list interface of the contact application, the option for initiating a transfer from a first account of the first user to a second account of the second user using the transfer application, the option displayed with a second user contact information for the second user in the contact list interface, the option identifying the second user as using the transaction processor for transfers;
in response to receiving a selection of the icon by the first user, populate a transfer interface in the transfer application with the second user contact information; and
in response to receiving a request to process the transfer, communicate a transfer form to the transaction processor for processing the transfer.

### Claim 24 (depends on 23)

The user device of claim 23, wherein executing the instructions further causes the user device to receive, by the transfer application from the first user, a request to view the contact list interface for the contact application, wherein the contact list interface comprising the contact information is displayed within a graphical user interface (GUI) for the user device.

### Claim 25 (depends on 23)

The user device of claim 23, wherein executing the instructions further causes the user device to display, by the transfer application in the contact list interface for the contact application through the API, a first icon corresponding to the second user payment account and a second icon designating a first verification status for the second user payment account, wherein the first icon identifies the second user as a user of the transaction processor.

### Claim 26 (depends on 25)

The user device of claim 25, wherein the first verification status is determined by the transaction processor based on a past transaction history of the second user with the transaction processor and indicates that the second user payment account has been authenticated with the transaction processor.

### Claim 27 (depends on 23)

The user device of claim 23, wherein executing the instructions further causes the user device to receive an input for the transfer from the first user via the transfer interface within the contact application.
