SYNTHETIC PROOF WALKTHROUGH

Flag duplicate transaction references before reconciliation

A synthetic normalization result over customer-provided statement records with no bank connection.

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.

Two supplied statement rows share the same normalized transaction reference.

  1. 01

    Supply statement rows

    The caller provides already authorized transaction records and a customer-controlled account reference.

  2. 02

    Normalize canonical fields

    The control normalizes references, direction, description, counterparty, currency, and dates.

  3. 03

    Expose unsafe source rows

    Repeated references and zero-amount rows return named issues before matching begins.

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
{
  "account_reference": "acct-fingerprint-2201",
  "transactions": [
    {
      "transaction_reference": "TX-2201",
      "posted_on": "2026-08-09",
      "amount": "-50.00",
      "currency": "USD",
      "description": "Northstar payment"
    },
    {
      "transaction_reference": "TX-2201",
      "posted_on": "2026-08-09",
      "amount": "-50.00",
      "currency": "USD",
      "description": "Northstar payment duplicate"
    }
  ]
}
Agent-readable output
{
  "status": "COMPLETED",
  "decision": "REVIEW_REQUIRED",
  "exceptions": [
    {
      "code": "BANK_TRANSACTION_DUPLICATE_REFERENCE",
      "severity": "HIGH",
      "message": "The supplied statement contains a duplicate transaction reference.",
      "evidence": {
        "transaction_reference": "TX-2201"
      }
    }
  ],
  "evidence": {
    "account_reference": "acct-fingerprint-2201",
    "transaction_count": 2
  },
  "next_action": "Deduplicate the source statement before reconciliation."
}

WHAT THIS PROVES

Evidence for a stop point—not permission to act.

Bank Statement Normalize never connects to a bank, retrieves a statement, verifies a balance, stores bank credentials, or posts a reconciliation.

Decision
REVIEW_REQUIRED
Named exception
BANK_TRANSACTION_DUPLICATE_REFERENCE
Evidence
transaction referenceTX-2201
Next action
Deduplicate the source statement before reconciliation.

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 →