Payment processing method and device, equipment and storage medium

Abstract

The invention provides a payment processing method and device, equipment and a storage medium, which can be applied to the technical fields of mobile payment, cloud computing, distributed systems, block chains and the like, and comprises the following steps: a public forwarding proxy server receives a first service request sent by terminal equipment; when the first URL of the first service request comprises the identification information of the first public gateway interface, a target payment server where the first public gateway interface is located is selected from N payment servers based on the identification information of the first public gateway interface, and the N payment servers are used for supporting different payment services; at least part of the public gateway interfaces configured on the N payment servers are obtained by splitting the public gateway interfaces of the first type; and sending the first service request to the target payment server, so that the target payment server processes the first service request through the first public gateway interface. Therefore, the management and maintenance reliability of the payment service is improved, and the payment processing performance and efficiency are improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, and in particular to a payment processing method, apparatus, device, and storage medium. Background Art

[0002] With the rapid development of the internet, mobile payments have emerged, bringing convenience to users' daily payments. Current mobile payment scenarios primarily include commercial payments, social payments, and coin top-ups and withdrawals. Commercial payments involve payments between consumers and merchants, while social payments can include sending red envelopes, transferring money, and face-to-face payments.

[0003] Current mobile payment methods typically involve a payment client sending a service request to a public forwarding proxy server based on a payment operation by an object (e.g., a user). The public forwarding proxy server then forwards the service request to a payment server for payment processing. However, current payment methods suffer from unclear payment service management, poor payment system maintainability, and inconvenience in updating payment services. Summary of the Invention

[0004] The present application provides a payment processing method, apparatus, device and storage medium. By allocating different types of payment services to different payment servers, the management and maintenance reliability of payment services can be improved, and version updates of the payment service system can be facilitated.

[0005] In a first aspect, the present application provides a payment processing method, applied to a public forwarding proxy server, comprising:

[0006] receiving a first service request sent by a terminal device, where the first service request is generated by the terminal device when the subject performs a payment operation for a first payment service;

[0007] When the first URL of the first service request includes identification information of a first public gateway interface for processing the first service request, a target payment server where the first public gateway interface is located is selected from N payment servers based on the identification information of the first public gateway interface, the N payment servers being used to support different payment services, and at least some of the public gateway interfaces configured on the N payment servers being obtained by splitting a first type of public gateway interface, the first type of public gateway interface including M payment functions, where N is a positive integer and M is a positive integer greater than 1;

[0008] The first service request is sent to the target payment server, so that the target payment server processes the first service request through the first common gateway interface.

[0009] In a second aspect, the present application provides a payment processing method, applied to a payment proxy server, comprising:

[0010] receiving a first service request sent by a public forwarding proxy server, where the first service request is generated by a terminal device when a subject performs a payment operation for a first payment service, a first URL of the first service request includes a command identifier corresponding to the first service request and does not include identification information of a first public gateway interface used to process the first service request, and the command identifier is used to indicate the first service request;

[0011] Determining identification information of the first public gateway interface based on the command identifier corresponding to the first service request;

[0012] selecting, based on the identification information of the first public gateway interface, a target payment server where the first public gateway interface is located from N payment servers, where the N payment servers are configured to support different payment services, and at least some of the public gateway interfaces configured on the N payment servers are obtained by splitting a first type of public gateway interface, where the first type of public gateway interface includes M payment functions, where N is a positive integer and M is a positive integer greater than 1;

[0013] Based on the identification information of the first public gateway interface, the first URL of the first business request is modified to obtain a second URL of the first business request, and the first business request including the second URL is sent to the target payment server, so that the target payment server processes the first business request through the first public gateway interface.

[0014] In a third aspect, the present application provides a payment processing method, applied to a target payment server, comprising:

[0015] receiving a first service request, where the first service request is generated when a subject performs a payment operation for a first payment service, the target payment server being one of N payment servers, the N payment servers being configured to support different payment services, and at least some of the public gateway interfaces configured on the N payment servers being split from a first-type public gateway interface, the first-type public gateway interface including M payment functions, where N is a positive integer and M is a positive integer greater than 1;

[0016] Based on the identification information of the first public gateway interface, calling the first public gateway interface in the target payment server to process the first service request, where the first public gateway interface is a public gateway interface used to process the first service request;

[0017] Among them, when the first URL of the first business request includes the identification information of the first public gateway interface, the first business request is sent by the public forwarding proxy server; when the first URL of the first business request includes the command identifier corresponding to the first business request and does not include the identification information of the first public gateway interface, the first business request is sent by the payment proxy server, and the command identifier is used to indicate the first business request.

[0018] In a fourth aspect, the present application provides a payment processing method, applied to a terminal device, comprising:

[0019] In response to the object's payment operation on the first payment service, generating a first service request and a first URL of the first service request;

[0020] The first business request is sent to a public forwarding proxy server, so that based on the first URL of the first business request, a target payment server where a first public gateway interface is located is selected from N payment servers to process the first business request, where the first public gateway interface is a public gateway interface used to process the first business request, the N payment servers are used to support different payment services, and at least some of the public gateway interfaces configured on the N payment servers are obtained by splitting a first type of public gateway interface, where the first type of public gateway interface includes M payment functions, where N is a positive integer and M is a positive integer greater than 1.

[0021] In a fifth aspect, the present application provides a payment processing device, applied to a public forwarding proxy server, comprising:

[0022] a receiving unit, configured to receive a first service request sent by a terminal device, where the first service request is generated by the terminal device when the subject performs a payment operation for a first payment service;

[0023] a processing unit configured to, when the first URL of the first service request includes identification information of a first public gateway interface for processing the first service request, select, based on the identification information of the first public gateway interface, a target payment server where the first public gateway interface is located from N payment servers, the N payment servers being configured to support different payment services, and at least some of the public gateway interfaces configured on the N payment servers being split from a first type of public gateway interface, the first type of public gateway interface including M payment functions, where N is a positive integer and M is a positive integer greater than 1;

[0024] A sending unit is configured to send the first service request to the target payment server, so that the target payment server processes the first service request through the first common gateway interface.

[0025] In some embodiments, the public forwarding proxy server stores identification information of a public gateway interface configured on each of the N payment servers, and the processing unit is specifically used to determine, based on the identification information of the first public gateway interface, the target server where the first public gateway interface is located from the identification information of the public gateway interface configured on each of the N payment servers stored by the public forwarding proxy server.

[0026] In some embodiments, the sending unit is further used to send the first business request to the payment proxy server when the first URL includes a command identifier corresponding to the first business request and does not include identification information of the first public gateway interface, so that the payment proxy server selects the target payment server from the N payment servers based on the command identifier corresponding to the first business request, and the command identifier is used to indicate the first business request.

[0027] In some embodiments, the receiving unit is further used to receive a processing result of the first business request, where the processing result is a processing result obtained by the target payment server processing the first business request through the first public gateway interface; the sending unit is further used to send the processing result to the terminal device; wherein, when the public forwarding proxy server sends the first business request to the target payment server, the processing result is sent by the target payment server, and when the public forwarding proxy server sends the first business request to the payment proxy server, the processing result is sent by the payment proxy server.

[0028] In a sixth aspect, the present application provides a payment processing device, applied to a payment proxy server, comprising:

[0029] a receiving unit, configured to receive a first service request sent by a public forwarding proxy server, where the first service request is generated by a terminal device when a subject performs a payment operation for a first payment service, a first URL of the first service request including a command identifier corresponding to the first service request and not including identification information of a first public gateway interface for processing the first service request, and the command identifier being used to indicate the first service request;

[0030] an interface determining unit, configured to determine identification information of the first public gateway interface based on a command identifier corresponding to the first service request;

[0031] a server determining unit configured to select, based on the identification information of the first public gateway interface, a target payment server where the first public gateway interface is located from N payment servers, where the N payment servers are configured to support different payment services, and at least some of the public gateway interfaces configured on the N payment servers are obtained by splitting a first type of public gateway interface, where the first type of public gateway interface includes M payment functions, where N is a positive integer and M is a positive integer greater than 1;

[0032] a modification and sending unit, configured to modify the first URL of the first business request based on the identification information of the first public gateway interface to obtain a second URL of the first business request, and send the first business request including the second URL to the target payment server, so that the target payment server processes the first business request through the first public gateway interface.

[0033] In some embodiments, the payment proxy server stores the correspondence between different business requests and different command identifiers, as well as the correspondence between different business requests and different public gateway interfaces. The interface determination unit is used to determine the identification information of the first business request from the correspondence between the different business requests and different command identifiers based on the command identifier corresponding to the first business request; and based on the identification information of the first business request, query and obtain the identification information of the first public gateway interface from the correspondence between the different business requests and different public gateway interfaces.

[0034] In some embodiments, the payment proxy server saves the identification information of the public gateway interface configured on each of the N payment servers, and the server determination unit is specifically used to determine the target server where the first public gateway interface is located from the identification information of the public gateway interface configured on each of the N payment servers based on the identification information of the first public gateway interface.

[0035] In some embodiments, the modification sending unit is configured to add identification information of the first common gateway interface to the first URL of the first service request to obtain a second URL of the first service request.

[0036] In some embodiments, the receiving unit is further used to receive the processing result of the first business request sent by the target payment server; the modified sending unit is further used to send the processing result to the public forwarding proxy server, so that the public forwarding proxy server sends the processing result to the terminal device.

[0037] In a seventh aspect, the present application provides a payment processing device, applied to a target payment server, comprising:

[0038] a receiving unit, configured to receive a first service request, where the first service request is generated when a subject performs a payment operation for a first payment service, the target payment server being one of N payment servers, the N payment servers being configured to support different payment services, and at least some of the public gateway interfaces configured on the N payment servers being split from a first type of public gateway interface, the first type of public gateway interface including M payment functions, where N is a positive integer and M is a positive integer greater than 1;

[0039] A calling unit is used to call the first public gateway interface in the target payment server based on the identification port information of the first public gateway interface to process the first business request, where the first public gateway interface is a public gateway interface used to process the first business request; wherein, when the first URL of the first business request includes the identification information of the first public gateway interface, the first business request is sent by the public forwarding proxy server; when the first URL of the first business request includes a command identifier corresponding to the first business request and does not include the identification information of the first public gateway interface, the first business request is sent by the payment proxy server, and the command identifier is used to indicate the first business request.

[0040] In some embodiments, the sending unit is further used to send the processing result of the first business request to the public forwarding proxy server when the first business request is sent by the public forwarding proxy server; and to send the processing result of the first business request to the payment proxy server when the first business request is sent by the payment proxy server.

[0041] In an eighth aspect, the present application provides a payment processing apparatus, applied to a terminal device, comprising:

[0042] a generating unit, configured to generate a first service request and a first URL of the first service request in response to a payment operation of the object for the first payment service;

[0043] A transceiver unit is configured to send the first service request to a public forwarding proxy server, so that based on a first URL of the first service request, a target payment server where a first public gateway interface is located is selected from N payment servers to process the first service request, where the first public gateway interface is a public gateway interface for processing the first service request, the N payment servers are configured to support different payment services, and at least some of the public gateway interfaces configured on the N payment servers are obtained by splitting a first type of public gateway interface, where the first type of public gateway interface includes M payment functions, where N is a positive integer and M is a positive integer greater than 1.

[0044] In some embodiments, the generating unit is specifically configured to obtain version information of the payment client in response to the object's payment operation on the first payment service; and generate a first URL for the first service request based on the version information of the payment client.

[0045] In some embodiments, the generation unit is specifically used to, when the version of the payment client is the first version, obtain the identification information of the first public gateway interface, and generate a first URL for the first business request based on the identification information of the first public gateway interface, the first URL includes the identification port information of the first public gateway interface, and the first version is the latest version of the payment client; when the version of the payment client is not the first version, and the first business request is a first type of business request, obtain the command identifier corresponding to the first business request, and generate a first URL for the first business request based on the command identifier corresponding to the first business request, the first URL includes the command identifier corresponding to the first business request, and the first type of business request includes a wallet binding information query request and a social payment authentication request.

[0046] In some embodiments, the transceiver unit is further configured to receive a processing result of the first service request sent by the public forwarding proxy server.

[0047] In a ninth aspect, an electronic device is provided, comprising a processor and a memory. The memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory to perform the method of any one of the first to fourth aspects and their respective implementations.

[0048] In a tenth aspect, a chip is provided for implementing the method described in any one of aspects 1 to 4 and their respective implementations. Specifically, the chip includes a processor configured to retrieve and execute a computer program from a memory, causing a device equipped with the chip to execute the method described in any one of aspects 1 to 4 and their respective implementations.

[0049] In the eleventh aspect, a computer-readable storage medium is provided for storing a computer program, wherein the computer program enables a computer to execute the method in any one of the above-mentioned first to fourth aspects and their respective implementations.

[0050] In the twelfth aspect, a computer program product is provided, comprising computer program instructions, wherein the computer program instructions enable a computer to execute the method in any one of the above-mentioned first to fourth aspects and their respective implementations.

[0051] In the thirteenth aspect, a computer program is provided, which, when executed on a computer, enables the computer to execute the method in any one of the first to fourth aspects and their respective implementations.

[0052] In summary, the present application splits payment services, assigning different payment services to N different payment servers for processing. Public gateway interfaces (CGIs) with complex payment functions are also split, and the split CGIs are configured on payment servers with corresponding functions. That is, the N payment servers in the embodiments of the present application are used to support different payment services, and at least some of the CGIs configured on the N payment servers are split CGIs of the first type. Thus, during actual payment processing, a terminal device generates a first service request and a first URL for the first service request in response to a payment operation performed by an object on a first payment service. The terminal device then sends the first service request to a public forwarding proxy server. The public forwarding proxy server parses the first URL and, upon detecting that the first URL includes identification information of a first CGI for processing the first payment service, selects a target payment server from the N payment servers, based on the identification information of the first CGI, where the first CGI is located, and then sends the first service request to the target payment server for payment processing. When the public forwarding proxy server detects that the first URL does not include the identification information of the first public gateway interface but includes a command identifier corresponding to the first service request, it sends the first service request to the payment proxy server. Based on the command identifier corresponding to the first service request, the payment proxy server determines the identification information of the first public gateway interface and, based on the identification information of the first public gateway interface, selects a target payment server where the first public gateway interface is located from among the N payment servers. Simultaneously, based on the identification information of the first public gateway interface, the payment proxy server modifies the first URL of the first service request to generate a second URL. Finally, the payment proxy server sends the first service request including the second URL to the target payment server for payment processing. It can be seen from this that the embodiment of the present application splits the payment service and distributes the split payment service to N different payment servers for processing. At the same time, the public gateway interface with complex functions (i.e., the first type of public gateway interface) is split, and the split public gateway interface is configured on the payment server with corresponding functions, so that different payment servers are responsible for part of the payment services, and each payment server is related and independent and does not interfere with each other. When the payment logic on one of the payment servers needs to be modified, it will not affect the payment logic on other payment servers, thereby improving the reliability and accuracy of the management, maintenance and modification of the payment service and payment system, facilitating the version update of the payment system, and thus improving the performance and efficiency of payment processing. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0054] Figure 1 This is a schematic diagram of existing payment processing;

[0055] Figure 2 A schematic diagram of an implementation environment involved in an embodiment of the present application;

[0056] Figure 3 A schematic diagram of a distributed system;

[0057] Figure 4 A schematic diagram of a block structure;

[0058] Figure 5 A flowchart of a payment processing method provided in one embodiment of the present application;

[0059] Figure 6A A schematic diagram of the split for payment services;

[0060] Figure 6B Another split diagram for payment services;

[0061] Figure 7 This is a schematic diagram of an interface split;

[0062] Figure 8 A schematic diagram of a payment client;

[0063] Figure 9 This is a schematic diagram of another payment client;

[0064] Figure 10 A payment processing diagram according to an embodiment of the present application;

[0065] Figure 11 A flowchart of a payment processing method provided in one embodiment of the present application;

[0066] Figure 12 A schematic diagram of a payment processing process according to an embodiment of the present application;

[0067] Figure 13 A payment processing diagram according to an embodiment of the present application;

[0068] Figure 14 A flowchart of a payment processing method provided in one embodiment of the present application;

[0069] Figure 15is a schematic block diagram of a payment processing device provided in one embodiment of the present application;

[0070] Figure 16 is a schematic block diagram of a payment processing device provided in one embodiment of the present application;

[0071] Figure 17 is a schematic block diagram of a payment processing device provided in one embodiment of the present application;

[0072] Figure 18 is a schematic block diagram of a payment processing device provided in one embodiment of the present application;

[0073] Figure 19 It is a schematic block diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0074] The following will be combined with the accompanying drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0075] It should be noted that the terms "first," "second," and the like in the specification and claims of this application and the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein. In an embodiment of the present invention, "B corresponding to A" means that B is associated with A. In one implementation, B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B solely based on A, but that B can also be determined based on A and / or other information. In addition, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or server that includes a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to these processes, methods, products, or devices. In the description of this application, unless otherwise specified, "plurality" means two or more than two.

[0076] The technical solution proposed in this application can be applied to technical fields such as mobile payment, cloud computing, distributed systems, blockchain, etc., to improve the convenience and client-side management and maintenance of payment services, facilitate version updates, and improve payment processing efficiency.

[0077] The following is an introduction to the relevant concepts involved in the embodiments of this application.

[0078] Cloud technology is a general term for network technologies, information technologies, integration technologies, management platform technologies, and application technologies based on the cloud computing business model. It can form a resource pool that can be used flexibly and conveniently on demand. Cloud computing technology will become a crucial support. Backend services for technical network systems, such as video websites, image websites, and more portals, require extensive computing and storage resources. With the rapid development and application of the internet industry, every item will likely have its own unique identifier, requiring transmission to backend systems for logical processing. Different levels of data will be processed separately, and data from various industries will require a strong system backend, which can only be achieved through cloud computing.

[0079] Cloud computing is a computing model that distributes computing tasks across a resource pool consisting of a large number of computers, enabling various application systems to access computing power, storage space, and information services as needed. The network that provides these resources is called the "cloud." To users, these resources appear infinitely scalable and can be accessed at any time, used on demand, expanded at any time, and paid for on a per-use basis.

[0080] A distributed system is one whose components are distributed across interconnected computers, communicating and coordinating their actions through message passing. This definition of a distributed system encompasses any system where networked computers can be deployed effectively. Computers connected by a network can be located at varying distances. They may be located in different countries around the world, or they may be in the same data center.

[0081] CGI (Common Gateway Interface) is a standard interface for external extension applications to interact with web servers. It enables external programs to process form data sent by clients on the www and respond to it. This response can be files, images, sounds, videos, and anything else that appears on a browser form. There are many common ways for servers to interact with clients, and CGI technology is one of them. External extension applications written according to the CGI standard can process data entered by client browsers and complete client-server interaction.

[0082] A URL (Uniform Resource Locator) is a way to identify the location of information on the Internet. A URL consists of multiple parts, including the protocol, domain name, port number, path, and query parameters.

[0083] An instant messaging client is an internet-based communication tool that allows users to communicate with each other in real time through text, voice, video, and other means. These communication tools typically provide instant messaging, voice calls, video calls, file transfers, and other functions, allowing users to communicate and collaborate conveniently.

[0084] Mobile payment refers to electronic currency payments made by mobile clients using electronic devices such as mobile phones. It effectively connects the internet, terminal devices, and financial institutions to form a new payment system. Mobile payment has pioneered new payment methods and popularized electronic currency. In the embodiments of this application, mobile phones, tablet computers, and other terminal devices are equipped with instant messaging clients, which can be used to make mobile payments.

[0085] Current mobile payment methods, such as Figure 1 As shown, the payment client sends a service request to the public forwarding proxy server based on the payment operation of the object (such as the user), and the public forwarding proxy server sends the service request to the payment server for payment processing. Figure 1 As shown, in current payment methods, all payment service logic is coupled to a single payment server. This leads to unclear payment service management, poor payment system maintainability, and difficulty in achieving Quality of Service (QoS). Furthermore, the sheer volume of code and libraries piled together results in a very long compilation time, resulting in low payment service rollout efficiency. Furthermore, when system upgrades are needed, staff members modify a single module, which can easily introduce service code features that are not yet ready for rollout during releases. This leads to a chaotic code structure, error-prone modifications, and high rollout risk, severely impacting version iteration speed and payment processing efficiency.

[0086] To address the above technical issues, the embodiments of the present application split payment services, assigning different payment services to N different payment servers for processing. Public gateway interfaces (CGIs) with complex payment functions are also split, and the split CGIs are configured on payment servers with corresponding functions. That is, the N payment servers in the embodiments of the present application are used to support different payment services, and at least some of the CGIs configured on the N payment servers are split CGIs of the first type. Thus, during actual payment processing, a terminal device generates a first service request and a first URL for the first service request in response to a payment operation performed by an object on a first payment service. The terminal device then sends the first service request to a public forwarding proxy server. The public forwarding proxy server parses the first URL and, upon detecting that the first URL includes identification information of a first CGI for processing the first payment service, selects a target payment server from the N payment servers, based on the identification information of the first CGI, where the first CGI is located, and then sends the first service request to the target payment server for payment processing. When the public forwarding proxy server detects that the first URL does not include the identification information of the first public gateway interface but includes a command identifier corresponding to the first service request, it sends the first service request to the payment proxy server. Based on the command identifier corresponding to the first service request, the payment proxy server determines the identification information of the first public gateway interface and, based on the identification information of the first public gateway interface, selects a target payment server where the first public gateway interface is located from among the N payment servers. Simultaneously, based on the identification information of the first public gateway interface, the payment proxy server modifies the first URL of the first service request to generate a second URL. Finally, the payment proxy server sends the first service request including the second URL to the target payment server for payment processing. It can be seen from this that the embodiment of the present application splits the payment service and distributes the split payment service to N different payment servers for processing. At the same time, the public gateway interface with complex functions (i.e., the first type of public gateway interface) is split, and the split public gateway interface is configured on the payment server with corresponding functions, so that different payment servers are responsible for part of the payment services, and each payment server is related and independent and does not interfere with each other. When the payment logic on one of the payment servers needs to be modified, it will not affect the payment logic on other payment servers, thereby improving the reliability and accuracy of the management, maintenance and modification of the payment service and payment system, facilitating the version update of the payment system, and thus improving the performance and efficiency of payment processing.

[0087] The following introduces the implementation environment of the support processing method provided in the embodiment of the present application.

[0088] Figure 2This is a schematic diagram of an implementation environment involved in an embodiment of the present application, including a terminal device 101, a public forwarding proxy server 102, a payment proxy server 103, and N payment servers 104.

[0089] Among them, the terminal device 101 and the public forwarding proxy server 102 can be connected to each other through wired or wireless communication, the public forwarding proxy server 102 and the payment proxy server 103 can be connected to each other through wired or wireless communication, the public forwarding proxy server 102 and the payment server 104 can be connected to each other through wired or wireless communication, and the payment proxy server 103 and the payment server 104 can be connected to each other through wired or wireless communication.

[0090] The terminal device 101 is provided with a payment client. In one example, the payment client is a separate client. In another example, the payment client is parasitic on another client, for example, the payment client can be a payment module in an instant messaging client.

[0091] The public forwarding proxy server 102 is used to identify the service request sent by the payment client, determine whether the client request is a service request, and when it is a service request, execute the support processing method of the embodiment of the present application to complete the payment processing.

[0092] The payment proxy server 103 is a forwarding layer introduced to ensure compatibility between new and old versions of payment clients. After processing the service requests of the old version of the payment client through the payment proxy server 103, it is forwarded to the new and different payment server 104, realizing an efficient and secure backend payment service splitting and reconstruction technology.

[0093] Each of the N payment servers 104 can process at least one payment service, and different payment servers 104 process different types of payment services.

[0094] In an embodiment of the present application, a subject (e.g., a user) can perform a payment operation on the payment client, such as a payment operation for a first payment service. The payment client generates a service request based on the subject's payment operation. The terminal device 101 sends the service request to the public forwarding proxy server 102. In this embodiment of the present application, the payment processing flow of the public forwarding proxy server 102 differs depending on the difference between the new and old versions of the payment client.

[0095] In some cases, when the payment client is a new version of the payment client, the first URL of the first service request generated by the payment client includes identification information of a first common gateway interface (CGI) used to process the first service request. In this case, the public forwarding proxy server 102 selects a target payment server where the first CGI is located from the N payment servers 104 based on the identification information of the first CGI included in the first URL, and sends the first service request to the target payment server.

[0096] In some cases, when the payment client is an older version of the payment client and the first service request involves interface A, the first URL of the first service request generated by the payment client includes a command identifier corresponding to the first service request but does not include identification information of the first public gateway interface used to process the first service request. The public forwarding proxy server 102 sends the first service request to the payment proxy server 103. The payment proxy server 103 determines the identification information of the first public gateway interface based on the command identifier corresponding to the first service request, and selects the target payment server where the first public gateway interface is located from the N payment servers 104 based on the identification information of the first public gateway interface. At the same time, based on the identification information of the first public gateway interface, the payment proxy server 103 modifies the first URL of the first service request to generate a second URL. Finally, the payment proxy server 103 sends the first service request with the second URL to the target payment server for processing.

[0097] In this way, the target payment processor calls the first public gateway interface in the target payment server based on the received first business request to perform payment processing on the first payment business. The embodiment of the present application splits the payment service and distributes the split payment service to N different payment servers for processing. At the same time, the public gateway interface with complex functions (i.e., the first type of public gateway interface) is split and the split public gateway interface is configured on the payment server with corresponding functions, so that different payment servers are responsible for part of the payment service, and each payment server is independent and does not interfere with each other. When the payment logic on one of the payment servers needs to be modified, it will not affect the payment logic on other payment servers. This can improve the reliability and accuracy of the management, maintenance and modification of the payment service and payment system, facilitate the version update of the payment system, and thus improve the performance and efficiency of payment processing.

[0098] In some embodiments, the server involved in the embodiments of the present application may be one or more servers. When there are multiple servers, there are at least two servers for providing different services, and / or there are at least two servers for providing the same service, such as providing the same service in a load balancing manner, which is not limited in the embodiments of the present application. Among them, the above-mentioned server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. DNS server 101 can also become a node of the blockchain.

