NL2026430B1 - A method of supporting identification of customer data related to a merchant and a server arranged for supporting a method of supporting identification of customer data related to a merchant, using a payment means of the customer. - Google Patents
A method of supporting identification of customer data related to a merchant and a server arranged for supporting a method of supporting identification of customer data related to a merchant, using a payment means of the customer. Download PDFInfo
- Publication number
- NL2026430B1 NL2026430B1 NL2026430A NL2026430A NL2026430B1 NL 2026430 B1 NL2026430 B1 NL 2026430B1 NL 2026430 A NL2026430 A NL 2026430A NL 2026430 A NL2026430 A NL 2026430A NL 2026430 B1 NL2026430 B1 NL 2026430B1
- Authority
- NL
- Netherlands
- Prior art keywords
- merchant
- customer
- server
- loyalty
- card
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 67
- 238000012508 change request Methods 0.000 claims description 9
- 150000003839 salts Chemical class 0.000 claims description 5
- 239000003205 fragrance Substances 0.000 claims 1
- 230000009286 beneficial effect Effects 0.000 description 9
- 238000004891 communication Methods 0.000 description 4
- 230000000694 effects Effects 0.000 description 4
- 238000007620 mathematical function Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
- G06Q30/0238—Discounts or incentives, e.g. coupons or rebates at point-of-sale [POS]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
- G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
- G06Q30/0226—Incentive systems for frequent usage, e.g. frequent flyer miles programs or point systems
- G06Q30/0229—Multi-merchant loyalty card systems
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Development Economics (AREA)
- Strategic Management (AREA)
- Finance (AREA)
- Game Theory and Decision Science (AREA)
- Entrepreneurship & Innovation (AREA)
- Economics (AREA)
- Marketing (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Cash Registers Or Receiving Machines (AREA)
Abstract
A method (1, 101, 201) of supporting identification, by a server (17), of customer data related to a merchant, using a payment means, such as a payment card, of said customer, wherein said server comprises: - a user register (19) comprising customer identifications for identifying customers, wherein each of said customer identifications is associated with a customer data and a hash value of a financial institution related data, such as bank related data, - a merchant register (21) comprising merchant identifications for identifying merchants, wherein each of said merchant identifications is associated with one or more loyalty program identifications, wherein said merchant register further comprises merchant display data associated with said customer identifications; - a loyalty program register (23) comprising access information for accessing loyalty cards servers associated with corresponding loyalty program identifications, wherein said loyalty cards servers comprise customer display data associated with loyalty cards.
Description
Title A method of supporting identification of customer data related to a merchant and a server arranged for supporting a method of supporting identification of customer data related to a merchant, using a payment means of the customer.
Background According to a first aspect, the present disclosure relates to a method of supporting identification, by a server, of customer data related to a merchant, using a payment means, such as a payment card, of said customer.
According to a second aspect, the present disclosure relates to a server arranged for supporting a method of supporting identification, by said server, of customer data related to a merchant, using a payment means, such as a payment card, of said customer.
The present disclosure is directed to a server which comprises a user register comprising customer identifications for identifying customers, wherein each of said customer identifications is associated with a customer data and a hash value of a financial institution related data, such as bank related data.
It further comprises a merchant register comprising merchant identifications for identifying merchants, wherein each of said merchant identifications is associated with one or more loyalty program identifications, wherein said merchant register further comprises merchant display data associated with said customer identifications.
It even further comprises a loyalty program register comprising access information for accessing loyalty cards servers associated with corresponding loyalty program identifications, wherein said loyalty cards servers comprise customer display data associated with loyalty cards.
The method according the present disclosure comprises the steps of: - receiving, by said server, from a card reader, an identification request message for identifying said customer, wherein said identification request message comprises financial institution related data stored onto said payment means that identify a financial institution account number of said customer and wherein said message comprises a merchant identification for identifying said merchant; - creating, by said server, using a one-way hash function, a hash value by hashing said financial institution related data and, preferably, a salt value; - determining, by said server, an associated customer identification in said user register based on said hash value; - determining, by said server, one or more loyalty program identifications associated with said received merchant identification in said merchant register; - accessing, by said server, a loyalty card server using access information in said loyalty program register corresponding to said determined one or more loyalty program identifications; - retrieving, by said server, from said loyalty card server a loyalty card, by providing said loyalty card server with said customer identification and said one or more loyalty program identifications; and - transmitting, by said server, to a merchant device, said retrieved loyalty card.
The card reader, preferably a merchant device comprising the card reader, is coupled to the server. To this end, the card reader and/or the merchant device, may be registered with the server. The server is arranged for receiving an identification request message from the card reader, for instance after a customer indicated he/she wants to buy something using a payment card.
Within the context of the present disclosure a payment card is to be understood as a physical bank card or credit card as well as an electronic device emulating a payment card or EMV means.
The card reader may be connected to the server in several manners, for example using a public communication network. A public communication network is, for example, the internet. Another option is to use a telecommunication network, like 4G or 5G communication networks.
It is noted that the card reader may be connected to a computer device of the merchant, and the computer device may then be connected to the internet. In the end, the messages exchanged between the card reader and the server may thus also be exchanged between the computer device of the merchant and the server.
In an offline environment a merchant may indicate on the card reader and/or the merchant device his intention to identify said customer using the payment card of the customer. Alternatively, the identification of the customer using the payment card of the customer may be an integrated routine.
The method according to the present disclosure relies at least partly on the insight that known loyalty programs may require a customer participating in the loyalty program to present a loyalty card at each purchase. The applicant has noted that customers relatively often fail to bring along their loyalty card when making a purchase. By using a payment card of the customer, there is no longer a need for the customer to present a loyalty card when making a purchase. Instead, the customer may present the payment card the customer is using for making the purchase.
Moreover, the relative large amount of loyalty programs available to a customer may place a burden on the customer since the customer needs to carry a relative large amount of loyalty cards. It is further noted that a loyalty card may be lost thereby introducing significant cost on behalf of the merchant for maintaining the customer participating in the loyalty program. By using a payment card of said customer, there is no longer a need for the customer to present a relative large amount of loyalty cards. Instead, the customer may present a single payment card for participation in loyalty programs of different merchants.
In addition, the presence of a relative large amount of loyalty cards may pose a burden to the environment. Known loyalty cards may be made of plastic that pose a risk to the environment if lost or disposed of. By using a payment card of said customer, there is no longer a need for production of a relative large amount of plastic loyalty cards that may pose a risk to the environment.
The present method avoids the need for involving the issuer of the payment card for use of the payment card for instance in a loyalty program as a means for identification of customer data, such as preferences of the customer, related to the merchant. The enrolment of the customer relies on the data that is stored on the payment card and that may be collected by the payment device. As such, no request for identification of the customer involving the issuer of the payment card is needed. Within the context of the present disclosure a card reader is to be understood as a device that requires no certification by designated authorities such as a financial institution, insurance company or government. A card reader is a device that may not be certified as regards compliance with an EMV standard for using EMV cards.
Within the context of the present disclosure the payment means may comprise the Primary account number, PAN, corresponding to the consumer.
In an embodiment of the method according to the present disclosure, the method may comprise the steps of: - retrieving, by said server, from said merchant register, merchant display data associated with said customer identification; - retrieving, by said server, from said loyalty card server customer display data associated with said loyalty card, by providing said loyalty card server with said customer identification and said one or more loyalty program identifications; and wherein, during said step of transmitting, said merchant display data and said customer display data are transmitted.
Preferably, said method further comprises the step of: - outputting, by said merchant device, said loyalty card, said merchant display data and said customer display date for display by said merchant device. Outputting the loyalty card, the merchant display data and the customer display data is beneficial for instance for avoiding the merchant to enquire for customer data, such as preferences, each time the customer indicates he/she wants to buy something,
thereby reducing the amount of work for the merchant for presenting a personalised offer to the customer. It is beneficial if said method further comprises the steps of: 5 - receiving, by said server, from said merchant device or said card reader, a change request message for changing said customer display data associated with said customer identification, wherein said change request message comprises customer display data and said customer identification; - accessing, by said server, using said access information in said loyalty program register, each loyalty card server in said loyalty program register corresponding to said determined one or more loyalty program identifications associated with said received customer identification and said merchant identification; and - transmitting, by said server, said received customer display data comprised by said change request message to said loyalty cards servers. This is advantageous for allowing the merchant to collect the customer data, such as preferences of the customer, after presenting the payment card to the card reader.
This is beneficial for reducing the amount of effort from the merchant and/or the customer for participating in the loyalty program and/or providing a personalised offer to the customer.
Preferably, said merchant display data comprises: - a date stamp associated with a previous date of retrieving, by said server, from said merchant register, said merchant display data associated with said customer identification; wherein said method comprises the steps of: - determining, by said server, a time period since said previous date of retrieving based on said date stamp; - transmitting, by said server, to said merchant device, an update request message for updating said customer display data when said time period exceeds a predetermined period of time; - receiving, by said server, updated customer display data associated with said customer identification;
- accessing, by said server, using said access information in said loyalty program register, each loyalty card server in said loyalty program register corresponding to said determined one or more loyalty program identifications associated with said received customer identification and said merchant identification; and - transmitting, by said server, said received updated customer display data comprised by said loyalty cards servers. This is beneficial for maintaining the customer display data up to date.
Preferably, the predetermined period of time is in the range of 3 to 12 months, preferably 6 months. Such a time period is very beneficial for maintaining the customer related data up to date while avoiding a relative large effort for maintaining the customer related data up to date.
It is beneficial if said financial institution related data comprises at least one of a financial institution account number and a credit card number. This is beneficial since a financial institution account number and a credit card number are unique numbers that may be related to a single customer.
It is advantageous, if said card reader is comprised by at least one of an unsafe payment device, a payment desk and a shop display device.
The card reader may be a device that is connected via USB or a wireless connection to the merchant device such as a payment desk, wherein the card reader is connected to the server via the payment desk and the payment desk transmits and receives messages from the server.
Alternatively, the card reader itself may be connected to the internet for instance via wireless connection or via a UTP cable. To this end the card reader maybe equipped with a WiFi transceiver, a Bluetooth receiver or transceiver, a Zigbee receiver or transceiver, or anything alike.
In an embodiment of the method according to the present disclosure, said merchant display data and/or said customer display data comprise at least one of a preferred colour, a preferred scent, a preferred shoe size and a preferred size of clothes. It is advantageous if said merchant display data and/or said customer display data are encrypted, and wherein said method further comprises the step of: - decrypting, by said card reader, said merchant display data and/or said customer display data. This is beneficial for avoiding the risk, or at least significantly reducing the risk, that privacy sensitive information that may be contained by said merchant display data and/or said customer display data is acquired by an unauthorised third party. Preferably, asymmetric encryption is used for encrypting and decrypting said identification request message. Preferably, said method further comprises the step of: - establishing between said card reader and said server, over a public network, a secure connection for carrying traffic; and wherein said identification request message is transmitted, by said card reader, via said secure connection and/or said merchant display data and/or said customer display data are received, by said card reader, via said secure connection. Establishing said secure connection between said server and said card reader, is beneficial for avoiding the risk, or at least significantly reducing the risk, that privacy sensitive information is acquired by an unauthorised third party.
In an embodiment of the method according to the first aspect of the present disclosure wherein encryption of the merchant display data and/or the customer display data and a secure connection are combined the security of the transfer is increased while man-in-the-middle attacks are avoided.
According to the second aspect, the present disclosure relates to a server arranged for supporting a method of supporting identification, by said server, of customer data related to a merchant, using payment means, such as a payment card, of said customer, wherein said server comprises:
- a user register comprising customer identifications for identifying customers, wherein each of said customer identifications is associated with a customer data and a hash value of a financial institution related data, such as bank related data; - a merchant register comprising merchant identifications for identifying merchants, wherein each of said merchant identifications is associated with one or more loyalty program identifications, wherein said merchant register further comprises merchant display data associated with said customer identifications; - a loyalty program register comprising access information for accessing loyalty cards servers associated with corresponding loyalty program identifications, wherein said loyalty cards servers comprise customer display data associated with loyalty cards; - receive equipment arranged for receiving from a card reader, an identification request message for identifying said customer, wherein said identification request message comprises financial institution related data stored onto said payment means that identify a financial institution account number of said customer and comprising a merchant identification for identifying said merchant; - processing equipment arranged for: - creating, using a one-way hash function, a hash value, by hashing said financial institution related data and, preferably a salt value; - determining, an associated customer identification in said user register based on said hash value; - determining, one or more loyalty program identifications associated with said received merchant identification in said merchant register; - access equipment, arranged for accessing a loyalty card server using access information in said loyalty program register corresponding to said determined one or more loyalty program identifications; - retrieve equipment arranged for retrieving, from said loyalty card server, a loyalty card and customer display data associated with said loyalty card, by providing said loyalty card server with said customer identification and said one or more loyalty program identifications; and - transmit equipment arranged for transmitting, to a merchant device, said retrieved loyalty card.
Embodiments of the server according to the second aspect are also applicable to the method according to the first aspect of the present disclosure, and vice versa.
Effects of the server according to the second aspect correspond to or are similar to effects of the method according to the first aspect of the present disclosure presented above. Effects of the method according to the first aspect as presented above correspond to or are similar to effects of the server according to the second aspect of the present disclosure.
The present disclosure will how be explained by means of a description of preferred embodiments of a method according to the present disclosure and a server according to the present disclosure, in which reference is made to the following schematic figures, in which: Fig. 1: a method of supporting identification, by a server, of customer data related to a merchant, using a payment means of said customer according to the present disclosure is shown; Fig. 2: a further method of supporting identification, by a server, of customer data related to a merchant, using a payment means of said customer according to the present disclosure is shown; Fig. 3: another method of supporting identification, by a server, of customer data related to a merchant, using a payment means of said customer according to the present disclosure is shown; Fig. 4: a server in accordance with the present disclosure is shown. Detailed description Figure 1 shows a flow chart of a method 1 in accordance with the present disclosure. The method 1 comprises several steps as indicated with reference numerals 3, 5, 7, 9, 11, 13 and 15. These steps are elaborated in more detail here below.
The steps 3, 5,7, 9, 11, 13 and 15 are all performed by a particular server 17 that may be connected to a public network. The server 17 may be connected to the internet, to a telecommunication network or anything alike. In essence, the server 17 may comprises three registers 19, 21 and 23. These registers 19, 21 and 23 may be contained in a single database, or may be distributed among multiple databases.
The first register is the user register 19. The user register 19 comprises customer identifications for identifying customers, wherein each of the customer identifications is associated with a customer data and a hash value of a financial institution related data. The financial institution related data itself is not stored on the server for privacy reasons. The customer identification may be a unique word, number or anything alike. The customer data may be considered as meta data associated to a particular customer, like the home address, the telephone number or anything alike. The first register is used to obtain a customer identification based on a determined hash value of the financial institution related data. This is explained in more detail later below.
The second register is the merchant register 21. The merchant register 21 comprises merchant identifications for identifying merchants, wherein each of the merchant identifications is associated with one or more loyalty program identifications. As such, each merchant may be subscribed to a particular loyalty program. Such a subscription may be maintained in the merchant register. In addition, the merchant register further comprises merchant display data associated with the customer identifications.
The third register is the loyalty program register 23 comprising access information for accessing loyalty cards servers associated with corresponding loyalty program identifications, wherein said loyalty cards servers comprise customer display data associated with loyalty cards. That is, the servers belonging to the loyalty cards may be third party server, i.e. not under control of the same operator as the claimed server itself. The loyalty program register may thus comprise Application Programming Interface, API, related information for access the corresponding loyalty card servers.
As indicated with reference numeral 3, the server 17 may receive, from a card reader (not shown), an identification request message for identifying the customer, wherein the identification request message comprises financial institution related data stored onto said payment means that identify a financial institution account number of the customer and wherein the message comprises a merchant identification for identifying the merchant. A one-way hash function is then used for creating, as indicated with reference numeral 5, a hash value by hashing the financial institution related data and a salt value. Typically, a one-way hash function, also known as a message digest, is a mathematical function that takes a variable-length input string and converts it into a fixed-length binary sequence that is computationally difficult to invert—that is, generate the original string from the hash.
Next, a customer identification is determined, as indicated with reference numeral 7, in the user register 19 based on the created hash value. The hash value is thus used as an input for obtaining the customer identification.
The server 17 determines, as indicated with reference numeral 9, one or more loyalty program identifications associated with the received merchant identification in the merchant register. The server 17 may thus uses the merchant identification as an input for obtaining the loyalty program identifications that are associated with the merchant.
The server 17 accesses, during a step of accessing 11, a loyalty card server using access information in said loyalty program register 23 corresponding to said determined one or more loyalty program identifications; The server 17 retrieves, as indicated by reference numeral 13, from the loyalty card server a loyalty card, by providing the loyalty card server with the customer identification and the one or more loyalty program identifications.
Finally, the loyalty card that is received from the loyalty card server, as indicated with reference numeral 15, is transmitted to a merchant device.
Method 101, shown in Figure 2, differs mainly from method 1 in that method 101 comprises further steps. Elements of method 101 that are similar to elements of method 1 are provided with a reference number equal to the reference number of the element in method 1 raised by 100.
As indicated by reference numeral 117, the server 17 may retrieve from the merchant register 21, merchant display data associated with the customer identification and subsequently retrieve 119 from the loyalty card server customer display data associated with the loyalty card, by providing the loyalty card server with the customer identification and the one or more loyalty program identifications. In addition, during step 115 of method 101, the merchant display data and/or the customer display data are transmitted.
The merchant device may output 121 the loyalty card, the merchant display data and/or the customer display date for display. In an embodiment of method 1, method 1 also may comprise a step of outputting the loyalty card, the merchant display data and the customer display date for display by the merchant device.
Method 101 further may comprise a step 123, during which the server 17 receives, from the merchant device or the card reader, a change request message for changing the customer display data associated with the customer identification, wherein the change request message comprises customer display data and the customer identification.
In a next step 125 of method 101, the server 17 may access, using the access information in the loyalty program register 23, each loyalty card server in the loyalty program register 23 corresponding to the determined one or more loyalty program identifications associated with the received customer identification and the merchant identification.
Finally, the server 17 may transmit 127 the received customer display data comprised by the change request message to the loyalty cards servers.
Method 201, shown in Figure 3, differs mainly from method 1 in that the merchant display data of method 201 comprises a date stamp associated with a previous date of retrieving, by said server, from said merchant register, said merchant display data associated with said customer identification and in that the method 201 comprises further steps. Elements of method 201 that are similar to elements of method 1 are provided with a reference number equal to the reference number of the element in method 1 raised by 200. As indicated by reference numeral 229, the server 17 may be arranged for determining 229 a time period since said previous date of retrieving based on said date stamp. Next, an update request message may be transmitted 231, by said server 17, to said merchant device, for updating the customer display data when said time period exceeds a predetermined period of time. The server 17 may receive, during a step of receiving 233, updated customer display data associated with the customer identification and accessing 235, using the access information in the loyalty program register 23, each loyalty card server in the loyalty program register corresponding to the determined one or more loyalty program identifications associated with the received customer identification and the merchant identification. Finally, the received updated customer display data comprised by said loyalty cards servers is transmitted, by said server 17, during a step of transmitting
237. Figure 4 discloses the server 17 in accordance with the present disclosure. The server 17 is arranged for supporting the method 1 of supporting identification, by said server 17, of customer data related to a merchant, using payment means, such as a payment card, of said customer, wherein said server comprises: - a user register 19 comprising customer identifications for identifying customers, wherein each of said customer identifications is associated with a customer data and a hash value of a financial institution related data, such as bank related data; - a merchant register 21 comprising merchant identifications for identifying merchants, wherein each of said merchant identifications is associated with one or more loyalty program identifications, wherein said merchant register further comprises merchant display data associated with said customer identifications; - a loyalty program register 23 comprising access information for accessing loyalty cards servers associated with corresponding loyalty program identifications, wherein said loyalty cards servers comprise customer display data associated with loyalty cards; - receive equipment 25 arranged for receiving from a card reader, an identification request message for identifying said customer, wherein said identification request message comprises financial institution related data stored onto said payment means that identify a financial institution account number of said customer and comprising a merchant identification for identifying said merchant; - processing equipment 27 arranged for: - creating, using a one-way hash function, a hash value, by hashing said financial institution related data and said salt value; - determining, an associated customer identification in said user register based on said hash value; - determining, one or more loyalty program identifications associated with said received merchant identification in said merchant register; - access equipment 29, arranged for accessing a loyalty card server using access information in said loyalty program register corresponding to said determined one or more loyalty program identifications; - retrieve equipment 31 arranged for retrieving, from said loyalty card server, a loyalty card and customer display data associated with said loyalty card, by providing said loyalty card server with said customer identification and said one or more loyalty program identifications; and - transmit equipment 33 arranged for transmitting, to a merchant device, said retrieved loyalty card.
The present disclosure is not limited to the examples as disclosed above, and can be modified and enhanced by those skilled in the art beyond the scope of the present disclosure as disclosed in the appended claims without having to apply inventive skills and for use in any data communication, data exchange and data processing environment, system or network.
Claims (11)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
NL2026430A NL2026430B1 (en) | 2020-09-08 | 2020-09-08 | A method of supporting identification of customer data related to a merchant and a server arranged for supporting a method of supporting identification of customer data related to a merchant, using a payment means of the customer. |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
NL2026430A NL2026430B1 (en) | 2020-09-08 | 2020-09-08 | A method of supporting identification of customer data related to a merchant and a server arranged for supporting a method of supporting identification of customer data related to a merchant, using a payment means of the customer. |
Publications (1)
Publication Number | Publication Date |
---|---|
NL2026430B1 true NL2026430B1 (en) | 2022-05-09 |
Family
ID=72886153
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
NL2026430A NL2026430B1 (en) | 2020-09-08 | 2020-09-08 | A method of supporting identification of customer data related to a merchant and a server arranged for supporting a method of supporting identification of customer data related to a merchant, using a payment means of the customer. |
Country Status (1)
Country | Link |
---|---|
NL (1) | NL2026430B1 (en) |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014086762A1 (en) * | 2012-12-03 | 2014-06-12 | Vitisco Nv | A method and system for providing universal access to a service amongst a plurality of services |
WO2019102233A1 (en) * | 2017-11-27 | 2019-05-31 | Loyalty Angels Ltd | Method and system for identifying users in two domains |
-
2020
- 2020-09-08 NL NL2026430A patent/NL2026430B1/en not_active IP Right Cessation
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014086762A1 (en) * | 2012-12-03 | 2014-06-12 | Vitisco Nv | A method and system for providing universal access to a service amongst a plurality of services |
WO2019102233A1 (en) * | 2017-11-27 | 2019-05-31 | Loyalty Angels Ltd | Method and system for identifying users in two domains |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10044507B2 (en) | Zero-knowledge environment based social networking engine | |
EP3844934B1 (en) | A computer system and method of operating same for handling anonymous data | |
US6615353B1 (en) | User authentication method and user authentication system | |
US8364713B2 (en) | Personal data manager systems and methods | |
US20200084051A1 (en) | Systems and methods for preserving privacy and incentivizing third-party data sharing | |
JP5626537B2 (en) | Request offline profile data for online use in confidentiality | |
US20190066079A1 (en) | Methods and systems using a computing platform for routing virtual receipts to customers with a scan-able code generated by the merchant | |
US20100274859A1 (en) | Method And System For The Creation, Management And Authentication Of Links Between Entities | |
CN110365670A (en) | Blacklist sharing method, device, computer equipment and storage medium | |
CN108509806B (en) | Big data accurate marketing system and equipment with privacy protection | |
JP2005512208A (en) | Method and apparatus for distributing computer content | |
US20020051541A1 (en) | System and method for maintaining state between a client and server | |
KR20060055314A (en) | Stateless methods for resource hiding and access control support based on uri encryption | |
CN103348373A (en) | Personal-information transmission/reception system, personal-information transmission/reception method, personal-information provision device, preference management device, and computer program | |
US20190066064A1 (en) | Methods and systems using a computing platform for routing virtual receipts by the merchant with a scan-able code generated by the customer | |
US20220067125A1 (en) | Method for distributing certificate of right to use digital content, and computer program stored in medium in order to carry out method | |
US20230274259A1 (en) | Method and system for controlling display of a representation of a physical user token in a digital wallet | |
US11003789B1 (en) | Data isolation and security system and method | |
CN102349086A (en) | Personal data manager systems and methods | |
NL2026430B1 (en) | A method of supporting identification of customer data related to a merchant and a server arranged for supporting a method of supporting identification of customer data related to a merchant, using a payment means of the customer. | |
CN110266686B (en) | Data sharing method, device, equipment and computer readable storage medium | |
CN110278245B (en) | Block chain based APP message sharing method, system, device and storage medium | |
JP2019046262A (en) | Information processing apparatus, information processing method, and information processing program | |
CN110266698A (en) | Pass through the Knowledge Sharing data cochain method and its equipment of block chain | |
NL2026199B1 (en) | A method of registering, by a server, a customer for a loyalty program, using a payment means, such as a payment card, of said customer, as well as a related server. |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
MM | Lapsed because of non-payment of the annual fee |
Effective date: 20231001 |