✅ Opt-In

🧾 Description

The Opt-In step allows the user to approve or deny Ditto ID's request to store their identity data (particularly the captured selfie) in the system for future authentication purposes.

This is the final step of the identity verification process on IdvWebServer.

👤 User Interaction

After successful document verification and selfie capture, the user is shown an Opt-In prompt with two options:

• ✅ Approve: Consent to store biometric (selfie) data in Ditto ID system
• ❌ Deny: Decline storage; the data will not be saved

The decision is collected via a UI prompt with APPROVE and DENY buttons.

💾 If User Approves

• The user's selfie is stored in Ditto ID's secure database.
• The user is considered identity verified and onboarded.
• Ditto ID marks the verification session as successful.
• User is redirected back to the enterprise portal using the redirectUrl provided during IDV Web Token generation.

🚫 If User Denies

• Selfie and other session data are discarded.
• User is redirected to the enterprise portal.
• Enterprise app can show a message such as:

  "User declined identity verification. Please try again later."

🔐 Security Considerations

• This step provides explicit user consent for data usage and storage.
• Aligns with data privacy regulations like GDPR, ensuring biometric data is not stored without consent.

🔁 Redirect

The user is redirected back to the redirectUrl provided in the original IDVWebToken request. From there, the enterprise app can:

1. ✅ Use Verify IDVWebToken API to fetch verification result
2. 🔄 Update user status using the Update Status of User API

🔗 Related APIs (Post Opt-In)

🔍 Verify IDVWebToken

GET https://<GM-API-SERVER-IP>:9442/v1/idvWebTokens/{web_session_id}

Returns final verification status and KYC reference (if enabled).

🔄 Update Status of User

PUT https://<GM-API-SERVER-IP>:9442/v1/users/{userId}/status

Body:

{
  "status": "CREATED"
}

Used to mark the user as fully enrolled after successful IDV flow.

🧩 Final Step

After Opt-In, the user is redirected to the enterprise app, which can proceed with login, access enablement, or further onboarding.