WO2017011790A1

WO2017011790A1 - Electronic payment system and methods of processing an electronic payment

Info

Publication number: WO2017011790A1
Application number: PCT/US2016/042604
Authority: WO
Inventors: Ravi REMAMRUTHAM
Original assignee: Equipay, Llc
Priority date: 2015-07-16
Filing date: 2016-07-15
Publication date: 2017-01-19

Abstract

A computer-implemented method for facilitating an electronic payment to a payee from a payer is provided. The computer-implemented method using a mobile computer device coupled to a memory device. The method includes locating, by the mobile computer device, a machine readable code; receiving, by the mobile computer device, product information from the machine readable code; decoding, by the mobile computer device, the machine readable code; retrieving, by the mobile computer device, a validation token from a merchant associated with the product information; and processing, by the mobile computer device, an electronic payment transaction based at least on the validation token for a product associated with the product information.

Description

ELECTRONIC PAYMENT SYSTEM AND METHODS OF PROCESSING AN

ELECTRONIC PAYMENT

CROSS REFERENCE TO RELATED APPLICATION

[0001] This application claims priority to U.S. Provisional Patent Application Serial Number 62/193,154, filed on July 16, 2015, which is incorporated in its entirety by reference.

BACKGROUND

[0002] The field of the disclosure relates generally to processing electronic payments in both online and in-person commercial transactions, and more particularly, to network-based systems and methods for processing of electronic payments in which payer information is provided by a secure "one-touch" payment mechanism that simultaneously transmits required payer information to a merchant without additional or minimal input from the payer.

[0003] Known electronic payment systems enable users to make payments, for example retail purchases, electronically using a payment card. The payment card is either presented personally, in the situation of a purchase being made at a brick-and-mortar retail facility, or presented electronically, in the form of various items of information associated with the payment card and the underlying account associated with the card. Some known payment systems use a payment network, such as a credit card network, to transfer payments from users to payees.

[0004] In the environment of commercial transactions, consumers who use transaction cards to make purchases, particularly in on-line transaction situations, are often required to conduct onerous processes such as to provide significant amounts of information in order to complete the transaction. For example, consumers are often required to provide their name, email address, billing address, shipping address, transaction card information (such as the card number, expiry date, and security code). When entering such information, the merchant website typically requests permission of the consumer to store the consumer's information (registration), which information is typically stored in the merchant's database. Consumers accordingly may over the course of time have their payment and other personal information stored in the databases of numerous merchants. [0005] The acquisition and storage, even temporarily, of consumer payment information by numerous merchants and vendors presents a significant challenge with respect to security issues. Merchants and vendors that become participants in such payment systems are typically required by the proprietors of such payment systems to undertake substantial security measures in order to protect data, such as consumer payment information, that is stored on merchant or vendor databases. The conventional processes may be burdensome and fear of card security/fraud may influence a customer to abandon the transaction.

[0006] Accordingly, it would be desirable to provide systems and methods for receiving and processing consumer payment information that addresses security issues and further reduces the number of locations in which consumer payment information is stored. Additionally, it would be desirable to provide for systems and methods that facilitate processing of electronic payments in which payer information is provided by a secure "one-touch" payment mechanism that simultaneously transmits required payer information to a merchant without additional or minimal input from the payer.

[0007] In the environment of social media, advertisers have recognized that as people spend more time on social media sites, the users can be a prime audience for advertising both on the desktop and mobile platforms. While social site advertising may have a higher "click-through" rate than traditional banner advertising, the number of conversions, from site visitor to a financial transaction with a customer, may be as low as 1.7% for the desktop and 2% for mobile sites and applications. A reason for the low conversion is that users may be reticent to be distracted from the social reason that the users are on the social media site. Users may be aware that clicking or tapping on an advertisement will take the user sway from the social site to the advertised product or service site.

[0008] Accordingly, it would be desirable to allow advertisers and retailers to share products and/or services on social media sites in a manner that visitors cannot peruse information about the product/service but also purchase the product/service immediately via a mobile smartphone or tablet device. Moreover, it would be desirable, for users to share products/services with friends or connections in their social network. In turn, these friends can subsequently also purchase the products/services of the social network immediately, securely, and without friction. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Features, aspects, and advantages of the present disclosure will become better understood when the following Detailed Description is read with reference to the accompanying drawings in which like characters represent like parts throughout, wherein:

[0010] FIG. 1 is a schematic diagram illustrating an exemplary multi-party payment card industry system for enabling typical payment-by-card transactions;

[0011] FIG. 2 is a simplified block diagram of a typical server architecture of a system that facilitates processing of electronic payments in accordance with one embodiment of the present disclosure;

[0012] FIG. 3 is an expanded block diagram of the typical system shown in FIG. 2 in accordance with one embodiment of the present disclosure;

[0013] FIG. 4 illustrates an exemplary configuration of a client system shown in FIGS. 2 and 3, in accordance with one embodiment of the present disclosure;

[0014] FIG. 5 illustrates an exemplary configuration of a server system shown in FIGS. 2 and 3, in accordance with one embodiment of the present disclosure;

[0015] FIG. 6 is a diagram of a consumer-to-merchant payment environment in accordance with one embodiment of the present disclosure;

[0016] FIG. 7 is a schematic diagram illustrating a conventional Internet based transaction;

[0017] FIGS. 8A and 8B are schematic diagrams illustrating exemplary screenshots and instructions for processing electronic payments in accordance with one embodiment of the present disclosure;

[0018] FIG. 9 is a flow chart illustrating an exemplary method for processing electronic payments in accordance with one embodiment of the present disclosure;

[0019] FIG. 10 is a flow chart illustrating an exemplary method for processing electronic payments in accordance with one embodiment of the present disclosure; [0020] FIG. 11 is a schematic diagram illustrating exemplary architecture in accordance with one embodiment of the present disclosure;

[0021] FIG. 12 is a screenshot of a conventional pre-checkout screen in accordance with one embodiment of the present disclosure;

[0022] FIG. 13 is a screenshot of a checkout screen as shown in FIG. 13 in accordance with one embodiment of the present disclosure;

[0023] FIG. 14 is a screenshot illustrating a quick response code in accordance with one embodiment of the present disclosure;

[0024] FIG. 15 is a schematic illustration of a mobile computer device scanning the quick response code shown in FIG. 14 in accordance with one embodiment of the present disclosure;

[0025] FIG. 16 is a schematic illustration of the mobile computer device shown in FIG. 15 reviewing the product shown in the screenshot in accordance with one embodiment of the present disclosure;

[0026] FIG. 17 is a schematic illustration of the mobile computer device shown in FIG. 15 paying for products shown in the screenshot in accordance with the present disclosure;

[0027] FIG. 18 is a schematic illustration of the mobile computer device shown in FIG. 15 completing a payment transaction for the product shown in the screenshot in accordance with one embodiment of the present disclosure;

[0028] FIG. 19 is a schematic illustration of a payment transaction for multiple sites with a single checkout using the mobile computer device shown in FIG. 15 in accordance with one embodiment of the present disclosure;

[0029] FIG. 20 is a schematic illustration of an electronic payment transaction using an electronic shopping cart in accordance with one embodiment of the present disclosure;

[0030] FIG. 21 is a schematic illustration of a payment transaction for a single product in accordance with one embodiment of the present disclosure; [0031] FIG. 22 is a schematic illustration of a computer device in communication with a third party social network;

