TECHNIQUES FOR VERIFYING A SENDER IDENTITY USING A USER-GENERATED IDENTIFIER

Methods, systems, and devices to support techniques for verifying a sender identity using a user-generated identifier are described. A user having one or more accounts with an organization may generate a unique identifier to associate with one or more accounts, and the organization may include the unique identifier in subsequent electronic communications to the user. For example, the user may generate and transmit the unique identifier to the organization using a device, and the organization may associate the unique identifier with the one or more accounts of the user. The organization may establish a communication session with the user, such as by generating a message which includes information associated with the one or more accounts. The organization may embed the unique identifier into the message and transmit the message to the user. The message including the unique identifier may provide verification that the sender is the organization.

FIELD OF TECHNOLOGY

The present disclosure relates generally to computer systems and software, and more specifically to techniques for verifying a sender identity using a user-generated identifier.

BACKGROUND

Companies and organizations, such as financial institutions, may communicate with users (e.g., customers), for example, to convey account information to users or alert users of potential problems associated with user accounts. Such communications may be sent using various electronic or digital messaging techniques such as via email, push notifications, text messages, or the like. Increasingly, malicious third parties may attempt to impersonate the identity of a legitimate financial institution by sending electronic communications that appear to be from the financial institution. These malicious third parties may use such techniques in an attempt to obtain sensitive financial information from the user, such as account names, account passwords, or other private and personal information. In many cases, particularly for messages received using mobile devices, real time verification that the electronic communication is from the legitimate financial institution may be difficult. Malicious third parties may exploit this condition by sending spoofed messages (e.g., message imitating the legitimate financial institution) to unsuspecting users, which may lead to various forms of fraud to consumers.

SUMMARY

The described techniques relate to improved methods, systems, devices, and apparatuses that support techniques for verifying a sender identity using a user-generated identifier. Generally, the described techniques provide for identifying a user-generated unique identifier and including the user-generated unique identifier in electronic communications from an organization to the user. For example, as part of one or more actions taken to set up a new account, modify an existing account, or both, a user may be given the ability to generate and transmit the unique identifier to an organization using a device (e.g., a smartphone, a tablet, a laptop computer, or the like), and the organization may then associate the user's unique identifier with one or more accounts of the user. Subsequently, the organization may establish a communication session with the user, such as by generating a message (e.g., a text message, a push notification) for communicating some information associated with the one or more accounts. The organization may embed the user's unique identifier into the message, and transmit the message to the user. After receiving the message, the user may verify (e.g., in real time) that the message includes the user-generated unique identifier, which may indicate that the received message is from the organization (e.g., and not from a malicious third party). As such, the unique identifier may serve as a secure indication that is created by the user and only known by the user and the organization and therefore non-reproducible or scalable by unauthorized third parties, thereby enhancing the security of electronic communications and enabling efficient verification of the sender of messages to include those that include private and sensitive information (e.g., personal information, financial information, request for user action).

A method is described. The method may include receiving, at a system managed by an organization, a unique identifier generated by a user and provided via a device associated with the user, the user having one or more accounts associated with the organization, establishing a communication session between the organization and the user, generating, by the system and as part of the communication session, a message associated with the one or more accounts provided by the organization, embedding the unique identifier into the message, and transmitting, as part of the communication session, the message to the device associated with the user.

An apparatus is described. The apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to receive, at a system managed by an organization, a unique identifier generated by a user and provided via a device associated with the user, the user having one or more accounts associated with the organization, establish a communication session between the organization and the user, generate, by the system and as part of the communication session, a message associated with the one or more accounts provided by the organization, embed the unique identifier into the message, and transmit, as part of the communication session, the message to the device associated with the user.

Another apparatus is described. The apparatus may include means for receiving, at a system managed by an organization, a unique identifier generated by a user and provided via a device associated with the user, the user having one or more accounts associated with the organization, means for establishing a communication session between the organization and the user, means for generating, by the system and as part of the communication session, a message associated with the one or more accounts provided by the organization, means for embedding the unique identifier into the message, and means for transmitting, as part of the communication session, the message to the device associated with the user.

A non-transitory computer-readable medium storing code is described. The code may include instructions executable by a processor to receive, at a system managed by an organization, a unique identifier generated by a user and provided via a device associated with the user, the user having one or more accounts associated with the organization, establish a communication session between the organization and the user, generate, by the system and as part of the communication session, a message associated with the one or more accounts provided by the organization, embed the unique identifier into the message, and transmit, as part of the communication session, the message to the device associated with the user.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the device associated with the user, a prompt for the unique identifier and receiving, from the device and in response to the prompt, an indication of a first identifier generated by the user, wherein the unique identifier comprises the first identifier.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that the first identifier may be unique among a plurality of identifiers stored in a database of the system, wherein the unique identifier comprises the first identifier based at least in part on the first identifier being unique.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the device associated with the user, a first prompt for the unique identifier, receiving, from the device and in response to the first prompt, an indication of a first identifier generated by the user, transmitting, to the device, an indication that the first identifier may be not unique based at least in part on a comparison of the first identifier with a plurality of identifiers stored in a database of the system, wherein the indication that the first identifier may be not unique comprises a second prompt for the unique identifier, and receiving, from the device and in response to the second prompt, a second identifier generated by the user, the second identifier being different from the first identifier, wherein the unique identifier embedded into the message comprises the second identifier based at least in part on the second identifier being unique among the plurality of identifiers stored in a database of the system.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for embedding an additional identifier associated with the organization into the unique identifier, wherein the message comprises the unique identifier with the embedded additional identifier.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, at the system, a second unique identifier generated by the user and provided via the device, the second unique identifier being different than the unique identifier and associating the second unique identifier with at least one account of the one or more accounts.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for generating, by the system and as part of the communication session, one or more additional messages associated with the one or more accounts after transmitting the message and transmitting the one or more additional messages to the device associated with the user, wherein the one or more additional messages exclude the unique identifier.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for providing, as part of an outbound call associated with the communication session, an indication that the user may have requested that the message comprising the unique identifier be provided by a representative of the organization, wherein the communication session comprises communications between the representative and the user, and wherein the message may be transmitted in response to the provided indication.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for determining that a threshold duration after identifying the unique identifier may have been satisfied and transmitting, to the device associated with the user, a request message comprising an indication to modify the unique identifier.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for configuring the threshold duration of based at least in part on an input from the user.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the message comprises a multimedia messaging service (MMS) message, a short message/messaging service (SMS) message, push notification, or any combination thereof.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the unique identifier comprises a phrase, a code, a pictogram, an image, an audio message recorded by the user, or any combination thereof.

A method is described. The method may include generating, by a system managed by an organization, a unique identifier associated with a user, the user having one or more accounts associated with the organization, wherein the unique identifier is automatically generated in response to a request received at the system from a device associated with the user, establishing a communication session between the organization and the user, generating, by the system and as part of the communication session, a message associated with the one or more accounts provided by the organization, embedding the unique identifier into the message, and transmitting, as part of the communication session, the message to the device associated with the user.

An apparatus is described. The apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to generate, by a system managed by an organization, a unique identifier associated with a user, the user having one or more accounts associated with the organization, wherein the unique identifier is automatically generated in response to a request received at the system from a device associated with the user, establish a communication session between the organization and the user, generate, by the system and as part of the communication session, a message associated with the one or more accounts provided by the organization, embed the unique identifier into the message, and transmit, as part of the communication session, the message to the device associated with the user.

Another apparatus is described. The apparatus may include means for generating, by a system managed by an organization, a unique identifier associated with a user, the user having one or more accounts associated with the organization, wherein the unique identifier is automatically generated in response to a request received at the system from a device associated with the user, means for establishing a communication session between the organization and the user, means for generating, by the system and as part of the communication session, a message associated with the one or more accounts provided by the organization, means for embedding the unique identifier into the message, and means for transmitting, as part of the communication session, the message to the device associated with the user.

A non-transitory computer-readable medium storing code is described. The code may include instructions executable by a processor to generate, by a system managed by an organization, a unique identifier associated with a user, the user having one or more accounts associated with the organization, wherein the unique identifier is automatically generated in response to a request received at the system from a device associated with the user, establish a communication session between the organization and the user, generate, by the system and as part of the communication session, a message associated with the one or more accounts provided by the organization, embed the unique identifier into the message, and transmit, as part of the communication session, the message to the device associated with the user.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, generating the unique identifier may include operations, features, means, or instructions for randomly generating the unique identifier such that the unique identifier may be different from a plurality of other identifiers stored in a database of the system.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, generating the unique identifier may include operations, features, means, or instructions for generating a plurality of unique identifiers that may be each different from a plurality of other identifiers stored in a database of the system, the method further comprising, transmitting, to the device, a first message including an indication of the plurality of unique identifiers, and receiving, from the device, a second message indicating a selection of a first unique identifier from the plurality of unique identifiers, wherein the unique identifier embedded into the message comprises the first unique identifier based at least in part on receiving the second message indicating the selection.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the device, a first message including an indication of the unique identifier generated by the system and receiving, from the device, a second message indicating that the unique identifier may be accepted by the user, wherein the unique identifier may be embedded into the message based at least in part on receiving the second message indicating that the unique identifier may be accepted by the user.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, to the device, a first message including an indication of a first unique identifier generated by the system, the first unique identifier being unique among a plurality of other identifiers stored in a database of the system, receiving, from the device, a second message indicating that the unique identifier may be not accepted by the user, transmitting, to the device and in response to the second message, a third message including an indication of a second unique identifier generated by the system, the second unique identifier being different from the first unique identifier and being unique among the plurality of other identifiers stored in the database of the system, and receiving, from the device, a fourth message indicating that the second unique identifier may be accepted by the user, wherein the unique identifier embedded into the message comprises the second unique identifier based at least in part on the fourth message indicating that the second unique identifier may be accepted by the user.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving the request from the device based at least in part on one or more failed attempts by the user to generate the unique identifier.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving the request from the device based at least in part on establishing at least one of the one or more accounts by the organization.

DETAILED DESCRIPTION

An organization, such as a financial institution (e.g., a bank, a lender), may provide one or more accounts to a user and may transmit communications to the user, where the communications include some information associated with the accounts. For example, the organization may send alerts about account changes, prompts to update account information, alerts about possible fraudulent activity, or the like, to a device of the user, such as a smartphone or tablet. In some cases, the organization may transmit such communications using electronic communications, such as text messages or push notifications, among other examples, which may improve convenience, enable efficient and timely notifications, and increase user engagement.

Some electronic communications, however, may provide relatively fewer authentication opportunities compared with other types communications. For example, text messages may be sent from an unrecognized number and it may be difficult to verify whether a text message is from a trusted source based solely on the sender's number. Similarly, while received emails may include a relatively more detailed “from” line to review (e.g., for verifying whether the sending is legitimate or potentially fraudulent), text messages may lack such identifiers. Additionally, some electronic communications may include an identifier associated with a legitimate organization, but such identifiers may be publicly available, and therefore easily duplicated by a malicious third party, for example, when attempting to obtain private information from the user. As a result, a user may not be able to tell whether a message was sent by a legitimate source based solely on an identifier of the organization (e.g., a known and widely-available logo) included with a received message. Accordingly, the user may be at relatively greater risk of falling prey to a malicious third party impersonating the organization (e.g., using a phishing attempt (e.g., an attempt to get a user to depart with something of value, such as money or personal information, through deceptive communications)). Thus, techniques to improve the security of electronic communications are desired to enable enhanced authentication of a source (e.g., the identity of the sender) for various electronic communications.

As described herein, a user having one or more accounts with an organization may generate a unique identifier (e.g., a unique phrase, a unique image, a unique code, among other examples) for association with one or more accounts, and the organization may include the unique identifier in subsequent electronic communications to the user. For example, as part of setting up a new account, modifying an existing account, or both, the user may generate and transmit the unique identifier to the organization using a device (e.g., a smartphone, a tablet, a laptop, or the like), and the organization may associate the unique identifier with the one or more accounts of the user. Subsequently, the organization may establish a communication session with the user, such as by generating a message (e.g., text message, a push notification, an email) that includes information associated with the one or more accounts. The organization may embed the unique identifier into the message and transmit the message to the user (e.g., to the device of the user). After receiving the message, the user may verify that the message includes the unique identifier, the presence of which may enable verification that the source of the message is the organization, rather than a malicious third party. In some aspects, the unique identifier may be generated by the user and transmitted to the organization. In other examples, the unique identifier may be automatically and randomly generated by the organization, for example, based on a request received from the user. In such cases, the automatically and randomly-generated identifier may be transmitted to the user for approval, and once approved, the identifier may be used for subsequent communications between the organization and the user.

Aspects of the disclosure are initially described in the context of systems and process flows with reference toFIGS.1through6. Aspects of the disclosure are further illustrated by and described with reference to systems and flowcharts that relate to techniques for verifying a sender identity using a user-generated identifier with reference toFIGS.7,8, and9.

This description provides examples, and is not intended to limit the scope, applicability or configuration of the principles described herein. Rather, the ensuing description will provide those skilled in the art with an enabling description for implementing various aspects of the principles described herein. As can be understood by one skilled in the art, various changes may be made in the function and arrangement of elements without departing from the application.

FIG.1illustrates an example of a system100that supports techniques for verifying a sender identity using a user-generated identifier in accordance with one or more aspects of the present disclosure. The system100may include one or more users105which may interact with one or more organizations110(e.g., entities, companies, banks, corporations, credit unions, lenders) using one or more devices115over a network, such as the Internet. Accordingly, a user105described herein may be associated with one or more devices115(e.g., a desktop computer, a laptop, a smartphone, a tablet, other computing system, or any combination thereof). Similarly, the organization110described herein may be associated with or may utilize one or more devices (e.g., computers, servers, databases, platforms, or the like), such as a server120, a database125, a communication center130which includes one or more representatives135, or any combination thereof.

In some examples, the organization110and the one or more devices115may communicate using various messages and communications protocols. For instance, the organization110and the one or more devices115may communicate via a wireless communications system supporting various types of communication content such as messaging (e.g., text messaging), voice, video, packet data, broadcast, and so on. Such wireless communications systems may be capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power) over one or more radio frequency spectrum bands. Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems, which may be referred to as New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). Additionally, or alternatively, the organization110and the one or more devices115may communicate using one or more wired communications system supporting the various types of communication content (e.g., messaging, voice, video, packet data, and so forth).

