Online fee processing method, device, equipment and storage medium

Abstract

The present application relates to the express field, disclose a kind of online expense processing method, device, equipment and storage medium, obtain the payment data generated by service end, obtain current payment data, the payment data at least includes order initiation time, order number and order information;All generated current payment data is stored in database, and history payment database is obtained;According to current payment data and history payment database, current payment data is checked and de-duplication processing is carried out, and checked and de-duplicated payment data is obtained;Third party system returns payment element according to checked and de-duplicated payment data, and transaction center arouses service end to complete payment this method has adopted first check factor and second check factor, and the payment data of same service end, different service end is respectively de-duplicated, greatly improve de-duplication efficiency, and combined with hash table to realize Bloom filter to reduce false positive error.

Description

Technical Field

[0001] This invention relates to the field of express delivery, and more particularly to an online payment processing method, apparatus, device, and storage medium. Background Technology

[0002] In recent years, the express delivery market has been in a phase of rapid growth, with domestic express delivery volume reaching hundreds of billions of yuan annually and growing at a rate of 20% per year. This has placed higher demands on the company's cost control and service. The company currently has multiple business channels, such as WeChat mini-program order processing, Alipay mini-program order processing, Baidu mini-program order processing, app order processing, and order placement on behalf of customers. These business channels may experience duplicate initiation of fees or duplicate order placements in the fee processing. Summary of the Invention

[0003] The main objective of this invention is to solve the problem that existing technologies cannot effectively remove duplicate payment data.

[0004] The first aspect of this invention provides an online fee processing method based on a transaction center, the online fee processing method comprising:

[0005] The system acquires payment data generated by the business side to obtain current payment data, which includes at least the order initiation time, order number, and order information. All generated current payment data is stored in the database to obtain a historical payment database. Based on the current payment data and the historical payment database, the current payment data is verified and deduplicated to obtain verified and deduplicated payment data. The third-party system returns payment elements based on the verified and deduplicated payment data, and the transaction center invokes the business side to complete the payment.

[0006] Optionally, in a second implementation of the first aspect of the present invention, all generated current payment data are stored in a database to obtain a historical payment database, including:

[0007] All current payment data generated by the business side is stored in the database; a preset time value is set for data to be removed; based on the preset time value, payment data that exceeds the preset time value in the historical payment database is removed to obtain the historical payment database.

[0008] Optionally, in a third implementation of the first aspect of the present invention, the step of performing verification and deduplication processing on the current payment data based on the current payment data and the historical payment database to obtain the verified and deduplicated payment data includes:

[0009] The system determines whether the current payment data is duplicated in the historical payment database based on the first verification factor. If yes, it sends a duplicate order information message to the business terminal. If no, it determines whether the current payment data is duplicated in the historical payment database based on the second verification factor. If yes, it sends a duplicate order information message to the business terminal. If no, it obtains the deduplicated payment data. The first verification factor includes at least the sender's contact number, recipient's address, recipient's contact number, business terminal type, sender's address, and payment amount. The second verification factor consists of the sender's region, sender's contact number, recipient's address, and recipient's contact number.

[0010] Optionally, in a fourth implementation of the first aspect of the present invention, the step of performing verification and deduplication processing on the current payment data based on the current payment data and the historical payment database to obtain the verified and deduplicated payment data includes:

[0011] The first verification factor of the current payment data is verified to obtain a first verification code; the first verification factor of the historical payment data in the historical payment database is verified to obtain a second verification code; the second verification factor of the current payment data is verified to obtain a third verification code; the second verification factor of the historical payment data in the historical payment database is verified to obtain a fourth verification code; the second verification code generated from the historical payment data is stored in the database to obtain a first historical verification code database; the fourth verification code generated from the historical payment data is stored in the database to obtain a second historical verification code database; it is determined whether the first verification code of the current payment data is in the first historical verification code database: if yes, order duplicate information is sent to the business end; if no, it is determined whether the third verification code of the current payment data is in the second historical verification code database; if yes, order duplicate information is sent to the business end; if no, the deduplicated payment data is obtained.

