Platform transaction monitoring method and device, equipment and storage medium

Abstract

The invention relates to the technical field of network payment, in particular to a platform transaction monitoring method and device, equipment and a storage medium, and the method comprises the steps: querying an interface information record table corresponding to a transaction request in response to the transaction request of a user; calling a transaction interface corresponding to the transaction request according to the interface information record table to obtain a transaction data message; the interface information record table is updated according to the transaction data message, and the transaction result is fed back, so that the fund account of the user does not need to be monitored, and the transaction data message generated in the transaction service process is called through the transaction interface corresponding to the transaction request to realize effective monitoring of the transaction service; the technical problem of low monitoring efficiency of the transaction service result in the prior art is avoided.

Description

Technical Field

[0001] The present invention relates to the technical field of network payment, and particularly to a platform transaction monitoring method, device, equipment and storage medium. Background Art

[0002] With the development of network technology, the payment form has been converted from physical currency to digital currency payment. At the same time, a large number of shopping platforms and payment platforms have emerged. In the transaction process among users, shopping platforms, and payment platforms, due to network and interface occupancy, etc., situations such as duplicate transactions or terminated transactions may occur. In the network transaction process, funds are not transferred end-to-end. When duplicate transactions or transaction termination problems occur, the funds owned by users cannot be monitored by shopping platforms and payment platforms, lacking monitoring means for transaction results, and the efficiency of monitoring transaction services is low.

[0003] The above content is only used to assist in understanding the technical solution of the present invention, and does not represent an admission that the above content is prior art. Summary of the Invention

[0004] The main purpose of the present invention is to provide a platform transaction monitoring method, device, equipment and storage medium, aiming to solve the technical problem of low monitoring efficiency for transaction service results in the prior art.

[0005] To achieve the above purpose, the present invention provides a platform transaction monitoring method, and the method includes the following steps:

[0006] In response to a transaction request from a user, query an interface information record table corresponding to the transaction request;

[0007] According to the interface information record table, call a transaction interface corresponding to the transaction request to obtain a transaction data message;

[0008] Update the interface information record table according to the transaction data message and feedback a transaction result.

[0009] Optionally, the transaction request at least includes: a cash withdrawal request;

[0010] The step of calling a transaction interface corresponding to the transaction request according to the interface information record table to obtain a transaction data message includes:

[0011] In response to the cash withdrawal request, query a cash withdrawal interface information record table of the user;

[0012] Detect whether the cash withdrawal interface information record table is recorded;

[0013] If so, detect a status parameter of the cash withdrawal interface information record table;

[0014] When the state parameter is a preset parameter, call the cash withdrawal transaction interface to determine whether there is a historical record of calling the transaction interface;

[0015] If there is no historical record of calling the transaction interface, call the transaction interface corresponding to the cash withdrawal request to obtain the transaction data message.

[0016] Optionally, the platform transaction monitoring method further includes:

[0017] In response to the cash withdrawal compensation query request, call the cash withdrawal transaction status query interface, where the cash withdrawal compensation query request is a periodically generated status query task;

[0018] Obtain the distributed lock permission of the user account;

[0019] When successfully obtaining the distributed lock permission of the user account, query whether the bank interface log table is an empty set;

[0020] If not, call the cash withdrawal service query interface to query whether there is an empty set of cash withdrawal services;

[0021] If not, call the transaction interface corresponding to the cash withdrawal request to obtain the transaction data message.

[0022] Optionally, the transaction request further includes: a payment request;

[0023] The step of calling the transaction interface corresponding to the transaction request according to the interface information record table to obtain the transaction data message further includes:

[0024] In response to the payment request, query the payment interface information record table corresponding to the user;

[0025] Detect whether the payment interface information record table is recorded;

[0026] If so, detect the state parameter of the payment interface information record table;

[0027] When the state parameter is a preset parameter, call the payment interface corresponding to the payment request to obtain the transaction data message.

[0028] Optionally, the platform transaction monitoring method is further used for:

[0029] In response to the payment compensation query request, call the payment transaction status query interface, where the payment compensation query request is a periodically generated status query task;

[0030] Obtain the distributed lock permission of the user account;

[0031] When successfully obtaining the distributed lock permission of the user account,

[0032] Generate a standard status flag, and call the main payment process program based on the standard status flag to determine whether there is a new payment record.

[0033] Optionally, the transaction request further includes: a recharge request;

[0034] The step of calling the transaction interface corresponding to the transaction request according to the interface information record table to obtain a transaction data message further includes:

