Introduction

WL Sips is a secure, multichannel 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 subscription payment solution implementation until the release.

Who does this document target

This document is intended to help you implement the recurring payments for the services they provide to their customers (hereinafter referred to as subscribers).

The purpose is to present the features of subscription payments and explain how to implement them with the WL Sips solution.

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

  • Functional presentation
  • Functionality set-up guide
Note: WL Sips does not manage the subscribers personal details (first name, surname, address, age, email, telephone, etc.), just the payment details that let you debit or credit your subscribers.

Prerequisites

Subscription payments require your subscribers' payment details to be stored by WL Sips to ensure that you can make payments.

Therefore, here are some points to address before you can get started:

  • To comply with the GDPR, you must complete your internal personal data processing register, specifying that the card details are stored in WL Sips platform. For more information on the GDPR, please refer to our Sips information systems security .
  • Inform your customers that their recurring payment details and methods will be stored (duration, amount, frequency etc.).
  • Check with your acquirer that your contract supports recurring payments.

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).

Subscription service overview

Subscription payments have several steps:

  • Subscriber enrolment,
  • Subscriber payment,
  • Subscriber management,
  • Subscriber authentication.

Subscriber details Storage

When you record a subscriber in your information system, you should allocate a unique account ID that WL Sips will use to store the subscriber's payment details. You can then debit the subscriber on a recurring basis by file transfer or in online mode.

Diagram showing the principle of subscription payments with a card:

You manage the subscriber's ID, which is associated to your customer's account. WL Sips stores the subscriber's payment details in a secure PCI space called a wallet.

The diagram above also applies to subscription payments with an SDD mandate.

In this case, WL Sips stores the mandate ID in the wallet database.

The subscription service is based on the WL Sips wallet, a secure virtual wallet, where the subscriber's payment details are stored:

  • The wallet is a single payment method.
  • 1 subscriber = 1 wallet = 1 payment method.
  • Subscriber ID = merchantWalletId .

The payment methods compatible with recurring payments are:

  • Carte CB, Visa, Mastercard, Amex,
  • Mandat SDD (SEPA Direct Debit).

WL Sips stores in the wallet all the information you need to debit your subscriber based on their User ID:

  • CB, Visa, Mastercard
    • Card number
    • Expiry date
    • Card type
  • SDD mandate
    • Mandate ID
Note: every webshop has its own subscriber database by default.

However, WL Sips allows the same wallet database to be shared among several stores of the same brand.

If this applies to you, please contact technical support.

Subscriber enrolment

The subscriber enrolment involves recording subscriber payment details in the WL Sips wallet. The enrolment may or may not be associated with a first payment.

Subscribers can be enrolled via 3 interfaces:

  • Sips Paypage : you save the subscriber's payment details when the first payment is made from pages hosted by WL Sips .
  • Sips Office M2M: you manage your own pages for entering payment details and you use the online web interface to record the subscriber in the WL Sips wallet.
  • Sips Walletpage : you save the subscriber's payment details outside the context of a payment on the wallet management pages hosted by WL Sips .

Subscriber payment

Recurring payments are then made based on the subscriber's ID without you having to communicate any sensitive information.

Subscribers can be debited or credited via 2 types of interfaces:

  • Sips Office M2M: you connect to WL Sips via an online web interface for transmitting debit or credit requests.
  • Sips Office Batch : on each due date, you transfer a file to WL Sips containing the debit or credit requests of the subscribers.

Subscriber management

The subscription service is based on a single payment method wallet (1 wallet = 1 payment method).

Wallet management consist of the :

  • replacement of a payment method by deleting the existing wallet and creating a new one .
  • removal of a wallet and the payment details at the request of the subscriber (legal obligation).

Expired payment mean :

  • payment means and associated wallets expired from more than 3 months, are automatically removed from the wallet database

Subscriber authentication

In the subscription payment process, you should authenticate your customers before accessing the subscriber IDs stored in your customer database.

Once the authentication has been made, you transmit the WL Sips subscriber ID in the request via the merchantWalletId field.

Your management of the subscriber IDs attributed to your customers should:

  • guarantee a 1-1 relationship between the subscriber and the customer (1 customer = 1 subscriber) .
  • allow the storage of subscriber IDs.
Attention: you are responsible for subscriber authentication.

