Payout blocked · forward this instead of a screenshot
Processor asked why payout was blocked. Send a verify URL — not your admin panel.
Velaru sits before disbursement — SC→USDC off-ramp, prize release, affiliate withdraw. On HOLD, compliance gets a signed receipt + public /verify link counsel can open in incognito. No kickoff call. No trust-me screenshot.
What gets forwarded internally: "Processor asked why we blocked redemption — here's external verify, not our back office." Velaru signs the HOLD at the gate moment. Strangers check green/red at
/verify without your login.
Self-serve eval · ~5 min · no call
- Run 60s demo — withdraw blocked → HOLD → verify URL
- Open /verify in incognito — paste receipt or follow demo link
- Pricing — $149 packet · $249/mo monitor · volume email
- Skim integrate — pre-disbursement hook shape + OpenAPI
- Volume pricing — sandbox → pilot → production bps
Start here · proof
60s redemption HOLD demo
Autorun walkthrough: player requests $2,500 USDC off-ramp → compliance HOLD → restraint receipt → stranger verify. No API key.
Run payout-gate demo →
Eng sandbox · $25
GAM starter credits
500 governed hops prepaid — wire payout_auth in sandbox before production weld. Self-serve Stripe.
Instant lane →
Integration · API
Clear-before-wire hook
payout_auth before wire/USDC API. Execute disbursement only on PERMIT; surface verify URL on HOLD.
Integrate API →
Production · after pilot
Gate weld + register
$25k one write + $5k/mo management · κ register · bps on attested volume. After sandbox proof.
Gate /operator →
Pre-disbursement flow (operator rail)
- Player requests SC redemption / USDC off-ramp / prize release
- Velaru
payout_auth hop → PERMIT or HOLD + signed receipt
- Your disbursement API fires only on PERMIT
- On HOLD: support sends /verify link — counsel checks in incognito
Minimal integration shape
POST /api/v1/payout_auth
{ "action": "redemption_release", "amount_usd": 2500, "asset": "USDC",
"user_id": "…", "operator_tenant": "…" }
→ { "result": "HOLD", "verify_url": "https://velaru.xyz/verify?entry_id=…" }
Operator verticals in mandate registry
Processor embed · B2B2B volume
MoonPay / Ramp class
Pre-disbursement hook
One integration on your rail → every operator inherits clear-before-wire. Bps on attested volume.
Processor one-pager →
Legal · paste
Operator clauses
§10–§15 payout gate, processor rider, escrow, MCP fuse, bps fee.
Download clauses →
Agents · dev
MCP fuse-required
Fail-closed tools · GAM credits · Cursor config.
MCP dev lane →
Sample clause · clear-before-wire
Payout Release Gate. Operator shall not initiate wire, ACH, stablecoin transfer, or third-party payout API call until Operator has obtained a Velaru payout authorization attestation (PERMIT) or documented HOLD with stranger-verifiable restraint receipt at /verify.
Nisaba LLC · Free fuse check · hello@velaru.xyz