QR Box Test Sound Works, but Real Payments Are Silent: What Does It Mean?

If the QR Box can play its test sound but remains silent during a real payment, the box's audible output is working during the test. Troubleshooting should then continue with the merchant app notification, configuration, device status, and connectivity.

What Does a Successful Test Sound Tell You?

The QR Box Can Produce Sound

If the direct test produces a sound, the QR Box audible-output function is working at the time of the test.

It Does Not Confirm the Real Payment Path

A successful sound test does not confirm that a real payment notification is reaching the QR Box through every required stage.

Check the Merchant App Notification

Confirm that the payment appears in the merchant banking application and that the phone receives the merchant app notification normally.

Check Configuration and Connectivity

If the merchant app is notifying normally, review device status, Connect Hub Merchant Manager configuration, phone permissions, and connectivity of the relevant devices.

Separate the QR Box Sound Test from the Real Payment Test

A sound test answers whether the QR Box can produce an audible alert. A real payment test checks the broader path, including the merchant banking application, phone settings, system status, and the QR Box. Treating these as separate tests makes troubleshooting more precise.

If the QR Box plays its test sound normally but remains silent when a real payment is made, this result already helps narrow down the problem. It shows that the QR Box is capable of producing sound at the time of the test. However, a sound test and a real payment notification are different stages. The sound test checks whether the QR Box itself can produce an audible alert. A real payment begins with a payment event and a notification from a supported source before that event can be used with the QR Box. Therefore, if the test sound works but a real payment produces no sound, it is useful not to immediately conclude that the QR Box is faulty. The next step is to determine whether the real payment event is progressing correctly through the notification setup. The first place to check is the merchant banking application. Confirm that the payment appears in the received-payment records and that the phone receives the merchant application's notification normally. If the merchant application does not generate the expected notification, the later parts of the notification setup will not have that information to use. If the phone receives the merchant app notification normally, check Connect Hub Merchant Manager and confirm that the relevant device status and configuration are ready for use. Also verify that the intended merchant banking application and QR Box are configured correctly. Phone permissions and settings should also be reviewed. Seeing the merchant app notification on the phone screen does not necessarily confirm that every setting required by the notification system remains correctly configured. Internet connectivity on both the phone and QR Box should also be checked. The devices do not need to use the same internet network, but the required parts of the system need working connectivity for notification events to be delivered normally. In practical troubleshooting, a successful test sound is useful evidence because it indicates that the QR Box can produce an audible alert at that moment. Attention can then move to whether the real payment event reaches the notification system and is correctly associated with the intended QR Box. A useful approach is to collect evidence from each stage, such as the merchant app's payment record, the device-status screen in Connect Hub Merchant Manager, and the relevant settings or permissions. After any correction, perform another small real payment test. The meaning of “the test sound works, but a real payment is silent” is therefore best understood by separating the problem into two parts: the QR Box audible-output function, which has successfully passed the test at that moment, and the real payment notification path, which still needs to be checked from the notification source through configuration and connectivity. Customer payments continue to go directly to the merchant's bank account. Connect Hub uses notification information from supported sources to help merchants recognize payment events through the configured notification system.