SYNTHETIC PROOF WALKTHROUGH

Pause a vendor remittance change for out-of-band verification

A synthetic review packet for changed customer-controlled remittance evidence without exposing bank details or claiming ownership verification.

See the three stepsRead the product contract →
NO KEY · NO UPLOAD · NO CUSTOMER DATAThis demonstration runs entirely in your browser using the visible synthetic fixture below.

THREE STEPS

Put the control before the consequential action.

The submitted remittance reference and fingerprint differ from the trusted customer baseline.

  1. 01

    Store a customer-controlled baseline

    The customer supplies a remittance reference and a one-way account fingerprint instead of a raw account number.

  2. 02

    Compare the proposed change

    The API checks the submitted reference and fingerprint against that organization’s own baseline.

  3. 03

    Verify outside the request channel

    A change produces REVIEW_REQUIRED and directs the customer to a previously trusted contact path.

VISIBLE SYNTHETIC CONTRACT

Inspect exactly what the workflow sees.

The input and output are representative of the named product contract. Copy them into an architecture note, test fixture, or internal review—never treat this browser-only demonstration as a live control result.

Customer-authorized input
{
  "vendor_reference": "northstar",
  "remittance_reference": "WIRE-NORTHSTAR-02",
  "account_fingerprint": "bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb"
}
Agent-readable output
{
  "status": "COMPLETED",
  "decision": "REVIEW_REQUIRED",
  "exceptions": [
    {
      "code": "REMITTANCE_DETAILS_CHANGED",
      "severity": "HIGH",
      "message": "Submitted remittance details differ from the customer-controlled vendor baseline.",
      "evidence": {
        "vendor_reference": "northstar"
      }
    }
  ],
  "next_action": "Pause the change and verify it through a trusted, out-of-band vendor contact."
}

WHAT THIS PROVES

Evidence for a stop point—not permission to act.

The comparison does not verify bank-account ownership, contact the vendor, update a vendor record, or authorize payment.

Decision
REVIEW_REQUIRED
Named exception
REMITTANCE_DETAILS_CHANGED
Evidence
vendor referencenorthstar
Next action
Pause the change and verify it through a trusted, out-of-band vendor contact.

KEEP BUILDING

Move from the synthetic fixture to the exact API contract.

Review the product inputs, outputs, errors, and safety boundary before using authorized data. The related implementation guide explains the design decisions behind the control.

Product contract →Implementation guide →Security posture →

Try the control through the supported buyer path.

Create a workspace, issue a scoped key, and test the control with synthetic or authorized data.

Start free workspaceExplore all four demos →