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.
| Logo |
|
|---|---|
| Info | The 4-star card is a private card that combines payment facilities and loyalty benefits. The design of tailor-made products and services has been adapted to customers, expectations and needs. 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. |
| Type | Payments by Credit Card |
| Card Scheme |
|---|
| Carte 4Etoiles |
cofidis3xcb |
cofidis4xcb |
facilypay-3x |
facilypay-3xsansfrais |
facilypay-4x |
facilypay-4xsansfrais |
Process flow chart
Paygate interface
Format Description a alphabetical as alphabetical with special characters n numeric an alphanumeric ans alphanumeric with special characters ns numeric with special characters bool boolean expression (true or false) 3 fixed length with 3 digits/characters ..3 variable length with maximum 3 digits/characters enum enumeration of allowed values dttm ISODateTime (YYYY-MM-DDThh:mm:ss) Abbreviation Description CND condition M mandatory O optional C conditional Notice: Please note that the names of parameters can be returned in upper or lower case.Definitions
Data formats
Abbreviations
Comment If a parameter is mandatory, then it must be present If a parameter is optional, then it can be present, but it is not required If a parameter is conditional, then there is a conditional rule which specifies whether it is mandatory or optional
Special characters
Cofidis accepts only a limited range of special characters according the table below:
Character | Name |
|---|---|
| : | Colon |
| . | Full stop/period |
| Space | |
| @ | At sign |
| + | Plus sign |
| % | Percent sign |
| * | Asterisk |
| / | Forward slash |
| _ | Underscore |
| - | Dash (hyphen/minus sign) |
Credit card brands
Credit card brand, correct spelling for CCBrand |
|---|
Carte 4Etoiles (Carte Helline4etoiles – branded) |
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:
https://www.computop-paygate.com/cofidis.aspx |
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter. The following table describes the encrypted payment request parameters:
Parameters for credit card payments via Cofidis form interface
The following table gives the result parameters which Computop Paygate transmits to URLSuccess or URLFailure and URLNotify. If you have specified the Response=encrypt parameter, the following parameters are sent Blowfish encrypted to your system:
pls. be prepared to receive additional parameters at any time and do not check the order of parameters the key (e.g. MerchantId, RefNr) should not be checked case-sentive
Return parameters for URLSuccess, URLFailure and URLNotify via Cofidis form interface
Credit card payment with Cofidis via standard Paygate form interface
In order to execute an TLS credit card payment with Cofidis via standard Paygate form, please use the following URL:
https://www.computop-paygate.com/payssl.aspx |
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter. The following table describes the encrypted payment request parameters:
Parameters for credit card payments with Cofidis via Paygate form
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. Computop then replaces the capture transaction code by 590 and changes it back when invoicing to the one transferred during the reservation. The invoice number and date are adopted at the same time and transferred to Cofidis.
Type of financing | PGI request | Transaction code | Number of instalments |
|---|---|---|---|
Small instalment | Capture, tel. Authorisation | 460 | 0 (irrelevant) |
Small instalment | Credit | 470 | 0 (irrelevant) |
Down payment | Capture | 423 | 1 |
Down payment | Credit | 523 | 1 |
Monthly instalment | Capture | 423 | x |
Monthly instalment | Credit | 523 | x |
Payment suspension | Capture | 974 | 0 (irrelevant) |
Payment suspension | Credit | 975 | 0 (irrelevant) |
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 Paygate forms for credit card payments with Cofidis via Paygate form
The following table gives the result parameters which Computop Paygate transmits to URLSuccess or URLFailure and URLNotify. If you have specified the Response=encrypt parameter, the following parameters are sent Blowfish encrypted to your system: pls. be prepared to receive additional parameters at any time and do not check the order of parameters the key (e.g. MerchantId, RefNr) should not be checked case-sentive
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:
https://www.computop-paygate.com/direct.aspx |
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter. The following table describes the encrypted payment request parameters:
The following table describes the result parameters with which the Computop Paygate responds to your system pls. be prepared to receive additional parameters at any time and do not check the order of parameters the key (e.g. MerchantId, RefNr) should not be checked case-sentive
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:
https://www.computop-paygate.com/capture.aspx |
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter. The following table describes the encrypted payment request parameters:
Parameters for captures of Cofidis via socket connections
The following table describes the result parameters with which the Computop Paygate responds to your system pls. be prepared to receive additional parameters at any time and do not check the order of parameters the key (e.g. MerchantId, RefNr) should not be checked case-sentive
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:
https://www.computop-paygate.com/credit.aspx |
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter. The following table describes the encrypted payment request parameters:
Parameters for credit of credit card payments with Cofidis via socket connection
The following table describes the result parameters with which the Computop Paygate responds to your system pls. be prepared to receive additional parameters at any time and do not check the order of parameters the key (e.g. MerchantId, RefNr) should not be checked case-sentive
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. Paygate can reverse an authorisation so that it no longer block the limit any more.
To carry out a reversal with a reference transaction, please use the following URL:
https://www.computop-paygate.com/reverse.aspx |
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.
Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter. The following table describes the encrypted payment request parameters:
Parameters for reversals of credit card payments with Cofidis via socket connection
The following table describes the result parameters with which the Computop Paygate responds to your system pls. be prepared to receive additional parameters at any time and do not check the order of parameters the key (e.g. MerchantId, RefNr) should not be checked case-sentive
Response parameters for reversals of credit card payments with Cofidis via socket connections
Batch processing via the interface
Grundsätzliche Informationen zur Arbeit mit Batch-Dateien sowie zu deren Aufbau erfahren Sie im separaten Handbuch zum Batchmanager. Im Batch-Verfahren sind nicht alle Funktionen verfügbar, die für die Online-Schnittstelle verfügbar sind.
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
Die folgende Tabelle beschreibt die einzelnen Felder und Werte, die im Datensatz (Record) innerhalb der Batch-Datei verwendet werden:
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>
Die folgende Tabelle beschreibt die Antwort-Parameter, die der Batch-Manager im Record-Bereich zu jeder Transaktion speichert (hier nicht erklärte Standardparameter wie etwa <TransID> oder <RefNR> und Aufrufparameter werden unverändert zum Aufruf wieder zurückgegeben und sind vorstehend beschrieben):
Description of result parameters within the record for Batch files