WO2009001355A2 - Dispositif, système et procédé d'achat protégé - Google Patents

Dispositif, système et procédé d'achat protégé Download PDF

Info

Publication number
WO2009001355A2
WO2009001355A2 PCT/IL2008/000869 IL2008000869W WO2009001355A2 WO 2009001355 A2 WO2009001355 A2 WO 2009001355A2 IL 2008000869 W IL2008000869 W IL 2008000869W WO 2009001355 A2 WO2009001355 A2 WO 2009001355A2
Authority
WO
WIPO (PCT)
Prior art keywords
user
purchase
item
profile
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/IL2008/000869
Other languages
English (en)
Other versions
WO2009001355A3 (fr
Inventor
Yosef Salomon
Eran Tamir
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Publication of WO2009001355A2 publication Critical patent/WO2009001355A2/fr
Anticipated expiration legal-status Critical
Publication of WO2009001355A3 publication Critical patent/WO2009001355A3/fr
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/06—Buying, selling or leasing transactions

Definitions

  • Some embodiments are related to the field of performing commercial transactions, for example, using online and offline commerce systems.
  • Some electronic communication systems allow users to engage in electronic commerce (“e-commerce").
  • e-commerce electronic commerce
  • a user may utilize a Personal Computer (PC) connected to the Internet in order to purchase various products from a web-site of a merchant.
  • the user may pay for the purchased products by entering his credit card details; and the purchased products are shipped by the merchant to a shipping address provided by the user.
  • PC Personal Computer
  • a user who is a parent may allow his child to utilize the parent's credit card in order to purchase online various products, for example, movies, books, or video games.
  • the unsupervised child may purchase online products that are inappropriate for children, or products that the parent does not approve of, for example, movies or video games that include violent content or sexual content.
  • Some embodiments include, for example, devices, systems, and methods of protected purchasing.
  • Some embodiments include, for example, a method for protected purchasing of items via a communication network having a server; and the method includes: receiving at the server a request from a user to purchase an item; based on a profile of the user, determining whether or not the item is approved for purchase by the user; and if the item is approved for purchase by the user, allowing processing of a transaction to purchase the item by the user.
  • the method includes: if the item is unapproved for purchase by the user, disallowing processing of the transaction to purchase the item by the user, and removing a visual representation of the item from a group of one or more visual representations of items available for purchase by the user.
  • disallowing includes: blocking submission of transaction data to a payment authorization system.
  • the profile of the user includes one or more lists selected from the group consisting of: a list of items that are pre-approved for purchase by the user; a list of items that are restricted for purchase by the user; a list of categories of items that are pre-approved for purchase by the user; and a list of categories of items that are restricted for purchase by the user.
  • the profile of the user is based on an input received from a supervising user, wherein the supervising user is authorized to modify the user profile, and wherein the user is unauthorized to modify the user profile.
  • the method includes: classifying the item as allowed for purchase or disallowed for purchase, based on a category to which the item belongs.
  • the method includes: classifying the item as allowed for purchase or disallowed for purchase, based on a content of the item.
  • the method includes: checking whether or not the user is authenticated, based on a query to a database able to store session identifiers or authenticated users; and if the user is unauthenticated, disallowing processing of the transaction to purchase the item by the user.
  • receiving the request includes receiving the request through an
  • receiving the request includes receiving the request through a point-of-sale terminal.
  • Some embodiments include, for example, a system for protected purchasing of items via a communication network; and the system includes: a classification server to receive a request from a user to purchase an item; to determine, based on a profile of the user, whether or not the item is approved for purchase by the user; and if the item is approved for purchase by the user, to allow processing of a transaction to purchase the item by the user.
  • the classification server is to generate output indicating to disallow processing of the transaction to purchase the item by the user and to remove a visual representation of the item from a group of one or more visual representations of items available for purchase by the user.
  • the classification server is to generate output indicating to block submission of transaction data to a payment authorization system.
  • the profile of the user includes one or more lists selected from the group consisting of: a list of items that are pre-approved for purchase by the user; a list of items that are restricted for purchase by the user; a list of categories of items that are pre-approved for purchase by the user; and a list of categories of items that are restricted for purchase by the user.
  • the profile of the user is based on an input received from a supervising user, wherein the supervising user is authorized to modify the user profile, and wherein the user is unauthorized to modify the user profile.
  • the classification server is to classify the item as allowed for purchase or disallowed for purchase, based on a category to which the item belongs.
  • the classification server is to classify the item as allowed for purchase or disallowed for purchase, based on a content of the item.
  • the system includes: an authentication server to check whether or not the user is authenticated, based on a query to a database able to store session identifiers or
  • the classification server is to receive the request through an Internet web-site. [0025] In some embodiments, the classification server is to receive the request through a point- of-sale terminal.
  • Some embodiments may include, for example, a computer program product including a computer-useable medium including a computer-readable program, wherein the computer- readable program when executed on a computer causes the computer to perform methods in accordance with some embodiments of the invention.
  • Some embodiments may provide other and/or additional benefits and/or advantages. BRIEF DESCRIPTION OF THE DRAWINGS
  • Figures 1-6 are schematic block diagram illustrations of systems for protected purchasing, in accordance with some demonstrative embodiments of the invention.
  • wired links and/or wired communications some embodiments are not limited in this regard, and may include one or more wired or wireless links, may utilize one or more components of wireless communication, may utilize one or more methods or protocols of wireless communication, or the like. Some embodiments may utilize wired communication and/or wireless communication.
  • Some embodiments may be used in conjunction with various devices and systems, for example, a Personal Computer (PC), a desktop computer, a mobile computer, a laptop computer, a notebook computer, a tablet computer, a server computer, a handheld computer, a handheld device, a Personal Digital Assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., a device incorporating functionalities of multiple types of devices, for example, PDA functionality and cellular phone functionality), a vehicular device, a non-vehicular device, a mobile or portable device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless Access Point (AP), a wireless Base Station (BS), a Mobile Subscriber Station (MSS), a wired or wireless Network Interface Card (NIC), a wired or wireless router, a wired or wireless modem, a wired or wireless network, a Local Area Network (LAN), a Wireless LAN,
  • Some embodiments may be used in conjunction with one or more types of wireless communication signals and/or systems, for example, Radio Frequency (RF), Infra Red (IR), Frequency-Division Multiplexing (FDM), Orthogonal FDM (OFDM), OFDM Access (OFDMA), Time-Division Multiplexing (TDM) 3 Time-Division Multiple Access (TDMA), Extended TDMA (E-TDMA), General Packet Radio Service (GPRS), extended GPRS, Code- Division Multiple Access (CDMA), Wideband CDMA (WCDMA), CDMA 2000, Multi-Carrier Modulation (MDM), Discrete Multi-Tone (DMT), Bluetooth (RTM), Global Positioning System (GPS), IEEE 802.11 (“Wi-Fi”), IEEE 802.16 (“Wi-Max”), ZigBee (TM), Ultra- Wideband (UWB), Global System for Mobile communication (GSM), 2G, 2.5 G, 3 G, Third Generation Partnership Project (3GPP), 3GPP Long Term Evolution (LTE
  • wireless device or “wireless computing device” as used herein include, for example, a device capable of wireless communication, a communication device or communication station capable of wireless communication, a desktop computer capable of wireless communication, a mobile phone, a cellular phone, a laptop or notebook computer capable of wireless communication, a PDA capable of wireless communication, a handheld device capable of wireless communication, a portable or non-portable device capable of wireless communication, or the like.
  • web or "Web” as used herein includes, for example, the World Wide Web; a global communication system of interlinked and/or hypertext documents, files, web-sites and/or web-pages accessible through the Internet or through a global communication network; including text, images, videos, multimedia components, hyperlinks, or other content.
  • system includes, for example, the a protected online transaction system in accordance with some embodiments
  • the term "merchant” as used herein includes, for example, an electronic commerce ("e- commerce”) web site, e.g., “eBay.com”, “Amazon.com”, or the like; and/or an offline commerce establishment or real-world non-virtual site (e.g., an offline store or shop).
  • e- commerce electronic commerce
  • eBay.com electronic commerce
  • Amazon.com electronic commerce establishment
  • real-world non-virtual site e.g., an offline store or shop.
  • web site or "site” as used herein include, for example, a web site of a i merchant.
  • restricted merchant includes, for example, an e-commerce web site that sell products that are by category restricted to the system. For example, if the system provides a protective layer for teenager users, then merchants of sexual materials or firearms are restricted merchants.
  • the term "user” as used herein includes, for example, the actual user who utilizes the payment method in order to perform an online purchase.
  • the user is a teenager.
  • activator includes, for example, the initiator of the payment method who creates the user profile and deposits money into it.
  • the activator is a parent of the teenager, a supervising user, or the like.
  • client or “client application” as used herein includes, for example, an application that is installed on the computing device of the user.
  • portal includes, for example, a portal or interface to the system which performs services such as, for example, creating a new profile for an activator, modifying details of an existing profile of an activator, viewing statistics or information on usage of an account of an activator, or the like.
  • server or “server computer” as used herein include, for example, one or more server computer that store the system logic and algorithms and/or process the different requests.
  • multiple servers may be used, for example: an authentication server for user authentication; a users server to manage the user details (e.g., user profile, statistics regarding the user account, or the like); and a classification server to store algorithms for identifying and classifying products, as well as classified products data.
  • issuer includes, for example, an issuer or operator of a payment method; for example, a bank of financial institution that issues credit cards or debit cards; an online payment institution (e.g., PayPal); an issuer of a virtual or real-life prepaid card or secured card; or the like.
  • authorization system includes, for example, a system owned, controlled, or operated by an issuer, the system able to approves or deny a payment transaction placed by a user.
  • MCC Manufacturing Category Code
  • a code or a number e.g., a four-digit number
  • profile or "user profile” as used herein include, for example, a profile of a user.
  • the user profile is defined by the activator, and not by the user.
  • online and “offline” as used herein may refer, for example, to the location of the merchant and/or to the location in which payment takes place.
  • an “online” merchant includes an e-commerce web site; and an “online” payment method includes a payment method performed through a communication network (e.g., the Internet).
  • An “offline” merchant includes, for example, a "brick and mortar” store, a real-life store or a physical store; and an
  • offline payment method includes a payment method performed in the real-life store (e.g., physically handing over a credit card, or physically swiping a payment card).
  • card or "payment card” as used herein includes, for example, a credit card, a debit card, a secured credit card, a secured debit card, a prepaid credit card, a prepaid debit card, a one-time payment card, a payment card that can be refilled or reloaded, a payment card associated with a bank account, a payment card unassociated with a bank account, or the like.
  • the term "payment method” as used herein includes, for example, a method of payment utilizing a payment card, a method of payment utilizing an online payment service (e.g., PayPal), a method of payment utilizing a direct debit from a bank account of the purchaser to a bank account of the merchant, or other suitable payment methods.
  • an online payment service e.g., PayPal
  • a method of payment utilizing a direct debit from a bank account of the purchaser to a bank account of the merchant or other suitable payment methods.
  • a system provides a protective layer on top of existing payment methods.
  • the system is able to identify, before the actual purchase is executed, whether the product intended to be purchased is allowed or prohibited. This identification is done according to a pre-defined user profile, and the result is an approved transaction or a blocked transaction.
  • the system utilizes a pre-authorization content filter, which identifies the product being purchased and matches the product to the user profile before the payment transaction takes place.
  • the system may be used to allow protect or restricted online purchasing by teenage users; for example, an activator (a parent) may utilize the system to ensure that the user (a child or teenager) is not able to purchase products that include sexual content, violent content, or other content that the parent deems inappropriate.
  • an activator a parent
  • the system allow teenager users and pre-teenager users to use their pocket money in order to purchase on the Internet products that are pre-defined as "safe" for them.
  • the system ensures that the user is not able to purchase any product that does not comply with the user's pre-defined profile. For example, a teenager's prepaid card is used by the system, and the system blocks any attempt to purchase alcohol, gambling services, gambling products, and products that contain sexual content or violent content.
  • the system may be used with other implantations in order to restrict or limit the products that can be purchased online.
  • a family card allows families to better set the spending limits and control the family's budget; a student card is funded by the student's parents and can be used only for pre-approved purposes (e.g., payment of electricity bills, payment of dorms monthly rent, payment for food); an ecological card or environment- friendly card, which allows the system to block the purchase of non-environment-friendly products or services; and other suitable types of cards or blocking parameters.
  • the system may include multiple components or modules, for example: user authentication module or component; integration with merchants module or component; integration with issuers module or component; client module or component; server module or component; portal module or component for activating, modifying, and controlling the user account; and a users portal module or component.
  • user authentication module or component integration with merchants module or component; integration with issuers module or component; client module or component; server module or component; portal module or component for activating, modifying, and controlling the user account; and a users portal module or component.
  • the system may include or may utilize multiple flows or algorithms, for example: account creation flow; product classification flow; regular transaction flow; session protected transaction flow; enhanced collaboration with merchants flow; and offline transaction flow.
  • a user authentication component or module is used.
  • the user needs to authenticate with the system's authentication server.
  • a unique digital signature is saved in the authentication server.
  • the signature is attached to the shopping cart and is validated by the issuer approval server before approving the transaction.
  • the digital signature has an expiration time, so the user may need to re-authenticate after a certain amount of time.
  • the authentication may be done in one or more methods, for example: a username and password method, in which the user has to insert a fixed password (e.g., a sequence of characters, letters, digits, signs, or the like); a method in which the user has to answer a question selected randomly out of a list of pre-defined security questions; a two- factor authentication, in which the user, in addition to entering a password, needs to insert a token to the computer or computing device, such that even if his password was compromised, a
  • third party may not access his account unless the third party has the physical token as well.
  • each account supported by the system is associated with an activator and one or more users. Each one of them has a different authentication data, and upon authentication has different permissions in the system portal.
  • an integration with merchants component or module is used, utilizing one or more levels of integration, for example, basic integration or enhanced integration.
  • the basic level of integration allows the user to use the system as a payment method. It requires the merchant to support the payment method that the system is attached to. For example, the system provides a protective layer on top of credit card, branded by Visa; and all the merchant has to do is to support the Visa payment method in his web site in order to be integrated with the system.
  • the enhanced level of integration may be implemented on top of the basic level of integration.
  • the enhanced level of integration allows the merchant to tailor his web site to the specific user. A tailored web site helps to maximize the exposure of relevant products to the specific user. In addition, it may save the user the disappointment while trying to purchase items that do not comply with his profile.
  • the merchant may obtain statistical information from the system.
  • the enhanced level of integration may include, for example, receiving recommendations from the system regarding allowed products. For example the user tries to purchase a restricted product; instead of only blocking the purchase of the restricted product, the merchant's web site may ask the system to search for an allowed or pre-approved product which is similar to the required product (if such replacement product exists).
  • a merchant web site may be required to comply with a protocol (e.g., as described herein with reference to Figure 5). For example, a merchant ID and authentication identifier are used; this information is issued by the system in a manual procedure which identifies the merchant.
  • this protocol allows a merchant to identify a user in the merchant internal database by using the system authentication server.
  • the merchant web site may query on a specific user profile from the system user's server.
  • the protocol to query about the user's profile allows a web site to query the user's profile, for example, whether or not the user is allowed to purchase a category of products, or a specific product.
  • the actual purchase using the system and the classification of products may be performed using the client, and may not require specific integration from the merchant, e.g., except for supporting the relevant payment method(s).
  • the flow of the actual purchase may be in accordance with "regular transaction” and "session protected transaction", e.g., as discussed herein with reference to Figures 3 and 4, respectively.
  • an integration with issuers component or module may be used, for example, for system integration with credit card issuers and other card issuers.
  • the integration with the issuer may be performed in two phases, for example, creation of an account, and actual payment transaction.
  • the activator may set payment details: the amount of money that he wants to charge into the new account; and how he selects to do that (for example, to charge
  • the Activator may set the account profile both in terms of spending limitation and content limitation.
  • the issuer portal transfers that data, after the account creation, to the system's server.
  • the system server sends a password in exchange for that data, so that the Activator may start using the account. For example, in the implementation of a teenager's prepaid card, the activator (parent)
  • the spending limitation e.g., monthly, weekly, and/or daily
  • the content limitation e.g., no sexual content, no video games, or the like.
  • the issuer authorization system approves the transaction; alternatively, the issuer authorization system blocks the transaction.
  • the integration utilizing session protected transaction if the user did not authenticate against the system, he is not able to execute the actual purchase; thereby decreasing the fraud on the system.
  • the integration utilizing session protected transaction if the user did not authenticate against the system, he is not able to execute the actual purchase; thereby decreasing the fraud on the system.
  • a client component or module may be used.
  • the client includes a software application running on the user's computing device.
  • the client has two main functionalities: to initiate the authentication, and to identify merchant web sites and products.
  • the user may activate the client and the user is prompted to authenticate.
  • the client takes the authentication information and pass it securely (e.g., using SSL) to the system authentication server. In case the authentication succeeded, it returns the user profile.
  • the client With respect to identifying merchant web sites and products, the client is hooked to the user's browser and checks the URL that the user is browsing into. If it is a merchant site, the client identifies this case and sends the information to the system classification server. The classification server determines whether or not this site is allowed or not. Then, in allowed sites, the client may operate to identify each product and send it to the system server for classification. In some embodiments, once the product is classified, the client adds a visual and/or other (e.g., audible) notification of the analysis result, in order to convey to the user the classification results.
  • a visual and/or other notification of the analysis result e.g., audible
  • a visual icon stating that the product is allowed for purchase by this user may be added in proximity to the product's name or description.
  • an icon may indicate the restriction, or the client may remove any visual reference to the product. If the product is restricted, then the client may block the option of adding the product to the shopping cart; or may actively remove the product from the shopping cart if, for example, the classification took place after the product was added to the shopping cart [0075]
  • the client may be implemented as an add-on or plug-in or extension to the user's web browser, for example, that needs to be downloaded and/or installed.
  • the system may utilize a client-less implementation; for example, users who do not wish to install an add-on application may navigate to a specific portal that replaces the client functionality, and from that portal they may navigate to merchant web sites.
  • a client-less implementation for example, users who do not wish to install an add-on application may navigate to a specific portal that replaces the client functionality, and from that portal they may navigate to merchant web sites.
  • some of the Figures may include an add-on client, although other suitable implementations may be used.
  • one or more system servers may be used, for example, an authentication server, a users server, and a classification server.
  • the authentication server performs user authentication; and manages the revocation lists in case the system identifies a user who tries to bypass the system or is suspended for various reasons. Each authentication has an expiration time.
  • the authentication server may ask the user to re-authenticate if the expiration time elapses.
  • the users server stores information about the users, for example, account details, user profile, list of products purchased by a user, and other data relevant for managing the user account.
  • the classification server may classify products in substantially real time.
  • the classification information may be stored in a products database, for example, in order to provide quicker answer starting from the second time that a particular product is queried.
  • the actual classification may be performed using one or more filters that screen the product in a workflow.
  • the filters may include, for example, web sites black lists, web sites white lists, text mining algorithms, advanced Natural Language Processing (NLP) algorithms, and image analysis algorithms.
  • NLP Natural Language Processing
  • black list of blocked web sites, and/or a white list of approved web sites may be used, optionally utilizing MCCs.
  • MCCs For example, in an implementation for a teenager card, any web site with MCC associated with pornography or gambling is automatically added to the black list. Additionally, the activator may manually add specific web sites to the user's black list or white list.
  • TF/IDF may check for number of occurrences of keywords and the value of each keyword in order to determine whether a product is allowed or restricted.
  • the advanced NLP algorithms may operate on the products that the system has no certain determination about, e.g., resulted from using other filters.
  • the image analysis algorithms may be used, for example, to classify a product having an insufficient textual description; the classification server performs image analysis scan on the product image in order to obtain additional information to be used for product classification.
  • Some embodiments may utilize a portal for activating and controlling the user account, e.g., as described herein with reference to Figure 1.
  • the activator sets the profile for the user who will use the account for purchases.
  • different categories and values may be set in the account profile.
  • the profile may include: user name; user gender; user age, or date of birth, or year of birth; user's address; home address or shipping address; method of authentication and an initial password; the initial amount of money available on the teenager card; the payment method to be used; the user profile; and other suitable parameters.
  • the user profile may include, for example: limitations or restrictions on product content, e.g., level of violence or sexuality; limitations or restrictions of product content by classification, e.g., the parent wishes to prevent his child from purchasing computer games; limitations or restrictions on spending, e.g., setting monthly, weekly, and/or daily quota(s); maximum amount of money allowed to be spent in a single transaction; number of transactions allowed to be performed per day, per week, or per month; or the like.
  • the activator may modify the user profile even when the account is active. Additionally, the activator may suspend or cancel the account.
  • the settings may be managed and modified from the system portal. Upon login to the portal, the system identifies whether the logged-in person is an activator or a regular user, and provides access to different functionalities accordingly.
  • Some embodiments may utilize a users portal, for example, a platform that allows users and/or activators to obtain statistical and behavioral information about the usage of their account.
  • a users portal for example, a platform that allows users and/or activators to obtain statistical and behavioral information about the usage of their account.
  • the user and/or the activator may be able to see information of the user's past purchases, as well as to analyze the personal history of purchases of the user.
  • the statistical analysis may indicate: the categories of products that the user purchased; the spending ratio in the last week or month; the average spending ratio per week or month; or the like.
  • the statistical information may be obtained using a web browser, a handheld device, a cellular phone, a computer, or the like.
  • the system may be used outside of the e-commerce world, or in the real world, non-virtual world, or "brick and mortar" commerce.
  • integration with issuers may be performed with regard to offline payments.
  • information about the purchased item(s) is sent to a server by a point-of-sale terminal (or other suitable money transfer device) in a real-world store, and the product information is verified by the profiling engine, e.g., as described herein with reference to Figure 6.
  • Figure 1 schematically illustrates a system 100 for protected purchasing, in accordance with some demonstrative embodiments of the invention.
  • arrows for demonstrative purposes, arrows
  • 101-107 demonstrate a flow of account creation within system 100.
  • an activator utilizes an activator device 121 to navigate to an issuer portal
  • the activator utilizes the activator device 121 to fill in the details required for creating the account (arrow 102).
  • the details may include, for example, payment information, budget limitations, and content limitations.
  • the payment information includes, for example, the activator credit card details, the amount of money to deposit into the new account, whether the deposit is one-time or recurring, and the period of time for automatic reloading of deposits into the account.
  • the budget limitations include, for example, limitations on daily spending, weekly spending, monthly spending, spending per product, spending per type of product (e.g., video games), or the like.
  • the content limitations include, for example, limitations on the types of products the user may or may not purchase; e.g., the user is not allowed to purchase products having violent content, products having sexual content, or video games.
  • the issuer portal 122 checks whether or not the activator is an existing customer. If the activator is not an existing customer, the issuer portal 122 further checks the activator for fraud
  • a third party fraud detector 123 e.g., "The 41st Parameter” fraud detection and prevention solution.
  • the issuer portal 122 creates an account in the issuer system, charges the activator, and transfers the money into the created account (arrow 104).
  • the created account is stored in an accounts database 124.
  • the issuer portal 122 sends the budget limitations information and the content limitations information to a users server 125 (arrow 105).
  • the users server 125 stores the user information in a users database 126 (arrow 106), and creates new passwords for the user and the activator.
  • the users server 125 sends back the passwords to the issuer portal 122 (arrow 107), so that the activator and the user may use the passwords.
  • the users server 125 and the users database 126 may be part of a sub-system 199 which may be owned, controlled, operated by a first entity; whereas other components of system 100 may be owned, controlled, and/or operated by one or more other entities.
  • FIG. 2 schematically illustrates a system 200 for protected purchasing, in accordance with some demonstrative embodiments of the invention.
  • arrows For demonstrative purposes, arrows
  • a user utilizes a user device 221 in order to open or launch a client application 222, through which the user enters user authentication data (arrow 201).
  • the client application 222 may be implemented as a web browser or web navigation software; the client application 222 may include, may be associated with, or may allow utilization of, for example,
  • an add-on 250 e.g., a browser plug-in or extension or add-on, or a web-based portal.
  • an add-on component 250 is shown, for demonstrative purposes, other suitable components or modules may be used, for example, a web-based portal which may not necessarily require downloading of software and/or installation of software.
  • the add-on 250 sends the authentication data to an authentication server 223 (arrow 202).
  • the authentication server 223 attempts to authenticate the user; if the user passes the authentication, a protected session is stored in a sessions database 224 (arrow 203). [00100] The authenticated user utilizes the user device 221 and the client application 222 in order to navigate to a merchant web site 225 (arrow 204). [00101] The add-on 250 identifies the merchant web site 225, and sends identifying details
  • the classification server 226 checks whether or not the merchant web site 225 is allowed according to the user profile; the classification server 226 sends the response (e.g., allowed web site or restricted web site) back to the add-on 250 (arrow 206). [00103] If the merchant web site 225 is an allowed web site, then the add-on 250 identifies each product that the user is browsing, and sends the product information to the classification server 226 for product classification (arrow 207).
  • the classification server 226 classifies the product and validates it against the user's profile, namely, determines whether or not the user is allowed to purchase this product according to the user's profile.
  • a response e.g., a binary approval or rejection response
  • classification server 226 cannot determine whether or not the specific product is allowed, then, as a default, the specific product is blocked; and an alert is sent by the classification server 226 to an alert log 227 accessible by a system administrator (arrow 209).
  • the authentication server 223, the sessions database 224, the classification server 226, and the alert log 227 may be part of a sub-system 299 which may be owned, controlled, operated by a first entity; whereas other components of system 200 may be owned, controlled, and/or operated by one or more other entities.
  • FIG. 3 schematically illustrates a system 300 for protected purchasing, in accordance with some demonstrative embodiments of the invention.
  • arrows 301-309 demonstrate a flow of performing a regular transaction using an account within system 300.
  • a user utilizes a user device 321 in order to open or launch a client application 322, through which the user enters user authentication data (arrow 301).
  • the client application 322 may be implemented as a web browser or web navigation software; the client application 322 may include, may be associated with, or may allow utilization of, for example, an add-on 350, e.g., a browser plug-in or extension or add-on, or a web-based portal.
  • an add-on component 350 is shown, for demonstrative purposes, other suitable components or modules may be used, for example, a web-based portal which may not necessarily require downloading of software and/or installation of software.
  • the add-on 350 sends the authentication data to an authentication server 323
  • the authentication server 323 attempts to authenticate the user; if the user passes the authentication, a protected session is stored in a sessions database 324 (arrow 303).
  • the authenticated user utilizes the user device 321 and the client application 322 in order to navigate to a merchant web site 325 (arrow 304).
  • the add-on 350 identifies the merchant web site 325, and sends identifying details of the merchant web site 325 to a classification server 326 for web site classification (arrow
  • the classification server 326 checks whether or not the merchant web site 325 is allowed according to the user profile; the classification server 326 sends the response (e.g., allowed web site or restricted web site) back to the add-on 350. If the merchant web site 325 is an allowed web site, then the add-on 350 identifies each product that the user is browsing, and sends the product information to the classification server 326 for product classification.
  • the classification server 326 classifies the product and validates it against the user's profile, namely, determines whether or not the user is allowed to purchase this product according to the user's profile.
  • a response (e.g., a binary approval or rejection response) is returned by the classification server 326 to the client application (arrow 306), indicating whether a purchase of this product is allowed or blocked.
  • the user may utilize the user device 321 to add the allowed product to the user's virtual shopping cart. If the product is not allowed, the add-on 350 blocks the user's ability to add the product to the user's virtual shopping cart. [00115]
  • the merchant web site 325 sends the user's shopping cart (which includes only allowed products) to an issuer authorization system 327 (arrow 307), where the transaction is validated and either approved or rejected.
  • the issuer authorization system 327 sends back to the merchant web site 325 a response indicating approval or rejection of the transaction (arrow 308).
  • the user device 321 receives a notification indicating whether the transaction was executed or failed (arrow 309).
  • the authentication server 323, the sessions database 324, and the classification server 326 may be part of a sub-system 399 which may be owned, controlled, operated by a first entity; whereas other components of system 300 may be owned, controlled, and/or operated by one or more other entities.
  • Figure 4 schematically illustrates a system 400 for protected purchasing, in accordance with some demonstrative embodiments of the invention.
  • arrows 401-411 demonstrate a flow of performing a session protected transaction using an account within system 400.
  • a user utilizes a user device 421 in order to open or launch a client application 422, through which the user enters user authentication data (arrow 401).
  • the client application 422 may be implemented as a web browser or web navigation software; the client application 422 may include, may be associated with, or may allow utilization of, for example, an add-on 450, e.g., a browser plug-in or extension or add-on, or a web-based portal.
  • an add-on component 450 is shown, for demonstrative purposes, other suitable components or modules may be used, for example, a web-based portal which may not necessarily require
  • the add-on 450 sends the authentication data to an authentication server 423
  • the authentication server 423 attempts to authenticate the user; if the user passes the authentication, a protected session is stored in a sessions database 424 (arrow 403).
  • the authenticated user utilizes the user device 421 and the client application 422 in order to navigate to a merchant web site 425 (arrow 404).
  • the add-on 450 identifies the merchant web site 425, and sends identifying details of the merchant web site 425 to a classification server 426 for web site classification (arrow 405).
  • the classification server 426 checks whether or not the merchant web site 425 is allowed according to the user profile; the classification server 426 sends the response (e.g., allowed web site or restricted web site) back to the add-on 450. If the merchant web site 425 is an allowed web site, then the add-on 450 identifies each product that the user is browsing, and sends the product information to the classification server 426 for product classification (arrow
  • the classification server 426 classifies the product and validates it against the user's profile, namely, determines whether or not the user is allowed to purchase this product according to the user's profile.
  • a response e.g., a binary approval or rejection response
  • the add-on 450 (arrow 406), indicating whether a purchase of this product is allowed or blocked.
  • the user may utilize the user device 421 to add the allowed product to the user's virtual shopping cart. If the product is not allowed, the add-on 450 blocks the user's ability to add the product to the user's virtual shopping cart.
  • the merchant web site 425 sends the user's shopping cart (which includes only allowed products) to an issuer authorization system 427 (arrow 407), where the transaction is validated and either approved or rejected.
  • the issuer authorization system 427 queries the authentication server 423 to check whether or not the particular user has an authenticated session (arrow 408). Additionally, the issuer authorization system 427 may check whether the products of the current transaction are allowed or restricted.
  • the authentication server 423 sends back to the issuer authorization system 427 a response indicating that the user is authenticated or non-authenticated (arrow 409).
  • the issuer authorization system 427 sends back to the merchant web site 425 a response indicating approval or rejection of the transaction (arrow 410); and the user device 421 receives a notification indicating whether the transaction was executed or failed
  • the authentication server 423, the sessions database 424, and the classification server 426 may be part of a sub-system 499 which may be owned, controlled, operated by a first entity; whereas other components of system 400 may be owned, controlled, and/or operated by one or more other entities.
  • FIG. 5 schematically illustrates a system 500 for protected purchasing, in accordance with some demonstrative embodiments of the invention.
  • arrows 501-506 demonstrate a flow of enhanced collaboration with merchants within system 500.
  • a user utilizes a user device 521 in order to open or launch a client application 522, through which the user enters user authentication data (arrow 501).
  • the client application 522 may be implemented as a web browser or web navigation software; the client application 522 may include, may be associated with, or may allow utilization of, for example, an add-on 550, e.g., a browser plug-in or extension or add-on, or a web-based portal.
  • an add-on component 550 is shown, for demonstrative purposes, other suitable components or modules may be used, for example, a web-based portal which may not necessarily require downloading of software and/or installation of software.
  • the add-on 550 sends the authentication data to an authentication server 523
  • the authentication server 523 attempts to authenticate the user; if the user passes the authentication, a protected session is stored in a sessions database 524 (arrow 503).
  • the authenticated user utilizes the user device 521 and the client application 522 in order to navigate to a merchant web site 525 (arrow 504).
  • the merchant web site 525 has enhanced integration with system 500; accordingly, upon login of the user to the merchant web site 525, the merchant web site sends a query about the user profile to a users server 526 (arrow 505).
  • the users server 526 replies by sending back to the merchant web site 525 user's information (arrow 506), for example, fields of interest to the user, categories in which the user is allowed to purchase or is blocked from purchasing, or the like.
  • the user's information may be utilized by the merchant web site 525 in order to tailor the user experience, as well as the products offered to the user, to the user's preferences and purchase restrictions.
  • the actual purchase of a product by a user from a merchant web site 525 may be performed, for example, using flows similar to the flows described with reference to Figures 3 and 4.
  • the authentication server 523, the sessions database 524, and the users server 526 may be part of a sub-system 599 which may be owned, controlled, operated by a first entity; whereas other components of system 500 may be owned, controlled, and/or operated by one or more other entities.
  • Figure 6 schematically illustrates a system 600 for protected purchasing, in accordance with some demonstrative embodiments of the invention.
  • arrows 601-606 demonstrate a flow of an offline transaction utilizing system 600.
  • a user utilizes a payment article 621, for example, a payment card, at an offline merchant location in order to purchase one or more products.
  • a payment article 621 for example, a payment card
  • the user may swipe a credit card or a debit card at a Point of Sale (POS) terminal 622 (arrow 601), and may optionally perform other or additional operations, e.g., enter a PIN or code, sign with a pen, sign with an electronic pen, beam or wireless transfer user data or user identity data, or the like.
  • POS Point of Sale
  • the POS terminal 622 sends to an authentication server 623, for example, user authentication information as well as details of the purchased products (arrow 602).
  • the authentication server 623 verifies the details of the payment article 621 versus the additional information entered by the user at the POS terminal 622. If the user is identified, the purchase details are sent from the authentication server 623 to a classification server 624 (arrow 603), in order to analyze the purchased products based on the user profile. [00145]
  • the classification server 624 sends to the authentication server 623 a response indicating approval and/or denial (arrow 604).
  • the response may indicate that all the products that the user attempts to purchased are allowed; the response may indicate that all the products that the user attempts to purchase are denied; or the response may indicate that one or more of the products that the user attempts to purchase are allowed and one or more of the products that the user attempts to purchase are denied.
  • the authentication server 623 sends the verification and/or denial information to the POS terminal 622 (arrow 605).
  • the POS terminal 622 sends a query to a card issuer authorization system 625, the query representing an attempted purchase of only the products that were approved by the classification server 624 (arrow 606).
  • the issuer authorization system 625 sends a query to the authentication server
  • the authentication server 623 sends a response to the issuer authorization system
  • the issuer authorization system 625 sends a response to the POS terminal 622, indicating whether the transaction is approved or denied (arrow 609).
  • the authentication server 623 and the classification server 623 are identical to the authentication server 623 and the classification server
  • sub-system 699 may be owned, controlled, operated by a first entity; whereas other components of system 600 may be owned, controlled, and/or operated by one or more other entities.
  • one or more components described herein may be implemented using suitable hardware components and/or software components, for example, a processor, a memory unit, a storage unit, an input unit, an output unit, a wireless or wired communication unit, an Operating System (OS), one or more software applications, or the like.
  • a processor for example, a processor, a memory unit, a storage unit, an input unit, an output unit, a wireless or wired communication unit, an Operating System (OS), one or more software applications, or the like.
  • OS Operating System
  • Some embodiments may utilize client/server architecture, publisher/subscriber architecture, fully centralized architecture, partially centralized architecture, fully distributed architecture, partially distributed architecture, scalable Peer to Peer (P2P) architecture, or other suitable architectures or combinations thereof.
  • P2P Peer to Peer
  • computing may refer to operation(s) and/or process(es) of a computer, a computing platform, a computing system, or other electronic computing device, that manipulate and/or transform data represented i as physical (e.g., electronic) quantities within the computer's registers and/or memories into other data similarly represented as physical quantities within the computer's registers and/or memories or other information storage medium that may store instructions to perform operations and/or processes.
  • Some embodiments may take the form of an entirely hardware embodiment, an
  • some embodiments may take the form of a computer program product accessible from a computer-usable or computer-readable medium providing program
  • a computer-usable or computer-readable medium may be or may include any apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
  • the medium may be or may include an electronic,
  • a computer-readable medium may include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a Random Access Memory (RAM), a Read-Only Memory (ROM), a rigid magnetic disk, an optical disk, or the like.
  • RAM Random Access Memory
  • ROM Read-Only Memory
  • optical disks include
  • CD-ROM Compact Disk - Read-Only Memory
  • CD-R/W Compact Disk - Read/Write
  • DVD or the like.
  • a data processing system suitable for storing and/or executing program code may include at least one processor coupled directly or indirectly to memory elements, for example, through a system bus.
  • the memory elements may include, for
  • I/O devices including but not limited to keyboards, displays, pointing devices, etc.
  • I/O controllers may be coupled to the system either directly or through intervening I/O controllers.
  • network adapters may be coupled to the system to enable the data processing system to become coupled to other data processing systems or remote printers or storage devices, for example, through intervening private or public networks.
  • modems, cable modems and Ethernet cards are demonstrative examples of types of network adapters. Other suitable components may be used.
  • Some embodiments may be implemented by software, by hardware, or by any combination of software and/or hardware as may be suitable for specific applications or in accordance with specific design requirements. Some embodiments may include units and/or sub-units, which may be separate of each other or combined together, in whole or in part, and may be implemented using specific, multi-purpose or general processors or controllers. Some
  • embodiments may include buffers, registers, stacks, storage units and/or memory units, for temporary or long-term storage of data or in order to facilitate the operation of particular implementations.
  • Some embodiments may be implemented, for example, using a machine-readable medium or article which may store an instruction or a set of instructions that, if executed by a
  • Such machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, electronic device, electronic system, computing system, processing system, computer, processor, or the like, and may be implemented using any suitable combination of hardware and/or software.
  • the machine-readable medium or article may include, for example, any suitable type of memory unit, memory device, memory article, memory medium, storage device, storage article, storage medium and/or storage unit; for example, memory, removable or non-removable media, erasable or non-erasable media, writeable or re- writeable media, digital or analog media, hard disk drive, floppy disk, Compact Disk Read Only Memory (CD-ROM), Compact Disk Recordable (CD-R), Compact Disk Re- Writeable (CD- RW), optical disk, magnetic media, various types of Digital Versatile Disks (DVDs), a tape, a cassette, or the like.
  • any suitable type of memory unit for example, any suitable type of memory unit, memory device, memory article, memory medium, storage device, storage article, storage medium and/or storage unit; for example, memory, removable or non-removable media, erasable or non-erasable media, writeable or re- writeable media, digital or analog media, hard disk drive, floppy disk, Compact Disk
  • the instructions may include any suitable type of code, for example, source code, compiled code, interpreted code, executable code, static code, dynamic code, or the like, and may be implemented using any suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language, e.g., C, C++, Java, BASIC, Pascal, Fortran, Cobol, assembly language, machine code, or the like.
  • code for example, source code, compiled code, interpreted code, executable code, static code, dynamic code, or the like
  • suitable high-level, low-level, object-oriented, visual, compiled and/or interpreted programming language e.g., C, C++, Java, BASIC, Pascal, Fortran, Cobol, assembly language, machine code, or the like.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

L'invention concerne un dispositif, un système et un procédé d'achat protégé. Par exemple, un procédé pour l'achat protégé d'articles par l'intermédiaire d'un réseau de communication ayant un serveur, comprend : la réception, au niveau du serveur, d'une requête provenant d'un utilisateur pour acheter un article ; sur la base d'un profil de l'utilisateur, la détermination du fait que l'article est approuvé ou non pour un achat par l'utilisateur ; et si l'article est approuvé pour un achat par l'utilisateur, l'autorisation du traitement d'une transaction pour acheter l'article par l'utilisateur.
PCT/IL2008/000869 2007-06-25 2008-06-25 Dispositif, système et procédé d'achat protégé Ceased WO2009001355A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US94595107P 2007-06-25 2007-06-25
US60/945,951 2007-06-25

Publications (2)

Publication Number Publication Date
WO2009001355A2 true WO2009001355A2 (fr) 2008-12-31
WO2009001355A3 WO2009001355A3 (fr) 2010-01-07

Family

ID=40186120

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IL2008/000869 Ceased WO2009001355A2 (fr) 2007-06-25 2008-06-25 Dispositif, système et procédé d'achat protégé

Country Status (1)

Country Link
WO (1) WO2009001355A2 (fr)

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5907831A (en) * 1997-04-04 1999-05-25 Lotvin; Mikhail Computer apparatus and methods supporting different categories of users
JP3202968B2 (ja) * 1998-06-30 2001-08-27 インターナショナル・ビジネス・マシーンズ・コーポレーション 表示制御情報生成方法及びコンピュータ
US7031945B1 (en) * 2000-07-24 2006-04-18 Donner Irah H System and method for reallocating and/or upgrading and/or rewarding tickets, other event admittance means, goods and/or services
US20030195858A1 (en) * 2002-04-10 2003-10-16 Fujio Watanabe Distributed information storage, authentication and authorization system
US20040172279A1 (en) * 2002-08-22 2004-09-02 Ncommon Partners Lp System and method for objectively managing complex familial interactions and responsibilities
US20050096986A1 (en) * 2003-09-05 2005-05-05 De La Rue International, Limited Method of electronically managing payment media

Also Published As

Publication number Publication date
WO2009001355A3 (fr) 2010-01-07

Similar Documents

Publication Publication Date Title
US20230419294A1 (en) Contacts for misdirected payments and user authentication
US10552828B2 (en) Multiple tokenization for authentication
US9934502B1 (en) Contacts for misdirected payments and user authentication
CN113656781B (zh) 跨应用程序统一登录
US11580523B2 (en) NFC card verification
US9852416B2 (en) System and method for authorizing a payment transaction
US11354673B1 (en) Data security enhancement for online transactions involving payment card accounts
US20160155114A1 (en) Smart communication device secured electronic payment system
AU2021200597A1 (en) Processing a mobile payload
US20030055785A1 (en) System and method for electronic wallet transactions
US20090063312A1 (en) Method and System for Processing Secure Wireless Payment Transactions and for Providing a Virtual Terminal for Merchant Processing of Such Transactions
US20180068309A1 (en) System and method for authorizing payment transaction based on device locations
WO2015107442A1 (fr) Systèmes et procédés d'émission de cartes de paiement mobile par réseau de communication mobile et dispositifs connectés à internet
AU2011203835A1 (en) Method and apparatus for billing purchases from a mobile phone application
CA3054287C (fr) Contacts pour paiements mal achemines et authentification d'utilisateur
US20190026704A1 (en) Method of registering a membership for an electronic payment, system for same, and apparatus and terminal thereof
US20180183805A1 (en) System and method of authorization of simple, sequential and parallel requests with means of authorization through previously defined parameters
US9792603B1 (en) Companion applets for web-based transactions
Anwar et al. In Wallet We Trust: Bypassing the Digital Wallets Payment Security for Free Shopping
US20140006271A1 (en) Cross-network electronic payment processing system and method
WO2009001355A2 (fr) Dispositif, système et procédé d'achat protégé
HK1228129B (zh) 一种支付方法及装置
WO2015056119A1 (fr) Système et procédé pour permettre des transactions

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08763626

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08763626

Country of ref document: EP

Kind code of ref document: A2