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 upon shipping, deferred payment, recurring payment, payment in instalments, etc.).

The purpose of this document is to explain the CB means of payment integration into WL Sips .

Who does this document target?

This document is intended to help you implement the CB means of payment on your e-commerce site.

It includes:

  • functional information for you
  • implementation instructions for your technical team

To get an overview of the WL Sips solution, we advise you to consult the following documents:

  • Functional presentation
  • Functionality set-up guide

Understanding CB payments with WL Sips

General principles

France has its own CB acceptance network, separate from the global Visa and Mastercard networks. Most French cards are co-badged CB + Visa or CB + Mastercard, and therefore have 2 logos, CB and Visa or Mastercard.

To pay with a CB network card, cardholders have to provide their card details, namely:

  • Card number
  • Expiry date
  • Visual security code
  • If the cardholder's card and your merchant ID are enrolled in 3-D Secure, the customer will be required to enter a dynamic one-time use code, usually received on their mobile phone.

Acceptance rules

Available functionalities

Payment channels
Internet V Default payment channel
MOTO V
Fax V
IVS V
Means of payment
Immediate payment X
End-of-day payment V Default method
Deferred payment V Limited to 99 days, except for 3-D Secure which is limited to 6 days because of the liability shift rules.
Payment upon shipping V Limited to 99 days, except for 3-D Secure which is limited to 6 days because of the liability shift rules.
Payment in instalments V
Subscription payment V
Batch payment V
OneClick payment V

Authorisation request

The authorisation validity duration for cards in the CB networks is 6 days. In case of a deferred payment for a period of 6 days or less, WL Sips makes an authorisation request to the acquirer for the total amount of the transaction, which will be settled afterwards according to the mean of payment you have requested.

In the case of a deferred payment (non 3-D Secure) for a period beyond 6 days, WL Sips makes two authorisation requests to the acquirer:

  • the 1st online authorisation request, called “account verification”, allows to check the account status and validity without impacting the authorisation cap.
Note: the authorisation request must be supported by your acquirer, and you must have the appropriate option on your acquiring contract. Otherwise, a real authorisation for a small amount (for example, EUR 2.00 in the euro zone) is made to check the cardholder's account validity.
  • the 2nd authorisation request for the real amount, made during the bank remittance.

Payment remittance in the bank

Payments are remitted to a bank according to the payment terms you set. As standard, the remittance in bank is triggered at night as from 10 pm CET (Central European Time) via a file exchange with the acquirer.

3-D Secure

Overview

The Visa and MasterCard networks have established the 3-D Secure programme, ensuring the cardholder’s authentication during online payments in order to limit fraud.

The Visa and MasterCard networks make reference to the 3-D Secure programme by using the "Verified By Visa" and "MasterCard SecureCode" slogans. If you are a 3-D Secure programme member, the payment transaction is subject to authentication by the cardholder.

The bank that issued the card and the relevant network (Visa or MasterCard) will be involved in this authentication process.

This programme has several assets. In fact, you make sure that your customer is indeed the cardholder because he authenticates with his bank. For this type of transactions, you are provided with a payment guarantee, under certain circumstances depending on the banking regulation in force.

Limitations on differed payments

In the case of a differed payment using the 3-D secure authentication programme, the delay cannot exceed 6 days (if you request a delay beyond 6 days, the WL Sips system will automatically force it to 6 days during the payment process).

Deactivation on demand

When you subscribe to the 3-D Secure authentication programme, all 3-D Secure eligible payments will be processed using this authentication system. However, it is possible to deactivate the 3-D Secure authentication programme on demand, by populating a dedicated flag in the request.

Attention: beforehand, you must subscribe to the option allowing to deactivate the 3-D Secure authentication programme on demand.
This deactivation on demand is possible on the Sips Paypage interface only.
No liability shift will apply if 3-D Secure authentication is bypassed.

Account verification on your initiative

