INFORMATION SETS

Technical Field

[0001] The present disclosure relates generally to validating of information and/or information sets, and more specifically, to systems, subsystems, processors, devices, logic, methods, and processes for performing validation and/or authentication of information, information sets, information exchanges, value exchanges, transactions, interactions, or the like.

Background

[0002] There are various occasions celebrated around the world that involve the giving of gifts. For example, birthdays, anniversaries, and Christmas typically involve gift giving and/or exchanging. Chinese New Year is celebrated in China and many other parts of the world. Chinese New Year celebrations involve, among other things, the giving of money. More specifically, a giver (who is normally an older person, married person, and/or person in a position of authority) will place money in a red-colored envelope (referred to herein as a "red envelope"), optionally write a recipient name and a message onto the red envelope, and give the red envelope to a recipient (who is normally a younger person, single/unmarried person, and/or person with a lower position). It is not uncommon for a giver to give out tens (or even hundreds) of red envelopes each Chinese New Year.

Brief Summary

[0003] There are presently a variety of ways in which users can give gifts, information, and/or value to other users. Greeting cards, or the like, have been used by users to send messages and/or greetings to other users, and may also include gifts of value (e.g., money, cash, fiat currency, gift certificates, gift cards, etc.) within the greeting card. Gift cards, or the like, which are offered by specific merchants, enable users to purchase a specific pre-set or pre-loaded value or add a specific user- selectable value for the gift card. Gift cards are generally limited in use to within participating merchants. As another example, red envelopes are generally used by those who celebrate Chinese New Year.

[0004] Recent developments in technology have improved the way users give gifts and/or exchange information and/or value. When it comes to red envelopes for Chinese New Year (and other similar giving of value for other occasions), however, not much has changed over the years. Time and effort are required by each giver in preparing red envelopes for Chinese New Year. Similar time and efforts are also required in preparing for the exchange of information and/or value for other holidays and/or occasions.

[0005] Present example embodiments relate generally to and/or include systems, subsystems, processors, devices, logic, methods, and processes for addressing conventional problems, including those described above and in the present disclosure, and more specifically, example embodiments relate to systems, subsystems, processors, devices, logic, methods, and processes for validating and/or authenticating information, information sets, exchanges of information, exchanges of value, transactions, interactions, or the like, in a secure, encrypted (and/or hashed), and reliable manner.

[0006] In an exemplary embodiment, a method of validating information is described. The method includes performing a validatable information set generation process. The validatable information set generation process includes performing, by a first setup processor, a first setup process. The first setup process includes generating a first payload (also referred to as a payload). The first setup process also includes encrypting (and/or hashing, such as SHA-256, SHA-3, etc.) the first payload to arrive at a first encrypted payload. The first encrypted payload is decryptable using a first secret key. The first setup process also includes generating a first encrypted payload identifier. The first setup process also includes generating an association between the first encrypted payload and the first encrypted payload identifier. The first setup process also includes storing the association between the first encrypted payload and the first encrypted payload identifier in a first database. The validatable information set generation process also includes performing, by a second setup processor, a second setup process. The second setup process includes encrypting the first payload to arrive at a second encrypted payload. The second encrypted payload is decryptable using a second secret key. The second secret key is different from the first secret key. The second encrypted payload is not decryptable using the first secret key. The first encrypted payload is not decryptable using the second secret key. The second setup process also includes generating a final payload. The final payload includes the second encrypted payload and a deep link. The second setup process also includes encoding a final unique QR code with the final payload. The validatable information set generation process also includes generating, by a third setup processor, a final information set. The final information set includes the final unique QR code and the first encrypted payload identifier. The method also includes, responsive to a first mobile device of a first user receiving the final information set, performing a final information set validation process. The final information set validation process includes performing, by the first mobile device, an extraction process. The extraction process includes extracting, from the final information set, the final unique QR code and the first encrypted payload identifier. The extraction process also includes obtaining the final payload encoded in the final unique QR code. The extraction process also includes extracting, from the final payload, the second encrypted payload and the deep link. The final information set validation process also includes executing, by the first mobile device, the deep link extracted from the final payload. When the deep link is executed, the deep link is configured to establish a first communication channel between the first mobile device and a validation processor, and transmit, from the first mobile device to the validation processor via the first communication channel, the second encrypted payload and the first encrypted payload identifier. The final information set validation process also includes performing, by the validation processor, a validation process. The validation process includes receiving, from the first mobile device, the second encrypted payload and the first encrypted payload identifier. The validation process also includes applying the second secret key to the received second encrypted payload to determine whether or not the received second encrypted payload is decryptable by the second secret key. The validation process also includes, responsive to a determination that the received second encrypted payload is decryptable by the second secret key, obtaining a first validation result. The first validation result is a decrypted version of the received second encrypted payload. The validation process also includes performing an association search, in the first database, using the received first encrypted payload identifier as a search query. The validation process also includes, responsive to a determination, based on the association search, that the first encrypted payload identifier is associated with the first encrypted payload, obtaining the first encrypted payload from the first database. The validation process also includes applying the first secret key to the obtained first encrypted payload to determine whether or not the obtained first encrypted payload is decryptable by the first secret key. The validation process also includes, responsive to a determination that the obtained first encrypted payload is decryptable by the first secret key, obtaining a second validation result, the second validation result being a decrypted version of the obtained first encrypted payload. The validation process also includes comparing the first validation result with the second validation result. The validation process also includes, responsive to a determination, based on the comparing, that the first validation result matches the second validation result, validating the final information set. The validation process also includes, responsive to a determination, based on the comparing, that the first validation result does not match the second validation result, not validating the final information set. [0007] In another exemplary embodiment, a method of validating information is described. The method includes performing a validatable information set generation process. The validatable information set generation process includes performing a first setup process. The first setup process includes generating a first payload. The first setup process also includes encrypting the first payload to arrive at a first encrypted payload. The first setup process also includes generating a first encrypted payload identifier. The first encrypted payload identifier is associated with the first encrypted payload. The validatable information set generation process also includes performing a second setup process. The second setup process includes encrypting the first payload to arrive at a second encrypted payload. The second encrypted payload is different from the first encrypted payload. The second setup process also includes encoding a final unique QR code with the second encrypted payload. The second setup process also includes generating a final information set. The final information set includes the final unique QR code and the first encrypted payload identifier. The method also includes performing a validation process for the final information set. The validation process includes extracting, from the final information set, the final unique QR code and the first encrypted payload identifier. The validation process also includes obtaining, from the final unique QR code, the second encrypted payload. The validation process also includes decrypting the second encrypted payload. The validation process also includes performing an association search using the first encrypted payload identifier as a search query. The validation process also includes, responsive to a determination, based on the association search, that the first encrypted payload identifier is associated with the first encrypted payload: obtaining the first encrypted payload; decrypting the first encrypted payload; comparing the decrypted first encrypted payload with the decrypted second encrypted payload; and validating the final information set when the decrypted first encrypted pay load matches the decrypted second encrypted payload.

[0008] In another exemplary embodiment, a method of validating information is described. The method includes performing, by a first setup processor, a first setup process. The first setup process includes generating a first payload. The first setup process also includes encrypting the first payload to arrive at a first encrypted payload. The first encrypted payload is decryptable using a first secret key. The first setup process also includes generating a first encrypted payload identifier. The first setup process also includes generating an association between the first encrypted payload and the first encrypted payload identifier. The first setup process also includes storing the association between the first encrypted payload and the first encrypted payload identifier in a first database. The method also includes performing, by a second setup processor, a second setup process. The second setup process includes encrypting the first payload to arrive at a second encrypted payload. The second encrypted payload is decryptable using a second secret key. The second secret key is different from the first secret key. The second encrypted payload is not decryptable using the first secret key. The first encrypted payload is not decryptable using the second secret key. The second setup process also includes generating a final payload. The final payload includes the second encrypted payload and a deep link. The second setup process also includes encoding a final unique QR code with the final payload. The method also includes generating, by a third setup processor, a final information set. The final information set includes the final unique QR code and the first encrypted payload identifier. [0009] In another exemplary embodiment, a method of validating information is described. The method includes receiving, by a mobile device of a first user, a first unique QR code information set. The first unique QR code information set includes a first unique QR code and a first unique identifier. The method also includes decoding, by the mobile device, the first unique QR code to obtain a first encrypted payload and a deep link encoded in the first unique QR code. The method also includes executing the deep link. The deep link, when executed, is configured to establish a first communication channel between the mobile device and a validation processor, and transmit, from the mobile device to the validation processor via the first communication channel, the first encrypted payload and the first unique identifier. The method also includes receiving, at the validation processor from the mobile device, the first encrypted payload and the first unique identifier. The method also includes decrypting, by the validation processor, the first encrypted payload to arrive at a first validation result. The method also includes performing, by the validation processor, an association search using the received first unique identifier as a search query. The method also includes, responsive to a determination, based on the association search, that the first unique identifier is associated with a second encrypted payload, decrypting the second encrypted payload to arrive at a second validation result. The method also includes comparing the first validation result with the second validation result. The method also includes, responsive to a determination, based on the comparing, that the first validation result matches the second validation result: determining, from the first and/or second validation results, whether or not the first unique QR code information set has been configured by any user.

Brief Description of the Figures [0010] For a more complete understanding of the present disclosure, example embodiments, and their advantages, reference is now made to the following description taken in conjunction with the accompanying figures, in which like reference numbers indicate like features, and:

[0011] Figure 1 is an illustration of an example embodiment of a system for validating information, including information sets;

[0012] Figure 2 is an illustration of an example embodiment of a first setup processor;

[0013] Figure 3 is an illustration of an example embodiment of a second setup processor;

[0014] Figure 4 is an illustration of an example embodiment of an information set (or final information set);

[0015] Figure 5 is an illustration of an example embodiment of a validation processor;

[0016] Figure 6 is an illustration of an example embodiment of a validation engine;

[0017] Figure 7 is an illustration of an example embodiment of a method of validating information, including information sets;

[0018] Figure 8A is an illustration of an example embodiment of a validatable information set generation process;

[0019] Figure 8B is an illustration of an example embodiment of a first setup process;

[0020] Figure 8C is an illustration of an example embodiment of a second setup process;

[0021] Figure 8D is an illustration of an example embodiment of a method of generating an information set, including a final information set;

[0022] Figure 9A is an illustration of an example embodiment of an information set validation process;

[0023] Figure 9B is an illustration of an example embodiment of an extraction process;

[0024] Figure 9C is an illustration of an example embodiment of a method of executing a deep link extracted from a final payload; and

[0025] Figure 9D is an illustration of an example embodiment of a validation process.

[0026] Although similar reference numbers may be used to refer to similar elements in the figures for convenience, it can be appreciated that each of the various example embodiments may be considered to be distinct variations.

[0027] Example embodiments will now be described with reference to the accompanying figures, which form a part of the present disclosure and which illustrate example embodiments which may be practiced. As used in the present disclosure and the appended claims, the terms "embodiment", "example embodiment", "exemplary embodiment", and "present embodiment" do not necessarily refer to a single embodiment, although they may, and various example embodiments may be readily combined and/or interchanged without departing from the scope or spirit of example embodiments. Furthermore, the terminology as used in the present disclosure and the appended claims is for the purpose of describing example embodiments only and is not intended to be limitations. In this respect, as used in the present disclosure and the appended claims, the term "in" may include "in" and "on", and the terms "a", "an", and "the" may include singular and plural references. Furthermore, as used in the present disclosure and the appended claims, the term "by" may also mean "from," depending on the context. Furthermore, as used in the present disclosure and the appended claims, the term "if ¹ may also mean "when" or "upon", depending on the context. Furthermore, as used in the present disclosure and the appended claims, the words "and/or" may refer to and encompass any and all possible combinations of one or more of the associated listed items.

Detailed Description

[0028] Various product and service offerings are available today that enable users to give gifts and/or exchange information and/or value. For example, greeting cards have been used by users to send messages and/or greetings to other users. Gift cards, which are a relatively more recent example offered by specific merchants (e.g., Walmart, Takashima, Amazon, Apple, Starbucks, etc.), enable users to purchase a specific stored value (e.g., USD 100 or other amount or currency) or load/add a specific user-selectable value to the gift card. A recipient receiving the gift card can then use the gift card to purchase products and/or services from one or more participating merchants. As another example, red envelopes, which are used by those who celebrate Chinese New Year, are loaded with money and given to recipients.

[0029] Recent developments in technology have improved the way users give gifts and/or exchange information and/or value. For example, virtual greeting cards are now widely available for users to electronically send to others. Single-use gift cards (e.g., plastic cards) and red envelopes (which are paper-based), however, have not really changed over the years. For red envelopes, each giver will be required to engage in a certain amount of preparatory work, including visiting a financial institution (or automated teller machine, or ATM), withdrawing of "crisp" or new money from the financial institution (or ATM), changing such money as needed so as to have appropriate denominations and amounts to place into each red envelope, inserting/loading of specific amounts of money into each red envelope, adding of greetings and recipient name onto the red envelope, and sealing of each red envelope. It is recognized in the present disclosure that a significant amount of time and effort is required by each giver in preparing red envelopes for Chinese New Year. Similar time and efforts are also required preparing for the exchange of information and/or value for other holidays and/or occasions.

[0030] Present example embodiments relate generally to and/or include systems, subsystems, processors, devices, logic, methods, and processes for addressing conventional problems, including those described above and in the present disclosure. As a non-limiting example, present example embodiments enable one or more of the following: the setting up and/or generating of information sets (e.g., information set 130, as illustrated in Figure 4); incorporating of such information sets into, on, and/or as part of gifts (e.g., inserted into, printed on, and/or secured to a red envelope, etc.); preconfiguring such information sets to be pre-loaded with value and/or other information; enable users 10 (e.g., givers 10) to, among other things, load/add value and/or other information in and/or to the gift (e.g., load USD 20 in a red envelope via the information set 130); and/or enable users (e.g., recipients, who may be a different user than the giver 10 who loaded/added; or who may be the same user as the giver 10) to receive, claim, and/or accept value and/or other information loaded/added in and/or to the gift (i.e., the information set 130). More specifically, example embodiments relate to systems, subsystems, processors, devices, logic, methods, and processes for validating and/or authenticating information, information sets, exchanges of information, exchanges of value, transactions, interactions, or the like, in a secure, encrypted (and/or hashed), and reliable manner, including, but not limited to one or more of the following: performing a validatable information set generation process (e.g., process 800, as illustrated in Figures 7 and 8A); performing a first setup process (e.g., process 810, as illustrated in Figures 8A and 8B); performing a second setup process (e.g., process 820, as illustrated in Figures 8 A and 8C); generating an information set or a final information set (e.g., process 830, as illustrated in Figures 8A and 8D); performing an information set validation process (e.g., process 900, as illustrated in Figures 7 and 9A); performing an extraction process (e.g., process 910, as illustrated in Figures 9A and 9B); executing a deep link extracted from a final payload (e.g., process 920, as illustrated in Figures 9A and 9C); and performing a validation process (e.g., process 930, as illustrated in Figures 9A and 9D). It is to be understood in the present disclosure that one or more elements, actions, and/or aspects of example embodiments may include and/or implement, in part or in whole, solely and/or in cooperation with other elements, using, for example, networking technologies, cloud computing, distributed ledger technology (DLT) (e.g., blockchain), artificial intelligence (Al), machine learning, deep learning, encryption, hashing, etc. Furthermore, although example embodiments described in the present disclosure may be mostly described as pertaining to exchanges of value (e.g., gifting of a certain amount of fiat currency (e.g., USD 50 or other amount or currency) from one user (e.g., giver 10) to another user (e.g., recipient 10), such as the giving of red envelopes for Chinese New Year), it is to be understood in the present disclosure that example embodiments are not limited to such, and may also be directed to exchanges of information (e.g., textual messages, graphical images, photos, videos, etc.), exchanges of digital assets (e.g., cryptocurrencies (e.g., Bitcoin, Ethereum, etc.), non-fungible tokens (NFT), other digital tokens, etc.), etc. without departing from the teachings of the present disclosure. Furthermore, as used in the present disclosure, the terms "encrypting", "encryption", and "encrypt" are terms known in the art and, where applicable, may refer to a conversion of an input, via a secret key, into a series of characters (or encrypted input) in such a way that the input can be readily recovered (or decrypted) from the encrypted input via the secret key. Furthermore, the terms "hashing" and "hash", or the like, is a term known in the art and, where applicable, may refer to a transformation or mapping of an input into a fixed-length string or series of characters (e.g., by using a hashing algorithm, hashing function, or the like).

