Back to results
US 10,706,399 B1Granted
Systems and methods for client-side management of recurring payment transactions
AssigneeWorldpay, LLC
InventorSnehal Desai
Life of this patent
Estimating the term…
Abstract
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.
Claims12
A computer-implemented method for client-side management of recurring electronic transactions, comprising:
- receiving, at an acquirer processor, registration messages from merchant systems, the registration messages registering merchants associated with the merchant systems into a recurring electronic transaction computing platform;
- generating, at the acquirer processor, computer-executable instructions which, when executed by one or more processors of a consumer computing device, cause a graphical user interface to be displayed within an application executing on the consumer computing device;
- transmitting, by the acquirer processor, the computer-executable instructions to the consumer computing device;
- determining, at the acquirer processor, a list of merchants available for processing recurring electronic transactions based on the registration messages, the recurring electronic transactions being initiated by a consumer through interaction with the graphical user interface;
- transmitting, by the acquirer processor, the list of merchants to the application executing on the consumer computing device;
- receiving, at the acquirer processor, a selection of a merchant among the list of merchants and a selection of a merchant category code (MCC) from the consumer computing device, the selections being made by the consumer through interaction with the graphical user interface;
- receiving, at the acquirer processor, transaction data directly from the consumer computing device independent of the merchant systems, wherein the transaction data comprises a merchant identifier, the MCC, a transaction amount, a recurring transaction schedule, and a transaction account number;
- and
- communicating with an issuer processor associated with the transaction account number to seek transaction authorization for the received transaction data.
6 more elements
A recurring electronic transaction system, comprising:
- an acquirer processor computing system comprising a processor executing instructions stored in memory, wherein the instructions cause the processor to:
- receive registration messages from merchant systems, the registration messages registering merchants associated with the merchant systems into a recurring electronic transaction computing platform;
- generate computer-executable instructions which, when executed by one or more processors of a consumer computing devices, cause a graphical user interface to be displayed within an application executing on the consumer computing device;
- transmit the computer-executable instructions to the consumer computing device;
- determine a list of merchants available for processing recurring electronic transactions based on the registration messages, the recurring electronic transactions being initiated by a consumer through interaction with the graphical user interface;
- transmit the list of merchants to the application executing on the consumer computing device;
- receive a selection of a merchant among the list of merchants and a selection of a merchant category code (MCC) from the consumer computing device, the selections being made by the consumer through interaction with the graphical user interface;
- receive transaction data directly from the consumer computing device independent of the merchant systems, wherein the transaction data comprises a merchant identifier, the MCC, a transaction amount, a recurring transaction schedule, and a transaction account number;
- and
- communicate with an issuer processor associated with the transaction account number to seek transaction authorization for the received transaction data.
7 more elements
Dependencies are inferred from the claim text.