WL SIPS DOCS

Release 22.5

go directly to content

Search by keywords

CACF_3X CACF_4X 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 CACF_3X and CACF_4X mean of payment integration integration into WL Sips.

This document is intended to help you implement the CACF_3X and CACF_4X mean of payment integration 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

The CACF is a private mean of payment offered by major retailers, with the exclusive acquirer Crédit Agricole.

The CACF_3X and CACF_4X are credit means of payment in instalments.

At the end of this type of payment, you are credited with the amount in one time and the cardholder will be debited in 3 or 4 times (depending on the chosen mean of payment).

Payment channels
Internet V Default payment channel
MOTO X
Fax X
IVR X
Means of payment
Immediate payment X
End-of-day payment V
Deferred payment V
Payment upon shipping V
Payment in instalments X
Subscription payments X
Batch payment X
OneClick payment X
Currency management
Multicurrency acceptance X
Currency settlement X
Dynamic currency conversion X

The customer selects the CACF_3X et CACF_4X means of payment.

They are then redirected to the required information entry page:


Screenshot showing the fields for entering personal data

Screenshot showing the fields for entering personal data such as date of birth or mobile number as well as a payment summary with the details of the chosen deadlines. This page contains a Validate button to go to the next step.


Screenshot showing the input fields for the payment data

Screenshot showing the input fields for the payment data containing the card number, the validity date and the visual cryptogram.this page contains a Validate button to go to the next step and a Cancel button to stop the payment.

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


Screenshot of the validation page of the pre-contractual conditions

Screenshot of the validation page of the pre-contractual conditions. The payment summary is also displayed there.

In order to offer the CACF_3X and CACF_4X means of payment on your website, you have to sign an acceptance contract with Crédit Agricole Consumer Finance. Thereafter, you transmit us the contract number for recording in our information system.

WL Sips offers you two solutions to integrate the CACF_3X and CACF_4X means of payment:

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

The remittance modes available for a 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:


Diagram of the payment process.

The transaction is switched to Validation mode with a capture_mode Validation or to Cancel mode with a capture_mode Author_capture. With a response_code 00, a status To Validate in Validation mode or a status To capture in Cancellation mode is retrieved. With a response_code 17, the status is Aborted. For all other codes, the status is Refused.

The payment process for Sips Paypage is described below:


Payment kinematics with Paypage

1- The customer proceeds to the payment (finalization of the order) 2- Customer is redirected to the payment page 3- Redirection to the payment page 4- Customer is redirected to Sips (payment finalization) 5- The customer is redirected to the merchant site (manual response) 6- The Sips engine sends an automatic response to the merchant site

The following fields have a particular behaviour:

Field name Remarks/rules
captureMode AUTHOR_CAPTURE or VALIDATION
captureDay The value sent in the request must be 8 at a maximum.
A larger value will be forced to 8.
customerLanguage Allows to choose the language used on WL Sips and CACF pages.
orderId Mandatory
customerId Mandatory
customerContact.email Mandatory
billingContact.title Mandatory {0,4} ANS (example: MR / MME / MISS …)
billingContact.firstname Mandatory
billingContact.lastname Mandatory
billingContact.mobile Mandatory
billingContact.phone Mandatory
billingAddress.street Mandatory
billingAddresst.streetNumber Mandatory
billingAddress.zipCode Mandatory
billingAddress.city Mandatory
billingAddress.country Mandatory

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

Status Response fields Action to take
Payment accepted acquirerResponseCode = 00
authorisationId = (cf. the Data Dictionary).
paymentMeanBrand = CACF_3X or CACF_4X
paymentMeanType = ONELINE_CREDIT
You can deliver the order.
Pending transaction acquirerResponseCode = (cf. the Data Dictionary). You must wait until you receive the second automatic response for this transaction to know its final status and whether you can ship the goods. If you do not receive the automatic response, you will need to check the transactions report regularly.
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:


Payment kinematics with Office

1- The customer makes the payment (order finalization) 2- The merchant initializes the payment (PaymentProviderInitialize) 3- The merchant redirects the customer (redirectionUrl) 4- The customer is redirected to the merchant's website (merchantReturnUrl) 5- The merchant finalizes the payment (PaymentProviderFinalize) 6- The merchant displays the payment result.

