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

The purpose of this document is to explain how to implement the OneClick solution until the release.

Who does this document target?

This document is intended to help you to set up a secure solution for your regular customers to store their payment details for future purchases. It presents the OneClick payment features and describes how to implement them with the WL Sips solution.

The purpose of the OneClick solution is to facilitate the purchase process (and thus increase the conversion rate) by improving the customer experience, particularly for mobile payments.

The principle is to allow customers to pay on WL Sips payment pages in a single click, without having to re-enter their payment details for each purchase.

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

  • Functional Presentation
  • Feature Implementation Guide
Attention: WL Sips does not manage the customers personal information (first name, surname, address, age, email, telephone, etc.), just the payment details.

Prerequisites

The OneClick payment requires your customers payment details to be stored by WL Sips so you can accept payments.

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 .

Overview of the OneClick service

The OneClick payment has several steps:

  • enrolment of customer payment details
  • OneClick payment
  • management of customer payment details
  • customer authentication.

Storage of customer payment details

When you record a customer in your information system, you should allocate to him a unique account identifier ( merchantWalletId ) that WL Sips will use to store the customer's payment details. This ID will be used for subsequent payments.

A block diagram of the OneClick payment with a card :

The diagram above also applies to the OneClick payment with an SDD mandate, a PayPal account, or a Paylib wallet.

The OneClick service is based on the WL Sips wallet, a secure virtual wallet, PCI-compliant, where customer payment details are stored:

  • The wallet is a multi-purpose payment method.
  • OneClick identifier = merchantWalletId .
  • Payment method ID = paymentMeanSequence .

The payment methods that can be used with OneClick are:

  • CB, Visa, Mastercard, Amex, Bancontact, Oney cards
  • PayPal account
  • SDD mandate (SEPA Direct Debit)
  • Paylib wallet

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

  • CB, Visa, Mastercard, Amex, Bancontact, Oney cards
    • Card number
    • Expiry date
    • Card type
  • PayPal account
    • PayPal account identifier
  • Paylib wallet
    • Paylib wallet identifier
  • SDD mandate
    • Mandate ID
Note: every shop has its own customer database by default. However, WL Sips allows the same wallet database to be shared among several shops of the same brand.

If this applies to you, please contact technical support.

Enrolment of customer payment details

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

Customers can be enrolled via 4 interfaces:

  • Sips Paypage : the payment details are recorded during a purchase from the payment pages hosted by WL Sips .
  • Sips Office : you manage your own pages for entering payment details and you use the online web interface to record the customer in the WL Sips wallet (NB: the enrolment of PayPal or Paylib as a payment method is not available with the Sips Office interface).
  • Sips Walletpage : the payment details are recorded, outside of a purchase, from the wallet management pages stored by WL Sips .
  • Sips In-App : you record the customer payment details during the first payment made through your mobile application.

OneClick payment

For subsequent payments, you transfer the customer ID in the requests, so that WL Sips can find payment details, which have already been recorded in the wallet.

Attention: if the customer ID is not transmitted in the request or if the transmitted value is not known to WL Sips , the customer will pay in a classic way and not in OneClick mode.
3 types of interface for debiting customers:
  • Sips Paypage : for each purchase, you transmit the customer ID in the payment request.
  • Sips Office : you connect to the WL Sips via an online web interface for transmitting debit requests.
  • Sips In-App : for each purchase, you transmit the customer ID in the payment request.

Management of customer payment details

To complete the enrolment of payment methods and their use for making purchases, you can manage the content of the wallets. Several interfaces give you access to the wallet.

5 types of interface for managing the wallet content:

  • Sips Paypage : customers can modify their wallets during a purchase.
  • Sips In-App : customers can modify their wallets, inside or outside a purchase.
  • Sips Walletpage : customers can modify their wallets, outside of a purchase.
  • Sips Office : merchants can make changes to customer wallets.
  • Sips Office Extranet : merchants can delete payment methods from their customer wallets.

Expired payment mean :

  • if the payment mean is expired, it is not selectable on the OneClick payment page
  • payment means expired from more than 3 months, are automatically removed from the wallet database

Customer authentication

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

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

Your User IDs management allocated to your customers should:

  • guarantee a 1-1 relationship between the customer and their User ID (1 customer = 1 OneClick User ID).
  • allow the permanent storage of OneClick User IDs.
Attention: customer authentication is your responsibility.

WL Sips manages the secure storage of customer payment details.

Pages customisation

To maintain the graphic charter of your e-commerce website, the Sips Paypage and Sips Walletpage interfaces pages can be customised.

Please view the Payment pages customisation guide (Paypagel) for more information.

Reporting

For more information, please see the reports description guide.

Choice of OneClick connectors

WL Sips offers several interfaces for enrolling customers and processing payments. It is therefore helpful to analyse your business requirements when choosing the most suitable connectors for your circumstances.

The table below will help you make your choice.

Interfaces
Use cases
Sips Paypage Sips Office Sips In-App Sips Walletpage Sips Office Extranet Recommendations for choosing the connector
Management of the enrolment pages
You outsource the pages for entering payment details to avoid the PCI requirements. V X X V X If you use Sips Paypage to process your payments, you can take advantage of this existing integration to manage your customer enrolment.
If not, we recommend the use of Sips Walletpage .
You manage the pages for entering payment details that you integrate into your customer enrolment process. X V V X X Sips Office meets your e-commerce needs. For m-commerce, we recommend the use of Sips In-App .
Enrolment with or without payment
You allow your customers to enrol their payment methods during a purchase. V V V X X Sips Paypage , Sips Office or Sips In-App meet your needs, depending on whether or not you have decided to outsource the payment details entry pages.
You allow your customers to enrol their payment methods outside of a purchase. X V V V X Sips Walletpage , Sips Office or Sips In-App meet your needs, depending on whether or not you have decided to outsource the payment details entry pages.
OneClick payment
You outsource the payment pages. V X X X X Sips Paypage meets your need.
You manage the payment pages on your website or mobile application. X V V X X Sips Office meets your e-commerce needs. For m-commerce, we recommend the use of Sips In-App .
Crediting the customer
You need to credit one of your customers outside of a refund context. X V X X X Sips Office meets your need.
Managing your customer payment details
A customer wants to change the alias of one of their payment methods. V V X V X Reuse the same interface as the one used for enrolment. However, if you use Sips In-App for the enrolment, we recommend using Sips Office in this case.
A customer wants to delete one of their payment methods. V V V V V Reuse the same interface as the one used for enrolment. However, if you use Sips In-App for the enrolment, we recommend using Sips Office in this case.
If you cannot, or do not want to develop access to the delete function for your customers, you can delete the payment method from your customers' wallets from the Sips Office Extranet .
A customer wants to delete his wallet. X V X V X If you already use Sips Walletpage to process other use cases, you can keep this interface to let your customers delete their wallets.

Implementation

In order to implement the OneClick , you should get a suitable connector guide to learn about the technical details of implementation.

Enrolling your customer payment details 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

Here is an example of payment process valid for the payment methods CB, VISA and MASTERCARD.

1.To record your customer payment details, you should redirect them to Sips Paypage , sending the transaction details in the request (amount, currency, etc.), as well as the customer ID ( merchantWalletId field).

2. WL Sips displays the payment page, the customer provides their payment details then confirms.

3. WL Sips proceeds with 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 customer payment details in the wallet.

8. WL Sips displays the payment receipt page with a confirmation message that the customer payment method has been recorded.

9. WL Sips returns the manual and automatic responses containing the transaction details, including the result of customer registration in the wallet.

10. WL Sips may or may not send the transaction for remittance, depending on the settings that you have configured in the payment request.

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

Setting the request

To enrol a customer for the OneClick service via Sips Paypage , you should populate the fields below:

Field Value setting
merchantWalletId Customer unique ID

Please refer to one of the Sips Paypage guides corresponding to the selected connector (JSON, POST or SOAP) to learn how to populate the request, depending on your business requirement.

Analysing the response

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

The following fields are related to the customer enrolment:

Status Response fields Action to take
Transaction accepted Customer enrolled

responseCode = 00

acquirerResponseCode = 00

paymentMeanId = sequence number of the payment method

merchantWalletId = same as request

walletType = MERCHANT_WALLET

Store the following customer details in your customer database:
  • merchantWalletId
  • paymentMeanId
  • panExpiryDate
  • maskedPAN
Transaction accepted Customer not enrolled

responseCode = 00

acquirerResponseCode = 00

paymentMeanId = not populated

merchantWalletId = same request

walletType = not populated

Transaction accepted but the customer payment method has not been enrolled for the following reasons:
  • the customer did not want to register their payment method.
  • the customer entered a virtual card.
  • the maximum number of authorised payment methods for the wallet has been reached.
  • a temporary technical problem occurred during the enrolment of the payment method in the wallet.
Transaction declined Customer not enrolled responseCode = different from 00 Please refer to the Sips Paypage guide corresponding to the selected connector (JSON, POST or SOAP) to analyse the WL Sips response.

Enrolling your customer payment details with Sips Office

Before recording the payment method in the wallet, you should have to check it first via a 3-D Secure authentication request and via a standard payment request.

Note: please note it is not possible to enrol a PayPal account nor a Paylib wallet in the wallet with Sips Office .

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 take
Customer enrolled

walletReponseCode = 00

paymentMeanId = sequence number of the payment method

You can complete customer registration in your information system

Customer not enrolled

Invalid request

walletReponseCode = xx

paymentMeanId = not populated

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

Enrolling your customer payment details with Sips Walletpage

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

Description

1. During the process of enrolling your customers, you redirect them to Sips Walletpage to enter their payment details. Customers select a payment method, provide their payment details, then confirm.

2. WL Sips proceeds with 3-D Secure verification.

3. WL Sips makes anti-fraud checks.

4. WL Sips sends an authorisation request to the acquirer (which does not lead to a payment).

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. Customers can then see their payment method on the home page.

7. WL Sips returns the manual and automatic responses containing the wallet content.

Setting the request

Walletpage is the interface that allows customers to manage their wallets. To enrol a customer for the OneClick service via Sips Walletpage , you should populate the fields below:

Field Value setting
merchantWalletId Customer unique ID
PaymentMeanBrandList List of the payment methods that you want to offer for OneClick payment.

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

WL Sips returns a manual and an automatic response. The 2 responses are sent through 2 different URLs. The automatic response is always sent, as soon as the URL has been filled in the wallet management request. The information contained in the manual and automatic responses is strictly identical.

Status Response fields Action to take
Customer enrolled walletPaymentMeanDataList and walletCreationDateTime entered by the customer. Store the following customer details in your customer database:
  • merchantWalletId
  • paymentMeanId
  • panExpiryDate
  • maskedPAN
Customer not enrolled walletPaymentMeanDataList not populated
walletCreationDateTime not populated
Resubmit a customer enrolment request.

Enrolling your customer's payment details with Sips In-App

Before you register the means of payment in the wallet, you are first required to check it via a 3-D Secure authentication request and a standard payment request.

Flow description

The registration of a card in the wallet is a 4-step process:

  • checking the 3-D Secure enrolment of the customer's card
  • redirecting the customer to their bank's ACS
  • sending the 3-D Secure authorisation request (with or without payment)
  • adding the card in the wallet

Initialising the request for registration of payment details

You initialise the payment using the walletInitialize method. Apart from the mandatory data of this method, here are the request data you need to pay attention to.

Field name Value setting
merchantWalletId Customer's unique identifier
sdkOperationName ADDCARD

Analysing the initialisation response from the customer's payment details registration

Use cases Response fields Action to take
Successful initialisation of the registration request redirectionStatusCode = 00 You send the necessary data to the mobile application for further card registration:
Invalid initialisation request redirectionStatusCode = 12, 30 One or more data in the request are invalid. Check the redirectionStatusMessage field and fix the incorrect value.
WL Sips server temporarily unavailable redirectionStatusCode = 99 Resubmit the request. If the issue lasts, please alert Worldline 's technical support.

Setting up the payment details registration request

If the initialisation of the registration request has succeeded, send the request via the addCard method of the Sips In-App SDK. Apart from the mandatory data of this method, here are the request data you need to pay attention to.

Field name Value setting
cardExpiryDate Value already retrieved.
cardNumber Value already retrieved.
paymentMeanBrand Value already retrieved.
redirectionData Value retrieved as a response to walletInitialize .
redirectionUrl . Value retrieved as a response to walletInitialize .

Analysing the payment details registration response

Use cases Response fields Action to take
Card registered in the wallet inAppResponseCode = 00

paymentMeanId = sequence number of the means of payment added to the wallet

Display to the customer the confirmation of their successful card registration.
Temporary technical issue inAppResponseCode = 99 Resubmit the request. If the issue lasts, please alert Worldline 's technical support.
Invalid request inAppResponseCode = 12 One or more data in the request are invalid. Check the errorFieldName field and fix the incorrect value.

Paying on Sips Paypage with OneClick

The payment phase in OneClick mode is possible if the buyer has previously registered a payment method in their WL Sips wallet. During the OneClick payment kinematic, the customer does not have to re-enter their payment details, they simply select one of the payment methods previously recorded in the wallet and enter the security code.

Description

1. You redirect the customer to Sips Paypage , sending the transaction data in the request (amount, currency, etc.), as well as the unique customer ID ( merchantWalletId field).

2. WL Sips displays the payment page, the customer provides their payment method, enter the security code, then confirms.

3. WL Sips proceeds with 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. WL Sips displays the payment ticket page with a payment confirmation message.

8. WL Sips returns the manual and automatic responses containing the transaction details, including the result of the customer registration in the wallet.

9. WL Sips may or may not send the transaction for remittance, depending on the parameters that you have configured in the payment request.

Setting the request

To offer OneClick payment via Sips Paypage , you should fill the fields below:

Field Value setting
merchantWalletId Customer unique ID
fraudData.bypass3DS

MERCHANTWALLET if you want to deactivate 3-D Secure authentication during a OneClick payment.

Otherwise not populated

IMPORTANT: given the recent regulation of the 14th of September 2019 that makes authentication mandatory for online payments, by bypassing the 3-D Secure authentication, you are exposed to "soft decline" payment refusals ( acquirerResponseCode = A1). For you not to lose any sales, following this type of refusal, we automatically ask the customer to 3-D Secure authenticate themselves, and send a second authorisation request with the proof of customer authentication.

Please refer to one of the Sips Paypage guide corresponding to the selected connector (JSON, POST or SOAP) to learn how to enter the request, depending on your business requirement.

Analysing the response

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

The fields related to a OneClick payment are as follows:

Status Status Action to take

Transaction accepted

The customer uses a payment method already enrolled in the wallet.

responseCode = 00

acquirerResponseCode = 00

paymentMeanId = sequence number of the payment method

merchantWalletId = same request

walletType = MERCHANT_WALLET

panEntryMode = WALLET

Confirm your order for sending

Transaction accepted

The customer chooses to use a payment method not enrolled in the wallet.

responseCode = 00

acquirerResponseCode = 00

paymentMeanId = not populated

merchantWalletId = same request

walletType = not populated

panEntryMode = MANUAL

Confirm your order for sending

Transaction refused

responseCode = XX

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

In response to the payment request to the financial establishment, any reply code associated with a fraud risk, or a reply code indicating that the payment method can never be used, will trigger the automatic deletion of the payment method from the wallet. See below for the list of the codes concerned ( acquirerResponseCode field):

Value Description
04 Retain the card
07 Retain the card, special circumstances
14 Invalid cardholder number
15 Card issuer unknown
33 Card expired
34 Suspected fraud
41 Lost card
43 Stolen card
54 Card expired
57 Unauthorised transaction for this cardholder
59 Suspected fraud
63 Security rules not followed

Crediting the customer with OneClick on Sips Office

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

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

Description

1. You send a credit request using the walletCreditHolder method, sending the transaction data in the request (amount, currency, etc.), as well as the unique customer ID ( merchantWalletId and paymentMeanId fields).

