System, method, and apparatus for integrating multiple payment options on a merchant webpage

Abstract

A system, method, and apparatus is provided for integrating multiple payment options on a merchant webpage. The method includes receiving, from a merchant system associated with a merchant webpage, a payment data capture request, generating, with at least one processor, web payment capture data based on the payment data capture request, the web payment capture data configured to adapt the merchant webpage to receive payment information input by a user, communicating, to the merchant system, the web payment capture data, receiving, directly from a client computer via at least one client-side script executed by the client computer based on the web payment capture data, the payment information input by the user, generating, with at least one processor, a transient payment token based on the payment information, and directly communicating the transient payment token to the client computer.

The invention claimed is: 
     
       1. A computer-implemented method comprising:
 receiving, from a merchant system associated with a merchant webpage, a payment data capture request; 
 generating, with at least one processor, web payment capture data based on the payment data capture request, the web payment capture data configured to adapt the merchant webpage to receive payment information input by a user; 
 communicating, to the merchant system, the web payment capture data; 
 receiving, directly from a client computer via at least one client-side script executed by the client computer based on the web payment capture data, the payment information input by the user; 
 generating, with at least one processor, a transient payment token based on the payment information, the transient payment token comprising the payment information after being encrypted; and 
 directly communicating the transient payment token to the client computer. 
 
     
     
       2. The computer-implemented method of  claim 1 , further comprising receiving, from the merchant system associated with the merchant webpage, a selected payment method, and generating at least one consumer data capture field based on the selected payment method. 
     
     
       3. The computer-implemented method of  claim 2 , further comprising generating normalized payment information by normalizing the payment information based on the payment method, wherein the transient payment token comprises the normalized payment information. 
     
     
       4. The computer-implemented method of  claim 1 , wherein the web payment capture data is configured to adapt the merchant webpage by:
 generating, on the merchant webpage, at least a portion of a graphical user interface (GUI) configured to receive the payment information from the user; and 
 configuring the at least one client-side script to validate the web payment capture data and process the payment information. 
 
     
     
       5. The computer-implemented method of  claim 1 , further comprising generating a cryptographic signature of the web payment capture data, wherein the at least one client-side script is configured to validate the web payment capture data based on the cryptographic signature. 
     
     
       6. The computer-implemented method of  claim 1 , further comprising encrypting the payment information with the at least one client-side script based on a public key embedded in the web payment capture data. 
     
     
       7. The computer-implemented method of  claim 1 , wherein the web payment capture data is configured to adapt the merchant webpage by configuring the merchant webpage to initiate a transaction through a single Application Programming Interface (API) call. 
     
     
       8. The computer-implemented method of  claim 1 , wherein the at least one client-side script is configured to pass the transient payment token from the client computer to the merchant system via the merchant webpage. 
     
     
       9. The computer-implemented method of  claim 1 , further comprising:
 receiving the transient payment token from the merchant system; and 
 generating an authorization request based on the transient payment token. 
 
     
     
       10. The computer-implemented method of  claim 1 , wherein at least a portion of the payment information is stored only in active memory. 
     
     
       11. A system for integrating multiple payment options on a merchant webpage, comprising at least one processor programmed or configured to:
 receive, from a merchant system associated with a merchant webpage, a payment data capture request; 
 generate web payment capture data based on the payment data capture request, the web payment capture data configured to adapt the merchant webpage to receive payment information input by a user; 
 communicate, to the merchant system, the web payment capture data; 
 receive, directly from a client computer via at least one client-side script executed by the client computer based on the web payment capture data, the payment information input by the user; 
 generate a transient payment token based on the payment information, the transient payment token comprising the payment information after being encrypted; and 
 directly communicate the transient payment token to the client computer. 
 
     
     
       12. The system of  claim 11 , wherein the at least one processor is further programmed or configured to receive, from the merchant system associated with the merchant webpage, a selected payment method, and generate at least one consumer data capture field based on the selected payment method. 
     
     
       13. The system of  claim 12 , wherein the at least one processor is further programmed or configured to generate normalized payment information by normalizing the payment information based on the payment method, wherein the transient payment token comprises the normalized payment information. 
     
     
       14. The system of  claim 11 , wherein the web payment capture data is configured to adapt the merchant webpage by:
 generating, on the merchant webpage, at least a portion of a graphical user interface (GUI) configured to receive the payment information from the user; and 
 configuring the at least one client-side script to validate the web payment capture data and process the payment information. 
 
     
     
       15. The system of  claim 11 , wherein the at least one processor is further programmed or configured to generate a cryptographic signature of the web payment capture data, wherein the at least one client-side script is configured to validate the web payment capture data based on the cryptographic signature. 
     
     
       16. The system of  claim 11 , wherein the at least one processor is further programmed or configured to encrypt the payment information with the at least one client-side script based on a public key embedded in the web payment capture data. 
     
     
       17. The system of  claim 11 , wherein the web payment capture data is configured to adapt the merchant webpage by configuring the merchant webpage to initiate a transaction through a single Application Programming Interface (API) call. 
     
     
       18. The system of  claim 11 , wherein the at least one client-side script is configured to pass the transient payment token from the client computer to the merchant system via the merchant webpage. 
     
     
       19. The system of  claim 11 , wherein the at least one processor is further programmed or configured to:
 receive the transient payment token from the merchant system; and 
 generate an authorization request based on the transient payment token. 
 
     
     
       20. A computer program product for integrating multiple payment options on a merchant webpage, comprising at least one non-transitory computer-readable medium including program instructions that, when executed by at least one processor, cause the at least one processor to:
 receive, from a merchant system associated with a merchant webpage, a payment data capture request; 
 generate web payment capture data based on the payment data capture request, the web payment capture data configured to adapt the merchant webpage to receive payment information input by a user; 
 communicate, to the merchant system, the web payment capture data; 
 receive, directly from a client computer via at least one client-side script executed by the client computer based on the web payment capture data, the payment information input by the user; 
 generate a transient payment token based on the payment information, the transient payment token comprising the payment information after being encrypted; and 
 directly communicate the transient payment token-to the client computer.