The architecture

How a sale becomes a fiscal receipt

Tax-Bridge sits between the systems you sell with and the tax authority's signing service. One normalized request in, one legally fiscalized document out.

CONNECTORS Xero Odoo POS / ERP REST / webhook TAX-BRIDGE normalize → map 32-hex idempotent id mutual-TLS + PAC two-tier retry store journal · QR queue · vault · audit TAXCORE V-SDC signs the invoice returns journal QR + verify URL tax authority cloud canonical JSON mutual TLS fiscal result

Normalize once

Every connector maps its invoice into one canonical schema — tax-inclusive line items with tax labels, payments, buyer and cashier. The TaxCore-specific shaping lives in a single place in the Bridge, so connectors stay thin.

Authenticate per shop

Each shop's certificate (PFX) and PAC are decrypted in memory only at signing time and used for a mutual-TLS handshake with the V-SDC. Secrets are never logged and never leave the vault in the clear.

Fiscalize idempotently

A deterministic 32-hex request id makes the call safe to retry. The sandbox V-SDC fails ~half the time transiently; a quick in-process retry plus a durable queue means a sale is fiscalized exactly once — or not at all.

Return a compliant document

The SDC's response — journal, QR (GIF) and verification URL — is stored verbatim and rendered byte-for-byte. Print it on paper or deliver it electronically; scan the QR to verify it against the authority.