Sales Data and Support Status
The restaurant/café software using the API is the primary sale application. Its source identity and version remain separate from Android, SDK and fiscal software versions.
The limited invoice/buyer/fiscal contract is implemented in source. It is awaiting release and exact device/issuer acceptance; production capabilities remain disabled for the new context protocol.
| Area | Status |
|---|---|
| Itemized sales and source application identity | Source implementation ready; release status is separate |
| Existing invoice references, dates and collected allocations | Source implementation ready; capability gated; no receivable balance verification |
| Buyer identity type, separate person names, legal name and address | Encrypted input and device-bound access implemented; not a full sector/regulatory profile |
| New document number/UUID/date, independent fiscal result and alarms | Device writer, authenticated history, outbox and panel read wired; real issuer execution remains disabled |
| Common read-only recovery coordinator | Implemented in source; exact vendor query driver and device acceptance remain required |
| Reissuance/cancellation, manual fiscal resolution and original-document reversal execution | Not enabled |
| Subscriber/institution collections, sector profiles, exemptions, jewellery, advances and capture documents | Planned work remains open |
| Routing, terminal management, applied configuration tracking, all-mode designs/Agency and OTA | Remain in the delivery plan. Android signed version checking is implemented in source; the OTA installer and device acceptance remain open. Version checking |
An existing invoice reference, the original document of a reversal and a newly issued document are three distinct concepts. Approved payment plus document failure never authorizes a new charge. No legacy signature vector or B-19 document is silently redefined by this feature.
7 November: Android execution preparation
New fiscal content v2 preserves the original registered software name and declared version in the device-verified content. Historical v1 content remains unchanged. Plain requests without fiscal data do not gain a new device source channel in this delivery.
Android now has an execution port, immutable SDK/profile binding, atomic local persistence of payment and fiscal evidence, and a narrow Pavo request plan. These do not constitute a connected SDK or accepted document issuance. Authenticated vendor results/queries, observed test-mode evidence and physical-device acceptance are still required before opening financial execution. This is not a completed all-device POS product or BKM/TekPOS compliance claim.
7 November: common query and recovery
The Android recovery coordinator now handles signed PAYMENT_QUERY, original execution/profile binding, PAYMENT_QUERY_RESULT, document-only queries and durable outbox persistence. The real vendor query driver remains unbound and financial execution stays disabled. An uncertain outcome never authorizes another charge, document issuance or execution-channel switch. Bank approval and fiscal outcome remain separate facts.
Under K-43, releasing the original device reservation does not resolve the old payment. MANUAL_REVIEW is a review state; a separate new operation still needs its own authorization. The new device recovery-state read requires backend/gateway release. Protocol package 2.5.0 leaves commands v5/v6 and B-19 v2 unchanged. Vendor/device acceptance and manual fiscal resolution/cancellation remain open.
7 November correction: automatic checks and device continuity
Automatic queries and report reconciliation are the primary path; manual review is a last resort when the provider cannot supply definitive evidence. Repeated NFC/same-result delivery remains one transaction, and conflicting evidence is flagged per transaction. A review flag does not impose a permanent device-wide ban; each new operation still needs its own authorization, SDK availability and server reservation. Android fiscal queries continue hourly after the first six reads.
The follow-up backend delivery adds a durable cursor from the first account/merchant binding UTC date, bounded historical planning, and append-only recovery generations for EXPIRED days. The latest 7 dates have priority; aging pending days are retained. reportCoverage on the existing provider transaction list exposes completion separately from planning, pending work and finality. A new report hint wakes a stopped uncertain-payment query; advisory evidence cannot approve it. Exact intraday boundaries, COMPLETE re-audits, provider retention/timezone guarantees and real SDK acceptance remain open. One backend SQL migration; device package 2.5.1 and command/event/config/signature formats stay unchanged. Source/test delivery, not production deployment.
8 November: Pavo financial driver
The Android source now connects sale, linked full/item refunds, same-device/current-batch void and original-transaction queries. A single-use submission follows the durable journal start record. Reconnects and uncertain results never create another charge. A completed void is success for the void request; identical repeated tender rows are deduplicated, while conflicting observations keep that transaction uncertain. Bank approval is preserved independently of fiscal-document failures.
Real-device support remains disabled. Activation requires acceptance of the exact PavoPay build/signers, authenticated response channel, actual test/live mode and bank/terminal mapping. A generic exported onNewIntent callback is insufficient. The implemented OS ActivityResult channel is available only for builds whose producer explicitly confirms that return contract; the documentation's PendingIntent example only launches the application. Delivery of the registered initiating application's identity and frozen original item links for reversals remains a backend requirement. No device acceptance was performed; a source push is neither production deployment nor BKM/TekPOS certification.
This Android delivery adds no public endpoint or protocol version: package 2.7.0, command v5/v6, source context v1–v3 and configuration v2 remain unchanged.