In some cases, messaging between the organization110and the one or more devices115may be supported by a core network providing user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network, for example, may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity that manages access and mobility and at least one user plane entity that routes packets or interconnects to external networks. In some aspects, user IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services for one or more network operators. The IP services may include access to the Internet, Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service.

The server120may include a framework in which to run the one or more applications associated with the one or more devices115. For example, the server120may be an application server and may implement system software on which the applications may run. More generally, the server120may provide a software framework for creating and running applications. As such, the server120may support administrative functions for creating, modifying, or otherwise managing various applications. For example, an administrative user or software developer may create and customize an application using various software or components of the server120(e.g., an application builder, an application programming interface (API), or other application tools). The server120may support building applications or pages that may be rendered on a number of different user interface types at the devices115(e.g., including different types and versions of devices115). In some cases, the server120may perform data processing, and the server120may be an example of a cloud device or may be located at a data center. The server120may support serving dynamic content and transferring applications or application data from one device115to another. In some cases, the server120may further provide for hosting business logic applications and processes using various protocols.

In some cases, the server120may be part of a client-server system, a mobile device system, an electronic banking system, a mobile network system, or the like, which may support techniques to enable a user105to verify the identity of the organization110using a user-generate unique identifier145. For example, as part of a communication session140between the organization110and the user105, the organization110may include the user-generated unique identifier145within one or more messages150of the communication session140.

The communication session140may include the signaling of the one or more messages150between the organization110and the one or more devices115, where such messages may include text messages, push notifications, email, or the like. Text messages may refer to short messaging service (SMS) or multimedia messaging service (MMS), which may respectively relate to communications protocols for sending and receiving messages (e.g., via cellular networks). For example, SMS may sometimes be associated with a threshold quantity of characters (e.g., associated with a threshold quantity of bits) included in a message and may enable the inclusion of a link (e.g., a uniform resource locator (URL)) within a message. MMS may not have such character thresholds (or may have relatively greater character limits and/or threshold quantities of bits) and may further enable the inclusion of media files (e.g., pictures, audio files, video files, gifs, or the like) within a message. Push notifications may refer to relatively short messages sent to a user's one or more devices (e.g., the one or more devices115) from a backend server to a user interface, for example, via an application (e.g., a mobile application, a desktop application). Push notification may appear on the interface of the user's one or more devices115even when an associated application is not in use. In other examples, the messages of the communication session140may include an email or other type of electronic or digital message not explicitly described herein.

In some examples, the communication session140may additionally or alternatively include one or more voice communications between the organization110and the one or more devices115. Such voice communications may include, for example, recorded voice messages, IP telephony (e.g., voice over IP (VOIP) communications) for the delivery of voice communications and multimedia sessions over an IP network (e.g., the Internet), or both. The communication session140may include an outbound call from a representative of the organization110to the user105(e.g., to the one or more devices115) or an inbound call from the one or more devices115to a representative of the organization110.

As described herein, a user105having one or more accounts with the organization110may generate a unique identifier145and provide, using the one or more devices115, the unique identifier145to the organization110. For example, the user105may use an application associated with the organization110, such as a banking application or online portal, among other examples, to create and input a unique identifier145to the application via the one or more devices115. The application may transmit the unique identifier to the organization110, and the organization110may store the unique identifier145, for example in a database125. The organization110may embed the unique identifier145in future communications between the organization110and the user105(e.g., the one or more devices115of the user105). In some cases, the organization110may, as part of communications between the organization110and the user105, transmit the unique identifier145to a different device115than the device115used to provide (e.g., generate and transmit) the unique identifier145. For example, the user105may use a first device115, such as a laptop, to provide the unique identifier145to the organization110, and the organization110may transmit communications, including the unique identifier145, to a second device115, such as a mobile phone (e.g., smartphone) of the user105. That is, the user105may receive one or more messages150including the unique identifier145from the organization110via any device115(e.g., one or more devices115that are registered with the organization110).

