Skip to main content

Digital Certificate

In order to comply with TicketBAI, the billing or POS system must be equipped with a software that generates an XML file for each transaction, signs it with a digital certificate and sends it to the corresponding Tax Authority.

The signature of the TicketBAI Files is carried out in the SIGN ES API signing component.

Each invoice will be chained to the previous one and the digital signature guarantees that the information is not tampered with. For this, a digital certificate provided by a Qualified Trust Service Provider (eIDAS QTSP) is required.

TicketBAI legislation allows the use of the following types of Digital Certificates:

  • Device certificate
  • Natural person or entity representative certificate
  • Company seal
  • Self-employed certificate

Device Certificate

At fiskaly, we've decided to implement a Device Certificate due to it's multiple advantages:

  • It has been created exclusively for TicketBAI. It does not provide access to any other of the taxpayer's information within the Tax Authority.
  • The taxpayer does not have to provide it's own private certificate.
  • The signing and sending of the TicketBAI files can be done with the same certificate.

fiskaly’s SIGN ES API uses a Device Certificate provided exclusively for TicketBAI by Izenpe. The certificate is contained by each Signing Device object, but must be associated to the taxpayer’s NIF within the corresponding Tax Authority (See Certificate Registration section).

By performing the registration of fiskaly’s Device Certificate, the effort is minimized. However, the system allows for the introduction of a Device Certificate by the POS provider if required.


Due to the certificate type selected, TicketBAI legislation does not allow for the creation of invoices by a third party or recipient. Only invoices created by the taxpayer indicated in the Signing component can be issued and sent to the Tax Authorities.


stay up-to-date