A laboratory finding is a symptom: "expected AAC, terminal requested ARQC", "field 55 tag 95 wrong". The root cause is somewhere in the trace. These worked examples show how to get from one to the other. Each one can be reproduced in the simulator and checked with the trace analyzer.
Reading a failed test log
Needs: Supporter
Worked examples: from a laboratory finding to the root cause in the trace.
This is a supporter feature. Create a free account, then try every supporter feature free for 7 days.
The opening of the article
In the full article
- Example 1 — "The terminal went online instead of declining"
- Example 2 — "CDA failed but the transaction was approved"
- Example 3 — "Field 55 tag 9F37 does not match"
- Example 4 — "Script results missing"
- A method that works
The rest of the article opens with a supporter pass, which you can try free for 7 days.