Devices

How SDK instances register as devices, and how to manage them from the dashboard.

Every running SDK instance registers itself as a device against the Validation Gateway. The SDK identifies each device automatically, so you don’t manage device identifiers yourself.

Registration

A device must be registered once before it can open a session and validate. The SDK does this for you:

Kotlin

mbkyc.registerDevice("lobby-kiosk").getOrThrow()

Swift

try await mbkyc.registerDevice(name: "lobby-kiosk")

C#

await mbkyc.RegisterDeviceAsync("lobby-kiosk");

TypeScript

await client.registerDevice('lobby-kiosk');

Registration is authenticated with a JWT (key_id in the payload). The backend stores the device against your organization. You can check status at any time:

val status = mbkyc.checkRegistration().getOrThrow()
// active | inactive | not_found

What happens on the wire

The meta block carries OS, OS version, and app version so you can identify devices in the dashboard.

Managing devices from the portal

In Operations → Devices you can see and manage every device registered to your organization:

Action	Effect
View	See all registered devices, with name, OS metadata, status, and last activity.
Register	Devices register themselves on first run via registerDevice(); they then appear here.
Status	active devices can validate; an inactive device is rejected at handshake.

A device that is inactive or never registered cannot complete the handshake, so validate calls will fail. If you see registration errors, confirm the device shows as active in the portal.