[0012] Optionally, in a fifth implementation of the first aspect of the present invention, determining whether the first verification code of the current payment data is in the first historical verification code database includes:

[0013] A Bloom filter is used. The Bloom filter is initialized by creating a bit array of a specific size and initializing all bits to 0. Multiple hash functions are used to calculate the hash value of the payment data in the first historical verification code database, and the corresponding bits in the Bloom filter are set to 1. The same hash function is used to calculate the hash value of the current payment data, and the corresponding counters in the bit array are checked to determine whether all counters are greater than 0.

[0014] Optionally, in a sixth implementation of the first aspect of the present invention, determining whether the third verification code of the current payment data is in the second historical verification code database includes:

[0015] A Bloom filter is used. The Bloom filter is initialized by creating a bit array of a specific size and initializing all bits to 0. Multiple hash functions are used to calculate the hash value of the payment data in the second historical verification code database, and the corresponding bits in the Bloom filter are set to 1. The same hash function is used to calculate the hash value of the current payment data, and the corresponding counters in the bit array are checked to determine if all counters are greater than 0. The selected hash function is used to calculate the hash value of the current payment data, and the current payment data is inserted into the hash table. The hash table is checked to determine if the current payment data is indeed a member.

[0016] Optionally, in the seventh implementation of the first aspect of the present invention, the step of completing the payment based on the deduplicated payment data includes:

[0017] Enter the current user's username and password;

[0018] Extract the account name information, perform online analysis, and obtain the first digit sequence of the account information, the length of the account information, and the number of account information types;

[0019] Based on the first digit sequence of the account information, the length of the account information, the number of account information types, the account name information, and the account password, determine whether the account information verification is successful, and issue a verification failure command or a verification success command.

[0020] Complete the payment based on the successful verification command and the deduplicated payment data.

[0021] A second aspect of the present invention provides an online payment processing device, comprising: an acquisition unit for acquiring payment data generated by a business terminal to obtain current payment data, wherein the payment data includes at least the order initiation time, order number, and order information; a storage unit for storing all generated current payment data in a database to obtain a historical payment database; a deduplication unit for performing verification and deduplication processing on the current payment data based on the current payment data and the historical payment database to obtain verified and deduplicated payment data; and a payment unit for a third-party system to return payment elements based on the verified and deduplicated payment data, and for a transaction center to invoke the business terminal to complete the payment.

[0022] A third aspect of the present invention provides an electronic device comprising: a memory and at least one processor, wherein the memory stores instructions, and the memory and the at least one processor are interconnected via a circuit; the at least one processor invokes the instructions in the memory to cause the electronic device to perform the online fee processing method described above.

[0023] A fourth aspect of the present invention provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the online fee processing method described above.

[0024] The technical solution of this invention provides an online fee processing method based on a transaction center. This method uses a first verification factor and a second verification factor to perform deduplication processing on payment data from the same business terminal and different business terminals, respectively, which greatly improves the deduplication efficiency. At the same time, it combines a hash table to implement a Bloom filter to reduce false positive errors. Attached Figure Description

[0025] Figure 1 This is a first flowchart of an online fee processing method provided in an embodiment of the present invention;

[0026] Figure 2 This is a second flowchart of the online fee processing method provided in an embodiment of the present invention;

[0027] Figure 3 A third flowchart of the online fee processing method provided in the embodiments of the present invention;

[0028] Figure 4 This is a schematic diagram of a first structure of the online fee processing device provided in an embodiment of the present invention;

[0029] Figure 5 This is a schematic diagram of a second structure of the online fee processing device provided in an embodiment of the present invention;

[0030] Figure 6 This is a schematic diagram of a third structure of the online fee processing device provided in an embodiment of the present invention;

