Choose a KYC issuance path

DALP supports two current ways to produce compliance claims for KYC and AML workflows:

• manual claim issuance by a configured trusted issuer
• provider-driven intake through a Sumsub or Elliptic compliance-provider integration

Choose one path per claim topic and policy unless your operating model explicitly needs an override process. Issuing duplicate claims for the same subject and topic can make reviews harder and should be deliberate.

Use manual KYC claim issuance

Use Verify KYC via API when compliance staff or an internal back-office system reviews KYC evidence and then issues the claim.

This path fits when:

• the review happens inside your organisation
• your claim issuer is a staff-controlled or service-controlled issuer
• the KYC data is submitted and reviewed through DALP user/KYC flows
• provider evidence exists, but the final claim decision is made by your own compliance process

The issuer must be configured as a trusted issuer for the relevant claim topic. The API caller needs the claim-issuer role and wallet verification for the claim transaction.

Use provider intake with Sumsub

Use Onboard a compliance provider and Map compliance-provider subjects when Sumsub should produce identity verdicts for DALP identities.

This path fits when:

• Sumsub creates and reviews applicants
• Sumsub applicant-review webhooks should issue or revoke the configured claim topic
• Sumsub applicant-on-hold events should appear in the integration's monitoring history
• the provider integration EOA should be the on-chain claim issuer

Each Sumsub integration is bound to one claim topic. If one Sumsub programme covers multiple topics, create one integration per topic.

Use provider intake with Elliptic

Use provider intake when Elliptic should monitor wallets and produce AML alert history for DALP identities.

This path fits when:

• the subject is a wallet address already linked to a DALP identity
• Elliptic wallet alerts should be normalised to DALP severity scores
• severe alerts should revoke the configured claim topic when they meet the integration's revocation threshold
• the provider integration EOA should be the on-chain claim issuer

Elliptic integrations use wallet monitoring topics. The dapp exposes threshold tiers so operators can decide which alert severity level causes claim revocation.

Keep the paths distinct

Manual KYC issuance and provider-driven intake can coexist in one DALP environment, but they should not compete silently for the same claim topic.

Before enabling provider intake for a topic that is already issued manually, confirm:

• which issuer should be authoritative for the topic
• whether manual claims become overrides, fallbacks, or legacy evidence
• how rejected provider verdicts or high-severity alerts should affect existing claims
• which team owns provider dashboard configuration and webhook replay requests

See also

• Verify KYC via API
• Onboard a compliance provider
• Map compliance-provider subjects
• How compliance provider intake works