A payment docking management method, a payment middle platform, a medium and a program product

Abstract

The application relates to the technical field of data management, in particular to a payment docking management method, a payment middle platform, a medium and a program product. The method comprises the following steps: after receiving the sent payment information, sending payment acceptance information to a user end and a corresponding payment merchant end according to the payment information, and writing the payment information into an asynchronous processing queue corresponding to the payment merchant end; when the number of to-be-paid orders contained in the asynchronous processing queue corresponding to the payment merchant end exceeds a preset number threshold, identifying payment features contained in each payment information, wherein the payment features comprise interface specifications, data formats, communication protocols and risk monitoring; determining a target payment channel of each payment information based on the payment features contained in all the payment information; establishing communication between the corresponding user end and the to-be-paid merchant end according to the target payment channel of each payment information, and completing an order payment operation based on the corresponding target payment channel. The application can improve the payment efficiency in the diversified payment process.

Description

Technical Field

[0001] This application relates to the field of data management technology, and in particular to a payment integration management method, payment middleware, media and program products. Background Technology

[0002] The diversification of payment methods is a major feature of current payment operations. With the popularization of mobile internet and the development of technology, payment methods no longer rely solely on traditional cash or bank cards, but have expanded to include a variety of emerging payment methods such as QR code payment, NFC payment, sound wave payment, fingerprint payment, and blockchain payment. This diversification of payment methods can provide users with a convenient payment experience.

[0003] When dealing with different types of payment processing operations, it is usually necessary to establish different payment business logic with the payment platform corresponding to each payment method to ensure the smoothness and accuracy of the payment process. However, since the interface standards, communication protocols and data processing methods corresponding to different payment methods may be different, the complexity of the payment process may be increased when connecting with various payment platforms, which may affect payment efficiency. Summary of the Invention

[0004] To improve payment efficiency in diversified payment processes, this application provides a payment integration management method, a payment middleware platform, media, and program products.

[0005] Firstly, this application provides a payment integration management method, which adopts the following technical solution:

[0006] A payment integration management method includes:

[0007] Upon receiving payment information from the user, payment acceptance information is sent to both the user and the corresponding payment merchant based on the payment information. The payment information is then written into the asynchronous processing queue corresponding to the payment merchant. The payment information includes the order to be paid, the payment method, and the payment merchant. The asynchronous processing queue is used to store the payment information.

[0008] When the number of pending orders in the asynchronous processing queue corresponding to the payment merchant exceeds a preset threshold, the payment characteristics contained in each payment information are identified. The payment characteristics include interface specifications, data format, communication protocol, and risk monitoring.

[0009] Based on the payment characteristics contained in all payment information, the target payment channel corresponding to each payment information is determined;

[0010] Establish communication between the corresponding user terminal and the merchant terminal to be paid based on the target payment channel corresponding to each payment information, and complete the order payment operation based on the corresponding target payment channel.

[0011] By adopting the technical solution, in the process of processing the payment operation, asynchronous processing is realized by returning the payment acceptance information and writing the payment information into the asynchronous processing queue to wait for subsequent payment processing. Since different payment information may correspond to different interface specifications, data formats, communication protocols, etc. in the face of diversified payment processes, a long time may be consumed in determining the target payment channel corresponding to each payment information, thereby affecting the payment processing efficiency. If synchronous processing is adopted, the payment operation of the next payment information cannot be started until the payment operation corresponding to the previous payment information is completed, which may result in a long overall payment processing period and affect the user's payment experience. Asynchronous processing can handle diversified payment requests and then process them based on the asynchronous processing queue, thereby reducing the user's waiting time. In addition, the target payment channel is determined based on the payment characteristics contained in different payment information, that is, the appropriate payment channel can be selected according to the specific circumstances of different payment information, thereby improving the intelligent degree and accuracy in determining the target payment channel, and facilitating the improvement of the efficiency in the process of payment operation.

[0012] In a possible implementation manner, the target payment channel corresponding to the payment information is determined based on the payment characteristics contained in the payment information, including:

[0013] Each payment characteristic value corresponding to each payment characteristic is identified from the payment information, and a sub-function channel corresponding to each payment characteristic value is determined from a preset sub-function channel list corresponding to each payment characteristic. The preset sub-function channel list contains sub-function channels corresponding to different payment characteristic values.

[0014] All sub-function channels corresponding to the payment information are combined to obtain the target payment channel of the payment information. The target payment channel is composed of multiple sub-function channels.

[0015] By adopting the technical solution, the sub-function channel corresponding to each payment characteristic is determined by the payment characteristic identified from the payment information and the payment characteristic value corresponding to each payment characteristic, which facilitates the improvement of the accuracy in determining the sub-function channel. In addition, all sub-function channels corresponding to the payment information are combined to determine the final target payment channel, which facilitates the satisfaction of different payment requirements of diversified payment information, thereby facilitating the flexibility in determining the target payment channel.

[0016] In a possible implementation manner, all sub-function channels corresponding to each payment information are combined to obtain the target payment channel of each payment information, including:

[0017] identify the writing time of each payment information when written into the asynchronous processing queue and the payment identifier contained in each payment information, and determine the expected operation duration corresponding to each payment information based on the payment duration mapping relationship of each payment identifier, the payment duration mapping relationship being the corresponding relationship between the payment identifier and the expected operation duration;

