From 3c21df6c1a991d314e8f229f70a70a882b4bcf7d Mon Sep 17 00:00:00 2001 From: arebra Date: Wed, 25 Sep 2024 14:05:07 +0200 Subject: [PATCH 1/2] DEVP-452: First edition of UI migration --- .../display-payment-ui/ui-migration.md | 103 +++++++++++++++++ .../checkout-v2/ui-migration.md | 34 ++++++ .../payment-menu-v2/ui-migration.md | 109 ++++++++++++++++++ 3 files changed, 246 insertions(+) create mode 100644 checkout-v3/get-started/display-payment-ui/ui-migration.md create mode 100644 old-implementations/checkout-v2/ui-migration.md create mode 100644 old-implementations/payment-menu-v2/ui-migration.md diff --git a/checkout-v3/get-started/display-payment-ui/ui-migration.md b/checkout-v3/get-started/display-payment-ui/ui-migration.md new file mode 100644 index 0000000000..5584077980 --- /dev/null +++ b/checkout-v3/get-started/display-payment-ui/ui-migration.md @@ -0,0 +1,103 @@ +--- +title: Change UI Option +permalink: /:path/ui-migration/ +description: | + Walking you through switching from Seamless View to Redirect +menu_order: 7 +--- + +Due to changes in [PCI-DSS requirements][pci]{:target="_blank"} coming with v4 +in March 2025, using [Seamless View][seamless-view] to display the payment UI +will give you, as a merchant, more responsibilities than using our +[Redirect][redirect] integration. This is because Seamless View is hosted by +you. As the Redirect page is hosted by us, we also handle the responsibilities. + +To read more about how PCI-DSS affects you, we have further reading avaliable +in [Danish][da]{:target="_blank"}, [Finnish][fi]{:target="_blank"}, +[Norwegian][no]{:target="_blank"} and [Swedish][se]{:target="_blank"}. + +If you currently have a Seamless View integration and don't want the impending +responsibilities, switcing to Redirect is a very manageable task. Here's what +you need to do: + +#### Use Redirect Operation + +In the operations node of the [payment response][post-response], right next to +`view-checkout` which you should currently be using, you'll find +`redirect-checkout`. The corresponding `href` contains a url which leads to the +Redirect UI. All you need to do is send the payer to this address. + +{% capture response_content %}{ + "operations": [ + { + "method": "GET", + "href": "https://ecom.externalintegration.payex.com/payment/menu/b934d6f84a89a01852eea01190c2bbcc937ba29228ca7502df8592975ee3bb0d?_tc_tid=30f2168171e142d38bcd4af2c3721959", + "rel": "redirect-checkout", + "contentType": "text/html" + }, + ] +}{% endcapture %} + + {% include code-example.html + title='Redirect-Checkout Operation' + header=response_header + json= response_content + %} + +#### Remove Seamless View Code + +You can remove all code related to the `