Cryptographic Proof of Payment

Trust control panel for programmable Bitcoin

Cryptographic receipts + delivery proofs + deterministic dispute rails on Stacks

Standard Receipt

Sync Delivery

Completed

Immediate delivery proof included

Receipt ID0x32...89a
Timestamp2 min ago
Click to flip stack

Provisional Receipt

Async Pending

Processing

Job queued, delivery commitment pending

Receipt ID0x1c...4f2
Timestamp15 min ago
Click to flip stack

Final Receipt

Async Complete

Verified

Delivery commitment set, revision incremented

Receipt ID0x9a...b3d
Timestamp1 hour ago
Click to flip stack

Payment to Proof

1

Request → 402

Service returns 402 payment-required with Stacks address and price.

2

Pay → Deliver

You pay on-chain. Service delivers. stxact generates signed receipt.

3

Verify → Dispute

Receipt proves payment occurred. File disputes if needed. Reputation updates.

What a receipt proves

Every stxact receipt contains 15 canonical fields, cryptographically signed by the seller.

Payment transaction ID
On-chain proof of payment with block hash and height
Request hash
SHA-256 of the original API request (method, path, body, timestamp)
Delivery commitment
Hash of what was delivered (proves service fulfillment)
ECDSA signature
Seller's cryptographic signature over all fields
Receipt Format (Canonical)
STXACT-RECEIPT:
  receipt_id
  request_hash
  payment_txid
  seller_principal
  buyer_principal
  delivery_commitment
  timestamp
  block_height
  block_hash
  key_version
  revision
  service_policy_hash
  signature

Trust infrastructure for x402

Production-grade settlement layer for payment-required services

Cryptographic Receipts

ECDSA-signed delivery proofs with request hash binding and on-chain anchoring

Dispute Resolution

Deterministic refund rails with on-chain execution and state machine validation

Portable Reputation

Logarithmic scoring system anchored to Stacks principals, resistant to farming