Skip to content

Troubleshooting

Bluetooth permission

If scanning returns no devices, verify that your app has been granted Bluetooth access. When running for the first time, the OS shows a permission prompt during the first startScan() call. If the user dismisses the scanner before tapping Allow, have them dismiss and re-open the scanner after granting permission in Settings.

The NSBluetoothAlwaysUsageDescription key must be present in your Info.plist before the prompt will appear.

Physical device required

The SDK cannot run on the iOS Simulator. Deploy to a physical device for all testing with the PAX D135.

Device pairing indicators

LEDStatus
OrangeReady for pairing
GreenBattery fully charged
Green only (post-connect)Connected and ready
BlueWaiting for card interaction
Off + beepingCard detected

Firewall settings

The PAX D135 downloads its encryption keys from PAX servers during first-time configuration. This traffic uses the internet connection of the phone or tablet the D135 is paired with. If that network has a firewall, allow the following PAX hosts for the environment your Device is designated for:

EnvironmentHost
Sandboxrkilt.pax.us:33619
Productionrki.pax.us:33519

Troubleshooting Your Terminal

For device-level issues such as connectivity, charging, and LED status, see the Troubleshooting Your Terminal guide.

Contact support

Email support@finix.com with a description of the issue, your device serial number, and your SDK version.