--- title: Verification MetaData description: Explains the PingOne Verify verification metaData data model and endpoint for retrieving scores from a verification transaction component: pingone-api-ea page_id: pingone-api-ea:verify:early-access/document-authentication-using-nfc-chip-verification/verification-metadata canonical_url: https://developer.pingidentity.com/pingone-api-ea/verify/early-access/document-authentication-using-nfc-chip-verification/verification-metadata.html llms_txt: https://developer.pingidentity.com/pingone-api-ea/llms.txt docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md revdate: 2026-09-16 section_ids: verify-all-verification-metadata-data-model: All verification metaData data model verify-specific-verification-metadata-data-model: Specific verification metaData data model verify-verification-metadata-data-model: Verification metaData data model verify-data-object-data-model: data object data model verify-data-object-for-type-document_authentication-and-provider-signicat: data object for DOCUMENT_AUTHENTICATION + SIGNICAT [EA] verify-signicat-verification-status-verdict: Verification Status Verdict verify-signicat-verification-status-reason-code: Verification Status Reason Code --- # Verification MetaData For each verification attempt, you can retrieve all scores in the transaction returned from verification services. The `metaData` endpoint, `/v1/environments/{{envID}}/users/{{userID}}/verifyTransactions/{{transactionID}}/metaData`, receives all requests for scores associated with the verification attempt and returned from verification services. ## All verification metaData data model When [all metaData](https://developer.pingidentity.com/pingone-api/verify/verification-metadata/read-all-verification-metadata.html) for a verification transaction are requested, the [verification metaData](#verify-verification-metadata-data-model) for each verification type of the most recent retry appears in a `metaData` array in the response. The verification metaData data model for each verification type of earlier retries appear in a `previousAttempts` array in the response. | Property | Type | Required | Mutable | Description | | ------------------ | --------- | -------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | | `_embedded` | Object | N/A | Read-only | Container for returned data. | | `metaData` | Object\[] | N/A | Read-only | Array of [verification metaData objects](#verify-verification-metadata-data-model) for each verification type for the most recent verification attempt. | | `previousAttempts` | Object\[] | N/A | Read-only | Array of [verification metaData objects](#verify-verification-metadata-data-model) for each verification type for unacceptable verification attempts. | | `size` | Integer | N/A | Read-only | The number of objects returned in `metaData`. | ## Specific verification metaData data model When [specific metaData](verification-metadata/read-one-verification-metadata.html) for a verification type within a verification transaction are requested, the [verification metaData data model](#verify-verification-metadata-data-model) appears as the response, regardless of which retry attempt it is. ### Verification metaData data model | Property | Type | Required | Mutable | Description | | --------------- | ------- | -------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------ | | `data` | Object | N/A | Read-only | Data model by provider and type as seen in the *Data model* column of [data object data model](#verify-data-object-data-model). | | `id` | String | N/A | Read-only | Identifier (UUID) of the transaction metaData. | | `provider` | String | N/A | Read-only | The provider of metaData in the object as seen in the *Provider* column of [data object data model](#verify-data-object-data-model). | | `retry.attempt` | Integer | N/A | Read-only | Number of the retry attempt when submitting images. | | `status` | String | N/A | Read-only | Status of the check. Can be `SUCCESS` or `FAIL`. | | `type` | String | N/A | Read-only | The type of metaData in the object as seen in the *Type* column of [data object data model](#verify-data-object-data-model). | ### data object data model The `data` object in verification metaData varies depending on the values of `type` and `provider` as seen in the table. | Type | Provider | Data model | | ------------------------ | -------- | ---------------------------------------------------------------------------------------- | | DOCUMENT\_AUTHENTICATION | SIGNICAT | [data model](#verify-data-object-for-type-document_authentication-and-provider-signicat) | #### data object for DOCUMENT\_AUTHENTICATION + SIGNICAT \[EA] Signicat provides document authentication using Near Field Communication (NFC), which securely reads the embedded chip in "smart" documents. | Property | Type | Required | Mutable | Description | | ---------------------------------- | ------- | -------- | --------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `sessionId` | String | N/A | Read-only | Provider's session identifier (UUID) for the verification. | | `success` | Boolean | N/A | Read-only | Whether or not the verification was successful. | | `finishingState` | String | N/A | Read-only | Final state of the verification. Can be `NOT_STARTED`, `BUSY`, or `DONE`. | | `activeAuthentication` | String | N/A | Read-only | Active authentication verdict. Refer to [Verification Status Verdict](#verify-signicat-verification-status-verdict) | | `activeAuthenticationReason` | String | N/A | Read-only | Reason for the active authentication verdict. Can be null. Refer to [Verification Status Reason Code](#verify-signicat-verification-status-reason-code). | | `countrySigner` | String | N/A | Read-only | Country signer verification verdict. Refer to [Verification Status Verdict](#verify-signicat-verification-status-verdict). | | `countrySignerReason` | String | N/A | Read-only | Reason for the country signer verification verdict. Can be null. Refer to [Verification Status Reason Code](#verify-signicat-verification-status-reason-code). | | `documentSigner` | String | N/A | Read-only | Document signer verification verdict. Refer to [Verification Status Verdict](#verify-signicat-verification-status-verdict). | | `documentSignerReason` | String | N/A | Read-only | Reason for the document signer verification verdict. Can be null. Refer to [Verification Status Reason Code](#verify-signicat-verification-status-reason-code). | | `extendedChipAuthentication` | String | N/A | Read-only | Extended chip authentication verdict. Refer to [Verification Status Verdict](#verify-signicat-verification-status-verdict). | | `extendedChipAuthenticationReason` | String | N/A | Read-only | Reason for the extended chip authentication verdict. Can be null. Refer to [Verification Status Reason Code](#verify-signicat-verification-status-reason-code). | | `hashTable` | String | N/A | Read-only | Hash table verification verdict. Refer to [Verification Status Verdict](#verify-signicat-verification-status-verdict). | | `hashTableReason` | String | N/A | Read-only | Reason for the hash table verification verdict. Can be null. Refer to [Verification Status Reason Code](#verify-signicat-verification-status-reason-code). | ##### Verification Status Verdict | Verdict | Description | | --------------------- | ------------------------------------------------------------------------------------ | | NOT\_PRESENT | Item is not present | | PRESENT\_FAILED | Item is present but failed verification, check the corresponding Reason for details. | | PRESENT\_NOT\_CHECKED | Item is present but was not checked for verification. | | PRESENT\_SUCCEEDED | Item is present and successfully verified. | | UNKNOWN | Item's verification status is unknown. | ##### Verification Status Reason Code | Reason Code | Description | | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | ALL\_HASHES\_MATCH | All hashes (that were computed of data-groups read) match (with hashes stored in the security object document). This is the successful case for hash table verification. | | CERTIFICATE\_EXPIRED | Certificate expired. | | COULD\_NOT\_BUILD\_CHAIN\_FAILURE | Could not build certificate chain. This is the abnormal failure case for country signer verification. | | FOUND\_A\_CHAIN\_SUCCEEDED | Found a certificate chain to a trust anchor. This is the successful case for country signer verification. | | HASH\_MISMATCH\_FAILURE | Hash mismatch failure. This is a failure case for hash table verification. | | NO\_CSCA\_TRUST\_ANCHORS\_FOUND\_FAILURE | No Country Signer Certificate Authority root certificates (trust anchors) were found. This is a failure case for country signer verification. | | NO\_VERIFIER | The verifier was not configured. | | NON\_MATCH\_ALERT | Non-matched verification. | | NOT\_SUPPORTED | The specific mechanism is not supported by the chip. | | PRESENCE\_DETECTED | The specific mechanism is present (supported by the chip). | | READ\_ERROR\_CONFIGURATION\_FAILURE | The reader or the verifier could not be configured correctly. | | READ\_ERROR\_SOD\_FAILURE | The verifier could not acquire or parse the chip's security object document. | | SIGNATURE\_CHECKED | The signature checked. This is the successful case for active authentication and document signer verification. | | SIGNATURE\_FAILURE | The signature failed. This is a failure case for active authentication and document signer verification. | | STORED\_HASH\_NOT\_FOUND | The stored hash could not be found. This is a failure case for hash table verification. | | SUCCEEDED | The verification succeeded. This is the general successful case for verification. | | UNEXPECTED\_EXCEPTION\_FAILURE | Reader or verifier encountered an unexpected exception. This is a general failure case for verification. | | UNKNOWN | Item's verification status is unknown. No further information could be determined. Default value. | | UNSUPPORTED\_DIGEST\_ALGORITHM\_FAILURE | The verification requires a digest algorithm not supported by the verifier. This is a failure case for hash table verification. | | UNSUPPORTED\_KEY\_TYPE\_FAILURE | Unsupported key type failure during verification. | | UNSUPPORTED\_DIGEST\_SIGNATURE\_FAILURE | The verification requires a signature algorithm not supported by the verifier. This is a failure case for active authentication and document signer verification. |