Developers · Integration Studio
Your first integration
Signing in opens your Abraxas account only. Eligibility is a signed result defined by each partner policy. Identity or liveness appears only when a policy requires it. Choose what to verify, create a test app, send a request, receive a signed proof, and check it independently.
Choose a policy pack
Select what your customers must prove. These are the same Launchpad policy packs—identity or liveness is never the default path.
Sandbox institutional protocol access shares only organization_eligible with your application.
Need help choosing? Guided matching (optional)
What are you trying to accomplish?
Choose the outcome first. Abraxas recommends one integration path — advanced options stay available below.
Advanced integration paths
Open to see Solana gates, webhooks, onchain deployment kits, and other specialized paths.
What does your application need to verify?
Describe the product gate in structured choices. Studio matches the smallest existing policy capable of answering the requirement. A new or Production policy requires review. This planner never issues Production access, custom policies, or approval.
Policy privacy contract
Holders disclose the minimum required for Sandbox institutional protocol access. Your app receives the disclosed result—not raw identity data.
See requirement, assurance, and verification methods
- Requirement
- Sandbox institutional protocol access
- Purpose
- Technical sandbox policy only. It is not live KYB, KYC, AML/KYT, legal certification, production access, Utila integration, or permission to move funds. Sandbox test result for technical integration only. It is not a live KYB or Production approval. The holder completes the existing organization or authorized-signer eligibility flow after an operator issues a sandbox test result. The partner receives an opaque institutional result bound to activate_protocol_access, not a company file.
- Assurance
- L2
- Stays private
- legal name, company registration number, documents, beneficial owners, address, wallet, provider payload, raw receipt, callback URL, secret
Signing in opens your Abraxas account. It does not prove age, identity, residency, wallet control, membership, or any other eligibility claim.
- Google / account sign-in · does not qualify
- Use an existing private verification · does not qualify
- Partner-provided eligibility check · does not qualify
- Privacy-preserving verification · can qualify
- Self-attestation (browse only) · does not qualify
- Identity / liveness · does not qualify
Technical path, implementation, and starter kit
Advanced integration path
Recommended default: Hosted Partner Flow
Choose a different technical path
Implementation · Hosted Partner Flow
A working starter is available for this path. Open documentation
How this connection works
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" };
}
Generate your starter kit
Choose your platform, then generate a downloadable project with the selected Abraxas connection. Sign in and create a sandbox to pin a live application binding.
Technical 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.
Platform
Any product with an HTTPS backend. Canonical integration. Works with: verify_with_abraxas, hosted_partner_flow, server_receipt_verify, webhook_events, trading_venue, payment_authorization, portable_action_contract, wallet_standard_binding, nft_collection_gate, 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.
Add optional capabilities
Optional capabilities
Your selected path is included automatically. Add only extra capabilities your service needs.
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 receive raw wallet history, balances, addresses, or whale rankings; activity categories remain partner-owned.
- 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.