[0032] FIG. 23 is a flow chart illustrating an exemplary method for sharing electronic commerce information to the third party social network shown in FIG. 19 in accordance with one embodiment of the present disclosure;

[0033] FIG. 24 is a flow chart illustrating an exemplary method for sharing electronic commerce information to a third party social network in accordance with one embodiment of the present disclosure; and

[0034] FIG. 25 illustrates exemplary screenshots of purchasing information displayed on a third party social network in accordance with one embodiment of the present disclosure.

DETAILED DESCRIPTION OF THE DRAWINGS

[0035] The following detailed description illustrates embodiments of the disclosure by way of example and not by way of limitation. It is contemplated that the disclosure has general application to processing financial transaction data by a third party in industrial, commercial, governmental and/or residential applications.

[0036] As used herein, an element or step recited in the singular and proceeded with the word "a" or "an" should be understood as not excluding plural elements or steps, unless such exclusion is explicitly recited. Furthermore, references to "example embodiment" or "one embodiment" of the present disclosure are not intended to be interpreted as excluding the existence of additional embodiments that also incorporate the recited features. Moreover, the term social media and/or third party social network can include computer networks combined with social networking software to produce a medium for social interaction. A relationship over a computerized social networking service can be characterized by context, direction, and strength. The content of a relation refers to the resource that is exchanged. In a computer mediated communication context, social pairs can exchange different kinds of information, including sending a data file or a computer program as well as providing emotional support or arranging a meeting. For electronic commerce, information exchanged may also correspond to exchanges of money, goods or services. [0037] Social media and/or third party social network can include computer- mediated tools that allow people to create, share or exchange information, ideas, and pictures/videos in virtual communities and networks. Social media is defined as "a group of Internet-based applications that build on the ideological and technological foundations of web based platforms or systems and that allow the creation and exchange of user-generated content. Furthermore, social media can depend on mobile and web-based technologies to create highly interactive platforms through which individuals and communities share, co-create, discuss, and modify user-generated content. They introduce substantial and pervasive changes to communication between businesses, organizations, communities, and individuals. These changes are the focus of the emerging field of techno self-studies. Social media differ from traditional or industrial media in many ways, including quality, reach, frequency, usability, immediacy and permanence. Social media can operate in a dialogic transmission system, (many sources to many receivers). This is in contrast to traditional media that operates under a mono-logic transmission model (one source to many receivers). In the embodiments described herein, social media or third party social networks can include, but is not limited to, Facebook, Twitter, Pinterest, Google, Tumblr, Qzone, Sina Weibo, VK, and YouTube.

[0038] Moreover, electronic commerce, also known as E-commerce for short, can include trading in products or services using computer networks, such as the Internet. Electronic commerce draws on technologies such as mobile commerce, electronic funds transfer, supply chain management, Internet marketing, online transaction processing, electronic data interchange, inventory management systems, and automate data collection systems.

[0039] The embodiments described herein relate to electronic financial transactions, specifically, commercial transactions between a consumer (payer) and a merchant (payee), and particularly through online transactions. Described in detail herein are exemplary embodiments of systems and processes that facilitate such electronic payments from an account associated with a payer to an account associated with a payee. The system described herein includes a computer device coupled to a memory device. The computer device and memory device are part of a payment network. A technical effect of the systems and processes described herein is achieved by performing at least one of the following steps: (a) locating, by the mobile computer device, a machine readable code; (b) receiving, by the mobile computer device, product information from the machine readable code; (c) decoding, by the mobile computer device, the machine readable code; (d) retrieving, by the mobile computer device, a validation token from a merchant associated with the product information; and (e) processing, by the mobile computer device, an electronic payment transaction based at least on the validation token for a product associated with the product information.

[0040] Another technical effect of the systems and processes described herein is achieved by performing at least one of the following steps: (a) conducting, by the computer device, an electronic commerce transaction; (b) storing, by the computer device, purchasing information, based on the electronic commerce transaction; (c) transmitting, by the computer device, the purchasing information to the third party social network; and (d) assigning, by the computer device, at least one loyalty credit based on the transmitted purchasing information.

[0041] In one embodiment, a computer program is provided, and the program is embodied on a computer readable medium. In an exemplary embodiment, the system is executed on a single computer system, without requiring a connection to a server computer. Alternatively, the system can be executed on multiple computer systems connected to a server computer and/or "Cloud" servers and/or computers. In a further exemplary embodiment, the system is being run in a Windows® environment (Windows is a registered trademark of Microsoft Corporation, Redmond, Wash.). In yet another embodiment, the system is run on a mainframe environment and a UNIX® server environment (UNIX is a registered trademark of X/Open Company Limited located in Reading, Berkshire, United Kingdom). The application is flexible and designed to run in various different environments without compromising any major functionality. In some embodiments, the system includes multiple components distributed among a plurality of computing devices. One or more components are in the form of computer- executable instructions embodied in a computer-readable medium. The systems and processes are not limited to the specific embodiments described herein. In addition, components of each system and each process can be practiced independent and separate from other components and processes described herein. Each component and process can also be used in combination with other assembly packages and processes.

[0042] In one embodiment, a computer program is provided, and the program is embodied on a computer readable medium and utilizes a Structured Query Language (SQL) with a client user interface front-end for administration and a web interface for standard user input and reports. In an exemplary embodiment, the system is web enabled and is run on a business-entity intranet. In yet another embodiment, the system is fully accessed by individuals having an authorized access outside the firewall of the business-entity through the Internet. In a further exemplary embodiment, the system is being run in the Windows® environment. The application is flexible and designed to run in various different environments without compromising any major functionality.

[0043] The term processor, as used herein, may refer to central processing units, microprocessors, microcontrollers, reduced instruction set circuits (RISC), application specific integrated circuits (ASIC), logic circuits, and any other circuit or processor capable of executing the functions described herein. As used herein, the terms "software" and "firmware" are interchangeable, and include any computer program stored in memory for execution by a processor, including RAM memory, ROM memory, EPROM memory, EEPROM memory, and non-volatile RAM (NVRAM) memory. The above memory types are exemplary only, and are thus not limiting as to the types of memory usable for storage of a computer program. Moreover, the terms user, payer, customer, and consumer are interchangeable and the terms vendor and merchant are interchangeable.

[0044] The embodiments described herein relate to a secure, trusted and one- touch/tap checkout process for the customer. The embodiments described herein provide for a payment system that simultaneously or nearly simultaneously transmits required payer information to a merchant without additional input from the payer. The embodiments described herein relate to an electronic checkout process which facilitates reducing electronic cart abandonment. The embodiments described herein facilitate impulse purchases, collect billing and shipping information while auto transmitting contact information. The embodiments described herein do not necessarily need any form of registration and can assimilate into existing ecommerce infrastructure with reduced and/or minimal change and disruption. The embodiments described herein facilitate: selling products off printed or electronic advertisements, direct mailings, catalogs; leveraging existing ecommerce infrastructure and investment to provide multi-channel shopping (online, mobile, and offline); sell durable goods in showrooms with ecommerce fulfillment; and sell off images on social media. The exemplary embodiments are not limited to a specific industry vertical and can be implemented on any digital or physical media to facilitate the electronic transaction. Media includes, but is not limited to, website (product or electronic shopping cart), physical catalog, digital or virtual catalog, printed and electronic media ads, email campaigns, banner advertisements, physical products and brick and mortar stores. [0045] FIG. 1 is a schematic diagram 20 illustrating an exemplary multi-party payment card industry system for enabling typical payment-by-card transactions in which historical transactions are utilized at least in part with an ensemble aggregate merchant prediction system. As utilized herein, aggregate merchant refers to a high level grouping of merchant locations. More specifically, the various individual merchant locations for a retailer are aggregated together (e.g., linked to one another in a database) to form an aggregate merchant. One merchant location is therefore a component of an aggregate merchant. Typically, an aggregate merchant is utilized when referring to a chain of stores and locations are aggregated together, as further described herein, based on a number of field values stored in a database of transaction data. The present disclosure relates to a payment card system, such as a credit card payment system using a network interchange for the exchange of financial transaction data between financial institutions that are members of the network.

