Skip to main content
Development is on from the moment you sign up. It is not billed and needs nothing. Production needs four things, and the Console’s dashboard walks you through them in a Go to production card. Until all four are done, your Development gates and keys keep working as usual.

​
1. Verify your domain

Add your root domain, for example meridianairlines.com. The Console shows a TXT record with a name and a value. Add it at your DNS provider, then select the check. A new record can take a few minutes to show up. A verified domain does two things:
  • It unlocks production gates. Activating a Production gate needs at least one verified domain on your organization.
  • It bounds your live site keys. Every allowed origin on a pk_live_ key must sit under a verified domain: the root itself, or any subdomain of it. https://www.meridianairlines.com, https://checkout.meridianairlines.com and https://*.meridianairlines.com are all under meridianairlines.com. Test keys (pk_test_) are exempt, so you can build before your domain is verified.
If you save a live key with an origin outside your verified domains, the Console names the origin and refuses the save, for example “shop.example.net isn’t on a verified domain (meridianairlines.com). Verify it first, or use a test key.”

​
2. Submit your business for review

Enter your legal name, EIN, website and intended use. A person reviews it, usually within a day. Your Development environment keeps working while the review is open. If BotShield needs more, the step says so.

​
3. Create your Developer passkey

Your Developer passkey is a passkey on your own Console account. Every production change is confirmed with it, at the moment you make the change: BotShield asks for a fresh confirmation when your last one is more than 5 minutes old. That includes:
  • Placing and activating a Production gate, and changing a Production gate’s settings, including Who may pass.
  • Revoking or rotating production keys.
Only someone holding the passkey can make these changes. Development changes never ask for it.

​
4. Pick a plan

Every organization starts on Free, and Free covers your first production gate. Pick a paid plan when you need more production gates. Development gates are never limited. Draft and Active production gates count toward the limit; Archived ones do not.

​
When Activate is refused

Activate on a Production gate checks the steps in this order and stops at the first one that is missing: The domain is checked before the passkey, so you are never asked for a passkey only to be refused. Placing a Production gate can return the two passkey codes and the plan limit.
Gates and keys already live keep running. These checks run when you place, activate or save. They never run when a person passes a gate. A Production gate that was active before you verified a domain stays active.

​
Next steps

Place a gate

Place and activate the Production gate.

Testing

The pre-launch checklist.

Keys and environments

Site keys, API keys and the two environments.

Who may pass

Set the levers before you launch.