• DeutschEnglish

Cetelem FullCB

About Cetelem FullCB

General information about Cetelem FullCB

Logo

COO 6505 1000 14 2593028 COO 6505 1000 12 2593024

Info

Cetelem FullCB or Cetelem 3xCB/4xCB is also known as BNPP PF FullCB (BNP Paribas Personal Finance FullCB).

Cetelem 3x/4x 3x/4x FullCB, as a mean of payment allows consumers to pay in 3 or 4 installments for online purchases between 90€ and 3000€ with CB, Visa or Mastercard debit cards. The merchant is guaranteed to receive the full amount of the transaction once the credit request is approved/validated by Cetelem. The accepted credit cards are Cartes Bancaires (CB), French VISA and French MasterCard. The other card brands such as Electron, Maestro, prepaid cards and virtual cards are not accepted.

Once the payment has been approved, the cardholder is debited with 1/3 or 1/4 of the purchase price and then its payment card is debited monthly for the remaining due dates. The merchant is paid the total amount of the order within 48 hours after the collection request.

Payments are guaranteed.

Type

Payments by Credit Card

Process flow chart

Cetelem FullCB process flow

Paygate interface

Definitions

Data formats

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)

Abbreviations

Abbreviation

Description

Comment

CND

condition

M

mandatory

If a parameter is mandatory, then it must be present

O

optional

If a parameter is optional, then it can be present, but it is not required

C

conditional

If a parameter is conditional, then there is a conditional rule which specifies whether it is mandatory or optional

Notice: Please note that the names of parameters can be returned in upper or lower case.

Payment with Cetelem FullCB via form interface

To make a payment with Cetelem FullCB, please use the following URL:

https://www.computop-paygate.com/CetelemFullCB.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:

KeyFormatCNDDescription

MerchantID

ans..30

M

MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too.

TransID

ans..64

M

TransactionID provided by you which should be unique for each payment

RefNr

an..30

C

Supplementary transaction identifier. Only the following characters are allowed:

  • Alphabetical letters [A-Za-z] (from A to Z lower or upper case)

  • Numbers [0-9] (from 0 to 9)

Notice: If RefNr is not present, TransID will be used instead. Therefore in such case TransID should meet format and length of RefNr.

Amount

n..10

M

Amount in the smallest currency unit (e.g. EUR Cent). Please contact the Computop Helpdesk, if you want to capture amounts <100 (smallest currency unit).

Currency

a3

M

Currency, three digits DIN / ISO 4217, e.g. EUR, USD, GBP. Please find an overview here: A1 Currency table

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:

OrderDesc

ans..768

O

Description of goods and prices. Intended purpose on the statement of account.

URLSuccess

ans..256

M

Complete URL which calls up Paygate if payment has been successful. The URL may be called up only via port 443. This URL may not contain parameters: In order to exchange values between Paygate and shop, please use the parameter UserData.

Common notes:

  • We recommend to use parameter "response=encrypt" to get an encrypted response by Paygate

  • However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess/URLNotify. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.

URLFailure

ans..256

M

Complete URL which calls up Paygate if payment has been unsuccessful. The URL may be called up only via port 443. This URL may not contain parameters: In order to exchange values between Paygate and shop, please use the parameter UserData.

Common notes:

  • We recommend to use parameter "response=encrypt" to get an encrypted response by Paygate

  • However, fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess/URLNotify. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.

Response

a7

O

Status response sent by Paygate to URLSuccess and URLFailure, should be encrypted. For this purpose, transmit Response=encrypt parameter.

URLNotify

ans..256

M

Complete URL which Paygate calls up in order to notify the shop about the payment result. The URL may be called up only via port 443. It may not contain parameters: Use the UserDataparameter instead.

Common notes:

  • Before follow-up actions (capture / credit / reversal) are carried out on an existing transaction, the first Notify must have been answered by the shop.

  • Fraudster may just copy the encrypted DATA-element which are sent to URLFailure and send the DATA to URLSuccess/URLNotify. Therefore ensure to check the "code"-value which indicates success/failure of the action. Only a result of "code=00000000" should be considered successful.

UserData

ans..1024

O

If specified at request, Paygate forwards the parameter with the payment result to the shop.

ReqId

ans..32

O

To avoid double payments or actions (e.g. by ETM), enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction or action is submitted again with the same ReqID, Computop Paygate will not carry out the payment or new action, but will just return the status of the original transaction or action.