[0035] In response to the recharge request, verify the transaction record table, which records the transaction record data of the user;

[0036] Query the recharge interface information record table corresponding to the user;

[0037] Detect whether the recharge interface information record table is recorded;

[0038] If not, call the payment interface corresponding to the recharge request and verify whether there is a network exception;

[0039] If there is no network exception, generate a recharge information record table;

[0040] Update the transaction record table according to the recharge information record table.

[0041] Optionally, after verifying whether there is a network exception, it further includes:

[0042] If there is a network exception, switch the service query interface and return to the step of querying the recharge interface information record table corresponding to the user;

[0043] When the number of switches is greater than the preset number, generate an alarm message.

[0044] In addition, to achieve the above object, the present invention also proposes a platform transaction monitoring device, and the platform transaction monitoring device includes:

[0045] A query module, configured to query the interface information record table corresponding to the transaction request in response to a transaction request of a user;

[0046] A call module, configured to call the transaction interface corresponding to the transaction request according to the interface information record table to obtain a transaction data message;

[0047] An update module, configured to update the interface information record table according to the transaction data message and feedback a transaction result.

[0048] In addition, to achieve the above object, the present invention further provides a platform transaction monitoring device, which includes: a memory, a processor, and a platform transaction monitoring program stored on the memory and executable on the processor. The platform transaction monitoring program is configured to implement the steps of the platform transaction monitoring method as described above.

[0049] In addition, to achieve the above object, the present invention further provides a storage medium, on which a platform transaction monitoring program is stored. When the platform transaction monitoring program is executed by a processor, it implements the steps of the platform transaction monitoring method as described above.

[0050] In addition, to achieve the above object, the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the steps of the platform transaction monitoring method as described above.

[0051] The present invention responds to a user's transaction request, queries an interface information record table corresponding to the transaction request; calls a transaction interface corresponding to the transaction request according to the interface information record table to obtain a transaction data message; updates the interface information record table according to the transaction data message, and feeds back a transaction result. It is not necessary to monitor the user's fund account, but to effectively monitor the transaction business by calling the transaction data message generated during the transaction business process through the transaction interface corresponding to the transaction request, avoiding the technical problem of low monitoring efficiency for transaction business results in the prior art. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] The accompanying drawings herein are incorporated into the specification and form a part of the specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application.

[0053] To more clearly illustrate the technical solutions in the embodiments of the present application or in the prior art, the following will briefly introduce the accompanying drawings required for use in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0054] Figure 1 It is a schematic flowchart of the first embodiment of the platform transaction monitoring method of the present invention;

[0055] Figure 2 It is a schematic flowchart of the second embodiment of the platform transaction monitoring method of the present invention;

[0056] Figure 3 It is a schematic flowchart of the cash withdrawal business process of an embodiment of the platform transaction monitoring method of the present invention;

[0057] Figure 4 Schematic diagram of the cash withdrawal compensation service process for an embodiment of the platform transaction monitoring method of the present invention;

[0058] Figure 5 Schematic diagram of the process for the third embodiment of the platform transaction monitoring method of the present invention;

[0059] Figure 6 Schematic diagram of the payment service process for an embodiment of the platform transaction monitoring method of the present invention;

[0060] Figure 7 Schematic diagram of the payment compensation service process for an embodiment of the platform transaction monitoring method of the present invention;

[0061] Figure 8 Schematic diagram of the process for the fourth embodiment of the platform transaction monitoring method of the present invention;

[0062] Figure 9 Schematic diagram of the recharge service process for an embodiment of the platform transaction monitoring method of the present invention;

[0063] Figure 10 Block diagram of the structure of the first embodiment of the platform transaction monitoring device of the present invention;

[0064] Figure 11 Schematic diagram of the structure of the platform transaction monitoring device, which is the hardware operating environment involved in the solution of the embodiment of the present invention.

[0065] The implementation, functional features and advantages of the object of the present invention will be further described with reference to the embodiments and the accompanying drawings. Detailed implementation manners

[0066] It should be understood that the specific embodiments described herein are only used to explain the technical solutions of the present application and are not used to limit the present application.

[0067] For a better understanding of the technical solutions of the present application, the following will be described in detail in conjunction with the accompanying drawings of the specification and the specific implementation manners.

[0068] Based on this, an embodiment of the present invention provides a platform transaction monitoring method. Referring to Figure 1 , Figure 1 Schematic diagram of the process for the first embodiment of a platform transaction monitoring method of the present invention.

[0069] In this embodiment, the platform transaction monitoring method includes:

[0070] Step S10: In response to a user's transaction request, query the interface information record table corresponding to the transaction request.

[0071] Step S20: Call the transaction interface corresponding to the transaction request according to the interface information record table to obtain a transaction data message.

[0072] Step S30: Update the interface information record table according to the transaction data message and feedback the transaction result.

[0073] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication, and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device or a platform cloud server that can implement the above functions. Hereinafter, the platform cloud server will be taken as an example to illustrate this embodiment and the following embodiments.

[0074] It should be understood that in the network transaction process, the purchaser's funds will not be directly given to the shopping platform or the payment platform, and affected by the network status or program anomalies of the user or the platform, there may be a situation where the same commodity is submitted for multiple orders, or the order ends before payment, which will cause economic losses to users and platforms, and also affect the security and reliability of network payment.

[0075] Based on this, this embodiment does not need to monitor the user's fund account, but realizes the effective monitoring of the transaction business by calling the transaction data message generated in the transaction business process through the transaction interface corresponding to the transaction request.

[0076] Among them, the transaction request includes at least a withdrawal request, a payment request, and a recharge request. The withdrawal request is used to request to withdraw the balance, red envelope, or other digital funds available for commodity transactions in the user account on the platform to other platforms or banks; the recharge request is used to request to convert the digital funds of other platforms or banks into the balance, red envelope, or other digital funds available for commodity transactions in the user account on the platform; the payment request is used to pay the amount marked for a certain commodity. No matter what kind of request, it will face the situation of virtual funds flowing on multiple sides. Therefore, this embodiment will illustrate the above three requests.

[0077] The interface information record table is used to record transaction records and is used to subsequently determine whether there are record data in the historical transaction records that are the same as the user's transaction request, so as to determine whether there are duplicate transactions or transaction failures.

[0078] It should be understood that different types of transaction requests correspond to different transaction interfaces. The transaction interface is used to pull up the transaction page, provide transaction auxiliary information, and can also detect the network status between the current user and the platform to avoid transaction losses caused by poor network status.

[0079] The transaction data message at least includes data such as the transaction object, transaction amount, transaction time, and transaction code. By parsing the transaction data message, all information in a single transaction process can be determined to facilitate the confirmation of whether there are duplicate transactions or transaction failures.

[0080] In addition, after successfully completing a single transaction, by feeding back the transaction result to the user to provide a transaction proof, the user can end the transaction, suspend the transaction interface, and prevent duplicate transactions or fund losses caused by factors such as API hijacking.

[0081] In this embodiment, by responding to the user's transaction request, querying the interface information record table corresponding to the transaction request; calling the transaction interface corresponding to the transaction request according to the interface information record table to obtain the transaction data message; updating the interface information record table according to the transaction data message, and feeding back the transaction result, there is no need to monitor the user's fund account, but to effectively monitor the transaction business by calling the transaction data message generated in the transaction business process through the transaction interface corresponding to the transaction request, avoiding the technical problem of low monitoring efficiency for the transaction business result in the prior art.

[0082] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar content as in the above-mentioned embodiment one can be referred to the above introduction and will not be elaborated hereinafter. On this basis, please refer to Figure 2 , step S20, includes:

[0083] Step S201: Respond to the cash withdrawal request and query the cash withdrawal interface information record table of the user.

[0084] Step S202: Detect whether the cash withdrawal interface information record table is recorded.

[0085] Step S203: If so, detect the status parameter of the cash withdrawal interface information record table.

[0086] Step S204: When the status parameter is a preset parameter, call the cash withdrawal transaction interface to determine whether there is a historical record of calling the transaction interface.

[0087] Step S205: If there is no historical record of calling the transaction interface, call the transaction interface corresponding to the cash withdrawal request to obtain the transaction data message.

[0088] It should be noted that referring to Figure 3 , Figure 3This is a schematic diagram of the process for the cash withdrawal business in this embodiment. In this embodiment, when a user initiates a cash withdrawal request, the user terminal generates a transaction water table, and the identifier of the transaction water table is a preset character (set to 0 in this embodiment). The user terminal remotely calls the payment service. When the platform receives the cash withdrawal request and the call request raised by the user, it checks whether the platform already has a historical record of this cash withdrawal business by querying the interface information record table, so as to avoid repeated cash withdrawals.