For INTERNET and MOTO channels, on the Sips Office and Sips Office Batch interfaces only, you are allowed to perform an account verification on your own initiative (not conditioned by the deferred payment delay). To do this, you have to set the transaction amount to “0”. Therefore, WL Sips will perform an account verification from the acquirer, and the transaction will be stored in the WL Sips information system, but won’t be remitted in bank.

Attention: the account verification system must be supported by your acquirer, and you must have the appropriate option on your acquiring contract. Otherwise, an attempt to perform an account verification on your initiative will be handled as a standard authorisation request with an amount of “0”.

Lost and stolen cards checking

If you have the required option, a card checking is done using a lost and stolen list provided by the acquirer. This checking will be carried out during the transaction validation or the remittance steps.

If the provided card is in the lost and stolen cards list during the validation, the operation is rejected.

If the provided card is in the lost and stolen cards list during the remittance, the transaction will not be remitted.

Attention: this checking must be supported by your acquirer. The checking prior to validation is carried out only if the transaction was not authorised on the same day but the transaction authorisation is still valid.

Choosing the brand for a co-badged card

As a payment acceptance solution, WL Sips 2.0 is subject to the European MIF Regulation (EU's OJ 2015/751 L123 of 19/5/2015). Among these rules, the "brand selection" requires you to offer customers with a co-badged card the choice of brand at the time of payment, which affects the payment page.

A co-badged card is a card that supports at least two brands. Most cards issued in France are co-badged with the CB brand. For CB acceptance, the possible combinations of co-badged cards are:

  • CB + Visa
  • CB + MasterCard
  • CB + VPAY
  • CB + Maestro
  • CB + Visa Electron

Thus, you must allow customers with a co-badged card to select the brand.

The screen below shows an example of a CB + Visa co-badged card, with the CB brand as default. The customer can change the brand by clicking on the link at the bottom of the screen.

Note: for cards that are not co-badged, no choice of brand is given.

If you performed the WL Sips solution integration before the MIF / Brand selection migration, the VPay and Electron brands have been assimilated into the Visa brand and Maestro into the MasterCard brand.

If you wish to differentiate between the Vpay, Visa Electron and Maestro brands, you must specify this during the store registration on Sips or make the request to the distributor.

The identification of these brands affects the returned payment response: the paymentMeanBrand field can take one of the new values VPAY, VISA_ELECTRON or MAESTRO.

When a duplication request is issued on a transaction that has been subject to a brand selection process, the new transaction will exploit the selection result from the initial transaction.

Reversal request

A reversal request aims to cancel the modification of the issuer authorisation cap.

This reversal request is always linked to an authorisation request.

Tip: the reversal request is available for acquirers accepting it (please contact us to have the list).

The reversal request is sent to the acquirer in the following case:

  • the merchant fully cancels the transaction;
  • the authorisation server doesn't respond positively to an authorisation request for the following reasons: "approved after identification" or "approved for partial amount";
  • no response has been received after an authorisation request (timeout);

Signing your CB acceptance contract

In order to offer the CB means of payment on your website, you have to sign a distance selling contract with your acquiring bank. Thereafter, you transmit us the contract number for recording in our information system.

Making a CB payment

WL Sips offers you three solutions to integrate the CB means of payment:

  • Sips Paypage which directly acts as the payment interface with customers via their web browser.
  • Sips Office which gives you the opportunity to display your payment pages and works through a server-to-server dialog.
  • Sips Office Batch which allows you to process batch payments.

The remittance modes available for a CB transaction are:

  • Cancellation mode: default mode allowing transaction remittance on a predefined date, called capture delay. When this capture delay is reached, the remittance is sent automatically. This delay is set via the captureDay field with its 0 default value (end-of-day payment).
  • Validation mode: you must validate the transaction to trigger the remittance. A capture delay must also be defined. When this capture delay is reached or exceeded, you will not be able to validate the transaction, which will therefore expire automatically.

The diagram below explains the different transaction statuses according to the chosen capture mode:

Making a CB payment with Sips Paypage

The payment process for Sips Paypage is described below:

Setting the payment request

The following fields have a particular behaviour:

Field name Remarks/rules
statementReference The value sent to this field will appear on your account statement ( Available only for some acquirers ).
fraudData.bypass3DS If set to “ALL”, the 3-D Secure authentication programme will not be applied during the payment.
Note: the field paymentMeanBrand can be set to VISA for Vpay and Electron cards and to MASTERCARD for Maestro cards.
Note: for the 3-D Secure v2 payments, it is recommended to populate some fields to foster the frictionless. Please refer to the 3-D Secure guide .

Analysing the response

The following table summarises the different response cases to be processed:

Status Response fields Action to take
Payment accepted acquirerResponseCode = 00
authorisationId = (cf. the Data Dictionary).
paymentMeanBrand = MASTERCARD or VISA
You can deliver the order.
Acquirer refusal acquirerResponseCode = (cf. the Data Dictionary). The authorisation is refused for a reason unrelated to fraud.
If you have not opted for the "new payment attempt" option (please read the Functionality set-up Guide for more details), you can suggest that your customer pay with another means of payment by generating a new request.
Soft decline acquirerResponseCode = A1 The acquirer has refused the payment because there was no 3-D Secure authentication.
Please try the payment again by activating the 3-D Secure authentication.
Refusal due to the number of attempts reached responseCode = 75 The customer has made several attempts that have all failed.
Refusal due to a technical issue acquirerResponseCode = 90-98 Temporary technical issue when processing the transaction. Suggest that your customer redo a payment later.

For the complete response codes ( responseCode ) and acquirer response codes ( acquirerResponseCode ), please refer to the Data dictionary .

Brand selection on Sips Paypage

In the case of Sips Paypage , the payment process and the brand selection are managed by Sips. In return, WL Sips notifies the merchant about the brand selection made by the customer through the following fields:

Field Description
paymentMeanBrand Brand selected for the transaction acceptance
paymentMeanBrandSelectionStatus

Brand selection method. This field takes the following values:

  • Empty: brand selection not activated for the shop.
  • "NOT_APPLICABLE": brand selection activated but transaction not eligible.
  • "APPLIED_DEFAULT": acceptance of the default brand (with no selection action by the holder).
  • "APPLIED_HOLDER": the holder specifically chooses the brand.

This field has been restored in the latest versions of the connector and of the transaction reports.

To activate the brand selection, you must first:

  1. Give your default brand choices for each co-badged card combination in order to configure the brand selection on the WL Sips server:
    • CB + VISA = CB or Visa
    • CB + MASTERCARD = CB or MasterCard
    • CB + VPAY = CB or VPay
    • CB + MAESTRO = CB or Maestro
    • CB + VISA ELECTRON = CB or Visa Electron
  2. Guarantee the customisation compatibility with the choice of brand in case you use your own customisation (via a merchant CSS).

Specific case: payment method selection page hosting by the merchant

If you host the payment method selection page, you must avoid confusion between the payment method and brand selections, for example the card logos grouping.

Specific case: dynamic brand filtering requested by the merchant

If you request dynamic brand filtering using via the paymentMeanBrandList field of the payment request, then the paymentMeanBrandSelectionStatus field calculation rules are:

Co-badged card? Filtering Holder’s action PaymentMeanBrand SelectionStatus
YES One of the card brands is not in the paymentMeanBrandList list. N/A NOT_APPLICABLE
YES All of the card brands are in the paymentMeanBrandList list. Default brand acceptance (no selection action) APPLIED_DEFAULT
YES All of the card brands are in the paymentMeanBrandList list. The holder specifically chooses the brand. APPLIED_HOLDER
NO / N/A NOT_APPLICABLE

You must control the dynamic payment method filtering to avoid impacting on the payment process and to be compliant with the purchase contract.

If the card entered is not compatible with the list of accepted cards then WL Sips does not accept the transaction and will invite the customer to try again. After 3 attempts, WL Sips rejects the transaction.

Recommendation: most of the CB cards are co-badged in France (CB-VISA, CB-VPAY, CBVISAELECTRON, CB-MASTERCARD and CB-MAESTRO), and we advise you not to separate the CBVISAVPAY-VISA ELECTRON-MASTERCARD-MAESTRO brands at the time of payment.

Making a CB payment with Sips Office

The payment process for Sips Office is described below:

Setting the payment request

To make a payment with Sips Office , you must use the cardOrder method.

In the case of a payment not secured by 3-D Secure, the following fields must be populated:

Field name Remarks/rules
cardNumber Mandatory
cardExpiryDate Mandatory, if specified on the card.
cardCSCValue Mandatory in some countries (3 digits)
Note: if allowed by the acquirer the CVV can be optional for transactions that use the MOTO payment channel.
The paymeantMeanBrand field can be populated with VISA for Vpay and Electron cards and with MASTERCARD for Maestro cards.

Brand selection on Sips Office

Transaction acceptance

In the case of Sips Office and Sips In-App for transaction acceptance, you can manage the brand selection. You must detect cards that are co-badged with the CB brand and offer a choice of brand to the cardholder, then send this choice to Sips by populating the following fields:

Field Description
paymentMeanBrand

Brand selected for the transaction acceptance. Mandatory field for Brand selection ( paymentMeanBrandSelectionStatus field populated).

  • If the holder has not made any specific brand choice then you indicate the default brand in this field.
  • In the event of a brand error, the transaction is declined (response code 14).
  • If the paymentMeanBrandSelectionStatus field is populated and the paymentMeanBrand field is empty, then the transaction is rejected (response code 30).
  • The Vpay and Electron brands must be associated with Visa and the Maestro brands with MasterCard (changes to come in an upcoming release).
paymentMeanBrandSelectionStatus

Brand selection method. This field takes the following values:

  • Empty: brand selection not activated by the shop (default value).
  • "NOT_APPLICABLE": brand selection activated but transaction not eligible.
  • "APPLIED_DEFAULT": acceptance of the default brand (with no selection action from the holder).
  • "APPLIED_HOLDER": the holder specifically chooses the brand.

This field is available in the latest versions of the connector and has been restored in the latest versions of the transaction reports.

For the detection of cards co-badged with CB, you must ask your acquirer to receive the cards reference file named "Liste d'acceptation enrichie VADS (pour le grand commerce / PAT)" (secure distance selling enriched acceptance list (for large retailers / PSPs), flow id SICB - CNFFHV2). This list allows you to identify the brands of a card from its BIN. Finally, you must avoid confusion between the payment method and brand selections, for example the card logos grouping.

Managing your CB transactions

Available cash operations

The following operations are available on CB transactions:

Cash management
Cancellation V Depending on your acquirer, a total cancellation can cause a reversal request sending.
Validation V Validation available on the partial amount of the transaction.
Refund V Refund available on the partial amount of the transaction and for amounts greater than the initial amount (unlimited refund).
Duplication V
Recycling V
Credit V

The diagram below informs you which cash management operation is available when a transaction is in a given state:

Viewing your CB transactions

Reports

The reports provided by WL Sips allow you to have a comprehensive and consolidated view of your transactions, cash operations, accounts and chargebacks. You can use this information to improve your information system.

The availability of CB transactions for each type of report is summarised in the table below:

Reports availability
Transactions report V
Operations report V
Reconciliations report V
Chargebacks report V
Note: for CB transactions, the paymentMeanBrand field is populated with the value CB.

Sips Office Extranet

You can view your CB transactions and perform various cash management operations with Sips Office Extranet .

Here are the details of a CB transaction: