x402 for machine payments —
OMATrust for machine trust
OMATrust ties x402 Signed Receipts to your service, preventing identity attacks that can impact your online reputation.
x402 receipts need authorization
How do you know which reviews are legitimate?
x402 receipts prove a service transaction. Reviews without receipts are filtered out.
Three levels of key authorization
Each level addresses a specific failure mode. Start with Level 1 and add layers as your security requirements grow.
Your domain proves your keys
Create a DNS TXT record or host a DID document at your domain listing your authorized signing keys. Any receipt signed by an unlisted key fails authorization — even if the signature is valid.
Prevents unrelated signers from claiming a service identity. Gives verifiers a live ownership check.
Durable key authorization
A Controller Witness creates a historical authorization record on the blockchain. Verification continues even when your own endpoint is unavailable or you rotate your keys.
Receipts remain verifiable during CDN outages or DNS issues. Past signatures are still valid even when the key is not listed anymore.
Revoke a compromised key instantly
Enterprise key binding lets you broadcast revocation. Every verifier in the ecosystem rejects the compromised key immediately.
Supports regulated environments, security policy enforcement, and key lifecycle management.
Receipts become attestations
Reviews, disputes, and audits can reference portable proof of service interaction.
Keys bind to service identity
Receipts resolve through DNS/DID, witnesses, and key lifecycle controls.
Agents inherit better signals
Machine clients can evaluate reputation without trusting raw wallet volume.
Protect your x402 service reputation
Turn signed receipts into verified trust signals with service identity, authorized signing keys, witness continuity, and revocation controls.