[0031] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0032] This invention provides an online payment processing method, apparatus, device, and storage medium. The method involves acquiring payment data generated by the business terminal to obtain current payment data, which includes at least the order initiation time, order number, and order information. All generated current payment data is stored in a database to obtain a historical payment database. Based on the current payment data and the historical payment database, the current payment data is validated and deduplicated to obtain validated and deduplicated payment data. A third-party system returns payment elements based on the validated and deduplicated payment data, and the transaction center initiates the business terminal to complete the payment. This method employs a first validation factor and a second validation factor to deduplicatize payment data from the same business terminal and different business terminals, significantly improving deduplication efficiency. Simultaneously, a Bloom filter is implemented using a hash table to reduce false positive errors.

[0033] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” or “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0034] For ease of understanding, the specific process of the embodiments of the present invention is described below. Please refer to [link / reference]. Figure 1 The first embodiment of the online fee processing method in this invention includes:

[0035] 101. Obtain payment data generated by the business terminal to obtain current payment data, wherein the payment data includes at least the order initiation time, order number, and order information;

[0036] In a logistics order, payment data will include the following information:

[0037] Order number: A unique identifier for a logistics order.

[0038] Payment Amount: The total cost of the logistics service, including shipping, handling fees, and any other additional charges.

[0039] Payment methods: Payment methods such as credit card, debit card, bank transfer or cash on delivery.

[0040] Payment date and time: The date and time of payment.

[0041] Sender and recipient information: The name, address and other identifying information of the sender and recipient.

[0042] Payment Reference Number: A unique identifier assigned to a payment, such as a transaction ID or reference number.

[0043] Payment status: Information on whether the payment was successful, failed, or pending.

[0044] Delivery information: Information about the delivery address, estimated delivery time, and delivery status.

[0045] In this embodiment, payment data is collected as the data basis for data deduplication.

[0046] Payment data in logistics orders is typically verified through a combination of automated checks and manual reviews.

[0047] However, some common steps for verifying payment data in logistics orders include:

[0048] Format verification: Check payment data to ensure it is formatted correctly, such as the correct number of digits for a credit card or valid email address.

[0049] Authorization: Check the payment method to see if the funds are available and if the payment has been authorized. For example, you can verify credit card payments through the card issuer.

[0050] Fraud detection: Examining payment data against internal and external databases to detect potential fraud. This may include checking for duplicate payments, unusual payment patterns, or payments from known fraudsters.

[0051] Manual review: In some cases, payment data may be reviewed by human operators to ensure its legality and accuracy.

[0052] These steps are to ensure that payment data is valid, payments are authorized, and payments are not fraudulent.

[0053] This invention collects data from different business terminals in a unified manner, thereby making data deduplication judgment more accurate and comprehensive.

[0054] 102. Store all generated current payment data in the database to obtain the historical payment database;

[0055] Specifically, the present invention stores all current payment data generated by the business terminal in a database; sets a preset time value for removing data; and removes payment data in the historical payment database that exceeds the preset time value according to the preset time value, thereby obtaining the historical payment database.

[0056] In embodiments of the invention, data in the database can be cleared based on a time threshold using a process called data aging or data expiration. In embodiments of the invention, the database management system (DBMS) sets an expiration date or timestamp for each record in the database.

[0057] In an embodiment of the present invention, the following is an overview of the process:

[0058] Define a time threshold: Set a time threshold before any data is considered expired. This time threshold is typically specified in days, weeks, or months.

[0059] Update expiration timestamp: Each time a record is updated in the database, the expiration timestamp is also updated to reflect the current time.

[0060] Run a regular cleanup process.

[0061] Furthermore, in embodiments of the present invention, data can be deleted based on time thresholds in the database, using either a time-based expiration mechanism or a time-based deletion mechanism.

[0062] Time-based expiration: In this method, each record in the database is stamped with a timestamp or expiration date. Records that exceed the time limit are automatically deleted or marked for deletion.

[0063] Time-based deletion mechanism: In this method, a periodic task runs in the background to delete records older than a time threshold. This task may be daily, weekly, or in several other times.

