The EU’s PFOF ban under MiFIR Article 39a becomes fully effective 30 June 2026 — 12 days from publication. Germany’s temporary exemption (the only one granted among EU Member States) expires on that date, closing the last window for EU-regulated brokers to receive payment-for-order-flow from market makers.
Why this matters for the risk-management chapter. The PFOF ban is not primarily a payments story — it is an execution model story. Brokers that were running B-book or hybrid B-book/A-book models, supported by PFOF revenue from market makers, must now route client orders to external LPs as A-book. That transition changes the risk management procurement requirements structurally:
-
LP FIX execution report storage becomes mandatory. MiFID II Article 27 requires internal evidence of best execution. For A-book brokers, this means retaining the FIX execution report from each LP alongside the MT4/MT5 trade record. Risk vendors with native LP FIX connectivity (Centroid, oneZero, PrimeXM, TFB Trade Processor) have an inherent structural advantage over overlay analytics products.
-
Multi-LP exposure aggregation becomes operationally critical. A-book brokers routing to 3–5 LPs need real-time consolidated exposure views across all LP relationships. Chapter vendors with multi-LP aggregation depth: Centroid (400+ institutions, MT4/MT5/cTrader/FIX simultaneous connection), oneZero (Liquidity Hub 8.0, $250B+ ADV, 14M transactions/day), PrimeXM (120+ market makers + tier-1 banks, XCore engine).
-
B-book revenue models require recalibration. Brokers that do not fully transition to A-book — and there will be many in the Cyprus/EU market operating hybrid models — face stricter internal risk management requirements because the B-book revenue offset is reduced. Hybrid A/B risk segmentation (Brokeree’s core capability) becomes more critical, not less.
The Cyprus CySEC operator landscape. Most CySEC-licensed brokers were already running hybrid execution models with substantial A-book routing under ESMA leverage caps and MiFID II Article 27 obligations. The PFOF deadline primarily affects German-market-facing operators. For Cyprus-native operators, the practical impact is confirmation that the A-book trajectory is now fully mandated EU-wide — validating existing risk infrastructure investments.
Chapter vendor positioning post-PFOF.
| Execution transition requirement | Lead vendors |
|---|---|
| LP FIX execution report storage + best-execution audit trail | Centroid Risk, oneZero, PrimeXM |
| Multi-LP exposure aggregation | Centroid Risk (400+ institutions), oneZero (Liquidity Hub 8.0) |
| Hybrid A/B segmentation for operators not fully converting | Brokeree Risk (hybrid A-Book/B-Book segmentation native) |
| Stack-integrated A-book routing + risk | B2Risk (B2Prime LP + B2TRADER risk integrated) |
Operator action item before 30 June 2026. Verify your risk-mgmt vendor’s FIX execution report storage implementation. Specifically: (1) Does the vendor retain LP-side FIX execution reports alongside the MT4/MT5 trade record? (2) Is the timestamp resolution sub-second for Article 27 margin call + stop-out logging? (3) Does the vendor’s dispute-resolution data structure support CySEC inspection queries on best execution evidence?
The 30 June deadline is a procurement accelerator, not a wait-and-see event.