The unique identifier145may include a phrase, a passcode, a logo, pictogram (e.g., an emoji), an image (e.g., a portable network graphic (PNG) image, a joint photographic experts group (JPEG) image, or the like), letters, numerals, special characters, an audio file (e.g., an audio message recorded by the user105, such as the user's own voice or another audio recording), among other examples, or any combination thereof. In some cases, the user105may input the unique identifier145to the one or more devices115as part of setting up the one or more accounts of the user105. Additionally, or alternatively, the user105may generate or update (or both) a unique identifier145as part of improving security of an account. For instance, the user105may periodically update the unique identifier145. In some aspects, a type of the message that includes the unique identifier145may be based on the unique identifier. For example, when the unique identifier145is an image, the message may be an example of an MMS text message, and when the unique identifier145is a text string (e.g., a phrase, a code), the message may be an example of an SMS text message or push notification. In some aspects, the unique identifier145may be referred to as a “know your sender” identifier or some other terminology.

In some cases, the user105may generate multiple unique identifiers145. For example, the user105may generate a unique identifier145for each of two or more accounts associated with the user105. Additionally, the user105may generate multiple types of unique identifiers145(e.g., passcodes, phrases, images, audio files), with each type of unique identifier145corresponding to or configured for a type of communication, such as text communication, voice communication, relatively high sensitivity communication, relatively low sensitivity communication, or the like.

In some examples, the organization110may verify that the user-generated unique identifier145is unique (e.g., unique among identifiers of other users105associated with the organization110, such as identifiers stored in the database125), and the organization110may store the unique identifier145in the database125. Such verification may be based on a comparison of the user-generated unique identifier145with the other identifiers stored in the database125. Based on the comparison, the organization110may indicate to the user105(e.g., via the one or more devices115) that the user-generated identifier145is unique. Alternatively, in the case where the user-generated identifier145is not unique based on the comparison, the organization110may request that the user105(e.g., via the one or more devices115) generate an additional, different user-generated identifier145. Such a process may occur until the user-generated identifier145is determined to be unique and associated with one or more accounts of the user105by the organization110. In some aspects, the user-generated identifier145may be used by the organization110for communications associated with a particular account (e.g., a savings account, a checking account, a credit card account), a particular line of business (e.g., deposit accounts, mortgage accounts, investment accounts), or for all communications (e.g., at a total relationship level), or any combination thereof.

Subsequently, the organization110may initiate the communication session140between the organization110and the user105. For example, the organization110may generate and transmit a message150, such as a text message (e.g., an SMS message, an MMS message, a push notification, or the like) to the one or more devices115of the user105. To authenticate the message150to the user105, the organization110may embed (e.g., automatically embed) the user-generated unique identifier145into the message150prior to transmitting the message150to the one or more devices115. After receiving the message150, the one or more devices115may display the message150, along with the embedded unique identifier145, to the user105via an interface of the one or more devices115, which may allow the user105to verify the identity of the source of the message150.

In some examples, the communication session140may be an example of or may include an audio message to the user105from organization110. For example, the organization110may communicate sensitive information, such as account information (e.g., login codes), account warnings or notifications (e.g., transaction validation warnings), or the like, using a pre-recorded voice message (e.g., to ask the user105to call back, to provide the user105with a reminder or other information) to the one or more devices115of the user105. In such cases, the pre-recorded voice message may include (e.g., automatically include) the unique identifier145. For example, the user105may generate a unique identifier145that includes an audio message recorded by the user105, and the pre-recorded voice message may play the audio message (e.g., at the beginning of the call, at the end of the call), which may allow the user105to verify the identity or source of the pre-recorded voice message (e.g., to determine that the pre-recorded voice message is authentic). In some aspects, respective unique identifiers145may be generated for different types of communications. For example, a unique identifier145associated with pre-recorded voice messages may be different than another unique identifier145associated with other messages, such as text messages, push notifications, or email.

Additionally, or alternatively, the communication session140may be an example of a live telephone call between the organization110and the user105. For example, a representative135of the organization110(e.g., a customer service representative) may initiate the telephone call as part of, for example, an outbound call associated with an account of the user105, a call-back associated with a service request by the customer, or the like. In such cases, the representative135may concurrently, and as part of the communication session140, send the unique identifier145to the user's device115, which may allow the user105to verify that the caller is from the organization110.

For example, as part of the telephone call between the representative135and the user105, the user105may request verification of the identity of the representative135. In such cases, the representative135may cause the system100(e.g., using the server120or other device included in the communication center130) generate a message (e.g., a text message), which includes the unique identifier145, and may cause the system100to transmit the message to the one or more devices115. Additionally, or alternatively, the representative135may cause the system100to transmit the message which includes the unique identifier145to the one or more devices115without a request from the user105during the telephone call. For example, as part of setting up the unique identifier145, the user105may request to automatically receive the unique identifier145for future telephone calls from the organization110. Accordingly, the representative135may cause the system100to generate and transmit a message which includes the unique identifier145as part of initiating the telephone call and based on the request from the user105.

Including (e.g., prominently displaying) the user-generated unique identifier145in a message150transmitted to the one or more devices115from the organization110may enable enhanced security for the one or more messages150received from the organization110. As an example, the user105may verify the identity of the sender of the one or more messages150based on the presence of the user-generated unique identifier. Accordingly, the user105may better detect fraudulent messages, such as phishing attempts or other cyber fraud attempts, which may improve security and reliability of sensitive information associated with the user105. Moreover, the user105may perform further actions after receiving the secure messages with increased confidence that the sender is verified, which may enable the user105to take timely action (e.g., related to one or more accounts) in accordance with the content of a received message150.

FIG.2illustrates an example of a process flow200that supports techniques for verifying a sender identity using a user-generated identifier in accordance with one or more aspects of the present disclosure. The process flow200or aspects thereof may be implemented by a device115-aassociated with a user (e.g., a user105) and by a server120-aassociated with an organization (e.g., an organization110), which may each be examples of the corresponding entities as described with reference toFIG.1. For example, the device115-amay be an example of the one or more devices115described with reference toFIG.1. Additionally, the server120-amay be associated with a system managed by an organization and may further support the operation of one or more applications associated with the organization, and the system may enable the communication of one or more messages between the organization and the user. In the following description of the process flow200, the operations may be performed in a different order than the order shown. For example, specific operations may be left out of the process flow200, or other operations may be added to process flow200.

The process flow200may illustrate methods to generate, manage, and communicate a user-generated unique identifier, such as the unique identifier145as described with reference toFIG.1. In some cases, the server120-amay be in communication with the device115-ausing one or more communication channels, such as via an online portal, a website or application (e.g., a client-server application), a communication session in which the server120-acommunicates messages (e.g., text messages, telephone calls) with the device115-a, or both.

By way of example, as part of setting up an account with the organization at205(e.g., a checking account, savings account, mortgage account, or the like), the server120-amay, at210, provide the device115-awith one or more options to generate a unique identifier for the account. Additionally, or alternatively, the user may, using the device115-aat215, access a profile of one or more existing accounts (e.g., login to an online portal, which may display aspects of the profile on the device115-a). The user may, at220, access and modify one or more account settings associated with the profile, and may determine to generate a unique identifier for an account of the one or more accounts, or to update one or more existing unique identifiers associated with the one or more accounts.

In some examples, the profile may support (e.g., may allow the user to configure one or more parameters using the device115-ato cause the server120-ato perform operations which allow) associating a same unique identifier to multiple accounts of the one or more accounts. Additionally, or alternatively, the profile may support associating a different unique identifier for each of the one or more accounts. Further, the profile may support associating multiple unique identifiers with a same account. For example, the profile may support associating a first unique identifier associated with a first security level with an account, and may support associating a second unique identifier associated with a second, different security level with the account. In some cases, the profile may support configuring the first security level, the second security, or both, for example, by allowing the user to associate particular types of communications with a particular security level. For instance, communications associated with possible fraud may be configured with a relatively highest security level, whereas communications confirming a deposit to an account may be configured with a relatively lower security level.

At225, the device115-amay determine, based on an input from the user, whether to generate a unique identifier, or whether to request a unique identifier from the server120-a. If the device115-adetermines to generate the unique identifier, the user may, at230, input an identifier (e.g., may upload an image, may input a passcode, may input a code, may input a phrase, may upload an audio recording) to the device115-a(e.g., via an application), and the device115-amay transmit the identifier to the server120-a. In some examples, such as if the user has determined to update an existing identifier, the user may input an identifier different than the existing identifier.

In some cases, the server120-amay, at235, compare the received identifier with a database125-aof identifiers (e.g., identifiers associated with other users of the organization) to determine whether the identifier is unique. If the server120-adetermines that the identifier is unique, the server120-amay, at240, associate the unique identifier with one or more accounts of the user (e.g., in accordance with options provided at210, in accordance with the settings accessed at220). Alternatively, if the server120-adetermines that the identifier is not unique, the server120-amay transmit an indication to the device115-a, and the user may provide one or more additional identifiers (e.g., until the server120-adetermines that a provided identifier is unique).

In some examples, at225, the user may determine to request, using the device115-a, a unique identifier from the server120-a. In such cases, the server120-amay, at245, automatically generate the unique identifier (e.g., unique among the identifiers of the database125). For example, the server120-amay randomly generate the unique identifier, and may ensure that the generated unique identifier is unique among identifiers of the database125(e.g., by randomly generating and checking the generated identifier against the database125, or by other means). In some cases, the device115-amay request the unique identifier from the server120-ain response to one or more failed attempts by the user to generate the unique identifier. That is, if the user is unable or unwilling to generate their own unique identifier using the device115-aafter any number of attempts (e.g., one or more attempts at a user-generated identifier were not complex enough to be unique), the user may request that the system automatically generate (e.g., randomly generate) the unique identifier. At245, the system may provide the generated identifier to the user (e.g., for approval). In cases where they server120-aautomatically and randomly generates the unique identifier, the system may use various techniques for generating the identifier, such as randomly generating one or more alphanumeric strings, randomly generating one or more images, randomly generating one or more phrases, or any combination thereof, among other examples.

In some examples, the server120-amay determine (e.g., via input to the device115-a) whether the user accepts the generated unique identifier. If the user accepts the unique identifier, the server120-amay, at240, associate the unique identifier with the one or more accounts. In some aspects, the unique identifier may be associated with a single account, or may be associated with one or more accounts associated with a particular business line (e.g., deposit accounts), or may be associated with a variety of accounts provided to the user by the organization (e.g., across various lines of business, particular accounts in respective lines of business), among other examples. Alternatively, if the user does not accept the unique identifier, the server120-amay generate one or more additional unique identifiers (e.g., until the user accepts a generated unique identifier) and associate the accepted unique identifier with the one or more accounts. The user, via the device115-a, may request any number of unique identifiers be generated until a unique identifier is selected and indicated to the server120-a.

In some examples, the device115-amay modify an identifier generated by the server120-a, such as by adding additional characters, images, or both (e.g., provided by user input to the device115-a) to the generated identifier. Additionally, or alternatively, the server120-amay generate multiple unique identifiers, and may transmit the multiple unique identifiers to the device115-a. The user may select one of the multiple unique identifiers (e.g., via input to the device115-a), and the device115-amay transmit the selection to the server120-a.

To further enhance the security provided by the unique identifier, the server120-amay embed an image or code, such as image associated with the organization (e.g., a logo, an emblem, or the like), a phrase or code associated with the organization, or both, into the unique identifier. For example, if the unique identifier includes an image, the server120-amay overlay an image associated with the organization over the image of the unique identifier. Additionally, or alternatively, if the unique identifier includes an alphanumeric passcode (e.g., a text string), the server120-amay convert the passcode into an image, and may overlay the image associated with the organization over the converted image. Embedding the image or code in the unique identifier may allow for enhanced identification (e.g., by the user) of the unique identifier, reduce the likelihood of a malevolent third party from impersonating the organization (e.g., reduce the likelihood of phishing, spear-phishing, smishing, vishing, or other similar actions), or both.

In some examples, the server120-amay update a security score associated with the user in response to setting up the one or more unique identifiers. For example, the server120-amay award a badge or certification to the user, which may indicate that the user has enabled unique identifier verification. Such rewards may incentivize and increase the use of the one or more unique identifiers across various accounts of the user, thereby enhancing security for messages sent by the organization.

Subsequent to associating the unique identifier with the one or more accounts, the server120-amay embed the unique identifier within a message150-ato the user (e.g., to the device115-a) associated with the one or more accounts. For example, the server120-amay generate a message150-a, such as a text message, email or any other digital or electronic communication, to inform the user of a change of one or more account settings associated with the one or more accounts. The server120-amay embed the unique identifier, along with one or more identifier associated with the organization (e.g., a logo, phrase, or the like) into the message150-a, and may transmit the message150-ato the device115-a.

Upon the device115-areceiving the message150-a, the user may, at255, determine whether the message150-ais authentic (e.g., whether the source of the message150-ais the organization, or whether the message150-ais fraudulent). If the message150-aincludes the unique identifier, the user may, at260, verify that the organization sent the message150-a. Alternatively, if the message150-adoes not include the unique identifier, the user may, at275, determine that the message150-amay be fraudulent. Accordingly, the user may perform one or more actions, such as ignoring the message150-a, deleting the message150-a, reporting the message150-a(e.g., to the organization), or any combination thereof.

In some examples, the device115-amay configure one or more parameters associated with providing a reminder to the user to update the unique identifier. For example, at280, the device115-amay configure or enable the configuration of a duration of time between reminders (e.g., configure whether to receive reminders weekly, monthly, quarterly, annually). Accordingly, after determining that the duration has elapsed at285, the server120-amay, at290, generate a message150-awhich includes an indication that the duration has elapsed, and may transmit the message150-ato the device115-a(e.g., as a reminder to the user). In some examples, the server120-amay embed the unique identifier into the reminder message150-a. In some cases, the user may reset or update the unique identifier used for messaging with some periodicity to further enhance the security benefits of using such an identifier for messaging.

To enhance security of the unique identifier, the server120-amay not display the unique identifier within the profile. Instead, the profile may support a request by the device115-ato transmit a message150-awhich includes one or more unique identifiers associated with the one or more accounts. For example, the profile may include a forgotten identifier feature, which may allow the user, using the device115-a, to request a reminder of the one or more unique identifiers. In response to the request, the server120-amay embed the one or more unique identifiers into a message150-a, and may transmit the message150-ato the device115-ato provide the user with a reminder of a previously-generated unique identifier.

FIG.3illustrates an example of a device300that supports techniques for verifying a sender identity using a user-generated identifier in accordance with one or more aspects of the present disclosure. The device300may be an example of a device115or a device115-adescribed with reference toFIGS.1and2. For example, the device300may be a smartphone, a tablet, a desktop computer, or other computing system. In some examples, the device300may provide an interface by which a user (e.g., a user105) may interact with the device300to manage one or more unique identifiers associated with one or more accounts of the user.

The device300may illustrate one or more messages150received from an organization (e.g., from a server120managed by the organization110, from a system managed by the organization), which may include one or more unique identifiers145(e.g., a unique identifier145-a). In some cases, the device300may be configured to receive messages, such as text messages (e.g., SMS messages, MMS messages), telephone calls, or both from the organization as part of a communication session between the organization and the user. The device300may be further configured to display the messages150, along with the unique identifiers145, to the user.

For example, the message150-bmay be an example of a message transmitted to the device300, which may include transaction information associated with an account of the user (e.g., information indicating that a transaction was successful, information asking the user if a charge is authorized, or the like). Prior to transmitting the message150-b, the organization may embed the unique identifier145-ainto the message150-b. After receiving the message150-b, the device300may display the message150-b, along with the unique identifier145-a, to the user. Accordingly, the user may determine that the unique identifier145-ais correct (e.g., verify that the unique identifier145-ais the same as the user-generated identifier associated with the account), and accordingly verify the authenticity of the communication session (e.g., verify the source of the message150-b). In some aspects, the inclusion of the unique identifier145-ain the first message (e.g., message150-b) of a series of messages may be based on whether the first message requests some information from the user (e.g., requires interaction by the user), whereas following messages in the series may omit the unique identifier145-a.

In some examples, the organization may transmit multiple messages150as part of a same communication session. For example, the organization may transmit another message150-c, which may include additional information associated with the communication session. Because the user may verify authenticity of the communication session using the unique identifier145-awithin the message150-b, the organization may refrain from embedding (e.g., not embed) the unique identifier145-ain subsequent messages of the same communication session, such as the message150-c.

A unique identifier145-amay include a phrase (e.g., a string of characters, numerals, or other symbol), a passcode, a pictogram (e.g., an emoji), an image, an audio message recorded by the user, or any combination thereof. By way of example, the unique identifier145-aillustrated inFIG.3may include a pictogram305. Additionally, or alternatively, the unique identifier145-amay include a code310(e.g., a passcode, a string of numerals). In some examples, the unique identifier145-amay optionally include an additional identifier315associated with the organization, such as a logo of the organization. The additional identifier315may be embedded in the unique identifier145-a.

In some cases, the user may generate the unique identifier145-aas part of setting up the account, such as by inputting the unique identifier to the device300, which may provide the input unique identifier145-ato the organization (e.g., via an application managed by the organization). Additionally, or alternatively, the user may generate the unique identifier145-aas part of updating the account (e.g., as part of associating a new unique identifier145with the account, updating a unique identifier145-aassociated with the account, or both). In some examples, the organization may modify the user-generated unique identifier145-ato include the additional identifier315.

FIG.4illustrates an example of a device400that supports techniques for verifying a sender identity using a user-generated identifier in accordance with one or more aspects of the present disclosure. The device400may be an example of one or more devices115described with reference toFIG.1or a device115-adescribed with reference toFIG.2, or a device300described with reference toFIG.3. For example, the device400may be a smartphone, a tablet, or other computing system. In some examples, the device400may provide an interface by which a user (e.g., a user105) may interact with the device400to manage one or more unique identifiers associated with one or more accounts of the user.

In some examples, the device400may run one or more instances of an application405associated with an organization (e.g., provided by a system managed by the organization), such as a financial institution (e.g., a bank, a lender). The application may provide the user with various features and services related to the one or more accounts (e.g., checking accounts, savings accounts, investment accounts, retirement accounts) that are established and held with the organization. For example, the user may be provided with (e.g., the system may transmit to the device400) one or more widgets, icons, modules, menus, prompts, text fields, or the like, to perform various actions and functions within the application405.

The application405may enable the user to manage one or more unique identifiers as part of creating a new account, modifying an existing account, or both. For example, as part of creating an account, modifying the account, or both, the system managed by the organization may transmit an indication to the application405to display a prompt to the user to generate a unique identifier to associate with the account. In some examples, the application405may provide a menu410, which may allow the user to input a selected type for the unique identifier, such as a phrase, a passcode, a pictogram, an image, an audio message recorded by the user, or any combination thereof.

In response to user input to the menu410, the application405may display one or more additional prompts to the user. For example, if the user selected a text-based type for the unique identifier (e.g., a phrase, a passcode, a pictogram, or any string of characters), the application405may display a text field415. The user may generate an identifier and input the identifier to the text field415. Additionally, or alternatively, if the user selected an image-based type for the unique identifier, the application405may display an image field420, which may allow the user to input (e.g., upload) an image file, such as a PNG file, a JPEG file, or the like, as the identifier.

Upon receiving the input identifier, the application405may, via the device400, transmit the identifier to the system. Accordingly, the system may verify whether the identifier is unique (e.g., unique among a database of identifiers associated with other users). If the system verifies that the identifier is unique, the system may associate the identifier with the account, and may embed the unique identifier in subsequent messages associated with the account to the user. Alternatively, if the system does not verify that the identifier is unique (e.g., if the system identifies a same or similar identifier within the database), the system may transmit a message to the device400indicating that the identifier is not unique. Accordingly, the application405may display an additional prompt to the user to generate a second identifier, which the application405may transmit to the system. The system may determine whether the second identifier is unique, and so on, until a unique identifier is obtained.

FIG.5illustrates an example of a process flow500that supports techniques for verifying a sender identity using a user-generated identifier in accordance with one or more aspects of the present disclosure. The process flow500or aspects thereof may be implemented by a device115-bassociated with a user (e.g., a user105) and by a server120-bassociated with an organization (e.g., an organization110), which may each be examples of the corresponding entities as described with reference toFIGS.1through4. For example, the device115-bmay be an example of one or more devices115, a device115-a, a device300, or a device400, as described with reference toFIGS.1through4. The server120-cmay be an example of a server120or a server120-adescribed with reference toFIGS.1and2. The server120-b, in some examples, may provide functionality for, or support aspects of, a system managed by an organization. In the following description of the process flow500, the operations may be performed in a different order than the order shown. For example, specific operations may also be left out of the process flow500, or other operations may be added to process flow500.

The process flow500may illustrate a method to associate a user-generated unique identifier with one or more accounts of the user, and include the unique identifier in communications from the server120-bto the device115-b. In some examples, the user may generate the unique identifier as part of setting up a new account. Additionally, or alternatively, the user may update or associate an additional unique identifier with an existing account.

At505, the server120-bmay transmit a prompt for a unique identifier to the device115-b. For example, as part of setting up a new account, modifying an existing account, or both, the user may determine to generate and associate a unique identifier of the account. Accordingly, the user may, using the device115-b, access an application managed by the server120-b, such as an application405as described with reference toFIG.4. In response, the server120-bmay transmit or provide the prompt to the device115-b

Accordingly, at510, the user may generate an identifier and input the identifier to the device115-b(e.g., input in response to the prompt). For example, the user may generate a phrase, a passcode, a pictogram, an image, an audio message recorded by the user, or any combination thereof, and may input the generated identifier to the device115-b. The device115-bmay, at515, transmit the identifier to the server120-b, and the server120-bmay, at520, determine whether the identifier is unique.

For example, the server120-bmay compare the received identifier with one or more identifiers stored in a database (e.g., a database125) and associated with other users (e.g., accounts of other users), and may determine whether the received identifier is the same or similar to an identifier of the one or more identifiers. If the server120-bdetermines that the received identifier is not unique, the server120-bmay transmit an indication (e.g., an error message) to the device115-b, along with a prompt to generate and input an additional identifier. Accordingly, the process flow500may return to510.

Alternatively, the server120-bdetermines that the received identifier is unique, the server120-bmay, at525, associate the identifier with the user (e.g., one or more accounts of the user). For example, the server120-bmay store the unique identifier within a profile of the user. In some examples, as part of associating the identifier with the user, the server120-bmay modify the received identifier. For example, the server120-bmay embed an additional identifier, such as an image associated with organization (e.g., a logo of the organization), a phrase associated with the organization, or both, within the received identifier. In some cases, to embed the additional identifier, the server120-bmay overlay the additional identifier onto the received identifier.

In some cases, the user may request that the server120-bgenerate a unique identifier for the user (e.g., rather than the user generating the unique identifier). For example, as part of setting up or modifying the account, the user may cause (e.g., via the application) the device115-bto transmit an indication to the server120-bto generate an identifier. Accordingly, at530, the server120-bmay generate a unique identifier and associate the unique identifier with the user.

In some cases, the server120-bmay determine whether the user approves the generated identifier. For example, at535, the server120-bmay transmit the generated identifier to the device115-b. If the user approves the identifier, the user may cause (e.g., via the application) the device115-bto transmit an acknowledgment to the server120-b, and the server120-bmay associate the identifier with the account. Alternatively, if the user does not approve the identifier, the user may cause the device115-bto transmit a request to the server120-bfor a second identifier. Accordingly, the process flow500may return to530.

The server120-bmay include the unique identifier associated with an account in subsequent communication associate with the account to the device115-b. For example, at540, the server120-bmay establish a communication session between the device115-band the server120-b. As part of the communication session, the server120-bmay generate a message associated with the account (e.g., a message which includes account information). In some examples, the message may include an MMS message, an SMS message, a push notification, or any combination thereof.

At545, the server120-bmay embed the unique identifier in the message. For example, the server120-bmay attach the unique identifier to the message, or otherwise modify the message to display the unique identifier. Accordingly, at550the server120-bmay transmit the message, including the embedded identifier, to the device115-b. After receiving the message, the device115-bmay, at555support verifying the source of the message (e.g., the sender of the message) by displaying the message and embedded identifier to the user. By viewing the embedded identifier, the user may verify the source of the message, and thus increase security of communications between the organization and the user.

FIG.6illustrates an example of a process flow600that supports techniques for verifying a sender identity using a user-generated identifier in accordance with one or more aspects of the present disclosure. The process flow600or aspects thereof may be implemented by a device115-cassociated with a user (e.g., a user105) and by a server120-cassociated with an organization (e.g., an organization110), which may each be examples of the corresponding entities as described with reference toFIGS.1through5. For example, the device115-cmay be an example of one or more devices115, a device115-a, a device300, a device400, or a device115-b, as described with reference toFIGS.1through5. The server120-cmay be an example of a server120, a server120-a, or a server120-bdescribed with reference toFIG.1,2or3. In some aspects, the server120-cmay provide functionality for, or support aspects of, a system managed by an organization. In the following description of the process flow600, the operations may be performed in a different order than the order shown. For example, specific operations may also be left out of the process flow600, or other operations may be added to process flow600.

The process flow600may illustrate a method for the user to verify the identity of the organization as part of an outbound call (e.g., a telephone call to the device115-c) from a representative of the organization, such as the representative135. In some examples, at605, the user may, using an application managed by the server120-c(e.g., an application405), configure one or more account settings to request to receive a unique identifier associated with the user as part of communications associated with one or more accounts of the user from the representative.

Accordingly, as part of establishing a communication session at610, a representative of the organization may initiate an outbound call to the device115-c(e.g., using an automated dialing system or dial-assisted call system). In some cases, at615, the server120-cmay transmit the unique identifier to the device115-cusing a same communication channel as the communication session. For example, if the unique identifier includes an audio message, the server120-cmay play the audio file as part of establishing the communication session at610(e.g., upon the device115-canswering the outbound call).

Additionally, or alternatively, the server120-cmay transmit the unique identifier to the device115-cusing a communication channel different than the communication channel used for the communication session. For example, if the user has requested to receive the unique identifier (e.g., requested using one or more profile or account settings at605) as part of outbound calls, the server120-cmay transmit the unique identifier to the device115-cat615using a message, such as an MMS message, an SMS message, a push notification, or a combination thereof.

In some cases, a user may, at620, request the unique identifier during the communication session, for example as part of the telephone call between the representative and the user. In such cases, at625, the server120-cmay support transmitting the unique identifier to the device115-cusing a message, such as an MMS message, an SMS message, a push notification, or a combination thereof. To enhance security of the unique identifier, the server120-cmay not display the unique identifier to the representative. For example, the server120-cmay provide a function to the representative to transmit the unique identifier, without revealing the unique identifier to the representative. Accordingly, the representative may execute the function using the server120-cto transmit the unique identifier to the device115-c.

FIG.7illustrates a system700including a device705that supports techniques for verifying a sender identity using a user-generated identifier in accordance with one or more aspects of the present disclosure. The device705may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as an action response component720, an input/output (I/O) controller710, a database controller715, a memory725, a processor730, and a database735. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus740).

