WO2015121833A1

WO2015121833A1 - Security tag deactivation

Info

Publication number: WO2015121833A1
Application number: PCT/IB2015/051080
Authority: WO
Inventors: Alan Joseph O'REGAN; Horatio Nelson HUXHAM; Tara Anne MOSS; Hough Arie VAN WYK; Selim Aissi; Gyan Prakash; Ajit Gaddam
Original assignee: Visa International Service Association
Priority date: 2014-02-14
Filing date: 2015-02-13
Publication date: 2015-08-20

Abstract

A system and method for deactivating a security tag are provided. The method is performed on a mobile device and includes the steps of facilitating payment for a selected product using the mobile device, receiving or allowing access to a deactivation code corresponding to the selected product from a product server; and deactivating a security tag of the selected product by means of wireless proximity communication of the deactivation code from the mobile device to the security tag.

Description

SECURITY TAG DEACTIVATION

CROSS-REFERENCES TO RELATED APPLICATIONS

[0001 ] This application claims priority to South African provisional patent application number 2014/01 125 filed on 14 February 2014 entitled "Electronic tag deactivation", which is incorporated by reference herein.

BACKGROUND TO THE INVENTION

[0002] Electronic article surveillance (EAS) is a method employed to prevent shoplifting and removal of property from certain locations. Articles may be fitted with special electronic security tags. When an active tag is moved into a detection area, typically near an exit point provided with a detection system, the tag activates an alarm. Some tags, for example microwave tags, are removable from products, and can be re-used. These tags are typically removed at a checkout counter or point-of-sale, for example at a retailer or library. Other tags can be disabled by a magnetic or electromagnetic field, and remain on the article. A further example of security tags is radio frequency identification (RFID) tags. After deactivation, these tags may be moved into a detection area without activating an alarm.

[0003] Self-checkout systems currently in use at retail stores provide customers with the opportunity to pay for items with minimal or no assistance from a store employee. Generally, self-checkout systems enable customers to scan barcodes themselves on products that they wish to buy. After scanning, they are required to pay for the products by any accepted method, and may be required to deactivate or remove security tags associated with the products they are purchasing by taking the products to a dedicated security tag point. Self-checkout may be preferred by retailers due to the fact that the required amount of staff is reduced. However, shoplifting remains a major drawback of systems in which a store employee is not involved in the payment process.

[0004] Systems are available which allow users to scan a barcode on a product in a retail store with their mobile phone, and add the product to a virtual basket. Once all the products have been added to the basket, they can process the payment via their mobile phone. The payment may be processed on the user's mobile device, and an electronic receipt shown to a store employee may be used as proof of payment before the customer is allowed to leave the store. Unfortunately, this system still requires an employee to interact with the customer, negating the main advantage of a self-checkout system. BRIEF SUMMARY OF THE INVENTION

[0005] In accordance with an embodiment of the invention there is provided a method for deactivating a security tag, the method performed on a mobile device and including the steps of: facilitating payment for a selected product using the mobile device by communication of payment credentials from the mobile device to a remote payment authorizing server, wherein an identifier of the mobile device is provided to the remote payment authorizing server; receiving or allowing access to a deactivation code corresponding to the selected product from a product server; and deactivating a security tag of the selected product by means of wireless proximity communication of the deactivation code from the mobile device to the security tag.

[0006] Further features provide for the method to include the steps of capturing or receiving information associated with the selected product including a product identifier; and including using the product identifier to identify the selected product facilitating payment for the specific product or a group of products; and for the information to be captured from the security tag.

[0007] Still further features provide for the step of facilitating payment for a selected product to be a pre-authorization of payment for the selected product to reserve funds for the selected product; and wherein deactivating a security tag of the selected product deactivates the security tag for a predetermined period of time; and wherein the method includes confirming if the payment is to be finalized within the predetermined period of time.

[0008] Yet further features provide for the step of facilitating payment to include providing payment credentials prior to capturing information associated with one or more selected products; and receiving a deactivation code for each selected product from a product server on receipt of a product identifier for the selected product. [0009] Further features provide for the step of facilitating payment to include providing payment credentials after scanning a selected product; and receiving a deactivation code from the product server on confirmation of successful payment for the selected product.

[0010] In at least one embodiment, the deactivation code may be a radio frequency or a serial number.

[0011 ] A further feature provides for the step of allowing access to a deactivation code to provide an unlock code for a deactivation code already loaded on the mobile device. [0012] A still further feature provides for the step of capturing information associated with the selected product to include a locked deactivation code.

[0013] The invention extends to a method for deactivating a security tag, the method performed at a product server and including the steps of: receiving confirmation of payment for a selected product, wherein the confirmation includes an identifier of a mobile device and a product identifier; looking up the product identifier to obtain a deactivation code or unlock instruction for a deactivation code for the selected product; transmitting the deactivation code or the unlock instruction for the deactivation code corresponding to the selected product to the mobile device using the identifier of the mobile device. [0014] A further feature provides for the step of receiving confirmation of payment for a selected product to be received from a payment authorizing server.

[0015] The invention extends to a mobile device for deactivating a security tag, comprising: a payment facility component for facilitating payment for a selected product using the mobile device by communication of payment credentials from the mobile device to a remote payment authorizing server, wherein an identifier of the mobile device is provided to the remote payment authorizing server; a deactivation code component for receiving or allowing access to a deactivation code corresponding to the selected product from a product server; and a deactivating component for deactivating a security tag of the selected product including a wireless proximity communication component for communication of the deactivation code from the mobile device to the security tag.

