CN120181965A

CN120181965A - Order data acquisition method, system, device, reconciliation platform and storage medium

Info

Publication number: CN120181965A
Application number: CN202510303812.1A
Authority: CN
Inventors: 袁会亮
Original assignee: Beijing QIYI Century Science and Technology Co Ltd
Current assignee: Beijing QIYI Century Science and Technology Co Ltd
Priority date: 2025-03-14
Filing date: 2025-03-14
Publication date: 2025-06-20

Abstract

The embodiment of the invention provides a method, a system and a device for acquiring order data, a platform to be reconciled and a storage medium, and relates to the technical field of electronic payment. The method comprises the steps of obtaining a platform identifier of a payment platform needing to obtain order data currently as a platform identifier to be filled currently, filling the platform identifier to be filled currently into a preset code template to obtain a current order obtaining code, operating the current order obtaining code to generate an order obtaining request for obtaining the current order data, and sending the current generated order obtaining request to a payment center so that the payment center sends the current order data to a platform to be checked based on the received order obtaining request, wherein the current order data is order data which is paid through the payment platform needing to obtain the order data currently, and receiving the current order data sent by the payment center. Order data acquisition efficiency can be improved.

Description

Order data acquisition method, system and device, to-be-reconciled platform and storage medium

Technical Field

The present invention relates to the field of electronic payment technologies, and in particular, to a method, a system, a device, a platform to be reconciled, and a storage medium for acquiring order data.

Background

In the scene of online shopping, when a user makes an order in a shopping platform, the user can select a target payment mode to be used from payment modes supported by the shopping platform to pay. The shopping platform may send the user's order data to the payment center, which forwards the order data to the target payment platform providing the target payment means. It is apparent that the user's order data can be recorded both locally on the shopping platform and in the payment centre. In order to ensure the fund safety, the shopping platform can acquire order data from the payment center, and then check the recorded order data and the acquired order data, namely check account with the payment center, so as to check out abnormal orders with problems of repeated payment, incorrect payment and the like.

In the related art, for each payment method supported by the shopping platform, a technician may write a code based on an identification of the payment method. Running the compiled code, the shopping platform may generate a request indicating the payment means and send the request to the payment center. After receiving the request, the payment center can search the order data paid by the payment mode from the recorded order data, and then send the searched order data to the shopping platform.

Therefore, when the shopping platform adds the supported payment mode, the technician needs to write the code based on the identifier of the newly added payment mode, and then obtains the order data for payment by the newly added payment mode from the payment center based on the newly written code. Obviously, this may result in inefficient acquisition of order data.

Disclosure of Invention

The embodiment of the invention aims to provide a method, a system and a device for acquiring order data, a platform to be reconciled and a storage medium, so as to improve the acquisition efficiency of the order data. The specific technical scheme is as follows:

in a first aspect of the present invention, there is first provided an order data obtaining method, where the method is applied to a to-be-reconciled platform for providing an ordering service in a server, and the method includes:

acquiring a platform identifier of a payment platform of which the order data is required to be acquired currently as a current platform identifier to be filled;

Filling a current platform identifier to be filled in a preset code template to obtain a current order acquisition code, wherein the code template is used for generating an order acquisition request for acquiring order data and sending the generated order acquisition request to a payment center;

Running a current order acquisition code to generate an order acquisition request for acquiring current order data, and sending the current order acquisition request to the payment center so that the payment center sends the current order data to the platform to be checked based on the received order acquisition request, wherein the current order data is order data paid through a payment platform which needs to acquire the order data currently;

and receiving current order data sent by the payment center.

Optionally, the method further comprises the step of returning to execute the record sequence of the platform identifications of the payment platforms currently supported by the to-be-checked platform, and determining the current to-be-filled platform identifications until the order data of the payment platforms currently supported by the to-be-checked platform is acquired.

Optionally, when a modification instruction for the recording sequence is received, modifying the recording sequence according to a modification mode carried in the modification instruction, wherein the modification mode comprises at least one of adding a platform identifier in the recording sequence, deleting a designated platform identifier in the recording sequence and adjusting the sequence of the platform identifiers in the recording sequence.

Optionally, the step of acquiring the platform identifier of the payment platform currently required to acquire the order data as the current platform identifier to be filled includes acquiring the platform identifier of the payment platform currently required to acquire the order data as the current platform identifier to be filled when the preset acquisition period is reached each time under the condition that an order acquisition instruction carrying the preset acquisition period is received.

Optionally, the step of filling the current platform identifier to be filled with a preset code template to obtain a current order acquisition code includes the step of filling the current platform identifier to be filled with a preset code template in a default time period to obtain the current order acquisition code, wherein the default time period is a time period between the moment when the current order data to be paid by a payment platform needing to acquire the order data is acquired last time and the current moment, the step of running the current order acquisition code to generate an order acquisition request for acquiring the current order data and sending the current generated order acquisition request to the payment center to enable the payment center to send the current order data to the platform to be checked based on the received order acquisition request, and the step of running the current order acquisition code to generate an order acquisition request for acquiring the current order data in the default time period and sending the current generated order acquisition request to the payment center to enable the payment center to send the current order data in the default time period to the platform to be checked based on the received order acquisition request.

Optionally, the step of filling the current platform identifier to be filled with a preset code template to obtain a current order acquisition code includes filling the current platform identifier to be filled with and the identifier of the current recorded interface with the preset code template to obtain the current order acquisition code, the step of running the current order acquisition code to generate an order acquisition request for acquiring current order data and sending the current order acquisition request to the payment center so that the payment center sends the current order data to the platform to be checked based on the received order acquisition request, and the step of running the current order acquisition code to generate an order acquisition request for acquiring the current order data and sending the current order acquisition request to the payment center through the interface indicated by the identifier of the current recorded interface so that the payment center sends the current order data to the platform to be checked based on the received order acquisition request.

Optionally, an order number and an order amount of an order are recorded in order data, after receiving current order data sent by the payment center, the method further comprises searching for to-be-checked order data paid through the payment platform from all order data recorded locally by the to-be-checked platform for each payment platform receiving the order data, judging whether to-be-checked order data with the same order number as the order number recorded by the to-be-checked order data exists in the received order data of the payment platform, determining that the to-be-checked order data is abnormal if the to-be-checked order data does not exist, judging whether the order amount recorded in the to-be-checked order data is consistent with the order amount recorded in the to-be-checked order data if the order amount recorded in the to-be-checked order data is consistent with the order amount recorded in the to-be-checked order data, determining that the to-be-checked order data is inconsistent with the order amount recorded in the to-be-checked order data if the to-be-checked order number is not consistent with the order amount recorded in the to-checked order data, and determining that the to-be-checked data is abnormal if the to-be-checked data is not consistent with the order amount recorded in the to-be-checked order data exists.

In a second aspect of the present invention, there is further provided an order data acquisition system, the order data acquisition system including a to-be-reconciliation platform and a payment center for providing an order placing service in a server side, wherein:

the to-be-reconciled platform is configured to execute the order data acquisition method according to any one of the first aspect;

the payment center is used for sending order data to the platform to be checked based on the received order acquisition request sent by the platform to be checked.

In a third aspect of the present invention, there is also provided an order data obtaining apparatus, where the apparatus is applied to a to-be-reconciled platform for providing an order placing service in a server, and the apparatus includes:

the first identifier acquisition module is used for acquiring a platform identifier of a payment platform which needs to acquire order data currently, and taking the platform identifier as a current platform identifier to be filled;

The code acquisition module is used for filling the current platform identification to be filled into a preset code template to obtain a current order acquisition code, wherein the code template is used for generating an order acquisition request for acquiring order data and sending the generated order acquisition request to a payment center;

The code running module is used for running the current order acquisition code to generate an order acquisition request for acquiring current order data, and sending the current order acquisition request to the payment center so that the payment center can send the current order data to the platform to be checked based on the received order acquisition request, wherein the current order data is order data which is paid through a payment platform which needs to acquire the order data currently;

and the receiving module is used for receiving the current order data sent by the payment center.

