Settlement
Funds never touch GunVaultHQ. Here is how the rail actually settles.
GunVaultHQ is the compliance + orchestration substrate. The settlement rail is whatever rail the customer's policy selects. The design routes — it does not custody. This page describes what the substrate is built to interoperate with, and what is gated until counsel review and federal firearms-payment- regime audit clear.
How the model works
- Substrate routes, never custodiesdesign constraint, not just policy
- Programmable-money primitivesbuilt on, not built around
- Regulated-stablecoin compatibilityaudited-reserve rails preferred
- Capability Gate engagedlive toggle closed until clearance
TL;DR
GunVaultHQ's settlement model is decoupled: the compliance engine decides, the settlement rail executes. The rail can be a regulated-stablecoin path or a USD path — selected by the customer's policy. The compliance substrate is built. The live-rail toggle is gated behind per-state counsel sign-off on the no-MTL posture and federal firearms-payment-regime audit clearance.
What the substrate decides
Before any settlement instruction is emitted, the compliance engine resolves the transaction against the controlling regulation — federal, state, and (where applicable) local — and attaches the citation to the decision.
- Regulatory classification with citation
- Federal credentialing surface, per-transaction
- State-policy classification (per-jurisdiction by design; firearms starter fixture today)
- Audit-chain anchor — every decision Knox-anchored, independently verifiable
These run locally today. The decisions are real. The customer-facing wire is the gated piece.
What the rail can be
The compliance engine is rail-agnostic. The same decision works whether the customer's policy routes through a USD rail or a regulated-stablecoin rail.
- USD path
- Routed via the customer's elected processor or bank rail when activation conditions clear.
- Regulated-stablecoin path
- Routed via an audited 1:1-reserve stablecoin (USDC). The reserve attestation is published by the issuer; the substrate does not mint, custody, or issue any token.
Customer policy selects. Substrate routes. GunVaultHQ never touches the funds.
Why a regulated-stablecoin path matters here
Operator-banking risk in the licensed firearms channel is real. Lawful manufacturers, dealers, and adjacent service providers have lost processor relationships under industry-class policies rather than for any compliance failure of their own.
A rail with audited 1:1 reserves and on-chain transparency is auditable in ways a closed processor is not — both for the operator and for the regulator examining the operator. The compliance engine's citation lives on the same audit chain the settlement instruction references.
GunVaultHQ does not mint, does not custody, does not issue any token. The stablecoin rail is operated by a third-party issuer with its own regulatory posture. Customers who do not want a stablecoin path use USD.
Capability Gate — explicit
- Built
- Compliance engine, classification primitives with citation, audit-chain wiring, multi-rail adapter pattern.
- Gated
- Customer-facing live-rail toggle, per-state counsel sign-off on the no-MTL posture, federal firearms-payment-regime audit clearance, real-rail credential provisioning.
- In production today
- No customer-facing live commerce surface. Substrate operates locally; nothing on this page is a deployed customer-facing service.
- Path to live
- Counsel review, regulator engagement, and rail-issuer onboarding all proceed independently of this page. The substrate stands ready for each.
What this is not
- GunVaultHQ does not custody funds.
- GunVaultHQ does not act as a money transmitter.
- GunVaultHQ does not mint, issue, or offer any token.
- GunVaultHQ does not require customers to hold cryptocurrency.
- GunVaultHQ does not provide investment advice.
- GunVaultHQ does not act as the FFL of record for any transaction.
Designed to support the existing federal and state firearms- compliance regime — not to replace or circumvent it.