Verify
Who Sees It
Section titled “Who Sees It”Verify is offered to a member whose role may manage customers.
The page works through the desktop companion application, connected under Settings, in TCC Connection. The connection is per browser. Where it is missing, the page says Verifying from this portal goes through the desktop application on your computer. This browser is not connected to it yet. It links to Install the desktop application, and to Connect it in Settings for a role that may open Settings. Any other member reads A person with administrator rights connects it in Settings.
Where It Is
Section titled “Where It Is”Under Verification in the menu.
What It Is For
Section titled “What It Is For”Somebody on the telephone reads you three words. This page tells you whether those words belong to one of your organisation’s connections right now.
The three words change on a schedule, so a correct answer means the person held the code at that moment, not that they held it once.
Checking a Code
Section titled “Checking a Code”The page has three boxes, Word 1, Word 2 and Word 3, and the button Verify. Capitals do not matter, and pressing Enter in any box runs the check.
A match reads Identity confirmed with the name of the connection, and a summary line below it. No match reads No match found.
A wrong answer is not proof of fraud on its own. A word misheard, a code that has just rotated, or a person who is not one of your connections all read the same way. Ask for the current three words again before you conclude anything.
Where the Answer Comes From
Section titled “Where the Answer Comes From”The check runs against your own organisation’s connections, through the companion you configured. There is no central directory of everybody’s codes being searched, and nothing about the person is looked up anywhere else.
The API Tab
Section titled “The API Tab”The second tab, API Integration, is documentation rather than a control. It is there so the same check can run inside a system you already use, such as a helpdesk or a CRM.
It shows the address of the Verification Endpoint, the request that carries the three words, and the answer that comes back.
It also shows Webhook Authentication: a pattern where an incoming request carries the three words in a header, and your own server checks them against the same endpoint before it acts. That is how an automated caller proves who it is.
Nothing on this tab needs to be filled in. Copy what you need.
Related Pages
Section titled “Related Pages”To prove that a message came from your organisation rather than to check a person, use Seals.
To let a partner issue sealed codes on your behalf, see Business Partners.