Encoding table

An encoding table is the private key that links the codes in anonymised data back to real values: which provider hides behind a code, which currency behind CUR-2. In Reconora’s design it is created at the merchant’s site on first run, together with a secret, and it never leaves the merchant.

How it works

An encoding table is written by the anonymisation module the first time it runs at the merchant’s site. An illustrative fragment:

P-07   -> <provider name>    kept by the merchant
P-12   -> <provider name>    kept by the merchant
CUR-2  -> <currency>         kept by the merchant

The anonymised package carries only the codes. Reconora reconciles the codes and returns the result in the same codes, for example P-07 · CUR-2 · 3 lines missing from the statement. The merchant decodes it locally.

Why it matters

The encoding table is what keeps re-identification in the merchant’s hands. Without the table and the secret, the codes cannot be reversed. On one anonymised merchant day the package covered 96 providers and 29 currencies, and Reconora saw none of their names. The module’s full source code is given to the merchant, so the security team can confirm that the table is never sent anywhere.

How to spot it

Ask any vendor that offers anonymised processing three questions. Where is the mapping created? Who holds it? Can the vendor decode the data without the merchant? If the answer to the last one is yes, the vendor holds an encoding table too.

Related terms

Anonymisation · Merchant log · Provider statement · Security

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