[0016] A further feature provides for the mobile device to include a scanning component for capturing information associated with the selected product including a product identifier.

[0017] Further features provide for the payment facility component for facilitating payment for a selected product to facilitate a pre-authorization of payment for the selected product to reserve funds for the selected product; for the deactivating component for deactivating a security tag of the selected product to deactivate the security tag for a predetermined period of time; and for the mobile device to include a confirmation component for receiving user confirmation if the payment is to be finalized within the predetermined period of time.

[0018] A still further feature provides for the deactivation code to include at least one of a radio frequency signal and a serial number. [0019] A yet further feature provides for the deactivation code component to include a pre-loaded deactivation code for a selected product and to receive an unlock code for the pre-loaded deactivation code.

[0020] A further feature provides for the scanning component for capturing information associated with the selected product to include capturing a locked deactivation code.

[0021 ] A still further feature provides for the mobile device to be a consumer's personal communication device having mobile payment capabilities by communication with a remote payment authorizing server. [0022] A yet further feature provides for the mobile device to be a store-provided handheld point of sale device in which a payment card is insertable and having mobile payment capabilities by dedicated communication with a remote payment authorizing server.

[0023] The invention extends to a product server for deactivating a security tag, comprising: a payment confirmation component for receiving confirmation of payment for a selected product, wherein the confirmation includes an identifier of a mobile device and a product identifier; a database component for looking up the product identifier to obtain a deactivation code or unlock instruction for a deactivation code for the selected product; and a deactivation code transmitting component for transmitting the deactivation code or the unlock instruction for the deactivation code corresponding to the selected product to the mobile device using the identifier of the mobile device.

[0024] A further feature provides for the payment confirmation component to receive confirmation of payment for a selected product from a payment authorizing server.

[0025] A still further feature provides for the product server to be at a retail environment and the server communication component to use a local wireless network for communication with one or more mobile devices in the retail environment.

[0026] A yet further feature provides for the product server to be remote from a retail environment and for the server communication component to use remote data communication with one or more mobile devices.

[0027] According to another aspect of the present invention there is provided a computer program product for deactivating a security tag the computer program product comprising a computer-readable medium having stored computer-readable program code for performing the steps of: facilitating payment for a selected product using the mobile device by communication of payment credentials from the mobile device to a remote payment authorising server, wherein an identifier of the mobile device is provided to the remote payment authorizing server; receiving or allowing access to a deactivation code corresponding to the selected product from a product server; and deactivating a security tag of the selected product by means of wireless proximity communication of the deactivation code from the mobile device to the security tag.

[0028] According to another aspect of the present invention there is provided a computer program product for deactivating a security tag the computer program product comprising a computer-readable medium having stored computer-readable program code for performing the steps of: receiving confirmation of payment for a selected product, wherein the confirmation includes an identifier of a mobile device and a product identifier; looking up the product identifier to obtain a deactivation code or unlock instruction for a deactivation code for the selected product; and transmitting the deactivation code or the unlock instruction for the deactivation code corresponding to the selected product to the mobile device using the identifier of the mobile device. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] FIG. 1 illustrates a system for deactivating a security tag according to an embodiment of the invention;

[0030] FIG. 2A illustrates a method of deactivating a security tag as carried out at a mobile device according to an embodiment of the invention; [0031 ] FIG. 2B illustrates a method of deactivating a security tag as carried out at a product server according to an embodiment of the invention;

[0032] FIG. 3 shows a mobile device according to an embodiment of the invention;

[0033] FIG. 4 shows a product server according to an embodiment of the invention;

[0034] FIG. 5 is a flow diagram illustrating a first example embodiment of the method according to the present invention;

[0035] FIG. 6 is a flow diagram illustrating a second example embodiment of the method according to the present invention;

[0036] FIG. 7 is a flow diagram illustrating a third example embodiment of the method according to the present invention; [0037] FIG. 8 is a swim-lane flow diagram a fourth example embodiment of the method according to the present invention; [0038] FIG. 9 illustrates an embodiment of a computing device in accordance with the present invention; and

[0039] FIG. 10 illustrates an embodiment of a block diagram of a communication device in accordance with the present invention. DETAILED DESCRIPTION

[0040] Embodiments of the described methods and systems for deactivating a security tag are provided. A mobile device is used by a consumer in a retail environment to effect payment for products which may be goods and/or services. The products may be secured with a security tag to restrict the use or movement of the product including preventing unauthorized removal from a location or unauthorized access to the product.

[0041 ] A security tag may prevent opening of the product packaging or may spoil or damage the product. This may apply to packaging which contains goods, but may also apply to a product in the form of a service in which service activation instructions are within the packaging. The security tag may provide an alarm if tampered with. [0042] A security tag may prevent removal of the product from a location by activating an alarm if the security tag passes through a gateway having a detection system.

[0043] A security tag may take various different forms examples of which are described below. The described method and system provide deactivation of a security tag by a mobile device upon confirmation of payment transaction for the goods from the mobile device.

[0044] In a first embodiment, the mobile device may be the consumer's own personal mobile device, for example in the form of a mobile phone or tablet having communication capabilities. The consumer's mobile device may have payment capabilities. Payment capabilities may take various forms, in one example, a mobile wallet securely stores payment credentials in the mobile device, in another example, a cloud based payment system stores the payment credentials remotely and payment is authorized from the consumer's device. The form of payment capability is not restricted in this description as long as authorization is securely provided by the consumer via the mobile device.

