Electronic transaction method and apparatus

Abstract

An electronic product transaction method at a merchant consolidator server operated by a merchant consolidator service provider, comprising: a user interface including a plurality of selectable merchant options, each merchant option including a link to a corresponding plurality of selectable product options, each product option including information about a product offered for sale, rent or hire by the corresponding merchant; receiving selections of a plurality of merchant options and a plurality of product options by the user; generating transaction data identifying the plurality of merchants and the plurality of products, the transaction data including data about a commission payable to the merchant consolidator service provider; receiving instructions from the user to pay for the selected products; and sending the transaction data to a remote payment server to authenticate and make payment from the user to the plurality of merchants for the products and for the commission to the merchant consolidator service provider.

Description

[0001] This application is a divisional application of patent application No. 2016800830300, filed on December 30, 2016, entitled "Electronic Transaction Method and Apparatus". Technical Field

[0002] This invention relates to electronic trading methods and apparatus, and in one aspect, it relates to electronic trading methods and apparatus that combine or facilitate transactions by a user using common combined trading pairs of multiple products from multiple merchants. Background Technology

[0003] E-commerce has become increasingly popular in recent years, and most businesses have their own websites to offer their products (goods and services) for sale, rental, or employment. When users want to visit multiple businesses' websites to buy goods, they must select the items they want to buy on each website to put them in their "shopping basket," complete the purchase on one website, and then move to the next website to buy the products on that website in a similar manner.

[0004] This process requires users to log into multiple websites and enter details of multiple transactions from multiple merchants. This is a tedious process when users want to buy products from a large number of merchants. Summary of the Invention

[0005] One aspect provides a method for electronic product transactions at a merchant merger server operated by a merchant merger service provider, the method comprising: generating an interface and outputting it to a user, the interface including a plurality of selectable merchant options, each merchant option including links to a plurality of selectable product options of the corresponding merchant, each product option including information about products offered by the corresponding merchant for sale, rental, or employment; the user receiving selections of the plurality of merchant options and the plurality of product options from the plurality of merchants; generating transaction data identifying the plurality of merchants and the plurality of products, the transaction data including data about commissions payable to the merchant merger service provider; receiving instructions from the user to pay for the selected products; and sending the transaction data to a remote payment server to authenticate and perform payments from the user to the products of the plurality of merchants, as well as to the commissions to the merchant merger service provider.

[0006] Another aspect of the present invention provides a merchant merger server operated by a merchant merger service provider, the merchant merger server comprising: at least one processor; and a memory storing instructions executable by the at least one processor to: generate an interface and output it to a user, the interface including a plurality of selectable merchant options, each merchant option including links to a plurality of selectable product options of the corresponding merchant, each product option including information about products offered by the corresponding merchant for sale, rental, or employment; receiving, by the user, selection of the plurality of merchant options and the plurality of product options from the plurality of merchants; generating transaction data identifying the plurality of merchants and the plurality of products, the transaction data including data about commission payable to the merchant merger service provider; receiving instructions from the user to pay for the selected product; and sending the transaction data to a remote payment server to authenticate and perform the payment from the user to the products of the plurality of merchants and to perform the payment to the commission to the merchant merger service provider.

[0007] Another aspect of the present invention provides a carrier medium or storage medium carrying code executable by a processor to perform the electronic product transaction method. Attached Figure Description

[0008] Figure 1 This is a schematic diagram illustrating a trading system according to one embodiment;

[0009] Figures 2a to 2j This is a schematic diagram of a user interface generated through a transaction process according to one embodiment;

[0010] Figure 3 This is a flowchart of a transaction process according to one embodiment;

[0011] Figure 4 This is given according to one embodiment. Figure 3 A flowchart with more details on steps S14 to S17 of the flowchart; and

[0012] Figure 5 This is a schematic diagram of the basic computing device used in one embodiment. Detailed Implementation

[0013] In the following detailed description, reference is made to the accompanying drawings, which form part of the detailed description, and in which specific embodiments are shown by way of illustration that allow the inventive subject matter to be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice them, and it will be understood that other embodiments may be used, and structural, logical, and electrical modifications may be made without departing from the scope of the inventive subject matter. Such embodiments of the inventive subject matter may be referred to herein, individually and / or collectively, with the term "invention," which is used for convenience only and is not intended to actively limit the scope of this application to any single invention or inventive concept.

[0014] Therefore, the following description is not intended to be limiting, and the scope of the inventive subject matter is defined by the appended claims.

[0015] In the following embodiments, the same components are labeled with the same reference numerals.

[0016] In the following embodiments, data is described as being stored in at least one database. The term database is intended to encompass any data structure (and / or combination of multiple data structures) used for storing and / or organizing data, including but not limited to relational databases (e.g., Oracle databases, MySQL databases, etc.), non-relational databases (e.g., NoSQL databases, etc.), in-memory databases, spreadsheets, comma-separated value (CSV) files, Extensible Markup Language (XML) files, text (TXT) files, flat files, spreadsheet files, and / or any other widely used or proprietary format for data storage. Databases are typically stored in one or more data storage devices. Therefore, each database referenced herein (e.g., in the specification and / or the accompanying drawings of this application) will be understood as being stored in one or more data storage devices. A “file system” can control how data is stored and / or retrieved (e.g., disk file systems (e.g., FAT, NTFS, optical discs, etc.), flash file systems, tape file systems, database file systems, transactional file systems, network file systems, etc.). For brevity, databases are described herein in relation to this disclosure. However, the systems and techniques disclosed herein may be implemented using file systems or combinations of databases and file systems.

