No final status

A payment has no final status when the provider has not reported whether it succeeded or failed. The last known state is pending, created or in progress. It is not a loss and not an error. The payment is awaiting a callback, a status response or a statement line that settles it.

How it works

No final status is a state, not an outcome. Each provider reports progress in its own words. These words are mapped to a canonical status, and only some canonical statuses are final. Illustrative, synthetic example:

PAY-4C8A  Provider J  callback 1: status "INIT"       -> not final
PAY-4C8A  Provider J  callback 2: status "PROCESSING" -> still not final
(no further callback, no statement line yet)          -> no final status

The payment stays open until a final word arrives from any source.

Why it matters

No final status should never be counted as lost money or as success. Counting it as lost inflates discrepancies. Counting it as success hides risk. On one anonymised merchant day, 14,191 of 114,065 transactions in scope had no final status from the provider. Many later resolve through a statement. The ones that never do become questions for the provider.

How to spot it

  • Take the last status for every payment, not the first.
  • Separate final outcomes from progress states.
  • Age the open payments: hours old is normal, days old needs a question.
  • Check the statement before chasing a callback.

Related terms

Canonical status · Callback · Day edge · Timing difference · Reconciliation

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