Hummand presents
Live presence and match are native. The rest is plugged through the same interface,
with an honest label and a record in the receipt.
hummand.presenca, hummand.match and passkey available; Serpro in accreditation;
the others with adapter and mock, in target architecture.
Sources · what every step queriesEvery policy step queries a source through the same interface: a request goes in, a summary with no personal data comes out; the sensitive part stays encrypted and the transient part is discarded. Every source has an adapter with a real contract and a mock with the personas of the acceptance scenarios; the real one enters when accreditation or the client arrives. The receipt records the source, the component and the version.A source is where each confirmation comes from: Hummand’s own presence check or an external service, like the civil database. A mock is a test version of a source, which answers like the real one without querying it.
hummand.presencaavailablehummand.matchavailableserpro.datavalidin accreditationserpro.cpfin accreditationgovbr.oidctarget architecturepasskeyavailabledispositivo.atestacaotarget architectureicp.brasiltarget architectureocr.documentotarget architecturecrctarget architecturesisobitarget architectureSources
Bureaus, fraud scores, device fingerprinting, PEP and sanctions lists, geolocation or behaviour
as proof, age estimation from a face: not sources. SMS is only the delivery channel for the link.
No real source enters before a client pulls it. Until then the adapter exists, has a contract and answers with the personas
of the acceptance scenarios; in production, a source that exists only as a mock responds as unavailable.
hummand.presenca · hummand.matchserpro.datavalidPaste the JSON and the public key. No account, nothing sent: it runs in your browser.
Open the verifier