Ahead of the switch to widget 5.2, there are two things to check in your integration: the V5 script and the merchant token. Here are the answers to the most common questions.

What do I need to check before the switch?

Two things: that your site loads the V5 widget script, and that every widget carries the merchant token. If both are in place, the switch to 5.2 happens automatically.

How can I check quickly?

It takes about a minute. Open a product page, view the page source and search for scalapay-widget. There you can read the script address and the merchant-token attribute.

What happens on switch day?

With the V5 script and merchant token, the widget moves to 5.2 automatically. With the V5 script but no token, it stays on 5.1. With V3, V1 or a loader without a version, the old widget remains and 5.2 won’t arrive until the merchant updates.

Merchants using an e-commerce plugin or app

My shop runs on WooCommerce, PrestaShop, Magento or Shopify. What should I do?

Update the plugin. Check that you have the latest Scalapay plugin and, if not, install it from your platform’s marketplace or from developers.scalapay.com. Old versions load the V3 widget, which will never get 5.2.

Where do I enter the merchant token?

In the plugin’s widget settings, using the merchant token from the Merchant Portal. If the plugin has no merchant token field, it is out of date: update it first.

How do I confirm everything is correct?

Clear the shop cache, open a product page and check the source: you should see the V5 script and a merchant-token on every widget.

Merchants with a custom integration

The widget is added in our own code or theme. Which script should we load?

Exactly this one: https://cdn.scalapay.com/widget/v5/js/scalapay-widget.js

How do I spot an outdated script?

Any address containing /widget/v3/ or /js/scalapay-widget/ (V1) is outdated, as is the loader without ?version=V5, which loads V3.

Where does the merchant token go?

In every <scalapay-widget> tag (product, cart, checkout), as merchant-token='…' with the token from the Merchant Portal, spelled exactly.

Do I need to change the widget attributes too?

Yes, use the 5.2 data model. V3 attributes such as number-of-installments do nothing on V5 and should be removed.

In short

V5 script plus a merchant token on every widget: with these two in place, the switch to 5.2 happens on its own.