Removable tag element with access credentials

Abstract

A method and system for conducting transactions using a removable marking element are disclosed. A removable marking element containing a voucher can be associated with an account. A user can activate and manage the account via a mobile device. The mobile device can access the account by providing a product identifier. The product identifier can be provided in the removable marking element packaging. For example, the product identifier can be encoded in a machine-readable code on the packaging.

Description

[0001] This invention application is a divisional application of the invention patent application with international application number PCT / US2017 / 033336, international application date May 18, 2017, application number 201780038720.9 entering the Chinese national phase, and name “Removable marking element with access credentials”.

[0002] Cross-reference to related applications

[0003] This application is an international patent application claiming the benefit of the filing date of U.S. patent application No. 15 / 192,656, filed June 24, 2016, which is incorporated herein by reference in its entirety for all purposes. Technical Field Background Art

[0004] People often carry multiple items. For example, a person may carry a cell phone, driver's license, access badge, insurance card, wallet, and many other devices and the cards inside them. Carrying these items can be inconvenient and uncomfortable, and the items can be lost or stolen.

[0005] In some cases, a person may not wish to or be permitted to carry certain items, but may still need the functionality of the items. For example, a person attending an event (e.g., a concert) may not be allowed to bring handbags into the event area. Consequently, the attendee may not have a handbag to store tickets, wallets, driver's licenses, etc. However, the event attendee may still wish to use tickets for entry, driver's licenses for proof of age, and / or credit cards for purchases during the event.

[0006] Embodiments of the invention address these and other problems, individually and collectively. Summary of the Invention

[0007] One embodiment of the present invention relates to a method. The method includes obtaining, by a mobile device, a product identifier by obtaining a machine-readable code associated with a removable marking element adapted to be adhered to the skin. The removable marking element includes an integrated circuit configured to transmit, during a transaction, first access credentials associated with a first account to an access device via a wireless communication channel. The method also includes transmitting, by the mobile device, a message including the product identifier, a value associated with a second account, and the second access credentials to a server computer. The server computer identifies the first account based on the product identifier, and the server computer loads the first account with the value from the second account.

[0008] Another embodiment of the present invention relates to a mobile device configured to perform the above-described method.

[0009] Another embodiment of the present invention relates to a method comprising: receiving, by a server computer, from a mobile device a message comprising a value associated with a second account, a second access credential, and a product identifier associated with a removable marking element adapted to be adhered to the skin. The mobile device obtains the product identifier by obtaining a machine-readable code associated with the removable marking element. The removable marking element comprises an integrated circuit configured to transmit, during a transaction, a first access credential associated with a first account to an access device via a wireless communication channel. The method further comprises identifying the first account based on the product identifier and loading the first account with the value from the second account.

[0010] Another embodiment of the present invention relates to a server computer configured to execute the above method.

[0011] Another embodiment of the present invention relates to a method comprising capturing, by a user via a mobile device, a product identifier associated with a removable marking element suitable for adhering to the skin. The method further comprises providing a value and a second access credential to the mobile device. The mobile device sends the product identifier, the value, and the second access credential to a server computer. The server computer identifies a first account associated with the product identifier, and the server computer credits the first account with the value from the second account. The method further comprises: applying the removable marking element to the user's body by the user; and presenting the product identifier to an access device by the user to conduct a transaction. The access device obtains a first access credential from the removable marking element, and the access device sends the first access credential to the server computer. The server computer authorizes the transaction based on the first account. The method also comprises receiving an indication that the transaction is authorized.

[0012] Additional details regarding embodiments of the invention can be found in the detailed description and accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 A block diagram of a system according to an embodiment of the present invention is shown.

[0014] Figure 2 Examples of removable marking elements and associated packaging according to embodiments of the present invention are shown.

[0015] Figure 3 An example of a removable marking element applied to a user's skin is shown in accordance with an embodiment of the present invention.

[0016] Figures 4A to 4B An example of account management functionality on a mobile device according to an embodiment of the present invention is shown.

[0017] Figures 5A to 5B A further example of account management functionality on a mobile device according to an embodiment of the present invention is shown.

[0018] Figure 6 A block diagram of an exemplary mobile device according to an embodiment of the present invention is shown.

[0019] Figure 7 A block diagram of an authorization computer according to an embodiment of the present invention is shown.

[0020] Figure 8 A flow chart illustrating a method for managing and conducting transactions with removable marking elements is shown, according to an embodiment of the present invention. DETAILED DESCRIPTION

[0021] Embodiments of the present invention relate to removable marking elements that can be used for transactions. For example, the removable marking element can be associated with an account of an authorized entity. The removable marking element can be presented to an access device to conduct a transaction, and the transaction can be authorized based on the removable marking element account (e.g., the authorized entity).

[0022] In some embodiments, the removable marking element may include credentials. For example, the removable marking element may include access credentials that can be used to identify an account that owns the removable marking element.

[0023] In some embodiments, the removable marking element may include an embedded or attached microchip (or any other suitable type of integrated circuit), and the microchip may store access credentials. The chip may be capable of transmitting via contact or contactless transmission (e.g., NFC, IR, etc.) transmits the access credentials to the access device.

[0024] In some embodiments, the removable marking element may include a marking such as a stego image. For example, the access credential may be encoded into a stego image. The access device (or another suitable computer) may be capable of decoding the stego image to obtain the access credential.

[0025] Thus, embodiments of the present invention allow for the use of removable marking elements in place of typical transaction devices (e.g., access cards, payment devices, personal identification cards, etc.). This advantageously improves user convenience and device security. Instead of carrying one or more cards or other devices, the user simply attaches the removable marking element to their body (e.g., forearm). For example, the removable marking element may be adhered to the user's skin. A typical transaction device may be lost or stolen, but a removable marking element may not be forgotten or stolen because the removable marking element may be attached to the user's body. Additionally, the removable marking element may advantageously serve as a transaction device for children who typically do not have a typical transaction device or cannot be trusted with a typical transaction device. A parent may apply the removable marking element to the child's body and may manage the removable marking element account on the child's behalf (e.g., via a mobile device).

[0026] In some embodiments, a user can use a mobile device to activate, inject capital, link and / or manage a removable marking element account. For example, a user can contact an authorized entity (also referred to as a removable marking element account issuer) via a mobile device and request to activate a removable marking element account. The user can also provide funds, an access code, a login code, security information or any other suitable transaction-related information of a removable marking element account. For example, a user (via a mobile device) can provide a certain amount of funds for a removable marking element account, or can link a removable marking element account to a separate payment account. A mobile device can also be used as a tool for managing permissions, restrictions and any other suitable controls and parameters of a removable marking element account.

[0027] Thus, embodiments provide a convenient way for users to manage their removable markings. The removable marking element may not have a user interface for account management, but the mobile device may act as an intermediary between the removable marking element and the removable marking element account (e.g., at an authorized entity).

[0028] In some embodiments, a product identifier can be provided for initial access to a removable marking element account (e.g., to fund an account or to link a mobile device to a removable marking element). For example, the product identifier can be printed on the packaging for the removable marking element in the form of a machine-readable code (e.g., a barcode). When a user obtains the removable marking element, the user can scan the machine-readable code using a mobile device. The mobile device can then transmit the product identifier to an authorized entity. As a result, the authorized entity can identify the removable marking element account based on the product identifier and can allow the mobile device to access the removable marking element account.

[0029] Thus, embodiments provide a convenient way to activate and link a removable tag element so that it can be used to conduct transactions. In some embodiments, a user can scan (or otherwise obtain) a machine-readable code that comes with a removable tag element and then instantly access the removable tag element account (e.g., to activate, fund, manage, etc.). Thus, even if the removable tag element does not display an account identifier, the user can access and manage the removable tag element account.

[0030] In other embodiments, instead of a machine-readable code, an alphanumeric product identifier can be printed on the packaging. Additionally, the machine-readable code or product identifier can be mailed or telegraphed after obtaining the removable marking element (e.g., instead of printing the product identifier on the packaging).

