Skip to main content

Β· 4 min read
SIGN DE Team

TSS Update Postponed​

Update Postponed

The previously announced update of the SIGN DE API on Sunday, June 5, 2022 is postponed. Therefore, the scheduled maintenance is no longer necessary and is canceled.

The reason is an bug discovered during testing that can cause updated TSS instances to transition to a permanent secure state. In consequence, the announced actions for 5.6.2022 and 6.6.2022 will not take place. We are analyzing the reason for the problem, and will proceed with fixing it. This will require a recertification of the SMAERS. A new update date will be announced in advance once the process is complete.

FAQ of Postponed Update​

Below you can find answers to some questions you may have on the postponed TSS update.

Does the postponed update affect my operation of SIGN DE?​

Customers will feel no impact from the postponement of the update. The presently running certified TSS version (1.0.5-1.2.0) is stable and works reliably.

The changes in the updated versions concern further improvements in stability, but are not critical for the normal operation of the SIGN DE API.

Why was the update postponed?​

During the extensive testing in our TEST environment, a bug was detected. Under certain circumstances, this bug results in some of the SMAERS instances that were updated from version 1.0.5 to version 1.0.6 entering an unrecoverable secure state.

β€˜New’ SMAERS instances, that were created in version 1.0.6, are not affected by this bug. No problems have been detected with the new CSPL version 1.3.0.

Fixing this problem is only possible by changing the implementation of our SMAERS, which means that it has to undergo a recertification process before it can be deployed to production. As a result, the planned update has to be postponed until that process is completed.

What is the impact of the postponed update?​

The postponement affects the update of the TSS in the LIVE environment. In TEST, which has already been updated, the TSS version 1.0.6-1.3.0 will continue to run for testing purposes. This means that:

  • In LIVE environment, the TSS version will remain at 1.0.5-1.2.0 (the β€˜old’ version). This means that for the customers, nothing will change compared to now.

  • In TEST environment, the TSS version will remain at 1.0.6-1.3.0 (the β€˜updated’ version). As the environment is set up to create new TSS instances only in this version, the bug will not affect customers' TSS instances in the TEST environment. The behaviour of this version from a customer perspective is indistinguishable from the previous version, meaning that the β€˜updated’ TSS instances will behave the same as the β€˜old’ ones. No tests or other customer-side integration will be affected, apart from the presence of the updated TSS version in the info.csv file of TSS exports.

Why was the problem not detected earlier?​

Despite extensive automated and manual testing, the bug was not detected during development or certification because the specific circumstances that triggered it were difficult to anticipate and test for in advance. The complexity of the TSS is such that some behaviors are rare and will only be detectable in large-scale and highly dynamic environments.

However, this was precisely why an extended period of testing in TEST environment, which more closely approximates the conditions and behavior of our LIVE environment, was planned for before the update in LIVE environment took place.

Will the update still take place in the future?​

The changes incorporated in TSS version 1.0.6-1.3.0 will be part of the next update, which will take place once the SMAERS recertification is complete, leading to a new SMAERS version (1.0.x). The update will then upgrade the TSS version in TEST environment and LIVE environment to version 1.0.x-1.3.0.

It is difficult to estimate how much time the development and recertification effort will require, but the anticipated delay is in the order of at least a few months. Should an update date be decided upon, we will notify customers in advance in the same manner as we did for this update.

Why not update the CSPL, if it has no problems?​

The TSS certification process requires the separate certification of both the individual component versions (SMAERS and CSPL) as well as their combination (i.e., the TSS as a whole). Hence we are not allowed to update only the CSPL, as this would lead to the TSS instances in LIVE environment being in an uncertified version (1.0.5-1.3.0).

Best, the fiskaly SIGN DE Team

Β· 5 min read
SIGN DE Team

TSS Update on June 5, 2022​

Update Postponed

The previously announced update of the SIGN DE API on Sunday, June 5, 2022 is postponed. Therefore, the scheduled maintenance is no longer necessary and is canceled. You can find more information in our related blog post Postponed Update

Here you find more information on our scheduled maintenance on June 5, 2022. We will update our system to make it even better.

SIGN DE - TSS Update Announcement​

info

Scheduled Maintenance Sunday, June 5, 2022, 08:00-16:00 CET SIGN DE API will undergo scheduled maintenance on Sunday, 5.6.2022, between 08:00 and 16:00 (CET).

The maintenance will involve a rolling update of LIVE TSS instances from version 1.0.5-1.2.0 to version 1.0.6-1.3.0 (where the former is the SMAERS version and the latter is the CSPL version).

During the maintenance window, the following restrictions apply:

  • Data Exports are disabled.
  • TSS state transitions to DISABLED are not possible.
  • API calls may take longer than usual or run into timeouts.
  • Service interruptions may occur.

Note for June 6, 2022​

