Unattended and kiosk payments
Integrate Self/Series through the device SDK and coordinate payment outcomes with a kiosk or machine fulfillment workflow.
Separate payment control from the kiosk UI
Self/Series is supported through the Windows/Linux Payment Device SDK. The package includes ChipDNA Server, sample clients, and API documentation. A Windows emulator supports early development. device
Configure a Windows development station
The reviewed Windows guide requires Windows 10 or 11 with .NET Framework 4.7.2 or newer and an API-source gateway key. In chipdna.config.xml, configure an uppercase ApplicationIdentifier, the device identifier, and the correct COM port. Run ChipDNAServer.exe in console mode for development. Set the client terminal identifier and server address; the documented local default is 127.0.0.1:1869. Run the CLI sample, start a transaction, and follow the device prompts. The Windows CLI example expresses 123 as 1.23. Do not carry that amount convention into an unrelated API without checking its contract.
Complete the payment lifecycle
The SDK requires confirmation after authorization to complete the payment flow; void handles cancellation before settlement. For Windows production, the guide recommends an automatically started service. Live deployment also changes account credentials and endpoint configuration. Recommended kiosk state Application responsibility Order reserved Keep inventory or machine availability reserved for a bounded period. Payment in progress Prevent a new customer from inheriting the previous session. Payment approved Persist the result before triggering the fulfillment policy. Fulfillment fails Record the exception and apply the agreed void/refund workflow. Session closed Clear customer-visible data while preserving transaction audit records.
Test interruptions deliberately
These are recommended integration tests for your machine workflow. They are not additional SDK methods or gateway promises. Disconnect power after authorization but before the machine reports fulfillment. Restart the kiosk UI while the payment service remains running. Restart the payment service and confirm the application detects that it is unavailable. Simulate an out-of-stock or mechanical failure after payment approval. Recover an ambiguous result without dispensing twice or starting another charge.
Prepare unattended operations
Create a runbook that distinguishes payment trouble from machine trouble. Include the order reference, device identity, application build, and last known payment state in support diagnostics; exclude raw payment credentials and card data. Pilot on the actual operating system, device connection, and network environment. Verify service startup after an unattended reboot. Confirm session cleanup, receipt behavior, and remote support access. Reconcile payment records with machine fulfillment events. Expand only after recovery and reconciliation work without developer intervention. Windows configuration examples are not Linux installation instructions. Validate the specific Linux package and device support before committing to that deployment target.