WITNESSPayment checks on NEAR.
PUBLIC TESTNET RECORDS
The Case FilePayment Evidence ↗
W / 001PAYMENT INTEGRITY, DOCUMENTEDNEAR TESTNET / CASE M4

Same invoiceWrong account

The owner approved a supplier. The agent proposed a different receiving account for the same invoice. WITNESS enforced the original instruction.

THE INVOICE AMOUNT DIDN'T CHANGE. THE DESTINATION DID.
01 - THE DISCREPANCY

One approval, two outcomes

OWNER AUTHORIZATIONFORM / M4
Approval on record

WITNESS Demo Supplier

Pay to
mujeebwajid-witness-supplier.testnet
Payment limit
0.005 NEAR
Reference
WITNESS-DEMO-002
APPROVED BEFORE REQUEST
≠
AGENT REQUESTFORM / P5
Same amount, different recipient

Receiving account changed

Pay to
mujeebwajid-witness-agent.testnet
Payment
0.005 NEAR
Proposal
P5 / RECIPIENT_MISMATCH
RECEIVER ≠ APPROVED SUPPLIER
DENIED
The destination changed

P5 named the agent's account. The contract rejected the proposal with RECIPIENT_MISMATCH; no payment was sent.

View P5 receipt
Recorded on NEAR TestnetThese are historical cases. Switching tabs never signs or sends a transaction.

Live check not yet requested.

02 - EXPLORE THE MECHANISM

Test the switch. Inspect the proof.

Two ways to understand the same boundary - a local rehearsal and a public record.

Try an attack in the simulator
01 / THE EXPERIMENT

Choose an attack

Run different manipulations against the same trusted supplier payment.

Choose an attack to begin.
02 / THE EVIDENCE

Two versions of the truth

What the business authorized, compared with what the agent proposed.

ONE SOURCE OF AUTHORITY
ORIGINAL BUSINESS MANDATEOWNER AUTHORIZED
AB
ABC SuppliesRegistered supplier · Invoice INV-3119
Recipientabc-supplier.testnet
Maximum amount5 NEAR
Mandate version1
Authority referencesha256:…
Established by owner BEFORE the invoice is processed
AI PAYMENT PROPOSALAWAITING PROPOSAL
AI
Agent requestSubmitted through proposal-only role
Recipient-
Amount-
Mandate version-
Authority reference-
No proposal submitted yet.
◎
WITNESS is readyChoose an attack. We will show what the deterministic policy decides and why.
WAITING
03 / AUDIT TRAIL

Payment black box

LOCAL EVENTS
Run a scenario to generate an audit trail.
THE ATTACK SURFACE

The incoming invoice

FICTIONAL DATA
ABC / SUPPLIESINV-3119
October delivery5.00 NEAR
Vendor addressabc-supplier.testnet
PAYABLE5.00 NEAR
Attack text appears here after a scenario is selected. The agent input is not trusted authorization.
Check the on-chain records (read only)
03 / INDEPENDENT CHAIN EVIDENCE

NEAR Testnet observer

Read actual finalized contract storage and verify transaction receipts. This section never invents a result.

TESTNET · CHECKING
Read-only: this panel reads the contract through public Testnet RPC. It holds no keys and never submits a transaction. The simulator above is a separate, local experiment.
Deployed contractNot configuredAvailable vault funds-Funds reserved in flight-
Mandate-
Proposal-
Select a real proposal ID to display its actual contract status.

-

Waiting for Testnet configuration…

On-chain audit entries

No Testnet events displayed.

Verify a real transaction receipt

Paste a transaction hash and its actual signing account. Only receipts addressed to the configured vault are accepted.

No receipt verified yet.