[0017] In the following embodiments, the term data storage is intended to encompass any computer-readable storage medium and / or device (or collection of data storage media and / or devices). Examples of data storage include, but are not limited to, optical discs (e.g., CD-ROM, DVD-ROM, etc.), magnetic disks (e.g., hard disks, floppy disks, etc.), memory circuitry (e.g., solid-state drives, random access memory (RAM), etc.). Another example of data storage is a host storage environment, which includes a collection of physical data storage devices that can be remotely accessed and quickly set up as needed (often referred to as "cloud" storage).

[0018] In one embodiment, the functions or algorithms described herein are implemented in hardware, software, or a combination of software and hardware. Software includes computer-executable instructions stored on a computer-readable medium (e.g., memory or other type of storage device). Further, the above functions may correspond to modules, which may be software, hardware, firmware, or a combination thereof. Multiple functions may be executed as needed in one or more modules, and the above embodiments are merely examples. The software executes on a digital signal processor, ASIC, microprocessor, or other type of processor that operates on a system (e.g., a personal computer, server, router, or other device capable of processing data, including network interconnection devices).

[0019] Some embodiments utilize associated control and data signals between and through module communication to implement functions in two or more specific interconnected hardware modules or devices, or as part of an application-specific integrated circuit. Therefore, the example flow can be applied to software, firmware, and hardware implementations.

[0020] A generalized embodiment provides a method for electronic product transactions at a merchant merger server operated by a merchant merger service provider. An interface (e.g., a web interface or webpage) is generated and output to a user. The interface includes multiple selectable merchant options, such as webpage links. Each merchant option includes links to multiple selectable product options of the corresponding merchant. Each product option includes information about products offered by the corresponding merchant for sale, rental, or employment. Thus, the merchant merger server hosts the interface, which in one embodiment can include webpages or websites of each of multiple merchants, enabling each merchant to offer its products for sale, rental, or employment from a public site. The user can select from multiple merchant options and multiple product options. The merchant merger server generates transaction data that identifies the multiple merchants and multiple products. The transaction data includes data about commissions payable to the merchant merger service provider. When an instruction from the user is used to pay for the selected goods, the transaction data is sent to a remote payment server to authenticate and process the payment from the user to the products of the multiple merchants, as well as to the commission to the merchant merger service provider.

[0021] Therefore, in one embodiment, the transaction data includes merged transaction data of multiple transactions with multiple merchants, and a single payment is authenticated by the user to make a payment to multiple merchants.

[0022] In one embodiment, the transaction data includes data regarding the payment methods for each of the multiple merchants. In other words, merchants can supply payment information to the consolidation service provider, specifying how payments will be made for products offered for sale, rental, or employment on the merchant consolidation server, and this can be supplied as part of the transaction data to the payment server to receive single payments from users and to authenticate and process multiple payments to merchants for products purchased by users in the transaction.

[0023] In one embodiment, authentication of the transaction can be received from the payment server, and in response to receiving authentication, the transaction status is updated from open to closed. In this way, the transaction data can include data about products in a state where they have not yet been purchased (often referred to as the 'shopping basket'). Once the transaction is authenticated, the shopping basket is emptied and the products are moved to the purchased state. This is represented in the transaction data as a closed transaction state.

[0024] In one embodiment, information about the products offered by each merchant for sale, rental, or employment includes the quantity of products available to the merchant and the quantity of products available to the merchant that can be updated.

[0025] In another embodiment, this amount is notified to the merchant server of each of the multiple merchants to update the inventory at the merchant's location. If there is inventory available to fulfill the order, this ensures that the product is only provided for sale, rental, or employment.

[0026] In one embodiment, transaction data can be notified to the merchant server of each of multiple merchants to update the inventory data at the merchant server. This data can also be used to enable merchants to initiate the delivery of products from their warehouses or stores.

[0027] In one embodiment, the interface allows the user to select a merchant option to enter a merchant interface area where product options are selectable by the user, and selects product options from multiple merchants' products to generate transaction data by displaying common shopping basket options in each merchant interface area and allowing the user to select to add each merchant's products to the common shopping basket.

[0028] In one embodiment, a merchant interface is generated and output to receive product data from merchants to generate product options for each merchant's merchant options. In one embodiment, the merchant interface can be used to select a template to generate an interface for product options, and in one embodiment, the merchant interface is provided by an API on a merchant merger server, to which applications on the merchant server connect.

[0029] Therefore, merchants interact with the merchant merger server to set up and maintain the web pages or websites they host on the merger server. Merchants can create merchant web pages using code or templates available on the merger server. Alternatively, merchants can download their own web pages (HTML code) to the merger server, where the code is modified to ensure that the links and functions hosted on the merger server will operate. The merchant interface can also be used to notify merchants of transactions, enabling them to update their inventory and synchronize it with the product quantity data stored on the merchant merger server. In this way, if a merchant's inventory decreases through sales via other channels, or if inventory is replenished, the decrease or increase in product inventory can be accurately reflected on the merchant merger server.

