Patent Publication Number: US-2022217136-A1

Title: Identity verification through multisystem cooperation

Description:
TECHNICAL FIELD 
     The present disclosure relates generally to multisystem data transferring and, more specifically, to identity verification through multisystem cooperation. 
     BACKGROUND 
     The internet has enabled individuals to interact with organizations and other entities without ever stepping foot inside the physical buildings operated by the entities. For example, an individual may provide information to an entity simply by entering the information into a form displayed on a webpage belonging to the entity or otherwise transmitting the information electronically to the entity. 
     SUMMARY 
     This disclosure contemplates an identity verification system that may be used to help verify the identity of a user who is providing electronic information to an entity system. In particular, the disclosed system may be used to verify a user&#39;s identity when the user is attempting to engage in an electronic transaction with an entity system by using an internet-connected device to provide account information to the entity system. When the user enters an account number into a field displayed on a webpage of the entity, a system associated with the institution at which the user&#39;s account is held generates a validation number for the transaction. The institution system then transmits this validation number to a second device, which the user/account holder had previously registered with the system. After receiving the validation number on his/her second device, the user enters the validation number into the webpage displayed on his/her first device and transmits it to the entity system as part of the user&#39;s transaction request. The entity system then provides the validation number that it received from the user back to the institution system for authentication. If the validation number received by the institution system matches the validation number that the institution system originally transmitted to the second device, the institution system determines that the user who is attempting to conduct the transaction with the entity system is in fact the account holder (as opposed to an individual who has obtained the account holder&#39;s information and is attempting to impersonate the account holder), and instructs the entity system to approve the requested transaction. On the other hand, if the received validation number does not match the validation number originally transmitted by the institution system to the second device, the institution system instructs the entity system to decline the requested transaction. An embodiment of the identity verification system is described below. 
     According to one embodiment, a system includes a first subsystem associated with an institution and a second subsystem associated with an entity. The first subsystem includes a memory and a hardware processor communicatively coupled to the memory. The second subsystem includes a hardware processor. The hardware processor of the first subsystem receives, from a first user device, a request for a validation number. The first user device transmitted the request for the validation number in response to a determination that an account number had been entered into a first field of a webpage displayed on the first user device. The webpage is associated with the entity. The account number corresponds to an account held at the institution. In response to receiving the request for the validation number, the processor of the first subsystem randomly generates the validation number. The processor of the first subsystem also stores a copy of the validation number in the memory. The processor of the first subsystem additionally transmits the validation number to a second user device associated with the account. The hardware processor of the second subsystem receives, from the first user device, a request for a transaction. The request for the transaction includes the validation number. The first user device transmitted the request for the transaction in response to the second user device receiving the validation number and the validation number being entered into a second field of the webpage displayed on the first user device. The processor of the second subsystem also transmits the validation number received in the request for the transaction to the first subsystem. In response to receiving the validation number, the hardware processor of the first subsystem determines that the validation number received from the second subsystem matches the copy of the validation number stored in the memory. In response to determining that the validation number received from the second subsystem matches the copy of the validation number stored in the memory, the processor of the first subsystem transmits a message to the second subsystem authorizing the transaction. 
     Certain embodiments provide one or more technical advantages. As an example, an embodiment includes a mobile device application that, in response to the mobile device receiving a validation number, is configured to automatically display a pop-up notification of the validation number on the mobile device display. In this manner, the embodiment enables a user of the mobile device to efficiently access the validation number, and conserves processing resources that would otherwise be expended by the user using his/her mobile device to navigate to the mobile application and accessing the validation number within the mobile application. As another example, in certain embodiments, a user device is configured to determine when a user has entered an account number into a field displayed on a webpage and, in response, automatically replace the account verification fields traditionally displayed on the webpage with a field for input of a validation number. In this manner, certain embodiments conserve the processing and networking resources that would otherwise be expended by (1) the device transmitting the account number and the traditional account verification data to a merchant system, (2) the merchant system determining that the account number belongs to an institution for which the user should transmit a validation number to the merchant system, and (3) the merchant system transmitting a request to the user&#39;s device to display a field for input of the validation number. The system described in the present disclosure may particularly be integrated into a practical application of an identity verification system for use by an institution that conducts electronic transactions on behalf of its account holders, who initiate the transactions by providing account details to entities through webpages belonging to the entities. 
     Certain embodiments may include none, some, or all of the above technical advantages. One or more other technical advantages may be readily apparent to one skilled in the art form the figures, descriptions, and claims included herein. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       For a more complete understanding of the present disclosure, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which: 
         FIG. 1  illustrates an example identity verification system; and 
         FIGS. 2A and 2B  present a flowchart illustrating a method by which the first user device, second user device, institution system, and entity system of the identity verification system of  FIG. 1  act cooperatively to verify the identity of a user who is attempting to engage in a transaction with the entity system. 
     
    
    
     DETAILED DESCRIPTION 
     Embodiments of the present disclosure and its advantages may be understood by referring to  FIGS. 1 through 2B  of the drawings, like numerals being used for like and corresponding parts of the various drawings. 
     I. System Overview 
       FIG. 1  illustrates an example identity verification system  100  that includes first device  102 , user  104 , second device  106 , network  108 , entity system  110 , and institution system  112 . Entity system  110  is associated with an entity with which user  104  may conduct a transaction. Institution system  112  is associated with an institution at which user  104  holds an account that user  104  may use to conduct the transaction. Generally, when user  104  attempts to engage in a transaction with entity system  110  using first device  102 , institution system  112 , entity system  110 , first device  102 , and second device  106  act cooperatively to verify the identify of user  104 , with the aid of a validation number  130 , generated by institution system  112  for the transaction. While described throughout this disclosure as being a number, validation number  130  may be any suitable sequence of characters. For example, in certain embodiments, validation number  130  may be an alphanumeric number, or any other suitable sequence of characters. Details of the manner by which validation number  130  is generated and subsequently used by first device  102 , second device  106 , entity system  110 , and institution system  112  to confirm the identity of user  104  are presented below, and in the discussion of  FIGS. 2A and 2B . 
     First device  102  and second device  106  are used by user  104  to communicate with components of system  100  over network  108 . As illustrated in  FIG. 1 , in certain embodiments first device  102  and second device  106  are separate devices. In some embodiments, first device  102  and second device  106  are the same device. For example, first device  102  and second device  106  may both correspond to a smart phone operated by user  104 . 
     First device  102  includes display  114 . First device  102  is configured to display a webpage  116  belonging to entity system  110  on display  114 . For example, user  104  may use first device  102  to access a web browser installed on first device  102  and use the web browser to navigate to webpage  116 . Webpage  116  is an interactive webpage through which user  104  may initiate a transaction with entity system  110 . For example, user  104  may use webpage  116  to purchase one or more goods from the entity associated with entity system  110 . As illustrated in  FIG. 1 , webpage  116  may display one or more fields  140   a/b . For example, webpage  116  may display a first field  140   a  for input of an account number  136 , and a second field  140   b  for input of a validation number  130 . While illustrated in  FIG. 1  as including two fields  140   a/b , webpage  116  may display any number of fields  140   a/b . Furthermore, in certain embodiments, webpage  116  may be configured to adjust the number of displayed fields  140   a/b  in response to receiving input from user  104 . For example, in certain embodiments, when webpage  116  first loads, webpage  116  may be configured to display a set of fields  140   a/b  that includes a field for input of a credit/bank card number, a field for input of an expiry date of the credit/bank card, and a field for input of a card verification value (CVV) number. Then, in response to user  104  entering a credit/bank card number that is associated with institution system  112 , device  102  may be configured to replace the field for input of the expiry date of the credit/bank card and the field for input of the CVV number with a field  140   b  for input of a validation number  130 . 
     In response to user  104  entering an account number  136  that is associated with institution system  112  into first field  140   a , first device  102  is configured to transmit transaction initiation message  138  to institution system  112 . As described in further detail below, and in the discussion of  FIGS. 2A and 2B , transaction initiation message  138  is used by first device  102  to request that institution system  112  generate a validation number  130  for the transaction that user  104  is initiating. First device  102  may be configured to determine that user  104  has entered an account number  136  that is associated with institution system  112  into field  140   a  in any suitable manner. For example, in certain embodiments, device  102  is configured to make this determination based on the first four numbers of account number  136 . In response to user  104  entering a validation number  130  into second field  140   b , first device  102  is configured to transmit transaction request  144  to entity system  110 . Transaction request  144  includes account number  136  and validation number  130 . As described in further detail below, and in the discussion of  FIGS. 2A and 2B , entity system  110  uses the information transmitted in transaction request  144  to verify user  104 &#39;s identity and to process the requested transaction. 
     First device  102  includes any appropriate device for displaying webpage  116  and for communicating with components of system  100  over network  108 . For example, first device  102  may be a mobile phone, a computer, a laptop, a tablet, an IoT device, and/or an automated assistant, among others. In addition to including display  114 , first device  102  may include any other appropriate user interface, such as a microphone, keypad, or other appropriate terminal equipment usable by user  104 . In some embodiments, an application executed by a processor of first device  102  may perform the functions described herein. 
     Second device  106  is configured to receive validation number  130  from institution system  112  and present validation number  130  to user  104 . Second device  106  may be configured to receive and present validation number  130  to user  104  in any suitable manner. As an example, in certain embodiments, an application installed on second device  106  is configured to receive validation number  130  from institution system  112  and to present validation number  130  to user  104 . For example, the application may be configured to automatically generate a pop-up notification  142  that includes validation number  130  on the display  107  of second device  106 . In some embodiments, second device  106  may automatically turn on display  107  in order to present pop-up notification  142  to user  104 . In this manner, second device  106  may display validation number  130  to user  104  even though user  104  is not actively operating second device  106 . In certain embodiments, second device  106  may be configured to display pop-up notification  142  to user  104  for a set amount of time, after which validation number  130  may no longer be available to user  104 . In some embodiments, user  106  may be able to view validation number  130  even after pop-up notification  142  has disappeared from display  107 . For example, in such embodiments, user  104  may view validation number  130  by navigating to the application that generated pop-up notification  142  and viewing validation number  130  within the application. As another example of the manner by which second device  106  may present validation number  130  to user  104 , in certain embodiments, second device  106  may receive validation number  130  from institution system  112  in an SMS message or any other electronic message (e.g., email), and present the electronic message to user  104  on display  107 . As a further example, in certain embodiments in which second device  106  is the same device as first device  102 , in response to receiving validation number  130  from institution system  112 , second device  106  may be configured to automatically populate second field  140   b , displayed on webpage  116 , with validation number  130 . 
     Second device  106  includes any appropriate mobile device for displaying validation number  130  to user  104 , and for communicating with components of system  100  over network  108 . For example, second device  102  may be a mobile phone, a laptop, a tablet, an IoT device, and/or an automated assistant, among others. In addition to including display  107 , second device  102  may include any other appropriate user interface, such as a microphone, keypad, or other appropriate terminal equipment usable by user  104 . In some embodiments, an application executed by a processor of second device  106  may perform the functions described herein. 
     Network  108  facilitates communication between and amongst the various components of system  100 . This disclosure contemplates network  108  being any suitable network operable to facilitate communication between such components. Network  108  may include any interconnecting system capable of transmitting audio, video, signals, data, messages, or any combination of the preceding. Network  108  may include all or a portion of a public switched telephone network (PSTN), a public or private data network, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a local, regional, or global communication or computer network, such as the Internet, a wireline or wireless network, an enterprise intranet, or any other suitable communication link, including combinations thereof, operable to facilitate communication between the components. 
     Entity system  110  is associated with a given entity with which user  104  is attempting to engage in a transaction. For example, entity system  110  may belong to a merchant with an online store, and/or any other entity with which user  104  may attempt to engage in a transaction. As illustrated in  FIG. 1 , entity system  110  includes a processor  118  and a memory  120 . This disclosure contemplates processor  118  and memory  120  being configured to perform any of the functions of entity system  110  described herein. For example, processor  118  may execute instructions  122  stored in memory  120  to perform any of the functions described herein. Generally, entity system  110  is configured to: (1) receive a transaction request  144  from first device  102  that includes a validation number  130 ; (2) provide the received validation number  130  to institution system  112  for authentication; (3) receive an authentication result  148  back from institution system  112 , indicating whether or not the validation number  130  received from first device  102  matches the validation number  130  stored by institution system  112 ; and (4) approve or decline transaction request  144  based on authentication result  148 . These functions of entity system  110  are described in further detail below, in the discussion of  FIGS. 2A and 2B . 
     Processor  118  is any electronic circuitry, including, but not limited to central processing units (CPUs), graphics processing units (GPUs), microprocessors, application specific integrated circuits (ASIC), application specific instruction set processor (ASIP), and/or state machines, that communicatively couples to memory  120  and controls the operation of entity system  110 . Processor  118  may be 8-bit, 16-bit, 32-bit, 64-bit or of any other suitable architecture. Processor  118  may include an arithmetic logic unit (ALU) for performing arithmetic and logic operations, processor registers that supply operands to the ALU and store the results of ALU operations, and a control unit that fetches instructions from memory and executes them by directing the coordinated operations of the ALU, registers and other components. Processor  118  may include other hardware and software that operates to control and process information. Processor  118  executes software, such as instructions  122 , stored on memory to perform any of the functions described herein. Processor  118  controls the operation and administration of entity system  110  by processing information received from first device  102 , second device  106 , network  108 , and/or institution system  112 . Processor  118  may be a programmable logic device, a microcontroller, a microprocessor, any suitable processing device, or any suitable combination of the preceding. Processor  118  is not limited to a single processing device and may encompass multiple processing devices. In certain embodiments in which processor  118  encompasses multiple processing devices, such devices may be located at geographically separate locations from one another and connected to one another by a network (e.g., network  108 ). 
     Memory  120  may store, either permanently or temporarily, data, operational software, or other information for processor  118 , such as instructions  122 . Memory  120  may include any one or a combination of volatile or non-volatile local or remote devices suitable for storing information. For example, memory  120  may include random access memory (RAM), read only memory (ROM), magnetic storage devices, optical storage devices, or any other suitable information storage device or a combination of these devices. The software represents any suitable set of instructions, logic, or code embodied in a computer-readable storage medium. For example, the software may be embodied in memory  120 , a disk, a CD, or a flash drive. In particular embodiments, the software may include an application, such as instructions  122 , executable by processor  118  to perform one or more of the functions described herein. 
     Institution system  112  is associated with a given institution at which user  104  holds an account that the user may use to complete a transaction with entity system  110 . For example, institution system  112  may belong to a bank, a credit card company, and/or any other financial institution with which user  104  may hold an account. As illustrated in  FIG. 1 , institution system  112  includes a processor  124  and a memory  126 . This disclosure contemplates processor  124  and memory  126  being configured to perform any of the functions of institution system  112  described herein. For example, processor  124  may execute instructions  128  stored in memory  126  to perform any of the functions described herein. Generally, institution system  112  is configured to: (1) receive transaction initiation message  138  from first device  102 , indicating that user  104  is attempting to initiate a transaction with entity system  110 ; (2) in response to receiving transaction initiation message  138 , randomly generate a validation number  130  for the transaction; (3) store a copy of validation number  130  in memory  126 ; (4) transmit validation number  130  to second device  106 ; (5) receive an authentication request  146  from entity system  110 , which includes a validation number  130  received by entity system  110  from first device  102 ; (6) compare the received validation number  130  with the copy of the validation number  130  stored in memory  126 ; and (7) transmit a message  148  to entity system  110  instructing entity system  110  to approve or decline transaction request  144 , based on the results of the comparison. These functions of institution system  112  are described in further detail below, in the discussion of  FIGS. 2A and 2B . 
     Processor  124  is any electronic circuitry, including, but not limited to central processing units (CPUs), graphics processing units (GPUs), microprocessors, application specific integrated circuits (ASIC), application specific instruction set processor (ASIP), and/or state machines, that communicatively couples to memory  126  and controls the operation of institution system  112 . Processor  124  may be 8-bit, 16-bit, 32-bit, 64-bit or of any other suitable architecture. Processor  124  may include an arithmetic logic unit (ALU) for performing arithmetic and logic operations, processor registers that supply operands to the ALU and store the results of ALU operations, and a control unit that fetches instructions from memory and executes them by directing the coordinated operations of the ALU, registers and other components. Processor  124  may include other hardware and software that operates to control and process information. Processor  124  executes software, such as instructions  128 , stored on memory to perform any of the functions described herein. Processor  124  controls the operation and administration of institution system  112  by processing information received from first device  102 , second device  106 , network  108 , and/or entity system  110 . Processor  124  may be a programmable logic device, a microcontroller, a microprocessor, any suitable processing device, or any suitable combination of the preceding. Processor  124  is not limited to a single processing device and may encompass multiple processing devices. In certain embodiments in which processor  124  encompasses multiple processing devices, such devices may be located at geographically separate locations from one another and connected to one another by a network (e.g., network  108 ). 
     Memory  126  may store, either permanently or temporarily, data, operational software, or other information for processor  124 , such as instructions  128 . Memory  126  may include any one or a combination of volatile or non-volatile local or remote devices suitable for storing information. For example, memory  126  may include random access memory (RAM), read only memory (ROM), magnetic storage devices, optical storage devices, or any other suitable information storage device or a combination of these devices. The software represents any suitable set of instructions, logic, or code embodied in a computer-readable storage medium. For example, the software may be embodied in memory  126 , a disk, a CD, or a flash drive. In particular embodiments, the software may include an application, such as instructions  128 , executable by processor  124  to perform one or more of the functions described herein. 
     Memory  126  also stores copies of the validation numbers  130   a  through  130   n  that have been generated by institution system  112 . In certain embodiments, memory  126  stores copies of the validation numbers that it has generated and that are outstanding. For example, memory  126  stores copies of the validation numbers that institution system  112  has not yet received back from entity system  110  in authentication requests  146 . In some embodiments, memory  126  stores a full set of historical validation numbers  130   a  through  130   n  (e.g., copies of both the outstanding validation numbers  130  and those validation numbers  130  that institution system  112  has received back from entity system  110  in authentication requests  146 ). Institution system  112  may use this full set of historical validation numbers  130   a  through  130   n  to help ensure that any new validation numbers  130  that it generates have not previously been used for identity verification purposes, as described in further detail below, in the discussion of  FIGS. 2A and 2B . 
     In certain embodiments, memory  126  also stores a set of times  132  and a set of account details  134 . Each time of the set of times  132  is associated with a validation number  130 , and corresponds to the time at which the validation number was generated by institution system  112 . In certain embodiments, validation numbers  130  may expire after a certain amount of time. In such embodiments, institution system  112  uses set of times  132  to determine whether or not a validation number  130  received in an authentication request  146  has expired, as described in further detail below, in the discussion of  FIGS. 2A and 2B . In certain embodiments, for each user  104  who holds an account with the institution associated with institution system  112 , account details  134  stores information about the user and/or his/her account. For example, for a given user  104 , account details  134  may store the account number  136  assigned to the user&#39;s account as well as an identification of second device  106 , to which institution system  112  should send validation numbers  130 , and/or any other information that institution system  112  may use to transmit validation numbers  130  to second device  106 . For example, account details  134  may include a cell phone number assigned to second device  106 , an email address belonging to user  104 , and/or any other suitable identification information that may be used to transmit validation number  130  to second device  106 . 
     Modifications, additions, or omissions may be made to the systems described herein without departing from the scope of the invention. For example, system  100  may include any number of users  104 , first devices  102 , second devices  106 , entity system  110 , and institution systems  112 . The components may be integrated or separated. Moreover, the operations may be performed by more, fewer, or other components. Additionally, the operations may be performed using any suitable logic comprising software, hardware, and/or other logic.  FIGS. 2A and 2B  present a flowchart (described in conjunction with elements of  FIG. 1 ) illustrating an example method  200  by which first device  102 , second device  106 , institution system  112 , and entity system  110  act cooperatively to verify the identify of a user  104  who is attempted to engage in a transaction with entity system  110 . 
     In step  202  first device  102  determines whether or not user  104  has entered an account number  136  into a field  140   a  of a webpage  116  associated with entity system  110 . If, in step  202  first device  102  determines that user  104  has entered an account number  136  into field  140   a , in step  204  first device  102  transmits a message  138  to institutions system  112  requesting that institution system  112  generate a validation number  130 . In step  206  institution system  112  randomly generates a validation number  130 . Institution system  112  may randomly generate validation number  130  in any suitable manner. As an example, in certain embodiments in which validation number  130  corresponds to a sequence of numerical digits, institution system  112  may generate validation number  130  using a random number generator stored in memory  126 . For example, institution system  112  may use the random number generator to generate a validation number  130  that is 5 digits in length, 10 digits in length, or any other suitable length. In some embodiments, institution system  112  may use the random number generator to randomly generate a length for the validation number as well as to randomly generate the digits that make up the validation number. In certain embodiments in which validation number  130  is an alphanumeric number, institution system  112  may use the random number generator to: (1) randomly determine a length for the validation number; (2) randomly determine a number of letters to include in the validation number, randomly determine those letters, and randomly assign each of those letters to a position within the validation number; (3) randomly determine a number of digits to include in the validation number, randomly determine those digits, and randomly assign each of those digits to a position within the validation number; and/or (4) randomly determine a number of wildcard characters to include in the validation number, randomly determine those wildcard characters, and randomly assign each of those wildcard characters to a position within the validation number. 
     In step  208  institution system  112  compares the randomly generated validation number  130  to historical validation numbers  130   a  through  130   n  stored in memory  120  to determine whether or not the validation number  130  already exists. If, in step  208  institution system  112  determines that validation number  130  already exists in memory  126 , method  200  returns to step  206 , where institution system  112  randomly generates a new validation number  130 . If, in step  208  institution system  112  determines that validation number  130  does not already exist in memory  126 , in step  210  institution system  112  transmit validation number  130  to second device  106 . In step  212  second device  106  displays validation number  130  to user  104  on display  107 . In response to second device  106  displaying validation number  130 , user  104  may enter validation number  130  into a second field  140   b  of the webpage  116  that is displayed on first device  102 . 
     In step  214  first device  102  determines whether user  104  has entered validation number  130  into second field  140   b  of webpage  116 . If, in step  214  first device  102  determines that user  104  has entered validation number  130  into second field  140   b , in step  216  first device  102  transmits validation number  130  to entity system  110  in transaction request  144 . In step  218  entity system  110  determines whether or not it has received validation number  130 . If, in step  218  entity system  100  determine that it has received validation number  130 , in step  220  entity system  110  transmits the received validation number  130  to institution system  112  for authentication. 
     In step  222  institution system  112  determines whether or not the validation number  130  received from entity system  110  matches the copy of the original validation number  130  that institution system  112  transmitted to second device  106 . In certain embodiments, institution system  112  additionally determines whether or not it has received the validation number within a threshold amount of time since it first generated the validation number (e.g., whether or not the validation number has expired). If, in step  222  institution system  112  determines that the validation number  130  received from entity system  110  does not match the copy of the validation number  130  stored in memory  126  and/or that the validation number  130  has been received after the threshold amount of time since it was first generated, in step  226  institution system  112  generates message  148  instructing entity system  110  to decline user  104 &#39;s transaction request  144 . If, in step  222  institution system  112  determines that the validation number  130  received from entity system  110  matches the copy of the validation number  130  stored in memory  126  and, in certain embodiments, that the validation number  130  was received within the threshold time since its creation, in step  224  institution system generates message  148  instructing entity system  110  to approve user  104 &#39;s transaction request  144 . In step  228  institution system  112  transmits message  148  to entity system  110 . In certain embodiments, in step  230  institution system  112  also sends instructions to second device  106  to delete any copies of validation number  130 , such that validation number  130  is no longer available on second device  106 . In response to receiving such instructions, second device  102  deletes validation number  130 , in step  232 . In step  234  entity system  110  transmits transaction result message  142  to first device  102 . Transaction result message  142  may include any suitable information. As an example, in certain embodiments in which institution system  112  transmitted an authentication result message  148  to entity system  110  instructing entity system  110  to deny the requested transaction, transaction result message  142  may indicate that entity system  110  has denied the transaction. As another example, in certain embodiments in which institution system  112  transmitted an authentication result message  148  to entity system  110  instructing entity system  110  to approve the transaction request  144 , entity system  110  may have used account number  136  to process the transaction. In such embodiments, transaction result message  142  may indicate that entity system has processed the transaction, and may include information such as a confirmation number. In step  236 , in response to receiving transaction result message  142 , first device  102  displays the contents of transaction result message  142  on display  114 . For example, first device  102  may display a message to user  104  on display  114  indicating that entity system  110  has approved or declined the transaction. 
     Modifications, additions, or omissions may be made to method  200  depicted in  FIGS. 2A and 2B . Method  200  may include more, fewer, or other steps. For example, steps may be performed in parallel or in any suitable order. While discussed as first device  102 , second device  106 , institution system  112 , and entity system  110  (or components thereof) performing certain steps, any suitable components of system  100 , may perform one or more steps of the method. 
     Although the present disclosure includes several embodiments, a myriad of changes, variations, alterations, transformations, and modifications may be suggested to one skilled in the art, and it is intended that the present disclosure encompass such changes, variations, alterations, transformations, and modifications as falling within the scope of the appended claims.