Closed (fixed)
Project:
Commerce Unzer
Version:
3.0.x-dev
Component:
Code
Priority:
Major
Category:
Task
Assigned:
Reporter:
Created:
13 Aug 2025 at 13:20 UTC
Updated:
1 Dec 2025 at 09:14 UTC
Jump to comment: Most recent
Problem/Motivation
According to an email from Unzer the old Unzer service will be switched off and
only what they call "UnzerOne" will be available after end of 2025-09.
If I understand the migration wizard at https://docs.unzer.com/unzerone-migration/ correctly
that means that the v1 routes will no longer work and one needs to use the v2 routes.
Since we are not using the REST API directly but via the PHP-SDK
we need to use different classes from the SDK that hopefully talk to the new endpoints.
Proposed resolution
Change commerce_unzer to use the updated classes from the SDK.
The classes provide a different interface and features though, so they are not a drop-in replacement.
Comments
Comment #2
cspitzlayComment #3
cspitzlayComment #4
cspitzlayAccording to an answer I received from Unzer support only the old "heidelpay SGW and NGW" interfaces will be switched off.
The offsite payment gateway of commerce_unzer uses the REST API (indirectly, via the Unzer PHP-SDK) which will be supported after end of 2025-09.
I am still trying to get confirmation that this also applies to the paypage v1 route,
since Paypage v1 is marked as "legacy" in the Unzer documentation.
Comment #5
cspitzlayOk, paypage v1 will continue to work, although they recommend using v2.
They mentioned only a "soft" reason though: "technologically more up-to-date".
Comment #6
cspitzlayWe have been using the paypage v2 for a while now. No issues so far.