eFTI Gates and authority access: what software vendors need to understand

The eFTI Gate is the public-side exchange boundary

Implementing Regulation (EU) 2024/1942 defines eFTI Gates as ICT components that mediate the exchange between competent-authority systems and eFTI platforms.

The Gate routes authorised access requests to the relevant platform and carries responses and follow-up communication back toward the authority.

Platforms do not expose ordinary user APIs to authorities

The 2025 eFTI platform requirements specify machine-to-machine access over secure connections between the eFTI platform and an eFTI Gate. A platform must establish such a connection with at least one Gate.

That is a different trust and transport boundary from the APIs used by shippers, carriers or TMS users.

The Gate network reduces connection complexity

The regulatory architecture is designed so a platform does not need a separate bespoke connection to every authority in every Member State. Gates connect through the broader exchange environment and mediate authority access.

For product architecture, that means the platform-facing Gate connector can remain a specialised component with clear authentication, message and audit responsibilities.

Secure message exchange has its own technical requirements

The authority-access rules define secure and authenticated communication, security certificates and eDelivery-based message exchange between relevant components. These are not details that should be duplicated in ordinary TMS business logic.

A readiness architecture can therefore isolate the Gate-facing transport component and keep shipment preparation, customer workflow and authority exchange as separate concerns.

• Authority request validation.
• Secure Gate authentication.
• Routing to the correct eFTI data set.
• Response and follow-up communication.
• Operational logs and access events.
• Separation from customer-facing API credentials.