The PCI DSS v4.x transition illustrates why brokerage payment integration requires an identified security scope and ongoing ownership.

The verified record

The PCI Security Standards Council’s transition guidance said PCI DSS v3.2.1 was retired on 31 March 2024 and that the future-dated v4.x requirements would take effect on 31 March 2025. The guidance presented this as a period for organisations to understand the requirements and implement necessary changes. PCI SSC guidance on future-dated v4.x requirements ↗

The milestone concerns payment-data security requirements. It is not a brokerage licence, a merchant-account approval or a guarantee that a particular deposit will be accepted.

Why it matters

For a brokerage integrating card payments, a functioning checkout is only one visible part of the service. The business needs to establish which parties and systems handle payment data and who owns the resulting security work.

Using an external provider can change that scope, but a claim about reduced scope must be supported by the actual integration. A redirect, an embedded page and a server-side handling flow should not be treated as equivalent simply because the customer sees the same deposit amount.

What to check next

Before making a current compliance claim, consult the applicable standard, assessment route and payment-provider requirements. Map data movement and responsibility through the chosen integration. Historical transition dates can explain why controls changed, but they cannot certify the security of today’s website or substitute for evidence from its actual payment environment.