[0018] determine the access time corresponding to each sub-function channel according to the expected operation duration corresponding to each payment information and the writing time;

[0019] generate an execution time wheel corresponding to each preset sub-function channel list according to the access time of each sub-function channel, the preset sub-function channel list to which each sub-function channel belongs, and the preset execution time wheel corresponding to each preset sub-function list, each preset execution time wheel containing a plurality of time bins;

[0020] Combine the access time corresponding to each payment information and each execution time wheel to obtain the target payment channel corresponding to each payment information.

[0021] By adopting the above technical solution, since different payment information may contain the same payment features, that is, the sub-function channels used by different payment information in determining the target payment channel may be the same, by analyzing the sub-function channels required by multiple payment information, the expected operation duration of each payment information and the access time of each sub-function channel, multiple execution time wheels are constructed, and according to the flow of the execution time wheel at the corresponding time, the target payment channel of each payment information is determined after the sub-function channels are efficiently combined, thereby improving the accuracy and speed of determining the target payment channel corresponding to each payment information.

[0022] In one possible implementation, the generation of the execution time wheel corresponding to each preset sub-function channel list according to the access time of each sub-function channel, the preset sub-function channel list to which each sub-function channel belongs, and the preset execution time wheel corresponding to each preset sub-function list includes:

[0023] determine the to-be-executed sub-function channel of each time bin in each preset execution time wheel according to the access time of each payment information;

[0024] determine the execution duration of each sub-function channel corresponding to the time bin according to the access time of each sub-function channel corresponding to each preset sub-function channel list;

[0025] generate the execution time wheel of each preset sub-function channel list according to the execution duration of each time bin and the to-be-executed sub-function channel.

[0026] By adopting the technical scheme, the execution time and sequence of each sub-function channel can be controlled by storing each sub-function channel in the execution time wheel according to the access time, and the manual intervention in determining the target payment channel can be reduced by establishing the execution time wheel, thereby improving the processing efficiency.

[0027] In a possible implementation manner, the channel combination is performed on the execution time wheel and the access time corresponding to the payment information, including:

[0028] If it is detected that the current time is the access time of the payment information, the execution time bin corresponding to each execution time wheel at the access time is obtained;

[0029] The sub-function channel to be executed corresponding to each execution time bin is identified, and the sub-function channel to be executed corresponding to each execution time bin is combined.

[0030] By adopting the technical scheme, the execution time bin that needs to be accessed is determined by matching the current time with the access time corresponding to each execution time bin in the execution time wheel, that is, the sub-function channel that needs to be accessed is determined, and only when the current time is consistent with the access time, the corresponding sub-function channel can be combined, so that the accuracy of determining the sub-function channel to be executed is improved, and the accuracy of the channel combination result is improved.

[0031] In a possible implementation manner, the communication between the corresponding user terminal and the to-be-paid merchant terminal is established according to the target payment channel corresponding to the payment information, and the order payment operation is completed based on the corresponding target payment channel, and the method further includes:

[0032] The order payment operation process is detected in real time, and the operation feature is collected according to a preset frequency;

[0033] When the abnormal operation feature appears in the operation feature, the standby payment channel is started, and the standby payment channel is determined as the target payment channel of the to-be-paid order, and the abnormal operation feature includes network delay and payment channel maintenance.

[0034] By adopting the technical scheme, the payment operation process is monitored in real time, and when the abnormal operation feature is detected, the standby payment channel is started in time and is determined as the target payment channel of the to-be-paid order, so that the automatic switching mechanism can greatly reduce the need for manual intervention, and the automation degree and efficiency of the payment process are improved, and the continuity of the payment process is ensured by switching to the standby payment channel in time when the abnormal condition is found.

[0035] In a second aspect, the application provides an electronic device, which adopts the following technical scheme:

[0036] A payment middle platform, comprising:

[0037] at least one processor;

[0038] a memory;

[0039] at least one application program, wherein the at least one application program is stored in the memory and is configured to be executed by the at least one processor, and the at least one application program is configured to execute the payment docking management method.

[0040] In a third aspect, the present application provides a computer readable storage medium, which adopts the following technical solution:

[0041] A computer readable storage medium, comprising a computer program capable of being loaded and executed by a processor to execute the payment docking management method.

[0042] In a fourth aspect, the present application provides a computer program product, which adopts the following technical solution:

[0043] A computer program product, comprising a computer program, which is executed by a processor to implement the payment docking management method.

[0044] In summary, the present application includes at least one of the following beneficial technical effects:

[0045] In the process of processing payment operations, asynchronous processing is realized by returning payment acceptance information and writing payment information into an asynchronous processing queue to wait for subsequent payment processing. Since different payment information may correspond to different interface specifications, data formats, communication protocols, etc. in the face of diversified payment processes, a long time may be consumed in determining the target payment channel corresponding to each payment information, thereby possibly affecting the payment processing efficiency. If synchronous processing is used, the next payment operation of the payment information cannot be started until the previous payment operation corresponding to the payment information is completed, which may result in a long overall payment processing period and may affect the payment experience of the user. Asynchronous processing can accommodate diversified payment requests, and then process them based on asynchronous processing queues, thereby reducing the waiting time of the user. In addition, the target payment channel is determined based on the payment characteristics contained in different payment information, that is, the appropriate payment channel can be selected according to the specific circumstances of different payment information, thereby improving the intelligent degree and accuracy in determining the target payment channel, and thereby facilitating the improvement of the efficiency in the process of payment operations.

