Skip to content

Voice Broadcast APP: Overview and Pipeline ​

Updated: 11/17/26, 11:11:43 AM

The Voice Broadcast APP is a payment reminder tool that runs on an Android phone. Once the APP is installed and activated, the phone becomes a virtual device: on a successful payment it announces the received amount by voice, and with a receipt printer connected it prints the receipt at the same time. There is no need to buy physical hardware such as cloud speakers or cloud printers; an idle phone covers both "hear the payment arrive" and "keep the receipt".

Core Capabilities ​

CapabilityDescription
Voice broadcastOn a successful payment, announces the received amount and the payment channel; the voice clips are built into the APP, so it does not depend on phone TTS and does not use mobile data
Receipt printingWith a receipt printer connected, prints automatically on a successful payment; 58 / 80mm paper widths supported
Online statusThe APP reports a heartbeat to the platform at a fixed interval; both the admin panel and the merchant panel show whether the device is online
Multilingual interfaceThe interface supports 10 languages: Simplified Chinese, Traditional Chinese (Taiwan / Hong Kong), English, Japanese, Korean, Indonesian, Malay, Thai and Vietnamese, following the system language or set manually in the APP; notifications, the home-screen widget and error messages switch with the language (path: Settings → Display & Language). The broadcast voice is built from built-in Chinese clips and does not change with the interface language
App-level switchesEach payment app can enable / disable voice broadcast and receipt printing independently, and choose the receipt layout (path: App List → open its configuration → App Workbench → Payment Broadcast)
Test broadcast / test printDevice lists on both the admin panel and the merchant panel offer test entries, so the broadcast and print chain can be verified without a real payment
Phone-side extrasDesktop amount widget, on-device payment history queries and do-not-disturb hours, all used inside the APP

How a Payment Message Travels ​

  1. The platform receives a successful payment result and publishes a message by device number;
  2. The message goes through the Artemis broker and is pushed to the phone over a persistent MQTT over WebSocket (wss) connection;
  3. The APP decrypts the message and plays the voice; when printing is needed it takes the receipt command stream delivered by the platform for the paper width;
  4. The APP reports the broadcast acknowledgement to the platform and keeps a heartbeat every 5 minutes.

For the topic contract of the message pipeline, the receipt rendering method and the activation acknowledgement mechanism, see Design Architecture.

Device and Printing Compatibility ​

ItemSupported range
PhoneAndroid 8.0 or later, APK installed
Printer58 / 80mm ESC/POS thermal receipt printer
ConnectionClassic Bluetooth (SPP), USB, network printer (RAW TCP 9100)
Print dataThe ESC/POS command stream rendered by the platform; the APP outputs it as-is and does no local layout

The phone and a network printer must be on the same LAN; enter the printer IP and port. The paper width setting in the APP must match the paper actually used, otherwise the receipt layout breaks.

Two Design Boundaries ​

  • Orders from the online API and EasyPay sources are not announced or printed by default: the feature targets manual cashier scenarios, and API orders have no in-store broadcast need;
  • Broadcast messages are encrypted with the device key: the access account may only subscribe, not publish, on the message service, which prevents forged payment messages (built in on the platform, no configuration needed).

How to Obtain ​

  • The open-source edition can download daxpay-virtual-device-release.apk directly (Android 8.0+); it is also available in the download areas of the website product page and the system demo page;
  • The commercial edition installer goes through the commercial release channel; the two installers can coexist on one phone;
  • The source code is delivered as source with the Ecosystem Extension Pack (source-code license included).

The server address is built into the installer at compile time; the APP offers no runtime input. After switching to an installer that points at another environment, activation is required again, which is expected behavior.

Continue Reading ​