[0031] Example embodiments will now be described below with reference to the accompanying figures, which form a part of the present disclosure.

[0032] Example embodiments of a system (e.g., system 100).

[0033] FIGURE 1 illustrates an example embodiment of a system (e.g., system 100) for setting up, managing, updating, validating, and/or authenticating information and/or information sets (as described in the present disclosure). The system 100 is configurable or configured to perform a variety of actions, functions, methods, and/or processes including, but not limited to, enabling users 10 (e.g., users 10 using a mobile device 10) to interact with, store, amend, transport, transfer, withdraw, and/or receive information and/or information sets. Such information and/or information sets may include, but are not limited to, data/information, instructions, requests, interactions, transactions, messages, photos, graphics, video, value (e.g., fiat currency such as Singapore Dollars or SGD, US Dollars or USD, etc.), digital assets (e.g., cryptocurrencies and digital tokens such as Bitcoin or BTC, Ethereum or ETH, etc.), information sets, and/or the like (each as applicable) (referred to herein as "information" or "transactions"). The system 100 also enables users 10 to select, store, configure, setup, generate, update, amend, and/or validate information by scanning or capturing of information sets (e.g., information set 130, as illustrated in Figure 4; referred to herein as an "information set" 130, "first information set" 130, "final information set" 130, or the like); validate (or authenticate) the authenticity of information, including information sets 130; validate the completeness of information, including information sets 130; and/or validate the origin/source of information, including information sets 130.

[0034] For example, the system 100 may securely generate, setup, configure, transfer, update/change, cancel, and/or validate information sets 130. Information sets 130 can be used by users 10 to interact with, store, transport, transfer, receive, update/change, and/or cancel information. As will be further described in the present disclosure, an example embodiment of the system 100 may include one or more setup processors (e.g., first setup processor 200 and/or second setup processor 300) configurable or configured to perform, among other things, the configuring, setting up, generating, and/or updating of unique information sets. Thereafter, each unique information set may be configurable or configured by users 10 (e.g., a first user 10 using a mobile device 10) to include one or more payloads that include information (and/or a representation of and/or reference/link to the information) (referred to herein as a "payload", "first payload", "information payload", or the like). The first user 10 may then transfer or give the information (e.g., transfer a certain amount of value, such as USD 50; transfer or give a message, such as a birthday greeting; transfer or give an image, graphic, and/or video; etc.) to a second user 10 by providing, sending, transferring, giving, or the like, the information set 130 to the second user 10. To access the payload (i.e., the information stored therein), a validation process (e.g., validation process 900, as illustrated in Figure 7) is first performed by the system 100 so as to validate the information set 130. The validation process 900 ensures, among other things, that the information set 130 was generated by the setup processors 200, 300 of the system 100, the information set 130 is valid and/or authentic (and/or not tampered with); the information in the information set 130 is complete; and/or the information in the information set is valid (e.g., has not yet been transferred (or used, spent, consumed, redeemed, received, etc.), such as to another user 10, the first user 10, and/or the second user 10).

[0035] To perform the actions, functions, processes, and/or methods described above and in the present disclosure, example embodiments of the system 100 include one or more elements. For example, the system 100 includes one or more first setup processors (e.g., first setup processor 200) configurable or configured to perform, among other things, a first setup process. As will be further described in the present disclosure, the first setup process includes generating, among other things, a first payload (or also referred to as a payload), a first encrypted payload, and a first encrypted payload identifier (or also referred to as an encrypted payload identifier) that is associated with the first encrypted payload. The system 100 also includes one or more second setup processors (e.g., second setup processor 300) configurable or configured to perform, among other things, a second setup process. As will be further described in the present disclosure, the second setup process includes generating, among other things, a second encrypted payload, a final payload, and a final unique QR code encoded with the final payload. The system 100 also includes one or more information set generators (e.g., information set generators 400) configurable or configured to perform, among other things, the generating of information sets 130 (or also referred to as final information sets 130) based on one or more results of the first and second setup processes. For example, as will be further described in the present disclosure, the information set generator 400 is configurable or configured to generate information sets 130 that each include one or more unique QR codes (e.g., unique QR code 130a, as illustrated in Figure 4, or any other unique code such as a barcode, etc.) and one or more encrypted payload identifiers (e.g., encrypted payload identifier 130b, as illustrated in Figure 4), which are generated by the second setup processor 300 and first setup processor 200, respectively. The system 100 also includes one or more validation processors (e.g., validation processor 500) configurable or configured to perform, among other things, the validating of information sets 130 (e.g., to confirm the information set 130 was indeed generated by the information set generator 400, is valid and/or authentic, has not been tampered with, is not an unauthorized information set (e.g., fake, counterfeit, etc.), etc.).

[0036] The system 100 may also include one or more information set distributors (e.g., information set distributor 600) configurable or configured to perform, among other things, the printing, forming, distributing, and/or making available of information sets 130 (including those generated by the information set generator 400). For example, the information set distributor 600 may be in the form of a vending machine, or the like. The system 100 may also include and/or communicate with one or more networks, communication channels, or the like (e.g., communication channel 120 or network 120), which may be used to enable communication between elements of the system 100. For example, when a mobile device 10 of a first user 10 receives an information set 130, the communication channel 120 or network 120 may be used to communicate one or more elements of the information set 130 (and/or information derived, obtained, decoded, decrypted, and/or generated from the information set 130) to the validation processor 500 to validate the information set 130. It is to be understood in the present disclosure that when the information set 130 is provided to the first user 10 by a second user 10 in the form of a printout (e.g., a red envelope; or displayed on a mobile device 10 of the second user 10, such as a virtual red envelope), the first user 10 "receives" or is provided with the information set 130 by capturing, scanning, or the like, the information set 130 (e.g., using a camera of the mobile device 10 of the first user 10). Alternatively or in addition, the information set 130 may be provided to the first user 10 by the second user 10 within and/or in the form of an electronic message, email, SMS, instant message, or the like. The system 100 may also include and/or communicate with one or more databases, distributed ledgers, or the like (e.g., database 110), which may be configurable or configured to store, among other things, information sets 130, unique QR codes 130a, other types of codes 130a, encrypted payload identifiers 130b, payloads, secret keys (e.g., first secret keys used by and/or for the first encryption engine 204 (as illustrated in Figure 2) to encrypt payloads and used by and/or for the first decryption engine 503 (as illustrated in Figure 6) to decrypt first encrypted payloads; second secret keys used by and/or for the second encryption engine 304 (as illustrated in Figure 2) to encrypt payloads and used by and/or for the second decryption engine 504 (as illustrated in Figure 6) to decrypt second encrypted payloads); etc. The system 100 may also include and/or communicate with one or more users 10, mobile devices 10, computing devices 10, communication devices 10, merchants 10, financial institutions, or the like.

[0037] Although the figures may illustrate the system 100 as having one first setup processor 200, one second setup processor 300, one information set processor 400, one validation processor 500, one information set distributor 600, one network 120 or communication channel 120, and two databases 110, it is to be understood that the system 100 may include more or less than one first setup processor 200, more or less than one second setup processor 300, more or less than one information set processor 400, more or less than one validation processor 500, more or less than one information set distributor 600, more or less than one network 120 or communication channel 120, and more or less than two databases 110 without departing from the teachings of the present disclosure. For example, the system 100 may include one or more first setup processors 200 configurable or configured to perform some, most, and/or all of the functions of the second setup processor 300, information set generator 400, and/or validation processor 500. As another example, the system 100 may include one or more second setup processors 300 configurable or configured to perform some, most, and/or all of the functions of the first setup processor 200, information set generator 400, and/or validation processor 500. As another example, the system 100 may include one or more information set generators 400 configurable or configured to perform some, most, and/or all of the functions of the first setup processor 200, second setup processor 300, and/or validation processor 500. As another example, the system 100 may include one or more validation processors 500 configurable or configured to perform some, most, and/or all of the functions of the first setup processor 200, second setup processor 300, and/or information set generator 400. Each of the elements of the system 100 may be configurable or configured to connect to, communicate with, and/or receive communications from one or more users 10, one or more computing devices 10, one or more databases 110, one or more networks 120, and/or one or more external systems (not shown, such as a transaction processor for a financial institution, payment processor, payment gateway, POS, and/or the like).

[0038] As used in the present disclosure, when applicable, a reference to a system 100 (and/or one or more of its elements), first setup processor 200 (and/or one or more of its elements), second setup processor 300 (and/or one or more of its elements), information set generator 400 (and/or one or more of its elements), and/or validation processor 500 (and/or one or more of its elements) may also refer to, apply to, and/or include one or more computing devices, processors, servers, systems, cloud-based computing, or the like, and/or functionality of one or more processors, computing devices, servers, systems, cloud-based computing, or the like. The system 100 (and/or one or more of its elements), first setup processor 200 (and/or one or more of its elements), second setup processor 300 (and/or one or more of its elements), information set generator 400 (and/or one or more of its elements), and/or validation processor 500 (and/or one or more of its elements) may be or have any processor, server, system, device, computing device, controller, microprocessor, microcontroller, microchip, semiconductor device, or the like, configurable or configured to perform, among other things, the generating and/or updating of payloads; encrypting (and/or hashing) of payloads using first secret keys to arrive at first encrypted payloads; generating of encrypted payload identifiers 130b; generating of associations between first encrypted payloads and encrypted payload identifiers 130b; encrypting (and/or hashing) of payloads using second secret keys to arrive at second encrypted payloads; generating of final payloads having second encrypted payloads and deep links (e.g., a deep link may include instructions and/or links for a mobile device 10 to, among other things, launch a particular mobile app (e.g., DBS Digibank app, other financial institution mobile apps, payment apps such as PayPal, electronic wallets, cryptocurrency-related app, etc.; or launch a mobile app platform or store (e.g., Apple App Store, Google Play Store, etc.) to download a particular mobile app) and/or perform a particular functionality or action including, but not limited to, establishing a communication channel between the mobile device 10 and a validation processor (e.g., validation processor 500) and transmitting certain information (a second encrypted payload and a first encrypted payload identifier, as obtained from a final information set) along the communication channel to the validation processor 500); encoding of final unique QR codes 130a (or any other unique code 130a) with final payloads (e.g., in such a way that, when a mobile device 10 scans the final unique QR code 130a, the mobile device 10 obtains the final payload, including the second encrypted payload and the deep link); generating of final information sets 130 having final unique QR codes 130a and first encrypted payload identifiers 130b, and/or any one or more other actions, functions, methods, and/or processes described above and in the present disclosure. Alternatively, or in addition, the system 100, first setup processor 200 (and/or one or more of its elements), second setup processor 300 (and/or one or more of its elements), information set generator 400 (and/or one or more of its elements), and/or validation processor 500 (and/or one or more of its elements) may include and/or be a part of a virtual machine, processor, computer, node, instance, host, or machine, including those in a networked computing environment.

[0039] As used in the present disclosure, a communication channel 110, network 110, cloud 110, or the like, may be or include a collection of devices and/or virtual machines connected by communication channels that facilitate communications between devices and allow for devices to share resources. Such resources may encompass any types of resources for running instances including hardware (such as servers, clients, mainframe computers, networks, network storage, data sources, memory, central processing unit time, scientific instruments, and other computing devices), as well as software, software licenses, available network services, and other non-hardware resources, or a combination thereof. A communication channel 110, network 110, cloud 110, or the like, may include, but is not limited to, computing grid systems, peer to peer systems, mesh-type systems, distributed computing environments, cloud computing environment, telephony systems, voice over IP (VoIP) systems, voice communication channels, voice broadcast channels, text-based communication channels, video communication channels, etc. Such communication channels 110, networks 110, clouds 110, or the like, may include hardware and software infrastructures configured to form a virtual organization comprised of multiple resources which may be in geographically disperse locations. Communication channel 110, network 110, cloud 110, or the like, may also refer to a communication medium between processes on the same device. Also as referred to herein, a network element, node, or server may be a device deployed to execute a program operating as a socket listener and may include software instances.

[0040] These and other elements of the system 100 will now be further described with reference to the accompanying figures.

[0041] The first setup processor (e.g., first setup processor 200).

[0042] As illustrated in at least Figure 1, the system 100 for setting up, managing, updating, and validating information and/or information sets includes one or more first setup processors (e.g., first setup processor 200). The first setup processor 200 is configurable or configured to perform, among other things, a first setup process (e.g., process 810, as illustrated in Figure 8B). The first setup processor 200 is configurable or configured to generate a pay load (e.g., first payload). Alternatively, the first setup processor 200 may obtain/retrieve and/or receive an already generated or pre-generated payload. The first setup processor 200 is also configurable or configured to encrypt the payload (e.g., encrypt the first payload using a first secret key) to arrive at an encrypted payload (e.g., first encrypted payload). The first setup processor 200 is also configurable or configured to generate an encrypted payload identifier (e.g., first encrypted payload identifier). Alternatively, the first setup processor 200 may obtain/retrieve and/or receive an already generated or pre-generated encrypted payload identifier. The first setup processor 200 is also configurable or configured to generate an association, link, relation, or the like (referred to herein as an "association") between the encrypted payload and the encrypted payload identifier (e.g., association between the first encrypted payload and the first encrypted payload identifier).

[0043] To perform the actions, functions, processes, and/or methods described above and in the present disclosure, example embodiments of the first setup processor 200 include one or more elements. For example, as illustrated in FIGURE 2, the first setup processor 200 includes one or more payload processors (e.g., payload processor 202). The first setup processor 200 also includes one or more first encryption engines (e.g., first encryption engine 204). The first setup processor 200 also includes one or more payload identifier processors (e.g., payload identifier processor 206). The first setup processor 200 also includes one or more association engines (e.g., association engine 208). Although the figures may illustrate one payload processor 202, one first encryption engine 204, one payload identifier processor 206, and one association engine 208, it is to be understood that the first setup processor 200 may include more or less than one payload processor 202, more or less than one first encryption engine 204, more or less than one payload identifier processor 206, and/or more or less than one association engine 208 without departing from the teachings of the present disclosure. It is also to be understood in the present disclosure that, although the actions, functions, processes, and/or methods performed by the first setup processor 200 may be described in the present disclosure as being performed by one or more particular elements of the first setup processor 200, the actions, functions, processes, and/or methods performed by a particular element of the first setup processor 200 may also be performed by one or more other elements and/or cooperatively performed by more than one element of the first setup processor 200 (and/or other elements of the system 100) without departing from the teachings of the present disclosure. It is also to be understood in the present disclosure that, although the actions, functions, processes, and/or methods performed by the first setup processor 200 are described in the present disclosure as being performed by particular elements of the first setup processor 200, the actions, functions, processes, and/or methods performed by two or more particular elements of the first setup processor 200 may be combined and performed by one element of the first setup processor 200 without departing from the teachings of the present disclosure.

