Test and live environments
HumanPass separates test and live sites and credentials. Prefixes make accidental mixing easier to identify.
| Environment | Sitekey prefix | Secret prefix | Purpose |
|---|---|---|---|
| Test | hp_site_test_ |
hp_secret_test_ |
Local development and integration testing |
| Live | hp_site_live_ |
hp_secret_live_ |
Production traffic |
Test environment
Section titled “Test environment”Use a test site while building your integration. Test sites can allow exact localhost origins in non-production runtimes.
Test responses still follow normal expiry, action, hostname, and single-use rules. This makes local behavior representative of production without using live credentials.
Live environment
Section titled “Live environment”Live origins require HTTPS. Add the exact production hostnames that render the widget and use only the matching live secret on your backend.
Promotion checklist
Section titled “Promotion checklist”Before switching to live:
- Create or select the live site.
- Add all production hostnames.
- Configure the intended mode and allowed actions.
- Replace the browser sitekey.
- Replace the backend secret through your secret manager.
- Set
expectedHostnameandexpectedActionin backend verification. - Test success, expired-token, duplicate-token, and HumanPass-unavailable paths.
