JP6386151B2 - Open wallet for electronic transactions - Google Patents

Description

  This application claims the benefit of US Provisional Application No. 61 / 536,275, filed September 19, 2011, the entire contents of which are incorporated herein by reference.

  The present disclosure relates generally to methods and / or systems for mobile commerce and / or electronic commerce. In particular, the present disclosure relates to a method and / or system that provides payment processing support for merchants doing business over a telecommunications network such as the Internet and / or a wireless network. However, it should be understood that the subject matter disclosed herein is equally applicable to other similar applications and / or environments.

  As a background, mobile commerce is expanding rapidly around the world. Consumer adoption of smartphones has brought a perfect storm for the new mobile payment ecosystem. More and more retailers and sellers are targeting mobile messaging, mobile shopping applications, mobile optimized websites, mobile search, social mobile applications, barcode scanning applications, location-based Use services, etc. to contact their consumers through mobile devices. However, it is still a challenge to enable user-friendly payments from mobile devices, which causes an unsatisfactory transition to this mobile payment ecosystem and limits the potential of this mobile payment ecosystem.

  One particular challenge is that it is cumbersome to make a payment that requires the user to enter payment data, billing data, and shipping data. To address this challenge, there are a number of companies that build "mobile wallets" that provide container applications that store all of the user's payments and personal data. The user can then access this data with a “single click”. Mobile wallets address the challenges described above, but with mobile wallets, retailers or sellers will support a number of different mobile wallets such as GOOGLE WALLET, VISA WALLET, AMEX WALLET, SPRINT WALLET, ISIS WALLET, MASTERCARD WALLET, etc. New challenges arise, such as the need for Managing and building integration and connectivity into the diverse wallet ecosystem, where each wallet solution, whether slightly or prominent, is challenging for retailers or sellers. Furthermore, if the adoption of mobile wallets by consumers is minimal, the benefits are reduced by supporting many different mobile wallets.

  At the same time, consumers are readily adopting “mobile banking applications” such as native mobile applications and mobile optimized web applications. The mobile banking application allows consumers access to credit cards, bank accounts, and other payment account data (eg, PAYPAL®, AMAZON PAYMENTS, etc.). Mobile banking applications are simple and easy for consumers to use and provide great utility for people to manage their financial accounts on the go. However, most mobile banking applications are inadequate in that they simply provide account service data such as access to current balances, transaction history, branch and ATM locator data, etc. It is.

The present invention provides new and improved methods and / or systems that overcome the above and other problems.
INCORPORATION BY REFERENCE The following applicants' applications are hereby incorporated by reference in their entirety.

Keresman, III et al. U.S. Pat. No. 7,051,002 to Balasbramanian et al., Entitled “General Merchant Platform for Payment Authentication”. U.S. Patent Application Publication No. 2009/0313147 entitled "Realization of Alternative Payments for Electronic Retailers"

  According to one aspect, a system is provided for completing a transaction between a first party and a second party. The system includes at least one program memory that includes instructions executable by the processor. Instructions executable by the processor include one or more banking applications and / or wallets that include personal data or access to personal data to complete the transaction. The instructions executable by the processor further include an open commerce wallet exchange (OCWE) module that uses the open commerce wallet exchange protocol to request a request for personal data from a second party. Receive and receive a selection of one of a banking application and / or wallet from the first party and use the authentication embedded in the selected banking application and / or wallet to identify the first party Authenticate, receive personal data from the selected banking application and / or wallet, provide personal data to the merchant using the open commerce wallet exchange protocol, Configured to complete the-transactions. The system further includes at least one processor that executes instructions executable by the processor of the program memory.

  According to one aspect, a method is provided for completing a transaction between a first party and a second party. This method is performed by at least one processor. A request for personal data to complete a transaction is received from a second party using an open commerce wallet exchange (OCWE) protocol. A selection of one of one or more banking applications and / or wallets is received from the first party. One or more banking applications and / or wallets include personal data or access to personal data. The first party is authenticated using authentication selected in the selected banking application and / or wallet. The personal data is received from the selected banking application and / or wallet and the merchant is provided with personal data using the OCWE protocol to complete the transaction.

  According to one aspect, a system is provided for completing a transaction between a first party and a second party. The system includes at least one processor programmed to receive a request for personal data from the second party to complete a transaction using an open commerce wallet exchange (OCWE) protocol. including. The processor is further programmed to receive a selection from the first user of one of one or more banking applications and / or wallets associated with the system. One or more banking applications and / or wallets include personal data or access to personal data. The processor is further programmed to receive personal data from the selected banking application and / or wallet, provide the personal data to the merchant using an open commerce wallet exchange protocol, and complete the transaction.

