System and method for transmitting anonymized transactions between nodes of a computer network

By using intermediate node processors to transmit anonymous transactions in the computer network, the problem that merchants cannot control payment methods and privacy protection in the existing system is solved, and a more flexible and secure currency transaction process is achieved.

CN113795857BActive Publication Date: 2024-11-26SHIFT4 TECHNOLOGY LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080034352.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-05-20
Filing Date
2020-04-19
Publication Date
2024-11-26
Estimated Expiration
2040-04-19

AI Technical Summary

Technical Problem

The existing computer network system cannot avoid merchants processing or storing the properties of payment mechanisms when transmitting transactions, and does not allow merchants to prioritize payment methods, limiting merchants' flexibility and privacy protection in currency transactions.

Method used

Through the processor of the intermediate node, anonymous transactions are transmitted between the source and destination nodes of the computer network, data elements are extracted and analyzed, transactions are verified based on conditional elements and product attributes, merchants are allowed to choose a priority payment method, and if necessary, to The user sends a notification message to obtain approval.

Benefits of technology

It realizes merchants' flexible choice of payment methods and privacy protection in currency transactions, reduces the storage and processing needs of sensitive information, and improves the security and privacy of transactions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113795857B_ABST
    Figure CN113795857B_ABST
Patent Text Reader

Abstract

A system and method for transmitting a transaction between a source node and a destination node of a computer network by at least one processor of an intermediate node may include: receiving a request to transmit a transaction from a source node to a destination node; extracting at least one data element from the transaction request; obtaining at least one condition element from a first database; anonymizing the transaction; and transmitting the anonymized transaction from the intermediate node to the destination node based on at least one of the at least one condition element and the extracted at least one data element.
Need to check novelty before this filing date? Find Prior Art

Description

Field of the Invention

[0001] The present invention relates generally to computer communication networks. More particularly, the present invention relates to transmitting anonymized transactions between a first node and a second node of a computer network. Background of the Invention

[0003] State-of-the-art systems for transmitting and providing routing for data over computer networks are configured to deliver data from a source node to a destination node, and typically do not consider the content or value of the data that may be contained in the payload of the transaction.

[0004] This limitation is particularly severe in implementations that may involve the transfer of potentially sensitive data, such as in the case of a monetary exchange (ME) transaction between two parties (eg, a merchant and a customer).

[0005] In this case, both parties agree on all the details (e.g., price of the product, payment terms, etc.). The customer may provide the attributes of the payment mechanism (e.g., credit card number), and the merchant may forward these attributes to the credit card company through the acquirer. The acquirer may request payment authorization, and once the information is received, the information may be communicated back from the bank to the credit card company, to the acquirer, and to the merchant who may provide the product to the user. Such communications are typically conducted in whole or in large part through computer systems such as servers maintained by the parties. SUMMARY OF THE INVENTION

[0007] State-of-the-art systems do not enable merchants (eg, merchant computer systems) to avoid processing or storing attributes of payment mechanisms (eg, credit card numbers).

[0008] Furthermore, state-of-the-art systems may mandate that merchants communicate and / or collaborate with acquirers and do not allow merchants to impose their own priorities on payment methods, such as by preferring one payment method (e.g., a first credit card) over another (e.g., a second credit card) by offering a more attractive price.

[0009] Embodiments of the present invention may include systems and methods for transmitting transactions between a source node and a destination node of a computer network by at least one processor of an intermediate node.

[0010] Embodiments of the method may include:

[0011] receiving a request to transmit a transaction from a source node to a destination node;

[0012] extracting at least one data element from the transaction request;

[0013] Obtain at least one condition element from a first database;

[0014] receiving a transaction corresponding to the request from a source node;

[0015] Anonymize transactions; and

[0016] An anonymized transaction is transmitted from the intermediate node to the destination node based on at least one of the at least one conditional element and the extracted at least one data element.

[0017] The at least one data element extracted may be selected from a list consisting of:

[0018] a value of a first user attribute for a first user associated with the source node;

[0019] a value of a second user attribute of a second user associated with the destination node;

[0020] The values ​​of the product attributes; and

[0021] The value of the logistics indicator.

[0022] Embodiments of the invention may include anonymizing the transaction by excluding at least one value of the first user attribute from the requested transaction.

[0023] According to some embodiments, the transaction may be a monetary transaction (ME) transaction. Embodiments of the method may include anonymizing the transaction so as not to include attributes of the first user.

[0024] The extracted at least one data element may also include a reference to an entry in the second database. Embodiments of the method may include:

[0025] presenting a query regarding a value of at least one product attribute to a second database;

[0026] Obtaining a response from a second database; and

[0027] Parse the response to verify the value of at least one product attribute.

[0028] Embodiments of the method may include transmitting the anonymized transaction to a destination node based on verification of the value of the at least one product attribute.

[0029] The transaction may be a monetary transaction transaction, and the at least one conditional element may be related to the monetary transaction transaction. Additionally or alternatively, the at least one conditional element may be or may include, for example:

[0030] Second product attributes;

[0031] Commissions; and

[0032] Acceptable payment methods.

[0033] Embodiments of the present invention may include sending at least one first notification message to a computing device associated with a first user prior to transmitting the anonymized transaction to enable the first user to approve the anonymized transaction.

[0034] Additionally or alternatively, embodiments may include sending at least one second notification message to a computing device associated with the second user.The at least one second notification message may be sent prior to transmitting the transaction to enable the second user to approve the transaction.

[0035] The at least one second notification message may be associated with one or more anonymized transactions and may include one or more data elements, including, for example, second product attributes and logistics elements.

[0036] Embodiments of the present invention may include a system for transmitting a transaction between a first node and a second node of a computer network. Embodiments of the system may include: a non-transitory memory device storing instructions; and a processor associated with the memory device and configured as a module to execute the instruction code. When executing the instruction code, the processor may be configured to:

[0037] receiving a request to transmit a transaction from a source node to a destination node;

[0038] extracting at least one data element from the received transaction request;

[0039] Obtain at least one condition element from a first database;

[0040] receiving a transaction corresponding to the request from a source node;

[0041] Anonymize transactions; and