[0064] This invention significantly reduces the amount of data and improves data processing efficiency by removing payment data from the historical payment database that exceeds a preset time value.

[0065] 103. Based on the current payment data and the historical payment database, perform verification and deduplication on the current payment data to obtain the verified and deduplicated payment data;

[0066] Specifically, the system determines whether the current payment data is duplicated in the historical payment database based on the first verification factor. If yes, it sends a duplicate order information message to the business terminal. If no, it determines whether the current payment data is duplicated in the historical payment database based on the second verification factor. If yes, it sends a duplicate order information message to the business terminal. If no, it obtains the deduplicated payment data. The first verification factor includes at least the sender's contact number, recipient's address, recipient's contact number, business terminal type, sender's address, and payment amount. The second verification factor consists of the sender's region, sender's contact number, recipient's address, and recipient's contact number.

[0067] In an embodiment of the present invention, a first verification factor and a second verification factor are set. The first verification factor includes the service terminal type. The first verification factor is first evaluated to determine whether duplicate data exists within the same service terminal. Then, the second verification factor is evaluated to determine whether duplicate data exists across different service terminals. This method significantly improves operational efficiency.

[0068] 104. Complete the payment based on the deduplicated payment data after verification.

[0069] Specifically, including:

[0070] Input the current user's account name and password; extract the account name information, perform online analysis to obtain the first digit sequence of the account information, the length of the account information, and the number of account information types; based on the first digit sequence of the account information, the length of the account information, the number of account information types, the account name information, and the account password, determine whether the account information verification is successful, and issue a verification failure command or a verification success command; based on the verification success command and the payment data after verification and deduplication, complete the payment.

[0071] This invention employs a two-factor authentication method, making account payments more secure.

[0072] In this embodiment, the payment elements for online payment include:

[0073] Payment method: The method of payment, such as credit card, debit card, online banking, or mobile wallet.

[0074] Payment details: Information about the payment, such as the amount, currency, and payment reference.

[0075] Payer Information: Information about the payer, such as their name, address, and email address.

[0076] Payee Information: Information about the payee, such as their name, address, and bank account details.

[0077] Payment security: Measures taken to ensure payment security, such as encryption, Secure Sockets Layer (SSL) certificates, and two-factor authentication.

[0078] Payment confirmation: A payment confirmation or receipt can be sent to the payer and the payee.

[0079] These elements are typically collected and processed by payment service providers or gateways, which are responsible for the secure transmission and processing of payment information.

[0080] In embodiments of the present invention, the detailed process of online payment typically involves the following steps:

[0081] Payment method selection: The payer selects the payment method they wish to use, such as credit card, debit card, or online banking.

[0082] Enter payment details: The payer enters payment details, such as amount, currency, and payment reference.

[0083] Enter payer information: Payers enter their personal information, such as their name, address, and email address.

[0084] Recipient Information Input: The payer enters the recipient's information, such as their name, address, and bank account details.

[0085] Payment security authentication: Payment service providers or gateways use encryption, SSL certificates, or two-factor authentication to check the security of payments.

[0086] Payment processing: Payment service providers or gateways process payments by securely transmitting payment information to relevant financial institutions (such as banks).

[0087] Payment confirmation: The payment service provider or gateway sends a payment confirmation or receipt to the payer and the payee.

[0088] Settlement: Payments are settled between the payer's and payee's financial institutions.

[0089] Please see Figure 2 The second embodiment of the online fee processing method in this invention includes:

[0090] 201. Obtain payment data generated by the business terminal to obtain current payment data, wherein the payment data includes at least the order initiation time, order number, and order information;

[0091] 202. Store all generated current payment data in the database to obtain the historical payment database;

[0092] 203. Based on the current payment data and the historical payment database, perform verification and deduplication on the current payment data to obtain the verified and deduplicated payment data;