Optionally, the first identifier obtaining module is specifically configured to determine, according to a recording sequence of platform identifiers of each payment platform currently supported by the platform to be checked, a current platform identifier to be filled;

the device further comprises a second identifier acquisition module, a second identifier acquisition module and a third identifier acquisition module, wherein the second identifier acquisition module is used for returning to execute the step of determining the current platform identifier to be filled according to the record sequence of the platform identifier of each payment platform currently supported by the platform to be checked after the receiving module executes receiving the current order data sent by the payment center, until the order data of each payment platform currently supported by the platform to be checked is acquired.

Optionally, the device further comprises an adjustment module, when receiving a modification instruction for the recording sequence, modifying the recording sequence according to a modification mode carried in the modification instruction, wherein the modification mode comprises at least one of adding a platform identifier in the recording sequence, deleting a designated platform identifier in the recording sequence, and adjusting the sequence of the platform identifiers in the recording sequence.

Optionally, the first identifier obtaining module is specifically configured to obtain, when the preset obtaining period is reached each time when an order obtaining instruction carrying the preset obtaining period is received, a platform identifier of a payment platform that needs to obtain the order data currently, as a current platform identifier to be filled.

The code obtaining module is specifically configured to fill a preset code template with a current platform identifier to be filled and a default time period to obtain a current order obtaining code, wherein the default time period is a time period between a time when the current order data to be paid through a payment platform requiring to obtain the order data is obtained last time and a current time, and the code running module is specifically configured to run the current order obtaining code to generate an order obtaining request for obtaining the current order data in the default time period, and send the current order obtaining request to the payment center to enable the payment center to send the current order data in the default time period to the platform to be reconciled based on the received order obtaining request.

The code running module is specifically used for running the current order acquisition code to generate an order acquisition request for acquiring current order data, and sending the current generated order acquisition request to the payment center through the interface indicated by the identifier of the current recorded interface so that the payment center sends the current order data to the platform to be checked based on the received order acquisition request.

Optionally, an order number and an order amount of an order are recorded in order data, the device further comprises a checking module, a checking module and a checking module, wherein the checking module is used for executing, after the receiving module executes receiving current order data sent by the payment center, executing checking of the order amount recorded in the order data to be checked, from all the order data recorded locally by the checking platform, checking of the order data to be checked, checking whether the recorded order number is consistent with the order number recorded in the order data to be checked, determining that the checking data is abnormal if the checking data is not present, judging whether the order amount recorded in the order data to be checked is consistent with the order amount recorded in the order data to be checked if the checking data is present, determining that the checking data is not consistent with the order amount recorded in the order data to be checked if the checking data is not present, and determining that the checking data is not consistent with the abnormal if the checking data is present.

In a fourth aspect of the present invention, a to-be-reconciled platform is provided, which includes a processor, a communication interface, a memory and a communication bus, where the processor, the communication interface, the memory complete communication with each other through the communication bus, the memory is used for storing a computer program, and the processor is used for implementing any one of the order data acquisition methods described in the first aspect when executing the program stored in the memory.

In yet another aspect of the present invention, there is also provided a computer readable storage medium having a computer program stored therein, which when executed by a processor, implements any of the order data acquisition methods described above.

In yet another aspect of the invention, there is also provided a computer program product containing instructions which, when run on a computer, cause the computer to perform any of the order data acquisition methods described above.

The order data acquisition method comprises the steps of obtaining a platform identifier of a payment platform needing to acquire order data currently in a server side by a to-be-reconciled platform used for providing order service, filling a preset code template into the current to-be-filled platform identifier to obtain a current order acquisition code, generating an order acquisition request used for acquiring the order data by the code template, sending the generated order acquisition request to a payment center, running the current order acquisition code to generate the order acquisition request used for acquiring the current order data, sending the current generated order acquisition request to the payment center, and sending the current order data to the to-be-reconciled platform by the payment center based on the received order acquisition request, wherein the current order data is the order data which is paid by the payment platform needing to acquire the order data currently, and receiving the current order data sent by the payment center.

Based on the above processing, after obtaining the current platform identifier to be filled of the payment platform which needs to obtain the order data, the to-be-checked platform in the server side fills the current platform identifier to be filled into the preset code template to obtain the current order obtaining code, and obtains the current order data from the payment center by running the current order obtaining code. Obviously, when the payment mode supported by the reconciliation platform is changed, namely when the payment platform for acquiring order data is changed, only the acquired platform identification is required to be changed, and then a corresponding order acquisition code can be automatically generated based on the acquired platform identification without re-writing the code, so that the order data acquisition efficiency can be improved.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below.

FIG. 1 is a first flowchart of a method for acquiring order data according to an embodiment of the present invention;

FIG. 2 is a second flowchart of an order data acquisition method according to an embodiment of the present invention;

FIG. 3 is a third flowchart of an order data acquisition method according to an embodiment of the present invention;

FIG. 4 is a block diagram of an order data acquisition device according to an embodiment of the present invention;

fig. 5 is a block diagram of a to-be-reconciled platform provided in an embodiment of the invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be described below with reference to the accompanying drawings in the embodiments of the present invention.

In the scene of online shopping, when a user makes an order in a shopping platform, the user can select a target payment mode to be used from payment modes supported by the shopping platform to pay. The shopping platform may send the user's order data to the payment center, which forwards the order data to the target payment platform providing the target payment means. Obviously, order data may be recorded both locally on the shopping platform and in the payment center. In order to ensure the fund security, the shopping platform (i.e. the platform to be checked out in the subsequent embodiment) may check out with the payment center to check out abnormal orders with problems of repeated payment, incorrect payment, etc. In the related art, for each payment mode supported by the shopping platform, a technician may write a code based on the identification of the payment mode, and order data for payment through the payment mode may be acquired from a payment center based on the code written by the technician. For example, for payment method 1 supported by shopping platform A, the platform identity of payment platform 1 providing payment method 1 is mall_A. The technical staff writes a code 1 based on the mark 'mall_A', runs the code 1, the shopping platform A generates and sends a request 1 carrying the mark 'mall_A' to the payment center, after the payment center receives the request 1, the payment center searches the order data corresponding to the mark 'mall_A' (i.e. the order data paid in the payment mode 1) from the recorded order data, and then sends the searched order data to the shopping platform A.

Therefore, when the shopping platform adds the supported payment mode, the technician needs to write the code based on the identifier of the newly added payment mode, and then obtains the order data for payment by the newly added payment mode from the payment center based on the newly written code. If the payment method 2 supported by the shopping platform a is newly added, and the platform identifier of the payment platform 2 providing the payment method 2 is mall_a_plus, a technician needs to write the code 2 based on the identifier "mall_a_plus" and run the code 2, and the shopping platform a generates and sends a request 2 carrying the identifier "mall_a_plus" to the payment center. Thus, the subsequent payment center can send order data for payment by payment means 2 to shopping platform a based on request 2. Obviously, this may result in inefficient acquisition of order data.

In order to solve the above problems, the embodiment of the present invention provides an order data obtaining method, which is applied to a to-be-reconciled platform for providing a billing service in a server, that is, the to-be-reconciled platform can support a billing operation of a user. If the user can purchase the product in the mall platform, the mall platform can be the platform to be checked out, and if the user can purchase the browsing permission of the video in the video platform, the video platform can also be the platform to be checked out. The invention is not limited to a particular type of platform to be reconciled.

The platform identification of the payment platform which needs to acquire the order data at present is acquired by the platform to be checked, and after the platform identification is taken as the current platform identification to be filled, the current platform identification to be filled can be filled into a preset code template, so that a current order acquisition code is obtained. The code template is used for generating an order acquisition request for acquiring order data and sending the generated order acquisition request to the payment center. Correspondingly, the current order acquisition code is operated, the to-be-checked platform can generate an order acquisition request for acquiring current order data, and the current generated order acquisition request is sent to the payment center. The payment center may send current order data to the reconciliation platform based on the received order acquisition request. The current order data is order data paid through a payment platform which needs to acquire the order data currently. Further, the to-be-reconciled platform may receive current order data sent by the payment center. Thus, the to-be-reconciled platform acquires the current order data from the payment center. Obviously, when the payment mode supported by the platform to be checked out is changed, namely, when the payment platform for acquiring order data is changed, the platform to be checked out only needs to change the acquired platform identification, and then a corresponding order acquisition code can be automatically generated based on the acquired platform identification without re-writing the code, so that the order data acquisition efficiency can be improved.

