Release 22.6

go directly to content

Search by keywords

Simplified migration to WL Sips 2.0

To search in the page use Ctrl+F on your keyboard

WL Sips is a secure multi-channel e-commerce payment solution that complies with the PCI DSS standard. It allows you to accept and manage payment transactions by taking into account business rules related to your activity (payment on despatch, deferred payment, recurring payment, payment in instalments, etc.).

The purpose of this document is to explain the migration to WL Sips 2.0.

This document is intended for merchants having the WL Sips 1.0 offer and wishing to keep their merchant_id.

It is intended to facilitate the migration to WL Sips 2.0.

Tip: after reading this document we invite you to carefully read the documentation tree structure available in appendix 2, this will allow you to read the documentation useful for your migration.
Attention: if you wish to opt for the "New merchantID 2.0" choice, we invite you to use the "Quick Start Guide" which will be more in line with your needs.
What remains after migration What changes after migration
Data and formats New format for requests and for automatic and manual responses.
New payment URL.
New cash management URL via Sips Office.
Transaction identification Operation with transaction_id (using the s10TransactionId field)
Cash management Same access to Sips Office Extranet.
Same cash management rights.
Admin user created to access to cash management from MEX
Reporting Unchanged reports format.
Access to extranets CustomPages
Ability to use the CustomPages extranet to prepare and test your page customisation.
Sips Download
Access to MEX is created for the downloading of the secret key.
Fraud Anti-fraud checks are maintained.
Registration procedure No re-enrolment of the merchant's shops.
Connectors New non-intrusive connectors to replace APIs.
New secret key (per shop) that replaces the WL Sips 1.0 certificate.
File transfer FTP account unchanged.
The remitter_id does not change.
No change in the naming or in the format of the request and response files.
Means of payment New international means of payment.
Means of payment only in 2.0.
Page customisation A new page customisation is implemented with the help of the CustomPages tool and WL Sips support.
Attention: so as to be compliant with the MIF and 3DSv2 regulations, brand choice and 3-D Secure are now mandatory features. We invite you to contact the support if your shops do not currently benefit from these features.

We have identified a list of crucial steps to successfully complete the migration from WL Sips 1.0 to WL Sips 2.0. These steps can be mapped as follows:

Diagram describing the different steps of the technical migration and the contractual modifications.

Avant la migration la transaction initiale est faite sur le site commerçant avec subscription 1.0 et les paiements récurrents sont opérés avec le batch Subscription 1.0. Après la migration, la transaction initiale C.I.T. est opérée sur le site du commerçant avec paypage 2.0 et le paiement récurrent M.I.T. est opéré avec Sips Office Batch 2.0 avec la fonction walletorder.

The purpose of this paragraph is to show you the successive technical steps you will need to follow so as to successfully complete your evolution to WL Sips 2.0.

You have a webshop in 1.0, so you have a merchant_id that allows you to identify yourself. All your transactions are carried out with this merchant_id and you get consolidated reports as well as an overview of all your transactions in the (Sips Office Extranet) extranet, all means of payment combined.

Step 1: prepare for migration

Prior to migration from 1.0 to 2.0, you should get in touch with the WL Sips Support:

  • by phone: 0 811 107 022 (0.05€ / min + price, Monday to Friday from 9am to 5pm)
  • by e-mail: sips@worldline.com

The support will perform the following steps:

  • registration of your administrative contact and technical contact on your shop. This step is intended to generate the users necessary to retrieve your secret key.
  • sending of an information e-mail. This e-mail includes the migration completion report to be returned duly filled out in step 4.

Step 2: integrate the 2.0 connectors and test with simulation data

This step requires technical knowledge. A basic knowledge of the standards for today’s web programming languages, such as Java, PHP or .Net, is required to implement the connection.

You will choose the connector you want to integrate. This choice is made according to your need. For example, if you are currently using WL Sips Payment 1.0, you can choose the Sips Paypage connector.

On the other hand, the integrator will have to choose the connector type: JSON, POST, or SOAP (for Sips Office).

Your integration will necessarily be with a transaction_id generated on your side. This configuration is mandatory so as to:

  • allow your shop to run with 1.0 APIs and 2.0 connectors
  • keep the formats of 1.0 reports

Informational table