[0046] Since the same payment features can be contained in different payment information, that is, the sub-function channels used by different payment information in determining the target payment channel can be the same, by analyzing the sub-function channels required to be used by multiple payment information, and the predicted operation time length of each payment information and the access time of each sub-function channel, multiple execution time wheels are constructed, and according to the flow of the execution time wheel at the corresponding time, the target payment channel of each payment information is determined after the sub-function channels are efficiently combined, so as to facilitate improving the accuracy and rate when determining the target payment channel corresponding to each payment information. BRIEF DESCRIPTION OF DRAWINGS

[0047] Figure 1 is a flowchart of a payment docking management method in an embodiment of the present application;

[0048] Figure 2 is a flowchart of a method for determining a target payment channel in an embodiment of the present application;

[0049] Figure 3 is a schematic diagram of an execution time bin in an embodiment of the present application;

[0050] Figure 4 is a structural schematic diagram of a payment middle platform in an embodiment of the present application. DETAILED DESCRIPTION

[0051] The following will be described in detail with reference to the accompanying drawings. Figures 1-4 The present application will be further described in detail.

[0052] Those skilled in the art can make modifications to the present embodiments without creative contribution after reading the present specification, but as long as they are within the scope of the claims of the present application, they are protected by the patent law.

[0053] In order to make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme of the embodiments of the present application will be described clearly and completely below with reference to the accompanying drawings of the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present application.

[0054] Specifically, the embodiment of the present application provides a payment docking management method, which is executed by a payment middle platform. The payment middle platform can be a server or a terminal device. The server can be a physical server, a server cluster composed of multiple physical servers, a distributed system, or a cloud server providing cloud computing services. The terminal device can be a smart phone, a tablet computer, a notebook computer, a desktop computer, etc., but is not limited thereto. The terminal device and the server can be directly or indirectly connected through wired or wireless communication, and the embodiment of the present application does not make any limitation here.

[0055] Reference Figure 1 , Figure 1 is a flowchart of a payment docking management method in the embodiment of the present application. The method comprises steps S110-S140, wherein:

[0056] Step S110: After receiving the payment information sent by the user end, the payment information is written into the asynchronous processing queue corresponding to the payment merchant end, and the payment information is sent to the user end and the corresponding payment merchant end according to the payment information. The payment information includes the order to be paid, the payment method and the payment merchant. The asynchronous processing queue is used to store the payment information.

[0057] Specifically, the user end is generally a consumer end. The user end and the payment merchant end communicate through the payment middle platform, that is, the user end can send the order to be paid to the payment middle platform. After receiving the payment information sent by the user end, the payment middle platform can forward the payment information to the payment merchant end after packaging and processing the payment information, so as to complete the order payment. The packaging and processing of the payment information is to write the payment information into the asynchronous processing queue corresponding to the payment merchant end. When the number of payment information to be processed is less than the preset processing number, the payment middle platform can directly process the payment information received from the user end without writing the payment information into the asynchronous processing queue corresponding to the payment merchant end. When the number of payment information to be processed is not less than the preset processing number, in order to reduce the calculation pressure of the payment middle platform and to reduce the probability of abnormality in the payment process, the payment middle platform can first feed back the payment acceptance information to the user end and the corresponding payment merchant end after receiving the payment information sent by the user end, and then write the payment information into the asynchronous processing queue corresponding to the payment merchant end for subsequent processing, that is, when the number of payment information is not less than the preset processing number, the payment information is operated in an asynchronous manner. The specific preset processing number is not limited in the embodiment of the present application, and can be set by the relevant technical personnel.

[0058] Different asynchronous processing queues correspond to different payment merchant sides. Since the payment information contains a payment merchant, the payment merchant in the payment information can be determined by feature recognition, and then the asynchronous processing queue path corresponding to the payment merchant is obtained, and the payment information sent by the user side is written based on the path. The payment method is the payment method selected by the user side, such as face payment, fingerprint payment, etc.

[0059] Step S120: When the number of to-be-paid orders contained in the asynchronous processing queue corresponding to the payment merchant exceeds the preset number threshold, the payment features contained in each payment information are identified, including interface specification, data format, communication protocol, and risk monitoring.

[0060] Specifically, the number of to-be-paid orders is the number of payment information in the asynchronous processing queue. When the number of to-be-paid orders contained in the asynchronous processing queue corresponding to the payment merchant does not exceed the preset number threshold, each payment information in the asynchronous processing queue can be processed by allocating processing time, for example, the preset number threshold is 4, when the number of payment information contained in the asynchronous processing queue corresponding to the payment merchant is 3, different payment information can be allocated processing time period, for example, 10:00 processes the first payment information, 10:01 processes the second payment information, and 10:02 processes the third payment information. By allocating the processing time period, the working pressure of the payment platform at a certain moment is reduced. When the number of to-be-paid orders contained in the asynchronous processing queue exceeds the preset number threshold, if the processing time period is allocated, the payment processing time may be prolonged, which may reduce the user experience and the use experience of the payment merchant side.

