Nexi payment support (SoftPOS)​

Nexi is now supported as a payment provider. The integration is based on the Nexi MyPayments SoftPOS app — a software-based card reader — so no separate payment terminal is required: the Android device running the InStore App acts as the card reader.

Supported actions are payment, refund and cancel, all triggered directly from the InStore App.

Affected issue(s): #728

SumUp payment support​

SumUp is now supported as a payment provider. Payments are processed through the SumUp app (PaymentSwitch), which means a SumUp Solo or Solo Light reader can be used without any additional integration effort.

When a merchant API key is configured in the settings, the InStore App additionally uses the SumUp cloud API for:

• refund
• cancel
• improved payment receipts with the full transaction details

Without an API key, only payment is available. See the feature matrix in our Documentation for the exact scope.

Affected issue(s): #739

Official GP tom certification​

The InStore App has successfully passed the official GP tom certification process and is now listed as a certified partner solution: GP tom: fiskaltrust InStore App.

The GP tom App2App integration is approved for production use from InStore App v1.3.2-rc3 onwards.

Affected issue(s): #112

Other Changes​

Bug fixes​

• [Receipt] When printing a receipt on Shift4 fails (e.g. because of a connection error) it was still reported as successful #758

The Service Portal now warns you immediately when the account you are working on is changed in another browser tab — for example after switching to a different account or signing in as a different user. Out-of-date tabs are blocked with a clear message, so nothing is accidentally done on the wrong account.

Why This Matters​

The Service Portal can only be signed in as one user and one active account per browser. Many of you — especially PosDealers who manage several customer accounts — work in multiple tabs at the same time. Until now, switching the account in one tab silently affected every other open tab: those tabs kept displaying the previous account while everything you did in them was already applied to the newly selected account.

In the worst case, this meant configuration changes could land on the wrong customer account without any visible hint that something was off. This update removes that risk: the moment your account context changes anywhere in the browser, every other tab tells you — instantly and unmissably.

What Changed​

• When the active account changes in another tab, all other open portal tabs immediately show a blocking warning dialog. It names both accounts — the one the tab was showing and the one the browser is now working on — so you always know exactly what happened.
• The dialog cannot be dismissed by accident: to continue, you choose Reload page, which takes you to the dashboard of the now-active account.
• If a different user signed in on the same browser, the warning offers an additional Sign out option.
• If you switch back to the original account before reloading, the warning disappears by itself and you can simply keep working.
• Nothing changes for anyone working in a single tab — the warning only ever appears when a tab has genuinely fallen out of sync.

Impact​

This affects all markets and requires no action on your side. The warning is most valuable for PosDealers and consultants who work on several customer accounts in parallel tabs — accidental changes on the wrong account are now effectively prevented. The feature is being rolled out gradually; the warning currently appears on the portal's modernized pages, which cover the vast majority of daily workflows.

This release makes the automatic Epson RT printer reboot after a successful daily closing, which was introduced always-on in 1.3.85, opt-in via a new SCU configuration flag.

