# Every payment provider, one language.

Reconora’s normalizer reads each payment provider’s callbacks, responses and statements in their native format and translates them into one canonical model. On live merchant traffic it reads 96 providers; adding a new one is a configuration, not an integration project.

## Eight primitives in every payment message

Every provider transmits the same 8 primitives — only names, places and formats change:

1. The merchant’s ID (echoed back)
2. The provider’s ID
3. The status
4. The amount and its role (requested, paid, fee, net)
5. The currency
6. The event time
7. The error
8. The message type and channel (create, poll, callback)

## One example: as received → as translated

A provider callback arrives with the amount in minor units, the status in `payment.status`, two time fields and four different identifiers. The normalizer recognises the message by its structure, applies the provider’s rule, and emits one event: status SUCCEEDED, amount as an integer with currency and precision, time in UTC with its source, every identifier kept with its origin. A body damaged by the logger’s masking is repaired and flagged.

## Why it matters to you

- **New providers without a project.** A provider is described once by a rule; the engine is shared.
- **No silent format drift.** When a provider changes its message, a new shape appears and is flagged instead of being read as empty.
- **Safe by design.** Final statuses are assigned only by approved rules; an unknown value never becomes “paid”.

## Providers we read

96 providers from live merchant traffic — names are not disclosed — and more, including the providers listed on [our providers page](https://reconora.com/providers).

[Start a free pilot](https://reconora.com/pilot) · [Book a 20-min call](https://calendar.google.com/calendar/appointments/schedules/AcZssZ2qcg1D27PGeYQ91fuYaSo7oy6D4tQ0onTGhC2mSdAWZpCuMUozMxIan4qYWtSk56H-hZTTZAC7)

---
Source: https://reconora.com/normalizer · Updated 2026-10-16