[0089] Specifically, if it is detected that the cash withdrawal interface information record table has been recorded, then by detecting the status parameter of the cash withdrawal interface information record table, if the status parameter is 0, the query cash withdrawal water interface is called to detect whether there is a historical record of calling the water interface. If there is no historical record of calling the water interface, the transaction interface corresponding to the cash withdrawal request is called to obtain the transaction data message. Before obtaining the transaction data message, it is also possible to detect whether there is a network anomaly through the transaction interface. When there is no network anomaly, then call the transaction interface to obtain the transaction data message feedback by the bank. If there is a network anomaly, query the interface retry log record. If it is within 3 retries, generate a warning message. If it is beyond 3 retries, return the initialization state to the caller and perform the cash withdrawal compensation process.

[0090] Among them, if it is detected that the cash withdrawal interface information record table has not been recorded, it indicates that this transaction has not been successfully executed. The interface information record table can be newly created to call the transaction interface corresponding to the cash withdrawal request to obtain the transaction data message.

[0091] In this embodiment, after obtaining the transaction message data feedback by the bank, it can be detected whether the structure header of the transaction message data is an empty set. If so, it indicates that a transaction anomaly has occurred, and the interface information record table needs to be updated in a timely manner, and the transaction business status is modified to "failed".

[0092] After obtaining the non-empty transaction message data, the transaction business status of this time can be modified to "processing" or "completed", and the transaction business status is fed back to the user. At the same time, the remote call Portal service process is called to prompt the user to modify the transaction water and modify the user's account information to complete information synchronization.

[0093] Furthermore, the platform transaction monitoring method further includes:

[0094] In response to the cash withdrawal compensation query request, call the cash withdrawal water status query interface, and the cash withdrawal compensation query request is a periodically generated status query task;

[0095] Obtain the distributed lock permission of the user account;

[0096] When successfully obtaining the distributed lock permission of the user account, query whether the bank interface log table is an empty set;

[0097] If not, call the cash withdrawal service query interface to query whether there is an empty set of cash withdrawal services;

[0098] If not, call the transaction interface corresponding to the cash withdrawal request to obtain the transaction data message.

[0099] In a specific implementation, after multiple retry failures, it is necessary to perform cash withdrawal compensation for this cash withdrawal service to avoid invalid processes occupying the running memory and improve the platform's business processing efficiency. Specifically, refer to Figure 4 , Figure 4 which is the schematic diagram of the cash withdrawal compensation process in this embodiment.

[0100] Among them, when more than 3 retry failures occur, a certain time interval can be set to initiate the cash withdrawal compensation service. In the cash withdrawal compensation service, obtain the distributed lock of the user's account to obtain the relevant operation permissions of the user's account. The distributed lock is used to ensure that only one user or one machine reads and operates to avoid the situation where multiple processes perform cash withdrawal compensation simultaneously or repeat cash withdrawal compensation simultaneously.

[0101] Specifically, after successfully obtaining the distributed lock permission of the user's account, query whether the bank interface log table is an empty set; if not, call the cash withdrawal service query interface to query whether there is an empty set of cash withdrawal services; if not, call the transaction interface corresponding to the cash withdrawal request to obtain the transaction data message, and return the step of updating the interface information record table according to the transaction data message and feedbacking the transaction result.

[0102] In this embodiment, in response to the cash withdrawal request, query the cash withdrawal interface information record table of the user; detect whether the cash withdrawal interface information record table is recorded; if so, detect the status parameter of the cash withdrawal interface information record table; when the status parameter is a preset parameter, call the cash withdrawal transaction interface to determine whether there is a historical record of calling the transaction interface; if there is no historical record of calling the transaction interface, call the transaction interface corresponding to the cash withdrawal request to obtain the transaction data message, reduce the situation where multiple processes execute the cash withdrawal service simultaneously, and reduce the cash withdrawal risk.

[0103] Based on the second embodiment of the present application, in the third embodiment of the present application, the same or similar content as in the above-mentioned first embodiment can be referred to the above introduction and will not be repeated hereinafter. On this basis, please refer to Figure 5 , step S20 further includes:

[0104] Step S201ˋ: In response to the payment request, query the payment interface information record table corresponding to the user;

[0105] Step S202ˋ: Detect whether the payment interface information record table is recorded;

[0106] Step S203`: If so, detect the status parameter of the payment interface information record table;

[0107] Step S204`: When the status parameter is a preset parameter, call the payment interface corresponding to the payment request to obtain the transaction data message.

[0108] It should be noted that, referring to Figure 6 , Figure 6 is the process schematic diagram of the payment service in this embodiment. Different from the cash withdrawal service, for the payment service, the status flag of the interface information record table will change only after successful payment. Therefore, in this embodiment, when the user initiates a payment request, the user terminal will query the status flag of the interface log. If the status flag is 0, it will detect whether there is a record table. If there is, it will directly call the payment service; if not, it will determine whether the user terminal has generated a payment service interface. If not, it will create a new interface log table and remotely call the payment service.

