json4.1 KB

Fieldnote Supply Shop: Chargeback representment submission

Chargeback representment submission for Fieldnote Supply Shop. The whole case as one object: amounts, evidence pointers and timeline. The amounts object separates netExposure of 150.00 from cardholderTotal of 151.20, which differ by the 16.20 USD of tax, so a reader cannot confuse what the seller loses with what the cardholder paid.

Data import JSON parsing

Preview, first 50 linesjson

{
  "schemaVersion": 1,
  "generatedAt": "2026-09-08",
  "caseId": "CB-2026-0001",
  "orderId": "ORD-006",
  "currency": "USD",
  "reasonCode": "10.4",
  "reason": "Other fraud, card absent environment",
  "openedOn": "2026-08-28",
  "representmentDue": "2026-09-11",
  "submittedOn": "2026-09-08",
  "amounts": {
    "disputed": "135.00",
    "chargebackFee": "15.00",
    "netExposure": "150.00",
    "taxChargedSeparately": "16.20",
    "cardholderTotal": "151.20"
  },
  "evidence": [
    {
      "ref": "EV-01",
      "description": "Order record showing the order date, customer and status",
      "sourceSet": "wave one ecommerce",
      "sourceFile": "orders-export.csv",
      "sourceRecord": "ORD-006",
      "supports": "the order exists and was placed by the cardholder"
    },
    {
      "ref": "EV-02",
      "description": "Order line detail showing what was bought",
      "sourceSet": "wave one ecommerce",
      "sourceFile": "order-lines-export.csv",
      "sourceRecord": "LINE-011;LINE-012",
      "supports": "the order is 6 units across 2 lines totalling 135.00 USD"
    },
    {
      "ref": "EV-03",
      "description": "Payment capture line from the settlement",
      "sourceSet": "wave one ecommerce",
      "sourceFile": "settlement-transactions.csv",
      "sourceRecord": "ORD-006-CAP",
      "supports": "exactly 135.00 USD was captured on 2026-08-06"
    },
    {
      "ref": "EV-04",
      "description": "Shipping manifest entry showing dispatch",
      "sourceSet": "wave one ecommerce",
      "sourceFile": "shipping-manifest.csv",
      "sourceRecord": "SHP-2026-0006",
      "supports": "the goods were dispatched on 2026-08-07 to British Columbia, Canada"

… 144 lines total: download for the full file.

Specifications

Document Set: banking
Industry: finance
Source Kit: accounting-reconciliation
Entity: Fieldnote Supply Shop
Synthetic: true
As Of: 2026-09-08
Evidence Items: 8
Timeline Events: 7
Net Exposure: 150.00
Cardholder Total: 151.20

Testing contract

Expected to pass

Scenario: Parse the amounts object and check that disputed plus chargebackFee is netExposure and that disputed plus taxChargedSeparately is cardholderTotal.
Expected result: 135.00 plus 15.00 is 150.00, and 135.00 plus 16.20 is 151.20. The two totals are deliberately different numbers built from the same capture.

What is a .json file?

JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.

How to use this file

Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.

How to use this file for testing

“Fieldnote Supply Shop: Chargeback representment submission” is a deterministic Testaroo fixture for Data import, JSON parsing. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: JSON · 4,204 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.

Code examples

import json

with open("chargeback-representment.json") as f:
    data = json.load(f)
print(type(data), len(data))

Generated by generation/industry_documents_two.py. Free for any use, no attribution required, license.