Exact approval and payment evidence

Authorize the current revision and reconstruct its Arc payment outcome.

Last updated: 9/10/2026

Approve the exact expense

Human authority binds to the persisted expense revision and report.

01

Prepare the approval

On /org/[orgId]/approvals, locate approval.card and choose Prepare exact approval (prepare-approval). Verify the signer, vault, chain, policy version, report hash, and digest.

02

Sign the prepared data

Choose Sign with registered Privy wallet (sign-approval). Submission revalidates the current expense revision and report while holding the authority boundary. Concurrent revisions and stale approvals fail.

03

Automatic policy path

An owner can choose Execute under policy only for automatic_ready_for_payment. Recipient, per-payment cap, lifetime allowance, reserve, policy version, expiry, and pause state must all permit execution.

Consumer approvals page with exact revision and wallet approval material
The approval view makes the exact signer, revision, report, vault, chain, and policy context reviewable.

Inspect the receipt

The activity surface joins intent, provider attempt, chain receipt, and reconciliation without hiding uncertainty.

04

Open payment activity

On /org/[orgId]/activity, read each payment.card and choose Inspect intent, attempts, and receipt. A live explorer link appears only for a verified non-local transaction.

05

Read the unified timeline

On /org/[orgId]/activity/[paymentId], inspect payment-evidence-timeline: expense revision, Graph decision, human approval or automatic rule, executor context, immutable intent, attempts, Arc Paid event, USDC Transfer, and reconciliation history.

Consumer payment activity page showing payment records and evidence status
Activity distinguishes local payment evidence from a verified live Arc transaction.