Referring to fig. 1, fig. 1 is a first flowchart of an order data obtaining method according to an embodiment of the present invention. The order data acquisition method is applied to a to-be-checked platform for providing an order service in a server, and can comprise the following steps:

S101, acquiring a platform identifier of a payment platform which needs to acquire order data currently, and taking the platform identifier as a current platform identifier to be filled.

S102, filling the current platform identification to be filled in a preset code template to obtain a current order acquisition code.

The code template is used for generating an order acquisition request for acquiring order data and sending the generated order acquisition request to the payment center.

And S103, running a current order acquisition code to generate an order acquisition request for acquiring current order data, and sending the current order acquisition request to a payment center so that the payment center sends the current order data to a platform to be reconciled based on the received order acquisition request.

The current order data is order data paid through a payment platform which needs to acquire the order data currently.

S104, receiving current order data sent by the payment center.

According to the order data acquisition method provided by the embodiment of the invention, after the current platform to be filled identification of the payment platform requiring acquisition of the order data is acquired by the to-be-checked platform in the server side, the current platform to be filled identification is filled into a preset code template to obtain a current order acquisition code, and the current order data is acquired from the payment center by running the current order acquisition code. Obviously, when the payment mode supported by the reconciliation platform is changed, namely when the payment platform for acquiring order data is changed, only the acquired platform identification is required to be changed, and then a corresponding order acquisition code can be automatically generated based on the acquired platform identification without re-writing the code, so that the order data acquisition efficiency can be improved.

For step S101, the to-be-checked-out platform may support multiple payment methods, that is, when the user performs the order-placing operation in the to-be-checked-out platform, any payment platform may be selected from multiple payment platforms to perform payment. And aiming at each payment platform, the order data of the payment platform, namely, the order data of the user when paying through the payment platform when the user performs an order placing operation in the to-be-checked platform.

In some embodiments, for each paymate, the platform identification of that paymate may indicate that paymate, as well as indicating the platform to be reconciled. The platform identifier of the payment platform can be an identifier distributed by a payment center to the payment platform when the payment platform is supported by the reconciliation platform. As with paymate 1 supported by shopping mall A, the identification assigned by the paymate 1 to paymate 1 by the paymate center may be mall_A_1.

In some embodiments, for each paymate, the paymate's platform identification may indicate the paymate, but not the platform to be reconciled. The identity of paymate 1 as supported by shopping platform a may be pay_1. Subsequently, the payment center may obtain a platform identifier of the platform to be reconciled based on the order acquisition request sent by the platform to be reconciled. If the platform to be checked out can package the order acquisition request and the platform identification of the platform to be checked out into a request message, and then send the request message to the payment center.

When the order data of the payment platform needs to be acquired, the platform to be checked can acquire the platform identification of the payment platform which needs to acquire the order data currently. The target platform for short is a platform identifier of the target payment platform, and the target platform identifier for short is a target platform identifier.

In one implementation, a technician may input an order acquisition instruction carrying a target platform identification to a platform to be checked. The platform to be checked can extract the target platform identification carried in the order acquisition instruction.

It will be appreciated that the number of target platform identifiers carried in the order acquisition instructions may be one or more. The invention is not limited in this regard.

The manner in which the technician enters the order acquisition instructions into the reconciliation platform may also include a variety of ways. For example, in order to facilitate the operation of a technician, an operation interface may be displayed in the display interface of the reconciliation platform. The technician can input an order acquisition instruction to the platform to be reconciled by clicking an order acquisition button provided in the operation interface.

In the case that the technician does not indicate a paymate, the target platform identifier carried in the order acquisition instruction may be a platform identifier of each paymate supported by the paymate.

In the case where the technician indicates a paymate, the target platform identifier carried in the order acquisition instruction is the platform identifier of the paymate indicated by the technician. The platform identification of each payment platform supported by the platform to be checked can be displayed in the operation interface, and the technician can select the target platform identification of the target payment platform to be acquired currently from the platform identifications displayed in the operation interface.

Obviously, the manner in which the technician inputs the order acquisition instruction carrying the target platform identifier to the platform to be checked in the actual scene is not limited to this. The invention is not limited to a specific manner in which a technician inputs an order acquisition instruction carrying a target platform identification to a platform to be checked.

In another implementation, the to-be-reconciled platform may periodically obtain order data from the payment center, i.e., the to-be-reconciled platform may periodically obtain the target platform identification. The specific manner in which the reconciliation platform periodically obtains the target platform identification is referred to in the detailed description of the subsequent embodiments.

For step S102, the to-be-reconciled platform may store a pre-written code template locally. The code template may be code written by a technician in a written manner specified by a programming syntax and may be invoked through an interface. Obviously, in the invention, the technician only needs to write the code template, and does not need to write the code for each payment platform.

The code template may include a plurality of platform identification fill-in locations that are not filled with platform identifications. And filling the platform identifier in the code template, namely filling the platform identifier in the platform identifier filling position in the code template, so that the code template filled with the platform identifier becomes a complete and operable code. After the platform identifier is filled in the code template, the code template filled with the platform identifier is operated to realize that an order acquisition request for acquiring order data of the payment platform indicated by the filled platform identifier is generated, and the generated order acquisition request is sent to the payment center.

It can be understood that when the target platform identifier is one, that is, when the current platform identifier to be filled is one, the platform to be checked out fills the target platform identifier into the code template to obtain the current order acquisition code.

When the target platform identifiers are a plurality of, for example, when a technician selects a plurality of platform identifiers in the operation interface, the platform to be checked can sequentially fill the plurality of target platform identifiers into the code template according to a specified sequence. The order as specified may be a selection order by the skilled person. Correspondingly, the platform to be checked can operate the obtained order acquisition code after filling the target platform identification into the code template each time to obtain the order acquisition code so as to obtain the order data of the payment platform indicated by the currently filled target platform identification. Obviously, the current order acquisition code is obtained by filling the target platform identification into the code template.

For step S103 and step S104, the to-be-checked platform may run the current order acquisition code after obtaining the current order acquisition code. If the platform to be reconciled can be provided with a compiling tool for running codes, the compiling tool compiles the current order acquisition codes so as to run the current order acquisition codes. And running the current order acquisition code, namely generating an order acquisition request for acquiring the current order data, and sending the current generated order acquisition request to a payment center. The currently generated order acquisition request may carry the current platform identifier to be filled.

In some embodiments, for each order data recorded by the payment center, the payment center may correspond to record the platform identification of the paymate used when the order data was completed, as well as the platform identification of the platform on which the order data was placed.

At this time, under the condition that the platform identifier of one payment platform can indicate the payment platform and indicate the platform to be checked out, the payment center can extract the current platform identifier to be filled from the received order acquisition request. The payment center can determine the target payment platform and the to-be-reconciled platform indicated by the current to-be-filled platform identifier according to the extracted current to-be-filled platform identifier. And then, according to the determined platform identification of the target payment platform and the platform identification of the platform to be checked out, searching the order data which is ordered in the platform to be checked out and paid through the target payment platform from the recorded order data, namely searching the current order data.

In the case where the platform identifier of one payment platform may indicate the payment platform, but not the platform to be reconciled, the payment center may acquire the platform identifier of the platform to be reconciled based on the order acquisition request sent by the platform to be reconciled. For example, if the platform to be checked out encapsulates the currently generated order acquisition request and the platform identifier of the platform to be checked out into a request message, then the request message is sent to the payment center. The payment center may extract the platform identification of the platform to be reconciled and the currently generated order acquisition request from the request message. According to the extracted platform identification of the platform to be checked and the platform identification of the payment platform carried in the currently generated order acquisition request, the payment center can search the current order data from the recorded order data.

