CHAPAYMENT user manual
This package is for developers integrating a payment-state component into a Windows program. It is not a standalone checkout application. Double-clicking the DLL will not open a payment screen.
Download and verify
- Download the Windows x64 ZIP and its SHA-256 checksum file from the same release page.
- In PowerShell, run
Get-FileHash .\CHAPAYMENT_0.2.0-preview_Windows_x64.zip -Algorithm SHA256and compare the value with the published checksum. - Extract the archive to a new folder. Keep its bin and manuals folders together.
- Use 64-bit Windows and a 64-bit application. The native runtime is statically linked.
A matching hash detects accidental changes; it is not a publisher signature. This preview DLL has not been Authenticode-signed.
What the download can do
A programmer can call the DLL to validate an integer amount and apply the documented state rules. Run bin\card-cli.exe --self-test to perform the built-in contract checks. It does not read a card, contact a bank or make a charge.
Run the native checks
Open a command prompt in the extracted bin folder. Run card-cli.exe --self-test, then card-cli.exe --discover. To probe a listed reader, run card-cli.exe --probe followed by its exact name in quotes. This connects and disconnects without reading payment credentials. The DLL and helper do not depend on Python. Optional ICPP orchestration is maintained privately.
Reader diagnostics
The updated local EPOS Admin menu includes Card reader diagnostics, which calls this DLL directly. It lists readers exposed through Windows PC/SC and reports when Windows Smart Card service is unavailable. USB HID and serial terminals may require a separate vendor adapter. A listed reader is not necessarily supported for payments.
Troubleshooting
| Symptom | Action |
|---|---|
| DLL will not load | Check x64 application architecture and the exact DLL path. Do not download replacement runtime DLLs from unrelated sites. |
| Reader TEST is missing | Restart the updated EPOS executable with the simulator environment setting. The service also needs sandbox mode and simulator enabled. |
| UNKNOWN payment | Keep the retry record. In this test build use recover. Real payments would require provider reconciliation; do not assume a timeout means decline. |
| Reader service unavailable | Ask the administrator to check the Windows Smart Card service and installed reader driver. Do not change the payment state to compensate. |
| No readers listed | Check the cable, driver and interface type. This preview does not claim support for every USB reader. |
| Print failure | Recover or reprint the receipt through EPOS. Do not repeat the payment. |
Update and remove
Close programs that load the DLL before replacing it. Keep a backup of the previous version and verify the new package checksum. ABI changes require programmer review. To remove this SDK, close consuming applications and remove its extracted folder; no service, driver or registry registration is installed by extracting it. Removing this SDK does not remove EPOS records.
Before reporting an issue
Record the package version, Windows architecture, application version, exact error and reproduction steps. Do not include card numbers, PINs, CVV values, merchant secrets or customer data. Share diagnostics through your established ChapAI support contact.