Integration · SDK
Everything else on this site is infrastructure. This is the bit a nervous person uses once, at the moment they are deciding whether to finish registering — so it is where abandonment is won or lost.
What it does
Capture
Document detection with live framing guidance, then a short liveness sequence. Where a camera is unavailable or refused, it falls back to upload rather than dead-ending the registration.
Gate
The gate runs on the handset. A frame that would fail the check is refused while the document is still in the player's hand.
Hand over
The SDK holds a short-lived step token scoped to one check. An intercepted token is worth one check that has already been opened, for fifteen minutes.
Platforms
No framework assumption; mounts into an element you provide.
Camera and file-upload paths, no third-party analytics inside the SDK.
Same two paths, same absence of analytics.
Player-facing strings, including European rather than Brazilian Portuguese.
Colour, radius and type are yours; the layout stays ours because it is the part that was tested against abandonment.
The capture flow is operable without a pointer and does not animate for a player who asked it not to.