[0061] At this time, the payment features contained in the payment information need to be identified, and other ways are used to process the multiple payment information in the asynchronous processing queue. Different payment channels corresponding to different interface specifications may differ in technical implementation, business logic, security requirements, etc. For example, in terms of technical implementation, different payment channel providers may use different technical architectures and development languages, and the interface specifications provided by different payment channel providers may differ, so the interface specification contained in the payment information needs to be considered when determining the payment channel corresponding to the payment information.

[0062] When the payment information flows in the payment channel, it is necessary to ensure that the payment information sent by the user end can be accurately received by the payment merchant end, so when selecting the payment channel, the data format contained in the payment information needs to be considered and analyzed. When the data format of the payment information sent by the client cannot be received by the payment merchant end, data format conversion needs to be performed through the payment channel during the transmission of the payment information, so as to ensure that the data format of the payment information is a data format that can be received and recognized by the payment merchant end. The data format contained in the payment information includes the data format sent by the user end and the data format that can be received by the payment merchant end.

[0063] Since the payment information may need to be transmitted between different operation ends, the communication protocol defines the rules and standards that should be followed when transmitting information between these operation ends. Only by following the correct communication protocol can the accuracy and integrity of the payment information during transmission be ensured. Therefore, when determining the payment channel, the communication protocol contained in the payment information needs to be considered, so that the determined payment channel can transmit information according to the communication protocol contained in the payment information.

[0064] In addition, different payment information may correspond to different importance levels, and the importance level of the payment information corresponds to the risk monitoring level required during information transmission. Therefore, when determining the payment channel, the risk monitoring level contained in the payment information needs to be considered, so that the determined payment channel can perform risk monitoring according to the corresponding level.

[0065] The payment features contained in the payment information can be determined according to the preset payment feature mapping relationship when generating a payment order, wherein the preset payment feature mapping relationship contains payment features corresponding to different payment amounts, payment user identities, payment times, etc. By identifying the payment amount, payment user identity, payment time, etc. in the payment information, the payment feature corresponding to the payment information can be determined. The specific content of the preset payment feature mapping relationship is not limited in the embodiments of the present application, and can be determined by relevant technical personnel according to historical experience and uploaded to the payment platform. The number of payment features contained in the same payment information is not limited in the embodiments of the present application.

[0066] Step S130: Based on the payment features contained in all payment information, determine the target payment channel corresponding to each payment information.

[0067] Specifically, different payment features correspond to a sub-function channel, and after combining multiple sub-function channels, the target payment channel corresponding to each payment information can be determined. The determination process of the target payment channel corresponding to any payment information can be:

[0068] The payment feature value corresponding to each payment feature is identified from the payment information, and the sub-function channel corresponding to each payment feature value is determined from the preset sub-function channel list corresponding to each payment feature. The preset sub-function channel list contains sub-function channels corresponding to different payment feature values. All sub-function channels corresponding to the payment information are combined to obtain a target payment channel of the payment information, and the target payment channel is composed of multiple sub-function channels.

[0069] Specifically, different payment features correspond to a preset sub-function channel list, and each preset sub-function channel list contains sub-function channels corresponding to different payment feature values under the current payment feature. The payment feature value is a specific payment feature content. For example, when the payment feature is a communication protocol, different payment feature values can be communication protocol a, communication protocol b, communication protocol c, and communication protocol d. The sub-function channels corresponding to different payment feature values are different. For example, communication protocol a corresponds to sub-function channel 11, communication protocol b corresponds to sub-function channel 12, communication protocol c corresponds to sub-function channel 13, and communication protocol c corresponds to sub-function channel 14. Sub-function channels belonging to the same preset sub-function channel list have the same prefix number. For example, sub-function channel 11 corresponding to communication protocol a and sub-function channel 12 corresponding to communication protocol b have the same prefix number "1". Using the preset sub-function channel list to determine the sub-function channels corresponding to different payment features can improve the accuracy of determining the sub-function channels. The preset sub-function channel list corresponding to each payment feature can be determined by relevant staff based on historical operation data analysis, and the specific content is not limited in the embodiments of the present application.

[0070] After determining the sub-function channels corresponding to each payment feature included in the payment information, the multiple sub-function channels are combined. The combination method is not limited in the embodiments of the present application. For example, when the sub-function channels corresponding to each payment feature included in the payment information are sub-function channel 11, sub-function channel 22, and sub-function channel 33, the combination method can be sub-function channel 11, sub-function channel 22, and sub-function channel 33, or sub-function channel 11, sub-function channel 33, and sub-function channel 22. As long as the target payment channel formed after combination can meet the demand of each payment feature on the payment channel.

[0071] Step S140: According to the target payment channel corresponding to each payment information, the communication between the corresponding user terminal and the to-be-paid merchant terminal is established, and the order payment operation is completed based on the corresponding target payment channel.

[0072] Specifically, after the payment platform determines the target payment channel corresponding to each payment information, the communication between the user end and the corresponding payment merchant end is established through the target payment channel, so that the user can make an order payment. After the merchant confirms the collection, the feedback confirmation information can be fed back to the payment platform, and the payment platform can forward the feedback confirmation information to the user end. Since the feedback confirmation information does not contain important data content, other data transmission channels other than the target payment channel can be used in the feedback confirmation information process to reduce the use frequency of the target payment channel and facilitate subsequent order operation tasks.

