Overview

Use this checklist before launching Begini in a live environment. Work through each section and confirm everything is in place before switching to Production credentials.

Integration

• Assessment sessions can be created successfully (API) or links generated correctly (no-code)
• Integration ID and API key confirmed for the Production environment
• Unique IDs are being assigned correctly — unique per user, no PII, 5–60 alphanumeric characters
• Your system can map UIDs back to internal customer or application records

Assessment flow

• Full end-to-end assessment completed successfully on a real device
• Assessment loads correctly on target device types and browsers
• Completion, cancellation, and expiry redirect URLs configured in the Production tab of the Deployment Centre
• User instructions are clear and the journey feels smooth

Results

• Completed assessments appear in Beacon under the correct deployment
• Risk score, trust score, and trait indicators are visible and understood
• Your team knows how results will be reviewed and used in decisioning
• Export functionality tested if results will be pulled via Beacon

Webhooks (if applicable)

• Production webhook endpoint configured in Beacon → Deployment Centre → Production tab
• Webhook endpoint is publicly accessible over HTTPS
• HMAC signature verification implemented and tested — see Securing Webhooks (HMAC)
• Test API (POST /v1/webhooks-management/test) returns 200 against Production endpoint
• All relevant event types handled correctly (psychometric_score.complete, application.expired, etc.)
• Duplicate event handling in place

Security

• Production API key stored server-side in an environment variable or secret manager — not in code
• API key not present in any frontend code or source control
• Test and Production environments clearly separated — separate keys, endpoints, redirect URLs
• Beacon access restricted to appropriate users only

Branding (if applicable)

• Logo uploaded in the Production deployment (500×120px PNG, transparent background)
• Primary and secondary colours configured in the Production deployment

Operations

• Relevant team members have Beacon access
• Someone owns ongoing monitoring of results and completion rates
• Process defined for handling low-trust sessions
• Basic escalation path in place if issues arise post-launch

Final check

Before switching your integration to Production credentials, run one complete test session end-to-end using Production settings — session creation, assessment completion, result receipt — and confirm everything behaves as expected.

Next steps

• Creating a Session — API session creation reference
• Securing Webhooks (HMAC) — implement webhook signature verification
• Managing Deployments — configure Production settings
• Operations Troubleshooting — diagnose issues post-launch