[0044] These elements of the first setup processor 200 will now be further described with reference to the accompanying figures.

[0045] The payload processor (e.g., payload processor 202),

[0046] As illustrated in Figure 2, an example embodiment of the first setup processor 200 includes one or more payload processors (e.g., payload processor 202). The payload processor 202 is configurable or configured to generate a pay load (e.g., first payload). The payload may be or include any unique information. For example, the pay load may be or include a unique series of characters, alphanumeric characters, numbers, letters (e.g., in English and/or other languages), and/or the like. Alternatively or in addition, the payload may be randomly generated. The payload may be of any length, and may be application/requirement-specific (e.g., selected based on the number of unique payloads required). For example, the payload may be a series of 18-24 characters, or more or less. Alternatively or in addition, the payload may be or include one or more symbols, codes, images, or the like. The pay load may also include editable, configurable, customizable, and/or settable information and/or information fields and/or categories, such as a payload identifier (e.g., the aforementioned unique series of 18-24 characters), status (e.g., valid, deposited, transferred, pending, redeemed, expired, etc.), transaction/action type (e.g., transfer funds, send or display message/information, etc.), quantity or value (if applicable) (e.g., USD 100), geographical restrictions (if any), creation/setup/configure/initial validation date (e.g., date that a gifter/sender user adds/loads value, uploads a message, etc.), redeem/receive/final validation date (e.g., date that a receiver/recipient user accepts the added/loaded value, receives the uploaded message, etc.), expiry date or redeemable period (or final validation date), a corresponding/associated encrypted payload identifier (e.g., first encrypted payload identifier, as generated by the payload identifier processor 206), etc. Alternatively, the payload may include a pointer, reference, relation, association, link, or the like ("association", "associated", etc.), to another payload (e.g., information pay load, which may also be stored in a first database 110) that includes the editable, configurable, customizable, and/or settable information and/or information fields and/or categories, such as the payload identifier (e.g., the unique series of 18-24 characters), the status (e.g., valid, deposited, transferred, pending, redeemed, expired, etc.), the transaction/action type (e.g., transfer funds, send or display message/information, etc.), the quantity or value (if applicable) (e.g., USD 100), the geographical restrictions (if any), the creation/setup/configure/initial validation date (e.g., date that a gifter/sender user adds/loads value, uploads a message, etc.), the redeem/receive/final validation date (e.g., date that a receiver/recipient user accepts the added/loaded value, receives the uploaded message, etc.), the expiry date or redeemable period (or final validation date), a corresponding/associated encrypted payload identifier (e.g., first encrypted payload identifier, as generated by the payload identifier processor 206), etc. As used in the present disclosure, a reference to a payload may also include any one or more information payloads that is associated to the payload.

[0047] It is to be understood in the present disclosure that the payload processor 202 may also obtain/retrieve and/or receive an already or previously generated payload.

[0048] After the payload processor 202 generates and/or obtains the payload, the pay load processor 202 is configurable or configured to store the pay load, such as in a first database 110, or the like. Alternatively or in addition, the pay load processor 202 is configurable or configured to provide and/or make available the payload to the first encryption engine 204 and the second setup processor 300 (i.e., the information selector 302 and/or the second encryption engine 304). The payload processor 202 may also provide the payload to one or more other elements of the system 100.

[0049] The first encryption engine (e.g., first encryption engine 204),

[0050] As illustrated in Figure 2, an example embodiment of the first setup processor 200 includes one or more first encryption engines (e.g., first encryption engine 204). The first encryption engine 204 is configurable or configured to receive the payload from the payload processor 202 (and/or the first database 110), and encrypt the payload to arrive at a first encrypted pay load. In an example embodiment, the first encrypted payload is different from the second encrypted payload generated by the second encryption engine 304 (as described in the present disclosure). The first encrypted payload may be obtained by encrypting the payload with a first secret key. In an example embodiment, the first secret key is a different secret key than the second secret key used by the second encryption engine 304 to generate the second encrypted payload (as described in the present disclosure); or put differently, the first secret key cannot decrypt the second encrypted payload, and the second secret key cannot decrypt the first encrypted payload. It is to be understood in the present disclosure that the encryption of the payload to arrive at the first encrypted payload may be performed using any encryption algorithm or methodology known in the art. For example, the encryption algorithm may include, but are not limited to, Advanced Encryption Standard (AES), Triple Data Encryption Standard (TripleDES), Blowfish Encryption Algorithm, RSA Security, IDEA Encryption Algorithm, MD5 Encryption Algorithm, HMAC Encryption Algorithm, Twofish Encryption Algorithm, etc.

[0051] After the first encryption engine 204 generates the first encrypted payload, the first encryption engine 204 is configurable or configured to store the first encrypted payload, such as in the first database 110, or the like. The first encryption engine 204 is also configurable or configured to provide and/or make available the first encrypted payload to the association engine 208 (for association with the first payload identifier, as described in the present disclosure). The first encryption engine 204 may also provide the first encrypted payload to one or more other elements of the system 100.

[0052] The payload identifier processor (e.g., payload identifier processor 206),

[0053] As illustrated in Figure 2, an example embodiment of the first setup processor 200 includes one or more payload identifier processors (e.g., pay load identifier processor 206). The payload identifier processor 206 is configurable or configured to generate an encrypted payload identifier (e.g., first encrypted payload identifier). The encrypted payload identifier may be or include any unique information. For example, the encrypted payload identifier may be a unique series of characters, alphanumeric characters, numbers, letters (e.g., in English and/or other languages), and/or the like. Alternatively or in addition, the encrypted payload identifier may be a series of randomly generated characters, alphanumeric characters, numbers, letters (e.g., in English and/or other languages), and/or the like. The encrypted payload identifier may be of any length, and may be application/requirement- specific (e.g., selected based on the number of unique encrypted payload identifiers required). For example, the encrypted payload identifier may be or include a series of 5-10 characters, or more or less. Alternatively or in addition, the encrypted payload identifier may be or include one or more symbols, codes, images, or the like.

[0054] It is to be understood in the present disclosure that the payload identifier processor 206 may also obtain/retrieve and/or receive an already or previously encrypted payload identifier.

[0055] After the payload identifier processor 206 generates and/or obtains the encrypted pay load identifier, the payload identifier processor 206 is configurable or configured to store the encrypted payload identifier, such as in the first database 110, or the like. Alternatively or in addition, the payload identifier processor 206 is configurable or configured to provide and/or make available the encrypted payload identifier to the association engine 208 and the information set generator 400. The payload identifier processor 206 may also provide the encrypted payload identifier to one or more other elements of the system 100.

[0056] The association engine (e.g., association engine 208),

[0057] As illustrated in Figure 2, an example embodiment of the first setup processor 200 includes one or more association engines (e.g., association engine 208). The association engine 208 is configurable or configured to receive the first encrypted payload from the first encryption engine 204 (and/or the first database 110). The association engine 208 is also configurable or configured to receive the encrypted pay load identifier from the payload identifier processor 206 (and/or the first database 110). The association engine 208 is then configurable or configured to generate or create an association between the first encrypted payload and the encrypted payload identifier. It is to be understood that an association between the first encrypted payload and the encrypted payload identifier may be any association, reference, relation, link, or the like, that enables the encrypted payload to be obtained based on the first encrypted pay load identifier, and vice versa. For example, when the first encrypted payload and the encrypted payload identifier are associated, the association search engine 502 (see Figure 6) of the validation processor 500 may readily obtain the first encrypted payload based on a search (e.g., search of the first database 110) using the first encrypted payload identifier as a search query.

[0058] After the association engine 208 generates the association between the first encrypted payload and the encrypted payload identifier, the association engine 208 is configurable or configured to store the generated association, such as in the first database 110, or the like. Alternatively or in addition, the association engine 208 is configurable or configured to provide and/or make available the association between the first encrypted payload and the encrypted payload identifier to the association search engine 502. The association engine 208 may also provide the association between the first encrypted payload and the encrypted payload identifier to one or more other elements of the system 100.

[0059] The second setup processor (e.g., second setup processor 300).

[0060] As illustrated in at least Figure 1, the system 100 for setting up, managing, updating, and validating information and/or information sets includes one or more second setup processors (e.g., second setup processor 300). The second setup processor 300 is configurable or configured to perform, among other things, a second setup process (e.g., process 820, as illustrated in Figure 8C). The second setup processor 300 is configurable or configured to encrypt the pay load (e.g., encrypt the first payload using a second secret key, which is different from the first secret key used by the first encryption engine 204) to arrive at an encrypted payload (e.g., second encrypted payload, which is different from the first encrypted payload generated by the first encryption engine 204). The second setup processor 300 is also configurable or configured to generate final payload. The final pay load may include the second encrypted payload and a deep link. The second setup processor 300 is also configurable or configured to encode a final unique QR code with the final payload, that is, encode the final unique QR code with the second encrypted payload and a deep link.

[0061] To perform the actions, functions, processes, and/or methods described above and in the present disclosure, example embodiments of the second setup processor 300 include one or more elements. For example, as illustrated in FIGURE 3, the second setup processor 300 may include one or more information selectors (e.g., information selector 302). The second setup processor 300 may also include one or more second encryption engines (e.g., second encryption engine 304). The second setup processor 300 may also include one or more final payload processors (e.g., final payload processor 306). The second setup processor 300 may also include one or more final unique QR code processors (e.g., final unique QR code processor 308). Although the figures may illustrate one information selector 302, one second encryption engine 304, one final payload processor 306, and one final unique QR code processor 308, it is to be understood that the second setup processor 300 may include more or less than one information selector 302, more or less than one second encryption engine 304, more or less than one final payload processor 306, and more or less than one final unique QR code processor 308 without departing from the teachings of the present disclosure. It is also to be understood in the present disclosure that, although the functions and/or processes performed by the second setup processor 300 are described in the present disclosure as being performed by particular elements of the second setup processor 300, the functions and/or processes performed by a particular element of the second setup processor 300 may also be performed by one or more other elements and/or cooperatively performed by more than one element of the second setup processor 300 (and/or other elements of the system 100) without departing from the teachings of the present disclosure. It is also to be understood in the present disclosure that, although the functions and/or processes performed by the second setup processor 300 are described in the present disclosure as being performed by particular elements of the second setup processor 300, the functions and/or processes performed by two or more particular elements of the second setup processor 300 may be combined and performed by one element of the second setup processor 300 without departing from the teachings of the present disclosure.

[0062] These elements of the second setup processor 300 will now be further described with reference to the accompanying figures.

[0063] The information selector (e.g., information selector 302),

[0064] As illustrated in Figure 3, an example embodiment of the second setup processor 300 includes one or more information selectors (e.g., information selector 302). The information selector 302 is configurable or configured to select, obtain, and/or receive information required by the other elements of the second setup processor 300.

[0065] For example, the information selector 302 is configurable or configured to obtain payloads (e.g., first payload) from the payload processor 202 (and/or from the first database 110). Alternatively or in addition, the information selector 302 is configurable or configured to obtain payloads (e.g., first payload) by first obtaining first encrypted payloads from the first encryption engine 304 (and/or from the first database 110), followed by decrypting each first encrypted pay load to arrive at the payload (e.g., first payload). It is to be understood that such decrypting of the first encrypted payload may be performed by the information selector 302, the first decryption engine 503 (see Figure 6), and/or one or more other elements of the system 100.

[0066] Once the information selector 302 obtains the payloads, the information selector 302 is configurable or configured to provide and/or make available the payloads to the second encryption engine 304 (and may also provide and/or make available the payload to one or more other elements of the system 100). In some example embodiments, the payload (from the payload processor 202; from a decryption of the first encrypted payload; and/or from the first database 110) may also be provided directly to the second encryption engine 304 (i.e., without first providing the pay load to the information selector 302).

[0067] The information selector 302 is also configurable or configured to obtain deep links (which may be generated by the information selector 302 and/or one or more other elements of the system 100), as described in the present disclosure. The deep link may be and/or include instructions and/or links for a mobile device 10 to, among other things, launch a particular mobile app (e.g., DBS Digibank app, other financial institution mobile apps, payment apps such as PayPal, electronic wallets, etc.; or launch a mobile app platform (e.g., Apple App Store, Google Play Store, etc.) to download such particular mobile app) and/or perform a particular functionality and/or action including, but not limited to, establishing a communication channel between the mobile device 10 and a validation processor (e.g., validation processor 500) and transmitting certain information (a second encrypted payload and a first encrypted payload identifier, both of which is obtained from a final information set, as described in the present disclosure) along the communication channel to the validation processor 500. The information selector 302 is then configurable or configured to provide and/or make available the deep link to the final payload processor 306 (and/or one or more other elements of the system 100). In some example embodiments, the deep link may also be provided directly to or generated by the final pay load processor 306 (i.e., without first providing the deep link to the information selector 302).

[0068] The second encryption engine (e.g., second encryption engine 304),

[0069] As illustrated in Figure 3, an example embodiment of the second setup processor 300 includes one or more second encryption engines (e.g., second encryption engine 304). The second encryption engine 304 is configurable or configured to receive pay loads (e.g., first payload) from the information selector 302. Alternatively or in addition, the second encryption engine 304 is configurable or configured to receive payloads directly from the payload processor 202 (and/or the first database 110). Alternatively or in addition, the second encryption engine 304 is configurable or configured to obtain payloads by first obtaining first encrypted payloads from the first encryption engine 304 (and/or from the first database 110), followed by decrypting each first encrypted payload to arrive at the payload. It is to be understood that such decrypting of the first encrypted payload to arrive at the payload may be performed by the information selector 302, second encryption engine 304, the first decryption engine 503 (see Figure 6), and/or one or more other elements of the system 100. 1 [0070] After the second encryption engine 304 receives/obtains the payload, the second encryption engine 304 is configurable or configured to encrypt the payload to arrive at a second encrypted payload. In an example embodiment, the second encrypted payload (i.e., the encrypted result after the pay load is encrypted by the second encryption engine 304) is different from the first encrypted payload generated by the first encryption engine 204 (i.e., the encrypted result after the payload is encrypted by the first encryption engine 204). The second encrypted payload may be obtained by encrypting the payload with a second secret key. In an example embodiment, the second secret key is a different secret key than the first secret key used by the first encryption engine 204 to generate the first encrypted payload (as described in the present disclosure); or put differently, the second secret key cannot decrypt the first encrypted payload, and the first secret key cannot decrypt the second encrypted payload. It is to be understood in the present disclosure that the encryption of the payload to arrive at the second encrypted payload may be performed using any encryption algorithm or methodology known in the art. For example, the encryption algorithm may include, but are not limited to, Advanced Encryption Standard (AES), Triple Data Encryption Standard (TripleDES), Blowfish Encryption Algorithm, RSA Security, IDEA Encryption Algorithm, MD5 Encryption Algorithm, HMAC Encryption Algorithm, Twofish Encryption Algorithm, etc. The encryption algorithm used by the second encryption engine 304 may be the same as or different from the encryption algorithm used by the first encryption engine 204.

[0071] After the second encryption engine 304 generates the second encrypted payload, the second encryption engine 304 is configurable or configured to store the second encrypted payload, such as in the second database 110, or the like. Alternatively or in addition, the second encryption engine 304 is configurable or configured to provide and/or make available the second encrypted payload to the final pay load processor 306 (for generating the final pay load), as described in the present disclosure. The second encryption engine 304 may also provide the second encrypted payload to one or more other elements of the system 100.

