US 12,033,130 B2
Smart stager
Paul Augusto Melgar, Eagan, MN (US); Scott Anthony Kostelecky, Maple Grove, MN (US); Cheryl Lynn Magers, Prior Lake, MN (US); Christian Michael Fuchs, Minneapolis, MN (US); Sonja Elizabeth Dery, Coon Rapids, MN (US); Joseph Richard Braga, Minneapolis, MN (US); David Allan Motley, St. Paul, MN (US); Gary Cecil Lugar, Maple Grove, MN (US); and Constance Marie Arrington, Minneapolis, MN (US)
Assigned to MoneyGram International, Inc., Dallas, TX (US)
Filed by MoneyGram International, Inc., Minneapolis, MN (US)
Filed on Jun. 30, 2021, as Appl. No. 17/363,347.
Application 17/363,347 is a continuation of application No. 16/706,403, filed on Dec. 6, 2019, granted, now 11,055,687.
Application 16/706,403 is a continuation of application No. 15/256,484, filed on Sep. 2, 2016, granted, now 10,504,099, issued on Dec. 10, 2019.
Prior Publication US 2021/0398102 A1, Dec. 23, 2021
This patent is subject to a terminal disclaimer.
Int. Cl. G06Q 40/00 (2023.01); G06Q 20/10 (2012.01); G06Q 20/22 (2012.01)
CPC G06Q 20/29 (2013.01) [G06Q 20/10 (2013.01)] 10 Claims
OG exemplary drawing
 
1. A method for providing a recurring money transfer transaction service, the method comprising:
receiving, by a processor of a central server computing device operating in an electronic money transfer network, a request to establish a recurring money transfer transaction from an input to a Graphic User Interface (“GUI”) of a first computing device of a first sending party;
providing, by the processor of the central server, an authorization code corresponding to the recurring money transfer transaction for display on the GUI of the first computing device of the first sending party, wherein the first computing device of the first sending party is associated with a first user profile stored in a database accessible to the central server via the money transfer network;
receiving, by the processor of the central server, a request to access the recurring money transfer transaction, wherein the request to access the recurring money transfer transaction is received from an input to a GUI of a second computing device of a second sending party and includes the authorization code, and wherein inclusion of the authorization code in the request to access the recurring money transfer transaction indicates the second computing device of the second sending party is authorized to access the recurring money transfer transaction records stored in the database;
linking, by the processor of the central server, the first user profile associated with the first sending party to a second user profile associated with the second sending party to establish a multi-sender profile for the recurring money transfer transaction, wherein the multi-sender profile is accessible via the authorization code by the first sending party, the second sending party, or both;
storing the multi-sender profile in the database;
receiving, by the processor of the central server, a request from the first sending party or the second sending party or both to configure receiving party information from a receiving party, wherein the request includes the authorization code and receiver staging information for the recurring money transfer transaction, including at least one payment amount for the money transfer transaction;
storing configuration records containing the receiving party information in the database;
receiving, by the processor of the central server, payment account designation information from an input to the GUI of the first computing device of the sending party and an input to the GUI of the second computing device of the second sending party, the payment account designation information identifying a first financial account indicated by the first sending party and a second financial account indicated by the second sending party, the first financial account identified in the first user profile of the first sending party and the second financial account identified in the first user profile of the second sending party;
associating, by the processor of the central server, in the database, the first financial account and the second financial account with the multi-sender profile, wherein the multi-sender profile excludes at least some of the confidential information associated with the first financial account and the second financial account;
determining, by the processor of the central server, a funding amount received from the first computing device of the first sending party and the second computing device of the second sending party in connection with a current instance of the recurring money transfer transaction, wherein a first portion of funds is provided by the first sending party using the first financial information and a second portion of funds is provided by the second sending party using the second financial information;
verifying, by the processor of the central server, using the multi-sender profile and the received authorization code, whether the funding amount received from the first sending party and the second sending party is greater than or equal to the payment amount; and
in response to a verification that the amount of the funds received from the first sending party and the second sending party is greater than or equal to the transaction amount, initiating the money transfer transaction, in accordance with conditions specified in the multi-sender profile information to provide at least a portion of the transaction amount to the receiving party.