# Transactions: confirmation must represent execution

https://thiago.limaesilvatecnologia.com.br/en/artigos/transaction-integrity/

Published: 2026-09-12

Users should authorize the parameters producing the effect.

Content produced with AI assistance for Thiago Silva’s website. Independent editorial analysis; it does not represent clients or employers.

Reading-path month: August 2026

Collection published on September 12, 2026. Months organize the reading path; they are not earlier publication dates.

A short architecture article. The technical reference supports the topic; hypothetical scenarios and assessment proposals are editorial analysis, not accounts of personal implementations.

## The architecture decision

Generic confirmation can become detached from actual amount, recipient or resource. Review integrity between presentation and execution.

## Practical application

Editorial proposal: for a hypothetical transfer, record confirmed parameters and execution checks. Consider expiry and subsequent changes.

## How to verify

Change a parameter after confirmation in testing and observe the decision. Include repetition and communication failure. Protect the actual operation while providing a clear way to restart transactions no longer matching authorization.

## Sources

- [OWASP — Transaction Authorization Cheat Sheet](https://cheatsheetseries.owasp.org/cheatsheets/Transaction_Authorization_Cheat_Sheet.html). Accessed: 2026-09-12.

[Profile: Thiago Silva | Cyber Architect](https://thiago.limaesilvatecnologia.com.br/en/perfil/)