Versions Compared

Old Version 26

changes.mady.by.user writer

Saved on

compared with

New Version Current

changes.mady.by.user writer

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Multiexcerpt include
SpaceWithExcerptDOCBNP
MultiExcerptNameLogo BNP
PageWithExcerptAxepta BNP Paribas Online 1.0 - EN





Table des matières

Table of Contents


Description

The reconciliation file (Settlement File) consolidates all data from the various payment methods used by the merchant to meet their reconciliation and reporting needs. Clearing (compensation) and settlement information is retrieved from various payment service providers and acquirers.

For instant transfers, reconciliation relies on specific statuses such as Settled, Unsettled, Executed, Settled Late, or Settled on Failed Initiation. These statuses, classified as final or transitional, allow tracking the payment's progress reliably until completion. The merchant will receive two types of files depending on the transaction status: the CTSF (Computop Settlement File) or the CTPF (Computop Transaction Processing File) (see CTPF file zoom).

The file is presented in CSV format (Comma Separated Values – values separated by commas).

It is available:

  • From the AXEPTA BNP Paribas Merchant Portal (the file is available for up to 60 days in the Back Office).

  • Via an SFTP connection in pull mode (for configuration and account identification information, please contact BNP Paribas support).

Please note that reconciliation files are generated based on the frequency at which clearing and settlement information from the payment system(s), provider(s), or acquirer(s) is made available.


Info

sFTP informations

The files will be automatically deleted from the Axepta sFTP server after 14 days.

The reconciliation file is generated only when transactions are processed.



File structure

The file is provided in a CSV format (comma separated file).

Each Settlement File is structured into :

  • a header record,
  • one or multiple detail records
  • and a total record.

The encoding for the line breaks is configurable at merchant level. Some fields may contain values of variable length. Where sizes are not given, a field size limitation does not apply.

Data format

FormatDescription

a

Alphabetic characters A-Z, a-z

n

Numeric digits, 0-9

an

Alphanumeric characters A-Z, a-z, 0-9

ans

Alphanumeric and special characters

ns

Numeric and special characters

3

Fixed length data element of 3 characters

..17

Variable length data element up to a maximum of 3 characters. The minimum length is defined by the specific requirements of the data element itself, but shall be at least 1 character.

tstp

Timestamp, format: <DD.MM.YYYY hh:mm:ss>



File name (.ctsf)

Naming convention :         <MERCHANT_ID>#<FILE_CREATION_DATE>#<COUNTER>.ctsf

N°

Élément

Format

Exemple

1

MERCHANT_ID

An..20

ACME01

2

FILE_CREATION_DATE

N8

20201014

3

COUNTER

N3

001

File name example:            ACME01#20201014#001.ctsf       

  


Settlement file's table (CTSF) (version 1.5)

Header record


N°

Field Name

Format

Description

Mandatory (Yes, No, Variable)

Example

1

RECORD_TYPE

N3

Header record: Identifies the respective entry as header record, value ‘100’.

Y

100

2

MERCHANT_ID

An..30

Merchant's identification (MID) provided by Axepta BNP Paribas during the onboarding phase

Y

BNP_MERCHANT_ECOM_FR_EUR

3

DATE

N8

Date the Settlement File was created, <DDMMYYYY>.

Y

20250424

4

VERSION

An..4

Version (current version is 1.5)

Y

1.5


Detail record


Fields 45 to 50 will stay empty until future enhancements.

  • For 1 succesful transaction there will be a line on the setllment file with 50 columns
  • Empty fields must be ignored


N° 

Element

Format

Description

Mandatory (Yes, No, Variable)

Example

1

RECORD_TYPE

An3

Detail record: Identifier that specifies the payment method and type of account ledger entry (e.g. debit and credit). Charges to customers are indicated as debits and payments to customers as credits.

Link to the "RECORD TYPE" table: RECORD TYPE TABLE

Y

Card : 510

instant transfer : 810

2

SALE_CHANNEL

An..32

Transaction Channel

ECOM (internet browser), MOTO (IVR), APP (mobile app), PAYBYLINK (payment link), POS)

Y

ECOM, MOTO, APP, PAYBYLINK, POS

3

MERCHANT_ID

An..30

Merchant's identification (MID) provided by AXEPTA BNP Paribas during onboarding phase (1MID =1 shop)

Y

BNP_MERCHANT_ECOM_FR_EUR

4

ACQUIRING_CONTRACT_ID

An..50

Contract ID provided by the processor or acquirer (BNP Paribas, PPRO, AMEX, PayPal, etc)

V (Y for card, N for instant transfer)

