Versions Compared

Old Version 18

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 back officeMerchant 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 transfers 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 transferstransfer)

4970600 (For BNP Paribas)

instant transfers 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 transferstransfer)

Carte : 34979735700010

instant transfers 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 transferstransfer

. V for card :

  * Y for POS

  * N for the rest

POS : STORE1

instant transfers 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 transferstransfer

. V for card :

  * Y forPOS

  * N for the rest

POS : 0431775016

instant transfers 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 transfers transfer : FR76300040000101234567891

9

PAY_TYPE

An..32

Payment method or POS for POS transactions

Y

Card / SCT (instant transferstransfer) / 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 transfers 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 transferstransfer

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 transfers transfer : FR7630003000010000102020119

19

CARD_SCHEME

Ans..32

Scheme

CB, VISA, MASTERCARD

V (Y for card, N for SCT)

card : CB

Instant transfers 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 transfers 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 transfers 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 transfers 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 transferstransfer

30004 if the customer pays with a BNP card

Instant transfers 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 transferstransfer

Instant transfers 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 transferstransfer

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 transferstransfer)

Card : 869843

Instant transfers 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 transferstransfer

Settled Payment by card : 0000341501170 

Instant transfers 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 transferstransfer

Card : 1.875

Instant transfers transfer : N/A

34

SCHEME_FEE*

Ans..20

Charged by the card schemes for using their network

V

  • Y for card,
  • N for Instant transferstransfer

Card : 1.875

Instant transfers transfer : N/A

35

ACQUIRER_FEE*

Ans..20

Charges for the services of Acquirer.

V

  • Y for card,
  • N for Instant transferstransfer

Card : 1.875

Instant transfers 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 transferstransfer

Card : 1.875

Instant transfers 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 transferstransfer

Card : 110034150116

Instant transfers 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 transferstransfer

Card : 1261#duplicateprocessing

Instant transfers 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 transferstransfer

Card : 600 

Instant transfers 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 transferstransfer

Card : 20200421

Instant transfers 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


Valeurs du champ

Values of the field "Record_Type"


