Multi-commerce channel wallet for authenticated transactions

Abstract

A phone-based electronic wallet providing authenticated transactions across multiple channels of commerce. The electronic wallet may be used for point-of-sale payments, remote mobile payments and/or web-based payments, and may use authentication tools such as offline PINs, SecureCode PINs and/or online PINs.

1 . A method for removing pop-up windows during an authentication process involving a cardholder using a payment card in an electronic transaction, comprising the steps of:
 sending authentication criteria directly from an access control sever to a merchant plug-in;   translating said authentication criteria to a language compatible with said merchant plug-in;   forwarding said authentication criteria through said merchant plug-in to a device operated by said cardholder for entry of said authentication credentials associated with said payment card in the absence of a pop up window.   
     
     
         2 . The method according to  claim 1 , wherein said authentication criteria are transmitted in HTML markup, and further comprising the step of translating said HTML markup into application programming interface protocol. 
     
     
         3 . The method according to  claim 2 , further comprising the step of returning said authentication credentials through said merchant plug-in to said access control server for validation of said credentials. 
     
     
         4 . The method according to  claim 3 , further comprising the step of translating the authentication credentials received by said merchant plug-in from said application programming interface protocol to said HTML markup. 
     
     
         5 . The method according to  claim 4 , further comprising the step of sending a validation response from said access control server to said merchant plug-in for subsequent transmission to a merchant participating in said electronic transaction. 
     
     
         6 . A method of authenticating the identity of a cardholder during an electronic transaction involving a payment card utilizing 3D Secure protocols, comprising the steps of:
 a) sending a verify enrollment request to a directory server;   b) identifying an access control server associated with said card;   c) sending a verify enrollment response from said access control server to said directory server, said verify enrollment response including a URL address of said access control server;   d) sending said verify enrollment response to a merchant plug-in associated with a merchant involved in said electronic transaction;   e) sending a payor authentication request from said merchant plug-in to said access control server;   f) sending a browser HTML markup from said access control server to said merchant plug-in;   g) extracting data from said HTML markup associated with said authentication of said card;   h) transmitting said extracted data to a wallet application associated with said cardholder for entry of authentication credentials;   i) sending said credentials from said wallet application through said merchant plug-in to said access control server;   j) sending said translated credentials from said merchant plug-in to said access control server for validation;   k) transmitting, upon validation of said credentials, a payer authentication response and a payment authorization from said access control server to said merchant plug-in;   l) transmitting said authorization from said merchant plug-in to said wallet application for subsequent transmission to said merchant.   
     
     
         7 . The method according to  claim 6 , wherein said extracting step includes the further steps of interpreting said HTML markup. 
     
     
         8 . The method according to  claim 6 , comprising the further step of translating said extracted data into application programming interface protocol. 
     
     
         9 . The method according to  claim 6 , wherein said authentication credentials are sent from said wallet application to said merchant plug-in via application programming interface protocol. 
     
     
         10 . The method according to  claim 6 , further comprising the step of displaying a request for said cardholder to enter authentication credentials into said cardholder's phone. 
     
     
         11 . The method according to  claim 6 , further comprising the step of translating said credentials received from said wallet application into an appropriate format for receipt by said access control server. 
     
     
         12 . The method according to  claim 11 , further comprising the step of translating said credentials from said application programming interface protocol to said HTML markup 
     
     
         13 . A method of reducing fraudulent transactions associated with electronic commerce, comprising the steps of:
 providing a wallet application for storage on a mobile phone;   entering of data associated with a payment card into said wallet application;   authenticating the identity of the cardholder associated with said payment card via an authentication process;   placing said wallet application into an authenticated state whereby the data associated with said payment card is stored in a secure manner within said wallet application; and   communicating said authenticated state of said wallet to a merchant during said electronic translation.   
     
     
         14 . The method according to  claim 13 , comprising the further steps of:
 analyzing said financial transaction to assign a risk factor to such transaction;   determining whether further authentication is required based upon said assigned risk factor.   
     
     
         15 . A system for authenticating the identity of a cardholder during an electronic transaction involving a payment card enrolled in an authentication program, comprising:
 a directory server for verification of the enrollment of said card in said program;   an access control server in communication with said directory server, said access control server containing authentication credentials associated with said card;   a merchant plug-in in communication with said directory server and said access control server; and   wherein said merchant plug-in is capable of receiving authentication criteria directly from said access control server and is further capable of translating said criteria to a language which allows transmission of said criteria through said merchant plug-in to an electronic device associated with said cardholder.   
     
     
         16 . The system according to  claim 15 , wherein said merchant plug-in includes a translator for extracting data from said authentication criteria received from said access control server. 
     
     
         17 . The system according to  claim 15 , further comprising a mobile phone and a wallet application, said application being stored on said phone and adapted to receive said authentication criteria from said merchant plug-in for subsequent entry of said validation credentials.