Introduction to RECEIPT
What is RECEIPT?
Section titled “What is RECEIPT?”RECEIPT replaces paper receipts with legally compliant digital receipts that customers access via QR code, email, or link. No app download or account creation required — receipts are viewed in the browser at receipt.fiskaly.com.
Unlike SIGN (which is legally required for fiscal compliance), RECEIPT is an optional product. It adds value by reducing paper waste and improving customer experience, but it is not a regulatory obligation.
Do you need RECEIPT?
Section titled “Do you need RECEIPT?”| Scenario | Recommendation |
|---|---|
| You want to reduce or eliminate paper receipts | Yes — RECEIPT replaces paper with digital |
| You need fiscal signing for POS transactions | No — that is SIGN, not RECEIPT |
| You want end-to-end audit trail from signing to receipt delivery | Use RECEIPT + SIGN together |
| You only issue B2B invoices | No — use E-INVOICE instead |
How it works
Section titled “How it works”- Your POS sends transaction data to the RECEIPT API after completing a sale
- fiskaly generates a digital receipt with your merchant branding and all required fields
- The customer receives the receipt via QR code (scan at POS), static code (counter display), email, or direct link
- The receipt is hosted at
receipt.fiskaly.com— immutable, always accessible, no app needed
If you also use fiskaly SIGN, RECEIPT can automatically link digital receipts to signed transactions, providing fiscal signature data and QR code validation on the receipt itself.
Key features
Section titled “Key features”| Feature | Details |
|---|---|
| EU-wide compliance | Meets electronic document requirements under EU VAT Directive for all EU countries |
| No customer app | Receipts are web-based — no download, no account, no registration |
| Multiple delivery channels | QR code, static code, email, or shareable link |
| SIGN integration | Optional automatic linking to signed transactions for audit trail |
| ISO 27001 certified | Data security guaranteed by fiskaly’s ISO 27001 certification |
| Immutable | Receipts cannot be modified after creation — full audit trail |
Integration effort
Section titled “Integration effort”| Scenario | Duration | Notes |
|---|---|---|
| Basic integration | 1-2 weeks | Auth, create receipts, display QR code at POS |
| With SIGN linkage | +1-2 days | Link receipt creation to SIGN transaction responses |
The integration is country-independent — the same API works across all EU countries.
Try it
Section titled “Try it”Create a demo receipt to see the customer experience before integrating.
Next steps
Section titled “Next steps”Integration Guide
Step-by-Step Integration walkthrough with code examples
RECEIPT API Reference
Full OpenAPI specification with all endpoints and schemas
For common questions about RECEIPT, see the FAQ on support.fiskaly.com.
Was this page helpful?