[0030] In one embodiment, the user interface and merchant interface can be provided as a conventional website with outputs and indicator devices and keyboard input displayed to the user. In an alternative embodiment, the interface can be provided by any form of output (e.g., visual or auditory) and any form of input (e.g., keyboard, touchscreen, indicator devices (e.g., mouse, trackball, touchpad, or pen device), audio recognition hardware and / or software that recognizes the user's voice or speech, gesture recognition input hardware and / or software, etc.).

[0031] In one embodiment, a user interface can be provided using the method disclosed in pending application number entitled "USER INTERFACE METHOD AND APPARATUS" filed on the same date as this application by the same applicant and inventor (Agency Reference 11043PUS), the entire contents of which are incorporated herein by reference.

[0032] In this embodiment, the term "product" includes any product sold, employed, or rented by a merchant, and can include goods and services.

[0033] Specific embodiments will now be described with reference to the accompanying drawings.

[0034] Reference Figure 1 Describe the implementation examples. Figure 1 This describes a trading system according to one embodiment.

[0035] Merchant merger server 100 is configured to connect to a network (e.g., the Internet 50). Merchant merger server 100 provides merchant merging services to multiple users to purchase products from multiple merchants using a single merged transaction (or a shared shopping basket), wherein a single payment from a user is split into multiple payments to the merchants and a commission for the merging service via a payment function.

[0036] In this embodiment, a single user is represented by device 1. However, in practice, multiple users will use multiple user devices. Device 1 can include any type of computing or processor, such as a personal computer, laptop, tablet, personal memo pad, mobile device, smartphone, mobile phone, video player, television, audio player, multimedia device, personal digital assistant, etc. User device 1 is provided with a web browser 2 that accesses web server 101 at merger server 100, and an email client 3 (e.g., Microsoft Outlook™) that receives emails when a merge transaction is completed from email server 107 of merger server 100.

[0037] In this embodiment, two businesses are represented by computers 200a and 200b. The first business's computer 200a is connected to the Internet 50 and includes an application 203 running on the computer that accesses a database 201 containing the business's products. The application 203 can access API 106 at the merger server 100. The first business's computer 200a is therefore a large business with a large number of products listed on a website created on the merger server 100. When the first business's website or webpages are created, data about the products is stored in database 201 and can be downloaded to database 105 at the merger server 100. Product data can be downloaded in a defined format (e.g., in XML according to a defined XML schema) so that the data can be easily recognized by the merger server 100. API 106 and application 203 enable data to be transmitted back to the first business's computer 200a. This data can include transaction data and product quantity data. Transaction data allows the business to determine where to deliver the products, and upon receiving the transaction data, the business begins the delivery process. Alternatively, in cases where there are issues with the payment process, merchants can wait for payment from payment authorities before they can begin completing an order.

[0038] The second merchant's computer 200b is connected to the Internet 50 and consists only of a web browser 204 and an email client 205. Therefore, this merchant does not have any applications and can only access the merger server 100 via web browser 101. Web browser 101 can provide access through a proper merchant login process, enabling the second merchant to use its computer 200b to access the merchant website or the merchant web administrator area, allowing the second merchant to download product data and build its website or webpages for e-commerce. The second merchant's computer 200b also provides an email client 205 (e.g., Microsoft Outlook™) to receive emails when a merge transaction is completed from the merger server 100's email server 107. The second merchant can therefore manually update any internal records on the inventory maintained by the second merchant.

[0039] In this embodiment, a payment gateway server 300 operated by the PayPal™ payment gateway provides payment functionality. This payment gateway server 300 is separate from a payment authorization server 350 operated by a financial institution, such as the credit card company. The payment gateway server 300 provides a database 305 containing data necessary for providing payment gateway services, such as bank account information, including user information, user login information, and user transaction history. The payment authorization server 350 provides a database 355 containing user and merchant account information. This embodiment assumes the existence of a single payment authorization. Because a merchant may not have an account with payment authorization associated with the payment authorization server 350, more than one payment authorization may be required to complete a transaction. In this case, the payment authorization can be used to pay for intermediate payment authorizations.

[0040] In an alternative embodiment, a single server may be used, providing both payment gateway and payment authorization functionality. In both embodiments, the payment functionality is separate from and distinct from the merger server and operations. It is provided by one or two third parties.

[0041] Merger server 100 includes a web server 101 connected to the Internet 50. Web server 101 is connected to web page storage 102, which stores static web pages and templates required by the web server to generate web pages and use them in the web browsers of a second merchant's computer 200b and a user's device 1. Application server 103 is configured to connect to web server 101 and is used to generate static web pages for the web server and perform other functions of the merger service. Database server 104 is configured to connect to application server 103 to provide the application server with access to database 105, which contains merchant data, product data, and transaction data, as described in more detail below.

[0042] Merger server 100 also provides an email server, which is connected to the Internet 50 and controlled by application server 103, to generate an email and send it to the second merchant's computer 200b and the user's device 1 when the merger transaction is completed.

[0043] The data stored in database 105 of merger server 100 includes the following:

[0044] Merchant data

[0045] This data is unique to each merchant and is identified by a merchant identifier.

[0046] Merchant ID

[0047] • Name, trademarks, etc.

[0048] • Username and password used by the merchant to log in to their administrator section hosted on Merger Server 100, in order to create and manage their website or web pages hosted on Merger Server 100.

[0049] • Merchant description / information

[0050] • Contact information and email address

[0051] • Merchant rating – based on the merchant's popularity and / or performance in previous transactions.

[0052] • Payment Information – Details of the merchant's payment gateway and / or authorized account to enable payment processing.

[0053] • Commission ID

[0054] • Currency – the currency accepted by merchants

[0055] Product Data

[0056] This data is unique to each product and is identified by a product identifier.

[0057] •Product ID

[0058] • Merchant ID — The merchant to which the product belongs

[0059] • Quantity – The amount of product available for purchase

[0060] • Category ID — The category (product type) to which the product belongs.

[0061] • Commission ID – Each product can have a different commission applied to it.

[0062] •Product Description

[0063] • Product image / video ID

[0064] •Product price data

[0065] Commission data

[0066] This data defines unique commission data that can be applied to each product or product category and is identified by a commission identifier.

[0067] • Commission ID

[0068] • Percentage or fixed commission

[0069] • Commission value, such as 2% or £1.00

[0070] Product category data

[0071] This data defines unique category data to be grouped together with product type and identified by category identifiers.

[0072] • Category ID

[0073] • Commission ID

[0074] • Category Description

[0075] Web page data

[0076] This data defines the unique webpage attributes that display product options that can be selected by the user. Webpage identifiers identify the webpage data.

[0077] • Page ID

[0078] Merchant ID

[0079] • Page data (e.g., skin data)

[0080] • Metadescription

[0081] • Template ID

[0082] •Product ID

[0083] Template data

[0084] This data defines the templates that can be used for web page design. This allows businesses to use templates to create web pages hosted by the merger server. Each template is uniquely identified by a template identifier.

[0085] • Template ID

[0086] • Template data

[0087] User data

[0088] This data is unique to each user and is identified by a user identifier.

[0089] • User ID

[0090] •name

[0091] • Contact information and email address

[0092] • Username and password are used for user login to the merger server.

[0093] • Currency – The preferred currency for users conducting transactions.

[0094] • Language – The user's preferred language

[0095] • Personal profile picture

[0096] • Preferred payment permissions include public login data (e.g., username but not password).

[0097] • Favorites – A user's saved favorite products or merchants.

[0098] •Historical Data – User Products for Transaction History Data and Observational History Data

[0099] Merchant Merger Data

[0100] • Merger account details used for payments — Merger's payment gateway and / or authorization account details

[0101] Merged transaction data

[0102] This data is unique to merged transactions executed by a user in a session involving multiple products from multiple merchants and is identified by a merged transaction identifier.

[0103] • Merged Transaction ID

[0104] • Session ID — This is generated by the user at the start of the session and is used to ensure that the merge transaction identifier can only be used within a single session of the user.

[0105] • User Profile and ID – In the event that a user changes their profile after a transaction, the user profile and user ID are stored separately.

[0106] • The date and time of the transaction – this can be the start time and / or end time.

[0107] • Total value of transactions

[0108] • Currency of the transaction

[0109] • For merged transactions, the total commission payable to the merger service provider.

[0110] • Transaction status – open or closed. A transaction is open until payment is approved by payment authorities.

[0111] • Real-time Transaction ID – This is the transaction ID issued for a transaction based on payment permissions.

[0112] Transaction data

[0113] This data is unique to each merchant and can contain transaction data for multiple products from that merchant, as well as the total price due to the merchant. Transaction data is uniquely identified by transaction identifiers.

[0114] • Transaction ID

[0115] • Merchant Information and ID – In the event that a merchant changes their information after a transaction, the merchant information and merchant ID are stored separately.

[0116] • Product Information and ID – In cases where the merchant changes the product information after a transaction, the product information and product ID are stored separately.

[0117] • Merged Transaction ID

[0118] • The date and time of the transaction with the merchant – this can be a different time from the combined transaction time, but must be a time between the start and end times of the combined transaction.

[0119] • Product quantity – This is the quantity of each product ordered and is linked to the product ID listed above in the transaction data.

[0120] • Product Price – This is the price of each product ordered and is linked to the product ID listed above in the transaction data.

[0121] • Currency of the transaction

[0122] • Exchange rate to be applied to the transaction

[0123] • Total value for the merchant – Total price of all products (product price * quantity) + shipping cost

[0124] • Delivery data – estimated dates and costs for each product (each product may have a different delivery date)

[0125] To enable users to use the merger server 100, users can access a signature webpage to enter user data. Users can also create accounts using a payment gateway that operates the payment gateway server 300. Alternatively, users can access the merger server 100 as customer users by entering temporary information that is not permanently stored in their user accounts.

[0126] To establish a merchant's website or webpage, each merchant can sign in to the merger payment service and enter merchant data. Alternatively, merchants can access the merger server 100 as customer users by entering temporary information not permanently stored in their user accounts. Merchants can then log in to the web portal to access the administrator area or download and install application 203 to access API 106. Merchants can download product data using, for example, XML, and they can design and save webpages for their products using available templates and web data (e.g., skin data). They can also download style data (e.g., brand) and trademark data to customize the webpages. Product data and webpage data are then stored in database 105. Merchants can also download their own webpages, which are modified to ensure that customers seeking to purchase products are directed to a page hosted by the merger server to consolidate transactions / purchases from multiple merchants.

[0127] Now it will be adopted as a reference. Figure 3 The flowchart generated from the transaction process Figures 2a to 2j A schematic diagram of the user interface is used to describe a transaction process according to one embodiment. Figure 1 The operation of the system.

[0128] exist Figure 3 In step S11, the web server 101 of the merger server 100 serves as the login webpage for the user's device 1, which is presented and displayed through the web browser 2 to receive user login information sent to the merger server 100 (step S12). In step S13, the web server 101 generates a session identifier, which is recorded in the database 105 using the database server 104 of the merger server 100 via the application server 103. Then, in step S14, the web server 101 of the merger server 100 serves as the login webpage, which is presented and displayed as... Figure 2a The login page shown is 400a.

[0129] The landing page 400a includes multiple merchant options 401, including links to selectable HTML links to merchant product options (web pages). The landing page includes a shopping basket 402 and a checkout option 403. The shopping basket 402 indicates how many products are in the basket (in an open transaction state). In the illustrated embodiment, there is one product, and the checkout option 403 can be selected by the user to check out or complete the transaction for the product in the shopping basket.

[0130] The browser interface also provides standard forward and back navigation options for webpage navigation.

[0131] Figure 2bThe browser interface shown is the one displayed after the user selects a merchant option; in this embodiment, the interface is for the merchant "Quick Store". The Quick Store merchant webpage 400b is displayed to show the types of products available for purchase from the merchant. In this example, there are four product types to choose from: camera, laptop, television, and speaker. Each type cursor 405 can be selected by the user to display a webpage with individual products available for purchase from the merchant within the selected type. The merchant product type page includes a shopping basket 402 and a checkout option 403. The shopping basket 402 indicates how many products are in the basket (in an open transaction state), and in the illustrated embodiment, there is only one product. The checkout option 403 can be selected by the user to check out or complete the transaction for the products in the shopping basket.

[0132] Figure 2c The browser interface is shown after the user selects a product category option; in this example, the interface is for the category "Camera". The product list webpage 400c displays selectable product options 406 as selectable links to view more information and purchase a camera. The product category list page includes a shopping basket 402 and a checkout option 403. The shopping basket 402 indicates how many products are in the basket (in an open transaction state). In the illustrated embodiment, there is one product, and the checkout option 403 can be selected by the user to check out or complete the transaction for the products in the shopping basket.

[0133] Figure 2d The browser interface is shown after the user selects Camera B as the product option. A product webpage 400d is displayed to show information about the selected product option, and the selectable "Add to Cart" option 409 is shown, allowing the user to choose whether to add the product to the transaction data or to the cart. Before the user makes a selection, the cart 402 still only shows one item.

[0134] exist Figure 3 In step S15 of the flowchart, the user's selection of the product is received, and in step S16, transaction data is opened and filled in. Figure 2d In the example shown, the transaction has been opened due to the previous selection and placement of the product in shopping basket 402.

[0135] Figure 2e Shown when the user selects Figures 2a to 2d Choose either of the shopping basket options 402 to view the shopping basket in the browser interface. The shopping basket webpage 400e is displayed listing the selected products and shows the checkout option 403 where the previously displayed option to add to the shopping basket was shown. In this example, the shopping basket shows the previously selected products, which are in Figures 2a to 2dThe item shown is in the shopping cart; it's a dress from the merchant "Dress Up." The most recently selected product, camera B, is also displayed along with the total transaction price. Therefore, the shopping cart display indicates that transactions from two merchants have been combined, with the transaction data still open.

[0136] exist Figure 3 In step S17, the user's selection to check out via option 203 is received and displayed. Figure 2f The browser interface. The checkout page 400f displays a list of products along with product details and other information, such as delivery date and cost. It also shows the user's options to choose to pay for the combined transaction. When the user selects to pay for the transaction and the checkout process is complete, ... Figure 3 In step S18, the merging server 100 determines the commission payable to the merging service provider and stores it in the merging transaction data. In step S19, the merging server 100 sends the merging transaction data record to the payment gateway server 300, and in step S20, the payment gateway server 300 extracts user data and generates a login window, which is sent to the web browser 2 of the user's device 1. In step S21, as... Figure 2g As shown, a payment login window 400g is displayed by the web browser 2 of the user's device 1. In this example, the payment gateway service provider is "PaySomeOne". In step S22, the user's device 1 receives the user's login information from the payment gateway service. In an alternative embodiment, the user may wish to enter other payment information, such as credit card information, to directly grant payment permissions.

[0137] In step S23, the payment gateway server 300 verifies the user's reliability, and if the user is not verified (step S24), a message is sent back to the user's device 1 to be displayed by the browser 2 in step S25 to notify the user of verification failure. If verification has failed, the transaction can be modified to a closed state without a real-time transaction ID. This removes the product from the shopping cart, as the shopping cart represents products in an open transaction state. A closed transaction without a real-time transaction ID is identified as a failed transaction. Alternatively, the merged transaction ID can include a transaction failure flag, which is set when the transaction fails.

[0138] If the user is verified (step S24), then as follows Figure 2h The payment confirmation webpage 400h shown can be displayed to the user to confirm payment for the goods by selecting the confirmation option 410.

[0139] In step S26, the payment is then processed by sending a request to the payment authorization server to authenticate the transaction, thereby sending the transaction data to the payment authorization server. In step S27, the payment authorization server 350 performs payment authorization, and if not approved (step S28), a message is sent back to the user's device 1 to be displayed by the browser 2 in step S25 to notify the user of verification failure. If verification has failed, the transaction can be modified to a closed state without a real-time transaction ID. This removes the product from the shopping cart, as the shopping cart represents products in an open transaction state. A closed transaction without a real-time transaction ID is identified as a failed transaction. Alternatively, the merged transaction ID can include a transaction failure flag, which is set when the transaction fails.

[0140] If the payment authorization has been approved (step S28), the approval is communicated to the merger server 100, and in step S29, the payment approval is recorded in database 105 as part of the merged transaction data. In step S30, the user's device 1's web browser 2 receives and displays the payment approval notification, as shown in... Figure 2i As shown on webpage 400i. In step S29, the recorded approval is also sent back to the merger server to update the quantity data of the purchased products in database 105 in step S31, and to update the status of the merge transaction from open to closed in step S32 and assign the real-time transaction ID from payment authorization server 350 to the merge transaction data in database 105. In step S33, then, the email server 107 of the merger server 100 outputs the transaction information to the user's device 1 via email, and in step S34, the user's device 1's email client 3 receives and displays a notification of successful transaction, as shown in... Figure 2j As shown on webpage 400j. Merger server 100's email server 107 also outputs email or API messages containing transaction information to merchant computers 200a and 200b of the merchants involved in the merger transaction, and the email clients 205 or applications 203 of merchant computers 200a and 200b receive and display a notification of a successful transaction. Figure 3 (Not shown in the image). This allows merchants to update their inventory in their database.

[0141] The approval and filing of the transaction in step S29 also enables the payment gateway server to initiate payments to the merchant for the product and to the merger for commissions in step S35. Therefore, in step S36, the payment authorization server 350 stores the transaction in the merchant's account and the merger's account.

[0142] Figure 4 More detailed Figure 3 The flowchart shows steps S14 to S17.

[0143] In step S100, the merger server 100 sends the login webpage to the user's device 1's web browser 2, and in step S101, the user's device 1's web browser 2 waits to receive the user's selection of the merchant option (see...). Figure 2a When the user selects a merchant option, in step S100, the merger server 100 serves the merchant's webpage, and in step S103, the web browser 2 of the user's device 1 waits for the user's selection of the product (see...). Figure 2c --Notice, Figure 4 The flowchart skips the steps of generating and displaying merchant product category options, such as... Figure 2b As shown in the figure.

[0144] When the user selects a product option in step S103, in step S104, the merger server opens and populates the transaction data, as this is the first product data added to the merge transaction. Then, in step S105, the process waits to determine whether the user has selected another product (step S105). If the user selects another product, in step S106, web browser 2 or the user's computer 1 receives the user's selection of the other product option, and in step S107, the merger server updates the merge transaction data using the new transaction data. The process then returns to step S105 to determine whether another product has been selected.

[0145] If no other product is selected in step S105, then in step S108, the process determines whether to select another merchant. If so, then in step S109, the web browser 2 of the user's device 1 receives the selection of another merchant, and the process returns to step S100 so that the merger server 100 serves the merchant's webpage of the newly selected merchant.

[0146] If no other merchant is selected in step S108, then in step S110, the web browser 2 of the user's device determines whether the user's checkout selection has been received, and if so, the process continues to... Figure 3 If not, the process returns to step S18. If not, the process returns to step S105 to wait for the selection of product use, or to wait for the selection of merchant in step S108.

[0147] The update to the product quantity stored on the merger server in step S31 can be used to notify the merchant when the quantity falls below a threshold (which can be zero or any other number chosen by the merchant). Furthermore, the merchant interface can be used to notify the merchant of each transaction, enabling them to update their inventory and synchronize it with the product quantity data stored on the merchant merger server. In this way, if a merchant's inventory decreases through sales via other channels, or if inventory is replenished, the decrease or increase in product inventory can be accurately reflected on the merchant merger server.

[0148] In this embodiment, the fulfillment of product orders is delegated to the merchant to arrange delivery of products from their warehouses, stores, or even directly from their suppliers. In an alternative embodiment, the merger service provider assists the merchant in fulfilling orders, for example, by sending instructions directly to the supplier to deliver products directly to the customer.

[0149] In one embodiment, if product update step S31 indicates that the product is unavailable for purchase (i.e., the product quantity reaches zero), the merger server can enable the user to enter a request to be notified when inventory is replenished and the product is again available for sale from the merchant. The user can request notification, for example, via email or text, and in one embodiment, the merger server can send instructions to the merchant's computer, such as via email or via API, to instruct the merchant to notify the user when the product is replenished. In an alternative embodiment, the merger server can perform the function of notifying the user when the product quantity on the merger server is later updated by the merchant.

[0150] Therefore, the process of embodiments of the present invention enables users to make multiple purchases of products from multiple merchants by selecting to access the website or webpage of each merchant hosted on the merger server and then using a third-party payment service to make a single payment for all products.

[0151] In this embodiment, the merger service provider is not responsible for payments and does not authenticate payments. The merchant merger service is provided by hosting merchant webpages on a single website, where landing page access begins with options for each merchant website hosted by the merger service. Thus, the landing page can be likened to visiting a shopping mall where a user can choose to visit each merchant in turn to select items to purchase. In this embodiment, however, the user only needs to pay for all selected items once using a common, single merge transaction facilitated by the merger service provider.

[0152] In this embodiment, although the user interface is described as a webpage, any suitable interface technology may be used. In one embodiment, the interface displaying merchant options may be output as a virtual marketplace, but the user can navigate to select a merchant. In this embodiment, the merchant's product selection may be output as items selected by navigating within the virtual version of the merchant's store.

[0153] Basic computing device

[0154] Figure 5 This is a block diagram illustrating a basic computing device 600, in which one or more exemplary embodiments of the present invention may be implemented. The computing device 600 and its components (including their connections, relationships, and functions) are intended to be exemplary only and not to limit the implementation of the one or more exemplary embodiments. Other computing devices suitable for implementing one or more exemplary embodiments may have different components, including components with different connections, relationships, and functions.

[0155] For example, computing device 600 can include, for example, Figure 1 Any of the servers or user devices shown.

[0156] The computing device 600 may include a bus 602 or other communication mechanisms to address the main memory 606 and to transfer data between and among the various components of the device 600.

[0157] The computing device 600 may also include one or more hardware processors 604 coupled to the bus 602 to process information. The hardware processor 604 may be a general-purpose microprocessor, a system-on-a-chip (SoC), or other processor.

[0158] Main memory 606 (e.g., random access memory (RAM) or other dynamic storage device) may also be coupled to bus 602 to store information and software instructions to be executed by processor(s) 604. During the execution of software instructions to be executed by processor(s) 604, main memory 606 may also be used to store temporary variables or other intermediate information.

[0159] When software instructions are stored in a storage medium accessible by one or more processors 604, they make computing device 600 a dedicated computing device, specifically designed to perform the operations specified in the software instructions. The terms “software,” “software instructions,” “computer program,” “computer-executable instructions,” and “processor-executable instructions” are broadly interpreted to cover any machine-readable information (whether human-readable or not) that instructs a computing device to perform specific operations, including but not limited to application software, desktop applications, scripts, binaries, operating systems, device drivers, bootloaders, shells, utilities, system software, JavaScript, web pages, web applications, plug-ins, embedded software, microcode, compilers, debuggers, interpreters, virtual machines, linkers, and text editors.

[0160] The computing device 600 may also include a read-only memory (ROM) 608 or other static storage device coupled to the bus 602 to store static information and software instructions of processor(s) 604(s).

[0161] One or more mass storage devices 610 may be coupled to bus 602 to permanently store information and software instructions on a fixed or removable medium (e.g., magnetic, optical, solid-state, magneto-optical, flash memory, or any other available mass storage technology). The mass storage may be shared on a network or may be dedicated to a specific purpose. Typically, at least one of the mass storage devices 610 (e.g., the device's main hard disk) stores the bulk of programs and data for the operation of the computing device, including operating systems, user applications, drives and other supporting files, and all other types of data files.

[0162] The computing device 600 may be coupled to a display 612, such as a liquid crystal display (LCD) or other electronically visualized display, via a bus 602 to display information to a computer user. In some configurations, a touch-sensitive surface (e.g., resistive, capacitive, etc.) incorporating touch detection technology may be overlaid on the display 612 to form a touch-sensitive display for transmitting touch gestures (e.g., fingers or light pens) to processor(s) 604.

[0163] Input device 614 (including alphanumeric and other keys) may be coupled to bus 602 to communicate information and command selection to processor 604. In addition to or in lieu of alphanumeric and other keys, input device 614 may include one or more physical buttons or switches, such as, for example, a power (on / off) button, a "home" button, a volume control button, etc.

[0164] Another type of user input device can be a cursor control 616, such as a mouse, trackball, cursor, or touchscreen arrow keys, to communicate directional information and command selection to processor 604 and control cursor movement on display 612. This input device typically has two degrees of freedom on two axes (a first axis (e.g., x) and a second axis (e.g., y)), allowing the device to specify a position in a plane. Other input device embodiments include audio or speech recognition input modules that recognize audio input (e.g., speech), visual input devices capable of recognizing user gestures, and keyboards.

[0165] Although in some configurations (e.g., Figure 5 In the configuration shown, one or more of the display 612, input device 614, and cursor control 616 are external components (i.e., peripheral devices) of the computing device 600, but in other configurations, some or all of the display 612, input device 614, and cursor control 616 are integrated as part of the forming elements of the computing device 600.

[0166] In addition to or in place of display 612, any other form of user output device, such as an audio output device or a haptic (vibration) output device, can be used.

[0167] The functions of the disclosed systems, methods, and modules can be executed by computing device 600 in response to processor(s) 604 executing one or more programs containing software instructions stored in main memory 606. These software instructions can be read into main memory 606 from another storage medium (e.g., storage device(s) 610 or a transmission medium). Execution of the software instructions stored in main memory 606 causes processor(s) 604 to perform the functions of one or more embodiments.

[0168] Although the functionality and operation of one or more example embodiments can be implemented entirely using software instructions, the functionality may be performed in other embodiments using a hard-connected circuit system or programmable circuit system (e.g., ASIC, FPGA, etc.) of computing device 600 in place of or in combination with software instructions, depending on the requirements of the specific implementation at hand.

[0169] As used herein, the term "storage medium" refers to any non-transitory medium that stores data and / or software instructions that enable a computing device to operate in a specific form. Such storage media can include non-volatile media and / or volatile media. For example, non-volatile media include non-volatile random access memory (NVRAM), flash memory, optical discs, magnetic disks, or solid-state drives, such as storage device 610. Volatile media include dynamic memory, such as main memory 606. Common forms of storage media include floppy disks, hard disks, solid-state drives, magnetic tape or any other magnetic data storage media, CD-ROMs, any other optical data storage media, any physical media with a perforated pattern, RAM, PROMs and EPROMs, FLASH-EPROMs, NVRAM, flash memory, any other memory chips or cartridges.

[0170] Storage media differ from transmission media but can be used in conjunction with them. Transmission media participate in the transfer of information between storage media. For example, transmission media include coaxial cables, copper wires, and optical fibers, including wires containing bus 602. Transmission media can also take the form of sound waves or light waves, such as those generated during radio wave and infrared data communication. Machine-readable media carrying instructions in coded form can include both non-transitory storage media and transmission media.

[0171] Various forms of media may involve carrying one or more software instructions sequentially to processor(s) 604 for execution. For example, the software instructions may initially execute on a disk or solid-state drive of a remote computer. The remote computer is able to load the software instructions into its dynamic memory and transmit the software instructions via a telephone line using a modem. A modem local to computing device 600 is able to receive data over the telephone line and convert the data into an infrared signal using an infrared transmitter. An infrared detector is able to receive the data carried in the infrared signal, and appropriate circuitry is able to place the data on bus 602. Bus 602 carries the data to main memory 606, from which processor(s) 604 retrieves and executes the software instructions. The software instructions received by main memory 606 may optionally be stored on storage device(s) 610 before or after execution by processor(s) 604.

[0172] The computing device 600 may also include one or more communication interfaces 618 coupled to a bus 602. The communication interface 618 provides dual-path data communication coupled to a wired or wireless network link 620 connected to a local network 622 (e.g., Ethernet, wireless LAN, mobile phone network, Bluetooth wireless network, etc.). The communication interface 618 transmits and receives electrical, electromagnetic, and optical signals carrying digital data streams representing various types of information. For example, the communication interface 618 may be a wired network interface card, a wireless network interface card, or has an integrated radio antenna or modem (e.g., ISDN, DSL, or cable modem).

[0173] One or more network links 620 typically provide data communication with other data devices via one or more networks. For example, network link 620 may provide connection to a host computer via local network 622 or to data devices operated by an Internet Service Provider (ISP). The ISP, in turn, provides data communication services via a global packet data communication network (now commonly referred to as the "Internet"). The one or more local networks 622 and the Internet use electrical, electromagnetic, and optical signals that carry digital data streams. Signals carrying digital data to and from computing device 600 via various networks, signals on the one or more network links 620, and signals via the one or more communication interfaces 618 are example forms of transmission media.

[0174] The computing device 600 is capable of sending messages and receiving data, including program code, via one or more networks, one or more network links 620, and one or more communication interfaces 618. In the example of the Internet, the server can send application request code via the Internet, an ISP, one or more local networks 622, and one or more communication interfaces 618.

[0175] The received code may be executed by processor 604 upon receipt and / or stored in storage device 610 or other non-volatile storage for later execution.

[0176] One aspect provides a carrier medium, such as a non-transitory storage medium or a transient medium, wherein the non-transitory storage medium stores code executed by a machine's processor to perform the method, and the transient medium carries processor-executable code executed by the machine's processor to perform the method. Embodiments can be implemented in programmable digital logic that implements computer code. The code can be supplied to programmable logic, such as a processor or microprocessor, on the carrier medium. One such embodiment of the carrier medium is a transient medium, i.e., a signal, such as an electrical signal, electromagnetic signal, acoustic signal, or optical signal. Another form of carrier medium is a non-transitory storage medium that stores code, such as a solid-state memory, magnetic media (hard disk drive), or optical media (optical disc (CD) or digital versatile optical disc (DVD)).

[0177] Those skilled in the art will readily understand that various other changes may be made to the details, arrangement of materials and components, and method stages without departing from the principles and scope of the subject matter of the invention as set forth in the appended claims, which have been described and illustrated in order to explain the nature of the subject matter of the invention.

Claims

1. A method for electronic product transactions at a merchant merger server operated by a merchant merger service provider, the method comprising: A user interface is generated and output to the user. The user interface includes multiple selectable merchant options, each merchant option includes links to multiple selectable product options of the corresponding merchant, and each product option includes information about products offered by the corresponding merchant for sale, rental or employment. The user receives a selection of multiple merchant options and multiple product options from the multiple merchants; Generate transaction data that identifies the plurality of merchants and the plurality of products, the transaction data including data about commissions payable to the merchant merger service provider; Receive instructions from the user to pay for the selected product; as well as The transaction data is sent to a remote payment server to authenticate and process payments from the user to the products of the multiple merchants, as well as to make payments to the merchant merger service provider for the commission.

2. The electronic product transaction method according to claim 1, wherein, The transaction data includes data about the payment method for each of the plurality of merchants.

3. The electronic product transaction method according to claim 1 or 2, comprising receiving authorization for the transaction from the payment server, and updating the status of the transaction from open to closed in response to receiving the authorization.

4. A merchant merger server operated by a merchant merger service provider, the merchant merger server comprising: A device for generating an interface and outputting it to a user, the interface including multiple selectable merchant options, each merchant option including links to multiple selectable product options of the corresponding merchant, each product option including information about products offered by the corresponding merchant for sale, rental or employment; A means for receiving, by the user, a selection of multiple merchant options and multiple product options from the multiple merchants; A means for generating transaction data, the transaction data identifying the plurality of merchants and the plurality of products, the transaction data including data regarding commissions payable to the merchant merger service provider; A device for receiving instructions from the user to pay for a selected product; as well as A means for sending the transaction data to a remote payment server to authenticate and process payments from the user to the products of the plurality of merchants, as well as to make payments of the commission to the merchant aggregator service provider.

5. The merchant merger server according to claim 4, wherein, The transaction data includes data about the payment method for each of the plurality of merchants.

6. The merchant merger server according to claim 4 or 5, comprising means for receiving authorization of a transaction from the payment server, and means for updating the state of the transaction from open to closed in response to receiving the authorization.

7. A merchant merger server operated by a merchant merger service provider, the merchant merger server comprising: At least one processor; and A memory storing instructions that can be executed by the at least one processor to: A user interface is generated and output to the user. The user interface includes multiple selectable merchant options, each merchant option includes links to multiple selectable product options of the corresponding merchant, and each product option includes information about products offered by the corresponding merchant for sale, rental or employment. The user receives a selection of multiple merchant options and multiple product options from the multiple merchants; Generate transaction data that identifies the plurality of merchants and the plurality of products, the transaction data including data about commissions payable to the merchant merger service provider; Receive instructions from the user to pay for the selected product; as well as The transaction data is sent to a remote payment server to authenticate and process payments for the products from the user to the multiple merchants, as well as to make payments to the merchant merger service provider for the commission.

8. A carrier medium carrying processor-executable code executed by a processor to perform the method according to any one of claims 1 to 3.

9. A non-transitory storage medium storing processor-executable code executed by a processor to perform the method according to any one of claims 1 to 3.

10. A merchant merger server operated by a merchant merger service provider, the merchant merger server comprising: At least one processor; and A memory for storing instructions that can be executed by the at least one processor to perform the method according to any one of claims 1 to 3.

Images