The following lists the built-in security feature of the LISNR Radius 3.0 SDK:
Radius 3.0 contains a built-in feature called ToneLock for securing transmitted payload data. The ToneLock feature allows a developer to add an unique identifier (UUID) to a transmitted Tone, ensuring that it cannot be received unless the receiving device has the same identifier set. If the receiving device is not enabled with ToneLock and the ToneLock UUID does not match the value of the transmitter's ToneLock, the payload will not be demodulated. ToneLock is not the same technique as encryption but it does prevent the same type of man in the middle (data interception) fraud attempts.
ToneLock will be enabled for the Point1000 and Point2000 tone profiles
In addition for Radius 2.0 SDK and prior versions:
SDK and API tokens limit who can use Radius
SDK/API Tokens are cryptographically signed using key(s) specific to LISNR, adding a level of protection to prevent unauthorized use
a Radius Tone can not be generated/transmitted or unintentionally demodulated by an unauthorized user without the use of the Radius SDK
LISNR's patent portfolio
Radius SDK is a transport mechanism. Payload contents are never stored or observed.
The Point1000/Point2000 tone profile(s) are close range (3 feet) and physically difficult to intercept
The Point1000/Point2000 tone profile(s) provides a high throughput (1000-2000 bits/sec) to support additional security measures listed below.
The Radius SDK can also enable and support the transmission of OTP (one time passwords), tokenized, or encrypted payloads that are generated by our users and can ensure a secure connection.
QR Code comparison - fraud attempts with QR codes are caused by malicious users generating fake QR codes which can be easily done by any type of user. LISNR's Radius SDK has an advantage over this because it is much easier to create a fake/malicious QR code and put it in front of a consumer VS creating a Radius tone from scratch that is able to be demodulated by our SDK.