WL Sips manages the secure storage of subscriber payment details.

Pages customisation

To maintain the corporate identity of your e-commerce website, the Sips Paypage and Sips Walletpage interfaces can be customised.

Please view the Page Customisation Guide for more information.

Reporting

We encourage to use the version TAB20_V2 or higher of the transaction reports, in order to locate the merchantWalletId field.

For more information, please see the Reports Description Guide.

Choice of WL Sips connectors for subscriptions

Given that WL Sips offers several interfaces for enrolling subscribers and processing payments, it is worth assessing your business requirements in order to select the connectors best suited to your situation.

The table below helps you make your choice.

Use cases Sips Paypage Sips Office Sips In-App Sips Office Batch Sips Walletpage Sips Office Extranet BackOffice Recommendations for choosing the interface
Management of the enrolment pages
You outsource the pages for entering payment details to avoid the PCI requirements. V X X X V X If you use Sips Paypage to process your payments, you can take advantage of this existing integration to manage your subscriber enrolment. Otherwise use the Sips Walletpage to enrol your subscribers.
You manage the pages for entering payment details that you integrate into your subscriber enrolment process. X V V X X X Sips Office meets your e-commerce requirements. For m-commerce, we encourage the use of Sips In-App .
Enrolment with or without payment
You enrol the subscriber during a payment. V V V X X X Sips Paypage , Sips Office or Sips In-App depending on whether or not you have decided to outsource the payment details entry pages.
You enrol the subscriber outside the context of a payment. X V V V V X Sips Walletpage , Sips Office ou Sips In-App meet your requirements, depending on your decision to outsource or not the payment order entry pages.
Debiting or crediting the subscriber
You debit or credit your subscribers at fixed intervals (e.g. flat rates or services billed after consumption). X V X V X X The Sips Office Batch file mode is the connector used for the periodic batch processing of subscriber payments, but you could use Sips Office too.
You debit or credit your subscribers at varying intervals (e.g. prepaid services or the subscriber has to add money to the account before consumption). X V X X X X The Sips Office transactional mode is the connector used for debiting or crediting your subscribers at varying intervals.
Managing subscribers
Updating the subscriber's payment method The update is processed like a subscriber enrolment by registering the payment details in a new wallet. Reuse the same connector as the one to enrol subscribers.
subscriber X V V V V V Use Sips Office if you want the option to delete in real time and Sips Office Batch if you do not. If you do not want to automate this function, you can delete your subscribers from the BackOffice WL Sips .
Initialisation of the subscriber database
You migrate an existing database. X X X V X X Sips Office Batch allows you to initialise the subscriber database from an existing database.

Implementation

To implement WL Sips subscriptions, you should get a suitable Connector Guide.

Enrolling the subscriber with Sips Walletpage

With Sips Walletpage , you allow your subscribers to enrol outside of a payment context.

Description

  1. During the process of enrolling your subscribers, you redirect them to Sips Walletpage to enter their payment details. Subscribers select a payment method, provide their payment details, then confirm.
  2. WL Sips verifies the 3-D Secure.
  3. WL Sips performs anti-fraud checks.
  4. WL Sips sends an authorisation request to the Acquirer.
  5. WL Sips records the payment method data in the wallet if the anti-fraud checks are OK and the authorisation is accepted.
  6. WL Sips displays the home page containing a confirmation message. The subscriber may then see his or her payment method on the home page.
  7. WL Sips returns the manual and automatic responses containing the wallet content.

Setting the request

Sips Walletpage is the interface that allows subscribers to manage their wallets.

To respond to the subscription use case, you should populate the fields as follows:

Field Value setting as part of the subscription
merchantWalletId Subscriber ID
PaymentMeanBrandList List of the payment methods that you want to offer for subscriptions.
walletActionnameList Creation of wallet by adding a payment method (value = ADDPM).

Please refer to the Sips Walletpage guide to learn how to fill the request, depending on your business requirements.

Analysing the response

Status Response fields Action to be performed
Subscriber enrolled

walletPaymentMeanDataList contains 1 payment method

walletCreationDateTime populated

Store the following customer details in your subscriber database:

  • merchantWalletId
  • paymentMeanId
  • PanExpiryDate
  • maskedPAN

You can submit recurring payments.

Subscriber not enrolled

walletPaymentMeanDataList not populated

walletCreationDateTime not populated

Resubmit a wallet enrolment request.

Enrolling the subscriber with Sips Paypage

This is a typical Sips Paypage payment process, where the payment details are recorded in the wallet if the transaction is accepted.

Description

  1. To record the subscribers' payment details, you should redirect them to Sips Paypage , sending the transaction data in the request (amount, currency, etc.), as well as the subscriber ID ( merchantWalletId field).
  2. WL Sips displays the payment page, the subscriber provides their payment details, then confirms.
  3. WL Sips makes a 3-D Secure verification.
  4. WL Sips makes anti-fraud checks.
  5. WL Sips sends an authorisation request to the Acquirer.
  6. WL Sips records the transaction in the back office.
  7. If the transaction is approved WL Sips records the subscriber payment details in the wallet.
  8. WL Sips displays the payment receipt page with a confirmation message that the subscriber payment method has been registered.
  9. WL Sips returns the manual and automatic responses containing the transaction details, including the result of the subscriber registration in the wallet.
  10. WL Sips may or may not send the transaction for collection, depending on the parameters that you have configured in the payment request.
Note: due to regulatory constraints, you should first inform the subscriber that the means of payment is recorded and refer to the relevant CNIL notices.

Setting the request

This is a standard Sips Paypage request in which you send the subscriber ID ( merchantWalletId field) to register the payment details in the wallet.

To enrol a subscriber without an associated 1st payment, you send a transaction in validation mode without validating ( captureMode field = VALIDATION).

Please refer to one of the Sips Paypage Guides to learn how to populate the request, depending on your business requirements.

Analysing the response

WL Sips returns a typical Sips Paypage manual and automatic response.

The fields related to subscriber enrolment are as follows:

Status Response fields Actions to be performed

Transaction accepted

Subscriber enrolled

responseCode = 00

acquirerResponseCode = 00

paymentMeanId = 1

merchantWalletId = idem requête

Store the following customer details in your subscriber database:

  • merchantWalletId
  • paymentMeanId
  • PanExpiryDate
  • maskedPAN

You can submit recurring payments.

Transaction accepted

Subscriber not enrolled

responseCode = 00

acquirerResponseCode = 00

paymentMeanId = non renseigné

merchantWalletId = idem requête

The transaction was accepted but a temporary technical problem occurred during enrolment of the payment method in the wallet.

Transaction declined

Subscriber not enrolled

responseCode = XX (différent de 00) Please refer to the Sips Paypage Connector Guide to analyse the WL Sips response.

Enrolling the subscriber with Sips Office

Before recording the payment method in the wallet, you should have to check it first via a standard payment request.

Description

You manage the data entry for payment methods on your website.

  1. Step 1 : You send a request to WL Sips to verify the payment method before enrolling the customer.
    • The 3-D secure authentication to verify that the customer is the cardholder of CB, Visa, Mastercard cards.
    • Anti-fraud checks that you have configured according to your business rules (e.g. foreign cards, commercial cards, etc.).
    • Authorisation request to the acquirer to verify that the card is still valid (not stolen, lost etc.).
      1. WL Sips records the transaction.
      2. WL Sips may or may not send the transaction for remittance to the acquirer, depending on the elements provided in the request.
    • WL Sips sends you the results of the payment methods verification.
  2. Step 2 : Once the payment method has been verified, you send a second request to WL Sips to register the payment method in the wallet.

  3. WL Sips returns the payment method registration response.

The sequence described above applies to the Amex, Oney and SDD payment methods.

Setting the payment method verification requests

Use the methods below, depending on the verification level of the payment method to be enrolled.

Carte CB, Visa, Mastercard, Oney, AMEX

CheckOut service methods Verification type

cardCheckEnrollment

cardValidateAuthentication

3-D Secure authentication

cardCheckEnrollment

cardValidateAuthenticationAndOrder

3-D authentication and authorisation request with anti-fraud checks

SDD mandate

CheckOut service methods Verification type
directDebitOrder SDD authorisation request with anti-fraud checks

Please refer to one of the Sips Office guides corresponding to the selected connector (JSON or SOAP), as well as the Payment methods guides, to learn how to populate the request, depending on your business requirements.

Analysing the authentication response

cardValidateAuthentication method

Status Response fields Action to take
Authenticated cardholder holderAuthentResponseCode = 00 You can register the card in the wallet using the addcard method.
Failure to authenticate cardholder holderAuthentResponseCode=01 Tell the customer that their card number is invalid and ask them to enrol another payment method.
Other refusals holderAuthentResponseCode=XX

If 3-D Secure authentication is required for your business to enrol a card, ask the customer to enrol another payment method.

If the 3-D Secure authentication is not required for your business to enrol a card, you can proceed to card verification with a cardOrder request.

Analysing the authorisation response with anti-fraud checks

CardOrder, cardValidateAuthenticationAndOrder and directDebitOrder methods

Status Response fields Action to take
Transaction accepted

responseCode = 00

acquirerResponseCode = 00

You can register the card for the wallet using the addcard or addDirectDebit method.
Transaction refused responseCode = XX Tell the customer that their card number is invalid and ask them to enrol another payment method.

Setting the enrolment request for customer payment details

Use the methods below, depending on the payment method to be enrolled. The merchantWalletId field contains the customer ID.

Carte CB, Visa, Mastercard, Oney, Amex

Wallet service methods Type of action
addcard Adding a new card to the wallet

SDD mandate

Wallet service methods Type of action
addDirectDebit Adding a mandate to the wallet

Please refer to the adequate Sips Office guide, as well as the Payment methods guides, to learn how to populate the request, depending on your business requirements.

Analysing the enrolment response

Status Response fields Action to be performed
Subscriber enrolled

walletReponseCode = 00

paymentMeanId = 1

You can debit or credit your subscriber

Subscriber not enrolled

Invalid request

walletReponseCode = xx

paymentMeanId = not populated

Please refer to the Sips Office Connector Guide to analyse the WL Sips response

Enrolling the subscriber with Sips Office Batch

The Sips Office Batch interface involves the same enrolment procedure as Sips Office JSON/SOAP with one major difference:

Note: the cardholder 3-D Secure authentication during the means of payment verification step is not available with Sips Office Batch .

All other aspects outlined in Paragraph 3.1.2 also apply to Sips Office Batch .

Debiting the subscriber with Sips Office Batch

Once the subscriber is registered, you can debit him/her in offline mode with Sips Office Batch .

Description

You format a Sips Office Batch file using the WalletOrder method.

Each WalletOrder registration contains:

  • The ID of the subscriber to be debited ( merchantWalletid field).
  • The transaction data (amount, order reference etc.).
  1. You send the file to Sips via FTPS or SFTP.
  2. WL Sips retrieves the subscriber payment details stored in the wallet.
  3. WL Sips executes the anti-fraud checks that you configured for your store.
  4. WL Sips sends the authorisation requests to acquirers.
  5. WL Sips stores the transaction in the back office.
  6. WL Sips formats the response file and sends it to you.
  7. In the evening, WL Sips sends the payment collection of accepted transactions.

Please consult the Sips Office Batch XML or Sips Office Batch CSV guides to find out more about implementation (file structure, description of records, file transfer, error management etc.).

Setting the request

To generate a recurring subscription payment using the walletOrder method, you should complete the following fields:

Field Value Comment
merchantWalletID ˂Subscriber ID˃
paymentMeanId 1 The payment method ID in the wallet is mandatory even though the wallet contains only one payment method.
paymentPattern RECURRING_N Recurring payment to indicate to the acquirer that there is no 3-D Secure data and CVV.
cardCSCValue Not populated Recurring payment to indicate to the acquirer that there is no 3-D Secure data and CVV.

captureMode

captureDay

Not populated Payment collection the same evening

Please refer to Sips Office Batch XML or Sips Office Batch CSV Guides to learn how to complete the other fields for the request, depending on your business requirements.

Analysing the response

Status Response fields Action to be performed
Transaction accepted responseCode = 00 Check the next day in the transaction log that the payment has actually been sent ( transactionStatus = CAPTURED)
Transaction declined responseCode = XX Please refer to the Sips Office Batch Connector Guide to analyse the WL Sips response.

Debiting the subscriber with Sips Office

The Sips Office JSON/SOAP connector also offers the walletOrder method in message mode with the same rules involved in formatting the request and analysis of the response.

Please refer to Sips Office to find out more about the implementation.

Crediting the subscriber with Sips Office Batch

You can credit a subscriber based on their ID without reference to an initial debit transaction.

Note: this feature is supported only by CB, Mastercard and Visa cards.

Description

The Sips Office Batch solution allows batch payments to be made.

You format a Sips Office Batch file using the walletCredit method.

Each walletCredit record contains:

  • The ID of the subscriber to be debited ( merchantWalletOrderId field)
  • The transaction data (amount, order reference etc.).
  1. You send the file to WL Sips via FTPS or SFTP.
  2. WL Sips retrieves the subscriber payment details stored in the wallet.
  3. WL Sips sends the authorisation requests to acquirers.
  4. WL Sips stores the transaction in the back office.
  5. WL Sips formats the response file and sends it to you.
  6. In the evening, WL Sips sends the payment collection of accepted transactions.

Please consult the Sips Office Batch XML or Sips Office Batch CSV guides to find out more about implementation (file structure, description of records, file transfer, error management etc.).

Setting the request

To generate a recurring subscription payment using the walletCredit method, you should complete the following fields:

Field Value Comment
merchantWalletID ˂subscriber id˃
paymentMeanId 1 The payment method ID in the wallet is mandatory even though the wallet contains only one payment method.

Please refer to Sips Office Batch XML Sips Office Batch CSV guides to learn how to complete the other fields for the request, depending on your professional requirements.

Analysing the response

Status Response fields Actions to be performed
Transaction accepted responseCode = 00 Check the next day in the transaction log that the payment has actually been sent ( transactionStatus = CREDITED)
Transaction denied responseCode = XX Please refer to the Sips Office Batch Connector Guide to analyse the WL Sips response

Crediting the subscriber Sips Office

The Sips Office JSON/SOAP connector also offers the option to credit a subscriber using the walletCreditHolder method in message mode.

The rules involved in formatting the request and analysis of the response are the same as those for Sips Office Batch .

Please refer to Sips Office to find out more about the implementation.

Managing a customer's payment methods and account

With Sips Walletpage

Description

The Sips Walletpage interface allows the subscriber to autonomously manage his wallet. The following features are available:

  • consulting the contents of a subscriber account
  • adding a payment mean to a blank subscriber account
  • editing the payment mean of a subscriber account
  • deleting the payment mean from a subscriber account
  • updating a payment mean of a subscriber account
  • removing a subscriber account

Setting the request

All management features are available to the user by default. However, it is possible to reduce the scope of these features, by indicating the list of features required in the walletActionNameList field.

For the wallet management you should populate the fields below:

Field Value
merchantWalletId Customer ID
walletActionList List of proposed features on Sips Walletpage . If not populated, all the features are available

Please refer to the Sips Walletpage guide corresponding to the selected connector (JSON, POST or SOAP) to learn how to populate the request, depending on your business requirements.

Analysing the response

Status Response fields Action to take
Customer removed walletPaymentMeanDataList not populated
Customer not removed walletPaymentMeanDataList populated

You can update your information system with the new wallet content.

With Sips Office and Sips Office Batch

Overview

The "Wallet" service of the Sips Office interface allows the merchant to manage the wallet contents of his customers. The following features are available:

  • Obtaining the complete content of a subscriber account.
  • Obtaining details of a payment mean contained in a subscriber account.
  • Creating a new subscriber account.
  • Deleting a subscriber account.
  • Deleting a payment method from a subscriber account.

Using the Sips Office or Sips Office Batch interfaces, you need to manage the wallet management pages to allow your subscribers to manage their accounts.

Viewing the content of an OneClick account with Sips Office

Sips Office allows you to view customer details through a getWalletData request.

  • Setting the request
    To view the content of a wallet with the getWalletData method, you should populate the fields below:
    Field Value
    merchantWalletID Customer identifier

    Please refer to the Sips Office guide corresponding to the selected connector (JSON or SOAP) to learn how to populate the other fields for the request, depending on your business requirements.

  • Analysing the response
    Status Response fields Action to take
    Customer found in the wallet database

    walletReponseCode = 00

    walletPaymentMeanDataList filled with the payment methods recorded in the wallet

    The customer exists in the wallet.

    Analyse the walletPaymentMeanDataList field to access the customer payment method details
    • paymentMeanBrand
    • paymentMeanId
    • maskedPAN
    • PANExpiryDate
    Customer not found in the wallet database

    walletReponseCode = 25

    The account has been deleted or was not created.
    Other refusals

    walletReponseCode = xx

    Please refer to the Sips Office guide corresponding to the selected connector (JSON or SOAP) to analyse the WL Sips response.