[0093] Specifically, in this embodiment, the first verification factor of the current payment data is verified to obtain a first verification code; the first verification factor of the historical payment data in the historical payment database is verified to obtain a second verification code; the second verification factor of the current payment data is verified to obtain a third verification code; the second verification factor of the historical payment data in the historical payment database is verified to obtain a fourth verification code; the second verification code generated from the historical payment data is stored in a database to obtain a first historical verification code database; the fourth verification code generated from the historical payment data is stored in a database to obtain a second historical verification code database; it is determined whether the first verification code of the current payment data is in the first historical verification code database: if yes, order duplicate information is sent to the business terminal; if no, it is determined whether the third verification code of the current payment data is in the second historical verification code database; if yes, order duplicate information is sent to the business terminal; if no, the deduplicated payment data is obtained.

[0094] Regarding the identification of duplicate data, this embodiment adopts the following scheme:

[0095] 2031. Use a Bloom filter, initialize the Bloom filter, create a bit array of a specific size, and initialize all bits to 0;

[0096] 2032. Calculate the hash value of the payment data in the first historical verification code database using multiple hash functions, and set the corresponding bit in the Bloom filter to 1;

[0097] 2033. Calculate the hash value of the current payment data using the same hash function, check the corresponding counters in the bit array, and determine whether all counters are greater than 0.

[0098] In this embodiment of the invention, a Bloom filter is used for data deduplication. A Bloom filter is a probabilistic data structure used to test whether an element is a member of a set. It is used in computer systems to check whether an item has been processed. It is a space-saving and fast alternative to the traditional hash table data structure. A Bloom filter works by dividing a large bit array into smaller segments and using multiple hash functions to map elements to these segments. When an element is added to the Bloom filter, the hash function is used to set the corresponding bits in the bit array. To check if an element is in the set, the hash function checks the corresponding bits in the bit array. If all bits are set, the element is considered to be in the set. However, if one or more bits are not set, the element is not in the set, although the probability of a false positive is small. Bloom filters are widely used in various applications such as network routers, databases, and web browsers, where it is important to check whether an item has been processed without a full database query. Its efficiency and speed trade-off is that it can produce false positives but not false negatives.

[0099] A hash function is a mathematical function that takes an input (or "message") and returns a fixed-size string, typically a "digestor" unique to the input's unique value. Hash functions are used for many purposes, including verifying data integrity, indexing data in hash tables, and generating digital signatures. Widely used examples of hash functions include SHA-256, MD5, and SHA-1.

[0100] This invention employs two data deduplication checks, thereby effectively improving data deduplication efficiency.

[0101] 204. Complete the payment based on the deduplicated payment data after verification.

[0102] Please see Figure 3 The third embodiment of the online fee processing method in this invention includes:

[0103] 301. Obtain payment data generated by the business terminal to obtain current payment data, wherein the payment data includes at least the order initiation time, order number, and order information;

[0104] 302. Store all generated current payment data in the database to obtain the historical payment database;

[0105] 303. Based on the current payment data and the historical payment database, perform verification and deduplication on the current payment data to obtain the verified and deduplicated payment data;

[0106] Specifically, in this embodiment, the first verification factor of the current payment data is verified to obtain a first verification code; the first verification factor of the historical payment data in the historical payment database is verified to obtain a second verification code; the second verification factor of the current payment data is verified to obtain a third verification code; the second verification factor of the historical payment data in the historical payment database is verified to obtain a fourth verification code; the second verification code generated from the historical payment data is stored in a database to obtain a first historical verification code database; the fourth verification code generated from the historical payment data is stored in a database to obtain a second historical verification code database; it is determined whether the first verification code of the current payment data is in the first historical verification code database: if yes, order duplicate information is sent to the business terminal; if no, it is determined whether the third verification code of the current payment data is in the second historical verification code database; if yes, order duplicate information is sent to the business terminal; if no, the deduplicated payment data is obtained.

[0107] Regarding the identification of duplicate data, this embodiment adopts the following scheme:

[0108] 3031. Use a Bloom filter, initialize the Bloom filter by creating a bit array of a specific size and initializing all bits to 0;