Table 1. Shop in transactionId mode - You connect to WL Sips with a transactionId generated by you
Data Transaction creation via:
Sips Paypage Sips Office Sips Office Extranet
transactionId provided by you Standard processing Standard processing Offered by WL Sips, editable and displayed in red
Absent transactionId Reject code = 12 Reject code = 12 Reject code = 12
transactionReference provided by you Reject code = 12 Reject code = 12 N/A
Absent transactionReference OK OK N/A
Additional reference generated by WL Sips transactionReference transactionReference transactionReference
Response content s10TransactionId

The online documentation website provides you with dedicated documents for each connector in the 'Developers' section. We invite you to refer to the documentation tree structure available in Appendix 2 herein for reference documents. You can use the online documentation site for all additional documentation.

Tip: if you would like to customise your payment pages, you can use our tool CustomPages, which allows you to test and view how the pages are rendered. To do so, please refer to the CustomPages documentation in order to use the tool.
If you do not customise your page, the default template of the page will be applied.

After integration and to perform your tests, simulation data is available in the dedicated documentation of the connectors you integrate.

For the Sips Paypage connector, the simulation data consists of a URL, a merchant_id and a dedicated secret key, which will allow you to do some tests without impacting your current workflow.

Table 2. transactionId generated by you
Field Value
Your ID (merchantId) 002001000000003
Key version (keyVersion) 1
Secret key 002001000000003_KEY1

This is a simulation. So the transactions made will not be viewable in your Sips Office Extranet.

Tip: for the Sips Office connector, we suggest you contact our support.

Step 3: retrieve the secret key on MEX and go live

The first time you contacted our support, you were asked for technical contact details. Using this information, a MEX user was created on our download platform. A login e-mail was sent to the identified contact.


Worldline provides a secret key on MEX that helps secure exchanges between your site and the WL Sips server.

You are responsible for storing the key and must take all steps to:

  • restrict access to the key
  • backup the key in an encrypted manner
  • never copy the key to an unsecured disk
  • never send the key (e-mail, mail) unsecurely.

The compromising of the secret key (and its use by a malicious third party) would disrupt your normal webshop operation, including unjustified transactions and cash management operations (such as refunds).

The very same secret key is used on the various connectors.

If needed, you can also make a key renewal request via this extranet.

Once your website and/or application connection has been tested, you are now able to validate the production connection.

Prior to this, we recommend turning your site and/or application offline to prevent customers from making transactions during this validation phase.

To switch to the production server, you need to change the URL and use your webshop credentials: merchantId 1.0, secretKey and keyVersion.

Sips Paypage connector:

WL Sips URL JSON: https://payment-webinit.sips-services.com/rs-services/v2/paymentInit
merchantId merchant_ID 1.0
SecretKey Secret key you retrieve via the Sips Download extranet
keyVersion Secret key version retrieved from Sips Download (obviously 1 for the 1st key)

Sips Office connector:

WL Sips URL https://office-server.sips-services.com
merchantId merchant_ID 1.0
SecretKey Ssecret key you retrieve via Sips Download
KeyVersion Secret key version retrieved from Sips Download (obvioously 1 for the 1st key)

Your payment system will be fully operational.

Attention: in the event that you detect an anomaly (unidentified issue during the test phase of your internal developments), you can switch the flows back to WL Sips 1.0 via the APIs.
IMPORTANT: this technical cohabitation solution remains possible until the maintenance of the 1.0 APIs comes to an end. However, once you send us the migration completion report, the 1.0 APIs will be deactivated for your shop.
During this technical cohabitation phase, you must ensure the uniqueness of your transaction identifiers to avoid duplicates between the transactions generated via WL Sips 1.0 and the transactions generated via WL Sips 2.0.

Step 4: validate the migration completion

Once your website has been migrated to the 2.0 connectors, you must send a migration completion report to the support at sips@worldline.com. This report was provided to you in the informational e-mail sent at the time you made your migration request.

Tip: if your migration involves multiple shops, please note the relevant "merchant_ids" in the migration completion report.

Image illustrating the pv to be transmitted at the end of the migration.

In this document, the data to be provided are: the merchant_id, the title of your store and the name of your Worldline Sips Account Manager. You will have to fill in the text with your name, the name of your company as well as the date of completion of the migration. In the second part of the document, you will have to indicate the detailed choice of the evolution, i.e. the connector(s) that you have integrated. Finally, you will have to date and sign the document.

Your migration is now complete and you are eligible for 2.0 options and means of payment.

The WL Sips 1.0 service stops on 12/31/2021.

