Files
hardlink/README.md
T

30 lines
1.6 KiB
Markdown

# Hardlink
Hardlink is the Windows hotel-kiosk service for K720 card dispensing, door-key
encoding, room-ticket and payment-receipt printing, and terminal payments. It
supports Assa Abloy, Omnitec, Salto, TLJ and dormakaba lock servers, and CreditCall
(ChipDNA), Dojo, PayBridge and Trust Payments providers.
## Documentation
- [Configuration](docs/configuration.md): local service/device settings,
room-ticket layout and CMS-only Trust configuration.
- [Operations](docs/operations.md): builds, deployment layout, hardware HTTP
endpoints, diagnostics, logs and offline verification.
- [Payment API](docs/payment-api.md): unified Sale/PREAUTH requests, NDJSON
results, transaction ownership, receipts and CreditCall streaming details.
- [K720 hardware contract](docs/hardware/k720.md): preparation, uncertain-handoff
recovery, delivery clearance and maintenance invariants.
- [Release history](docs/releases.md).
- [Historical archive](docs/archive/README.md): superseded Trust plans and
audits, retained as dated evidence rather than current operating instructions.
Hardlink owns payment-provider selection and terminal processing. The native
Fyne applications use the common Sale/PREAUTH contract and own their financial
calculations, PMS descriptions, PMS posting and guest journeys. Trust settings
come from CMS; no local `trust:` YAML section or currency-evidence flag is needed.
The deprecated XML payment routes remain solely for legacy compatibility.
`/testissuedoorcard` remains an operational diagnostic available on production
kiosks regardless of TestMode, and retains the encoded card inside the dispenser.