info

As a consequence of the TSS update, on June 6, 2022 between 05:00 and 08:00 (CET) the first request to a TSS may take up to 15 seconds.

FAQ of TSS Update​

Below you can find answers to some questions you may have on the TSS update on June 5, 2022.

What does the update entail?​

The update concerns the deployment of the new certified versions for the SMAERS (from version 1.0.5 to 1.0.6) and CSPL (from version 1.2.0 to 1.3.0), together representing an update of the entire TSS to version 1.0.6-1.3.0.

The TSS update will also represent the deployment of version 2.1.0 of SIGN DE API.

You can find the certification documents for the new versions at Certification | fiskaly.developer.

What are the effects of the update?​

The new versions of SMAERS and CSPL include bugfixes and stability improvements. Customers' operations should not be affected, as there are no changes to the API. The only visible differences are in the exports triggered after the update: the exports will include the update logs, and the TSS version in the info.csv will be incremented to 1.0.6-1.3.0. Old exports, i.e. exports triggered before the update, will not be affected by it.

Only TSS instances that are in the states UNINITIALIZED or INITIALIZED will be updated. All existing and new TSS instances in the state CREATED will be in the new version once they are transitioned into the UNINITIALIZED state. An update of DEFECTIVE and DISABLED instances is not possible due to technical reasons.

Customers may experience some temporarily increased latency in the handling of their first post-update requests due to the need to re-establish communication between SMAERS and CSPL, and synchronize the update logs across all components.

What do I need to do?​

Customers do not need to do anything on their side. As mentioned above, there are no effects on customer operations apart from some restrictions and the inevitable interruptions during the update process.

We recommend to follow our guide on how to deal with service interruptions and timeouts at Error and Timeout-Handling | fiskaly.developer.

After the update is completed, you can verify the update by checking your info.csv files in the data exports of INITIALIZED TSS instances for the correct TSS version.

Can I continue to use SIGN DE API during the update timeframe?​

In principle, yes. During the maintenance window, individual calls may fail, time out or take longer than usual.

Data Exports and the TSS state transition to state DISABLED will also be temporarily disabled during the maintenance window. HTTP endpoints regarding these operations will respond with HTTP status code 503.

Otherwise SIGN DE API will remain available and functional throughout the maintenance window.

When will the update take place?​

The update will take place as a rolling update over longer periods of time during the announced maintenance window. It does not mean that it will start at exactly 8:00 or last until exactly 16:00, but during that period different parts of SIGN DE API will be updated at various times.

What does it mean that the data exports are disabled?​

During the maintenance window the export endpoints will return HTTP status 503.

How long will the data exports be disabled?​

The data exports may be disabled and re-enabled for longer periods of time at various points during the announced maintenance window. We recommend avoiding data exports during the maintenance window entirely.

How long will the TSS disabling functionality be disabled?​

The TSS disabling functionality may be disabled and re-enabled for longer periods of time at various points during the announced maintenance window. We recommend avoiding setting TSS instances to state DISABLED during the maintenance window entirely.

What does it mean that service interruptions can occur?​

In addition to the disabled functionality, during the rolling update process, individual TSS instances may be temporarily unreachable or busy as their components are being updated.

Some TSS instances may temporarily display increased latency in the handling of their first post-update requests due to the need to re-establish communication between SMAERS and CSPL, and synchronize the update logs across all components.

Happy updating, the fiskaly SIGN DE Team

Β· 2 min read
Hannah Roegele

Hi!

Check out our latest updates, as we start another round of technology seminars: This time we talk about V2 technical details.

Latest Updates:​

KassenSichV API V2 is live​

On Friday we went live with V2. Please make sure to use the correct production URLs. Here is an overview of the URLs and the V2 guide to read:

KassenSichV API V2.0​

  • πŸš€ Deployed.

Dashboard V2.0​

We've deployed the V2 Dashboard, being able to display and populate V1 and V2 resources.

New:​

  • Integration of Sign V2 (KassenSichV V2).
  • "DSFinV-K Exports" moved to a sole menu (currently available for V1 only).
  • Moved "API Keys" to the "Settings" menu.
  • "Status" moved to a sole menu.

Fixed:​

  • Fixed metadata display issue.

Seminar: Technical Details V2​

In this seminar we will focus on the technical details of the fiskaly Cloud TSS V2. We will address, among other things, the scenarios of migration from V1 to V2 and the direct implementation of V2. As usual, you can send us your questions in advance or ask them live in the seminar. We look forward to receiving numerous questions via sales@fiskaly.com.

Register now

  • German: Wednesday, July 28, 2021, 4:30 - 5:30 pm CEST
  • English: Thursday, July 29, 2021, 4:30 - 5:30 pm CEST

Cheers, Hannah from fiskaly

Β· One min read
Hannah Roegele

Hi!

