Contents
About Cetelem FullCB
General information about Cetelem FullCB
| 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. |
Process flow chart
Payment platform interface
Payment with Cetelem FullCB via Payment platform form interface
To make a payment with Cetelem FullCB, please use the following URL:
Notice: For security reasons, Payment platform 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:
Parameter | Format | CND | Description |
|---|---|---|---|
MerchantID | ans..30 | M | ID of merchant. Additionally this parameter has to be passed in plain language too. |
TransID | ans..64 | M | Merchant transaction number, which should be unique for each payment |
RefNr | an12 | M | Order identifier. This number must be unique. Only the following characters are allowed:
Notice: If RefNr is not present, TransID will be used instead. Therefore in such case TransID should meet format and length of RefNr. Notice: If the value is already used (=Payment OK), the following transaction will be rejected. |
Amount | n..10 | M | Amount in the smallest currency unit (e.g. EUR Cent) Please contact the helpdesk, if you want to capture amounts <100 (smallest currency unit). |
Currency | a3 | M | Currency, three digits DIN / ISO 4217. Only EUR is permissible. |
MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm |
URLSuccess | ans..256 | M | Complete URL which calls up Payment platform 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 Payment platform and shop, please use the parameter UserData. |
URLFailure | ans..256 | M | Complete URL which calls up Payment platformif 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 Payment platform and shop, please use the parameter UserData. |
Response | a7 | O | Status response sent by Payment platform to URLSuccess and URLFailure, should be encrypted. For this purpose, transmit Response=encrypt parameter. |
URLNotify | ans..256 | M | Complete URL which Payment platform 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 UserData parameter instead. |
UserData | ans..1024 | O | If specified at request, Payment platform forwards the parameter with the payment result to the shop |
ReqID | ans..32 | O | To avoid double payments, enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction is submitted again with the same ReqID, the payment platform will not carry out the payment, but will just return the status of the original transaction. Please note that the payment platform must have a finalized transaction status for the first initial action. Submissions with identical ReqID for an open status will be processed regularly. |
OrderDesc | ans..768 | M | Description of goods and prices. Intended purpose on the statement of account |
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 value to be set by the merchant to return some information unencrypted, e.g. the MID |
Custom | ans..1024 | O | The merchant can submit several values separated by | which are returned unencrypted and separated by &. Custom=session=123|id=456 will change in the answer to Session=123&id=456 |
| 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 |
| ans..100 | M | E-Mail-Address of the customer | |
| Phone | ans..30 | M | Phone number of the customer Allowed formats are:
Only following area calling codes are accepted: 33 |
| 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 Payment platform 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 |
The following table describes the result parameters that the Payment platform transmits to your URLSuccess, URLFailure or URLNotify. If you have specified the Response=encrypt parameter, the following parameters are forwarded Blowfish encrypted to your system:
Parameter | Format | CND | Description |
|---|---|---|---|
MID | ans..30 | M | ID of merchant |
PayID | an32 | M | ID assigned by Payment platform for the payment, e.g. for referencing in batch files |
XID | an32 | M | ID for all single transactions for one payment assigned by Payment platform |
TransID | ans..64 | M | Merchant transaction number, which should be unique for each payment |
RefNr | an12 | M | Order identifier. This number must be unique. Only the following characters are allowed:
Notice: If RefNr is not present, TransID will be used instead. Therefore in such case TransID should meet format and length of RefNr. Notice: If the value is already used (=Payment OK), the following transaction will be rejected. |
Status | a..30 | M | OK in the case of URLSuccess and AUTHORIZE_REQUEST or FAILED in the case of 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 status analysis! |
Code | n8 | M | Error code according to Payment platform Response Codes Excel file |
MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm |
UserData | ans..1024 | O | If specified at request, Payment platform forwards the parameter with the payment result to the shop |
PaymentPurpose | ans..26 | M | Purpose of payment |
PaymentGuarantee | a..12 | C | 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..256 | C | Detailed PPRO error message. Notice: Is returned only if Status=FAILED. Use is possible only in agreement with support. |
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 value to be set by the merchant to return some information unencrypted, e.g. the MID |
Custom | ans..1024 | O | The merchant can submit several values separated by | which are returned unencrypted and separated by &. Custom=session=123|id=456 will change in the answer to Session=123&id=456 |
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:
Notice: For security reasons, Payment platform 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:
Parameter | Format | CND | Description |
|---|---|---|---|
MerchantID | ans..30 | M | ID of merchant. Additionally this parameter has to be passed in plain language too. |
PayID | an32 | M | ID assigned by Payment platform for the payment to be credited |
TransID | ans..64 | M | Merchant transaction number, which should be unique for each payment |
Amount | n..10 | M | Amount in the smallest currency unit (e.g. EUR Cent) Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit). |
Currency | a..3 | M | Currency code, three digits DIN / ISO 4217 |
MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm |
ReqID | ans..32 | O | To avoid double payments, enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction is submitted again with the same ReqID, the payment platform will not carry out the payment, but will just return the status of the original transaction. Please note that the payment platform must have a finalized transaction status for the first initial action. Submissions with identical ReqID for an open status will be processed regularly. |
The following table describes the Payment platform response parameters:
Parameter | Format | CND | Description |
|---|---|---|---|
MID | ans..30 | M | ID of merchant |
PayID | an32 | M | ID assigned by Payment platform for the payment, e.g. for referencing in batch files |
XID | an32 | M | ID for all single transactions (authorisation, capture, credit note) for one payment assigned by Payment platform |
TransID | ans..64 | M | Merchant transaction number, which should be unique for each payment |
Status | a..30 | M | OK or FAILED |
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 | n8 | M | Error code according to Payment platform Response Codes Excel file |
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 |