In some embodiments, when a paymate supports a paymate, the paymate may be assigned an identification by the paymate. The assigned identification may indicate a platform to be reconciled and the paymate. For each order data recorded by the payment center, the payment center may correspondingly record an identification assigned to the paymate to which the order data pertains.

At this time, when the platform identifier of one payment platform can indicate the payment platform and indicate the platform to be checked, that is, when the platform identifier is the identifier allocated by the payment center to the payment platform, the payment center extracts the current platform identifier to be filled from the received order acquisition request, and then searches the corresponding recorded order data with the identifier being the current platform identifier to be filled from the recorded order data, that is, searches the current order data.

In the case where the platform identifier of one payment platform may indicate the payment platform, but not the platform to be reconciled, the payment center may acquire the platform identifier of the platform to be reconciled based on the order acquisition request sent by the platform to be reconciled. According to the platform identification of the platform to be checked and the platform identification of the payment platform carried in the received order acquisition request, the payment center can determine the identification distributed by the payment center for the payment platform when the platform to be checked supports the payment platform. And then, searching the corresponding recorded order data identified as the current platform identification to be filled from the recorded order data, namely searching the current order data.

After the payment center finds the current order data, the current order data can be sent to the to-be-checked platform. If the payment center can sequentially send the current order data to the to-be-checked platform according to the order placing time corresponding to the current order data.

Or in order to improve the efficiency of sending the order data to the platform to be reconciled, the payment center may make the current order data into a compressed package according to a designated compression mode, and then send the compressed package to the platform to be reconciled. If the designated compression mode is that a new folder is created and named according to a preset naming mode, the current order data is copied into the folder, and then the folder is compressed by using a zip (compression) mode. For example, the preset naming mode can be naming according to a naming format of 'acquisition time-platform identification-file format'. The compressed package may be named as "2024-01-01_mall_a_pay.csv.zip".

Correspondingly, after the shopping platform A acquires the compressed package sent by the payment center, the compressed package is decompressed according to a decompression mode corresponding to a designated compression mode, and order data in the compressed package are obtained.

It can be understood that, in the case that the number of the payment platforms currently supported by the to-be-reconciliation platform is plural, the to-be-reconciliation platform may decompress each compression packet after acquiring the compression packet corresponding to each payment platform to acquire order data of each payment platform, or the to-be-reconciliation platform may decompress the acquired compression packet after acquiring the compression packet of each payment platform to acquire order data of the payment platform.

In some embodiments, referring to fig. 2, based on fig. 1, step S101 may include the steps of:

s1011, determining the current platform identification to be filled according to the recording sequence of the platform identifications of the payment platforms currently supported by the platform to be checked.

Accordingly, after step S104, the method may further include the steps of:

s105, returning to execute the step of determining the current platform identification to be filled according to the record sequence of the platform identification of each payment platform currently supported by the platform to be checked until the order data of each payment platform currently supported by the platform to be checked is obtained.

Under the condition that order data of all payment platforms currently supported by the to-be-checked-out platform are required to be acquired, in order to acquire the order data of all payment platforms, the to-be-checked-out platform can traverse platform identifiers of all payment platforms currently supported by the to-be-checked-out platform so as to sequentially acquire the order data of all payment platforms currently supported by the to-be-checked-out platform.

Specifically, the platform identifier of each payment platform currently supported by the platform to be checked can be recorded locally by the platform to be checked, the platform to be checked can determine the current platform identifier to be filled according to the recording sequence of the currently recorded platform identifiers, acquire the order data of the payment platform indicated by the current platform identifier to be filled from the payment center based on the current platform identifier to be filled, and then continuously determine the current platform identifier to be filled according to the recording sequence. And so on until the to-be-checked-out platform obtains the order data of each payment platform currently supported by the to-be-checked-out platform.

Illustratively, the platform identification of each paymate currently supported by the to-be-reconciled platform a may be recorded in a data table, as shown in table 1:

TABLE 1

The business party provides a payment platform of a corresponding payment mode, for example, "a payment business party" provides a payment platform of a payment mode ", and the business party may be denoted as partner. The status of a business party may indicate whether or not the to-be-reconciled platform a currently supports the business party. When the state of the business party is valid, the to-be-checked-out platform A currently supports the payment party, and when the state of the business party is invalid, the to-be-checked-out platform A does not currently support the payment party. Based on the table 1, the payment platform currently supported by the to-be-checked platform A comprises an a payment service party, a b payment service party and a d payment service party, namely when the user makes an order in the to-be-checked platform A, the payment mode to be used can be selected from the a payment mode, the b payment mode and the d payment mode. The recording sequence of the platform identification of each payment platform currently supported by the to-be-reconciled platform A is "mall_A", "mall_A_plus" and "A_D".

The first platform identifier in the recording sequence, namely "mall_a", is used as the current platform identifier to be filled. Filling the current platform identifier to be filled into a code template to obtain a current order acquisition code; the current order acquisition code is run to acquire current order data from the payment center. Thus, order data of the payment service party is obtained. Then, the next platform identifier in the recording sequence, namely "mall_a_plus", is used as the current platform identifier to be filled. Further, current order data is obtained from the payment center based on the current platform identification to be filled. Thus, order data of the payment service party is obtained. Then, the next platform identifier in the recording sequence, namely "A_D", is used as the current platform identifier to be filled in. Further, current order data is obtained from the payment center based on the current platform identification to be filled. Thus, order data of the payment service party is obtained. And so on until the to-be-checked-out platform obtains the order data of each payment platform currently supported by the to-be-checked-out platform. Since the platform A to be checked does not support the current C payment mode, i.e. the platform identification based on the C payment service party, i.e. "A_C_pay", is not needed as the current platform identification to be filled.

Based on the processing, the platform to be checked can traverse the platform identification of each payment platform currently supported by the platform to be checked, and sequentially acquire the order data of each payment platform until the order data of each payment platform currently supported by the platform to be checked is acquired. Therefore, the probability that the order data of the payment platform currently supported by the to-be-checked platform is not acquired can be reduced, so that the order data of each payment platform currently supported by the to-be-checked platform can be acquired.

In some embodiments, the method may further comprise the step of, when a modification instruction for the recording order is received, modifying the recording order in a modification manner carried in the modification instruction. The modification mode comprises at least one of adding platform identifiers in the recording sequence, deleting the designated platform identifiers in the recording sequence, and adjusting the sequence of the platform identifiers in the recording sequence.

When the payment platform currently supported by the to-be-checked-out platform is changed, the to-be-checked-out platform can receive a modification instruction for the recording sequence. As based on the foregoing examples, an input box of modification instructions may also be provided in the operator interface, in which a technician may input modification instructions. The technician can input the platform identification of the payment platform newly supported by the reconciliation platform in the input box. Or when the platform identification of each payment platform currently supported by the platform to be checked out is recorded in the data table, the technician can also modify the data recorded in the data table. And the modification mode of the data recorded in the data table, namely the modification mode carried in the modification instruction, is carried out by technicians.

It can be understood that in an actual application scenario, the to-be-reconciled platform can be newly added with a supported payment platform, or can not support a historically supported payment platform any more, and when an order is acquired from a payment center, the acquisition sequence of order data of each payment platform can be adjusted according to service requirements. Thus, the modification manner for the recording order can indicate the above-described various manners.

Specifically, when the payment platform supported by the newly added payment platform is to be checked, the modification mode includes adding the platform identification in the recording sequence, and at this time, the modification instruction carries the platform identification to be added. After the reconciliation platform receives the modification instruction, the platform identifier carried in the modification instruction may be added to the recording sequence, e.g. the platform identifier may be added to the last of the recording sequence.

In some embodiments, the modification may also indicate the recording order corresponding to the platform identity to be added. If the to-be-reconciled platform supports the payment platform 1 newly and the first order data of the payment platform 1 is required to be acquired, the modification mode may indicate that the platform identifier of the payment platform 1 is to be recorded for the first time, and correspondingly, after receiving the modification instruction, the to-be-reconciled platform may directly add the platform identifier of the payment platform 1 to the forefront in the recording sequence.

