US 12,443,939 B1
Systems and methods for providing recommendations relating to enrollment and payment type
Ashish B. Kurani, Hillsborough, CA (US); James C. Noe, Charlotte, NC (US); Imran Haider, San Ramon, CA (US); Frank Fehrenbach, New York, NY (US); Guruprasadh Ragothaman, San Francisco, CA (US); Matthew C. Strader, San Francisco, CA (US); Palani Munuswamy, San Francisco, CA (US); Chandra Subramanian, San Francisco, CA (US); George Atala, San Francisco, CA (US); Mattie L. Morris, Chandler, AZ (US); Braden More, San Francisco, CA (US); Loftlon Worth, San Francisco, CA (US); and Nathan B. Coles, San Francisco, CA (US)
Assigned to Wells Fargo Bank, N.A., San Francisco, CA (US)
Filed by Wells Fargo Bank, N.A., San Francisco, CA (US)
Filed on Aug. 31, 2022, as Appl. No. 17/900,705.
Application 17/900,705 is a continuation in part of application No. 17/720,117, filed on Apr. 13, 2022, granted, now 12,079,795.
Claims priority of provisional application 63/287,426, filed on Dec. 8, 2021.
Claims priority of provisional application 63/208,908, filed on Jun. 9, 2021.
Claims priority of provisional application 63/189,513, filed on May 17, 2021.
Claims priority of provisional application 63/174,935, filed on Apr. 14, 2021.
This patent is subject to a terminal disclaimer.
Int. Cl. G06Q 20/22 (2012.01); G06Q 20/10 (2012.01)
CPC G06Q 20/227 (2013.01) [G06Q 20/102 (2013.01)] 20 Claims
OG exemplary drawing
 
11. A method comprising:
establishing, by one or more processors of a first server executing a first application, a connection between the first application and a second application executing on a second server, responsive to receipt of an application programming interface (API) call by an API gateway circuit relating to the first application of the first server, the first application and the second application linked to a first account holder, the API gateway circuit managing a plurality of APIs including a first API corresponding to the API call and the connection established responsive to authenticating information included in the API call;
receiving, by the one or more processors via the API gateway from the second application, an API signal comprising invoice data of a plurality of invoices for the first account holder, the invoice data including, for each of the plurality of invoices, a respective payment amount, a respective recipient identifier, and a first payment type;
identifying, by the one or more processors, that at least one recipient corresponding to the respective recipient identifier for an invoice of the plurality of invoices, is enrolled to accept a second payment type with one or more second account holders;
identifying, by the one or more processors, from the plurality of invoices received from the second application, a subset of invoices corresponding to the at least one recipient;
computing, by the one or more processors, a difference between a first value corresponding to usage of the first payment type for payment of the subset of invoices and a second value corresponding to usage of the second payment type for payment of the subset of invoices; and
presenting, by the one or more processors on a user interface, a recommendation to enroll the first account holder with the second payment type based on the difference.