Documentation / Platform glossary / Master File Key / Terminal Master Key
A master file key, also called a terminal master key, is payment-industry vocabulary for the top key in a PIN and terminal hardware security module hierarchy. It parallels cloud envelope encryption structurally, but the standards, hardware, and procedures are different.
In PCI PIN environments an MFK or TMK protects the zone and terminal keys that in turn encrypt PIN blocks and terminal traffic. The shape is familiar — an apex key protecting operational keys protecting data — but three things distinguish it from cloud key management.
The hardware is mandated. Keys live in certified hardware security modules under PCI PIN requirements, not in a software key service. The procedures are ceremonial. Loading or rotating an MFK typically involves documented key ceremonies with split knowledge and dual control, where multiple custodians each hold a component and no individual can reconstruct the key. The data is different. These hierarchies protect PIN blocks and card-present traffic between terminals, acquirers, and networks, not documents at rest.
The vocabulary itself is a frequent source of confusion. TMK, ZMK, BDK, and MFK all appear in payment documentation with meanings specific to that domain, and mapping them onto DEK and KEK terminology produces approximate translations at best.
Most enterprise SaaS never deploys these tiers, because they only apply when a system participates in card-present PIN processing. The term matters for recognition: encountering MFK or TMK in an assessment signals a payment context with its own standards, not the cloud envelope model, and the distinction prevents a conversation where both sides use the same words for different things.
Payment integrators and PCI assessors use this vocabulary, and engineers who know only cloud key hierarchies can misread it as a synonym for a master encryption key. It is a sibling pattern with different obligations, not an alternative name.
Recognizing which model is in play also clarifies scope quickly: a platform that does not handle PIN data has no MFK tier, and saying so is a clearer answer than describing an unrelated hierarchy.
QueryTek products handle documents and knowledge workflows rather than card-present PIN processing, so they follow cloud envelope patterns rather than PIN HSM segmentation. This term appears here as industry literacy; payment key ceremonies are outside product scope.
