System and method for redeeming tokens

Abstract

Systems and methods for redeeming tokens are provided. One example computer-implemented method includes receiving, by a processing network, an authorization request for a user to redeem a token from a first institution, and checking a data structure hosted address associated with the redemption of the token. The method further includes, in response to the data structure address indicating the token, authorizing the redemption whereby the institution transfers the value associated with the token to the user.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of and priority to U.S. Provisional Application No. 63 / 405,845, filed on September 12, 2022. The entire disclosure of the above application is incorporated herein by reference. Technical Field

[0003] The present disclosure is generally directed to systems and methods for use in employing a data structure for a token and supporting redemption of the token via the data structure. Background Art

[0004] This section provides background information related to the present disclosure which is not necessarily prior art.

[0005] As we all know, cryptocurrencies are exchanged as a form of money, wherein the cryptocurrency does not rely on any central authority to maintain or sustain the cryptocurrency. Moreover, stablecoins are cryptocurrencies, the value of which is pegged to the value of another currency, commodity, or financial instrument. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The drawings described herein are for illustrative purposes only of selected embodiments and not all possible implementations, and are not intended to limit the scope of the present disclosure.

[0007] Figure 1 An example system suitable for redeeming tokens of the present disclosure is shown;

[0008] Figure 2 is available in Figure 1 A block diagram of an example computing device used in the system; and

[0009] Figure 3 An example method for redeeming tokens is shown, which can be used with Figure 1 used in combination with the system.

[0010] Corresponding reference numerals indicate corresponding parts throughout the several views of the drawings. DETAILED DESCRIPTION

[0011] Example embodiments will now be described more fully with reference to the accompanying drawings.The description and specific examples included herein are intended for purposes of illustration only and are not intended to limit the scope of the present disclosure.

[0012] Certain tokens may be associated with a value, whereby the token may be exchanged for a product (e.g., a good or service, etc.), or another currency (e.g., U.S. dollars, etc.). An example token is a stablecoin, whose value is pegged to the value of another currency, commodity, or financial instrument. In this manner, a stablecoin may have a value of $50, whereby the exchange of the stablecoin may be tied to a common currency, commodity, or financial instrument. That is, technical deficiencies limit the manner and / or convenience of exchanging such tokens (e.g., stablecoins, etc.) for various reasons, whereby the availability of the token is limited in a technical manner as being burdensome, prohibitive, and / or cumbersome.

[0013] Uniquely, the systems and methods herein provide for the exchange of tokens (e.g., stablecoins, etc.) at one or more locations (e.g., institutions, etc.), where the locations are associated with a processing network. In this manner, the processing network is improved to include a specific data structure associated with the exchange, whereby the tokens are transferred to the data structure and confirmed, and the separate transfer of funds associated with the tokens is then partitioned into the processing network messaging. Thus, the exchange of such tokens utilizes the improved processing network in a manner that advances the ease and / or usability of the tokens to users.

[0014] Figure 1 An example system 100 is shown in which one or more aspects of the present disclosure may be implemented. Although system 100 is presented in one arrangement, other embodiments may include portions of system 100 (or other portions) arranged in other ways, depending on, for example, privacy concerns and / or requirements.