[0073] For the embodiments of the present application, in the process of processing payment operations, asynchronous processing is realized by returning payment acceptance information and writing payment information into an asynchronous processing queue for subsequent payment processing. Since different payment information may correspond to different interface specifications, data formats, communication protocols, etc. in the face of diversified payment processes, it may take a long time to determine the target payment channel corresponding to each payment information, thereby affecting the payment processing efficiency. If synchronous processing is used, the payment operation of the next payment information cannot be started until the payment operation corresponding to the previous payment information is completed, which may result in a long overall payment processing period and may affect the user's payment experience. Asynchronous processing can handle diversified payment requests first and then process them based on the asynchronous processing queue, thereby reducing the user's waiting time. In addition, the target payment channel is determined based on the payment characteristics contained in different payment information, that is, the appropriate payment channel can be selected according to the specific circumstances of different payment information, thereby improving the intelligent degree and accuracy of determining the target payment channel, and thereby facilitating the improvement of the efficiency in the payment operation process.

[0074] Further, in order to improve the accuracy and speed of determining the target payment channel corresponding to each payment information, all sub-function channels corresponding to each payment information are combined to obtain the target payment channel of each payment information, which can specifically include steps S1-S4, as shown in Figure 2

[0075] Step S1: identifying the writing time when each payment information is written into the asynchronous processing queue and the payment identifier contained in each payment information, and determining the expected operation time corresponding to each payment information based on each payment identifier and the payment time mapping relationship. The payment time mapping relationship is the corresponding relationship between the payment identifier and the expected operation time.

[0076] Specifically, the writing time when each payment information is written into the corresponding asynchronous processing queue can be determined through log information. The earlier the writing time, the higher the processing demand of the corresponding payment information. In order to improve the user experience of the user end and the corresponding payment merchant end, the payment information needs to be sorted and processed according to the writing time of each payment information when processing the payment information.​

[0077] Different payment identifiers correspond to different payment scales, and the size and complexity of the payment order amount can affect the payment duration. For example, large payments or orders involving multiple goods may require more time to check and confirm payment information. Therefore, when determining the expected operation duration, the payment identifier of the payment information needs to be considered and analyzed. The larger the payment amount and the more the number of goods orders, the larger the corresponding payment scale. When determining the payment scale corresponding to the payment information, the payment amount and the number of goods orders contained in the payment information can be identified first, and then the payment scale corresponding to the payment information is determined through the scale mapping relationship. The scale mapping relationship contains the payment amount and the number of goods orders corresponding to different payment scales. The specific content is not limited in the embodiments of the present application.

[0078] After determining the payment identifier, the expected operation duration corresponding to each payment identifier can be directly determined according to the payment duration mapping relationship, i.e., the expected operation duration corresponding to each payment information can be directly determined. The payment duration mapping relationship contains the expected operation duration corresponding to different payment identifiers. The specific content is not limited in the embodiments of the present application.

[0079] Step S2: determining the access time corresponding to each sub-function channel according to the expected operation duration corresponding to each payment information and the write time.

[0080] Specifically, since the payment information is written into the asynchronous processing queue, the actual processing time of the payment information may be later than the generation time of the payment information. When determining the access time of each payment information in the asynchronous processing queue, the first written payment information can be determined according to the write time of each payment information, and the delay processing duration is determined based on the number of payment information contained in the asynchronous processing queue. Since the more the number of payment information, the more the amount of data analysis before determining the target payment channel, the more the number of payment information contained in the asynchronous processing queue, the longer the delay processing duration corresponding to the delay processing duration. There is a corresponding relationship between the number of payment information and the delay processing duration. According to the corresponding relationship, the delay processing duration corresponding to each asynchronous processing queue can be determined. The access time corresponding to the first written payment information is determined first, and the write time of the first written payment information is taken as the starting time. After the delay processing duration, the access time corresponding to the first written payment information is determined. Then, the access time of the next written payment information is determined after the expected operation duration of the first written payment information, for example, the write time of the first written payment information a is 10:00, and the delay processing duration is 1 minute. The access time of the payment information a is 10:01. When the expected operation duration of the payment information a is 2 minutes, the access time of the next written payment information b is 10:03.

[0081] Step S3: generating an execution time wheel corresponding to each preset sub-function channel list according to the access time of each sub-function channel, the preset sub-function channel list to which each sub-function channel belongs, and the preset execution time wheel corresponding to each preset sub-function list, each preset execution time wheel containing a plurality of time bins.

[0082] Specifically, since the sub-function channels included in different preset sub-function lists are different, and the access time corresponding to each sub-function channel may also be different, it is necessary to construct a corresponding execution time wheel for each preset sub-function list, and then simultaneously execute a plurality of execution time wheels to form the target payment channel of each payment information. Since the sub-function channels included in the same sub-function channel list have similarity in use, the preset execution time wheel is determined for each preset sub-function list, which facilitates to reduce the modification range of the preset execution time wheel, thereby facilitating to improve the rate when determining the execution time wheel. Each execution time wheel contains a plurality of time bins, each time bin corresponding to a sub-function channel. If the pointer included in the execution time wheel at the current time points to a certain time bin, it represents that the sub-function channel in the corresponding time bin needs to be accessed at the current time.

