October 22, 2026 · 6 min read

Stablecoin Reserve Attestations vs. Transaction-Level Compliance Evidence: What Can Each Prove?

What reserve attestations can establish about backing, what policy receipts can verify about covered payments, and where each claim ends.

TL;DR

A reserve attestation examines an issuer’s backing assertion for specified dates. For issuers covered by NYDFS guidance (opens in a new tab), the monthly examination covers the last business day of the period and at least one randomly selected business day.
A transaction-level policy receipt (opens in a new tab) can show that a covered proposed payment satisfied a defined policy before execution. Its scope depends on the action, policy version, and inputs bound to the receipt.
Neither substitutes for the other. Reserve evidence does not establish a payment’s legitimacy, while a valid receipt does not prove reserve backing, authenticate every external input, or establish settlement on its own.
This comparison addresses evidence scope, not cost or vendor selection. Neither evidence type replaces required reporting or audits.

What a reserve attestation proves

A reserve attestation examines management’s assertion about reserve backing at specified dates. The examination uses records of outstanding tokens and reserve assets, including valuations and reconciliations. The accountant’s report should identify the records, assertions, and dates it covers. An independent accountant examines the assertion against the requirements of the engagement. The resulting report addresses that assertion, not every payment made with the stablecoin.

Under New York’s guidance for DFS-regulated USD-backed stablecoins (opens in a new tab), issuers should maintain sufficient reserves at each business-day end. The required monthly CPA examination covers management’s assertions for the period’s last business day and at least one randomly selected business day. Those assertions include reserve value by asset class, units outstanding, reserve adequacy, and reconciling items at the selected times.

The GENIUS Act (opens in a new tab) sets out a separate set of requirements for permitted payment stablecoin issuers. It requires monthly reserve disclosures, an examination of the previous month-end report by a registered public accounting firm, and a monthly officer certification. Check the Act’s reporting provisions (opens in a new tab) for the applicable publication and submission requirements. These are distinct obligations, not one attestation covering every day.

Neither monthly examination establishes reserve adequacy on unexamined intervening days or determines whether a particular transaction was legitimate. New York’s guidance calls for a separate annual attestation of reserve-related internal controls. A monthly reserve examination does not establish that broader control conclusion, and neither examination replaces other applicable audits or reporting duties.

What a transaction-level policy receipt proves

A transaction-level policy receipt is independently verifiable evidence that a proposed covered action passed a check against a specified policy version before execution. Inherence’s technical description (opens in a new tab) specifies a proof bound to the proposed action, the policy version, and the public inputs needed for verification. An independent verifier must use an accepted verification key and check that the receipt refers to the expected action. Proof validity alone cannot establish that the verifier accepted the policy version.

For a payment, the verifier checks the action binding against the intended payee, amount, and payment instrument. The verifier must also check that the receipt is current, belongs to the intended payment record, and cannot be reused for another action. If a policy sets a cumulative spending limit, an authoritative state service must track spending across the covered paths. A proof cannot account for activity that bypassed that service.

Inherence describes a pre-execution gate that blocks covered actions when they fail defined controls. Payment integrations using that gate remain proposed architecture unless validated. For example, a proposed payment integration could check that a stablecoin transfer stays within a per-payment limit and goes to an approved payee before initiation. A receipt for a passing transfer could let a third party verify that those defined checks passed for the bound payment and policy version without disclosing protected inputs encoded in the proof. Inherence provides evidence for covered actions routed through the defined enforcement path and evaluated against committed or attested inputs. A receipt does not establish the truth of every external input or cover actions outside that path. Separate payment-rail records must establish settlement, and receipts do not replace statutory reporting or audits.

Where the two regimes legally sit

The GENIUS Act (opens in a new tab) sets distinct reserve-disclosure, examination, and certification requirements for permitted payment stablecoin issuers. Their applicability must be assessed against the Act’s effective-date provisions and implementing rules. The Act also requires certain issuers with more than $50 billion in outstanding stablecoins to prepare audited annual financial statements, subject to its stated exception for specified SEC reporting. Separately, the Act treats permitted issuers as financial institutions for Bank Secrecy Act and sanctions purposes and sets requirements for anti-money-laundering controls.

For OCC-supervised entities, the applicable OCC rulemaking (opens in a new tab) must be checked separately from the Act. Confirm the linked bulletin’s publication, final-rule status, effective date, and treatment of Bank Secrecy Act and sanctions standards against the primary rulemaking record before publication.

A transaction-level policy receipt can provide independently verifiable evidence about a covered action evaluated before execution. Neither the Act nor the OCC rule treats such a receipt as satisfying reserve, examination, audit, or reporting duties. A receipt also does not independently establish the truth of every external input or cover actions outside its defined enforcement path.

Comparison table: claim, timing, inputs, verifier, open questions

Reserve examinations and transaction-level receipts support different claims. Each requires a verifier to check its scope and inputs.

Evidence claim	Timing/frequency	Required inputs	Independent verifier	Unanswered questions
Reserve examination. An accountant examines management’s assertion about reserve backing at specified times.	The period depends on the engagement. NYDFS guidance (opens in a new tab) requires monthly examinations covering period-end and one randomly selected business day for covered issuers.	Reserve asset records, outstanding unit counts, valuations, and reconciling items.	An independent accountant examines the defined assertion.	The examination does not establish backing on unexamined days or determine whether a particular payment complied with policy.
Transaction-level policy receipt. A receipt provides independently verifiable evidence that a proposed covered action passed a defined policy check before execution.	A receipt can be generated when each covered action is evaluated.	The proposed action, committed policy version, proof, expected public inputs, and verification parameters.	An independent verifier checks the proof and its binding to the action and accepted policy version.	The receipt does not establish reserve backing, settlement, the truth of external inputs, or conduct outside the enforcement path. See Inherence’s receipt model (opens in a new tab).

A receipt for an intervening payment answers a conduct question that the reserve examination does not address. Its verifier still needs separate evidence for backing and settlement.

Where the two evidence types can work together

For a payment made between examined reserve dates, an issuer or diligence reviewer can consult both records. The reserve report addresses backing at its examined dates. A receipt addresses whether the covered proposed payment passed its policy check.

Inherence proposes a payment integration that would check covered actions against defined controls before execution and block actions that fail. An independently verifiable receipt (opens in a new tab) could document a passed check against a committed policy version. That evidence would apply only to actions routed through the defined enforcement path and evaluated against committed or attested inputs. It would not authenticate every external input or cover payments outside that path.

A verifier would still need payment-rail records to establish settlement. AP2- and x402-style adapters remain proposed architecture, not demonstrated deployments. Link the relevant AP2 and x402 technical specifications if these protocols remain in the published example. Neither evidence type replaces required reserve examinations, reporting, or audits.

Buyer questions to ask before relying on either

Which reserve dates did the examination test, and which payment actions passed through the receipt’s defined enforcement path?
Can the buyer identify the independent examiner or receipt verifier and obtain the report or verification materials needed to check the claim?
Which reserve figures, payment details, and policy inputs came from authenticated sources, and which relied on management or another party’s assertions?
Does the receipt identify the exact action and policy version evaluated before execution?
Does a separate payment-rail record confirm settlement, or does the receipt establish only that the proposed action passed its policy check?
Which actions fall outside the evidence’s scope, and which statutory reports or audits must the issuer provide separately?

Conclusion

For a backing claim, examine the reserve report’s dates, assertions, and accountant’s conclusion. For a payment-policy claim, verify the receipt’s action binding, policy version, and enforcement-path coverage. Obtain separate records for settlement and any required statutory reporting or audits.