The CACF_3X and CACF_4X payments initialisation is made by calling the PaymentProviderInitialize method.

The following generic fields are defined in the case of a payment initialisation:

Field name Remarks/rules
merchantReturnUrl Merchant return URL.
paymentMeanBrand Must be populated with CACF_3X or CACF_4X.

You must populate the following specific fields in the initialisation request for a CACF_3X or CACF_4X payment:

Field name Remarks/rules
orderId Mandatory
customerId Mandatory
customerContact.email Mandatory
customerLanguage Allows to choose the language used on WL Sips and CACF pages.
billingContact.title Mandatory {0,4} ANS (example: MR / MME / MISS…)
billingContact.firstname Mandatory
billingContact.lastname Mandatory
billingContact.mobile Mandatory
billingContact.phone Mandatory
billingAddress.street Mandatory
billingAddress.streetNumber Mandatory
billingAddress.zipCode Mandatory
billingAddress.city Mandatory
billingAddress.country Mandatory

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

Status Response fields Action to take
Payment initialisation accepted acquirerNativeResponseCode = 00
messageVersion = message version retrieved in response to the payment initialisation.
redirectionData = redirection data retrieved in response to the payment initialisation.
redirectionUrl = redirection URL to the mean of payment website.
Redirect the customer to redirectionUrl.
Payment initialisation rejected
responseCode = <> 00
See the field errorFieldName, then fix the request.
If the problem persists, contact the technical support.
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 customer must be redirected to the redirectionUrl URL provided in response of the paymentProviderInitialize method. This redirection consists in making a POST call on the redirectionUrl URL received in the response to the payment initialisation. The POST settings to be transmitted are redirectionData and messageVersion also received in the response to the payment initialisation.

At the end of the payment process, the customer is redirected to the URL provided in the merchantReturnUrl initialisation request. The following fields are sent to POST and must be retrieved to finalise the payment.

Field name Remarks/rules
responseCode Redirection process response code
redirectionData Redirection data retrieved in response to the payment initialisation.
messageVersion Message version retrieved in response to the payment initialisation.
amount Transaction amount in cents
merchantId Shop identifier
transactionReference Transaction reference
transactionId Transaction identifier
transactionDate Transaction date

This last step allows you to obtain the payment status. The settings obtained during the redirection after the payment process on the means of payment website are to be transmitted during this call. The method used to finalise a payment is paymentProviderFinalize.

Tip: you can obtain a code 24 "Operation impossible" in response to your paymentProviderFinalize request. This code means that this request has already been sent and processed for the transaction in question. If you are unable to identify this processing, please use the GetTransactionData function of the diagnostic service: this operation allows you to retrieve information relating to a transaction previously created using the WL Sips.

You must provide the following specific fields in the finalisation request for a payment CACF_3X or CACF_4X.

Field name Remarks/rules
redirectionData Redirection data retrieved after the customer returns to your website (cf. Redirecting the customer to the means of payment website).
messageVersion Message version retrieved after the customer returns to your website (cf. Redirecting the customer to the means of payment website).

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 = CACF_3X or CACF_4X
transactionStatus = (cf. the Data Dictionary).
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.

Please refer to the paragraph Analysing the response.

The following operations are available on CACF_3X and CACF_4X transactions:

Cash management
Cancellation V
Validation V
Refund V
Duplication X
Credit X

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


Diagram describing the possible cash operations on the transactions.

For a transaction in To Validate status, either it expires or it is validated and passes to To Capture. When the transaction is in To Capture, you can make a partial cancellation and the remaining amount to be debited remains in To Capture status. You can also cancel it completely and the transaction will go to the status Cancelled. If no action is taken on the transaction, it goes to the status Captured. Once it is in Captured status, you can make a partial refund and the transaction remains in Captured status; you can also make a total refund and the transaction changes to Credited status.

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 the CACF_3X and CACF_4X 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 CACF_3X and CACF_4X transactions, the paymentMeanBrand field is populated with values CACF_3X or CACF_4X. 

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

Here are the details of a CACF_3X and CACF_4X transaction:


detail of the transaction

Capture of the detail of the transaction indicating that in the field Payment method CACF 3X or CACF 4X is recovered

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