Please note that the Computop Paygate must have a finalized transaction status for the first initial action (authentication/authorisation). This does not apply to 3-D Secure authentications that are terminated by a timeout. The 3-D Secure Timeout status does not count as a completed status in which the ReqID functionality on Paygate does not take effect. Submissions with identical ReqID for an open status will be processed regularly.

Notice: Please note that a ReqID is only valid for 12 month, then it gets deleted at the Paygate.

SellingPoint

ans..50

O

Selling point

Service

ans..50

O

products or service sold

Channel

ans..64

O

Configuration channel of the PPRO contract (account and ContractID are stored in the system). If it exists, it may overwrite channels stored in the system.

Plain

ans..50

O

A single value to be set by the merchant to return some information unencrypted in response/notify, e.g. the MID.

"Plain"-parameter is part of encrypted "Data" in Computop Paygate and therefore protected against manipulation.

Custom

ans..1024

O

"Custom"-parameter is added to the request data before encryption and is part of encrypted "Data" in Computop Paygate request. By this they are protected against manipulation by a consumer.

The Custom-value is added to the Computop Paygate response in plain text and the "|" is replaced by a "&". By this you can put a single value into Custom-parameter and get multiple key-value-pairs back in response for your own purpose.

Please find a sample here: Custom

PayType

n1

M

Cetelem payment method that shall be used. 1 → Cetelem3xCB, 2 → Cetelem4xCB

EnhancedData

ans..400

O

Specific data of the merchant, based on the agreement between BNPP PF FullCB and the merchant. Format below is used:

VARIABLE_NAME1=VALUE| VARIABLE_NAME2=VALUE|…

Customer information

Salutation

a..4

M

Values accepted: M, Mme, Mlle and with a mapping from english to france salutation (Mr, Mrs, Miss)

FirstName

ans..40

M

First name of the customer

LastName

ans..40

M

Last name of the customer

Email

ans..100

M

E-Mail-Address of the customer

Phone

ans..30

M

Phone number of the customer

Allowed formats are:

  • The area calling code (ACC) plus 9 digits

  • 00 followed by the ACC and 9 digits

  • «+» followed by the ACC and 9 digits

  • 0 followed by 9 digits

Only following area calling codes are accepted:

33

262 (La Réunion

)269 (Mayotte)

508 (Saint-Pierre and Miquelon)

590 (Guadeloupe & Saint Barthélemy & Saint Martin)

594 (Guyana)

596 (Martinique)

681 (Wallis and Futuna)

687 (New Caledonia)

689 (French Polynesia)

CustomerInformation

ans..400

O

Specific data that can be provided for specific actions, based on the agreement between BNPP PF FullCB and the merchant. Format below:

VARIABLE_NAME1=VALUE| VARIABLE_NAME2=VALUE|…

The Paygate only forwards this information without any validation.

Invoicing address

bdFirstName

ans..40

M

First name for the invoicing address

bdLastName

ans..40

M

Last name for the invoicing address

bdStreet

ans..60

M

Street name and street number in the invoicing address

bdAddressAddition

ans..60

O

Additional/complementary address line

bdZip

n..5

M

Postal code in the invoicing address

bdCity

ans..40

M

Town/city in the invoicing address

bdCountryCode

a2

M

Country code of invoicing address according to ISO-3166-1, alphanumeric 2 chars

Shipping address

UseBillingData

a..3

M

Use billing data as shipping data (yes/no) – if yes, all Shipping address parameters are mandatory except "sdAddressAddition"

sdFirstName

ans..40

O

First name in the delivery address

sdLastName

ans..40

O

Last name in the delivery address

sdStreet

ans..60

O

Street name and street number in the delivery address

sdAddressAddition

ans..60

O

Address addition in the delivery address – also optional if "UseBillingData" is true / yes

sdZip

n..5

O

Postcode in the delivery address

sdCity

ans..40

O

Town/city in the delivery address

sdCountryCode

a2

O

Country code of delivery address according to ISO-3166-1, alphanumeric 2 chars

Parameters for payments with CeletemFullCB

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

KeyFormatCNDDescription

mid

ans..30

M

MerchantID, assigned by Computop

PayID

an32

M

ID assigned by Paygate for the payment, e.g. for referencing in batch files as well as for capture or credit request.

XID

an32

M

ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate

TransID

ans..64

M

TransactionID provided by you which should be unique for each payment

RefNr