[0109] The user terminal remotely calls the payment service. Different from the synchronous call method used in the cash withdrawal service, in the face of the payment service, this embodiment uses an asynchronous call method to query the interface information record table to check whether the platform already has a historical record of this cash withdrawal service, so as to avoid repeated cash withdrawals.

[0110] Specifically, if it is detected that the payment interface information record table has been recorded, then by detecting the status parameter of the payment interface information record table, if the status parameter is 0, call the transaction interface corresponding to the payment request to obtain the transaction data message. Before obtaining the transaction data message, it is also possible to detect whether there is a network exception through the transaction interface. When there is no network exception, then call the transaction interface to obtain the transaction data message feedback by the bank. If there is a network exception, query the interface retry log record. If it is within 3 retries, generate a warning message. If it is beyond 3 retries, return the initialization state to the caller and perform the payment compensation process.

[0111] Among them, if it is detected that the payment interface information record table has not been recorded, it indicates that this transaction has not been successfully executed, and the result of payment failure will be directly returned.

[0112] In this embodiment, after obtaining the transaction message data feedback by the bank, it can be detected whether the structure header of the transaction message data is an empty set. If so, it indicates that a transaction exception has occurred, and it is necessary to update the interface information record table in time and modify the transaction service status to "failed" or "unknown exception".

[0113] After obtaining the transaction message data that is not an empty set, the transaction business status of this time can be modified to "processing" or "successful", and the transaction business status can be fed back to the user. At the same time, the remote call Portal service process is called to prompt the user to modify the transaction record and modify the user's account information to complete information synchronization.

[0114] Further, the platform transaction monitoring method is also used for:

[0115] In response to a payment compensation query request, call the payment record status query interface, where the payment compensation query request is a periodically generated status query task;

[0116] Obtain the distributed lock permission of the user account;

[0117] When successfully obtaining the distributed lock permission of the user account,

[0118] Generate a standard status flag, and based on the standard status flag, call the payment main process program to determine whether there is a new payment record.

[0119] In a specific implementation, refer to Figure 7 , Figure 7 which is the flow diagram of payment compensation in this embodiment. When the retry fails more than 3 times, the payment compensation service can be initiated after a certain interval. In the payment compensation service, the distributed lock of the user account is obtained to obtain the relevant operation permissions of the user account. The distributed lock is used to ensure that only one user or one machine reads and operates to avoid the situation where multiple processes perform cash withdrawal compensation simultaneously or repeatedly.

[0120] Specifically, after successfully obtaining the distributed lock permission of the user account, by generating a standard status flag and based on the standard status flag, calling the payment main process program to determine whether there is a new payment record, and returning the step of updating the interface information record table according to the transaction data message and feeding back the transaction result.

[0121] In this embodiment, in response to the payment request, query the payment interface information record table corresponding to the user; detect whether the payment interface information record table is recorded; if so, detect the status parameter of the payment interface information record table; when the status parameter is a preset parameter, call the payment interface corresponding to the payment request to obtain the transaction data message, reducing the situation where multiple processes execute the payment service simultaneously and reducing the risk of duplicate payment.

[0122] Based on the third embodiment of the present application, in the fourth embodiment of the present application, the content that is the same as or similar to the above-mentioned first embodiment can be referred to the above introduction and will not be repeated hereinafter. On this basis, please refer to Figure 8, step S20 further includes:

[0123] Step S201ˋˋ: In response to the recharge request, verify the transaction record table, which records the transaction record data of the user;

[0124] Step S202ˋˋ: Query the recharge interface information record table corresponding to the user;

[0125] Step S203ˋˋ: Detect whether the recharge interface information record table is recorded;

[0126] Step S204ˋˋ: If not, call the payment interface corresponding to the recharge request and verify whether there is a network exception;

[0127] Step S205ˋˋ: If there is no network exception, generate a recharge information record table;

[0128] Step S206ˋˋ: Update the transaction record table according to the recharge information record table.