The I/O controller710may manage input signals745and output signals750for the device705. The I/O controller710may also manage peripherals not integrated into the device705. In some cases, the I/O controller710may represent a physical connection or port to an external peripheral. In some cases, the I/O controller710may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another operating system. Additionally, or alternatively, the I/O controller710may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller710may be implemented as part of a processor. In some examples, a user may interact with the device705via the I/O controller710or via hardware components controlled by the I/O controller710.

The database controller715may manage data storage and processing in a database735. The database735may be external to the device705, temporarily or permanently connected to the device705, or a data storage component of the device705. In some cases, a user may interact with the database controller715. In some other cases, the database controller715may operate automatically without user interaction. The database735may be an example of a persistent data store, a single database, a distributed database, multiple distributed databases, a database management system, or an emergency backup database.

Memory725may include random-access memory (RAM) and read only memory (ROM). The memory725may store computer-readable, computer-executable software including instructions that, when executed, cause the processor to perform various functions described herein. In some cases, the memory725may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The processor730may include an intelligent hardware device (e.g., a general-purpose processor, a digital signal processor (DSP), a central processing unit (CPU), a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor730may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the processor730. The processor730may be configured to execute computer-readable instructions stored in memory725to perform various functions (e.g., functions or tasks supporting techniques for verifying a sender identity using a user-generated identifier).

For example, the action response component720may be configured as or otherwise support a means for receiving, by a system managed by a system (e.g., the system700), a unique identifier generated by a user and provided via a device (e.g., a smartphone, a tablet, a laptop computer, or the like) associated with the user, the user having one or more accounts associated with the organization. The action response component720may be configured as or otherwise support a means for establishing a communication session between the organization and the user. The action response component720may be configured as or otherwise support a means for generating, by the system and as part of the communication session, a message associated with the one or more accounts provided by the organization. The action response component720may be configured as or otherwise support a means for embedding the unique identifier into the message. The action response component720may be configured as or otherwise support a means for transmitting, as part of the communication session, the message to the device associated with the user.

Additionally, or alternatively, the action response component720may be configured as or otherwise support means for generating, by a system (e.g., the system700) managed by an organization, a unique identifier associated with a user, the user having one or more accounts associated with the organization, where the unique identifier is automatically generated in response to a request received at the system from a device associated with the user. The action response component720may be configured as or otherwise support a means for establishing a communication session between the organization and the user. The action response component720may be configured as or otherwise support a means for generating, by the system and as part of the communication session, a message associated with the one or more accounts provided by the organization. The action response component720may be configured as or otherwise support a means for embedding the unique identifier into the message. The action response component720may be configured as or otherwise support a means for transmitting, as part of the communication session, the message to the device associated with the user.

By including or configuring the action response component720in accordance with examples as described herein, the device705may support techniques for verifying a sender identity using a user-generated identifier.

FIG.8illustrates a flowchart showing a method800that supports techniques for verifying a sender identity using a user-generated identifier in accordance with one or more aspects of the present disclosure. The operations of the method800may be implemented by a user generated identifier support system or its components as described herein. For example, the operations of the method800may be performed by a user generated identifier support system as described with reference toFIGS.1through3. In some examples, a user generated identifier support system may execute a set of instructions to control the functional elements of the user generated identifier support system to perform the described functions. Additionally, or alternatively, the user generated identifier support system may perform aspects of the described functions using special-purpose hardware.

At805, the method may include receiving, at a system managed by an organization, a unique identifier generated by a user and provided via a device associated with the user, the user having one or more accounts associated with the organization. The operations of805may be performed in accordance with examples as disclosed herein.

At810, the method may include establishing a communication session between the organization and the user. The operations of810may be performed in accordance with examples as disclosed herein.

At815, the method may include generating, by the system and as part of the communication session, a message associated with the one or more accounts provided by the organization. The operations of815may be performed in accordance with examples as disclosed herein.

At820, the method may include embedding the unique identifier into the message. The operations of820may be performed in accordance with examples as disclosed herein.

At825, the method may include transmitting, as part of the communication session, the message to the device associated with the user. The operations of825may be performed in accordance with examples as disclosed herein.

In some examples, an apparatus as described herein may perform a method or methods, such as the method800. The apparatus may include features, circuitry, logic, means, or instructions (e.g., a non-transitory computer-readable medium storing instructions executable by a processor) for receiving, at a system managed by an organization, a unique identifier generated by a user and provided via a device associated with the user, the user having one or more accounts associated with the organization, establishing a communication session between the organization and the user, generating, by the system and as part of the communication session, a message associated with the one or more accounts provided by the organization, embedding the unique identifier into the message, and transmitting, as part of the communication session, the message to the device associated with the user.

Some examples of the method800and the apparatus described herein may further include operations, features, means, or instructions for transmitting, to the device associated with the user, a prompt for the unique identifier and receiving, from the device and in response to the prompt, an indication of a first identifier generated by the user, wherein the unique identifier comprises the first identifier.

Some examples of the method800and the apparatus described herein may further include operations, features, means, or instructions for determining that the first identifier may be unique among a plurality of identifiers stored in a database of the system, wherein the unique identifier comprises the first identifier based at least in part on the first identifier being unique.

Some examples of the method800and the apparatus described herein may further include operations, features, means, or instructions for transmitting, to the device associated with the user, a first prompt for the unique identifier, receiving, from the device and in response to the first prompt, an indication of a first identifier generated by the user, transmitting, to the device, an indication that the first identifier may be not unique based at least in part on a comparison of the first identifier with a plurality of identifiers stored in a database of the system, wherein the indication that the first identifier may be not unique comprises a second prompt for the unique identifier, and receiving, from the device and in response to the second prompt, a second identifier generated by the user, the second identifier being different from the first identifier, wherein the unique identifier embedded into the message comprises the second identifier based at least in part on the second identifier being unique among the plurality of identifiers stored in a database of the system.

Some examples of the method800and the apparatus described herein may further include operations, features, means, or instructions for embedding an additional identifier associated with the organization into the unique identifier, wherein the message comprises the unique identifier with the embedded additional identifier.

Some examples of the method800and the apparatus described herein may further include operations, features, means, or instructions for receiving, at the system, a second unique identifier generated by the user and provided via the device, the second unique identifier being different than the unique identifier and associating the second unique identifier with at least one account of the one or more accounts.

Some examples of the method800and the apparatus described herein may further include operations, features, means, or instructions for generating, by the system and as part of the communication session, one or more additional messages associated with the one or more accounts after transmitting the message and transmitting the one or more additional messages to the device associated with the user, wherein the one or more additional messages exclude the unique identifier.

Some examples of the method800and the apparatus described herein may further include operations, features, means, or instructions for providing, as part of an outbound call associated with the communication session, an indication that the user may have requested that the message comprising the unique identifier be provided by a representative of the organization, wherein the communication session comprises communications between the representative and the user, and wherein the message may be transmitted in response to the provided indication.

Some examples of the method800and the apparatus described herein may further include operations, features, means, or instructions for determining that a threshold duration after identifying the unique identifier may have been satisfied and transmitting, to the device associated with the user, a request message comprising an indication to modify the unique identifier.

Some examples of the method800and the apparatus described herein may further include operations, features, means, or instructions for configuring the threshold duration of based at least in part on an input from the user.

In some examples of the method800and the apparatus described herein, the message comprises an MMS message, an SMS message, push notification, or any combination thereof.

In some examples of the method800and the apparatus described herein, the unique identifier comprises a phrase, a code, a pictogram, an image, an audio message recorded by the user, or any combination thereof.

FIG.9illustrates a flowchart showing a method900that supports techniques for verifying a sender identity using a user-generated identifier in accordance with one or more aspects of the present disclosure. The operations of the method900may be implemented by a user generated identifier support system or its components as described herein. For example, the operations of the method900may be performed by a user generated identifier support system as described with reference toFIGS.1through3. In some examples, a user generated identifier support system may execute a set of instructions to control the functional elements of the user generated identifier support system to perform the described functions. Additionally, or alternatively, the user generated identifier support system may perform aspects of the described functions using special-purpose hardware.

At905, the method may include generating, by a system managed by an organization, a unique identifier associated with a user, the user having one or more accounts associated with the organization, wherein the unique identifier is automatically generated in response to a request received at the system from a device associated with the user. The operations of905may be performed in accordance with examples as disclosed herein.

At910, the method may include establishing a communication session between the organization and the user. The operations of910may be performed in accordance with examples as disclosed herein.

At915, the method may include generating, by the system and as part of the communication session, a message associated with the one or more accounts provided by the organization. The operations of915may be performed in accordance with examples as disclosed herein.

At920, the method may include embedding the unique identifier into the message. The operations of920may be performed in accordance with examples as disclosed herein.

At925, the method may include transmitting, as part of the communication session, the message to the device associated with the user. The operations of925may be performed in accordance with examples as disclosed herein.

In some examples, an apparatus as described herein may perform a method or methods, such as the method900. The apparatus may include features, circuitry, logic, means, or instructions (e.g., a non-transitory computer-readable medium storing instructions executable by a processor) for generating, by a system managed by an organization, a unique identifier associated with a user, the user having one or more accounts associated with the organization, wherein the unique identifier is automatically generated in response to a request received at the system from a device associated with the user, establishing a communication session between the organization and the user, generating, by the system and as part of the communication session, a message associated with the one or more accounts provided by the organization, embedding the unique identifier into the message, and transmitting, as part of the communication session, the message to the device associated with the user.

In some examples of the method900and the apparatus described herein, generating the unique identifier may include operations, features, circuitry, logic, means, or instructions for randomly generating the unique identifier such that the unique identifier may be different from a plurality of other identifiers stored in a database of the system.

In some examples of the method900and the apparatus described herein, generating the unique identifier may include operations, features, circuitry, logic, means, or instructions for generating a plurality of unique identifiers that may be each different from a plurality of other identifiers stored in a database of the system, the method further comprising, transmitting, to the device, a first message including an indication of the plurality of unique identifiers, and receiving, from the device, a second message indicating a selection of a first unique identifier from the plurality of unique identifiers, wherein the unique identifier embedded into the message comprises the first unique identifier based at least in part on receiving the second message indicating the selection.

Some examples of the method900and the apparatus described herein may further include operations, features, means, or instructions for transmitting, to the device, a first message including an indication of the unique identifier generated by the system and receiving, from the device, a second message indicating that the unique identifier may be accepted by the user, wherein the unique identifier may be embedded into the message based at least in part on receiving the second message indicating that the unique identifier may be accepted by the user.

Some examples of the method900and the apparatus described herein may further include operations, features, means, or instructions for transmitting, to the device, a first message including an indication of a first unique identifier generated by the system, the first unique identifier being unique among a plurality of other identifiers stored in a database of the system, receiving, from the device, a second message indicating that the unique identifier may be not accepted by the user, transmitting, to the device and in response to the second message, a third message including an indication of a second unique identifier generated by the system, the second unique identifier being different from the first unique identifier and being unique among the plurality of other identifiers stored in the database of the system, and receiving, from the device, a fourth message indicating that the second unique identifier may be accepted by the user, wherein the unique identifier embedded into the message comprises the second unique identifier based at least in part on the fourth message indicating that the second unique identifier may be accepted by the user.

Some examples of the method900and the apparatus described herein may further include operations, features, means, or instructions for receiving the request from the device based at least in part on one or more failed attempts by the user to generate the unique identifier.

Some examples of the method900and the apparatus described herein may further include operations, features, means, or instructions for receiving the request from the device based at least in part on establishing at least one of the one or more accounts by the organization.

It should be noted that these methods describe examples of implementations, and that the operations and the steps may be rearranged or otherwise modified such that other implementations are possible. In some examples, aspects from two or more of the methods may be combined. For example, aspects of each of the methods may include steps or aspects of the other methods, or other steps or techniques described herein. Thus, aspects of the disclosure may provide for techniques for verifying a sender identity using a user-generated identifier (e.g., a user-generated unique identifier).

Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The various illustrative blocks and modules described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). The functions of each unit may also be implemented, in whole or in part, with instructions embodied in a memory, formatted to be executed by one or more general or application-specific processors.