[0083] Among them, in order to improve the processing efficiency, when generating an execution time wheel corresponding to each preset sub-function channel list according to the access time of each sub-function channel, the preset sub-function channel list to which each sub-function channel belongs, and the preset execution time wheel corresponding to each preset sub-function list, specifically can include:

[0084] According to the access time of each payment information, determine the to-be-executed sub-function channel of each time bin in each preset execution time wheel; according to the access time of each sub-function channel corresponding to each preset sub-function channel list, determine the execution duration of the time bin corresponding to each sub-function channel; according to the execution duration of each time bin and the to-be-executed sub-function channel, generate the execution time wheel of each preset sub-function channel list.

[0085] Specifically, the access time of the payment information, that is, the access time of the payment information in the execution of the payment operation process all sub-function channels, according to the access time of each sub-function channel, the sub-function channels belonging to the different preset sub-function channel list are written into the corresponding time bin, because the number of payment information contained in the asynchronous processing queue is different, and different payment information may use the same sub-function channel, therefore, in the execution time wheel corresponding to each preset sub-function channel list, the number of time bins containing sub-function channels is different, for example, the asynchronous processing queue contains 4 payment information, payment information a, payment information b, payment information c and payment information d, the payment characteristics contained in the payment information are interface specification 1, data format 2, communication protocol 3 and risk monitoring 4, wherein each payment characteristic corresponds to a preset sub-function channel list, the preset sub-function list corresponding to interface specification 1 contains sub-function channel 11, sub-function channel 12, sub-function channel 13 and sub-function channel 14, each sub-function channel corresponds to a payment characteristic value, similarly, the preset sub-function list corresponding to data format 2 contains sub-function channel 21, sub-function channel 22, sub-function channel 23 and sub-function channel 24, communication protocol and risk monitoring also correspond to a preset sub-function list, the payment information contained in the asynchronous processing queue may traverse the sub-function channel corresponding to each payment characteristic, that is, payment information 1 needs to use sub-function channel 11, payment information 2 needs to use sub-function channel 12, payment information 3 needs to use sub-function channel 13, and payment information 4 needs to use sub-function channel 14, but different payment information may also reuse sub-function channel, for example, payment information 1 needs to use sub-function channel 11, payment information 2 needs to use sub-function channel 11, payment information 3 needs to use sub-function channel 12, and payment information 4 needs to use sub-function channel 13, the specific use needs to be selected and determined according to the payment characteristic value of each payment characteristic in each payment information. Therefore, when operating the payment information in the asynchronous processing queue, the execution time wheel corresponding to the preset sub-function channel list may only contain part of the sub-function channels in the preset sub-function list.

[0086] The sub-function channel corresponding to the determined time bin can be determined as a to-be-executed sub-function channel. Since different payment information can use the same sub-function channel, when determining the execution duration of the time bin corresponding to the to-be-executed sub-function channel, comparison and analysis of multiple payment information are required. For example, payment information a needs to use sub-function channel 11, and the access time is 10:00; payment information b needs to use sub-function channel 11, and the access time is 10:02; payment information c needs to use sub-function channel 12, and the access time is 10:04. It can be determined that the execution time period of sub-function channel 11 is 10:00-10:04, that is, the execution duration of the time bin corresponding to sub-function channel 11 is 4 minutes.

[0087] According to the execution duration of each time bin and the corresponding to-be-executed sub-function channel, an execution time wheel is generated, as shown in Figure 3 Figure 3 Figures (a) and (b) are included in the figure, wherein figure (a) can represent the execution time wheel corresponding to the preset sub-function list of interface specification 1, and figure (b) can represent the execution time wheel corresponding to the preset sub-function list of data format 2. There is the same sub-function channel 11 in payment information 1 and payment information 2. When the pointer corresponding to the current time points to the time bin corresponding to sub-function channel 11 in figure (a), the pointer in the corresponding figure (b) points to sub-function channel 22. Based on sub-function channel 11 and sub-function channel 22, the target payment channel corresponding to payment information 1 is determined. As time passes, the pointer of the execution time wheel in figure (a) points to the time bin corresponding to sub-function channel 11 at 10:02, while the pointer of the execution time wheel in figure (b) has already pointed to the time bin corresponding to sub-function channel 22. At this time, the target payment channel of payment information 2 can be determined based on sub-function channel 11 and sub-function channel 21.

[0088] When the number of sub-function channels is less than the number of time bins, the execution time wheel can include idle time bins. When the number of sub-function channels is higher than the number of time bins, the data written in the executed time bin can be overwritten by data overwriting. The establishment of the execution time wheel helps to reduce manual intervention in the process of determining the target payment channel, thereby facilitating the improvement of processing efficiency.

[0089] Step S4: Based on the access time of each payment information and each execution time wheel, the target payment channel corresponding to each payment information is obtained.

[0090] Specifically, the sub-function channels that need to be combined in each execution time wheel are determined according to the access time of each payment information, and then the target payment channel corresponding to the payment information is obtained by connecting each sub-function channel.

[0091] ​Further, for any payment information, if it is detected that the current time is the access time of the payment information, the execution time bin corresponding to the access time of each execution time wheel is obtained; the to-be-executed sub-function channel corresponding to each execution time bin is identified, and the to-be-executed sub-function channel corresponding to each execution time bin is combined.