[0099] In one example, when the server of the embodiment of the present application is a node in the blockchain system, such as Figure 3 As shown, Figure 3 This is an optional structural diagram of a blockchain system involved in an embodiment of the present application. It consists of multiple nodes (any form of electronic device connected to the network, such as servers and user terminals), forming a peer-to-peer network. The peer-to-peer protocol is an application layer protocol running on top of the Transmission Control Protocol (TCP). In a distributed system, any machine, such as a server or terminal, can join and become a node. Nodes include hardware layers, middle layers, operating system layers, and application layers.

[0100] See also Figure 3 The functions of each node in the blockchain system shown include routing, a basic node function used to support communication between nodes. In addition to routing, nodes can also have application functions. Applications are deployed within the blockchain to implement specific services based on actual business needs. They record data related to these functions, forming log data. This log data carries a digital signature indicating the source of the task data. This log data is then transmitted to other nodes in the blockchain system, which then add it to a temporary block upon successful verification of its source and integrity.

[0101] For example, the services implemented by the application include: wallets, shared ledgers, smart contracts and blockchains. Among them, the wallet is used to provide the function of conducting electronic currency transactions, including initiating transactions (that is, sending the transaction record of the current transaction to other nodes in the blockchain system. After the other nodes successfully verify, as a response to acknowledge the validity of the transaction, the record data of the transaction is stored in a temporary block of the blockchain; of course, the wallet also supports querying the remaining electronic currency in the electronic currency address. The shared ledger is used to provide functions such as storage, query and modification of account data, and sends the record data of the operation on the account data to other nodes in the blockchain system. After the other nodes verify that it is valid, the record data is stored in a temporary block as a response to acknowledge the validity of the account data. Confirmation can also be sent to the node that initiated the operation. Smart Smart contracts are computerized protocols that can execute the terms of a contract. These are implemented through code deployed on a shared ledger and executed when certain conditions are met. Based on actual business needs, the code is used to complete automated transactions, such as querying the logistics status of a buyer's purchased goods and transferring the buyer's electronic currency to the merchant's address after the buyer signs for the goods. Of course, smart contracts are not limited to executing contracts for transactions; they can also execute contracts that process received information. A blockchain consists of a series of blocks that are sequentially generated. Once a new block is added to the blockchain, it cannot be removed. Blockchain records the data submitted by nodes in the blockchain system.

[0102] See also Figure 4 , Figure 4 This is an optional schematic diagram of the block structure provided by the embodiment of the present application. Each block includes the hash value of the transaction record stored in this block (the hash value of this block) and the hash value of the previous block. The blocks are connected by hash values ​​to form a blockchain. In addition, the block can also include information such as the timestamp when the block was generated. Blockchain is essentially a decentralized database, a series of data blocks generated using cryptographic methods. Each data block contains relevant information used to verify the validity of its information (anti-counterfeiting) and generate the next block.

[0103] The present embodiment of the present application does not limit the specific type of terminal device 101. In some embodiments, terminal device 101 may include, but is not limited to, mobile phones, computers, intelligent voice interaction devices, smart home appliances, vehicle-mounted terminals, aircraft, wearable smart devices, medical devices, and the like. Devices are often equipped with a display device, which can be a monitor, display screen, touch screen, and the like. The touch screen can also be a touch screen, touch panel, and the like.

[0104] It should be noted that the implementation environment of the embodiment of the present application includes but is not limited to Figure 2shown.

[0105] The following describes the technical solutions of the embodiments of the present application in detail through some embodiments. The following embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments.

[0106] Figure 5 A flowchart of a payment processing method provided in accordance with an embodiment of the present application.

[0107] like Figure 5 As shown, the payment processing process of the embodiment of the present application includes:

[0108] S101: A terminal device generates a first service request and a first URL of the first service request in response to a payment operation of a first payment service by a subject.

[0109] The payment processing method of the embodiment of the present application can be used in various mobile payment systems or Internet payment systems.

[0110] The payment processing method of the embodiment of the present application can be applied to payment business scenarios such as commercial payment, social payment, user change page, change recharge, change withdrawal, etc. For example, social payment can also include sending red envelopes, transferring money, face-to-face payment, etc.

[0111] In an embodiment of the present application, to improve the management and maintenance of payment services, the payment services of an existing payment server are split and the split payment services are distributed to N different payment servers. For example, the payment services are split according to the functions of the payment services of the existing payment server, and the different payment services after the split are distributed to N different payment servers. In this way, each of the N payment servers only needs to perform part of the payment services provided by it, which can improve the management and maintenance of payment services.

[0112] In one example, Figure 6A As shown on the right, the payment services of commercial payment, social payment, user information, change recharge and change withdrawal in the existing payment server can be split into new separate services. For example, the commercial payment service is assigned to the first payment server, the social payment service is assigned to the second payment server, the user information service is assigned to the third payment server, and the change recharge and change withdrawal services are assigned to the fourth payment server.

[0113] In one example, Figure 6BAs shown on the right, the payment core processes (e.g., including commercial and social payments), user information, transfer payment, change top-up, and change withdrawal services in the existing payment server can be split into new separate services. For example, the user information service can be assigned to the third payment server, the transfer payment service to the fifth payment server, the change top-up and change withdrawal services to the sixth payment server, and the payment core process service to the seventh payment server.

[0114] Depend on Figure 6A and Figure 6B As shown on the left side of the figure, in existing payment solutions, all payment requests from payment clients are processed by a single payment server, which results in unclear payment business management, poor maintainability, and difficulty in achieving Quality of Service (QOS). Furthermore, the large amount of code and libraries piled together results in a very long compilation time, slowing down version iterations and affecting payment processing efficiency. To solve this technical problem, Figure 6A and Figure 6B As shown on the right side of , in an embodiment of the present application, the payment service is split according to the functions of the payment service of the existing payment server, and the split payment service is distributed to N different payment servers for processing, so that different payment servers are responsible for part of the payment services, and each payment server is related and independent without interfering with each other. When the payment logic on one of the payment servers needs to be modified, it will not affect the payment logic on other payment servers, thereby improving the reliability and accuracy of the management, maintenance and modification of the payment service, facilitating the version update of the payment system, and thereby improving the performance and efficiency of payment processing.

[0115] It should be noted that the above Figure 6A and Figure 6B This is an example of splitting payment services. In the embodiment of the present application, different payment services can be split onto different payment servers according to actual needs.

[0116] In an embodiment of the present application, after different payment services are assigned to different payment servers based on the above steps, the CGI interfaces associated with these payment services are also configured on the payment servers corresponding to these payment services. For example, the CGI interfaces associated with commercial payment services are assigned to the first payment server. In this way, when a payment client sends a commercial payment request, it can complete the corresponding processing by calling the relevant CGI interface on the first payment server.

[0117] In some embodiments, at least some of the public gateway interfaces on the N payment servers of the embodiments of the present application are obtained by splitting the first type of public gateway interface, and the first type of public gateway interface includes M payment functions. That is, in the embodiments of the present application, for some public gateway interfaces with complex functions, they are recorded as the first type of public gateway interfaces and split, and the split public gateway interfaces are configured on the corresponding payment servers among the above-mentioned N payment servers. For example, according to the payment function of the first type of public gateway interface, the first type of public gateway interface is split into multiple public gateway interfaces, and these public gateway interfaces are respectively configured on the payment servers with corresponding functions.

[0118] For example, for some relatively complex first-type CGI interfaces, the first-type CGI interface can be split into multiple CGI interfaces with different payment functions based on its M payment functions, where M is greater than 1. Each of the multiple CGI interfaces with different functions is then assigned to a payment server with the corresponding function based on its function.

[0119] For example, a first-type CGI interface has payment function 1 and payment function 2. Thus, the first-type CGI interface can be split into two second CGI interfaces, designated as second CGI interface 1 and second CGI interface 2. Second CGI interface 1 has payment function 1, and second CGI interface 2 has payment function 2. From N payment servers, select payment server 1 that has payment function 1, and configure second CGI interface 1 on payment server 1. Similarly, select payment server 2 that has payment function 2 from N payment servers, and configure second CGI interface 2 on payment server 2.

[0120] In a specific example, the first type of CGI interface may be interface A (e.g., tenpay interface). Interface A is a relatively large CGI interface with multiple functions. Interface A may be split into multiple CGI interfaces based on the functions of interface A. Figure 7As shown, it is assumed that interface A has at least payment function 1 and payment function 2. It is assumed that payment function 1 is wallet card binding information query and payment function 2 is social payment authentication. In an embodiment of the present application, the two payment functions of interface A are split into two different CGI interfaces, for example, interface A1 (such as wallet card binding information query interface (bindquery)) and interface A2 (such as social payment authentication interface (snsauthen)). Then, the two interfaces A1 and A2 are configured on the corresponding payment servers. For example, wallet card binding information query can be understood as one of the user information services, so the interface A1 can be configured on the third payment server. For another example, social payment authentication can be understood as one of the social payment services, so the interface A2 can be configured on the second payment server.

[0121] In an embodiment of the present application, based on the above method, the payment services of an existing payment server are split and the split payment services are distributed to N different payment servers. At the same time, the first type of public gateway interface with complex functions, such as the tenpay interface, is split and the split public gateway interface is configured on the payment server with the corresponding function. On this basis, the payment processing method of the embodiment of the present application can improve the reliability and accuracy of the management, maintenance and modification of the payment service, facilitate the version update of the payment system, and thus improve the performance and efficiency of payment processing.

[0122] In some embodiments, in order to improve the detection of the split public gateway interface, a command indicator (Command Promp, abbreviated as CMD) is set for each split public gateway interface to realize the detection of various dimensions of the public gateway interface, facilitate more rapid location of problems, and complete unified and complete detection of the interface.

[0123] In some embodiments, after the public gateway interface is split, the embodiment of the present application needs to grayscale control the traffic routed to the old version of the payment server and the new payment server after the split according to the object identifier (uin) and percentage, so as to gradually expand the scope of use of the payment system proposed in the embodiment of the present application. In this process, the above interface division can also be improved based on object feedback, such as re-dividing the interface to further improve payment reliability.

[0124] In the embodiment of the present application, a payment client is installed on the terminal device, and the object triggers the payment client to enter the payment interface. The payment interface includes multiple types of payment services. The object can perform a payment operation on one of these multiple types of payment services according to actual needs. For the sake of description, this payment service is recorded as the first payment service.

[0125] In one example, Figure 8 As shown on the left, the payment client is a separate client installed on the terminal device. The object triggers the icon of the payment client on the terminal device to open the payment client and display Figure 8 The payment interface on the right includes multiple types of payment services, and the object can choose to operate a first payment service.

[0126] In one example, some instant messaging software integrates a payment function, so the client of the instant messaging software can be understood as the payment client of the embodiment of the present application. Figure 9 As shown on the left, the object triggers the client of the instant messaging software installed on the terminal device to display Figure 9 In the communication interface shown on the right, the object can find the first payment service and perform operations by triggering relevant options in the communication interface.

[0127] For example, assuming that the first payment service is sending a red envelope, Figure 9 As shown on the right, the object triggers the target contact in the communication list, such as Xiao Shuai Shuai, to enter the chat interface, which includes a chat display area and a chat options area. The chat options area includes payment options such as red envelopes and transfers.

[0128] For example, when the subject triggers the red envelope option, a red envelope interface is displayed, in which the subject can enter the red envelope amount and trigger the "insert red envelope" option. In response to the subject's triggering operation on the "insert red envelope" option, the terminal device can generate a first service request.

[0129] For example, when the subject triggers the transfer option, a transfer interface is displayed, in which the subject can enter the transfer amount and trigger the transfer option. In response to the subject's triggering operation on the transfer option, the terminal device can generate a first service request.

[0130] For example, when the subject scans the other party's payment code, a payment interface is displayed, in which the subject can enter the payment amount and trigger the payment option. In response to the subject's triggering operation on the transfer option, the terminal device can generate a first service request.

[0131] In some embodiments, the subject may also enter a change interface, which includes recharge and withdrawal options. Exemplarily, when the subject triggers the recharge option, the recharge interface is displayed, and the subject can enter the recharge amount in the recharge interface and trigger the confirmation option. In response to the subject's triggering operation on the recharge confirmation option, the terminal device may generate a first business request. Exemplarily, when the subject triggers the withdrawal option, the withdrawal interface is displayed, and the subject can enter the withdrawal amount in the withdrawal interface and trigger the confirmation option. In response to the subject's triggering operation on the withdrawal confirmation option, the terminal device may generate a first business request.

[0132] As can be seen from the above, in the embodiment of the present application, when an object performs a payment operation on the first payment service, a first service request and a URL of the first service request may be generated. For ease of description, the URL is referred to as the first URL. This allows the client to send the first service request to the corresponding payment server for processing based on the URL of the first service request.

[0133] The specific process of generating the first URL of the first service request is introduced below.

[0134] In the embodiment of the present application, when the versions of the payment client are different, the first URL of the generated first service request may be different. Based on this, the above S101 includes the following steps S101-A and S101-B:

[0135] S101-A. In response to a payment operation of a first payment service by an object, obtaining version information of a payment client;

[0136] S101-B. Generate a first URL for the first service request based on the version information of the payment client.

[0137] In some cases, the client may not have updated the payment client version in a timely manner, and the payment client installed on the terminal device may still be an old version of the payment client. The data processing logic of the new and old versions of the payment client may differ, resulting in a different first URL for the generated first service request. Based on this, when generating the first URL for the first service request, the terminal device first obtains the version information of the payment client installed on the terminal device, and then generates the first URL for the first service request based on the version information of the payment client.

[0138] The embodiment of the present application does not limit the specific method of generating the first URL of the first service request based on the version information of the payment client.

[0139] In one possible implementation, when the version of the payment client is the first version (i.e., the latest version), or the version of the payment client is not the first version, and the first service request is not a first-type service request, then the above S101-B includes the following steps S101-B11 and S101-B12:

[0140] S101-B11. The terminal device obtains identification information of a first common gateway interface for processing a first service request;

[0141] S101-B12. Generate a first URL for the first service request based on the identification information of the first public gateway interface, where the first URL for the first service request includes the identification information of the first public gateway interface.

[0142] As can be seen from the above, in the embodiments of the present application, different payment services are assigned to different payment servers for processing. Thus, for each payment server, the payment server includes a common gateway interface (CGI) for processing corresponding service requests. For example, payment server 1 is configured to process service request 1 and service request 2. When processing service request 1, payment server 1 invokes CGI 1 for processing, and when processing service request 2, it invokes CGI 2 for processing.

[0143] In the embodiment of the present application, the new version of the payment client saves the correspondence between each business request and different public gateway interfaces.

[0144] For example, the correspondence between different service requests and different public gateway interfaces is shown in Table 1 below:

[0145] Table 1

[0146]

[0147] In this way, the terminal device can find the identification information of the first public gateway interface used to process the first business request based on the corresponding relationship shown in Table 1 above. Assuming that the first business request is business request 1, the corresponding identification information of the first public gateway interface is public gateway interface 1. The embodiment of the present application does not limit the specific form of the identification information of the business request. For example, it can be the name of the business request, or the index of the business request, etc., which can uniquely identify the payment business. At the same time, the embodiment of the present application does not limit the specific form of the identification information of the public gateway interface. For example, it can be the name of the public gateway interface, or the index of the public gateway interface, etc., which can uniquely identify the public gateway interface.

[0148] In an embodiment of the present application, for a first version (i.e., new version) of a payment client, for a first type of public gateway interface, such as interface A, the payment client stores the public gateway interface information after the interface A is split. As shown above, assuming that interface A is split into interface A1 and interface A2, the first version of the payment client stores the correspondence between the wallet card binding information query request and interface A1, as well as the correspondence between the social payment authentication request and interface A2.

[0149] In one example, under the first version of the payment client, when a user sends a red envelope and enters a payment password to make a payment, the terminal device generates a first service request in response to the user's password entry. This first service request is a social payment authentication request. Based on the correspondence between the social payment authentication request and interface A2 stored in the first version of the payment client, the terminal device generates the first URL for the first service request as follows: file1 / interfaceA / interfaceA2, where A2 is the identification information of the first common gateway interface used to process the social payment authentication request (here, the interface name is used to represent the interface identification information).

[0150] In one example, under the first version of the payment client, when a user accesses their wallet to view their WeChat Pay change, the terminal device generates a first service request in response to the viewing operation. This first service request is a wallet card binding information query request. Based on the correspondence between the wallet card binding information query request and interface A1 stored in the first version of the payment client, the terminal device generates the first URL of the first service request as follows: file1 / interfaceA / interfaceA1, where A1 is the identification information of the first common gateway interface used to process the wallet card binding information query request (here, the interface name is used to represent the interface identification information).

[0151] It should be noted that the old version of the payment client includes a correspondence between non-first-type service requests and the common gateway interface. Therefore, when the version of the payment client is not the first version and the first service request is not a first-type service request, for example, it is not a wallet card binding information query request or a wallet card binding information query request, the first URL of the first service request can also be generated using this method.

[0152] The above describes the process of generating the first URL of the first service request when the payment client is the first version (ie the latest version) or the version of the payment client is not the first version and the first service request is not a first type service request.

[0153] In one possible case, when the payment client is not the first version (i.e., not the latest version) and the first service request is a first type service request, the above S101-B includes the following steps S101-B21 and S101-B22:

[0154] S101-B21. The terminal device obtains a naming identifier corresponding to the first service request;

[0155] S101-B22. Generate a first URL for the first service request based on the naming identifier corresponding to the first service request, where the first URL includes the naming identifier corresponding to the first service request.

[0156] In an embodiment of the present application, when the version of the payment client is not the first version but an old version, and the first business request is a first type business request, the terminal device generates a first URL for the first business request based on the URL generation logic stored on the old version of the payment client. For example, when the first business request is a wallet card binding information query request and a social payment authentication request, the routing logic stored on the old version of the payment client is to route according to the command identifier (cgicmd) of interface A (such as the tenpay interface). Based on this, when the terminal device generates the first UR for the first business request, it first obtains the naming identifier corresponding to the first business request.

[0157] For example, for a wallet card binding information query request, the value of the named identifier is a first value, and for a social payment authentication request, the value of the named identifier is a second value. The first value and the second value have different values, and the embodiments of this application do not limit the specific values ​​of the first value and the second value. For example, the first value is 1 and the second value is 0. Alternatively, the first value is 0 and the second value is 1.

[0158] In this way, when the first business request is a wallet card binding information query request or a social payment authentication request, and the payment client is not the first version, the terminal device obtains the naming identifier corresponding to the first business request, and generates the first URL of the first business request based on the naming identifier corresponding to the first business request.

[0159] For example, assuming the payment client version is not the first version, that is, an older version, and assuming the first service request is a wallet card binding information query request, the terminal device obtains a named identifier corresponding to the wallet card binding information query request, such as cmd ID=1. Thus, when the terminal device generates the first URL for the wallet card binding information query request, it includes cmd ID=1 in the first URL. For example, the first URL for the wallet card binding information query request can be represented as: file1 / interfaceA, where interfaceA's cmd ID=1. For example, assuming the first service request is a social payment authentication request, the terminal device obtains a named identifier corresponding to the social payment authentication request, such as cmd ID=0. Thus, when the terminal device generates the first URL for the social payment authentication request, it includes cmd ID=0 in the first URL. For example, the first URL for the social payment authentication request can be represented as: file1 / interfaceA, where interfaceA's cmd ID=0.

[0160] The above describes the process of generating the first URL for the first service request when the payment client is not the first version of the payment client.

[0161] In the embodiment of the present application, after the terminal device generates the first service request and the first URL of the first service request based on the above steps, it executes the following step S102.

[0162] S102: The terminal device sends a first service request to a public forwarding proxy server.

[0163] In an embodiment of the present application, the terminal device is communicatively connected to the public forwarding proxy server, and the terminal device can send the first service request generated above and the URL of the first service request to the public forwarding proxy server.

[0164] S103. When the first URL of the first business request includes identification information of a first public gateway interface for processing the first business request, the public forwarding proxy server selects a target payment server where the first public gateway interface is located from the N payment servers based on the identification information of the first public gateway interface.

[0165] Among them, N payment servers are used to support different payment services, and at least part of the public gateway interfaces configured on the N payment servers are obtained by splitting the first type of public gateway interface, N is a positive integer, and M is a positive integer greater than 1.

[0166] As can be seen from the above, in the embodiment of the present application, the first URL of the first service request generated by the terminal device includes two situations:

[0167] Case 1: When the payment client installed on the terminal device is a payment client of the first version (i.e., the latest version), or the payment client is a payment client of the first version, and the first business request is not a first-type business request, for example, it is not a wallet card binding information query request or a social payment authentication request, the generated first URL includes the identification information of the first public gateway interface corresponding to the first business request.

[0168] Case 2: When the payment client installed on the terminal device is not the first version (i.e., the old version) of the payment client, and the first business request is a first type of business request (for example, a wallet card binding information query request and a social payment authentication request), the generated first URL includes the command identifier corresponding to the first business request, and does not include the identification information of the first public gateway interface.

[0169] Based on this, upon receiving the first service request sent by the terminal device, the public forwarding proxy server parses the first URL of the first service request. If the first URL contains identification information of a first public gateway interface for processing the first service request, the public forwarding proxy server selects a target payment server where the first public gateway interface is located from the N payment servers based on the identification information of the first public gateway interface.

[0170] The embodiment of the present application does not limit the specific manner in which the public forwarding proxy server selects the target payment server where the first public gateway interface is located from N payment servers based on the identification information of the first public gateway interface.

[0171] In one possible implementation, the public forwarding proxy server stores identification information of the public gateway interface configured on each of the N payment servers. In this case, the public forwarding proxy server can determine the target server where the first public gateway interface is located based on the identification information of the first public gateway interface and the public gateway interface configured on each of the N payment servers stored in the public forwarding proxy server.

[0172] For example, the identification information of the common gateway interface configured on each of the N payment servers is shown in Table 2:

[0173] Table 2

[0174]

[0175] As can be seen from Table 2 above, payment server 1 among the N payment servers is configured with several public gateway interfaces, such as public gateway interface a1 and public gateway interface a2. Payment server 2 is configured with several public gateway interfaces, such as public gateway interface b1 and public gateway interface b2. It should be noted that Table 2 above is merely an example, and embodiments of the present application are not limited thereto. For example, in some embodiments, one public gateway interface may be configured on each payment server.

[0176] In this way, the public forwarding proxy server parses the first URL of the first service request and obtains the identification information of the first public gateway interface corresponding to the first service request. Then, based on the identification information of the first public gateway interface, the public forwarding proxy server queries Table 2 to obtain the target server where the first public gateway interface is located. For example, assuming that the identification information of the first public gateway interface is a1, i.e., the first public gateway interface is public gateway interface a1, as shown in Table 2. Public gateway interface a1 is configured on payment server 1, and therefore payment server 1 is determined as the target server where the first public gateway interface is located.

[0177] In one possible implementation, the public forwarding proxy server transmits the identification information of the first public gateway interface to other data processing servers, which store the corresponding relationships shown in Table 2. In this way, the data processing server can, based on the identification information of the first public gateway interface, search the corresponding relationships shown in Table 2 to find the identification information of the target payment server where the first public gateway interface is located. The data processing server then transmits the retrieved identification information of the target payment server where the first public gateway interface is located to the public forwarding proxy server. Based on the identification information of the target payment server, the public forwarding proxy server determines the target server where the first public gateway interface is located from among N payment servers.

[0178] For example, assuming the first public gateway interface is interface A1, which is configured on a third payment server, the third payment server can be determined as the target server for the first public gateway interface. Assuming the first public gateway interface is interface A2, which is configured on a second payment server, the second payment server can be determined as the target server for the first public gateway interface.

[0179] In the embodiment of the present application, the public forwarding proxy server selects the target payment server where the first public gateway interface corresponding to the first service request is located from the N payment servers based on the above steps, and then performs the following step S104.

[0180] S104: The public forwarding proxy server sends the first service request to the target payment server.

[0181] In this embodiment, when the first URL of the first business request includes the identification information of the first public gateway interface, the public forwarding proxy server can directly select the target payment server where the first public gateway interface is located from the N payment servers based on the identification information of the first public gateway interface, and then send the first business request directly to the target payment server for processing.

[0182] S105: The target payment server calls the first public gateway interface in the target payment server based on the identification port information of the first public gateway interface to process the first service request.

[0183] The target payment server of the embodiment of the present application is configured with a first public gateway interface for processing the first service request among the N payment servers. Optionally, in addition to the first public gateway interface, the target payment server may be configured with other public gateway interfaces.

[0184] Based on this, when the target payment server receives the first service request, it searches for the first public gateway interface from the public gateway interfaces configured on the target payment server based on the first public gateway interface identification information included in the first URL of the first service request. It then calls the first public gateway interface to process the first service request.

[0185] As can be seen from the above, in the embodiment of the present application, by splitting the payment service, the split payment service is distributed to N different payment servers for processing, and at the same time, the public gateway interface with complex functions (i.e., the first type of public gateway interface) is split, and the split public gateway interface is configured on the payment server with corresponding functions. In this way, each payment server is independent and does not interfere with each other. When the payment logic and other information on one of the payment servers are modified, it will not affect the payment logic on other payment servers. In actual use, the terminal device sends the first business request to the public forwarding proxy server, and the public forwarding proxy server selects the corresponding target payer from the N payment servers based on the identification information of the first public gateway interface corresponding to the first business request to process the first business request. When there are multiple business requests, different payment servers can be selected for processing based on the first public gateway interface corresponding to the business request, which can improve the processing efficiency of the payment. At the same time, when upgrading or modifying some payment services, it is only necessary to upgrade or modify the CGI interface on the payment server where these payment services are located, which will not affect the execution of other payment services, thereby improving the reliability and accuracy of the management, maintenance and modification of payment services and payment systems, facilitating version updates of payment systems, and thus improving payment performance and efficiency.

[0186] In some embodiments, after the target payment server calls the first public gateway interface to process the first service request, it can also send the processing result of the first payment service to the public forwarding proxy server. Then, the public forwarding proxy server sends the processing result to the terminal device.

[0187] The following takes the first service request being a wallet card binding information query request or a social payment authentication request as an example to further illustrate the method of the embodiment of the present application.

[0188] In one example, it is assumed that the version of the payment client is the first version (ie the latest version), and the first service request is a wallet card binding information query request. Figure 10 As shown, the payment processing method of the embodiment of the present application includes the following steps:

[0189] Step 11: The terminal device generates a wallet-binding card information query request and a first URL of the wallet-binding card information query request.

[0190] For example, Figure 10 As shown, the first URL of the wallet card binding information query request is: file1 / interfaceA / interfaceA1.

[0191] Step 12: The terminal device sends the wallet card binding information query request to the public forwarding proxy server.

[0192] Step 13: The public forwarding proxy server parses the first URL of the wallet card binding information query request, obtains the identification information A1 of the first public gateway interface, and selects the third payment server as the target payment server from the N payment servers based on the identification information A1 of the first public gateway interface.

[0193] Step 14: The public forwarding proxy server sends the wallet card binding information query request to the third payment server.

[0194] Step 15: The third payment server processes the wallet card binding information query request.

[0195] In an embodiment of the present application, the wallet card binding information query service is configured as a separate service on the third payment server, so that the wallet card binding information query request can be processed by calling interface A1 on the third payment server.

[0196] In one example, it is assumed that the version of the payment client is the first version (ie the latest version), and the first service request is a social payment authentication request. Figure 10 As shown, the payment processing method of the embodiment of the present application includes the following steps:

[0197] Step 21: The terminal device generates a social payment authentication request and a first URL of the social payment authentication request.

[0198] For example, Figure 10 As shown, the first URL for social payment authentication is: file1 / interfaceA / interfaceA2.

[0199] Step 22: The terminal device sends the social payment authentication request to the public forwarding proxy server.

[0200] Step 23: The public forwarding proxy server parses the first URL of the social payment authentication request, obtains the identification information A2 of the first public gateway interface, and selects the second payment server as the target payment server from the N payment servers based on the identification information A2 of the first public gateway interface.

[0201] Step 24: The public forwarding proxy server sends the first service request to the second payment server.

[0202] Step 25: The second payment server processes the social payment authentication request.

[0203] In an embodiment of the present application, the social payment authentication service is configured as a separate service on the second payment server, so that the processing of the social payment authentication request can be completed by calling interface A2 on the second payment server.

[0204] above Figure 10 The left side shows the existing payment processing method, which processes the wallet card binding information query request and the social payment authentication request. That is, the URLs generated by the terminal device for the wallet card binding information query request and the social payment authentication request are the same, both of which are file 1 / interface A. The payment server calls different Handles for processing based on the value of cmdID of interface A in the URL, and the processing logic is complex. In the embodiment of this application, Figure 10 As shown on the right, the wallet card binding information query service and the social payment authentication service are split into two different services and deployed on the payment servers with corresponding functions. In this way, wallet card binding information query requests and social payment authentication requests can be processed by calling different payment servers, facilitating business management and maintenance.

[0205] The payment processing method provided in an embodiment of the present application splits payment services, assigning different payment services to N different payment servers for processing. Public gateway interfaces (CGIs) with complex payment functions are also split, and the split CGIs are configured on payment servers with corresponding functions. That is, the N payment servers in the embodiment of the present application are used to support different payment services, and at least some of the CGIs configured on the N payment servers are split CGIs of the first type. Thus, during actual payment processing, a terminal device generates a first service request and a first URL for the first service request in response to a payment operation performed by an object on a first payment service. The terminal device then sends the first service request to a public forwarding proxy server. The public forwarding proxy server parses the first URL and, upon detecting that the first URL includes identification information of a first CGI for processing the first payment service, selects a target payment server from the N payment servers, based on the identification information of the first CGI, where the first CGI is located, and then sends the first service request to the target payment server for payment processing. It can be seen from this that the embodiment of the present application splits the payment service and distributes the split payment service to N different payment servers for processing. At the same time, the public gateway interface with complex functions (i.e., the first type of public gateway interface) is split, and the split public gateway interface is configured on the payment server with corresponding functions, so that different payment servers are responsible for part of the payment services, and each payment server is related and independent and does not interfere with each other. When the payment logic on one of the payment servers needs to be modified, it will not affect the payment logic on other payment servers, thereby improving the reliability and accuracy of the management, maintenance and modification of the payment service and payment system, facilitating the version update of the payment system, and thus improving the performance and efficiency of payment processing.

[0206] The above describes the payment processing process when the first URL of the first service request includes the identification information of the first public gateway interface for processing the first service request. Figure 11 , when the first URL includes the command identifier corresponding to the first business request and does not include the identification information of the first public gateway interface, the payment processing method provided in the embodiment of the present application is introduced.

[0207] Figure 11 A flowchart of a payment processing method provided in accordance with an embodiment of the present application.

[0208] like Figure 11 As shown, the payment processing method of the embodiment of the present application includes the following steps:

[0209] S201. The terminal device generates a first service request and a first URL of the first service request in response to a payment operation of a first payment service by an object.

[0210] The specific implementation process of the above S201 can refer to the specific description of the above S101, which will not be repeated here.

[0211] S202: The terminal device sends a first service request to a public forwarding proxy server.

[0212] In an embodiment of the present application, the terminal device is in communication with the public forwarding proxy server. The terminal device can send the first service request generated above and the URL of the first service request to the public forwarding proxy server, and the public forwarding proxy server performs the following step S203.

[0213] S203: When the first URL includes the command identifier corresponding to the first service request but does not include the identification information of the first common gateway interface, the public forwarding proxy server sends the first service request to the payment proxy server.

[0214] As can be seen from the above, in the embodiment of the present application, the first URL of the first service request generated by the terminal device includes two situations:

[0215] Case 1: When the payment client installed on the terminal device is a payment client of the first version (i.e., the latest version), or the payment client is a payment client of the first version, and the first business request is not a first-type business request, for example, it is not a wallet card binding information query request or a social payment authentication request, the generated first URL includes the identification information of the first public gateway interface corresponding to the first business request.

[0216] Case 2: When the payment client installed on the terminal device is not the first version (i.e., the old version) of the payment client, and the first business request is a first type of business request (for example, a wallet card binding information query request and a social payment authentication request), the generated first URL includes the command identifier corresponding to the first business request, and does not include the identification information of the first public gateway interface.

[0217] Based on this, after receiving the first service request sent by the terminal device, the public forwarding proxy server parses the first URL of the first service request. If it is detected that the first URL includes the command identifier corresponding to the first service request but does not include the identification information of the first public gateway interface, the public forwarding proxy server sends the first service request to the payment proxy server.

[0218] In the embodiments of this application, Figure 12As shown, the payment proxy server can be understood as an intermediate forwarding component, which is set up to take into account the old version of the payment client. As the version is updated, when all payment clients are the new version of the payment client, the payment proxy server can be cancelled.

[0219] S204: The payment proxy server determines identification information of the first common gateway interface based on the command identifier corresponding to the first service request.

[0220] In an embodiment of the present application, when the payment client installed on the terminal device is not the first version of the payment client, and the first business request is a first type of business request, the first URL of the first business request generated by the terminal device includes a command identifier corresponding to the first business request.

[0221] For example, when the version of the payment client is not the first version and the first service request is a wallet card binding information query request, the first URL of the wallet card binding information query request generated by the terminal device can be expressed as: file 1 / interface A, where cmd ID of interface A = 1.

[0222] For another example, when the version of the payment client is not the first version and the first service request is a social payment authentication request, the first URL of the social payment authentication request generated by the terminal device can be expressed as: file 1 / interface A, where the cmd ID of interface A = 0.

[0223] In this way, when the payment proxy server receives the first business request sent by the public forwarding proxy server, it parses the first URL of the first business request, obtains the command identifier corresponding to the first business request included in the first URL, and then determines the identification information of the first public gateway interface based on the command identifier corresponding to the first business request.

[0224] The embodiment of the present application does not limit the specific method of determining the identification information of the first common gateway interface based on the command identifier corresponding to the first service request.

[0225] In a possible implementation, the payment proxy server stores the correspondence between different service requests and different command identifiers, as well as the correspondence between different service requests and different public gateway interfaces. In this case, the above S204 includes the following steps:

[0226] S204-A. The payment proxy server determines identification information of the first service request based on the command identifier corresponding to the first service request and from the correspondence between different service requests and different command identifiers.

[0227] S204-B: The payment proxy server queries and obtains the identification information of the first public gateway interface based on the identification information of the first service request in the correspondence between different service requests and different public gateway interfaces.

[0228] In this implementation, the payment proxy server stores the correspondence between different service requests and different command identifiers, as well as the correspondence between different service requests and different public gateway interfaces.

[0229] Exemplarily, the correspondence between different service requests and different public gateway interfaces is shown in Table 3:

[0230] Table 3

[0231] Business request identification information Identification information of the command identifier Business request d1 Command identifier e1 Business request d2 Command identifier e2 …… ……

[0232] In this way, the payment proxy server can obtain the identification information of the first service request from Table 3 based on the command identifier corresponding to the first service request. For example, when the command identifier corresponding to the first service request is e1, the identification information of the first service request can be determined to be d1.

[0233] In one example, when the service request is a wallet card binding information query request, the corresponding cmd ID of interface A is 1. Thus, when the cmd ID (i.e., naming identifier) ​​in the first URL of the first service request is 1, it indicates that the first service request is a wallet card binding information query request.

[0234] In one example, when the service request is a social payment authentication request, the cmd ID of the corresponding interface A is 0. Thus, when the cmd ID (i.e., the naming identifier) ​​in the first URL of the first service request is 0, it indicates that the first service request is a social payment authentication request.

[0235] The payment proxy server determines the identification information of the first business request from the correspondence between different business requests and different command identifiers based on the command identifier corresponding to the first business request, and then executes the above-mentioned step S204-B. The payment proxy server obtains the identification information of the first public gateway interface from the correspondence between different business requests and different public gateway interfaces based on the identification information of the first business request.

[0236] In one example, the correspondence between different service requests and different public gateway interfaces is shown in Table 4:

[0237] Table 4

[0238] Business request identification information Public gateway interface identification information Business request d1 Public Gateway Interface g1 Business request d2 Public Gateway Interface g2 …… ……

[0239] In this way, the payment proxy server can obtain the identification information of the first public gateway interface corresponding to the first service request from Table 4 based on the identification information of the first service request. For example, if the first service request is service request d2, then by searching Table 4, the public gateway interface g2 corresponding to the first service request can be obtained, and the first public gateway interface corresponding to the first service request can be determined to be public gateway interface g2.

[0240] In one possible implementation, the correspondence between the different service requests and different command identifiers, as well as the correspondence between different service requests and different public gateway interfaces, is stored on another data processing server. Thus, after receiving the first service request, the payment proxy server sends the first service request to the data processing server. Based on the command identifier corresponding to the first service request, the data processing server determines the identification information of the first service request from the stored correspondence between different service requests and different command identifiers, as shown in Table 3. Next, the data processing server retrieves the identification information of the first public gateway interface from the stored correspondence between different service requests and different public gateway interfaces, as shown in Table 4.

[0241] For example, assuming that the cmd ID (i.e., naming identifier) ​​in the first URL of the first service request is 1, the first service request is determined to be a wallet card binding information query request. As can be seen from the above, the first public gateway interface corresponding to the wallet card binding information query request is interface A1. Assuming that the cmd ID (i.e., naming identifier) ​​in the first URL of the first service request is 0, the first service request is determined to be a social payment authentication request. As can be seen from the above, the first public gateway interface corresponding to the social payment authentication request is interface A2.

[0242] S205: The payment proxy server selects a target payment server where the first public gateway interface is located from the N payment servers based on the identification information of the first public gateway interface.

[0243] Based on the above steps, after the payment server determines the identification information of the first public gateway interface corresponding to the first service request, it selects a target payment server where the first public gateway interface is located from the N payment servers based on the identification information of the first public gateway interface.

[0244] For example, the payment server stores identification information of the public gateway interface configured on each of the N payment servers. Thus, based on the identification information of the first public gateway interface determined above, the payment server can determine the target server where the first public gateway interface is located from the identification information of the public gateway interface configured on each of the N payment servers stored by the payment server.

[0245] For example, assuming the first public gateway interface is interface A1, which is configured on a third payment server, the third payment server can be determined as the target server for the first public gateway interface. Assuming the first public gateway interface is interface A2, which is configured on a second payment server, the second payment server can be determined as the target server for the first public gateway interface.

[0246] S206: The payment server modifies the first URL of the first service request based on the identification information of the first common gateway interface to obtain a second URL of the first service request.

[0247] It should be noted that there is no order of precedence between the above S205 and the above S206 in the specific execution process, that is, the above S206 can be executed after the above S205, or before the above S205, or synchronously with the above S205, and the embodiment of the present application does not limit this.

[0248] In the embodiment of the present application, since the first URL of the first business request includes the identification information of the first public gateway interface corresponding to the first business request, in order to enable the target payment server to quickly and accurately call the first public gateway interface corresponding to the first business request to process the first business request, the payment server in the embodiment of the present application, after determining the identification information of the first public gateway interface corresponding to the first business request based on the above steps, modifies the first URL of the first business request to obtain the second URL of the first business request, so that the second URL includes the identification information of the first public gateway interface corresponding to the first business request. In this way, the target payment server can directly call the first public gateway interface to process the first business request based on the identification information of the first public gateway interface corresponding to the first business request in the second URL, thereby improving the processing speed of the first business request.

[0249] The embodiment of the present application does not limit the specific manner in which the payment server modifies the first URL of the first service request based on the identification information of the first public gateway interface to obtain the second URL of the first service request.

[0250] In a possible implementation, the payment server may replace some parameters in the first URL with identification information of the first common gateway interface to obtain the second URL of the first service request.

[0251] In a possible implementation, the payment server directly adds the identification information of the first common gateway interface to the first URL of the first service request to obtain the second URL of the first service request.

[0252] For example, the first public gateway interface is interface A1, the identification information of interface A1 is A1, the first URL of the wallet card binding information query request is: file 1 / interface A, and then A1 is added to the first URL, and the second URL of the wallet card binding information query request is: file 1 / interface A / interface A1.

[0253] For another example, the first public gateway interface is interface A2, the identification information of interface A2 is A2, the first URL of the social payment authentication request is: file 1 / interface A, and then A2 is added to the first URL, and the second URL of the social payment authentication request is: file 1 / interface A / interface A2.

[0254] S207: The payment server sends the first service request including the second URL to the target payment server.

[0255] S208: The target payment server calls the first public gateway interface in the target payment server based on the identification port information of the first public gateway interface to process the first service request.

[0256] In this embodiment of the present application, the second URL includes the identification information of the first public gateway interface. Thus, when the target payment server receives the first service request, it queries the first public gateway interface from the public gateway interfaces configured on the target payment server based on the identification information of the first public gateway interface included in the second URL of the first service request. It then calls the first public gateway interface to process the first service request.

[0257] As can be seen from the above, in the embodiment of the present application, by splitting the payment service, the split payment service is distributed to N different payment servers for processing, and at the same time, the public gateway interface with complex functions (i.e., the first type of public gateway interface) is split, and the split public gateway interface is configured on the payment server with the corresponding function. In this way, the payment servers are independent and do not interfere with each other. When the payment logic and other information on one payment server are modified, it will not affect the payment logic on other payment servers. In actual use, the terminal device sends a first service request to the public forwarding proxy server, and the public forwarding proxy server sends the first service request to the payment proxy server. The payment proxy server determines the identification information of the first public gateway interface corresponding to the first service request, and adds the identification information of the first public gateway interface to the first URL of the first service request to obtain a second URL. At the same time, the payment proxy server selects the corresponding target payer from the N payment servers based on the identification information of the first public gateway interface corresponding to the first service request to process the first service request. When there are multiple service requests, different payment servers can be selected for processing based on the first public gateway interface corresponding to the service request, which can improve the processing efficiency of the payment. At the same time, when upgrading or modifying some payment services, it is only necessary to upgrade or modify the CGI interface on the payment server where these payment services are located, which will not affect the execution of other payment services, thereby improving the reliability and accuracy of the management, maintenance and modification of payment services and payment systems, facilitating version updates of payment systems, and thus improving payment performance and efficiency.

[0258] In some embodiments, after the target payment server calls the first public gateway interface to process the first service request, it may also send the processing result of the first payment service to the payment proxy server, which then sends the processing result to the public forwarding proxy server. The public forwarding proxy server then sends the processing result to the terminal device.

[0259] The following takes the first service request being a wallet card binding information query request or a social payment authentication request as an example to further illustrate the method of the embodiment of the present application.

[0260] In one example, it is assumed that the version of the payment client is not the first version (ie, not the latest version), and the first service request is a wallet card binding information query request. Figure 13 As shown on the right, the payment processing method of the embodiment of the present application includes the following steps:

[0261] Step A1: The terminal device generates a wallet-binding card information query request and a first URL of the wallet-binding card information query request.

[0262] For example, Figure 13 As shown on the right, the first URL of the wallet card binding information query request is: file 1 / interface A, where cmdID of interface A = 1.

[0263] Step A2: The terminal device sends the wallet card binding information query request to the public forwarding proxy server.

[0264] Step A3: The public forwarding proxy server sends the wallet card binding information query request to the payment proxy server.

[0265] The public forwarding proxy server parses the first URL of the wallet card binding information query request, and when obtaining that the first URL of the wallet card binding information query request includes cmdID=1 of interface A, it sends the wallet card binding information query request to the payment proxy server.

[0266] Step A4: The payment proxy server uses the command identifier corresponding to the wallet card binding information query request to determine the identification information of interface A1.

[0267] Among them, the first public gateway interface corresponding to the wallet card binding information query request is interface A1, and then based on the correspondence between different business requests and different command identifiers, and the correspondence between different business requests and different public gateway interfaces, the identification information of interface A1 is determined.

[0268] Step A5: The payment proxy server selects a third payment server where the interface A1 is located from the N payment servers based on the identification information of the interface A1.

[0269] For example, based on the identification information A1 of the first common gateway interface, a third payment server is selected as the target payment server from the N payment servers.

[0270] Step A6: Based on A1, the payment proxy server modifies the first URL of the wallet card binding information query request to obtain the second URL of the wallet card binding information query request.

[0271] For example, the identification information of interface A1 is A1, and the first URL of the wallet card binding information query request is: file 1 / interface A. Then, A1 is added to the first URL, and the second URL of the wallet card binding information query request is: file 1 / interface A / interface A1.

[0272] Step A7: The payment proxy server sends a wallet card binding information query request including the second URL to the third payment server.

[0273] Step A8: The third payment server processes the wallet card binding information query request.

[0274] In an embodiment of the present application, the wallet card binding information query service is configured as a separate service on the third payment server, so that the wallet card binding information query request can be processed by calling interface A1 on the third payment server.

[0275] In one example, it is assumed that the version of the payment client is not the first version (ie, not the latest version), and the first service request is a social payment authentication request. Figure 13 As shown on the right, the payment processing method of the embodiment of the present application includes the following steps:

[0276] Step B1: The terminal device generates a social payment authentication request and a first URL of the social payment authentication request.

[0277] For example, Figure 13 As shown on the right, the first URL of the social payment authentication request is: file 1 / interface A, where cmdID of interface A = 1.

[0278] Step B2: The terminal device sends the social payment authentication request to the public forwarding proxy server.

[0279] Step B3: The public forwarding proxy server sends the social payment authentication request to the payment proxy server.

[0280] The public forwarding proxy server parses the first URL of the social payment authentication request, and when obtaining that the first URL of the social payment authentication request includes cmdID=0 of interface A, the public forwarding proxy server sends the social payment authentication request to the payment proxy server.

[0281] Step B4: The payment proxy server uses the command identifier corresponding to the social payment authentication request to determine the identification information of interface A2.

[0282] Among them, the first public gateway interface corresponding to the social payment authentication request is interface A2, and then based on the correspondence between different business requests and different command identifiers, and the correspondence between different business requests and different public gateway interfaces, the identification information of interface A2 is determined.

[0283] Step B5: The payment proxy server selects a second payment server where interface A2 is located from the N payment servers based on the identification information of interface A2.

[0284] For example, based on the identification information A2 of the first common gateway interface, a second payment server is selected as the target payment server from the N payment servers.

[0285] Step B6: The payment proxy server modifies the first URL of the social payment authentication request based on interface A2 to obtain the second URL of the social payment authentication request.

[0286] For example, the identification information of interface A2 is A2, and the first URL of the social payment authentication request is: file 1 / interface A. Then, A2 is added to the first URL, and the second URL of the social payment authentication request is: file 1 / interface A / interface A2.

[0287] Step B7: The payment proxy server sends the social payment authentication request including the second URL to the second payment server.

[0288] Step B8: The second payment server processes the social payment authentication request.

[0289] In an embodiment of the present application, the social payment authentication service is configured as a separate service on the second payment server, so that the processing of the social payment authentication request can be completed by calling interface A2 on the second payment server.

[0290] In an embodiment of the present application, the social payment authentication service is configured as a separate service on the second payment server, so that the processing of the social payment authentication request can be completed by calling interface A2 on the second payment server.

[0291] above Figure 13 The left side shows the existing payment processing method, which processes the wallet card binding information query request and the social payment authentication request. That is, the URLs generated by the terminal device for the wallet card binding information query request and the social payment authentication request are the same, both of which are file 1 / interface A. The payment server calls different handles (Handle) for processing based on the value of cmdID of interface A in the URL, and the processing logic is complex. In the embodiment of this application, Figure 13 As shown on the right, the wallet card binding information query service and the social payment authentication service are split into two different services and deployed on the payment servers with corresponding functions. In this way, wallet card binding information query requests and social payment authentication requests can be processed by calling different payment servers, facilitating business management and maintenance.

[0292] The video search method provided in the embodiment of the present application splits the payment service, assigns different payment services to N different payment servers for processing, and also splits the public gateway interface with complex payment functions, and configures the split public gateway interface on the payment server with the corresponding function. That is, the N payment servers in the embodiment of the present application are used to support different payment services, and at least part of the public gateway interfaces configured on the N payment servers are obtained by splitting the public gateway interface of the first type. In this way, during the actual payment processing, the terminal device generates a first business request and a first URL of the first business request in response to the object's payment operation on the first payment business. Then, the terminal device sends the first business request to the public forwarding proxy server. The public forwarding proxy server parses the first URL, and when it is checked that the first URL does not include the identification information of the first public gateway interface but includes the command identifier corresponding to the first business request, it sends the first business request to the payment proxy server. The payment proxy server determines the identification information of the first public gateway interface based on the command identifier corresponding to the first business request, and based on the identification information of the first public gateway interface, selects the target payment server where the first public gateway interface is located from the N payment servers, and at the same time, based on the identification information of the first public gateway interface, modifies the first URL of the first business request to generate a second URL, and finally sends the first business request including the second URL to the target payment server for payment processing. It can be seen from this that the embodiment of the present application splits the payment service and distributes the split payment service to N different payment servers for processing. At the same time, the public gateway interface with complex functions (i.e., the first type of public gateway interface) is split, and the split public gateway interface is configured on the payment server with corresponding functions, so that different payment servers are responsible for part of the payment service, and each payment server is related and independent and does not interfere with each other. When the payment logic on one of the payment servers needs to be modified, it will not affect the payment logic on other payment servers, thereby improving the reliability and accuracy of the management, maintenance and modification of the payment service and payment system, facilitating the version update of the payment system, and thus improving the performance and efficiency of payment processing.

[0293] The above describes the payment processing method of the embodiment of the present application from two aspects. Figure 14 An overall introduction to the payment processing method provided in the embodiments of the present application is given.

[0294] Figure 14 A flowchart of a payment processing method provided in accordance with an embodiment of the present application.

[0295] like Figure 14 As shown, the payment processing process of the embodiment of the present application includes:

[0296] S301: The terminal device generates a first service request and a first URL of the first service request in response to a payment operation of a first payment service by an object.

[0297] The specific implementation process of the above S301 can refer to the specific description of the above S101, which will not be repeated here.

[0298] S302: The terminal device sends a first service request to a public forwarding proxy server.

[0299] S303: The public forwarding proxy server parses the first URI of the first service request.

[0300] As can be seen from the above, in the embodiment of the present application, the first URL of the first service request generated by the terminal device includes two situations:

[0301] Case 1: When the payment client installed on the terminal device is a payment client of the first version (i.e., the latest version), or the payment client is a payment client of the first version, and the first business request is not a first-type business request, for example, it is not a wallet card binding information query request or a social payment authentication request, the generated first URL includes the identification information of the first public gateway interface corresponding to the first business request.

[0302] Case 2: When the payment client installed on the terminal device is not the first version (i.e., the old version) of the payment client, and the first business request is a first type of business request (for example, a wallet card binding information query request and a social payment authentication request), the generated first URL includes the command identifier corresponding to the first business request, and does not include the identification information of the first public gateway interface.

[0303] Based on this, after receiving the first service request sent by the terminal device, the public forwarding proxy server parses the first URL of the first service request. When the first URL of the first service request includes identification information of the first public gateway interface for processing the first service request, the following steps S304 to S305 are executed.

[0304] S304. When the first URL of the first business request includes identification information of a first public gateway interface for processing the first business request, the public forwarding proxy server selects a target payment server where the first public gateway interface is located from the N payment servers based on the identification information of the first public gateway interface.

[0305] S305: The public forwarding proxy server sends the first service request to the target payment server.

[0306] The specific execution process of the above S304 and S305 can refer to the specific description of the above S103 and S104, which will not be repeated here.

[0307] In some embodiments, when the public forwarding proxy server detects that the first URL includes a command identifier corresponding to the first service request but does not include identification information of the first public gateway interface, steps S306 to S310 are executed.

[0308] S306: When the first URL includes the command identifier corresponding to the first service request but does not include the identification information of the first common gateway interface, the public forwarding proxy server sends the first service request to the payment proxy server.

[0309] The specific implementation process of the above S306 can refer to the specific description of the above S203, which will not be repeated here.

[0310] S307: The payment proxy server determines identification information of the first common gateway interface based on the command identifier corresponding to the first service request.

[0311] The specific implementation process of the above S307 can refer to the specific description of the above S204, which will not be repeated here.

[0312] S308: The payment proxy server selects a target payment server where the first public gateway interface is located from the N payment servers based on the identification information of the first public gateway interface.

[0313] The specific implementation process of the above S308 can refer to the specific description of the above S205, which will not be repeated here.

[0314] S309: The payment server modifies the first URL of the first service request based on the identification information of the first common gateway interface to obtain a second URL of the first service request.

[0315] The specific implementation process of the above S309 can refer to the specific description of the above S206, which will not be repeated here.

[0316] S310: The payment server sends the first service request including the second URL to the target payment server.

[0317] The specific implementation process of the above S310 can refer to the specific description of the above S207, which will not be repeated here.

[0318] S311. The target payment server calls the first public gateway interface in the target payment server based on the identification port information of the first public gateway interface to process the first service request.

[0319] The specific implementation process of the above S311 can refer to the specific description of the above S104 or S208, which will not be repeated here.

[0320] The embodiment of the present application splits the payment service, assigning different payment services to N different payment servers for processing, and also splits the public gateway interface with complex payment functions, and configures the split public gateway interface on the payment server with the corresponding function. In other words, the N payment servers in the embodiment of the present application are used to support different payment services, and at least some of the public gateway interfaces configured on the N payment servers are obtained by splitting the public gateway interface of the first type. When the payment client is the first version or the first service request is not a first type service request, the public forwarding proxy server selects the target payment server where the first public gateway interface is located from the N payment servers based on the identification information of the first public gateway interface. When the payment client is not the first version, in order to be compatible with the old version, an embodiment of the present application sets up a payment proxy server, so that the public forwarding proxy server sends the first business request to the payment proxy server, and the payment proxy server determines the identification information of the first public gateway interface based on the command identifier corresponding to the first business request, and based on the identification information of the first public gateway interface, selects the target payment server where the first public gateway interface is located from N payment servers, and at the same time, based on the identification information of the first public gateway interface, modifies the first URL of the first business request to generate a second URL, and finally sends the first business request including the second URL to the target payment server for payment processing. It can be seen from this that the embodiment of the present application splits the payment service and distributes the split payment service to N different payment servers for processing. At the same time, the public gateway interface with complex functions (i.e., the first type of public gateway interface) is split, and the split public gateway interface is configured on the payment server with corresponding functions, so that different payment servers are responsible for part of the payment services, and each payment server is related and independent and does not interfere with each other. When the payment logic on one of the payment servers needs to be modified, it will not affect the payment logic on other payment servers, thereby improving the reliability and accuracy of the management, maintenance and modification of the payment service and payment system, facilitating the version update of the payment system, and thus improving the performance and efficiency of payment processing.

[0321] Combined with the above Figures 5 to 14 , describes in detail the model training and image processing method embodiments of the present application, and the following is combined with Figure 15 , describe in detail the device embodiments of the present application.

[0322] Figure 15 FIG1 is a schematic block diagram of a payment processing device provided in an embodiment of the present application. The device 10 can be applied to a public forwarding proxy server.

[0323] As shown in Figure 15 The payment processing apparatus 10 comprises:

[0324] a receiving unit 11 configured to receive a first service request sent by a terminal device, the first service request being generated by the terminal device when an object performs a payment operation on a first payment service;

[0325] a processing unit 12 configured to, when the first URL of the first service request comprises identification information of a first common gateway interface used for processing the first service request, select a target payment server in which the first common gateway interface is located from N payment servers based on the identification information of the first common gateway interface, the N payment servers being used for supporting different payment services, and at least part of the common gateway interfaces configured on the N payment servers being obtained by splitting a first type of common gateway interface, the first type of common gateway interface comprising M payment functions, the N being a positive integer, and the M being a positive integer greater than 1;

[0326] a sending unit 13 configured to send the first service request to the target payment server, so that the target payment server processes the first service request through the first common gateway interface.

[0327] In some embodiments, the common forwarding proxy server stores identification information of the common gateway interfaces configured on each of the N payment servers, and the processing unit 12 is specifically configured to determine the target server in which the first common gateway interface is located from the identification information of the common gateway interfaces configured on each of the N payment servers stored by the common forwarding proxy server based on the identification information of the first common gateway interface.

[0328] In some embodiments, the sending unit 13 is further configured to, when the first URL comprises a command identifier corresponding to the first service request and does not comprise the identification information of the first common gateway interface, send the first service request to a payment proxy server, so that the payment proxy server selects the target payment server from the N payment servers based on the command identifier corresponding to the first service request, the command identifier being used for indicating the first service request.

[0329] In some embodiments, the receiving unit 11 is further used to receive a processing result of the first business request, where the processing result is a processing result obtained by the target payment server processing the first business request through the first public gateway interface; the sending unit 13 is further used to send the processing result to the terminal device; wherein, when the public forwarding proxy server sends the first business request to the target payment server, the processing result is sent by the target payment server, and when the public forwarding proxy server sends the first business request to the payment proxy server, the processing result is sent by the payment proxy server.

[0330] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. To avoid repetition, they will not be described here. Specifically, Figure 15 The device shown can execute the embodiment of the above-mentioned payment processing method, and the aforementioned and other operations and / or functions of each module in the device are respectively for implementing the method embodiments corresponding to the public forwarding proxy server, which will not be repeated here for the sake of brevity.

[0331] Figure 16 2 is a schematic block diagram of a payment processing device provided in an embodiment of the present application. The device 20 can be applied to a payment proxy server.

[0332] like Figure 16 As shown, the payment processing device 20 includes:

[0333] a receiving unit 21 configured to receive a first service request sent by a public forwarding proxy server, where the first service request is generated by a terminal device when a subject performs a payment operation for a first payment service, a first URL of the first service request including a command identifier corresponding to the first service request and not including identification information of a first public gateway interface for processing the first service request, and the command identifier being used to indicate the first service request;

[0334] An interface determining unit 22, configured to determine identification information of the first public gateway interface based on a command identifier corresponding to the first service request;

[0335] a server determining unit 23 configured to select, based on the identification information of the first public gateway interface, a target payment server where the first public gateway interface is located from N payment servers, where the N payment servers are configured to support different payment services, and at least some of the public gateway interfaces configured on the N payment servers are obtained by splitting a first type of public gateway interface, where the first type of public gateway interface includes M payment functions, where N is a positive integer and M is a positive integer greater than 1;

[0336] The modification and sending unit 24 is configured to modify the first URL of the first business request based on the identification information of the first public gateway interface to obtain a second URL of the first business request, and send the first business request including the second URL to the target payment server, so that the target payment server processes the first business request through the first public gateway interface.

[0337] In some embodiments, the payment proxy server stores the correspondence between different business requests and different command identifiers, as well as the correspondence between different business requests and different public gateway interfaces. The interface determination unit 22 is used to determine the identification information of the first business request from the correspondence between the different business requests and the different command identifiers based on the command identifier corresponding to the first business request; and based on the identification information of the first business request, query and obtain the identification information of the first public gateway interface from the correspondence between the different business requests and different public gateway interfaces.

[0338] In some embodiments, the payment proxy server saves the identification information of the public gateway interface configured on each of the N payment servers, and the server determination unit 23 is specifically used to determine the target server where the first public gateway interface is located from the identification information of the public gateway interface configured on each of the N payment servers based on the identification information of the first public gateway interface.

[0339] In some embodiments, the modification sending unit 24 is configured to add the identification information of the first common gateway interface to the first URL of the first service request to obtain the second URL of the first service request.

[0340] In some embodiments, the receiving unit 21 is further used to receive the processing result of the first business request sent by the target payment server; the modified sending unit 24 is further used to send the processing result to the public forwarding proxy server, so that the public forwarding proxy server sends the processing result to the terminal device.

[0341] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. To avoid repetition, they will not be described here. Specifically, Figure 16 The device shown can execute the embodiment of the above-mentioned payment processing method, and the aforementioned and other operations and / or functions of each module in the device are respectively for implementing the corresponding method embodiments of the payment proxy server, which will not be repeated here for the sake of brevity.

[0342] Figure 17Schematic block diagram of a payment processing device provided by an embodiment of the present application. The device 30 can be applied to a target payment server.

[0343] like Figure 17 As shown, the payment processing device 30 includes:

[0344] A receiving unit 31 is configured to receive a first service request, where the first service request is generated when a subject performs a payment operation for a first payment service, the target payment server being one of N payment servers, the N payment servers being configured to support different payment services, and at least some of the public gateway interfaces configured on the N payment servers being split from a first type of public gateway interface, the first type of public gateway interface including M payment functions, where N is a positive integer and M is a positive integer greater than 1;

[0345] The calling unit 32 is used to call the first public gateway interface in the target payment server based on the identification port information of the first public gateway interface to process the first business request, where the first public gateway interface is a public gateway interface used to process the first business request; wherein, when the first URL of the first business request includes the identification information of the first public gateway interface, the first business request is sent by the public forwarding proxy server; when the first URL of the first business request includes the command identifier corresponding to the first business request and does not include the identification information of the first public gateway interface, the first business request is sent by the payment proxy server, and the command identifier is used to indicate the first business request.

[0346] In some embodiments, the sending unit 31 is further used to send the processing result of the first business request to the public forwarding proxy server when the first business request is sent by the public forwarding proxy server; and to send the processing result of the first business request to the payment proxy server when the first business request is sent by the payment proxy server.

[0347] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. To avoid repetition, they will not be described here. Specifically, Figure 17 The device shown can execute the embodiment of the above-mentioned payment processing method, and the aforementioned and other operations and / or functions of each module in the device are respectively for implementing the method embodiments corresponding to the target payment server, which will not be repeated here for the sake of brevity.

[0348] Figure 18 4 is a schematic block diagram of a payment processing device provided in an embodiment of the present application. The device 40 can be applied to a terminal device.

[0349] like Figure 18 As shown, the payment processing device 40 includes:

[0350] A generating unit 41 is configured to generate a first service request and a first URL of the first service request in response to a payment operation of the object for the first payment service;

[0351] The transceiver unit 42 is configured to send the first business request to a public forwarding proxy server, so that based on the first URL of the first business request, a target payment server where a first public gateway interface is located is selected from N payment servers to process the first business request, where the first public gateway interface is a public gateway interface for processing the first business request. The N payment servers are configured to support different payment services, and at least some of the public gateway interfaces configured on the N payment servers are obtained by splitting a first type of public gateway interface. The first type of public gateway interface includes M payment functions, where N is a positive integer and M is a positive integer greater than 1.

[0352] In some embodiments, the generating unit 41 is specifically configured to obtain version information of the payment client in response to the object's payment operation on the first payment service; and generate a first URL for the first service request based on the version information of the payment client.

[0353] In some embodiments, the generation unit 41 is specifically used to, when the version of the payment client is the first version, obtain the identification information of the first public gateway interface, and generate a first URL for the first business request based on the identification information of the first public gateway interface, the first URL including the identification port information of the first public gateway interface, and the first version is the latest version of the payment client; when the version of the payment client is not the first version and the first business request is a first type of business request, obtain the command identifier corresponding to the first business request, and generate a first URL for the first business request based on the command identifier corresponding to the first business request, the first URL including the command identifier corresponding to the first business request, and the first type of business request includes a wallet binding information query request and a social payment authentication request.

[0354] In some embodiments, the transceiver unit 42 is further configured to receive a processing result of the first service request sent by the public forwarding proxy server.

[0355] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. To avoid repetition, they will not be described here. Specifically, Figure 18The device shown can execute the embodiment of the above-mentioned payment processing method, and the aforementioned and other operations and / or functions of each module in the device are respectively for implementing the method embodiments corresponding to the terminal device. For the sake of brevity, they are not repeated here.

[0356] The apparatus of the embodiment of the present application is described above from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that the functional module can be implemented in hardware form, can be implemented by instructions in software form, or can be implemented by a combination of hardware and software modules. Specifically, the steps of the method embodiment in the embodiment of the present application can be completed by the hardware integrated logic circuit and / or software form instructions in the processor, and the steps of the method disclosed in the embodiment of the present application can be directly embodied as being executed by a hardware decoding processor, or can be executed by a combination of hardware and software modules in the decoding processor. Optionally, the software module can be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps in the above method embodiment in conjunction with its hardware.

[0357] Figure 19 is a schematic block diagram of an electronic device provided in an embodiment of the present application, Figure 19 The electronic device may be a public forwarding proxy server, a payment proxy server, a target payment server or a terminal device.

[0358] like Figure 19 As shown, the electronic device 30 may include:

[0359] The memory 31 and the processor 32 are configured to store a computer program 33 and transmit the program code 33 to the processor 32. In other words, the processor 32 can call and run the computer program 33 from the memory 31 to implement the method in the embodiment of the present application.

[0360] For example, the processor 32 may be configured to execute the steps of the above method according to the instructions in the computer program 33 .

[0361] In some embodiments of the present application, the processor 32 may include but is not limited to:

[0362] General-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.

[0363] In some embodiments of the present application, the memory 31 includes but is not limited to:

[0364] Volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus random access memory (DR RAM).

[0365] In some embodiments of the present application, the computer program 33 may be divided into one or more modules, which are stored in the memory 31 and executed by the processor 32 to implement the method for recording a page provided by the present application. The one or more modules may be a series of computer program instruction segments capable of performing specific functions, and the instruction segments are used to describe the execution process of the computer program 33 in the electronic device.

[0366] like Figure 19 As shown, the electronic device 30 may further include:

[0367] The transceiver 34 may be connected to the processor 32 or the memory 31 .

[0368] The processor 32 may control the transceiver 34 to communicate with other devices. Specifically, the processor 32 may send information or data to other devices or receive information or data sent by other devices. The transceiver 34 may include a transmitter and a receiver. The transceiver 34 may further include one or more antennas.

[0369] It should be understood that the various components in the electronic device 30 are connected via a bus system, wherein the bus system includes not only a data bus but also a power bus, a control bus and a status signal bus.

[0370] According to one aspect of the present application, a computer storage medium is provided, on which a computer program is stored. When the computer program is executed by a computer, the computer is enabled to perform the method of the above-mentioned method embodiment. Alternatively, the present application also provides a computer program product containing instructions. When the computer is executed by the instructions, the computer is enabled to perform the method of the above-mentioned method embodiment.

[0371] According to another aspect of the present application, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the method of the above-described method embodiment.

[0372] In other words, when implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a digital video disc (DVD)), or a semiconductor medium (e.g., a solid-state drive (SSD)).

