> For the complete documentation index, see [llms.txt](https://docs.complycube.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.complycube.com/documentation/integration-resources/integration-checklist.md). # Integration Checklist Use this checklist to launch your KYC, AML, and identity verification integration from Sandbox to Live. ### Overview When you’ve finished development and testing, use this checklist to confirm your integration is production-ready. ### Setup * [ ] [Activate your account](https://portal.complycube.com/activate) in the Web Portal and obtain your **Live** API key. * [ ] Use our [testing data](/documentation/integration-resources/testing-data.md) to simulate scenarios for all services you plan to use. Ensure your integration handles both success and error responses correctly. * [ ] Ensure your integration is configured to use the correct environment by supplying the appropriate [API key](https://portal.complycube.com/developers/key). ### Validation * [ ] If you have integrated our native [Mobile SDKs](/documentation/sdks/master.md), install and test the ComplyCube [iOS and Android mobile apps](/documentation/integration-resources/complycube-mobile-app.md) to validate your workflows. * [ ] Handle `4xx` and `5xx` errors gracefully: validate inputs, retry transient errors, and provide helpful user feedback. * [ ] Respect [rate limits](https://docs.complycube.com/api-reference/rate-limits) and [service quotas](https://docs.complycube.com/api-reference/service-quota) to avoid throttling or service denials in production. ### Webhooks * [ ] Configure [webhook](https://portal.complycube.com/developers/webhooks) endpoints in the Live environment (note that Sandbox and Live webhooks are separate). * [ ] Ensure your endpoint [verifies authenticity](/documentation/integration-resources/webhooks.md#signature-verification), handles retries or missed deliveries, and is idempotent (safe to process the same event more than once). ### Monitoring and security * [ ] If using **continuous monitoring** (e.g. AML Screening Checks), ensure it is **enabled** only for active clients and **disabled** when no longer needed. * [ ] Subscribe to our [status page](https://status.complycube.com) so your team is notified of any service disruptions or planned maintenance. * [ ] If you use our SDKs, subscribe to [ComplyCube on GitHub](https://github.com/complycube) to stay informed about SDK updates and notifications. * [ ] Store API keys securely, [rotate](https://portal.complycube.com/developers/key) them regularly, and never expose them in client-side code. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.complycube.com/documentation/integration-resources/integration-checklist.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.