Developers · Partner Launchpad
Partner Action Control Plane
The Partner Action Control Plane lives inside Partner Launchpad. It does not create a second dashboard, identity system, receipt issuer, or demo product.
What it operates
Signed-in partners use Launchpad to see one sandbox app’s pinned policy, configured capabilities, readiness, and the next real setup step. Capabilities are Hosted Partner Flow, receipt verification, webhooks, trading venue access, payment authorization, and optional Wallet Standard binding.
Google sign-in creates an Abraxas account. It does not prove age, identity, residency, wallet control, membership, or any other eligibility claim.
Action authorization stays generic
Trading and payment stay named action contracts on the same core rules: partner_id, policy_id, policy_version, action_scope, expires_at, one_time_nonce, current_receipt.
The Trading Venue Adapter never creates a trade, submits an order, opens a wallet, mints a token, or moves funds. It answers whether one named action may proceed.
An approved authorization is not a payment, transfer, charge, subscription, or settlement. The merchant or payment partner executes its own payment flow. Abraxas never moves funds.
Wallet binding proves control of a self-custodial wallet for one action contract. It is not identity verification and does not reveal private wallet information.
A webhook event is not authorization. Fetch GET /api/receipts/{id}/public and verify the signed receipt on your server before granting access.
Sandbox checklist
- policy selected
- hosted callback allowlisted
- partner flow tested
- receipt verification connected
- webhook endpoint verified
- trading preflight tested
- payment preflight tested
- wallet binding tested
- production upgrade readiness
Production credentials stay on the reviewed Launchpad upgrade path. The control plane cannot issue live keys, activate Production, or treat a sandbox pass as authorization.