[0092] Specifically, the execution time bin is the time bin pointed to by the current time pointer in each execution time wheel, the to-be-executed sub-function channel corresponding to each execution time bin is obtained, and the target payment channel of the payment information can be generated after the multiple sub-function channels are connected. When combining the multiple to-be-executed sub-function channels, the combination can be performed in sequence, or the combination can be performed after sorting according to importance. The specific combination manner is not limited in the embodiments of the present application.

[0093] By matching the current time with the access time corresponding to each execution time bin in the execution time wheel, the execution time bin that needs to be accessed is determined, that is, the sub-function channel that needs to be accessed is determined. Only when the current time is consistent with the access time, the corresponding sub-function channel can be combined. The time matching facilitates to improve the accuracy of determining the to-be-executed sub-function channel, thereby facilitating to improve the accuracy of the channel combination result.

[0094] Further, in order to ensure the continuity of the payment process, the communication between the corresponding user terminal and the to-be-paid merchant terminal is established according to the target payment channel corresponding to the payment information, and the order payment operation is completed based on the corresponding target payment channel. Subsequently, the following steps are further included.

[0095] The order payment operation process is detected in real time, and the operation characteristics are collected according to a preset frequency. When an abnormal operation characteristic appears in the operation characteristics, a backup payment channel is started, and the backup payment channel is determined as the target payment channel of the to-be-paid order. The abnormal operation characteristic includes network delay and payment channel maintenance.

[0096] Specifically, the payment platform can supervise the order payment operation process corresponding to each payment information, and can collect the operation characteristics generated in the operation process. The operation characteristics include execution network speed, execution channel running date, etc. When the execution network speed is higher than the preset standard network speed, it indicates that there may be network delay in the order payment operation process. The specific preset standard network speed is not limited in the embodiments of the present application, and can be uploaded by relevant staff. When the execution channel running date is located in the maintenance time period, it indicates that the payment channel maintenance exception may occur in the order payment operation process.

[0097] The backup payment channel can be determined by relevant staff in advance and uploaded to the payment platform. If the target payment channel corresponding to the payment information has abnormal operation characteristics during the payment operation process, the backup payment channel is started. The adaptation degree between the backup payment channel and the payment information is lower than the adaptation degree between the payment information and the corresponding target payment channel, but the order payment can also be completed through the backup payment channel. Since the payment amount, payment user identity, payment time and the like of the payment information are considered and analyzed in the process of determining the target payment channel, the probability of payment information leakage or tampering is small when the order payment is performed through the target payment channel. The backup payment channel can only ensure the completion of the order payment and cannot provide high-level security protection for the payment information during the payment process. Therefore, the backup payment channel is started only when the target payment channel is abnormal, and the backup payment channel is switched to in time after the abnormality is found, so as to facilitate the continuity of the payment process.

[0098] In an embodiment of the present application, a payment platform is provided, as shown in Figure 4 Figure 4 The payment platform 400 shown in the figure includes a processor 401 and a memory 403. The processor 401 and the memory 403 are connected, such as through a bus 402. Optionally, the payment platform 400 can also include a transceiver 404. It should be noted that in actual application, the transceiver 404 is not limited to one, and the structure of the payment platform 400 does not constitute a limitation on the embodiments of the present application.

[0099] The processor 401 can be a CPU (Central Processing Unit, central processor), a general-purpose processor, a DSP (Digital Signal Processor, digital signal processor), an ASIC (Application Specific Integrated Circuit, application specific integrated circuit), an FPGA (Field Programmable Gate Array, field programmable gate array) or other programmable logic devices, transistor logic devices, hardware components or any combination thereof. It can realize or execute various exemplary logic blocks, modules and circuits described in combination with the disclosure content of the present application. The processor 401 can also be a combination of computing functions, such as one or more microprocessor combinations, combinations of DSP and microprocessor, etc.

[0100] ​The bus 402 can include a path for transmitting information between the above-mentioned components. The bus 402 can be a PCI (Peripheral Component Interconnect) bus or an EISA (Extended Industry Standard Architecture) bus, or the like. The bus 402 can be divided into an address bus, a data bus, a control bus, and the like. For convenience of representation, Figure 4 Only one line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0101] The memory 403 can be a ROM (Read Only Memory) or other type of static storage device that can store static information and instructions, a RAM (Random Access Memory) or other type of dynamic storage device that can store information and instructions, an EEPROM (Electrically Erasable Programmable Read Only Memory), a CD-ROM (Compact Disc Read Only Memory) or other optical disk storage, a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to this.

[0102] The memory 403 is used to store application program codes for implementing the scheme of the present application, and is controlled by the processor 401 to execute. The processor 401 is used to execute the application program codes stored in the memory 403 to realize the content shown in the foregoing method embodiments.

[0103] The payment platform can include, but is not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Tablet Personal Computers), PMPs (Portable Multimedia Players), and vehicle-mounted terminals (such as vehicle-mounted navigation terminals), and fixed terminals such as digital TVs and desktop computers. It can also be a server or the like. Figure 4 The payment platform shown is only an example and should not limit the functions and use range of the embodiments of the present application.

[0104] The embodiments of the present application provide a computer readable storage medium, and the computer readable storage medium stores a computer program. When the computer program runs on a computer, the computer can execute the corresponding content in the foregoing method embodiments.

