Skip to main content
On a headless storefront — Composable Storefront (PWA Kit) or Storefront Next — you place the same BotShield Gate at checkout using the BotShield client SDK instead of the Experience Cloud component. The verification is pushed into your Salesforce org exactly the same way, as a BotShield_Gate__c record.

Approach

1

Add the SDK to your storefront

Add the BotShield web component, <botshield-verify>, at your checkout step, with your site key and the gate’s key in scope. Add your storefront’s origin to the site key’s allowed origins; a production (pk_live_) key’s origins must sit under a domain your organization has verified.
2

Gate the purchase

Intercept the checkout so the order is placed only after your server has verified the BotShield token for the current request. See Verify on your server. A gate always asks, so every checkout gets a fresh passkey confirmation.
3

Read the pushed row

If the gate is selected under Pushing to Salesforce (see Install and setup), BotShield pushes the BotShield_Gate__c record into your org; downstream automation (order creation, fulfillment) can key off that row.
The widget, transport, and field mapping are the same as the Experience Cloud flow — only the placement differs (your storefront code vs. Experience Builder). See Experience Cloud for the record fields and how to act on them.

Reference implementation

Coral Cloud demo repo

A Salesforce Experience Cloud demo wired to BotShield end to end. Its checkout gate shows the same pattern you place in a headless storefront.