[0042] Based on at least one of the at least one conditional element and the extracted at least one data element, the anonymized transaction is transmitted to a destination node. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The subject matter relating to the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification. However, the invention as to its organization and method of operation, as well as its objects, features, and advantages, will be further understood from the accompanying Figure 1 When read together, it is best understood by reference to the following detailed description, wherein:

[0045] Figure 1 is a block diagram depicting a computing device that may be included in a system for communicating anonymized transactions between a first node and a second node of a computer network according to some embodiments;

[0046] Figure 2Ais a block diagram depicting a system known in the art for transmitting transactions between a source node and a destination node in a computer network;

[0047] Figure 2B is a transaction flow diagram depicting a method known in the art for transmitting a transaction between a source node and a destination node in a computer network;

[0048] Figure 3A is a block diagram depicting a system for transmitting anonymized transactions between a source node and a destination node of a computer network according to some embodiments of the present invention;

[0049] Figure 3B is a transaction flow diagram depicting a method for transmitting anonymized transactions between a source node and a destination node of a computer network according to some embodiments of the present invention; and

[0050] Figure 4 is a flow chart depicting a method for transmitting anonymized transactions between a source node and a destination node of a computer network according to some embodiments of the present invention.

[0051] It will be understood that, for simplicity and clarity of illustration, the elements shown in the figures are not necessarily drawn to scale. For example, for clarity, the size of some elements may be exaggerated relative to other elements. In addition, reference numerals may be repeated in multiple figures to indicate corresponding or similar elements where deemed appropriate.

[0052] Detailed description of the invention

[0053] In the following detailed description, many specific details are set forth in order to provide a thorough understanding of the present invention. However, it will be appreciated by those skilled in the art that the present invention may be practiced without these specific details. In other cases, known methods, processes and components are not described in detail to avoid blurring the present invention. Some features or elements described about an embodiment may be combined with features or elements described about other embodiments. For the sake of clarity, the same or similar features or elements may not be discussed repeatedly.

[0054] Although embodiments of the present invention are not limited in this regard, discussions using terms such as, for example, "processing," "computing," "calculating," "determining," "establishing," "analyzing," "examining," and the like may refer to operations and / or processes of a computer, computing platform, computing system, or other electronic computing device that manipulates and / or converts data represented as physical (e.g., electronic) quantities within a computer's registers and / or memory to other data similarly represented as physical quantities within a computer's registers and / or memory or other information non-transitory storage medium that may store instructions for performing the operations and / or processes. Although embodiments of the present invention are not limited in this regard, the terms "plurality" and "a plurality" as used herein may include, for example, "multiple" or "two or more." The terms "plurality" or "a plurality" may be used throughout the specification to describe two or more components, devices, elements, units, parameters, and the like. The term "set" when used herein may include one or more items. Unless expressly provided, the method embodiments described herein are not limited to a particular order or sequence. Additionally, some of the described method embodiments or elements thereof may occur or be performed simultaneously, at the same point in time, or in parallel.

[0055] Embodiments of the present invention may include methods and systems for communicating anonymized transactions between a first node and a second node of a computer network.

[0056] Reference now Figure 1 , Figure 1 is a block diagram depicting a computing device that may be included in an embodiment of a system for communicating anonymized transactions between a first node and a second node of a computer network according to some embodiments.

[0057] The computing device 1 may include a controller 2, an operating system 3, a memory 4, an executable code 5, a storage system 6, an input device 7, and an output device 8. The controller 2 may be, for example, a central processing unit (CPU) processor, a chip, or any suitable computing device or computing-related device. The controller 2 (or one or more controllers or processors, possibly across multiple units or devices) may be configured to perform the methods described herein, and / or to perform or act as various modules, units, etc. More than one computing device 1 may be included in a system according to an embodiment of the present invention, and one or more computing devices 100 may act as a component of a system according to an embodiment of the present invention.

[0058] Operating system 3 may be or may include any code segment (e.g., a code segment similar to executable code 5 described herein) designed and / or configured to perform tasks involving coordination, scheduling, arbitration, supervision, control, or otherwise managing the operation of computing device 1 (e.g., scheduling the execution of software programs or tasks or enabling software programs or other modules or units to communicate). Operating system 3 may be a commercial operating system. It should be noted that operating system 3 may be an optional component, for example, in some embodiments, the system may include a computing device that does not require or include operating system 3.

[0059] The memory 4 may be or may include, for example, a random access memory (RAM), a read-only memory (ROM), a dynamic RAM (DRAM), a synchronous DRAM (SD-RAM), a double data rate (DDR) memory chip, a flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short-term memory unit, a long-term memory unit, or other suitable memory unit or storage device unit. The memory 4 may be or may include a plurality of possibly different memory units. The memory 4 may be a non-transitory readable medium of a computer or a processor, or a non-transitory storage medium of a computer, such as RAM. In one embodiment, a non-transitory storage medium such as the memory 4, a hard drive, another memory device, etc. may store instructions or codes that, when executed by a processor, cause the processor to perform the methods described herein.

[0060] The executable code 5 may be any executable code, such as an application, program, process, task, or script. The executable code 5 may be executed by the controller 2 under the control of the operating system 3. For example, the executable code 5 may be an application that may communicate, transmit, or send an anonymized transaction between a first node and a second node of a computer network, as further described herein. Although for clarity, Figure 1 Executable code 5 of a single project is shown, but the system according to some embodiments of the present invention may include multiple executable code segments similar to executable code 5, which can be loaded into memory 4 and cause controller 2 to execute the methods described herein.

[0061] The storage device system 6 may be or may include, for example, flash memory as known in the art, memory internal to or embedded in a microcontroller or chip as known in the art, a hard drive, a recordable CD-R drive, a Blu-ray Disc (BD), a Universal Serial Bus (USB) device, or other suitable removable and / or fixed storage unit. Data may be stored in the storage device system 6 and may be loaded from the storage device system 6 into the memory 4 where it may be processed by the controller 2. In some embodiments, in Figure 1Some of the components shown in the embodiment may be omitted. For example, the memory 4 may be a non-volatile memory having the storage capacity of the storage system 6. Therefore, although shown as a separate component, the storage system 6 may be embedded or included in the memory 4.

