Merchant log

A merchant log is the merchant’s own record of payment activity: the requests its platform sent to providers, the responses and callbacks it received, and the status it assigned to each payment. It is one side of three-way reconciliation, and usually the largest and most varied source a reconciliation has to read.

How it works

A merchant log grows with every step of a payment. The platform writes the outgoing request, the provider’s reply, every callback and the final status it decided on. An illustrative trail for one synthetic payment:

09:14:02Z  request   PAY-1A2B  Provider A  amount: 1500  CUR-1
09:14:05Z  response  PAY-1A2B  status: pending
09:15:40Z  callback  PAY-1A2B  status: success

Several records describe one payment. Reconciliation has to fold them into one line with one outcome before it compares anything.

Why it matters

The merchant log is what the merchant believes happened, and it is big. On one anonymised merchant day the logs held 1.5 million records. They folded into 790,948 events and 318,804 transactions. A log that drops callbacks or masks fields carelessly makes every later comparison weaker.

How to spot it

Pick ten recent payments and trace each one in your logs. Do you find the request, the provider’s reply and a final status for every one? Are amounts and identifiers readable, or damaged by masking? Do callbacks from every provider land in the same place?

Related terms

Callback · Provider statement · Three-way reconciliation · Anonymisation · How Reconora works

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