[0015] The illustrated system 100 generally includes a processing network 102, two financial institutions 104A and 104B (e.g., banks, etc.), a user computing device 106 associated with a user 108 (who may or may not be associated with institution 104A), a token issuer 110 (e.g., a stablecoin issuer, etc.), and a clearing system 112, each of which is coupled to one or more networks. The one or more networks (e.g., Figure 1 The network may include, but is not limited to, a local area network (LAN), a wide area network (WAN) (e.g., the Internet, etc.), a mobile network, a virtual network, and / or a network capable of supporting Figure 1 One or more of additional suitable public and / or private networks for communication between two or more parts shown in, or any combination thereof, etc.

[0016] In this example embodiment, processing network 102 is configured to coordinate the exchange of tokens (e.g., stablecoins (e.g., USDC, etc.) etc.) submitted by user 108 via computing device 106. Processing network 102 may include, for example, a MasterCard, Visa, or American Express card processing network or other suitable processing network, etc.

[0017] Institutions 104A, 104B each include a financial institution such as, for example, a bank, which is configured to participate in the transfer of funds between accounts. Institutions 104A, 104B are configured to issue one or more accounts to users including user 108, etc., and other entities such as, for example, token issuer 110, etc. Accounts may include, but are not limited to, debit accounts, savings accounts, checking accounts, and / or payment accounts (e.g., credit accounts, debit accounts, prepaid accounts, etc.), etc.

[0018] In this example embodiment, the token issuer 110 is configured to issue tokens such as, for example, stablecoins, cryptocurrencies, etc., which can be transferred by users (e.g., user 108, etc.) in exchange for products (e.g., goods, services, etc.) and / or legal tender. Legal tender includes, for example, government-backed currencies, such as, for example, U.S. dollars (USD$), euros (€), etc. Tokens typically each include a unique data sequence. The token may have a fixed value pegged to a legal tender, commodity, or other financial instrument. For example, then, the token may have a static "value" of $50. It should be appreciated that other denominations, static or non-static, may be associated with other tokens in various embodiments. Such a token may provide static value or stability by holding a reserve asset as collateral or controlling the supply through an algorithmic formula.

[0019] The clearing system 112 of the system 100 is illustrated as part of the processing network 102. The clearing system 112 is configured to clear and settle transactions initiated through the processing network 102, whereby funds move from institution to institution, etc. It should be appreciated that the clearing system 112 may be separate from the processing network 102 in other embodiments. More importantly, the system 100 also includes a data structure 114, such as a blockchain structure (e.g., managed or controlled by the processing network 102, a third party, etc.), which is an immutable data structure. The data structure 114 is organized by address, thereby storing data based on blocks and / or their addresses. The data structure 114 may be part of the processing network 102 as in this embodiment, or separate therefrom, and / or may be managed by the processing network 102, the token issuer 110, etc.

[0020] Based on the above, a user 108 who holds or otherwise possesses a token associated with a particular value (e.g., a stablecoin, a cryptocurrency, etc.) may wish to exchange the token for a local currency or a fiat currency through an institution 104A. That is, the institution 104A has issued an account to the user 108, and the user 108 wishes to exchange the token for funds commensurate with the value of the token deposited in the account. In connection therewith, the institution 104A is configured to exchange the token through the processing network 102, whereby the institution 104A is configured to instruct the user 108 to transfer the token (e.g., the token, the amount associated with the token, etc.) to a data structure 114 at a specific address thereof, namely, an escrow address (e.g., as an escrow contract and / or associated with an escrow contract, etc.). The escrow address is a location on the data structure 114, which may be managed by the processing network 102 and / or the token issuer 110.

[0021] In response, user 108 transfers or posts the token (e.g., an amount associated with the token, etc.) to data structure 114 at the escrow address via computing device 106. In connection with user 108 transferring the token, institution 104A is configured to initiate a transaction for redemption of the token (or the value associated with the token). Specifically, institution 104A is configured to write an authorization request consistent with the redemption (e.g., consistent with ISO 8583 standard, etc.) and submit the authorization request to processing network 102. The authorization request may include a data element indicating the redemption of the token (e.g., a data element including an indicator of TOKEN_REDEMPTION_REQUEST, etc.), or the authorization request may include a new optional data element that is present only when the authorization request is related to the redemption of the token.

[0022] The processing network 102 is further configured to receive an authorization request from the institution 104A to identify a request for exchange of tokens (e.g., based on the inclusion of data elements indicating exchange of tokens, etc.), and to interact with the data structure 114 to check the tokens and / or associated value or balance in the escrow address (based on the information included in the authorization request, etc.). In response to the check indicating that the value / tokens are posted to the escrow address, the processing network 102 is configured to authorize the transaction, whereby an authorization reply (e.g., consistent with the ISO 8583 standard, etc.) is written and sent to the institution 104A. In addition, the processing network 102 is configured to alert the token issuer 110 of the authorization of the transaction to exchange the tokens. In response, the token issuer 110 is configured to destroy the tokens (e.g., one or more stablecoins, etc.) submitted to the data structure 114 at the escrow address. It should be understood that in this embodiment, the escrow address is a "one-way" address only and only the token issuer 110 is allowed to access the escrow address once the tokens are posted there. That is, any tokens in this escrow address indicated by the processing network 102 and / or the authorization are destroyed. It should be appreciated that the above may also be automated via smart contracts, which may be optionally enforced to enhance the efficiency of the above interactions.

[0023] Thus, consistent with the authorization, institution 104A is configured to submit the transaction (i.e., the redemption transaction) to processing network 102 (e.g., as part of a clearing file, etc.) for clearing. In connection therewith, institution 104a is configured to pay funds to user 108 based on the processing network authorization. Processing network 102, and more specifically clearing system 112 in this example, is configured to clear transactions between institution 104A and institution 104B, which is the issuer of the issuance account to token issuer 110. In this manner, clearing system 112 is configured to direct funds from institution 104B to institution 104A (potentially along with other transactions), which results in two settlement amounts. A first settlement amount is paid from processing network 102 to institution 104A for enabling redemption of tokens, and a second settlement amount is paid from institution 104B (on behalf of token issuer 110) to processing network 102 for redemption of tokens. The token issuer 110 is configured to then pay the institution 104B (or allow the institution 104B to debit its account). This effectively provides a transfer from the account of the token issuer 110 at the institution 104B to the account of the user 108 at the institution 104A.

[0024] Once a transaction is settled, the associated obligations are resolved.

[0025] although Figure 1104A and 104B are shown, but it should be appreciated that in other embodiments multiple institutions may be included in the system 100. More importantly, it should be appreciated that the clearing and settlement of transactions for exchanging tokens may be combined with one or more other transactions (whether or not related to the exchange) between institutions 104A and 104B and other institutions.

[0026] Figure 2 It shows that it can be Figure 1 An example computing device 200 for use in system 100 of the present invention is shown. Computing device 200 may include, for example, one or more servers, workstations, personal computers, laptops, tablet computers, smart phones, etc. Furthermore, computing device 200 may include a single computing device, or it may include multiple computing devices located in close proximity or distributed over a geographic area, so long as the computing devices are specifically configured to function as described herein. Figure 1 In the example embodiment of the present invention, each of the processing network 102, the institutions 104A-B, the user computing devices, the token issuers, the clearing system 112, and the data structure 114 may be considered, may include, and / or may be implemented in a computing device consistent with the computing device 200, coupled to one or more networks of the system 100 (and in communication with it). However, the system 100 should not be considered limited to the computing device 200, as different computing devices and / or arrangements of computing devices may be used in other embodiments, as described below. In addition, different components and / or arrangements of components may be used in other computing devices.

[0027] refer to Figure 2 , the example computing device 200 includes a processor 202 and a memory 204 coupled to (and in communication with) the processor 202. The processor 202 may include one or more processing units (e.g., in a multi-core configuration, etc.). For example, the processor 202 may include, but is not limited to, a central processing unit (CPU), a microcontroller, a reduced instruction set computer (RISC) processor, an application specific integrated circuit (ASIC), a programmable logic device (PLD), a gate array, and / or any other circuit or processor capable of implementing the functionality described herein.

[0028] Memory 204, as described herein, is one or more devices that allow data, instructions, etc. to be stored therein and retrieved therefrom. Memory 204 may include one or more computer-readable storage media such as, but not limited to, dynamic random access memory (DRAM), static random access memory (SRAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), solid-state devices, flash drives, CD-ROMs, thumb drives, floppy disks, magnetic tapes, hard disks, and / or any other type of volatile or non-volatile physical or tangible computer-readable media. Memory 204 may be configured to store, without limitation, token addresses, liquidation records, account balances, and / or other types of data (and / or data structures) suitable for use as described herein.

[0029] In addition, in various embodiments, computer executable instructions may be stored in memory 204 for execution by processor 202 to cause processor 202 to perform one or more of the functions described herein, and thus memory 204 is a physical, tangible, and non-volatile computer-readable storage medium. Such instructions often improve the efficiency and / or performance of processor 202 and / or other computer system components configured to perform one or more of the various operations herein (e.g., one or more of the operations described herein, etc.), thereby converting computing device 200 into a special-purpose computing device when (or in connection with) performing such one or more operations. It should be appreciated that memory 204 may include a variety of different memories, each implemented in one or more of the functions or processes described herein.

[0030] In the example embodiment, computing device 200 also includes a presentation unit 206 and an input device 208 .

[0031] The presentation unit 206 is coupled to (and in communication with) the processor 202 (however, it should be appreciated that the computing device 200 may include output devices other than the presentation unit 206, etc.). The presentation unit 206 outputs information visually or audibly, for example, to a user of the computing device 200, etc. Also, various interfaces may be displayed at the computing device 200, and in particular at the presentation unit 206, to display certain information related thereto. The presentation unit 206 may include, but is not limited to, a liquid crystal display (LCD), a light emitting diode (LED) display, an organic LED (OLED) display, an "electronic ink" display, a speaker, etc. In some embodiments, the presentation unit 206 may include multiple devices.

[0032] The input device 208 receives input from the user 112 of the computing device 200 (i.e., user input), such as, for example, input to redeem tokens, etc., as further described herein. The input device 208 may include a single input device or multiple input devices. The input device 208 is coupled to (and in communication with) the processor 202 and may include, for example, one or more of a keyboard, a pointing device, a mouse, a camera, a touch-sensitive panel (e.g., a touchpad or touch screen, etc.), another computing device, and / or an audio input device. In various example embodiments, a touch screen, such as included in a tablet computer, a smart phone, or a similar device, may be present as both the presentation unit 206 and the input device 208.

[0033] In addition, the illustrated computing device 200 also includes a network interface 210 coupled to (and in communication with) the processor 202 and the memory 204. The network interface 210 may include, but is not limited to, a wired network adapter, a wireless network adapter (e.g., an NFC adapter, a Bluetooth adapter, a TM Adapter, etc.), a mobile network adapter, or other device capable of transmitting to one or more different networks described herein and / or communicating with other devices described herein. In some example embodiments, computing device 200 may include processor 202 and one or more network interfaces incorporated into or combined with processor 202.

[0034] Figure 3 An example method 300 is shown for use in redeeming tokens. The example method 300 is described as being implemented in the system 100, and further reference is made to the computing device 200. However, the methods herein should not be understood as being limited to the system 100 or the computing device 200, as the methods may be implemented in other systems and / or computing devices. Moreover, the systems and computing devices herein should not be understood as being limited to the example method 300.

[0035] At the outset, it should be understood that a number of tokens have been issued by the token issuer 110, whereby each token is associated with a certain value that may be static or dynamic. More importantly, the user 108 holds the tokens issued by the token issuer.

[0036] To redeem the token for funds deposited in the account issued by the institution 104A to the user 108, the user 108 requests the institution 104A to redeem the token (e.g., generate and submit a request, etc.) via the computing device 106 at 302. The request may be submitted through an interface associated with a website or application of the institution 104A (as displayed to the user 108 at, for example, the computing device 106). In connection therewith, the request may include, for example, an indication of the token that the user 108 wishes to redeem (e.g., to be distinguished from other tokens that the user 108 may have / own, etc.), such as, for example, an amount, an identifier of the token issuer 110, and an identifier that distinguishes the token from other tokens of the user (and / or other tokens issued by the token issuer 110, etc.), etc. In response, at 304, the institution 104A instructs the user 108 to transfer the token to the data structure 114, and specifically to a particular address of the data structure 114, i.e., the escrow address.

[0037] Next, at 306 , the user 108 , via the computing device 106 , transfers the token to the data structure 114 at the escrow address (eg, via an interface associated with a website or application of the institution 104A or otherwise, etc.).

[0038] Next, if Figure 3 As shown, the institution 104A writes an authorization request for trading funds to the user's account at 308 (e.g., also in response to a redemption request, etc.). The authorization request can be an ISO 8583 standard message, and can include (for example and without limitation) the account number of the user 108, the amount to be transferred (i.e., the value of the token to be redeemed (subject to one or more fees), the identifier of the token issuer 110, the custodian address of the token, an indication of the token (e.g., the symbol of the token (e.g., USDC (USD Coin), EUROC (Euro Coin), Tether USDT, etc.), etc.), etc. (e.g., included in one or more specific data elements of the authorization request, etc. (e.g., standard data elements, optional data elements, etc.)). The authorization request also includes an indication of a redemption request for the token, thereby distinguishing the authorization request from a conventional authorization request (e.g., thereby omitting the account number of the token issuer 110 and other data, etc.). At 310, the authorization request is sent to the processing network 102.

[0039] Upon receiving the authorization request, the processing network 102 identifies the request as a redemption request (based on the content of the data element in the authorization request) and confirms at 312 that the token is included at the escrow address of the data structure 114. When it is confirmed that it exists and has a value consistent with the amount of the authorization request, the processing network 102 authorizes the transaction. In this regard, the processing network 102 writes an authorization reply at 314, which includes the transaction amount, the account number of the token issuer 110 and / or the identifier of the institution 104B, etc. In this example, the processing network 102 includes or maintains a record of the accounts of token issuers (including the account of the token issuer 110). As such, the processing network 102 identifies from the record the account of the token issuer 110 to be used in the transaction based on the information included in the authorization request (e.g., the identifier of the token issuer 110, the indication / symbol of the token, etc.). The authorization reply is sent to the institution 104A at 316.

[0040] At the same time, or before or after, at 318, the processing network 102 instructs the token issuer 110 to destroy the token. More specifically, in this example embodiment, the processing network instructs the token issuer 110 to destroy a specific amount of tokens from the escrow address of the token at the data structure 114 (e.g., "destroy [x] amount of [token symbol] from the escrow contract," etc.). In response, the token issuer 110 destroys the tokens in the data structure 114 (e.g., the amount of tokens associated with the request / transaction, etc.) at 320. In some example embodiments, the token destruction may be automatically performed following the instructions from the processing network 102 (e.g., the token destruction may be an automated operation, etc.). Additionally, in some example embodiments, the token issuer 110 may delegate the token destruction to the processing network 102, whereby the processing network 102 may notify the token issuer of the destruction instruction (or not) and may subsequently destroy the tokens (at 320).

[0041] Related to the above, after authorization, the transaction is cleared and settled by and between institutions 104A and 104B through processing network 102, whereby funds are transferred from institution 104B to institution 104A. Funds are debited from the account issued to token issuer 110 at institution 104B and credited to user 108's account at institution 104A.

[0042] In view of the above, the systems and methods herein provide for exchanging tokens, such as, for example, stablecoins, through the emergence of data structures and / or improvements to processing networks. In this way, the exchange of tokens utilizes the improved processing network in a manner that promotes the ease and / or usability of the tokens to users.

[0043] As previously described, it should be appreciated that the functions described herein can be described in computer executable instructions stored on a computer readable medium in some embodiments, and can be performed by one or more processors. Computer readable media is a non-transient computer readable storage medium. As an example and not limitation, such a computer readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures that can be accessed by a computer. The above combination should also be included in the scope of computer readable media.

[0044] It should also be recognized that one or more aspects of the present disclosure transform a general-purpose computing device into a special-purpose computing device when configured to perform the functions, methods and / or processes described herein.

[0045] As will be appreciated based on the foregoing description, the above-described embodiments of the present disclosure may be implemented using computer programming or engineering techniques including computer software, firmware, hardware, or any combination or subset thereof, wherein the technical effect may be achieved by performing at least one or more of the operations recited in the claims, such as, for example: (a) receiving an authorization request from a first institution for a user to redeem a token; (b) checking a data structure escrow address associated with the redemption of the token; (c) in response to the data structure address indicating the token, authorizing the redemption, whereby the institution transfers the value associated with the token to the user; (d) receiving a settlement record of at least the token redemption; and / or settling the redemption between the first institution and a second institution associated with the token issuer of the token.

[0046] In addition, the above-mentioned embodiments of the present disclosure may be implemented using computer programming or engineering techniques including computer software, firmware, hardware, or any combination or subset thereof, wherein the technical effect may be achieved by executing at least one or more of the operations stated in the claims.

[0047] Example embodiments are provided so that the present disclosure will be thorough and will fully convey the scope to those skilled in the art. Numerous specific details, such as examples of specific components, devices, and methods, are set forth to provide a thorough understanding of the embodiments of the present disclosure. It will be clear to those skilled in the art that specific details need not be employed, that the example embodiments may be embodied in many different forms and that neither should be construed as limiting the scope of the present disclosure. In some example embodiments, well-known processes, well-known device structures, and well-known techniques are not described in detail.

[0048] The terms used herein are only used for the purpose of describing specific example embodiments and are not intended to be restrictive. As used herein, the singular forms "one", "an" and "the" may be intended to include plural forms unless the context clearly indicates otherwise. The terms "comprise", "contain", "include" and "have" are inclusive, thus specifying the presence of stated features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or their groups. The method steps, processes and operations described herein should not be interpreted as necessarily requiring them to be performed in the specific order discussed or illustrated, unless specifically identified as the order of execution. It is also to be understood that additional or alternative steps may be adopted.

[0049] When a feature is referred to as being "on," "engaged to," "connected to," "coupled to," "associated with," "included in," or "in communication with" another feature, it may be directly on, engaged to, connected to, coupled to, associated with, included in, or in communication with another feature, or intervening features may be present. As used herein, the term "and / or" and the phrase "at least one" include any and all combinations of one or more of the associated listed items.

[0050] Although the terms first, second, third, etc. may be used to describe various features in this article, these features should not be limited by these terms. These terms may only be used to distinguish one feature from another feature. Terms such as "first", "second" and other numerical terms do not imply sequence or order when used in this article unless clearly indicated by the context. Therefore, the first feature discussed herein may be referred to as the second feature without departing from the teachings of the exemplary embodiments.

[0051] No element recited in a claim is intended to be a means-plus-function element within the meaning of 35 U.S.C. § 112(f) unless the element is expressly recited using the phrase "means for" or, in the case of a method claim, using the phrases "operation of" or "step of."

[0052] The foregoing description of example embodiments has been provided for the purpose of illustration and description. It is not intended to be exhaustive or to limit the present disclosure. Individual elements or features of a particular embodiment are generally not limited to that particular embodiment, but are interchangeable where applicable and may be used in selected embodiments, even if not specifically shown or described. It may also vary in many ways. Such variations should not be considered as departing from the present disclosure, and all such modifications are intended to be included within the scope of the present disclosure.

Claims

1. A computer-implemented method for exchanging tokens, the method comprising: Receiving, by the processing network, an authorization request from the first institution for a user to redeem a token; The processing network checks the escrow address of the data structure associated with the redemption of the token; Responsive to the data structure escrow address indicating the token, redemption of the token is authorized, whereby the institution transfers the value associated with the token to the user.

2. The computer-implemented method of claim 1, wherein: The data structure comprises an immutable blockchain data structure.

3. The computer-implemented method of claim 1, wherein: Tokens include stablecoins.

4. The computer-implemented method of claim 1 , further comprising: receiving, by the processing network, a settlement record for at least the exchange of tokens; as well as An amount associated with the exchange is settled by the processing network between the first institution and a second institution associated with a token issuer of the token.

5. The computer-implemented method of claim 4, wherein: The data structure hosting address is a one-way-only address; and The data structure hosting address can only be accessed by the token issuer.

6. The computer-implemented method of claim 1, wherein: The data structure escrow address is associated with the amount of tokens available to the user.

7. The computer-implemented method of claim 6, further comprising: After the redemption of tokens is authorized, instructions to destroy tokens are generated.

8. The computer-implemented method of claim 6, further comprising destroying the token after redemption of the token is authorized.

9. The computer-implemented method of claim 1, wherein: The authorization request includes an indication of the token issuer of the token and the token symbol of the token.

10. A non-transitory computer-readable storage medium comprising executable instructions that, when executed by at least one processor in conjunction with redeeming a token, cause the at least one processor to: receiving, from the first institution, an authorization request for a user to redeem a token; Check the data structure escrow address associated with the redemption of tokens; Responsive to the data structure escrow address indicating the token, redemption of the token is authorized, whereby the institution transfers the value associated with the token to the user.

11. The non-transitory computer readable storage medium of claim 10, wherein the executable instructions, when executed by the at least one processor, further cause the at least one processor to: Receive settlement records for at least token redemptions; and An amount associated with the exchange is settled between the first institution and a second institution associated with a token issuer of the token.

12. The non-transitory computer-readable storage medium of claim 10, wherein: The authorization request includes an indication of the token issuer of the token, the token symbol of the token, and the data structure escrow address of the token; and Wherein the executable instructions, when executed by the at least one processor, further cause the at least one processor to retrieve a data structure escrow address from the authorization request prior to checking the data structure address associated with redemption of the token.

13. The non-transitory computer readable storage medium method of claim 12, wherein: The data structure escrow address is associated with the amount of tokens available to the user.

14. The non-transitory computer readable storage medium method of claim 13, wherein: The executable instructions, when executed by the at least one processor, further cause the at least one processor to generate instructions to destroy the token after the token is redeemed.

15. The non-transitory computer readable storage medium method of claim 13, wherein: The executable instructions, when executed by the at least one processor, further cause the at least one processor to destroy the token after the token is redeemed.

16. A system for exchanging tokens, the system comprising a computing device, the computing device being configured to: receiving, from the first institution, an authorization request for a user to redeem a token; Check the data structure escrow address associated with the redemption of tokens; Responsive to the data structure escrow address indicating the token, redemption of the token is authorized, whereby the institution transfers the value associated with the token to the user.

17. The system of claim 16, further comprising a data structure in communication with a computing device, the data structure comprising the data structure hosting address.

18. The system of claim 17, wherein: The data structure comprises an immutable blockchain data structure.

19. The system of claim 18, wherein: The data structure hosting address is a one-way-only address; and The data structure hosting address can only be accessed by the token issuer.

20. The system of claim 19, wherein: The computing device is further configured to instruct destruction of the token in response to the token being redeemed.

Images