[0373] Those skilled in the art will appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0374] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the modules is only a logical function division. In actual implementation, there may be other division methods, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some common gateway interface, and the indirect coupling or communication connection of the device or module can be electrical, mechanical or other forms.

[0375] Modules described as separate components may or may not be physically separate, and components displayed as modules may or may not be physical modules, i.e., they may be located in one place or distributed across multiple network elements. Some or all of the modules may be selected based on actual needs to achieve the purpose of the present embodiment. For example, the functional modules in the various embodiments of the present application may be integrated into a processing module, or each module may exist physically separately, or two or more modules may be integrated into a single module.

[0376] The above content is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A payment processing method, characterized in that: Applied to a public forwarding proxy server, the method comprises: receiving a first service request sent by a terminal device, where the first service request is generated by the terminal device when the subject performs a payment operation for a first payment service; When the first URL of the first service request includes identification information of a first public gateway interface for processing the first service request, a target payment server where the first public gateway interface is located is selected from N payment servers based on the identification information of the first public gateway interface, the N payment servers being used to support different payment services, and at least some of the public gateway interfaces configured on the N payment servers being obtained by splitting a first type of public gateway interface, the first type of public gateway interface including M payment functions, where N is a positive integer and M is a positive integer greater than 1; The first service request is sent to the target payment server, so that the target payment server processes the first service request through the first common gateway interface.

