dido:99_annexes:annex-b-terms-and-definitions:t:transaction

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dido:99_annexes:annex-b-terms-and-definitions:t:transaction [2026/07/11 11:14] – ↷ Page moved from dido:99_annexes:99_annexes:annex-b-terms-and-definitions:t:transaction to dido:99_annexes:annex-b-terms-and-definitions:t:transaction nick_didodido:99_annexes:annex-b-terms-and-definitions:t:transaction [2026/07/18 12:33] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Transaction ====== ====== Transaction ======
  
-[[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]+[[dido:99_annexes:annex-b-terms-and-definitions:start|Go up to Terms and Definitions]]
  
 ===== Discussion ===== ===== Discussion =====
Line 9: Line 9:
 In a financial system, a Transaction provides the business context for validation, interpretation, state management, settlement, audit, provenance, evidence, and review. A Transaction may describe an agreed financial event, a proposed financial event, an instruction, an order, a transfer, a contract event, or another governed business interaction, depending on the applicable domain profile. In a financial system, a Transaction provides the business context for validation, interpretation, state management, settlement, audit, provenance, evidence, and review. A Transaction may describe an agreed financial event, a proposed financial event, an instruction, an order, a transfer, a contract event, or another governed business interaction, depending on the applicable domain profile.
  
-The Financial Systems Archetype treats a Transaction as a conceptual business item, not as a message, file, database record, API payload, or runtime event. Later, logical and implementation profiles define the information structures, endpoints, services, and artefacts that represent or process transactions.+The Financial Systems Archetype treats a Transaction as a conceptual business item, not as a message, file, database record, API payload, or runtime event. Later, logical and implementation profiles define the information structures, endpoints, services, and artifacts that represent or process transactions.
  
 ===== Definition ===== ===== Definition =====
Line 17: Line 17:
 ===== Source ===== ===== Source =====
  
-Generalised from financial-system transaction concepts used by the [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:f:financial_system|Financial System]] and [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:f:foreign_exchange_domain|Foreign Exchange Domain]] material in the FX Demo [[dido:99_annexes:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]].+Generalised from financial-system transaction concepts used by the [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_system|Financial System]] and [[dido:99_annexes:annex-b-terms-and-definitions:f:foreign_exchange_domain|Foreign Exchange Domain]] material in the FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]].
  
 ===== Note ===== ===== Note =====
  
-A Transaction is not a message, file, [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:t:an_application_programming_interface_api_provides_an_implementation_interface_through_which_software_components_systems_services_applications_tools_or_users_request_provide_exchange_or_control_information_or_behaviour]] payload, database row, DDS sample, event stream record, or deployment artefact. Those artefacts may represent, carry, store, or process transaction information.+A Transaction is not a message, file, [[fxdemo:dido_99_annexes:annex-b-terms-and-definitions:t:an_application_programming_interface_api_provides_an_implementation_interface_through_which_software_components_systems_services_applications_tools_or_users_request_provide_exchange_or_control_information_or_behaviour]] payload, database row, DDS sample, event stream record, or deployment artifact. Those artifacts may represent, carry, store, or process transaction information.
  
 ===== Example ===== ===== Example =====
  • dido/99_annexes/annex-b-terms-and-definitions/t/transaction.1783793684.txt.gz
  • Last modified: 2026/07/11 11:14
  • by nick_dido