IP Library Granted Patent US 10,949,829
Granted Patent B2
US 10,949,829 · App. 15/851,423 · Granted Mar 16, 2021

Processing a mobile payload

Inventors: Alan Paulin (San Francisco, CA); Peter Westen (San Francisco, CA); Shawn Welch (San Francisco, CA); Daniel Federman (San Francisco, CA); Michael Gershunovsky (San Francisco, CA); Ayokunle Omojola (San Francisco, CA)
Assignee: Square, Inc.
G06Q20/3223G06Q20/02G06Q20/102G06Q20/223G06Q20/322G06Q20/325G06Q20/3221G06Q20/3226G06Q20/3255G06Q20/3274G06Q20/3276G06Q40/12H04L51/04H04L51/046H04L51/10
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 10,949,829
App. No.
15/851,423
Granted
Mar 16, 2021
Kind
B2
Abstract

Disclosed herein are systems and methods for processing a payment request. A mobile device associated with a payor may generate a user interface having two screen portions. The first screen portion may be configured to display received and sent messages and further configured to receive a command to transmit a message. The second screen portion may be configured to access a third-party application and configured to populate a new message with a payload. The mobile device may receive an inputted amount in the second screen portion representing the payment amount. The mobile device may transmit a request including the payor's identification and the payment amount to a third-party Payment Processing System (PPS) and receive a payload from the PPS. The mobile device may populate and transmit a message to the recipient that contains the payload.

Claims (39)

1. A computer-implemented method comprising:

receiving, by a messaging server, from a first messaging application executing on a first mobile device operated by a payor, a request to transmit a payment message,

wherein the payment message comprises an identifier of a second mobile device operated by a payee and further comprises a payload containing a hyperlink and a token string comprising alphanumerical values,

wherein the payload does not comprise the identifier,

wherein a payment processing server generates the payload after receiving a payment request from the first messaging application executing on the first mobile device and transmits the payload to a payment application executing on the first mobile device that then transmits the payload to the first messaging application, wherein the first messaging application inserts the payload into a displayed message field on the first mobile device,

wherein the hyperlink comprises a uniform resource locator that is configured, upon an activation of the hyperlink, to instruct the payment processing server to update a balance value of funds associated with an account data record of the payee; and

transmitting, by the messaging server, the payment message to a second messaging application executing on the second mobile device, wherein the second messaging application inserts the payment message into a displayed message field on the second mobile device,

wherein the messaging server hosts a messaging service compatible with the first messaging application and the second messaging application.

2. The computer-implemented method according to claim 1 , wherein the token string is embedded into the payload and not displayed.

3. The computer-implemented method according to claim 1 , wherein the payload is configured to be activated based on the payee operating the second mobile device interacting with the payload.

4. The computer-implemented method according to claim 3 , wherein interacting with the payload comprises the payee engaging with the hyperlink.

5. The computer-implemented method according to claim 3 , further comprising:

transmitting, by the messaging server, a notification to the first mobile device that the payload has been activated.

6. The computer-implemented method according to claim 1 , wherein the request to transmit the payment message is received via the payor operating the first mobile device inputting the request in the first messaging application executing on the first mobile device.

7. The computer-implemented method according to claim 1 , wherein upon receiving the request to transmit the payment message, the payment processing server generates a graphical user interface component configured to receive payment data.

8. The computer-implemented method according to claim 7 , wherein the graphical user interface component is configured to be displayed while the first mobile device is displaying the first messaging application.

9. The computer-implemented method according to claim 7 , wherein the graphical user interface component comprises an interactive input element configured to receive a payment amount.

10. The computer-implemented method according to claim 1 , wherein the payment message further comprises a text input received from the first mobile device.

11. The computer-implemented method according to claim 1 , wherein the first messaging application comprises an interactive input element configured to generate the request to transmit a payment message; and

wherein the messaging server receives the request to transmit the payment message after the first messaging application has received an interaction of the payor with the interactive input element.

12. A computer system comprising:

a first mobile device operated by a payer and executing a first messaging application and a payment application;

a second mobile device operated by a payee and executing a second messaging application and the payment application;

a payment processing server coupled to the first mobile device via the payment application and the first messaging application and to the second mobile device via the payment application;

a messaging server coupled with the first mobile device and the second mobile device via the first messaging application and the second messaging application, wherein the messaging server is configured to:

receive, from the first messaging application executing on the first mobile device operated by a payor, a request to transmit a payment message, wherein the payment message comprises an identifier of a second mobile device operated by a payee and further comprises a payload containing a hyperlink and a token string comprising alphanumerical values, wherein the payload does not comprise the identifier; and

transmit the payment message to the second messaging application executing on the second mobile device, wherein the second messaging application inserts the payment message into a displayed message field on the second mobile device, wherein the messaging server hosts a messaging service compatible with the first messaging application and the second messaging application, and wherein the payload is received from the payment processing server; and

wherein the payment processing server is configured to:

generate the payload after receiving a payment request from the first messaging application executing on the first mobile device;

and transmit the payload to the payment application executing on the first mobile device that then transmits the payload to the first messaging application, wherein the first messaging application inserts the payload into a displayed message field on the first mobile device, wherein the hyperlink comprises a uniform resource locator that is configured, upon an activation of the hyperlink, to instruct the payment processing server to update a balance value of funds associated with an account data record of the payee.

13. The computer system of claim 12 , wherein the token string is embedded into the payload and not displayed.

14. The computer system of claim 12 , wherein the payload is configured to be activated based on the payee operating the second mobile device interacting with the payload.

15. The computer system of claim 14 , wherein interacting with the payload comprises the payee engaging with the hyperlink.

16. The computer system of claim 14 , wherein the messaging server is further configured to:

transmit a notification to the first mobile device that the payload has been activated.

17. The computer system of claim 12 , wherein the request to transmit the payment message is received via the payer operating the first mobile device inputting the request in the first messaging application executing on the first mobile device.

18. The computer system of claim 12 , wherein upon receiving the request to transmit the payment message, the payment processing server generates a graphical user interface component configured to receive payment data.

19. The computer system of claim 18 , wherein the graphical user interface component is configured to be displayed while the first mobile device is displaying the first messaging application.

20. The computer system of claim 18 , wherein the graphical user interface component comprises an interactive input element configured to receive a payment amount.

Assignments (2)
CHANGE OF NAME Recorded Dec 29, 2021
From: SQUARE, INC.
To: BLOCK, INC.
Reel/Frame 058598/0925 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 21, 2017
From: PAULIN, ALAN; WESTEN, PETER; WELCH, SHAWN; FEDERMAN, DANIEL; GERSHUNOVSKY, MICHAEL; OMOJOLA, AYOKUNLE
To: SQUARE, INC.
Reel/Frame 044466/0697 →
Continuity (3)
Continuation 15282833 · Sep 30, 2016
Provisional Application 62393504 · Sep 12, 2016
Related Publication 20180114211A1 · Apr 26, 2018
Cited By (2)
US 1,111,022 US 12,243,028