Abstract: Value based tokens are generated for inclusion on a data carrier which may be applied to a media such as a coupon, bank note etc. The tokens are generated by a core system which communicates with application specific wrappers. The wrappers supply token parameters to the core that are specific to the application and the core generates the tokens, and stores them for later authentication. The core then encodes the tokens onto a data carrier under the control of the wrapper and distributes the tokens under the control of the wrapper. When a token is presented for validation, for example by a customer in a shop, the encoded data carrier is scanned and the token retrieved. It is passed back to the core by the wrapper for validation of its identification number and other parameters.

Abstract: Items that require authentication, such as coupons or tickets are printed with a data carrier such as a data matrix or an RFID device. Encoded on the data carrier is a value based token, which comprises a header, a payload and a security portion. The header identifies the token type and also includes a unique identification of the token. A PIN flag may also be included. The payload may be encrypted and contain data which gives an authorised party access to a portion of a databases that stores information corresponding to the token identifier. The security portion may comprise a hash or a digital signature.

Abstract: Personalised money may be produced on-line and carry an identifier having at least a first and a second data set. The first data set may represent a unique item identifier and the second data set other item related information. Both data sets are encrypted and printed on the money, for example encoded in a data matrix symbol. The user may present the printed money for redemption at which point the data matrix symbol is scanned to retrieve the encrypted data sets. The data set including the unique identifier may be sent to a remote location for decryption and comparison against a stored identifier. The second data set may be decrypted and compared locally. Different encryption may be used for the two data sets.

Abstract: An identification system where providing' identification data sets that contain different types of information accessible by different parties, removes the need for all potential readers of the object to be able to access all information, and to contact a third party during the verification process is disclosed. The identification data sets are encrypted and printed in a portable physical form as an identity object. Graphical symbols, such as a data matrix, or RFID tags or secure chips may be used to store encrypted data. These may be incorporated into a passport or other identification document. Additional identity objects may be printed for use in identifying objects connected with a user or source that contain a subset of the information in the original data matrix.

Abstract: Medical prescriptions may be produced in electronic form and carry a plurality of encoded, encrypted data sets. The first data set may represent a unique prescription identifier and the second data set a patient identifier such as a PIN: Both data sets are encrypted and printed on the item, for example encoded in a data matrix. The patient may present a printed prescription to a chemist at which point the data matix symbol is canned to retrieve the encrypted data sets. The data set including the unique identifier may be sent to a remote location for decryption and comparison against a stored identifier to verify the prescription as genuine. The second data set may be decrypted and compared locally to verify that the person presenting the prescription is the patient or an authorised representative of the patient. If both data sets are vertified, the chemist maydispense the medicine. Further data sets may include details of the prescription and prescription history, and details of the doctor and the chemist.

Abstract: The security of invoices as between purchaser and supplier may be improved by printing a data matrix symbol or other glyph on the invoice. The data matrix contains two layers or portions of data. The first layer or portion contains invoice data and the second layer or portion contains secure data relating to the purchaser and supplier. This may include a trusted supplier status, a trusted supplier code and a unique voice identifier, or a reference thereto. On receipt of the invoice by the purchaser the data matrix is scanned and the trusted supplier status and supplier codes retrieved. These may be compared against a store of codes and status to verify the invoice as authentic. The secure data or a reference to the secure data may be re-encoded into a data matrix which may be affixed to a remittance advice sent by the purchaser to the supplier.

Abstract: A security paper such as a bank note has a data matrix printed or attached to it. The data matrix includes an encoded unique identifier for the security paper which may be read by a scanner and compared with a store of unique identifiers to authenticate the bank note. The remote store may include an indication as to whether or not the bank note is activated or whether it has not been issued or has been released from circulation. Data on the data matrix may be arranged in layers with a second layer containing further data associated with the bank note. The data in one or more layers may be encrypted using different encryption algorithms whereby different parties may have access to the data on different layers. RFID tags may be used in addition or as an alternative to data matrixes.