KSeF 2.0 vs 1.0: What Changed in the API and the FA(3) Schema
On 1 February 2026 the FA(3) schema replaced FA(2) and the production 1.0 API stopped working. This was a new integration contract, not an upgrade. Main API changes: JWT authentication decoupled from sessions, mandatory encryption of every invoice, KSeF certificates, per-invoice batch processing, new duplicate detection, new permission model. Main schema changes: an attachment node, a new "Employee" party role, the 0% rate and the NP code split into specific codes, flexible payment terms, IBAN up to 34 characters. The consequences are commercial, not only technical: invoice numbering, VAT rate mapping, and who in your accounting team can actually see a client's invoices.














