Hummand presents

Sources

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 and hummand.match available; Serpro in accreditation;
the others with adapter and mock, in target architecture.

Sources · what every step queries

Native or plugged,
labelled.

Every 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.

Category
ProductSources

Sources

Out by choice

Bureaus, anti-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.

What we don't do

Mock with a real contract

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.

Where to start

Active challenge, live human, comparison with the client reference, same person; image and template discardedhummand.presenca · certified componenthummand.match · transientactive challengelivecomparisonsame personclient reference · hash in the receiptimage and template: discardedhummand.presenca · hummand.match

Live presence and match

Availablenative, in production
Traits
Question
is there a living human right now, and is it the same person as the reference?
Component
certified third-party liveness detection, declared in the receipt
Retention
zero: image and template discarded; the hash of the reference remains
Step
live presence with match, level 2
See the act
CPF and selfie go into the civil identity source, in accreditation; only the verdict persists, encrypted; the raw response never leavesserpro.datavalid · real and mock adapter · minimized responseCPF · selfieSerpro Datavalidin accreditationverdictpersists encryptedraw response: never leavesserpro.datavalid

Civil identity

In accreditationSerpro Datavalid, on their timeline
Traits
Question
who it is, against the government database (driver licence, national ID)?
Minimization
only the verdict persists, encrypted; the raw data never leaves
Situation
real and mock adapter ready; accreditation in progress
Step
civil identity, level 3
Talk to us
1.0

Verify a receipt

Paste the JSON and the public key. No account, nothing sent: it runs in your browser.

Open the verifier
2.0

Talk to us

A technical conversation, straight with the people who build it, no sales script.

Contact