Microsoft, Marvell and Utimaco are changing who operates the payment HSM stack. Public preview establishes the architecture; production banks, service levels and pricing are still absent.
Microsoft, Marvell and Utimaco launched Azure Payment HSM v2 in public preview on September 17 in the western United States and western Europe. The service combines Marvell LiquidSecurity hardware, Utimaco Atalla payment software and Azure operations for PIN processing, card issuance, payment authentication and key management.
The useful change is operational responsibility. Azure's earlier Payment HSM offering used a dedicated hardware model that left customers with substantial lifecycle work. Version 2 is presented as a fully managed service, shifting provisioning, scaling and more of the operational burden into Azure and its partners.
Payment HSMs have resisted that migration because they sit directly inside transaction authorization and must meet specialized payment-security requirements. A conventional cloud HSM can protect general cryptographic keys without reproducing the payment functions and operational controls that banks and processors have built around dedicated appliances.
The service targets a concrete operating-cost pool: appliance refreshes, specialist administration, peak-capacity provisioning and resilience engineering. It also concentrates more dependency in Azure. A bank that moves payment cryptography into a managed service exchanges some internal operating burden for vendor and cloud-platform dependence.
Azure Payment HSM dates to 2022 and was built around dedicated bare-metal devices. Version 2 changes the operating model rather than inventing the workload. Banks can now compare the labor, refresh cycle and peak-capacity cost of dedicated infrastructure with a managed-service bill.
That comparison cannot yet be completed from public information. Microsoft, Marvell and Utimaco disclosed no production customers, pricing or service-level commitments. Public preview establishes the procurement option; the financial case starts when banks can compare an actual managed-service price and uptime contract with the cost of running the appliances themselves.