About Cofidis

General information about Cofidis

The 4-star card was launched by Cofidis as soon as it was created in 1982, initially exclusively for customers of the 3 Suisses brand. It is a private card that combines payment facilities and loyalty benefits. The design of tailor-made products and services, adapted to customers' expectations and needs, has enabled Cofidis, over the years, to extend the 4-star card to other brands (in stores and on the Internet) such as Feu Vert, Maty, Blancheporte, Helline, Bon prix, etc.

From now on, we are talking about the 4-star network. Pay for your purchases in several instalments.

The 4-star card is a revolving credit card that offers you the possibility, depending on the amount of your purchases and the brand, to pay in several instalments.

Process flow chart

Cofidis process flow via the form interface

Multiexcerpt include
SpaceWithExcerpt EN MultiExcerptName Platform-Kurz PageWithExcerpt Wording

interface

Special characters

Cofidis accepts only a limited range of special characters according the table below:

Credit card brands

Credit card payment with Cofidis via Cofidis form interface

In order to execute an TLS credit card payment via Cofidis form, please use the following URL:

Parameters for credit card payments via Cofidis form interface

Return parameters for URLSuccess, URLFailure and URLNotify via Cofidis form interface

Credit card payment with Cofidis via standard

Multiexcerpt include
SpaceWithExcerpt EN MultiExcerptName Platform-Kurz PageWithExcerpt Wording

form interface

In order to execute an TLS credit card payment with Cofidis via standard

Parameters for credit card payments with Cofidis via

Note regarding Cofidis parameter Addata1: Cofidis expects all reservations to be made with the transaction code 590 and replaced by the correct transaction code during the capture. Since the invoice number and date may not yet be known at the time of the reservation, transfer spaces in their place during the reservation. If the transaction code is no longer available when invoicing, the reservation can already be carried out with the correct code.

Cofidis transaction codes

To adapt the layout of the SSL-page to your shop you can use the following unencrypted parameters to configure colours, fonts and images.

Layout parameters for

Credit card payment via Server-to-Server connection

In order to execute a TLS credit card payment with Cofidis via a server-to-server connection, please usel the following URL:

Capture of a credit card payment with Cofidis

Captures are possible via a Server-to-Server connection. To perform a capture via a Server-to-Server connection, please use the following URL:

Parameters for captures of Cofidis via socket connections

Response parameters for captures of Cofidis via socket connections

Credit with reference

Credits (refunds) are possible via a Server-to-Server connection. For a Credit with reference to a capture the amount of the Credit is limited to the amount of the previous capture.

To carry out a credit with a reference transaction, please use the following URL:

Parameters for credit of credit card payments with Cofidis via socket connection

Response parameters for credits of credit card payments with Cofidis via socket connections

Reversal

Reversals are possible via a Server-to-Server connection. A credit card authorisation lowers the customer's credit line.

To carry out a reversal with a reference transaction, please use the following URL:

Notice: Reverse.aspx does not only reverse authorisations, but any LAST TRANSACTION STAGE!! If the last transaction was a capture, Reverse.aspx initiates the reverse, e.g. a credit. Therefore, the utmost caution is urged. Use is at your own risk. We recommend checking the transaction status with Inquire.aspx before using Reverse.aspx.

Parameters for reversals of credit card payments with Cofidis via socket connection

Response parameters for reversals of credit card payments with Cofidis via socket connections

Batch processing via the interface

Basic information about using Batch files and about their structure can be found in the Batch Manager manual. Within batch processing not alle functions are available which are usually available for the online interface.

This section describes the parameters which must be transferred within the data set (Record) for executing payments / credits with Cofidis and which information can be found within the response file about the payment status.

For Batch calls there must be considered batch versions, from which optional parameters depend. All version designations starting with „2.“ pertain calls for a group of enterprises. That means within a batch file for a particular MerchantID can be transferred transactions for other merchants with a separate Sub-MID.

Following table gives an overview of all batch versions that are possible for a specific action and their specialities:

Description of the possible batch versions

The structure for a Cofidis payment within a Batch file to be submitted is the following:

HEAD,<MerchantID>,<Date>,<Version>
CC,Capture,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>
CC,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>
CC,Reverse,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>
FOOT,<CountRecords>,<SumAmount>

Example for Master MID function:

HEAD,[Master]MerchantID,Date,2.x
Type,Action,[Slave]MID,Amount,Currency,TransID,Data (depends on Action)
FOOT,CountRecords,SumAmount

The following table describes the individual fields and values used within the data set (record) in the batch file:

Description of fields within the record for Batch files

The record area within the response file for Batch transactions looks as follows:

HEAD,<MerchantID>,<Date>,<Version>
CC,Capture,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>,<Code>
CC,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>,<Code>
CC,Reverse,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID>,<Status>,<Code>
FOOT,<CountRecords>,<SumAmount>

The following table describes the response parameters which the Batch Manager saves in the Record area for each transaction (standard parameters not explained here, such as <TransID> or <RefNR> and request parameters are returned unchanged and correspond to the call as specified before):

Description of result parameters within the record for Batch files