Introduction to fiskaly

fiskaly provides cloud-based fiscal compliance APIs for European POS systems. If your software handles cash or card transactions in a country with fiscal signing laws, fiskaly handles the regulatory complexity so your team does not have to.

This page answers the three questions every new customer asks: what does fiskaly do, which products do I need, and how much work is the integration.

💡Just want to write code?

Skip to the Quick Start — sandbox access and your first signed transaction in under 5 minutes.

What fiskaly does

European countries require electronic cash registers to cryptographically sign transactions, generate audit-ready exports, and in some cases transmit data to tax authorities in real-time. The regulations, formats, and certification requirements differ by country.

fiskaly replaces all of that with a single REST API:

1. You send transaction data (amounts, VAT rates, payment type)
2. fiskaly signs it with a certified cryptographic module (TSS, SCU, etc.)
3. You receive a signature to print on the receipt (often as a QR code)
4. fiskaly stores the audit trail and generates compliant exports on demand

No hardware. No local crypto modules. No manual filing. The signing infrastructure runs in certified cloud data centers and is always up-to-date with regulatory changes.

Which products do you need?

This depends on which countries you operate in and what your obligations are. Here is the decision framework:

Question	Product	Required?
Do you process POS transactions in DE, AT, FR, ES, IT, or SE?	Sign DE / AT / FR / ES / IT / SE (digital signing, per country)	Yes — legally required
Do you operate in Germany?	DSFinV-K (fiscal export)	Yes — required for audits
Do you operate in Germany?	SUBMIT DE (ELSTER filing)	Yes — required since 2025
Do you operate in Germany?	Management API (org management)	Optional
Do you need to archive fiscal data for 10-30 years?	SAFE	Recommended
Do you issue B2B invoices in Belgium (or soon DE/FR/IT/PL)?	E-Invoice	Yes (BE), coming for others
Do you want to replace paper receipts?	eReceipt	Optional

Most common starting point: SIGN DE + DSFINVK DE + SUBMIT DE for a Germany-only POS integration. This covers the full legal obligation.

📘For Product Managers

See the Integration Planning Guide for effort estimates, team requirements, dependency maps, and a rollout timeline template you can adapt for your roadmap.

How the API works (all products)

Every fiskaly product follows the same integration pattern:

1. Authenticate

   POST /auth with your API key and secret. You receive a Bearer token valid for 24 hours and a refresh token valid for 48 hours.

2. Provision resources (one-time)

   Create the signing resource for your country: a TSS in Germany, a SCU in Austria, a signing unit in France/Italy/Spain. Each resource maps to a physical location or POS terminal.

3. Sign transactions

   For each transaction, PUT the transaction data (state, amounts, VAT rates) against the signing resource. The response includes a cryptographic signature.

4. Generate exports

   On demand or on a schedule, trigger compliant data exports (DSFINVK DE, TSS export, archive) via the API.

Two API architectures

fiskaly provides two API architectures, both actively supported:

Specialized APIs (SIGN DE, SIGN AT, SIGN ES) — purpose-built for a single country’s regulations. Deep, optimized, country-specific endpoints and resource models.

Unified API (SIGN FR, SIGN IT, SIGN SE coming) — one shared resource model across countries. Integrate once, add another country by changing the payload schema.

	Specialized APIs	Unified API
Countries	Germany, Austria, Spain	France, Italy, Sweden (coming)
Org management	Separate Management API	Built into the product API
Adding a country	Integrate a separate API	Change the payload schema
Best for	Single-country depth	Multi-country expansion

See The Unified API for the full comparison, resource model, and integration walkthrough.

Multi-country expansion

The expansion path depends on which countries you are adding:

• Adding another Unified API country (e.g., FR + IT): ~1 week. Same base URLs, same headers, same resource model — only the Taxpayer fiscalization section and Record payload schema change.
• Adding another Specialized API (e.g., DE + AT): 1-3 weeks. Similar patterns but different API surfaces and endpoints.
• Mixing architectures (e.g., DE + FR): You integrate both. They share the same Bearer token authentication pattern but have different resource models and base URLs.

Environments

fiskaly provides two environments for every product:

Environment	Purpose	Data	Billing
TEST (Sandbox)	Development and integration testing	Ephemeral — can be reset	Free
LIVE (Production)	Real transactions with real signatures	Permanent — audit-relevant	Billed per contract

All new organizations start in TEST. You switch to LIVE through the HUB after completing your integration.

⚠️TEST and LIVE are separate

Resources created in TEST do not exist in LIVE. Plan for a provisioning step in your go-live checklist.

Our Products

SIGN DE (Germany)

KassenSichV — BSI-certified Cloud-TSS, valid until 2033

SIGN AT (Austria)

RKSV — cloud-based signing with FinanzOnline integration

SIGN FR (France)

NF525 — certified signing with offline replay mode

SIGN ES (Spain)

TicketBAI & Verifactu — real-time XML submission

SIGN IT (Italy)

Corrispettivi telematici — cloud RT with receipt lottery

SIGN SE (Sweden)

InfraSec TCS — X.509 certificate-based signing

Next Steps

Quick Start (Developers)

First API call in under 5 minutes. Sandbox, cURL, and multi-language examples.

Integration Planning (PMs)

Effort estimates, team requirements, dependency maps, and rollout templates.

API Reference

All product endpoints, base URLs, authentication, and rate limits.

AI & Agent Integration

MCP server, machine-readable endpoints, and best practices for AI-powered integrations.