Technology, technology, and technology: that's the focus in our next online seminar this week.

Technical Details fiskaly Cloud TSS​

We invite you to our next online seminar this week with a focus on technology. To answer all your questions thoroughly, one of our senior developers will be present. We are looking forward to your attendance.

Register now

  • German: Thursday, July 15, 2021, 10:00-10:45 am CEST
  • English: Friday, July 16, 2021, 10:00-10:45 am CEST

Cheers, Hannah from fiskaly

Β· One min read
Hannah Roegele

Hi!

Today I have a very short Update for you. We reached another milestone:

info

πŸš€ πŸš€ Transaction Handling is live. πŸš€ πŸš€

Reminder online Seminars​

Our online Seminars on Certified Operation fiskaly Cloud TSS are coming up this week. Additionally we'll discuss the decision of the Bundesrat (German Federal Council) on the KassenSichV and the changes it brings.

Register here:

  • German: Thursday, July 8, 2021, 10:00-10:45 am CEST
  • English: Friday, July 9, 2021, 10:00-10:45 am CEST

Cheers, Hannah from fiskaly

Β· 2 min read
Hannah Roegele

Hi, have a look at the changelog for the latest updates in the fiskaly system.

Latest Updates​

Roadmap to V2​

We published our Roadmap to V2, and it is available at: developer.fiskaly.com/v2-roadmap

We finished phase 1...​

… of our Roadmap successfully. This means following is done:

  • TSS Initialization
  • Client Handling
  • Authentication
  • Test only Environment
  • Documentation Update
  • Base-Url: sign.fiskaly.dev
  • TX-Handling ~End-of-Week

Phase 2 is nearly complete! This implementation generates certified TSSs, thus clearing the hurdle of fiscalization for many years to come. From now on, we will be in a continuous process of improvement with each new deployment.

Postman​

For a quick first demo, you may use Postman. We prepared a Postman collection that allows you to step through the most important functions of this API.

FAQ’s V2​

We’ll soon push a new FAQ’s section: If you want to place some questions there, please reach out to sales@fiskaly.com.

QR Code replaces readable TSS Signature​

On June 25, 2021, the German Bundesrat approved the ordinance amending the KassenSichV. The addition to Β§ 6 sentence 2 KassenSichV makes it possible to omit printing certain information in plain text on a receipt, and instead display it in a QR code. Source: Bundesrat (TOP 86) or read our Blogpost.

Online Seminars​

In our next online seminars we talk about the law amendment and give you updates on our system. Join us and register here:

  • German: Thursday, July 8, 2021, 10:00-10:45 am CEST
  • English: Friday, July 9, 2021, 10:00-10:45 am CEST

Cheers, Hannah from fiskaly

Β· One min read
Hannah Roegele

Hi, have a look at the changelog for the latest updates in the fiskaly system.

Latest Deployment Notes​

fiskaly Dashboard v0.14​

  • Show metadata of entities.
  • Fixed duplicates of organizations in the organization list.
  • Fixed DSFinV-K download button.

Management API v0.8​

  • Fixed duplicate listing of organizations in rare cases.

DSFinV-K v0.8​

  • Fixed TSE_SERIAL field in tse.csv.
  • Fixed UST_SCHLUESSEL field in business_cases.csv.
  • Fixed inserting Cash Point Closing with coupons.
  • Fixed count field on responses of list endpoints.
  • Performance improvements.

Cheers, Hannah from fiskaly

Β· 2 min read
Johannes Ferner
Dr. Patrick Gaubatz
Simon Tragatschnig

Hi there,

info

The fiskaly Cloud-TSS has now been fully certified by the German Federal Office for Information Security (BSI)! πŸš€

"More than two years of planning, postponements, hurdles and changes, as well as improvements in requirements are behind us. Now the time has finally come! The certified fiskaly Cloud TSS is the first Cloud TSS to be certified for the entire duration! I am very proud of fiskaly and the incredible team effort over the last months." Johannes Ferner, CEO fiskaly GmbH

fiskaly is thus the only cloud TSS to accomplish the full certificate duration and is certified until 2029. The fiskaly Cloud TSS is 100% software-based and can be integrated into all systems and POS architectures.

info

Hard Facts about fiskaly Cloud TSS​

  • the only cloud-based TSS with maximum certificate validity until 2029!
  • real cloudbased TSS without additional hardware requirements!
  • scalable operation & roll-out!
  • open for innovative retail concepts!

Download Certificates​

You can find the official certificates below:

  • CSP-L - β€œSignature Server”
  • SMAERS - β€œConnector”
  • TR - β€œend2end Check”

Download

IGZTK - Become a member​

We recommend you to join the IGZTK - Interest Group of Future-Oriented Technology Manufacturers for POS Systems: igztk.com

tip

