nexo FAST calls it the Terminal Configuration Data: a stack of tables, one per subject. Each top-level block in the file – e2, eb, f0… – is one of those tables, and inside them the same DFxx tag does not mean the same thing from one table to the next. This tool resolves every field within its own block, cites the section it comes from, and decodes the ones that carry a bit table.
File format read: sepaConfig (XML).
The other way round: tick what you want enabled, get the value to write into the file. Useful to prepare a parameter set, or to check that a value someone is asking for really matches what everyone thinks it does. Same gesture as “build a tag” in the EMV Parser, but on the vocabulary of a configuration file.