Verifying Credentials

​

Verification Flow

1. Start verification — the verifier starts a session with a programId. The program defines what to check and how.
2. Consent + discovery — the SDK requests the holder’s consent and loads the matching encrypted credential from DStorage.
3. Proof generation — the holder decrypts the credential and generates a signature-based proof, including a zero-knowledge proof where the program requires one, disclosing only the requested claims.
4. Verification — the proof is checked against the program’s settings off-chain by default, or recorded on-chain through the Universal Verifier when the program requires it.
5. Result — on success the SDK returns a W3C Verifiable Presentation containing the disclosed claims and proof material.

​

Verifier integration checklist

1. Create or select a Verification Program in the Developer Dashboard (Verifier → Program).
2. Configure the program:
   • Accepted proof type (BJJ_SIG_2021)
   • Requested claims and whether selective disclosure is required
   • Whether ZKP is required
   • Off-chain vs on-chain verification
   • The Issuer’s DID to constrain trusted issuers (optional)
3. Publish the program and take note of the programId.
4. Integrate the AIR Verifier SDK.
5. Start verification with the programId.
6. Handle outcomes: Compliant, Non-compliant, No matching credential, User declined consent, or proof/verification failure.
7. On success, consume the returned Verifiable Presentation.

​

Start verification

public async verifyCredential({
    authToken,
    programId,
    redirectUrl,
    fieldsToDisclose,
  }: {
    authToken: string;
    programId: string;
    redirectUrl?: string;
    fieldsToDisclose?: "*" | string[];
  }): Promise<CredentialVerificationResult>

type CredentialVerificationResult = {
  status: "Compliant";
  zkProofs: Record<string, string>;
  transactionHash: string;
  disclosedData: {
    credentialSubject: IssuedCredential;
    credentialType: string;
    issuerDid: string;
    issuanceDate: string;
    expirationDate: string;
    proof: CredentialProof[];
  };
};

Future<CredentialVerificationResult> verifyCredential({
  required String authToken,
  required String programId,
  String? redirectUrl,
});

​

Compliance encryption private key

​

Recommended verification modes