Canonical status
A canonical status is one shared meaning for a payment’s state that replaces each provider’s own wording. Providers say paid, SUCCESS or confirmed for the same outcome. Translating them into one canonical value lets payments from every provider be counted and reconciled the same way.
How it works
A canonical status comes from a rule per provider: where the status sits in the message, and what each raw value means. An illustrative mapping:
Provider A transaction.status = "SUCCESS" -> SUCCEEDED
Provider B state = "confirmed" -> SUCCEEDED
Provider C status = "paid" -> SUCCEEDED
Provider C status = "hold_review" -> unknown, awaiting a person
The last line matters most. A value nobody has mapped stays unknown until a person confirms its meaning. It never becomes “paid” by guesswork.
Why it matters
Without canonical statuses, every report needs a hand-kept translation per provider, and new values slip through. On one anonymised merchant day, 318 raw status values, found under 39 different paths in the messages, reduced to 9 meanings. The full list of meanings is part of Reconora’s model and is not published.
How to spot it
Export the distinct status values per provider from your logs. Count them. Look for values your team maps by hand in a spreadsheet, and for values that appeared only recently. Each of those is a place where a payment can be misread.
Related terms
Normalisation · Message shape · No final status · Callback · The canonical model
Try it on one day of your data
One day of your data, reconciled, and the report stays with you whether or not you continue.
Updated