IP Library Granted Patent US 12,561,664
Granted Patent B1
US 12,561,664 · App. 18/421,853 · Granted Feb 24, 2026

Electronic audible payment messaging

Inventors: Jesse Wilson (San Francisco, CA); Terrill Dent (Waterloo, CA)
Assignee: Block, Inc.
G06Q20/3255G06Q20/22G06Q20/40G06Q30/06G10L15/083H04L51/02
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,561,664
App. No.
18/421,853
Granted
Feb 24, 2026
Kind
B1
Abstract

In one embodiment, a method includes receiving, at a payment-service-system server, a payment request from a voice-recognition server. The payment request includes a sender identifier, a recipient identifier, and an amount and is received by the payment-service-system server responsive to the voice-recognition server identifying one or more audible payment keywords in an encoded audio file received from a user computing device. The method includes transmitting, by the payment-service-system server, a confirmation request to the user computing device to confirm the payment request. The method includes receiving, at the payment-service-system server, a confirmation of the payment request from the user computing device. The method includes, upon receiving the confirmation of the payment request, automatically debiting the amount from a sender account associated with the sender identifier and crediting the amount to a recipient account associated with the recipient identifier.

Claims (59)

1 . A method comprising:

receiving, by a messaging-service server, from a user computing device of a user, a message generated within a messaging application associated with the messaging-service server and executing on the user computing device, the message including at least a user identifier encoded in message data of the message, the message data being generated as part of a conversation between at least the user of the messaging application and a software agent associated with a payment-service-system server;

determining, by the messaging-service server and based on the message data, that the message includes a syntax;

in response to determining that the message includes the syntax, forwarding, by the messaging-service server, the message to the payment-service-system server;

querying, by the payment-service-system server, a database to determine whether the user identifier is associated with a user account associated with the payment-service-system server;

identifying, based on a determination that the user identifier is associated with the user account, and using the software agent to process the message data, a banking-related action to be performed in association with the user account;

generating, using the software agent, a human-readable textual message that states the banking-related action to be performed;

transmitting, by the payment-service-system server, the human-readable textual message and a confirmation request to the messaging-service server;

forwarding, by the messaging-service server, to the user computing device, the human-readable textual message and the confirmation request for display on the user computing device within the messaging application to confirm the banking-related action, the confirmation request being an interactive prompt presented within the messaging application;

receiving, by the messaging-service server, from the user computing device and in association with an interaction with the interactive prompt, a confirmation to perform the banking-related action; and

upon receiving the confirmation, transmitting, by the messaging-service server, an instruction to the payment-service-system server to automatically perform the banking-related action in association with the user account.

2 . The method of claim 1 , further comprising:

accessing, by the payment-service-system server, historical data associated with the user identifier, the historical data comprising payment history, message history data, user data, and merchant data;

determining, by the payment-service-system server, context associated with the conversation; and

generating, by the payment-service-system server, based on the historical data and the context, a recommendation including one or more additional actions or reminders for the user.

3 . The method of claim 2 , wherein the context comprises a date associated with the conversation, a time associated with the conversation, a location associated with the conversation, the user associated with the conversation, or one or more goods or services associated with the conversation.

4 . The method of claim 1 , further comprising generating results data based at least in part on processing performed, by the software agent, on the message data, wherein identifying the banking-related action is based at least in part on the results data.

5 . The method of claim 1 , wherein the message comprises one of a voice command or an instant message.

6 . The method of claim 1 , wherein the confirmation comprises one of a voice command requesting the banking-related action or an instant message requesting the banking-related action.

7 . The method of claim 1 , wherein performing the banking-related action comprises one or more of (i) initiating a transfer of funds between one or more financial accounts associated with the user identifier, (ii) initiating the transfer of the funds from a first financial account associated with the user identifier to a second financial account associated with a second user, (iii) canceling the transfer of the funds, (iv) accessing banking information associated with the one or more financial accounts associated with the user identifier, or (v) initiating an online payment associated with the user identifier.

8 . The method of claim 1 , wherein the software agent corresponds to a chatbot.