[0031] In some embodiments, the product identifier can be used to identify the removable marking element account (e.g., for customer management), but the product identifier cannot be used to authorize payment for the transaction. In some embodiments, instead of including the product identifier, a transaction access credential can be provided to the user for initial account linking (e.g., the access credential can be printed as a machine-readable code on the removable marking element packaging).

[0032] Embodiments of the present invention allow removable marking elements and removable marking element accounts to be used for transactions of any suitable type. For example, a removable marking element account can be used as a payment account, and the removable marking element can be used for payment transactions. Additionally, a removable marking element account can be used as an access account, and the removable marking element can be used for access transactions. For example, a removable marking element can be used to access restricted areas (e.g., activities, buildings, etc.) or access restricted information (e.g., private computers, private databases, etc.). As another example, a removable marking element account can be used as an identity account, and the removable marking element can be used for identity verification. For example, a removable marking element can be used as identification (e.g., a driver's license or passport) when passing through security (e.g., at an airport).

[0033] For purposes of description, the removable marking element account will be primarily described herein as a payment account. However, as described above, the removable marking element account may be used as any other suitable type of account.

[0034] Before discussing specific embodiments of the present invention, some terms may be described in detail.

[0035] A "removable marking element" may comprise a removable marking. In some embodiments, the removable marking element may comprise an image on a person's skin. The removable marking element may fade and disappear within a specific time period (e.g., 2 hours, 1 day, 3 days, 1 week, 2 weeks, 1 month, or any other suitable amount of time). The removable marking element may be removed by washing. The removable marking element may be attached to the surface of a person's skin, and the removable marking element may be applied as an adhesive, drawn, painted, or sprayed in the form of body paint. In some embodiments, the removable marking element may be plastic that is transferred from paper or cardboard to the skin (e.g., by applying with a damp cloth). Examples of removable marking elements include temporary tattoos, stickers, body paint, makeup, and any other suitable material that can be applied to a user's body and then removed.

[0036] In some embodiments, the removable marking element may comprise a data storage medium, such as an electronic or magnetic data storage medium. For example, the removable marking element may comprise an embedded or attached integrated circuit (eg, a microchip).

[0037] A "temporary tattoo" may comprise an imaged laminate. The laminate may be attached to human skin. The laminate may comprise a printable release coating on a backing sheet, and the image is printed onto the printable release coating using ink. An ink-permeable film may be attached to the image, and an adhesive may be included on the exposed side of the film. The coating, image, and film may be attached to human skin by pressing the coating, image, film, and adhesive combination onto the skin (and removing the release sheet backing sheet from the film / image / coating).

[0038] A "removable marking element account" may include records associated with a removable marking element at an account provider. A removable marking element account may also be associated with an individual or organization. Examples of removable marking element accounts include payment accounts, access accounts, secure data accounts, membership accounts, mobile network accounts, identity accounts, or any other suitable type of account. A removable marking element account may include or be associated with a value, such as an amount of funds (e.g., a monetary value), access credentials, security information, identity data, or any other suitable data value. A removable marking element account may be identified by one or more sets of information, such as access credentials and / or product identifiers.

[0039] A "payment account" may include a user account that can be used for payment. Examples of payment accounts include a credit card account, a bank account (e.g., a checking account or savings account), a prepaid account, or any other suitable account associated with payment. In some embodiments, a payment account may be associated with one or more removable tokens. A payment account may be identified based on payment account information (e.g., payment credentials).

[0040] An "Access Account" may include a user account that may be used to gain access to restricted areas or restricted information.

[0041] A "credential" may be any suitable information that serves as reliable evidence of value, ownership, identity, or authority. A credential may be a string of numbers, letters, or any other suitable characters that can be presented or contained in any object or document that can serve as confirmation.

[0042] An "access credential" may be a credential associated with an authorization. For example, an access credential may provide access to funds, entry, secure clearing, or any other suitable type of access. An access credential may be associated with an account, such as a removable marking element account, a payment account, or a security account, and the access credential may include an account identifier. Examples of access credentials include payment credentials (e.g., a primary account number), entry credentials, security credentials, identity credentials, and any other suitable type of credential. An example of a security credential is a security code, which may be any suitable information associated with security. For example, a security code may include a set of alphanumeric characters, an image, or any other suitable value associated with access to a secure area or secure information.

[0043] "Payment credentials" may include the type of access credentials used for payment. Payment credentials may be directly associated with an account or may be derived from information associated with the account. Examples of payment credentials may include a PAN (primary account number or "account number"), user name, expiration date, and verification values ​​such as CVV (card verification value), dCVV (dynamic card verification value), CVV2 (card verification value 2), CVC3 card verification value, etc. An example of a PAN is a 16-digit number, such as "4147 0900 0000 1234."

[0044] A "product identifier" may be any suitable information for identifying a product. In some embodiments, a product identifier may be associated with a removable marking element account, but may not be configured for use with the removable marking element account. For example, a product identifier may be a non-transactional identifier.

[0045] A "steganographic image" may include an image containing hidden information. Examples of stego images include: a scrambled image, an image containing invisible information, an image containing blurred or obscured information, an image containing encoded information, and any other suitable image containing covert information. In some embodiments, when a stego image is viewed by the human eye (e.g., without the use of a tool or manipulation to reveal the hidden information), the viewer may see a "decorative target image." A decoy target image may be any suitable image that does not reveal the hidden information. In some embodiments, a decoy target image may appear to be an inconspicuous standard image and may not contain any indication that the covert data is present (e.g., it may not be obvious or detectable that the image is a stego image). A decoy target image may take the form of a generic image (e.g., an identification or landscape), a decorative photograph, a white noise image, a scrambled image, a blank or empty image, an image selected by the user, or any other suitable image.

[0046] A "mobile device" may include any suitable device that is movable. In some embodiments, a mobile device may be any suitable electronic device that may or may not be carried and operated by a user, and that may also provide telecommunication capabilities to a network. Examples of telecommunication capabilities include the use of a mobile phone (wireless) network, a wireless data network (e.g., 3G, 4G, or similar networks), Wi-Fi, Wi-Max, or any other communication medium that can provide access to a network, such as the Internet or a private network. Examples of mobile devices include mobile phones (e.g., cell phones), PDAs, tablet computers, netbooks, laptop computers, personal music players, handheld dedicated readers, and the like. Other examples of mobile devices include wearable devices such as smart watches, fitness bands, anklets, rings, earrings, and the like, as well as automobiles with telecommunication capabilities. A mobile device may include any suitable hardware and software for performing such functions, and may also include multiple devices or components (e.g., when a device remotely accesses a network by being tethered to another device, i.e., using the other device as a modem, the two devices used together may be considered a single mobile device).

[0047] A "device identifier" may include any suitable information used to identify a device. Examples of device identifiers include an MSISDN, a phone number, an SMS text address, an IP address, or any other information that can be used to identify a mobile device. In some embodiments, the device identifier may include a unique device number, such as an International Mobile Station Equipment Identity (IMEI) number, a unique serial number of a Subscriber Identity Module (SIM) card (i.e., an Integrated Circuit Card Identifier (ICCI)), or a unique International Mobile Subscriber Identity (IMSI).

[0048] An "application" may be computer code or other data stored on a computer-readable medium (eg, a memory element or a secure element) that is executable by a processor to perform tasks.

[0049] A "machine-readable code" may include information that can be read by a machine. In some embodiments, a machine-readable code includes information that can be scanned, photographed, received in an electronic message, or otherwise accessed by a machine, such as a computer or mobile device. An example of a machine-readable code is a barcode. A barcode may include numbers and a pattern of parallel lines of varying widths that encode information. A mobile device can scan the barcode to determine the size and width of the lines in the barcode, and the mobile device can obtain information based on the size and distance between the parallel lines. Another example of a machine-readable code is an RFID (radio frequency identification) chip. A mobile device may be able to scan an RFID chip by emitting radio waves. The RFID chip may respond to radio waves that convey information stored in the RFID chip.

[0050] An "access device" may be any suitable device that provides access to a remote system. An access device may also be used to communicate with a merchant computer, a transaction processing computer, an authentication computer, or any other suitable system. The access device may generally be located in any suitable location, for example, at the merchant's location. The access device may have any suitable form factor. Some examples of access devices include POS or point-of-sale devices (e.g., POS terminals), cellular phones, PDAs, personal computers (PCs), tablet PCs, handheld dedicated readers, set-top boxes, electronic cash registers (ECRs), automated teller machines (ATMs), virtual cash registers (VCRs), kiosks, security systems, access systems, and the like. The access device may use any suitable contact or contactless mode of operation to send or receive data to or from a user device, or to associate with a user device. In some embodiments where the access device may include a POS terminal, any suitable POS terminal may be used, and may include a reader, a processor, and a computer-readable medium. The reader may include any suitable contact or contactless mode of operation. For example, an exemplary card reader may include a radio frequency (RF) antenna, an optical scanner, a barcode reader, or a magnetic stripe reader to interact with a removable tag element, a payment device, and / or a mobile device.

[0051] An "authorization request message" may be an electronic message requesting authorization for a transaction. In some embodiments, the authorization request message is sent to a transaction processing computer and / or the issuer of a payment card to request authorization of the transaction. According to some embodiments, the authorization request message may conform to ISO 8583, a standard for systems for exchanging electronic transaction information associated with payments made by a user using a payment device or payment account. The authorization request message may include an issuer account identifier that may be associated with the payment device or payment account. The authorization request message may also include additional data elements corresponding to "identification information," including, by way of example only: a service code, CVV (card verification value), dCVV (dynamic card verification value), PAN (primary account number or "account number"), payment token, user name, expiration date, and the like. The authorization request message may also include "transaction information," e.g., any information associated with the current transaction, such as the transaction amount, merchant identifier, merchant location, acquiring bank identification number (BIN), card acceptor ID, information identifying the item being purchased, and any other information useful in determining whether to identify and / or authorize the transaction.

[0052] An "authorization response message" may be a message in response to an authorization request. In some cases, the authorization response message may be an electronic message generated by the issuing financial institution or a transaction processing computer in response to the authorization request message. The authorization response message may include (by way of example only) one or more of the following status indicators: approved - the transaction was approved; rejected - the transaction was not approved; or call center - the response is pending and the merchant must call a toll-free authorization number for more information. The authorization response message may also include an authorization code, which may be a code that the credit card issuing bank returns to the merchant's access device (e.g., a POS device) in response to the authorization request message in an electronic message (directly or through the transaction processing computer) indicating that the transaction is approved. The code may serve as evidence of authorization. As noted above, in some embodiments, the transaction processing computer may generate or forward the authorization response message to the merchant.

[0053] A "server computer" may include a powerful computer or computer cluster. For example, a server computer may be a mainframe, a small computer cluster, or a group of servers operating as a unit. In one example, a server computer may be a database server connected to a network server. The server computer may be connected to a database and may include any hardware, software, other logic, or combination thereof for servicing requests from one or more client computers.

[0054] Figure 1A system 100 is shown that includes several components. The system 100 includes a removable marking element 115 and a mobile device 120 operated by a user 110. The removable marking element 115 can be associated with a machine-readable code 112. The system 100 also includes a resource provider computer 130, a transfer computer 140, a transaction processing computer 150, and an authorization entity computer 160, each of which can be embodied by one or more computers. The removable marking element 115 can communicate with an access device 125, which can in turn communicate with the resource provider computer 130. Furthermore, the mobile device 120, the resource provider computer 130, the transfer computer 140, the transaction processing computer 150, and the authorization entity computer 160 can all be in operable communication with each other via any suitable communication channel or communication network. Suitable communication networks may be any one and / or a combination of the following: direct interconnection, the Internet, a local area network (LAN), a metropolitan area network (MAN), an operating mission as a node in the Internet (OMNI), a secure custom connection, a wide area network (WAN), a wireless network (e.g., using protocols such as, but not limited to, Wireless Application Protocol (WAP), I-mode, etc.), and the like.

[0055] Messages between computers, networks, and devices may be transmitted using secure communication protocols such as, but not limited to, File Transfer Protocol (FTP); Hypertext Transfer Protocol (HTTP); Secure Hypertext Transfer Protocol (HTTPS), Secure Sockets Layer (SSL), ISO (e.g., ISO 8583), and the like.

[0056] The user 110 may be able to use the removable tagging element 115 to conduct transactions with a resource provider associated with the resource provider computer 130. The removable tagging element 115 may store information associated with the removable tagging element account (e.g., a payment account or an access account) and / or the user 110. For example, the removable tagging element 115 may store access credentials (e.g., payment credentials or other account identifiers) and may provide this information to the access device 125 during a transaction.

[0057] Figure 2 , an example of a removable marking element 115 and associated packaging according to some embodiments of the present invention is shown in FIG. The removable marking element 115 may include an image 217. The image 217 is visible when the removable marking element 115 is applied to (or adhered to) the user's skin. In some embodiments, the removable marking element 115 may be personalized. For example, the user 110 may select or provide a specific image 217 that may be implemented as the removable marking element 115.

[0058] The removable tag element 115 can be associated with an account at the authorized entity computer 160 (also referred to as a "removable tag element account"). The removable tag element account can be associated with a set of access credentials 219 (e.g., payment credentials or access credentials). The access credentials 219 can include an account identifier, such as a primary account number (PAN), and any other suitable information. In some embodiments, the removable tag element 115 can be combined with the access credentials 219.

[0059] In some embodiments, the removable marking element 115 may include an integrated circuit 218, such as a microchip. The integrated circuit 218 may be embedded in the removable marking element 115, and the removable marking element 115 may be attached to a person (e.g., by adhering to the skin). The integrated circuit 218 may be capable of storing information and may be capable of transmitting information to another device (e.g., the access device 125). In some embodiments, the integrated circuit 218 may store access credentials 219.

[0060] Figure 3 , an example of a removable marking element 115 applied to a user's skin and interacting with an access device 125 according to some embodiments is shown in FIG. As shown, the removable marking element 115 can be applied to the user's forearm (or any other suitable location). An integrated circuit 218 embedded in the removable marking element 115 can thereby be attached to the user's forearm. In some embodiments, the integrated circuit 218 can be undetectable to the human eye (or at least briefly glanced at) because it can be small and / or hidden by an image pattern. The user 110 can present the integrated circuit 218 to the access device 215, and the integrated circuit 218 and the access device 215 can then be able to communicate through physical contact or a wireless communication channel (e.g., via NFC).

[0061] In some embodiments, the integrated circuit 218 may store any other suitable information. For example, the integrated circuit 218 may store the user's contact information (e.g., phone number or address), medical information, or any other suitable information. In some embodiments, the removable marking element 115 may also be used as a safety or tracking device for the child. If a child is lost, the merchant (or other entity with a scanning access device) can scan the integrated circuit 218 to obtain information about the child, such as the parent's phone number, medical information, or meeting place. In some embodiments, the integrated circuit 218 may also include GPS functionality (e.g., to track the child, or to track the location of a transaction).

[0062] Back to Figure 2In some embodiments, the removable marking element 115 may alternatively or additionally include a stego image. For example, some or all of the image 217 may be a stego image. In some embodiments, the access credential 219 may be hidden within the stego image. In some embodiments, the access device 125, the authorized entity computer 160, or any other suitable computer is capable of decoding the stego image and obtaining the access credential 219 (e.g., based on a photograph or scan of the stego image).

[0063] The user 110 may obtain the removable marking element 115 from a store, issuer, security administrator, or any other suitable entity. In some embodiments, the removable marking element 115 may be pre-programmed or otherwise already contain access credentials 219 before the user obtains the removable marking element 115. However, the removable marking element account may be inactive, empty, and / or contain no funds or access information. Therefore, after obtaining the removable marking element 115, the user 110 may seek to activate, load, manage, and / or personalize the removable marking element 115 and the removable marking element account.

[0064] like Figure 2 As shown, the removable marking element 115 can be provided to the user 110 in packaging 216, and the packaging 216 can contain information for accessing the removable marking element account and / or activating the removable marking element 115. In some embodiments, this information can take the form of a machine-readable code 112. Providing such account identification information on the packaging 216 can be beneficial because the removable marking element 115 may not contain any visible or user-readable account information.

[0065] In some embodiments, the removable marking element 115 may be visible within the packaging 216, thereby allowing the user 110 to select the removable marking element 115 based on the image 217. In some embodiments, the machine-readable code 112 may not be visible or scannable until the packaging 216 is opened and the removable marking element 115 is removed. For example, the machine-readable code 112 may be hidden behind the removable marking element 115 when the packaging 216 has not been opened.

[0066] In some embodiments, machine-readable code 112 may include a barcode, an RFID chip, or any other suitable type of machine-readable code. Mobile device 120 may read or scan machine-readable code 112, or otherwise obtain information from the machine-readable code. For example, machine-readable code 112 may be a barcode, and mobile device 120 may scan or capture an image of the barcode. In another example, machine-readable code 112 may be an RFID chip, and mobile device 120 may be able to use RF to communicate with the RFID chip and obtain information encoded in the RFID chip.

[0067] The machine-readable code 112 may include removable marking element account identification information. For example, the machine-readable code 112 may include a product identifier or access credential 219. The product identifier may be used to identify the removable marking element account, but may not be used for transactions. The product identifier may be included on the packaging 216 to allow activation of the removable marking element account without exposing sensitive information (e.g., transaction information). The access credential 219 may identify the removable marking element account and may be used for transactions involving the removable marking element account.

[0068] Thus, the machine-readable code 112 may enable the user 110 to access the removable marking element account. As a result, once the user 110 obtains the removable marking element 115, the user 110 may be able to activate and manage the removable marking element account (e.g., even if the account information is not printed on the removable marking element 115).

[0069] Back to Figure 1 In some embodiments, the user 110 may use the mobile device 120 to activate and manage the removable marking element 115. For example, the user 110 may operate the mobile device 120 to scan the machine-readable code 112. The mobile device 120 may be able to determine account identification information (e.g., a product identifier or access credentials) from the machine-readable code 112.

[0070] The mobile device 120 may communicate with the authorized entity computer 160 regarding the removable marking element account. For example, the mobile device 120 may include an application programmed to communicate with the authorized entity computer 160. The application may include a URL or other information for contacting the authorized entity computer 160. The application may also include instructions for the mobile device 120 to communicate with the authorized entity computer 160 upon obtaining the removable marking element identifier (e.g., by scanning a machine-readable code).

[0071] In some embodiments, once the mobile device 120 scans the machine-readable code 112, the mobile device 120 may send the machine-readable code information (e.g., a product identifier) ​​to the authorization entity computer 160. The authorization entity computer 160 may identify the removable marking element account based on the machine-readable code information and allow the user 110 to manage the account via the mobile device 120. In some embodiments, the authorization entity computer 160 may also link or associate the mobile device 120 with the removable marking element account (e.g., the mobile device 120 may be configured as a management device). As a result, the machine-readable code 112 may enable the user 110 to activate, fund, and otherwise manage the removable marking element 115 and the removable marking element account.

[0072] In some embodiments, instead of the machine readable code 112, Figure 2 The packaging 216 in the removable marking element 115 may include another type of information. For example, the packaging 216 may include a printed alphanumeric product identifier or access credential 219. Alternatively, the removable marking element account identification information may be mailed to the user 110 or electronically transmitted to the user's mobile device 120 when the user 110 initially requests or obtains the removable marking element 115. For example, the user 110 may provide the mailing address or mobile device 120 contact information to the removable marking element 115 provider (e.g., a merchant or issuer).

[0073] In another embodiment, if the removable marking element 115 contains a steganographic image, the user 110 can capture the image of the removable marking element 115 with the mobile device 120. The mobile device 120 can transmit the image to the authorized entity computer 160, thereby gaining access to the removable marking element account.

[0074] Please refer to Figures 4A to 4B An example of managing a removable marking element account via mobile device 120 according to some embodiments of the present invention is described.

[0075] Figure 4A An example mobile device 120 graphical user interface or display of mobile device 120 is shown. The mobile device 120 graphical user interface may be provided by a removable marking element management application. The removable marking element application may communicate with the authorized entity computer 160 and provide account management instructions thereto. Figure 4A As shown, in addition to activating a removable marking element account, the removable marking element application may also allow user 110 to link removable marking element 115 with mobile device 120. For example, user 110 may select the "Link Removable Marking Element" function 422, whereupon mobile device 120 may activate a camera or other scanner to scan machine-readable code 112. Once scanned, mobile device 120 may transmit the machine-readable code information, mobile device identification information (e.g., a phone number, email address, MSISDN, etc.), and any other suitable information to authorization entity computer 160 (e.g., via a URL or other contact information stored in the application). Authorization entity computer 160 may then link the removable marking element account with mobile device 120. For example, authorization entity computer 160 may associate a mobile device identifier with the removable marking element account.

[0076] The mobile device 120 (e.g., via the removable tagging element application) may also allow the user 110 to manage removable tagging element account settings, such as removable tagging element 115 permissions and restrictions. For example, the user 110 may select the "Manage Permissions" function 424, and the user 110 may then specify the parameters of the account. The user 110 may indicate when and where the removable tagging element 115 may be used, the types of transactions for which the removable tagging element 115 may be used, and any other suitable restrictions. For example, the removable tagging element 115 may be worn by a child, and a parent may set purchase limits. The user 110 may also be able to block or suspend an account (e.g., if the user 110 suspects fraud or improper use).

[0077] The mobile device 120 may also allow the user 110 to add funds, provide access credentials or a security code, or otherwise provide value or access data to the removable tag element account (e.g., via the removable tag element application). For example, the user 110 may select the "add funds" function 423. The user 110 may then provide payment information for the second account and specify an amount of funds to be transferred from the second account to the removable tag element account. The second account may be a pre-existing separate account associated with the user 110. Thus, the removable tag element account may be funded by the second account, and the removable tag element account may effectively serve as a prepaid account.

[0078] Figure 4B An example user interface for transferring funds is shown. User 110 can select one of the multiple linked removable tags 115 (e.g., by selecting one of the linked accounts in account list 427) and specify the amount of funds to transfer (e.g., by entering a value in amount field 428). User 110 can also provide information about a second account serving as a source of funds. Once the funding request is submitted, the removable tag element account can be funded as a prepaid account.

[0079] Alternatively, in some embodiments, user 110 may request that the removable marking element account be associated with a second account (e.g., a separate debit account, credit account, or prepaid account) so that the second account can be charged when the removable marking element 115 is used for a transaction. Thus, the removable marking element 115 can effectively serve as a payment device for the second account.

[0080] In some embodiments, as described above, the removable marking element 115 can be used for transactions other than payments. For example, instead of funds, the user 110 can provide identification, security, or access information via the removable marking element application, so that the removable marking element 115 can be used as an access badge or security token. The user 110 can also provide login credentials for a separate access or security account, so that the authorized entity computer 160 can obtain the access or security credentials from the separate account and load the credentials into the removable marking element account (or link the removable marking element account with the separate account).

[0081] Figure 5A , an example of a mobile device display screen for configuring access functionality according to an embodiment of the present invention is shown in FIG. The mobile device 120 (e.g., via a removable tag element application) may allow the user 110 to provide a security code, entry credentials, login information, or otherwise provide access data to the removable tag element account. For example, the user 110 may select the “Configure Access” function 523.

[0082] Then, if Figure 5B As shown, the mobile device 120 may provide a user interface for configuring access. The user 110 may select one of the multiple linked removable tags 115 (e.g., by selecting one of the several linked accounts in the account list 527) and may also provide a security code (e.g., by entering a value in the security code 528). For example, the user 110 may enter a security code for accessing a building. The mobile device 120 may then send the security code to the authorized entity computer 160, and the authorized entity computer 160 may associate the security code with the removable tag element account. As a result, the removable tag element 115 may then be associated with the security code and may be configured to provide access rights (e.g., access rights to the building).

[0083] Alternatively, in some embodiments, the user 110 may request that the removable marking element account be associated with a second account (e.g., a separate security account or access account). For example, the user 110 may provide access credentials or login information associated with the second account. As a result, when the removable marking element 115 is used to access a transaction, the second account can be identified and used to authorize the transaction. For example, a security code (or other access credentials) from the second account can be used to authorize the transaction. Thus, the removable marking element 115 can effectively serve as a token for the second account. For example, the removable marking element 115 can be used as a replacement for a pre-existing access badge.

[0084] Figure 6, an example of a mobile device 120 according to some embodiments of the present invention is shown in FIG. The mobile device 120 may include circuits for implementing certain device functions (e.g., a telephone). The functional elements responsible for implementing these functions may include a processor 120A, which may execute instructions for implementing the functions and operations of the device. The processor 120A may access a memory 120E (or another suitable data storage area or element) to retrieve instructions or data for executing instructions, such as a mobile application. A data input / output element 120C, such as a keyboard or touch screen, may be used to enable a user to operate the mobile device 120 and input data (e.g., user authentication data). The data input / output element may also be configured to output data (e.g., via a speaker). A display 120B may also be used to output data to the user. A communication element 120D may be used to enable data transmission between the mobile device 120 and a wired or wireless network (e.g., via an antenna 120H) to facilitate connection to the Internet or other networks and implement data transmission functions. Mobile device 120 may also include a contactless element interface 120F to enable data transmission between the contactless element 120G of the device and other elements, wherein the contactless element 120G may include a secure memory and a near-field communication data transmission element (or another form of short-range communication technology). Mobile device 120 may also include a camera 120J. Camera 120J can be used to capture or scan images, such as photos of machine-readable codes, steganographic images, removable tags, or any other suitable photo objects. As mentioned above, a cellular phone or similar device is an example of the mobile device 120 that can be used according to an embodiment of the present invention. However, without departing from the basic concept of the present invention, other forms or types of devices may be used. For example, mobile device 120 may alternatively take the form of a key card, a tablet computer, a wearable device, a vehicle such as a car, etc.

[0085] The memory 120E may include the removable marking element application 120K and any other suitable modules or data. The mobile device 120 may have any number of mobile applications installed or stored on the memory 120E, and is not limited to Figure 6. The memory 120E may also include code executable by the processor 120A to implement a method comprising: obtaining a product identifier by obtaining a machine-readable code associated with a removable marking element adapted to be adhered to the skin, wherein the removable marking element comprises an integrated circuit configured to transmit, during a transaction, a first access credential associated with a first account to an access device via a wireless communication channel; and transmitting a message comprising the product identifier, a value associated with a second account, and the second access credential to a server computer, wherein the server computer identifies the first account based on the product identifier, and wherein the server computer loads the first account with the value from the second account.

[0086] The removable marking element application 120K can provide a user interface for the user 110 to provide input for activating and managing the removable marking element using the mobile device 120. The removable marking element application 120K can be programmed to cause the processor 120A to communicate with the authorized entity computer 160 or any other suitable manager of the removable marking element account. For example, the removable marking element application 120K can include information for contacting the authorized entity computer 160, such as a URL, email address, or phone number. The removable marking element application 120K can also include instructions for scanning a machine-readable code associated with the removable marking element, sending the machine-readable code and mobile device 120 identification information to the authorized entity computer 160, receiving funding information and management information from the user 110, authorizing the sending of funding information and management information to the entity computer 160, storing information about one or more removable marking element accounts (e.g., product identifiers), and performing any other suitable account management functions. In some embodiments, the removable marking element application 120K can be provided to the mobile device 120 by the authorized entity computer 160 or any other suitable entity. Additionally, the functionality of the removable token element application 120K may be incorporated into the mobile wallet application.

[0087] Back to Figure 1 The resource provider computer 130 may be associated with a resource provider, which may be an entity that can provide resources such as goods, services, information, and / or access. Examples of resource providers include merchants, access devices, secure data access points, and the like. A merchant may generally be an entity that participates in a transaction and can sell goods or services or provide access to goods or services.

[0088] The resource provider may accept a variety of payment methods (e.g., removable marking elements 115) and may use a variety of tools to conduct different types of transactions. For example, the resource provider may operate a physical store and use access devices 125 for in-person transactions. The resource provider may also sell goods and / or services via a website and accept payments over the Internet.

[0089] Transfer computer 140 may be associated with an acquirer, which may typically be a commercial entity (e.g., a commercial bank) that has a business relationship with a particular merchant or other entity. Some entities may perform the functions of both an issuer and an acquirer. Some embodiments may encompass such a single-entity issuer-acquirer. Transfer computer 140 may be more specifically referred to as an acquirer computer.

[0090] The transaction processing computer 150 may be located between the transmitting computer 140 and the authorization entity computer 160. The transaction processing computer 150 may include data processing subsystems, networks, and operations used to support and deliver authorization services, exception document services, and clearing and settlement services. For example, the transaction processing computer 150 may include a server connected to a network interface (e.g., via an external communication interface) and an information database. The transaction processing computer 150 may represent a transaction processing network. An exemplary transaction processing network may include VisaNet TM Such as VisaNet TM VisaNet's transaction processing network handles credit card transactions, debit card transactions, and other types of commercial transactions. TM Specifically, it includes the VIP system (Visa Integrated Payment System) for processing authorization requests and the BaseII system for performing clearing and settlement services. The transaction processing computer 150 can use any suitable wired or wireless network, including the Internet.

[0091] The transaction processing computer 150, the transmitting computer 140, and the authorization entity computer 160 may execute appropriate routing tables to route authorization request messages and / or authorization response messages using access credentials (eg, payment credentials), merchant identifiers, or other account identifiers.

[0092] The authorization entity computer 160 may be associated with an authorization entity, which may be an entity that authorizes the request. An example of an authorization entity may be an issuer, which may generally refer to a business entity (e.g., a bank) that maintains a user account. The issuer may issue and manage a removable marking element account associated with the removable marking element 115.

[0093] The authorized entity may also be a local service provider (e.g., an event organizer) or an authentication entity (e.g., a security administrator or identity authenticator). For example, the removable tag element 115 may be used as a replacement for a typical payment device or identification card for a particular event (e.g., a concert or sporting event), and the removable tag element 115 may be provided by the event's administrator. Additionally, the removable tag element account may be funded with event-specific funds or used in a closed-loop system. For example, a user 110 may purchase a certain number of ride tickets at a theme park, and the ride tickets may be loaded onto the removable tag element account.

[0094] Figure 7 An example of an authorization entity computer 160 according to some embodiments of the present invention is shown in The authorization entity computer 160 includes a processor 160A, a network interface 160B, a user database 160C, and a computer-readable medium 160D.

[0095] The computer-readable medium 160D may include a transaction processing module 160E, a linking module 160F, a funding module 160G, a management module 160H, and any other suitable software modules. The computer-readable medium 160D may also include code executable by the processor 160A to implement a method comprising: receiving a message from a mobile device comprising a value associated with a second account, a second access credential, and a product identifier associated with a removable marking element adapted to be adhered to the skin, wherein the mobile device obtains the product identifier by obtaining a machine-readable code associated with the removable marking element, and wherein the removable marking element comprises an integrated circuit configured to transmit a first access credential associated with a first account to an access device via a wireless communication channel during a transaction; identifying the first account based on the product identifier; and loading the first account with the value from the second account.

[0096] The account database 160C may contain information associated with one or more accounts. This may include account records for removable marking element accounts and / or typical accounts (e.g., regular credit, debit, or prepaid accounts that may be associated with a typical payment device). Figure 7As shown, account database 160C may include a first account 160X and a second account 160Z. In some embodiments, first account 160X may be a removable marking element account, and second account 160Z may be a separate account used as a source of value (e.g., funds or access credentials) for first account 160X, or may be otherwise associated with first account 160X. For example, second account 160Z may be a pre-existing regular payment account used to fund first account 160X. In some embodiments, first account 160X may initially be empty and have no value until value is loaded from second account 160Z into first account 160X.

[0097] The first account 160X may include first access credentials, a product identifier, a fund amount, an access code, information about an associated mobile device, information about an associated second account 160Z, a transaction history, and / or any other suitable information. The second account 160Z may include second access credentials, a fund amount, an access code, information about an associated mobile device, information about an associated first account 160X, a transaction history, and / or any other suitable information.

[0098] In some embodiments, second account 160Z may not be managed by authorized entity computer 160. For example, second account 160Z may be an external account of a different authorized entity (e.g., a different security administrator or bank). Alternatively, the reverse arrangement may occur (e.g., first account 160X may be an external account of a different authorized entity, and second account 160Z may be managed by authorized entity computer 160).

[0099] The transaction processing module 160E may include code that causes the processor 160A to process a transaction. For example, the transaction processing module 160E may contain logic that causes the processor 160A to analyze the transaction risk and authorize or deny an authorization request message for the transaction. The transaction processing module 160E may be configured to determine whether an account (e.g., a removable token account) has sufficient funds or a suitable access code to conduct the transaction. The transaction processing module 160E may also be configured to debit or credit the removable token account and send a transaction notification to a mobile device associated with the transaction.

[0100] The linking module 160F may include code that causes the processor 160A to establish an association between an account and / or a device. For example, the linking module 160F may contain logic that causes the processor 160A to associate a removable tag element account with a mobile device (e.g., by storing a mobile device identifier in a removable tag element account record in the account database 160C).

[0101] The funding module 160G may include code that causes the processor 160A to provide funds or access codes to the removable tag element account. For example, the funding module 160G may contain logic that causes the processor 160A to receive a funding request (including a funding amount and a payment source (e.g., a pre-existing independent payment account, such as the second account 160Z)), extract funds from the payment source, and credit the funds to the removable tag element account. The funding module 160G may also be configured to load access, security, login, or identity credentials to the removable tag element account.

[0102] The management module 160H may include code that causes the processor 160A to manage the removable tag element account. For example, the management module 160H may contain logic that causes the processor 160A to receive management instructions from a user (e.g., via a mobile device) and apply settings to the removable tag element account. For example, the management module 160H may be configured to set account usage limits, associate a phone number or address with the account, temporarily block or lock the account, and otherwise manage the account.

[0103] Please refer to Figure 8 800 according to an embodiment of the present invention. Reference will also be made to some elements in other figures. In embodiments of the present invention, the steps shown in method 800 may be performed sequentially or in any suitable order. In some embodiments, one or more of the steps may be optional.

[0104] The various messages described below can use any suitable form of communication. In some embodiments, the request or response can be in the form of an electronic message, such as an email, a short message service (SMS) message, a multimedia message service (MMS) message, a hypertext transfer protocol (HTTP) request message, a transmission control protocol (TCP) packet, or a web form submission. The request or response can be directed to any suitable location, such as an email address, a telephone number, an Internet Protocol (IP) address, or a uniform resource locator (URL). In some embodiments, the request or response can include a mix of different message types, such as both an email message and an SMS message.

[0105] The authorized entity computer 860 may establish (and / or activate) one or more removable marking component accounts. The authorized entity computer 860 may provide access credentials and / or product identifiers for each removable marking component account. The authorized entity computer 860 may also associate one or more removable labels with each removable marking component account.

[0106] The authorized entity computer 860 or a separate entity may manufacture the removable tag. Each removable tag element may include an integrated circuit, and each integrated circuit may be configured to include access credentials that identify an associated removable tag element account. In some embodiments, the removable tag element account may initially contain no value but may be associated with the access credentials and a functional removable tag element. For example, each removable tag element account may be configured as an unloaded prepaid account.

[0107] The removable label may be packaged for distribution, and the packaging may include a product identifier for identifying the account of the removable label element. For example, the packaging may include a machine-readable code.

[0108] User 810 may wish to use removable marking element 815. For example, user 810 may obtain removable marking element 815 to use as a payment device, to provide to a child as a payment device, to use as a ticket to an event, to use as a security badge, to use as personal identification, or for any other suitable purpose. In this method description, an example of removable marking element 815 being used as a payment device will be described.

[0109] User 810 can obtain removable marking element 815 from a store, bank, event organizer, or any other suitable service provider. Removable marking element 815 can be in packaging. User 810 can open removable marking element 815 and apply it to their body (e.g., forearm). The packaging can also contain a machine-readable code for accessing and activating a removable marking element account associated with removable marking element 815.

[0110] In step S802, user 810 may operate mobile device 820 to scan, photograph, or otherwise obtain a machine-readable code. For example, mobile device 820 may scan a barcode or RFID chip on a package. User 810 may also activate a removable marking element application on mobile device 820.

[0111] At step S804, the mobile device 820 may display options for activating the removable marking element 815 and / or linking the removable marking element 815 with the mobile device 820. At step S806, the user 810 may initiate the removable marking element 815 activation and / or linking process (e.g., selecting an “activate” or “link” indicator, or scanning a machine-readable code).

[0112] At step S808, mobile device 820 may send a request to authorization entity computer 860 to activate removable marking element 815 and / or link removable marking element 815 with mobile device 820. The request may include information identifying removable marking element 815 and the associated removable marking element account. For example, the request may include information from the scanned machine-readable code (e.g., access credentials or product identifier). The request may also include information about mobile device 820, such as an MSISDN, phone number, email address, or any other suitable contact information.

[0113] At step S810, authorized entity computer 860 may receive the request and identify the removable marking element account based on the information in the request. Authorized entity computer 860 may activate the removable marking element account, making removable marking element 815 available for transactions. Authorized entity computer 860 may also establish an association between the removable marking element account and mobile device 820. For example, authorized entity computer 860 may add mobile device 820 identification information to the removable marking element account record in the removable marking element account database.

[0114] At step S812, the authorization entity computer 860 may send an activation and / or linking response message back to the mobile device 820. The mobile device 820 may notify the user 810 that the account is activated.

[0115] Mobile device 820 may also store information about the linked removable marking element account and / or removable marking element 815. For example, mobile device 820 may store access credentials, product identifiers, images or icons similar to removable marking element 815, and / or any other suitable information. As a result, mobile device 820 may contact authorized entity computer 860 in the future for additional removable marking element account management. Alternatively, user 810 may rescan the barcode in the future to perform additional account management activities.

[0116] At step S814, the mobile device 820 may prompt the user 810 to provide funds to the removable marking element account.For example, the mobile device 820 may provide a display screen with space for entering payment information and an amount.

[0117] At step S816, user 810 may provide information regarding a funding source (e.g., a separate payment account) and an amount to be loaded onto the removable marking element account for use with removable marking element 815. In some embodiments, user 810 may request that the separate payment account be used as a regular funding source for the removable marking element account, or that the removable marking element account be automatically reloaded when it falls below a certain balance.

[0118] At step S818, the mobile device 820 may send a funding request to the authorization entity computer 860. The request may include any suitable data values. For example, the request may include funding information provided by the user 810, account identification information (e.g., a product identifier), a request to purchase a specific amount of tickets or closed-loop currency, and any other suitable information.

[0119] At step S820, the authorized entity computer 860 may transfer funds to the removable marking element account. For example, the authorized entity computer 860 may debit the separate account (e.g., as instructed by the user 810) and credit the removable marking element account. Transferring funds may involve transferring funds from the separate funding account to the removable marking element account. For example, one or more authorization request messages, clearing messages, and settlement messages may be sent between the authorized entity computer 860 and the issuer of the separate funding account to transfer the funds.

[0120] In some embodiments, the authorized entity computer 860 may establish an association between the removable tag element account and the separate account, allowing the removable tag element account to continuously withdraw funds. In some embodiments, the authorized entity computer 860 may identify the removable tag element account based on account identification information (e.g., a product identifier) ​​received in the load request or based on the mobile device 820 that sent the request.

[0121] At step S822, the authorization entity computer 860 may send a funding response to the mobile device 820. The response may indicate that the removable marking element account has been successfully funded. The mobile device 820 may also notify the user 810 that the account has been funded.

[0122] In step S824, the mobile device 820 may prompt the user to provide account settings. For example, the mobile device 820 may present one or more options for account usage and notification to the user 810.

[0123] At step S826, user 810 may specify one or more account settings. For example, user 810 may set usage restrictions for removable tag element 815, such as when removable tag element 815 may be used (e.g., total duration, time of day, day of week, etc.), where removable tag element 815 may be used (e.g., location or merchant type), how removable tag element 815 may be used (e.g., types of items that may be purchased, or spending limits), or any other suitable type of usage control. User 810 may also provide similar parameters for when transaction notifications should be sent (e.g., based on time, location, merchant, item type, transaction amount, etc.).

[0124] At step S828, mobile device 820 may send an account management request to authorization entity computer 860. The request may include account setup information provided by user 810, account identification information (eg, product identifier), and any other suitable information.

[0125] At step S830, the authorization entity computer 860 may update the account settings associated with the removable marking element account. For example, the authorization entity computer 860 sets usage restrictions, notification parameters, and any other appropriate account personalization requested by the user 810. In some embodiments, the authorization entity computer 860 may identify the removable marking element account based on account identification information (e.g., a product identifier) ​​received in the account management request or based on the mobile device 820 that sent the request.

[0126] At step S832, the authorization entity computer 860 may send an account management response to the mobile device 820. The response may indicate that the removable marking element account settings have been successfully updated. The mobile device 820 may also notify the user 810 that the account has been updated.

[0127] In some embodiments, the mobile device 820 may combine one or more of steps S808, S818, and S828 into one step. For example, the mobile device 820 may send a message containing information for activating the account and loading funds.

[0128] The removable marking element account can then be activated, funded, and personalized. As a result, the removable marking element 815 can be ready for use. For example, the user 810 can apply the removable marking element 815 to their body and use it for transactions. The user 810 can present the removable marking element 815 to the access device 825 at the resource provider location.

[0129] At step S834, the removable marking element 815 may provide the access credentials (e.g., PAN) to the access device 825. For example, the access device 825 may be able to communicate with the removable marking element 815 (e.g., via a wireless communication channel such as NFC) or capture an image of the removable marking element 815 (e.g., a steganographic image).

[0130] At step S836, the access device 825 may send the removable marking element account credentials to the resource provider computer 830. The access device 825 may also provide transaction information to the resource provider computer 830, such as information about the purchased goods and / or services, the transaction amount, and any other suitable information.

[0131] At step S838, the resource provider computer 830 may generate a transaction request message (e.g., an authorization request message) for the transaction. The transaction request message may include the transaction amount, access credentials, merchant ID, and / or any other suitable information. In some embodiments, the transaction request message may alternatively be generated by the access device 825.

[0132] The transaction request message can then be transmitted and routed to the authorization entity computer 860 for authorization. For example, at step S840, the resource provider computer 830 sends the transaction request message to the transmitting computer 840. At step S842, the transmitting computer 840 can forward the transaction request message to the transaction processing computer 850. At step S844, the transmitting computer 840 forwards the transaction request message to the transaction processing computer 860.

[0133] At step S846, authorization entity computer 860 may authorize the transaction. For example, authorization entity computer 860 may perform risk processing, identify the removable marking element account based on the transaction request message, determine that the removable marking element account has sufficient funds, determine that the transaction can be authorized, and / or debit the removable marking element account for the transaction amount. Authorization entity computer 860 may then generate a transaction response message indicating that the transaction is authorized.

[0134] The transaction response message may then be transmitted and routed back to the access device 825. For example, in steps S848 to S854, the authorization entity computer 860 may send the transaction response message to the transaction processing computer 850, which may forward the transaction response message to the transmitting computer 840, which may forward the transaction response message to the resource provider computer 830, which may forward the transaction response message to the access device 825.

[0135] The access device 825 may display an indication of successful authorization to the user 810 and / or service personnel. The user 810 may then be allowed to leave with the purchased goods and / or services.

[0136] At step S856, the authorized entity computer 860 may send a transaction notification to the mobile device 820. For example, the notification may include information about the purchased item, the location of the purchase, the remaining funds in the removable tag element account, the expected remaining validity period of the removable tag element (e.g., before it disappears and falls from the body), and / or any other suitable information. The notification and / or mobile device application may also prompt the user 810 to deposit more funds into the removable tag element account (e.g., if the balance is below a threshold).

[0137] At some point in time, a clearing and settlement process may occur between the transmitting computer 840 , the transaction processing computer 850 , and the authorizing entity computer 860 .

[0138] After a certain amount of time, the removable marking element 815 may decay naturally and fall from the user's body, or the user 810 may remove the removable marking element 815. At this time (or at another suitable time, such as a future event), the user 810 may apply a new removable marking element and may repeat the method 800 using the new removable marking element.

[0139] Thus, user 810 can conduct transactions using removable tag element 815. User 810 may not need to carry a separate payment instrument or access card, removable tag element 815 can sit comfortably on the skin rather than in a pocket (e.g., reducing pocket bulk), and removable tag element 815 can be securely attached to the user's body. In addition, user 810 can conveniently activate and top up a removable tag element account (e.g., via a mobile device and a machine-readable code).

[0140] Embodiments of the present invention have many advantages. For example, in embodiments of the present invention, a removable marking element can be used in place of a typical transaction device (e.g., an access card, a payment device, a personal identification card, etc.). This advantageously improves user convenience, device security, and cost-effectiveness because the removable marking element can be less expensive, easier to use, and less likely to be lost than a typical transaction device. Instead of carrying one or more cards or other devices (e.g., in a handbag or pocket), the user simply attaches the removable marking element to their body (e.g., a forearm). For example, the removable marking element can be adhered or otherwise attached to the user's skin. This can also improve ease of use because the user only needs to present their forearm to the scanner to conduct a transaction (e.g., instead of placing a typical transaction device in a wallet and removing it to conduct a transaction). A typical transaction device can be lost or stolen, but a removable marking element is unlikely to be forgotten or stolen because it can be attached to the user's body.

[0141] Additionally, the removable tagging element can advantageously serve as a transaction device for children who typically do not have a typical transaction device or cannot be trusted with a typical transaction device. Parents can apply the removable tagging element to the child's body and manage the removable tagging element account on the child's behalf (e.g., via a mobile device). Parents can also track the child's spending and location via notifications sent to the parent when the child makes a transaction.

[0142] Embodiments of the present invention also advantageously provide a convenient way for users to manage their removable markings. The removable marking element may not have a user interface for account management, but the mobile device can act as an intermediary between the removable marking element and the removable marking element account (e.g., at an authorized entity).

[0143] Embodiments of the present invention also advantageously provide a convenient way to activate and link a removable marking element. A user can scan a machine-readable code with the removable marking element (e.g., printed or attached to the packaging) and then instantly access the removable marking element account (e.g., to activate, provide funding, manage, etc.). Alternatively, the user can enter an alphanumeric code printed on the packaging. In some embodiments, the code can alternatively be mailed or transmitted (e.g., via email or SMS) to the user. Thus, the user can access the removable marking element account even if the account information is not visible on the removable marking element.

[0144] A computer system that can be used to implement any entity or component described herein will now be described. The subsystems in the computer system are interconnected via a system bus. Additional subsystems include a printer, keyboard, fixed disk, and monitor, which can be connected to a display adapter. Peripheral devices and input / output (I / O) devices can be connected to an I / O controller and can be connected to the computer system by any number of means known in the art (e.g., serial ports). For example, a serial port or external interface can be used to connect a computer device to a wide area network such as the Internet, a mouse input device, or a scanner. Interconnection via the system bus allows a central processing unit to communicate with each subsystem and control the execution of instructions from system memory or fixed disk and the exchange of information between subsystems. System memory and / or fixed disk can embody computer-readable media.

[0145] As described above, the services of the present invention may involve the implementation of one or more functions, processes, operations, or method steps. In some embodiments, the functions, processes, operations, or method steps may be implemented by executing an instruction set or software code by a suitably programmed computing device, microprocessor, data processor, or the like. The instruction set or software code may be stored in a memory or other form of data storage element accessible by the computing device, microprocessor, or the like. In other embodiments, the functions, processes, operations, or method steps may be implemented by firmware, a dedicated processor, an integrated circuit, or the like.

[0146] Any software components or functions described in this application can be implemented as software code executed by a processor using any suitable computer language (e.g., Java, C++, or Perl), using, for example, traditional or object-oriented techniques. The software code can be stored as a series of instructions or commands on a computer-readable medium, such as random access memory (RAM), read-only memory (ROM), magnetic media such as a hard drive or floppy disk, or optical media such as a CD-ROM. Any such computer-readable medium can reside on or within a single computing device and can be present on or within different computing devices within a system or network.

[0147] While certain exemplary embodiments have been described in detail and shown in the drawings, it is to be understood that such embodiments are merely illustrative of the invention and not restrictive, and that the invention is not limited to the specific arrangements and constructions shown and described, since various other modifications may occur to those skilled in the art.

[0148] As used herein, the use of "a," "an," or "the" is intended to mean "at least one" unless clearly indicated to the contrary.

Claims

1. A method comprising: obtaining, by the mobile device, a non-transaction product identifier from a machine-readable code associated with a removable marking element adapted to be adhered to the skin, wherein the removable marking element comprises an integrated circuit configured to transmit, during a transaction, a first transaction access credential associated with the first account to an access device via a wireless communication channel; as well as A message including the non-transaction product identifier and a second transaction access credential associated with a second account is sent by the mobile device to a server computer, wherein the server computer identifies the first account based on the non-transaction product identifier, and wherein the server computer loads the first account with a value associated with the second account based on the second transaction access credential.

2. The method of claim 1 , wherein a user applies the removable marking element to the user's body and presents the removable marking element to the access device for use in the transaction, and wherein the access device obtains the first transaction access credential from the removable marking element and sends the first transaction access credential to an authorization entity computer for authorizing the transaction.

3. A method according to claim 2, wherein the value represents a link to the second account, and wherein the authorization entity computer identifies the second account based on the first transaction access credential and the link to the second account after receiving the first transaction access credential from the access device, and uses the second account to authorize the transaction. 4 . The method according to claim 3 , wherein the first transaction access credential is a first 16-digit payment account number, the second transaction access credential is a second 16-digit payment account number, and the second account is a debit account, a credit account, or a prepaid account. The method according to claim 3 , wherein the authorization entity computer is the server computer.

6. A method according to claim 2, wherein the value represents a security code for accessing a location, and wherein the authorization entity computer identifies the first account based on the first transaction access credential after receiving the first transaction access credential from the access device and uses the security code to authorize the transaction.

7. The method of claim 2, wherein the value represents a monetary amount, and wherein the authorization entity computer identifies the first account based on the first transaction access credential after receiving the first transaction access credential from the access device and authorizes the transaction using the monetary amount.

8. The method of claim 1, wherein the machine-readable code is a barcode printed on packaging associated with the removable marking element, and wherein obtaining the non-transactional product identifier comprises scanning the barcode.

9. The method of claim 1 , further comprising: receiving, by the mobile device, from a user, restrictions on use of the first account, the restrictions comprising at least one of: a spending limit on the first account, a temporary suspension of the first account, and a specific time during which the first account can be used for the transaction; as well as A second message including the non-transaction product identifier and the restriction is sent by the mobile device to the server computer, wherein the server computer identifies the first account based on the non-transaction product identifier, and wherein the server computer updates the first account to include the restriction.

10. The method according to claim 1, comprising: displaying, by the mobile device, an option for linking the removable marking element with the mobile device; receiving user input from the mobile device to initiate a linking process; sending, by the mobile device, a request to the server computer to associate the removable marking element with the mobile device, the request including the non-transaction product identifier; as well as A response message is received by the mobile device from the server computer indicating that an association between the removable marking element and the mobile device has been created.

11. A mobile device comprising: processor; as well as A computer-readable medium comprising code executable by the processor for implementing the method according to any one of claims 1 to 10.

12. A method comprising: receiving, by a server computer, from a mobile device, a message including a non-transactional product identifier associated with a first account and also including a second transactional access credential associated with a second account, wherein the non-transactional product identifier is associated with a removable marking element adapted to be adhered to the skin, and wherein the removable marking element includes an integrated circuit configured to transmit the first transactional access credential associated with the first account to an access device over a wireless communication channel during a transaction; identifying, by the server computer, the first account based on the non-transaction product identifier; as well as The first account is loaded with a value associated with the second account based on the second transaction access credential by the server computer.

13. The method of claim 12 , wherein a user applies the removable marking element to the user's body and presents the removable marking element to the access device for the transaction, the access device obtaining the first transaction access credential from the removable marking element, and further comprising: receiving, by the server computer, from the access device, a transaction request message including the first transaction access credential; authorizing, by the server computer, the transaction based on the first transaction access credential; as well as A transaction response message indicating that the transaction is authorized is sent by the server computer to the access device.

14. The method of claim 13, wherein the value represents a monetary amount or a link to the second account, and wherein authorizing the transaction comprises: identifying the first account based on the first transaction access credential; as well as The transaction is authorized using the monetary amount or the link to the second account.

15. A server computer comprising: processor; as well as A computer-readable medium comprising code executable by the processor for implementing the method according to any one of claims 12 to 14.

16. A method comprising: affixed to a body of a user via a removable marking element, wherein the removable marking element is associated with a non-transaction product identifier, wherein a server computer receives a message including the non-transaction product identifier associated with a first account and also including a second transaction access credential associated with a second account, wherein the server computer identifies the first account based on the non-transaction product identifier, and the server computer causes the first account to be loaded with a value associated with the second account based on the second transaction access credential; as well as The integrated circuit of the removable marking element transmits a first transaction access credential associated with the first account to an access device via a wireless communication channel during a transaction, wherein the access device transmits the first transaction access credential to an authorization entity computer for authorizing the transaction.

17. The method of claim 16, wherein the removable marking element comprises a laminate and the integrated circuit, the laminate comprising an adhesive and an image, and wherein the integrated circuit is attached to or embedded within the laminate.

18. The method of claim 16, wherein the removable marking element comprises the integrated circuit and a temporary tattoo or sticker, wherein the integrated circuit is attached to or embedded within the temporary tattoo or sticker.

19. A method according to claim 16, wherein the value represents a monetary amount or a link to the second account, and wherein the authorization entity computer identifies the first account based on the first transaction access credential after receiving the first transaction access credential from the access device, and uses the monetary amount or the link to the second account to authorize the transaction.

20. The method of claim 19, wherein the first transaction access credential is a first 16-digit payment account number, the second transaction access credential is a second 16-digit payment account number, and the second account is a debit account, a credit account, or a prepaid account.

Images