CN111415144A - Data verification method and device for withdrawal plan, computer equipment and storage medium - Google Patents
Data verification method and device for withdrawal plan, computer equipment and storage medium Download PDFInfo
- Publication number
- CN111415144A CN111415144A CN202010186917.0A CN202010186917A CN111415144A CN 111415144 A CN111415144 A CN 111415144A CN 202010186917 A CN202010186917 A CN 202010186917A CN 111415144 A CN111415144 A CN 111415144A
- Authority
- CN
- China
- Prior art keywords
- plan
- verification
- withdrawal
- service system
- 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
- 238000013524 data verification Methods 0.000 title claims abstract description 60
- 238000000034 method Methods 0.000 title claims abstract description 54
- 238000012795 verification Methods 0.000 claims abstract description 112
- 238000004422 calculation algorithm Methods 0.000 claims description 26
- 238000012550 audit Methods 0.000 claims description 18
- 238000004590 computer program Methods 0.000 claims description 5
- 238000010200 validation analysis Methods 0.000 claims 5
- 238000013502 data validation Methods 0.000 claims 2
- 230000000694 effects Effects 0.000 abstract description 3
- 230000003287 optical effect Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 238000004364 calculation method Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 239000013307 optical fiber Substances 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000012546 transfer Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
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/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/102—Bill distribution or payments
-
- 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/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/108—Remote banking, e.g. home banking
-
- 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- Economics (AREA)
- Strategic Management (AREA)
- Development Economics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Marketing (AREA)
- Technology Law (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The embodiment of the invention provides a data verification method and device for a payment plan, computer equipment and a storage medium. The data verification method of the withdrawal plan comprises the following steps: receiving a first payment plan sent by a service system, wherein the first payment plan is generated according to transaction data through the service system; performing data verification on the first withdrawal plan according to a preset verification strategy; and when the first withdrawal plan is verified successfully, sending a verification success message to the service system so that the service system can put money according to the verification success message. The first payment plan of the business system is verified through the auditing system, and the effect of improving the accuracy of data verification of the payment plan is achieved.
Description
Technical Field
The embodiment of the invention relates to the technical field of internet finance, in particular to a data verification method and device of a withdrawal plan, computer equipment and a storage medium.
Background
With the rapid development of internet finance, online payment or online transfer scenes are more and more performed through the internet.
At present, a common scheme is that a service system generates a payment plan according to a service rule of the service system, data of the payment plan is verified, and online payment or online transfer is performed for payment after the verification is successful.
However, the business system affects the data generation logic during the business requirement iteration process, resulting in inaccurate data verification of the withdrawal plan.
Disclosure of Invention
The embodiment of the invention provides a data verification method and device of a withdrawal plan, computer equipment and a storage medium, so as to achieve the effect of improving the accuracy of data verification of the withdrawal plan.
In a first aspect, an embodiment of the present invention provides a data verification method for a withdrawal plan, including:
receiving a first payment plan sent by a service system, wherein the first payment plan is generated according to transaction data through the service system;
performing data verification on the first withdrawal plan according to a preset verification strategy;
and when the first withdrawal plan is verified successfully, sending a verification success message to the service system so that the service system can put money according to the verification success message.
Optionally, the first database corresponding to the auditing system and the second database corresponding to the business system are isolated from each other; and/or
And the first access operation authority of the auditing system and the second access operation authority of the business system are independent.
Optionally, the first withdrawal plan corresponds to a unique contract number, the auditing system includes a verification record, and the data verification of the first withdrawal plan according to a preset verification strategy includes:
judging whether the check record comprises an audit success result corresponding to the contract number;
when the verification record comprises an audit success result corresponding to the contract number, the first payment plan is failed to verify;
when the verification record does not comprise an audit success result corresponding to the contract number, generating a second withdrawal plan according to transaction data sent by the service system;
and verifying the first withdrawal plan according to the second withdrawal plan.
Optionally, the first dispensing plan includes one or more first check messages, the second dispensing plan includes one or more corresponding second check messages, and checking the first dispensing plan according to the second dispensing plan includes:
judging whether the one or more first check messages and the one or more second check messages are completely the same;
when the one or more first check-up information and the one or more second check-up information are completely the same, the first withdrawal plan is checked successfully;
and marking the contract number corresponding to the first withdrawal plan and storing the contract number in the verification record.
Optionally, before the determining whether the one or more first check messages and the one or more second check messages are completely the same, the method includes:
decrypting sensitive information in the one or more first verification information by a first decryption algorithm;
decrypting sensitive information in the one or more second check-up information by a second decryption algorithm, the first decryption algorithm and the second decryption algorithm being different.
Optionally, the first payment plan is multiple, and the receiving the first payment plan sent by the service system includes:
and sequentially receiving first withdrawal plans sent by the service system according to a preset batch sequence, wherein the preset batch corresponds to at least two first withdrawal plans, and the number of the preset batch is determined according to the plurality of first withdrawal plans and the number of the first withdrawal plans corresponding to each preset batch.
Optionally, the preset batches are multiple, and the data verification of the first withdrawal plan according to a preset verification policy includes:
and simultaneously verifying at least two first withdrawal plans of each preset batch until the verification of the preset batches is completed.
In a second aspect, an embodiment of the present invention provides a data verification apparatus for a withdrawal plan, including:
the receiving module is used for receiving a first payment plan sent by a service system, and the first payment plan is generated according to transaction data through the service system;
the verification module is used for performing data verification on the first withdrawal plan according to a preset verification strategy;
and the notification module is used for sending a verification success message to the service system when the first withdrawal plan is verified successfully, so that the service system can put money according to the verification success message.
In a third aspect, an embodiment of the present invention provides a computer device, including:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement a method of data verification of a dispensing plan as in any embodiment of the invention.
In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, on which a computer program is stored, which when executed by a processor, implements a data verification method for a withdrawal plan according to any embodiment of the present invention.
According to the embodiment of the invention, a first payment plan sent by a service system is received, and the first payment plan is generated according to transaction data through the service system; performing data verification on the first withdrawal plan according to a preset verification strategy; and when the first withdrawal plan is verified successfully, sending a verification success message to the service system so that the service system can put money according to the verification success message. The problem that the data verification of the withdrawal plan is inaccurate due to the fact that the data generation logic is influenced in the business requirement iteration process of the business system is solved, and the effect of improving the data verification accuracy of the withdrawal plan is achieved.
Drawings
FIG. 1 is a flowchart illustrating a data verification method for a payment plan according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a data verification method for a payment plan according to a second embodiment of the present invention;
fig. 3 is a schematic structural diagram of a data verification device for a payment plan according to a third embodiment of the present invention;
fig. 4 is a schematic structural diagram of a computer device according to a fourth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Before discussing exemplary embodiments in more detail, it should be noted that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart may describe the steps as a sequential process, many of the steps can be performed in parallel, concurrently or simultaneously. In addition, the order of the steps may be rearranged. A process may be terminated when its operations are completed, but may have additional steps not included in the figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc.
Furthermore, the terms "first," "second," and the like may be used herein to describe various orientations, actions, steps, elements, or the like, but the orientations, actions, steps, or elements are not limited by these terms. These terms are only used to distinguish one direction, action, step or element from another direction, action, step or element. For example, a first withdrawal plan may be planned as a second withdrawal plan, and similarly, the second withdrawal plan may be referred to as a first withdrawal plan, without departing from the scope of the present application. Both the first and second dispensing plans are dispensing plans, but they are not the same dispensing plan. The terms "first", "second", etc. are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of the present invention, "a plurality" means at least two, e.g., two, three, etc., unless specifically limited otherwise.
Example one
Fig. 1 is a schematic flowchart of a data verification method for a withdrawal plan according to an embodiment of the present invention, which is applicable to a scenario in which data of the withdrawal plan is verified by an auditing system, where the method may be executed by a data verification apparatus for the withdrawal plan, and the apparatus may be implemented in a software and/or hardware manner and may be integrated on a computer device.
As shown in fig. 1, a data verification method for a withdrawal plan provided in an embodiment of the present invention is applied to an auditing system, and the method includes:
s110, receiving a first payment plan sent by a service system, wherein the first payment plan is generated according to transaction data through the service system.
Wherein the first withdrawal plan is generated by the business system from the transaction data. Specifically, the first withdrawal plan is generated by the business system according to the business process and the first rule. Transaction data refers to data generated by a user at the time of consumption. Optionally, the transaction data includes, but is not limited to, name of the consumer, amount of consumption, content of consumption, time of consumption, identification card information of the consumer, and the like, and is not limited herein. Specifically, the transaction data corresponding to different consumption scenarios are different. Taking the case that the borrower performs network consumption borrowing as an example, the transaction data is borrowing application data submitted based on fund demand when the user consumes on line (for example, an application program). Specifically, the business system and the auditing system are decoupled from each other. Decoupling is to separate a service system from an auditing system to process problems, and can be understood that the service system and the auditing system do not interfere with each other in hardware and software.
And S120, performing data verification on the first withdrawal plan according to a preset verification strategy.
The preset verification strategy refers to a mode of performing data verification on the first payment plan. In the present embodiment, the specific verification policy is not limited.
In an optional embodiment, the first withdrawal plan corresponds to a unique contract number, the auditing system includes a verification record, and the data verification of the first withdrawal plan according to a preset verification policy includes:
judging whether the check record comprises an audit success result corresponding to the contract number; when the verification record comprises an audit success result corresponding to the contract number, the first payment plan is failed to verify; when the verification record does not comprise an audit success result corresponding to the contract number, generating a second withdrawal plan according to transaction data sent by the service system; and verifying the first withdrawal plan according to the second withdrawal plan.
In the present embodiment, the contract number is a label corresponding to the first dispensing plan. Specifically, when a user consumes on a platform of a service system, a unique contract number is generated. The verification record refers to a record of the past verification before the current verification is performed. Specifically, each time the check is performed, when the check is successful, the contract number is marked, and it is determined that the audit of the contract number is successful. In the embodiment, whether the check record comprises the audit success result corresponding to the contract number is judged, and when the check record comprises the audit success result corresponding to the contract number, the contract number is verified to pass and the money is released before the check, and at this time, the first money withdrawal plan fails to be checked; and when the verification record does not comprise an audit success result, indicating that the contract number is not verified successfully and the money is not put before the verification, and generating a second payment plan according to transaction data sent by the service system. Specifically, the second withdrawal plan is generated by the auditing system according to the transaction data through a second rule of the auditing system. Specifically, the first payment plan is generated in the business system according to the transaction data through the business process and the first rule, and the second payment plan is generated in the auditing system according to the transaction data through the second rule.
Illustratively, taking the network consumption loan of a borrower as an example, after generating transaction data, the business system respectively calculates a commission fee, an exchange rate and the like for the transaction data according to a business process and a first rule, and finally determines a first withdrawal plan; and the auditing system calculates the transaction data through a second rule, such as a preset formula, to obtain a second payment plan. Since the business system needs to perform calculation according to the business processes, calculation of a certain business process may be skipped, for example, without calculating a commission fee, data of the first withdrawal plan may be in error. The auditing system can obtain a second payment plan through the calculation of the second rule without being influenced by the business process, so that the second payment plan is accurate, and the first payment plan can be verified according to the second payment plan.
In an optional embodiment, the first dispensing plan includes one or more first check messages, the second dispensing plan includes one or more corresponding second check messages, and checking the first dispensing plan according to the second dispensing plan includes:
judging whether the one or more first check messages and the one or more second check messages are completely the same; when the one or more first check-up information and the one or more second check-up information are completely the same, the first withdrawal plan is checked successfully; and marking the contract number corresponding to the first withdrawal plan and storing the contract number in the verification record.
In this embodiment, optionally, the one or more first check information items include one or more of a first loan amount, a first borrower name, a first identification card, a first bank card number, and a first mobile phone number, and the one or more second check information items include one or more of a second loan amount, a second borrower name, a second identification card, a second bank card number, and a second mobile phone number. Illustratively, when the first verification information includes the first loan amount and the first borrower name, the second verification information includes the second loan amount and the second borrower. Specifically, when the one or more first check information and the one or more second check information are completely the same, the first withdrawal plan is verified successfully, and the contract number corresponding to the first withdrawal plan is marked and then stored in the verification record. And after the contract number is marked and stored in the verification record, the verification record comprises an audit success result of the contract number.
In an optional embodiment, before determining whether the one or more first check-up information and the one or more second check-up information are identical, the method includes:
decrypting sensitive information in the one or more first verification information by a first decryption algorithm; decrypting sensitive information in the one or more second check-up information by a second decryption algorithm, the first decryption algorithm and the second decryption algorithm being different.
In this embodiment, the sensitive information in the first check information and the second check information is encrypted by using different encryption algorithms, and is decrypted by using a corresponding decryption algorithm when the check is required. Alternatively, the sensitive information may be the loan amount, the borrower information, and the like, which is not limited herein. Optionally, the first decryption algorithm and the second decryption algorithm are DES symmetric decryption algorithm, MD5 encryption algorithm, or RSA asymmetric encryption algorithm, which is not limited herein, and the first decryption algorithm and the second decryption algorithm are different. Sensitive information is encrypted before verification, and different encryption algorithms are adopted, so that the verification safety is higher
S130, when the first payment plan is verified successfully, a verification success message is sent to the service system, so that the service system can put money according to the verification success message.
In this step, when the first withdrawal plan is successfully verified, a verification success message is sent to the service system, and the service system can deposit money according to the verification success message. Optionally, the payment put by the service system may be made by calling a third party payment interface, and the specific manner of payment put is not limited here.
Illustratively, when the user a needs to perform network loan, the user a submits loan application data on a platform of the business system, and transaction data is obtained according to the loan application data submitted by the user. The service platform generates a first payment plan according to the transaction data and sends the first payment plan to the auditing system. And after receiving the first withdrawal plan, the auditing system verifies the first withdrawal plan according to a preset verification strategy, and sends a verification success message to the service system when the verification is successful. The service system can put money according to the verification success message.
In this embodiment, the first withdrawal plan is sent to the auditing system for verification, and since the auditing system and the service system are decoupled from each other, the auditing system is not affected by service iteration, so that the accuracy of data verification performed by the auditing system is higher. In addition, when the auditing system sends a verification success message to the service system, the service system can deposit money, so that economic loss caused by repeated money deposit or wrong money deposit amount of the service system is avoided.
In an optional embodiment, a first database corresponding to the auditing system and a second database corresponding to the business system are isolated from each other; and/or the first access operation authority of the auditing system and the second access operation authority of the business system are independent.
Specifically, the embodiment includes that a first database corresponding to the auditing system and a second database corresponding to the business system are isolated from each other; or the first access operation authority of the auditing system and the second access operation authority of the business system are independent; or the first database corresponding to the auditing system and the second database corresponding to the service system are mutually isolated, and the first access operation authority of the auditing system and the second access operation authority of the service system are mutually independent.
In the embodiment, the first database corresponding to the auditing system and the second database corresponding to the business system are isolated from each other, and even if the data of one database is stolen, the data of the other database cannot be influenced, so that the data security is improved. In addition, the first access operation authority of the auditing system and the second access operation authority of the service system are independent, so that the possibility of manual tampering of data is greatly reduced, and the safety of the data is further improved.
According to the technical scheme of the embodiment of the invention, a first payment plan sent by a service system is received, and the first payment plan is generated according to transaction data through the service system; performing data verification on the first withdrawal plan according to a preset verification strategy; when the first withdrawal plan is successfully verified, a verification success message is sent to the service system so that the service system can deposit money according to the verification success message, and the first withdrawal plan is sent to the auditing system for verification.
Example two
Fig. 2 is a flowchart illustrating a data verification method for a payment plan according to a second embodiment of the present invention. The embodiment is further detailed in the technical scheme, and is suitable for a scene of verifying data of a plurality of payment plans through an auditing system. The method may be performed by a data verification device of the withdrawal plan, which may be implemented in software and/or hardware, and may be integrated on a computer device.
As shown in fig. 2, a data verification method for a payment plan according to a second embodiment of the present invention includes:
s210, first withdrawal plans sent by the service system according to a preset batch sequence are sequentially received, the preset batch corresponds to at least two first withdrawal plans, the number of the preset batch is determined according to the first withdrawal plans and the number of the first withdrawal plans corresponding to each preset batch, and the first withdrawal plans are generated through the service system according to transaction data.
Wherein the first withdrawal plan is generated by the business system from the transaction data. Specifically, the first withdrawal plan is generated by the business system according to the business process and the first rule. Transaction data refers to data generated by a user at the time of consumption. Specifically, the business system and the auditing system are decoupled from each other. Decoupling is to separate a service system from an auditing system to process problems, and can be understood that the service system and the auditing system do not interfere with each other in hardware and software.
In this embodiment, the first payment plan generated by the business system is multiple, each payment plan corresponds to one transaction data, and each transaction data corresponds to one consumption order. The auditing system sequentially receives first withdrawal plans sent by the business system according to a preset batch sequence, and each preset batch corresponds to two or more than two first withdrawal plans. Illustratively, the number of the first withdrawal plans is 10, and when each preset batch corresponds to 2 first withdrawal plans, the first withdrawal plans are divided into 5 batches to be received in sequence; when each preset batch corresponds to 10 first payment plans, the payment plans are divided into 1 batch to be received in sequence.
S220, performing data verification on the first withdrawal plan according to a preset verification strategy.
The preset verification strategy refers to a mode of performing data verification on the first payment plan. In the present embodiment, the specific verification policy is not limited.
In an optional embodiment, the predetermined lot is multiple, and the data verification of the first withdrawal plan according to the predetermined verification policy includes:
and simultaneously verifying at least two first withdrawal plans of each preset batch until the verification of the preset batches is completed.
In the embodiment, all the first withdrawal plans of the same batch are verified simultaneously until the verification of a plurality of preset batches is completed, so that the verification time is shortened, and the verification efficiency is improved.
And S230, when the first payment plan is verified successfully, sending a verification success message to the service system so that the service system can put money according to the verification success message.
In this step, when the first withdrawal plan is successfully verified, a verification success message is sent to the service system, and the service system can deposit money according to the verification success message. Optionally, the payment put by the service system may be made by calling a third party payment interface, and the specific manner of payment put is not limited here.
According to the technical scheme of the embodiment of the invention, a first payment plan sent by a service system is received, and the first payment plan is generated according to transaction data through the service system; performing data verification on the first withdrawal plan according to a preset verification strategy; when the first withdrawal plan is successfully verified, a verification success message is sent to the service system so that the service system can deposit money according to the verification success message, and the first withdrawal plan is sent to the auditing system for verification.
EXAMPLE III
Fig. 3 is a schematic structural diagram of a data verification apparatus for a payment plan according to a third embodiment of the present invention, where this embodiment is applicable to a scenario in which an auditing system verifies data of the payment plan, and the apparatus may be implemented in a software and/or hardware manner and may be integrated on a computer device.
As shown in fig. 3, the data verification apparatus for a withdrawal plan provided in this embodiment may include a receiving module 310, a verifying module 320, and a notifying module 330, where:
the receiving module 310 is configured to receive a first payment plan sent by a service system, where the first payment plan is generated according to transaction data through the service system; the verification module 320 is configured to perform data verification on the first withdrawal plan according to a preset verification strategy; the notification module 330 is configured to send a verification success message to the service system when the first withdrawal plan is verified successfully, so that the service system deposits money according to the verification success message.
Optionally, the first database corresponding to the auditing system and the second database corresponding to the business system are isolated from each other; and/or the first access operation authority of the auditing system and the second access operation authority of the business system are independent.
Optionally, the first withdrawal plan corresponds to a unique contract number, the auditing system includes a verification record, and the verification module 320 includes: an audit success result judging unit, configured to judge whether the check record includes an audit success result corresponding to the contract number; when the verification record comprises an audit success result corresponding to the contract number, the first payment plan is failed to verify; the second payment plan generating unit is used for generating a second payment plan according to the transaction data sent by the service system when the verification record does not include an audit success result corresponding to the contract number; and the verification unit is used for verifying the first payment plan according to the second payment plan.
Optionally, the first withdrawal plan includes one or more first check messages, the second withdrawal plan includes one or more corresponding second check messages, and the checking unit is specifically configured to determine whether the one or more first check messages and the one or more second check messages are completely the same; when the one or more first check-up information and the one or more second check-up information are completely the same, the first withdrawal plan is checked successfully; and marking the contract number corresponding to the first withdrawal plan and storing the contract number in the verification record.
Optionally, the apparatus further comprises: the decryption module is used for decrypting the sensitive information in the one or more first check information through a first decryption algorithm; decrypting sensitive information in the one or more second check-up information by a second decryption algorithm, the first decryption algorithm and the second decryption algorithm being different.
Optionally, the first withdrawal plans are multiple, the receiving module 310 is specifically configured to sequentially receive the first withdrawal plans sent by the service system according to a sequence of preset batches, where the preset batches correspond to at least two first withdrawal plans, and the number of the preset batches is determined according to the multiple first withdrawal plans and the number of the first withdrawal plans corresponding to each preset batch.
Optionally, the preset batches are multiple, and the checking module 320 is specifically configured to check at least two first dispensing plans of each preset batch at the same time until the plurality of preset batches are checked.
The data verification device for the withdrawal plan provided by the embodiment of the invention can execute the data verification method for the withdrawal plan provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method. Reference may be made to the description of any method embodiment of the invention not specifically described in this embodiment.
Example four
Fig. 4 is a schematic structural diagram of a computer device according to a fourth embodiment of the present invention. FIG. 4 illustrates a block diagram of an exemplary computer device 612 suitable for use in implementing embodiments of the present invention. The computer device 612 shown in fig. 4 is only an example and should not bring any limitations to the functionality or scope of use of embodiments of the present invention.
As shown in fig. 4, the computer device 612 is in the form of a general purpose computer device. Components of computer device 612 may include, but are not limited to: one or more processors 616, a memory device 628, and a bus 618 that couples the various system components including the memory device 628 and the processors 616.
A program/utility 640 having a set (at least one) of program modules 642 may be stored, for example, in storage 628, such program modules 642 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. The program modules 642 generally perform the functions and/or methods of the described embodiments of the present invention.
The processor 616 executes various functional applications and data processing by running programs stored in the storage device 628, for example, implementing a data verification method for a withdrawal plan provided by any embodiment of the present invention, which may include:
receiving a first payment plan sent by a service system, wherein the first payment plan is generated according to transaction data through the service system;
performing data verification on the first withdrawal plan according to a preset verification strategy;
and when the first withdrawal plan is verified successfully, sending a verification success message to the service system so that the service system can put money according to the verification success message.
According to the technical scheme of the embodiment of the invention, a first payment plan sent by a service system is received, and the first payment plan is generated according to transaction data through the service system; performing data verification on the first withdrawal plan according to a preset verification strategy; when the first withdrawal plan is successfully verified, a verification success message is sent to the service system so that the service system can deposit money according to the verification success message, and the first withdrawal plan is sent to the auditing system for verification.
EXAMPLE five
An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements a data verification method for a withdrawal plan according to any embodiment of the present invention, where the method may include:
receiving a first payment plan sent by a service system, wherein the first payment plan is generated according to transaction data through the service system;
performing data verification on the first withdrawal plan according to a preset verification strategy;
and when the first withdrawal plan is verified successfully, sending a verification success message to the service system so that the service system can put money according to the verification success message.
The computer-readable storage media of embodiments of the invention may take any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including AN object oriented programming language such as Java, Smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages.
According to the technical scheme of the embodiment of the invention, a first payment plan sent by a service system is received, and the first payment plan is generated according to transaction data through the service system; performing data verification on the first withdrawal plan according to a preset verification strategy; when the first withdrawal plan is successfully verified, a verification success message is sent to the service system so that the service system can deposit money according to the verification success message, and the first withdrawal plan is sent to the auditing system for verification.
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (10)
1. A data verification method of a withdrawal plan is applied to an auditing system, and comprises the following steps:
receiving a first payment plan sent by a service system, wherein the first payment plan is generated according to transaction data through the service system;
performing data verification on the first withdrawal plan according to a preset verification strategy;
and when the first withdrawal plan is verified successfully, sending a verification success message to the service system so that the service system can put money according to the verification success message.
2. The data verification method of a withdrawal plan according to claim 1, wherein a first database corresponding to the auditing system and a second database corresponding to the business system are isolated from each other; and/or
And the first access operation authority of the auditing system and the second access operation authority of the business system are independent.
3. The data verification method of a withdrawal plan as claimed in claim 1, wherein the first withdrawal plan corresponds to a unique contract number, the auditing system includes a verification record, and the data verification of the first withdrawal plan according to a preset verification policy includes:
judging whether the check record comprises an audit success result corresponding to the contract number;
when the verification record comprises an audit success result corresponding to the contract number, the first payment plan is failed to verify;
when the verification record does not comprise an audit success result corresponding to the contract number, generating a second withdrawal plan according to transaction data sent by the service system;
and verifying the first withdrawal plan according to the second withdrawal plan.
4. The method for data validation of a dispense plan according to claim 3, wherein the first dispense plan includes one or more first validation messages, the second dispense plan includes a corresponding one or more second validation messages, and the validation of the first dispense plan according to the second dispense plan includes:
judging whether the one or more first check messages and the one or more second check messages are completely the same;
when the one or more first check-up information and the one or more second check-up information are completely the same, the first withdrawal plan is checked successfully;
and marking the contract number corresponding to the first withdrawal plan and storing the contract number in the verification record.
5. The method of data validation of a withdrawal plan according to claim 4, comprising, prior to said determining whether said one or more first validation information and said one or more second validation information are identical:
decrypting sensitive information in the one or more first verification information by a first decryption algorithm;
decrypting sensitive information in the one or more second check-up information by a second decryption algorithm, the first decryption algorithm and the second decryption algorithm being different.
6. The data verification method for a dispensing plan according to claim 1, wherein the first dispensing plan is plural, and the receiving of the first dispensing plan transmitted from the business system includes:
and sequentially receiving first withdrawal plans sent by the service system according to a preset batch sequence, wherein the preset batch corresponds to at least two first withdrawal plans, and the number of the preset batch is determined according to the plurality of first withdrawal plans and the number of the first withdrawal plans corresponding to each preset batch.
7. The method for verifying data of a dispensing plan according to claim 6, wherein the predetermined lot is plural, and the verifying data of the first dispensing plan according to the predetermined verification policy includes:
and simultaneously verifying at least two first withdrawal plans of each preset batch until the verification of the preset batches is completed.
8. A data verification device for a dispensing plan, comprising:
the receiving module is used for receiving a first payment plan sent by a service system, and the first payment plan is generated according to transaction data through the service system;
the verification module is used for performing data verification on the first withdrawal plan according to a preset verification strategy;
and the notification module is used for sending a verification success message to the service system when the first withdrawal plan is verified successfully, so that the service system can put money according to the verification success message.
9. A computer device, comprising:
one or more processors;
storage means for storing one or more programs;
when executed by the one or more processors, cause the one or more processors to implement a data verification method for a withdrawal plan as claimed in any of claims 1 to 7.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out a method of data verification of a dispensing plan according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010186917.0A CN111415144A (en) | 2020-03-17 | 2020-03-17 | Data verification method and device for withdrawal plan, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010186917.0A CN111415144A (en) | 2020-03-17 | 2020-03-17 | Data verification method and device for withdrawal plan, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111415144A true CN111415144A (en) | 2020-07-14 |
Family
ID=71491139
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010186917.0A Pending CN111415144A (en) | 2020-03-17 | 2020-03-17 | Data verification method and device for withdrawal plan, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111415144A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108492105A (en) * | 2018-03-07 | 2018-09-04 | 物数（上海）信息科技有限公司 | Transaction in assets monitoring and managing method, system, equipment and storage medium based on block chain |
| CN108765145A (en) * | 2018-04-18 | 2018-11-06 | 链家网（北京）科技有限公司 | A kind of contract and transaction data consistency desired result method and device |
| CN108990424A (en) * | 2017-03-30 | 2018-12-11 | 株式会社三井住友银行 | Banking system and the method executed by banking system |
| CN109214823A (en) * | 2018-08-27 | 2019-01-15 | 北京京东金融科技控股有限公司 | Transaction verification method, device, storage medium and electronic equipment based on block chain |
| CN110751485A (en) * | 2019-10-28 | 2020-02-04 | 腾讯科技（深圳）有限公司 | Data processing method and equipment |
-
2020
- 2020-03-17 CN CN202010186917.0A patent/CN111415144A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108990424A (en) * | 2017-03-30 | 2018-12-11 | 株式会社三井住友银行 | Banking system and the method executed by banking system |
| CN108492105A (en) * | 2018-03-07 | 2018-09-04 | 物数（上海）信息科技有限公司 | Transaction in assets monitoring and managing method, system, equipment and storage medium based on block chain |
| CN108765145A (en) * | 2018-04-18 | 2018-11-06 | 链家网（北京）科技有限公司 | A kind of contract and transaction data consistency desired result method and device |
| CN109214823A (en) * | 2018-08-27 | 2019-01-15 | 北京京东金融科技控股有限公司 | Transaction verification method, device, storage medium and electronic equipment based on block chain |
| CN110751485A (en) * | 2019-10-28 | 2020-02-04 | 腾讯科技（深圳）有限公司 | Data processing method and equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109872149B (en) | Method and system for using trustworthiness of digital certificates | |
| US11321783B2 (en) | Method and device for data processing based on blockchain | |
| US20190188657A1 (en) | Method and system for outside guarantees for a blockchain transaction | |
| CN108352019B (en) | Method and system for fraud detection using mobile communication devices | |
| CN114788222A (en) | Method and system for secure and verifiable offline blockchain transactions | |
| CN108874654B (en) | Idempotent validity test method, device and equipment and readable medium | |
| CN112581253A (en) | Method for determining credit limit and secure multiparty computing system | |
| EP4358000A1 (en) | Digital currency-based payment method, platform, terminal, and payment system | |
| CN111899111A (en) | Capital matching method, device, server and storage medium | |
| CN111784347A (en) | Resource transfer method and device | |
| CN110781134A (en) | Data processing method and device, computer storage medium and electronic equipment | |
| CN110599140A (en) | Digital currency verification method and system | |
| CN111367776A (en) | Recording method, device, equipment and storage medium of resource transfer service | |
| CN111865726B (en) | Service message testing method, device, computer system and storage medium | |
| WO2021121030A1 (en) | Resource transfer method, settlement terminal, and server node | |
| CN111415144A (en) | Data verification method and device for withdrawal plan, computer equipment and storage medium | |
| CN112037056B (en) | Transaction processing method, device, equipment and storage medium | |
| CN111932255B (en) | Method and device for realizing transaction reconciliation based on encrypted currency | |
| CN112085469B (en) | Data approval method, device, equipment and storage medium based on vector machine model | |
| CN113034285A (en) | Request processing method and device, computer equipment and storage medium | |
| CN111949337A (en) | Accounting processing method, device, terminal and storage medium | |
| CN106533685A (en) | Identity authentication method, identity authentication device, and identity authentication system | |
| CN110942313A (en) | Gas card interaction method, gas card payment method and gas card reader | |
| CN116703395B (en) | Digital RMB payment method, device, equipment, system and medium | |
| CN117217921B (en) | Transaction 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 |