Minor units

Minor units express an amount as an integer in the smallest unit of the currency, for example 15000 cents instead of 150.00. Payment providers use both forms, often without saying which. Reconciliation must know the unit for every message shape, because a wrong guess makes an amount a hundred times too large or small.

How it works

Minor units remove decimals from an amount. Major units keep them. The same payment can arrive in both forms from different sources. Illustrative, synthetic example:

merchant log  PAY-9A41  CUR-1  amount: 150.00   (major units)
callback      PAY-9A41  CUR-1  amount: 15000    (minor units)
statement     PAY-9A41  CUR-1  amount: 150      (major units)

All three describe one amount. A naive join reports two of them as different in money. Some currencies also have no minor unit, or more than two decimal places.

Why it matters

Minor units cannot be guessed from the number. 15000 may be a large payment in major units or a small one in minor units. A wrong guess is a hundredfold error that looks like a real discrepancy. On one anonymised merchant day, 190 message rules used major units and 51 used minor units. The unit belongs to the message shape, not to the provider as a whole.

How to spot it

  • Look for amount differences that are exact multiples of a hundred.
  • Check whether the field holds a decimal point or only an integer.
  • Compare one known payment across log, callback and statement.
  • Record the unit per message shape and currency, not per provider.

Related terms

Normalisation · Message shape · Canonical status · Callback · Normalizer

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