[0109] 3032. Calculate the hash value of the payment data in the second historical verification code database using multiple hash functions, and set the corresponding bit in the Bloom filter to 1;

[0110] 3033. Calculate the hash value of the current payment data using the same hash function, check the corresponding counters in the bit array, and determine whether all counters are greater than 0;

[0111] 3034. Calculate the hash value of the current payment data using the selected hash function, and insert the current payment data into the hash table;

[0112] 3035. Check the hash table to determine if the current payment data is indeed from a member.

[0113] 304. Complete the payment based on the deduplicated payment data after verification.

[0114] A hash table is a data structure that allows efficient access to data based on a key. It works by taking a key, calculating a hash value for it, and then using that hash to index into an array of buckets or slots storing the actual data. To search for an element in a hash table, the key is hashed to find its index in the array, and then the corresponding bucket is searched to retrieve the data. The hash function must be designed to map the key to an index in the array in a uniformly distributed manner so that data is stored evenly and retrieved efficiently. Unlike Bloom filters, hash tables provide accurate results; they can definitively tell you whether an element is in the set.

[0115] In this embodiment of the invention, a Bloom filter and a hash table are used for deduplication. The Bloom filter is used for fast set membership testing with a very low probability of false positives, while the hash table is used for precise lookup of elements in the set. This reduces the problem of false positives in deduplication.

[0116] The above describes the method for modifying the delivery address of express packages in embodiments of the present invention. The following describes the online fee processing device in embodiments of the present invention. Please refer to [link / reference]. Figure 4 One embodiment of the online fee processing device in this invention includes:

[0117] 401. Acquisition unit, used to acquire payment data generated by the business terminal to obtain current payment data, wherein the payment data includes at least the order initiation time, order number, and order information;

[0118] 402. Storage unit, used to store all generated current payment data into the database to obtain the historical payment database;

[0119] 403. Deduplication unit: This unit verifies and deduplicates the current payment data based on the current payment data and the historical payment database, resulting in deduplicated payment data.

[0120] 404. Payment Unit, used to complete payment based on the payment data after verification and deduplication.

[0121] Please see Figure 5 A second embodiment of the online fee processing device in this invention includes:

[0122] 501. Acquisition unit, used to acquire payment data generated by the business terminal to obtain current payment data, wherein the payment data includes at least the order initiation time, order number, and order information;

[0123] 502. Storage unit, used to store all generated current payment data into the database to obtain the historical payment database;

[0124] 503. A deduplication unit, used to perform verification and deduplication processing on the current payment data based on the current payment data and the historical payment database, to obtain the verified and deduplicated payment data; the deduplication unit specifically includes:

[0125] 5031. A first verification processing unit is used to perform verification processing on the first verification factor of the current payment data to obtain a first verification code;

[0126] 5032. A second verification processing unit is used to verify the first verification factor of the historical payment data in the historical payment database to obtain a second verification code;

[0127] 5033. The third verification processing unit is used to verify the second verification factor in the current payment data to obtain the third verification code;

[0128] 5034. The fourth verification processing unit is used to verify the second verification factor of the historical payment data in the historical payment database to obtain the fourth verification code.

[0129] 5035. First historical verification code database, used to store the second verification code generated from historical payment data;

[0130] 5036. The second historical verification code database is used to store the fourth verification code generated from historical payment data;

[0131] 5037. Judgment unit: Determines whether the first verification code of the current payment data is in the first historical verification code database; if yes, sends order duplicate information to the business end; if no, determines whether the third verification code of the current payment data is in the second historical verification code database; if yes, sends order duplicate information to the business end; if no, obtains the payment data after verification and deduplication.

[0132] 504. Payment Unit: Used to complete payment based on the deduplicated payment data after verification.

[0133] Please see Figure 6 A third embodiment of the online fee processing device in this invention includes:

[0134] 601. Acquisition unit, used to acquire payment data generated by the business terminal to obtain current payment data, wherein the payment data includes at least the order initiation time, order number, and order information;

