Solution
The payment system
protects secrets.
Attackers target them.
Lokblok removes them.
PCI. EMV. HSMs. MFA. All built around one assumption: the key exists somewhere. Lokblok removes it entirely.
The Problem Nobody Fixes
The most advanced security frameworks in existence, all built around protecting a key that still exists.
The payments industry has hardened the environment around the key with HSM boundaries, key rotation, dual control, tokenisation, and MFA. But every major breach follows the same pattern:
The attacker doesn't break cryptography.
They reach the key.
The structural gap
PCI DSS hardens the environment around the key.
EMV improves how the key is used.
Neither eliminates the thing being attacked.
The Five Ways Payments Get Compromised
Different attacks. Same root cause.
Session hijacking
Active session tokens intercepted and replayed before expiry.
Device compromise
Terminal or endpoint malware extracts key material during processing.
Credential leakage
Stored credentials exposed via configuration errors, logs, or cloud misconfig.
Insider access
Privileged users or vendors access key material with legitimate credentials.
Server-side HSM misuse
Keys exploited via legitimate API calls from compromised application layers.
Every major attack vector succeeds by reaching a key that exists between operations.
The Lokblok Model
Zero-Persistence Cryptography.
Lokblok removes persistent keys entirely. Between operations, there is nothing to steal, nothing to compel, and nothing to harvest.
With Phantom Secrets™: what's removed
Instead
No vault to break into.
No attack surface between transactions.
You don't prove controls. You remove the condition.
How It Works
Four mechanisms. One coherent system.
Ephemeral key reconstruction: Phantom Secrets™Learn more →
Keys exist only during a transaction. Reconstructed inside the HSM or secure element, used, and destroyed immediately after. Nothing persists between operations.
Cryptographic workflow enforcement: ToughID™Learn more →
Every action requires a verified chain: identity, device, and context. Produces a non-repudiable audit record, not a log that can be altered, but a cryptographic proof.
Ephemeral authentication: Phantom Gate™Learn more →
No passwords. No long-lived FIDO keys. No API tokens. Each authentication event reconstructs a one-time key, verifies both client and server, then destroys the key.
Hardware enforcement: Toughkey™ / HSM / SIMLearn more →
All operations occur inside certified hardware. No key material ever leaves the boundary. The boundary isn't a policy. It's enforced by the hardware itself.
What This Means in Practice
Three risks that disappear entirely.
No keys at rest. Anywhere.
Not in HSM memory, MPC nodes, devices, or servers. There is no at-rest state. Keys reconstruct on demand and cease to exist immediately after.
No ceremony risk
Traditional key ceremonies move sensitive material and expose full keys during assembly. Lokblok uses Regen Tokens, which are public data. Custodians carry nothing. Keys assemble only inside hardware.
No dwell-time risk
In traditional systems, attackers sit inside infrastructure and harvest keys over time. With Lokblok, nothing exists to harvest. Time inside your infrastructure becomes irrelevant.
Payments Use Cases
Every payment model. Same architecture.
Card Infrastructure (PCI / EMV)
- ZMK, TMK, PEK never persist
- No exposure during key ceremonies
- No retroactive decryption risk
Stablecoin & Settlement Rails
- No persistent signing keys
- No irreversible loss from key compromise
- Human governance enforced cryptographically
Tokenisation Platforms
- Token service provider keys do not persist
- No breachable key layer
Authentication (3DS / WebAuthn)
- No long-lived device credentials
- Mutual attestation prevents relay attacks
Why Current Alternatives Aren't Enough
Every approach has a structural limitation.
HSM
Key persists inside the boundary. The boundary can be bypassed.
MPC / TSS
Shares persist across nodes. All nodes must be simultaneously compromised, which is difficult but not impossible.
FIDO2 / WebAuthn
Device keys persist. A compromised device compromises the credential.
Tokenisation
Root keys still exist behind the token vault.
Lokblok
Why This Matters Now
Payments are evolving: stablecoins, CBDCs, real-time settlement, AI-initiated transactions. When settlement is final, key compromise becomes catastrophic. The industry is scaling risk.
Lokblok changes the model
Regulatory Alignment
Lokblok doesn't bypass standards.
It fulfils their intent.
PCI DSS
- Eliminates stored key risk (Req 3.6 / 3.7)
- Stronger than procedural dual control
EMVCo
- Works with 3DS & Secure Payment Confirmation
- Adds ephemeral keys + mutual attestation
PSD2 / SCA
- Hardware-bound, ephemeral authentication
- Stronger than device-bound credentials
GDPR / eIDAS
- No stored identity artifacts
- Data minimisation by design
Commercial Impact
The payments industry built better locks.
Lokblok removes the vault.
Reduce systemic risk
No catastrophic key compromise events. The attack surface between transactions ceases to exist.
Improve compliance posture
Architectural alignment with PCI, EMV, and PSD2: not just policy compliance, but structural compliance.
Enable new payment models
Stablecoins, CBDCs, and agentic payments require a different security model. This is it.
Lower operational complexity
No rotation schedules. No backup processes. No key lifecycle overhead. Nothing to manage.
Products Used in This Solution