4970600 (For BNP Paribas)

instant transfer : N/A

5

BUSINESS_REGISTRATION_NUMBER

An..50

Registration number of the company (Siret number in France)

V (Y for card, N for instant transfer)

Carte : 34979735700010

instant transfer : N/A

6

STORE ID

Ans..120

Data only available for POS transaction → indicates the merchant's store where the purchase was made

V :

. N for instant transfer

. V for card :

  * Y for POS

  * N for the rest

POS : STORE1

instant transfer : N/A

7

TERMINAL ID

Ans..32

Data only available for POS transaction → indicates the terminal ID (POS terminal) used for the transaction

V :

. N for instant transfer

. V for card :

  * Y forPOS

  * N for the rest

POS : 0431775016

instant transfer : N/A

8

MERCHANT_ACCOUNT_NUMBER

An..34

Merchant account number indicated in the BNP reconciliation file:

. Card:

Case M01-C01: Account number with 11 characters

Case M01-C02 Concatenation of :

* Bank code with 5 characters ("30004" for BNPP)

* Branch code with 5 characters

* Account number with 11 characters

. Instant transfers : IBAN

See use cases

Y


Card : 01234567891

instant transfer : FR76300040000101234567891

9

PAY_TYPE

An..32

Payment method or POS for POS transactions

Y

Card / SCT (instant transfer) / POS

10

PAYMENT_CREATION_DATE

Tstp

Date and time the payment has been created, <DD.MM.YYYY hh:mm:ss>.

Card: Authorization Date

Instant Transfer: Date on which the transfer was initiated

Y

20.04.2020 14:18:23

11

PAYMENT STATUS

A2

The status is always "OK" as these are successful and settled payments, except for transfers in specific use cases M02-C03 and M02-C05 where the value will be "NOK".

See use cases.

Y

Card : OK

instant transfer : OK, NOK

12

ARCHIVE REFERENCE NUMBER

An12

Transaction Number (Account Holder)

End-to-End Reference generated by AXEPTA (Unique, random)

Y

00200Y2049Z8

13

TRANSACTION_ID

Ans..64

Unique transaction reference submitted by the merchant to recognize a payment for an order. It might be shared across a sequence of related transactions (requests) that constitute a payment (e.g. authorization, capture, credit, etc).

Y

890_XUoqyBWuGw

14

AUTHORIZATION_AMOUNT

N..12

Authorized amount in smallest unit of transaction currency.

V (Y for card, Value zero for SCT)

789 (in cents) for card - N/A for instant transfers

15

AUTHORISATION_NUMBER

Ans..6

Authorization number - only for card payments (ecom & POS transactions)

V (Y for card, N for SCT)

02129F for card - N/A for instant transfer

16

TRANSACTION_AMOUNT

N..12

The amount that has been processed by the payment scheme in smallest unit of the transaction currency.

Y

700 (in cents)

17

TRANSACTION_CURRENCY

A3

Refers to the three-letter ISO 4217 currency code of the currency in which the transaction was processed.

Y

EUR

18

CUSTOMER_INFO

Ans..160

Constructed field encompassing specific customer related information depending on the payment method. 

Details CUSTOMER INFO

Y

Card: 4111xxxxxxxx9996#VISA 

Instant transfer : FR7630003000010000102020119

19

CARD_SCHEME

Ans..32

Scheme

CB, VISA, MASTERCARD

V (Y for card, N for SCT)

card : CB

Instant transfer : N/A

20

CARD_TYPE

A1

Available for cards (BNPP acquiring) and POS transactions

Card type :

            C for Credit card

            D for Debit card

            P for Prepaid card

            U for Universal card

            b Unknown (Blank)

V (Y for card, N for SCT)

Card : D

Instant transfer : N/A

21

CARD_NATURE

A1

Available for cards (BNPP acquiring) and POS transactions

Card Nature

            P Consumer Card

            E Commercial Card

            b Unknown (Blank)

V (Y for card, N for SCT)

Card : P

Instant transfer : N/A

22

ISSUING_BANK_BIN

N..6

Available for cards (BNPP acquiring) and POS transactions

Issuing Bank BIN 

V (Y for card, N for SCT)

Instant transfer : N/A

23

ISSUING_BANK_ID

N..5

Available for cards (BNPP acquiring) and POS transactions

Issuing bank Identifier 

V :

  • V pour la carte :

  > V pour CB :

     * Y for M01-C01 (Settled)

     * N for M01-C02 (Unpaid)

  > N for Visa and Mastercard

  • N for Instant transfer

30004 if the customer pays with a BNP card

Instant transfer : N/A

