Contents


Document history

Date

Name

Change

02.03.2020

Peter Posse

Original version

 


About Cetelem Presto

General information about Cetelem Presto

 

Presto is an online credit solution, facilitated by Cetelem as part of BNPP Personal Finance. With this means of payment, merchants provide the financing capability for major purchases, to their customers, who can further pay by installments, ranging between 4-48 installments and order amount ranging between €150 to €16,000.

Consumers can purchase directly online on the merchant online stores supporting Cetelem Presto as payment method, proceeding the necessary step including e-signature on the BNP PF credit application form. The approval can be instant for complete applications or within 48 hours for incomplete credit applications.

 

Process flow chart



Payment platform 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

CND

condition

M

mandatory

O

optional

C

conditional


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


Payment with Cetelem Presto via Payment platform form interface

To make a payment with Cetelem Presto, 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.

Notice: Please keep in mind that a session expires within 60 minutes. An iFrame integration is not recommended.

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's transaction number, which shall be unique for each payment

RefNr

an12

M

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 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 platform 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 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.

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

Languagea2OLanguage of Cetelem page. Possible values: FR
GoodsCategoryn3M

Category of the good(s). Possible values are shown in the table below.

Note: Payment platform does not make any validation and act as a forwarder for this parameter.

InstallmentAmountn..10Omonthly rate
InstallmentNumbern..2ONumber of month of the payment by installments (1-48)
Customer information
Salutationans..10OSalutation. Values accepted: Mr/MR, Mrs/MME, Miss/MLE
FirstNameans..23MFirst name of the customer
LastNameans..23MLast name of the customer
MaidenNameans..30OMaiden name of the customer
DateOfBirthns10ODate of birth within format YYYY-MM-DD
NatIdentNrans..20ONational identification
Phonea8..15OPhone number (fixed network)
MobileNra8..15OPhone number (mobile)
Emailans..49ME-Mail-Address of the customer
AddrStreetans..32MStreet name and street number
AddrStreet2ans..32OAddress addition
AddrZIPn5MPostal code
AddrCityans..30MTown/city
WorkPhoneans..10OPhone number (business)

 

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, assigned by BNP

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’s transaction number

RefNr

an12

M

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..30

M

OK or AUTHORIZE_REQUEST in the case of URLSuccess and 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

TransactionID

ans..32

M

Cetelem contract number

CodeExt

ans..256

O

External error code

ErrorTextans..256ODescription of external error code

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, assigned by BNP

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’s transaction number

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

 

  • No labels