SYNTHETIC PROOF WALKTHROUGH

Block the same vendor invoice from a second franchise location

A synthetic location-aware duplicate check against customer-provided franchise invoice history.

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 same normalized vendor, invoice number, amount, and currency already appear at another supplied location.

  1. 01

    Supply the location baseline

    The customer sends one invoice, its location and vendor references, and authorized cross-location history.

  2. 02

    Compare normalized identity

    The control checks vendor reference, invoice number, amount, currency, location state, and supplied vendor approval.

  3. 03

    Stop the second route

    A match at another location returns BLOCKED with the matched customer references.

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
{
  "invoice": {
    "vendor_name": "Northstar Supply",
    "invoice_number": "FR-2201",
    "currency": "USD",
    "total": "100.00"
  },
  "location_reference": "DEN-01",
  "vendor_reference": "northstar",
  "approved_vendor_references": [
    "northstar"
  ],
  "historical_invoices": [
    {
      "location_reference": "AUS-02",
      "vendor_reference": "northstar",
      "invoice_number": "FR-2201",
      "currency": "USD",
      "total": "100.00"
    }
  ]
}
Agent-readable output
{
  "status": "COMPLETED",
  "decision": "BLOCKED",
  "exceptions": [
    {
      "code": "FRANCHISE_CROSS_LOCATION_DUPLICATE",
      "severity": "CRITICAL",
      "message": "A matching vendor invoice already exists for another location in the supplied franchise history.",
      "evidence": {
        "matched_location_reference": "AUS-02",
        "matched_invoice_number": "FR-2201",
        "matched_total": "100.00",
        "currency": "USD"
      }
    }
  ],
  "evidence": {
    "location_reference": "DEN-01",
    "vendor_reference": "northstar",
    "history_records_checked": 1
  },
  "next_action": "Reconcile the original location and invoice record before routing a second bill."
}

WHAT THIS PROVES

Evidence for a stop point—not permission to act.

The API searches only history supplied in this request. It does not access another organization, ERP, franchise system, or payment record.

Decision
BLOCKED
Named exception
FRANCHISE_CROSS_LOCATION_DUPLICATE
Evidence
matched location referenceAUS-02matched invoice numberFR-2201matched total100.00currencyUSD
Next action
Reconcile the original location and invoice record before routing a second bill.

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.

RapidAPI provides the subscription, key, quota, and capped marketplace plan for this synchronous control.

Get an API key on RapidAPIExplore every synthetic demo →