Verify a PRAMAAN badge
Badge verification should check signature where implemented, expiry, key ID, revocation/status, and consent/share context. Online status may be required for revocation and current-state checks.
Try sample badge input only.
Do not paste private worker data. Use sample badge IDs or QR test values.
Signature is one part of trust.
- 1
Decode badge
Read sample payload and key ID.
- 2
Canonicalize payload
Use stable ordering before signature verification.
- 3
Verify signature
Use Ed25519 wording only where implemented for the badge type.
- 4
Check expiry/revocation
Online status may be required for revocation and current state.
- 5
Show result
Valid, expired, revoked, unknown key, tampered, or network unavailable.
{
"badge_id": "bdg_sample_001",
"subject": { "display_name": "Sandbox Worker" },
"status": "current",
"expires_at": "2027-05-25T00:00:00Z",
"key_id": "sample_public_key_2026_01",
"visibility": ["status", "validity", "role_signal"]
}Can this verify offline?
Only signature checks can be offline where public-key verification is implemented. Revocation, current status, and consent/share context may require online checks.
Does the public badge expose raw documents?
No public badge sample should expose raw Aadhaar, PAN, OTPs, private documents, or unnecessary PII.