[0072] The final payload processor (e.g., final payload processor 306),

[0073] As illustrated in Figure 3, an example embodiment of the second setup processor 300 includes one or more final payload processors (e.g., final payload processor 306). The final payload processor 306 is configurable or configured to receive second encrypted payloads from the second encryption engine 304 (and/or the second database 110). The final payload processor 306 is also configurable or configured to obtain (e.g., from another element of the system 100, such as the information selector 302) or generate deep links. In this regard, each deep link may be and/or include instructions, commands, code, links, and/or the like, for a computing device 10 (e.g., a mobile device 10) that receives the deep link (e.g., extracts the deep link from the final unique QR code, as described in the present disclosure) to, among other things, visit or launch a website, link, or the like; launch a particular installed app (e.g., DBS Digibank app, other financial institution apps, payment apps such as PayPal, electronic wallets, social media apps such as Facebook, WeChat, Line, etc.); login to a particularly installed app, website, and/or the like; launch an app distribution platform or store (e.g., Apple App Store, Google Play Store, etc.) to download, install, register, and/or login to a particular app; establish a communication channel (e.g., a first communication channel) between a mobile device 10 of the user 10 and the validation processor 500; and/or transmit, from the mobile device 10 of the user 10 to the validation processor 500, data extracted and/or obtained from the final information set 130 (including the second encrypted payload and the first encrypted payload identifier 130b).

[0074] After the final payload processor 306 receives/obtains the second encrypted payload and the deep link, the final pay load processor 306 is configurable or configured to generate a final payload. The final payload includes the second encrypted payload and the deep link. Once the final payload is generated, the final payload may be stored, such as in the second database 110, or the like. Alternatively or in addition, the final payload processor 306 is configurable or configured to provide and/or make available the final pay load to the final unique QR code processor 308 (for encoding into the final unique QR code, as described in the present disclosure). The final payload processor 306 may also provide the final payload to one or more other elements of the system 100. Alternatively, the second encrypted payload and the deep link may be provided directly to the final unique QR code processor 308 (e.g., from the second encryption engine 304 and the information selector 302, respectively) without requiring the final payload processor 306 to generate the final pay load.

[0075] The final unique OR code processor (e.g., final unique OR code processor 308), [0076] As illustrated in Figure 3, an example embodiment of the second setup processor 300 includes one or more final unique QR code processors (e.g., final unique QR code processor 308). The final unique QR code processor 308 is configurable or configured to receive final pay loads from the final payload processor 306. Alternatively or in addition, the final unique QR code processor 308 may receive second encrypted payloads (e.g., from the second encryption engine 304 and/or the second database 110) and deep links (e.g., from one or more elements of the system 100, such as the information selector 302).

[0077] After the final unique QR code processor 308 receives/obtains the final payload, the final unique QR code processor 308 is configurable or configured to encode the final payload (as generated by the final pay load processor 306) into a unique QR code so as to arrive at a final unique QR code (e.g., final unique QR code 130a, as illustrated in Figure 4). That is, the final unique QR code processor 308 is configurable or configured to generate a final unique QR code 130a having the final payload encoded in the final unique QR code 130a.

[0078] In example embodiments where the final unique QR code processor 308 receives the second encrypted payload (e.g., from the second encryption engine 304 and/or the second database 110) and the deep link (e.g., from one or more elements of the system 100, such as the information selector 302), the final unique QR code processor 308 is configurable or configured to encode the second encrypted payload and the deep link into a unique QR code so as to arrive at a final unique QR code (e.g., final unique QR code 130a, as illustrated in Figure 4). That is, the final unique QR code processor 308 is configurable or configured to generate a final unique QR code 130a having the second encrypted payload and the deep link encoded in the final unique QR code 130a.

[0079] As used in the present disclosure, an "encoding", "coding", or the like, of information (e.g., the final payload; and/or the second encrypted payload and the deep link) into a final unique QR code 130a refers to a configuring, setting up, generating, creating, or the like, of a unique QR code in such a way that, when such configured unique QR code is scanned by a QR code scanner (e.g., a mobile device 10 with a camera that is configured to scan QR codes), the QR code scanner is able to decode such configured unique QR code so as to obtain, result in, and/or arrive at the information (e.g., the final payload, the second encrypted payload, and/or the deep link). Furthermore, as used in the present disclosure, a final unique QR code 130a may be a reusable unique QR code or a one-time use QR code.

[0080] The information set generator (e.g„ information set generator 400).

[0081] As illustrated in at least Figure 1, the system 100 for setting up, managing, updating, and validating information and/or information sets includes one or more information set generators (e.g., information set generator 400). The information set generator 400 is configurable or configured to perform, among other things, the generating of information sets 130 (or final information sets 130) (e.g., process 830, as illustrated in Figure 8D). [0082] In an example embodiment, the information set generator 400 is configurable or configured to obtain and/or receive final unique QR codes 130a. Each final unique QR code 130a may be generated by the final unique QR code processor 308 of the second setup processor 300 and provided to the information set generator 400, as illustrated in Figure 3. As described in the present disclosure, the final unique QR code 130a may be a unique QR code encoded with the final payload, which includes the second encrypted payload and a deep link.

[0083] The information set generator 400 is also configurable or configured to obtain and/or receive first encrypted payload identifiers 130b (i.e., the first encrypted payload identifiers 130b associated with the first encrypted payload). Each first encrypted payload identifier 130b may be generated by the pay load identifier processor 206 of the first setup processor 300 and provided to the information set generator 400, as illustrated in Figure 3. As described in the present disclosure, the first encrypted payload identifier may be a unique series of characters, such as a unique series of between 5 to 15 characters, or more or less; and the first encrypted payload identifier is associated with the first encrypted payload in such a way that the first encrypted payload identifier is obtainable (e.g., from the first database 110) based on a search using the first encrypted payload identifier as the search query.

[0084] Once the information set generator 400 receives the final unique QR code 130a and its corresponding first encrypted payload identifier 130b, the information set generator 400 is then configurable or configured to generate a final information set 130. As illustrated in FIGURE 4, the final information set 130 generated by the information set generator 400 includes the final unique QR code 130a and the first encrypted payload identifier 130b. Although the figures may illustrate the final information set 130 as having one final unique QR code 130a and one first encrypted payload identifier 130b, it is to be understood that the final information set 130 may include more than one final unique QR code 130a and/or more than one first encrypted payload identifier 130b without departing from the teachings of the present disclosure. Furthermore, although the figures may illustrate the final information set 130 as having an arrangement of the final unique QR code 130a provided above the first encrypted pay load identifier 130b, it is to be understood that the final unique QR code 130a and the first encrypted payload identifier 130b may be arranged in other arrangements without departing from the teachings of the present disclosure. For example, the first encrypted payload identifier 130b may also be provided above, to the left, or to the right of the final unique QR code 130a. [0085] The validation processor (e.g., validation processor 500).

[0086] As illustrated in at least Figure 1, the system 100 for setting up, managing, updating, and validating information and/or information sets includes one or more validation processors (e.g., validation processor 500). The validation processor 500 is configurable or configured to perform, among other things, a final information set validation process (e.g., process 900, as illustrated in Figure 9A). The final information set validation process 900 includes obtaining relevant information from final information sets 130 and performing validation of final information sets 130 (i.e., ones that are generated by the information set generator 400 and/or one or more elements of the system 100) based on such obtained relevant information. The validation processor 500 may also perform and/or execute one or more user desired actions after performing a successful validation (e.g., the validation process 930) including, but not limited to, adding, storing, amending, etc. of recipients 10 who will receive final information sets 130 (e.g., adding of a recipient 10 for each final information set 130, such as a adding a first user 10 as a recipient 10 of a red envelope 130; adding of multiple recipients 10 for multiple final information sets 130, such as adding first, second, and third users 10 as 3 recipients 10 of 3 red envelopes 130; adding of multiple recipients 10 for one final information set 130, such as adding of first, second, third, fourth, and fifth users 10 as recipients 10 for one red envelope 130 (e.g., in situations where a user 10 is giving monetary gifts to several recipients 10 using just one final information set 130)); adding, storing, amending, etc. of gifters/senders 10 who will give (or load) final information sets 130 (e.g., adding of a gifter 10 for each final information set 130, such as a adding a first user 10 as a gifter 10 of a red envelope 130; adding of multiple gifters 10 for multiple final information sets 130, such as adding first, second, and third users 10 as 3 gifters 10 of 3 red envelopes 130; adding of multiple gifters 10 for one final information set 130, such as adding of first, second, third, fourth, and fifth users 10 as gifters 10 for one red envelope 130 (e.g., in situations where multiple users 10 are combining together to give a monetary gift to one recipient 10 using just one final information set 130)); adding, storing, amending, etc. of information (e.g., loading of information, such as a message, picture, video, etc., into a final information set 130 and/or for association with a final information set 130); adding, storing, amending, etc. of value (e.g., loading of value, such as fiat currency or cryptocurrency, into a final information set 130 and/or for association with a final information set 130); performing of transactions; recording of transactions (e.g., in a database 110 and/or distributed ledger 110); etc. [0087] The final information set validation process 900 performed by the validation processor 500 includes performing an extraction process (e.g., process 910, as illustrated in Figure 9B) and a deep link execution process (e.g., process 920, as illustrated in Figure 9C). These processes 910, 920 are performable by a mobile device 10 that has received the information set 130 (i.e., the information set 130 that is being validated by the validation processor 500) and/or the validation processor 500. In this regard, the extraction process 910 first involves extracting a final unique QR code 130a and a first encrypted payload identifier 130b from the received information set 130. The extraction process 910 then includes decoding of the final unique QR code 130a to arrive at a final pay load. The extraction process 910 further includes extracting of a second encrypted pay load and a deep link from the final payload. In terms of the deep link execution process 920, the process 920 includes establishing a communication channel 120 between the mobile device 10 (i.e., the mobile device 10 that received the information set 130) and the validation processor 500. The deep link execution process 920 further includes transmitting, from the mobile device 10 to the validation processor 500 via the communication channel 120, the second encrypted pay load and the first encrypted payload identifier 130b extracted in the extraction process 910.

[0088] To perform the actions, functions, processes, and/or methods described above and in the present disclosure, example embodiments of the validation processor 500 include one or more elements. For example, as illustrated in FIGURE 5, the validation processor 500 includes one or more validation engines (e.g., validation engine 510) for performing the validation process 900. The validation engine 510 includes one or more information selectors (e.g., information selector 501). The validation engine 510 also includes one or more association search engines (e.g., association search engine 502). The validation engine 510 also includes one or more first decryption engines (e.g., first decryption engine 503). The validation engine 510 also includes one or more second decryption engines (e.g., second decryption engine 504). The validation engine 510 also includes one or more comparators (e.g., comparator 505). The validation engine 510 also includes one or more validators (e.g., validator 506). The validation processor 500 may also include one or more transaction processors (e.g., transaction processor 520) for performing, among other things, transactions, preparing for transactions, interactions with other systems and/or platforms (not shown), etc. Although the figures may illustrate one validation engine 510, one information selector 501, one association search engine 502, one first decryption engine 503, one second decryption engine 504, one comparator 505, one validator 506, and one transaction processor 520, it is to be understood that the validation processor 500 may include more or less than one validation engine 510, more or less than one information selector 501, more or less than one association search engine 502, more or less than one first decryption engine 503, more or less than one second decryption engine 504, more or less than one comparator 505, more or less than one validator 506, and more or less than one transaction processor 520 without departing from the teachings of the present disclosure. It is also to be understood in the present disclosure that, although the functions and/or processes performed by the validation processor 500 are described in the present disclosure as being performed by particular elements of the validation processor 500, the functions and/or processes performed by a particular element of the validation processor 500 may also be performed by one or more other elements and/or cooperatively performed by more than one element of the validation processor 500 (and/or other elements of the system 100) without departing from the teachings of the present disclosure. It is also to be understood in the present disclosure that, although the functions and/or processes performed by the validation processor 500 are described in the present disclosure as being performed by particular elements of the validation processor 500, the functions and/or processes performed by two or more particular elements of the validation processor 500 may be combined and performed by one element of the validation processor 500 without departing from the teachings of the present disclosure.

[0089] These elements of the validation processor 500 will now be further described with reference to the accompanying figures.

[0090] The validation engine (e.g., validation engine 510),

[0091] As illustrated in at least Figure 5, the validation processor 500 includes one or more validation engines (e.g., validation engine 510). The validation engine 510 includes one or more information selectors (e.g., information selector 501). The validation engine 510 also includes one or more association search engines (e.g., association search engine 502). The validation engine 510 also includes one or more first decryption engines (e.g., first decryption engine 503). The validation engine 510 also includes one or more second decryption engines (e.g., second decryption engine 504). The validation engine 510 also includes one or more comparators (e.g., comparator 505). The validation engine 510 also includes one or more validators (e.g., validator 506).

[0092] These elements of the validation engine 510 will now be further described with reference to the accompanying figures.

[0093] The information selector e.g-, information selector 501). [0094] As illustrated in Figure 6, an example embodiment of the validation engine 510 includes one or more information selectors (e.g., information selector 501). The information selector 501 is configurable or configured to receive, select, extract, and/or obtain information from the mobile device 10 that received the information set 130 (i.e., the information set 130 that is being validated by the validation processor 500). As described in the present disclosure, such mobile device 10 first receives the information set 130 (e.g., via scanning of the information set 130 using a camera of the mobile device 10). The mobile device 10 is then configurable or configured to perform an extraction process (e.g., extraction process 910). The extraction process 910 includes extracting a final unique QR code 130a and a first encrypted pay load identifier 130b from the received information set 130. The extraction process 910 also includes obtaining a final payload encoded in the final unique QR code 130a. This may be performed by decoding the final unique QR code 130a so as to arrive at a final payload. The extraction process 910 also includes extracting a second encrypted payload and a deep link from the final payload. The mobile device 10 is then configurable or configured to execute the extracted deep link. The deep link may include instructions, commands, code, links, and/or the like, for the mobile device 10 that extracted the deep link from the final unique QR code to, among other things, visit or launch a website, link, or the like; launch a particular installed app (e.g., DBS Digibank app, other financial institution apps, payment apps such as PayPal, electronic wallets, social media apps such as Facebook, WeChat, Line, etc.); login to a particularly installed app, website, and/or the like; launch an app distribution platform or store (e.g., Apple App Store, Google Play Store, etc.) to download, install, register, and/or login to a particular app; etc.

[0095] The executing of the deep link may also include causing the mobile device 10 to establish a communication channel 120 between the mobile device 10 and the validation processor 500 (e.g., the information selector 501). The communication channel 120 is established between the mobile device 10 and the validation processor 500 so as to enable the validation processor 500 to perform validation of the information set 130.

[0096] The deep link is further configured to cause the mobile device 10 to transmit, to the information selector 501 via the communication channel 120, the second encrypted payload and the first encrypted payload identifier 130b.

[0097] After the information selector 501 receives the second encrypted payload and the first encrypted payload identifier 130b, the information selector 501 is configurable or configured to provide the second encrypted payload to the second decryption engine 503 and the first encrypted payload identifier 130b to the association search engine 502.

[0098] The communication channel 120 may remain established between the mobile device 10 and the validation processor 500 so as to enable the validation processor 500 to return the results of the validation of the information set 130.

[0099] The association search engine (e.g., association search engine 502).

[00100] As illustrated in Figure 6, an example embodiment of the validation engine 510 includes one or more association search engines (e.g., association search engine 502). The association search engine 502 is configurable or configured to receive the first encrypted payload identifier 130b from the information selector 501. Alternatively or in addition, the association engine 502 is also configurable or configured to receive the first encrypted pay load identifier 130b directly from the communication channel 120 and/or mobile device 10.

