An FX Transaction Candidate represents candidate FX Transaction information received by the FX Demo logical node network before validation, interpretation, contract state processing, or cash-flow computation.
The FX Transaction Candidate preserves the information submitted for processing, including transaction identifiers, currency pair, counterparties, trade date, settlement date, notional amounts, rate information, contractual references, source context, intake timestamp, and provenance reference as applicable to the FX Demo logical profile.
The FX Transaction Candidate participates primarily in the FX Logical Data Plane. It also supports the FX Logical Audit and Provenance Plane because later validation, interpretation, contract state, computation, release, replay, and evidence relationships trace back to the candidate input.
candidate Transaction information received for FX processing
Specialization of Logical Data Structure Definition and Logical Data Structure Instance from Part 2: Distributed Node-Based Logical Architecture, Sections 8.2 and 8.3, and Data Structure Definition and Data Structure Instance from Part 1: Conceptual Architecture, Sections 7.7 and 7.8; generalised from FX transaction intake material in the original FX Demo Reference Architecture.
An FX Transaction Candidate is not a file, API payload, DDS sample, Protocol Buffers message, IDL structure, database row, user-interface form, or wire-format message. Implementation profiles select those representations.
An FX Transaction Candidate contains the submitted details for an FX forward transaction before the FX Validation Node determines whether the candidate satisfies logical validation expectations.