Verifactu vs. TicketBAI: key implementation differences

Tip

Last updated on 2025-08-28.

In SIGN ES the integration flow is essentially the same for both Verifactu and TicketBAI. 

The differences come from territory-specific rules related to (1) how to handle offline/connection-loss scenarios, (2) the QR placement and mandatory texts on the invoice, and (3) the certificate used to sign.

 

Offline / connection-loss: 

Verifactu: https://developer.fiskaly.com/sign-es/integration_process 

TicketBAI: https://developer.fiskaly.com/sign-es/connectionloss

 

QR positioning & compliant texts: 

Verifactu: https://developer.fiskaly.com/sign-es/invoicecompliance_verifactu 

TicketBAI: https://developer.fiskaly.com/sign-es/invoicecompliance

 

Signer / certificate: 

TicketBAI requires a device certificate: https://developer.fiskaly.com/sign-es/device_certificate 

Verifactu uses fiskaly’s electronic certificate: https://developer.fiskaly.com/sign-es/electronic_certificate