[0046] In a typical payment card system, a financial institution called the "issuer" issues a payment card, such as a credit card, to a consumer, who uses the payment card to tender payment for a purchase from a merchant. To accept payment with the payment card, the merchant must normally establish an account with a financial institution that is part of the financial payment system. This financial institution is usually called the "merchant bank" or the "acquiring bank" or "acquirer bank." When a cardholder/consumer 22 tenders payment for a purchase with a payment card (also known as a financial transaction card), the merchant 24 requests authorization from the merchant bank 26 for the amount of the purchase. The request may be performed over the telephone, but is usually performed through the use of a point-of-sale terminal, which reads the consumer's account information from the magnetic stripe on the payment card and communicates electronically with the transaction processing computers of the merchant bank. Alternatively, a merchant bank may authorize a third party to perform transaction processing on its behalf. In this case, the point-of-sale terminal will be configured to communicate with the third party. Such a third party is usually called a "merchant processor" or an "acquiring processor." The merchant request to the merchant bank 26 can include a "chip" transaction technology.

[0047] Using the interchange 28, the computers of the merchant bank or the merchant processor will communicate with the computers of the issuer bank 30 to determine whether the consumer's account is in good standing and whether the purchase is covered by the consumer's available credit line. Based on these determinations, the request for authorization will be declined or accepted. If the request is accepted, an authorization code is issued to the merchant.

[0048] When a request for authorization is accepted, the available credit line of consumer's account 32 is decreased. Normally, a charge is not posted immediately to a consumer's account because bankcard associations have promulgated rules that do not allow a merchant to charge, or "capture," a transaction until goods are shipped or services are delivered. When a merchant ships or delivers the goods or services, the merchant captures the transaction by, for example, appropriate data entry procedures on the point-of-sale terminal. If a consumer cancels a transaction before it is captured, a "void" is generated. If a consumer returns goods after the transaction has been captured, a "credit" is generated.

[0049] After a transaction is captured, the transaction is settled between the merchant 24, the merchant bank 26, and the issuer 30. Settlement refers to the transfer of financial data or funds between the merchant's account, the merchant bank, and the issuer related to the transaction. Usually, transactions are captured and accumulated into a "batch," which transactions are settled as a group. Data that is associated with such transactions, as described further herein, is utilized in the art of predicting future purchasing activities.

[0050] Financial transaction cards or payment cards can refer for example only to credit cards, debit cards, and prepaid cards. These cards can all be used as a method of payment for performing a transaction. As described herein, the term "financial transaction card" or "payment card" includes cards such as credit cards, debit cards, and prepaid cards, but also includes any other devices that may hold payment account information, such as mobile phones, personal digital assistants (PDAs), and key fobs.

[0051] FIG. 2 is a simplified block diagram of the exemplary system 100 that facilitates processing of electronic payments in accordance with one embodiment of the present disclosure. In the exemplary embodiment, system 100 facilitates ensuring that a person attempting to use a transaction card or its corresponding account number is the legitimate cardholder. More specifically, in the exemplary embodiment, system 100 includes a server system 112 communicatively coupled to a plurality of client systems 114, also known as input devices. [0052] In the exemplary embodiment, client systems 114 are computers that include a web browser, which enable client systems 114 to access server system 112 using the Internet. More specifically, client systems 114 are communicatively coupled to the Internet through many interfaces including, but not limited to, at least one of a network, such as the Internet, a local area network (LAN), a wide area network (WAN), or an integrated services digital network (ISDN), a dial-up-connection, a digital subscriber line (DSL), and a cable modem. Client systems 114 can be any device capable of accessing the Internet including, but not limited to, a desktop computer, a laptop computer, a personal digital assistant (PDA), a cellular phone, a smartphone, or other web-based connectable equipment.

[0053] System 100 may also include an input or point-of-sale (POS) terminals 115, for example, a POS terminal and/or a cardholder workstation, which is connected to client systems 114 and may be connected to server system 112. Input terminals 115 may be interconnected to the Internet through a variety of interfaces including a network, such as a LAN or a WAN, dial-in-connections, cellular connections, cable modems, wireless modems, and special high-speed ISDN lines. Input terminals 115 may be any device capable of interconnecting to the Internet to provide transaction card information to client systems 114 and/or server system 112.

[0054] A database server 116 is communicatively coupled to a database 120 that contains a variety of information including, but not limited to, a name of a cardholder, an account number, a transaction history, a billing address, a shipping address, the cardholder's date of birth, telephone number(s) associated with the cardholder (e.g., a mobile, work, or home telephone number), email addresses associated with the cardholder, and other cardholder-related information. Moreover, the database 120 can include multiple account numbers associated with a single cardholder. More specifically, a cardholder may be issued multiple transaction cards. Database 120 may store the multiple transaction card numbers associated with the single cardholder. In addition, each particular account number can have its own corresponding set of information specific to the particular account number. For example, different account numbers can have different shipping addresses associated therewith. In the exemplary embodiment, database 120 is stored remotely from server system 112. In some embodiments, database 120 is decentralized. In the exemplary embodiment, a person can access database 120 via client systems 114 by logging onto server system 112. [0055] In the example embodiment, server system 112 may be associated with an interchange network, and may be referred to as an interchange computer system. Additionally, a check out platform may be associated with the interchange network. Server system 112 may be used for processing transaction data and for registering cardholders and/or merchants into a plurality of programs offered by the interchange network, including, but not limited to, an express check out program. In addition, at least one of client systems 114 may include a computer system associated with an issuer of a transaction card. Accordingly, server system 112 and client systems 114 may be utilized to process transaction data relating to purchases made by a cardholder utilizing a transaction card that is processed by the interchange network and issued by the associated issuer. Another client system 114 may be associated with a user or a cardholder seeking to register, access information, or process a transaction with at least one of the interchange network, the issuer, or the merchant.

[0056] FIG. 3 is an expanded block diagram of the exemplary system 100. System 100 includes server system 112, client systems 114 and input terminals 115. Server system 112 further includes database server 116, an application server 124, a web server 126, a fax server 128, a directory server 130, and a mail server 132. A disk storage unit 134 is coupled to database server 116 and directory server 130. Servers 116, 124, 126, 128, 130, and 132 are coupled in a local area network (LAN) 136. In addition, a system administrator's workstation 138, a user workstation 140, and a supervisor's workstation 142 are coupled to LAN 136. Alternatively, workstations 138, 140, and 142 are coupled to LAN 136 using an Internet link or are connected through an intranet.

