This document is intended for merchants wishing to understand the sending procedure of reports generated by the Mercanet e-Payment Solution offer, and wishing to understand the structure and the data of these reports.

To get an overview of the Mercanet solution, we advise you to consult the following documents:

• Functional presentation
• Functionality set-up guide

Each file is made up of four successive parts:

1. Report type: this first part indicates the report type and provides further general information like the report name, the generation date or the TAB20 version in use. This part is the first line of the file and begins with the "TITLE" keyword.
2. Report header: second line of the file. The header lists the column names, is specific to each report type and begins with the "HEADER" keyword.
3. Report body: the following lines that begin with a distinct keyword depending on the report type ("TRANSACTION", "OPERATION", etc.). Strictly speaking, this part is the one that includes the records (transactions, cash operations).
4. Report end: the last part of a file, this part marks the end of the file and includes a single field with "END" (transactions or operations report) or "FOOTER" (de rapprochement des transactions or chargebacks report) as a keyword.

Reports "override" (i.e. alter) date formats used in some fields, which means they overwrite formats that were originally defined in the Mercanet data dictionary.

Below is a table of fields altered and date formats overriden in each report:

This guide uses the following convention:

• The "Position" column indicates the field position (i.e. the column) in the report.
• The "Field name" column indicates the designation used in the header.

This report includes all payment transactions made (whether accepted or refused) on your webshop since the last report was sent, except duplicates (code 94) and pending transactions (code 60).

The report can be used to mitigate situations where your information system is not notified of a successful transaction: as an example, if you choose to integrate the Mercanet payment pages, a websurfer may forget to click on the “Back to shop” button (no manual response); or a network-related issue may arise (no automatic response).

Thanks to an automatic (or manual) processing tool, you can analyse this report, update your databases and make sure all orders the payment of which has been accepted will be delivered.

The implementation guides for each payment means may contain clarifications or exceptions, we recommand you consult these guides before any implementation.

Download sample file

The operations report informs you of changes in the status of transactions during their life cycle. This report contains the changes made to payment transactions, i.e. events that may change the transaction status (for example, the "validate" operation changes the "TO_VALIDATE" status of a transaction to " TO_CAPTURE "). So, you can also make an analysis of these files and update your databases. The report also includes operations sent to the bank. Consequently, you can use it to check the accounting transactions.

Download sample file

This report results from the reconciliation between transactions and return flows concerning payments processed by your banks or financial institutions.

The Reconciliations report includes transactions made on your webshop and credited on (or debited from) your bank account.

Upon receiving the payment notifications from the acquirer or the financial institution, Mercanet carries out a reconciliation with these transactions, which makes it possible to add the Mercanet context for the transaction (transaction number, merchant references etc.) to the acquirer's or financial institution's information. This means you are informed in detail of reconciled transactions and alerted in case of non-reconciliation.

The Reconciliations report availability or comprehensiveness is subject to the availability of post-payment return flows provided by your banks or financial institutions.

Download sample file

This report results from the reconciliation between transactions and return flows concerning outstanding payments processed by your banks or financial institutions.

The Chargebacks report includes, among transactions made on your webshop and already credited on (or debited from) your account, those subject to an outstanding payment (for instance due to a customer dispute).

Upon receiving the chargeback notifications from the acquirer or the financial institution, Mercanet carries out a reconciliation with these transactions, which makes it possible to add the Mercanet context for the transaction (transaction number, merchant references etc.) to the acquirer's or financial institution's information.

The Chargebacks report availability or comprehensiveness is subject to the availability of outstanding payment return flows provided by your banks or financial institutions.

Since the TAB20_V8 version, the chargeback report deletes the redundant separator at the end of the header, body and footer in order to be consistent with the other reports.

Download sample file

The Expired cards report identifies all the cards stored and due to expire soon. Thus, you can warn your customers that their card will expire soon and ask them to store their new card.

The extracted cards are the cards that will expire within a time frame of one to three months, depending on settings.

Download sample file