2. The method according to claim 1, characterized in that The public forwarding proxy server stores identification information of a public gateway interface configured on each of the N payment servers, and selecting a target payment server where the first public gateway interface is located from the N payment servers based on the identification information of the first public gateway interface includes: Based on the identification information of the first public gateway interface, the target server where the first public gateway interface is located is determined from the identification information of the public gateway interface configured on each of the N payment servers stored in the public forwarding proxy server.

3. The method according to claim 1, characterized in that The method further comprises: When the first URL includes a command identifier corresponding to the first business request and does not include identification information of the first common gateway interface, the first business request is sent to the payment proxy server, so that the payment proxy server selects the target payment server from the N payment servers based on the command identifier corresponding to the first business request, where the command identifier is used to indicate the first business request.

4. The method according to any one of claims 1 to 3, characterized in that The method further comprises: receiving a processing result of the first service request, where the processing result is a processing result obtained by the target payment server processing the first service request through the first public gateway interface; Sending the processing result to the terminal device; When the public forwarding proxy server sends the first business request to the target payment server, the processing result is sent by the target payment server; when the public forwarding proxy server sends the first business request to the payment proxy server, the processing result is sent by the payment proxy server.

5. A payment processing method, characterized in that: Applied to a payment proxy server, the method includes: receiving a first service request sent by a public forwarding proxy server, where the first service request is generated by a terminal device when a subject performs a payment operation for a first payment service, a first URL of the first service request includes a command identifier corresponding to the first service request and does not include identification information of a first public gateway interface used to process the first service request, and the command identifier is used to indicate the first service request; Determining identification information of the first public gateway interface based on the command identifier corresponding to the first service request; selecting, based on the identification information of the first public gateway interface, a target payment server where the first public gateway interface is located from N payment servers, where the N payment servers are configured to support different payment services, and at least some of the public gateway interfaces configured on the N payment servers are obtained by splitting a first type of public gateway interface, where the first type of public gateway interface includes M payment functions, where N is a positive integer and M is a positive integer greater than 1; Based on the identification information of the first public gateway interface, the first URL of the first business request is modified to obtain a second URL of the first business request, and the first business request including the second URL is sent to the target payment server, so that the target payment server processes the first business request through the first public gateway interface.

