Granted Patent B2

US 12,321,917 · App. 17/446,207 · Granted Jun 3, 2025

Inventors: William J. Wied (Austin, TX); Manuela Dragan (Westfield, NJ); Stephen E. Dinan (Austin, TX)

Assignee: Worldpay, LLC

G06Q20/227G06Q20/065G06Q20/108

Abstract

Claims (87)

1. A method for a user to initiate a payment from an originating account to a receiving account, the method comprising:

training a machine learning model based on first information related to past fund transfers stored in a transaction database that indicates respective likelihoods that each originating account of a plurality of originating accounts stored in an account database will be selected by the user, and based on second information related to past fund transfers stored in the transaction database that indicates respective likelihoods that each receiving account of a plurality of receiving accounts stored in the account database will be selected by the user for a particular originating account;

determining, using the trained machine learning model, the originating account based on the first information related to past fund transfers stored in the transaction database that indicates respective likelihoods that each originating account of the plurality of originating accounts stored in the account database will be selected by the user;

prefilling, using the trained machine learning model, the originating account on a user interface based on determining the originating account;

determining, using the trained machine learning model, an order of the plurality of receiving accounts based on second information related to past fund transfers stored in the transaction database that indicates respective likelihoods that each receiving account of the plurality of receiving accounts stored in the account database will be selected by the user for a particular originating account;

displaying the plurality of receiving accounts on the user interface in the determined order;

receiving, via the user interface, an input selection by the user to indicate a receiving account from among the plurality of receiving accounts, the receiving account being an account that is to receive the payment;

updating the trained machine learning model based on the input selection by the user to indicate the receiving account;

receiving an input selection by the user as to an amount of the payment;

displaying, via the user interface, an indicia prompting the user to select for the payment to be carried out using a default payment setting or for the payment to be carried out using a user-defined payment setting;

displaying, via the user interface, available payment options associated with the user-defined payment setting, delivery times corresponding to the available payment options, and fees corresponding to the available payment options;

receiving, via the user interface, the user's input selection of the payment to be carried out, by one or the other of:

receiving an input selection by the user for the payment to be carried out using a default payment setting, and thereafter performing payment optimization logic to determine the default payment setting, a payment time or date, and a transaction cost based on one or more of geography data that identifies whether the electronic transaction is a domestic transaction or a cross-border transaction, non-processing window data that identifies an amount of time needed to process the electronic transaction, and real-time fraud data that identifies a likelihood of fraud associated with the electronic transaction; or alternatively,

receiving an input selection by the user for the payment to be carried out using a user-defined payment setting, and thereafter performing payment optimization logic based on received user-defined payment settings, including the originating account, the receiving account, and the payment amount, and receiving an input selection by the user indicating a chosen payment setting; and

receiving an input selection by the user indicating a selected payment option;

transmitting, to a server, an API call including information identifying the user's input selection;

receiving, from the server, an API response including indicia describing a payment method associated with the selected payment and a summary of transaction information associated with either of: the input selection of the user-defined payment setting or the input selection of the default payment setting;

transmitting and displaying, to the user interface, the indicia describing the payment method associated with the selected payment and the summary of transaction information associated with either of: the input selection of the user-defined payment setting or the input selection of the default payment setting; and

displaying, via the user interface, a prompt for a user selection associated with the summary of transaction information and the payment method.

2. The method of claim 1 , wherein receiving an input selection by the user to specify a receiving account comprises the user selecting the originating account and the receiving account from a dropdown menu that includes available accounts.

3. The method of claim 1 , further comprising:

displaying only the payment options that would complete the payment.

4. The method of claim 1 , further comprising:

displaying the payment options that would complete the payment in an order based on a number of days required to complete the payment.

5. The method of claim 1 , further comprising:

displaying the payment options that would complete the payment in an order based on a cost associated with completing the payment.

6. The method of claim 1 , further comprising:

indicating the payment options that are not available by dimming the payment options that would not complete the payment.

