RunOnProof Payment Decision

RunOnProof Payment Decision

One organizational offer backed by five internal seller specializations. Buyer supplies a signed BuyerPaymentMandate and funds exactly one 0.79 USDC escrow. Coverage is federal-only. State coverage and state good standing are not asserted in Phase 1. Returns a signed Proof Capsule with deterministic replay; never executes the supplier payment.

What 0.79 USDC includes

Use RunOnProof Payment Decision before releasing a US supplier payment when federal-only coverage fits your task. One fee covers one structured decision, the necessary checks within the supported scope, reasons, conditions, remediation, evidence references and the corresponding signed Proof Capsule.

The analysis binds the supplier, invoice or obligation digest, amount, declared payee, payment destination and signed buyer mandate to the same operation. It applies the supported policy, checks mandate scope and limits, evaluates supported federal evidence and identifies a declared payee/destination mismatch. Preserve the result and proof to inspect why this specific operation received its decision.

Inputs to prepare

Use the complete current input schema: requesting agent and key, buyer context and signed BuyerPaymentMandate, supplier identity and supported federal identifiers, invoice/obligation reference and document digest, amount and currency, payee and destination references/fingerprints, payment-instruction digest, economic purpose, policy and freshness requirements, evidence references, disclosure, correlation, and declared payment exposure and valuation basis. Keep private keys local. Follow the buyer-authority contract for your channel; free Agent ID alone does not grant payment authority.

Read and verify the result

The canonical result is ALLOW, ALLOW_WITH_CONDITIONS, HOLD, BLOCK or UNDETERMINED. Read machine_action, reasons, conditions, limitations and validity together. HOLD and UNDETERMINED are not authorization to pay. A delivered HOLD can be a valid paid decision. Verify the Proof Capsule signature and its request/evidence bindings using the published keys and guide. A signature does not independently establish the truth of buyer assertions.

Coverage and limits

US FEDERAL_ONLY. No state-registry or state-good-standing assurance, no confirmation of bank-account ownership and no comprehensive guarantee of invoice economic authenticity. The invoice digest is bound to the signed request; its economic authenticity remains a buyer assertion. RunOnProof never executes the supplier payment.

Repetition and recovery

0.79 USDC per decision, at most one charge for the same decision; no subscription or recurring billing. Preserve the original request and idempotency information. Recover an acquired result through the published authenticated recovery flow without paying again. On Virtuals, preserve the same ACP job and follow its native recovery guide; do not add an x402 payment. Changed business inputs are not a replay. A HOLD is not automatically free, and no universal refund is promised.

Inspect before buying

• Current input schema
• Purchase, signing and recovery guide
• Virtuals ACP guide
• Proof verification keys
• Existing synthetic request

The example is SYNTHETIC_NOT_EXECUTABLE: placeholder signatures and fixed dates are not valid authority, receipts or production evidence. Do not submit them for payment.