[00101] After the association search engine 502 receives the first encrypted payload identifier 130b, the association search engine 502 is configurable or configured to perform an association search in the first database 110 using the received first encrypted payload identifier 130b as a search query. If the received first encrypted payload identifier 130b is able to locate a first encrypted pay load based on the association search, then the received first encrypted payload identifier 130b is determined to be associated with the first encrypted payload. On the other hand, if the received first encrypted payload identifier 130b is unable to locate a first encrypted payload based on the association search, then the received first encrypted payload identifier 130b is determined to not be associated with the first encrypted payload.

[00102] In an example embodiment, when the association search engine 502 determines that the received first encrypted payload identifier 130b is associated with a particular first encrypted payload based on the association search, the association search engine 502 obtains that particular first encrypted payload that is associated with the received first encrypted payload identifier 130b. The association search engine 502 then provides that particular first encrypted payload to the first decryption engine 503.

[00103] The first decryption engine (e.g., first decryption engine 503).

[00104] As illustrated in Figure 6, an example embodiment of the validation engine 510 includes one or more first decryption engines (e.g., first decryption engine 503). The first decryption engine 503 is configurable or configured to receive the first encrypted payload (which was identified by the association search engine 502 as being associated with the first encrypted payload identifier 130b (which was extracted from the information set 130)). The first decryption engine 503 is also configurable or configured to obtain a first secret key (e.g., as used by the first encryption engine 204 in the first setup process (e.g., process 810) to encrypt the payload to arrive at the first encrypted payload).

[00105] After the first decryption engine 503 receives the first encrypted payload from the association search engine 502 and receives the first secret key (e.g., used by the first encryption engine 204), the first decryption engine 503 is configurable or configured to determine if the first encrypted payload received from the association search engine 502 is decryptable using such first secret key. If such first secret key is able to decrypt the first encrypted payload received from the association search engine 502, then the first encrypted payload is the first encrypted payload generated in the first setup process (e.g., process 810). On the other hand, if such first secret key is unable to decrypt the first encrypted pay load received from the association search engine 502, then the first encrypted payload received from the association search engine 502 is not the first encrypted payload generated in the first setup process (e.g., process 810).

[00106] In an example embodiment, when the first encrypted payload received from the association search engine 502 is determined to be decryptable by the first secret key (e.g., used by the first encryption engine 204), the first decryption engine 503 obtains a validation result (e.g., referred to herein as the "second validation result"). The second validation result is or includes a decrypted version of the first encrypted payload. The second validation result is then provided to the comparator 505 for performing a comparison with a first validation result (as obtained by the second decryption engine 504).

[00108] As illustrated in Figure 6, an example embodiment of the validation engine 510 includes one or more second decryption engines (e.g., second decryption engine 504). The second decryption engine 504 is configurable or configured to receive the second encrypted payload from the information selector 501 (i.e., the second encrypted payload that was extracted from the information set 130). The second decryption engine 504 is also configurable or configured to obtain a second secret key (e.g., as used by the second encryption engine 304 in the second setup process (e.g., process 820) to encrypt the pay load to arrive at the second encrypted pay load). [00109] After the second decryption engine 504 receives the second encrypted payload from the information selector 501 and receives the second secret key (e.g., used by the second encryption engine 304), the second decryption engine 504 is configurable or configured to determine if the second encrypted payload received from the information selector 501 is decryptable using such second secret key. If such second secret key is able to decrypt the second encrypted payload received from the information selector 501, then the second encrypted payload is the second encrypted payload generated in the second setup process (e.g., process 820). On the other hand, if such second secret key is unable to decrypt the second encrypted payload received from the information selector 501, then the second encrypted payload received from the information selector 501 is not the second encrypted payload generated in the second setup process (e.g., process 820).

[00110] In an example embodiment, when the second encrypted payload received from the information selector 501 is determined to be decryptable by the second secret key (e.g., as used by the second encryption engine 304), the second decryption engine 504 obtains a validation result (e.g., referred to herein as the "first validation result"). The first validation result is or includes a decrypted version of the second encrypted pay load. The first validation result is then provided to the comparator 505 for performing a comparison with a second validation result (as obtained by the first decryption engine 503).

[00112] As illustrated in Figure 6, an example embodiment of the validation engine 510 includes one or more comparators (e.g., comparator 505). The comparator 505 is configurable or configured to receive the second validation result from the first decryption engine 503 (i.e., the decrypted version or result of the first encrypted payload). The comparator 505 is also configurable or configured to receive the first validation result from the second decryption engine 504 (i.e., the decrypted version or result of the second encrypted payload).

[00113] After the comparator 505 receives the first and second validation results, the comparator 505 is configurable or configured to compare the first and second validation results. When the first validation result matches the second validation result, the comparator 505 provides the successful comparison/result to the validator 506 to perform validation of the information set 130. On the other hand, when the first validation result does not match the second validation result, the comparator 505 provides the unsuccessful comparison/result to the validator 506 to not perform validation of the information set 130. [00114] The validator (e.g., validator 506).

[00115] As illustrated in Figure 6, an example embodiment of the validation engine 510 includes one or more validators (e.g., validator 506). The validator 506 is configurable or configured to receives the results of the comparison of the first and second validation results performed by the comparator 505.

[00116] When the validator 506 receives a successful comparison/result from the comparator 505, the validator 506 performs a validation of the information set 130. The validator 506 also provides the successful validation result to the mobile device 10 (e.g., via the established communication channel 120). In an example embodiment, a validation (or successful validation) of the information set 130 enables a user 10 (or mobile device 10 of the user 10) to perform any one or more permitted and/or configured action on the information set 130 (e.g., add/load a certain amount of fiat currency value (e.g., USD or SGD) and/or cryptocurrency value (e.g., bitcoin or BTC, ethereum or ETH, etc.); add a message or other information such as photos, videos, etc.; transfer to another user 10, etc.), determine a status of the information set 130 (e.g., a new information set 130 that has not yet been configured and/or validated by a user 10; or one that was previously used, previously loaded, previously redeemed, etc.), and/or confirm an authenticity, origin, etc. of the information set 130.

[00117] After the validator 506 provides a validation (or successful validation) of the information set 130 to the user 10 (or mobile device 10 of the user), the validator 506 may receive, from the user 10 (or mobile device 10 of the user 10) a request to perform one or more permitted and/or configured actions on the information set 130. The validator 506 may then provide the validation (or successful validation) of the information set 130 along with the received request to perform one or more permitted and/or configured actions on the information set 130 to the transaction processor 520 to perform such permitted and/or configured actions on the information set 130.

[00118] The transaction processor (e.g., transaction processor 520).

[00119] As illustrated in at least Figure 5, the validation processor 500 includes one or more transaction processors (e.g., transaction processor 520). The transaction processor 520 is configurable or configured to perform and/or execute the one or more user desired, permitted and/or configured actions received from the validator 506 (which received such actions from the user 10 or mobile device 10 of the user 10). Such actions include, but are not limited to, adding, storing, amending, etc. of recipients 10 who will receive final information sets 130 (e.g., adding of a recipient 10 for each final information set 130, such as a adding a first user 10 as a recipient 10 of a red envelope 130; adding of multiple recipients 10 for multiple final information sets 130, such as adding first, second, and third users 10 as 3 recipients 10 of 3 red envelopes 130; adding of multiple recipients 10 for one final information set 130, such as adding of first, second, third, fourth, and fifth users 10 as recipients 10 for one red envelope 130 (e.g., in situations where a user 10 is giving monetary gifts to several recipients 10 using just one final information set 130)); adding, storing, amending, etc. of gifters/senders 10 who will give (or load) final information sets 130 (e.g., adding of a gifter 10 for each final information set 130, such as a adding a first user 10 as a gifter 10 of a red envelope 130; adding of multiple gifters 10 for multiple final information sets 130, such as adding first, second, and third users 10 as 3 gifters 10 of 3 red envelopes 130; adding of multiple gifters 10 for one final information set 130, such as adding of first, second, third, fourth, and fifth users 10 as gifters 10 for one red envelope 130 (e.g., in situations where multiple users 10 are combining together to give a monetary gift to one recipient 10 using just one final information set 130)); adding, storing, amending, etc. of information (e.g., loading of information, such as a message, picture, video, etc., into a final information set 130 and/or for association with a final information set 130); adding, storing, amending, etc. of value (e.g., loading of value, such as fiat currency (e.g., USD, SGD, etc.) and/or cryptocurrency (e.g., BTC, ETH, etc.), into a final information set 130 and/or for association with a final information set 130); performing of transactions (e.g., transfer value from one or more users 10 to one or more other users 10; transfer value from one or more mobile devices 10 to one or more other users 10 and/or mobile devices 10; etc.); recording of transactions (e.g., in a database 110 and/or distributed ledger 110); etc.

[00120] In an example embodiment, certain actions performed and/or performable by a gifter 10 (e.g., loading money, revising money already loaded, etc.) may include and/or be performed subject to, pursuant to, and/or as part of one or more gamification elements and/or features. For example, the transaction processor 520 and/or one or more elements of the system 100 may provide an option for a gifter 10 to participate in playing one or more games (and/or other features, such as watch a video, take a poll, view an advertisement, etc.) before loading value into a final information set 130. Example embodiments may provide an incentive to gifters 10 who participate in such games and/or other features (e.g., bonus money, points, cryptocurrencies, etc.; reduction or elimination of service fees (if charged); etc.). Alternatively, a gifter 10 may be required (i.e., not an option) to participate in playing one or more games and/or other features before performing an action. [00121] In another example embodiment, certain actions performed and/or performable by a recipient 10 (e.g., redeeming money, regifting to another user 10, etc.) may include and/or be performed subject to, pursuant to, and/or as part of one or more gamification elements and/or features. For example, the transaction processor 520 and/or one or more elements of the system 100 may provide an option for a recipient 10 to participate in playing one or more games (and/or other features, such as watch a video, take a poll, view an advertisement, etc.) before redeeming value from a final information set 130. Example embodiments may provide an incentive to recipients 10 who participate in such games and/or other features (e.g., bonus money, points, cryptocurrencies, etc.; reduction or elimination of service fees (if charged); etc.). Alternatively, a recipient 10 may be required (i.e., not an option) to participate in playing one or more games and/or other features before performing an action.

[00122] In another embodiment, the transaction processor 520 and/or one or more elements of the system 100 may provide an option for both gifter 10 and recipient 10 to participate in playing one or more games (and/or other features, such as watch a video, take a poll, view an advertisement, etc.), which may be played or performed separately (e.g., different times and/or different independent games) and/or together (e.g., at the same time and/or the same game, such as competing with each other). Example embodiments may provide an incentive to gifters 10 and/or recipients 10 who participate in such games and/or other features (e.g., bonus money, points, cryptocurrencies, etc.; reduction or elimination of service fees (if charged); etc.). Alternatively, an example embodiment may only allow the recipient 10 to redeem if the recipient 10 beats the gifter 10, etc. Alternatively, gifter 10 and recipient 10 may be required (i.e., not an option) to participate in playing one or more games and/or other features before performing an action.

[00123] The information set distributor (e.g., information set distributor 600).

[00124] As illustrated in at least Figure 1, the system 100 for setting up, managing, updating, and validating information may include one or more information set distributors (e.g., information set distributor 600). The information set distributor 600 is configurable or configured to perform, among other things, a distributing, making available, sending, transmitting, and/or generating/printing of one or more information sets 130. For example, when the information sets 130 are in physical form (e.g., a print out on a paper, card, object, or the like, such as in the form of a red envelope for Chinese New Year, a birthday gift, a gift card, payment, etc.), the information set distributor 600 may be a vending machine, printing facility, and/or the like. When the information sets 130 are in digital, electronic, and/or virtual form (e.g., a digital, electronic, and/or virtual representation of a red envelope for Chinese New Year, a birthday gift, a gift card, payment, etc., such as via an email, instant message, other message, mobile application interaction, etc.), the information set distributor 600 may be a vending machine, geolocation, code (e.g., a QR code, barcode, or the like, which sends the user 10 to a virtual marketplace, vending machine, application platform (e.g., Apple App Store, Google Play Store, etc.), mobile application, or the like), or the like.

[00125] An example embodiment of an information set distributor 600 in the form of a vending machine 600 may include one or more user interfaces (e.g., a touchscreen display, buttons, credit card scanner, money slots, etc.), communication functionality (e.g., network connectivity, such as internet connectivity, for communicating with example embodiments of the first setup processor 200, second setup processor 300, information set generator 400, validation processor 500, and/or database 110; Bluetooth, WiFi, NFC, QR code scanner, bar code scanner, etc. for communicating with user devices, printed information sets 130, etc.), printing functionality (e.g., for printing physical information sets 130, receipts, etc.), and software-related functionality (e.g., software installed in the vending machine 600) that enables a user 10 to interact with the vending machine 600 via the one or more interfaces and/or communication functionality to generate one or more information sets 130. For example, the vending machine 600 may enable the user 10 to enter one or more recipients (optional) and select a quantity of information sets to generate, display, load, customize (e.g., with a message), and/or distribute (e.g., for physical forms of information sets 130, mailing address for recipients; for electronic forms of information sets 130, email address, social media handle, mobile device number, etc. for recipients). The vending machine 600 may also enable the user 10 select an amount of value to add/load to one or more of the generated information sets 130 (e.g., add the same amount to all information sets 130; or add custom amounts to each information set 130). The vending machine 600 may also enable the user 10 to select one or more messages to add to one or more of the generated information sets 130 based on the recipient 10 who will receive each of the one or more information sets 130. Other features and/or functionalities of the vending machine 600 are also contemplated in the present disclosure, including features and/or functionalities present in ATMs and conventional vending machines, or the like.

[00126] An example embodiment of the vending machine 600 is then configurable or configured to generate the requested one or more information sets 130. In an example embodiment, the vending machine 600 communicates with the first setup processor 200, second setup processor 300, and information set generator 400 to generate the one or more information sets 130, as described above and in the present disclosure. Alternatively or in addition, the vending machine 600 may include one or more functionalities of the first setup processor 200, second setup processor 300, and/or information set generator 400 for use in generating the one or more information sets 130.

[00127] An example embodiment of the vending machine 600 is also configurable or configured to validate information sets 130, such as for recipients 10 who receive information sets 130 from a user 10. In an example embodiment, the vending machine 600 communicates with the validation processor 500 (and the first setup processor 200, second setup processor 300, and/or information set generator 400, as needed) to validate one or more such information sets 130, as described above and in the present disclosure. Alternatively or in addition, the vending machine 600 may include one or more functionalities of the validation processor 500 (and the first setup processor 200, second setup processor 300, information set generator 400, as needed) for use in validating the one or more information sets 130.

[00128] Example embodiments of a method of setting up, managing, updating, and validating information sets (e.g„ method 700).

[00129] An example embodiment of a method (e.g., method 700) of setting up, managing, updating, and/or validating information and information sets 130, is illustrated in FIGURE 7.

[00130] The method 700 includes performing a validatable information set generation process (e.g., method 800). Such method 800 is performed in order to setup or generate an information set 130 that can be later validated (e.g., by method 900, as described in the present disclosure). For example, the method 800 of performing a validatable information set generation process may be performed by the first setup processor 200, second setup processor 300, and information set generator 400 (see Figures 1-3), as described in the present disclosure.