[0129] It should be noted that the recharge request is used to request the conversion of digital funds from other platforms or banks into the balance, red envelopes or other digital funds available for commodity transactions in the user's account on the platform. Therefore, in the recharge business, it is necessary for the user to have confirmed the payment, that is, after the recharge business has been completed, the relevant recharge request will be executed. Refer to Figure 9 , Figure 9 is the schematic diagram of the recharge process of this embodiment. In the recharge process, by verifying the transaction record table and querying the recharge interface information record table corresponding to the user to detect whether the recharge interface information record table is recorded. If it is not recorded, call the payment interface corresponding to the recharge request and verify whether there is a network exception; if there is no network exception, generate a recharge information record table; finally, update the transaction record table and the user's fund account table according to the recharge information record table.

[0130] Further, after verifying whether there is a network exception, it further includes:

[0131] If there is a network exception, switch the service query interface and return to the step of querying the recharge interface information record table corresponding to the user;

[0132] When the number of switches is greater than the preset number, generate an alarm message.

[0133] Among them, different from the withdrawal and payment services, in this embodiment, if there is a network anomaly, but the user has actually completed the recharge payment, that is, the user's funds have been transferred out. At this time, if there is a network anomaly, the retry log record can be queried through the query interface, and when the number of retries is less than or equal to 3, the retry log record can be retried through the new modification interface to re-invoke the payment interface corresponding to the recharge request to achieve the recharge of the user account.

[0134] If the number of retries is greater than 3, an alarm message is generated to remind the platform to conduct manual review or recharge again to avoid affecting the user experience.

[0135] In this embodiment, by responding to the recharge request, the transaction water table is verified, and the transaction water table records the transaction record data of the user; the recharge interface information record table corresponding to the user is queried; it is detected whether the recharge interface information record table is recorded; if not, the payment interface corresponding to the recharge request is called, and it is verified whether there is a network anomaly; if there is no network anomaly, a recharge information record table is generated; the transaction water table is updated according to the recharge information record table, reducing the situation where the user recharge service cannot be executed due to network anomalies and improving the user experience.

[0136] This application also provides a platform transaction monitoring device. Please refer to Figure 10 , the platform transaction monitoring device includes:

[0137] A query module 10, configured to query the interface information record table corresponding to the transaction request in response to the user's transaction request.

[0138] An invocation module 20, configured to invoke the transaction interface corresponding to the transaction request according to the interface information record table to obtain a transaction data message.

[0139] An update module 30, configured to update the interface information record table according to the transaction data message and feedback the transaction result.

[0140] In this embodiment, by responding to the user's transaction request, querying the interface information record table corresponding to the transaction request; invoking the transaction interface corresponding to the transaction request according to the interface information record table to obtain a transaction data message; updating the interface information record table according to the transaction data message and feedbacking the transaction result, there is no need to monitor the user's fund account, but the transaction data message generated during the transaction service process is invoked through the transaction interface corresponding to the transaction request to effectively monitor the transaction service, avoiding the technical problem of low monitoring efficiency for the transaction service result in the prior art.

[0141] In one embodiment, the calling module 20 is further configured to, in response to the cash withdrawal request, query the cash withdrawal interface information record table of the user; detect whether the cash withdrawal interface information record table is recorded; if so, detect the status parameter of the cash withdrawal interface information record table; when the status parameter is a preset parameter, call the cash withdrawal transaction interface to determine whether there is a historical record of calling the transaction interface; if there is no historical record of calling the transaction interface, call the transaction interface corresponding to the cash withdrawal request to obtain the transaction data message.

[0142] In one embodiment, the calling module 20 is further configured to, in response to the cash withdrawal compensation query request, call the cash withdrawal transaction status query interface, where the cash withdrawal compensation query request is a periodically generated status query task; obtain the distributed lock permission of the user account; when successfully obtaining the distributed lock permission of the user account, query whether the bank interface log table is an empty set; if not, call the cash withdrawal service query interface to query whether there is an empty set of cash withdrawal services; if not, call the transaction interface corresponding to the cash withdrawal request to obtain the transaction data message.

[0143] In one embodiment, the calling module 20 is further configured to, in response to the payment request, query the payment interface information record table corresponding to the user; detect whether the payment interface information record table is recorded; if so, detect the status parameter of the payment interface information record table; when the status parameter is a preset parameter, call the payment interface corresponding to the payment request to obtain the transaction data message.

[0144] In one embodiment, the calling module 20 is further configured to, in response to the payment compensation query request, call the payment transaction status query interface, where the payment compensation query request is a periodically generated status query task; obtain the distributed lock permission of the user account; when successfully obtaining the distributed lock permission of the user account, generate a standard status flag, and call the payment main process program based on the standard status flag to determine whether there is a new payment record.

