Search Results

§1 — System architecture & components XPOS ESDC is an application-based E-SDC for Windows 10/11 (x64). It is a single self-contained package that runs a background fiscal service and an operator UI in one process, so the UI and the POS-facing service share one...

§3 — Authentication & token acquisition Access to TaxCore.API requires a bearer token obtained by authenticating with the on-card PKI certificate. XPOS ESDC performs a mutual-TLS request to /api/v3/sdc/token in which the client certificate and private key are ...

§5 — Identity from the Secure Element The taxpayer identity is read directly from the SE certificate — nothing is entered by the operator. FieldSource in the certificate TINCertificate OID (tag-6) UIDSERIALNUMBER (subject) Company nameSubject O Store / busin...

§8 — Digital signature & verification URLEvery invoice type — Normal, Advance, Copy, Training, Proforma — is signed on the SE and produces a unique verification URL encoded into the receipt QR code. The URL payload is assembled to the FRCS specification and co...

§9 — Audit package format & storage Each signed invoice yields an audit package containing the invoice { request, result }. The package is encrypted as follows: Payload — encrypted with AES-256 (CBC, PKCS7 padding) using a one-time key and IV. Key transport —...

§13 — Real-time clock & time synchronisation As a software E-SDC there is no dedicated hardware RTC. Time accuracy is maintained by NTP synchronisation against the server provided by FRCS (set via SetTimeServerUrl), performed hourly — well within the 48-hour r...

§16 — Error codes XPOS ESDC returns only the prescribed FRCS error codes; any manufacturer-specific message is listed in the User Manual. Representative mappings: CodeMeaning 1300No card / Secure Element not present 1500PIN required 2100 / 2110PIN incorrect ...

XPOS ESDC exposes a local HTTP service that a Point of Sale (the built-in POS, or your own POS/ERP) uses to fiscalise sales. This guide is the integration reference for developers building against that service. Base URL The service listens on port 8888 on all...

These endpoints establish that the SDC is ready and unlock signing for the session. GET /api/v3/attention Lightweight health check. Returns whether the SDC is available and which card readers are connected. GET /api/v3/attention 200 OK { "available": true,...

The core endpoint. Signs a sale on the Secure Element and returns the fiscal result (verification URL, QR, journal, signature). Requires a PIN previously verified via POST /api/v3/pin. POST /api/v3/invoices Content-Type: application/json RequestId: 4b1e...uni...

The SDC uses two error shapes: field validation errors (HTTP 400) and operational response codes (in the body/status). Validation errors (HTTP 400) When a request fails structural or business validation, the SDC returns HTTP 400 with a modelState array — one ...

Read-back endpoints for reprinting, reconciliation and reporting. These query stored records and do not touch the card. Invoice history GET /api/v3/invoices?from=2026-08-01&to=2026-08-13&uid=EKLBHT3Y Returns fiscalised invoice records for the period (defaults...

The Legacy V2 API exists for compatibility with older POS integrations (the FiscoBridge-era contract). New integrations should use v3. V2 signing reuses the exact same fiscalisation pipeline as v3 — only the request parser and the returned result shape differ....