[0045] In a second embodiment, the mobile device may be a store provided mobile device in the form of a handheld point of sale (POS) device in which a consumer's payment card may be inserted. The store provided mobile device will have secure financial processing channels from the device. [0046] These and further embodiment are described further below, in particular with reference to FIGS. 5 to 8.

[0047] Referring to FIG. 1 an embodiment of a system (100) for deactivation of a security tag is illustrated. [0048] A user (122) in a retail environment uses a mobile device (1 10). The mobile device (1 10) may a user's own mobile communication device such as a smartphone, tablet, etc. or may be a store-provided mobile device in the form of a handheld POS device.

[0049] The mobile device (1 10) may have capabilities and features which are described in more detail in reference to FIG. 3 including at least a payment capability and a tag deactivation capability.

[0050] The mobile device (1 10) may be in communication with a financial transaction server (1 14) which may be provided by a financial institution for secure remote communication for payment transactions from mobile devices.

[0051 ] The mobile device (1 10) may also be in communication with a product server (1 16) which may have an associated database (1 18) storing product identifiers, information, and security tag information including deactivation codes. The product server (1 16) may be local to the retail environment, for example, a store product server within a local network, or may be provided remotely, for example for a range of stores in which case communication with the mobile device (1 10) may be via a wide area network, or other mobile communication channels.

[0052] In use, a user may visit a retail store at which he or she wishes to transact.

Products (120, 122) in the retail store are equipped with anti-theft security tags (124, 126). In one embodiment the security tags are near-field communication (NFC) tags. However, the type of security tag used may be any suitable EAS-type tag including, but not limited to, magnetic, acousto-magnetic, microwave, and radio frequency. These tags may be uniquely associated with a specific product.

[0053] The security tags may be configured to set off an alarm (128) associated with a detection system (130) when the tags are brought into a detection zone of the detection system (130). The detection zone may be located near an entrance and/or exit of the store so that the alarm (128) is only activated when a product with an active security tag is removed from the store itself, rather than when moved around within the store. With NFC security tags, an active tag may be configured to transmit an "active" message to the detection zone when scanned. [0054] Other forms of security tag (124, 126) may be used with the described system which may include an alarm in the security tag (124, 126) which may sound or send an alert to a monitoring system when the security tag (124, 126) is tampered with.

[0055] Referring to FIG. 2A, a flow diagram (200) of an embodiment of a method for deactivating a security tag is provided. The method may be performed on a mobile device, for example, with the functionality provided by an application running on the mobile device and accessing functionality from other features and programs on the mobile device.

[0056] The method may capture or receive (201 ) information associated with a selected product including a product identifier. For example, the method may scan a code provided at the product, or may capture the information from a tag such as a product information tag which may be incorporated into a security tag.

[0057] The method may facilitate payment (202) for a selected product using the mobile device by communication of payment credentials from the mobile device to a remote payment authorising server. An identifier of the mobile device may be provided to the remote payment authorizing server for further communication of the deactivation code. Facilitating payment for a selected product may be a pre-authorization of payment for the selected product to reserve funds for the selected product. Facilitating payment may include providing payment credentials prior to capturing information associated with one or more selected products. Alternatively, these may be provided after scanning a selected product. [0058] The method may then receive (203) a deactivation code corresponding to the selected product from a product server or may allow access to a deactivation code, for example, where a deactivation code is already provided on the mobile device or has been received whilst capturing information relating to the selected product. If a deactivation code has already been received, it may be in a form unusable by the mobile device until access is allowed to it. For example, the deactivation code may be encrypted or partially provided and a decryption key may be provided.

[0059] The method may then deactivate (204) a security tag of the selected product by means of wireless proximity communication of the deactivation code from the mobile device to the security tag. Deactivating a security tag of the selected product may deactivate the security tag for a predetermined period of time. The deactivation code may includes at least one of a radio frequency signal and a serial number.

[0060] Referring to FIG. 2B, a flow diagram (250) of an embodiment of a method for deactivating a security tag is provided as performed at a product server (1 16) such as that of FIG. 1 . [0061 ] The method may include receiving (251 ) confirmation of payment for a selected product including an identifier of a mobile device from which the payment has been made and a product identifier.

[0062] The method may look up (252) the product identifier to obtain a deactivation code or unlock instruction for a deactivation code for the selected product. This may be stored in a database accessed by the product server.

[0063] The server may transmit (253) the deactivation code or the unlock instruction for the deactivation code corresponding to the selected product to the mobile device using the identifier of the mobile device. [0064] FIG. 3 shows a mobile device (300) for use in the system and method described with reference to FIG. 1 and FIG. 2. The mobile device (300) may be a personal communication device, typically a smartphone of a user, and includes a payment facility component (310), a scanning component (320), a deactivation code component (330) and a deactivation component (340). [0065] The payment facility component (310) is used to facilitate payment for a product. In the embodiment described with reference to FIG. 1 , the payment component contains account details of the user at a financial institution. At least some of the properties of a payment card may need to be transmitted to the financial institution to successfully facilitate payment. It is envisaged that the payment component may be a mobile payment component such as a mobile wallet. In such an embodiment of the invention, a user has a mobile wallet containing electronic money on their mobile device, typically a smartphone. There may then be no need for the financial institution to be directly involved in the transaction. Information regarding a product is still obtained from the product server as described above. However, when a user indicates to the mobile application that they wish to purchase an item, the electronic money is transferred straight to the product server, where the server deals therewith in an appropriate manner. The product server recognizes successful receipt of the money, and transmits the deactivation code as described above.

[0066] The scanning component (320) is used to scan a product information tag in order to capture information associated with a specific product, including a product identifier. In the embodiment described with reference to FIG. 1 , the capturing component is an NFC reader which reads information from the tag. As described above, the capturing component may also be a camera which captures an image of a barcode or QR code for analysis by the smartphone, an infrared component, or the like. [0067] The deactivation code component (330) is used to receive the deactivation code from the product server, or may be used to allow access to a deactivation code stored on the mobile device. If operation of the method is facilitated by an application operating on the mobile device, the application may include a database which has unlocking codes of various products pre-loaded thereon. In response to receiving an indication from the remote server that payment has been successfully facilitated for a specific product in the form of an unlock code, the deactivation code of the product may be released for use.

[0068] It should be noted that the scanning component may be configured to also capture a locked deactivation code. After payment for the product has been processed, the mobile device may be presented with an unlock code for unlocking the locked deactivation code.

[0069] The deactivating component (330) is used to deactivate a security tag of a specific product. The deactivating component may include a wireless proximity communication component for communicating the deactivation code from the mobile device to the security tag. The wireless proximity communication component may be of any suitable type, including a Bluetooth component, a RFID component, a NFC component, or the like. In some embodiments, the deactivation component may be a transmitter which transmits a deactivation code in the form of frequency waves at a specific frequency required to disable a tag as described above, a serial number serving as a "kill command", or the like. [0070] In the embodiment where funds are reserved and a temporary deactivation code is transmitted to a security tag, the payment facility component may facilitate a pre- authorization of payment for the selected product to reserve funds for the product. The deactivating component may deactivate the security tag for a predetermined amount of time. It is envisaged that the mobile device may include a confirmation component for receiving user confirmation if payment is to be finalized. Payment may then be finalized by transmitting the preserved funds to the merchant's financial account.

[0071 ] It should be noted that the deactivation code may be transmitted by the deactivation component to the security tag in the form of a radio frequency signal, a serial number, or any other suitable format. In the embodiment where the deactivation code is pre- loaded on the mobile device and released upon receiving an unlock code, a database component containing such codes may be associated with the deactivation code component.

[0072] It is envisaged that the scanning component may include capturing a locked deactivation code from the security tag. Once payment has been successfully processed, the mobile device may receive an unlock code for unlocking the deactivation code. The security tag may then be deactivated using the unlocked deactivation code.

[0073] In an embodiment where the mobile device is a personal communication device of a consumer or user, the mobile device may have the required mobile payment capabilities allowing it to process payment via a remote payment authorization server, or via a mobile wallet operating on the mobile device.

[0074] It is envisaged that a user's account may only be debited by a financial institution once for an amount of transactions performed at a single retailer. In such an embodiment, a user will transmit a number of product identifiers to a financial institution. As long as the user's account can support a specific purchase value, the financial institution may send a "payment processed" message to the product server. The product server will then transmit a deactivation code for every such message received. The financial institution may then at a later stage, for example when instructed to do so by the user, after a predetermined amount of time, or upon reaching a certain transaction value, debit the user's account in a single transaction. It should be noted that the value of any product for which a "payment processed" message has been transmitted to the product server will be debited from a user's account to prevent a user from deactivating a product for which they have not paid.

[0075] In an alternative embodiment of the invention, the mobile device is a handheld point of sale (POS) device which accepts a payment credential of a user, for example a payment card. The POS device includes a payment facility component, a deactivation code component, a scanning component and a deactivation component similar to that described with respect to the mobile device described with reference to FIG. 3.

[0076] In such a POS embodiment, a user inserts a payment card into the device, and proceeds to scan articles which they would like to purchase. The user may initially be prompted for a PIN code before they start to scan products. The user may then proceed to scan all articles he or she wishes to purchase, transmitting product identifiers and payment credentials to a financial institution or to a remote server after every scan. A deactivation code is received from the product server after each successful payment, allowing a user to deactivate a tag on a product after facilitating payment therefore, and before scanning a next product.

[0077] Referring to FIG. 4, a block diagram shows a server (1 16) for use in deactivating a security tag. The server (1 16) may be a product server as shown in FIG. 1 . [0078] The product server (1 16) may include a payment confirmation component

(401 ) for receiving confirmation of payment for a selected product. The payment confirmation component (401 ) may receive the payment confirmation from a payment server of a financial intuition or via the mobile device which has originated the payment transaction. The payment confirmation may include at least an identifier of the mobile device and a product identifier;

[0079] The remote server (1 16) may include or have access to a database component (1 17) for looking up the product identifier to obtain a deactivation code or unlock instruction for a deactivation code for the selected product. [0080] The product server (1 16) may also include a deactivation code transmitting component (402) for transmitting the deactivation code or the unlock instruction for the deactivation code corresponding to the selected product to the mobile device using the identifier of the mobile device.

[0081 ] The product server (1 16) may be provided at a retail environment and a server communication component (403) may use a local wireless network for communication with one or more mobile devices in the retail environment. Alternatively, the product server (1 16) may be remote from a retail environment and the server communication component (403) may use remote data communication with one or more mobile devices.

[0082] Referring to FIG. 5, a first embodiment of a method of operation of the system (100) is shown as it is performed on the mobile device (1 10) of FIG. 1 when the mobile device (1 10) is a user's own communication device such as a smartphone.