[0145] In one embodiment, the calling module 20 is further configured to, in response to the recharge request, verify the transaction log table, where the transaction log table records the transaction record data of the user; query the recharge interface information record table corresponding to the user; detect whether the recharge interface information record table is recorded; if not, call the payment interface corresponding to the recharge request and verify whether there is a network exception; if there is no network exception, generate a recharge information record table; update the transaction log table according to the recharge information record table.

[0146] In one embodiment, the calling module 20 is further configured to, if there is a network exception, switch the service query interface and return to the step of querying the recharge interface information record table corresponding to the user; when the number of switches is greater than the preset number, generate an alarm message.

[0147] The present application provides a platform transaction monitoring device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein, the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the platform transaction monitoring method in the first embodiment above.

[0148] Reference is made below to Figure 11 , which shows a schematic structural diagram of a platform transaction monitoring device suitable for implementing the embodiments of the present application. The platform transaction monitoring device in the embodiments of the present application may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions: tablet computers), PMPs (Portable Media Players), vehicle terminals (such as vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 11 The platform transaction monitoring device shown is merely an example and should not impose any limitation on the functions and usage scope of the embodiments of the present application.

[0149] As Figure 11As shown in the figure, the platform transaction monitoring device may include a processing device 1001 (such as a central processing unit, a graphics processing unit, etc.), which may perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM: Random Access Memory) 1004. In the RAM 1004, various programs and data required for the operation of the platform transaction monitoring device are also stored. The processing device 1001, the ROM 1002, and the RAM 1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems may be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touchpad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 may allow the platform transaction monitoring device to communicate with other devices wirelessly or wiredly to exchange data. Although the figure shows a platform transaction monitoring device having various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems may be implemented or had alternatively.

[0150] In particular, according to the embodiments disclosed in the present application, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes program codes for performing the methods shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network through the communication device, or installed from the storage device 1003, or installed from the ROM 1002. When the computer program is executed by the processing device 1001, the above functions defined in the methods of the embodiments disclosed in the present application are executed.

[0151] The platform transaction monitoring device provided by the present application adopts the platform transaction monitoring method in the above embodiments and can solve the technical problems of platform transaction monitoring. Compared with the prior art, the beneficial effects of the platform transaction monitoring device provided by the present application are the same as those of the platform transaction monitoring method provided by the above embodiments, and other technical features in the platform transaction monitoring device are the same as those disclosed in the method of the previous embodiment, and will not be elaborated here.

[0152] It should be understood that each part disclosed in this application can be implemented by hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in a suitable manner in any one or more embodiments or examples.

[0153] As described above, the above are only specific embodiments of this application, but the protection scope of this application is not limited thereto. Any person skilled in the art within the technical scope disclosed in this application can easily think of changes or substitutions, which should all be covered within the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

[0154] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., computer programs) stored thereon, and the computer-readable program instructions are used to execute the platform transaction monitoring method in the above embodiments.

[0155] The computer-readable storage medium provided by this application can be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM) or flash memory, optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above. In this embodiment, the computer-readable storage medium can be any tangible medium that contains or stores a program, and this program can be used by or combined with an instruction execution system, device, or device. The program code contained on the computer-readable storage medium can be transmitted by any appropriate medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0156] The above computer-readable storage medium can be included in the platform transaction monitoring device; or it can exist separately and not be assembled into the platform transaction monitoring device.

[0157] The above computer-readable storage medium carries one or more programs. When the above one or more programs are executed by the platform transaction monitoring device, the platform transaction monitoring device is enabled to perform platform transaction monitoring.

[0158] Computer program code for performing the operations of this application can be written in one or more programming languages or combinations thereof. The above-mentioned programming languages include object-oriented programming languages such as Java, Smalltalk, C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, executed as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (for example, by connecting through the Internet using an Internet service provider).

[0159] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and this module, program segment, or part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than that marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, as well as the combination of blocks in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0160] The modules involved in the embodiments described in this application can be implemented in software or in hardware. Among them, the name of the module does not constitute a limitation to the unit itself in some cases.

[0161] The readable storage medium provided in this application is a computer-readable storage medium, and the computer-readable storage medium stores computer-readable program instructions (i.e., computer programs) for performing the above-mentioned platform transaction monitoring method, which can solve the technical problems of platform transaction monitoring. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the platform transaction monitoring method provided in the above embodiments, and will not be elaborated here.

[0162] The present application also provides a computer program product, including a computer program which, when executed by a processor, implements the steps of the platform transaction monitoring method as described above.