9 . A payment-service-system server comprising:

one or more processors; and

one or more non-transitory computer-readable media storing instructions executable by the one or more processors, wherein the instructions program the one or more processors to perform operations comprising:

receiving, from a messaging-service server, a message generated within a messaging application associated with the messaging-service server and executing on a user computing device, the message including at least a user identifier encoded in message data of the message;

querying a database to determine whether the user identifier is associated with a user account associated with the payment-service-system server;

identifying, using natural language processing, a currency indicator or a payment word in the message;

in response to identifying the currency indicator or the payment word in the message, determining, using a software agent associated with the payment-service-system server to process the message data, a banking-related action to be performed in association with the user account;

generating, using the software agent, a human-readable textual message that states the banking-related action to be performed;

transmitting, to the messaging-service server, the human-readable textual message and a confirmation request for display on the user computing device within the messaging application to confirm the banking-related action; and

upon the messaging-service server receiving, from the user computing device and in association with an interaction with the messaging application, a confirmation to perform the banking-related action, receiving, from the messaging-service server, an instruction to automatically perform the banking-related action in association with the user account.

10 . The payment-service-system server of claim 9 , wherein the message data is generated as part of a conversation between at least a user of the messaging application and the software agent.

11 . The payment-service-system server of claim 10 , the operations further comprising:

accessing historical data associated with the user identifier, the historical data comprising payment history, message history data, user data, and merchant data;

determining context associated with the conversation;

generating based on the historical data and the context, a recommendation including one or more additional actions or reminders for the user; and

transmitting the recommendation to the messaging-service server for display on the user computing device within the messaging application.

12 . The payment-service-system server of claim 9 , wherein the software agent corresponds to a chatbot.

13 . The payment-service-system server of claim 9 , wherein the confirmation request comprises an interactive prompt presented within the messaging application and wherein the confirmation is received as a response to the interactive prompt.

14 . The payment-service-system server of claim 9 , the operations further comprising generating results data based at least in part on processing performed by the software agent on the message data, wherein determining the banking-related action is based at least in part on the results data.

15 . The payment-service-system server of claim 9 , wherein the message comprises one of a voice command or an instant message.

16 . The payment-service-system server of claim 9 , wherein the confirmation comprises one of a voice command requesting the banking-related action or an instant message requesting the banking-related action.

17 . The payment-service-system server of claim 9 , wherein performing the banking-related action comprises one or more of (i) initiating a transfer of funds between one or more financial accounts associated with the user identifier, (ii) initiating the transfer of the funds from a first financial account associated with the user identifier to a second financial account associated with a second user, (iii) canceling the transfer of the funds, (iv) accessing banking information associated with the one or more financial accounts associated with the user identifier, or (v) initiating an online payment associated with the user identifier.

18 . One or more non-transitory computer-readable media maintaining instructions that, when executed by one or more processors of a payment-service-system server, program the one or more processors to perform operations comprising:

receiving, from a messaging-service server, a message generated within a messaging application associated with the messaging-service server and executing on a user computing device, the message including at least a user identifier encoded in message data of the message;

querying a database to determine whether the user identifier is associated with a user account associated with the payment-service-system server;

identifying, using natural language processing, a currency indicator or a payment word in the message;

in response to identifying the currency indicator or the payment word in the message, determining, using a software agent associated with the payment-service-system server to process the message data, a banking-related action to be performed in association with the user account;

generating, using the software agent, a human-readable textual message that states the banking-related action to be performed;

transmitting, to the messaging-service server, the human-readable textual message and a confirmation request for display on the user computing device within the messaging application to confirm the banking-related action; and

upon the messaging-service server receiving, from the user computing device and in association with an interaction with the messaging application, a confirmation to perform the banking-related action, receiving, from the messaging-service server, an instruction to automatically perform the banking-related action in association with the user account.

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

the message data is generated as part of a conversation between at least a user of the messaging application and the software agent;

the confirmation request comprises an interactive prompt presented within the messaging application; and

the confirmation is received as a response to the interactive prompt.