[0062] Input device 7 can be or can comprise any suitable input device, assembly or system, for example detachable keyboard or keypad, mouse etc.Output device 8 can comprise one or more (may be detachable) display or monitor, loudspeaker and / or any other suitable output device.As shown in frame 7 and 8, any applicable input / output (I / O) device can be connected to computing device 1.For example, can comprise wired or wireless network interface card (NIC), universal serial bus (USB) device or external hard disk drive in input device 7 and / or output device 8.It will be appreciated that, as shown in frame 7 and 8, any suitable number of input device 7 and output device 8 can be operably connected to computing device 1.

[0063] Systems according to some embodiments of the present invention may include components such as, but not limited to, multiple central processing units (CPUs) or any other suitable general-purpose or specific processors or controllers (e.g., a controller similar to controller 2), multiple input units, multiple output units, multiple memory units, and multiple storage device units.

[0064] For the convenience of the reader, Table 1 below contains the terms used throughout this document:

[0065] Table 1

[0066]

[0067]

[0068]

[0069] Reference now Figure 2A and Figure 2B , Figure 2A is a block diagram depicting a system for transmitting transactions between a source node and a destination node of a computer network 2000 as is known in the art, Figure 2B is a transaction flow diagram depicting a method for transmitting transactions between a source node and a destination node of a computer network 2000 as is known in the art.

[0070] like Figure 2A and 2BAs shown, a commercially available system for transmitting transactions between a source node and a destination node of a computer network 2000 may require a first user (e.g., a customer) who may be associated with a first computing device 10A and a second user (e.g., a merchant) who may be associated with a second computing device 10B to agree on the details of the transaction. For example, in the case where the transaction is a monetary exchange (ME) transaction, in which a product can be purchased in exchange for a monetary value, the customer and the merchant should agree on the attributes of the product, including, for example, the product's identity, price, payment terms, etc.

[0071] For example, as shown in step S101, a first user (eg, a customer) may use an operation such as Figure 1 A first user of computing device 10A (eg, a smartphone) connects (eg, via one or more computer networks such as the Internet) to a computer such as Figure 1 The second computing device 10B of device 100A may be associated with a second user (e.g., a merchant). As is known in the art, the first user may provide information (e.g., their payment card details) via a connection (e.g., over the Internet) 100A.

[0072] In another example, the first computing device 10A may be a payment card reader and the second computing device 10B may be a vending machine. As is known in the art, the first user may provide information (e.g., his payment card details) 100A to the second computing device 10B (e.g., a vending machine) through a payment card reader.

[0073] As shown in steps S102 and S103, the second computing device 10B may forward information 100B (e.g., credit card details) to an intermediate node 30 (e.g., an acquirer node). The intermediate node 30 (e.g., an acquirer) may in turn forward information 100C to a source node 40 (e.g., a credit card company).

