Skip to content
Novus Examples
json112 B

Fintech Payment Intent (JSON)

Stripe-style payment intent SAMPLE JSON for checkout integration tests.

API testing
Preview, first 7 linesjson
{
  "id": "pi_sample_001",
  "amount": 4999,
  "currency": "usd",
  "status": "requires_payment_method"
}

Specifications

Domain
fintech
Amount Cents
4999

Testing contract

Expected to pass
Scenario
Exercise Fintech Payment Intent (JSON) in its fintech workflow. Stripe-style payment intent SAMPLE JSON for checkout integration tests.
Expected result
top-level keys are id, amount, currency, status; selected values: {"amount": 4999, "status": "requires_payment_method"}. Declared feature checks: domain=fintech; amount_cents=4999.

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

“Fintech Payment Intent (JSON)” is a deterministic Novus Examples fixture for API testing. 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 · 112 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("payment-intent.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.