providing a computerized aggregate payment architecture for carrying out the method, wherein the method provides an aggregated plurality of payment channels between the merchants and third-party payers comprising a unified interface for processing customer payment transactions, wherein the payment architecture is in electronic communication with a plurality of third-party payers, each comprising a transaction object;

wherein the payment architecture comprises a multiple layer server/client configuration wherein the merchants comprise a plurality of client POS terminals in electronic communication with a server of the payment architecture;

wherein the payment architecture comprises a back end for a plurality of third payment platforms established by the third-party payers and each providing a specific payment method or payment service type;

wherein the payment architecture comprises at least three independent software service layers which are in communication with one another in the payment architecture, comprising:

wherein the plurality of channels are connected to and in communication with the plurality of transaction nodes via a scheduling interface, wherein a specific channel is assigned to process a transaction in accordance with a specific transaction node, wherein the scheduling interface matches each channel with a specific third-party payer platform in accordance with an application protocol for that platform;

wherein each channel is logically independent of every other channel and shielded from an upstream transaction node to maintain unified, consistent transaction processing despite changes to other channels;

wherein the relay server of the payment architecture is configured to provide transaction node redundancy in processing a transaction, wherein if a specific transaction node is not available to transfer a transaction to a matched channel in the channel gateway, the relay server transfers the processing of the transaction to another transaction node based on a stored data structure comprising a mapping table and based on transaction node assignment rules;

wherein the payment architecture executes the steps of the method as follows:

acquiring, by the access frontend, transaction information from a client, wherein the transaction information comprises location information of the client or the location information of the server of a specific third-party payer which is the transaction object;

assigning, by the relay server, based on the location information, the transaction information to a transaction node that has jurisdiction over payment transactions of the location information by: matching, based on a service type of the transaction information, an assignment rule in the mapping table, such that requests for the same service type from the same client are processed by the same transaction node,

wherein the transaction node is deployed in the core service layer performing transaction service processing, and wherein the transaction node is classified as one of a plurality types of transaction nodes according to a location of a transaction object,

wherein the transaction object is a third party payment platform, and wherein the transaction node is assigned according to whether the transaction object is a bank in a domestic country or a bank in a foreign country, or is a non-bank third party payment platform in a domestic country or a non-bank third party payment platform in a foreign country;

acquiring, according to the assignment rule, information of a usage state of a matched transaction node, wherein the usage state comprises a predetermined transaction traffic ratio of the assigned transaction node;

in response to the usage state of the transaction node meeting a first predetermined condition, assigning, based on the location information, the transaction information to the transaction node that has jurisdiction over the location information;

matching, according to the transaction node, a channel gateway in a channel docking layer that pre-establishes an electronic connection relationship via an application interface with the transaction node, and

sending a transaction request in the transaction information to a transaction object over the matched channel gateway such that the transaction object processes the transaction request, wherein the transaction object is identified based on the transaction information, and wherein the channel gateway communicates with the transaction node by the scheduling interface, and the channel gateway and the scheduling interface form a communication interface,

wherein the scheduling interface is configured to shield interaction details to enable a connection of the transaction node with different transaction objects through a unified scheduling interface and maintain a consistent transaction process for different transaction objects; and

acquiring, by the transaction node, a processing result from the transaction object, and transmitting information of the processing result to the client,

wherein the client is configured to maintain one set of processes for interacting with the aggregated payment architecture having different transaction nodes through the unified scheduling interface.