[0057] Each workstation, 138, 140, and 142 is a personal computer having a web browser. Although the functions performed at the workstations typically are illustrated as being performed at respective workstations 138, 140, and 142, such functions can be performed at one of many personal computers coupled to LAN 136. Workstations 138, 140, and 142 are illustrated as being associated with separate functions only to facilitate an understanding of the different types of functions that can be performed by individuals having access to LAN 136.

[0058] Server system 112 is configured to be communicatively coupled to various individuals, including employees 144 and to third parties, e.g., account holders, customers, auditors, etc., 146 using an ISP Internet connection 148. The communication in the exemplary embodiment is illustrated as being performed using the Internet, however, any other WAN type communication can be utilized in other embodiments, i.e., the systems and methods described herein are not limited to being practiced using the Internet. In addition, and rather than WAN 150, local area network 136 could be used in place of WAN 150.

[0059] In the exemplary embodiment, any authorized individual having a workstation 154 can access system 100. At least one of the client systems includes a manager workstation 156 located at a remote location. In one embodiment, workstations 154 and 156 are personal computers having a web browser. Also, workstations 154 and 156 are configured to communicate with server system 112. Furthermore, fax server 128 communicates with remotely located client systems, including a client system 146 using a telephone link. Fax server 128 is configured to communicate with other workstations 138, 140, and 142 as well.

[0060] As used herein, the terms "software" and "firmware" are interchangeable, and include any computer program stored in memory for execution by personal computers, workstations, clients, and servers, including RAM memory, ROM memory, EPROM memory, EEPROM memory, and non-volatile RAM (NVRAM) memory. The above memory types are exemplary only, and are thus not limiting as to the types of memory usable for storage of a computer program.

[0061] FIG. 4 illustrates an exemplary configuration of a user computer device 202 operated by a user 201 for system 100. User computer device 202 may include, but is not limited to, client systems 114, 138, 140, and 142, POS terminals 115, workstation 154, and manager workstation 156. User computer device 202 includes a processor 205 for executing instructions. In some embodiments, executable instructions are stored in a memory area 210. Processor 205 may include one or more processing units (e.g., in a multi-core configuration). Memory area 210 is any device allowing information such as executable instructions and/or transaction data to be stored and retrieved. Memory area 210 may include one or more computer readable media.

[0062] User computer device 202 also includes at least one media output component 215 for presenting information to user 201. Media output component 215 is any component capable of conveying information to user 201. In some embodiments, media output component 215 includes an output adapter (not shown) such as a video adapter and/or an audio adapter. An output adapter is operatively coupled to processor 205 and operatively coupleable to an output device such as a display device (e.g., a cathode ray tube (CRT), liquid crystal display (LCD), light emitting diode (LED) display, or "electronic ink" display) or an audio output device (e.g., a speaker or headphones). In some embodiments, media output component 215 is configured to present a graphical user interface (e.g., a web browser and/or a client application) to user 201. A graphical user interface may include, for example, an online store interface for viewing and/or purchasing items, and/or a wallet application for managing payment information.

[0063] In some embodiments, user computer device 202 includes an input device 220 for receiving input from user 201. User 201 may use input device 220 to select and/or enter, without limitation, one or more items to purchase, a purchase request, access credential information, and/or payment information. Input device 220 may include, for example, a keyboard, a pointing device, a mouse, a stylus, a touch sensitive panel (e.g., a touch pad or a touch screen), a gyroscope, an accelerometer, a position detector, a biometric input device, and/or an audio input device. A single component such as a touch screen may function as both an output device of media output component 215 and input device 220. User computer device 202 may also include a communication interface 225, which is communicatively coupleable to a remote device such as server system 112. Communication interface 225 may include, for example, a wired or wireless network adapter and/or a wireless data transceiver for use with a mobile telecommunications network.

[0064] Stored in memory area 210 are, for example, computer readable instructions for providing a user interface to user 201 via media output component 215 and, optionally, receiving and processing input from input device 220. A user interface may include, among other possibilities, a web browser and/or a client application. Web browsers enable users, such as user 201, to display and interact with media and other information typically embedded on a web page or a website from server system 112. A client application allows user 201 to interact with a server application of a merchant computer system, POS terminals 115, and/or server system 112.

[0065] FIG. 5 illustrates an exemplary configuration of a server computer device 301 such as server system 112 (shown in FIG. 2) for use with the system 100. Server computer device 301 may include, but is not limited to, a merchant computer system, POS terminals 115, database server 116, application server 124, web server 126, fax server 128, directory server 130, and/or mail server 132. Server computer device 301 also includes a processor 305 for executing instructions. Instructions may be stored in a memory area 310, for example. Processor 305 may include one or more processing units (e.g., in a multi-core configuration). Processor 305 is operatively coupled to a communication interface 315 such that server computer device 301 is capable of communicating with a remote device such as user computer device 202 or another server computer device 301. For example, communication interface 315 may receive requests from user computer device 114 via the Internet, as illustrated in FIG. 3.

[0066] Processor 305 may also be operatively coupled to a storage device 134. Storage device 134 is any computer-operated hardware suitable for storing and/or retrieving data, such as, but not limited to, data associated with database 120. In some embodiments, storage device 134 is integrated in server computer device 301. For example, server computer device 301 may include one or more hard disk drives as storage device 134. In other embodiments, storage device 134 is external to server computer device 301 and may be accessed by a plurality of server computer devices 301. For example, storage device 134 may include multiple storage units such as hard disks and/or solid state disks in a redundant array of inexpensive disks (RAID) configuration. Storage device 134 may include a storage area network (SAN) and/or a network attached storage (NAS) system.

[0067] In some embodiments, processor 305 is operatively coupled to storage device 134 via a storage interface 320. Storage interface 320 is any component capable of providing processor 305 with access to storage device 134. Storage interface 320 may include, for example, an Advanced Technology Attachment (ATA) adapter, a Serial ATA (SATA) adapter, a Small Computer System Interface (SCSI) adapter, a RAID controller, a SAN adapter, a network adapter, and/or any component providing processor 305 with access to storage device 134.

[0068] FIG. 6 is a simplified block diagram of an environment 400 of the present disclosure in which a method for processing electronic payments using a global payment directory is implemented in conjunction with or using at least one of the system 100, the server 1222, the computer device 202, and the server computer device 301. Environment 400 includes a payee (merchant) 402 and a payer (consumer) 404, both of which are connected (or connectable) to payment system 406, either directly or indirectly, through and/or using any of the mechanisms illustrated in FIGS. 1-5 as described herein. Consumer 404 will have associated with it at least one payment source account (or "consumer payment account"), from which payments to merchant 402 will be debited. Payment system 406 preferably additionally communicates with financial institution(s) 410, using the interchange systems as described herein. In the exemplary embodiment, the payment system 406 can include, individually or in combination, a computer device and a mobile computer device (for example a mobile smart phone).

[0069] FIG. 7 is a schematic diagram illustrating a conventional Internet or ecommerce based process. More particularly, the ecommerce process includes a registration screenshot 414 where the user enters their user name and password, register as a customer or checkout as a guest. The ecommerce process further includes the user providing an address 416. The user can also provide shipping instructions 418 including a shipping address 420. The ecommerce process further includes a payment section 422 wherein the user provides payment information such as credit information. The ecommerce process may further include a complete/confirmation section 424. The ecommerce process, however, may take time while subjecting the payer's personal and/or credit information to numerous merchant databases which may lead to fraud or security concerns.

