Use the prompt
- Click Copy and paste the prompt into your coding agent, in the repository of your application.
- Answer the questions the agent asks once: countries, data region, review policy, team and live tests.
- Confirm the stable person reference it proposes for
vendor_data. Your backend derives it from the authenticated user. - Review the generated implementation and its test results before enabling it for customers. Going live needs your explicit confirmation and a cost cap.
Pick your product combination
The same prompt works for a fintech, gaming, crypto or marketplace app. Tell the agent which actions you want to protect. A successful login does not mean an identity check passed or a payment can proceed.
Choose the SDK by product
- Identity verification
- Transaction monitoring
- Authentication
Use
@didit-protocol/sdk-web on web, or the native and wrapper SDKs on mobile. Your server creates a session; your app receives only its scoped URL or token. Read the JavaScript SDK guide.Protect credentials and decisions
Keep API keys and console management credentials on your backend. Browser and native apps receive only product-scoped session credentials or short-lived tokens. An Authentication publishable key is not an API key. Verify webhook signatures before applying updates, deduplicate deliveries byevent_id, and keep the statuses for each product separate. Do not treat a redirect, SDK callback or rendered success screen as server authorization. Report any unavailable dependency and unverified live flow explicitly.