[0083] In use, the user (1 12) visits a retail store at which he or she wishes to transact. The user launches an application on their smartphone which interact with functional capabilities of the smartphone to carry out the described method. [0084] The smartphone may capture information relating to a selected product by means of scanning (510) a product information tag. In the present embodiment, the product information tag is also the security tag on the product. It should, however, be noted that the product information tag may alternatively be a separate two-dimensional of three- dimensional bar code, such a QR code. Such other codes may be scanned with, for example, a camera of the mobile device, a Bluetooth component, or a radio frequency identification (RFID) component of the mobile device, depending on the type of product information tag that is employed. [0085] Scanning of an NFC security tag is performed by the user bringing their NFC- enabled smartphone in close proximity to the tag, with the smartphone reading data from the tag. The read data received may include unique identification details of the product including a unique product identifier, as well as optionally other details relating to the product, for example, regarding the retail store in which the product is located.

[0086] The smartphone then transmits (520), to the product server (1 16), either a request for further information regarding the selected product or a notification of intent to purchase the product and includes the unique product identifier. The server retrieves the requested data from the database (1 18) associated therewith, and transmits this information back to the smartphone, which receives (530) the data. If additional information has been requested, the user is able to study details of the watch, for example its unique features, warranty details, price, or the like.

[0087] If a user indicates that they wish to purchase the product, payment is facilitated (540) by means of a payment request, including payment credentials associated with the user and a unique identifier of the mobile device, transmitted to a remote payment server (1 14) of a financial institution. The unique identifier of the mobile device may allow the payment credentials to be checked for conformity to the mobile device, as may have been previously allowed, or it may allow the transaction to be traced back to the mobile device if required. The payment request may include at least a part of the unique details of the product, including the price and the product identifier.

[0088] If the payment is successfully processed, the financial institution may indicate this fact to the product server (1 16) in a payment processed message including the product identifier provided by the user in the payment transaction. Alternatively, this may be done via the mobile device with the user receiving a payment confirmation and forwarding this to the product server together with the product identifier.

[0089] The product server (1 16) may then retrieve a deactivation code, in the present embodiment a serial number corresponding to the product identifier, from the database (1 18) and transmits this to the smartphone. Security tags in some embodiments may have a "kill command" which is activated when an appropriate serial code is received. This serial number is transmitted as the deactivation code.

[0090] The smartphone receives (550) the deactivation code, and is prompted to deactivate the tag of the product which he or she has just paid for.

[0091 ] The user then again presents their smartphone to the security tag on the product. By means of NFC, the deactivation serial number is transmitted to the tag. If the serial code matches the "kill command", the tag is deactivated (560). Deactivation of the NFC tag may occur by deactivating the tag completely, rendering it unusable, or it may occur by the tag being configured to transmit an "inactive" code to the detection system when scanned. The user is then able to take the product with the tag thereon with him or her, and move into and through the detection zone of the detection system without activating the alarm.

[0092] It should be noted that the method described above may at least partially alleviate some of the abovementioned problems with current self-checkout systems. A user does not need to present an electronic slip to a store assistant. Any user walking through a detection area of a detection zone without activating the alarm may be assumed to have paid for the products in their possession.

[0093] If a product information tag is used which needs to be scanned and interpreted to extract the relevant information, for example a QR code, the mobile device may include an extracting component to extract the required information from the product. Alternatively, the details obtained from the product information tag may be transmitted to the remote product server, where the product may be extracted from the code by means of an extracting component of the server.

[0094] The type of security tag used may be any suitable EAS-type tag including, but not limited to, magnetic, acousto-magnetic, microwave, and radio frequency. In at least one embodiment, a tag is configured to deactivate when receiving a deactivation code in the form of a specific frequency, and the smartphone receives the deactivation frequency from the product server. By transmitting the correct frequency near the tag, the tag will be disabled, and the product with the tag can be removed from the store without activating a security alarm. In another embodiment, the tag is configured to deactivate upon receiving a deactivation code in the form of a serial number.

[0095] FIG. 6 shows a second embodiment of a method (600) in which the mobile device (1 10) is a handheld POS device and in which a number of products can be deactivated before payment is processed. A user may insert (610) a payment card into the POS device, which reads the required payment credentials from the card. The POS device may request (620) a PIN code in a next step, and, if the PIN code is correct, the POS device may enter a scanning mode in which product tags may be scanned.

[0096] It should be noted that the payment card in this embodiment may have a limited amount which it is allowed to spend. The limit may be set up on a month-by month, week-by-week, day-by-day, or on a per-retailer basis. [0097] The user may then scan (630) a security tag of a product that they wish to purchase, and the POS device may receive product details. Product details may be displayed on the POS device. A user may indicate (640) on the POS device that they wish to purchase the specific product and a total amount of the current purchase is calculated. The POS device may retrieve (650) a deactivation code from its memory and may deactivate the product in an appropriate manner. It should be noted that a POS device is associated with a specific retail store, and may have a database associated therewith which contains the deactivation codes of products in the store. The deactivation codes may be stored on the POS device and only released upon confirmation of a payment transaction for the identified product. Alternatively, the deactivation codes may be stored on a product server and communicated to the POS device when a payment confirmation for one or more selected products is received by the product server.

[0098] Finally, payment for the total value of products deactivated is processed

(660), typically by means of a standard POS electronic fund transmission using a financial account associated with the payment card. It should be noted that payment may be processed automatically when the appropriate limit has been reached. Alternatively, payment may be processed when a user removes their card from the POS device, or when a user indicates that they are done shopping in the particular retail store. The POS device will typically request, from the financial institution, the appropriate limit before entering the scanning mode. This limit may be an amount available in an account of the user. Alternatively, a user may be prompted what the maximum amount is that they wish to spend.

