Description of Reporting Contents

Description of Reporting Contents

Description of reporting Contents 1. DOCUMENT HISTORY...................................................................................................................... 3 2. GETTING IN TOUCH WITH TECHNICAL SUPPORT................................................................. 4 3. GENERAL PRINCIPLES OF REPORTING......................................................................................5 4. IDENTIFYING REPORT FILE TYPES.............................................................................................6 5. USING PREFORMATTED REPORTS..............................................................................................8 5.1. Understanding the structure of a transactions report.................................................................................. 8 5.2. Understanding the structure of an operations report.................................................................................12 5.3. Understanding the structure of a bank reconciliation report.....................................................................14 5.4. Understanding the structure of a chargebacks reconciliation report.........................................................16 6. CUSTOMIZING REPORT FILES.................................................................................................... 19 6.1. Configuring the mode of distribution of reporting files........................................................................... 19 6.2. Customizing the content of a transactions report..................................................................................... 20 Managing the contents of a transactions report................................................................................... 21 Managing the content of the columns in the transactions report......................................................... 22 Viewing the labels of columns available for customization................................................................ 23 Previewing the transactions report....................................................................................................... 25 7. VIEWING REPORT FILES VIA EXPORT.....................................................................................26 7.1. Exporting the transactions in progress......................................................................................................26 7.2. Exporting captures.....................................................................................................................................29 7.3. Exporting Captured transactions............................................................................................................... 30 8. ANNEXES............................................................................................................................................35 8.1. Table of formats........................................................................................................................................ 35 8.2. vads_auth_result.........................................................................................................................................36 8.3. vads_currency............................................................................................................................................ 37 1. DOCUMENT HISTORY Version Date Comment 2.2 06-Apr-2016 Complete overhaul of the document in accordance with the DITA standard 2.1c 21-Aug-2015 PayZen 2.4 version 2.1b 14-Oct-2014 PayZen 1.26.3 version Confidentiality All information contained in this document is confidential. Its use outside the scope of this consultation or its disclosure to external parties is subject to preliminary approval by Lyra Network. Description of reporting Intellectual property rights - 3 / 38 2. GETTING IN TOUCH WITH TECHNICAL SUPPORT In case of a problem with connection to the Back Office, click on "Forgotten password or locked password". For technical inquiries or support, you can reach us from Monday to Friday, between 9am and 6pm by phone at: 0 811 708 709 from France, (Azur Number – Cost of a local call from a landline) +33 567 223 329 from abroad, by e-mail: [email protected] To facilitate the processing of your demands, you will be asked to communicate your shop ID (8 digits). You will find this information in the subscription confirmation e-mail or in the Back Office (Settings > Shop > Configuration). Description of reporting Intellectual property rights - 4 / 38 3. GENERAL PRINCIPLES OF REPORTING The PayZen platform offers various reporting levels to merchants in order to accompany them in their daily data management. The merchant can make real-time or slightly delayed reports depending on the selected type. The platform provides preformatted reports and provides the ability to create custom exports from the Merchant Back Office. All report results are available in Test and/or Production mode and refer to the transaction identifier originally found in the payment request data. In order to receive the reconciliation and chargeback reports, the merchant must send a request to the purchaser so that this information can be transmitted to PayZen. Description of reporting Intellectual property rights - 5 / 38 4. IDENTIFYING REPORT FILE TYPES The used format is commonly called "CSV" (which stands for Comma Separated Values), it is notably supported by Microsoft Excel. The names of report files should strickly follow the provided guidelines and must provide 5 pieces of information all separated by the underscore character "_". Nomenclature Description CODE The code is made up of the original initials of the report name: • JO = Operations report • JT = Transactions report • JRB = Bank reconciliation report • JRI = Chargebacks reconciliation report SHOP-LABEL The shop name in capital letters as it was defined in the Merchant Back Office WEBSITE-IDENTIFIER The 8-digit website identifier as it was defined in the Merchant Back Office DATE or WEEK or MONTH One of the 3 pieces of information will be used depending on the report frequency: • Daily frequency: DATE of report generation in the YYMMDD format • Weekly frequency: WEEK of report generation in the YYWXX format (W stands for Week and XX for the number of the week) • Monthly frequency: MONTH of report generation in the YYMXX format (YY for the last two digits of the year, M for month and XX for the number of the month) VERSION The display of the version depends on the report type: • For the Transactions report: No version • For the Operations report: V3 • For the Bank reconciliation report: V1 • For the Chargebacks reconciliation report: V1 Examples • Daily The collected data informs about the transactions of the day. The file will be named: CODE_SHOP-LABEL_WEBSITE-IDENTIFIER_DATE_VERSION.csv The operations report of 06/04/2016 of the "demo_shop" shop (identifier 12345678) will be named: JO_DEMO-SHOP_12345678_160406_V3.csv The transactions report of 06/04/2016 of the "demo_shop" shop (identifier 12345678) will be named: JT_DEMO-SHOP_12345678_160406.csv • Weekly The collected data informs about the transactions of the week. The file will be named: CODE_SHOP-LABEL_WEBSITE-IDENTIFIER_WEEK_VERSION.csv The operations report of 06/04/2016 of the "demo_shop" shop (identifier 12345678) will be named: JO_DEMO-SHOP_12345678_16W14_V3.csv The transactions report of 06/04/2016 of the "demo_shop" shop (identifier 12345678) will be named: JT_DEMO-SHOP_12345678_16W14.csv • Monthly Description of reporting Intellectual property rights - 6 / 38 The collected data informs about the transactions of the month. The file will be named: CODE_SHOP-LABEL_WEBSITE-IDENTIFIER_MONTH_VERSION.csv The operations report of 06/04/2016 of the "demo_shop" shop (identifier 12345678) will be named: JO_DEMO-SHOP_12345678_16M04_V3.csv The transactions report of 06/04/2016 of the "demo_shop" shop (identifier 12345678) will be named: JT_DEMO-SHOP_12345678_16M14.csv Note In test mode, the filename is always prefixed with TEST_. Description of reporting Intellectual property rights - 7 / 38 5. USING PREFORMATTED REPORTS By default, the content of preformatted reports is configured on the PayZen platform. There are four types of preformatted reports available to the merchant: 1. Transactions report Transactions report, also called JT, is a workflow management tool. It informs the merchant about all the payments (accepted and refused) performed in his/her shop. The provided data can be processed automatically or manually. The merchant can analyze the content, update his/her databases, verify his/ her orders for which the payment has been accepted before making the delivery. 2. Operations report Operations report, also called JO, is a workflow management tool. It informs the merchant about the evolution of the transaction lifecycle in his/her shop. The provided data can be processed automatically or manually. The merchant can analyze the content, update his/her databases. 3. Bank reconciliation report Bank reconciliation report, also called JRB, is a workflow management tool. It allows the merchant to reconcile transactions perfomed on the payment platform with the payments that appear on his/her bank statement. 4. Chargebacks reconciliation report Chargebacks reconciliation report, also called JRI, is a workflow management tool. It allows the merchant to reconcile transactions perfomed on the payment platform with the received non- payments. Each preformatted report file consists of a series of records. A "record" is a list of parameters separated

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    38 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us