7. The method of claim 1 , further comprising:

the payment options that are not available by striking through text of the payment options that would not complete the payment.

8. A real-time transaction system comprising: one or more non-transitory computer readable media storing instructions for executing a real-time electronic transaction; and one or more processors configured to execute the instructions to perform operations comprising:

training a machine learning model based on first information related to past fund transfers stored in a transaction database that indicates respective likelihoods that each originating account of a plurality of originating accounts stored in an account database will be selected by the user, and based on second information related to past fund transfers stored in the transaction database that indicates respective likelihoods that each receiving account of a plurality of receiving accounts stored in the account database will be selected by the user for a particular originating account

determining, using the trained machine learning model, the originating account based on the first information related to past fund transfers stored in the transaction database that indicates respective likelihoods that each originating account of the plurality of originating accounts stored in the account database will be selected by the user;

prefilling, using the trained machine learning model, the originating account on a user interface based on determining the originating account;

determining, using the trained machine learning model, an order of the plurality of receiving accounts based on second information related to past fund transfers stored in the transaction database that indicates respective likelihoods that each receiving account of the plurality of receiving accounts stored in the account database will be selected by the user for a particular originating account;

displaying the plurality of receiving accounts on the user interface in the determined order;

receiving, via the user interface, an input selection by the user to indicate a receiving account from among the plurality of receiving accounts, the receiving account being an account that is to receive a payment;

receiving an input selection by the user as to an amount of the payment;

updating the trained machine learning model based on the input selection by the user to indicate the receiving account;

displaying, via the user interface, an indicia prompting the user to select for the payment to be carried out using a default payment setting and or for the payment to be carried out using a user defined payment setting;

displaying, via the user interface, available payment options associated with the user-defined payment setting, delivery times corresponding to the available payment options, and fees corresponding to the available payment options;

receiving, via the user interface, the user's input selection of the payment to be carried out, by one or the other of:

receiving an input selection by the user for the payment to be carried out using a default payment setting, and thereafter performing payment optimization logic to determine the default payment setting, a payment time or date, and a transaction cost based on one or more of geography data that identifies whether the electronic transaction is a domestic transaction or a cross-border transaction, non-processing window data that identifies an amount of time needed to process the electronic transaction, and real-time fraud data that identifies a likelihood of fraud associated with the electronic transaction; or alternatively,

receiving an input selection by the user for the payment to be carried out using a user-defined payment setting, and thereafter performing payment optimization logic based on received user-defined payment settings, including the originating account, the receiving account, and the payment amount, and receiving an input selection by the user indicating a chosen payment setting; and receiving an input selection by the user indicating a selected payment option;

transmitting, to a server, an API call including information identifying the user's input selection;

receiving, from the server, an API response including indicia describing a payment method associated with the selected payment and a summary of transaction information associated with either of: the input selection of the user-defined payment setting or the input selection of the default payment setting;

transmitting and displaying, to the user interface, the indicia describing the payment method associated with the selected payment and the summary of transaction information associated with either of: the input selection of the user-defined payment setting or the input selection of the default payment setting; and

displaying, via the user interface, a prompt for a user selection associated with the summary of transaction information and the payment method.

9. The system of claim 8 , wherein receiving an input selection by the user to specify a receiving account comprises the user selecting the originating account and the receiving account from a dropdown menu that includes available accounts.

10. The system of claim 8 , further comprising:

displaying only the payment options that would complete the payment.

11. The system of claim 8 , further comprising:

displaying the payment options that would complete the payment in an order based on a number of days required to complete the payment.

12. The system of claim 8 , further comprising:

displaying the payment options that would complete the payment in an order based on a cost associated with completing the payment.

13. The system of claim 8 , further comprising:

indicating the payment options that are not available by dimming the payment options that would not complete the payment.

14. A non-transitory computer-readable medium storing instructions for executing a real-time transaction, the instructions, when executed by one or more processors, causing the one or more processors to perform operations comprising:

