CN117291612A - Data verification method, device, equipment, medium and product - Google Patents
Data verification method, device, equipment, medium and product Download PDFInfo
- Publication number
- CN117291612A CN117291612A CN202311308356.7A CN202311308356A CN117291612A CN 117291612 A CN117291612 A CN 117291612A CN 202311308356 A CN202311308356 A CN 202311308356A CN 117291612 A CN117291612 A CN 117291612A
- Authority
- CN
- China
- Prior art keywords
- transaction
- payment
- order
- transaction flow
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 64
- 238000013524 data verification Methods 0.000 title claims abstract description 38
- 238000012545 processing Methods 0.000 claims abstract description 96
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 claims abstract description 92
- 238000012795 verification Methods 0.000 claims abstract description 71
- 230000002159 abnormal effect Effects 0.000 claims description 146
- 238000004590 computer program Methods 0.000 claims description 16
- 230000008569 process Effects 0.000 description 14
- 238000010586 diagram Methods 0.000 description 10
- 238000004891 communication Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 5
- 230000004044 response Effects 0.000 description 5
- 230000009471 action Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 3
- 230000005856 abnormality Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000007792 addition Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 239000010453 quartz Substances 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- VYPSYNLAJGMNEJ-UHFFFAOYSA-N silicon dioxide Inorganic materials O=[Si]=O VYPSYNLAJGMNEJ-UHFFFAOYSA-N 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2282—Tablespace storage structures; Management thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Accounting & Taxation (AREA)
- Data Mining & Analysis (AREA)
- General Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Finance (AREA)
- Software Systems (AREA)
- Computer Security & Cryptography (AREA)
- Computational Linguistics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application discloses a data verification method, a data verification device, data verification equipment, data verification media and data verification products, and relates to the technical field of data processing. According to the embodiment of the application, the first transaction flow water meter is acquired according to the preset time interval, the payment result identifier and the first payment amount of the order acquired from the third party system are utilized to verify the flow data of the order which is not paid in the first transaction flow water meter, and because the preset time interval is smaller than or equal to the first threshold value, namely the transaction data locally stored in a short time can be verified, the timeliness of verification is improved, and the consistency and the accuracy of transaction are guaranteed.
Description
Technical Field
The present disclosure relates to the field of data processing technologies, and in particular, to a data verification method, device, apparatus, medium, and product.
Background
In the process of paying orders or refunds based on electronic equipment, the users may cause abnormal order payment or refund abnormality due to network instability, abnormal service, overtime response and other reasons. For example, in the case of an abnormal order payment, it may happen that the account of the user has been paid successfully, but the electronic device does not receive a response of successful payment, resulting in an abnormal order payment state. For another example, in the case of abnormal refund, it may happen that the refund has been successfully returned to the account of the user, but the electronic device does not receive a response of the refund success, resulting in abnormal refund status of the order.
Content of the application
The embodiment of the application provides a data verification method, a device, equipment, a medium and a product, which can be used for verifying locally stored transaction flow data in time and improving the consistency and accuracy of transactions.
In a first aspect, an embodiment of the present application provides a data verification method, including:
acquiring a first transaction flow meter according to a preset time interval, wherein the preset time interval is smaller than or equal to a first threshold value, and the first transaction flow meter is used for storing first transaction flow data of at least one transaction locally, and the first transaction flow data comprises flow data of orders which are not paid;
for each transaction in the first transaction flow water meter, second transaction flow data corresponding to the transaction is obtained from a third party system, wherein the second transaction flow data comprises a payment result identifier of an order and a first payment amount;
and under the condition that at least one of the payment result identification and the first payment amount does not meet the first condition, updating the flow data of the order which is not paid in the first transaction flow water meter according to the payment result identification and the first payment amount.
In a second aspect, an embodiment of the present application provides a data verification apparatus, including: an acquisition module and an update module;
The acquisition module is used for acquiring a first transaction flow water meter according to a preset time interval, wherein the preset time interval is smaller than or equal to a first threshold value, the first transaction flow water meter is used for storing first transaction flow data of at least one transaction locally, and the first transaction flow data comprises flow data of orders which are not paid;
the acquisition module is further used for acquiring second transaction flow data corresponding to the transactions from the third party system for each transaction in the first transaction flow meter, wherein the second transaction flow data comprises a payment result identifier of the order and a first payment amount;
and the updating module is used for updating the flow data of the order which is not paid in the first transaction flow water meter according to the payment result identifier and the first payment amount under the condition that at least one of the payment result identifier and the first payment amount does not meet the first condition.
In a third aspect, an embodiment of the present application provides an electronic device, including:
a processor;
a memory for storing computer program instructions;
the computer program instructions, when executed by a processor, implement the method as described in the first aspect.
In a fourth aspect, embodiments of the present application provide a computer readable storage medium having stored thereon computer program instructions which, when executed by a processor, implement a method as described in the first aspect.
In a fifth aspect, embodiments of the present application provide a computer program product, instructions in which, when executed by a processor of an electronic device, cause the electronic device to perform the method according to the first aspect.
According to the embodiment of the application, the first transaction flow water meter is acquired according to the preset time interval, the payment result identifier and the first payment amount of the order acquired from the third party system are utilized to verify the flow data of the order which is not paid in the first transaction flow water meter, and because the preset time interval is smaller than or equal to the first threshold value, namely the transaction data locally stored in a short time can be verified, the timeliness of verification is improved, and the consistency and the accuracy of transaction are guaranteed.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments of the present application will be briefly described below, and it is possible for a person skilled in the art to obtain other drawings from these drawings without inventive effort.
FIG. 1 is a flowchart of a data verification method according to an embodiment of the present application;
FIG. 2 is a flowchart of another data verification method according to an embodiment of the present disclosure;
FIG. 3 is a block diagram of a data verification device according to an embodiment of the present application;
fig. 4 is a block diagram of an electronic device according to an embodiment of the present application.
Detailed Description
Features and exemplary embodiments of various aspects of the present application are described in detail below, and in order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are merely configured to explain the present application and are not configured to limit the present application. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the present application by showing examples of the present application.
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 … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
It should be noted that, the data acquisition, storage, use, processing and the like in all embodiments of the present application meet relevant regulations of national laws and regulations.
When the related technology performs data verification, transaction data is obtained from a third party payment system by manpower, and then the transaction data is compared with a local order state, so that the timeliness is poor, and the accuracy is low.
Therefore, the embodiment of the application provides a data verification method, device, equipment, medium and product, which can verify locally stored transaction flow data in time and improve the consistency and accuracy of transactions.
The following describes a data verification method provided in the embodiment of the present application with reference to specific embodiments, and fig. 1 is a flowchart of a data verification method provided in the embodiment of the present application. The method can be applied to a mall application program in the electronic equipment, and the mall application program can execute the data verification method provided by the embodiment of the application by adopting a java programming language and a Quartz job scheduling framework. The electronic device may be a desktop, a notebook, a server, a service platform, etc. having data processing functions.
As shown in fig. 1, the data verification method may include the steps of:
S110, acquiring a first transaction flow meter according to a preset time interval.
The preset time interval is smaller than or equal to a first threshold value, and the first transaction flow meter is used for storing first transaction flow data of at least one transaction locally, wherein the first transaction flow data comprises flow data of orders which are not paid.
S120, for each transaction in the first transaction flow water meter, second transaction flow data corresponding to the transaction is obtained from the third party system.
The second transaction arrangement data includes a payment result identification of the order and a first payment amount.
S130, updating the flow data of the order which is not paid in the first transaction flow water meter according to the payment result identification and the first payment amount under the condition that at least one of the payment result identification and the first payment amount does not meet the first condition.
According to the embodiment of the application, the first transaction flow water meter is acquired according to the preset time interval, the payment result identification and the first payment amount of the order acquired from the third party system are utilized to verify the flow data of the order which is not paid in the first transaction flow water meter, and because the preset time interval is smaller than the first threshold value, namely the transaction data locally stored in a short time can be verified, the timeliness of verification is improved, and the consistency and the accuracy of transaction are guaranteed.
The following describes the above steps in detail, as follows:
in S110, the preset time interval is smaller than or equal to the first threshold, which may be set to 5 minutes, for example, that is, the embodiment of the present application may obtain the first transaction flow meter once every 5 minutes or less, so as to implement real-time verification of transaction data, discover abnormal transactions in time, and reduce the frequency of order payment and order drop.
The first transaction flow meter is used for storing first transaction flow data of at least one transaction locally. The transactions herein may include, but are not limited to, transaction types such as payment transactions, refund transactions, and the like.
The first transaction flow data is transaction flow data locally stored by the electronic device when the user performs transactions based on the electronic device, and illustratively, the first transaction flow data can comprise flow data of orders which are not paid, and the flow data of the orders which are not paid can comprise, for example, date of the orders, amount of the orders and the like.
By way of example, transaction flow data of each transaction can be arranged according to transaction dates, so that verification can be conveniently carried out according to dates, and verification omission is avoided.
In S120, the third party system may be a payment system, which is associated with the mall application, i.e. the mall application may call the third party system to complete the verification.
The second transaction aggregate data is aggregate data for each transaction recorded in the third party system, and illustratively, the second transaction data may include a payment result identification of the order and the first payment amount.
The payment result identification is used to identify whether the payment result is a payment success or a payment failure. The first payment amount is a payment amount recorded by the third party system when the payment is successful.
For each transaction in the first transaction stream meter, the mall application may, for example, call an interface of the third party system through which second transaction stream data corresponding to the transaction is obtained.
For example, a certain amount of transaction flow data may be read from the first transaction flow table according to a preset frequency, and then, for each transaction, second transaction flow data corresponding to the transaction is obtained from the third party system.
The preset frequency may be set according to actual needs, for example, may be set to 10s, that is, the transaction flow data may be read from the first transaction flow table every 10 s. Illustratively, the number of transaction streamlines per read may not exceed 50, which may improve query efficiency.
For example, after the transaction flow data is read from the first transaction flow table, the flow state of the transaction flow data may be set as a query, the number of queries may be +1, and then the second transaction flow data corresponding to the transaction may be queried from the third party system.
In S130, the first condition may include, for example, at least one of an identification that the payment result identifies as a payment failure, a first payment amount not matching a locally stored second payment amount. The first payment amount and the second payment amount not matching may be the first payment amount and the second payment amount not being equal.
In an exemplary case that at least one of the payment result identifier and the first payment amount does not meet the first condition, the running data of the order which is not paid in the first transaction flow water meter can be updated according to the payment result identifier and the first payment amount, so that the checking of the running data information of the order which is not paid in the first transaction flow water meter is realized.
In practical application, the third party system may or may not have second transaction flow data corresponding to the transaction.
In an exemplary case, the third party system may be queried again when the query fails, that is, the second transaction flow data is not acquired, and in an exemplary case, if the number of queries reaches the upper limit value, the flow state of the transaction may be updated to be the end of the query, otherwise, the transaction is set to be queried, and the next round of query is waited. The upper limit value may be set to 3 times, for example.
In an exemplary case that the query is successful, that is, the second transaction flow data is obtained, the flow data of the order which is not paid in the first transaction flow water meter is checked according to the payment result identifier of the order and the first payment amount, so that automatic check of the transaction data is realized, manual execution is not needed, and therefore the check efficiency and the check accuracy are improved.
For example, in the case where the payment result is identified as successful payment and the first payment amount does not match the second payment amount, the abnormal transaction flow information may also be generated and stored in the abnormal transaction flow meter.
The abnormal transaction flow information is used for recording flow information of abnormal transactions, for example, abnormal flow data of orders which are not paid can be recorded in the embodiment of the application.
Illustratively, the abnormal transaction flow information may include, but is not limited to, an order exception type, a processing mode, and a processing status for outstanding payments.
The anomaly types may include, for example, types of inconsistent amounts, inconsistent payment status, non-existent orders, and the like. For example, in the embodiment of the present application, the abnormal type of the order of the outstanding payment is inconsistent.
The processing modes may include a manual processing mode and a system processing mode, and for an exception account, an exception transaction that cannot be processed by the system may be processed manually. The abnormal transactions that the system may process may include, for example, abnormal transactions waiting for a refund. For abnormal transactions waiting for refunds, the system may initiate online refunds, which may improve refund efficiency.
The processing state is used to identify whether the abnormal transaction is processed, and may include unprocessed, processed, no processing required, and so forth, for example.
And processing the abnormal flow information in the abnormal transaction flow water meter according to the corresponding processing mode.
In some embodiments, the step S130 may include the following steps:
updating the running state of the order with incomplete payment to be the end of the inquiry and updating the payment state of the order with incomplete payment to be the failure of payment under the condition that the payment result identifier is a first identifier, wherein the first identifier is used for identifying that the payment result of the order with incomplete payment is the failure of payment;
updating the running state and the payment state of the unfinished order according to the first matching result of the first payment amount and the locally stored second payment amount under the condition that the payment result identifier is the second identifier, wherein the second identifier is used for identifying that the payment result of the unfinished order is successful;
And under the condition that the first payment amount is not matched with the second payment amount stored locally as a result of the first matching, recording the verification state of the order which is not paid is verified to be wrong.
The first identifier is used to identify that the payment result of the order that is not paid is a payment failure, and the first identifier may be represented by "0" in an exemplary manner, or may be represented by other manners, which are not limited in the embodiment of the present application.
The second identifier is used to identify that the payment result of the order that is not paid is successful, and the first identifier may be indicated by "1" for example, or may be indicated by other manners, which are not limited in the embodiment of the present application.
For example, in the case that the payment result identifier is the first identifier, the running status of the order that is not paid may be updated as the query result, and at the same time, the payment status of the order that is not paid may be updated as the payment failure.
In an exemplary case, if the payment result identifier is the second identifier, it may be further determined whether the first payment amount matches the locally stored second payment amount, so as to obtain a first matching result. For example, the first matching result may include that the first payment amount matches the second payment amount, i.e. the first payment amount equals the second payment amount, or that the first payment amount does not match the second payment amount, i.e. the first payment amount does not equal the second payment amount.
And updating the running state and the payment state of the order of the unfinished payment according to the matching result of the first payment amount and the second payment amount.
For example, in the case where the first payment amount matches the second payment amount, the running status of the outstanding paid order may be updated to query end and the payment status of the outstanding paid order may be updated to payment success;
in the case where the first payment amount does not match the second payment amount, the running status of the order for outstanding payments may be updated to query completion and the payment status of the order for outstanding payments may be updated to payment success.
For example, in the case that the first payment amount does not match the second payment amount, the verification status of the order that has not been paid for may also be recorded as verified error in the first transaction flow meter.
After the round of scheduling is finished, the running data of the next order which is not paid is processed continuously.
According to the embodiment of the application, under the condition that the second transaction flow data exists, the flow state, the payment state and the verification state of the local unfinished order can be further verified according to the payment result identification and the first payment amount in the second transaction flow data, so that the timeliness of verification is improved, and the probability of ordering the order is reduced.
The embodiment of the application not only can utilize the transaction flow data in the third party system to verify the locally stored transaction flow data in real time, but also can verify the transaction flow data in the third party system based on the locally stored transaction flow data in real time. Illustratively, as shown in FIG. 2, the verification method may include the steps of:
s210, acquiring a first transaction flow meter according to a preset time interval.
S220, for each transaction in the first transaction flow water meter, second transaction flow data corresponding to the transaction is obtained from the third party system.
And S230, updating the flow data of the order which is not paid in the first transaction flow water meter according to the payment result identification and the first payment amount under the condition that at least one of the payment result identification and the first payment amount does not meet the first condition.
S240, acquiring a check file from the third party system.
The verification file includes transaction data for at least one transaction.
S250, inquiring the first transaction flow water meter and judging whether the first transaction exists in the first transaction flow water meter under the condition that the first transaction is payment transaction.
And S260, under the condition that the first transaction exists in the first transaction flow water meter and the local payment state of the first transaction is unknown or the payment fails, updating the payment state of the corresponding transaction in the first transaction flow water meter to be successful in payment, and checking the payment state to be checked.
S270, generating first abnormal transaction flow information of the first transaction, and storing the first abnormal transaction flow information into an abnormal transaction flow meter.
The process of S210-S230 may be referred to the above embodiments, and will not be described herein for brevity.
The following describes the other steps in detail, and is specifically as follows:
in S240, the verification file may include transaction data of each transaction, and illustratively, the mall application may obtain the verification file from the third party system at a preset time interval, so as to verify the transaction data in the third party system in real time.
For example, the verification file may be downloaded from the third party system, and when the verification file is not downloaded, the downloading state of the third party verification flowing information may be recorded as failure, the importing state as not started, the pairing state as not started, and the system operation and maintenance personnel may be notified to end the scheduling. The system operation and maintenance personnel can be informed by means of short messages, mails and the like.
For example, when the verification file is successfully downloaded, it may be recorded that the third party verification pipeline information is successfully downloaded, the import state is not started, and the verification state is not started.
For example, after the verification file is downloaded successfully, the verification file may be parsed to obtain transaction data of each transaction. The transaction data may be imported, for example, into a third party transaction verification trickle meter, which may be stored locally for recording verification flowing information for each transaction.
In S250, the first transaction is any transaction in the verification document, and for example, each transaction in the third-party transaction verification capillary flow meter may be used as the first transaction one by one according to the transaction date, and the verification process may be performed on the first transaction.
Taking the first transaction as a payment transaction for example, for each first transaction, it may be determined whether the first transaction exists in the first transaction flow meter, i.e. is stored locally.
In the case that the first transaction exists in the first transaction flow water meter, abnormal flow information of an order can be inserted into the abnormal transaction flow water meter, and the abnormal flow information can comprise the flow type of payment, the abnormal type of order does not exist, the processing mode of manual processing and the processing state of no processing.
For example, in the case where the first transaction exists in the first transaction flow meter, it may be further determined whether the payment status of the first transaction locally is successful. In an exemplary case where the first transaction exists in the first transaction flow meter and the payment status of the first transaction is unknown or fails, the payment status of the corresponding transaction in the first transaction flow may be updated to be successful and the verification status is verified to be incorrect.
The payment state is unknown and is caused by the fact that the mall application program does not receive the payment response due to network instability, service abnormality, response timeout and the like.
For example, in the case that the first transaction exists in the first transaction flow meter and the local payment state of the first transaction is unknown or the payment fails, the abnormal flow information of an order, that is, the first abnormal transaction flow information, may be inserted into the abnormal transaction flow meter.
For example, the first abnormal transaction flow information may include a flow type of payment, an abnormal type of payment status inconsistency, a processing mode of system processing, a processing status of waiting for a refund.
According to the method and the device for verifying the first transaction in the third party system, based on whether the first transaction exists locally or not, the first transaction in the third party system can be verified in real time in combination with the payment state of the first transaction locally, and timeliness of verification is guaranteed.
In the case that the first transaction exists in the first transaction flow meter and the local payment status of the first transaction is successful, the data verification method may further include the following steps, for example, after S250:
updating the verification state of the first transaction according to a second matching result of the third payment amount of the first transaction and the fourth payment amount of the locally stored transaction when the first transaction exists in the first transaction flow meter and the local payment state of the first transaction is successful;
and under the condition that the second matching result is that the third payment amount is not matched with the fourth payment amount, generating second abnormal transaction flow information of the first transaction, and storing the second abnormal transaction flow information into an abnormal transaction flow meter.
The third transaction amount is the transaction amount of the first transaction recorded in the third party system, and the fourth transaction amount is the transaction amount of the first transaction stored locally.
In an exemplary embodiment, the first transaction exists in the first transaction flow meter, and if the local payment status of the first transaction is that the payment is successful, it may be further determined whether the third transaction amount matches the fourth transaction amount, so as to obtain the second matching result.
For example, the second match result may include the third transaction amount matching the fourth transaction, or the third transaction amount not matching the fourth transaction. Based on the second match result, the verification status of the first transaction may be updated.
For example, in the event that the third payment amount matches the fourth payment amount, the verification status of the first transaction may be updated to verified; in the event that the third payment amount does not match the fourth payment amount, the verification status of the first transaction may be updated to verified errors.
For example, in the event that the third payment amount does not match the fourth payment amount, second abnormal transaction running water information for the first transaction may be generated and stored in the abnormal transaction running water meter. For example, the second abnormal transaction flow information may include that the flow type of the first transaction is payment, the abnormal type is inconsistent in amount, the processing mode is manual processing, and the processing state is waiting for processing.
According to the embodiment of the invention, when the first transaction exists in the first transaction flow water meter, and the local payment state of the first transaction is that the payment is successful, the flow data of the first transaction can be further checked based on the matching result of the third payment amount and the fourth payment amount, so that the accuracy of the checking result is improved, and meanwhile, under the condition that the third payment amount and the fourth payment amount are not matched, an abnormal transaction record can be inserted into the abnormal transaction flow water meter, and the follow-up checkout is convenient.
In some embodiments, the first transaction flow data may further include flow data of payment transactions, taking the first transaction as a refund transaction as an example, and the data verification method may further include the steps of:
under the condition that the first transaction is refund transaction, inquiring a second transaction flow water meter, judging whether the first transaction exists in the second transaction flow water meter or not, wherein the second transaction flow water meter is used for storing flow data of the refund transaction;
judging whether the first transaction exists in the first transaction flow water meter or not under the condition that the first transaction does not exist in the second transaction flow water meter, and obtaining a third judgment result;
and generating corresponding abnormal transaction running water information according to the third judgment result, and storing the corresponding abnormal transaction running water information into the abnormal transaction running water meter.
For example, in the case where the first transaction is a refund transaction, it may be determined whether the first transaction is present in the second transaction flow meter, i.e. whether there is local storage. For example, if the first transaction exists in the second transaction flow meter, it may be further determined whether the local refund status of the first transaction is successful and whether the amount of the first transaction in the third party system is equal to the locally stored amount, and if the local refund status of the first transaction is not successful (e.g., may be unsuccessful or unknown) and the amount is equal, the local order refund status may be updated to successful and the verification status is verified.
For example, if the first transaction is not successful in the local refund status (e.g., may be unsuccessful or unknown) and the amounts are not equal, the local order refund status may be updated to successful and the verification status is verified to be incorrect. And generating abnormal transaction flow information, and adding the abnormal transaction flow information into an abnormal transaction flow water meter, wherein the flow type of the abnormal transaction is refund, the abnormal type is inconsistent in state and amount, the processing mode is manual processing, and the processing state is waiting for processing.
For example, if the first transaction is successful in the local refund state, it may be further determined whether the refund amounts are equal, if not, the local verification state may be updated to be verified to be incorrect, and an abnormal transaction flow information is generated at the same time, and added to the abnormal transaction flow water meter, for example, the flow type of the abnormal transaction is refund, the abnormal type is inconsistent in amount, the processing mode is manual processing, and the processing state is waiting for processing.
For example, if the refund amounts are equal, the local check state may be updated to checked.
For example, in the case that the first transaction does not exist in the second transaction flow meter, that is, the first transaction does not exist in the local refund transaction flow data, it may be determined whether the first transaction exists in the first transaction flow meter, that is, whether the first transaction exists in the local payment transaction flow data, to obtain the third determination result.
And according to the third judgment result, corresponding abnormal transaction flow information can be generated, and the corresponding abnormal transaction flow information is stored into the abnormal transaction flow meter.
For example, in the case where the first transaction exists in the first transaction flow meter, fifth abnormal transaction flow information of the first transaction may be generated and stored into the abnormal transaction flow meter; in the case that the first transaction does not exist in the first transaction flow meter, sixth abnormal transaction flow information of the first transaction can be generated and stored in the abnormal transaction flow meter.
Illustratively, the fifth abnormal transaction flow information may include a flow type of refund, an abnormal type of order absence, a processing mode of manual processing, and a processing state of waiting for processing.
Illustratively, the sixth abnormal transaction flow information may include a flow type of refund, an abnormal type of order absence, a processing mode of manual processing, a processing status of no processing.
According to the embodiment of the invention, the refund transaction flow data in the third party system can be automatically checked by utilizing the locally stored refund transaction flow data and the locally stored payment transaction flow data, so that the checking efficiency and the accuracy of the checking result are improved.
In some embodiments, the first transaction aggregate data may also include aggregate data of orders that were paid successfully and that were not verified; correspondingly, the data verification method can further comprise the following steps:
updating the verification state of the first order to be verified by mistake under the condition that the first order does not exist in a third transaction flow water meter for each first order, wherein the first order is any one of the orders which are successfully paid and are not verified, and the third transaction flow water meter is used for storing flow data of each first transaction after verification processing;
generating third abnormal transaction flow information of the first order, and storing the third abnormal transaction flow information into an abnormal transaction flow meter;
updating the verification state of the first order according to the matching result of the local fifth payment amount of the first order and the sixth payment amount in the third transaction flow water meter when the first order exists in the third transaction flow water meter;
and under the condition that the fifth payment amount is not matched with the sixth payment amount, generating fourth abnormal transaction running water information of the first order, and storing the fourth abnormal transaction running water information into an abnormal transaction running water meter.
For each first order that is successfully paid and is not verified, the method can query whether the first order exists in the third transaction flow water meter, and when the first order does not exist in the third transaction flow water meter, the verification state of the first order can be updated to be in error after verification, and meanwhile abnormal transaction flow information of the first order, namely third abnormal transaction flow information, is generated and stored in the abnormal transaction flow water meter.
For example, the third abnormal transaction flow information may include a flow type of payment, an abnormal type of check details not present, a processing mode of manual processing, a processing state of waiting for processing.
For example, in the case that the first order exists in the third transaction flow meter, the verification state of the first order may be updated according to a result of matching the local fifth payment amount of the first order with the sixth payment amount in the third transaction flow meter.
For example, the check status of the first order may be updated to checked if the fifth payment amount matches the sixth payment amount, and the check status of the first order may be updated to checked if the fifth payment amount does not match the sixth payment amount.
For example, in the event that the fifth payment amount does not match the sixth payment amount, fourth abnormal transaction flow information for the first order may be generated and stored in the abnormal transaction flow meter.
Illustratively, the fourth abnormal transaction flow information may include a flow type of payment, an abnormal type of non-uniform amount, a processing mode of manual processing, and a processing state of waiting for processing.
According to the embodiment of the application, the transaction flow data in the third party system after verification can be utilized to verify the flow data of the order which is successfully paid and is not verified and stored locally in real time, and manual intervention is not needed, so that the verification efficiency is improved, errors caused by manual verification are avoided, and the accuracy and timeliness of the verification result are improved.
In some embodiments, for the running data of the second order that is successful and not checked in refund, for example, it may be queried whether the second order exists in the third transaction flow meter, if not, the check state of the second order may be updated to be checked, and an abnormal transaction running information is generated and stored in the abnormal transaction flow meter, for example, the abnormal transaction running information may include that the running type is refund, the abnormal type is check details are not present, the processing mode is manual processing, and the processing state is waiting to be processed.
For example, if the second order exists in the third transaction flow meter, it may be further determined whether the refund amount stored locally is consistent with the refund amount recorded in the third transaction flow meter, and if so, the verification status of the second order may be updated to verified; if the two orders are inconsistent, the verification state of the second order can be updated to be the verified error, and meanwhile, abnormal transaction flow information is generated and stored in the abnormal transaction flow meter, and the abnormal transaction flow information can comprise that the flow type is refund, the abnormal type is inconsistent in amount, the processing mode is manual processing, and the processing state is waiting for processing.
After the verification of the stream data of each transaction is finished, the verification state of the stream data of the final daily verification can be updated to be successful.
In some embodiments, after S130, the data verification method may further include the steps of:
and according to the processing mode of the abnormal transaction running water information in the abnormal transaction running water meter, adopting a corresponding processing strategy to process the abnormal transaction running water information.
For example, the abnormal transaction flow information in the abnormal transaction flow meter may be processed according to a preset frequency, which may be set according to actual needs, for example, may be performed every 5 minutes. Illustratively, the number of abnormal transaction flow information acquired from the abnormal transaction flow meter at a time may be smaller than N, and the size of N may be set according to actual needs, for example, N may be set to 50, so that the verification efficiency may be improved.
The processing mode and the processing state of the abnormal transaction flow information are set when the abnormal transaction flow water meter is added, so that the abnormal transaction flow information can be processed by adopting a corresponding processing strategy according to the processing mode and the processing state of the abnormal transaction flow information.
For each abnormal transaction flow information, it may be determined whether the processing mode of the abnormal transaction flow information is system processing and the processing state is waiting for refund, if not, the next transaction flow information is processed, if yes, the abnormal transaction flow information processing frequency +1 is updated, online refund is initiated, then whether refund is successful is determined, if refund fails, it may be determined whether the processing frequency exceeds the upper limit (3), if so, the processing mode of updating the abnormal transaction flow information is manual processing, the processing state is waiting for refund, and if not, processing is continued.
If the refund is successful, the processing state of the abnormal transaction flow information can be updated to be successful, then the next transaction is processed until the processing is finished, and the scheduling is finished.
For example, for abnormal transactions that the system cannot handle, the relevant personnel can view and verify the condition of the abnormal transaction, then manually reconcile and update the status of the abnormal transaction.
The user can log in the background, enter an order abnormal transaction management menu, screen the running information of abnormal transactions of manual processing, waiting to process/waiting for refund, initiate refund on line if the order needing refund is verified, and update the processing state of the abnormal transaction running information to be successful if refund is successful; if the refund fails, updating the processing state of the abnormal transaction flow information to wait for processing.
If the abnormal transaction flow information is checked, the processing state of the abnormal transaction flow information can be updated to be successful in manual processing.
According to the embodiment of the invention, the processing mode and the processing state of the abnormal transaction flow information in the abnormal transaction flow water meter can be processed by adopting the corresponding processing strategy, so that the consistency of the local information and the information in the third party system is ensured, and the transaction accuracy is improved.
According to the embodiment of the application, not only can real-time verification be realized, but also daily terminal verification can be performed, for example, the transaction flow data in the third party system can be verified by utilizing the locally stored transaction flow data, and the locally stored transaction flow data can be verified by utilizing the transaction flow data in the third party system, so that abnormal transactions can be found in time, and the consistency and accuracy of the transactions are improved. Meanwhile, for abnormal transactions, after verification, the system can refund in time, so that the fund loss of the user can be reduced.
Based on the same inventive concept, the embodiment of the present application further provides a data verification device, and the data verification device provided in the embodiment of the present application is described in detail below with reference to fig. 3.
Fig. 3 is a block diagram of a data verification device according to an embodiment of the present application.
As shown in fig. 3, the data verification apparatus may include: an acquisition module 310 and an update module 320;
an obtaining module 310, configured to obtain a first transaction flow meter according to a preset time interval, where the preset time interval is less than or equal to a first threshold, and the first transaction flow meter is configured to store first transaction flow data of at least one transaction locally, where the first transaction flow data includes flow data of an order that is not paid;
The obtaining module 310 is further configured to obtain, for each transaction in the first transaction flow meter, second transaction flow data corresponding to the transaction from the third party system, where the second transaction flow data includes a payment result identifier of the order and a first payment amount;
and the updating module 320 is configured to update the running data of the order that is not paid in the first transaction flow meter according to the payment result identifier and the first payment amount if at least one of the payment result identifier and the first payment amount does not satisfy the first condition.
According to the embodiment of the application, the first transaction flow water meter is acquired according to the preset time interval, the payment result identifier and the first payment amount of the order acquired from the third party system are utilized to verify the flow data of the order which is not paid in the first transaction flow water meter, and because the preset time interval is smaller than or equal to the first threshold value, namely the transaction data locally stored in a short time can be verified, the timeliness of verification is improved, and the consistency and the accuracy of transaction are guaranteed.
In some embodiments, the update module 320 is specifically configured to:
updating the running state of the order with incomplete payment to be the end of the inquiry and updating the payment state of the order with incomplete payment to be the failure of payment under the condition that the payment result identifier is a first identifier, wherein the first identifier is used for identifying that the payment result of the order with incomplete payment is the failure of payment;
Updating the running state and the payment state of the unfinished order according to the first matching result of the first payment amount and the locally stored second payment amount under the condition that the payment result identifier is the second identifier, wherein the second identifier is used for identifying that the payment result of the unfinished order is successful;
and under the condition that the first payment amount is not matched with the second payment amount stored locally as a result of the first matching, recording the verification state of the order which is not paid is verified to be wrong.
In some embodiments, the obtaining module 310 is further configured to obtain a verification file from the third party system after the updating module 320 updates the flow data of the order that is not paid in the first transaction flow meter according to the payment result identifier and the first payment amount, the verification file including transaction data of at least one transaction;
the data verification device may further include:
the inquiry module is used for inquiring the first transaction flow water meter and judging whether the first transaction exists in the first transaction flow water meter or not under the condition that the first transaction is payment transaction;
the updating module 320 is further configured to update the payment status of the corresponding transaction in the first transaction flow meter to be successful in payment and check the status to be checked to be error when the first transaction exists in the first transaction flow meter and the local payment status of the first transaction is unknown or the payment fails;
The data verification device may further include:
the generation module is used for generating first abnormal transaction flow information of the first transaction;
the storage module is used for storing the first abnormal transaction flow information into the abnormal transaction flow meter.
In some embodiments, the updating module 320 is further configured to update the verification status of the first transaction according to a second matching result of the third payment amount of the first transaction and the fourth payment amount of the locally stored transaction when the first transaction exists in the first transaction flow meter and the local payment status of the first transaction is successful after determining whether the first transaction exists in the first transaction flow meter;
the generation module is further used for generating second abnormal transaction flow information of the first transaction under the condition that the second matching result is that the third payment amount is not matched with the fourth payment amount;
the storage module is also used for storing the second abnormal transaction flow information into the abnormal transaction flow meter.
In some embodiments, the first transaction aggregate data further includes aggregate data of orders that were paid successfully and that were not verified;
the updating module 320 is further configured to update, for each first order, a verification status of the first order to be verified if the first order does not exist in the third transaction flow meter, where the first order is any one of the orders that are successfully paid and not verified, and the third transaction flow meter is configured to store flow data of each first transaction after verification processing;
The generation module is also used for generating third abnormal transaction flow information of the first order;
the storage module is also used for storing the third abnormal transaction running water information into the abnormal transaction running water meter;
the updating module 320 is further configured to update, when the first order exists in the third transaction flow meter, a verification state of the first order according to a result of matching the local fifth payment amount of the first order with the sixth payment amount in the third transaction flow meter;
the generation module is further used for generating fourth abnormal transaction flow information of the first order under the condition that the fifth payment amount is not matched with the sixth payment amount;
the storage module is also used for storing fourth abnormal transaction flow information into the abnormal transaction flow meter.
In some embodiments, the data verification apparatus may further include:
the processing module is configured to process the abnormal transaction flow information by adopting a corresponding processing policy according to a processing mode and a processing state of the abnormal transaction flow information in the abnormal transaction flow water meter after the updating module 320 updates the flow data of the order in which payment is not completed in the first transaction flow water meter according to the payment result identifier and the first payment amount.
Each module in the apparatus shown in fig. 3 has a function of implementing each step in fig. 1-2 and can achieve a corresponding technical effect, and for brevity description, a detailed description is omitted herein.
Based on the same inventive concept, the embodiment of the application also provides an electronic device, which can be, for example, a mobile phone, a tablet computer, a notebook computer, a palm computer and the like. The electronic device provided in the embodiment of the present application is described in detail below with reference to fig. 4.
As shown in fig. 4, the electronic device may include a processor 410 and a memory 420 for storing computer program instructions.
The processor 410 may include a central processing unit (Central Processing Unit, CPU), or an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or may be configured to implement one or more integrated circuits of embodiments of the present application.
Memory 420 may include mass storage for data or instructions. By way of example, and not limitation, memory 420 may include a Hard Disk Drive (HDD), floppy Disk Drive, flash memory, optical Disk, magneto-optical Disk, magnetic tape, or universal serial bus (Universal Serial Bus, USB) Drive, or a combination of two or more of the foregoing. In one example, memory 420 may include removable or non-removable (or fixed) media, or memory 420 may be a non-volatile solid state memory. In one example, memory 420 may be Read Only Memory (ROM). In one example, the ROM may be mask-programmed ROM, programmable ROM (PROM), erasable PROM (EPROM), electrically Erasable PROM (EEPROM), electrically rewritable ROM (EAROM), or flash memory, or a combination of two or more of these.
The processor 410 reads and executes the computer program instructions stored in the memory 420 to implement the method in the embodiment shown in fig. 1-2, and achieves the corresponding technical effects achieved by executing the method in the embodiment shown in fig. 1-2, which are not described herein for brevity.
In one example, the electronic device may also include a communication interface 430 and a bus 440. As shown in fig. 4, the processor 410, the memory 420, and the communication interface 430 are connected and communicate with each other through a bus 440.
The communication interface 430 is mainly used for implementing communication between each module, device and/or apparatus in the embodiments of the present application.
Bus 440 includes hardware, software, or both that couples the various components of the electronic device to one another. By way of example, and not limitation, bus 440 may include an accelerated graphics port (Accelerated Graphics Port, AGP) or other graphics Bus, an enhanced industry standard architecture (Extended Industry Standard Architecture, EISA) Bus, a Front Side Bus (FSB), a HyperTransport (HT) interconnect, an industry standard architecture (Industry Standard Architecture, ISA) Bus, an infiniband interconnect, a Low Pin Count (LPC) Bus, a memory Bus, a micro channel architecture (MCa) Bus, a Peripheral Component Interconnect (PCI) Bus, a PCI-Express (PCI-X) Bus, a Serial Advanced Technology Attachment (SATA) Bus, a video electronics standards association local (VLB) Bus, or other suitable Bus, or a combination of two or more of the above. Bus 440 may include one or more buses, where appropriate. Although embodiments of the present application describe and illustrate a particular bus, the present application contemplates any suitable bus or interconnect.
The electronic device may execute the data verification method in the embodiment of the present application after acquiring the first transaction flow meter according to the preset time interval, so as to implement the data verification method described in connection with fig. 1-2 and the data verification device described in connection with fig. 3.
In addition, in combination with the data verification method in the above embodiment, the embodiment of the application may be implemented by providing a computer storage medium. The computer storage medium has stored thereon computer program instructions; the computer program instructions, when executed by a processor, implement any of the data verification methods of the above embodiments.
It should be clear that the present application is not limited to the particular arrangements and processes described above and illustrated in the drawings. For the sake of brevity, a detailed description of known methods is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present application are not limited to the specific steps described and illustrated, and those skilled in the art can make various changes, modifications, and additions, or change the order between steps, after appreciating the spirit of the present application.
The functional blocks shown in the above-described structural block diagrams may be implemented in hardware, software, firmware, or a combination thereof. When implemented in hardware, it may be, for example, an electronic circuit, an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), suitable firmware, a plug-in, a function card, or the like. When implemented in software, the elements of the present application are the programs or code segments used to perform the required tasks. The program or code segments may be stored in a machine readable medium or transmitted over transmission media or communication links by a data signal carried in a carrier wave. A "machine-readable medium" may include any medium that can store or transfer information. Examples of machine-readable media include electronic circuitry, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio Frequency (RF) links, and the like. The code segments may be downloaded via computer networks such as the internet, intranets, etc.
It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, the present application is not limited to the order of the above-described steps, that is, the steps may be performed in the order mentioned in the embodiments, may be different from the order in the embodiments, or several steps may be performed simultaneously.
Aspects of embodiments of the present application are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions/acts specified in the flowchart and/or block diagram block or blocks. Such a processor may be, but is not limited to being, a general purpose processor, a special purpose processor, an application specific processor, or a field programmable logic circuit. It will also be understood that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware which performs the specified functions or acts, or combinations of special purpose hardware and computer instructions.
In the foregoing, only the specific embodiments of the present application are described, and it will be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the systems, modules and units described above may refer to the corresponding processes in the foregoing method embodiments, which are not repeated herein. It should be understood that the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the present application, which are intended to be included in the scope of the present application.
Claims (10)
1. A method of data verification, comprising:
acquiring a first transaction flow water meter according to a preset time interval, wherein the preset time interval is smaller than or equal to a first threshold value, the first transaction flow water meter is used for storing first transaction flow data of at least one transaction locally, and the first transaction flow data comprises flow data of orders which are not paid;
for each transaction in the first transaction flow water meter, second transaction flow data corresponding to the transaction is obtained from a third party system, and the second transaction flow data comprises a payment result identifier of the order and a first payment amount;
And under the condition that at least one of the payment result identifier and the first payment amount does not meet a first condition, updating the flow data of the unfinished order in the first transaction flow water meter according to the payment result identifier and the first payment amount.
2. The method of claim 1, wherein updating the aggregate data of the outstanding payment orders in the first transaction flow meter based on the payment result identification and the first payment amount if at least one of the payment result identification and the first payment amount fails to satisfy a first condition, comprises:
updating the running water state of the unfinished order to be the end of inquiry and updating the payment state of the unfinished order to be the payment failure under the condition that the payment result identifier is a first identifier, wherein the first identifier is used for identifying that the payment result of the unfinished order is the payment failure;
updating the running state and the payment state of the unfinished order according to a first matching result of the first payment amount and the locally stored second payment amount under the condition that the payment result identifier is a second identifier, wherein the second identifier is used for identifying that the payment result of the unfinished order is successful in payment;
And recording that the verification state of the order which is not paid is verified by mistake under the condition that the first payment amount is not matched with the second payment amount stored locally according to the first matching result.
3. The method of claim 1, wherein after updating the running data of the outstanding payment order in the first transaction flow meter based on the payment result identification and the first payment amount, the method further comprises:
obtaining a verification file from the third party system, wherein the verification file comprises transaction data of at least one transaction;
inquiring the first transaction flow water meter and judging whether the first transaction exists in the first transaction flow water meter or not under the condition that the first transaction is payment transaction;
updating the payment state of the corresponding transaction in the first transaction flow water meter to be successful in payment and checking the payment state to be checked to be error under the condition that the first transaction exists in the first transaction flow water meter and the local payment state of the first transaction is unknown or the payment fails;
generating first abnormal transaction flow information of the first transaction, and storing the first abnormal transaction flow information into an abnormal transaction flow meter.
4. The method of claim 3, wherein said determining whether said first transaction is present after said first transaction flow meter further comprises:
updating the verification state of the first transaction according to a second matching result of the third payment amount of the first transaction and the fourth payment amount of the transaction stored locally when the first transaction exists in the first transaction flow water meter and the first transaction is successful in payment in the local payment state;
and under the condition that the second matching result is that the third payment amount is not matched with the fourth payment amount, generating second abnormal transaction running water information of the first transaction, and storing the second abnormal transaction running water information into the abnormal transaction running water meter.
5. The method of claim 3, wherein the first transaction pipeline data further comprises pipeline data of successfully paid and unverified orders; the method further comprises the steps of:
updating the verification state of the first order to be verified by mistake for each first order when the first order does not exist in a third transaction flow water meter, wherein the first order is any one of the orders which are successfully paid and not verified, and the third transaction flow water meter is used for storing flow data of each first transaction after verification processing;
Generating third abnormal transaction running water information of the first order, and storing the third abnormal transaction running water information into an abnormal transaction running water meter;
updating the verification state of the first order according to the matching result of the local fifth payment amount of the first order and the sixth payment amount in the third transaction flow water meter when the first order exists in the third transaction flow water meter;
and under the condition that the fifth payment amount is not matched with the sixth payment amount, generating fourth abnormal transaction running water information of the first order, and storing the fourth abnormal transaction running water information into an abnormal transaction running water meter.
6. The method of any of claims 1-5, wherein after updating the running water data of the outstanding payment order in the first transaction flow meter based on the payment result identification and the first payment amount, the method further comprises:
and processing the abnormal transaction running water information by adopting a corresponding processing strategy according to the processing mode and the processing state of the abnormal transaction running water information in the abnormal transaction running water meter.
7. A data verification apparatus, comprising: an acquisition module and an update module;
The acquisition module is used for acquiring a first transaction flow water meter according to a preset time interval, wherein the preset time interval is smaller than or equal to a first threshold value, the first transaction flow water meter is used for storing first transaction flow data of at least one transaction locally, and the first transaction flow data comprises flow data of orders which are not paid;
the acquisition module is further configured to acquire, for each transaction in the first transaction flow meter, second transaction flow data corresponding to the transaction from a third party system, where the second transaction flow data includes a payment result identifier of the order and a first payment amount;
and the updating module is used for updating the flow data of the unfinished order in the first transaction flow water meter according to the payment result identifier and the first payment amount under the condition that at least one of the payment result identifier and the first payment amount does not meet a first condition.
8. An electronic device, comprising:
a processor;
a memory for storing computer program instructions;
the computer program instructions, when executed by the processor, implement the method of any of claims 1-6.
9. A computer readable storage medium having stored thereon computer program instructions, which when executed by a processor, implement the method of any of claims 1-6.
10. A computer program product, characterized in that instructions in the computer program product, when executed by a processor of an electronic device, cause the electronic device to perform the method of any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311308356.7A CN117291612A (en) | 2023-10-10 | 2023-10-10 | Data verification method, device, equipment, medium and product |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311308356.7A CN117291612A (en) | 2023-10-10 | 2023-10-10 | Data verification method, device, equipment, medium and product |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117291612A true CN117291612A (en) | 2023-12-26 |
Family
ID=89258476
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311308356.7A Pending CN117291612A (en) | 2023-10-10 | 2023-10-10 | Data verification method, device, equipment, medium and product |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117291612A (en) |
-
2023
- 2023-10-10 CN CN202311308356.7A patent/CN117291612A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111510908B (en) | Card opening method, device, equipment and medium | |
| CN111105225A (en) | Transfer method, device, equipment and storage medium | |
| CN114064112A (en) | Business process configuration method, device, equipment and storage medium | |
| CN115269439A (en) | Method, device, equipment and readable storage medium for testing data processing system | |
| CN117291612A (en) | Data verification method, device, equipment, medium and product | |
| CN116069751A (en) | Information processing method, apparatus, device and computer readable storage medium | |
| CN115905145A (en) | File processing method, device, equipment and computer storage medium | |
| CN115330481A (en) | Second-hand commodity transaction order processing method, device, equipment and storage medium | |
| CN114691742A (en) | Information processing method, device, equipment and medium | |
| CN115393049A (en) | Repayment reminding method and device | |
| CN114661740A (en) | Data processing method, device, equipment, computer storage medium and program product | |
| CN117273642A (en) | User information management method, device, equipment, medium and product | |
| CN116245516A (en) | Processing method, device, equipment and storage medium for outbound transaction request | |
| CN116523514A (en) | Method, device, equipment, storage medium and product for processing static graphic code | |
| CN116095668A (en) | Reporting method, reporting device, reporting equipment, reporting medium and reporting product | |
| CN114997939A (en) | Information processing method, information processing apparatus, electronic device, information processing medium, and program product | |
| CN115576912A (en) | Method, device and equipment for determining business data model information and storage medium | |
| CN117575755A (en) | Information processing method, device, equipment, medium and product | |
| CN117172769A (en) | Resource transfer method, device, equipment and storage medium | |
| CN115984008A (en) | Early warning method and device for fund supervision, electronic equipment and storage medium | |
| CN115203207A (en) | Data acquisition method, device, equipment, medium and product | |
| CN116188130A (en) | Method, apparatus, device, storage medium and program product for resource clearing | |
| CN114638676A (en) | Financial information acquisition method, device, equipment, medium and product | |
| CN114255132A (en) | Account checking method, account checking device, account checking equipment, storage medium and computer program product | |
| CN114691332A (en) | Data processing method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |