Skip to main content

​
Use Cases

BotShield is designed for platforms that need to verify human presence for critical actions. Here are common use cases.

​
E-Commerce and Retail

​
Limited-Access Product Drops

Protect high-demand product launches from bots and scalpers:
  • Sneaker releases
  • Limited edition collectibles
  • Concert merchandise
  • Exclusive collaborations

Example: Sneaker Drop

A sneaker brand integrates BotShield at checkout. When a user attempts to purchase a limited release, the platform creates a verification request via the API. The user verifies their presence in 5 seconds via Face ID, and the checkout proceeds. Bots cannot complete this flow.

​
High-Value Checkout

Require verification for expensive purchases:
  • Luxury goods
  • Electronics
  • High-ticket items
  • Custom orders
Integration pattern:
The verification is anonymous: your webhook receives a request_id and result, never a user identity. Correlate it back to your order via the metadata you passed in.

​
Ticketing and Events

​
Ticket Sales

Ensure fair access for real customers:
  • Concert tickets
  • Sports events
  • Theater shows
  • Festival passes

Example: Concert Tickets

A ticketing platform uses BotShield to prevent bot scalping. Before a ticket purchase is processed, the user must complete a presence verification. Real fans complete this in seconds. Automated scalping bots cannot.

​
Event Registration

Protect event registration from automated signups:
  • Conferences
  • Workshops
  • Limited-capacity events

​
Platform Actions

​
Account Recovery

Verify human presence during sensitive account operations:
  • Password reset
  • Email change
  • Security settings modification

​
High-Value Platform Actions

Protect critical platform operations:
  • API key generation
  • Payment method changes
  • Subscription modifications
  • Data exports

​
Content and Community

​
Public Posting

Reduce spam and abuse in public forums:
  • Comment systems
  • Review platforms
  • Community forums

​
Content Submission

Prevent automated content creation:
  • User-generated content
  • Form submissions
  • Upload systems

​
Financial Services

​
Transaction Verification

Verify human presence for financial actions:
  • Wire transfers
  • Large withdrawals
  • Account changes

​
Digital Agreements

Confirm human presence for legal documents:
  • Terms acceptance
  • Contract signing
  • Consent forms

​
Integration Patterns

​
Selective Enforcement

You choose which actions require verification. Not every action needs it — only the ones where bot abuse would cause harm:

​
Webhook-Driven Flow

The recommended pattern for production:
  1. User initiates action on your platform
  2. Your server creates a verification link via BotShield API
  3. User completes verification (5 seconds for returning users, or instant on MultiPass continuity)
  4. BotShield sends a signed, anonymous webhook (Svix envelope) to your callback URL
  5. Your server verifies the Svix signature, matches the request_id back to your action, and completes it

​
Next Steps