[0099] As an alternative method each item may be processed for payment individually using the POS device with each deactivation code being received or retrieved at the POS device upon confirmation of the payment for the selected product. This may be particularly relevant for high value products where only a small number of products is being purchased.

[0100] Referring to FIG. 7, a third embodiment of the described method (700) is illustrated. In this embodiment, the system may be configured such that the step of facilitating payment for the product is a pre-authorization of payment for the selected product in order to reserve funds for the selected product. The security tag may be deactivated for a predetermined amount of time, allowing a user to test out the product. If the product is returned after testing, the reserved funds may be released back to the user. If the product is not returned, or the user confirms that they wish to purchase the product, final transfer of the reserved funds may be processed to a merchant of the product. This embodiment may be applied in conjunction with any of the previously described embodiments. [0101 ] A product information or security tag may be scanned (710) to obtain identification information of a selected product. An option may be selected (720) by the user on the mobile device to temporarily deactivate the security tag on the selected product. This may be applicable when a user wishes to sample the product. For example in the case of a piece of clothing, a security tag may be part of a lock in the clothing preventing removal of the clothing from a rack or may include a wire preventing wearing of the clothing. A temporary deactivation of the tag may be provide in order to try the clothing on.

[0102] The mobile device may facilitate (730) a pre-authorization of funds against his payment credentials by communication with the payment server. An expiry time on the pre- authorization may be applied within which the pre-authorization may be cancelled.

[0103] A temporary deactivation code may be received (740) at the mobile device as in the previous embodiments this may be from a product server. The temporary deactivation code may deactivate (750) the security tag when transmitted from the mobile device. However, the deactivation of the security tag has a time limit after which it will reactivate. [0104] A user may select to cancel (760) the payment transaction within the time limit if they do not wish to proceed with the purchase. If no action is taken, the purchase may be automatically confirmed and the reserved funds deducted from the user's account. Alternatively, a positive confirmation may be provided by the user for the purchase which may be earlier than the time limit. [0105] Although the embodiments described above specifically mention a smartphone and a POS device as possible mobile device, it should be noted that any mobile device may be suitable for use, for example a feature phone, PDA, tablet PC, or the like.

[0106] It is envisaged that product deactivation codes may also be stored on a server associated with a specific retailer. The mobile device may then communicate with this server to obtain deactivation codes. Additionally, payment may be processed by means of this server as well. The product server and database may also be associated with and located at a specific retailer, with deactivation codes only shared with mobile devices transacting in the specific store. It is envisaged that communication with such a type of server may occur over a Wi-Fi communications channel. In particular, a handheld POS may be configured to communicate exclusively with a retailer-specific server over the retailer's Wi-Fi network dedicated for POS devices. Alternatively, an application operating on a user's mobile device may be configured to only communicate over dedicated local communication networks associated with approved retailers. [0107] In an additional embodiment, a user scans products at a self-checkout counter, processes payment therefore on their mobile device, and disables the security tags on the purchased products using their mobile device.

[0108] A swim-lane flow diagram of the method of such a fourth embodiment is shown in FIG. 8 with steps carried out at a mobile device (1 10) and a POS device (800). A user retrieves products that they wish to purchase in a store, and takes the products to a self-checkout counter. At the counter, the user scans (810) identification tags, typically barcodes, of the products using a POS device provided at the self-checkout counter. The user is presented (820) with an indication of the total cost of the purchase. [0109] The user may then process (830) payment therefore using their mobile device. Payment may be processed via a mobile wallet, or by transmitting payment credentials on the mobile device to an acquiring financial institution.

[0110] When payment has been successfully processed, the POS device receives an indication thereof and may transmit (840) the required deactivation codes to the mobile device of the user. The user may then deactivate (850) the security tags of the products using their mobile device as described above.

[0111 ] In an additional embodiment, the security tags may be modifiable by the POS device. Upon scanning the products, all tags of products being scanned at the time may be configured such that they share a single deactivation key. Once payment for the scanned articles have been processed, the POS device may provide the user with a single deactivation code that may be used to deactivate all of the products.

[0112] FIG. 9 illustrates an example of a computing device (900) in which various aspects of the disclosure may be implemented. The computing device (900) may be suitable for storing and executing computer program code. The various participants and elements in the previously described system diagrams may use any suitable number of subsystems or components of the computing device (900) to facilitate the functions described herein.

[0113] The computing device (900) may include subsystems or components interconnected via a communication infrastructure (905) (for example, a communications bus, a cross-over bar device, or a network). The computing device (900) may include at least one central processor (910) and at least one memory component in the form of computer- readable media.

[0114] The memory components may include system memory (915), which may include read only memory (ROM) and random access memory (RAM). A basic input/output system (BIOS) may be stored in ROM. System software may be stored in the system memory (915) including operating system software.

[0115] The memory components may also include secondary memory (920). The secondary memory (920) may include a fixed disk (921 ), such as a hard disk drive, and, optionally, one or more removable-storage interfaces (922) for removable-storage components (923).

[0116] The removable-storage interfaces (922) may be in the form of removable- storage drives (for example, magnetic tape drives, optical disk drives, floppy disk drives, etc.) for corresponding removable storage-components (for example, a magnetic tape, an optical disk, a floppy disk, etc.), which may be written to and read by the removable-storage drive.

[0117] The removable-storage interfaces (922) may also be in the form of ports or sockets for interfacing with other forms of removable-storage components (923) such as a flash memory drive, external hard drive, or removable memory chip, etc. [0118] The computing device (900) may include an external communications interface (930) for operation of the computing device (900) in a networked environment enabling transfer of data between multiple computing devices (900). Data transferred via the external communications interface (930) may be in the form of signals, which may be electronic, electromagnetic, optical, radio, or other types of signal. [0119] The external communications interface (930) may enable communication of data between the computing device (900) and other computing devices including servers and external storage facilities. Web services may be accessible by the computing device (900) via the communications interface (930).

