NewsContact

fiskaltrust APIs

The layer between your POS and the tax authority.

Three APIs cover the work at the counter, the rollout behind the counter and the receipt in the customer's hand. All three run on the same Middleware and the same credentials.

Find your APIStart with the quickstart

API layer

  • Your POS – till · app · ERP
  • API layer – POS System · PosDealer · Receipt
  • TAX – signed & reported
  • ARCHIVE – revision-safe
  • CUSTOMER – digital receipt

One layer in front of the Middleware. Three destinations behind every sale.

Core APIs, one credential set
3
Endpoints in the POS System API
5
Protocols, REST and gRPC
2
Markets behind the same interface
7

ORIENTATION

Match the API to the job.

Each API serves one role in the ecosystem. Pick your row and follow the link.

Your jobYour APIWhat you get
You build a POS systemPOS System APIFiscalise, pay, issue and export at the counter, in seven marketsRead more
You roll out to many outletsPosDealer APIOnboard operators, produce products and configure installations in bulkRead more
You deliver digital receiptsReceipt APICreate, store and hand over receipts across consumer channelsRead more

POS SYSTEM API

The counter API.

The central interface between your POS and the Middleware. Send the transaction once. The API signs under the local law, triggers payment, issues the receipt and exports the journals.

Five endpoints cover the fiscal lifecycle:

  • /echo
  • /pay
  • /sign
  • /issue
  • /journal
Two colleagues at white desks with a POS till, a receipt printer and a monitor

  • Receipt fiscalisation

    Signing, chaining and numbering in each country's legal format, returned in one response.

  • Payment execution

    A retry during processing blocks until the original operation finishes, then returns its result.

  • Receipt issuing and export

    Deliver on paper or digital, then export audit data in the national format on demand.

PosSystemAPI detailsSign a receipt in minutes

POS DEALER API

The rollout API.

Built for dealers and platforms managing many outlets. Automate the steps between a signed framework agreement and a producing till, without a technician in every shop.

A bearded man in front of two monitors showing a rollout console
PosDealer API details

  • Operator onboarding

    Create and manage POS operator accounts, including automated operator invitations.

  • Product production

    List entitlements and produce queue or outlet products against your rollout plans.

  • Configuration access

    Retrieve and list Middleware configurations per operator, straight from your own systems.

  • Batch rollout

    Provision outlets in bulk with pre-configured templates. On-site time per outlet drops from hours to minutes.

RECEIPT API

The customer API.

Standardised ReceiptRequest and ReceiptResponse structures carry every receipt from the sale to the customer.

Receipts live in the fiskaltrust.Cloud behind tamper-proof HTTPS links, ready for wallet, email, text or QR.

Receipt API details
A smiling man holds up a phone showing a digital receipt with a five-star rating

  1. Request

    The POS sends a ReceiptRequest with the transaction data.

  2. Sign and store

    The Middleware fiscalises the receipt and stores the digital version in the fiskaltrust.Cloud.

  3. Link

    The response carries a unique, tamper-proof HTTPS link to the receipt.

  4. Deliver

    The customer receives the receipt by QR, email, text or wallet. Feedback and loyalty attach to the same link.

Pick the API for your job. The Middleware underneath is the same.

FOUNDATION

Built to run at scale.

The API layer carries 5M+ receipts per day across seven markets. The design choices below keep integrations stable when regulation, hardware or scale changes.

  • REST
  • gRPC
  • SOAP (legacy)

  • Asynchronous processing

    Long-running operations return without blocking the till. The checkout stays fast under load.

  • Signature device abstraction

    Hardware TSE, cloud TSE, smartcard or online service. Your code calls one interface, the SCU handles the device.

  • SDKs and CLI tools

    Client libraries and command line tooling shorten the path from spec to running code, in the open on GitHub.

  • Sandbox per market

    Test against a near-full copy of the live system before your first production receipt.

SELF-SERVE

Everything you need before a call.

Judge feasibility and fit on your own terms. The stack is documented, public and testable today.

FAQ

Before you pick an API.

Straight answers to the questions integration teams raise first.

Do the three APIs share credentials?

Yes. One account in the fiskaltrust.Portal carries the credentials for every API you use. No separate contracts per interface.

Which API starts a typical integration?

The POS System API. Sign a sandbox receipt first, then add the PosDealer API for rollout automation and the Receipt API for consumer delivery.

Does one integration cover all seven markets?

Yes. The interface stays identical. Country logic lives in the Middleware and updates centrally when a regulation changes.

REST or gRPC?

Both carry the full API surface. Pick REST for the shortest start, gRPC for high transaction volumes. SOAP remains available for legacy systems.

Where do I test without legal obligation?

In the sandbox. The sandbox Portal issues test credentials, and the all-zero POS System ID lets you sign test receipts before registration.

Pick your API. Sign your first receipt.

The quickstart on the developer page takes you from zero to a signed sandbox receipt. The docs carry the full reference for all three APIs.

Open the quickstartRead the docs