Systems and methods for client-side management of recurring payment transactions
Systems and methods disclosed herein for the client-side management of recurring payment transactions. An account holder can interact with a consumer computing device, such as a smart phone or tablet computer, to provide billing parameters for recurring payments to a merchant. The billing parameters can be updated over time by the account holder.
1. A computer-implemented method for client-side management of recurring transactions, comprising:
receiving, by a consumer computing device, computer-executable instructions from an acquirer processor which cause a graphical user interface (GUI) to be displayed within a consumer application;
receiving, by the consumer application, a list of merchants available for processing recurring transactions from the acquirer processor;
receiving, via the GUI displayed within the consumer application, selection of a merchant among the list of merchants and a recurring transaction schedule;
transmitting, by the consumer application based on the recurring transaction schedule, a transaction authorization request directly to the acquirer processor, the transaction authorization request comprising a merchant identifier and a transaction account number; and
receiving, by the consumer application, a transaction authorization response from the acquirer processor.
2. The computer-implemented method of claim 1 , further comprising:
receiving, by the acquirer processor, registration messages from merchant systems, the registration messages registering merchants associated with the merchant systems into a recurring transaction platform;
determining, by the acquirer processor, the list of merchants available for processing recurring transactions based on the registration messages; and
transmitting, by the acquirer processor, the list of merchants to the consumer application.
3. The computer-implemented method of claim 1 , further comprising, prior to the consumer application receiving the transaction authorization response from the acquirer processor:
receiving, by the acquirer processor, the transaction authorization request from the application;
transmitting, by the acquirer processor, the transaction authorization request to a payment network;
receiving, by the acquirer processor, the transaction authorization response from the payment network; and
transmitting, by the acquirer processor, the transaction authorization response to the consumer application.
4. The computer-implemented method of claim 1 , further comprising:
receiving, via the GUI displayed within the consumer application, a change to the recurring transaction schedule.
5. The computer-implemented method of claim 4 , wherein the change to the recurring transaction schedule comprises a termination of all future payments to the merchant.
6. The computer-implemented method of claim 1 , wherein the recurring transaction schedule is any of a weekly payment cycle, a monthly payment cycle, a quarterly payment cycle, and a yearly payment cycle.
7. The computer-implemented method of claim 1 , wherein the recurring transaction schedule comprises a total number of recurring transactions and a transaction amount for each recurring transaction.
8. The computer-implemented method of claim 1 , wherein the GUI is displayed within the consumer application via an application server implemented on the acquirer processor.
9. The computer-implemented method of claim 1 , wherein the GUI is displayed using hypertext markup language (HTML), Java script, or a dedicated applet or application.
10. The computer-implemented method of claim 1 , wherein the consumer application is downloaded from the acquirer processor or a third-party software application provider.
11. A system for client-side management of recurring transactions, comprising:
one or more processors; and
one or more computer readable media storing instructions which, when executed by the one or more processors, cause the one or more processors to perform operations comprising:
receiving, by a consumer computing device, computer-executable instructions from an acquirer processor which cause a graphical user interface (GUI) to be displayed within a consumer application;
receiving, by the consumer application, a list of merchants available for processing recurring transactions from the acquirer processor;
receiving, via the GUI displayed within the consumer application, selection of a merchant among the list of merchants and a recurring transaction schedule;
transmitting, by the consumer application based on the recurring transaction schedule, a transaction authorization request directly to the acquirer processor, the transaction authorization request comprising a merchant identifier and a transaction account number; and
receiving, by the consumer application, a transaction authorization response from the acquirer processor.
12. The system of claim 11 , the operations further comprising:
receiving, by the acquirer processor, registration messages from merchant systems, the registration messages registering merchants associated with the merchant systems into a recurring transaction platform;
determining, by the acquirer processor, the list of merchants available for processing recurring transactions based on the registration messages; and
transmitting, by the acquirer processor, the list of merchants to the consumer application.
13. The system of claim 11 , the operations further comprising, prior to the consumer application receiving the transaction authorization response from the acquirer processor:
receiving, by the acquirer processor, the transaction authorization request from the application;
transmitting, by the acquirer processor, the transaction authorization request to a payment network;
receiving, by the acquirer processor, the transaction authorization response from the payment network; and
transmitting, by the acquirer processor, the transaction authorization response to the consumer application.
14. The system of claim 11 , the operations further comprising:
receiving, via the GUI displayed within the consumer application, a change to the recurring transaction schedule.
15. The system of claim 14 , wherein the change to the recurring transaction schedule comprises a termination of all future payments to the merchant.
16. The system of claim 11 , wherein the recurring transaction schedule is any of a weekly payment cycle, a monthly payment cycle, a quarterly payment cycle, and a yearly payment cycle.
17. The system of claim 11 , wherein the recurring transaction schedule comprises a total number of recurring transactions and a transaction amount for each recurring transaction.
18. The system of claim 11 , wherein the GUI is displayed within the consumer application via an application server implemented on the acquirer processor.
19. The system of claim 11 , wherein the GUI is displayed using hypertext markup language (HTML), Java script, or a dedicated applet or application.
20. One or more non-transitory computer readable media storing instructions which, when executed by one or more processors, cause the one or more processors to perform operations for client-side management of recurring transactions, the operations comprising:
receiving, by a consumer computing device, computer-executable instructions from an acquirer processor which cause a graphical user interface (GUI) to be displayed within a consumer application;
receiving, by the consumer application, a list of merchants available for processing recurring transactions from the acquirer processor;
receiving, via the GUI displayed within the consumer application, selection of a merchant among the list of merchants and a recurring transaction schedule;
transmitting, by the consumer application based on the recurring transaction schedule, a transaction authorization request directly to the acquirer processor, the transaction authorization request comprising a merchant identifier and a transaction account number; and
receiving, by the consumer application, a transaction authorization response from the acquirer processor.