Introduction

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 make it easier to personalise the pages of the Sips Paypage 2.0 offer for merchants currently subscribed to the Sips Paypage 1.0 offer.

Who does this document target?

This document is intended for merchants having the WL Sips 1.0 offer.

The document lists the major differences between 1.0 and 2.0 payment pages, and guides the reader through his migration actions from 1.0 to 2.0.

For full details of the WL Sips 2.0 payment pages customisation, please refer to the Payment pages personalisation guide (Paypage) document.

Contacting the support

For any technical question or request for assistance, our services are available:

  • by telephone at: +33 (0) 811 10 70 33
  • by e-mail: sips@worldline.com

In order to facilitate the processing of your requests, please provide your merchantId (15-digit number).

The 2.0 payment pages assets

The WL Sips 2.0 payment pages have been rewritten on strong, scalable, accessible, portable and easily maintainable bases. This quality is ensured by a simple HTML code that respects web standards.

Today, with the increase of web terminals number of (PC, tablets, smartphones, TV, etc.), with a multitude of sizes, screen resolutions and levels of support of very diverse web standards introduction into the market, we need to design web products that will need to provide access to information in this wide range of contexts without degradation of the customer experience.

WL Sips payment pages have been revised to better adapt to this new reality.

An accessible code

The rewriting of the HTML code allows to apply the principles of web accessibility to ensure a comfortable access to all the information and functionality of the WL Sips 2.0 payment pages, regardless of the physical or material constraints that the final customer may present.

A multi-device interface

The technology of "Responsive Web Design" (RWD) was used to adapt, quite naturally, the design and the layout of the payment pages to the size of the terminal from which this technology is viewed. This adaptation affects as well the resizing of the contents as the page structures with the goal to create the good conditions of consultation of the site pages without loss in comfort or in efficiency for the customer, whatever is the used terminal, whether it is in mobility or not.

What do the 2.0 payment pages contain?

The differences

The 2.0 payment pages of course display the payment details collection page as well as the payment result page. The only difference with the 1.0 payment pages, is the selection of payment methods.

Indeed, with 2.0, the payment method selection page can (at the choice of the merchant) be hosted by the Payment server.

What to do when switching from 1.0 to 2.0?

You want to keep the display of the payment methods selection on your server

When registering your merchant ID with the WL Sips 2.0 offer, you will need to indicate your wish to NOT DISPLAY the selection of payment methods on the WL Sips server, so that the configuration of your Merchant ID is in accordance with the expected.

In the payment request, you will indicate the payment method selected by the customer in the paymentMeanBrandList field of the connector (see Data Dictionary).

You want to deport the display of the payment methods selection on the WL Sips 2.0 Payment server

When registering your merchant ID with the WL Sips 2.0 offer, you will need to indicate your wish to DISPLAY the selection of payment methods on the WL Sips server, so that the configuration of your Merchant ID is in accordance with the expected.

In the payment request, you will indicate the payment method selected by the customer in the paymentMeanBrandList field of the connector (see Data Dictionary).

How to customise your 2.0 payment pages?

The differences

The 2.0 pages customisation is based on a single principle - the creation of a header, a footer and a CSS, while the pages 1.0 offered 3 more or less advanced opportunities - the display attributes use contained in the request, the use of an HTML template, the use of CSS.

The same CSS will contain the adaptations to the different screen sizes via the instructions of the "media requests" type.

Full details on the customisation of the 2.0 payment pages can be found in the Payment pages customisation guide (Paypage).

What to do when switching from 1.0 to 2.0?

We don't recommend attempts to reproduce exactly the visuals of the 1.0 payment pages on the 2.0 payment pages. First of all, because it's impossible, since the HTML code is different between the 2 servers. Then, because it is unfortunate to deprive oneself of the new opportunities offered by the 2.0 payment pages, in particular on the aspect adaptability to the screens size.

In order to personalise your 2.0 payment pages, you must follow the instructions in the Payment pages customisation guide (Paypage), then check the rendering with the "Template Creation Tool" tool during the "test_template" tool of 1.0.

To move fast

Customising your payment pages is an optional step to run in 2.0. If you want to migrate quickly your flow or part of one part of your flow to 2.0, you can postpone building your customisation, and therefore use the default customisation of the offer you subscribed to.

In a second step, you will be able to leave the CSS of the offer to enrich it with your own elements of personalisation (colour, font, etc.).

What are the deliverables to transmit in order to customise your 2.0 payment pages?

The differences

Few noticeable differences, the deliverables remain images, CSS and file template.

How to switch from 1.0 to 2.0?

Once you are satisfied with your pages rendering, you will transmit the personalisation elements contained in the directory named TEMPLATE of the tool "Template Creation Tool".

Custompages tool use

You can also use our CustomPages customisation assistance tool. This tool allows you to realise your personalisation, to see the rendering, and according to the type of access to put your CSS directly in production on your shop without going through a request to our 1st level support.

You will find all the necessary details on the use of our CustomPages tool In the document Payment pages customisation tool: Custompages document.

Summary

Customisation opportunities table

Feature Description Payment 1.0 Payment 2.0
Validation tool Tool to visualise the rendering produced by the elements of personalisation of the payment pages. V V
Customisation by CSS Formatting payment pages with style sheets. V V
Payment methods selection page Display of the payment methods offered to the customer. V V
Multi-languages Pages displayed according to the language of the customer and differentiable personalisation elements by language. V V
Multi-screen Native adaptation of the payment pages to the screen size. X V
Compliance with HTML 5 / CSS 3 Native adaptation of the payment pages to the screen size. X V
receipt_complement field Display of the data contained in the receipt_complement field of the API, on the response page. V X
Data field option CARD_NO_LOGO Non-display of the card logo on the bank details page. V V
Data field option NO_COPYRIGHT Non-display of the footer copyright. V V
Data field option NO_DISPLAY_CARD Deleting the card number after clicking on "Previous". V V
Data field option NO_DISPLAY_CANCEL Non-display of the button "Cancellation - return to the shop". V V
Data field option NO_SSL_SYMBOLS Non-display of the sentence on the payment details page: "You are connected to a secure server, you can fill in your form with confidence". V V
Data field option NO_WINDOWS_MSG Non-display of the sentence on the response page: "Depending on your browser setting, a window indicating the return to the unsecured mode may appear. This has no impact on the confidentiality of the previously exchanged information". V V
Data field option NO_DISPLAY_URL Non-display of the URL of the merchant site on the response page. V V
Data field option NO_RESPONSE_PAGE_POST Non-display of the response page and the redirection to the merchant website in POST mode. V V
Data field option NO_RESPONSE_PAGE Non-display of the response page and the redirection to the merchant website in GET mode. V X