When the payment platform supported by the history is no longer supported by the platform to be checked, the modification mode comprises deleting the appointed platform identification in the record sequence, and at the moment, the appointed platform identification is carried in the modification instruction. After the reconciliation platform receives the modification instruction, the designated platform identification in the recording order may be removed.

In some embodiments, in the case that the platform identifier of each paymate currently supported by the platform to be checked is recorded in the data table, and the state of each paymate is also recorded in the data table, adding the platform identifier in the recording sequence, and removing the designated platform identifier may be to modify the state of the paymate recorded in the data table. The technician can update the recording sequence only by simple state modification operation, such as modifying '1' to '0', so that order acquisition efficiency can be further improved.

When the acquisition sequence of the order data of each payment platform needs to be adjusted, the modification mode comprises the adjustment of the sequence of the platform identifications in the record sequence, and at this time, the modification instruction can carry the platform identifications of which the sequence needs to be adjusted and the adjusted sequence of the platform identifications. After the checking platform receives the modification instruction, the platform identification carried in the modification instruction can be determined from the record sequence, and then the determined platform identification is moved to the sequence carried in the modification instruction.

Based on the above processing, when receiving the modification instruction for the recording sequence, the to-be-checked platform can update the recording sequence, and then acquire the order data according to the updated recording sequence, that is, acquire the order data according to the payment platform currently supported by the to-be-checked platform. The method can reduce the probability that the order data of the payment platform currently supported by the to-be-checked platform is not acquired so as to acquire the order data of each payment platform currently supported by the to-be-checked platform, and also can reduce the probability that the order data of the payment platform not currently supported by the to-be-checked platform is acquired, reduce the data volume to be processed by a payment center, and enable the efficiency of returning the order data to be acquired by the payment center to be higher, namely the efficiency of acquiring the order data to be improved.

In some embodiments, step S1011 may include the step of, upon receiving an order acquisition instruction carrying a preset acquisition period, acquiring a platform identification of a payable platform currently requiring acquisition of order data as a current platform identification to be filled in each time the preset acquisition period is reached.

In an actual scenario, in order to ensure fund security, the to-be-reconciliation platform will typically periodically acquire order data from the payment center, and the preset acquisition period may be determined according to actual requirements. The to-be-reconciled platform can acquire order data from the payment center at a specified time of day, such as five points per day. Correspondingly, the acquisition period is preset, namely one day. Obviously, if the technician is required to manually input the platform identifier to the platform to be reconciled every time order data is acquired, the labor cost is increased. In order to reduce the cost, the technician may input an order acquisition instruction carrying a preset acquisition period to the to-be-checked-out platform. And then, based on the order data acquisition method provided by the invention, the platform identification of the payment platform which needs to acquire the order data at present can be automatically acquired by the platform to be checked as the current platform identification to be filled. The to-be-reconciled platform periodically acquires order data from the payment center, so that the acquired order data can be conveniently and uniformly managed and checked.

In some embodiments, after receiving the currently generated order acquisition request, the payment center may search all order data that is placed in the platform to be checked and paid through the target payment platform, where all the searched order data is the current order data.

In some embodiments, in order to reduce the probability of repeatedly acquiring order data, the currently generated order acquisition request sent by the to-be-reconciled platform to the payment center may also carry a time period of the order data to be acquired. If the code template also comprises a plurality of time filling positions which are not filled with time periods, the code template becomes a complete executable code after the time filling positions are filled with time.

In one implementation, an input box for a time period may also be provided in the operator interface, in which a technician may enter a specified time period. Subsequently, the platform to be reconciled can fill the designated time period input by the technician into the time filling position so as to obtain a complete and operable code. And then, the code is operated to generate an order acquisition request for acquiring the current order data in the appointed time period, the current generated order acquisition request is sent to a payment center, and the payment center sends the current order data in the appointed time period to a platform to be reconciliation based on the received order acquisition request.

In another implementation, the step S102 may include the step of filling the current platform identifier to be filled and a default time period into the code template to obtain the current order acquisition code, where the default time period is a time period between a time when the order data paid by the payment platform currently required to acquire the order data is acquired last time and the current time.

Accordingly, step S103 may include running a current order acquisition code to generate an order acquisition request for acquiring current order data within a default time period, and transmitting the current generated order acquisition request to the payment center to cause the payment center to transmit the current order data within the default time period to the reconciliation platform based on the received order acquisition request.

For each payment platform which needs to acquire order data at present, the to-be-checked platform can take the time period between the moment when the order data corresponding to the payment platform is acquired last time and the current moment as the default time period corresponding to the payment platform. Or in the case that the to-be-reconciliation platform periodically requests order data from the payment center, the to-be-reconciliation platform may use a time period between a time point at which the last time reached the preset acquisition period and the current time point as a default time period. Or in the case that the technician can input the specified time period, the default time period may be a time period between the moment when the technician inputs the specified time period and the current moment, or may be a time period between the ending moment of the specified time period and the current moment. Obviously, the possible situations in the actual scene are not limited to this, and the present invention is not limited to a specific acquisition manner of the default time period.

The platform to be checked can fill the current platform identifier to be filled into the platform identifier filling position, fill the default time period into the time filling position, and then obtain the complete executable code, namely the current order acquisition code.

Running the current order acquisition code, the to-be-reconciled platform may generate a current order acquisition request for acquiring current order data for a default period of time. And the current order data in the default time period is the order data which is paid through a payment platform which needs to acquire the order data currently in the default time period.

After receiving the current order acquisition code, the payment center can search the current order data in the default time period from the recorded order data, and then send the current order data in the default time period to the to-be-checked platform.

Based on the processing, the to-be-reconciliation platform can only acquire order data in a certain period of time from the payment center, so that the data volume to be processed by the payment center can be reduced, the efficiency of returning the order data to be acquired by the payment center is higher, and the efficiency of acquiring the order data can be improved. And the probability of repeatedly acquiring order data by the to-be-reconciled platform can be reduced, so that the subsequent to-be-reconciled platform does not need to repeatedly process the repeated order data, and the resource consumption of the to-be-reconciled platform is reduced.

In some embodiments, step S102 may include the step of populating a code template with a current platform identification to be populated and an identification of a currently recorded interface to obtain a current order acquisition code.

Accordingly, step S103 may include running a current order acquisition code to generate an order acquisition request for acquiring current order data, and sending the current generated order acquisition request to the payment center through an interface indicated by an identification of the currently recorded interface, so that the payment center sends the current order data to the to-be-reconciled platform based on the received order acquisition request.

In a practical scenario, the payment center may provide multiple interfaces. The to-be-reconciled platform may send an order acquisition request to the payment center via a currently active interface provided by the payment center. It will be appreciated that in a practical scenario, the payment center may alter the currently active interface due to factors such as hardware performance, user requirements, etc.

Such as the payment center may provide interface a, interface B, interface C. If there are 5 to-be-checked-out platforms to acquire order data from the payment center in the period 1, and 1 to-be-checked-out platform to acquire order data from the payment center in the period 2, a technician at the payment center side can set that in the period 1, the interface A, the interface B and the interface C are all effective interfaces, and in the period 2, the interface A is an effective interface. In the running process of the payment center, the interface A has hardware faults and needs to be overhauled, in the time period 1, the platform to be checked sends an order acquisition request to the payment center through the interface B and the interface C, and in the time period 2, the platform to be checked can send the order acquisition request to the payment center through the interface B. I.e. in a real scenario, it may be the case that the interface that sends the order acquisition request to the payment centre needs to be modified.

Therefore, in order to facilitate the processing under the condition, the code template can also comprise an interface identifier filling position which is not filled with an interface identifier, and the identifier of the interface currently available by the payment center can be correspondingly recorded in the to-be-checked platform. And filling the interface identifier with the identifier of the currently recorded interface to obtain the current order acquisition code which can be completely operated. And running the current order acquisition code, wherein the to-be-checked platform can generate an order acquisition request for acquiring current order data and send the current generated order acquisition request to the payment center through an interface indicated by the identifier of the currently filled interface.