Modifying a payment method of an OneClick account with Sips Office

Sips Office allows you to modify the alias of a customer payment method via the updatePaymentMean request.

  • Setting the request
    To modify a payment method via the updatePaymentMean request, you should populate the fields below:
    Field Value setting
    merchantWalletID Customer identifier
    paymentMeanId Sequence number of the payment method
    paymentMeanAlias New payment method alias

Please refer to the Sips Office guide corresponding to the selected connector (JSON or SOAP) to learn how to populate the other fields for the request, depending on your business requirements.

  • Analysing the response
Status Response fields Action to take
Alias modified

walletReponseCode = 00

walletActionDateTime populated

Customer not found in the wallet database

walletReponseCode = 25

The account doesn't exist.
Other refusals

walletReponseCode = xx

Please refer to the Sips Office guide corresponding to the selected connector (JSON or SOAP) to analyse the WL Sips response.

Deleting a payment method of an OneClick account with Sips Office

Sips Office allows you to delete a customer payment method via the deletePaymentMean request.

  • Setting the request

To modify a payment method via the deletePaymentMean method, you should populate the fields below:

Field Value setting
merchantWalletID Customer identifier
paymentMeanId Sequence number of the payment method

Please refer to the Sips Office guide corresponding to the selected connector (JSON or SOAP) to learn how to populate the other fields for the request, depending on your business requirements.

  • Analysing the response
Status Response fields Action to take
Payment method deleted

walletReponseCode = 00

walletActionDateTime populated

Customer/payment method not found in the wallet database

walletReponseCode = 25

Other refusals

walletReponseCode = xx

Please refer to the Sips Office guide corresponding to the selected connector (JSON or SOAP) to analyse the WL Sips response.

Deleting a customer with Sips Office

Sips Office allows you to delete a customer via the signOff request.

  • Setting the request

To delete a wallet with the signOff method, you should populate the fields below:

Field Value setting
merchantWalletID Customer identifier

Please refer to the Sips Office guide corresponding the selected connector (JSON or SOAP) to learn how to populate the other fields for the request, depending on your business requirements.

  • Analysing the response
Status Response field Action to take
Customer deleted walletReponseCode = 00 You can update your information system.
Customer not deleted walletReponseCode = xx Please refer to the Sips Office guide corresponding to the selected connector (JSON or SOAP) to analyse the WL Sips response.

With Sips Office Extranet

You can delete a payment method for a customer account via the Sips Office Extranet . This feature is protected by the access rights assigned to you upon registration. If you need this feature, but you don't have the access rights, please contact technical support.

Modifying the subscriber payment method

If the subscriber wishes to change his payment method (lost card, expired validity, ...), you must create a new wallet with a new subscriber ID to register the new payment details.

Handling the customers payment methods expiry

On a monthly basis, you will receive by email or SFTP an expired cards report. This report references customers whose payment methods are due to expire in 3 months.

Based on this expired cards report, you can alert your customers to update the payment methods recorded in their wallets.

Please note that you won't need this file to know the expiry dates of your customers payment methods. Indeed, when a customer enrols, you will receive information in response that you can store in your information system:

  • ID for the payment method in the wallet ( paymentMeanId field)
  • Payment method brand ( paymentMeanBrand field)
  • Expiry date ( panExpiryDate field)
  • Masked PAN ( maskedPan field)

For details of the expired cards report content, please view the "Report Description" document.

5 steps to getting started with Subscription

Step 1 - Subscribing to the service

Your store has not been registered to WL Sips .

If your store is not yet registered, you should complete the registration form (requesting the subscription service) and return it to Worldline .

Your store is already registered to WL Sips .

If your store is already registered to WL Sips , you should ask Worldline to activate the subscription service.

Configuration data of the subscription service.

  • Interfaces used for enrolment
    • Sips Paypage
    • Sips Walletpage
    • Office Server
    • Sips Office Batch
  • Interfaces used for debiting or crediting subscribers
    • Office server
    • Sips Office Batch
  • If a subscriber database is shared between several stores of the same brand, please give the brand ID.