2. WL Sips retrieves the customer payment details stored and sends an authorisation request to the acquirer

3. WL Sips records the transaction in the back office.

4. WL Sips returns the response to the credit request.

5. WL Sips may or may not send the transaction for collection, the same evening.

Setting the request

To credit a customer using the walletCreditHolder method, you should populate the fields below:

Field Value
merchantWalletId Customer unique ID
paymentMeanId Payment method ID

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
Transaction accepted responseCode = 00

Check the next day in the transaction report that the credit has actually been sent.

(transactionStatus = CREDITED)

Transaction refused responseCode = XX

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

Managing a customer's payment methods and account

With Sips Paypage

Description

During a purchase on the Sips Paypage interface, the customer can interact directly with their saved payment methods. The following features are available:

  • changing the name of the saved payment method (not available for expired payment method).
  • deleting a payment method.

Implementation

For the customer to be able to manage the content of their wallet during a purchase, no further development is required, this feature is available by default.

However, it is possible to remove this feature. To do this, please contact technical support.

With Sips Walletpage

Description

The Sips Walletpage interface for OneClick account management allows customers to manage their wallets independently. The following features are available:

  • viewing OneClick accounts contents
  • adding new payment methods to an existing OneClick account
  • changing the name of a payment method already enrolled
  • deleting a payment method in a OneClick account
  • deleting an OneClick 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 tou to manage the content of your customers wallets. The following features are available:

  • obtaining the complete contents of a OneClick account.
  • obtaining details on the payment method contained in a OneClick account.
  • creating a new OneClick account.
  • deleting a OneClick account.
  • adding new payment methods to an existing OneClick account.
  • updating a payment method of a OneClick account.
  • deleting a payment method from a OneClick account.

Using the Sips Office or Sips Office Batch interfaces, you should create and host the wallet management pages to allow your customers to manage their OneClick account.

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.

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 OneClick

Step 1 - Subscribing to the service

Your shop has not been registered to WL Sips .

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

Your shop is already registered to WL Sips .

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

Configuration data of the OneClick service

To access the OneClick service, you should contact technical support and provide the following information:

  • Do you want to receive the expired cards report?
  • If a customer database is shared between several shops of the same brand, please provide the brand ID.
Attention: if your customer database is shared between several shops, 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 shop 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 WL Sips connectors to connect your site to WL Sips and follow the instructions in the section 4 .

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 OneClick integration.

Test data
merchantId 201000076690001
secret key p64ifeYBVIaRcjaWoahCiw9L8wokNLqG2_YOj_POD4g
key version 1
test cards see " Test cards " page

Server Test URL
Paypage POST https://payment-webinit.test.sips-services.com/paymentInit
Paypage JSON https://payment-webinit.test.sips-services.com/rs-services/v2/paymentInit
Paypage SOAP https://payment-webinit.test.sips-services.com/services/v2/paymentInit
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 shop is configured in "transactionReference mode", without automatic generation of the transactionReference . Therefore, you must set the transactionReference field 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 customer enrolment

Immediately

  • Submit an enrolment request based on the enrolment scenario that you have chosen ( Sips Paypage , Sips Office or Sips Walletpage ).

How to validate customer debits

Immediately

  • Submit a debit request based on the debit scenario that you have chosen ( WL Sips , Sips Paypage or Sips Office ).
  • View the transaction via Sips Office Extranet , using the transactionReference or S10transactionId .

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.
  • If you wish, you can refund the transaction via Sips Office Extranet .

Two days later

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

How to validate customer management

Immediately

  • Submit one or several wallet management requests based on the debit scenario that you have chosen ( Sips Paypage , Sips Walletpage , Sips Office or Sips Office Extranet ).

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.

Customer debits

When you submit your first customer debits via Sips Paypage or Sips Office :

  • Monitor acceptance rates (number of responseCode00 per total number of transactions).
  • Check the nature of non-banking refusals.
    • Technical problem: responseCode 90, 97, 99
    • Acquirer fraud: responseCode 34