[0163] The computer program product provided by the present application can solve the technical problems of platform transaction monitoring. Compared with the prior art, the beneficial effects of the computer program product provided by the present application are the same as those of the platform transaction monitoring method provided by the above embodiments, and will not be elaborated here.

[0164] The above are only partial embodiments of the present application, and thus do not limit the patent scope of the present application. Any equivalent structural transformation made under the technical concept of the present application by using the content of the specification and drawings of the present application, or any direct / indirect application in other related technical fields, is included in the patent protection scope of the present application.

Claims

1. A platform transaction monitoring method, characterized in that, The platform transaction monitoring method includes: In response to a user's transaction request, query the interface information record table corresponding to the transaction request; Call the transaction interface corresponding to the transaction request according to the interface information record table to obtain a transaction data message; Update the interface information record table according to the transaction data message and feedback the transaction result.

2. The platform transaction monitoring method according to claim 1, characterized in that The transaction request at least includes: a withdrawal request; The step of calling the transaction interface corresponding to the transaction request according to the interface information record table to obtain a transaction data message includes: In response to the withdrawal request, query the user's withdrawal interface information record table; Detect whether the withdrawal interface information record table is recorded; If so, detect the status parameter of the withdrawal interface information record table; When the status parameter is a preset parameter, call the withdrawal transaction interface to determine whether there is a historical record of calling the transaction interface; If there is no historical record of calling the transaction interface, call the transaction interface corresponding to the withdrawal request to obtain a transaction data message.

3. The platform transaction monitoring method according to claim 2, wherein The platform transaction monitoring method further includes: In response to a withdrawal compensation query request, call the withdrawal transaction status query interface, where the withdrawal compensation query request is a periodically generated status query task; Obtain the distributed lock permission of the user account; When successfully obtaining the distributed lock permission of the user account, query whether the bank interface log table is an empty set; If not, call the withdrawal business query interface to query whether there is an empty set of withdrawal business; If not, call the transaction interface corresponding to the withdrawal request to obtain a transaction data message.

4. The platform transaction monitoring method according to claim 1, characterized in that The transaction request further includes: a payment request; The step of calling the transaction interface corresponding to the transaction request according to the interface information record table to obtain a transaction data message further includes: In response to the payment request, query the payment interface information record table corresponding to the user; Detect whether the payment interface information record table is recorded; If so, detect the status parameter of the payment interface information record table; When the status parameter is a preset parameter, call the payment interface corresponding to the payment request to obtain a transaction data message.

5. The platform transaction monitoring method according to claim 4, characterized in that, The platform transaction monitoring method is also used for: In response to a payment compensation query request, call the payment transaction status query interface, where the payment compensation query request is a periodically generated status query task; Obtain the distributed lock permission of the user account; When successfully obtaining the distributed lock permission of the user account, Generate a standard status flag and call the payment main process program based on the standard status flag to determine whether there is a new payment record.

6. The platform transaction monitoring method according to claim 1, wherein, The transaction request further includes: a recharge request; The step of calling the transaction interface corresponding to the transaction request according to the interface information record table to obtain a transaction data message further includes: In response to the recharge request, verify the transaction log table, where the transaction log table records the transaction record data of the user; Query the recharge interface information record table corresponding to the user; Detect whether the recharge interface information record table is recorded; If not, call the payment interface corresponding to the recharge request and verify whether there is a network exception; If there is no network exception, generate a recharge information record table; Update the transaction log table according to the recharge information record table.

7. The platform transaction monitoring method according to claim 6, wherein After verifying whether there is a network anomaly, it further includes: If there is a network anomaly, switch the service query interface and return to the step of querying the recharge interface information record table corresponding to the user; When the number of switches is greater than the preset number, generate an alarm message.

8. A platform transaction monitoring device, characterized in that, The platform transaction monitoring device includes: A query module, configured to query the interface information record table corresponding to the transaction request in response to a user's transaction request; A call module, configured to call the transaction interface corresponding to the transaction request according to the interface information record table to obtain a transaction data packet; An update module, configured to update the interface information record table according to the transaction data packet and feedback a transaction result.

9. A platform transaction monitoring device, characterized in that, The platform transaction monitoring device includes: a memory, a processor, and a platform transaction monitoring program stored on the memory and executable on the processor, the platform transaction monitoring program being configured to implement the platform transaction monitoring method according to any one of claims 1 to 7.

10. A storage medium, characterized in that, The platform transaction monitoring program is stored on the storage medium, and when the platform transaction monitoring program is executed by the processor, it implements the platform transaction monitoring method according to any one of claims 1 to 7.

Images