Skip to main content
Use this checklist to verify your application’s integration with AMLOK before enabling Live traffic. Run the business and consumer journeys in Sandbox and confirm that your application handles successful results, recovery paths and permission errors.

​
Evidence to retain

Record the environment, contract SHA-256/revision, operational profile ID/version, test scenario, request IDs, resource IDs and observed results. Retain redacted assertions and counts; do not store API keys, provider credentials, full identity files or signed capability URLs in test logs.

​
Client recovery exercise

Run the example to completion, interrupt it after command acceptance, and resume it with the same state. Independently reconcile its package, evidence, monitor, deal snapshot and billing entries. Verify both a business and a consumer fixture; applicability and missing values must remain explicit rather than forcing a business metric into consumer underwriting. Use two distinct Sandbox workspaces to test isolation. Check that your application selects the intended environment and never reuses Sandbox IDs or test controls in Live. Use separate Owner, Dev and Analyst users for console permission checks, and independently scoped API keys for programmatic checks. UI visibility never substitutes for server authorization.