[0135] 602. Storage unit, used to store all generated current payment data into the database to obtain the historical payment database;

[0136] 603. A deduplication unit, used to perform verification and deduplication processing on the current payment data based on the current payment data and the historical payment database, to obtain the verified and deduplicated payment data; the deduplication unit specifically includes:

[0137] 6031. Verification factor judgment unit, used to determine whether the current payment data is duplicated in the historical payment database based on the first verification factor: if yes, then send order duplicate information to the business end; if no, then determine whether the current payment data is duplicated in the historical payment database based on the second verification factor: if yes, then send order duplicate information to the business end; if no, then obtain the payment data after verification and deduplication.

[0138] 604. Payment Unit, used to complete payment based on the payment data after verification and deduplication.

[0139] Figure 7 This is a schematic diagram of the structure of an electronic device 700 provided in an embodiment of the present invention. The electronic device 700 can vary significantly due to differences in configuration or performance. It may include one or more central processing units (CPUs) 710 (e.g., one or more processors) and a memory 720, and one or more storage media 730 (e.g., one or more mass storage devices) for storing application programs 733 or data 732. The memory 720 and storage media 730 can be temporary or persistent storage. The program stored in the storage media 730 may include one or more modules (not shown in the diagram), each module including a series of instruction operations on the electronic device 700. Furthermore, the processor 710 may be configured to communicate with the storage media 730 and execute the series of instruction operations in the storage media 730 on the electronic device 700.

[0140] Electronic device 700 may also include one or more power supplies 740, one or more wired or wireless network interfaces 750, one or more input / output interfaces 760, and / or one or more operating systems 731, such as Windows Server, MacOSX, Unix, Linux, FreeBSD, etc. Those skilled in the art will understand that... Figure 7 The illustrated electronic device structure does not constitute a limitation on electronic devices and may include more or fewer components than illustrated, or combine certain components, or have different component arrangements.

[0141] The present invention also provides a computer-readable storage medium, which can be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium, wherein the computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the steps of an online fee processing method.

[0142] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the system, device, or unit described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0143] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0144] The above-described embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. An online fee processing method, characterized by, The online fee processing method comprises: obtaining payment data generated by a service end to obtain current payment data, the payment data at least including order initiation time, order number and order information; storing all generated current payment data into a database to obtain a historical payment database; checking and de-duplicating the current payment data according to the current payment data and the historical payment database to obtain checked and de-duplicated payment data, including: checking a first check factor of the current payment data to obtain a first check code; checking a first check factor of historical payment data in the historical payment database to obtain a second check code; checking a second check factor of the current payment data to obtain a third check code; checking a second check factor of the historical payment data in the historical payment database to obtain a fourth check code; storing the second check code generated by the historical payment data into a database to obtain a first historical check code database; storing the fourth check code generated by the historical payment data into a database to obtain a second historical check code database; judging whether the first check code of the current payment data is in the first historical check code database: if yes, sending order duplication information to the service end; if no, judging whether the third check code of the current payment data is in the second historical check code database: if yes, sending order duplication information to the service end; if no, obtaining the checked and de-duplicated payment data; completing payment according to the checked and de-duplicated payment data; the first check factor at least including sender contact number, receiver address, receiver contact number, service end type, sender address and payment amount; the second check factor consisting of sender area, sender contact number, receiver address and receiver contact number; the judgment whether the first check code of the current payment data is in the first historical check code database comprises: using a Bloom filter, initializing the Bloom filter, creating a bit array of a specific size, and initializing all bits to 0; calculating the hash value of the payment data in the first historical check code database using multiple hash functions, and setting the corresponding bits in the Bloom filter to 1; calculating the hash value of the current payment data using the same hash function, checking the corresponding counters in the bit array, and judging whether all counters are greater than 0; the judgment whether the third check code of the current payment data is in the second historical check code database comprises: using a Bloom filter, initializing the Bloom filter, creating a bit array of a specific size, and initializing all bits to 0; calculating the hash value of the payment data in the second historical check code database using multiple hash functions, and setting the corresponding bits in the Bloom filter to 1; calculating the hash value of the current payment data using the same hash function, checking the corresponding counters in the bit array, and judging whether all counters are greater than 0; calculating the hash value of the current payment data using the selected hash function, and inserting the current payment data into the hash table; checking the hash table to judge whether the current payment data is indeed a member.

