Skip to content
Novus Examples
json188 B

Webhook Payload — Stripe Payment (JSON)

SAMPLE stripe payment webhook JSON body for signature-verification and parser tests.

API testingJSON parsing
Preview, first 12 linesjson
{
  "id": "evt_sample_001",
  "type": "payment_intent.succeeded",
  "data": {
    "object": {
      "id": "pi_sample",
      "amount": 2500,
      "currency": "usd"
    }
  }
}

Specifications

Kind
webhook
Style
stripe-payment

Testing contract

Expected to pass
Scenario
Exercise Webhook Payload — Stripe Payment (JSON) in its api workflow. SAMPLE stripe payment webhook JSON body for signature-verification and parser tests.
Expected result
top-level keys are id, type, data; selected values: {"type": "payment_intent.succeeded"}. Declared feature checks: kind=webhook; style=stripe-payment.

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

“Webhook Payload — Stripe Payment (JSON)” is a deterministic Novus Examples fixture for API testing, JSON parsing. OpenAPI/Swagger specs, GraphQL SDL, JSON Schema, paginated and problem+json error payloads, and webhook samples, for testing API clients, mock servers, contract tests, and schema validators.

Documented properties for this file: JSON · 188 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("stripe-style-payment-webhook.json") as f:
    data = json.load(f)
print(type(data), len(data))

Related files

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