# US 2025/0225513 A1 · Systems and methods for validating transactions

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

- Number: US 2025/0225513 A1
- Document ID: US20250225513A1
- Status: Published application
- Kind: A1
- Application number: 18/407,937
- Filed: 2024-01-09
- Published: 2025-07-10
- Earliest claimed: 2024-01-09
- Assignees: Capital One Services, LLC
- Applicants: Capital One Services, LLC
- Inventors: Kevin OSBORN; Srinivasa CHIGURUPATI; John JONES
- Web page: https://patentgrep.com/patent/US20250225513A1

## CPC

- G06Q 20/401: {Transaction verification}
- G06Q 20/02: involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
- G06Q 20/3825: {Use of electronic signatures}
- G06Q 20/3827: {Use of message hashing}
- G06Q 20/3829: {involving key management}
- G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction}
- H04L 9/3247: {involving digital signatures}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- G06Q 2220/00: Business processing using cryptography
- 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 of validating transactions are provided. An exemplary system includes a server including a memory and a processor. The server is configured to: receive from an entity a transaction validation request of validating a transaction; validate the transaction; generate a logging record of the transaction validation; cryptographically hash the logging record to create a hashed logging record; digitally sign the hashed logging record using a key to create a signed hashed logging record; and transmit the signed hashed logging record to a computer device.

## Claims

### Claim 1

A system of validating transactions, comprising a server including a memory and a processor, wherein the server is configured to:
receive from an entity a transaction validation request of validating a transaction;
validate the transaction;
generate a logging record of the transaction validation;
cryptographically hash the logging record to create a hashed logging record;
digitally sign the hashed logging record using a key to create a signed hashed logging record; and
transmit the signed hashed logging record to a computer device.

### Claim 2 (depends on 1)

The system according to claim 1, wherein the key is a public key or a private key.

### Claim 3 (depends on 2)

The system according to claim 2, wherein the public key is obfuscated.

### Claim 4 (depends on 1)

The system according to claim 1, wherein the key is managed by a hardware security module of the server.

### Claim 5 (depends on 1)

The system according to claim 1, wherein the entity digitally signs the hashed logging record using the key by accessing to the server.

### Claim 6 (depends on 1)

The system according to claim 1, wherein the logging record comprises a monotonically increasing sequence number.

### Claim 7 (depends on 1)

The system according to claim 1, wherein the logging record comprises a hash of hashes of previous logging records.

### Claim 8 (depends on 1)

The system according to claim 1, wherein the signed hashed logging record is transmitted to the computer device in real time.

### Claim 9

A method of validating transactions performed by a server, comprising:
receiving from an entity a transaction validation request of validating a transaction;
validating the transaction;
generating a logging record of the transaction validation;
cryptographically hashing the logging record to create a hashed logging record;
digitally signing the hashed logging record using a key to create a signed hashed logging record; and
transmitting the signed hashed logging record to a computer device.

### Claim 10 (depends on 9)

The method according to claim 9, wherein the signed hashed logging record is transmitted to the computer device in batch.

### Claim 11 (depends on 9)

The method according to claim 9, wherein the signed hashed logging record is transmitted to the computer device through file logging service.

### Claim 12 (depends on 9)

The method according to claim 9, wherein the signed hashed logging record is transmitted to the computer device through a messaging service.

### Claim 13 (depends on 9)

The method according to claim 9, wherein the server is further configured to generate a heartbeat-patterned message to monitor runtime of the server.

### Claim 14 (depends on 13)

The method according to claim 13, wherein the heartbeat-patterned message comprises timestamps indicating a time interval.

### Claim 15 (depends on 9)

The method according to claim 9, wherein the logging record comprises an event identity, event type information, a timestamp, and event details.

### Claim 16

A non-transitory, computer-readable medium comprising instructions for validating transactions that, when executed on a computer arrangement, cause the computer arrangement to perform actions comprising:
receiving from an entity a transaction validation request of validating a transaction;
validating the transaction;
generating a logging record of the transaction validation;
cryptographically hashing the logging record to create a hashed logging record;
digitally signing the hashed logging record using a key to create a signed hashed logging record; and
transmitting the signed hashed logging record to a computer device.

### Claim 17 (depends on 16)

The non-transitory, computer-readable medium according to claim 16, wherein the key is managed by a hardware security module.

### Claim 18 (depends on 16)

The non-transitory, computer-readable medium according to claim 16, wherein the logging record comprises an event identity, event type information, a timestamp, and event details.

### Claim 19 (depends on 16)

The non-transitory, computer-readable medium according to claim 16, wherein the logging record comprises a hash of hashes of previous logging records.

### Claim 20 (depends on 16)

The non-transitory, computer-readable medium according to claim 16, wherein the actions further comprises generating a heartbeat-patterned message.
