How Can Connect Hub Have No Monthly Fee, Deduct No Payment Fee, and Let Funds Go Directly to the Merchant?

Connect Hub is not part of the payment clearing or fund-receiving path. Customer payments go directly to the merchant's bank account, while the system uses bank notification information as an operational input. Connect Hub develops the system itself with a business model intended to keep merchant costs predictable.

How Can Connect Hub Operate Without Deducting Payment Fees?

Funds Go Directly to the Merchant

Connect Hub does not receive or temporarily hold customer funds. Payments continue to the merchant's bank account through the bank's payment channel.

Notification Information Is the Operational Starting Point

The system works with notification information from supported banking channels and uses that information for alerts and related operational functions.

The Merchant's Phone Receives the Notification

For phone-based setups, the merchant's device is the endpoint that receives notifications from supported banking applications before relevant information is used by the Connect Hub system.

Connect Hub Develops Its Own System

Developing the relevant system itself allows Connect Hub to design its service structure and business model around making costs more controllable for merchants.

Separate the Money Path from the Notification Path

Customer funds move through the bank's payment system directly to the merchant's account. Connect Hub operates on the notification-information and post-payment operational side, rather than acting as an intermediary that clears the funds.

A common question is how Connect Hub can operate without a monthly fee or deducting a fee from each customer payment, and whether merchant funds pass through Connect Hub in the process. The key point is that Connect Hub is not responsible for receiving or clearing funds between the customer and the merchant. When a customer pays through the bank's payment channel, the funds go directly to the merchant's bank account according to the bank's payment system. Connect Hub does not receive the customer's funds, temporarily hold them, deduct a transaction fee, and later transfer the remaining amount to the merchant. Connect Hub operates on the notification and operational side of the process rather than in the movement of money. For supported setups, Connect Hub uses notification information from banks or supported merchant banking applications as an initial operational input. This allows the system to recognize that a payment event has occurred and use that information for audible notifications or related operational functions. In setups that use a phone, the merchant's phone acts as an endpoint where notifications from supported banking applications are received. Connect Hub Merchant Manager works with the notification information received from those supported applications to the extent required for the service. This structure differs from a service provider that sits directly in the payment path. Connect Hub does not need to receive customer funds first and then settle those funds to the merchant. Another reason this model can be designed without deducting a fee from every transaction is that Connect Hub develops the relevant system itself and uses a business model intended to make system costs easier for merchants to understand and control. Therefore, when a customer pays 100 baht through the bank's payment channel, Connect Hub's role is not to receive that 100 baht, deduct a service fee, and forward the remainder. The funds continue through the bank's payment process to the merchant's account, while Connect Hub works with notification information associated with the payment event. Separating the “money path” from the “notification-information path” is fundamental to understanding how Connect Hub works. The money path involves the customer, the bank's payment channel, and the merchant's bank account. The notification path involves using information received from supported sources to help the merchant recognize the payment event and support related operational functions. For the same reason, if a QR Box does not sound or a notification is delayed, this does not automatically mean that customer funds are being held by Connect Hub. Connect Hub was not holding or clearing those funds in the first place. For merchants, this structure keeps payment receipt clearly separated from the notification system. Funds continue to go directly to the merchant's bank account, while Connect Hub operates as a technology system for payment-event awareness and related merchant automation. The reason Connect Hub can therefore operate without a monthly fee and without deducting a payment fee is not that it takes control of merchant funds. It is based on a system and business model that separates notification services from payment clearing, together with Connect Hub developing the relevant technology itself to maintain control over the service's cost structure.