I am not very familiar with the PromptPay architecture, but a quick search reveals that the user-facing app for QR scanning is bank-owned, rather than a Third-Party Application Provider (TPAP) like Google Pay is for UPI. In the case of UPI, you can link multiple accounts from the same or different banks to a single TPAP.
Another potential difference is the interbank protocol implementation. For UPI, the messages involved in a transaction are asynchronous. When NPCI calls the remitter bank for a debit request (ReqPay message), the bank is only supposed to send back an acknowledgement message (Ack) in the same HTTP request. Once the processing is done, the bank's switch sends a response (RespPay message) to a callback endpoint at NPCI (which, in turn, returns an Ack to the remitter bank). A similar flow happens when NPCI sends a request to the beneficiary bank for credit.
I am not very familiar with the PromptPay architecture, but a quick search reveals that the user-facing app for QR scanning is bank-owned, rather than a Third-Party Application Provider (TPAP) like Google Pay is for UPI. In the case of UPI, you can link multiple accounts from the same or different banks to a single TPAP.
Another potential difference is the interbank protocol implementation. For UPI, the messages involved in a transaction are asynchronous. When NPCI calls the remitter bank for a debit request (ReqPay message), the bank is only supposed to send back an acknowledgement message (Ack) in the same HTTP request. Once the processing is done, the bank's switch sends a response (RespPay message) to a callback endpoint at NPCI (which, in turn, returns an Ack to the remitter bank). A similar flow happens when NPCI sends a request to the beneficiary bank for credit.