6. The method according to claim 5, characterized in that The payment proxy server stores correspondences between different business requests and different command identifiers, as well as correspondences between different business requests and different public gateway interfaces. The determining of identification information of the first public gateway interface based on the command identifier corresponding to the first business request includes: Based on the command identifier corresponding to the first service request, determining the identification information of the first service request from the correspondence between the different service requests and the different command identifiers; Based on the identification information of the first service request, the identification information of the first public gateway interface is queried in the correspondence between the different service requests and the different public gateway interfaces.

7. The method according to claim 6, characterized in that The payment proxy server stores identification information of a common gateway interface configured on each of the N payment servers, and selecting a target payment server where the first common gateway interface is located from the N payment servers based on the identification information of the first common gateway interface includes: Based on the identification information of the first public gateway interface, the target server where the first public gateway interface is located is determined from the identification information of the public gateway interface configured on each of the N payment servers.

8. The method according to claim 6, characterized in that The modifying the first URL of the first service request based on the identification information of the first common gateway interface to obtain the second URL of the first service request includes: The identification information of the first common gateway interface is added to the first URL of the first service request to obtain the second URL of the first service request.

9. The method according to any one of claims 5 to 8, characterized in that After sending the first service request including the second URL to the target payment server, the method further includes: receiving a processing result of the first service request sent by the target payment server; The processing result is sent to the public forwarding proxy server, so that the public forwarding proxy server sends the processing result to the terminal device.