[0070] FIG. 8 is a schematic diagram illustrating screenshots and instructions for processing electronic payment transactions by the payment system 406. The payment system 406 is configured to process ecommerce transactions between the payer 404 and a point of sale 426 of the merchant 402. In the exemplary embodiment, the payment system 406 includes an electronic application 428 coupled to the mobile computer device such as, but not limited to, a mobile phone or electronic tablet. Electronic application 428, which for reference is labeled MRTKPAY and/or MRKTPAY APP and/or MRKTPAY application and/or MRKTPAY System in the figures, is configured to electronically interact with the payment system 406. The point of sale 426 includes, but is not limited to, ecommerce websites (desktops and mobile), printed catalogs, physical products and/or packaging, advertising, and mail campaigns. The point of sale 426 can include any online interface or offline interface to enable the payment system 406 to conduct electronic transactions.

[0071] In the exemplary embodiment, the point of sale 426 includes a machine readable code 432 such as, for example only, a quick read code, known as a "QR" code. The QR code 432 includes machine readable information relating to the product and/or service offered by the merchant 402. The machine readable information can include for example a stock keeping unit ("SKU") number. The QR code 432 enables a single code regardless of the physical device used. Moreover, the QR code 432 is presented by the computer device 429 as a desktop web page. In another embodiment, the QR code 432 is presented by the computer device as a mobile web page. Alternatively, the QR code 432 is coupled to a physical object such as, but not limited, a product, advertising material, printed material (for example a label). Alternatively, the QR code 432 can include any type of code and/or architecture to enable the payment system 406 to function as described herein.

[0072] More particularly, in the exemplary embodiment, the QR Code 42 that is surfaced on a desktop or screen of mobile computer device 429 contains a URL that is configured so that if the user 404 uses a third party QR scanner, the link opens to a product page on a website associated with the MRKTPAY application 428 with a call-to-action for the user 404 to download and install the application 428. Alternatively, if the user scans for example a barcode or QR code 432 from within the MRKTPAY application 428, the application 428 is configured to decode the URL query string which contains at least one of the following information:

[0073] For creation of the QR code 432, in an embodiment, the browser calling an API on a server of the MRKTPAY application 428 creates the QR code 432. In an embodiment, the creation is standard "img" call the call returns a .PNG image that contains the QR code 432. Additional attributes that can be called include at least one of a size (for example, small, medium large, extra-large), color, embed logo? - Yes/No.

[0074] For validation of the QR code 432, in an embodiment, the MRKTPAY application 428 is configured to decode the QR code 432 and verify the QR code 432 for compliant information. More particularly, when a QR scanner in the MRKTPAY application 428 scans the QR code 432, the application 428 is configures to validate the following:

1 - Is the embedded URL have the correct host and URL structure?

2 - If yes, is the client ID a valid MRKTPAY client ID. 3 - If yes, is the product ID a valid product ID for that customer

[0075] The application 428 is configured to conduct a format check as well as a compliance check. If any of these tests fail, the user 404 is shown the appropriate error message by the mobile computer device 429.

[0076] The payment system 406 is configured to electronically link or connect to the merchant's or vendor's electronic commerce system to the mobile computer device application 428 to facilitate a single, efficient, and secure process for confident and complete electronic payment transaction. Upon completion of the electronic payment transaction, the payment system 406 is configured to transmit authorization information electronically to the payer's mobile computer device 429 to facilitate fulfillment by the appropriate vendor/merchant channels.

[0077] For the embodiment of a website accessed and/or viewed by the mobile computer device 429, the payments system is configured to electronically and automatically launch by a switching feature which is configured to link automatically to the mobile computer device 429 which is touched or tapped 434 by the payer 404. The payment system 406 is configured to commence a purchase process via the website, printed material, and/or physical product. The payment system 406 is configured to process and complete the electronic transaction using the personal mobile computer device 429 which may include a secure "one-touch" mechanism that simultaneously transmits all required information to the merchant 402 without additional input from the user 404. More particularly, the payment system 406 includes the mobile application 428 for mobile smart phones and tablet devices that receive and present transaction data to the user 404 and integrates with third party digit wallet systems and solutions 434, for example only, such as Apple Pay™. The payment system 406 and electronic application 428 can interact with any type of third party payment system and/or third party digital wallet systems and solutions. Moreover, the payment system 406 includes computer code that provides functionality to an ecommerce system used by the merchant 402 to enable the mobile application to receive information pertinent to the transaction in process. An infrastructural system is configured to bridge between the mobile application, payment gateway systems, and the ecommerce system.

[0078] In the exemplar embodiment, the user 404 downloads and installs the application for the payment system 406 from the merchant/repository application to the operating system of the mobile computer device 429. The user 404 can visit and/or access a website of a participating point of sale 426 by desktop, on the mobile computer device, and/or on the physical product or advertisement. For the desktop or mobile computer device, the user 404 can either add one or more products to an electronic shopping cart or navigate to a product/service for purchase.

[0079] For the desktop website, when the user 404 is ready to purchase or checkout, the user 404 clicks the respective link on the website to access the interface that presents the QR code 432. As noted, the QR code 432 contains respective information about the transaction, for example the product/service SKU or other descriptions. The QR code 432 contains information such as all the number of products placed in the electronic shopping cart with the quantity that the user 404 has selected. The mobile computer device is configured to electronically receive the production information from the QR code 432. More particularly, the mobile computer device 429 is configured to electronically scan the QR code 432.

[0080] For the mobile computer device website, when the user 404 is ready to checkout or purchase the product/service, the user 404 clicks or accesses the respective link on the mobile website. The payment system 406 is activated or launches using the URL scheme protocol. In the exemplary embodiment, a query string of the URL protocol includes information about the electronic transaction, for example the products or the services as described in the QR code 432.

[0081] For the retail transactions such as a brick mortar store, the merchant places the product or associated advertising to depict the QR code 432, for example on a label. When the user 404 is ready to purchase the product/service, the user 404 scans the QR code 432 using, for example, the mobile computer device 429 and the associated information such as the SKU number of the product/service to receive the production information. The transaction is then completed via the vendor's ecommerce system without any modifications there-to.

[0082] For the desktop website, the mobile website, and the retail store, where the mobile computer device 429 receives the associated information from the QR code 432, the payment system 406 is configured to acquire product/cart information from the ecommerce system of the merchant 402. The payment system 406 is configured to activate and use a digital system such as, but not limited to, Apple Pay™, to authorize and complete the transaction. [0083] FIGS. 9 and 10 are flow charts illustrating a method for electronic transactions using the payment system 406. In the exemplary embodiment, the user 404 installs 1002 the payment system 406 on the mobile computer device 429. The mobile computer device accesses 1004 at least one of the desktop website, the mobile website, and the physical product and locates the QR code 432. The mobile computer device 429 electronically reads 1006 the QR code 432 such as by, for example, scanning the QR code 432 at least one desktop website, the mobile website, and the physical product for receiving the product information from the QR code 432. The payment system 406 validates 1008 the QR code 432. If the QR code 432 is not validated 1010, the payment system 406 generates an error signal and prompts the user 404 to recheck the QR code 432 and/or access another QR code 432.

