How can there be no transaction if Sesame confirmed?

In some situations, Sesame confirmation codes are approved, but there is no transaction related to the confirmation. How can that happen?

In the process of approving a transaction, the first step is to process the Sesame codes, and only if those are accepted, to commit the transaction. It is possible that the transaction fails due to some unexpected cause, including its manual cancellation by the user.

Sesame confirmation states as noted in the card log are never changed after they are initially written, so the confirmation states keep stating the confirmation, even though no transaction is linked to them.

Posted on Thu, 04 May 2006, 16:08.


 
   ------ 8< ---------- 8< ----------- 8< ------ | OpenFortress*