24

TX_REGION

N..3

Available for cards (BNPP acquiring) and POS transactions

Transaction Regionality 

V :

  • V for card :

  > Y for M01-C01 (Settled)

  > N for M01-C02 (Unpaid)

  • N for Instant transfer

Instant transfer : N/A

25

CH_COUNTRY_CODE

N..6

Available for cards (BNPP acquiring) and POS transactions

Cardholder country code 

V :

  • V for card :

  > Y for M01-C01 (Settled)

  > N for M01-C02 (Unpaid)

  • N for Instant transfer

Card : FRA for french cardholders

Instant transfers : N/A

26

ORDER_DESCRIPTION

Ans..768

Description of the order to which the payment relates. (e.g., Monthly subscription fees for a TV box)

Y if the Merchant provides the data during payment initiation

Data not available for REST API V2

Data not available for REST API V2Electricity bill / Internet subscription

27

EXTENDED_INFO

Ans..200

Constructed field encompassing additional information that is available depending on the payment method.

  • For cards, this is the sum of the fees announced in data items 33, 34, 35, and 36 for a settled payment. Not provided for unpaid transactions (default 000000).

  • For Instant transfers, see the explanatory section in DETAIL CHAMP EXTENDED INFO

Y

Here is the link to find the detailed information about the content of this field : DETAIL CHAMP EXTENDED INFO

28

CAPTURE_DATE

Tstp

  • For Card : The date and time a transaction has been accepted by the acquirer / payment scheme for settlement, <DD.MM.YYYY hh:mm:ss>. If the time is not given it will be set to ‘00:00:00’. In case of non-payment, date of capture of the original operation..

  • For Instant transfers : date of the last event.

Y

24.04.2020 00:00:00

29

PAYOUT_ID

Ans..32

Settlement file ID  (Invoice number for PPRO transactions)

V (Y for card, N for Instant transfer)

Card : 869843

Instant transfer : N/A

30

PAYOUT_DATE

N8

Settlement Date = Value Date in the format <YYYYMMDD>

Note: The Value Date corresponds to the value date of the credit/debit on the account statement. Please note that this is not necessarily the accounting date (for example, an instant transfers initiated on a Saturday is accounted for on Monday evening with the value date of Saturday, and it is the Saturday date that appears on the statement). 

In case of non-payment, the PAYOUT_DATE will carry the value date of the non-payment.

Y

20250528

31

PAYOUT_REFERENCE

Ans..32

Settlement file reference number 

V

  • V for card (Y settled Payment and N for an unpaid)
  • N for Instant transfer

Settled Payment by card : 0000341501170 

Instant transfer : N/A

32

PAYOUT_CURRENCY

A3

Currency of account

Y

EUR

33

INTERCHANGE_FEE*

Ans..20

Fees charged by the card issuer.

V

  • Y for card,
  • N for Instant transfer

Card : 1.875

Instant transfer : N/A

34

SCHEME_FEE*

Ans..20

Charged by the card schemes for using their network

V

  • Y for card,
  • N for Instant transfer

Card : 1.875

Instant transfer : N/A

35

ACQUIRER_FEE*

Ans..20

Charges for the services of Acquirer.

V

  • Y for card,
  • N for Instant transfer

Card : 1.875

Instant transfer : N/A

36

PROCESSING_FEE

Ans..20

Charges for the services of Processors (PSP, Gateway, Network Operator).

V

  • Y for card,
  • N for Instant transfer

Card : 1.875

Instant transfer : N/A

37

CHARGEBACK FILE NUMBER**

Ans..20

Chargeback case number will allow the merchant to follow the chargeback file (exchanging with the schemes) –  Card only

V

  • V for card (N settled payment and Y for Unpaid)
  • N for Instant transfer

Card : 110034150116

Instant transfer : N/A

38

CHARGEBACK CODE AND REASON**

Ans..400

Chargeback code (provided by the scheme)  # Chargeback reason (text) – Card only

V

  • V for card (N settled payment and Y for Unpaid)
  • N for Instant transfer

Card : 1261#duplicateprocessing

Instant transfer : N/A

39

CHARGEBACK AMOUNT**

N..12

Chargeback amount – Card only

V

  • V for card (N settled payment and Y for Unpaid)
  • N for Instant transfer

Card : 600 

Instant transfer : N/A

40

CHARGEBACK DATE**

N8

Chargeback date – Card only

V

  • V for card (N settled payment and Y for Unpaid)
  • N for Instant transfer

Card : 20200421

Instant transfer : N/A

41

PAY ID

Ans..32

Payment ID generated by Axepta