[0084] Once the payment system 406 has validated the QR code 432, the payment system 406 decodes 1012 the QR code 432. In the exemplary embodiment, the payment system 406 decodes information such as, but not limited to, merchant identification, a transaction type, and an item identifier. The payment system 406 retrieves 1014 a validation token from the merchant 402. The payment system 406 can also return 1016 the validation token to the merchant 402. The payment system 406 sends 1018 a query to the merchant back-end system where the merchant receiver receives the query and validates 1020 the request. The merchant ecommerce system retrieves 1022 the product/service information. In an embodiment, the token is validated only during the payment process and is independent of the merchant 402 and the product. For PCI requirements, the application 428 is configured to not collect for example the user's credit card information. The third party system or solution may provide the token validation. That token process can include: the user 404 initiates payment for the product by using fingerprint technology on the TouchID sensor on the mobile computer device 429; the third party system/solution framework transmits the request to its servers with no visibility to the application 428; the third party system/solution server validates the card information and the mobile computer device 429 and transmits back a single-use token; the token is sent to the payment provider who then use it to open an encrypted communication directly with Apple's servers to retrieve the payment information; the payment provider authorizes and captures the payment; if the payment is authorized, the payment provider returns a successful charge ID; if the payment is declined, the payment provider returns an error message which is then shown to the user 404; and/or, if the payment is successful, the MRKTPAY application 428 is configured to place the order directly with the merchant's commerce system providing the buyer's details, with the product/s being ordered and the charge ID returned from the payment gateway. [0085] In the exemplary embodiment, the payment system 406 receives the merchant data and formats 1024 the merchant data for visual use. The mobile computer device 429 presents 1026 the data such as the product information to the user 404. When the user 404 receives 1028 the data, the payment system 406 can prompt 1030 the user 404 for any discount codes.

[0086] If the user 404 has a discount code, the payment system 406 transmits 1032, the discount code to the merchant 402. In response, the merchant 402 updates 1034 information such as the price of the product/service. In the exemplary embodiment, the payment system 406 updates 1036 the quantity of products purchased and variable product dimensions, if any. Moreover, the payment system 406 updates 1038 the pricing. The payment system 406 processes the electronic payment transaction using the application 428 and the mobile computer device 429 based at least on the validation token for the product/service associated with the product information retrieved from the QR code 432. Additionally, during the processing, the payment system 406 can transmit via the mobile computer device 429 the payer's contact information.

[0087] The user 404 taps 1040 the screen of the mobile computer device 429 to activate the third party payment system such as, for example only, the Apple Pay™ system. The third party payment system presents 1042 a summary sheet to the screen of the mobile computer device 429, the user 404 can pay 1044 for the transaction by touching a "pay" icon presented on the mobile computer device screen.

[0088] The third party payment system receives the payment request and analyze for approval 1046. If the payment request is received but not approved by the third party payment system, the third party payment system transmits 1048 an error signal to the mobile computer device 429. If the payment request is received and approved by the third party payment system, the third party payment system sends 1050 the payment token order information to a payment gateway for further processing 1052 such as by a credit card network. If the credit card network does not authorize the payment processing, then the credit card network generates a signal and sends 1054 the error signal to the mobile computer device 429.

[0089] FIG. 11 is a schematic illustrating architecture and representative screenshots and sequence steps by the payment system 406 for conducting ecommerce transactions. FIGS. 12-21 are representative screenshots and the mobile computer device 429 employing the payment system 406. More particularly, the payment system 406 is configured to generate the QR code 432. The mobile computer device 429 is further configured to scan the QR code 432 to receive the product information provided by the QR code 432. The mobile computer device presents the product information to the user 404. The user 404 activates the mobile computer device 429 to pay for the product. The electronic payment transaction is processed and finalized by payment system 406 and associated application 428 for a convenient, secure, and efficient transaction.

[0090] FIG. 22 is a schematic illustration of the user computer device 202 and/or user mobile computer device 429 operatively coupled to a third party social network 2100. FIGS. 23 and 24 are flow charts illustrating a method 2200 for sharing electronic commerce information 2102 between the computer device 202 and the third party social network 2100. FIG. 25 illustrates exemplary screenshots 2104 of purchasing information 2106 displayed on the third party social network 2100.

[0091] Subsequent to conducting 2202 the electronic commerce transaction, the computer device 202 is configured to store 2204 purchasing information 2106 associated with the electronic commerce transaction to the third party social network 2100. In the exemplary embodiment, the purchasing information 2106 includes at least one of a product information relating to a purchased product and/or a service information relating to a purchased service. In an embodiment, before finalizing the electronic commerce transaction, the computer device 202 can store or cache the purchasing information 2106, for example, in an electronic shopping cart (not shown).

[0092] The user accesses or "taps" either on an order completion screen presented by the computer device 202 or a platform such as, but not limited to, a Wish List/Bookmark/Favorite list screen or a Shopping Cart screen. On the order completion screen or the Wish List/Bookmark/Favorite list screen or the Shopping Cart screen, the computer device 202 presents a plurality of social networks 2100 to the user 404, wherein the user 404 selects one or more of the social networks 2100. The computer device 202 is configured to transmit 2206 the purchasing information 2106 that is associated with the electronic commerce transaction and/or associated with the stored purchasing information 2106 or the product(s) information from the Wish List/Bookmark/Favorite list screen or the Shopping Cart screen to the selected third party social network 2100. In an embodiment, the user 404 can purchase product(s) from the platform for example Bookmark and/or post products to social network(s) and/or delete product(s) from the Bookmark and/or the social network 2100. The system 406 includes a multi- retailer order history/summary (order summary) where the user can have access to all orders created via system 406, grouped by the retailer/merchant, and selectively sorted such as by sorted by most recent order. The user 404 can have the ability to re-order a product(s) and/or return a product(s) which can initiate a transaction on the retailer's ecommerce system. The system can further include a Lookbook feature where a retailer will have the ability to put together a group of products. The user 404 can purchase the entire "look" or remove any product the user 404 does not want from the shopping cart. Moreover, the user 404 can purchase any remaining product(s) in a single-click ecommerce transaction.

[0093] In an embodiment, the Bookmark and/or Lookbook includes a Uniform Resource Identifier that is stored for later retrieval in any of various storage formats. The Bookmarks can be accessed through a menu in the user's web browser, and folders can be used for organization. Social bookmarking service includes a centralized online service which enables users to add, annotate, edit, and share bookmarks of web documents. In an embodiment, "tagging" can be incorporated wherein "tagging" is configured to enable users to organize their bookmarks in flexible ways and develop shared vocabularies. Lookbook can include an electronic collection or catalog of information such as, but not limited to, photographs of a person, company, product line (for example, a clothing line), and a style for example of the user 404.

[0094] In an embodiment, the computer device 202 is configured to generate an image 2108 based on or associated with the transmitted purchasing information 2106. In the exemplary embodiment, the generated image 2108 includes at least one of a product image 2108, a service image 2108, a retailer logo, and a machine readable code such as, but not limited to, a QR code 2110. In an embodiment, the machine readable code is associated with the QR code 432 of the payment system 406 as previously described. Moreover, the generated image 2108 is transmitted to the third party social network 2100 by the computer device 202. In an embodiment, the transmitted purchasing information 2106 and the transmitted image 2108 can include the same transmission from the computer device 202 and to the third party social network 2100.

