Systems and methods for providing recommendations relating to enrollment and payment type
Systems and methods for providing recommendations relating to payment methods include establishing a connection between a first application executing on a first server and a second application executing on a second server where the first and second applications are linked to a first account holder. The first application may receive invoice data of a plurality of invoices from the second application. The first application may identify that at least one recipient is enrolled to accept a second payment type with one or more second account holders. The first application may identify a subset of invoices corresponding to the at least one recipient, compute a difference between a first value corresponding to usage of a first payment type and a second value corresponding to usage of the second payment type, and present a recommendation to enroll the first account holder with the second payment type based on the difference.
1. A system comprising:
a processing circuit comprising one or more processors communicably coupled to memory, the memory configured to store instructions that, when executed by the one or more processors, cause the one or more processors to:
establish a connection between a first application executing on a first server 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;
receive, by the API gateway of the first application 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;
identify, by the first application, 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;
identify, by the first application, from the plurality of invoices received from the second application, a subset of invoices corresponding to the at least one recipient;
compute, by the first application, 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
present, by the first application on a user interface, a recommendation to enroll the first account holder with the second payment type based on the difference.
2. The system of claim 1 , wherein the instructions further cause the one or more processors to:
receive, via an input to the user interface, a first request to enroll the first account holder; and
update, by the first application based on the first request, a payment type setting of the second application for invoices to be paid to the at least one recipient from the first payment type to the second payment type.
3. The system of claim 2 , wherein the instructions further cause the one or more processors to:
transmit, responsive to the first request, a second request to an account holder corresponding to the at least one recipient to accept payments via the second payment type from the first account holder.
4. The system of claim 3 , wherein updating the payment type setting is performed responsive to receiving a response to the second request indicating acceptance of payments via the second payment type from the first account holder.
5. The system of claim 2 , wherein updating the payment type setting is performed responsive to identifying an auto-enroll setting for the at least one recipient to accept payments via the second payment type is enabled.
6. The system of claim 1 , wherein the first application presents the recommendation responsive to the second value being greater than the first value.
7. The system of claim 1 , wherein, to identify that the at least one recipient is enrolled to accept the second payment type, the instructions are configured to cause the one or more processors to:
access, by the first application, one or more data structures storing information related to a plurality of recipients enrolled to accept the second payment type; and
perform, by the first application, a look-up function in the one or more data structures using the recipient identifier identified for the invoice.
8. The system of claim 1 , wherein the instructions further cause the one or more processors to:
identify, by the first application, second invoice data corresponding to a new invoice from the second application, the second invoice data including the recipient identifier corresponding to the at least one recipient; and
initiate, by the first application, a transaction using the second payment type with the recipient according to the second invoice data.
9. The system of claim 1 , wherein the first application comprises a financial institution application and wherein the second application comprises at least one of an enterprise resource planning (ERP) application or a customer relationship management (CRM) application.
10. The system of claim 1 , wherein establishing the connection between the first application and the second application is responsive to the first account holder registering a first account for the first application with a second account for the second application.
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.
12. The method of claim 11 , further comprising:
receiving, by the one or more processors via an input to the user interface, a first request to enroll the first account holder; and
updating, by the one or more processors based on the first request, a payment type setting of the second application for invoices to be paid to the at least one recipient from the first payment type to the second payment type.
13. The method of claim 12 , further comprising:
transmitting, by the one or more processors, responsive to the first request, a second request to an account holder corresponding to the at least one recipient to accept payments via the second payment type from the first account holder.
14. The method of claim 13 , wherein updating the payment type setting is performed responsive to receiving a response to the second request indicating acceptance of payments via the second payment type from the first account holder.
15. The method of claim 12 , wherein updating the payment type setting is performed responsive to identifying an auto-enroll setting for the at least one recipient to accept payments via the second payment type is enabled.
16. The method of claim 11 , wherein identifying that the at least one recipient is enrolled to accept the second payment type comprises:
accessing, by the one or more processors, one or more data structures storing information related to a plurality of recipients enrolled to accept the second payment type; and
performing, by the one or more processors, a look-up function in the one or more data structures using the recipient identifier identified for the invoice.
17. The method of claim 11 , further comprising:
identifying, by the one or more processors, second invoice data corresponding to a new invoice from the second application, the second invoice data including the recipient identifier corresponding to the at least one recipient; and
initiating, by the one or more processors, a transaction using the second payment type with the recipient according to the second invoice data.
18. The method of claim 11 , wherein the first application comprises a financial institution application and wherein the second application comprises at least one of an enterprise resource planning (ERP) application or a customer relationship management (CRM) application.
19. The method of claim 11 , wherein establishing the connection between the first application and the second application is responsive to the first account holder registering a first account for the first application with a second account for the second application.
20. A non-transitory computer readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to:
establish a connection between a first application executing on a first server 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;
receive, by the API gateway of the first application 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;
identify, by the first application, 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;
identify, by the first application, from the plurality of invoices received from the second application, a subset of invoices corresponding to the at least one recipient;
compute, by the first application, 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
present, by the first application on a user interface, a recommendation to enroll the first account holder with the second payment type based on the difference.