Create a sandbox integration

Find the right policy

Describe the product gate in structured choices. Studio matches existing policy packs only. A new or Production policy requires review. This planner never issues Production access, custom policies, or approval.

Discover · Choose a policy pack

These are the same packs Partner Launchpad uses. Identity or liveness is never the default path.

Discover · Narrow result

Requirement

Age 21 eligibility

Purpose

Confirm you meet a 21+ eligibility threshold without sharing your birth date with the partner.

Minimum disclosed result

age_eligible_21

Assurance

L2

Withheld

date of birth, government ID images, legal name, email

Google sign-in creates an Abraxas account. It does not prove age, identity, residency, wallet control, membership, or any other eligibility claim.

Partners receive a policy result, not evidence. Selective disclosure · Policy compatibility · Multi-chain Mainnet readiness

Identity is default: false.

• Google / account sign-in · does not qualify — Google sign-in creates an Abraxas account. It does not prove age, identity, residency, wallet control, membership, or any other eligibility claim.
• Use an existing private verification · does not qualify — A previous private verification may satisfy this request. The new partner receives only this policy’s result. Selecting reuse does not issue a result.
• Partner-provided eligibility check · does not qualify — Offer this route when the partner has configured an eligibility check.
• Privacy-preserving verification · can qualify — Share only the policy result. The partner does not receive ID images or a profile.
• Self-attestation (browse only) · does not qualify — Self-attestation is L0 browse access only. It cannot satisfy an authoritative policy and cannot settle Circle USDC.
• Identity / liveness · can qualify — This policy lists identity or liveness as an accepted assurance method. It is not the default first step when another qualifying method exists.

Discover · Choose an integration path

Discover · Hosted Partner Flow

Existing implementation. Docs: /docs/partner-flow

import { AbraxasPartnerKit, permitProtocolAction } from "@/lib/partner/integrationKit";

const kit = new AbraxasPartnerKit({
  partnerId: "your-partner-id",
  policyId: "your-policy-v1",
  policyVersion: 1,
  requirePolicyVersion: true,
  environment: "sandbox",
});

export async function startVerification(returnUrl: string) {
  return kit.createHostedVerificationUrl(returnUrl);
}

export async function completeVerification(callbackSearch: URLSearchParams) {
  const result = await kit.verifyCallback(callbackSearch);
  // Grant only when outcome is permitted.
  if (!permitProtocolAction(result)) {
    return { grant: false, outcome: result.outcome };
  }
  return { grant: true, outcome: "permitted" };
}

Integrate · Generate starter kit

Universal HTTPS is the canonical starter. A static or browser-only site cannot verify receipts or hold partner secrets.

• An HTTPS backend or serverless function. A static or browser-only site cannot verify receipts.
• Server-side secret storage. Never put partner secrets, API keys, or webhook secrets in browser code.
• An allowlisted callback URL for Hosted Partner Flow.
• Server-side public-receipt verification with live currently_valid checks.
• Signed webhook handling that re-fetches the public receipt before any grant.

Platform

Any product with an HTTPS backend. Canonical integration. Works with: hosted_partner_flow, server_receipt_verify, webhook_events, trading_venue, payment_authorization, portable_action_contract, wallet_standard_binding, solana_gate, evm_partner_adapter, onchain_protocol_gate, solana_onchain_eligibility_gate, evm_onchain_eligibility_gate, eligibility_presentation, cross_chain_protocol_access, testnet_gate_deployment, institutional_eligibility_gate, onchain_verifier_conformance.

Optional capabilities

Create · Create a sandbox integration

Signed-in partners can create an isolated sandbox integration through Partner Launchpad. The sandbox key is shown once. Production credentials stay on the reviewed upgrade path.

Explore the catalog without a session. Sign in on Partner Launchpad to create an isolated sandbox app on your tenant. The raw sandbox key is shown once.

Test · Sandbox checklist

1. Configure allowlisted callback. Register the development callback on the sandbox app. Hosted Partner Flow returns there with a receipt_id only. /docs/partner-flow · kit file .env.example
2. Start Hosted Partner Flow. Redirect the holder to hosted verification. Callback query keys are not authorization. /docs/partner-flow · kit file README.md
3. Verify a receipt from the server. Fetch GET /api/receipts/{id}/public and evaluate currently_valid on your backend. /verify?mode=receipt · kit file README.md

Upgrade · Production review

Production access is requested through the existing reviewed Launchpad process after sandbox readiness. This path never issues a production key, activates Production, submits payments or trades, creates wallets, or moves funds.