🇮🇹 Breaking Change: Automatic Epson RT printer reboot after daily closing is now opt-in (fiskaltrust/middleware#702)​

In 1.3.85 the Epson RT printer was rebooted automatically after every successful daily closing (ZReport) to work around printers that occasionally get stuck during the day. Because this behavior is not desirable for every deployment, it is now opt-in and disabled by default.

To keep the automatic post-closing reboot, set the new ForceRebootAfterDailyClosing flag to true in the Epson RT printer SCU configuration.

Deployments that were relying on the always-on behavior introduced in 1.3.85 will no longer reboot the printer after a daily closing until this flag is enabled. The manual reboot triggered from the POS via the Zero Receipt flag (0x0000_0040_0000_0000) is unaffected and continues to work as before.

Affected packages:​

• fiskaltrust.Middleware.SCU.IT.EpsonRTPrinter

This release brings full support for the Italian receipt lottery (Lotteria degli Scontrini) across all Italian SCUs, marks the first stable release of the Custom RT printer SCU, adds manual and automatic reboot support for the Epson RT printer, a recovery option for interrupted SCU switches in the German market, and a fix for the German QR-code that ensures tax amounts are always printed with exactly two decimal places.

🇮🇹 Release: Custom RT printer SCU is now generally available​

The Custom RT printer SCU, previously shipped as a release candidate in 1.3.84, is now generally available with 1.3.85. It can be used in production alongside the existing Epson RT printer and Custom RT server SCUs.

Affected packages:​

• fiskaltrust.Middleware.SCU.IT.CustomRTPrinter

🇮🇹 Feature: Full receipt lottery support across all Italian SCUs (fiskaltrust/middleware#698, fiskaltrust/middleware#699)​

The Italian receipt lottery (Lotteria degli Scontrini) is now fully supported on all three Italian SCUs. Sale receipts (POSRECEIPT) now correctly carry the customer's lottery code (codicelotteria) provided by the POS: the code is exposed both in the dedicated <rt-lottery-id> signature and in the Codice Lotteria: line of the [www.fiskaltrust.it] footer.

POS creators that already send the lottery code do not need to change anything — it will simply start appearing on the receipt signatures after updating, using the same flow across all three Italian SCUs.

Affected packages:​

• fiskaltrust.Middleware.SCU.IT.EpsonRTPrinter
• fiskaltrust.Middleware.SCU.IT.CustomRTPrinter
• fiskaltrust.Middleware.SCU.IT.CustomRTServer

🇮🇹 Feature: Manual and automatic Epson RT printer reboot (fiskaltrust/middleware#691, fiskaltrust/middleware#693)​

The Epson RT printer can occasionally get stuck during the day and needs to be restarted to continue processing receipts. The Epson RT printer SCU now supports two ways to trigger a printer reboot:

• Manual reboot from the POS: a new local ftReceiptCaseFlag (0x0000_0040_0000_0000) can be set on a Zero Receipt to instruct the SCU to reboot the connected printer on demand.
• Automatic reboot after daily closing: after a successful daily closing (ZReport), the Epson RT printer is now rebooted automatically. If the closing itself fails, no reboot is sent.

Because the printer does not respond to the reboot command, the operation blocks for up to the configured client timeout (~15s) before returning, so daily closings and manual reboots may take that much longer to complete.

Affected packages:​

• fiskaltrust.Middleware.SCU.IT.EpsonRTPrinter

🇩🇪 Feature: Void support for Initiate-SCU-Switch receipts (fiskaltrust/middleware#690)​

When switching from one TSE to another, a failed Finish-SCU-Switch previously left the queue in a state that was hard to recover from without manual intervention. It is now possible to void a previously issued Initiate-SCU-Switch receipt, which reconnects the queue to the source SCU. If the source SCU is no longer reachable, the existing Force flag can additionally be combined with the Void flag to reset the state anyway, after which the SCU switch can simply be reconfigured and retried.

Affected packages:​

• fiskaltrust.Middleware.Queue.*

🇩🇪 Bug Fix: QR-code tax totals always printed with two decimal places (fiskaltrust/middleware#678)​

The gross tax totals ("Brutto-Steuerumsätze") embedded in the German QR-code are now always formatted with exactly two decimal places, as required by the Kassensicherungsverordnung. Previously, receipts with more than two decimal places in a tax amount could produce a QR-code that did not conform to the expected format, which could cause issues during a tax audit. No POS-side change is needed — receipts processed after the update will use the corrected format automatically.

Affected packages:​

• fiskaltrust.Middleware.Queue.*

Added: New onboarding guides, POS System API content, and Delivery documentation​

New onboarding process guides​

Added two new onboarding guides to support partners throughout the fiskaltrust onboarding process:

• Onboarding Process – Roles and Flow: provides an overview of the onboarding process, key roles, responsibilities, and interactions between participants.
• PosDealer Onboarding Guide: offers step-by-step guidance for PosDealers, covering the activities required to onboard customers and prepare them for fiscalization.

Why it matters: These guides provide a clearer onboarding journey for both PosCreators and PosDealers, helping partners understand their responsibilities, reduce onboarding effort, and get customers operational more efficiently.

New POS System API section​

Added a dedicated POS System API section under PosCreators, including documentation for the API, a new guide for integrating with the POS System API using Android Intents, and a new migration guide from v0 to v2 to support upgrading existing implementations.

Why it matters: Users now have a single, structured entry point for POS System API documentation, including practical Android integration guidance and a clear migration path for moving from v0 to v2, making adoption and upgrades more straightforward and consistent.

Delivery page for Experience Middleware​

Added a new Delivery page under Experience Middleware to document delivery-related concepts and workflows.

Why it matters: Users can more easily understand and implement delivery scenarios within the fiskaltrust ecosystem.

Updated: API navigation improvements​

API version selection in the documentation​

Updated the APIs navigation menu to display both POS System API 2.0 and POS System API 2.1 versions.

Why it matters: Users can quickly access the documentation version that matches their implementation, making it easier to work with different API releases.

Creating a quote at the end of a business rollout now takes you straight to your basket. The extra "Almost Done!" confirmation page is gone, so checkout is one click shorter.

Why This Matters​

When you finished configuring a business rollout and created a quote, the portal used to stop on an intermediate "Almost Done!" page. That page did nothing except offer a single "Add to Basket" button — the same action the basket already lets you perform, since your quotes are listed right there in the checkout view. It was an extra screen and an extra click standing between you and completing your order, with no information or choice to justify it.

We removed that detour. Now, the moment your quote is created, its full configuration is loaded into your basket and you are taken directly to the cart, ready to review and check out. The result is a quicker, more direct path from "I've planned my rollout" to "I'm ready to order" — less clicking, less waiting, and no dead-end screens.

What Changed​

• After you create a quote at the end of a business rollout, you now land directly in the basket with your rollout configuration already added — there is no longer a separate "Almost Done!" page to click through.
• The button at the end of the rollout summary now reads "Create quote & go to basket", so it's clear up front that a single click both creates your quote and opens the cart.
• While this happens you'll see a short progress indicator for each step — first "We are creating your quote", then "Adding to basket".
• If your quote is created but adding it to the basket runs into a problem, your quote is never lost or duplicated: the button simply offers to add the existing quote again, so retrying can't create a second quote.

Impact​

This affects anyone who creates quotes through the business rollout flow in Rollout Management, across all markets. There's nothing you need to do — the faster flow applies automatically the next time you complete a rollout. Your quotes and orders behave exactly as before; only the path to your basket is shorter.

When you act on behalf of one of your operators, the fiskaltrust Service Portal now shows a clear, persistent banner across every screen — so you always know exactly whose account your actions affect.

Why This Matters​

As a dealer or consultant, you can step into one of your operators' accounts to help them set things up or resolve an issue. Until now, the portal looked exactly the same whether you were working in your own account or in an operator's — nothing on screen told the two apart. That made it easy to lose track of which context you were in, and to make changes against an operator's account while believing you were in your own.

The new banner removes that ambiguity. At a glance, and on every page, you can see whose account you are currently working in. It turns a subtle, error-prone situation into one that is obvious and safe — acting as a real safeguard, not just a label.

What Changed​

• Whenever you are acting on behalf of an operator, a banner stays pinned to the top of the portal. It remains visible no matter where you navigate.
• The banner names the operator and states the consequence in plain language: "You are acting on behalf of [Operator]. Everything you do here affects only this operator's account."
• To leave the operator's context, use Back to your account in the top bar. The banner disappears the moment you return to your own account.

Impact​

This update affects dealers and consultants who act on behalf of their operators. No action is required on your side — the banner appears automatically whenever you are working in an operator's account, and disappears as soon as you return to your own.

Availability​

The banner is already live in the Sandbox environment, where you can try it out today, and will be rolled out to Production across all markets over the coming days.

This release focuses on stability and correctness improvements for the Italian market — covering the Epson RT printer, the Custom RT server and Custom RT printer SCUs — and on a reliability fix for German TAR-file exports against the Fiskaly cloud TSE.

🇮🇹 Bug Fix: Monthly / Yearly closing receipts no longer fail on the Custom RT server (fiskaltrust/middleware#654)​

Sending some closing receipts (monthly, yearly) or other receipt cases that the Custom RT server does not actively process previously caused the SCU to throw an exception, which surfaced as a failed receipt on the POS side. The Custom RT server SCU now handles these cases gracefully: monthly and yearly closings are processed in the same way as a daily closing, and any other receipt cases that do not require signing simply return a successful, empty response. This means a POS can safely send closing receipts in all markets without having to know in advance whether the SCU supports them.

Affected packages:​

• fiskaltrust.Middleware.SCU.IT.CustomRTServer

🇮🇹 Bug Fix: Prevent duplicate fiscal receipts on Epson RT printer network timeouts (fiskaltrust/middleware#652)​

If the Epson RT printer had already printed a fiscal receipt but the response could not reach the Middleware due to a network timeout, the POS would retry the request and the printer would emit a second receipt — leading to duplicated receipts, VAT amounts and revenue. The Epson RT printer SCU now detects this situation by checking the printer's last emitted document against an internal cache and reconstructs the original response instead of triggering a retry. For the first receipt after a Middleware restart, a fallback based on the receipt amount is used.

Affected packages:​

• fiskaltrust.Middleware.SCU.IT.EpsonRTPrinter

🇮🇹 Feature: Support for subtotal-level discounts and surcharges on the Epson RT printer (fiskaltrust/middleware#643)​

The Epson RT printer SCU now correctly applies discounts and surcharges at the subtotal level ("sconto a subtotale") when generating fiscal receipts, matching the behaviour expected by Italian fiscal regulations. In addition, payment items with negative amounts caused by such discounts are now handled correctly, so the printer no longer rejects the receipt.

Affected packages:​

• fiskaltrust.Middleware.SCU.IT.EpsonRTPrinter
• fiskaltrust.Middleware.SCU.IT.CustomRTServer

🇩🇪 Bug Fix: Faster TAR-file exports against the Fiskaly cloud TSE (fiskaltrust/middleware#639)​

We've updated our polling so that exports should be available faster.

Affected packages:​

• fiskaltrust.Middleware.SCU.DE.FiskalyCertified

HomeScreen WebView configuration​

The HomeScreen WebView can now be enabled and its URL configured per device directly in the local settings. When active, the blue header bar is hidden, letting the WebView run in true fullscreen. Settings and receipt history remain just a left-edge swipe away.

Affected issue(s): #706, #594

Settings access PIN​

The settings page can now be locked with a 6-digit PIN, keeping unauthorized users like waiters from making configuration changes. Access is granted only after the correct PIN is entered, with a limit of 5 attempts per hour to deter brute-force attacks.

Affected issue(s): #699

UI/UX design refresh​

Continuation of the UI overhaul started in 1.3.0. The app's look and feel has been aligned with the new fiskaltrust design system, including a redesigned email and SMS input popups on the digital receipt screen. A new "Thank you" screen now closes the receipt flow, replacing the previous "Receipt was accepted..." notification which could appear on the wrong device in multi-terminal setups.

Affected issue(s): #581, #677, #678, #713

Other Changes​

Improvements​

• [Settings] Improve wording: replace Send per Mail/Send per SMS #683
• [Docs] Add Pax Global link #704

Bug fixes​

• [Payment] Progress screen is not usable on landscape screens (especially when they are small like on the Sunmi Smart Pad) + background color wrong #719
• [Payment] Worldline / PayOne SmartPOS - WPI Version Incompatibilities - TOM provides receipt as expected - SmartPOS uses new WPI_VERSION v2.2 format even if we request v2.1 -> moved to v2.2 for both integrations #696
• [Settings] When configuring a printer the Paper Width setting 48mm is not shown selected but can also not be clicked #695
• [Settings] Selecting a not available / turned off bluetooth printer - feels stuck - no info that we are trying to do a test printout #679
• [Printing] PayOne SmartPOS - Demo printout is not readable (looks like just some grey pixels in a single line) #734
• [Settings] app crash when deleting the tcp port for the network printer #736
• [Receipt] When using multiple devices with cbTerminalID configured still "Receipt was accepted..." message is shown on all devices and not just the one on which the receipt was accepted #713
• [Receipt] Consumer mode countdown is missing the "s" info just shows "... in 10" instead of "... in 10s" #735

We've made an important update to the role management in the fiskaltrust Service Portal. Now, if you are assigned only the PosOperator role, you won’t be able to sign into any other roles.

Why This Matters​

This change helps ensure that users with the PosOperator role focus on their specific responsibilities without the confusion of managing multiple roles. It simplifies the role management process and enhances compliance with our long-term goal of role restrictions.

What Changed​

• Users with only the PosOperator role will see that all other role sign-on buttons are disabled.
• When hovering over any disabled role, a helpful tooltip will appear, explaining that you can't sign any other roles while the PosOperator role is active.
• Existing users with multiple roles, including PosOperator, will not experience any changes to their current access.

Impact​

This update primarily affects users who hold the PosOperator role exclusively. If you are one of these users, you will notice the new restrictions in place. If you have multiple roles, you can continue using them as before for now, so no immediate action is required on your side. However, our long-term goal is to separate these roles more clearly. Therefore, users who are both POS Dealers and POS Operators should plan to migrate their POS Operator activities to a separate account in the future.

New payment vendor now supported: Shift4​

The new payment vendor Shift4 was added and supports all current features (payment, refund, cancel) including the new payment vendor provided tip.

Now supported payment vendors:

• Viva
• Hobex (POSit and ECR)
• Worldline / PayOne (Tab on Mobile and SmartPOS)
• Softpay.io
• Global Payments (GP tom and GP Pay)
• Shift4

Payment vendor provided tip support across payment providers​

Tips entered directly on the payment terminal are now reported back to the POS in a consistent way with all current supported payment vendors.

NOTE: To really use this fetaure, TIP support must be activated in most of the payment vendor configurations. If not enabled the standard payment flow without TIP will be used in the payment vendor applications and by us.

Affected issues: #534, #626, #632, #630, #384

Refund and cancel support expanded across payment providers​

Refund and cancel transactions - including payment vendor provided tip - are now supported on Viva, Hobex (POSit and ECR), Worldline / PayOne (Tab on Mobile and SmartPOS), Softpay.io, Global Payments (GP tom and GP Pay), Shift4.

See documentation for the newly added /pay actions refund and cancel

Affected issues: #578, #620, #635, #633, #609, #585

UI and performance overhaul​

Broad UI, usability and performance improvements across the app for a smoother day-to-day experience with main focus on the settings screen and startup loading. The performance improvement is especially visible on devices with older hardware and weaker CPU performance.

Affected issue: #651

Other Changes​

Features​

• [Payment] Hobex POSit and Softpay.io - add support for GetTransaction to allow retrieval of transaction result in case of connectivity issues with the payment vendor #619
• [Payment] Shift4 / S4 - printing support on Commerce Engine (running on PAX A800) #367
• [Printer] Add Scanner Support for viva Ciontek device (giveaway flow) #613
• [Payment] Shift4 / S4 - certification test #366

Improvements​

• [Settings] UX - Review and Refactor Print Delay Settings for Practical Use #262
• [Settings] printer config for network printer - try to provide better input keyboard for IP address so that no manual switch to numeric keyboard is necessary #546
• [Settings] Improve wording: replace Send per Mail/Send per SMS #683
• [Start Screen] Add some type of loading icon when the app is getting started #650
• [Pairing] Add a loading icon/progress bar when connecting to the cashbox after entering the pairing code #549
• [Docs] Update available-settings page to latest version #623
• [Docs] extend the manual installation guide to also give a link for the preview version for easier access to pre-release testable versions of the InStore App #521
• [DevKit] payment - tip handling is not clearly explained anywhere #596

Bug fixes​

• [Payment] Stuck in "4. Processing Payment" when a critical exception happens in the background payment state machine --> should somehow catch the error + continue after usual error info #605
• [Payment] Improve Viva receipt (remove 0 tip amount + add card name) #243
• [Payment] Worldline/PayOne - SmartPOS device support is broken and has to be reworked #657
• [Give Away] Add a popup with confirmation button to reensure that the receipt should get printed on the give away qr code #649
• [Email] Some valid email addresses fail to send despite being valid -> only check DNS MX records for the target domain #586
• [Pairing] Remove Long Press device pairing popup, since it has bugs and no one knows about it #554
• [Printer] Pax 3700 permission error for USB endpoint should only be shown in developer mode but not in normal mode so that users are not confused #560
• [Payment] GP tom is using sandbox package instead of prod package when using a prod build of the InStore App #685

SCU certificate expiration tracking​

The dashboard now shows when each SCU's certificate expires (DE market). Expiration dates are color-coded — green when more than 3 months out, yellow within 3 months, and red when expired — so operators can plan renewals before they become an emergency. The exact expiry date and timezone are available in a tooltip, and the queue detail view surfaces this information as well.

Redesigned data table​

The previous dashboard table has been replaced with a new flexible table that introduces column sorting, pagination, a search bar with filter chips, and smooth loading animations. Rows are now color-coded by health status — green for healthy, yellow for warnings, red for errors — giving an immediate visual overview of the entire fleet.

All queues are now included regardless of state (active, out of operation, not active), with state filtering handled through the new toolbar dropdowns instead of pre-filtering the data.

Smart filtering system​

The old stat-card filters have been replaced with multiple dropdown filters in the table toolbar:

• Issue filter — No Receipts (48h), Missing Daily Closing, SCU failures, SCU expiring in next 3 months, TAR file issues, and more — each showing a count
• Queue State filter — In Operation, Out Of Operation, Not Active
• CashBox Type filter — Cloud vs. Local
• Sorglos filter — Premium status

In-app receipt preview​

Clicking a receipt link now opens an in-app preview modal instead of navigating to an external URL. The modal embeds the digital receipt and optionally shows Request and Response tabs with the raw JSON data, making debugging faster without leaving the portal.

SCU failure state visibility​

A new column surfaces SSCD and USED failure states. Healthy SCUs show "OK" in green; failures show a red badge with the failure count. Hovering reveals detailed failure info including timestamps and queue item IDs.

Queue Detail View​

The detail view has been streamlined from a grid of metric cards to a clean list layout. It now includes the CashBox ID, POS System ID, and formatted receipt counters. DE-specific fields (certificate expiry, last TAR file, POS Archive status) are grouped in their own section. The "Last Failed Receipt" entry includes a button to open the receipt preview modal directly.

Account surrogation links​

Account names in the table are now clickable surrogation links, allowing partners to surrogate into a PosOperator's account directly from the dashboard.

CSV export​

The dashboard now includes a built-in CSV export that exports the currently filtered rows (not the full dataset). The export includes the new columns — SCU failure state, certificate expiry, and type information.

Layout fix​

Fixed an issue that caused an unnecessary scrollbar to appear on every page in the portal.

Available in the fiskaltrust Portal since March 17, 2026.

This release focuses on improvements and fixes for German market SCUs. It includes an update to the Fiskal Cloud Connector (FCC) to version 4.4.0 and a fix for certificate chain parsing in the SwissbitCloudV2 SCU.

🇩🇪 Improvement: Updated Fiskal Cloud Connector to version 4.4.0 (fiskaltrust/middleware#622)​

The bundled Fiskal Cloud Connector (FCC) has been updated from version 4.1.1 to 4.4.0.

Affected packages:​

• fiskaltrust.Middleware.SCU.DE.DeutscheFiskal
• fiskaltrust.Middleware.SCU.DE.SwissbitCloud

🇩🇪 Bug Fix: Fixed certificate chain parsing in SwissbitCloudV2 SCU (fiskaltrust/middleware#624)​

Fixed an issue where the SwissbitCloudV2 SCU returned the entire certificate chain as a single entry instead of properly splitting it into individual certificates. The TSE certificate chain is now correctly parsed into separate certificates, ensuring proper certificate validation and compliance checks.

Affected packages:​

• fiskaltrust.Middleware.SCU.DE.SwissbitCloudV2

This release brings important bug fixes and enhancements for the German and Greek markets. The focus is on improving reliability, compliance, and communication with fiscal service providers.

🇩🇪 Bug Fix: SwissbitCloudV2 Certificate Validation Error (fiskaltrust/middleware#615)​

Fixed an issue with certificate validation in the SwissbitCloudV2 SCU where the certificate chain was being incorrectly encoded as Base64. The certificates are now properly returned in their original Base64 format, resolving validation errors that could occur when verifying TSE certificates.

Affected packages:​

• fiskaltrust.Middleware.SCU.DE.SwissbitCloudV2

🇬🇷 Bug Fix: POS receipt refund now properly link to original receipts (fiskaltrust/middleware#601)​

Fixed an issue where refunds of POS Receipts were not linked to the original documents they referenced. When issuing a refund for a pos receipt and providing a reference to the original receipt, the system now properly correlates the documents using the multipleConnectedMarks field as required by Greek MyDATA regulations. This ensures that refunds for posreceipts are correctly associated with their original transactions, improving compliance and data accuracy in your fiscal reporting.

Affected packages:​

• fiskaltrust.Middleware.SCU.GR.MyDATA

🇩🇪 Enhancement: Improved Fiskaly API communication handling with Retry-After support (fiskaltrust/middleware#600)​

The middleware now properly handles server load situations when communicating with the Fiskaly TSE cloud service. When Fiskaly's servers are experiencing high load, they can signal the exact wait time needed before retrying a request. The middleware now respects these wait instructions, resulting in more reliable operations during peak usage periods. Additionally, the retry mechanism has been enhanced to handle more error scenarios automatically, reducing potential disruptions in your fiscalization workflows.

Affected packages:​

• fiskaltrust.Middleware.SCU.DE.FiskalyCertified

Enhancement: Configurable SQL command timeout for Entity Framework queues (fiskaltrust/middleware#612)​

You can now configure the SQL command timeout for Entity Framework (EF) queues using the new SqlCommandTimeoutSec configuration parameter. The default timeout is 180 seconds (3 minutes), which should be sufficient for most use cases.

To configure a custom timeout, add the SqlCommandTimeoutSec parameter to your queue configuration in the portal with the desired value in seconds.

Affected packages:​

• fiskaltrust.Middleware.Queue.EF

🇧🇪🇬🇷🇪🇸🇵🇹 Bug Fix: Resolved issue with incorrect success states during exception handling (fiskaltrust/middleware#586)​

This fix addresses a critical issue where the Middleware incorrectly returned success states when uncaught exceptions occurred during receipt processing. Previously, when an exception was thrown, the response would fail to properly mark the operation as failed, potentially leading to misleading status information. With this update, any uncaught exceptions are now properly logged and the receipt response is correctly marked as failed, ensuring accurate status reporting and improved error visibility.

Affected packages:​

• fiskaltrust.Middleware.Queue.AzureTableStorage
• fiskaltrust.Middleware.Queue.EF
• fiskaltrust.Middleware.Queue.MySQL
• fiskaltrust.Middleware.Queue.SQLite

Landscape display support​

This release introduces full landscape support, enabling users to operate the InStore App seamlessly on devices with landscape orientation and smaller screens. The user interface now adapts automatically to different display configurations.

Affected issue:
[Landscape support] allows to use the full functionality on landscape and smaller displays #356

Receipt preview: head down rotation support​

The receipt preview can now be rotated correctly when the device is turned upside down. This allows staff to easily show receipts to guests by simply rotating the device.

Affected issue:
[Receipt Preview] support to rotate the preview of the receipt to be rotated correctly when the user shows it to guests via rotating the device head down #304

Payment in progress screen​

A new payment status screen has been added that displays information about ongoing payment transactions. This provides clear visual feedback during payment processing instead of showing the Home screen.

Affected issue:
[Payment] add a new status / in progress screen (like "Payment starting...") that can show information about ongoing payment transactions so that we do not show the Home screen at this time #226

Other Changes​

Features​

• [Receipt] send by email - validate email address (syntax, domain check) #409
• [Receipt] send by SMS - validate phone number format #406
• [Receipt] send by SMS - dialogue should be with Numpad instead of full alphanumeric keyboard for easier phone number entry #83

Improvements​

• [Receipt] sending via SMS - delete misleading success popup #405
• [Docs] Add Viva Pax to "Also Supported" #503
• [Receipt History] Reorder (top receipt should be newest receipt) so that it is easier to find the last issues one without the need to scroll (which was the case on smaller, landscape devices) #477
• [Menu] Make LOGO size smaller when instore app is used on a small screen to allow showing more menu lines #476
• [Settings] rework "Print Demo" to have a better printout and rename to "Test printer connection" #283
• [Docs] Add documentation on how to install the InStore App from google play portal (Customer View) #359
• [Settings] cleanups (removed Middleware section, Danger Zone, Refresh DeviceConfiguration and NFC) #514
• [Settings] Select Printer - SmartPOS Printer gets also shown on Google Pixel and some other device - only show if available #542

Bug fixes​

• [Receipt] when the InStore app shows the settings screen while in the background a receipt issue arrives, the home screen replaces the settings screen but the receipt screen does not appear #399
• [Settings] printer selection - Bluetooth (BT) devices are only queried at startup so that later paired BT devices are not shown and and it does show all even if they do not support printing (like a headset) #295
• [Settings] IP Adresse reading error shown instead of real IP on Sunmi P2 SmartPad #500
• [Settings] make printer details are sometimes cut off and therefore partly unreadable --> shorten information to only show the important parts so that it is fully shown #382
• [Receipt Screen] toast showing action status or errors does overlap the last button on the screen #454
• [Android 7.1] full screen not correctly handled (results for example in "Copyright | fiskaltrust" is not shown in the side bar on Sunmi P2 Pro) #478
• [App icon] is not shown correctly on different Android versions #82
• [Receipt preview] is cut off and not scrollable and therefore not fully visible #293
• [Receipt History] showing receipts from receipt history has wrong scaling on Sunmi P2 Pro #284
• [Receipt] swipe up opens operator page if no operator buttons are configured --> only allow swipe up if there is at least 1 button configured #456
• [Settings] do not show "Print Demo" when printer "No printing" was selected as it makes no sense #160
• [Settings] Remove useless arrow in top header with no function in settings #446
• [Receipt printing] no delay in merchant mode available (also not configurable) as usually a trained user wants to have full control #470
• [App start] "No Internet Connection" Popup stays on screen, although the device has internet #524
• [Payment] Viva - refund and cancel do report the wrong action "payment" in the response payItem.Provider.Action info instead of "refund" or "cancel" --> will now report the real action executed #539

Release on Google Play​

The InStore App is now available on Google Play for easy installation and updates.

New payment provider: Shift4 payment integration (PREVIEW)​

You can now process payments with Shift4 terminal directly in the InStore App. This preview version supports payment, refund, and cancel actions.

Affected issue:
#138

Extended Viva Payment: refund and cancel support​

Viva Payments integration now supports refund and cancel actions in addition to payment processing.

Affected issue:
#161

Network printer support​

The InStore App now supports ESC/POS network printers with simple configuration. You can configure a network printer as the default printer using IP address and port without backend configuration.

Affected issues:
#395, #393

Device support for Android 16 and lower​

The InStore App now targets Android API Level 35 and supports devices running Android 16 and lower.

Affected issues:
#350, #232

Known Problems​

Other Changes​

Features​

• Support for Android 15 and Android 16 devices #415
• Include full version in APK filename #343
• Add v1 signature to APK for older devices (< Android 7.0) #352
• Restrict pairing code input to numbers only #291
• Hide IP address when mobile data is used #370
• Add documentation for InStore App installation from all supported portals #333
• Extend "Supported Stores" documentation #307
• Add documentation for "Refresh DeviceConfiguration" #259
• Add documentation for "Use local configuration" setting #260
• Add documentation for Terminal ID Filter #287
• Rename "multiterminal-support" to "multiterminal-settings" #334

Bug fixes​

• IP address section shows error on some devices (OM10, Sunmi P2 Pro) #275
• "Use prerelease" and "check for update" not working #310
• Failed test print still selects broken printer #317
• "App isn't responding" on first open after install (Android 12+) #318
• PAX A920 Pro demo print not working via NeptunePrinterProvider #316
• Multiple receipts printed when print delay expires #387
• Crash when entering pairing PIN without internet connection #331
• App crash at startup on slow systems #388
• Foreground service notification not visible by default #362
• Button remains visible after swiping down in merchant mode #433
• POS System API: Error when PIN starts with 0 (fixed) fiskaltrust/service-possystem-api#73

Affected markets: DE

Overview

In accordance with Section 146a (4) of the German Fiscal Code (AO), every electronic cash register or recording system must be reported to the responsible tax office within one month after being put into operation or taken out of operation. To support this legal requirement, we have implemented a complete Notification Management Process, including:

• Notification Management Page
• POS Operator Data pages
• Notification Worker (Azure Function)

New Features & Components

1. Notification Management Page (Dealer Portal) A new management interface is available for dealers, providing the ability to:

• View and manage all operators under their dealership
• Enable or disable automatic or manual notifications for each operator
• Review all sent notifications along with their statuses (successful, failed, pending)
• Trigger notifications manually for specific operators if needed

2. Operator Data Page

   A dedicated page where the operator can update all required data. The dealer sends the operator a link to this page. All necessary information for notifications is collected and validated here.

3. Notification Worker (Azure Function)

   A background worker runs every night at midnight, collecting the operator’s data and sending notifications to ERIC (third-party communication interface for German tax authorities).

Required Data for the Notification

Every notification must include:

• Operator information
• Outlet information
• Electronic recording system information


• Type of certified TSE
• Number of electronic recording systems
• Serial number of the electronic recording system
• Purchase date
• Commissioning date
• TSE information (extracted from the TseInfo JSON)

Common Issues Below is a list of frequently occurring errors and how to resolve them.

1. Invalid Tax Number Possible Causes a) The tax number does not match the scheme for the Bundesland (state) b) The company must report to another state than where it physically operates c) A regional 10–11 digit tax number is used instead of the required 13-digit number

2. Missing or Invalid Data: Third-Party CashRegister (TSE Serial Number)

   Error: TSE serial number must be at least 64 characters and hexadecimal (0-9, a-f, A-F)

3. Invalid TSE BSI Certification Number Required format: YYYY-NNNN

4. Missing Notification Product in the Outlet Problem: The outlet does not have an active notification product or carefree package.

5. ERIC Exception: Duplicate Serial Numbers Error: ERIC reports that the same recording system serial number is used multiple times. Cause: More than one queue shares the same Queue name. Solution: Operator → Configuration → Queues Remove duplicates: • Send “Out of Operation” receipt, or • Hide queue if it does not exist physically Then re-trigger the notification.

6. Missing TSE Information (TseInfoJson) Cause: No TSE data found in the last End-of-Day receipt → possible TSE connection problem. Solution: Check last End-of-Day receipt: • If TSE data exists → re-trigger notification • If not → fix the TSE connection problem or send a zero receipt to restore connection

7. Missing POS System Data (Model, Manufacturer) Cause: No valid POS System ID in the last End-of-Day receipt.

8. Invalid Date Order (PurchaseDate vs CommissioningDate) Error: Purchase date cannot be later than commissioning date.

9. ERIC Exception: Illegal Characters in Fields Error: Some characters in the legal company name or address are invalid.

Additional Notes

• To check if a POS System is assigned:

Operator → Related Queue → Receipt Journal

Last daily closing must show a correct POS System ID that exists in DE Dynamic

• A notification is only sent when:

✔ Notification state = true in Account Settings

✔ At least one outlet has an active notification subscription. And outlet should have at least one active queue or third party queue

✔ Operator has confirmed all required data

• Postal code and tax number both should be valid while validating the tax number ( The tax number must match the correct state (Bundesland) based on the postal code)

• We have implemented Notification_API and gradually extracting common logic from worker and portal into this API to centralize and simplify the validation and processing steps

• Notification will be send for active queues . Hidden queues or queues that became inactive before July 1st, 2025 will not receive notifications

Useful links:

• Knowledge base article on Notification Management:( you can find solutions for common error messages here) https://portal.fiskaltrust.de/KBArticle#/KA-01146/Tax%20office%20notifications:%20Solutions%20for%20error%20messages

• Correct tax identification number formats: https://de.wikipedia.org/wiki/Steuernummer

• 13-digit tax identification number converter: https://www.ueberbrueckungshilfe-unternehmen.de/DE/Infothek/Steuernummer-Umrechner/steuernummer-umrechner.html

Affected markets: ALL

Subscription Page Overview

As a PosDealer, you can get an overview of all your PosOperators' subscriptions in the PosDealer / Subscriptions tab of the fiskaltrust.portal. You can filter the list to display overdue or upcoming subscriptions and renew payments for multiple subscriptions simultaneously. On this page, you can also manage subscriptions by opting for automatic renewals, performing manual renewals, or canceling a subscription.

Improved: The Subscription Management page has been enhanced to provide a clearer overview of subscriptions. Users can now easily manage subscriptions renewal and cancellations. The interface has been redesigned for better usability and accessibility.

Users can now opt for automatic renewals for their subscriptions, ensuring uninterrupted service.

Once user opt out for automatic renewals a contract shows up. After signing that contract feature will be active .

Once the renewal is enabled ,Invoicing Type will be set to automatic and all subscriptions that PosDealer has been managing will be automatically renewed upon expiration.

If PosDealer decides to opt out from automatic renewals, a contract will be presented. After signing the contract, the automatic renewal feature will be deactivated. At that time ,the Invoicing Type will be set to manual, and all subscriptions managed by the PosDealer will require manual renewal upon expiration.

PosDealer is able to set automatic renewal individually for each subscription as well.Once the individual renewal is enabled for a subscription that subscription will be renewed automaticaly upon expiration.

Renewals can be performed in bulk, allowing users to select multiple subscriptions and renew them simultaneously.

For bulk renewals and cancellations users will be able to select multiple subscriptions using checkboxes and perform actions using buttons at the bottom of the page.

For individual subscriptions, action buttons are available in end of each subscription row. Once clicked, a confirmation dialog will appear to confirm the action. Using the action buttons you can pay for the individual subscription to extend it or choose to cancel it.

If PosDealer want to manage subscription manually they can either select multiple subscriptions using checkboxes and click on "Pay Subscription" button at the bottom of the page or use the action buttons available at the end of each subscription row to pay individual subscription.

There are 2 options while paying the subscription manually.

1. Dealer Package Option, If There is no entitlement for extending the subscription PosDealer can use DealerPackage option to add required entitlements to the shopping basket.

2. Entitlement Option, If there is enough entitlement to extend the subscription PosDealer can use Entitlement option to extend then entitlements will be assigned to selected subscriptions at the shopping basket.

After selecting the desired option and clicking on Pay button user will be informed via banner notification that the selected subscriptions have been added to the shopping basket.

There will be also easy access link to shopping basket in that notification. Clicking it will redirect user to shopping basket page where user can complete the payment process.

PosDealer can proceed to checkout from shopping basket page to complete the payment process.

Cancellation

Subscriptions can be canceled either individually or in bulk. PosDealer can select multiple subscriptions using checkboxes and click on the "Cancel Subscription" button at the bottom of the page to cancel them in bulk.

For individual subscriptions, action buttons are available at the end of each subscription row to cancel them.

Once cancel subscription is clicked a confirmation dialog will appear to confirm the action.

In that dialog user will be informed about the cancellation status and the remaining validity period of the subscription. Dealer can choose wheter to inform PosOperator via Email by using the Notify PosOperator checkbox in the dialog or not.

By confirming the cancellation the selected subscriptions will be canceled and PosDealer will receive a notification indicating the cancellation status and the remaining validity period of the subscription.

If notify PosOperator option was selected in the confirmation dialog PosOperator will receive an email notification about the cancellation.

Why it matters: These improvements streamline subscription management, making it easier for users to handle their subscriptions efficiently.

Access Links:

• Sandbox: https://portal-sandbox.fiskaltrust.de/PosDealer/Subscriptions
• Production: https://portal.fiskaltrust.de/PosDealer/Subscriptions

Affected markets: DE

Improved: Adding full tax id validation in Notification/company data page for Germany market. The system will now check the syntax and perform Erict checks when entering a tax id.

Why it matters: This enhancement helps ensure that tax IDs are valid and correctly formatted, reducing notification errors and improving data.

Change Portal Versioning​

Affected markets: ALL

Improved: Changing the fiskaltrust.portal versioning schema. Moved to date based versioning.

Why it matters: Moving to a new date base schema better reflects our current development and release cycle.

This release we've improved TAR-File export handling in the Queue, FiskalyCertified and SwissbitCloudV2 SCUs for the German market.

🇩🇪 Feature: Improved TAR-File Export handling in Zero Receipt (fiskaltrust/middleware#549)​

When performing a Zero-Receipt with the flag "Requests a download of the TSE-device TAR file" (0x0000_0000_0200_0000) the TAR-File export is now also attempted if the signing failed.

Affected packages:​

• fiskaltrust.Middleware.Queue.AzureTableStorage
• fiskaltrust.Middleware.Queue.SQLite
• fiskaltrust.Middleware.Queue.EF
• fiskaltrust.Middleware.Queue.MySQL

🇩🇪 Feature: Allow TAR-File deletion from SwissbitCloudV2 with open transactions (fiskaltrust/middleware#549)​

The TAR-File can now be deleted from the SwissbitCloudV2 TSE after an export even if there are open transactions on the TSE.

Affected packages:​

• fiskaltrust.Middleware.SCU.DE.SwissbitCloudV2

🇩🇪 Fix: Fiskaly TAR-File Export fails with E_TOO_MANY_REQUESTS (fiskaltrust/middleware#561)​

We've fixed an issue where TAR-File Exports from a FiskalyCertified TSE would fail with a E_TOO_MANY_REQUESTS error.
In some cases long running TAR-File Exports might take a few seconds longer due to this change.

Affected packages:​

• fiskaltrust.Middleware.Queue.AzureTableStorage
• fiskaltrust.Middleware.Queue.SQLite
• fiskaltrust.Middleware.Queue.EF
• fiskaltrust.Middleware.Queue.MySQL
• fiskaltrust.Middleware.SCU.DE.FiskalyCertified