an..30

C

Supplementary transaction identifier. Only the following characters are allowed:

  • Alphabetical letters [A-Za-z] (from A to Z lower or upper case)

  • Numbers [0-9] (from 0 to 9)

Notice: If RefNr is not present, TransID will be used instead. Therefore in such case TransID should meet format and length of RefNr.

Status

a..50

M

OK or AUTHORIZE_REQUEST (URLSuccess) as well as FAILED (URLFailure)

Description

ans..1024

M

Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis!

Code

an8

M

Error code according to Paygate Response Codes (A4 Error codes)

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:

UserData

ans..1024

O

If specified at request, Paygate forwards the parameter with the payment result to the shop.

PaymentPurpose

ans..26

O

Purpose of payment

PaymentGuarantee

a..12

C

Value

Description

NONE

no payment guarantee

VALIDATED

customer account valid, but no payment guarantee

FULL

payment guarantee

Notice: This parameter is only returned if the Status=OK.

ErrorText

ans..128

C

Detailed PPRO error message.

Notice: Is returned only if Status=FAILED. Use is possible only in agreement with Computop Helpdesk.

TransactionID

an..14

M

External identifier of the payment request

CodeExt

n2

M

Return code of the credit demand

PID

an..25

M

External identifier of the transaction request

Plain

ans..50

O

A single value to be set by the merchant to return some information unencrypted in response/notify, e.g. the MID.

"Plain"-parameter is part of encrypted "Data" in Computop Paygate and therefore protected against manipulation.

Custom

ans..1024

O

"Custom"-parameter is added to the request data before encryption and is part of encrypted "Data" in Computop Paygate request. By this they are protected against manipulation by a consumer.

The Custom-value is added to the Computop Paygate response in plain text and the "|" is replaced by a "&". By this you can put a single value into Custom-parameter and get multiple key-value-pairs back in response for your own purpose.

Please find a sample here: Custom

Return parameters for URLSuccess, URLFailure and URLNotify with Cetelem FullCB

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:

KeyFormatCNDDescription

MerchantID

ans..30

M

MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too.

PayID

an32

M

ID assigned by Paygate for the payment to be credited

TransID

ans..64

M

TransactionID provided by you which should be unique for each payment

Amount

n..10

M

Amount in the smallest currency unit (e.g. EUR Cent). Please contact the Computop Helpdesk, if you want to capture amounts <100 (smallest currency unit).

Currency

a3

M

Currency, three digits DIN / ISO 4217, e.g. EUR, USD, GBP. Please find an overview here: A1 Currency table

MAC

an64

M

Hash Message Authentication Code (HMAC) with SHA-256 algorithm. Details can be found here:

ReqId

ans..32

O

To avoid double payments or actions (e.g. by ETM), enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction or action is submitted again with the same ReqID, Computop Paygate will not carry out the payment or new action, but will just return the status of the original transaction or action.

Please note that the Computop Paygate must have a finalized transaction status for the first initial action (authentication/authorisation). This does not apply to 3-D Secure authentications that are terminated by a timeout. The 3-D Secure Timeout status does not count as a completed status in which the ReqID functionality on Paygate does not take effect. Submissions with identical ReqID for an open status will be processed regularly.

Notice: Please note that a ReqID is only valid for 12 month, then it gets deleted at the Paygate.

Parameters for credit payments with Cetelem FullCB 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

KeyFormatCNDDescription

mid

ans..30

M

MerchantID, assigned by Computop

PayID

an32

M

ID assigned by Paygate for the payment, e.g. for referencing in batch files as well as for capture or credit request.

XID

an32

M

ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Paygate

TransID

ans..64

M

TransactionID provided by you which should be unique for each payment

Status

a..50

M

OK (URLSuccess) or FAILED (URLFailure)

Description

ans..1024

M

Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis!

Code

an8

M

Error code according to Paygate Response Codes (A4 Error codes)

refnr

ans..40

O

Merchant’s unique reference number. Only characters a-zA-Z0-9,-_ are allowed.

ErrorText

ans..128

C

Detailed PPRO error message.

Notice: Is returned only if Status=FAILED. Use is possible only in agreement with Computop Helpdesk.

CodeExt

n2

M

Return code of the credit demand

PID

an..25

M

External identifier of the transaction request

Response parameters for credit payments with Cetelem FullCB via socket connection

Paygate

Documentation (EN)

Dokumentation (DE)

Paygate Status