For example, the payment center may send an interface identifier of an interface that is currently valid to the to-be-reconciled platform, and the to-be-reconciled platform may record the received interface identifier locally. When the order acquisition code needs to be generated, the interface identification of the local record is filled into the interface identification filling position. When the currently effective interface of the payment center is changed, the payment center can send indication information indicating the change of the effective interface to the platform to be checked, and the platform to be checked can update the identification of the locally recorded interface based on the indication information.

It will be appreciated that the interface identifier currently available to the payment centre may also be a plurality, in which case it may be configured based on the plurality of interface identifiers according to the service requirements.

For example, a technician may set a priority of use for a plurality of interfaces, and the to-be-reconciled platform may fill in the currently valid and highest priority interface identification into the interface identification fill-in location.

For example, the platform to be checked can acquire order data corresponding to different payment platforms through different interfaces. The identification of the interface corresponding to each payment service party can be correspondingly recorded in the data table. And filling the identifier of the interface corresponding to the payment service party into the interface identifier filling position to obtain an order acquisition code corresponding to the payment service party.

Obviously, in the actual scene, the recording mode, the use mode and the like of the identification of the interface are not limited to this, and the invention is not limited to this.

The greater the number of paytables currently supported by the to-be-reconciled tables, the greater the amount of code involved in the prior art, as compared to the prior art. Under the condition that the currently effective interface of the payment center is changed, based on the prior art, the identification of the interface to be changed is required to be searched in a large number of codes, and then the identification of the interface to be changed is sequentially changed, so that the modification process is complicated. Based on the embodiment of the invention, only the identification of the interface recorded by the platform to be checked is required to be changed, the modification process is simple, and the maintenance difficulty is low. And obviously, the more the number of payment platforms supported by the reconciliation platform is, the more the advantage of low code maintenance difficulty of the invention is outstanding.

In some embodiments, an order number and an order amount for an order are recorded in an order data.

After step S104, the method may further include the steps of:

and step 1, searching the to-be-reconciled order data paid by the payment platform from the order data locally recorded by the to-be-reconciled platform for each payment platform which receives the order data from the payment center.

Step 2, judging whether the received order data of the payment platform has the order data to be compared, wherein the order number recorded in the order data is consistent with the order number recorded in the order data to be compared, determining that the order data to be compared is abnormal under the condition that the order data to be compared is not present, and judging whether the order amount recorded in the order data to be compared is consistent with the order amount recorded in the order data to be compared under the condition that the order data to be compared is present.

And step 3, determining that the to-be-checked order data is abnormal if the order amount recorded in the to-be-checked order data is inconsistent with the order amount recorded in the to-be-checked order data, and determining that the to-be-checked order data is not abnormal if the order amount recorded in the to-be-checked order data is consistent with the order amount recorded in the to-be-checked order data.

The to-be-reconciled platform obtains order data from the payment center, namely order data recorded by the payment center and paid through the payment platform. In order to ensure the fund safety, the platform to be checked can compare the data recorded by the payment center with the data recorded locally.

Specifically, for each payment platform that receives order data from the payment center, that is, for each payment platform supported by the to-be-reconciled platform, the to-be-reconciled platform may search for to-be-reconciled order data that is paid by the payment platform from the locally recorded order data. When the checking platform records the order data locally, the platform identification corresponding to each order data is recorded correspondingly, namely, the payment by which payment platform each order data is paid is recorded. When checking, the platform to be checked can also search the order data of each payment platform from the locally recorded order data according to the recording sequence of the platform identification of each payment platform, namely, checking the order data of each payment platform in sequence based on the order data acquired from the payment center.

For each to-be-checked order data, when the to-be-checked order data with the recorded order number consistent with the order number recorded by the to-be-checked order data does not exist in the received order data of the payment platform, that is, when the payment center does not record the order data corresponding to the to-be-checked order data, the to-be-checked order data is abnormal, for example, an order corresponding to the to-be-checked order data (a subsequent to-be-checked order) may not be paid.

When the to-be-compared order data exist, if the order amount recorded in the to-be-compared order data is inconsistent with the order amount recorded in the to-be-compared order data, namely, the to-be-compared order may have abnormal payment, if repeated payment occurs. Obviously, the to-be-reconciled order data also has anomalies.

It will be appreciated that for each paymate that receives order data from a paymate, the paymate may be reconciled based on the obtained order data after the order data for payment by that paymate is obtained from the paymate. Or the platform to be checked out can also check out all the acquired order data after acquiring the order data of each payment platform currently supported by the platform to be checked out from the payment center.

It can be understood that, in the case that the to-be-checked-out platform obtains the order data in a certain period of time from the payment center each time, the to-be-checked-out platform can search the to-be-checked-out order data paid through the payment platform which needs to obtain the order data currently in the period of time from the locally recorded order data. And subsequently, checking the to-be-checked order data in the time period.

Based on the processing, the to-be-checked platform can check with the payment center, and can check out abnormal orders with the problems of repeated payment, incorrect payment and the like, so that the fund safety is ensured.

In some embodiments, referring to fig. 3, fig. 3 is a third flowchart of an order data obtaining method according to an embodiment of the present invention. The method may comprise the steps of:

s1, checking the arrival of a task (data of yesterday checking every morning).

In this step, the accounting task arrives, that is, the preset acquisition period is reached in the foregoing embodiment. In the embodiment of the invention, the acquisition period is preset, namely, one day.

S2, inquiring the yesterday ordered quantity of the mall.

In the step, the mall is the platform to be checked out in the embodiment, and the yesterday ordered quantity of the mall is locally recorded by the platform to be checked out, namely, the data of the order paid in the platform to be checked out by each payment mode in the current acquisition period, namely, the data of the mall introduced later.

S3, inquiring the configured service party data table, and traversing the returned data.

In this step, the business party is the payment platform in the foregoing embodiment, and the business party data table is the data table in the foregoing embodiment, where the data table records the platform identifier of each payment platform currently supported by the platform to be checked.

The data table is traversed by the platform to be checked to obtain the platform identification of each payment platform currently supported by the platform to be checked.

S4, requesting the payment center to acquire data according to the identification 'mall_A_plus', and acquiring '2024-01-01_mall_A_plus_pay.csv.zip' returned by the payment center.

In the step, after the platform identification mall_A_plus is acquired by the platform to be checked, a preset code template can be filled in the platform identification mall_A_plus to obtain a current order acquisition code, the current order acquisition code is operated to generate an order acquisition request for acquiring current order data, and the current generated order acquisition request is sent to a payment center. The payment center searches the current order data based on the received order acquisition request, and according to a specified compression mode, the current order data is manufactured into a compression packet, the compression packet is named as '2024-01-01_mall_A_plus_pay.csv.zip', and then the compression packet is sent to a platform to be reconciled.

S5, requesting the payment center to acquire data according to the mark 'mall_A', and acquiring '2024-01-01_mall_A_pay.csv.zip' returned by the payment center.

In the step, after the platform identification mall_A is acquired by the platform to be checked, the platform identification mall_A can be filled into a code template to obtain a current order acquisition code, the current order acquisition code is operated to generate an order acquisition request for acquiring current order data, and the current generated order acquisition request is sent to a payment center. The payment center searches the current order data based on the received order acquisition request, and according to a specified compression mode, the current order data is manufactured into a compression packet, the compression packet is named as '2024-01-01_mall_A_pay.csv.zip', and then the compression packet is sent to a platform to be checked.

S6, decompressing and summarizing.

In this step, after the to-be-checked platform obtains the compressed packets of the order data of each payment platform sent by the payment center, the compressed packets may be decompressed, and then the order data obtained by decompression may be summarized, for example, the order orders may be ordered according to order numbers.

And S7, comparing and recording with the mall data.

In this step, the mall data, that is, the order data of the payment to be made in the reconciliation platform in the previous embodiment, is recorded locally in the current acquisition period.

For each payment platform currently supported by the to-be-checked-out platform, the to-be-checked-out platform can search to-be-checked-out order data paid through the payment platform in the current acquisition period from the locally recorded order data. For each to-be-checked order data, determining whether to-be-checked order data with consistent order numbers exists in the order data acquired from the payment center based on the order numbers of the to-be-checked order data. If the order amount recorded in the order data to be compared is inconsistent with the order amount recorded in the order data to be compared, the order data to be compared is abnormal.

