Skip to main content
Didit’s integration prompt walks a coding agent through adding Identity verification, Business verification, Transaction monitoring, Authentication, or any combination, to an existing application. The agent inspects your code first, proposes only the products that help, and stays in sandbox until you confirm production.
Authentication is new. Its hosted flow, ES256 JWT issuer, auth events and bot protection are documented; its SDKs are published for JavaScript, React, Next.js, iOS, Android, Flutter and React Native. The prompt requires the agent to check the platform’s quickstart, keep adapters for unavailable packages disabled, and never invent a working SDK or claim that an unavailable integration passed.

Use the prompt

  1. Click Copy and paste the prompt into your coding agent, in the repository of your application.
  2. Answer the questions the agent asks once: countries, data region, review policy, team and live tests.
  3. Confirm the stable person reference it proposes for vendor_data. Your backend derives it from the authenticated user.
  4. Review the generated implementation and its test results before enabling it for customers. Going live needs your explicit confirmation and a cost cap.
The prompt is generated from one source and names its version and hash under Page context, so you can tell which version you copied. It links the pricing page instead of copying prices.

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

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 by event_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.
Last modified on November 16, 2026