# US 2026/0065267 A1 · System, apparatus and method for authentication in payment transactions

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

- Number: US 2026/0065267 A1
- Document ID: US20260065267A1
- Status: Published application
- Kind: A1
- Application number: 18/830,557
- Filed: 2024-09-10
- 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/US20260065267A1

## 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 system for dynamic authentication of payment transactions comprises a first computing system communicatively coupled to a computer communications network. The first computing system receives an activation request for a payment instrument from a second computing system, generates and transmits an activation token to the second system, receives an encrypted data item from the second system, and stores the encrypted data item with a payment instrument identifier. During a transaction, the first system receives a verification request with a dynamic authentication code from a payment issuer, retrieves the stored encrypted data item, validates the dynamic code using the data item, and transmits a verification result to the issuer indicating whether the transaction is authenticated based on the validation outcome. The system enables secure dynamic authentication without requiring constant communication between devices.

## Claims

### Claim 1

A system for dynamic authentication of a payment transaction, comprising:
a first computing system communicatively couplable to a computer communications network, wherein the first computing system is configured to:
receive from a second computing system communicatively couplable to the computer communications network a request to activate a payment instrument;
generate an activation token responsive to the request and transmit the activation token over the computer communications network to the second computing system;
receive over the computer communications network an encrypted data item from the second computing system responsive to the second computing system receiving the activation token;
wherein the encrypted data item is an encrypted version of a cryptographic secret generated locally by the second computing system;
store the encrypted data item with an identifier of the payment instrument in a database;
and, during a payment transaction:
receive, over the computer communications network, a verification request from a payment instrument issuer system communicatively couplable to the computer communications network, wherein the verification request comprises a dynamic authentication code generated by the second computing system using the locally stored cryptographic secret and provided to the payment issuer system by a user during the payment transaction;
retrieve the encrypted data item associated with the identifier of the payment instrument;
validate the dynamic authentication code using the data item; and
transmit a verification result to the issuer system indicating whether the payment transaction is authenticated based on the validation outcome.

### Claim 2 (depends on 1)

A system according to claim 1, wherein the second computing system further comprises:
an application configured to interact with the first computing system over the computer communications network; and
a secure processing environment configured to:
generate the data item;
encrypt the data item to create the encrypted data item;
store the encrypted data item in the second computing system; and
generate a dynamic authentication code using the stored data item.

### Claim 3 (depends on 2)

A system according to claim 2, wherein the encrypted data item is a time-based one-time password (TOTP) secret key; and the dynamic authentication code is a TOTP generated using the TOTP secret key and a current time value and optionally wherein the TOTPs change at predetermined time intervals.

### Claim 4 (depends on 3)

A system according to claim 3, wherein validating the dynamic authentication code comprises:
decrypting the encrypted data item to obtain a decrypted data item;
generating a verification TOTP using the decrypted data item and a time of the payment transaction; and
comparing the generated verification TOTP with the received dynamic authentication code.

### Claim 5 (depends on 2)

A system according to claim 2, the second computing device configured to generate dynamic authentication codes independent of further communications with the first computing system following activation and encrypted data item exchange until a deactivation request is received from the user or the issuer system.

### Claim 6 (depends on 1)

A system according to claim 1, wherein the identifier of the payment instrument is a token associated with the payment instrument.

### Claim 7 (depends on 1)

A system according to claim 1, further comprising an independent monitoring system configured to:
monitor the status of the first computing system; and
activate a fallback mechanism to use static authentication codes responsive to unavailability of the first computing system.

### Claim 8 (depends on 7)

A system according to claim 7, wherein the independent monitoring system comprises:
a monitoring administrative application programming interface (API) configured to receive status updates and control commands responsive to the status of the first computing device wherein the monitoring administrative API provides an interface for accessing real-time and historical data about system performance and security status; and
a security token API monitor comprising a monitoring component configured to monitor the availability and operational status of the first computing system, wherein the security token API monitor is configured to track token lifecycle, monitors token usage patterns, and detects potential security threat.

### Claim 9 (depends on 1)

A system according to claim 1, wherein the issuer system further comprises:
a connection management component configured to interact with the first computing system; and
a payment verification component configured to send verification requests to the first computing system.

### Claim 10 (depends on 1)

A system according to claim 1, wherein the first computing system is implemented using a distributed architecture across multiple locations comprising multiple geographic regions, for high availability and disaster recovery.

### Claim 11

A method for dynamic authentication in payment transactions, comprising:
receiving, by a first computing system communicatively couplable to a computer communications network, a request from a second computing system to activate a payment instrument;
generating, an activation token responsive to the request and transmitting it to the second computing system;
receiving, an encrypted data item from the second computing system responsive to the second computing system receiving the activation token;
wherein the encrypted data item is an encrypted version of a cryptographic secret generated locally by the second computing system;
storing the encrypted data item with an identifier of the payment instrument in a database;
and, during a payment transaction:
receiving, a verification request from a payment instrument issuer system, wherein the verification request comprises a dynamic authentication code generated by the second computing system system using the locally stored cryptographic secret and provided to the payment issuer system by a user during the payment transaction;
retrieving the encrypted data item associated with the identifier of the payment instrument;
validating the dynamic authentication code using the data item; and
transmitting a verification result to the issuer system indicating whether the payment transaction is authenticated based on the validation outcome.

### Claim 12 (depends on 11)

A method of claim 11, further comprising:
generating, by a secure processing environment of the second computing system, the data item;
encrypting the data item to create the encrypted data item;
storing the data item within the second computing system; and
generating the dynamic authentication code using the stored data item.

### Claim 13 (depends on 12)

A method of claim 12, wherein the data item is a time-based one-time password (TOTP) secret key, and the dynamic authentication code is a TOTP generated using the TOTP secret key and a current time value and optionally wherein the TOTPs change at predetermined time intervals.

### Claim 14 (depends on 13)

A method of claim 13, wherein validating the dynamic authentication code comprises:
decrypting the encrypted data item to obtain a decrypted data item;
generating a verification TOTP using the decrypted data item and a time of the payment transaction; and
comparing the generated verification TOTP with the received dynamic authentication code.

### Claim 15 (depends on 12)

A method of claim 12, further comprising:
generating, by the second computing system, dynamic authentication codes independent of further communication with the first computing system following activation and encrypted data item exchange until a deactivation request is received from the user via the second computing system or from the issuer system via the first computing system.

### Claim 16 (depends on 11)

A method of claim 11, wherein the identifier of the payment instrument is a token associated with the payment instrument rather than an actual payment instrument number.

### Claim 17 (depends on 11)

A method of claim 11, further comprising:
monitoring the status of the first computing system using an independent monitoring system; and
activating a fallback mechanism to use static authentication codes when the cloud platform is unavailable.

### Claim 18 (depends on 17)

A method of claim 17, wherein monitoring the status of the first computing system comprises: receiving status updates and control commands via a monitoring administrative module; and checking the availability of the first computing system using a security module monitor.

### Claim 19 (depends on 11)

A method of claim 11, further comprising:
interacting with the first computing system using a connection management component of the issuer system; and
sending verification requests to the first computing system using a payment verification backend of the issuer system.

### Claim 20 (depends on 11)

A method of claim 11, wherein the first computing system is implemented using a distributed architecture across multiple locations, comprising multiple geographic regions for high availability and disaster recovery.
