# US 2026/0065272 A1 · System, apparatus and method

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

- Number: US 2026/0065272 A1
- Document ID: US20260065272A1
- Status: Published application
- Kind: A1
- Application number: 19/314,967
- Filed: 2025-08-29
- Published: 2026-03-05
- Earliest claimed: 2024-08-29
- Assignees: Safecypher Ltd
- Applicants: Safecypher Ltd
- Inventors: Benjamin Marcus Jordan
- Web page: https://patentgrep.com/patent/US20260065272A1

## CPC

- G06Q 20/401: {Transaction verification}
- H04L 63/0846: {using time-dependent-passwords, e.g. periodically changing passwords}
- G06Q 20/38215: {Use of certificates or encrypted proofs of transaction rights}
- G06Q 20/3829: {involving key management}
- G06Q 20/385: {using an alias or single-use codes}
- G06Q 20/4016: {involving fraud or risk level assessment in transaction processing}
- G06Q 20/409: {Device specific authentication in transaction processing}
- H04L 63/0838: {using one-time-passwords}
- 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

A payment processing network configured for dynamic authentication integration is disclosed. The network comprises an Access Control Server (ACS) and an issuer processing system in communication over the network. The ACS is configured to receive an authentication request message (AReg) including a dynamic authentication code, extract the code, generate a validation request including the code, and transmit the validation request to the issuer processing system. The issuer processing system is configured to forward the validation request to a dynamic authentication system, receive a validation result from the dynamic authentication system, and return the validation result to the ACS. The ACS further comprises a risk calculation engine configured to receive the validation result, calculate a risk factor derived from transaction metadata, apply a risk modification algorithm that utilises the validation result and the risk factor to generate a modified risk factor, and generate an authentication response message (ARes) based on the modified risk factor for transmission over the communications network.

## Claims

### Claim 1

A payment processing network configured for dynamic authentication integration, the network comprising:
an Access Control Server ACS and issuer processing system operative to communicate with each other over the network, wherein the ACS is configured to:
receive from the communications network an Authentication Request (AReq) message comprising a dynamic authentication code;
extract the dynamic authentication code from the AReq message;
generate a validation request comprising the dynamic authentication code; and
transmit the validation request to the issuer processing system; and
wherein the issuer processing system is configured to:
receive the validation request from the ACS;
forward the validation request comprising the dynamic authentication code to a dynamic authentication system;
receive a validation result from the dynamic authentication system; and
return the validation result to the ACS;
the ACS further comprising a risk calculation engine configured to:
receive the validation result from the issuer processing system;
calculate a risk factor derived from transaction metadata;
apply a risk modification algorithm that utilises the validation result and the risk factor to generate a modified risk factor; and
generate an authentication response message (ARes) based on the modified risk factor for transmission over the communications network.

### Claim 2 (depends on 1)

A network according to claim 1, further comprising a computing device configured to generate the dynamic authentication code using a time-based algorithm and stored cryptographic secret within a secure processing environment.

### Claim 3 (depends on 1)

A network according to claim 1, wherein the dynamic authentication code is a time-based one-time password (TOTP) generated using a TOTP secret key and a current time value.

### Claim 4 (depends on 1)

A network according to claim 1 wherein the risk calculation engine is further configured to apply a weighting function responsive to the validation result indicating a successful dynamic code validation.

### Claim 5 (depends on 4)

A network according to claim 4, wherein the weighting function comprises applying a predetermined risk reduction factor to the risk factor derived from the transaction metadata.

### Claim 6 (depends on 1)

A network according to claim 1, wherein the ACS is further configured to:
identify the presence of a dynamic authentication code within the AReq messages based on an associated metadata flag; and
extract a dynamic Card Verification Value (dCVV) from a Card Security Code field within the AReq message upon identifying the presence of a dynamic authentication code.

### Claim 7 (depends on 1)

A network according to claim 1, wherein the dynamic authentication system is configured to validate the dynamic authentication code against a stored reference secret.

### Claim 8 (depends on 7)

A network according to claim 7, wherein the dynamic authentication system is further configured to:
decrypt a stored encrypted cryptographic secret corresponding to payment instrument identification data;
execute a time-based algorithm using the decrypted secret to generate a reference authentication code; and
execute a comparison between the received dynamic authentication code and the generated reference authentication code.

### Claim 9 (depends on 1)

A network according to claim 1, wherein the issuer processing system is further configured to execute static validation of the authentication code when dynamic validation is unavailable.

### Claim 10 (depends on 1)

An Access Control Server (ACS) for use in a network according claim 1, wherein the ACS is configured to:
receive an Authentication Request (AReq) message comprising a dynamic authentication code;
extract the dynamic authentication code from the AReq message;
generate a validation request comprising the dynamic authentication code;
transmit the validation request to an issuer processing system;
receive a validation result from the issuer processing system;
calculate a risk factor derived from transaction metadata;
apply a risk modification algorithm that utilises the validation result and the risk factor to generate a modified risk factor; and generate an authentication response message (ARes) based on the modified risk factor.

### Claim 11 (depends on 1)

An issuer processing system for use in a network according to claim 1,
wherein the issuer processing system is configured to:
receive a validation request from an ACS;
forward the validation request comprising a dynamic authentication code to a dynamic authentication system;
receive a validation result from the dynamic authentication system; and
return the validation result to the ACS.

### Claim 12

A method for dynamic authentication integration in payment processing over a network, the method comprising:
receiving, at an Access Control Server (ACS), an Authentication Request (AReq) message comprising a dynamic authentication code;
extracting the dynamic authentication code from the AReq message;
generating a validation request comprising the dynamic authentication code;
transmitting the validation request to an issuer processing system;
receiving, at the issuer processing system, the validation request from the ACS;
forwarding the validation request comprising the dynamic authentication code to a dynamic authentication system;
receiving a validation result from the dynamic authentication system at the issuer processing system;
returning the validation result to the ACS;
calculating, at the ACS, a risk factor derived from transaction metadata;
applying a risk modification algorithm that utilises the validation result and the risk factor to generate a modified risk factor; and
generating an authentication response message (ARes) based on the modified risk factor.

### Claim 13 (depends on 12)

A method according to claim 12, further comprising generating the dynamic authentication code using a time-based algorithm and stored cryptographic secret within a secure processing environment.

### Claim 14 (depends on 13)

A method according to claim 13, wherein generating the dynamic authentication code comprises generating a time-based one-time password (TOTP) using a TOTP secret key and a current time value.

### Claim 15 (depends on 12)

A method according to claim 12, further comprising applying a weighting function when the validation result indicates successful dynamic code validation.

### Claim 16 (depends on 15)

A method according to claim 15, wherein applying the weighting function comprises applying a predetermined risk reduction factor to the risk factor derived from the transaction metadata.

### Claim 17 (depends on 12)

A method according to claim 12, further comprising identifying the presence of a dynamic authentication code within the AReq messages based on associated metadata flag.

### Claim 18 (depends on 12)

A method according to claim 12, further comprising validating the dynamic authentication code against a stored reference secret at the dynamic authentication system.

### Claim 19 (depends on 18)

A method according to claim 18, wherein validating the dynamic authentication code comprises: executing a time-based algorithm using a stored secret to generate a reference authentication code; and executing a comparison between the received dynamic authentication code and the generated reference authentication code.

### Claim 20 (depends on 12)

A method according to claim 12, further comprising executing static validation of the authentication code when dynamic validation is unavailable.