training a machine learning model based on first information related to past fund transfers stored in a transaction database that indicates respective likelihoods that each originating account of a plurality of originating accounts stored in an account database will be selected by the user, and based on second information related to past fund transfers stored in the transaction database that indicates respective likelihoods that each receiving account of a plurality of receiving accounts stored in the account database will be selected by the user for a particular originating account;

determining, using the trained machine learning model, the originating account based on the first information related to past fund transfers stored in the transaction database that indicates respective likelihoods that each originating account of the plurality of originating accounts stored in the account database will be selected by the user;

prefilling, using the trained machine learning model, the originating account on a user interface based on determining the originating account;

determining, using the trained machine learning model, an order of the plurality of receiving accounts based on second information related to past fund transfers stored in the transaction database that indicates respective likelihoods that each receiving account of the plurality of receiving accounts stored in the account database will be selected by the user for a particular originating account;

displaying the plurality of receiving accounts on the user interface in the determined order;

receiving, via the user interface, an input selection by the user to indicate a receiving account from among the plurality of receiving accounts, the receiving account being an account that is to receive a payment;

updating the trained machine learning model based on the input selection by the user to indicate the receiving account;

receiving an input selection by the user as to an amount of the payment;

displaying, via the user interface, an indicia prompting the user to select for the payment to be carried out using a default payment setting or for the payment to be carried out using a user defined payment setting;

displaying, via the user interface, available payment options associated with the user-defined payment setting, delivery times corresponding to the available payment options, and fees corresponding to the available payment options;

receiving, via the user interface, the user's input selection of the payment to be carried out, by one or the other of:

receiving an input selection by the user to indicate that the payment is to be carried out using a default payment setting, and thereafter performing payment optimization logic to determine the default payment setting, a payment time or date, and a transaction cost based on one or more of geography data that identifies whether the electronic transaction is a domestic transaction or a cross-border transaction, non-processing window data that identifies an amount of time needed to process the electronic transaction, and real-time fraud data that identifies a likelihood of fraud associated with the electronic transaction; or alternatively,

receiving an input selection by the user for the payment to be carried out using a user-defined payment setting, and thereafter performing payment optimization logic based on received user-defined payment settings, including the originating account, the receiving account, and the payment amount, and receiving an input selection by the user indicating a chosen payment setting; and

receiving an input selection by the user indicating a selected payment option;

transmitting, to a server, an API call including information identifying the user's input selection;

receiving, from the server, an API response including indicia describing a payment method associated with the selected payment and a summary of transaction information associated with either of: the input selection of the user-defined payment setting or the input selection of the default payment setting;

transmitting and displaying, to the user interface, the indicia describing the payment method associated with the selected payment and the summary of transaction information associated with either of: the input selection of the user-defined payment setting or the input selection of the default payment setting; and

displaying, via the user interface, a prompt for a user selection associated with the summary of transaction information and the payment method.

15. The non-transitory computer-readable medium of claim 14 , wherein receiving an input selection by the user to specify a receiving account comprises the user selecting the originating account and the receiving account from a dropdown menu that includes available accounts.

16. The non-transitory computer-readable medium of claim 14 , further comprising:

displaying only the payment options that would complete the payment.

17. The non-transitory computer-readable medium of claim 14 , further comprising:

displaying the payment options that would complete the payment in an order based on a number of days required to complete the payment.

18. The non-transitory computer-readable medium of claim 14 , further comprising:

displaying the payment options that would complete the payment in an order based on a cost associated with completing the payment.

19. The non-transitory computer-readable medium of claim 14 , further comprising:

indicating the payment options that are not available by dimming the payment options that would not complete the payment.

20. The non-transitory computer-readable medium of claim 14 , further comprising:

the payment options that are not available by striking through text of the payment options that would not complete the payment.

Assignments (6)

Continuity (1)

References Cited (68)