2. The online fee processing method of claim 1, wherein, The current payment data generated is stored into the database to obtain a historical payment database, including: Storing all generated current payment data of the business end into the database; Setting a preset time value for eliminating data; According to the preset time value, eliminating payment data exceeding the preset time value in the historical payment database to obtain the historical payment database.

3. The online fee processing method of claim 1, wherein, The payment is completed according to the payment data after the verification and deduplication, including: Inputting account name information and account password of the current user; Extracting the account name information, performing online analysis, and obtaining a first digit sequence of the account information, a length of the account information, and a type number of the account information; According to the first digit sequence of the account information, the length of the account information, the type number of the account information, the account name information, and the account password, judging whether the account information verification is successful, and issuing a verification failure command or a verification success command; According to the verification success command and the payment data after the verification and deduplication, completing the payment.

4. An online fee processing apparatus, characterized by comprising: Including: An acquisition unit is configured to acquire payment data generated by a business end to obtain current payment data, the payment data at least including order initiation time, order number, and order information; A storage unit is configured to store all generated current payment data into a database to obtain a historical payment database; A deduplication unit is configured to perform verification and deduplication processing on the current payment data according to the current payment data and the historical payment database to obtain payment data after verification and deduplication; including: performing verification processing on a first verification factor of the current payment data to obtain a first verification code; performing verification processing on a first verification factor of historical payment data in the historical payment database to obtain a second verification code; performing verification processing on a second verification factor in the current payment data to obtain a third verification code; performing verification processing on a second verification factor of historical payment data in the historical payment database to obtain a fourth verification code; storing the second verification code generated by the historical payment data into a database to obtain a first historical verification code database; storing the fourth verification code generated by the historical payment data into a database to obtain a second historical verification code database; judging whether the first verification code of the current payment data is in the first historical verification code database: if yes, sending order duplication information to the business end; if no, judging whether the third verification code of the current payment data is in the second historical verification code database: if yes, sending order duplication information to the business end; if no, obtaining the payment data after verification and deduplication; A payment unit is configured to return payment elements according to the payment data after verification and deduplication by a third-party system, and a transaction center arouses the business end to complete payment. The judgment whether the first verification code of the current payment data is in the first historical verification code database includes: Using a Bloom filter, initializing the Bloom filter, creating a bit array of a specific size, and initializing all bits to 0; Using multiple hash functions to calculate hash values of payment data in the first historical verification code database, and setting corresponding bits in the Bloom filter to 1; Using the same hash function to calculate hash values of the current payment data, checking corresponding counters in the bit array, and judging whether all counters are greater than 0; The judging whether the third check code of the current payment data is in the second historical check code database comprises: Using Bloom filter, initializing Bloom filter, creating a bit array of a specific size, and initializing all bits to 0; Using multiple hash functions to calculate the hash value of the payment data in the second historical check code database, and setting the corresponding bit in the Bloom filter to 1; Using the same hash function to calculate the hash value of the current payment data, checking the corresponding counter in the bit array, and judging whether all the counters are greater than 0; Using the selected hash function to calculate the hash value of the current payment data, and inserting the current payment data into the hash table; Checking the hash table to determine whether the current payment data is indeed a member. 5.An electronic device comprising a memory and at least one processor, the memory having instructions stored therein; The at least one processor invokes the instructions in the memory to enable the electronic device to perform the steps of the online fee processing method according to any one of claims 1-3.

6. A computer-readable storage medium having stored thereon instructions, the computer-readable storage medium comprising: The instructions are executed by the processor to implement the steps of the online fee processing method according to any one of claims 1-3.

Images