Technical notes, implementation guides and architecture decisions based on the systems we are actively researching and building.
EUDI integration is more than adding a wallet button. Relying parties need a controlled flow for registration, requested attributes, verifier logic, policy, auditability and tenant-specific configuration.
Read guide →The eFTI Regulation applies in full from 9 July 2027. Software vendors can use the remaining implementation window to isolate eFTI logic, map datasets and prepare a stable integration boundary.
Read guide →A custom portal becomes useful when the same information is copied between people, status is unclear and recurring work depends on manual reminders or one person's spreadsheet.
Read guide →When catalogue, stock, orders and fulfilment are managed in separate systems, every integration becomes a reconciliation problem. A shared operational core can remove that duplication.
Read guide →OpenID4VP belongs in a dedicated verifier boundary with transaction state, request creation, wallet-facing endpoints and response validation. The business product should consume a smaller, stable result contract.
Read guide →The relying-party registration model is becoming structured machine-readable configuration, not just a company record. Product architecture should be able to represent services, intended uses and requested credential data explicitly.
Read guide →Registration certificates are becoming part of the live wallet interaction. Wallets validate them and compare requested data with registered scope, so relying-party software should make the same checks before sending the request.
Read guide →The decision is not simply code ownership versus a subscription. It is about who maintains protocol change, relying-party configuration, certificate lifecycle, validation logic and production operations.
Read guide →Treat eFTI as a versioned projection of transport data. Keep a stable internal shipment model and translate only the regulatory subsets required by the eFTI exchange.
Read guide →Competent-authority access is mediated through eFTI Gates and secure machine-to-machine communication. That boundary should remain distinct from ordinary customer APIs and user-facing transport workflows.
Read guide →