Checkout v2

Change UI Option

Walking you through switching from Seamless View to Redirect

Edit "Change UI Option" on GitHub

As parts of the PCI-DSS best practice becomes requirements with PCI-DSS v4 coming in April 2025, using the Seamless View integration to display the payment UI will give merchants more responsibilities than they currently have. This is because Seamless View is hosted by you. As the Redirect integration is hosted by Swedbank Pay, we also handle these responsibilities.

The updated requirements will include stricter controls and monitoring, particularly around the security of your checkout process. A script or other monitoring needs to be in place to verify that the checkout URL is correct and has not been tampered with. This is to avoid phishing or hijacking, and to secure that the URL provided is from us at Swedbank Pay.

See points 6.4.3 and 11.6.1 in the PCI-DSS link above for more.

Please note that this only applies to payment methods that are affected by PCI-DSS (Card, Vipps and/or Mobile Pay). If you only offer payment methods not affected by PCI-DSS (Invoice, Swish and/or Trustly), no actions are necessary. If you want to add PCI-DSS affected payment methods later, this is something you need to consider.

To learn more about how PCI-DSS affects you, we also have reading available in Danish, Finnish, Norwegian and Swedish.

If you currently have a Seamless View integration and don’t want the impending responsibilities, switcing to Redirect is normally possible, but the Checkin module used in Checkout v2 is only available using Seamless View. We strongly recommend switching to the newest version of Digital Payments and choose the Redirect UI option. We have written a migration guide to help you.