didit-sdk-integration
Installation
SKILL.md
Didit SDK Integration (Web, iOS, Android, React Native, Flutter)
Overview
Choose Identity verification, Transaction monitoring, Authentication, or any combination. For verification and monitoring, your backend uses the API key to create what the client needs; the client receives a credential for that purpose. End-user Authentication uses its own session credentials and requires an enabled application. Start with the three-product prompt.
| Product | Backend preparation | Client receives | Client integration |
|---|---|---|---|
| Verification sessions | POST /v3/session/ |
url (web) or session_token (iOS, Android, React Native, Flutter) |
startVerification |
| Transactions | POST /v3/transactions/sdk-token/ |
sdk_token |
submitTransaction, plus getTransaction on mobile |
| Events | POST /v3/events/sdk-token/ |
monitoring_token |
None: plain HTTPS to POST /v1/events/ |
| End-user Authentication (early access) | Confirm the enabled application's Authentication runtime | End-user access/refresh tokens | Hosted PKCE flow; dedicated SDKs are release-dependent |
Rules:
- Never put the API key in a browser, app or WebView. It stays on your backend.
- SDK results are UX hints. Grant access only after your backend confirms the outcome with a webhook or
GET /v3/session/{session_id}/decision/(sessions) orGET /v3/transactions/{uuid}/(transactions). - Colors, logo and intro screens come from the console White Label settings, not from SDK options.
Verification/transaction versions documented here: Web SDK 0.4.0, iOS 4.9.1, Android 4.9.1, React Native 4.9.1, Flutter 4.9.1. These versions do not establish availability of Authentication or @didit-protocol/signals.