FIG. 1 is a block diagram of an exemplary system for implementing an open commerce wallet exchange (OCWE). FIG. 2 is a sequence diagram of an exemplary transaction using OCWE.

  Referring to FIG. 1, a block diagram of an electronic commerce (e-commerce) system 10, such as a mobile commerce system, that implements an open commerce wallet exchange (OCWE) is provided. In a preferred embodiment, OCWE provides an open exchange that allows consumers to securely share personal data for completing transactions with merchants in a common and seamless format. Personal data includes, for example, payment and / or fulfillment data.

  The e-commerce system 10 includes a plurality of subsystems interconnected by one or more communication networks 12. The subsystem includes one or more consumer systems 14, one or more merchant systems 16, and one or more payment systems 18. The subsystem may further include a central OCWE system 20. Communication network 12 typically includes the Internet, but may additionally or alternatively include other types of communication networks. For example, the communication network 12 may include one or more of a local area network (LAN), a wireless network, a wide area network (WAN), and the like.

  Different parties (eg, legal persons or natural persons) typically provide each of the subsystems 14, 16, 18, 20 of the e-commerce system 10. However, it is also contemplated that the same party may provide multiple subsystems 14, 16, 18, 20 of the e-commerce system 10. For example, a merchant may provide one of merchant system 16 and OCWE system 20.

  The consumer system 14 allows the consumer to conduct transactions with the merchant via the communication network 12, and personal data for completing the transaction is exchanged using OCWE. Consumer system 14 includes a consumer system for each of the consumers. Further, the consumer system 14 is typically a mobile device such as a mobile phone, but other types of digital processing devices such as laptop computers are contemplated.

  Each consumer system 14 includes a plurality of subcomponents. The subcomponent includes at least one processor 22 and at least one program memory 24. The processor 22 executes instructions executable by the processor stored in the program memory 24 to perform one or more transactions, each transaction as described in connection with FIG.

  One or more banking applications and / or wallets 26 included in the instructions executable by the processor contain or include access to personal data that is required to complete the transaction. Security built into the banking application and / or wallet 26 prevents unauthorized access to personal data. The wallet provides a container for storing user payments and personal data. Wallets include, for example, GOOGLE WALLET, VISA WALLET, AMEX WALLET, SPRINT WALLET, ISIS WALLET, MASTERCARD WALLET, and the like. The banking application provides user access credit cards, bank accounts, and other payment account data. Banking applications include, for example, CITI CREDIT CARD MOBILE BANKING APPLICATION.

  A user interface of instructions executable by the processor allows the banking application and / or wallet 26 to interact with the consumer. That is, the user interface allows the banking application and / or wallet 26 to present data to the consumer using a subcomponent user output device 28, such as a display device. In addition, the user interface allows a consumer to communicate with a banking application and / or wallet 26 using a subcomponent user input device 30 such as a keyboard.

  The user interface further uses the user output device 28 to present to the consumer products and / or services sold by the merchant. Further, the user interface allows the consumer to use the user input device 30 to select products and / or services to purchase from the merchant. The user interface is typically a graphical user interface, such as a merchant website, that is presented to the consumer using the user output device 28. However, other types of user interfaces are contemplated, such as an interactive voice response (IVR) user interface.

  After the consumer has finished selecting products and / or services to purchase from the seller, the instructions executable by the processor send a purchase request to the seller system 16 corresponding to the seller. The purchase request identifies the selected product and / or service and, in some embodiments, indicates that the consumer desires to adopt OWCE. The consumer may, for example, use a user interface to indicate that he / she has finished selecting a product and / or service and / or wishes to adopt OWCE. In response to the purchase request, merchant system 16 calls OWCE to request personal data from the consumer.

  The OWCE module 32 included in the instructions executable by the processor allows the merchant system 16 to obtain personal data from the banking application and / or wallet 26 using the OCWE protocol. The OWCE module 32 may be, for example, an application of the consumer system 14 or may be incorporated into the operating system of the consumer system 14. In one embodiment, the OCWE module 32 communicates with the merchant system 16 through the OCWE system 20. In other embodiments, the OCWE module 32 communicates directly with the merchant system 16. Suitably, the OCWE module 32 requires authentication of the merchant system 16 before communicating with the merchant system 16.

  In response to a request for personal data from a merchant, the OWCE module 32 supports OWCE out of the banking application and / or wallet 26, and in some embodiments, the merchant merchant system 16 Determine a list of banking applications and / or wallets to support. To determine the banking application and / or wallet that supports OWCE, the OWCE module 32 provides the banking application and / or wallet 26 with an interface used to register with the OWCE (eg, application programming interfaces: A set of APIs). To determine the banking application and / or wallet that merchant system 16 supports, the request identifies the banking application and / or wallet that merchant system 16 supports.

  After the list is determined, the list is presented to the consumer using the user interface, allowing the consumer to select a banking application and / or wallet to use to complete the transaction. The selected banking application and / or wallet is then invoked. By invoking the selected banking application and / or wallet, the banking application and / or wallet must authenticate the consumer and provide the consumer with personal data entry and / or to complete the transaction. For example, it allows selection of personal data maintained by the selected application and / or wallet.

  The personal data is then provided to the merchant system 16 using OWCE. That is, personal data is provided to the OCWE module 32 via an interface provided to the banking application and / or wallet. The interface may be a set of APIs provided by the OCWE module 32, for example. The OCWE module 32 provides the personal data to the seller system 16 directly or by the OCWE system 20. In this way, OCWE provides merchant system 16 unified access to different banking applications and / or wallets regardless of the banking application and / or wallet 26's different communication protocols, data element requirements, and / or transmission standards Provide a customized interface.

  The OWCE module 32 further allows the consumer to register individual banking applications and / or wallet and master credentials with any form of authentication. That is, the consumer can register and specify the banking application and / or individual credentials of the wallet 26 in the consumer system 14 corresponding to the consumer with the OCWE. The consumer can further specify the master credentials and the type of authentication to use. The OWCE module 32 then proxies different authentication requirements of the banking application and / or wallet 26.

  The subcomponent further includes at least one storage memory 34 and at least one communication unit 36. The storage memory 34 provides data storage to the processor 22. The communication unit 36 provides the processor 22 with an interface for communicating with other subsystems of the e-commerce system 10 via the communication network 12. The consumer system 14 further includes at least one system bus and / or communication network 38 that interconnects sub-components of the consumer system 14.

  The merchant system 16 allows the merchant to conduct transactions with the consumer via the communication network 12, and personal data for completing the transaction is exchanged using OCWE. Each merchant system 16 is associated with one of the merchants. Further, each of the merchant systems 16 is composed of one or more computer servers, typically a plurality of computer servers.

  Each of the merchant systems 16 includes a plurality of subcomponents. The subcomponent includes at least one processor 40 and at least one program memory 42. The processor 40 executes instructions executable by the processor stored in the program memory 42 to perform one or more transactions, each transaction as described in connection with FIG.

  The OCWE module 44 included in the instructions executable by the processor allows the merchant system 16 to obtain personal data from the consumer system 14 using the OCWE protocol. In one embodiment, the OCWE module 44 communicates with the consumer system 16 through the OCWE system 20. In other embodiments, the OCWE module 44 communicates directly with the consumer system 14. Suitably, the OCWE module 44 requires authentication of the consumer system 14 before communicating with the consumer system 14.

  Suitably, merchant system 16 requests personal data from the consumer in response to receiving a purchase request from consumer's consumer system 14. The purchase request identifies the products and / or services that the consumer desires to purchase from the seller. In some embodiments, the purchase request indicates that the consumer wants to adopt OWCE. This is employed to determine whether the transaction should be processed as before or using OWCE. In response to receiving the personal data, merchant system 16 completes the transaction using payment system 18 as is conventional. Alternatively, if the OWCE system 20 is employed, the OWCE system 20 completes the transaction instead of using the payment system 18 as is conventionally done by merchants. The merchant system 16 provides an indication of completed transactions to the consumer system 14 and / or the OWCE system 20.

  The subcomponent further includes at least one storage memory 46 and at least one communication unit 48. The storage memory 46 provides data storage to the processor 40. The communication unit 48 provides the processor 40 with an interface for communicating with other subsystems of the e-commerce system 10 via the communication network 12. The merchant system 16 further includes at least one system bus and / or communication network 50 that interconnects the sub-components of the merchant system 16.

  Each payment system 18 is associated with a party that processes payments for merchants. Further, each payment system 18 is comprised of one or more computer servers, typically a plurality of computer servers, and a plurality of subcomponents embodying the computer servers. The subcomponent includes at least one processor 52 and at least one program memory 54. The processor executes instructions executable by the processor to complete the transaction between the merchant and the consumer stored in the program memory 54.

  Instructions executable by the processor process payments for one or more payment brands that provide one or more payment options. Payment brands include, for example, AMERICA EXPRESS, DISCOVER FINANCIAL SERVICES, JCB INTERNATIONAL, and MASTERCARD WORLDWIDE AND VISA INTERIONIONAL, and payment options include, for example, credit cards and debit cards.

  In some embodiments, payments for one or more alternative payment brands are processed by instructions executable by the processor, in addition or alternatively, which provide one or more alternative payment options. The Alternative payment brands include, for example, GOOGLE, PAYPAL, BILL ME LATER, MYECHECK, and SECURE VAULT PAYMENTS. Alternative payment options include, for example, GOOGLE CHECKOUT, PAYPAL EXPRESS, BILL ME LATER EXPRESS, and BILL ME LATER BUSINESS.

  The subcomponent further includes at least one storage memory 56 and at least one communication unit 58. The storage memory 56 provides data storage to the processor 52. The communication unit 58 provides the processor with an interface for communicating with other subsystems of the e-commerce system 10 via the communication network 12. Payment system 18 further includes at least one system bus and / or communication network 60 that interconnects subcomponents of payment system 18.

  The payment system 18 is, for example, a payment gateway or a universal merchant platform (UMP). UMP provides merchants with a unified interface for completing a transaction in part or in whole. For details of UMP, see, for example, Balasubramanian et al. U.S. Patent Application Publication No. 2009/0313147 entitled "Realization of Alternative Payments for Electronic Retailers", or Keresman, III et al. Attention should be directed to US Pat. No. 7,051,002, entitled “General Seller Platform for Payment Authentication”, both of which are hereby incorporated by reference.

  The OCWE system 20 is associated with a party that provides a centralized OCWE for merchants and consumers to share personal data. The OCWE system 20 includes a plurality of subcomponents. The subcomponent includes at least one processor 62 and at least one program memory 64. The processor 62 executes instructions executable by the processor to facilitate transactions between the merchant and the consumer stored in the program memory 64.

  The OCWE module 66 included in the instructions executable by the processor relays personal data between the consumer system 14 and the merchant system 16. Typically, the merchant system 16 connects to the OCWE module 66 and requests personal data from the consumer system 14. The OCWE module 66 then relays the request to the consumer system 14. The OCWE module 66 further authenticates the consumer system 14 and the merchant system 16 before exchanging personal data. Authentication can be performed using authentication credentials such as a password.

  The OCWE module 66 further allows the consumer to register individual banking application and / or wallet credentials to use the master credentials with any form of authentication. That is, the consumer can register and specify the banking application of the consumer system 14 and / or individual credentials of the wallet 26 corresponding to the consumer with the OCWE. The consumer can further specify the master credentials and the type of authentication to use. The OCWE module 66 then proxies the different authentication requirements of the banking application and / or the wallet 26.

  The subcomponent further includes at least one storage memory 68 and at least one communication unit 70. The storage memory 68 provides data storage to the processor. The communication unit 70 provides the processor 62 with an interface for communicating with other subsystems of the e-commerce system 10 via the communication network 12. The OCWE system 20 further includes at least one system bus and / or communication network 72 that interconnects the subcomponents of the OCWE system.

  Referring to FIG. 2, a sequence diagram illustrating a transaction between a consumer 74 and a merchant where the transaction is performed using OCWE is shown. Initially, the consumer 74 selects products and / or services to purchase from the seller using the consumer 74 consumer system 14. The consumer 74 then triggers the consumer system 14 to generate a purchase request and send the purchase request to the seller's merchant system 16. The trigger is executed, for example, by selecting a “Buy” button on the user interface. The purchase request includes an identifier that enables direct identification of the selected product and / or service or indirect identification of the selected product and / or service.

  In response to receiving the purchase request, merchant system 16 calls OCWE to determine personal data including settlement and / or fulfillment data to complete the transaction. The payment data includes data necessary to identify a payment option, such as an alternative payment option or a conventional payment option, and complete the transaction with the identified payment option. For example, according to conventional payment options such as a credit card or debit card, the payment data may include a card number and an expiration date. The fulfillment data includes data necessary to fulfill the merchant's obligations after settlement. For example, fulfillment data may include a shipping address.

  When calling OCWE, the merchant system 16 uses the OCWE communication protocol to request personal data from the consumer system 14. As shown, this entails requesting personal data by the OCWE system 20. However, it is also contemplated that personal data can be requested directly from the consumer system 14. The consumer system 14 supports OCWE in response to receiving the request, and in some embodiments is supported by the consumer system 14 banking application and / or wallet, which is supported by the merchant system 16. Determine the list. This list is displayed to the consumer 74 and one of the banking applications and / or wallets used to complete the transaction is selected.

  The selected banking application and / or wallet is then activated. A consumer 74 using the banking application and / or wallet authenticates using the banking application and / or the wallet's existing authentication mechanism. In addition, the authenticated consumer 74 permits the exchange of banking applications and / or wallet already existing personal data with the merchant system 16. Alternatively, the authenticated consumer 74 enters personal data. At this point, the personal data is provided to the merchant system 16. As shown, this is performed directly by the merchant system 16. However, it can also be performed indirectly by the OWCE system 20.

  Merchant system 16 then processes the transaction with the received personal data using existing payment processing and payment system 18. Alternatively, the OWCE system 20 presents personal data to the payment system 18 instead of the seller system 16. If the banking application and / or wallet has different communication protocols, data element requirements, and / or transmission standards, OWCE can seamlessly adjust, convert, and communicate between all devices and / or sites.

  Although the above has been described for a transaction between a seller and a consumer, a transaction between a retailer and a consumer is also contemplated. In such an embodiment, merchant system 16 is used as a retailer system. In addition, transactions are typically performed face-to-face between the consumer and the seller (or seller rep). Thus, the retailer system can be, for example, a point-of-sale information management system.

  OWCE can also be employed to translate from one form of communication protocol to another. For example, the OWCE initiates a wallet at the consumer system 14. Should consumers want to use their OWCE for other types of commerce, such as gaming devices, cars, TVs, etc., a single connection for a merchant may have a different communication protocol if the OWCE Will link to services that are translated into communication protocols.

  Advantageously, OWCE provides merchants and / or retailers with a unified interface for requesting personal data from banking applications and / or wallets. Merchants and / or retailers do not need to build multiple integrations or “settlement pipes” into dozens of wallets and / or thousands of mobile banking applications. If the banking application and / or wallet has different communication protocols, data element requirements, and / or transmission standards, OWCE can seamlessly modulate, translate, and communicate between all devices and / or sites.

  Suitably, the methods and systems described herein include a computer or other digital processing device including a digital processor, such as a microprocessor, microcontroller, graphics processing unit (GPU), etc. It should be understood that and are embodied by storage. In other embodiments, the system and method may be embodied by a server that includes a digital processor and includes or has access to digital data storage, such server being Internet or local Appropriately accessed via an area network, or the system and method can be embodied by a personal data assistant (PDA) that includes a digital processor and digital data storage, etc. A computer or other digital processing device suitably includes or is operatively connected to one or more user input devices, such as a keyboard for receiving user input. In addition, one or more display devices are included or operably connected to the one or more display devices. In other embodiments, input for controlling the method and system is received from another program running on the computer prior to or simultaneously with the method and system, or from a network connection, etc. Condition. Similarly, in other embodiments, the output can serve as an input to another program running on the computer following or simultaneously with the method and system, or network For example, it can be transmitted over a connection.

  In some embodiments, the exemplary methods described above, systems employing the methods, etc. of this application can be implemented (eg, by a digital processor) to implement the exemplary methods and / or systems. The present invention is embodied by a storage medium that stores various instructions. The storage medium can be, for example, a magnetic disk or other magnetic storage medium, an optical disk or other optical storage medium, a random access memory (RAM), a read-only memory (ROM), or Other electronic memory devices, or a set of chips or operably interconnected chips, an internet server from which stored instructions can be retrieved over the internet or a local area network, etc.

  In connection with the specific exemplary embodiments presented herein, certain structural and / or functional features are described as being incorporated into defined elements and / or components. Should be further understood. However, it is contemplated that these features may be similarly incorporated into other elements and / or components as needed for the same or similar benefits. Different aspects of the exemplary embodiments can be selectively employed as needed to achieve other alternative embodiments suitable for the desired application, thereby enabling other alternative embodiments. It should also be understood that the embodiments realize the respective advantages of the aspects incorporated therein.

  It is also to be understood that certain elements or components described herein may have their functionality suitably implemented by hardware, software, firmware, or a combination thereof. In addition, it is to be understood that certain elements described herein as being incorporated together can be stand-alone elements or otherwise separated under appropriate circumstances. is there. Similarly, a plurality of specific functions described as being performed by one specific element can be performed by a plurality of separate elements operating independently to perform the individual functions, Alternatively, certain individual functions can be separated and performed by multiple separate elements operating together. Alternatively, some elements or components otherwise described and / or shown herein as separate from one another can be physically or functionally combined as desired.

  More particularly, as used herein, a memory is a non-transitory computer readable medium, a magnetic disk or other magnetic storage medium, an optical disk or other optical storage medium, a random access memory. RAM), read-only memory (ROM), or other electronic memory device, or a set of chips or operably interconnected chips, stored instructions on the Internet / intranet or local area It should be understood to include one or more of internet / intranet servers, etc. that can be searched over the network. Further, as used herein, a processor can be a microprocessor, a microcontroller, a graphics processing unit (GPU), an application-specific integrated circuit (ASIC), an FPGA, Or the like, wherein the controller is (1) a processor and memory, wherein the processor executes computer-executable instructions on the memory incorporating the functionality of the controller, or (2) Including analog and / or digital hardware, user input devices include mouse, keyboard, touch screen display, 1 Includes one or more of one or more buttons, one or more switches, one or more toggles, a speech recognition engine, etc., the database includes one or more memories, and the display device is , LCD displays, LED displays, plasma displays, projection displays, touch screen displays, and the like.

  That is, the specification has been described with reference to preferred embodiments. Obviously, upon reading and understanding this specification, other changes and modifications will occur. The present invention is intended to be construed as including all such changes and modifications as long as they fall within the scope of the appended claims or their equivalents. That is, the various, disclosed above and other features and functions, or alternatives thereof, can be combined as desired into a number of other different systems or applications, and there are various It will be understood that alternatives, changes, variations, or improvements that are not currently anticipated or unexpected can be made by those skilled in the art and are also intended to be included in the following claims Let's go.

  Exemplary embodiments have been described in connection with the preferred embodiments. Obviously, other changes and modifications may be made upon reading and understanding the above detailed description. The exemplary embodiments are intended to be construed as including all such changes and modifications as long as they fall within the scope of the appended claims or their equivalents.