[0074] As is known in the art, source node 40 (e.g., a credit card company) may communicate (e.g., through a credit card issuer) with at least one additional node (e.g., a bank server that may manage a customer's bank account). Source node 40 may request payment authorization from at least one additional node (e.g., a bank server), and may receive confirmation (e.g., payment approval) from at least one additional node (e.g., a bank server). For simplicity, in Figure 2A and 2B This element of the transaction is not depicted in .

[0075] As shown in step S104 , the source node 40 (eg, a credit card company) may return a confirmation 100C′ (eg, payment approval) to the intermediate node 30 (eg, an acquirer).

[0076] As shown in step S105 , the intermediary node 30 may transmit, send or transfer the transaction 100D (eg, payment) to the destination node 20 (eg, a bank server that may process a merchant's bank account).

[0077] As shown in step S106 , the intermediate node 30 may transmit a notification 100B′ (eg, payment approval) to a second computing device 10B associated with the second user (eg, an online shopping website server or a vending machine).

[0078] As shown in step S107 , the second computing device 10B may continue to serve the first user 100A′ (eg, provide, deliver or transport products) according to the specific circumstances of the transaction (eg, shopping from an online server or purchasing products from a vending machine).

[0079] State-of-the-art systems for transmitting transactions (eg, ME transactions that may purchase products from an online shopping site or an unattended vending machine) may have several limitations or drawbacks, at least from the perspective of a second user (eg, a merchant).

[0080] For example, an ME transaction may require the presence of a merchant-side computing device 10B. This requirement may not be feasible in certain scenarios, such as when a product (e.g., a sandwich) may be unattended (e.g., at a market stall), and the first user (e.g., a customer) is trusted to pay for the product he may purchase.

[0081] Additionally, the second computing device 10B may need to comply with regulatory restrictions for maintaining or storing information related to the first user's attributes, including, for example, the user's bank account, credit card number, etc.

[0082] Embodiments of the present invention provide practical applications for transmitting anonymized transactions between a source node that may be associated with a first user (e.g., a server of the user's credit card company and / or a bank server holding the user's bank account) and a destination node (e.g., a computing device associated with a merchant) in order to circumvent the limitations or disadvantages described.

[0083] Reference now Figure 3A , which is a block diagram depicting a system 1000 for transmitting anonymized transactions between a source node 40 and a destination node 20 in a computer network 2000 by at least one processor of an intermediate node 30 according to some embodiments of the present invention. Figure 3B, which is a transaction flow chart depicting the steps of a method for transmitting anonymized transactions between a source node 40 and a destination node 20 of a computer network 2000 according to some embodiments of the present invention.

[0084] The computer network 2000 may be or may include, for example, a local area network (e.g., Ethernet), a wide area network (e.g., the Internet), a cellular network, and / or any combination thereof. Figure 3A As shown, the computer network 2000 may include one or more computing devices or nodes 70 (e.g., 70A, 70B, 70C, 70D, 70E), such as routers, gateways, switches, etc., for transmitting or providing routing for transactions between elements of the system 1000 and / or the network 2000 as known in the art.

[0085] Figure 3A and 3B The examples presented herein relate to a monetary exchange (ME) transaction in which money may be transferred between a first user, who may be a customer, and a second user, who may be a merchant, in exchange for a product 50, however it should be appreciated that embodiments of the present invention may be implemented in other configurations to reliably transfer anonymized transactions between a first entity and a second entity.

[0086] exist Figure 3A and 3B In the example depicted:

[0087] The source node 40 may be, for example, a first bank server that handles the customer's bank account and / or a server of a credit card issuer associated with the customer's credit card;

[0088] The destination node 20 may be, for example, a second bank server that handles the merchant's bank account; and

[0089] The intermediary node 30 may be, for example, an acquirer server, which may maintain a merchant's bank account, as is known in the art.

[0090] As shown in step S201, a first user associated with a first user device or computing device 10A (e.g., a user's smartphone) can obtain at least one reference or pointer to an entry in a user-side database 60A that may be associated with a product 50. For example, the product 50 (e.g., a sandwich that may be served at an unattended stall) may be associated with or may include computer-readable data (e.g., a barcode, a quick response (QR) code, etc.), which may include a reference 200E (e.g., a uniform resource locator (URL)) to an entry in the user-side database 60A, as known in the art. The first user can use the first user device 10A to read the computer-readable data (e.g., by scanning a barcode through an appropriate application) to obtain a reference 200E to an entry in the user-side database 60A, as known in the art.

[0091] As shown in steps S202 and S203 , the first user device 10A may communicate with the user-side database 60A using the reference 200E, and obtain one or more data elements 200F about or associated with the product 50 from the corresponding entry.

[0092] According to some embodiments, data element 200F may include at least one user-side product attribute, including, for example, product type (e.g., type of sandwich), product price, one or more possible payment options (e.g., via one or more payment cards), etc.

[0093] Additionally or alternatively, in the case where the product is a substantial product that can be offered to the first user for free taking and the first user can be trusted to pay for it (e.g., cookies or sandwiches on an unattended stall), the data element 200F may include at least one logistical indicator associated with the product. The logistical indicator may include, for example, information that allows tracking of product sales (e.g., keeping inventory), such as the location of the offered product (e.g., from which unattended stall the sandwich was taken), the number of a particular type of product in stock, the total amount of the product in stock, the number of a particular type of product presented for sale, the total amount of the product presented for sale, etc.

[0094] Additionally or alternatively, data element 200F may include at least one user attribute or data item associated with the second user. For example, in the case of an ME transaction, data element 200F may include a number or identifier of a bank account associated with a merchant (e.g., a seller of sandwiches).

[0095] Additionally or alternatively, data element 200F may include a reference (e.g., a URL) to an intermediary node 30. For example, where the transaction is an ME transaction, intermediary node 30 may be a computing device such as a server associated with or belonging to an acquirer (e.g., Figure 1 Elements 1).

[0096] The term "intermediate" may be used in this context to indicate that the intermediary node 30 may facilitate the role of a buffer or hub between a first party to a transaction, such as a user who may connect to a source node (e.g., their credit card issuer) (e.g., via a first computing device 10A) and a second party to a transaction, such as a merchant who may connect to a destination node (e.g., their bank server) (e.g., via a second computing device 10B), as explained herein. In some embodiments, the intermediary node 30 may communicate with at least one of the source node 40 and the destination node 20 to facilitate transactions (e.g., the transfer of at least one anonymized transaction payload or data structure) between the source node 40 and the destination node 20, as explained herein.

[0097] As shown in step S204, the first user may send a request 200A to transmit a transaction (e.g., transfer funds) from a source node to a destination node via a first user device 10A (e.g., a user's smartphone) to the intermediate node 30. Transmitting a transaction typically involves transmitting, transferring, or sending a data structure describing the transaction from node to node.

[0098] Regarding the example of purchasing a product (e.g., a sandwich from an unattended stall), the transaction may be a ME transaction that transfers money from a source node 40 (e.g., a customer's card issuer and / or bank account) to a destination node 20 (e.g., a merchant's bank account). Thus, request 200A may be or may include a data structure that may include, for example, one or more of: an identification of the customer's card issuer and / or bank account; an identification of the merchant's bank account; the type of transaction (e.g., a single payment, a monthly payment, etc.); and the price of the product purchased (e.g., a sandwich).

[0099] As described herein, the intermediate node 30 may then transmit or send an anonymous version 200B of the requested transaction to the destination node 20. The anonymous version 200B may be or may include a data structure that may describe a transaction from the source node 40 to the destination node 20, and may be devoid of information that may belong to or may define the users and / or their respective user devices 10A. For example, the transaction 200B may be or may include a data structure that may include, for example, one or more of the following:

[0100] The identification of the merchant's bank account;

[0101] The type of transaction; and

[0102] The amount paid for a purchased product (e.g., a sandwich).

[0103] Intermediate node 30 may receive request 200A to transfer a transaction from source node 40 to destination node 20 and may process the request as explained herein.

[0104] According to some embodiments, request 200A may include a value of a first user attribute of a first user associated with a source node. For example, in an implementation where the transaction is an ME transaction, source node 40 may be, for example, a bank server that handles a bank account of the first user and / or a server of a credit card issuer associated with a credit card of the first user. Thus, the value of the first user attribute may be a bank account number of the first user and / or a credit card number of the first user (e.g., a customer).

[0105] Additionally or alternatively, the request 200A may include a value of a second user attribute associated with the destination node regarding the second user. For example, in an implementation where the transaction is an ME transaction, the destination node 20 may be, for example, a bank server that processes a merchant's bank account. Therefore, the value of the second user attribute may be a bank account number of the second user (e.g., merchant).

[0106] Additionally or alternatively, the request 200A may include the values ​​of the user-side product attributes obtained from the user-side database 60 A. Taking the unattended sandwich stand as an example, the values ​​of the user-side product attributes may be the type of sandwich and its price.

[0107] Additionally or alternatively, the request 200A may include a value of a logistic indicator obtained from the user-side database 60 A. Taking an unattended sandwich stand as an example, the value of the logistic indicator may be a location (eg, a specific stand number) where the sandwiches are displayed.

[0108] Additionally or alternatively, request 200A may include a reference 200E (e.g., a URL) to a corresponding entry in user-side database 60A. As described herein, intermediary node 30 may use reference 200E to verify that information presented to the first user by user-side database 60A (e.g., the price of a product) matches information to be included in a transaction between source node 40 and destination node 20 (e.g., the amount of money to be exchanged between source node 40 and destination node 20).

[0109] According to some embodiments, the intermediate node 30 may receive the transaction request 200A and extract or copy at least one data element therefrom, including, for example, one or more first user attribute values, one or more second user attribute values, one or more user-side product attribute values, and / or one or more logistics indicator values.

[0110] As shown in steps S205 and S206, the intermediate node 30 may communicate 200G with the intermediate-side database 60B and obtain at least one condition element 200G' therefrom. For example, in an implementation where the transaction is an ME transaction, the at least one condition element may be related to a monetary transaction transaction and may include, for example: one or more intermediate-side product attributes; one or more acceptable payment methods (e.g., credit cards and / or debit cards that may be used for ME transactions); and one or more commission rates that the intermediate node 30 may levy for transmitting the transaction (e.g., commission rates that may be specific to one or more payment methods).

[0111] In some embodiments, at least one conditional element 200G' can be used to prioritize one or more parameters of a transaction. For example, in an implementation where the transaction is an ME transaction, a merchant can prioritize payment methods, such as by offering a more attractive price when using a preferred payment method to prioritize one payment method (e.g., a first credit card type) over another (e.g., a second credit card). The intermediary node 30 can be configured to communicate with the first computing device 10A and configure the computing device 10A to present a higher priority payment method (e.g., suggesting that a preferred credit card be used to perform an ME transaction).

[0112] Intermediate node 30 may communicate with source node 40 and may receive a transaction corresponding to transaction request 200A from source node 40. For example, assume that transaction request 200A is a request for an ME transaction and may include a transfer of a monetary value from source node 40 to destination node 20. Intermediate node 30 may communicate with source node 40 to pass the transaction request to source node 40 and receive a transaction corresponding to transaction request 200A (e.g., for the transfer of the same monetary value), which is destined to or targeted at destination node 20, as described in detail herein.

[0113] As shown in step S207, the intermediate node 30 may communicate 200C with the source node 40 based on the first user attribute value. For example, in an implementation where the transaction is an ME transaction, the intermediate node 30 (e.g., an acquirer server) may communicate 200C with the source node 40 (e.g., an issuer and / or a bank server) based on the first user attribute value (e.g., a customer's credit card number). Communication 200C may correspond to request 200A because it may include information originating from transaction request 200A. In this example, communication 200C may include a request from the source node 40 (e.g., a bank server and / or an issuer) to the destination node 20 (e.g., a bank server associated with a merchant) for payment authorization of a monetary value included in transaction request 200A.

[0114] As shown in step S210 , the intermediary node 30 (eg, acquirer) may receive the transaction 200C′ (eg, confirmation and / or payment approval) from the source node 40 (eg, card issuer and / or bank server).

[0115] Additionally or alternatively, communication 200C of intermediate node 30 may include commands and / or configurations for source node 40. Source node 40 may be configured to respond to command 200C by sending transaction 200C' corresponding to transaction request 200A from source node 40 to destination node 20 via intermediate node 30.

[0116] Regarding the example of ME transaction, transaction request 200A may include a request to transfer a specific amount of money between source node 40 and destination node 20. Communication 200C may include a command or instruction to cause source node 40 (e.g., a card issuer and / or bank server) to perform an action. In this example, intermediate node 30 may command source node 20 to process a payment or funds transfer (e.g., authorization of a pending payment request, as described above). Source node 40 may be configured to react to command 200C by sending payment transaction 200C' to destination node 20 (e.g., a bank server that handles a merchant bank account) via intermediate node 30.

[0117] According to some embodiments, the intermediate node 30 may be configured to receive the transaction 200C' and anonymize the transaction. For example, the intermediate node 30 may exclude, clear or remove one or more data elements related to the user attribute or identification of the first user, or change these elements to be anonymous. Anonymization may make it difficult or impossible for a third party to identify a party to the transaction, or to associate the transaction with a party. In some embodiments, at least one processor of the intermediate node 30 may exclude at least one value of the first user attribute (e.g., customer) from the requested transaction.

[0118] For example, in an implementation where the transaction is an ME transaction, at least one processor of the intermediary node 30 may be configured to anonymize the transaction so as not to include attributes of the first user, such as the first user's name, credit card number, bank account number, phone number, etc. In this case, the intermediary node 30 may delete one or more fields that include the attributes of the first user (e.g., bank account number) and may be included in the transaction request 200A, so that the data structure or transaction payload may be shorter. Additionally or alternatively, the intermediary node 30 may enter a space or an obviously incorrect value (e.g., XXXXX for name) in a personal data field.

[0119] As shown in step 211, the intermediate node 30 (e.g., acquirer) may transmit or transfer the anonymized transaction 200B from the intermediate node 30 to the destination node 20. The transmission of the anonymized transaction 200B may be based on or in accordance with at least one of the following items: at least one conditional element and at least one data element copied, obtained, or extracted from the transaction request 200A. For example, the requirements of the conditional element may be compared with the data element, and if the requirements are met, then the transmission is performed, and if the requirements are not met, then the transmission is not performed.

[0120] Destination node 20 may receive anonymized transaction 200B and may be configured to react thereto according to a particular implementation.

[0121] For example, in an implementation where the transaction is an ME transaction, the anonymized transaction 200B may include (e.g., as a transaction payload) a monetary value that may be the same or equivalent (e.g., in the case of a change in currency) to the product price (e.g., included in one or more user-side product attributes in the transaction request 200A). In this example, the destination node 20 may be a bank server that handles a merchant's bank account and may receive the anonymized ME transaction 200B. The destination node 20 may react to the transaction 200B by crediting the merchant's bank account with the monetary value included in the transaction.

[0122] In another example where the transaction is an ME transaction, a monetary value that may be equal to a commission imposed by the intermediary node 30 (eg, included in one or more conditional elements) may be removed from the anonymized transaction 200B.

[0123] In another example where the transaction is an ME transaction, if, for example, the credit card details (such as included in the first user attribute in the transaction request 200A) do not comply with one or more acceptable payment methods (such as included in one or more conditional elements), the intermediary node 30 may refrain from sending the reason why the anonymized transaction 200B was not sent to the destination node 20. Alternatively or additionally, if the intermediary node 30 (e.g., an acquirer) is configured to not allow ME transactions using a particular type of credit card (e.g., Visa), the intermediary node 30 may not send the anonymized transaction 200B to the destination node 20, and may therefore prevent completion of the ME transaction using a restricted credit card.

[0124] In another example where the transaction is an ME transaction, the intermediate node 30 can compare at least one user-side product attribute (e.g., obtained by the first user device or computing device 10A from the user-side database 60A and included in the transaction request 200A) and at least one corresponding intermediate-side product attribute (e.g., obtained from the intermediate-side database 60B) to verify that the information presented to the first user by the user-side database 60A (e.g., the price of the product) matches the information to be included in the transaction between the source node 40 and the destination node 20 (e.g., the amount of currency to be exchanged between the source node 40 and the destination node 20).

[0125] In some embodiments, the intermediary node 30 may utilize a reference 200E to the user-side database 60A to present a query to the user-side database 60A regarding the value of at least one user-side product attribute (e.g., the price of the product presented to the customer on the first computing device 10A). The intermediary node 30 may obtain a query response from the user-side database 60A and may analyze the response to verify the value of the at least one product attribute (e.g., the price) presented to the first user (e.g., the customer) on the first user's computing device (e.g., their smartphone).

[0126] One or more processors of the intermediate node 30 may be configured to transmit the anonymized transaction 200B to the destination node 20 based on or in accordance with verification of the value of the at least one product attribute. For example, if the verification is positive, the transaction may be sent, and if the verification is negative, the transaction may not be sent.

[0127] According to some embodiments, as shown in steps S208 and S209, at least one processor of the intermediate node 30 may be configured to send at least one user notification message 200A' to a computing device (e.g., first device 10A) that may be associated with a first user (e.g., a customer). The user notification message 200A' may be sent before the anonymized transaction 200B is transmitted to the destination node 20 so as to enable the first user (e.g., the customer) to approve the anonymized transaction.

[0128] Alternatively or additionally, the intermediary node 30 may configure the first computing device 10A to present or display (eg, in a computer program such as a computer program that is not provided to a first user (eg, a client)) the first computing device 10A. Figure 1 The device may display one or more data elements related to the transaction on a screen of an output device 8 and allow a user to select or interact with the presented data.

[0129] For example, the intermediary node 30 may configure the first computing device 10A to present one or more intermediary-side product attributes (e.g., the price that will be charged to the customer's bank account) and enable the user to verify or confirm that they wish to purchase the product. The intermediary node 30 may then proceed with processing the transaction based on the user's approval, as detailed herein (e.g., transmitting the anonymized transaction to the destination node 20 only if the customer approves to do so).

[0130] In another example, the intermediary node 30 may configure the first computing device 10A to present or display one or more conditional elements related to the payment method (e.g., a first price or commission for using a first payment card, a second price or commission for using a second payment card, etc.), and enable the user to select (e.g., by selecting a graphical representation on the screen) their preferred payment method. The intermediary node 30 may then continue to process the transaction according to the user's selection, as described in detail herein (e.g., communicating with a source node 40, such as a card issuer that may be associated with the selected payment card).

[0131] As shown in step S212 , at least one processor of the intermediate node 30 may be configured to send at least one second notification message 200D to a second computing device 10B associated with a second user (eg, a merchant).

[0132] According to some embodiments, at least one second notification message 200D may be related to or associated with one or more anonymized transactions 200B, and may include, for example, one or more corresponding intermediate-side product attributes and one or more corresponding logistics elements so as to notify a second user about one or more conditional elements of the one or more transactions.

[0133] For example, the intermediary node 30 may send a second notification message 200D before transmitting the anonymized transaction 200B so as to configure the second user device 10B (e.g., associated with or belonging to a merchant) to display a message that may prompt the user (e.g., the merchant) to approve the anonymized transaction. The second user device 10B may receive the user's approval and may transmit the approval to the intermediary node 30, which may then transmit the anonymized transaction 200B to the destination node 20.

[0134] In another example, the intermediate node 30 may send a second notification message 200D to a user's (e.g., merchant's) smartphone based on predetermined conditions (e.g., after a predetermined number or percentage of products have been sold) in order to track transactions (e.g., track inventory).

[0135] In another example, the second notification message 200D may include a logistic element, such as the location of one or more presented products. This may enable the intermediary node 30 to notify the user (e.g., merchant) of the location of a successful (e.g., busy) or unsuccessful (e.g., empty) point of sale via the second user device or computing device 10B.

[0136] In another example, the intermediary node 30 may send a second notification message 200D to a second computing device 10B (e.g., a smartphone) of a user (e.g., a merchant) at a predefined time (e.g., at the end of a day). This may enable the intermediary node 30 to aggregate transactions at a predetermined time (e.g., aggregate sales and revenue at the end of a day).

[0137] Those skilled in the art will appreciate that in implementations that may not necessarily include monetary transactions, including, for example, polling (e.g., in a public vote or survey) or election (e.g., between political candidates) systems, embodiments of the present invention may provide methods for controlling the transmission of anonymized transactions between a source node 40 and a destination node 20 of a computer network 2000.

[0138] For example, in the context of a municipal election campaign (e.g., a candidate is being voted in to serve as mayor of a municipality), one or more citizens may use their respective user devices 10A to select a particular political candidate. The selection may be accomplished, for example, by selecting one of a plurality of candidates via a dedicated software application that may be executed on the computing device 10A of the respective citizen or user. The request 200A may be sent from the device 10A to the intermediate node 30 and may include one or more data elements related to the citizen's identity (e.g., their name, identification number, etc.) and their selection (e.g., their preferred candidate).

[0139] In such an embodiment, the intermediate node 30 can be a computing device (e.g., a server) that can be associated with a central election commission, and the intermediate-side database 60B can store information related to candidates, political parties, and voters about each municipality (e.g., which candidates are electable in each municipality).

[0140] The intermediate node 30 may forward the request 200A as a message 200C to a source node 40, which in this example may be a computing device (e.g., a server) that may be associated with a civil registrar and may maintain a list of eligible voters (e.g., citizens who are allowed to vote based on their nominal age, registered residence, etc.).

[0141] As explained herein, the intermediate node 30 may control or configure the source node 40 to perform an action. In this example of a municipal election scenario, the intermediate node 30 may configure the source node 40 to:

[0142] determine whether a particular citizen is eligible to vote;

[0143] Maintaining records associated with each voter to determine whether the voter has voted (e.g., to prevent double voting); and

[0144] The voting transaction 200C', including, for example, approval of the vote, is returned via the intermediate node 30 to one or more destination nodes 20 (eg, a server associated with the municipality where the vote was conducted).

[0145] Intermediate node 30 may receive transaction 200C' from source node 40 and may:

[0146] Analyzing the received transaction 200C' according to at least one conditional element;

[0147] anonymize the received transaction 200C'; and

[0148] The anonymous version 200B of the transaction 200C′ is forwarded to one or more destination nodes 20 .

[0149] Regarding the municipal election example, the intermediate node 30 may:

[0150] analyzing the received voting transaction 200C' according to at least one conditional element by verifying that the user's request complies with data included in the intermediate-side database 60B (e.g., the user has selected a candidate representing the city in which the voter is registered);

[0151] anonymizing voting transaction 200C' (eg, omitting the voter's name or identification number) to produce anonymized transaction 200B; and

[0152] The anonymized transaction 200B is sent to one or more relevant or corresponding destination nodes 20 (eg, a server associated with the particular city for which the user voted).

[0153] One or more related or corresponding destination nodes 20 may be configured to react to the anonymized transaction 200B. With respect to the election example, one or more related or corresponding destination nodes 20 may count incoming votes and determine the winner of the election.

[0154] Thus, embodiments of the present invention may transmit one or more transactions (e.g., voting requests of one or more users) from a source node 20 (e.g., a civil registration server) to a destination node (e.g., a server of a particular city) in the following manner:

[0155] May be controlled or limited by the configuration of the intermediary node 30 (e.g., only if the user is eligible to vote in the requested city); and

[0156] Anonymisation is performed to exclude information that should not be processed or maintained by the destination node 20 (eg, identification details of the voter).

[0157] Reference now Figure 4 , which is a flowchart depicting a method according to some embodiments of the present invention for an intermediate node (e.g., Figure 3A element 30) of at least one processor (e.g., Figure 1 Elements 2) in computer networks (e.g. Figure 3A 2000) of the source node (e.g., Figure 3A 40) and the destination node (e.g. Figure 3A Anonymous transactions are transmitted between elements 20).

[0158] As shown in step S1005, at least one processor 2 of the intermediate node 30 may receive a request to transmit a transaction from the source node 40 to the destination node 20 (eg, Figure 3A For example, request 200A may be or may include a request to transfer a ME transaction, which may include transferring funds or currency from a source node 40 (e.g., a server that handles a first bank account) to a destination node 20 (e.g., a second server that handles a second bank account).

[0159] As shown in step S1010, at least one processor 2 of the intermediate node 30 can extract at least one data element from the transaction request. Regarding the example of the ME transaction, the processor 2 can extract, for example: one or more user attributes related to the first user (e.g., the first user's bank account, the user's credit card number, etc.); a reference (e.g., an IP address) of the source node 40 (e.g., a bank server that handles the first user's bank account); one or more user attributes about the second user (e.g., the second user's bank account); a reference (e.g., an IP address) of the destination node 20 (e.g., a bank server that handles the second user's bank account); and a monetary value that needs to be transmitted from the source node 40 to the destination node 20.

[0160] As shown in step S1015, at least one processor 2 of the intermediate node 30 can obtain information from a first database (e.g., Figure 3A Element 60B) obtains at least one conditional element. With respect to the example of an ME transaction, the at least one conditional element may be any condition that may be imposed on the ME transaction, including, for example, a commission that may be payable on a money transfer, a list of one or more acceptable credit cards (e.g., that the intermediate node 30 may accept for the purpose of a money transaction), etc.

[0161] At least one processor 2 of the intermediate node 30 may communicate with a source node 40 (eg, Figure 3A As shown in step S1020, the source node 40 may respond to the communication 200C, and the intermediate node 30 may receive a transaction corresponding to the request 200A from the source node 40 (e.g., Figure 3A Regarding the example of an ME transaction, the communication 200C may be a request to transmit the monetary value included in the request 200A from the source node 40 to the destination node 20 via the intermediate node 30.

[0162] As shown in step S1025, at least one processor 2 of the intermediate node 30 may anonymize the received transaction 200C'. With regard to the example of the ME transaction, the processor 2 of the intermediate node 30 may anonymize the transaction so as not to include the attributes of the first user, such as the name, credit card number, and / or bank account number of the first user, as described in detail herein.

[0163] As shown in step S1030, at least one processor 2 of the intermediate node 30 may anonymize the transaction (e.g., only when an acceptable credit card is used) based on at least one of the at least one conditional element (e.g., only when an acceptable credit card is used) and the extracted at least one data element (e.g., transferring monetary value between a first bank account and a second bank account). Figure 3A The element 200B) is transmitted from the intermediate node 30 to the destination node 20.

[0164] Embodiments of the present invention include several improvements over existing techniques for transmitting transactions between source and destination nodes in a computer network.

[0165] For example, an embodiment may allow a destination node to act as a passive receiver. In embodiments where the transaction is an ME transaction (e.g., in the unattended stall example), this may provide a practical application that may allow a merchant to not be connected to a network during the sales process (e.g., work offline), or even omit any computing device from the point of sale, while maintaining the ability to be paid for and maintain inventory of the products sold.

[0166] In another example, an embodiment can enable reliable transmission of anonymized transactions. In embodiments where the transaction is an ME transaction, the customer can be anonymous from the merchant's perspective. This can provide practical applications for merchants (e.g., small-scale merchants) that can avoid regulatory and / or resource (e.g., hardware and / or software) related restrictions that may be associated with maintaining and / or processing sensitive user information such as user identities, credit card numbers, bank account numbers, etc. In fact, the merchant can be completely removed from the transaction in order to keep the sensitive information flowing between the customer and the acquirer node, rather than between the customer and the merchant as commercially available systems typically perform.

[0167] As described herein, embodiments may further include feedback from the intermediary node 30 to the first user regarding the transaction fulfillment. In embodiments where the transaction is an ME transaction (e.g., in response to purchasing a product from an unattended point of sale), this may provide a practical application for providing a presentable proof of purchase to the customer.

[0168] Although certain features of the present invention have been illustrated and described herein, those of ordinary skill in the art will appreciate that many modifications, substitutions, changes and equivalents will occur to them. Therefore, it should be understood that the appended claims are intended to cover all such modifications and changes that fall within the true spirit of the present invention. In addition, the features or elements of different embodiments may be used or combined with other embodiments.

Claims

1. A method for transmitting a transaction between a source node and a destination node of a computer network by at least one processor of an intermediate node, the intermediate node being associated with a first database, the method comprising: receiving a request to transmit the transaction from the source node to the destination node; Extracting at least one data element from the request of the transaction, wherein the extracted at least one data element further comprises a reference to an entry in a second database, wherein the extracted at least one data element is selected from the list consisting of: a value of a first user attribute of a first user associated with the source node; a value of a second user attribute of a second user associated with the destination node; The values ​​of the product attributes; and The value of the logistics indicator; Obtain at least one condition element from the first database; receiving a transaction corresponding to the request from the source node; anonymize said transactions; presenting a query to the second database regarding the value of at least one product attribute; Obtaining a response from the second database; and analyzing the response to verify the value of the at least one product attribute; and An anonymized transaction is transmitted from the intermediate node to the destination node based on the verification of the value of the at least one product attribute, the at least one conditional element, and the extracted at least one data element. 2 . The method of claim 1 , further comprising anonymizing the transaction by excluding at least one value of the first user attribute from the requested transaction.

3. The method according to claim 1, wherein: The transaction is a monetary transaction, and wherein the method further comprises anonymizing the transaction so as not to include attributes of the first user.

4. The method according to claim 2, wherein: The transaction is a monetary transaction, and wherein the method further comprises anonymizing the transaction so as not to include attributes of the first user.

5. The method according to any one of claims 1-4, further comprising transmitting the anonymized transaction to the destination node based on verification of the value of the at least one product attribute.

6. The method according to any one of claims 1 to 4, wherein: The transaction is a monetary transaction transaction, and wherein the at least one conditional element is related to the monetary transaction transaction and is selected from the list consisting of: Second product attributes; Commissions; and Acceptable payment methods.

7. The method of any one of claims 1-4, further comprising, prior to transmitting the anonymized transaction, sending at least one first notification message to a computing device associated with the first user to enable the first user to approve the anonymized transaction.

8. The method of any one of claims 1-4, further comprising sending at least one second notification message to a computing device associated with the second user.

9. The method according to claim 8, wherein: The at least one second notification message is sent prior to transmitting the transaction to enable the second user to approve the transaction.

10. The method according to claim 8, wherein: The at least one second notification message is related to one or more anonymized transactions, and wherein the at least one second notification message comprises one or more data elements selected from a list consisting of second product attributes and logistic elements.

11. The method according to claim 9, wherein: The at least one second notification message is related to one or more anonymized transactions, and wherein the at least one second notification message comprises one or more data elements selected from a list consisting of second product attributes and logistic elements.

12. A system for transmitting a transaction between a first node and a second node in a computer network, the system comprising: a non-transitory memory device storing instructions; and a processor associated with the memory device and configured as a module for executing instruction codes, such that when the processor executes the instruction codes, the processor is configured to: receiving a request to transmit the transaction from a source node to a destination node; Extracting at least one data element from the received transaction request, wherein the extracted at least one data element further comprises a reference to an entry in the second database, wherein the extracted at least one data element is selected from the list consisting of: a value of a first user attribute of a first user associated with the source node; a value of a second user attribute of a second user associated with the destination node; The values ​​of the product attributes; and The value of the logistics indicator; Obtain at least one condition element from a first database; receiving a transaction corresponding to the request from the source node; anonymize said transactions; presenting a query to the second database regarding the value of at least one product attribute; Obtaining a response from the second database; and analyzing the response to verify the value of the at least one product attribute; and Based on the verification of the value of the at least one product attribute, the at least one conditional element, and the extracted at least one data element, an anonymized transaction is transmitted to the destination node.

13. The system according to claim 12, wherein: The processor is further configured to anonymize the transaction by excluding at least one value of the first user attribute from the requested transaction; The anonymization excludes attributes of the first user.

14. The system according to claim 12, wherein: The transaction is a monetary transaction, and wherein the processor is further configured to anonymize the transaction so as not to include attributes of the first user.

15. The system of claim 13, wherein: The transaction is a monetary transaction, and wherein the processor is further configured to anonymize the transaction so as not to include attributes of the first user.

16. The system according to any one of claims 12 to 15, wherein: The processor is further configured to transmit the anonymized transaction to the destination node based on verification of the value of the at least one product attribute.

17. The system according to any one of claims 12 to 15, wherein: The transaction is a monetary transaction transaction, and wherein the at least one conditional element is related to the monetary transaction transaction and is selected from the list consisting of: Second product attributes; Commissions; and Acceptable payment systems.

18. The system according to any one of claims 12 to 15, wherein: The processor is also configured to, prior to transmitting the anonymized transaction, send at least one first notification message to a computing device associated with the first user to enable the first user to approve the anonymized transaction.

19. The system according to any one of claims 12 to 15, wherein: The processor is also configured to send at least one second notification message to a computing device associated with the second user.

20. The system of claim 19, wherein: The at least one second notification message is sent prior to transmitting the transaction to enable the second user to approve the transaction.

21. The system of claim 19, wherein: The at least one second notification message is related to one or more anonymized transactions, and wherein the at least one second notification message comprises one or more data elements selected from a list consisting of second product attributes and logistic elements.

22. The system of claim 20, wherein: The at least one second notification message is related to one or more anonymized transactions, and wherein the at least one second notification message comprises one or more data elements selected from a list consisting of second product attributes and logistic elements.