Test & Production Environments
Understand the difference between test and live environments and how to manage them correctly.
Overview
Begini provides two separate environments for every deployment. Understanding the difference and keeping them properly separated is essential before you go live.
The two environments
Test is for development and integration work. Use it to build your integration, run test assessments, and validate your webhook handling. Test data does not appear on your production results screen, and Test integration IDs cannot handle the same volume of concurrent users as Production.
Production is for live applications with real users. Only production data appears in the Beacon results screen, and results here have direct business impact.
What is environment-specific
Everything in the Deployment Centre is scoped per environment. This includes:
| Item | Test | Production |
|---|---|---|
| Integration ID | Unique | Unique |
| API Key | Unique | Unique |
| Webhook endpoint | Separate | Separate |
| Redirect URLs | Separate | Separate |
| Branding config | Separate | Separate |
Changes made to one environment do not carry over to the other — branding, redirects, and webhook endpoints must be configured independently in each tab.
Finding your credentials
In Beacon, go to Deployment Centre and select your deployment. You will see a Test tab and a Production tab — the platform defaults to Test. Each tab shows its own Integration ID and API Key.
Important: switch to the Production tab and verify your credentials before going live. Using Test credentials in production will result in failed requests.
Common mistakes
- Using Test API keys in production (or vice versa)
- Configuring redirects or webhooks only in Test and forgetting to replicate them in Production
- Assuming data from Test sessions will appear in the Production results screen — it will not
Recommended workflow
- Build and test your integration fully in the Test environment
- Configure your production webhook endpoint and redirect URLs in the Production tab
- Validate HMAC verification against production credentials
- Switch your integration to use the Production API key and Integration ID
- Monitor your first live sessions in the Beacon results screen
Next steps
- Creating a Session — API session creation reference
- Managing Deployments — configure Production redirect URLs and webhook endpoint
- Go Live Checklist — full pre-launch readiness checklist
Was this article helpful?
Give feedback