Type de transactionDébitRemboursementDébitRemboursementSauf DébitRemboursementFraisDemande de récupération ()Fraude DébitRemboursementLitige en coursClôture du litige (résoluRetrait général du compte PayPalDébitRemboursementDébitRemboursementDébitRemboursementRemboursementAutorisationRégléNon régléExécutéRéglé en retard

Record

Payment method

Transaction type

Enregistrement

Moyen de paiement

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

Règlement sur initiation échouée

*Non disponible actuellement.

Settlement on Failed Initiation

*Currently not available. 

NB. Please ignore the NB. Veuillez ignorer les "Record_type" qui ne sont pas mentionnés dans le tableau ci-dessus.that are not mentioned in the table above.


Details of the fields with multiple information

Field

Détails des champs avec multiples informations

Champ

"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:

[Numéro de carte masqué ou token de la carte]#

[Marque (scheme) de la carte]
[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

RemboursementCredit

[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

VIREMENT Instant transfers (SCT)

[Compte du payeurPayer's Account]

Description: IBAN client du marchand effectuant le virementMerchant client's IBAN making the transfer

FR7630003000010000102020119

*Non disponible actuellementCurrently not available.


Champ

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]

ouor

[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

RemboursementCredit

[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 :   Fourni par le système de paiement ou le commerçant.

    Cela est traité individuellement, mais nous utilisons généralement la valeur « testchannel » pour les comptes test et « livechannel » pour les comptes live.

  • TAG : Dépend du système de paiement fourni par la plateforme de paiement (à convenir avec PPRO).

    Cela est traité individuellement. La liste la plus récente sera distribuée lors du processus d'intégration.

  • 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 requestCountry : Paramètre AddrCountryCode fourni dans la requête du commerçant.

·     GiropayPP
·     iDEALPP
·     SEPAPP
·     SofortPP

  • SellingPoint : Fourni par le commerçant Provided by merchant.


Impayés (chargeback)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)

[Statut Instanea Status]#[Instanea ID Instanea]#[Statut banque payeurPayer Bank Status]

    Statut
  • Instanea Status:
        *   *
        • Description:
      Statut du SCT dans Instanea (à titre indicatif)
        • Status of the SCT in Instanea (for information purposes)
        • Format: An..21 (
      valeurs
        • values: SUCCESS, SETTLEMENT_COMPLETE, SETTLEMENT_INCOMPLETE)
      • Instanea ID
        • Instanea
      • :
            *
            • Description:
          Référence unique du SCT dans
            • Unique reference of the SCT in Instanea
            *
            • Format: An..40
          • Statut banque payeur : 

            * Description : Statut renvoyé par la banque du payeur lors de l’invocation d’API Open Banking DSP2

            *
          • 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
          ISO
            • : ACSC, ACCP, RJCT)

      SETTLEMENT_COMPLETE#rq:3NHczGsuikTfPEwBtLNL3RrWCshz:5zKtXEAq#ACCP

      *Non disponible actuellement.

      Exemple d'un fichier de réconciliation CTSF

      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,,,,,
900530,6,4191071
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

      Cas d'usages

      Ces statuts des cas d'usages classifiés comme finaux ou transitoires, permettent de suivre avec fiabilité l'évolution du paiement jusqu'à son aboutissement. La distinction entre fichiers finaux (confirmant le statut définitif du paiement) et transitoires (fournis en J+1 pour suivi intermédiaire) garantit une vision complète et actualisée des encaissements.

      Liste des cas

      N° cas

      Méthode de paiement

      Statut

      Final ou transitoire

      Fichier de réconciliation

      M01-C01

      Carte

      RégléSettled

      Final

      CTSF

      M01-C02

      Carte

      ImpayéUnpaid

      Final

      CTSF

      M02-C01

      Virement instantané

      RégléSettled

      Final

      CTSF

      M02-C02

      Virement instantanéNon réglé

      		Unsettled

      Final

      CTSF

      M02-C03

      Virement instantanéExécuté

      		 Executed

      TransitoireTransitional

      CTPF

      M02-C04

      Virement instantanéRéglé en retard

      		 Settled Late

      Final

      CTSF

      M02-C05

      Virement instantanéRéglé sur initiation échouée

      		 Settlement on Failed Initiation

      Final

      CTSF

      Zoom cas d'usage virement instantané


      Detailed Use Case: Instant Transfer (SCT)

      Les cas d'usages se résument comme suit : 

      SCT initié à J (jour de vente)

      The use cases can be summarized as follows:

      SCT Initiated on Day J (Day of Sale)

      • Two
        • Deux
      • options:

      1- SCT réglé dans les temps : Settled on Time:

      • Accounting
        • Comptabilité
      • :
          Si
            • If J =
          jour ouvré France :

                     → Compte marchand BNP crédité à J en DDV J pour les paiements saisis à J entre 0h00 et 18h59.59

                     → Compte marchand BNP crédité à J+1 ouvré France en DDV J pour les paiements saisis à J entre 19h00 et 23h59

          Si J n’est pas un jour ouvré France : Compte marchand BNP crédité au prochain jour ouvré France en DDV J

          • Fichier de réconciliation : Paiement restitué dans le fichier final (M02-C01 SCT réglé) de J+1 ouvré France, avec une DDV à J

          2- SCT non réglé dans les temps (i.e. pas de trace dans le relevé de compte J [concernant la période J entre 0h00 et 18h59.59]ni dans le relevé intraday de J+1 ouvré France [concernant la période J entre 19h00 et 23h59]) :

          • A J+1 ouvré France : Paiement restitué dans le fichier transitoire (M02-C03 SCT exécuté) avec une DDV (informative) à J, compte marchand BNP non mouvementé
          • Suite à cela, 2 options (le SCT pourra être réglé en retard ou bien non réglé) :

          → SCT réglé en retard : 

          • Comptabilité : Compte marchand BNP crédité entre J+1 (avec annonce postérieure à la Production du fichier de réconciliation de J+1) et J+6 ouvré France en DDV de la date d’exécution réelle du SCT (comprise entre J et J+5)
          • Fichier de réconciliation : Paiement restitué dans le fichier final (M02-C04 SCT réglé en retard) entre J+2 et J+6 ouvré France avec une DDV égale à la date d’exécution réelle du SCT (comprise entre J et J+5)

          → SCT non réglé : à Ce cas arrive à J+6 ouvré France, lorsque le crédit n’est toujours pas visible en comptabilité ou en intraday avant de produire le fichier de réconciliation.

          • Comptabilité : Compte marchand BNP non mouvementé
          • Fichier de réconciliation : Paiement restitué dans le fichier final (M02-C02 SCT non réglé) à J+6 ouvré France avec une DDV (informative) à J

          Focus sur les dates pivot : 

          • J+1 ouvré France :
          • Si le règlement est visible dans la comptabilité ou l’intraday avant la production du fichier de réconciliation, alors le SCT est réglé
          • Si le règlement est visible dans la comptabilité ou l’intraday après la production du fichier de réconciliation, alors le SCT est réglé en retard
          • J+6 ouvré France :
          • Si le règlement est visible dans la comptabilité ou l’intraday avant la production du fichier de réconciliation, alors le SCT est réglé en retard
          • Sinon, alors le SCT est non réglé

          Cas particulier du SCT réglé sur initiation échouée :

          SCT initié à J (jour de vente) à Paiement NOK

          Un règlement arrive sur le compte marchand à D, date indéterminée

          SCT réglé sur initiation échouée : 

          • Comptabilité :

          Si D = jour ouvré France :

                       → Compte marchand BNP crédité à D en DDV D pour SCT exécuté à D entre 0h00 et 18h59.59

                       → Compte marchand BNP crédité à D+1 ouvré France en DDV D pour SCT exécuté à D entre 19h00 et 23h59

          Si D n’est pas un jour ouvré France : Compte marchand BNP crédité au prochain jour ouvré France en DDV D

            • 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

          • Fichier de réconciliation : Paiement restitué dans le fichier final (M02-C05 SCT réglé sur initiation échouée) de D+1 ouvré France, avec une DDV à D
          Info

          De manière générale, si un crédit ou débit sur le compte marchand ne peut pas être rapproché d’une opération, l’orientation est de ne pas le transmettre au marchand (risque de transmettre des données incomplètes).

          Le traitement de génération des fichiers de réconciliation étant totalement piloté par les fichiers issus des différents partenaires, il n’y a pas de process pour gérer le delta de ce qui ne serait pas présent dans les fichiers de réconciliation.

          Fichier de réconciliation CTPF

          1- Structure du fichier

          Contenu identique au fichier CTSF.

          2- Format de données

          Contenu identique au fichier CTSF.

          3- Nom du fichier (.ctpf)

          Convention de dénomination:         <MERCHANT_ID>#<FILE_CREATION_DATE>#<COUNTER>.ctpf

          Exemple de nom de fichier File name example :            BNP_TEST#20240130#001.ctpf

          N°

          ElémentElement

          Format

          ExempleExample

          1

          MERCHANT_ID

          An..20

          Master MID de niveau 2

          Ex: BNP_TEST_YYYY

          2

          COUNTER

          N3

          001 (Toujours égal à 001 car un seul fichier par MID par jour, ne sera pas incrémenté de 1 qu’en cas de nécessité d’envoyer un second fichier si incident)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*en cas d’anomalie sur une ou plusieurs lignes, BNP Axepta devra renvoyer le fichier complet et corrigé avec le compteur incrémenté.

          3

          FILE_CREATION_DATE

          N8

          20201014

          4-

          Table du fichier CTPF (Settlement file

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

          Contenu identique au fichier CTSF à l'exception que dans ce fichier on aura un seul record type 812F

          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

          Info

          N°cas

          Méthode de paiement

          Statut

          Description détaillée

          Fichier

          RECORD_TYPESens

          Débit/Crédit pour Cash Collection

          M02-C03

          Virement instantanéInstant tranfer

          Exécuté

          Virement instantané en succès lors du paiement client, pour lequel le règlement n’arrive pas encore sur le compte du marchand

          Transitoire

          81F

          Info (crédit)

          .

          5- Exemple d'un fichier CTPF

          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
          Moyens de paiement disponibles 



        Available payment Methods


        Catégorie

        Marque

        Prestataire / Acquéreur / Passerelle

        CartesCards

        CB, Visa, Mastercard

        BNP Paribas

        DinersBNP Paribas
        AMEXAMEX

        Virement  Transfer (SCT)Virement instantané

        Instant tranfer

        Instanea

        Solutions alternativesAlternative 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










        PPRORemarque 

        : En cas de Notice: In case of Bancontact via PPRO , les échecs de paiement seront également signalés dans le fichier de réconciliation pour que le commerçant puisse justifier les frais de transaction = 0,22 €. Les caractéristiques suivantes permettent au commerçant de reconnaître un échec de paiement : Les transactions erronées sont toujours renvoyées avec la date de la transaction (Transaction Date) 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 et une « saisie de montant » (Amount Capture) supplémentaire avec la valeur « 0 ». Seul le commerçant peut alors comptabiliser les frais de transaction 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

        *Non disponible pour le moment.Not available currently


        Data integration of external payment providers


        When you activate the AXEPTA Settlement file service, the payment methods

        Intégration des données des différents prestataires de paiement  

        Lorsque vous activez le fichier de réconciliation (Settlement file) AXEPTA, les moyens de paiement CB/VISA/MASTERCARD seront automatiquement inclus. Cependant, pour tous les autres moyens de paiement additionnels, nous vous invitons à contacter le support BNP Paribas will be automatically included.

        However, for any additionnal payment method, we invite you to contact our technical Support  (bnpparibas@computop.com) pour recevoir les instructions nécessaires à l'activation de ces moyens de paiement additionnels.

        Veuillez trouver ci-dessous les instructions nécessaires à l'activation des moyens de paiement alternatifs principaux :

        PayPal 

        Pour que nous puissions récupérer les fichiers de règlement de PayPal, nous avons besoin des données de votre compte SFTP PayPal.

        Pour cela vous devez :

        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
        3. Contacter votre « Account Manager » PayPal (si vous en avez un) ou le support client standard de PayPal pour qu’il active cette fonction SFTP dans votre compte client PayPal et que vous puissiez y accéder directement.
        4. Vous devrez ensuite, depuis votre compte PayPal, créer un compte SFTP sécurisé dans la section « information sur le compte - Creating a secure FTP server user ».
        5. Après avoir créé le serveur SFTP avec succès, veuillez nous envoyer les données d'accès SFTP : nom d'utilisateur et mot de passe.
        6. 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 : Veuillez trouver la documentation PayPal pour vous aider : https://developer.paypal.com/docs/reports/sftp-reports/settlement-report/#know-before-you-begin

        A noter :

        1. Nous ne demanderons jamais le mot de passe de votre compte PayPal (ces données sont strictement confidentielles), nous avons besoin uniquement des accès à votre compte SFTP de PayPal.
        2. Ne pas confondre l’activation du moyen de paiement PayPal dans Axepta (activation réalisée lors de votre inscription avec la solution Axepta) et l’intégration des fichiers de reporting PayPal dans Axepta (procédure décrite ci-dessus).

        AMEX

        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 directlyPour AMEX vous devrez fournir votre numéro de contrat AMEX et remplir un formulaire "AMEX EPA Application form" qui nous autorise à récupérer les fichiers de reporting d'AMEX. Le formulaire vous sera transmis par le support BNP Paribas (bnpparibas@computop.com) que nous vous invitons à contacter directement.