Verify Broker

The same question from the other side of the load.

Is this broker authorised to tender this freight, is the bond real, and is the payment instruction the one they actually gave you?

Request access

One party model, not a second product. A company can be a carrier and a broker at once, and each role is evaluated independently on the same legal entity. One revoked broker authority leaves the carrier side untouched.

Broker authority and bond

Granted status, pending application and pending revocation as separate facts, plus the surety on file. A pending revocation is flagged REVIEW, not BLOCK — it has not happened yet.

Payment instruction integrity

Destinations are compared by a stable protected identity, not by the last four digits. Two different accounts can mask identically; that must still read as a change, and it does.

Who may tender

Association with the company and authority for the class of operation are confirmed separately. A self-asserted job title is not evidence of either.

The payment-change case, specifically

It is the most expensive thing on this page, so it gets the strictest handling.

Situation	What we do
New destination appears	New pending version. The previously confirmed one does not vouch for it.
Two accounts, same last four digits	Reported as a change — comparison is on protected identity, not the mask.
Confirmation arrives for an older version	It does not approve the newer one. Version N+1 stays pending.
Callback reaches a number found on the invoice	Not independent. We need a channel with a different root.
Approval given	Bound to instruction version, party and that specific load, valid at most 24 hours.

Planned R1 Payment-change verification with compliance review before any sensitive instruction is accepted.