stxact Product and Flow Guide
Integration documentation for service operators, buyers, and auditors using trust receipts on Stacks.
Protocol Workflow
1. Register Service
Connect your Stacks wallet, submit endpoint metadata, and publish your service policy hash.
2. Receive x402 Payments
Buyer requests are challenged with payment requirements and retried after transaction confirmation.
3. Generate Signed Receipts
stxact creates a canonical receipt with seller signature, payment context, and optional delivery hash.
4. Verify and Resolve
Receipts can be verified independently. Disputes produce deterministic refund records and audit traces.
Receipt Verification Standard
Seller signature validity
Principal recovery and match
Payment transaction confirmation
Optional BNS ownership verification
Revision and delivery commitment status
Verify from the product UI or by API endpoint to support institutional audit workflows.
Core HTTP Endpoints
| Route | Purpose |
|---|---|
| /directory | Discover services and reputation |
| /receipts/:id | Inspect and verify a receipt |
| /disputes/new | File a structured dispute |
| /audit | Export CSV, JSON, and audit bundles |
Operational Guidance
Use idempotency keys for paid retries and avoid duplicate charges.
Anchor high-value receipts on-chain when third-party verification is required.
Publish service policy updates with stable policy hashes to preserve audit continuity.
For mainnet workloads, enforce multi-confirmation settlement and signed dispute actions.