And, since the to-be-reconciled platform can maintain the partner data distributed by the payment center through the data table, when the to-be-reconciled platform adds the supported payment platform, namely, newly butts against the payment partner, the newly butts against the payment partner can be stored in the configuration table (namely, the data table). When the checking task is executed, namely order data is to be acquired from a payment center, the platform to be checked firstly acquires data from a configuration table, namely the platform identification of each payment platform currently supported by the platform to be checked is acquired. And because the invention can obtain the order acquisition code based on the code template, namely, different partner data are configured, and the change logic is removed, so that the code flow can be multiplexed, and the code flow can support the reconciliation data function of different partners, namely, different platform identifications can be filled into the code template, and the order acquisition code for acquiring the order data of different payment platforms is obtained. I.e. configuring the variable logic, the optimized code logic is dynamically realized, and the reconciliation logic is not modified by the new payment method partner in the following.

Therefore, after the platform identification of each currently supported payment platform is obtained by the to-be-reconciled platform, the request payment center interface can be traversed based on the code template to obtain order data of the corresponding partner. And summarizing the order data acquired from the payment center, comparing the summarized order data with the order data locally recorded in the mall, and determining that the order data is abnormal when the quantity of the order data is inconsistent and/or when the amount of the order in the order data with the consistent order number is inconsistent. The subsequent mall can dynamically acquire the reconciliation data according to the partner by querying the partner configuration table no matter how many payment modes are docked, and the reconciliation logic does not need to be changed once for each payment mode, so that the order acquisition efficiency can be improved.

It can be understood that, because the variable logic is configured in the invention, the reconciliation data functions of different partner are paid through the code flow which can be multiplexed, when the number of the payment platforms supported by the reconciliation platform is large, the code amount of executing the order data acquisition method provided by the invention is necessarily smaller than the code amount of the method of correspondingly writing codes for each payment platform in the prior art.

Illustratively, the code amount of code written for one paymate is about 15 lines. In the case where n payment platforms are supported by the platform to be reconciled, based on the prior art, a technician needs to write n×15 lines of codes to obtain codes for acquiring order data corresponding to each payment platform.

Based on the order data acquisition method provided by the invention, the codes for acquiring the order data corresponding to each payment platform can be obtained only by the codes for calling the configuration table, the codes for representing the cyclic processing and the codes corresponding to the code templates. I.e. the code obtained on the basis of the invention comprises (15 + m) lines of code. In a practical scenario, m is typically only tens of lines of code, and only n lines of data are typically included in the configuration table to be invoked.

Therefore, under the condition that the number of the payment platforms supported by the platform to be checked is larger than the threshold value of the number of the platforms, the code quantity related to the method is smaller than that related to the prior art, namely, the code related to the method is simpler, and the maintenance difficulty is lower. The platform number threshold is calculated based on a specific code amount of code written for one paymate, and a specific code amount of code written in an actual scene representing calling the configuration table and code representing the loop processing. And obviously, the more the number of payment platforms supported by the reconciliation platform is, the more outstanding the advantages of simple codes and low maintenance difficulty are.

The invention also provides an order data acquisition system, which comprises a to-be-reconciliation platform and a payment center, wherein the to-be-reconciliation platform is used for providing the order service, the to-be-reconciliation platform is used for executing the order data acquisition method in any one of the embodiments, and the payment center is used for sending order data to the to-be-reconciliation platform based on the received order acquisition request sent by the to-be-reconciliation platform.

Based on the same inventive concept as the order data acquisition method, the embodiment of the invention also provides an order data acquisition device which is applied to a to-be-reconciliation platform for providing order service in a server. Referring to fig. 4, fig. 4 is a block diagram of an order data obtaining apparatus according to an embodiment of the present invention, where the apparatus includes:

the first identifier obtaining module 401 is configured to obtain a platform identifier of a payment platform that needs to obtain order data currently, as a current platform identifier to be filled;

The code acquisition module 402 is used for filling the current platform identification to be filled into a preset code template to obtain a current order acquisition code, wherein the code template is used for generating an order acquisition request for acquiring order data and sending the generated order acquisition request to a payment center;

The code running module 403 is configured to run a current order acquisition code to generate an order acquisition request for acquiring current order data, and send the current order acquisition request to the payment center, so that the payment center sends the current order data to the platform to be checked based on the received order acquisition request, where the current order data is order data that is paid through a payment platform that needs to acquire the order data currently;

And the receiving module 404 is configured to receive current order data sent by the payment center.

Optionally, the first identifier obtaining module 401 is specifically configured to determine, according to a recording order of platform identifiers of each payment platform currently supported by the platform to be checked, a current platform identifier to be filled;

The device further comprises a second identifier obtaining module, configured to, after the receiving module 404 performs receiving the current order data sent by the payment center, return to performing the step of determining the current platform identifier to be filled according to the recording sequence of the platform identifiers of the payment platforms currently supported by the platform to be checked, until the order data of the payment platforms currently supported by the platform to be checked is obtained.

Optionally, the first identifier obtaining module 401 is specifically configured to, when receiving an order obtaining instruction carrying a preset obtaining period, obtain, as a current platform identifier to be filled, a platform identifier of a payment platform on which order data is currently required to be obtained when the preset obtaining period is reached each time.

Optionally, the code obtaining module 402 is specifically configured to fill a current platform identifier to be filled and a default time period into a code template to obtain a current order obtaining code, where the default time period is a time period between a time when the current time is the last time when order data to be paid by a payment platform that needs to obtain the order data is obtained, and the code running module 403 is specifically configured to run the current order obtaining code to generate an order obtaining request for obtaining the current order data in the default time period, and send the current generated order obtaining request to the payment center, so that the payment center sends the current order data in the default time period to the platform to be reconciled based on the received order obtaining request.

Optionally, the code obtaining module 402 is specifically configured to fill a current platform identifier to be filled and a current recorded identifier of an interface into a code template to obtain a current order obtaining code, and the code running module 403 is specifically configured to run the current order obtaining code to generate an order obtaining request for obtaining current order data, and send the current generated order obtaining request to the payment center through the interface indicated by the current recorded identifier of the interface, so that the payment center sends the current order data to the platform to be checked based on the received order obtaining request.

Optionally, an order number and an order amount of an order are recorded in order data;

The device further comprises a reconciliation module, a checking module and a checking module, wherein the reconciliation module is used for executing each payment platform for receiving the order data from the payment center after the receiving module 404 executes receiving the current order data sent by the payment center, and searching the order data to be reconciled which is paid through the payment platform from the order data locally recorded by the payment platform; for each piece of to-be-checked order data, judging whether the received order data of the payment platform has to-be-checked order data with the recorded order number consistent with the order number recorded in the to-be-checked order data, determining that the to-be-checked order data has an abnormality when the to-be-checked order data does not exist, judging whether the order amount recorded in the to-be-checked order data is consistent with the order amount recorded in the to-be-checked order data when the to-be-checked order data exists, determining that the to-be-checked order data has an abnormality when the order amount recorded in the to-be-checked order data is inconsistent with the order amount recorded in the to-be-checked order data if the order amount recorded in the to-be-checked order data is inconsistent with the order amount recorded in the to-be-checked order data, and determining that the to-be-checked order data has no abnormality when the order amount recorded in the to-be-checked order data is consistent with the order amount recorded in the to-be-checked order data.

According to the order data acquisition device provided by the embodiment of the invention, after the to-be-checked platform for providing the order service in the server side acquires the current platform identifier to be filled of the payment platform needing to acquire the order data, the current platform identifier to be filled is filled into the preset code template to acquire the current order acquisition code, and the current order data is acquired from the payment center by operating the current order acquisition code. Obviously, when the payment mode supported by the reconciliation platform is changed, namely when the payment platform for acquiring order data is changed, only the acquired platform identification is required to be changed, and then a corresponding order acquisition code can be automatically generated based on the acquired platform identification without re-writing the code, so that the order data acquisition efficiency can be improved.