20 . The one or more non-transitory computer-readable media of claim 19 , the operations further comprising:

accessing historical data associated with the user identifier, the historical data comprising payment history, message history data, user data, and merchant data;

determining context associated with the conversation; and

generating, based on the historical data and the context, a recommendation including one or more additional actions or reminders for the user.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 21, 2024
From: WILSON, JESSE; DENT, TERRILL
To: SQUARE, INC.
Reel/Frame 066862/0214 →
CHANGE OF NAME Recorded Mar 21, 2024
From: SQUARE, INC.
To: BLOCK, INC.
Reel/Frame 066867/0679 →
Continuity (2)
Continuation 17072717 · Oct 16, 2020
Continuation 15638223 · Jun 29, 2017
References Cited (71)
US 8332314B2 · Griffin · 2012 [cited by applicant]
US 9324067B2 · Van et al. · 2016 [cited by applicant]
US 9342831B1 · Davis et al. · 2016 [cited by applicant]
US 9483763B2 · Van et al. · 2016 [cited by applicant]
US 9917802B2 · Melzer et al. · 2018 [cited by applicant]
US 9922380B2 · Isaacson et al. · 2018 [cited by applicant]
US 9922381B2 · Isaacson et al. · 2018 [cited by applicant]
US 9972318B1 · Kelly et al. · 2018 [cited by applicant]
US 9992335B2 · Vijaywargi et al. · 2018 [cited by applicant]
US 10235129B1 · Carlson et al. · 2019 [cited by applicant]
US 10423948B1 · Wilson et al. · 2019 [cited by applicant]
US 10810574B1 · Wilson et al. · 2020 [cited by applicant]
US 20050131813A1 · Gallagher et al. · 2005 [cited by applicant]
US 20070011104A1 · Leger et al. · 2007 [cited by applicant]
US 20080177659A1 · Lacey et al. · 2008 [cited by applicant]
US 20090094458A1 · Dionisio · 2009 [cited by applicant]
US 20100114775A1 · Griffin · 2010 [cited by applicant]
US 20100250687A1 · Smith et al. · 2010 [cited by applicant]
US 20100312645A1 · Niejadlik et al. · 2010 [cited by applicant]
US 20120158589A1 · Katzin et al. · 2012 [cited by applicant]
US 20120310752A1 · Gaddis · 2012 [cited by applicant]
US 20130018779A1 · Laquerre et al. · 2013 [cited by applicant]
US 20130204993A1 · Uribe-Etxebarria · 2013 [cited by applicant]
US 20140052633A1 · Gandhi · 2014 [cited by applicant]
US 20140058939A1 · Savla · 2014 [cited by applicant]
US 20140337207A1 · Zhang et al. · 2014 [cited by applicant]
US 20150046329A1 · Huxham et al. · 2015 [cited by applicant]
US 20150088998A1 · Isensee et al. · 2015 [cited by applicant]
US 20150095188A1 · Lee et al. · 2015 [cited by applicant]
US 20150127526A1 · Ye et al. · 2015 [cited by applicant]
US 20150269575A1 · Narayanan et al. · 2015 [cited by applicant]
US 20150348002A1 · Van et al. · 2015 [cited by applicant]
US 20150371223A1 · Li et al. · 2015 [cited by applicant]
US 20160117651A1 · Davis · 2016 [cited by applicant]
US 20160117665A1 · Davis · 2016 [cited by applicant]
US 20160117666A1 · Davis et al. · 2016 [cited by applicant]
US 20160117670A1 · Davis · 2016 [cited by applicant]
US 20160125371A1 · Grassadonia · 2016 [cited by examiner]
US 20160171481A1 · Mcelmurry et al. · 2016 [cited by applicant]
US 20160180316A1 · Wang · 2016 [cited by examiner]
US 20160180325A1 · Davis et al. · 2016 [cited by applicant]
US 20160224967A1 · Davis et al. · 2016 [cited by applicant]
US 20160283936A1 · Daniel et al. · 2016 [cited by applicant]
US 20160335532A1 · Sanghavi et al. · 2016 [cited by applicant]
US 20160360039A1 · Sanghavi et al. · 2016 [cited by applicant]
US 20170004588A1 · Isaacson et al. · 2017 [cited by applicant]
US 20170011383A1 · Melzer · 2017 [cited by applicant]
US 20170186115A1 · Sheppard et al. · 2017 [cited by applicant]
US 20170262837A1 · Gosalia · 2017 [cited by examiner]
US 20170270605A1 · Demark et al. · 2017 [cited by applicant]
US 20170374198A1 · De et al. · 2017 [cited by applicant]
WO 2017103326A1 · 2017 [cited by applicant]
Austin, Patrick Lucas, “Apple Just Added One More Way to Repay Your Friends”, Jun. 5, 2017, Lifehacker, 3 pages. [cited by applicant]
Barbosa, Greg, “Square Cash update includes promised Messages app plus Siri integration”, Sep. 13, 2016, 9to5 Mac, 3 pages. [cited by applicant]
BBVA Bank, “The latest from Apple and Google in mobile APIs for developing native applications”, Nov. 10, 2016, BBVA Bank News, 9 pages. [cited by applicant]
BI Intelligence—Finance, “Facebook Messenger Promotes P2P Payments”, Sep. 23, 2016, Business Insider, 4 pages. [cited by applicant]
Chowdhry, Amit, “Apple Patent Highlights An iMessage Payment Service”, Jan. 7, 2016, Forbes Tech, 3 pages. [cited by applicant]
Constine, Josh, “Facebook Introduces Free Friend-To-Friend Payments Through Messages”, Mar. 17, 2015, TechCrunch, 5 pages. [cited by applicant]
Constine, Josh, “Facebook Messenger Adds Group Chat Polls and AI Payment Suggestions”, Sep. 22, 2016, TechCrunch, 3 pages. [cited by applicant]
Crook, Jordan, “Apple launches iMessage Apps so third-party devs can join your convos”, Jun. 13, 2016, TechCrunch, 2 pages. [cited by applicant]
Fuhrmeister, Chris, “Apple Wants to Help You Split the Check With iMessage”, Jun. 15, 2016, Eater, 2 pages. [cited by applicant]
Goel, Vindu, “Apple to Offer App Developers Access to Siri and iMessage”, Jun. 13, 2016, The New York Times (Year: 2016), 2 pages. [cited by applicant]
Madore, P. H., “Apple Patent Reveals Siri-Assisted iMessage P2P Payments Platform”, Nov. 17, 2016, Hacked: Hacking Finance, Artificial Intelligence, 5 pages. [cited by applicant]
Peckham, James, “Apple is opening up Siri, iMessage and Maps—here's why that's a great thing”, Jun. 13, 2016, Tech Radar, 4 pages. [cited by applicant]
Quoc, Michael, “11 Examples of Conversational Commerce and Chatbots”, May 31, 2016, Chatbots Magazine by Octane AI, 24 pages. [cited by applicant]
Rao, Leena, “Square Cash Users Will Be Able to Send Money Via Apple iMessage”, Jun. 13, 2016, Fortune, 6 pages. [cited by applicant]
Statt, Nick, “Facebook's AI Assistant Will Now Offer Suggestions Inside Messenger”, Apr. 6, 2017, The Verge, 5 pages. [cited by applicant]
Tepper, Fitz, “You Can Now Send Your Friends Money Inside iMessage”, Jun. 5, 2017, TechCrunch, 3 pages. [cited by applicant]
Wagner, Kurt, “Facebook Messenger Adds Peer-to-Peer Payments Feature”, Mar. 17, 2015, Recode, 3 pages. [cited by applicant]
Yeung, Ken, “Facebook Adds Group Payments to Messenger”, Apr. 11, 2017, VentureBeat, 3 pages. [cited by applicant]
Yeung, Ken, “Facebook Messenger Gets Polls and Now Encourages Peer-to-Peer Payments”, Sep. 22, 2016, Venture Beat, 5 pages. [cited by applicant]