[0095] In the exemplary embodiment, when the computer device 202 transmits the image 2108 to the selected social network 2100, the transmitted image 2108 along with a URL link is posted to the user's selected social network 2100 feed and can be visited by at least one of the user's followers/friends 2112 associated with the user's social network 2100. Accordingly, the social network 2100 retrieves the transmitted purchasing information 2106 and/or image 2108 from the URL, and presents or displays the same to the user's followers/friends 112.

[0096] The user's followers/friends 2112 can use the electronic payment system 406 for example by scanning the QR code 2110 on the image 2108 posted on the social network 2100 site. Moreover, the followers/friends 2112 can buy the products/services associated with the purchasing information 2106 via the electronic payment system 406 as previously described. More particularly, the user's followers/friends 2112 can view the image 2108 on the respective social network 2100 on the computer device 202/429 (for example, the mobile phone or electronic tablet device) and tap or access the image 2108 to launch the electronic payment system 406 as previously described. Accordingly, the user's followers/friends 2112 can purchase the products/services associated with the purchasing information 2106, as transmitted by the user's computer device 202, without directly accessing the retailer' s website or point of sale 426.

[0097] In an embodiment, the computer device 202 is operatively coupled to and configured to interact with a computer device 2114 of a retailer's loyalty reward program 2116. The specific features for retailer royalty rewards can be optional when using system 406 and can be bypassed if a retailer does not opt-in for the functionality. The computer device 202 includes assigning 2208 as least one loyalty credit 2118 to the user 404, wherein the loyalty credit 2118 is based at least on the transmitted purchasing information 2106 and/or image 2108. For example, when the computer device 202 transmits the purchasing information 2106 of a particular retailer (online and/or brick and mortar retailer) to the third party social network 2100, the computer device 202 is configured to communicate the transmitted purchasing information 2106 to the computer device 2114 of the retailer's loyalty reward program 2116. The computer device 202 of the retailer's loyalty reward program 2116 generates an award value 2120 based on the at least one loyalty credit 2118. The retailer's computer device 2114 is configured to transmit the award value 2120 to the computer device 202. The computer device 202 is configured to receive the award value 2120 for storage and/or processing based on the loyalty reward program 2116.

[0098] The computer device 202 is configured to monitor the social network 2100 for third party interactions such as whether the user's followers/friends 2112 initiate a subsequent electronic commerce transaction 2122 in response to the transmitted purchasing information 2106 and/or transmitted image 2108.

[0099] In the exemplary embodiment, the at least one loyalty credit 2118 can be assigned by the computer device 202 for the transmitted purchasing information 2106 regardless if the user's followers/friends 2112 access the purchasing information 2106 and/or image 2108 from the third party social network 2100. If the followers/friends 2112 access the transmitted purchasing information 2106 and/or image 2108, then the computer device 202 can assign another loyalty credit 2118 to the user 404 for future processing by the retailer's loyalty reward program 2116. Moreover, if the user's followers/friends 2112 purchase a product/server based on the transmitted purchasing information 2106 and/or image 2108, the computer device 202 can assign another loyalty credit 2118 to the user 404 for future processing by the retailer's loyalty reward program 2116. Accordingly, the computer device 202 includes a multiparty/multi-retail ecommerce based loyalty system. In the exemplary embodiment, the computer system 202 is configured to facilitate peer-to-peer social ecommerce among the user 404 and the user's followers/friends 2112.

[0100] The systems and processes are not limited to the specific embodiments described herein. In addition, components of each system and each process can be practiced independent and separate from other components and processes described herein. Each component and process also can be used in combination with other assembly packages and processes.

[0101] Having described aspects of the disclosure in detail, it will be apparent that modifications and variations are possible without departing from the scope of aspects of the disclosure as defined in the appended claims. As various changes could be made in the above constructions, products, and methods without departing from the scope of aspects of the disclosure, it is intended that all matter contained in the above description and shown in the accompanying drawings shall be interpreted as illustrative and not in a limiting sense. For example, the example embodiments described herein relate to electronic payment for completion of an online transaction between a consumer and a merchant. In an alternative embodiment, the transaction may be at least partially conducted at a merchant's brick-and-mortar facility. In another alternative embodiment, the transaction may be conducted between two merchants. In still another alternative embodiment, the transaction may be conducted between two consumers. [0102] While the disclosure has been described in terms of various specific embodiments, those skilled in the art will recognize that the disclosure can be practiced with modification within the spirit and scope of the claims. As will be appreciated based on the foregoing specification, the above-described embodiments of the disclosure may be implemented using computer programming or engineering techniques including computer software, firmware, hardware or any combination or subset thereof. Any such resulting program, having computer- readable code means, may be embodied or provided within one or more computer-readable media, thereby making a computer program product, i.e., an article of manufacture, according to the discussed embodiments of the disclosure. The computer-readable media may be, for example, but is not limited to, a fixed (hard) drive, diskette, optical disk, magnetic tape, semiconductor memory such as read-only memory (ROM), and/or any transmitting/receiving medium such as the Internet or other communication network or link. The article of manufacture containing the computer code may be made and/or used by executing the code directly from one medium, by copying the code from one medium to another medium, or by transmitting the code over a network.

[0103] The above-described embodiments of methods and systems of transacting payer to payee payments provide an improved mechanism for facilitating a transaction but without requiring a merchant or other payer to store and/or transmit sensitive consumer data, and advantageously storing consumer data in a centralized location. As a result, the methods and systems described herein facilitate completion of transactions and performance of electronic payments with increased security.

[0104] This written description uses examples to disclose the disclosure and also to enable any person skilled in the art to practice the disclosure, including making and using any devices or systems and performing any incorporated methods. The patentable scope of the disclosure is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements with insubstantial differences from the literal languages of the claims.

Claims

WHAT IS CLAIMED IS:

1. A computer- implemented method for facilitating an electronic payment to a payee from a payer, the computer-implemented method using a mobile computer device coupled to a memory device, the computer-implemented method comprising: locating, by the mobile computer device, a machine readable code; receiving, by the mobile computer device, product information from the machine readable code; decoding, by the mobile computer device, the machine readable code; retrieving, by the mobile computer device, a validation token from a merchant associated with the product information; and processing, by the mobile computer device, an electronic payment transaction based at least on the validation token for a product associated with the product information.

2. The computer- implemented method of Claim 1, wherein locating the machine readable code comprises electronically scanning at least one of a desktop web page, a mobile computer device web page, an advertisement, and a product.

3. The computer-implemented method of Claim 1, wherein receiving the product information comprises electronically scanning the machine readable code.

4. The computer- implemented method of Claim 1, wherein decoding the machine readable code comprises decoding at least one of a merchant identification, a transaction type, and a product identifier.

5. The computer-implemented method of Claim 1, wherein the machine readable code comprise a quick response code.

6. The computer-implemented method of Claim 1, wherein the machine readable code is presented by the computer device on a desktop web page.

7. The computer-implemented method of Claim 1, wherein the machine readable code is presented by the computer device on a mobile web page.

8. The computer-implemented method of Claim 1, wherein the machine readable code is coupled to a physical object including at least one of the product and advertising material.