10. A payment processing method, characterized in that: Applied to a target payment server, the method includes: receiving a first service request, where the first service request is generated when a subject performs a payment operation for a first payment service, the target payment server being one of N payment servers, the N payment servers being configured to support different payment services, and at least some of the public gateway interfaces configured on the N payment servers being split from a first-type public gateway interface, the first-type public gateway interface including M payment functions, where N is a positive integer and M is a positive integer greater than 1; Based on the identification information of the first public gateway interface, calling the first public gateway interface in the target payment server to process the first service request, where the first public gateway interface is a public gateway interface used to process the first service request; Among them, when the first URL of the first business request includes the identification information of the first public gateway interface, the first business request is sent by the public forwarding proxy server; when the first URL of the first business request includes the command identifier corresponding to the first business request and does not include the identification information of the first public gateway interface, the first business request is sent by the payment proxy server, and the command identifier is used to indicate the first business request.

11. The method according to claim 10, characterized in that The method further comprises: When the first service request is sent by the public forwarding proxy server, sending the processing result of the first service request to the public forwarding proxy server; When the first service request is sent by the payment proxy server, the processing result of the first service request is sent to the payment proxy server.

12. A payment processing method, characterized in that: Applied to a terminal device, the method further includes: In response to the object's payment operation on the first payment service, generating a first service request and a first URL of the first service request; The first business request is sent to a public forwarding proxy server, so that based on the first URL of the first business request, a target payment server where a first public gateway interface is located is selected from N payment servers to process the first business request, where the first public gateway interface is a public gateway interface used to process the first business request, the N payment servers are used to support different payment services, and at least some of the public gateway interfaces configured on the N payment servers are obtained by splitting a first type of public gateway interface, where the first type of public gateway interface includes M payment functions, where N is a positive integer and M is a positive integer greater than 1.