Claims (19)

A system for completing a transaction between a first party and a second party, the system comprising:
At least one processor included in the first party's system;
And at least one program memory connected to the at least one processor and including instructions executable by the processor;
When the instructions of the program memory that can be executed by the processor are executed by the at least one processor,
Displaying a list of one or more banking applications and / or wallets to the first party;
Receiving from the first party one of the one or more banking applications and / or wallets selected by the first party from the displayed list;
Authenticating the first party using an authentication function built into the selected banking application and / or wallet;
Receiving a request for personal data from the second party using an open commerce wallet exchange (OCWE) protocol;
Receiving the personal data from the selected banking application and / or wallet;
Providing the received personal data to the second party using the open commerce wallet exchange protocol to complete the transaction.
system. The system of claim 1, wherein the instructions executable by the processor are implemented as an open commerce wallet exchange module, and the instructions executable by the processor are executed by the at least one processor, ,
A system that causes the one or more banking applications and / or wallets to perform providing an application programming interface (API) for communicating with the open commerce wallet exchange module. The system of claim 1, wherein instructions executable by the processor are executed by the at least one processor,
A system for performing the step of converting the one or more banking applications and / or different communication protocols of the wallet into the open commerce wallet exchange protocol. The system of claim 1, further comprising:
A system including the first party mobile device, the mobile device including the at least one program memory and the at least one processor.   The system of claim 1, wherein the first party is a consumer and the second party is a merchant or retailer.   2. The system of claim 1, wherein instructions executable by the processor, when executed by the at least one processor, provide the processor with the received personal data directly to the second party. A system to be executed.   2. The system of claim 1, wherein instructions executable by the processor are executed by the at least one processor, wherein the received personal data is sent to the second party and the third party. A system that performs the process of providing through an open commerce wallet exchange system. The system of claim 1, wherein instructions executable by the processor are executed by the at least one processor,
Receiving the indication from the second party that the transaction has been completed. The system of claim 1, wherein instructions executable by the processor are executed by the at least one processor,
A system for performing the step of receiving the request directly from the second party.   The system of claim 1, wherein the personal data includes payment data and / or fulfillment data. The system of claim 1, wherein instructions executable by the processor are executed by the at least one processor,
Receiving the request from the second party via the third party's open commerce wallet exchange system. A method for completing a transaction between a first party and a second party, wherein the method is performed by at least one processor included in the first party's system;
Displaying a list of one or more banking applications and / or wallets to the first party;
Receiving from the first party one of the one or more banking applications and / or wallets selected by the first party from the displayed list;
Authenticating the first party using an authentication function built into the selected banking application and / or wallet;
Receiving a request for personal data from the second party using an open commerce wallet exchange (OCWE) protocol;
Receiving the personal data from the selected banking application and / or wallet;
Providing the received personal data to the second party using the open commerce wallet exchange protocol and completing the transaction. The method of claim 12, further comprising:
Converting the one or more banking applications and / or different communication protocols of the wallet into the open commerce wallet exchange protocol.   13. The method of claim 12, wherein the first party is a consumer and the second party is a seller or retailer. The method of claim 12, further comprising:
Providing the received personal data directly to the second party. The method of claim 12, further comprising:
Providing the received personal data to the second party via a third party open commerce wallet exchange system. The method of claim 12, further comprising:
Receiving the request directly from the second party. The method of claim 12, further comprising:
Receiving the request from the second party via a third party open commerce wallet exchange system. A system for completing a transaction between a first party and a second party, comprising:
Having at least one processor included in the first party's system, the processor comprising:
Displaying a list of one or more banking applications and / or wallets to the first party;
Receiving from the first party one of the one or more banking applications and / or wallets selected by the first party from the displayed list;
Authenticating the first party using an authentication function built into the selected banking application and / or wallet;
Receiving a request for personal data from the second party using an open commerce wallet exchange (OCWE) protocol;
Receiving the personal data from the selected banking application and / or wallet;
Providing the received personal data to the second party using the open commerce wallet exchange protocol and completing the transaction.
system.

Images