1. Give the Knot team a heads up regarding your launch timeline.
  2. Request production access and retrieve your production client_id and secret from your Knot Dashboard. Ensure your production keys are used and secured - never saved in source control or client-accessible.
  3. Save your client_id and secret in your application server and create a new session each time you initialize the SDK.
  4. If implementing the web JS SDK, allowlist your domain for production in your Knot Dashboard.
  5. Handle all related webhooks for the product(s) you are integrating, as well as the MERCHANT_STATUS_UPDATE event if you display merchants natively in your app.
  6. Listen to client-side callbacks to monitor various events related to the user’s lifecycle through the Knot SDK, including the refresh session request event to know when to call Extend Session if the user is still in the SDK.
  7. Ensure you provide a value in the entry_point parameter when initializing the SDK. This value is provided back in webhooks to help you track the conversion of users through the flow.
  8. Remove any user_good or similar development environment test login credentials to prepare for production.