A published vocabulary for the moment a check stops.
When a check cannot go further, the product records a code from a published dictionary — not a sentence. A sentence looks like an explanation and is not one: you cannot group by it, count it, translate it, or show three years later that the check stopped for the reason recorded rather than one written afterwards. The sentence still gets written; it travels beside the code, not instead of it.
This is what makes a documented outcome different from a blank. A blank says nobody looked. A documented outcome names the source that was asked, the code for why it cannot answer, and the substitute the jurisdiction accepts instead.
7 categories · 24 codes · 6 classes of absenceTwo levels: exactly one category, one or more reasons.
A stop carries exactly one category — where the check ran out of road — and one or more reasons under it. Exactly one, because a record with two categories has no honest answer to the only question worth asking about a stop: what would resolve it. “The register is closed” and “the client did not consent” are two limits, each with its own attempts and its own way out, and merging them loses both.
Every reason also names the class of absence it stands for, and that class decides which actions exist at all. Where we did not reach the data, connecting a source or asking again are real options. Where nobody ever collected it, they are not options and never will be — what remains is the substitute the jurisdiction accepts, or a risk accepted over a named signature. A system that codes both as one word offers the wrong action, confidently.
Some of the categories are marked borrowed. The shape of the record — exactly one category above one or more reasons — follows the GLEIF Reporting Exceptions Format, in force under the policy of the supervisory body of the global LEI system. That is a statement about compatibility of shape. The values are ours, and no data comes from there.
This edition, and the terms it is published under.
Edition
Evix Stop Reason Dictionary · v0.3.0A code means what the edition that defined it says it means. A dossier issued three years ago cites the edition in force that day, so the reference keeps codes that are no longer offered for selection: a reference a code has vanished from makes the record that cites it unreadable.
Licence
CC-BY-4.0The dictionary — the codes, their structure and their definitions — is published under CC-BY-4.0. Use it in your own product, and credit Evix Lab. Nothing else in the product is licensed by that.
How to cite
Cite the permanent address together with the version number. Both are on this page because both are read from the dictionary itself when this page is built — there is no second copy here to fall out of step.
Evix Stop Reason Dictionary v0.3.0 · Evix Lab · https://api.evixlab.com/reference/stop-reasons · CC-BY-4.0Where the codes are.
The list of codes lives in exactly one place, and this is not it. Read it as JSON, or as the rendered reference — every code with its definition, its class of absence, and the actions that class allows.
The JSON answers without an account, and so does the reference. Whoever received a dossier with a code in it can read what that code means without asking us for access.