[0105] The embodiments of the present application provide a computer program product, which comprises a computer program, and the computer program is executed by a processor to realize the method in any of the above embodiments.

[0106] It should be understood that, although each step in the flowchart of the accompanying drawings is shown in sequence according to the indication of the arrow, these steps are not necessarily executed in sequence according to the indication of the arrow. Unless explicitly stated herein, the execution of these steps is not strictly limited in sequence, and they can be executed in other sequences. Moreover, at least part of the steps in the flowchart of the accompanying drawings can comprise multiple sub-steps or multiple stages, which are not necessarily executed at the same time, but can be executed at different times, and the execution sequence is not necessarily sequential, but can be executed in rotation or alternation with at least part of other steps or sub-steps or stages of other steps.

[0107] The above only describes some embodiments of the present application, and it should be pointed out that, for those skilled in the art, without departing from the principles of the present application, a number of improvements and refinements can be made, and these improvements and refinements should also be regarded as the protection scope of the present application.

Claims

1. A payment interface management method characterized by comprising: The application comprises the following technical scheme: When receiving the payment information sent by the user terminal, payment receiving information is sent to the user terminal and the corresponding payment merchant terminal according to the payment information, and the payment information is written into the asynchronous processing queue corresponding to the payment merchant terminal, the payment information including the order to be paid, the payment method and the payment merchant, and the asynchronous processing queue is used for storing payment information; When the number of orders to be paid contained in the asynchronous processing queue corresponding to the payment merchant exceeds a preset number threshold, the payment characteristics contained in each payment information are identified, the payment characteristics including interface specification, data format, communication protocol and risk monitoring; Based on the payment characteristics contained in all payment information, the target payment channel corresponding to each payment information is determined; According to the target payment channel corresponding to each payment information, the communication between the corresponding user terminal and the payment merchant terminal is established, and the order payment operation is completed based on the corresponding target payment channel; Wherein, based on the payment characteristics contained in all payment information, the target payment channel corresponding to the payment information is determined, comprising: Identifying the payment characteristic value corresponding to each payment characteristic from the payment information, and determining the sub-function channel corresponding to each payment characteristic value from the preset sub-function channel list corresponding to each payment characteristic, the preset sub-function channel list containing the sub-function channel corresponding to different payment characteristic values; Combining all sub-function channels corresponding to the payment information to obtain the target payment channel of the payment information, the target payment channel being composed of multiple sub-function channels; Wherein, combining all sub-function channels corresponding to the payment information to obtain the target payment channel of each payment information, comprising: Identifying the writing time when each payment information is written into the asynchronous processing queue and the payment identifier contained in each payment information, and determining the expected operation time corresponding to each payment information based on the payment identifier and the payment time length mapping relationship, the payment time length mapping relationship being the corresponding relationship between the payment identifier and the expected operation time; According to the expected operation time corresponding to each payment information and the writing time, the access time corresponding to each sub-function channel is determined; According to the access time of each sub-function channel, the preset sub-function channel list to which each sub-function channel belongs, and the preset execution time wheel corresponding to each preset sub-function list, an execution time wheel corresponding to each preset sub-function channel list is generated, each preset execution time wheel containing multiple time bins; Based on the access time corresponding to each payment information and each execution time wheel, the target payment channel corresponding to each payment information is obtained by channel combination.

2. The payment interface management method of claim 1, wherein, According to the access time of each payment information, the to-be-executed sub-function channel of each time bin in each preset execution time wheel is determined; according to the access time of each sub-function channel corresponding to each preset sub-function channel list, the execution time of the corresponding time bin of each sub-function channel is determined. ​ According to the execution duration of each time bin and the to-be-executed sub-function channel, an execution time wheel of each preset sub-function channel list is generated.

3. The payment interface management method of claim 1, wherein, Based on the access time and the execution time wheel corresponding to each payment information, the channel combination is performed, including: If it is detected that the current time is the access time of the payment information, the execution time bin corresponding to each execution time wheel at the access time is obtained; The to-be-executed sub-function channel corresponding to each execution time bin is identified, and the to-be-executed sub-function channel corresponding to each execution time bin is combined.

4. The payment interface management method of claim 1, wherein, According to the target payment channel corresponding to each payment information, the communication between the corresponding user terminal and the to-be-paid merchant terminal is established, and the order payment operation is completed based on the corresponding target payment channel, and then further including: The order payment operation process is detected in real time, and the operation characteristics are collected according to a preset frequency; When the abnormal operation characteristics appear in the operation characteristics, the standby payment channel is started, and the standby payment channel is determined as the target payment channel of the to-be-paid order, and the abnormal operation characteristics include network delay and payment channel maintenance.

5. A payment hub, characterized in that, The payment platform includes: At least one processor; Memory; At least one application program, wherein the at least one application program is stored in the memory and is configured to be executed by the at least one processor, and the at least one application program is configured to execute the payment docking management method in any one of claims 1-4.

6. A computer-readable storage medium, characterized in that, Including: The computer program is stored and can be loaded and executed by the processor to perform the payment docking management method in any one of claims 1-4.

7. A computer program product, characterised in that, The computer program is executed by the processor to implement the steps of the payment docking management method in any one of claims 1-4.

Images