9. The computer- implemented method of Claim 1, further comprising validating, by the mobile computer device, the validity of the machine readable code.

10. The computer- implemented method of Claim 1, further comprising transmitting, by the mobile computer device, contact information when processing the electronic payment transaction.

11. The computer- implemented method of Claim 1, further comprising collecting, by the mobile computer device, at least one of billing information and a shipment information.

12. The computer- implemented method of Claim 1, wherein receiving, by the mobile computer device, product information from the machine readable code comprises receiving a plurality of production information relating to a plurality of different products stored in an electronic shopping cart.

13. The computer- implemented method of Claim 1, wherein receiving, by the mobile computer device, product information from the machine readable code comprises receiving the product information for the product from a plurality of web pages.

14. A computer-implemented method for facilitating an electronic payment to a payee from a payer, the method implemented using a computer device coupled to a memory device, the method comprising: inputting, by the computer device, product information into a machine readable code; storing, by the computer device, the machine readable code in the memory device; presenting, by the computer device, in visual form the machine readable code to a mobile computer device; receiving a request from the mobile computer device for access to the product information from the machine readable code; and transmitting, by the computer device, the product information from the machine readable code and to the mobile computer device for conducting electronic payment transactions for a product associated with the product information.

15. A mobile computer system for facilitating electronic payments to a payee from a payer, the mobile computer system comprising: a processor; and a computer-readable storage device, wherein said computer system is associated with an interchange network and the computer-readable storage device has encoded thereon computer-executable instructions that are executable by the processor to perform functions comprising: locating, by the mobile computer device, a machine readable code; receiving, by the mobile computer device, product information from the machine readable code; decoding, by the mobile computer device, the machine readable code; retrieving, by the mobile computer device, a validation token from a merchant associated with the product information; and processing, by the mobile computer device, an electronic payment transaction based at least on the validation token for a product associated with the product information.

16. One or more non-transitory computer-readable storage media having computer- executable instructions embodied thereon for facilitating electronic payments to a payee from a payer, wherein, when executed by at least one processor of a computer device, the computer- readable instructions cause the processor to: locate, by the mobile computer device, a machine readable code; receive, by the mobile computer device, product information from the machine readable code; decode, by the mobile computer device, the machine readable code; retrieve, by the mobile computer device, a validation token from a merchant associated with the product information; and process, by the mobile computer device, an electronic payment transaction based at least on the validation token for a product associated with the product information.

17. A computer-implemented method for sharing electronic commerce information to a third party social network, the computer-implemented method using a computer device coupled to a memory device, the computer-implemented method comprising: conducting, by the computer device, an electronic commerce transaction; storing, by the computer device, purchasing information associated with the electronic commerce transaction; transmitting, by the computer device, the purchasing information to the third party social network; and assigning, by the computer device, at least one loyalty credit based on the transmitted purchasing information.

18. The computer-implemented method of Claim 17, wherein the purchasing information comprises at least of one product information and a service information.

19. The computer-implemented method of Claim 17, further comprising generating, by the computer device, an image based on the transmitted purchasing information.

20. The computer-implemented method of Claim 19, further comprising transmitting, by the computer device, the image to the third party social network.

21. The computer-implemented method of Claim 19, wherein the generated image comprises at least one of a product image, a service image, a retailer logo, and a machine readable code.

22. The computer-implemented method of Claim 19, wherein the generated image comprises a quick response code.

23. The computer- implemented method of Claim 22, wherein the quick response code is associated with an electronic payment system.

24. The computer-implemented method of Claim 17, further comprising monitoring, by the computer device, whether a subsequent electronic commerce transaction is initiated in response to the transmitted purchasing information.

25. The computer-implemented method of Claim 24, further comprising awarding, by the computer device, an additional at least one loyalty credit in response to the subsequent commerce transaction.

26. The computer implemented method of Claim 17, further comprising storing, by the computer device, the at least one loyalty credit.

27. The computer implemented method of Claim 17, further comprising accessing, by the computer device, a platform comprising at least one of a wish list, a Bookmark, and a favorite list and transmitting information relating to purchased products from the respective platform to the third party social network.

28. The computer implemented method of Claim 27, further comprising deleting, by the computer device, the purchased product information from the platform comprising the at least one of the wish list, the Bookmark, and the favorite list.

29. The computer implemented method of Claim 17, further comprising sorting, by the computer device, a multi-retailer order history/summary relating to an order summary of products.

30. The computer implemented method of Claim 29, further comprising providing access, by the computer device, of an order created which is grouped by a retailer and sorted by an order date.

31. The computer implemented method of Claim 30, wherein the order date comprises a most recent order.

32. The computer implemented method of Claim 30, further comprising providing, by the computer device, access to at least one of re-ordering a product and returning a product to initiate an electronic transaction on a retailer's ecommerce system.

33. The computer implemented method of Claim 17, further comprising accessing, by the computer device, a platform comprising a Lookbook which includes a retailer feature of putting together a group of products which a user can then purchase the entire look of products or remove products from an electronic shopping cart.

34. The computer implemented method of Claim 33, further comprising providing, by the computer device, access to the user to purchase the remaining products in a single ecommerce transaction.

35. A mobile computer system for sharing electronic commerce information to a third party social network, the mobile computer system comprising: a processor; and a computer-readable storage device, wherein said computer system is associated with an interchange network and the computer-readable storage device has encoded thereon computer-executable instructions that are executable by the processor to perform functions comprising: conducting, by the computer device, an electronic commerce transaction; storing, by the computer device, purchasing information associated with the electronic commerce transaction; and transmitting, by the computer device, the purchasing information to the third party social network.;

36. The mobile computer system of Claim 35, further comprising assigning, by the computer device, at least one loyalty credit based on the transmitted purchasing information.

37. The mobile computer system of Claim 35, further comprising a platform comprising at least one of a wish list, a Bookmark, and a favorite list which is configured to allow a user to at least one of: purchase a product from the platform, post the purchased product to the third party social network, and delete the products from the platform.

38. The mobile computer system of Claim 37, further comprising a multi-retailer order history/summary relating to an order summary of products.

39. The mobile computer system of Claim 38, wherein the system is configured to provide access of an order created which is grouped by a retailer and sorted by an order date.

40. The mobile computer system of Claim 39, wherein the order date comprises a most recent order.

41. The mobile computer system of Claim 40, wherein the system is configured to provide access to at least one of re-ordering a product and returning a product to initiate an electronic transaction on a retailer's ecommerce system.

42. The mobile computer system of Claim 35, further comprising a platform which includes a Lookbook having a retailer feature of putting together a group of products which a user can then purchase the entire look of products or remove products from an electronic shopping cart.

43. The mobile computer system of Claim 42, wherein the system is configured to provide access to the user to purchase the remaining products in a single ecommerce transaction.

44. One or more non-transitory computer-readable storage media having computer- executable instructions embodied thereon for sharing electronic commerce information to a third party social network, wherein, when executed by at least one processor of a computer device, the computer-readable instructions cause the processor to: conduct, by the computer device, an electronic commerce transaction; store, by the computer device, purchasing information associated with the electronic commerce transaction; transmit, by the computer device, the purchasing information to the third party social network; and assign, by the computer device, at least one loyalty credit based on the transmitted purchasing information.