How to generate your Releases report?
Generating channels
You can generate a Release report from your Mercado Pago account:
| Channels | Description |
| Mercado Pago panel | To manually generate the report from your Mercado Pago panel, go to Reports and choose "Created reports". Follow the step by step to generate reports from your panel. |
| API integration | Schedule the frequency of your report according to your needs. It can be both manually and on a scheduled basis. Read the documentation to generate reports through API. |
Technical characteristics of the report
Consider the following technical information when you want to generate, schedule and set up your reports
Report structure
Know the characteristics of the elements that make up your report.
| Element or action | Characteristics |
| Tables Detail | The detail of the tables includes information generated in at least 1 day. |
| Column Order | Fix |
| Maximum Period | Reports with data of up to 60 days. |
| Currency | Local (based on the country where the Mercado Pago account is registered) |
| Time zone of the columns | GMT-4 Take as reference the place where you download the report from. |
| Date selection via web | It must be based on the timezone of the user's account. For example, the timezone of Sao Paulo corresponds to the user account registered in Brazil. |
Report Export
All the options you have available when downloading your report.
| Element or action | Characteristics |
| Filename format | When the report is scheduled or manual: "prefix-custom-created-date.csv" Example: mystore-28-05-2019.csv |
| Download formats | .csv, .xlsx Tip:Download the report in .csv to import the data and use it in other applications. Download it in .xlsx to read the information in the spreadsheet tables. |
| File | Generated reports are saved in your Mercado Pago account. |
Notifications
Webhook
Webhook (also known as "web callback") is a simple method that allows an application or system to send real-time data whenever a particular event takes place, that is, it is a way to passively receive information between two systems via an HTTP POST. In the case of the reports used for reconciliation, a notification is sent to the user who has set up this service when their files are generated.
| Attribute | Description |
| transaction_id | Transaction ID |
| request_date | Request date |
| generation_date | Generation date |
| files | Available files |
| type | File format |
| url | Download link |
| name | File name |
| status | Report status |
| creation_type | Manual or scheduled creation |
| report_type | Report type |
| is_test | Determines if it is a test |
| signature | Notification signature |
Password for encryption
To ensure the notification process to the system, an attribute called signature will be sent in the body of the message (payload) in order to validate that the Webhook notification originated from Mercado Pago and that it is not an imitation.
The signature is build up by joining the transaction_id with the password for encryption configured in the "Webhook Notification" section, plus the generation_date of the report. Once the values are joined, they are encrypted using the BCrypt algorithm as follows:
signature = BCrypt(transaction_id + '-' + password_for_encryption + '-' + generation_date)
To validate that it is Mercado Pago who issued the notification, the verification function offered by the BCrypt algorithm for the desired language must be used.
Java example:
BCrypt.checkpw(transaction_id + '-' + password_for_encryption + '-' + generation_date, payload_signature)