[0120] The external communications interface (930) may also enable other forms of communication to and from the computing device (900) including, voice communication, near field communication, Bluetooth, etc.

[0121 ] The computer-readable media in the form of the various memory components may provide storage of computer-executable instructions, data structures, program modules, and other data. A computer program product may be provided by a computer-readable medium having stored computer-readable program code executable by the central processor (910). [0122] A computer program product may be provided by a non-transient computer- readable medium, or may be provided via a signal or other transient means via the communications interface (930).

[0123] Interconnection via the communication infrastructure (905) allows a central processor (910) to communicate with each subsystem or component and to control the execution of instructions from the memory components, as well as the exchange of information between subsystems or components.

[0124] Peripherals (such as printers, scanners, cameras, or the like) and input/output

(I/O) devices (such as a mouse, touchpad, keyboard, microphone, joystick, or the like) may couple to the computing device (900) either directly or via an I/O controller (935). These components may be connected to the computing device (900) by any number of means known in the art, such as a serial port.

[0125] One or more monitors (945) may be coupled via a display or video adapter

(940) to the computing device (900). [0126] FIG. 10 shows a block diagram of a communication device (1000) that may be used in embodiments of the disclosure. The communication device (1000) may be a cell phone, a feature phone, a smart phone, a satellite phone, or a computing device having a phone capability.

[0127] The communication device (1000) may include a processor (1005) (e.g., a microprocessor) for processing the functions of the communication device (1000) and a display (1020) to allow a user to see the phone numbers and other information and messages. The communication device (1000) may further include an input element (1025) to allow a user to input information into the device (e.g., input buttons, touch screen, etc.), a speaker (1030) to allow the user to hear voice communication, music, etc., and a microphone (1035) to allow the user to transmit his or her voice through the communication device (1000).

[0128] The processor (1010) of the communication device (1000) may connect to a memory (1015). The memory (1015) may be in the form of a computer-readable medium that stores data and, optionally, computer-executable instructions. [0129] The communication device (1000) may also include a communication element

(1040) for connection to communication channels (e.g., a cellular telephone network, data transmission network, Wi-Fi network, satellite-phone network, Internet network, Satellite Internet Network, etc.). The communication element (1040) may include an associated wireless transfer element, such as an antenna.

[0130] The communication element (1040) may include a subscriber identity module

(SIM) in the form of an integrated circuit that stores an international mobile subscriber identity and the related key used to identify and authenticate a subscriber using the communication device (1000). One or more subscriber identity modules may be removable from the communication device (1000) or embedded in the communication device (1000).

[0131 ] The communication device (1000) may further include a contactless element

(1050), which is typically implemented in the form of a semiconductor chip (or other data storage element) with an associated wireless transfer element, such as an antenna. The contactless element (1050) may be associated with (e.g., embedded within) the communication device (1000) and data or control instructions transmitted via a cellular network may be applied to the contactless element (1050) by means of a contactless element interface (not shown). The contactless element interface may function to permit the exchange of data and/or control instructions between mobile device circuitry (and hence the cellular network) and the contactless element (1050).

[0132] The contactless element (1050) may be capable of transferring and receiving data using a near field communications (NFC) capability (or near field communications medium) typically in accordance with a standardized protocol or data transfer mechanism (e.g., ISO 14443/NFC). Near field communications capability is a short-range communications capability, such as radio-frequency identification (RFID), Bluetooth, infrared, or other data transfer capability that can be used to exchange data between the communication device (1000) and an interrogation device. Thus, the communication device (1000) may be capable of communicating and transferring data and/or control instructions via both a cellular network and near field communications capability.

[0133] The data stored in the memory (1015) may include: operation data relating to the operation of the communication device (1000), personal data (e.g., name, date of birth, identification number, etc.), financial data (e.g., bank account information, a bank identification number (BIN), credit or debit card number information, account balance information, expiration date, loyalty provider account numbers, etc.), transit information (e.g., as in a subway or train pass), access information (e.g., as in access badges), etc. A user may transmit this data from the communication device (1000) to selected receivers.

[0134] The communication device (1000) may be, amongst other things, a notification device that can receive alert messages and access reports, a portable merchant device that can be used to transmit control data identifying a discount to be applied, as well as a portable consumer device that can be used to make payments. The foregoing description of the embodiments of the invention has been presented for the purpose of illustration; it is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Persons skilled in the relevant art can appreciate that many modifications and variations are possible in light of the above disclosure.

[0135] Some portions of this description describe the embodiments of the invention in terms of algorithms and symbolic representations of operations on information. These algorithmic descriptions and representations are commonly used by those skilled in the data processing arts to convey the substance of their work effectively to others skilled in the art. These operations, while described functionally, computationally, or logically, are understood to be implemented by computer programs or equivalent electrical circuits, microcode, or the like. The described operations may be embodied in software, firmware, hardware, or any combinations thereof. [0136] The software components or functions described in this application may be implemented as software code to be executed by one or more processors using any suitable computer language such as, for example, Java, C++, or Perl using, for example, conventional or object-oriented techniques. The software code may be stored as a series of instructions, or commands on a non-transitory computer-readable medium, such as a random access memory (RAM), a read-only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM. Any such computer- readable medium may also reside on or within a single computational apparatus, and may be present on or within different computational apparatuses within a system or network.