[00131] The validatable information set generation process 800 is performed when a final information set 130 is to be generated. For example, in situations/applications when a particular financial institution 600 (e.g., DBS Bank 600) would like to provide or offer users 10 a loadable gift card, Chinese New Year red envelope, or the like (physical and/or virtual), such gift card, red envelope, or the like, may include a scannable component, feature, section, codes, or the like, to enable the user 10 initiate loading/adding of value (e.g., fiat currency such as Singapore Dollars, US Dollars, digital assets, etc.), redeeming of value, adding of information (e.g., information, instructions, requests, interactions, transactions, messages, and/or the like), receiving of information, etc. (also referred to herein as "performing an action", or the like, on or to the final information set). Such components, features, sections, codes, or the like, are referred to herein as a final information set 130. When a final information set 130 is generated by example embodiments of the method 800 (and system 100), a first user 10 who obtains or receives the final information set 130 from the financial institution 600 (or from an information set distributor 600) may perform an action. As will be further described in the present disclosure, for a first user 10 (or any other user 10) to perform any action on the final information set 130 (e.g., add/load value, insert messages or other information, transfer to another user, etc.), determine a status of the received/obtained final information set 130 (e.g., a new final information set 130, or one that is previously used, previously loaded, previously redeemed, spent, expired, etc.), and/or determine authenticity, origin, etc. of the final information set 130, a mobile device 10 of the user 10 can receive the final information set 130 (e.g., via scanning using a camera of the mobile device 10 of the user 10). The received final information set 130 then enables the mobile device 10 to cooperate with one or more elements of the system 100 (as described in the present disclosure) to perform a validation of the final information set 130 before the user 10 performs an action (e.g., loading/adding value, adding information) to the final information set 130. Any such actions performed by a user 10 to the final information set 130 may include performing (or reperforming) one or more processes and/or actions of the method 800. For example, one or more of the following actions (or similar actions) of method 800 may be performed or re-performed: amend the first payload to reflect the one or more actions performed by the user 10 (in which case the first encrypted pay load, the second encrypted payload, the final payload, and/or the encoding in the final unique QR code may need to be changed/amended); not amend the first payload, but instead associate/point/link the first payload to a new/additional payload, or the like, having the one or more actions performed by the user 10 (in which case the first encrypted payload, the second encrypted payload, the final payload, and/or the encoding in the final unique QR code may not need to be changed/amended); regenerate a first encrypted payload by encrypting the amended first payload (if amended) with the first secret key; associate the first encrypted payload identifier to the regenerated first encrypted payload (if regenerated); regenerate a second encrypted payload by encrypting the amended first payload (if amended) with the second secret key; regenerate the final payload using the regenerated second encrypted payload (if regenerated); and/or encoding the final unique QR code with the regenerated final payload (if regenerated), which may be achieved by changing the encoding in the final unique QR code via a dynamic QR code, or the like. [00132] The method 700 also includes performing a final information set validation process (e.g., method 900). Such method 900 is performed in order to perform a validation of information sets 130 generated or setup by example embodiments of the method 800 (as described in the present disclosure). For example, the method 900 of performing a final information set validation process may be performed by the validation processor 500 (see Figures 1 and 5), and may also involve the first setup processor 200, second setup processor 300, and information set generator 400 (see Figures 1-3), as described in the present disclosure.

[00133] The final information set validation process 900 is performed when a final information set 130 (as generated by the validatable information set generation process 800, which includes a final unique QR code 130a and a first encrypted payload identifier 130b) is required to be validated. For example, in situations/applications where a final information set 130 is generated by a particular financial institution 600 (e.g., DBS Bank 600) for use by its users 10 as a loadable and redeemable gift card, red envelope, or the like (physical and/or virtual), a first user 10 (e.g., a user 10 that wants to add value to the gift card and give the gift card to a second user 10) that obtains or receives the final information set 130 from the financial institution 600 (or from an information set distributor 600) may desire to load/add value (e.g., a certain amount of fiat currency, such as USD 50) and/or add other information (e.g., information, instructions, requests, interactions, transactions, messages, value (e.g., fiat currency such as Singapore Dollars, US Dollars, etc.), digital assets, and/or the like). To do any action on the final information set 130 (e.g., add/load value, insert messages or other information, transfer to another user, etc.), to determine a status of the received/obtained final information set 130 (e.g., a new final information set 130, or one that is previously used, previously loaded, previously redeemed, etc.), and/or to determine authenticity, origin, etc. of the final information set 130, a mobile device 10 of the user 10 can receive (e.g., scan using a camera of the mobile device 10 of the user 10) the final information set 130. The mobile device 10 will then cooperate with one or more elements of the system 100 (as described in the present disclosure) to perform a validation of the final information set 130 before allowing the user 10 perform an action (e.g., loading/adding value, adding information) to the final information set 130.

[00134] These and other processes and/or actions of the method 700 will now be further described with reference to the accompanying figures.

[00135] Example embodiments of a method of performing a validatable information set generation process (e.g„ method 800). [00136] An example embodiment of a method (e.g., method 800) of performing a validatable information set generation process is illustrated in at least FIGURE 8A. The validatable information set generation process 800 is performed when a final information set 130 is to be generated.

[00137] The method 800 of performing the validatable information set generation process includes performing a first setup process (e.g., action 810). The method 800 also includes performing a second setup process (e.g., action 820). The method 800 also includes generating a final information set (e.g., action 830).

[00138] These and other processes and/or actions of the method 800 will now be further described with reference to the accompanying figures.

[00139] Performing a first setup process (e.g., action 810),

[00140] In an example embodiment, the method 800 of performing a validatable information set generation process includes performing a first setup process (e.g., action 810). For example, the first setup process may be performed by the first setup processor (see Figures 1 and 2), as described in the present disclosure.

[00141] As illustrated in FIGURE 8B, the first setup process 810 may include generating or obtaining a payload (e.g., a first payload) (e.g., action 812). For example, the payload may be generated by the payload processor 202 (see Figure 2), as described in the present disclosure. The payload may be or include any unique information. For example, the payload may be or include a unique series of characters, alphanumeric characters, numbers, letters (e.g., in English and/or other languages), and/or the like. Alternatively or in addition, the payload may be randomly generated. The payload may be of any length. For example, the payload may be a series of 18-24 characters, or more or less. The payload may also include editable, configurable, customizable, and/or settable information and/or information fields and/or categories, such as a payload identifier (e.g., the aforementioned unique series of 18-24 characters), status (e.g., valid, deposited, transferred, pending, redeemed, expired, etc.), transaction/action type (e.g., transfer funds, send or display message/information, etc.), quantity or value (if applicable) (e.g., USD 100), geographical restrictions (if any), creation/setup/configure/initial validation date (e.g., date that a gifter/sender user adds/loads value, uploads a message, etc.), redeem/receive/final validation date (e.g., date that a receiver/recipient user accepts the added/loaded value, receives the uploaded message, etc.), expiry date or redeemable period (or final validation date), a corresponding/associated encrypted payload identifier (e.g., first encrypted payload identifier, as generated by the payload identifier processor 206), etc. Alternatively, the payload may include a pointer, reference, relation, association, link, or the like ("association", "associated", etc.), to another payload (e.g., information pay load, which may also be stored in database 110) that includes the editable, configurable, customizable, and/or settable information and/or information fields and/or categories, such as the payload identifier (e.g., the unique series of 18-24 characters), the status (e.g., valid, deposited, transferred, pending, redeemed, expired, etc.), the transaction/action type (e.g., transfer funds, send or display message/information, etc.), the quantity or value (if applicable) (e.g., USD 100), the geographical restrictions (if any), the creation/setup/configure/initial validation date (e.g., date that a gifter/sender user adds/loads value, uploads a message, etc.), the redeem/receive/final validation date (e.g., date that a receiver/recipient user accepts the added/loaded value, receives the uploaded message, etc.), the expiry date or redeemable period (or final validation date), a corresponding/associated encrypted payload identifier (e.g., first encrypted payload identifier, as generated by the pay load identifier processor 206), etc. Once the first payload is generated or obtained, the first payload may be stored, such as in a first database 110. The first pay load may then be made available to one or more other elements of the system 100.

[00142] The first setup process 810 may also include encrypting the first pay load to arrive at an encrypted payload (e.g., first encrypted payload) (e.g., action 814). For example, the first payload may be encrypted by the first encryption engine 204 (see Figure 2), as described in the present disclosure. The first encrypted payload may be obtained by encrypting the first payload with a first secret key, or the like. It is to be understood in the present disclosure that any encryption algorithm or methodology known in the art may be employed to encrypt the first payload to arrive at the first encrypted payload. For example, the encryption algorithm may include, but are not limited to, Advanced Encryption Standard (AES), Triple Data Encryption Standard (TripleDES), Blowfish Encryption Algorithm, RSA Security, IDEA Encryption Algorithm, MD5 Encryption Algorithm, HMAC Encryption Algorithm, Twofish Encryption Algorithm, etc. Once the first encrypted payload is generated, the first encrypted pay load may be stored, such as in the first database 110.

[00143] The first setup process 810 may also include generating or obtaining a first encrypted payload identifier (e.g., action 816). For example, the first encrypted payload identifier may be generated or obtained by the payload identifier processor 206 (see Figure 2), as described in the present disclosure. The first encrypted payload identifier (e.g., first encrypted payload identifier 130b, as illustrated in Figure 4) may be or include any unique series or sequence of characters. For example, the encrypted payload identifier may be a unique series of characters, alphanumeric characters, numbers, letters (e.g., in English and/or other languages), and/or the like. Alternatively or in addition, the encrypted payload identifier may be a series of randomly generated characters, alphanumeric characters, numbers, letters (e.g., in English and/or other languages), and/or the like. The encrypted payload identifier may be of any length, and may be application/requirement-specific (e.g., selected based on the number of unique encrypted payload identifiers required). For example, the encrypted payload identifier may be or include a series of 5-10 characters, or more or less. Alternatively or in addition, the encrypted payload identifier may be or include one or more symbols, codes, images, or the like. Once the first encrypted payload identifier is generated, the first encrypted payload identifier may be stored, such as in the first database 110.

[00144] Once the first encrypted payload and the first encrypted payload identifier have been generated and/or obtained (e.g., from actions 812, 814, and 816), the first setup process 810 includes generating or creating an association between the first encrypted payload and the first encrypted payload identifier. For example, the association between the first encrypted payload and the first encrypted pay load identifier may be generated or obtained by the association engine (see Figure 2), as described in the present disclosure. The generated association may then be stored, such as in the first database 110. It is to be understood that an association between the first encrypted payload and the first encrypted payload identifier may be any association, reference, relation, link, or the like, that enables the first encrypted payload to be obtained based on the first encrypted payload identifier, and vice versa. For example, when the first encrypted payload and the first encrypted payload identifier are associated, the association search engine 502 (see Figure 6) of the validation processor 500 may readily obtain the first encrypted pay load based on a search of the first database 110 using the first encrypted payload identifier as a search query.

[00145] Performing a second setup process (e.g., action 820),

[00146] In an example embodiment, the method 800 of performing a validatable information set generation process includes performing a second setup process (e.g., action 820). For example, the second setup process may be performed by the second setup processor 300 (see Figures 1 and 3), as described in the present disclosure.

[00147] The second setup process 820 may include obtaining or receiving the first payload that was generated in the first setup process 810 (i.e., in action 812). For example, the first payload may be obtained or received by the information selector 302 (see Figure 3). In an example embodiment, the first payload may be obtained directly from the first database 100. Alternatively or in addition, the second setup process 820 may first obtain the first encrypted payload that was generated in the first setup process 810 (i.e., in action 814). In such an example, the second setup process 820 further includes decrypting the first encrypted payload using the first secret key (which was used in action 814 to encrypt the first payload to arrive at the first encrypted payload), so as to obtain the first payload.

[00148] As illustrated in FIGURE 8C, the second setup process 820 includes encrypting the first payload to arrive at a second encrypted payload (e.g., action 822). For example, the first payload may be encrypted by the second encryption engine 304 (see Figure 3), as described in the present disclosure. The second encrypted payload may be obtained by encrypting the first payload with a second secret key, or the like. In this regard, the second encrypted payload is different from the first encrypted payload. Furthermore, the second secret key is different from the first secret key. Put differently, the first encrypted payload can only be decrypted using the first secret key and cannot be decrypted using the second secret key; and the second encrypted payload can only be decrypted using the second secret key and cannot be decrypted using the first secret key. It is to be understood in the present disclosure that any encryption algorithm or methodology known in the art may be employed to encrypt the first payload to arrive at the second encrypted payload. It is also to be understood that the encryption algorithm used to generate the first encrypted payload may or may not be the same as the encryption algorithm used to generate the second encrypted payload. Once the second encrypted payload is generated, the second encrypted payload may be stored, such as in a second database 110. The second database 110 may be the same database as or different database from the first database 110. In preferred embodiments, the second database 110 is a different database than the first database 110.

[00149] The second setup process 820 may also include generating a final payload (e.g., action 824). For example, the final payload may be generated by the final payload processor 306 (see Figure 3), as described in the present disclosure. The final payload includes the second encrypted payload (as generated in action 822) and a deep link. In this regard, the deep link may include instructions, commands, code, links, and/or the like, for a computing device 10 (e.g., a mobile device 10) that receives the deep link (e.g., extracts the deep link from the final unique QR code, as described in the present disclosure) to, among other things, visit or launch a website, link, or the like; launch a particular installed app (e.g., DBS Digibank app, other financial institution apps, payment apps such as PayPal, electronic wallets, social media apps such as Facebook, WeChat, Line, etc.); login to a particularly installed app, website, and/or the like; launch an app distribution platform or store (e.g., Apple App Store, Google Play Store, etc.) to download, install, register, and/or login to a particular app; establish a communication channel (e.g., a first communication channel) between a mobile device 10 of the user 10 and the validation processor 500; and/or transmit, from the mobile device 10 of the user 10 to the validation processor 500, data extracted and/or obtained from the final information set 130 (including the second encrypted payload and the first encrypted payload identifier 130b). Once the final payload is generated, the final payload may be stored, such as in the second database 110.

[00150] Once the final payload has been generated (e.g., from action 824), the second setup process 820 includes encoding the final payload into a final unique QR code (e.g., final unique QR code 130a) (e.g., action 826). That is, a final unique QR code 130a is generated having the final payload encoded in the final unique QR code 130a. For example, the final unique QR code 130a may be generated by the final unique QR code processor 308 (see Figure 3), as described in the present disclosure. The final unique QR code 130a may then be provided to the information set generator 400 to generate an information set 130 (see Figure 4). The final unique QR code 130a may also be stored, such as in the first and/or second database 110. In example embodiments, the second setup process 820 may include encoding the second encrypted payload (as generated in action 822) and the deep link (as described in the present disclosure) into the final unique QR code 130a without generating the final payload (e.g., not performing action 824).

[00151] Generating a final information set (e.g., action 830),

[00152] In an example embodiment, the method 800 of performing a validatable information set generation process includes generating a final information set (e.g., action 830). For example, the final information set may be generated by the information set generator 400 (see Figures 1 and 3), as described in the present disclosure.

[00153] As illustrated in FIGURE 8D, the generating of the final information set 830 includes obtaining or receiving the final unique QR code (e.g., action 832), which was generated in the second setup process 820 (i.e., in action 826). For example, the final unique QR code may be obtained or received by the information set generator 400 (see Figure 3). In an example embodiment, the final unique QR code may be obtained from the second database 100. Alternatively or in addition, the final unique QR code may be obtained directly from the final unique QR code processor 308. [00154] The generating of the final information set 830 also includes obtaining or receiving the first encrypted payload identifier (e.g., action 834), which was generated or obtained in the first setup process 810 (i.e., in action 816). For example, the first encrypted payload identifier may be obtained or received by the information set generator 400 (see Figure 3). In an example embodiment, the first encrypted payload identifier may be obtained from the first database 100. Alternatively or in addition, the first encrypted payload identifier may be obtained directly from the payload identifier processor 206.

