Guard the creation step
Connect proof to the request that creates an account, not only to the page that contains the form. Your server still validates the submitted information and applies application rules before persisting the account.
USE CASE New accounts
Open the door
with more context.
Protect account creation and trial entry with browser verification while keeping onboarding simple for legitimate users.
WHAT TO COVER
Protect creation without slowing real users.
Keep identity checks separate
Browser verification is not email ownership, age verification, identity verification, or a guarantee of one account per person. Preserve the checks that your service needs for those questions.
Protect scarce benefits explicitly
Creating an account and granting a trial credit are separate operations. Decide which action needs protection and ensure that retrying a request cannot grant the same benefit repeatedly.
Measure onboarding completion
Start in Observe and compare grouped decisions with successful signup and activation. Include different browsers and normal interruptions in your testing; a page view is not evidence that someone finished onboarding.
- Signup request
- MANDATEBrowser verification
- Eligibility checks
- Account creation
More use cases
Where else abuse has an impact.
CAPABILITIESMANDATE VerifyBrowser verification for sign-in, account creation, checkout, and the other actions your application needs to protect. Invisible to the person using it.Read more INDUSTRIESSaaSApply browser verification to signup, sign-in, and limited-resource actions without putting machine APIs behind browser-only checks.Read more REQUEST INTEGRITYRetries, replay, and business outcomesRejecting reused proof and preventing a duplicate order solve different problems. A reliable action needs both boundaries to be clear.Read more