Agentic Commerce Requires Verifiable Payment Proofs

In a world of autonomous agents, a payment is not complete when two parties agree—it is complete when anyone can verify it without asking anyone else. Machine-to-machine commerce requires payments to leave behind objective, portable evidence that can be consumed by other agents, smart contracts, or external systems. Without such evidence, automation breaks down: every payment becomes a private event that must be trusted, re-checked, or disputed.

Globally-verifiable non-interactive payment proofs capture the ability of a payment system to produce objective, third-party verifiable evidence that a payment has occurred, without requiring ongoing interaction between the involved parties. This property comprises two complementary guarantees: (1) receiver non-repudiation, where the sender can prove that the receiver accepted a payment, and (2) invoice fulfillment verifiability, where the receiver can prove that a specific invoice—identified by a payment hash or ID—has been paid by someone.

This property is particularly important for agentic commerce, where payments are tightly coupled with automated service delivery such as compute, bandwidth, storage, or API access. In these settings, smart contracts or autonomous agents often act as arbiters that must decide whether to release resources, deliver results, or enforce penalties. For such decisions to be reliable, they must be based on **objective and globally verifiable evidence of payment finality**, rather than on private communication or interactive protocols. Without non-interactive proofs, systems must rely on trust assumptions, callbacks, or dispute-prone coordination, which significantly complicates automation and weakens security guarantees.

Bit2 provides globally-verifiable non-interactive payment proofs in both dimensions. For receiver non-repudiation, the sender can obtain a signed receipt from the aggregator before on-chain time-stamping, which becomes binding contingent on the inclusion of the corresponding commitment. This receipt can be presented as verifiable evidence that the payment has been accepted and will be enforced. For invoice fulfillment verifiability, Bit2 allows receivers to embed invoice identifiers into payments, enabling them to later produce publicly verifiable proofs that a specific invoice has been satisfied, independently of who performed the payment. These proofs can be verified by any third party or smart contract without requiring interaction with the sender or the aggregator.

In contrast, systems such as the Lightning Network and INTMAX2 do not provide globally-verifiable non-interactive payment proofs. Lightning payments rely on the revelation of preimages and local channel updates, which do not produce globally verifiable evidence that a payment was completed or that a specific invoice was fulfilled. Similarly, INTMAX2 focuses on client-side validation and compression but does not expose publicly verifiable proofs linking payments to invoice identifiers or acceptance events. As a result, these systems are less suitable for fully automated environments where external parties must independently verify payment outcomes.

Designing Bit2, we treated payments not as isolated transfers, but as verifiable events in a broader computational system. Every design choice—from client-side validation to SNARK-based state compression and commitment anchoring—was made to ensure that payments can be reliably consumed by other agents without ambiguity, coordination, or trust assumptions.

The result is a payment network where transactions are not only fast and scalable, but also cryptographically usable as inputs to automated decision-making. This is a fundamental requirement for agentic economies: payments must integrate seamlessly with code, contracts, and services. Bit2 is built with this future in mind—a system where money is not just transferred, but proven, verified, and acted upon by machines at scale.