Credential issuance

Paradym creates and issues verifiable credentials to holders. A Beam agent receives an issuance request, reads the subject data an application supplies, and applies your rule about who qualifies for which credential. Where the data and policy line up, the agent issues the credential through the connector and records that it was granted. Requests with incomplete data, unusual claims, or elevated privileges are routed to a person to approve before issuance. Routine, in-policy credentials are handled automatically, so teams avoid preparing each one by hand while keeping oversight of the exceptions.

Credential status revocation

Paradym maintains the status of credentials it has issued. A Beam agent reads status change requests and events, applies your rule for when a credential should be suspended or revoked, and updates the credential's state accordingly. Standard cases, like an expired term or a completed offboarding, are handled and recorded automatically. Requests to revoke high-trust credentials, or changes that look inconsistent with the holder's record, are routed to a person to confirm first. This keeps credential status accurate without staff manually managing each holder's standing across the directory.

Presentation request handling

Paradym checks proofs that holders present to support a claim. A Beam agent receives a presentation, reads the proof and the requested attributes, and applies your rule for what constitutes a valid match. Valid presentations are accepted and the outcome is recorded against the interaction, while invalid or expired ones are declined per policy. Presentations that are partially valid, unusual, or tied to sensitive access are routed to a person to judge before access is granted. The agent clears routine, clearly valid proofs on its own and leaves the borderline cases to human review.