13. The method according to claim 12, characterized in that The step of generating a first URL for the first service request in response to the object's payment operation on the first payment service includes: In response to the object's payment operation on the first payment service, obtaining version information of the payment client; Based on the version information of the payment client, a first URL for the first service request is generated.

14. The method according to claim 13, wherein: The generating, based on the version information of the payment client, a first URL for the first service request includes: When the version of the payment client is the first version, obtaining identification information of the first public gateway interface, and generating a first URL for the first service request based on the identification information of the first public gateway interface, where the first URL includes identification information of the first public gateway interface, and the first version is the latest version of the payment client; When the version of the payment client is not the first version and the first business request is a first type business request, a command identifier corresponding to the first business request is obtained, and based on the command identifier corresponding to the first business request, a first URL for the first business request is generated, where the first URL includes the command identifier corresponding to the first business request. The first type of business request includes a wallet card binding information query request and a social payment authentication request.

15. A payment processing device, characterized in that: Applied to a public forwarding proxy server, the device comprises: a receiving unit, configured to receive a first service request sent by a terminal device, where the first service request is generated by the terminal device when the subject performs a payment operation for a first payment service; a processing unit configured to, when the first URL of the first service request includes identification information of a first public gateway interface for processing the first service request, select, based on the identification information of the first public gateway interface, a target payment server where the first public gateway interface is located from N payment servers, the N payment servers being configured to support different payment services, and at least some of the public gateway interfaces configured on the N payment servers being split from a first type of public gateway interface, the first type of public gateway interface including M payment functions, where N is a positive integer and M is a positive integer greater than 1; A sending unit is configured to send the first service request to the target payment server, so that the target payment server processes the first service request through the first common gateway interface.

16. A payment processing device, characterized in that: Applied to a payment proxy server, the device includes: a receiving unit, configured to receive a first service request sent by a public forwarding proxy server, where the first service request is generated by a terminal device when a subject performs a payment operation for a first payment service, a first URL of the first service request including a command identifier corresponding to the first service request and not including identification information of a first public gateway interface for processing the first service request, and the command identifier being used to indicate the first service request; an interface determining unit, configured to determine identification information of the first public gateway interface based on a command identifier corresponding to the first service request; a server determining unit configured to select, based on the identification information of the first public gateway interface, a target payment server where the first public gateway interface is located from N payment servers, where the N payment servers are configured to support different payment services, and at least some of the public gateway interfaces configured on the N payment servers are obtained by splitting a first type of public gateway interface, where the first type of public gateway interface includes M payment functions, where N is a positive integer and M is a positive integer greater than 1; a modification and sending unit, configured to modify the first URL of the first business request based on the identification information of the first public gateway interface to obtain a second URL of the first business request, and send the first business request including the second URL to the target payment server, so that the target payment server processes the first business request through the first public gateway interface.

17. A payment processing device, characterized in that: Applied to a target payment server, the device comprises: a receiving unit, configured to receive a first service request, where the first service request is generated when a subject performs a payment operation for a first payment service, the target payment server being one of N payment servers, the N payment servers being configured to support different payment services, and at least some of the public gateway interfaces configured on the N payment servers being split from a first type of public gateway interface, the first type of public gateway interface including M payment functions, where N is a positive integer and M is a positive integer greater than 1; A calling unit is used to call the first public gateway interface in the target payment server based on the identification port information of the first public gateway interface to process the first business request, where the first public gateway interface is a public gateway interface used to process the first business request; wherein, when the first URL of the first business request includes the identification information of the first public gateway interface, the first business request is sent by the public forwarding proxy server; when the first URL of the first business request includes a command identifier corresponding to the first business request and does not include the identification information of the first public gateway interface, the first business request is sent by the payment proxy server, and the command identifier is used to indicate the first business request.

18. A payment processing device, characterized in that: Applied to a terminal device, the device includes: a generating unit, configured to generate a first service request and a first URL of the first service request in response to a payment operation of the object for the first payment service; A transceiver unit is configured to send the first service request to a public forwarding proxy server, so that based on a first URL of the first service request, a target payment server where a first public gateway interface is located is selected from N payment servers to process the first service request, where the first public gateway interface is a public gateway interface for processing the first service request, the N payment servers are configured to support different payment services, and at least some of the public gateway interfaces configured on the N payment servers are obtained by splitting a first type of public gateway interface, where the first type of public gateway interface includes M payment functions, where N is a positive integer and M is a positive integer greater than 1.

19. An electronic device, characterized in that: including processor and memory; The memory is used to store computer programs; The processor is configured to execute the computer program to implement the method according to any one of claims 1 to 4, 5 to 9, 10 to 11, and 12 to 14.

20. A computer-readable storage medium, characterized in that For storing computer programs; The computer program enables a computer to execute the method according to any one of claims 1 to 4, 5 to 9, 10 to 11, and 12 to 14.

Images