• France
status page
Demo shops
assistance
FAQContact support
Search
Categories
Tags
Europe (English)
France
Spain
Europe (English)
India
Homepage
Use cases
Create a payment
Create an installment payment
Create a multi-card (split) payment
Create a payment by Alias (Token)
Create a payment link
Create a recurring payment
Manage subscriptions
Manage your transactions (refund, cancel...)
Analyze your reports
API docs
Embedded Form
REST API
Hosted payment
Mobile payment
File exchange
SDD mandates by REST API
Snippets
Payment methods
Plugins
Marketplace
Guides
Merchant Back Office
Back Office Expert
Functional guides

Filename examples

Several verification processes are carried out before the files are processed in order to verify the file size and the compliance with the naming rules specific to each file type.

  • The request payment file (REQ) is named using the generation date, the shop number, the mode (Test or Production), the sequential number of the file within the day (<YYYYMMDD>.<shopId>.PAY.REQ.<z>.<xx>).

    Example: 20191130.12345678.PAY.REQ.T.01.csv

  • The response payment file (ANS) is also named using the generation date, the shop number, the mode (Test or Production), the sequential number of the file within the day (<YYYYMMDD>.<shopId>.PAY.ANS.<z>.<xx>).

    Example: 20191130.12345678.PAY.ANS.T.01.csv

  • Some files can be ignored and then identified via a suffix added to the name. In this case, the merchant receives a notification by e-mail.

    If the file size is 0 bytes, the name will have the suffix _ERROR.

    Example: (20191130.12345678.PAY.ANS.T.01_ERROR.csv

    If a file has already been processed, it is identified as a duplicate file. Thus, the name will have the _DUPLICATE suffix.

    Example: (20191130.12345678.PAY.ANS.T.01_DUPLICATE.csv)

Jobs
Legal
GDPR
25.20-1.11