Y

439d9f039ea1457191d6c45dd0c68ede

42

X-ID

Ans..32

Payment Event Identifier

Y

13a999a98w064012b61f9fc8a067510e

43

CUSTOMER ID

Ans..30

Client Identifier

Y


44

INVOICE ID

Ans..30

Invoice Identifier

Y


45

CONTRACT ID

Ans..30

 Contract Identifier

Y


46RESERVED 6-Champ réservé pour des évolutions futures 

47RESERVED 7-Champ réservé pour des évolutions futures 

48RESERVED 8-Champ réservé pour des évolutions futures 

49RESERVED 9-Champ réservé pour des évolutions futures 

50RESERVED 10-Champ réservé pour des évolutions futures 

*NB: Please note that this data is not available for bank accounts outside France and in non-EUR currencies.

**NB: Please note that this data is not available for bank accounts outside France.

Total record


N°

Element

Format

Description

Mandatory (Yes, No, Variable)

Example

1

RECORD_TYPE

N3

Total record: Identifies the respective entry as totals record, value ‘900’.

Y

900

2

RECORD_COUNT

N..5

Total number of rows in detailed records section. 1 line = 1 transaction 

Y

36

3

TOTAL_AMOUNT

N..12

Sum of all transaction amounts (credits are also summed up to the total amount) in the detailed record section in the smallest unit of transaction currency.

Y

79896


Values of the field "Record_Type"


Record

Payment method

Transaction type

500SEPA DIRECT DEBIT*Debit
501Credit
502Chargeback
510CARTES (CB/ VISA/ MC)Debit
511Credit
512

Chargeback*

  • Except Diners

510

AMEX

Debit

511

Credit

512

Chargeback

513Costs

514

Retrieval Request

517

Fraud elements (TC40/SAFE)

520

PAYPAL



Debit

521

Credit

522

Chargeback

524Litigation in process
525Closure of the dispute (resolved)
526General withdrawal from PayPal account

530

FLOA


Settled

531

debit

580

iDEAL*

Debit

581Credit

630

KLARNA*

Debit

631Credit

710

PPRO



Debit

711

Credit

712

Chargeback

720AMAZON PAY*Débit
721Credit
722Chargeback
723Authorization

810

SCTSettled
81EUnsettled
81F Executed
81G Settled Late

81H

 Settlement on Failed Initiation

*Currently not available. 

NB. Please ignore the "Record_type" that are not mentioned in the table above.


Details of the fields with multiple information

Field "Customer_Info"

Mode de paiement

Structure / Commentaire

Exemple

AMAZON PAY*

[Customer_Name]#
[Customer_E-Mail]

John Doe#
john.doe@gmail.com

CARTE (CB/VISA/MC/ AMEX)

Masked card number or card token and card brand:
[0000xxxxxxxx0000]#
[Brand]

4111xxxxxxxx9996#

Visa

SEPA DIRECT DEBIT*

[Account_Holder]#
[Account_Number]#
[Bank_ Code]#
[Bank]

ou

[Account_Holder]#
[IBAN]#
[BIC]#
[Bank]

ou

[IBAN]# '
[BIC]

John Doe#
10602437#
205950#
Barclays

ou

John Doe#
GB58BARC20595010602437#
BARCGB22#
Barclays

ou

GB58BARC20595010602437#
BARCGB22

iDEAL*

[Account_Holder]#
[IBAN]#
[BIC]#
[Bank]

John Doe#
NL12RABO0388375809#
RABONL2U#
Rabobank

KLARNA*

[OCR_No]#
[Invoice_No]

1834143680436#
519072450221831988

PAYPAL

[Payer_ID]#
[Payer]

A59XV256BZ#
john.doe@gmx.de

PPRO

Credit

[Acc_Holder]#
[Acc_Number]#
[Bank_Code]#

[Bank_Name]#
[BIC]#
[IBAN]


Chargeback

[Acc_Holder]#

[BIC]#

[IBAN]


John Doe#

#
RABONL2U#
Rabobank#
RABONL2U#
NL30RABO0205970948



John Doe#

RABONL2U#
NL30RABO0205970948

Instant transfers (SCT)

