Sandbox guide

Sandbox mode runs the real pipeline — consent, single-use code, PKCE redemption, field mapping — against a fixed test client and a fake consumer. No popup, no real PII, no charge.

Enable it

<script
  src="https://cdn.pryvc.com/v1/pryvc.js"
  data-client-id="pc_sandbox0sandbox0sandbox0"
  data-fields="first_name,last_name,email,phone,city"
  data-purpose="Quote request"
  data-mode="fill"
  data-env="test"
></script>

Clicking the button skips the consent popup and consents server-side as Casey Sandbox (sandbox@example.com, +1 555 555 0100, Springfield IL). Your form fills through the exact redeem path production uses — including the atomic single-use burn.

What sandbox proves

• Your field mapping (names, autocomplete attributes, data-pryvc-field overrides)
• Your filled / submitted / error event handling
• The origin checks (localhost is pre-verified for the sandbox client)

What it doesn’t do

• No emails, no webhooks, no billing state — sandbox shares are inert records.
• The sandbox client can’t request date_of_birth or address line fields beyond city.

When you’re ready, swap data-client-id for your real one and remove data-env="test".