Developers · Integration Studio

Partner starter kit generator

The universal Abraxas integration is HTTPS, hosted verification redirects, server-side receipt verification, and signed webhooks. Framework choice does not change the policy or receipt contract.

Minimum platform requirements

  • 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.

Supported platforms

  • Universal HTTPS (canonical) — Any product with an HTTPS backend. Canonical integration.
  • Next.js — App Router server routes. Secrets stay in the server runtime.
  • Express / Node — Node HTTP server using the same Partner Kit contracts.
  • Wix Velo — Good Trouble-style Wix backend. Secrets Manager names only. Frontend calls backend only.
  • Serverless function — Vercel Functions, Cloudflare Workers, or Netlify Functions with small host substitutions.
  • Solana partner backend — HTTPS partner backend plus the Solana eligibility gate. No on-chain personal data.
  • EVM contract integration — Partner-owned EIP-712 gate. Local Foundry tests only. Abraxas does not deploy a shared contract.
  • Solana program integration — Local/reference Anchor gate plus Ed25519 helpers. No live deployment or RPC.

What it generates

README, server route, .env.example, receipt verification, safe errors, optional webhook verification, a local receipt fixture, and a deployment checklist. Partner IDs, app IDs, keys, callbacks, and secrets are placeholders only. Reclaim proofs are verified on the Abraxas callback. Partners never receive the raw proof or app secrets.

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

What this starter kit does not do

  • Does not custody funds, cards, wallets, or tokens.
  • Does not issue Production access or live API keys.
  • Does not replace policy review or a written partner agreement.
  • Does not treat browser flags, callback query keys, or webhook bodies as grants.
  • Does not charge, capture, transfer, settle, or call Circle.
  • Does not sign a blockchain transaction or bind a wallet as identity.
  • Does not activate Mainnet, include RPC credentials, or execute partner chain transactions.
  • Does not treat a chain eligibility attestation as a payment, transfer, trade, token approval, or gas grant.
  • Does not rotate partner gate signers automatically or broadcast a signer-update transaction.
  • Does not treat an eligibility presentation as a bearer credential, passport, or automatic KYC/KYB approval.
  • Does not treat activate_protocol_access as a token transfer, mint, spend approval, order, payment, or custody action.
  • Does not call Utila, collect KYC/KYB evidence, or self-publish planning result categories.
  • Does not deploy a gate from the browser, Vercel, CI, or an API route.
  • Does not store company legal names, beneficial-owner data, or treat a wallet-control proof as KYB.

Open Studio

Generate a zip in Integration Studio. Partner Flow docs stay the receipt contract.