[Payer's Account]

Description: Merchant client's IBAN making the transfer

FR7630003000010000102020119

*Currently not available.


Field "Extended_Info"


Mode de paiement

Structure / Commentaire

Exemple

AMAZON PAY*

[SellerOrderId]#
[SellerReferenceId]#
[AmazonOrderReferenceId]#
[AmazonTransactionId]#
[TotalTransactionFee]


CARTES (CB/VISA/MC/ AMEX)

MERCHANT DISCOUNT RATE

[Merchant_Discount_Rate]#
[Merchant_Discount]
[Currency]

CHARGEBACK INFO

[Doc Request Reason]#
[Ref Initial Doc]

RETRIEVAL REQUEST

[ARN]#
[Reason_Code]#
[Status]

FRAUD ELEMENTS 

[ARN]#
[Code]#

1.875#
1.95#
EUR






74527646319021051645048#
0350#
MI1


74627546887030655470117#
6

SEPA DIRECT DEBIT*

[PmtInfId]

or

[Mandate_ID]#[IP address]

Chargeback [6]

[reasonCode]#[trigger]#[token]

reasonCode -

  • 4 digit SEPA reason code

trigger -

  • “CHB” = Chargeback

  • “B1”..”B3” = CB after 1st, 2nd or 3rd retry

token -

  • ACT - CB was initiated by the customer

  • RFND - CB was initiated by the merchant

  • FRM - format error

  • NSF - no sufficient

5e736c2d718843149b71e3439b292dfe

reasonCode=MD17#trigger=CHB#token=NSF

iDEAL*

NL#
[IP address]

NL#
82.151.44.149

KLARNA PAYMENTS*

[Merchant_Discount]

3.97

KLARNA SOFORT*

[Customer_ID]#
[Country]#
[Mandate_ID]#
[IP address]

9139795844#
DE#
9135762874-203185592#
78.49.133.9

PAYPAL

[Merchant_Discount]#
[Currency]#
[Transaction_Type (credit / debit)]

203#
EUR#
CR

PPRO

Credit

[Channel]#
[TAG]#
[Country]#
[Selling_Point]#
fixed_fee=[FIXED_FEE_AMOUNT]#
fixed_fee_currency=[FIXED_FEE_CURRENCY]#
external_fee=[EXTERNAL_FEE_AMOUNT]#
external_fee_currency=[EXTERNAL_FEE_CURRENCY]#
minimum_discount_fee=[MINIMUM_DISCOUNT_FEE_AMOUNT]#
discount_rate=[DISCOUNT_RATE]

  • Channel :  From payment scheme or provided by merchant.
    This is individually handled but usually we use the value "testchannel" for test accounts and "livechannel" for live accounts.

  • TAG : Depends on payment scheme provided by paygate (has to be arranged with PPRO).
    This is individually handled. The most current list will get distributed during the integration process.

  • Country : Parameter AddrCountryCode provided in merchant request.

·     GiropayPP
·     iDEALPP
·     SEPAPP
·     SofortPP

  • SellingPoint : Provided by merchant.


Chargeback

[Chargeback_ID]#
[Chargeback_Reason_Code]#
[Chargeback_RefNu

livechannel#
iDEALPP#
NL#
T63542
fixed_fee=0.45#
fixed_fee_currency=EUR#
external_fee=0.00#
external_fee_currency=EUR#
minimum_discount_fee=0.00#
discount_rate=0

1055329#
MD06#
15072617000095/OCMT/EUR26,49/CHGS/EUR4,20

VIREMENT (SCT)

[Instanea Status]#[Instanea ID]#[Payer Bank Status]

  • Instanea Status:
    • Description: Status of the SCT in Instanea (for information purposes)
    • Format: An..21 (values: SUCCESS, SETTLEMENT_COMPLETE, SETTLEMENT_INCOMPLETE)
  • Instanea ID:
    • Description: Unique reference of the SCT in Instanea
    • Format: An..40
  • Payer Bank Status:
    • Description: Status returned by the payer's bank during the invocation of the Open Banking DSP2 API
    • Format: An 4 (ISO codes: ACSC, ACCP, RJCT)

SETTLEMENT_COMPLETE#rq:3NHczGsuikTfPEwBtLNL3RrWCshz:5zKtXEAq#ACCP

*Currently not available.


Example of a settlement file (CTSF)


Code Block
100,BNP_MERCHANT_ECOM_FR_EUR,20240712,1.5
810,ECOM,BNP_MERCHANT_ECOM_FR_EUR,,,,,FR7630004000011234567890196,SCT,11.07.2024 10:21:46,OK,R10001020101,FR00000000_R10001020101,0,,1020106,EUR,FR7630003000010000102020169,,,,,,,,,SETTLEMENT_COMPLETE#rq:3NHczGsuikTfPEwBtLNL3RrWCshz:5zKtXEAq#ACCP,11.07.2024 10:21:46,,20240617,,EUR,,,,,,,,,439d4f039ea1457191d6c85dd0c68ede,13a559a980064012b61f9fc8a067510e,4004040236114,4004040236114,6021339431,,,,,
810,ECOM,BNP_MERCHANT_ECOM_FR_EUR,,,,,FR7630004000011234567890196,SCT,11.07.2024 10:30:10,OK,R20001020102,FR00000000_R20001020102,0,,1020102,EUR,FR7630003000010000102020266,,,,,,,,,SETTLEMENT_COMPLETE#rq:2xr7HYh8swas2decHqgdW9J6UGs:5zKtXEAq#ACCP,11.07.2024 10:30:10,,20240617,,EUR,,,,,,,,,9ea8d177a4fb483099b22c993fe87341,d63923d9a6bf49578339567640f259cf,4004043902726,4004043902726,6024196117,,,,,
81H,ECOM,BNP_MERCHANT_ECOM_FR_EUR,,,,,FR7630004000011234567890196,SCT,11.07.2024 10:47:00,NOK,R10001020502,FR00000000_R10001020502,0,,1020503,EUR,FR7630003000010000102050239,,,,,,,,,SETTLEMENT_COMPLETE#rq:4Yj9wXyGEJ9MAhTPkdE87tLWpW6F:5zKtXEAq#RJCT,11.07.2024 10:47:00,,20240618,,EUR,,,,,,,,,352a0f33832f456dbdf1c103c1309f35,121eb179d1ca4f259c15adee531c1b93,4004046135069,4004046135069,6025924409,,,,,
81H,ECOM,BNP_MERCHANT_ECOM_FR_EUR,,,,,FR7630004000011234567890196,SCT,11.07.2024 10:44:00,NOK,R10001020501,FR00000000_R10001020501,0,,1020501,EUR,FR7630003000010000102050142,,,,,,,,,SETTLEMENT_COMPLETE#rq:3qGVUvtMeMzyXpnKHX9hq6evuR4a:5zKtXEAq#RJCT,11.07.2024 10:44:00,,20240618,,EUR,,,,,,,,,61dc80e5c74a42cd98de84fef9aac23f,61515981a8b84fb7ad7fe866f81ebcc2,4004045078391,4004045078391,6025133184,,,,,
510,ECOM,BNP_MERCHANT_ECOM_FR_EUR,2222254,41488382700019,,,12345678901,CARD,11.07.2024 10:52:08,OK,276699858970,2024-07-22-04:47:59:978169,107512,889835,107512,EUR,400001xxxxxx8323#VISA,VISA,D,P,499022,16607,FRA,FRA,test:0000,0.00,22.07.2024 00:00:00,000622,20240823,0000622700257,EUR,0.07000,0.02493,0.00000,,,,,,c6b4cae05275402a8e9f88ac825d3f2d,1c704b8ac85b49f091bbbe82d9d53868,,473099,14191974E,,,,,
510,ECOM,BNP_MERCHANT_ECOM_FR_EUR,2222252,41488382700019,,,12345678901,CARD,11.07.2024 11:46:15,OK,vIjGbTIKo8xD,20240819114516,2347,169678,2347,EUR,497202xxxxxx7891#Cartes Bancaires,CB,D,P,499022,16607,FRA,FRA,paiement facture 13451226E,0.00,19.07.2024 00:00:00,000622,20240820,0000622700257,EUR,0.07000,0.02493,0.00000,,,,,,26328c156a0c47eb9cc92d4861e4749e,7ea7b0286c0b4f878ef21f6363d03eba,,26200000428774,013451226E,,,,,
900,6,4191071530,ECOM,BNP_MERCHANT_ECOM_FR_EUR,704685,,,,3277,Floa 4x,21.12.2025 17:46:21,OK,22243770,p8wbfdyeicc,99500,,99500,EUR,15168,,,,,,,,,3.48,22.12.2025 00:00:00,,20251222,,,,,,,,,,,903cf373ad1d4a7d945c68725b42efb3,1328928fd8ab4730ae1a0fb20b82853f,,,,,,,,
531,ECOM,BNP_MERCHANT_ECOM_FR_EUR,704684,,,,3277,Floa 3x,14.12.2025 18:47:55,OK,22242656,rdmlgfgh1f8,51450,,111,EUR,00107011,,,,,,,,,0.00,23.12.2025 00:00:00,,20251223,,,,,,,,,,,4f3d85bbcada48879c41149274a2f141,267cbf9ddad14ef5932160538722ced3,,,,,,,,
900,8,4290682

Use Cases

These use case statuses, classified as final or transitional, allow tracking the payment's progress reliably until completion. The distinction between final files (confirming the payment's final status) and transitional files (provided on D+1 for intermediate tracking) ensures a comprehensive and up-to-date view of collections.

List of Cases

N° case

Payment method

Status

Final or Transitional File

Settlement file

M01-C01

Carte

Settled

Final

CTSF

M01-C02

Carte

Unpaid

Final

CTSF

M02-C01

Virement instantané

Settled

Final

CTSF

M02-C02

Virement instantané

Unsettled

Final

CTSF

M02-C03

Virement instantané

 Executed

Transitional

CTPF

M02-C04

Virement instantané

 Settled Late

Final

CTSF

M02-C05

Virement instantané

 Settlement on Failed Initiation

Final

CTSF


Detailed Use Case: Instant Transfer (SCT)

The use cases can be summarized as follows:

SCT Initiated on Day J (Day of Sale)

  • Two options:

1- SCT Settled on Time:

  • Accounting:
    • If J = French business day: → Merchant BNP account credited on J with DDV J for payments entered on J between 00:00 and 18:59:59 → Merchant BNP account credited on J+1 French business day with DDV J for payments entered on J between 19:00 and 23:59
    • If J is not a French business day: Merchant BNP account credited on the next French business day with DDV J
  • Reconciliation File: Payment returned in the final file (M02-C01 SCT Settled) on J+1 French business day, with DDV on J

2- SCT Not Settled on Time (i.e., no trace in account statement J [concerning the period J between 00:00 and 18:59:59] nor in intraday statement of J+1 French business day [concerning the period J between 19:00 and 23:59]):

  • On J+1 French business day: Payment returned in the transitional file (M02-C03 SCT Executed) with an informative DDV on J, merchant BNP account not moved

  • Following this, two options (the SCT may be settled late or not settled):

→ SCT Settled Late:

  • Accounting: Merchant BNP account credited between J+1 (with announcement after the production of the reconciliation file of J+1) and J+6 French business day with DDV of the actual execution date of the SCT (between J and J+5)

  • Reconciliation File: Payment returned in the final file (M02-C04 SCT Settled Late) between J+2 and J+6 French business day with a DDV equal to the actual execution date of the SCT (between J and J+5)

→ SCT Not Settled: This case occurs on J+6 French business day, when the credit is still not visible in accounting or intraday before producing the reconciliation file.

  • Accounting: Merchant BNP account not moved

  • Reconciliation File: Payment returned in the final file (M02-C02 SCT Not Settled) on J+6 French business day with an informative DDV on J

Focus on Pivot Dates:

  • J+1 French business day:

    • If the settlement is visible in accounting or intraday before the production of the reconciliation file, then the SCT is settled

    • If the settlement is visible in accounting or intraday after the production of the reconciliation file, then the SCT is settled late

  • J+6 French business day:

    • If the settlement is visible in accounting or intraday before the production of the reconciliation file, then the SCT is settled late

    • Otherwise, the SCT is not settled

Special Case of SCT Settled on Failed Initiation:

SCT initiated on Day J (Day of Sale) with Payment NOK A settlement arrives on the merchant account on Day D, an undetermined date SCT Settled on Failed Initiation:

  • Accounting:

If D = French business day: → Merchant BNP account credited on D with DDV D for SCT executed on D between 00:00 and 18:59:59 → Merchant BNP account credited on D+1 French business day with DDV D for SCT executed on D between 19:00 and 23:59 If D is not a French business day: Merchant BNP account credited on the next French business day with DDV D

  • Reconciliation File: Payment returned in the final file (M02-C05 SCT Settled on Failed Initiation) on D+1 French business day, with DDV on D


Info

In general, if a credit or debit on the merchant account cannot be matched to a transaction, the recommendation is not to transmit it to the merchant (risk of transmitting incomplete data).

Since the generation of reconciliation files is entirely controlled by files from various partners, there is no process to manage the delta of what might not be present in the reconciliation files.

Settlement File (CTPF)

1- File structure

Content identical to the CTSF file.

2- Data format

Content identical to the CTSF file.

3- File name (.ctpf)

Naming convention :         <MERCHANT_ID>#<FILE_CREATION_DATE>#<COUNTER>.ctpf

File name example :            BNP_TEST#20240130#001.ctpf

N°

Element

Format

Example

1

MERCHANT_ID

An..20

Ex: BNP_TEST_YYYY

2

COUNTER

N3

001 (Always equal to 001 as there is only one file per MID per day, it will only be incremented by 1 if there is a need to send a second file in case of an incident)

*In case of an anomaly on one or more lines, BNP Axepta will need to resend the complete and corrected file with the counter incremented.

3

FILE_CREATION_DATE

N8

20201014

4- Settlement file's table (CTPF) (version 1.5)

Content identical to the CTSF file, except that this file will contain only one record type: 812F.

Info

N°case

Payment method

Status

Detail description

File

RECORD_TYPE

M02-C03

Instant tranfer

Executed

Instant transfer successful during customer payment, for which the settlement has not yet arrived in the merchant's account

Transitional

81F

.

5- Example of settlement file (CTPF)

Code Block
100,BNP_MERCHANT_ECOM_FR_EUR,20240712,1.5
81F,,BNP_MERCHANT_ECOM_FR_EUR,,,,,FR7630004000011234567890196,SCT,11.07.2024 10:33:17,OK,R10001020301,FR00000000_R10001020301,0,,1020306,EUR,FR7630003000010000102030160,,,,,,,,,SUCCESS#rq:223Qouegg7anR8dRQuBp1DYJkRv7:5zKtXEAq#ACCP,11.07.2024 10:33:17,,20240617,,EUR,,,,,,,,,18d660124f24469081bcf562d383e7ff,fd04a8e5798944779654a8fa77b334ba,4004031963567,4004031963567,6016656151,,,,,
81F,,BNP_MERCHANT_ECOM_FR_EUR,,,,,FR7630004000011234567890196,SCT,11.07.2024 10:40:40,OK,R10001020302,FR00000000_R10001020302,0,,1020302,EUR,FR7630003000010000102030257,,,,,,,,,SUCCESS#rq:4Qm586XZCd7XXC7snDXL4XBrmn4t:5zKtXEAq#ACCP,11.07.2024 10:40:40,,20240617,,EUR,,,,,,,,,6e72c27992144506bdaff60e89ce2af0,3454d2dfdf7741b6bbe75f7c40d2eed7,4004034268259,4004034268259,6017938424,,,,,
900,2,2040608



Available payment Methods


Catégorie

Marque

Prestataire / Acquéreur / Passerelle

Cards

CB, Visa, Mastercard

BNP Paribas

DinersBNP Paribas
AMEXAMEX

 Transfer (SCT)

Instant tranfer

Instanea

Alternative solutions

Amazon Pay*

Amazon

PayPal 

PayPal

Alipay

Wechat

Union Pay International (UPI)

Paysafecard

SEPA Direct Debit (SDD)

MyBank

Giropay

Klarna Sofort (Pay now)

TrustPay

Bancontact

iDeal

EPS

Przelewy24 (P24)

Multibanco

FPX MyClear

RHB Bank

eNets

POLi Payments

Boleto Bancario










PPRO

Notice: In case of Bancontact via PPRO also failed payments will be reported in the Settlement file, so that the merchant can account for the transaction fee = 0.22€. With following characteristics the merchant can recognize a failed payment: Faulty transactions are returned always with Transaction Date = 01.01.1970 01:00:00 and additional "Amount Capture" mit the value „0“. In this case the merchant only can account for the transaction fee (fixed_fee=0,22).

Klarna Payments (Klarna Pay Later)*Klarna
iDEAL*BNP Paribas

*Not available currently


Data integration of external payment providers


When you activate the AXEPTA Settlement file service, the payment methods CB/VISA/MASTERCARD will be automatically included.

However, for any additionnal payment method, we invite you to contact our technical Support  (bnpparibas@computop.com) to receive the required instructions for the data activation of these other payment methods.


Below are the instructions of the main alternative payment methods : 

PayPal 

In order for us to get the settlement and clearing files of PayPal, you need to provide us with your PayPal SFTP account information.

To do so, you need to :

  1. Contact your PayPal « Account Manager » to activate the SFTP functionnality in your PayPal customer account. Once it is activated, you will be able to directly access it via your PayPal account . 
  2. Then, from your PayPal account, create a secure SFTP account in the section "account information - Creating a secure FTP server user ».
  3. Once the SFTP is successfully created, please send to us your SFTP data access : login + password.

Please find the PayPal documentation that may help you :  https://developer.paypal.com/docs/reports/sftp-reports/settlement-report/#know-before-you-begin

Note :

  1. We will never ask for your PayPal account password (this data is confidential), we only need your PayPal SFTP account data information.
  2. Do not mix up the activation of PayPal as a payment method in AXEPTA (activation done during your subscription) with the integration of PayPal reporting files in Axepta (process just described above).

AMEX 

For AMEX you will need to provide your AMEX contract number and fill in the "AMEX EPA Application form" which allows us to retrieve the AMEX reporting files. The form will be provided by BNP Paribas support (bnpparibas@computop.com) that you will need to contact directly.