CloudCashBox
Fiscalisation without the box.
Every fiskaltrust setup runs through a CashBox, the container holding your fiscal configuration. The CloudCashBox runs this CashBox hosted in the fiskaltrust cloud. Your POS calls one endpoint, nothing gets installed or maintained at the counter.
POST /v2/signcashboxid: <your CashBoxId>accesstoken: <your AccessToken># Signed on the hosted side.# Nothing installed at the counter,# nothing to update on site.Same API as the local Middleware. The endpoint URL is the only difference.
- Entry price, per year
- 0 €
- Bundles for the common cases
- 3
- markets, chosen per till
- 7
- data centers
- EU
THE CONCEPT
First, the CashBox.
The CashBox is the unit of fiscal configuration in the fiskaltrust platform. One CashBox per till holds everything the law asks from your point of sale. Your POS addresses one CashBox with one ID and one access token, and the platform does the rest.
The CloudCashBox is the same CashBox, run for you on hosted infrastructure. Same configuration, same API, same five endpoints. The difference is where the software runs, not what your code sends.
CASHBOX
One per till
Addressed by cashbox ID and access token in every request.
QUEUE
The fiscal state machine
Numbers, chains and journals every receipt in your market's format.
SIGNATURE CREATION UNIT
The signing method
Connects the signature technology your market demands, hardware or cloud.
CLOUDCASHBOX
The hosted way to run it
The whole stack above, operated in the fiskaltrust cloud.
THE DESIGN
Cloud or local. Same integration.
Both columns run the same CashBox. The CloudCashBox hosts yours in the cloud, the Local Middleware runs yours at the counter. The API stays identical, so the choice is operational, not technical, and switching later never touches your code.
| CLOUDCASHBOX | LOCAL MIDDLEWARE | |
|---|---|---|
| Installation | None, the CashBox runs hosted | Launcher on Windows, Linux, macOS or Android |
| Signing hardware | None at the counter | Depends on the market and setup |
| Updates | Applied on the hosted side | Rolled out per installation |
| Connectivity | Requires a working internet connection | Signing works offline |
| Best for | Web POS, mobile checkouts, fast rollouts | Estates with offline requirements |
A compliance product ready to sell, with no hardware to buy, ship or replace
WHY PARTNERS SELL THIS
Rollouts shrink to configuration.
No device visits, no launcher installs, no hardware logistics. A new outlet is a Portal entry and an endpoint in the POS configuration.
Live in hours, not days
Provision the CloudCashBox in the Portal or via the PosDealer API and go live the same day.
European hosting
Data stays in European data centres, in line with the storage rules of each market.
Scales with the business
One outlet or one thousand, the hosted side carries the load without new hardware.
FAQ
Cloud questions, short answers.
The docs carry the technical depth.
What is the difference between a CashBox and the CloudCashBox?
The CashBox is the configuration unit: one per till, holding the Queue and the signature creation unit. The CloudCashBox is the hosted way to run one. Same API, same five endpoints, no local installation.
Does my integration change between cloud and local?
No. The request format stays identical. The endpoint URL is the only difference.
What happens when the internet fails?
Cloud signing pauses until connectivity returns. Counters with offline requirements run local or hybrid instead. The right split depends on the outlet location and connectivity.
Where does the data live?
In European data centres, meeting the residency rules of the supported markets.
Who applies updates?
We do, on the hosted side. Regulation changes reach every CloudCashBox without a rollout on your side.
Drop the box. Keep the compliance.
Tell us your estate and your markets. Sales maps cloud, local and hybrid per outlet.
You talk to real people