Known Issues
Tracked bugs across all Handpoint SDK and API products. Issues marked Open have no fix yet — check the workaround column. Issues marked Fixed include the version that resolved them.
To add or update an issue, edit data/knownIssues.js. Use visibility: 'internal' for issues not ready for public disclosure.
Pre-auth capture fails silently when terminal loses connectivity mid-capture
If the terminal drops its connection to Handpoint Cloud between the pre-auth and the capture call, the capture request may be lost without triggering a connection-loss callback. The transaction remains in an open authorized state with no indication of failure on the POS side.
Introduced: 7.1010.0
MOTO refund via GUID returns 200 but transaction is not refunded when original sale is older than 90 days
Refund requests targeting transactions older than 90 days return HTTP 200 with a SUCCESS status, but the acquirer rejects the refund silently. The transaction remains settled with no credit applied. Affects all TSYS-backed acquirers.
`transactionReference` silently stripped on moToSale — status poll by reference returns nothing
When `operation: "moToSale"` is sent to POST /transactions, the `transactionReference` field is ignored by the platform. The completed result contains a system-generated reference that does not match the sent value. As a result, GET /transactions/{transactionReference}/status returns no result for on-terminal MOTO transactions.
See also: MOTO Guide — On-terminal keyed entry
Tip adjustment returns SUCCESS status but amount is not updated in batch when applied within 60 s of the original sale
A race condition in the batch reconciliation layer causes tip adjustments submitted less than ~60 seconds after the original transaction to return a SUCCESS response from the SDK, but the batch record is not updated. The adjusted amount is absent from the settled batch.
Introduced: 7.1009.0Fixed: 7.1012.2
HiLite Bluetooth reconnection fails after iOS 17.4 background refresh
After an iOS background refresh cycle on iOS 17.4+, the HiLite device Bluetooth connection is not automatically re-established. The SDK reports `DeviceDisconnected` but does not attempt a reconnect within the expected 30-second window.
Introduced: 4.0.2
onMessageReceived callback not fired for STATUS_CHANGED events in Firefox 121+
A change in Firefox 121's WebSocket event handling breaks the `onMessageReceived` listener for `STATUS_CHANGED` event types. Other event types are unaffected. The device connection itself remains intact.
Introduced: 7.2.0Fixed: 7.2.4
ViscusDummy declines surface as HTTP 400 instead of a decline response on POST /moto/sale
In sandbox, when ViscusDummy declines a card (e.g. a trigger amount configured for decline), POST /moto/sale returns HTTP 400 with the message "Unable to perform Viscus operation" instead of a proper decline response with finStatus: "DECLINED". Integration code that treats 4xx as validation or gateway errors will mis-classify these as non-decline failures. This affects ViscusDummy only — production acquirers return a proper decline response.
See also: MOTO Guide — Remote sale error codes
[INTERNAL] Battery level callback fires twice on PAX A920 Pro on first connection
On A920 Pro firmware 5.x, the `onBatteryLevelChanged` callback is invoked twice with the same value immediately after initial SDK connection. This is cosmetic — no functional impact — but can cause duplicate log entries.
Introduced: 7.1011.0
[INTERNAL] Batch close response occasionally omits transactionCount field under high load
Under sustained load (>50 concurrent batch-close requests), the `/closeBatch` response sometimes returns without the `transactionCount` field. All other fields and the settlement itself are unaffected.