# Identity verification

Source: https://docs.settlemint.com/docs/operators/compliance/identity-verification
Configure the DALP identity-verification compliance module so an asset requires a verified-identity claim from a trusted issuer before holders may transact.



The identity-verification compliance module requires every involved identity in a regulated operation to carry a valid verification claim signed by a trusted issuer. The module is the platform's primary holder-eligibility gate for regulated assets where holders must complete KYC, accreditation, or another verification process before transacting.

For the architecture reference, see [Identity verification](/docs/compliance-security/security/compliance/identity-verification).

## Prerequisites [#prerequisites]

* The asset already exists (configure during creation) or you have the Asset administrator role on the deployed asset.
* One or more trusted issuers are configured on the platform to sign verification claims. See [Configure trusted issuers](/docs/operators/compliance/configure-trusted-issuers).
* The verification topic ID matches the claim shape your operating model uses (standard KYC, accreditation, qualified-investor, etc.).
* Every prospective holder has a registered OnchainID that will receive the verification claim.

## Configure during asset creation [#configure-during-asset-creation]

In the Asset Designer compliance step, pick the identity-verification module. Configure:

* The trusted-issuer addresses that may sign claims for this asset.
* The verification topic ID the module checks against.

The Asset Designer pre-selects sensible defaults from your platform's trusted-issuer configuration. Override only when the asset needs a non-default issuer or topic.

## Configure on an existing asset [#configure-on-an-existing-asset]

From the asset detail workspace, open the compliance tab and add or update the identity-verification module configuration. Changes apply forward; holders already verified under the old configuration keep their verified status until their claim expires.

## Operate verification claims [#operate-verification-claims]

Verification claims live on the holder's OnchainID, not on the asset. Verification operations run through:

* [Verify KYC](/docs/operators/compliance/verify-kyc) for the operator-managed claim issuance flow.
* [Manage KYC data](/docs/operators/compliance/manage-kyc-data) for refreshing, revoking, or inspecting existing claims.

When a claim expires or is revoked, the holder cannot transact under any asset that requires the verification topic until a new claim lands.

## Operating considerations [#operating-considerations]

* The module accepts any claim signed by a configured trusted issuer for the configured topic. To narrow further, use the identity allow-list alongside the verification module.
* Claim expiry is enforced at evaluation time. Plan re-verification cycles to match the claim TTL your issuer uses.
* The module does not check the holder's wallet itself, only the OnchainID. The wallet must be registered to the OnchainID through the identity registry.

## What stays external [#what-stays-external]

The KYC, accreditation, or other verification process the trusted issuer runs before signing a claim stays with the issuer. DALP records the resulting claim; it does not perform the verification.

## Troubleshooting [#troubleshooting]

| What you see                                 | What to check                                                                                            |
| -------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| Holder cannot transact despite a valid claim | Confirm the claim was signed by a trusted issuer the module accepts and that the topic ID matches.       |
| Claim expired in the middle of an operation  | Reissue the claim through [Verify KYC](/docs/operators/compliance/verify-kyc) and have the holder retry. |
| Multiple trusted issuers needed              | Add each issuer to the module configuration. The module accepts a claim signed by any configured issuer. |

## Read next [#read-next]

* [Compliance overview](/docs/operators/compliance/overview)
* [Configure trusted issuers](/docs/operators/compliance/configure-trusted-issuers)
* [Verify KYC](/docs/operators/compliance/verify-kyc)
* [Identity verification architecture](/docs/compliance-security/security/compliance/identity-verification)