Built, readiness-checked, and not switched on.
The channel that would carry finished customs filings from Lanexa to CBSA and CBP electronically. Built and readiness-checked, with credentials and carrier code stored.
This is the connection that would carry a finished customs filing from Lanexa to CBSA and CBP electronically. The client is written, the credentials and carrier code have a home in settings, and the readiness check runs. What has not happened is switching it on with a live account.
So today Lanexa prepares, validates, barcodes and packages the filing end to end — and then the finished filing travels the way it does now, through your customs broker or the portal. Nothing about that is hidden in a footnote elsewhere on this site; it is stated on the border pages too.
It is worth being clear about why this matters more than most integrations. Everything else Lanexa connects to degrades gracefully: if the weather service is unavailable you lose an advisory. Once filings run through this connection, an outage would stop cross-border loads from proceeding — which is exactly why it gets switched on deliberately rather than quietly.
Your broker still files
The filing is assembled for you; the transmission is not ours yet.
Credentials have a home
API key and SCAC are held in settings, ready for the day it goes live.
You will hear about it
When this switches on it becomes a changelog entry and this page changes state.
Where it stops.
It is not switched on. No filing is transmitted through it today — finished filings still travel via your broker or portal.