The embodiment of the invention also provides a platform to be checked out, as shown in fig. 5, which comprises a processor 501, a communication interface 502, a memory 503 and a communication bus 504, wherein the processor 501, the communication interface 502, the memory 503 and the communication bus 504 are used for completing communication between each other, the memory 503 is used for storing a computer program, and the processor 501 is used for realizing the order data acquisition method in any one of the previous embodiments when executing the program stored on the memory 503.

The communication bus mentioned by the above terminal may be a peripheral component interconnect standard (PERIPHERAL COMPONENT INTERCONNECT, abbreviated as PCI) bus or an extended industry standard architecture (Extended Industry Standard Architecture, abbreviated as EISA) bus, etc. The communication bus may be classified as an address bus, a data bus, a control bus, or the like. For ease of illustration, the figures are shown with only one bold line, but not with only one bus or one type of bus.

The communication interface is used for communication between the terminal and other devices.

The memory may include random access memory (Random Access Memory, RAM) or may include non-volatile memory (non-volatile memory), such as at least one disk memory. Optionally, the memory may also be at least one memory device located remotely from the aforementioned processor.

The Processor may be a general-purpose Processor, including a central processing unit (Central Processing Unit, CPU), a network Processor (Network Processor, NP), a digital signal Processor (DIGITAL SIGNAL Processor, DSP), an Application-specific integrated Circuit (ASIC), a Field-Programmable gate array (FPGA) or other Programmable logic device, discrete gate or transistor logic device, or discrete hardware components.

In yet another embodiment of the present invention, a computer readable storage medium is provided, in which a computer program is stored, which when executed by a processor, implements the order data acquisition method according to any of the above embodiments.

In yet another embodiment of the present invention, a computer program product containing instructions that, when run on a computer, cause the computer to perform the order data acquisition method of any of the above embodiments is also provided.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may 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 loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present invention, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk Solid STATE DISK (SSD)), etc.

It is noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.

In this specification, each embodiment is described in a related manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system, apparatus, platform to be reconciled, computer-readable storage medium, computer program product embodiments, the description is relatively simple, as it is substantially similar to the method embodiments, and relevant references are made to the section description of the method embodiments.

The foregoing description is only of the preferred embodiments of the present invention and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention are included in the protection scope of the present invention.

Claims

1. A method for acquiring order data, characterized in that the method is applied to a pending reconciliation platform for providing order services in a server, and the method comprises:

Obtain the platform ID of the payment platform for which order data is currently to be obtained, as the current platform ID to be filled in;

Fill the current platform identifier to be filled into the preset code template to obtain the current order acquisition code; wherein the code template is used to: generate an order acquisition request for acquiring order data, and send the generated order acquisition request to the payment center;

Run the current order acquisition code to generate an order acquisition request for acquiring the current order data, and send the currently generated order acquisition request to the payment center, so that the payment center sends the current order data to the to-be-reconciled platform based on the received order acquisition request; wherein the current order data is: order data paid through the payment platform for which the order data currently needs to be acquired;

Receive the current order data sent by the payment center.

2. The method according to claim 1, characterized in that the step of obtaining the platform identifier of the payment platform for which order data is currently required to be obtained as the current platform identifier to be filled in comprises:

Determine the current platform identifier to be filled in according to the order of recording the platform identifiers of the payment platforms currently supported by the to-be-reconciled platform;

After receiving the current order data sent by the payment center, the method further includes:

Return to the step of determining the current platform identifier to be filled in according to the order of recording the platform identifiers of the payment platforms currently supported by the platform to be reconciled, until the order data of the payment platforms currently supported by the platform to be reconciled is obtained.

3. The method according to claim 2, characterized in that the method further comprises:

When a modification instruction for the record sequence is received, the record sequence is modified according to the modification method carried in the modification instruction; wherein the modification method includes at least one of the following: adding a platform identifier to the record sequence, deleting a specified platform identifier in the record sequence, and adjusting the order of platform identifiers in the record sequence.

4. The method according to claim 1, characterized in that the step of obtaining the platform identifier of the payment platform for which order data is currently required to be obtained as the current platform identifier to be filled in comprises:

When an order acquisition instruction carrying a preset acquisition cycle is received, each time the preset acquisition cycle is reached, the platform identifier of the payment platform for which order data is currently required to be acquired is acquired as the current platform identifier to be filled in.

5. The method according to claim 1, characterized in that the step of filling the current platform identifier to be filled into a preset code template to obtain the current order acquisition code comprises:

Fill the current platform identifier and default time period into the preset code template to obtain the current order acquisition code; the default time period is: the time period between the last time the order data for payment was obtained through the payment platform for which the order data currently needs to be obtained and the current time;

The running of the current order acquisition code to generate an order acquisition request for acquiring the current order data, and sending the currently generated order acquisition request to the payment center, so that the payment center sends the current order data to the to-be-reconciled platform based on the received order acquisition request, includes:

Run the current order acquisition code to generate an order acquisition request for acquiring the current order data within the default time period, and send the currently generated order acquisition request to the payment center, so that the payment center sends the current order data within the default time period to the reconciliation platform based on the received order acquisition request.

6. The method according to claim 1, characterized in that the step of filling the current platform identifier to be filled into a preset code template to obtain the current order acquisition code comprises:

Fill the current platform ID to be filled in and the ID of the currently recorded interface into the preset code template to obtain the current order acquisition code;

Run the current order acquisition code to generate an order acquisition request for acquiring the current order data, and send the currently generated order acquisition request to the payment center through the interface indicated by the identifier of the currently recorded interface, so that the payment center sends the current order data to the reconciliation platform based on the received order acquisition request.

7. The method according to claim 1, characterized in that one order data records an order number and an order amount of an order;

For each payment platform that has received order data from the payment center, searching for order data to be reconciled that has been paid through the payment platform from among the order data locally recorded by the platform to be reconciled;

For each order data to be reconciled, determine whether there is any order data to be compared whose recorded order number is consistent with the order number recorded in the order data to be reconciled in the order data received from the payment platform;

In the case where the order data to be compared does not exist, determining that the order data to be reconciled is abnormal;

In the case where the order data to be compared exists, determining whether the order amount recorded in the order data to be compared is consistent with the order amount recorded in the order data to be reconciled;

If the order amount recorded in the order data to be compared is inconsistent with the order amount recorded in the order data to be reconciled, it is determined that there is an abnormality in the order data to be reconciled;

If the order amount recorded in the order data to be compared is consistent with the order amount recorded in the order data to be reconciled, it is determined that there is no abnormality in the order data to be reconciled.

8. An order data acquisition system, characterized in that the order data acquisition system includes a pending reconciliation platform and a payment center for providing order services on the server side, wherein:

The reconciliation platform is used to execute the method described in any one of claims 1 to 7 above;

The payment center is used to send order data to the platform to be reconciled based on the order acquisition request sent by the platform to be reconciled.

9. An order data acquisition device, characterized in that the device is applied to a pending reconciliation platform for providing order services in a server, and the device comprises:

A first identification acquisition module is used to acquire the platform identification of the payment platform for which order data is currently to be acquired as the current platform identification to be filled in;

A code acquisition module is used to fill the current platform identifier to be filled into a preset code template to obtain the current order acquisition code; wherein the code template is used to: generate an order acquisition request for acquiring order data, and send the generated order acquisition request to the payment center;

A code running module, used for running the current order acquisition code to generate an order acquisition request for acquiring the current order data, and sending the currently generated order acquisition request to the payment center, so that the payment center sends the current order data to the to-be-reconciled platform based on the received order acquisition request; wherein the current order data is: order data paid through the payment platform for which the order data currently needs to be acquired;

The receiving module is used to receive the current order data sent by the payment center.

10. A reconciliation platform, characterized in that it includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus;

Memory, used to store computer programs;

A processor, for implementing any of the methods described in claims 1-7 when executing a program stored in a memory.

11. A computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

12. A computer program product, characterized in that when the computer program product is run on a computer, the computer is enabled to execute the method according to any one of claims 1 to 7.