In this context, Worldline suggests you migrate to the WL Sips 2.0 service, which allows you to:

  • simplify the integration of WL Sips and standardise the connection methods with new state-of-the-art WL Sips connectors;
  • optimise the customer experience with new features and new customer interface ergonomics (Sips In-App application, webresponsive, etc.);
  • have more autonomy in the management of your transactions and your merchant settings with a new Extranet interface;
  • make your expansion in the global market easier with new means of payment;
  • take advantage of advanced features such as efficient anti-fraud, dashboard, etc.

In case you keep your merchant_id, the identification by transaction_ID is maintained, so you keep your logs in the old 1.0 format.

In addition, transactions with connectors will indeed be included in your 1.0 reports.

Attention: choosing this migration requires that the transaction_id be generated by the merchant through the s10TransactionId field and not by WL Sips.
S10TransactionId is an alternate transaction identifier that is compatible with WL Sips 1.0. It uniquely identifies a transaction over a day. The s10TransactionId/s10TransactionIdDate pair ensures the uniqueness of the transaction.

Some fields are not carried forward to 2.0. You need to take this into account in your implementation.

Please refer to Appendix 2: document tree structure

The customisation of the payment pages can be recovered if:

  • Customisation logo 1.0: currently, you don't specify the templateName in API 1.0. When you'll use the connector 2.0, you will have to specify in your request the parameter templateName = "custom-MerchandID" (the MerchantID is your identifier with 15 characters).
  • Customisation "template" or "css": currently you specify the templateName in API 1.0. You've generated your customisation with Custompages (or by sending to Worldline) whose name you will have to reuse in the templateName field.
Tip: we recommend that you work on your new page customisation using CustomPages and submit your customisation to our support for this customisation to be implemented.

It is recommended that you change the customisation of the payment pages to take advantage of the 2.0 payment pages.

A page customisation guide is provided along with the Custompages pages customisation tool.

Please refer to Appendix 2: document tree structure

The 1.0 Wallet base is quite usable with WL Sips 2.0.

This is the software object that incorporates the transactionId.

The s10TransactionReference field needs to be populated when a payment is made using an old 1.0 webshop.

The transactionReference field must not be populated.

Example with your own transactionId (typically when you increment the Ids from your database):

// $s10TransactionReference=array(
// "s10TransactionId" => "000001",
// // "s10TransactionIdDate" => "not needed", Please note that the date is not needed, WL Sips server will apply its date.
// );

Worldline provides a sample PHP code on Github that initiates a Sips Paypage payment on the simulation environment.

The list of means of payment available in 2.0 is provided on our online documentation website.

Please refer to Appendix 2: document tree structure

The fraud checks available in 2.0 are detailed in the "anti-fraud" guide.

Please refer to Appendix 2: document tree structure

The accepted currencies depend on the acquirer contract.

The expected currencies for Visa, Mastercard and Amex are listed in the Data Dictionary available on the online documentation.

Please refer to Appendix 2: document tree structure

Worldline provides simulation data, the details of which are in the connector documentation.

Once the simulation is validated, and so as to complete your migration, you need to implement your protection data: merchant_id, url and secret_key.

Your migration is considered successful if you do not get a WL Sips reject code.

From then on, the transactions are real and visible on the cash management extranet and in your reports. The funds will be remitted to your account. And if you have subscribed to the option, the transactions will be reconciled.

IMPORTANT: you must send the migration completion report to the support at sips@worldline.com.

Please refer to Appendix 2: document tree structure

Please find in this appendix a summary table of the reference documents available to accompany your migration:

Need Reference document
Connectors WL Sips Payment to Sips Paypage migration
Sips Office Server 1.0 to Sips Office 2.0 migration
Sips Office Batch1.0 to 2.0 migration
Pages customisation Migration of payment pages customisation
Reports 1.0 2.0 reports correlation
Fields 1.0 2.0 data correlation
Data dictionary Data dictionary
Online documentation Documentation en ligne WL Sips
Sips Office Extranet
Sips Download MEX
CustomPages CustomPages
Tip: if your migration is for the Subscription product, please read the 'Subscription 1.0 to Subscription 2.0 migration guide'.
Tip: if you would like to use Sips Office Batch 2.0, we suggest you read the corresponding documentation. However, please remember that the simplified migration allows you to keep Sips Office Batch 1.0.

This site uses trackers to improve your experience, perform analysis and researches on your use of WL Sips documentation website.
You have several options:
Closing this banner you refuse the use of trackers on your device.