[00155] The generating of the final information set 830 also includes generating the final information set that includes the final unique QR code and the first encrypted pay load identifier (e.g., action 836). For example, the final information set having the final unique QR code and the first encrypted payload identifier may be generated by the information set generator 400 (see Figure 3), as described in the present disclosure. Although the figures may illustrate the final information set 130 (see Figure 4) as having one final unique QR code 130a and one first encrypted payload identifier 130b, it is to be understood that the final information set 130 may include more than one final unique QR code 130a and/or more than one first encrypted payload identifier 130b without departing from the teachings of the present disclosure. Furthermore, although the figures may illustrate the final information set 130 as having an arrangement of the final unique QR code 130a provided above the first encrypted pay load identifier 130b, it is to be understood that the final unique QR code 130a and the first encrypted payload identifier 130b may be arranged in other arrangements without departing from the teachings of the present disclosure. For example, the first encrypted payload identifier 130b may be provided above, to the left of, to the right of, and/or below the final unique QR code 130a.

[00156] Example embodiments of a method of performing a final information set validation process (e.g., method 900).

[00157] An example embodiment of a method (e.g., method 900) of performing a final information set validation process is illustrated in at least FIGURE 9A. The final information set validation process 900 is performed when a final information set 130 (as generated by the validatable information set generation process 800, which includes a final unique QR code 130a and a first encrypted payload identifier 130b) is required to be validated.

[00158] The method 900 of performing the final information set validation process includes performing an extraction process (e.g., action 910). The method 900 also includes executing the deep link extracted from the final payload (e.g., action 920). The method 900 also includes performing a validation process (e.g., action 930).

[00159] These and other processes and/or actions of the method 900 will now be further described with reference to the accompanying figures.