[0137] Any of the steps, operations, or processes described herein may be performed or implemented with one or more hardware or software modules, alone or in combination with other devices. In one embodiment, a software module is implemented with a computer program product comprising a non-transient computer-readable medium containing computer program code, which can be executed by a computer processor for performing any or all of the steps, operations, or processes described. [0138] Finally, the language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter. It is therefore intended that the scope of the invention be limited not by this detailed description, but rather by any claims that issue on an application based hereon. Accordingly, the disclosure of the embodiments of the invention is intended to be illustrative, but not limiting, of the scope of the invention, which is set forth in the following claims.

Claims

WHAT IS CLAIMED IS:

A method for deactivating a security tag, the method performed on a mobile device and including the steps of:

facilitating payment for a selected product using the mobile device by communication of payment credentials from the mobile device to a remote payment authorising server, wherein an identifier of the mobile device is provided to the remote payment authorizing server;

receiving or allowing access to a deactivation code corresponding to the selected product from a product server; and

deactivating a security tag of the selected product by means of wireless proximity communication of the deactivation code from the mobile device to the security tag.

The method as claimed in claim 1 , which includes the step of:

capturing or receiving information associated with the selected product including a product identifier; and

including using the product identifier to identify the selected product.

The method as claimed in claim 1 , wherein

facilitating payment for a selected product is a pre-authorization of payment for the selected product to reserve funds for the selected product; and wherein

deactivating a security tag of the selected product deactivates the security tag for a predetermined period of time; and wherein the method includes

confirming if the payment is to be finalized within the predetermined period of time.

The method as claimed in claim 1 , wherein facilitating payment includes:

providing payment credentials prior to capturing information associated with one or more selected products; and wherein

receiving a deactivation code for each selected product from a product server on receipt of a product identifier for the selected product.

The method as claimed in claim 1 , wherein facilitating payment includes:

providing payment credentials after scanning a selected product; and wherein receiving a deactivation code from the product server on confirmation of successful payment for the selected product.

The method as claimed in claim 1 , wherein the deactivation code includes at least one of a radio frequency signal and a serial number.

The method as claimed in claim 1 , wherein allowing access to a deactivation code provides an unlock code for a deactivation code already loaded on the mobile device.

The method as claimed in claim 9, wherein capturing information associated with the selected product includes a locked deactivation code.

A method for deactivating a security tag, the method performed at a product server and including the steps of:

receiving confirmation of payment for a selected product, wherein the confirmation includes an identifier of a mobile device and a product identifier;

looking up the product identifier to obtain a deactivation code or unlock instruction for a deactivation code for the selected product;

transmitting the deactivation code or the unlock instruction for the deactivation code corresponding to the selected product to the mobile device using the identifier of the mobile device.

The method as claimed in claim 9, wherein receiving confirmation of payment for a selected product is received from a payment authorizing server.

A mobile device for deactivating a security tag, comprising:

a payment facility component for facilitating payment for a selected product using the mobile device by communication of payment credentials from the mobile device to a remote payment authorising server, wherein an identifier of the mobile device is provided to the remote payment authorizing server;

a deactivation code component for receiving or allowing access to a deactivation code corresponding to the selected product from a product server; and a deactivating component for deactivating a security tag of the selected product including a wireless proximity communication component for communication of the deactivation code from the mobile device to the security tag.

The mobile device as claimed in claim 1 1 , including: a scanning component for capturing information associated with the selected product including a product identifier.

The mobile device as claimed in claim 1 1 , wherein

the payment facility component for facilitating payment for a selected product facilitates a pre-authorization of payment for the selected product to reserve funds for the selected product; and wherein

the deactivating component for deactivating a security tag of the selected product deactivates the security tag for a predetermined period of time; and wherein the mobile device includes

a confirmation component for receiving user confirmation if the payment is to be finalized within the predetermined period of time.

The mobile device as claimed in claim 1 1 , wherein the deactivation code includes at least one of a radio frequency signal and a serial number. 5. The mobile device as claimed in claim 1 1 , wherein the deactivation code component includes a pre-loaded deactivation code for a selected product and receives an unlock code for the pre-loaded deactivation code. 6. The mobile device as claimed in claim 12, wherein the scanning component for capturing information associated with the selected product includes capturing a locked deactivation code.

The mobile device as claimed in claim 1 1 , wherein the mobile device is a consumer's personal communication device having mobile payment capabilities by communication with a remote payment authorizing server.

The mobile device as claimed in claim 1 1 , wherein the mobile device is a store- provided handheld point of sale device in which a payment card is insertable and having mobile payment capabilities by dedicated communication with a remote payment authorizing server.

A product server for use in deactivating a security tag, comprising a payment confirmation component for receiving confirmation of payment for a selected product, wherein the confirmation includes an identifier of a mobile device and a product identifier;

a database component for looking up the product identifier to obtain a deactivation code or unlock instruction for a deactivation code for the selected product;

a deactivation code transmitting component for transmitting the deactivation code or the unlock instruction for the deactivation code corresponding to the selected product to the mobile device using the identifier of the mobile device.

20. The product server as claimed in claim 19, wherein the payment confirmation component receives confirmation of payment for a selected product from a payment authorizing server.

21 . The product server as claimed in claim 19, wherein the product server is at a retail environment and a server communication component uses a local wireless network for communication with one or more mobile devices in the retail environment.

22. The product server as claimed in claim 19, wherein the product server is remote from a retail environment and a server communication component uses remote data communication with one or more mobile devices.