| |
What do the result codes in the card logs mean?
In listings of card logs, there are a few result codes that indicate
how the card's input was used in the action. Ideally, the only
events shown are confirmations.
The following list details what can be decided about an entered Sesame
confirmation code. Even if you can view these lists, then information
relating to other accounts may be hidden, for reasons of privacy.
- Confirm
- This is a confirmation that succeeded. Note that Sync also
indicates a succeeded confirmation.
If the transaction was confirmed with multiple cards, then those
other cards also indicate one of these success results.
- Wrong
- A wrong entry of a Sesame confirmation code is still recorded to
reserve its place in the sequence of confirmation codes. As a
result, the next attempt involves plugging in the card once more.
Entries are marked wrong to avoid that multiple guesses can be
made at the same Sesame code.
- Swallow
- The confirmation code was correct, but it was swallowed. This
is what happens when some other reasons makes it impossible to
complete the transaction; usually, it indicates that
another confirmation code for the same transaction
was entered wrongly.
- Sync
- This confirmation code is used to synchronise the server and the
card. It indicates that the Sesame code and the previous one (which
is marked Wrong) sufficed to resynchronise the card.
Note that Confirm also indicates
a succeeded confirmation. If the transaction was confirmed with
multiple cards, then those other cards also indicate one of these
success results.
- SynSwal
- This is the combination of Swallow with Sync. The code was
used to synchronise the server with the card, but it was swallowed
instead of being used to confirm a transaction.
If the last N entries of the card's log are Wrong, then a temporary lockout is set for the card. The lockout starts at the time of the last entry and takes a constant time multiplied by 2^N - 1. When attempting to enter a second code, the just-failed entry is ignored.
Posted on Tue, 02 May 2006, 10:49.
| |
|