# US 2026/0089155 A1 · Systems and methods for multi-factor authentication

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0089155 A1
- Document ID: US20260089155A1
- Status: Published application
- Kind: A1
- Application number: 18/894,320
- Filed: 2024-09-24
- Published: 2026-03-26
- Earliest claimed: 2024-09-24
- Assignees: Infobip Ltd.
- Applicants: Infobip Ltd.
- Inventors: Kwok Onn LOOI
- Web page: https://patentgrep.com/patent/US20260089155A1

## CPC

- G06Q 20/385: {using an alias or single-use codes}
- H04L 63/0838: {using one-time-passwords}
- G06Q 20/108: {Remote banking, e.g. home banking}
- G06Q 20/12: specially adapted for electronic shopping systems
- G06Q 20/401: {Transaction verification}
- G06Q 20/40145: {Biometric identity checks}
- G06Q 20/425: {using two different networks, one for transaction and one for security confirmation}
- H04L 2463/082: applying multi-factor authentication
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems and methods are disclosed for authentication. One or more processors may receive a user transaction request. One or more processors may generate an authentication request data object in response to the user transaction request, wherein the authentication request data object comprises an authentication code and a link. One or more processors may deliver the authentication request data object, including the authentication code and the link, to a pre-registered contact identifier associated with a decentralized identity. One or more processors may receive a response data object from the user selecting the link, wherein the response data object is associated with the decentralized identity and the authentication code. One or more processors may validate a user authentication based on the received response data object. One or more processors may authorize a transaction associated with the user transaction request upon successful validation of the user authentication.

## Claims

### Claim 1

A computer-implemented method for multi-factor authentication, the method comprising:
receiving, by one or more processors, a user transaction request;
generating, by the one or more processors, an authentication request data object in response to the user transaction request, wherein the authentication request data object comprises an authentication code and a link;
delivering, by the one or more processors, the authentication request data object, including the authentication code and the link, to a pre-registered contact identifier associated with a decentralized identity;
receiving, by the one or more processors, a response data object from a user selecting the link, wherein the response data object is associated with the decentralized identity and the authentication code;
validating, by the one or more processors, a user authentication based on the received response data object; and
authorizing, by the one or more processors, a transaction associated with the user transaction request upon successful validation of the user authentication.

### Claim 2 (depends on 1)

The computer-implemented method of claim 1, further comprising registering, by the one or more processors, the decentralized identity and the pre-registered contact identifier during a user onboarding process with an application provider, wherein the registering includes determining a level of assurance for the user, and wherein the generating an authentication request data object is based at least in part on the determined level of assurance.

### Claim 3 (depends on 2)

The computer-implemented method of claim 2, wherein the authentication code is generated based on details associated with biometric aspects of the user, details of the transaction, or one or more user-specific details, and the generation of the link is determined based on a desired channel and one or more user authentication methods.

### Claim 4 (depends on 1)

The computer-implemented method of claim 1, wherein the generating of the authentication request data object further comprises linking the decentralized identity and the authentication code.

### Claim 5 (depends on 1)

The computer-implemented method of claim 1, further comprising applying a machine-learning model to analyze user behavior patterns and actions associated with the user to identify potential fraud before generating the authentication request data object.

### Claim 6 (depends on 1)

The computer-implemented method of claim 1, wherein the response data object received from the user further includes biometric data, and the method further comprises combining the received authentication code and the biometric data into a single data packet.

### Claim 7 (depends on 6)

The computer-implemented method of claim 6, further comprising using the single data packet to unlock or approve the transaction, wherein the single data packet is required to contain data from both the generated authentication code and the biometric data.

### Claim 8 (depends on 1)

The computer-implemented method of claim 1, further comprising verifying the authenticity of the decentralized identity using a secure credential issued by an authorized entity.

### Claim 9 (depends on 1)

The computer-implemented method of claim 1, wherein the link directs the user to a secure authentication page, and the method further comprises presenting one or more additional challenges on the secure authentication page based on user behavior analysis.

### Claim 10 (depends on 1)

The computer-implemented method of claim 1, wherein the decentralized identity is a verifiable credential stored in a digital wallet on a device of the user, and the method further comprises verifying the verifiable credential as part of the validating the user authentication.

### Claim 11

A system comprising memory and one or more processors communicatively coupled to the memory, the one or more processors configured to:
receive a user transaction request;
generate an authentication request data object in response to the user transaction request, wherein the authentication request data object comprises an authentication code and a link;
deliver the authentication request data object, including the authentication code and the link, to a pre-registered contact identifier associated with a decentralized identity;
receive a response data object from a user selecting the link, wherein the response data object is associated with the decentralized identity and the authentication code;
validate a user authentication based on the received response data object; and
authorize a transaction associated with the user transaction request upon successful validation of the user authentication.

### Claim 12 (depends on 11)

The system of claim 11, wherein the one or more processors are further configured to register the decentralized identity and the contact identifier during a user onboarding process with an application provider.

### Claim 13 (depends on 12)

The system of claim 12, wherein the one or more processors are configured to generate the authentication code based on details associated with biometric aspects of the user, details of the transaction, or any other user-specific details.

### Claim 14 (depends on 11)

The system of claim 11, wherein the one or more processors are further configured to link the decentralized identity and the authentication code when generating the authentication request data object.

### Claim 15 (depends on 11)

The system of claim 11, wherein the one or more processors are further configured to apply a machine-learning model to analyze user behavior patterns and actions associated with the user to identify potential fraud before generating the authentication request data object.

### Claim 16 (depends on 11)

The system of claim 11, wherein the response data object received from the user further includes biometric data, and the one or more processors are further configured to combine the received authentication code and the biometric data into a single data packet.

### Claim 17 (depends on 16)

The system of claim 16, wherein the one or more processors are further configured to use the single data packet to unlock or approve the transaction, wherein the single data packet is required to contain data from both the generated authentication code and the biometric data.

### Claim 18 (depends on 11)

The system of claim 11, wherein the one or more processors are further configured to verify the authenticity of the decentralized identity using a secure credential issued by an authorized entity.

### Claim 19 (depends on 11)

The system of claim 11, wherein the link directs the user to a secure authentication page, and the one or more processors are further configured to present one or more additional challenges on the secure authentication page based on a determined level of assurance.

### Claim 20

One or more non-transitory computer-readable storage media including instructions that, when executed by one or more processors, cause the one or more processors to:
receive a user transaction request;
generate an authentication request data object in response to the user transaction request, wherein the authentication request data object comprises an authentication code and a link;
deliver the authentication request data object, including the authentication code and the link, to a pre-registered contact identifier associated with a decentralized identity;
receive a response data object from a user selecting the link, wherein the response data object is associated with the decentralized identity and the authentication code;
validate a user authentication based on the received response data object; and
authorize a transaction associated with the user transaction request upon successful validation of the user authentication.