For questions or for congratulations you can reach your sales manager or our sales team at sales@fiskaly.com.

Thank you very much for your trust and loyalty!

Your fiskaly Team Johannes Ferner (CEO), Simon Tragatschnig (COO) & Patrick Gaubatz (CTO)

Β· 2 min read
Hannah Roegele

Hi, have a look at the changelog for the latest updates in the fiskaly system.

Current Changelog:​

fiskaly Client v.1.2.200​

  • Re-implemented HTTP client configuration to fix problems with proxies and certificates.
  • Fixed number formatting & validation.
  • Fixed ARM builds.
  • Extended health check function.

This is the last planned update for version 1 - if you're experiencing any issues, make sure to install the latest version.

DSFinV-K v0.7.0 is deployed.​

  • Translated documentation into English.
  • Fixed missing businesscases.csv in exports.
  • Fixed missing itemamounts.csv in exports.
  • Fixed missing subitems.csv in exports.
  • Fixed order of CSV columns in multiple exported files.
  • Fixed the use of historic VAT definitions ("Historische SteuersΓ€tze") in a Cash Point Closing.
  • Fixed inconsistent revisions for Cash Registries.
  • Fixed response of upsertCashRegister to include the processing_flag and software field.
  • Wording improvements in the documentation.

Upcoming Online Seminar: Certification​

We invite you to join our next online seminar: Certification

Topics:​

  • Certification and all around certification Other important topics for providers of digital POS systems
  • The seminar is offered in German and English. Register now:

German: Thursday, May 27, 2021 - 3:00-3:45 pm CEST English: Friday, May 28, 2021 - 10:30-11:15 am CEST

links removed

Cheers, Hannah from fiskaly

Β· One min read
Hannah Roegele
Elias Priesching

Hi!

We have been carrying out some maintenance on our system during the last week.

Brand new: status.fiskaly.com

Our system is busier than ever before. In order to continue to give the best service and planning reliability we set up a status website for the fiskaly system:

status.fiskaly.com

Information about maintenance windows, as well as new functionalities in the respective products, will be sent out here in our Developer Newsletter.

Alternatively, you can find information about maintenance windows and status information at status.fiskaly.com.

Cheers, Hannah from fiskaly

Β· One min read
Hannah Roegele
Elias Priesching

Hi, have a look at the changelog for the latest updates in the fiskaly system.

Current Changelog:​

DSFinV-K v0.6.0​

  • Added linked dtd file to export.
  • Better error handling on invalid time formats.
  • Fixed export_creation_date time format in listCashPointClosings.
  • Fixed MAX_PARAMETERS_EXCEEDED error for Cash Point Closings.
  • Fixed misleading E_CLIENT_NOT_FOUND error for Cash Point Closings.
  • Fixed input of incl_vat, excl_vat and vat and allowing up to 5 decimal places.

Management API v0.9.0​

  • Added possibility to create main organizations in LIVE mode if the billing_options.bill_to_organization is set, the set organization is also in LIVE mode and a token with env:LIVE is present.
  • Added created_by_user field on multiple responses.
  • Fixed edge case where setting the billing_options.bill_to_organization for a MANAGED_ORGANIZATION raised an error.

Cheers, Hannah from fiskaly

Β· One min read
Hannah Roegele
Dr. Patrick Gaubatz

Hi, have a look at the changelog for the latest updates in the fiskaly system.

Current Changelog:​

Management API (0.8.0)​

  • Added new endpoint to remove a user from an organization.
  • Fixed the invite endpoint to invite new users to an organization.
  • Fix: Managed organizations could have had further managed organizations

Dashboard (0.12.0)​

  • Managed organizations can be set to LIVE mode when the main organization is already in LIVE
  • The display name is now displayed over the real name of an organization
  • Users can now be removed from an organization
  • Fixed sorting for multiple tables
  • Fixed 'an unknown error' when new users were invited to an organization
  • Managed organization count fixed on the Dashboard
  • Typo fixes

DSFinV-K API (0.5.1-alpha)​

  • Fixed E_TX_NOT_FOUND on cash point closings - with an empty transaction list or only transactions that contain errors
  • Fixed listExport with a client_id filter

Cheers, Hannah from fiskaly

Β· One min read
Hannah Roegele
Elias Priesching

Hi, welcome to our dev newsletter. Check the changelog for our latest changes in the fiskaly dashboard.

Latest Changelog:​

  • Fixed DE/EN translations
  • More consistent way of showing the display_name
  • Enable the Country Dropdown (non-germany) when creating new organizations
  • Added a new Count Widget to display the managed organizations
  • Added managed organization list to Settings > Organization Management
  • Fixed filter for state field
  • Fixed test banner when the organization is already set to LIVE
  • Fixed displaying empty fields of organization data

Cheers, Hannah from fiskaly

Dev-Newsletter

stay up-to-date