How Should a Store Set Up Payment Notifications Across Multiple Payment Points?

Stores with multiple counters, payment points, or work areas should design payment notifications around three practical questions: where each payment comes from, who needs to know about it, and where the audible alert should be heard.

Start with Three Questions

Where Does the Payment Come From?

Identify how many payment points the store has and which merchant app, account, or payment source is used at each one.

Who Needs to Know?

Decide whether all staff need to know about every payment or whether each counter or work area should receive only the notifications relevant to it.

Where Should the Sound Be Heard?

Place the QR Box or alert device according to where staff actually work rather than simply according to the phone's location.

Separate the Payment Source from the Alert Location

In a store with multiple payment points, treating the notification source and the place where staff need to hear the alert as separate decisions makes it easier to design around the actual workflow. Some payments may need to alert one area, while others may need to be recognized across several areas.

When a store has more than one payment point, designing a payment notification setup becomes more complex than in a single-counter environment. The question is no longer only, “Has the payment arrived?” The store may also need to understand which payment point the transaction relates to and which staff members need to know about it. For example, a business may have a front counter, a pickup area, another service station, or several employees working in separate parts of the premises. If all payment alerts come from only one location, some staff may hear notifications that are not relevant to their work, while another area that actually needs the information may not hear the alert clearly. The design should therefore begin with the store's payment workflow rather than with the number of QR Boxes or devices to install. The first question is how many payment points the business has and what payment source each one uses. If several points use the same merchant banking application or account, the merchant should consider whether every area needs to know about every payment or whether only certain staff members need the notification. The second question is who needs to recognize each payment. Some businesses may want every employee to hear the same notification, while others may want alerts separated by counter or working area. The third question is where the sound should be heard. The alert device should be placed according to where staff actually work. It does not necessarily need to be physically close to the phone. With supported Connect Hub setups, the phone and QR Box can be in different locations and use different internet connections, provided the required devices remain connected and correctly configured. For a multi-payment-point environment, separating the “source of the notification” from the “place where the alert needs to be heard” can make the design much clearer. For example, one payment source may need to alert only one work area, while another may need to be heard in several areas. With Connect Hub Merchant Manager, merchants can manage supported merchant banking applications and assign the QR Boxes intended to receive notifications from individual apps. This allows the notification arrangement to follow the store's operating workflow more closely. However, having multiple payment points does not automatically mean that every point needs a separate notification setup. If all counters are close together, the same staff members manage them, and one audible alert can be heard clearly throughout the area, a simpler arrangement may be sufficient. By contrast, if payment points are physically separated, managed by different teams, or responsible for different transactions, separating audible alerts or assigning notifications by work area may help staff recognize the events relevant to their own responsibilities. The key principle is to design around workflow rather than device count. Start with the payment source, identify who needs to know, determine where the sound needs to be heard, and then choose an appropriate device arrangement. Before normal operation, merchants should test payments from each payment point and confirm that notifications are heard in the intended locations. They should also verify that no work area receives or misses notifications contrary to the intended setup. Customer payments continue to go directly to the merchant's bank account. Connect Hub uses supported merchant-app notification information to help businesses organize payment-event awareness according to the workflow they have configured.