[00160] Performing an extraction process (e.g., action 910Y

[00161] In an example embodiment, the method 900 of performing a final information set validation process includes performing an extraction process (e.g., action 910). For example, the extraction process 910 may be performed by the information selector 501 of the validation processor 500 (see Figures 1, 5 and 6), as described in the present disclosure.

[00162] As illustrated in FIGURE 9B, the extraction process 910 may include extracting, from the final information set 130, the final unique QR code 130a and the first encrypted payload identifier 130b (e.g., action 912). Such extracting may be performed by a mobile device 10 of a user 10. More specifically, the extracting may be performed by scanning or capturing the final information set 130 via a camera of the mobile device 10 of the user 10.

[00163] The extraction process 910 may also include obtaining the final payload encoded in the final unique QR code (e.g., action 914). The final payload may be obtained by decoding the final unique QR code.

[00164] The extraction process 910 may also include extracting, from the final payload, the second encrypted payload and the deep link (e.g., action 916).

[00165] Execute the deep link extracted from the final payload (e.g., action 920),

[00166] In an example embodiment, the method 900 of performing a final information set validation process includes executing the deep link extracted from the final pay load (e.g., action 920). [00167] The executing of the deep link 920 may include executing a deep link (as known in the art), which may include executing instructions, commands, code, links, and/or the like, for the mobile device 10 of the user 10 that received the deep link (e.g., extracted the deep link from the final unique QR code, as described in the present disclosure) to, among other things, visit or launch a website, link, or the like; launch a particular installed app (e.g., DBS Digibank app, other financial institution apps, payment apps such as PayPal, electronic wallets, social media apps such as Facebook, WeChat, Line, etc.); login to a particularly installed app, website, and/or the like; launch an app distribution platform or store (e.g., Apple App Store, Google Play Store, etc.) to download, install, register, and/or login to a particular app. As illustrated in FIGURE 9C, the executing of the deep link 920 also includes establishing a communication channel (e.g., a first communication channel) between the mobile device 10 of the user 10 and the validation processor 500 (e.g., action 922). the executing of the deep link 920 also includes transmitting, from the mobile device 10 of the user 10 to the validation processor 500, the second encrypted payload and the first encrypted payload identifier 130b (e.g., action 924).

[00168] Performing a validation process (e.g., action 930),

[00169] In an example embodiment, the method 900 of performing a final information set validation process includes performing a validation process (e.g., action 930). For example, the validation process may be performed by the validation engine 510 of the validation processor 500 (see Figures 1, 5 and 6), as described in the present disclosure.

[00170] As illustrated in FIGURE 9D, the validation process 930 includes receiving, from the mobile device 10 of the user 10 that received the final information set 130, the second encrypted payload and the first encrypted payload identifier 130b (e.g., action 931). The second encrypted payload and the first encrypted payload identifier 130b may be received by the information selector 501 of the validation processor 500. Once received, the information selector 501 is configurable or configured to selectively provide the received second encrypted payload to the second decryption engine 504 (e.g., to perform actions 932, 933) and selectively provide the received first encrypted payload identifier 130a to the association search engine 502 (e.g., to perform actions 934-937).

[00171] In respect to the received second encrypted payload, the validation process 930 includes obtaining the second secret key that was used to generate the second encrypted payload in the second setup process 820 (i.e., used to encrypt the first pay load to arrive at the second encrypted payload). The second secret key is then applied to the received second encrypted payload (e.g., action 932) to determine whether or not the received second encrypted payload that was extracted from the final information set 130 is identical to the second encrypted payload generated in the second setup process 820 by encrypting the first payload. If the second secret key is able to decrypt the received second encrypted payload, then the received second encrypted payload is the second encrypted payload generated in the second setup process 820. On the other hand, if the second secret key is unable to decrypt the received second encrypted payload, then the received second encrypted payload is not the second encrypted payload generated in the second setup process 820.

[00172] In an example embodiment, when the received second encrypted payload is determined to be decryptable by the second secret key (or the received second encrypted payload is determined to be the second encrypted payload generated in the second setup process 820), the validation process 930 further includes obtaining a first validation result (e.g., action 933). The first validation result includes a decrypted version of the received second encrypted payload. For example, the second decryption engine 504 may perform the determination, corresponding decryption of the second encrypted payload, and obtaining of the first validation result.

[00173] In respect to the received first encrypted payload identifier, the validation process 930 includes performing an association search (e.g., in the first database 110) using the received first encrypted payload identifier as a search query (e.g., action 934). If the received first encrypted payload identifier is able to locate the first encrypted payload based on the search 934, then the received first encrypted payload identifier is the first encrypted payload identifier 130b generated in the first setup process 810 (e.g., action 816). Furthermore, the received first encrypted payload would also be determined to be associated with the first encrypted payload. On the other hand, if the received first encrypted payload identifier is unable to locate the first encrypted payload based on the search 934, then the received first encrypted payload identifier is not the first encrypted payload identifier 130b generated in the first setup process 810 (e.g., action 816). Furthermore, the received first encrypted payload would also be determined to not be associated with the first encrypted payload.

[00174] In an example embodiment, when the association search 934 (using the received first encrypted payload identifier 130a as a search query) determines that the received first encrypted payload identifier is associated with the first encrypted payload, the validation process 930 further includes obtaining the first encrypted payload that is associated with the received first encrypted payload identifier (e.g., action 935). The validation process 930 further includes obtaining the first secret key that was used to generate the first encrypted pay load in the first setup process 810 (i.e., used to encrypt the first payload to arrive at the first encrypted payload). The first secret key is then applied to the obtained first encrypted payload (e.g., action 936) to determine whether or not the obtained first encrypted payload is identical to the first encrypted payload generated in the first setup process 810. If the first secret key is able to decrypt the obtained first encrypted payload, then the obtained first encrypted pay load is the first encrypted pay load generated in the first setup process 810. On the other hand, if the first secret key is unable to decrypt the obtained first encrypted payload, then the obtained first encrypted payload is not the first encrypted payload generated in the first setup process 810. [00175] In an example embodiment, when the obtained first encrypted payload is determined to be decryptable by the first secret key (or the obtained first encrypted payload is determined to be the first encrypted payload generated in the first setup process 810), the validation process 930 further includes obtaining a second validation result (e.g., action 937). The second validation result includes a decrypted version of the obtained first encrypted pay load. For example, the first decryption engine 503 may perform the determination, corresponding decryption of the first encrypted payload, and obtaining of the second validation result.

[00176] Once the first validation result is obtained by decrypting the received second encrypted payload (e.g., action 933) and the second validation result is obtained by decrypting the obtained first encrypted payload (e.g., action 937), the validation process 930 further includes comparing the first validation result with the second validation result (e.g., action 938). For example, the comparator 505 of the validation processor 500 may perform the comparison of the first validation result and the second validation result.

[00177] When the first validation result matches the second validation result, the validation process 930 further includes validating the final information set (e.g., action 939). On the other hand, when the first validation result does not match the second validation result, the validation process 930 does not validate the final information set. In an example embodiment, a validation of the final information set enables a user 10 (or a mobile device 10 of the user 10) to perform any permitted and/or configured action on the final information set 130 (e.g., add/load value, insert messages or other information, transfer to another user, etc.), determine a status of the final information set 130 (e.g., a new final information set 130, or one that is previously used, previously loaded, previously redeemed, etc.), and/or confirm the authenticity, origin, etc. of the final information set 130. For example, the validator 506 of the validation processor 500 may perform the determination of whether or not the final information set is valid (or should be validated).

[00178] Once the final information set 130 is validated (e.g., action 939) by the validator 506, the validation process 930 may further include configuring and/or amending the final information set 130, or properties thereof, to reflect the actions requested/sent/instructed/commanded by the user 10 (or mobile device 10 of the user 10). Such configuring and/or amending of the final information set 130, or properties thereof, may be performed in several ways. For example, the first payload (as generated or obtained in the first setup process 810 (e.g., action 812) may be amended to include, among other things, the user's desired action(s) (e.g., add/load value, insert messages or other information, transfer to another user, etc.), status of the final information set, relevant dates (e.g., creation date, expiry date, etc.), etc. Alternatively or in addition, a separate or additional pay load which is linked to, associated with, attached to, and/or related to the first payload may be amended or created to include, among other things, the user's desired action(s) (e.g., add/load value, insert messages or other information, transfer to another user, etc.), status of the final information set, relevant dates, etc. The validation process 930 may also cooperate and/or interact with external processes and/or systems to execute such user desired action(s) (e.g., cooperate and/or interact with the user's 10 financial institution to withdraw, transfer, and/or deposit a user-specified value). For example, the above actions may be performed by the transaction processor 520 of the validation processor 500.

[00179] Example 1 - Example of setting up an information set.

[00180] As an example of setting up an information set 130, a financial institution may wish to offer to its customers 10 Chinese New Year red envelopes ("red envelopes"), or the like, according to example embodiments of the present disclosure, each of which are capable of being loaded with value by its users 10 (or "givers" 10) and given by such givers 10 to other users 10 (or "recipients" 10). An example embodiment of each red envelope will include, among other things, an information set 130. The information set 130 is validatable by a giver 10 when loading value into the red envelope. The information set 130 is also validatable by a recipient 10 when accepting/receiving the red envelope from the giver 10. When generating a unique information set 130 for each red envelope, the financial institution performs an example embodiment of the validatable information set generation process 800, which, as described in the present disclosure, involves use of, among other elements of the system 100, the first setup processor 230, second setup processor 240, and the information set generator 400. The validatable information set generation process 800 includes performing a first setup process 810, a second setup process 820, and a final information set generation process 830.

[00181] For the first setup process 810, a payload (or first payload) is generated or obtained (e.g., if already generated). The first payload may be or include any unique information (e.g., a unique series of 18-24 characters, or more or less). The first payload may also include editable, configurable, customizable, and/or settable information and/or information fields and/or categories, such as a payload identifier (e.g., the aforementioned unique series of 18-24 characters), status (e.g., valid, deposited, transferred, pending, redeemed, expired, etc.), transaction/action type (e.g., transfer or loading of funds, etc.), value loaded by user 10 (e.g., USD 100), a message (e.g., "Happy Chinese New Year 2021 ! ! ! "), geographical restrictions (if any), creation/setup/configure/initial validation date (e.g., date that a gifter/sender user adds/loads value, uploads a message, etc.), redeem/receive/final validation date (e.g., date that a recipient 10 accepts the added/loaded value), expiry date or redeemable period (or final validation date), a corresponding/associated encrypted payload identifier (e.g., first encrypted payload identifier, as generated by the pay load identifier processor 206), etc. Alternatively, the first payload may include a pointer, reference, relation, association, link, or the like, to another payload that includes one or more of the aforementioned editable, configurable, customizable, and/or settable information and/or information fields and/or categories. The first payload is then encrypted using a first secret key to arrive at a first encrypted payload. The first setup process 810 also includes generating or obtaining an encrypted payload identifier, which may be or include any unique series or sequence of characters (e.g., a unique series of 5-10 characters, or more or less). An association is then created/generated between the first encrypted payload and the first encrypted pay load identifier in such a way that the first encrypted payload can be obtained/searched for based on the first encrypted payload identifier, and vice versa.

[00182] For the second setup process 820, the actual red envelope may be printed by a third party manufacturing company. To ensure security, the manufacturing company may be provided with the first payload, the encrypted payload identifier, a second secret key (which is different from the first secret key) to perform a second encryption, and a desired deep link. The manufacturing company then encrypts the first payload using the second secret key to arrive at a second encrypted payload. A final pay load is then generated to include the second encrypted pay load and a deep link. In this regard, the deep link may include instructions, commands, code, links, and/or the like, for a computing device 10 (e.g., a mobile device 10 of the gifter 10) that receives the deep link (e.g., extracts the deep link from the final information set, as described in the present disclosure) to, among other things, visit or launch a website, link, or the like; launch a particular installed app (e.g., DBS Digibank app, other financial institution apps, payment apps such as PayPal, electronic wallets, social media apps such as Facebook, WeChat, Line, etc.); login to a particularly installed app, website, and/or the like; launch an app distribution platform or store (e.g., Apple App Store, Google Play Store, etc.) to download, install, register, and/or login to a particular app; establish a communication channel 120 between the mobile device 10 of the gifter 10 and an example embodiment of the validation processor 500; and/or transmit, from the mobile device 10 of the gifter 10 to the validation processor 500, data extracted and/or obtained from the information set 130 (including the second encrypted payload and the first encrypted payload identifier 130b). Once the final payload has been generated, the final payload is encoded into a final unique QR code 130a (which may be a unique QR code or any other code). That is, a final unique QR code 130a is generated having the final pay load encoded in the final unique QR code 130a. Alternatively, the second encrypted payload and the deep link may be encoded into the final unique QR code 130a without generating a final payload.

[00183] For the final information set generation process 830, a final information set 130 is generated or assembled having the final unique QR code 130a and the encrypted pay load identifier 130b. The final information set 130 is then printed (or provided, affixed, secured, etc. in other ways) onto the red envelope and made available and/or distributed to users 10 (gifters 10). For example, the red envelopes may be made available at branches of the financial institution, through special-purpose vending machines (which may perform some or all of the above actions of the validatable information set generation process 800 as well), etc. Alternatively or in addition, the red envelopes may be made available via websites, apps, etc. as virtual red envelopes (e.g., downloadable onto an app, mobile device 10, etc.).

[00184] Example 2 - Example of loading value to an information set.

[00185] As an example of loading value to an information set 130, a user 10 (gifter 10) may obtain an example embodiment of the red envelope from Example 1 , such as from a vending machine 600. The red envelope includes an information set 130 provided on the red envelope. To load/add value to the red envelope, the gifter 10 first scans the information set 130 using a mobile device 10 (e.g., camera of the mobile device 10) and performs an information set validation process 900. The information set validation process 900 includes performing an extraction process 910, an executing of a deep link 920, and performing of a validation process 930.

[00186] For the extraction process 910, the mobile device 10 identifies, scans, and/or extracts (each as applicable) from the information set 130 at least the following information: a QR code (i.e., the final unique QR code 130a) and a unique series of characters (i.e., the first encrypted pay load identifier 130b). The final unique QR code 130a is then decoded to obtain the final payload. From the final payload decoded from the final unique QR code 130a, a further extraction is performed to obtain the second encrypted payload and the deep link from the final payload.

[00187] For the deep link execution process 920, the mobile device 10 executes the deep link, which includes instructions, commands, code, links, and/or the like, for the mobile device 10 to, among other things, visit or launch a website, link, or the like; launch a particular installed app (e.g., DBS Digibank app, other financial institution apps, payment apps such as PayPal, electronic wallets, social media apps such as Facebook, WeChat, Line, etc.); login to a particularly installed app, website, and/or the like; launch an app distribution platform or store (e.g., Apple App Store, Google Play Store, etc.) to download, install, register, and/or login to a particular app. The executing of the deep link also includes establishing a communication channel 120 between the mobile device 10 of the gifter 10 and an example embodiment of the validation processor 500, and sending or making available the second encrypted payload and the first encrypted payload identifier 130b to the validation processor 500.

[00188] For the validation process 930, the validation processor 500 receives a request from the mobile device 10 of the gifter 10 to validate the information set 130 of the red envelope. To do so, the validation processor 500 receives and processes the second encrypted payload (referred to as the "received second encrypted pay load", which may or may not be the same as the second encrypted payload generated during the second setup process 820) and the first encrypted payload identifier 130b (referred to as the "received first encrypted pay load identifier" or "received encrypted payload identifier", which may or may not be the same as the encrypted payload identifier generated or obtained in the first setup process 810) from the mobile device 10.

[00189] To validate the received second encrypted payload (i.e., to confirm the received second encrypted payload is the same as the second encrypted payload generated during the second setup process 820), the validation process 930 first obtains the second secret key that was used to encrypt the second encrypted payload in the second setup process 820. The second secret key is then applied to the received second encrypted payload to determine whether or not the received second encrypted payload is identical to the second encrypted payload generated in the second setup process 820. If the second secret key is able to decrypt the received second encrypted payload, then the received second encrypted payload is the second encrypted payload generated in the second setup process 820. On the other hand, if the second secret key is unable to decrypt the received second encrypted pay load, then the received second encrypted payload is not the second encrypted payload generated in the second setup process 820. When the received second encrypted payload is determined to be decryptable by the second secret key, a first validation result is obtained. The first validation result includes a decrypted version of the received second encrypted payload, as decrypted by the second secret key. [00190] To validate the received first encrypted pay load identifier, the validation process 930 includes performing an association search (e.g., in the first database 110) using the received first encrypted payload identifier as a search query. If the received first encrypted payload identifier is able to locate the first encrypted payload, then the received first encrypted payload is associated with the first encrypted payload. When the association search (using the received first encrypted payload identifier 130a as a search query) determines that the received first encrypted payload identifier is associated with the first encrypted payload, the validation process 930 further includes obtaining the first encrypted payload that is associated with the received first encrypted payload identifier and obtaining the first secret key that was used to encrypt the first encrypted payload in the first setup process 810. The first secret key is then applied to the obtained first encrypted payload to determine whether or not the obtained first encrypted pay load is identical to the first encrypted pay load generated in the first setup process 810. If the first secret key is able to decrypt the obtained first encrypted payload, then the obtained first encrypted payload is the first encrypted payload generated in the first setup process 810. On the other hand, if the first secret key is unable to decrypt the obtained first encrypted payload, then the obtained first encrypted payload is not the first encrypted payload generated in the first setup process 810. When the obtained first encrypted pay load is determined to be decryptable by the first secret key, a second validation result is obtained. The second validation result includes a decrypted version of the obtained first encrypted payload, as decrypted by the first secret key. The validation process 930 then compares the first validation result with the second validation result. When the first validation result matches the second validation result, the validation process 930 concludes that the information set 130 is validated. On the other hand, when the first validation result does not match the second validation result, the validation process 930 concludes that the information set 130 is not valid or not validated. When an information set is validated, a gifter 10 (or a mobile device 10 of the gifter 10) can then perform any permitted and/or configured action (e.g., as permitted or configured by the financial institution and/or the system 100) on, for, with, etc. the information set 130. For example, the gifter 10 can add/load value, insert messages or other information, transfer to another user, change added/loaded value, cancel, etc. The gifter 10 can also determine a status of the information set 130 (e.g., a new final information set 130, or one that is previously used, previously loaded, previously redeemed, etc.), and/or confirm the authenticity, origin, etc. of the information set 130. When a gifter 10 performs a permitted and/or configured action on the information set 130, the validation process 930 may include amending or adding to the first payload (as generated or obtained in the first setup process 810) to reflect the desired gifter's action(s) (e.g., add/load value, insert messages or other information, transfer to another user, etc.), etc. Alternatively or in addition, a separate or additional payload which is linked to, associated with, attached to, and/or related to the first pay load may be amended or created to include, among other things, the gifter's desired action(s), etc. The validation process 930 may also cooperate and/or interact with external processes and/or systems to execute such user desired action(s) (e.g., cooperate and/or interact with systems of the financial institution to withdraw, transfer, and/or deposit a user- specified value from available funds of the gifter 10).

[00191] Example 3 - Example of receiving value from an information set.

[00192] As an example of receiving value from an information set 130, a user 10 (gifter 10) who has validated an information set 130 by performing example embodiments described in Example 2 may have loaded value (e.g., SGD 50, 0.0006 BTC, or any other form of value) into the red envelope. The gifter 10 may then give the red envelope to another user 10 (recipient 10). As described above, an example embodiment of the red envelope includes an information set 130 provided on the red envelope.

[00193] To receive the added/loaded value from the red envelope, the receiver 10 scans the information set 130 using a mobile device 10 of the gifter 10 (e.g., camera of the mobile device 10), which then performs an example embodiment of the information set validation process 900. The information set validation process 900 includes performing an extraction process 910, an executing of a deep link 920, and performing of a validation process 930.

[00194] For the extraction process 910, the mobile device 10 identifies, scans, and/or extracts (each as applicable) from the information set 130 at least the following information: a candidate QR code (which may be the final unique QR code 130a) and a candidate first encrypted payload identifier (which may be the first encrypted payload identifier 130b). The candidate QR code is then decoded to obtain a candidate final payload (which may be the final payload). From the candidate final payload, a further extraction is performed to obtain a candidate second encrypted payload (which may be the second encrypted payload) and a candidate deep link (which may be the deep link generated in the second setup process 820) from the final payload.

[00195] For the deep link execution process 920, the mobile device 10 executes the candidate deep link, which includes instructions, commands, code, links, and/or the like, for the mobile device 10 to, among other things, visit or launch a website, link, or the like; launch a particular installed app (e.g., DBS Digibank app, other financial institution apps, payment apps such as PayPal, electronic wallets, social media apps such as Facebook, WeChat, Line, etc.); login to a particularly installed app, website, and/or the like; launch an app distribution platform or store (e.g., Apple App Store, Google Play Store, etc.) to download, install, register, and/or login to a particular app. The executing of the candidate deep link also includes establishing a communication channel 120 between the mobile device 10 of the gifter 10 and an example embodiment of the validation processor 500. The executing of the candidate deep link further includes sending or making available the candidate second encrypted payload and the candidate first encrypted payload identifier to the validation processor 500. [00196] For the validation process 930, the validation processor 500 receives a request from the mobile device 10 of the gifter 10 to validate the information set 130 of the red envelope. To do so, the validation processor 500 receives and processes the candidate second encrypted payload and the candidate first encrypted payload identifier 130b from the mobile device 10.

[00197] To validate the candidate second encrypted payload (i.e., to confirm the candidate second encrypted payload is the same as or equal to the second encrypted payload generated during the second setup process 820), the validation process 930 first obtains the second secret key that was used to encrypt the second encrypted payload in the second setup process 820. The second secret key is then applied to the candidate second encrypted payload to determine whether or not the candidate second encrypted payload is identical to the second encrypted payload generated in the second setup process 820. If the second secret key is able to decrypt the candidate second encrypted payload, then the candidate second encrypted payload is the second encrypted payload generated in the second setup process 820. On the other hand, if the second secret key is unable to decrypt the candidate second encrypted payload, then the candidate second encrypted payload is not the second encrypted payload generated in the second setup process 820. When the candidate second encrypted payload is determined to be decryptable by the second secret key, a first validation result is obtained. The first validation result includes a decrypted version of the candidate second encrypted pay load, as decrypted by the second secret key.

[00198] To validate the candidate first encrypted pay load identifier, the validation process 930 includes performing an association search (e.g., in the first database 110) using the candidate first encrypted payload identifier as a search query. If the candidate first encrypted payload identifier is able to locate a result (referred to as a "candidate first encrypted payload"), then the candidate first encrypted payload identifier is determined to be associated with the candidate first encrypted payload. When the association search (using the candidate first encrypted payload identifier as a search query) determines that the candidate first encrypted payload identifier is associated with the candidate first encrypted pay load, the validation process 930 further includes obtaining the candidate first encrypted payload that is associated with the candidate first encrypted payload identifier and also obtaining the first secret key that was used to encrypt the first encrypted payload in the first setup process 810. The first secret key is then applied to the candidate first encrypted payload to determine whether or not the candidate first encrypted payload is identical to the first encrypted payload generated in the first setup process 810. If the first secret key is able to decrypt the candidate first encrypted pay load, then the candidate first encrypted payload is the first encrypted payload generated in the first setup process 810. On the other hand, if the first secret key is unable to decrypt the candidate first encrypted payload, then the candidate first encrypted payload is not the first encrypted payload generated in the first setup process 810. When the candidate first encrypted payload is determined to be decryptable by the first secret key, a second validation result is obtained. The second validation result includes a decrypted version of the candidate first encrypted payload, as decrypted by the first secret key. The validation process 930 then compares the first validation result (i.e., decrypted candidate first encrypted pay load) with the second validation result (i.e., decrypted candidate second encrypted payload). When the first validation result matches the second validation result, the validation process 930 concludes that the information set 130 is successfully validated (and the candidate first encrypted payload is the same as the first encrypted payload, the candidate first encrypted payload identifier is the same as the first encrypted payload identifier 130a, the candidate second encrypted payload identifier is the same as the second encrypted payload identifier, the candidate deep link is the same as the deep link generated in the second setup process 820, the candidate QR code is the same as the final unique QR code 130a, and the candidate final payload is the same as the final payload). On the other hand, when the first validation result does not match the second validation result, the validation process 930 concludes that the information set 130 is not valid or not validated.

[00199] When an information set 130 is validated, a gifter 10 (or a mobile device 10 of the gifter 10) can then perform any permitted and/or configured action (e.g., as permitted or configured by the financial institution and/or the system 100) on, for, with, etc. the information set 130. For example, the gifter 10 can add/load value, insert messages or other information, transfer to another user, change added/loaded value, cancel, etc. The gifter 10 can also determine a status of the information set 130 (e.g., a new final information set 130, or one that is previously used, previously loaded, previously redeemed, etc.), and/or confirm the authenticity, origin, etc. of the information set 130. When a gifter 10 performs a permitted and/or configured action on the information set 130, the validation process 930 may include amending and/or adding to the first payload (as generated or obtained in the first setup process 810) to reflect the desired gifter's action(s) (e.g., add/load value, insert messages or other information, transfer to another user, etc.), etc. Alternatively or in addition, a separate or additional payload which is linked to, associated with, attached to, and/or related to the first payload may be amended or created to include, among other things, the gifter's desired action(s), etc. The validation process 930 may also cooperate and/or interact with external processes and/or systems (not shown) to execute such user desired action(s) (e.g., cooperate and/or interact with systems of the financial institution to withdraw a user-specified value from a financial account, electronic wallet, virtual account, etc. of the gifter 10; and cooperate and/or interact with systems of another financial institution or payment gateway/processor to receive and deposit such user-specified value into a financial account, electronic wallet, virtual account, etc. of the recipient 10).

[00200] While various embodiments in accordance with the disclosed principles have been described above, it should be understood that they have been presented by way of example only, and are not limiting. Thus, the breadth and scope of the example embodiments described in the present disclosure should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the claims and their equivalents issuing from this disclosure. Furthermore, the above advantages and features are provided in described embodiments, but shall not limit the application of such issued claims to processes and structures accomplishing any or all of the above advantages.

[00201] For example, "communication," "communicate," "connection," "connect," "call," "calling," or other similar terms should generally be construed broadly to mean a wired, wireless, and/or other form of, as applicable, connection between elements, devices, computing devices, telephones, processors, controllers, servers, networks, telephone networks, the cloud, and/or the like, which enable voice and/or data to be sent, transmitted, broadcasted, received, intercepted, acquired, and/or transferred (each as applicable).

[00202] Also, as referred to herein, a processor, device, computing device, telephone, phone, server, gateway server, communication gateway server, and/or controller, may be any processor, computing device, and/or communication device, and may include a virtual machine, computer, node, instance, host, or machine in a networked computing environment. Also as referred to herein, a network or cloud may be or include a collection of machines connected by communication channels that facilitate communications between machines and allow for machines to share resources. Network may also refer to a communication medium between processes on the same machine. Also as referred to herein, a network element, node, or server may be a machine deployed to execute a program operating as a socket listener and may include software instances.

[00203] Database (or memory or storage) may comprise any collection and/or arrangement of volatile and/or non-volatile components suitable for storing data. For example, memory may comprise random access memory (RAM) devices, read-only memory (ROM) devices, magnetic storage devices, optical storage devices, solid state devices, and/or any other suitable data storage devices. In particular embodiments, database may represent, in part, computer-readable storage media on which computer instructions and/or logic are encoded. Database may represent any number of memory components within, local to, and/or accessible by a processor and/or computing device. [00204] Various terms used herein have special meanings within the present technical field. Whether a particular term should be construed as such a "term of art" depends on the context in which that term is used. Such terms are to be construed in light of the context in which they are used in the present disclosure and as one of ordinary skill in the art would understand those terms in the disclosed context. The above definitions are not exclusive of other meanings that might be imparted to those terms based on the disclosed context.

[00205] Words of comparison, measurement, and timing such as "at the time," "equivalent," "during," "complete," and the like should be understood to mean "substantially at the time," "substantially equivalent," "substantially during," "substantially complete," etc., where "substantially" means that such comparisons, measurements, and timings are practicable to accomplish the implicitly or expressly stated desired result.

Additionally, the section headings and topic headings herein are provided for consistency with the suggestions under various patent regulations and practice, or otherwise to provide organizational cues. These headings shall not limit or characterize the embodiments set out in any claims that may issue from this disclosure. Specifically, a description of a technology in the "Background" is not to be construed as an admission that technology is prior art to any embodiments in this disclosure. Furthermore, any reference in this disclosure to "invention" in the singular should not be used to argue that there is only a single point of novelty in this disclosure. Multiple inventions may be set forth according to the limitations of the claims issuing from this disclosure, and such claims accordingly define the invention(s), and their equivalents, that are protected thereby. In all instances, the scope of such claims shall be considered on their own merits in light of this disclosure, but should not be constrained by the headings herein.