Kwick Receipts platform MARcet is a transport and distribution layer for digital receipts. The transaction details and receipt content (prices, VAT, totals, line items, timestamps, merchant identifiers, etc.) is created by the merchant/POS system and submitted to Kwick Receipts.

Receipts in MARcet are merchant-authored documents. MARcet preserves the submitted receipt content for integrity and auditability, and distributes it to subscribers.

Kwick Receipts does not generate or “correct” fiscal receipt values. That is intentional and is a core feature of the service:

Integrity: once a receipt is retrieved by Kwick Receipts, the original merchant-submitted payload is preserved.
Auditability: subscribers can rely on the fact that the payload they receive matches what was submitted.
Clear responsibility: correctness of fiscal values (including VAT) remains the merchant’s responsibility.

👍
Receipts are always protected with integrity mechanisms (e.g. signing/hash) so subscribers can verify that a receipt has not been altered since acceptance.

Roles and responsibilities

Merchant/POS: generates the receipt content and is responsible for fiscal correctness (VAT, totals, etc.), including issuing corrections when needed.
Kwick Receipts (MARcet): validates schema/format and distributes receipts while preserving the merchant-submitted payload (and applying platform-level safety filtering where applicable).
Subscriber: consumes the receipt data, performs reconciliation/controls as required, and requests correction from the merchant if discrepancies are found.

MARcet does: schema validation, delivery, integrity protection (hash/signing where used), safety filtering (PII minimization, unsafe characters).

MARcet does not: calculate VAT, rewrite totals/line items, “fix” fiscal content after acceptance.

Validation vs. correctness

Kwick Receipts validates that receipts follow the published schema/format and required structural rules. We also support merchant partners pro-actively as part of our maintenance activities, to increase quality in merchant delivery.

Passing validation means the payload is well-formed and conforms to the format — it does not guarantee the merchant’s business logic (e.g. VAT calculation, Tip amount etc.) is correct.

Platform-level filtering and safety controls

To reduce risk and improve safety, Kwick Receipts may apply non-fiscal, platform-level filtering to incoming receipt data, such as:

filtering or minimizing personal data in receipt fields to reduce GDPR exposure
filtering unsafe characters (e.g. <, >, &) and similar measures to reduce injection/security risks

These controls are not intended to “correct” fiscal values, but to ensure safe processing and distribution of receipts.

Scenario with incorrect VAT (or other fiscal values)

If a merchant later identifies incorrect VAT:

Kwick Receipts will not modify the already accepted receipt content.
The merchant should issue a correction through their POS/accounting process (e.g. a corrective document such as a credit/cancellation/replacement referencing the original, depending on the merchant flow).
Subscribers may receive both the original and the corrective document (when the merchant provides it).

Support scope

Kwick Receipts supports merchants and subscribers in diagnosing and resolving format/schema and delivery issues (e.g. validation errors, missing/invalid fields, transport problems). We also work proactively with merchant partners to improve delivery quality over time — for example by monitoring integration quality signals, sharing recommendations, and helping partners interpret the specification correctly.

Fiscal correctness (VAT rules, tax decisions, pricing logic) is ultimately determined by the merchant/POS system that generated the receipt. When discrepancies are identified, we can assist with analysis and suggested remediation, but corrections must be issued by the merchant through their POS/accounting process.

We actively monitor integration quality and will reach out when we detect recurring issues, to help partners improve upstream data quality.

What subscribers should expect

Subscribers should treat VAT and other fiscal fields as merchant-provided values. If correctness is critical, subscribers should implement controls appropriate to their use case (e.g. reconciliation against their own systems/rules) and request correction from the merchant when needed.