To download the documentation of the MUX and Auxiliary Registry entries, through Web Services, you will need to use the Download Entries mode. To send the XML request, you will need to use the PCI generic messaging .

Within the XML request, in the specific data part of the request, it will be necessary to incorporate the specific messaging of the MUX_DESCARREGA modality.

Only documentation associated with entries generated by the applications can be recovered:

  • e-TRAM
  • e-NOTUM
  • EACAT/Transmissions
  • SIR

for the rest of the applications, it is NOT possible to recover the documentation of the records using this modality. A clear example of the entries that do NOT have the MUX_DESCARREGA modality available for downloading the documentation associated with them are those generated by the e – FACT application (Electronic Invoices); for these entries, the download will be via direct integration into the e.FACT Hub.

Additionally, as good practices in relation to downloading documentation associated with settlements, please note the following:

  • There may be entries that you have inventoried in your Registry, but, for example, by not responding within the maximum expected time of 15 seconds, we end up generating the entry in the Auxiliary Registry EACAT. Well, the MUX_CONSULTA mode is used to review the entries that have ended up in the Auxiliary Registry EACAT and thus, avoid making unnecessary consumptions of the MUX_DESCARREGA mode to retrieve the documents associated with the entries with your numbering, which in reality, we do not have inventoried, since they were finally registered in the Auxiliary Registry EACAT, with the typical numbering of this one (E/XXXXXX-2021 or S/XXXXXX-2021).