Trust center
Security at Receipt
Report suspected vulnerabilities privately to security@receiptprotocol.com. Do not include secrets or personal data in an initial report.
Commerce controls
Receipt signs and binds quotes to a buyer connection, immutable offer version, arguments hash, price ceiling, terms, expiry, and policy result. Purchases enforce wallet, session, scope, per-call, daily, seller, capability, verification, and side-effect rules server-side.
Payment integrity
Reservations, settlement, release, and refunds use idempotent commands and balanced append-only journal entries. Provider delivery is validated before settlement, and signed Receipt events preserve an auditable history.
Provider isolation
Seller metadata and provider output are untrusted. Provider credentials are decrypted only within the selected adapter path. HTTPS, DNS, private-network, redirect, timeout, and response-size checks protect upstream execution.
Account response
Users can pause spending, revoke sessions and trusted-client keys, block sellers or side effects, inspect transactions, and request remedies. Receipt can pause sellers, offers, capabilities, and adapters independently.