Patent Publication Number: US-2019180269-A1

Title: Systems, methods and devices to facilitate secure purchases of cryptocurrencies

Description:
CROSS-REFERENCE 
     This application is a continuation in part of application Ser. No. 15/711,312 filed Sep. 21, 2017 and entitled, “Systems, Methods and Devices to Facilitate Secure Purchases of Cryptocurrencies”, which is incorporated herein by reference. 
    
    
     FIELD 
     This disclosure relates to the production, distribution, and use of tamper resistant pre-paid cards to purchase cryptocurrencies and more particularly to systems, methods and devices to facilitate secure purchases of cryptocurrencies. 
     BACKGROUND 
     There are various known manners to provide cryptocurrencies for sale to individuals and other desiring to purchase cryptocurrency. One such manner is to provide an Automated Teller Machine (ATM) or ATM-like machine that sells and may buy a cryptocurrency such as bitcoin™ in exchange for an amount of fiat currency. These machines are expensive to buy and require a fair bit of maintenance, manual removal of cash, connection with an exchange, and many other ongoing items. In short, it is an expensive business model to scale ATMs to service more customers in more locations. 
     Another known manner is to provide a purchaser (e.g. in exchange for fiat currency) with a prepaid printed card or ticket having a code that is redeemed via an electronic interface such as to a cryptocurrency wallet to obtain the cryptocurrency. Known prepaid printed cards or tickets may be insecure. They are not verifiable by purchasers or consumers prior to purchasing. 
     SUMMARY 
     There is provided a physical card device and system that allows purchasers to buy one or more different kinds of cryptocurrencies through a digital sale system. Cards are printed and packaged using a printer system (e.g. substrate feeder, printer, opaque covering station, conveyor belt, optical verification unit(s) and packaging station along with associated software) that ensures that cards are manufactured properly and securely. The cards include a redemption code in a tamper resistant/tamper evident manner as well as a verification code. The cards are distributed to retailers to sell to purchasers, similar to gift cards, for redemption via an online store or mobile application (app). Retailers activate the cards, collect cash or other payment (e.g. credit, debit, gift card redemption, etc.) and dispense the cards, similar to lottery tickets or other cash-like products. The redemption process is provided by an electronic interface (e.g. software system) that provides access to buy a cryptocurrency and preferably to buy many different kinds of cryptocurrencies using a respective redemption code applied to each card. The verification code may be used to verify the authenticity and redeemability of the card prior to purchase. 
     There is disclosed a redemption device carrying one or more codes, the device comprising: a substrate having a face; a redemption code applied to a first portion of the face of the substrate; a verification code applied to a second portion of the face or another face of the substrate; and an opaque covering applied to the first portion to hide the redemption code leaving the verification coded visible, the covering applied in a manner such that a removal reveals the redemption code. 
     There is disclosed a process to produce a redemption device carrying one or more codes, the process comprising: providing a substrate having a face; applying a redemption code to a first portion of the face of the substrate; applying a verification code to a second portion of the face or another face of the substrate; and applying an opaque covering to the first portion to hide the redemption code leaving the verification coded visible, the covering applied in a manner such that a removal reveals the redemption code. 
     There is disclosed a production system for a redemption device carrying respective unique verification and redemption codes, the production system comprising: a code application station to apply the respective unique verification and redemption codes to respective redemption devices, the code application station receiving the codes from a computing device coupled to a data store storing the respective unique verification and redemption codes in association in respective pairs, the pairs associated with a respective activation status; wherein the code application station is configured to: receive one pair of the respective unique verification and redemption codes; apply a unique redemption code of the one pair to the first portion of the substrate; and, apply the unique verification code of the one pair to a second portion of the face or another face of the substrate; and an opaque covering station configured to receive the substrate and apply an opaque covering to the first portion to hide the unique redemption code leaving the unique verification code visible, the covering applied in a manner such that a removal reveals the unique redemption code. 
     There is disclosed a redemption device activation system to facilitate fraud and tamper detection, the system having a processor, a communication subsystem and a memory each in communication with the processor, the memory storing instructions which, when executed by the processor, configure the redemption device activation system to: communicate with a data store storing unique redemption codes and unique verification codes stored in association in respective pairs, the pairs of codes applied to respective redemption devices, where the unique redemption codes are not visible but revealable and the verification codes are visible and wherein at least some of which redemption devices are distributed for delivery to users through one or more channels; receive via the communication subsystem an activation request for one or more of the respective redemption devices; and activate the one or more of the respective redemption devices by updating a respective activation status associated with each of the respective unique verification codes, the status updated to indicate the respective redemption device is activated with redemption code ready for use. 
     There is disclosed a redemption device verification system to facilitate fraud or tampering detection having a processor, a communication subsystem and a memory each in communication with the processor, the memory storing instructions, which when executed by the processor, configure the redemption device verification system to: communicate with a data store storing unique redemption codes and unique verification codes stored in association in respective pairs, wherein the pairs of codes are applied to respective redemption devices where the respective verification codes are visible and the respective redemption codes are not visible on each of the respective redemption devices; wherein at least some of the respective redemption devices are distributed for delivery to users through one or more channels; and wherein the data store stores a respective activation status with each of the pairs of codes; receive via the communication subsystem a verification request for one of the respective redemption devices; determine the respective activation status from the data store; provide a reply that is responsive to the activation status. 
     There is disclosed a redemption system to redeem a redemption device, the redemption system having a processor, a communication subsystem and a memory each in communication with the processor, the memory storing instructions which, when executed by the processor, configure the redemption system to: communicate with a data store storing unique redemption codes and unique verification codes stored in association in respective pairs, wherein the pairs of codes are applied to respective redemption devices where the respective verification codes are visible and the respective redemption codes are not visible but revealable on each of the respective redemption devices; wherein at least some of the respective redemption devices are distributed for delivery to users through one or more channels; and wherein the data store stores a respective activation status and prepaid amount with each of the pairs of codes indicating whether or not the respective redemption device is activated with redemption code ready to use; receive via the communication subsystem a redemption request for one of the respective redemption devices including a respective redemption code; determine the respective activation status from the data store; authorize the redemption using the prepaid amount at activation status and provide a reply in accordance with the redemption; if the redemption is authorized, set the respective activation status accordingly. 
     These and other aspects will be apparent including computer program products which store instructions in a non-transient manner (e.g. in a storage device) which when executed by a computing device configure the device to perform operations as described herein. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIGS. 1A-1C  are illustrations of an example redemption device (e.g. prepaid card or ticket), in accordance with an embodiment. 
         FIG. 2  is a block diagram of a production, distribution and redemption system for a redemption device, in accordance with an embodiment. 
         FIG. 3  is a block diagram of a redemption device production system in accordance with an embodiment. 
         FIG. 4  is a flowchart of a redemption device production process, in accordance with an embodiment. 
         FIGS. 5A and 5B  are flowcharts of respective redemption device activation processes, showing operations of an activation system or systems in accordance with respective embodiments. 
         FIG. 6  is a flowchart of a redemption device verification process showing operations of a verification system in accordance with an embodiment. 
         FIG. 7  is a flowchart of a redemption process showing activities of redemption system in accordance with an embodiment. 
     
    
    
     While references to “an embodiment” are used herein, nothing should be implied or understood that features of one embodiment cannot be used or combined with features of another embodiment unless otherwise stated. The various systems, methods and devices shown and described herein may be used together unless otherwise stated. 
     DETAILED DESCRIPTION 
       FIGS. 1A-1C  are illustrations of an example redemption device  100 , in accordance with an embodiment.  FIG. 1A  shows a first face  100 A while  FIG. 1B  and  FIG. 1C  show an opposite face  100 B.  FIG. 1C  has a plastic film applied to or over a substrate  103  of device  100  as described further to obscure certain information.  FIG. 1A  comprises a gift-card like (pre-paid card) device, typically a substrate of a plastic material (though other substrate materials may be used). Polyvinylchloride (PVC) or other plastic may be used. 
     Face  100 A shows various information in various regions such as a brand logo  102 , a brand name  104  and a fiat currency denomination and amount  106  where NN is a place holder for a number such as  10 ,  20 ,  50 ,  100  etc. Other information and indicia may be displayed as may be desired. On face  100 B there is shown various information, typically codes, such as a visible card number  108 , secret card number  110  and SKU  112 . Other information (not shown) may be displayed on face  100 B such as contact information, contractual information, etc. 
     The information and indicia etc. may be printed on the card stock (substrate) or applied by other means. Repeatable information that appears on all devices  100  may be pre-printed. Information on face  100 A and some information on face  100 B is the same for all similar denomination cards and pre-printed stock stored for production runs to make devices  100  for distribution as described. This pre-printed stock may be obtained from a third party provider and the information unique to each card applied in a secure production environment. 
       FIG. 1C  shows a plastic film  114  applied over face  100 B. Film  114  covers secret card number  110  and provides a window  116  exposing visible card number  108  and SKU  112 . Other information may also be exposed but it is important that the secret card number  110  be hidden when the device  100  is distributed as further described. It is also preferably that this is hidden shortly after it is applied so that even when stored before distribution it is not visible. While if  FIG. 1C  the film is applied on face  100 B such as using an adhesive backed film, it may be applied over face  100 B using shrink wrapping techniques, etc. 
     Visible card number  108  is a unique verification code applied to a first portion of the face  100 B of the substrate. Secret card number  110  is a unique redemption code applied to a second portion of the face  100 B. The redemption code could be on another face of the substrate and the film applied to that face. The film  114  is an opaque covering applied to the first portion to hide the redemption code leaving the verification coded visible. Preferably, the covering is defined or applied in a manner such that a removal reveals the redemption code but can&#39;t be replaced exactly as it was. That is, replacement of the same film after its removal is detectable. For example, the film may stretch if removed (picked and pulled off in whole or in part) so that replacement is detectable to the eye or touch or both. The covering may be adhesively applied or applied in other ways (e.g. heat shrink). 
     The substrate (through one or more of size, shape, and substrate material configuration, etc.) may define a card or other product such as a ticket. 
     One or both of the redemption code and verification code may comprise one of: a code comprising characters or symbols of a language, e.g. including numeric characters and a machine-readable optical code comprising a 1D or 2D barcode. Other codes may be used (e.g. other image encoded data, etc.) In some examples, the redemption code may also be coded in magnetic form. 
     The redemption code and verification code are a pair of codes. They are stored in a data store in association with one another and in association with an activation status such that the verification code is usable to look-up the activation status. They are also stored in association with a respective fiat currency amount  106  as printed on the device  100 . In accordance with one example, which is preferred, the redemption code is a one-time use code to fully redeem the fiat currency amount of the device. When the redemption code is used the activation status is settable in the data store to indicate the redemption code is no longer usable. In one example, the activation status may comprises one of three states: not activated, activated with redemption code ready for use and activated with redemption code used. In another example, activation is a two-step process such that the states may comprise: not activated; first activation state (e.g. box-activated) but individual redemption code not ready for use; second activation state with redemption code ready for use; and activated with redemption code used. In another example (which may be combined with other examples), the redemption code may be used more than once to redeem up to the total prepaid fiat currency amount using partial amounts. The amount used with each redemption may reduce the available amount. An additional activation status may be used (e.g. stored) such as activated with partial amount remaining. 
     The redemption code may be stored in a data store in association with an activation status such that when the redemption code is provided to make a purchase of an amount of cryptocurrency, the activation status is determinable from the database and, responsive to the status (e.g. if the status is activated with redemption code ready for use or with partial amount remaining), a transfer of the cryptocurrency is authorizable to a purchaser. The activation status is settable to indicate the redemption code is used or to indicate that a partial amount remains. 
     The SKU is assistive for merchant use in a distribution chain, identifying a type of redemption device for example for use in inventory/POS systems. 
       FIG. 2  is a block diagram of a production, distribution/activation and redemption system  200  for a redemption device  100 , in accordance with an embodiment. There are three major phases for the system  200 : making redemption devices, getting redemption devices into the hands of customers, and finally the redemption by the customer of the redemption devices (e.g. for cryptocurrency). There is shown a computer system  202  comprising one or more component (computer) systems (e.g. as software or separate computer systems) such as redemption production system  204 , distribution/activation system  206  and redemption system  208 . Computer system  202  is coupled to data store  210  (e.g. a relational database). Computer system  202  is also coupled to redemption device production equipment  212  and product inventory/shipping system  214 . A retailer activation device  216  and a redeeming user device  218  are coupled to computer system  202  via a network  220  such as the internet represented. Though only one of each devices  216  and  218  are illustrated it is understood that a plurality of each such devices may be coupled to system  202  or respective retailers and redemption device recipients who wish to redeem a redemption device  100 . Also shown are a plurality (1, 2, 3 . . . M) of cryptocurrency exchanges (e.g. represented as cryptocurrency exchange # 1   230  and cryptocurrency exchange #M  232 ) coupled via network  220  such as to redemption system  208 . The network-related couplings may be wired or wireless and via public, private of a combination of public and private networks. It is understood that the couplings for devices  216  and  218  may be made when needed and are not necessarily permanently or long term coupled to system  202 . 
     Computing device  202 , data store  210 , production equipment  212  and product inventory/shipping system  214  (collectively issuing entity system  222 ) may be managed by a redemption device issuing entity. Issuing entity system  222  is usually managed in a secure environment (physically and electronically), though not necessarily in a single location. 
     Though not shown in detail, any of the individual components  204 - 214  of issuing entity system  222  may be configured as servers or other computing devices with communication capabilities configured to provide the features and functions described herein. As is well-known, such computing devices comprise one or more processing units, one or more memory or storage devices coupled thereto storing instructions (usually in the form of software (e.g. an operating system, applications, utilities, etc.), which when executed by the one or more processing units configure the respective computing devices to perform operations (e.g. a method or process). The computing devices may have input, output and/or I/O devices coupled thereto such as pointer devices, keyboards, microphones, speakers, display screens, gesture based I/O devices. Often such systems have one or more communication systems (e.g. buses, antennae, etc.) for internal and external communications. A computing device of the production equipment  212  may interface with production printers, optical verifiers, conveyors and the like. 
     Retailer activation device  216  and redeeming user device  218  are also computing systems, with similar components as described, albeit different instructions. Retailer activation device  216  may be a POS terminal at a point of sale coupled to a retailer server or other device (which may couple to system  202 ). It may be a personal device such as a laptop, tablet, personal computer or smartphone. Redeeming user device  218  may be a personal device as well. Retailer activation device  216  is managed by a retailer to activate new redemption devices  100  for providing (e.g. selling) to purchasers. Redeeming user devices (e.g.  218 ) are managed by those who wish to redeem a redemption device  100  or verify that such a redemption device  100  is valid/unused. This may be a purchaser or other person who receives a device  100  such as via a gift or resale or a person who wishes to verify device  100 , whether before or after a purchase or other receiving of the redemption device  100 . Cryptocurrency exchanges  230  and  232  are typically one or more server devices providing services to buy and sell cryptocurrency to others. Some cryptocurrency exchanges may offer a single type of cryptocurrency while others may offer more than one type. Exchanges may be made for fiat currency. Redemption system  208  may facilitate providing cryptocurrency to a redeeming user device (e.g. a wallet thereof or coupled thereto (not shown) from one or more of the cryptocurrency exchanges  230 ,  232  using a redemption device as further described). 
     Redemption device production system  204  interfaces with production equipment  212  to produce redemption devices  100 . Distribution/activation system  206  interfaces with product inventory/shipping system  214 , for example to manage distribution to retailers. It also interfaces with retailer activation devices  216  to activate new devices  100  prior to a purchase/sale by the retailers. Redemption system  208  may interface with redeeming user devices (e.g.  218 ) to control redemption. It may also interface with a redeeming user device  218  to verify that a device  100  is valid and unused. 
     Though not shown, any of the components of issuing entity system  222  may be configured as web servers or cloud servers to provide services such as to retailers and verifiers/redeemers. Other interfaces may be provided as well such as for (native) applications executing on respective devices  216  and  218  and communicating for the respective activation and redemption/verification services/functions. 
     Though shown as distinct components or systems within issuing entity system  222 , one computing device may provide more than one function or service of such systems. Similarly the functions or features of any one system as described may be configured as more than one computing device. Bright line distinctions may not apply. 
     It will be apparent that there are three major phases for the system  200 : making redemption devices  100 , distributing redemption devices  100  into the hands of customers through retailers, including activating the redemption devices  100 , and finally the redemption by the customer or other recipient (e.g. for cryptocurrency). 
       FIG. 3  is a block diagram of a production system  300  for redemption device comprising components of system  222 , namely redemption device production system  204  and data store  210  as well as production equipment  212 . Production equipment  212  is shown in more detail but it will be appreciated that for purposes of illustrative clarity it is simplified. For example, no conveyance system is shown. No separate computer control or other controls are shown. In the example, production equipment  212  comprises a substrate feeder  302  to feed stock (pre-printed plastic cards as described) to a code application station  304  for applying the verification and redemption codes. The code application station  304  may also apply SKU codes. Code application station  304  may comprise a printer. It may comprise other equipment for applying such codes. 
     In the present example, code application station  304  receives at least the verification and redemption codes for each respective device  100  that it produces from redemption device production system  204  (whether directly (as shown) or indirectly such as via a computing device controlling some or all or production equipment  212  (not shown). Prior to production, data store  210  stores the verification and redemption codes in association with one another, e.g. so as to permit the lookup of the other code using one of the codes. It preferably also stores the SKU in association with at least one of the verification and redemption codes. The SKU or other data is stored in store  210  to identify the fiat currency value  106  of the redemption device  100 . 
     Following code application station  304 , a redemption device bearing codes is provided (e.g. via a conveyancing system) to an optical verification unit  306  comprising one or more imaging devices (e.g. camera(s)), which optically read (e.g. optical character recognition (OCR)) and verify at least the verification and redemption codes for quality assurance purposes. The codes may be communicated to unit  306  from redemption device production system  204  (as shown) or from station  304  (not shown) or in another manner such as described above. It may be that station  306  is coupled to an imaging device and station  304  performs such a function. If a particular redemption device  100  fails verification it is rejected and may be conveyed to a collection of rejected devices  314 . These may be recycled. 
     If verified a device  100  is passed to opaque covering station  308  where the opaque covering is applied. In some examples, a plastic opaque film having a transparent window is applied such as using adhesive or by shrink wrap. In some examples only a portion of the device  100  bearing the redemption code is covered. In some examples other means (e.g. scratch coating) is applied to cover the redemption code. The film may be on a roll that is feed (not shown) to station  308 . The film may be preprinted with information, brand, etc. 
     In the present example, a second optical verification unit verifies that the covering does not obscure at least the verification code. It may also verify that the redemption code is covered. Opaque covering station  308  may be coupled to an imaging device to perform this function. Verification unit  310  may receive the applicable code or codes from production system  204  as shown or from any of the components of equipment  212  as described. Rejected devices  100  are gathered at  314  as described. 
     Devices with films that are verified are passed to a packaging station  312 . There the devices may be packaged (e.g. to boxes) for warehousing prior to delivery/shipping to retailers. Upon packaging the data store may be updated to store an initial status (e.g. not activated) for a device. The status may be updated after final verification and before packaging. 
     In some examples, boxes are assigned a unique box (serial) number to assist with later activation. The box number may also be used for inventory and shipping purposes. Each device  100  in a box is associated with the box number in data store  210 . The box number may be used to look up the respective devices (e.g. linked via a verification code or other means) to update the status (e.g. to activated but not used) at the time of activation. In this way a retailer may quickly activate a plurality of devices  100 . The boxes may hold devices  100  having the same or more than one different fiat currency amount  106 . 
       FIG. 3  thus illustrates a production system for a redemption device carrying respective unique verification and redemption codes. The production system may comprise a code application station to apply the respective unique verification and redemption codes to respective redemption devices, the code application station receiving the codes from (a computing device coupled to) a data store storing the respective unique verification and redemption codes in association in respective pairs, the pairs associated with a respective activation status. The code application station is configured to: receive one pair of the respective unique verification and redemption codes; apply a unique redemption code of the one pair to the first portion of the substrate; and, apply the unique verification code of the one pair to a second portion of the face or another face of the substrate. The production system comprises an opaque covering station configured to receive the substrate and apply an opaque covering to the first portion to hide the unique redemption code leaving the unique verification code visible, the covering applied in a manner such that a removal reveals the unique redemption code. When the device is produced and verified, the data store is configured to store the activation status set to not activated. 
       FIG. 4  is a flowchart of a redemption device production process  400 , in accordance with an embodiment. There is illustrated operations of a process to produce a redemption device carrying one or more codes. At  402  operations provide a substrate having a face. At  404 , operations apply a redemption code to a first portion of the face of the substrate and then at  406 , apply a verification code to a second portion of the face or another face of the substrate. At  408  there is applied an opaque covering to the first portion to hide the redemption code leaving the verification coded visible, the covering applied in a manner such that a removal reveals the redemption code. 
     As noted the substrate may define a card or ticket. The covering may be adhesively applied or applied by heat shrink or other means. In some examples, the covering is deformed by removal or partial removal such that a re-application of the opaque film to the substrate is detectable. 
     In some examples, the redemption code and verification code are applied by printing. 
     A one or both of the redemption code and verification code may comprise one of: a code comprising characters or symbols of a language, including numeric characters; and a machine-readable optical code comprising a 1D or 2D barcode. 
     The process may comprise storing in a data store the redemption code and verification code in association with one another and providing the data store to make the codes available for production purposes. The data store may be provided to verify at least one of the redemption code and verification code or an activation status. 
     The process may comprise using a camera and the data store to verify the redemption code and verification code are properly applied to the substrate. 
     The opaque covering may comprising an opaque portion of a film where the film also has a transparent portion. The process may comprise applying the redemption code and the verification code in a manner such that when the film is applied the redemption code is covered by the opaque portion and the verification code is covered by the transparent portion. The process may comprise using the data store and one of the camera or a second camera to verify the transparent portion is properly applied over the verification code. 
     The redemption code and verification code may also be stored in association with an activation status such that the verification code is usable to look-up the activation status and when the redemption code is used the activation status is settable to indicate the redemption code is no longer usable or that only a partial amount remains. When all of the amount is spent, the status may be set to the redemption code is no longer usable. The activation status may comprise one of the status as described elsewhere herein. 
     The process may comprise: producing a plurality of redemption devices each of the devices having respective unique redemption codes and unique verification codes stored in respective association in the data store; and each having respective activation statuses associated with the respective verification codes, the statuses set to not activated; grouping a set of the plurality of redemption devices for shipping together; assigning a unique grouping code to the set and storing the grouping code in the data store in association with the respective verification numbers from the set, the grouping code usable to set the respective activation statuses of the set to activated with redemption code ready for use. 
     The process may comprise storing the redemption code in a data store in association with an activation status such that when the redemption code is provided to make a purchase of an amount of cryptocurrency, the activation status is determinable from the database and, if activated with redemption code ready for use, a transfer of the cryptocurrency is authorizable to a purchaser and the activation status is settable to indicate the redemption code is used or that a partial amount is remaining as the case may be. 
     Though not shown, product inventory/shipping system  214  may interface to distribution/activation system  206  to update data store  210  when a box of devices  100  is or individual devices  100  are shipped to a particular retailer such as from a warehouse. The retailer may be associated with the box or individual devices such as for activation purposes or for delivery tracking, inventory management, etc. Delivery may be initiated on demand of a retailer. Delivery process may be controlled by a software program that manages the automatic shipments when inventory levels run low at a retail location. 
     A retailer may receive a box of cards or several boxes in a delivery. The retailer may activate each box of cards using an electronic interface via a computing device or other communication means (e.g. retailer activation device  216 ). This electronic interface may comprise a specialized application interface, a website interface, text message interface, a phone IVR system interface, an automated process linked through APIs, etc.) and device  216  may be configured accordingly. 
     Various methods of activation are described. In a first example, a single step activation process is provided. In one step, activating the box of cards activates every card within the box. As an alternative, individual cards could be activated using the verification code (Visible Card Number  108 ) on the card. Thus one or more cards may be activated via the single step process. Activating a box at a time may be much more convenient for retailers. The single step process is described further with reference to  FIG. 5A . 
     In a second example, activation may comprise a two-step activation process. A first step of the two-step activation process activates a box of redemption devices (e.g. cards) to a first or initial activation status. A second step of the two-step activation process activates to a second or final activation status an individual redemption device from a respective box that has been activated to the first activation status. The second or final status indicates the respective redemption device (e.g. a specific card  100  and more particularly the code therefor) is activated with redemption code ready for use. The second step may be performed in association with a sale of a specific individual card to a customer (e.g. when transferring). The two-step process is described further with reference to  FIG. 5B . The second request may be associated with the verification code of the individual redemption device to request its full activation to redemption code ready for use. 
       FIG. 5A  is a flowchart of a single step redemption device activation process, showing activities of distribution/activation system  206  or another activation system in accordance with an embodiment. Redemption device activation system  206  and the method described facilitates fraud and tamper detection. System  206  may comprise a processor, a communication subsystem and a memory each in communication with the processor. The memory stores instructions which, when executed by the processor, configure the system  206  to perform operations  500 A as shown in  FIG. 5A . At  502 A the system  206  is configured to communicate with a data store ( 210 ) storing unique redemption codes and unique verification codes stored in association in respective pairs, the pairs of codes applied to respective redemption devices, where the unique redemption codes are not visible but revealable and the verification codes are visible and wherein at least some of which redemption devices are distributed for delivery to users through one or more channels. At  504 A, operations receive via the communication subsystem an activation request for one or more of the respective redemption devices. At  506 A operations activate the one or more of the respective redemption devices by updating a respective activation status associated with each of the respective unique verification codes, the status updated to indicate the respective redemption device is activated with redemption code ready for use. 
     The unique redemption codes and the respective activation statuses are stored in association such that when a particular redemption code is provided to make a transfer of an amount of cryptocurrency, the activation status is determinable from the data store and, responsive to the status, a transfer of the cryptocurrency is authorizable to a purchaser of the cryptocurrency. As noted the activation status is settable to indicate the redemption code is used or a partial amount remains available if less than the available amount was spent. The data store stores a prepaid currency amount with each pair of codes, the prepaid currency amount being used to determine the amount of cryptocurrency to purchase in response to a redemption of the redemption device. In some examples, less than the available amount may be redeemed in a redemption transaction, leaving a partial amount remaining such as for another redemption transaction. 
     Operations may be configured to evaluate the respective activation status for a redemption device before activating and operate to only activate by updating the respective activation status if that status is not activated. Operations may be configured to evaluate a respective delivery status for a redemption device and operate to only activate by updating the respective activation status if that delivery status is delivered. A delivery status may be stored in the data store. 
     The data store may store a unique grouping code (e.g. box serial number) in association with a set of respective redemption devices. The grouping code may be stored in the data store in association with the respective verification numbers from the set, the grouping code usable to set the respective activation statuses of the set to activated with redemption code ready for use. An activation request received at system  206  (e.g. from device  216 ) may comprises the grouping code to activate all of the set. 
     Operations may comprise authenticating that the activation request is received from an authenticated user (e.g. retailer) before activating. 
     An activation confirmation may be provided (e. communicated to device  216  for a retailer). A retailer may authenticate with a user name and password or other means (e.g. voice recognition, two factor authentication, etc.). 
     It is understood that any status stored in data store  210  as described herein may be coded and need not be the text strings for each status referenced herein. Any reference to a status includes its equivalent. 
       FIG. 5B  is a flowchart of a two-step redemption device activation process  500 B, showing activities of distribution/activation system  206  or another activation system in accordance with an embodiment. Operations  500 B are similar in many respects to operations  500 A. For example at step  502 B, the system  206  is configured to communicate with a data store ( 210 ) storing unique redemption codes and unique verification codes stored in association in respective pairs, the pairs of codes applied to respective redemption devices, where the unique redemption codes are not visible but revealable and the verification codes are visible and wherein at least some of which redemption devices are distributed for delivery to users through one or more channels. In addition, sets of respective redemptions devices are grouped (e.g. such as per box) and are associated with respective unique grouping codes for use to activate respective sets in accordance with a two-step process. There is assigned and stored to the data store a unique grouping code for a set of respective redemption devices (e.g. two or more such as may be boxed together). Effectively the unique grouping code is stored in the data store in association with the respective verification numbers from the set. The grouping code usable (e.g. in the two step process) to set the respective activation statuses of the set to activated with redemption code ready for use. 
     At  504 B, operations receive via the communication subsystem a first step activation request for one or more of the respective redemption devices, typically in association with a box of redemption devices. The request is typically associated with a grouping code for the box. At  506 B, operations activate the redemption devices associated with the box to the first activation status (which may be a box activated status) but individual cards are not yet ready for use. As is understood, activating to the first activation state may comprise storing an applicable status identifier in a data store associated with each of the redemption devices from the box. Though not shown, an activation status check is typically performed to confirm the box was not previously activated and operations  506 A performed accordingly, etc. 
     At  508 B operations receive via the communication subsystem a second activation request in respect of an individual respective redemption device. It is understood that a second activation request may act as a request for more than one individual respective redemption device by providing respective codes for each such device. At  510 B, a status check is performed such as by looking up the activation status of the individual respective redemption device in the data store to determine that it is in the first activation state (e.g. a box activation state). If yes, the activation status is updated (at  512 B). The respective activation status associated with the respective unique verification code is updated to indicate the respective redemption device is activated with redemption code ready for use. If not in the first activated state (box activated), via no branch to  514 B, the activation status is not updated to a ready to use state. An error may be reported. 
     Though not shown in operations  500 B an opportunity may be provided to re-enter data to correct any data entry error such as from a retailer activation device, etc. Scanning a 2D or 3D code may be used to reduce data entry issues at a POS terminal, etc. Operations may be configured to shut down further use of the retailer activation device, for example, refusing further requests (e.g.  502 B,  508 B, etc.) from such a device and/or shut down use of the respective redemption device (e.g. such as by setting the activation status to an applicable status). Shutting down use of a respective redemption device or retailer activation device may be a last resort type measure. If the respective redemption device&#39;s status is already activated with a redemption code ready to use, a warning message may be provided indicating same. If the status reflects an earlier activation state (e.g. a pre-box activated status indicating it is ready for a first activation) a warning message may be provided to perform box activation (i.e. the first step of the two step process). Other options will be apparent. If too many incorrect requests are received from a retailer activation device (e.g. within a period of time), the device may be shut out until a verification and reset can be performed (not shown). 
     Various authentication and status checks described with reference to the one-step activation process (e.g. retailer activation device authentication, delivery authentication, etc.) may be performed with adaptation as may be necessary for the two-step activation process. 
     Though the activation process is described with reference to an activation system such as distribution/activation system  206 , retailers and retailer activation device  216  perform complimentary operations. For example, using a retailer activation device, the retailer may invoke an electronic interface to activation system. The retailer may provide input to authenticate to the activation system. In the single step activation process, the retailer may provide input to provide a grouping code or an individual device verification code and make a request (communication to the activation system) to activate the associated code pairs (respective verification and redemption codes on the devices associated with the code received from the retailer) setting the status to activated with redemption code unused. The associated redemption device  100  is activated though physically it has not changed. Similarly, using a retailer activation device the retailer may invoke an electronic interface to the activation system to activate cards in accordance with the two-step process described, requesting an activation to the initial state and requesting activation to the final activation state, setting the status to activated with redemption code unused. 
     Activated redemption devices  100  may be sold by retailers and purchased by customers. Customers may in turn give or resell such redemption devices  100  to others. Customers (or others) can verify either before or after purchasing a redemption device  100  that it has been activated. The Visible Card Number  108  (i.e. the verification code) that can be seen through the transparent window in the packaging of the redemption device  100  may be verified using an activation system provide a verification function. This isn&#39;t a mandatory step. This is a feature for the convenience of customers and others so that they can satisfy themselves that they&#39;re not being cheated by the seller (which is more relevant if people are reselling cards). 
       FIG. 6  is a flowchart of a redemption device verification process showing operations of a redemption device verification system in accordance with an embodiment. Verification system functions may be provided by distribution/activation system  206  or redemption system  208  for example. A redemption device verification system and process may facilitate fraud or tampering detection. Such a system may comprise a processor, a communication subsystem and a memory each in communication with the processor. The memory may store instructions, which when executed by the processor, configure the redemption device verification system to perform operations  600  such as in  FIG. 6 . At  602  the operations communicate with a data store storing unique redemption codes and unique verification codes stored in association in respective pairs, wherein the pairs of codes are applied to respective redemption devices where the respective verification codes are visible and the respective redemption codes are not visible on each of the respective redemption devices; wherein at least some of the respective redemption devices are distributed for delivery to users through one or more channels; and wherein the data store stores a respective activation status with each of the pairs of codes indicating whether or not the respective redemption device is activated with redemption code ready to use. At  604 , operations receive via the communication subsystem a verification request for one of the respective redemption devices. At  606  operations determine the respective activation status from the data store and, at  608 , provide a reply that is responsive to the activation status. The verification request comprises the respective verification code of the one of the respective redemption devices. The verification request may be received before or after a purchase of the one of the respective redemption devices. At  606  (though not shown) the verification look up in the database may also determine the amount of fiat currency associated with the device  100 . This may be the full amount before any redemption or a partial amount if the card is redeemed in part to purchase less than the full amount of equivalent cryptocurrency. It may be a zero amount if fully redeemed. The available amount may be provided with status. 
     The data store may update respective activation statuses in response to particular ones of the respective redemption devices being activated after delivery. The data store may update respective activation statuses in response to particular ones of the respective redemption devices being redeemed. 
     Complementary operations by a customer or other person using a verification device (e.g. a redeeming user device  218 ) verify a code. For example, input may be received by a verification device which invokes an electronic interface to the verification system. This may be a web interface, phone IVR system, text message interface, application interface etc. similar to described for activation. Input may be received providing a verification code which is communicated in a request to the verification system. A response may be received in reply with a relevant status, where the verification code is used by the verification system to look-up the status. In some examples the available amount is also included in the response as described herein. 
     To redeem a redemption device  100 , a customer or other person in receipt removes the opaque film (e.g. wrapper) to expose the Secret Card Number (redemption code) which is then input into an electronic interface as part of a redemption process. 
       FIG. 7  is a flowchart of a redemption process showing activities of a redemption system according to an embodiment where the redemption code is a one-time code to spend the full amount of the fiat currency associated with the redemption code. Redemption system functions may be provided by redemption system  208  or another redemption system for example. A redemption system and process redeems a redemption code such as to transfer an amount of cryptocurrency at a prevailing rate to the fiat currency amount  106  of the redemption device  100 . Preferably the customer may choose between or among types of cryptocurrencies. Such a redemption system may comprise a processor, a communication subsystem and a memory each in communication with the processor. The memory may store instructions, which when executed by the processor, configure the redemption system to perform operations  700  as in  FIG. 7 . 
     At  702  operations communicate with a data store storing unique redemption codes and unique verification codes stored in association in respective pairs, wherein the pairs of codes are applied to respective redemption devices where the respective verification codes are visible and the respective redemption codes are not visible but revealable on each of the respective redemption devices; wherein at least some of the respective redemption devices are distributed for delivery to users through one or more channels; and wherein the data store stores a respective activation status and prepaid amount with each of the pairs of codes indicating whether or not the respective redemption device is activated with redemption code ready to use. At  704  operations receive via the communication subsystem a redemption request for one of the respective redemption devices including a respective redemption code. At  706 , operations determine the respective activation status from the data store. At  708  operations authorize the redemption in the prepaid amount only if the respective activation status is activated with redemption code ready to use and provide a reply in accordance with the respective activation status (i.e. redemption). At  710 , if the redemption is authorized, operations set the respective activation status to activated with redemption code used. Though not shown in  FIG. 7 , in another example, the redemption system and data store may be configured to enable less than the available amount of the fiat currency to be spent in a single transaction (e.g. redeeming a portion of the available amount). The portion of the available amount to be spent in a redemption transaction may be received with the redemption request. This portion may be verified against the available amount in the data store to ensure sufficient funds. If a (further) partial amount of the available fiat currency remains after the redemption, the status may be set to indicate a partial amount remains. If none remains, the status is set to activated with redemption code used. The partial amount remaining is stored in the data store. 
     The operations facilitate a transfer of an amount of cryptocurrency at a prevailing rate using the prepaid amount (or partial amount as indicted in the request to redeem). The operations facilitate the transfer of the amount of cryptocurrency to an address associated with the redemption. request. 
     The redemption request may include a type of cryptocurrency and the operations facilitate the transfer according to the type of cryptocurrency requested. For example the electronic interface may provide a GUI or other interface to specify the type. A plurality of types (e.g. Bitcoin™, Ether™, etc.). Sub types (e.g. Bitcoin Classic) may be specified and are included within a type of cryptocurrency as used herein. It is understood that redemption may include purchasing more than one cryptocurrency type, e.g. buying two or more cryptocurrencies. 
     Operations of redemption system  208  (or a system with which it communicates) may communicate with a plurality (e.g. 1 . . . M) of cryptocurrency exchanges ( 230 ,  232 ) to enable purchases of different types of currencies as many exchanges only provide services for one or a few types of currencies. Operations may communicate with a plurality of cryptocurrency exchanges to enable purchasing at a minimized rate. The redemption services of redemption system  208  or a system with which it communicates may thus enable shopping around for a lowest price from two or more cryptocurrency exchanges ( 230 ,  232 ) to attempt to maximize the amount of cryptocurrency received for the amount of fiat currency. An interface may be provided to enable the redeeming user device  218  to select a particular cryptocurrency exchange for use when redeeming. 
     Operations (e.g. of redemption system  208  or a system with which it communicates) may communicate with a cryptocurrency exchange to obtain an inventory of cryptocurrency which is stored in a secure wallet (not shown) coupled to the redemption system and the redemption system transfers the amount of cryptocurrency from the secure wallet to the address associated with the redemption request. The redemption request may be received from an interface of a redeeming user&#39;s device having a redeeming user&#39;s cryptocurrency wallet (not shown) and the address may be associated with the redeeming user&#39;s cryptocurrency wallet. Cryptocurrency exchanges often do not facilitate instant withdrawals—they often delay a withdrawal for verification and/or batching, causing delay in fulfilling a purchase request. Operations which define an operational secure wallet coupled to the redemption system may thus speed delivery of cryptocurrency to a redeeming user, without waiting for an exchange. An inventory management process may be configured to review the balance of the operational secure wallet and make purchases (and possibly sales back to an exchange) to maintain a desired level of inventory. Operations may define an operational secure wallet to handle one or more cryptocurrency types and one or more fiat currency types. 
     The redemption system may transfer funds (e.g. using traditional payment networks or otherwise) to one or more third party cryptocurrency exchanges (e.g. Bittrex™, Shapeshift™) to reconcile the system&#39;s purchase of its inventory of cryptocurrency to settle/reconcile accounts. 
     Though described with reference to a redemption system, complementary operations may be performed by a redeeming user device  218  and its user to redeem a particular redemption device  100 . In one example, the particular redemption device may be printed with a QR or similar barcode having the redemption code and preferably verification code encoded therein to invoke a mobile wallet application (e.g. a redeeming user&#39;s cryptocurrency wallet) on redeeming user device  218 . 
     Once scanned, a GUI of the wallet application will prompt the redeeming user to input a selection (or type data) of which type of cryptocurrency they would like, if more than one type is offered. The GUI may present the prevailing price (or prices of each, if there are several options displayed). This price may be relative to the type of fiat currency of the prepaid amount associated with the redemption code. In some examples the user may input or select a portion of the prepaid amount or any remaining amount for the transaction. The user then inputs and the wallet application receives the confirmation of the purchase. The request is communicated (e.g. redemption code and preferably verification code), type of currency, (optionally amount of fiat currency), mobile wallet address) to the redemption system and redemption is performed to transfer the purchased amount of currency to the address of the mobile wallet and update the status in the data store. A request may be defined by more than one communication of the request data to the redemption system. 
     In another redemption example, the redemption device&#39;s codes can be entered into a website or mobile-ready website as part of a redemption process in which a user may input a selection (or type data) of a type of cryptocurrency they&#39;d like to buy. The redeeming user supplies an “address” for where they would like the cryptocurrency to be deposited. The redemption system then sends the amount of the type of cryptocurrency indicated at the prevailing rate using the prepaid fiat currency amount. The status in the data store is updated. This method doesn&#39;t require the redeeming user to use any particular blockchain wallet system but it does require that they have one. 
     The redemption device and systems described herein may be ideal for locations that are not well connected electronically, such as less developed countries or regions. Retailers in developed countries generally sell gift cards using electronic activation at the point of sale. This system doesn&#39;t require activation at the point of sale (although it could be done) and activation could be done using a very simple method such as a phone call or text message (to activate a box). 
     While this specification contains many specifics, these should not be construed as limitations, but rather as descriptions of features specific to particular implementations. Certain features that are described in this specification in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, various features that are described in the context of a single implementation may also be implemented in multiple implementations separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination. 
     Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the implementations described above should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products. 
     Various embodiments have been described herein with reference to the accompanying drawings. It will, however, be evident that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the broader scope of the disclosed embodiments as set forth in the claims that follow. Further, other embodiments will be apparent to those skilled in the art from consideration of the specification and practice of one or more embodiments of the present disclosure. It is intended, therefore, that this disclosure and the examples herein be considered as exemplary only, with a true scope and spirit of the disclosed embodiments being indicated by the following listing of exemplary claims.