Normalize Payment Provider Payloads
Normalize Stripe, Adyen, and PayPal transaction JSON into one canonical schema
- Normalizes provider-specific transaction payloads
- Converts amounts, timestamps, and status enums
- Produces one deterministic downstream transaction schema
Paste a payment-provider payload — instantly preview a normalized transaction record locally in your browser.
Why this package exists
Common problems
- Each payment provider names the same concept differently — `id` vs `transaction_id`, `created` vs `created_at`, `customer` vs `customer_id`.
- Status values are provider-specific: Stripe uses `succeeded`, others use `completed`, `Authorised`, or `success`.
- Amounts arrive as strings, integers, or floats while downstream analytics and reconciliation systems expect stable numeric types.
- Currency casing and timestamp formats vary across providers and internal integrations.
When to use
Use this when ingesting transactions from multiple payment providers and you need one canonical downstream transaction schema for analytics, accounting, reconciliation, AI workflows, or internal APIs.
Expected outcome
A normalized JSON transaction payload with stable field names, normalized status enum, numeric amounts, and deterministic downstream structure.
Automatically detects
- Provider envelopes
- String amounts
- Mixed status enums
- UNIX or ISO timestamps
- Lowercase currency codes
What the wizard asks
4 stepsEach step shows your input, the question, and a preview of the output.
- 1
Which transaction fields should reach downstream systems?
Strip provider-specific noise and keep only the fields your canonical transaction schema requires.
- 2
Rename provider fields into canonical transaction fields?· Optional
Map provider-specific field names into a stable internal transaction vocabulary downstream systems can rely on.
- 3
Normalize provider-specific transaction statuses?· Optional
Map provider-specific statuses (`succeeded`, `Authorised`, `success`) into one stable downstream enum.
- 4
Normalize transaction amounts into numeric JSON values?· Optional
Convert amounts into stable JSON numbers downstream analytics and reconciliation systems can safely process.