Signa ID overview
Accept a reusable Signa ID verification, ask a person for verified data, and check if a wallet is verified.
Signa ID is a reusable verified identity. A person verifies with Blaaiz one time and keeps the result in their Signa ID. The person can then share that verification with other businesses, and does not upload the documents again.
The person owns the Signa ID. Blaaiz shares nothing with your business until the person approves it.
Each use of Signa ID must be enabled for your business. Contact your account manager to request access.
How your business can use Signa ID
| Use | What happens | Access |
|---|---|---|
| Use Signa ID on a verification page | In a HOSTED Signa session, the person shares their Signa ID instead of new documents. The session completes as usual, and you get the same webhook. | Signa, with the Use Signa ID option turned on for your business. |
| Request data with Signa ID | Your page asks the person for verified data. The person approves in a popup, and your server gets the data. | Signa ID data release, and the signa-id:release scope. |
| Wallet status | Your page checks if a wallet belongs to a verified Signa ID. The answer holds no personal data. | No access needed. The endpoint is public. |
How a person gets a Signa ID
A person can create a Signa ID in two ways:
- On the Signa ID site,
https://id.blaaiz.com. The person signs in with an email code or a passkey, then verifies. - On a Signa verification page that Blaaiz hosts. The page can show the option Save my verified identity to Signa ID so I can reuse it. See Signa ID on the verification page.
What the person controls
- Before each share, the person sees your business name and the data that you ask for. For a data release, the person also sees the reason that you give.
- Each share needs a new selfie. Blaaiz checks that a live person is present and that the face matches the verified identity.
- The person can stop your access to the shared data at any time. Blaaiz can also stop it.
- You get only the data that the person approved.
What your business gets
Use Signa ID on a verification page completes a normal Signa session. The session result and the merchant.kyc.session.completed webhook have the same shape as for any other session. Read the details with the session data endpoints.
A data release gives you a release record and the approved data blocks. Your access to the data lasts 30 days from the release. When the person or Blaaiz stops your access earlier, Blaaiz sends the signa_id.grant.revoked webhook to your kyc_url. See Signa webhooks.
The wallet status gives only the facts that the on-chain attestation already makes public: the verification level, the country, and the expiry.
Next steps
GETGet a session document URL
Get a short-lived download URL for one image of a verification session. The URL is valid for 15 minutes. Download the image at once, and do not store or share the URL. An image that Blaaiz no longer keeps answers 410. This endpoint allows 30 requests each minute and 600 requests each hour for each business, together with the Signa ID release document endpoint. The session must be APPROVED or REJECTED: any other status answers 409. The response carries `Cache-Control: no-store`. Signa must be enabled for your business. Required scope: `compliance-kyc:pii:read`. No scope bundle contains this scope, `full-access` included, so select it by name when you create or rotate your credentials.
Request data with Signa ID
Next Page