FX Transaction Intake Endpoint

Go up to Terms and Definitions

The FX Transaction Intake Endpoint carries candidate FX transaction information from the FX Transaction Intake Node to downstream FX logical Nodes.

The endpoint supports transaction intake, validation, semantic interpretation, audit, provenance, and evidence expectations. It carries FX Transaction Candidate information or related intake messages governed by the FX Transaction Candidate information structure.

The FX Transaction Intake Endpoint participates primarily in the FX Logical Data Plane. It also relates to the FX Logical Audit and Provenance Plane because intake information requires traceability to the receipt context, resulting in expectations for Node, timestamp, and evidence.

carrying candidate FX transaction information from intake to downstream FX logical processing

Specialization of Logical Communication Endpoint from Part 2: Distributed Node-Based Logical Architecture, Section 7.2, and Communication Endpoint from Part 1: Conceptual Architecture, Section 7.6; generalised from transaction intake and topic material in the original FX Demo Reference Architecture.

The FX Transaction Intake Endpoint is not a DDS Topic, REST resource, RPC method, message queue, event stream, file, database table, or deployment artifact.

The FX Transaction Intake Node publishes an FX Transaction Candidate through the FX Transaction Intake Endpoint for consumption by the FX Validation Node.