Note: if your subscriber database is shared between several stores, you should state this in the registration form or inform technical support.

If this is not specified, WL Sips will set up a wallet database for your store only.

Step 2 - Implementing the service

When you have chosen the WL Sips interfaces that meet your needs (see section 3), you should integrate the Sips connectors to connect your site to WL Sips .

The previous section described how to use WL Sips within the framework of the subscription depending on the various connectors:

  • Name of methods
  • How to fill and analyse the subscription business fields

Please refer to the relevant connector guides to configure the payment requests based on your needs ( customerID , orderId , returnContext , etc.)

Step 3 - Testing the service in the acceptance environment

Once the implementation of the WL Sips connectors is complete, you can run tests to validate your WL Sips integration.

Contact technical support and ask them to configure your store on the acceptance environment and the transfer of files if you use Sips Office Batch .

Test data
merchantId 201000076660001
secret key 8yTiAEzvhl7xt3_oEbdaH9Y9NY9A4XpNEjkk6q6Dou4
key version 1
test cards see " Test cards " page

Server Test URL
WalletPage POST https://payment-webinit.test.sips-services.com/walletManagementInit
WalletPage JSON https://payment-webinit.test.sips-services.com/rs-services/v2/walletManagementInit
WalletPage SOAP https://payment-webinit.test.sips-services.com/services/v2/walletManagementInit
Attention:

the test webshop is configured in transactionReference mode, with no automated generation of the transactionReference . Therefore you need to send the populated transactionRefence in your test requests.

Step 4 Validating the service in production environment

You can now validate the connection to WL Sips in production environment.

Prior to this, we recommend that you isolate your website from the public, to prevent customers from making transactions during this validation phase.

You should change the URL to connect to the production WL Sips server, using the IDs received during registration for the merchantId, secretKey and keyVersion .

URL WL Sips URL of the WL Sips payment server received by email.
MerchantId Shop ID received by email.
SecretKey Secret key that you get from the Sips Download extranet.
KeyVersion Version of the secret key retrieved from Sips Download (logically 1 for the 1st key).
Tip: a common mistake is to forget one of these four settings, which always causes an error.

If you want to customise your payment pages or wallet management pages, please follow the procedure described in the Custompages document.

How to validate enrolment

Immediately

  • Submit an enrolment request based on the enrolment scenario that you have chosen.
  • Refer to the content of the wallet using the getWalletData of the Sips Office connector.
  • Resubmit the request with the same subscriber ID. Your enrolment should have been rejected owing to the fact that the wallet is based on a single payment method.

How to validate subscriber debit

Immediately

  • Submit a walletOrder request to trigger a subscriber debit.
  • View the transaction via Sips Office Extranet BackOffice using the transactionReference or transactionId .

The next day

  • Check that the transaction appears in the transactions report
  • Check your business account to make sure that the operation has been credited
  • Refund the transaction via Sips Office Extranet BackOffice (optional).

Two days later

  • Check that the refund operation appears in the operations report.
  • Check the debit on your business account after the refund.

How to validate subscriber credit

Immediately

  • Submit a walletCredit or WalletCreditHolder request to trigger a subscriber credit
  • View the transaction via Sips Office Extranet BackOffice using the transactionReference or transactionId .

The next day

  • Check that the transaction appears in the transactions report.
  • Check your account to make sure that the operation has been debited.

Step 5 - Launching the service in production environment

Once the transition in production environment has been validated, you can open your website to the public to enable your customers to use the OneClick service and to register.

Customer enrolment

During the day

  • Monitor acceptance rates (number of responseCode 00 per total number of transactions).
  • Check the nature of non-banking refusals.
    • Technical problem: responseCode 90, 97, 99
    • Fraud: responseCode 34, 3-D Failure
    • Maximum number of payment attempts reached: responseCode 75

The next day

  • Check that all transactions processed (accepted and refused) appear in the transactions report.
  • Check the operations you have made and remittances (if you have chosen this report option) in the operations report.

Subscriber debit

When you submit your first subscriber debits via Sips Office Batch or Sips Office :
  • Monitor acceptance rates (number of responseCode 00 per total number of transactions).
  • Check the nature of non-banking declines.
    • Technical problem: responseCode 90, 97, 99
    • Acquirer fraud: responseCode 34