| Both sides previous revision Previous revision Next revision | Previous revision |
| dido:99_annexes:annex-b-terms-and-definitions:f:fx_transaction_intake_endpoint [2026/07/11 11:15] – ↷ Links adapted because of a move operation nick_dido | dido:99_annexes:annex-b-terms-and-definitions:f:fx_transaction_intake_endpoint [2026/08/04 07:09] (current) – ↷ Links adapted because of a move operation nick_dido |
|---|
| The endpoint supports transaction intake, validation, semantic interpretation, audit, provenance, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|evidence]] expectations. It carries FX Transaction Candidate information or related intake messages governed by the FX Transaction Candidate information structure. | The endpoint supports transaction intake, validation, semantic interpretation, audit, provenance, and [[dido:99_annexes:annex-b-terms-and-definitions:e:evidence|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 [[dido:99_annexes:annex-b-terms-and-definitions:d:data_plane|Data Plane]]. It also relates to the FX Logical [[dido:99_annexes:annex-b-terms-and-definitions:a:audit_and_provenance_plane|Audit and Provenance Plane]] because intake information requires [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] to the receipt context, resulting in expectations for [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Node]], timestamp, and evidence. | The FX Transaction Intake Endpoint participates primarily in the FX Logical [[dido:99_annexes:annex-b-terms-and-definitions:d:data_plane|Data Plane]]. It also relates to the FX Logical [[dido:99_annexes:annex-b-terms-and-definitions:a:audit_and_provenance_plane|Audit and Provenance Plane]] because intake information requires [[dido:99_annexes:annex-b-terms-and-definitions:t:traceability|traceability]] to the receipt context, resulting in expectations for [[dido:99_annexes:annex-b-terms-and-definitions:f:financial_node|Node]], timestamp, and evidence. |
| |
| ===== Definition ===== | ===== Definition ===== |
| ===== Source ===== | ===== Source ===== |
| |
| Specialisation of Logical Communication Endpoint from [[fxdemo:02-part:start]], Section 7.2, and [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] from [[fxdemo:01-part:start]], Section 7.6; generalised from transaction intake and topic material in the original FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]]. | Specialization of Logical Communication Endpoint from [[fxdemo:02-part:start]], Section 7.2, and [[dido:99_annexes:annex-b-terms-and-definitions:c:communication_endpoint|Communication Endpoint]] from [[fxdemo:01-part:start]], Section 7.6; generalised from transaction intake and topic material in the original FX Demo [[dido:99_annexes:annex-b-terms-and-definitions:r:reference_architecture|Reference Architecture]]. |
| |
| ===== Note ===== | ===== Note ===== |
| |
| The FX Transaction Intake Endpoint is not a DDS Topic, REST resource, RPC method, message queue, event stream, file, database table, or deployment artefact. | The FX Transaction Intake Endpoint is not a DDS Topic, REST resource, RPC method, message queue, event stream, file, database table, or deployment artifact. |
| |
| ===== Example ===== | ===== Example ===== |