WL SIPS DOCS

Release 22.5

go directly to content

Search by keywords

Oney Card integration

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

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

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

This document is intended to help you implement the Oney card 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

Oney Bank is a French financial institution specialising in payment solutions and consumer credit.

The Oney cards allow to make cash or on credit payments.

To pay with an Oney card, cardholders have to provide their card details, namely:

  • Card number
  • Expiry date
  • The payment option of their choice
Payment channels
Internet V Default payment channel
MOTO X
Fax X
IVS X
Means of payment
Immediate payment V
End-of-day payment V Default method
Deferred payment V
Payment upon shipping V
Payment in instalments X
Subscription payment X
Batch payment V
OneClick payment V
Currency management
Multicurrency acceptance X EUR only
Currency settlement X EUR only

The OneClick functionality is available on the Oney card payment pages:


Image of a page for entering payment information with an Oney card

Page allowing you to enter your card number, expiry date and the financing option to choose from 3 choices: 1. Cash, 2. Revolving credit, 3. Deferral 3 months to 10 months at 14.90%, and to specify whether the card should be registered for a future purchase.

By default, the option is preselected to "no".

If the customer wishes to register his card for a future payment, he selects the "yes" option and can, if he so wishes, choose a name for this card:


Image for entering the name of a card if the customer wishes to register it

In future payments with the cards pre-registered in the wallet, the customer does not re-enter his card details. However, he chooses the financing option.

The customer selects the Oney card means of payment.

They are then redirected to the required information entry page:


The required information entry page

After providing the required information, the customer can choose their financing option. Depending on this choice, a simulation is displayed. Once the information is entered, they validate:



The payment ticket is displayed, then the customer returns to your website:


The payment ticket

In order to offer the Oney Card means of payment on your website, you have to sign an ONUS contract with Oney. Thereafter, you transmit us the contract number for recording in our information system. With this contract, you will accept two different card types:

  • private cards (exclusively Oney cards, trading name cards and Oney Gift Card)
  • bank cards (co-branded cards with CB, Visa, Mastercard)

WL Sips offers you three solutions to integrate the Oney card payment method:

  • 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 an Oney card 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.
  • Immediate mode: the authorisation and remittance are executed online simultaneously.
The diagram below explains the different transaction statuses according to the chosen capture mode:
diagram showing the different statuses of a transaction

If the merchant chooses validation mode, the transaction will either go to the To validate status if it has been accepted (response code 00) or to the refused status if it has been refused (response code different of 00). If the merchant chooses the cancellation mode, the transaction will either go to the To capture status if it was accepted (response code 00) or to the refused status if it was refused (response code different of 00). If the merchant chooses the immediate mode, the transaction will either go to the Captured status if it was accepted (response code 00) or to the refused status if it was refused (response code different of 00).

The payment process for Sips Paypage is described below:


diagram showing the payment kinematics via paypage

After finalising the order on the merchant's website, the customer proceeds to the payment. To do so, they are redirected to the payment pages hosted by WL Sips. The customer selects the Oney payment method and then enters their card number and financing option. The ticket with the payment result is displayed. Two responses are sent; a manual response that redirects the customer to the merchant website and an automatic response sent to the merchant website by the Sips server.

The following fields have a particular behaviour:

Field name Remarks/rules
paymentPattern Tհe value sent in the request is ignored.
The payment type is forced to ONE_SHOT.
paymentMeanData.accord.settlementMode

Not mandatory: the settlement method may be forced into the request.

Contact Oney for a complete list of these payment terms.

paypageData.bypassReceiptPage

Y or N

Not mandatory: populating this field with Y allows not to display the Oney card payment confirmation ticket.

templateName Not mandatory: allows to control the customisation template of Oney pages (cf. Oney customisation guide).
orderId Mandatory: maximum length of 9 characters allowed by Oney.
customerId Maximum length of 8 characters allowed by Oney.
customerLanguage Allows to choose the language used on WL Sips and Oney card pages.

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

Status Response fields Action to take
Payment accepted acquirerResponseCode = 00
acquirerResponseIdentifier = Oney identifier
authorisationId = (cf. the Data Dictionary).
paymentMeanTradingName = card name with reference to the trading name.
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.
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
responseCode = 90, 99
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.

The payment process for Sips Office is described below:


diagram showing the payment kinematics via office

The customer completes and pays for the order directly on the merchant website. The merchant collects the payment details and transmits the payment request to WL Sips via a cardOrder. The merchant displays the payment result to the customer via its website.

You can create an Oney card payment using the CardOrder method of the checkout service.

Field name Remarks/rules
cardExpiryDate Mandatory (format: YYYYMM)
cardNumber Mandatory
currencyCode Mandatory: EUR only (978)
orderChannel Mandatory (INTERNET)
paymentPattern Tհe value sent in the request is ignored.
The payment type is forced to ONE_SHOT.
paymentMeanBrand Must be populated with ACCORD.
paymentMeanData.accord.settlementMode Mandatory : contact Oney for a complete list of these payment terms.
orderId Mandatory: maximum length of 9 characters allowed by Oney.
customerId Maximum length of 8 characters allowed by Oney.
customerLanguage Allows to choose the language used on WL Sips and Oney pages.
holderData.birthDate Mandatory for the walletOrder format : YYYYMMDD

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

Status Response fields Action to take
Payment accepted acquirerResponseCode = 00
acquirerResponseIdentifier = Oney identifier
authorisationId = (cf. the Data Dictionary).
cardScheme = ACCORD
paymentMeanTradingName = card name with reference to the trading name.
You can deliver the order.
Acquirer refusal acquirerResponseCode = (cf. the Data Dictionary). The authorisation is refused for a reason unrelated to fraud, you can suggest that your customer pay with another means of payment by generating a new request.
Refusal due to a technical issue acquirerResponseCode = 90-98
responseCode = 90, 99
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.

The following operations are available on Oney card transactions:

Cash management
Cancellation V Partial cancellation allowed only for "cash" and "revolving credit" settlement methods.
Validation V Partial validation allowed only for "cash" and "revolving credit" settlement methods.
Refund V Partial refund allowed only for "cash" and "revolving credit" settlement methods.
Duplication V The original transaction payment option will be used.
Credit X

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


image too complex to be described, please contact the WL Sips support

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 Oney card 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 X
Note: for Oney card transactions, the paymentMeanBrand field is populated with the value ACCORD.

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



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

Configuration