Financial service processing method and device, storage medium and electronic equipment

Abstract

The invention discloses a financial service processing method and device, a storage medium and electronic equipment. The method comprises the following steps: receiving a target transaction request of a target financial service; a transaction event number corresponding to the target transaction request is obtained, and the transaction event number is determined based on the triggering time of the target transaction request; according to the transaction event number, judging whether a transaction corresponding to the target transaction request is a repeated transaction; and when it is determined that the transaction corresponding to the target transaction request is not the repeated transaction, handling the target financial service according to the target transaction request. Through the method and the device, the problem that repeated transactions are easy to occur in financial transaction business in a distributed scene in related technologies is solved.

Description

Technical Field

[0001] The present application relates to the field of fintech, and in particular, to a method and apparatus for processing financial services, a storage medium, and an electronic device. Background Art

[0002] With the development of the Internet, customers can conveniently use the core business services of financial institutions through the Internet to complete various non-cash transactions. In order to improve the processing efficiency of customer services, a distributed architecture is often adopted to process various financial services. For example, when a customer initiates a transfer transaction through a mobile phone channel, in a distributed scenario, the transaction randomly enters each server in the background. After the server receives the transfer request, it processes the transfer request. However, due to network jitter, the mobile phone channel may repeatedly initiate the same transfer transaction, affecting the security of the customer's funds.

[0003] In view of the problem that duplicate transactions are likely to occur in financial transaction services in a distributed scenario in the related art, no effective solution has been proposed yet. Summary of the Invention

[0004] The main objective of the present application is to provide a method and apparatus for processing financial services, a storage medium, and an electronic device, so as to solve the problem that duplicate transactions are likely to occur in financial transaction services in a distributed scenario in the related art.

[0005] To achieve the above objective, according to one aspect of the present application, a method for processing financial services is provided. The method includes: receiving a target transaction request for a target financial service; obtaining a transaction event number corresponding to the target transaction request, where the transaction event number is determined based on the trigger time of the target transaction request; determining, based on the transaction event number, whether the transaction corresponding to the target transaction request is a duplicate transaction; and in the case where it is determined that the transaction corresponding to the target transaction request is not a duplicate transaction, handling the target financial service according to the target transaction request.

[0006] Further, obtaining the transaction event number corresponding to the target transaction request includes: obtaining region number information and channel category information corresponding to the target transaction request; obtaining trigger time information corresponding to the target transaction request; and obtaining the transaction event number based on the region number information, the channel category information, and the trigger time information.

[0007] Furthermore, based on the area code information, the channel category information and the trigger time information, obtaining the transaction event number includes: splitting the area code information to obtain a first character string; splitting the channel category information to obtain a second character string; determining a timestamp corresponding to the trigger time information; and concatenating the first character string, the second character string and the timestamp to obtain the transaction event number.

[0008] Furthermore, based on the transaction event number, determining whether the transaction corresponding to the target transaction request is a duplicate transaction includes: obtaining historical transaction event numbers corresponding to multiple historical transaction requests; determining whether there is a target historical transaction event number that is the same as the transaction event number among the multiple historical transaction event numbers; if the target historical transaction event number does not exist, determining that the transaction corresponding to the target transaction request is not a duplicate transaction.

[0009] Furthermore, after determining whether there is a target historical transaction event number identical to the transaction event number among multiple historical transaction event numbers, the method further includes: if the target historical transaction event number exists, obtaining historical transaction information corresponding to the target historical transaction event number, wherein the historical transaction information at least includes transaction amount information and transaction object information; obtaining target transaction information corresponding to the target transaction request; determining whether the target transaction information is identical to the historical transaction information; if the target transaction information is identical to the historical transaction information, determining that the transaction corresponding to the target transaction request is a duplicate transaction.

[0010] Furthermore, when it is determined that the transaction corresponding to the target transaction request is a repeated transaction, the method further includes: obtaining a historical transaction result corresponding to the target historical transaction event number; and feeding back the historical transaction result to the target object corresponding to the target transaction request.

[0011] Furthermore, after determining whether the target transaction information is the same as the historical transaction information, the method also includes: if the target transaction information is not the same as the historical transaction information, determining that there is an abnormality in the target transaction request; when it is determined that there is an abnormality in the target transaction request, triggering a target signal to the target object corresponding to the target transaction request, wherein the target signal is used to instruct the target object to initiate a transaction request for the target financial service again.

[0012] To achieve the above object, according to another aspect of the present application, there is provided a processing device for financial services. The device includes: a receiving unit for receiving a target transaction request for a target financial service; a first obtaining unit for obtaining a transaction event number corresponding to the target transaction request, wherein the transaction event number is determined based on the triggering time of the target transaction request; a first judging unit for judging whether the transaction corresponding to the target transaction request is a duplicate transaction according to the transaction event number; and a handling unit for handling the target financial service according to the target transaction request when it is determined that the transaction corresponding to the target transaction request is not a duplicate transaction.

[0013] Further, the first obtaining unit includes: a first obtaining module for obtaining region number information and channel category information corresponding to the target transaction request; a second obtaining module for obtaining triggering time information corresponding to the target transaction request; and a first determining module for obtaining the transaction event number according to the region number information, the channel category information, and the triggering time information.

[0014] Further, the first determining module includes: a first splitting sub-module for splitting the region number information to obtain a first string; a second splitting sub-module for splitting the channel category information to obtain a second string; a determining sub-module for determining a time stamp corresponding to the triggering time information; and a splicing sub-module for splicing the first string, the second string, and the time stamp to obtain the transaction event number.

[0015] Further, the first judging unit includes: a third obtaining module for obtaining historical transaction event numbers corresponding to a plurality of historical transaction requests; a judging module for judging whether there is a target historical transaction event number identical to the transaction event number among the plurality of historical transaction event numbers; and a second determining module for determining that the transaction corresponding to the target transaction request is not a duplicate transaction if there is no such target historical transaction event number.

[0016] Further, the device further includes: a second obtaining unit for obtaining historical transaction information corresponding to the target historical transaction event number if there is the target historical transaction event number after judging whether there is a target historical transaction event number identical to the transaction event number among the plurality of historical transaction event numbers, wherein the historical transaction information at least includes transaction amount information and transaction object information; a third obtaining unit for obtaining target transaction information corresponding to the target transaction request; a second judging unit for judging whether the target transaction information is identical to the historical transaction information; and a first determining unit for determining that the transaction corresponding to the target transaction request is a duplicate transaction if the target transaction information is identical to the historical transaction information.

[0017] Further, the apparatus further includes: a fourth obtaining unit, configured to obtain a historical transaction result corresponding to the target historical transaction event number when it is determined that the transaction corresponding to the target transaction request is a duplicate transaction; and a feedback unit, configured to feedback the historical transaction result to a target object corresponding to the target transaction request.

[0018] Further, the apparatus further includes: a second determining unit, configured to determine that there is an abnormality in the target transaction request if the target transaction information is different from the historical transaction information after determining whether the target transaction information is the same as the historical transaction information; and a triggering unit, configured to trigger a target signal to a target object corresponding to the target transaction request when it is determined that there is an abnormality in the target transaction request, where the target signal is used to instruct the target object to initiate a transaction request for the target financial service again.

[0019] To achieve the above object, according to another aspect of the present application, there is also provided a computer-readable storage medium, where the computer-readable storage medium includes an executable program stored therein, and when the executable program runs, it controls a device where the computer-readable storage medium is located to execute the steps in any one of the above method embodiments.

[0020] To achieve the above object, according to another aspect of the present application, there is also provided an electronic device, including a memory and a processor, where a computer program is stored in the memory, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0021] In the embodiments of the present application, the following steps are adopted: receiving a target transaction request for a target financial service; obtaining a transaction event number corresponding to the target transaction request, where the transaction event number is determined based on the triggering time of the target transaction request; determining whether the transaction corresponding to the target transaction request is a duplicate transaction according to the transaction event number; and when it is determined that the transaction corresponding to the target transaction request is not a duplicate transaction, handling the target financial service, which solves the technical problem that duplicate transactions are likely to occur in financial transaction services in a distributed scenario in the related art. In this solution, after receiving the target transaction request of the user, it is determined whether the transaction corresponding to the target transaction request is a duplicate transaction according to the transaction event number corresponding to the target transaction request. When it is determined that it is not a duplicate transaction, the target financial service is handled. The problem of accurately identifying and determining whether a transaction is duplicate through the transaction event number is solved, and duplicate transactions of customers are avoided, thereby achieving the effect of improving the security of funds. Description of the Drawings

[0022] The accompanying drawings, which form a part of this application, are used to provide a further understanding of this application. The schematic embodiments and descriptions thereof of this application are used to explain this application and do not constitute an improper limitation to this application. In the drawings:

[0023] Figure 1 A hardware structure block diagram of a computer terminal for implementing a processing method of financial services is shown;

[0024] Figure 2 is a flow of a processing method of financial services provided according to an embodiment of this application Figure 1 ;

[0025] Figure 3 is a schematic diagram of a processing method of financial services provided according to an embodiment of this application;

[0026] Figure 4 is a flow of a processing method of financial services provided according to an embodiment of this application Figure 2 ;

[0027] Figure 5 is a schematic diagram of a processing device of financial services provided according to an embodiment of this application;

[0028] Figure 6 is a structure block diagram of an electronic device according to an embodiment of this application. Detailed Embodiments

[0029] In order to enable those skilled in the art to better understand the solution of this application, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of this application. Obviously, the described embodiments are only a part of the embodiments of this application, rather than all the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the scope of protection of this application.

[0030] It should be noted that the terms "first", "second", etc. in the specification and claims of this application and the above accompanying drawings are used to distinguish similar objects and do not necessarily need to describe a specific order or sequence. It should be understood that such data can be interchanged under appropriate circumstances so that the embodiments of this application described here can be implemented in an order different from those illustrated or described here. In addition, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or units not clearly listed or inherent to these processes, methods, products or devices.

[0031] It should be noted that the information collected in this application (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for display, data for analysis, etc.) are information and data authorized by the user or fully authorized by all parties. Moreover, the processing of relevant data, such as collection, storage, use, processing, transmission, provision, disclosure, and application, complies with relevant laws, regulations, and standards, takes necessary confidentiality measures, does not violate public order and good customs, and provides corresponding operation entrances for users to choose to authorize or refuse. For example, an interface is set between this system and relevant users or institutions to provide corresponding operation entrances for users to choose to agree or refuse the results of automated decision-making; if the user chooses to refuse, the expert decision-making process will be entered.

[0032] Embodiment 1

[0033] According to an embodiment of the present application, there is also provided an embodiment of a method for processing financial services. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. And although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than here.

[0034] The method embodiment provided by the first embodiment of the present application can be executed on a mobile terminal, a computer terminal, or a similar computing device. Figure 1 The hardware structure block diagram of a computer terminal (or mobile device) for implementing the method for processing financial services is shown. As Figure 1 shown, the computer terminal 10 (or mobile device) may include one or more processors 102 (shown as 102a, 102b,..., 102n in the figure) (the processor 102 may include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may further include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which can be included as one of the ports of the BUS bus), a network interface, a power supply, and / or a camera. Those of ordinary skill in the art can understand that Figure 1 the structure shown is only schematic and does not limit the structure of the above-mentioned electronic device. For example, the computer terminal 10 may further include more or fewer components than Figure 1 shown, or have a different configuration from Figure 1 shown.

[0035] It should be noted that the above-mentioned one or more processors 102 and / or other data processing circuits can generally be referred to as "data processing circuits" herein. The data processing circuit can be embodied in software, hardware, firmware or any combination thereof, in whole or in part. In addition, the data processing circuit can be a single independent processing module, or be incorporated in whole or in part into any one of other elements in the computer terminal 10 (or mobile device). As involved in the embodiments of the present application, the data processing circuit is a kind of processor control (such as the selection of a variable resistance terminal path connected to an interface).

[0036] The memory 104 can be used to store software programs and modules of application software, such as the program instructions / data storage devices corresponding to the processing method of financial services in the embodiments of the present application. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, that is, realizes the above-mentioned processing method of financial services. The memory 104 can include high-speed random access memory, and can also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memories. In some instances, the memory 104 can further include a memory remotely set relative to the processor 102, and these remote memories can be connected to the computer terminal 10 through a network. Examples of the above-mentioned network include but are not limited to the Internet, enterprise intranet, local area network, mobile communication network and their combinations.

[0037] The transmission device 106 is used to receive or send data via a network. Specific examples of the above-mentioned network can include the wireless network provided by the communication provider of the computer terminal 10. In one instance, the transmission device 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station and thus can communicate with the Internet. In one instance, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0038] The display can be a touch-screen liquid crystal display (LCD), which enables the user to interact with the user interface of the computer terminal 10 (or mobile device).

[0039] Under the above operating environment, the present application provides a processing method of financial services as follows Figure 2 shown. Figure 2 is the flowchart of the processing method of financial services according to Embodiment 1 of the present application Figure 1 . The processing method includes:

[0040] Step S201, receiving a target transaction request for a target financial service.

[0041] Optionally, the user can initiate a target transaction request for a target financial service through an application on the mobile phone. For example, the target financial service is a remittance service. The target transaction request is received by the backend server.

[0042] Step S202: Obtain a transaction event number corresponding to the target transaction request, where the transaction event number is determined based on the trigger time of the target transaction request.

[0043] Optionally, the backend server obtains the transaction event number corresponding to the target transaction request. It should be noted that the above transaction event number can be generated when the user initiates a target transaction request for a target financial service through an application on the mobile phone. For example, a unified rule can be used to generate the transaction event number corresponding to the target transaction request.

[0044] In an alternative embodiment, the transaction event number corresponding to the target transaction request can be generated according to the trigger time of the target transaction request. For example, if the trigger time is xx / xx / 20xx, the corresponding transaction event number is 20xxxxxx12. It should be noted that 12 can be a random number randomly generated when generating the transaction event number.

[0045] Step S203: Determine whether the transaction corresponding to the target transaction request is a duplicate transaction based on the transaction event number.

[0046] Optionally, after the backend server obtains the transaction event number corresponding to the target transaction request, it can determine whether the transaction corresponding to the target transaction request is a duplicate transaction according to the transaction event number and the historical transaction event numbers that have been processed. For example, it is determined whether there is a historical transaction event number that is the same as the transaction event number corresponding to the target transaction request. If there is no historical transaction event number that is the same as the transaction event number corresponding to the target transaction request, the transaction corresponding to the target transaction request is not a duplicate transaction.

[0047] Step S204: When it is determined that the transaction corresponding to the target transaction request is not a duplicate transaction, handle the target financial service according to the target transaction request.

[0048] Optionally, when it is determined that the transaction corresponding to the target transaction request is not a duplicate transaction, obtain the information related to the transaction corresponding to the target transaction request, and handle the target financial service for the user according to the information related to the transaction corresponding to the target transaction request. For example, if the target financial service is a remittance service, the information related to the transaction corresponding to the target transaction request can be information such as the transaction card number and the transaction amount.

[0049] In summary, after receiving the target transaction request from the user, determine whether the transaction corresponding to the target transaction request is a duplicate transaction based on the transaction event order number corresponding to the target transaction request. When it is determined that it is not a duplicate transaction, handle the target financial service. Through the transaction event order number, the problem of whether the transaction is repeated can be accurately identified and judged, avoiding duplicate transactions by the customer, and thus achieving the effect of improving the security of funds.

[0050] Optionally, in the method for processing financial services provided in the embodiments of the present application, obtaining the transaction event order number corresponding to the target transaction request includes: obtaining the region number information and channel category information corresponding to the target transaction request; obtaining the trigger time information corresponding to the target transaction request; and obtaining the transaction event order number based on the region number information, channel category information, and trigger time information.

[0051] In an optional embodiment, the following steps can be used to obtain the transaction event order number corresponding to the target transaction request: obtain the region number information and channel category information corresponding to the target transaction request. For example, the region number is 000001, and the channel category information is the mobile phone channel. Then obtain the trigger time information corresponding to the target transaction request. Finally, obtain the transaction event order number based on the region number information, channel category information, and trigger time information. For example, quantify the channel category information. For example, the mobile phone channel corresponds to 0004, and then assemble the region number information, the quantified channel category information, and the trigger time information into the transaction event order number.

[0052] Assembling the region number information, the quantified channel category information, and the trigger time information into the transaction event order number ensures the uniqueness and accuracy of the transaction event order number, and improves the accuracy of subsequent judgment of whether the transaction is repeated.

[0053] Optionally, in the method for processing financial services provided in the embodiments of the present application, obtaining the transaction event order number based on the region number information, channel category information, and trigger time information includes: splitting the region number information to obtain a first string; splitting the channel category information to obtain a second string; determining the time stamp corresponding to the trigger time information; and performing a splicing process on the first string, the second string, and the time stamp to obtain the transaction event order number.

[0054] In an optional embodiment, the following steps can be used to obtain the transaction event order number: the region number information can be a 6-digit postal code. For example, the region number is 000001. To improve the complexity and security of the transaction event order number, the region number information can be split. For example, split the region number information into two parts and use the first four digits and the last four digits as the above-mentioned first string. For example, the first string is 0100.

[0055] For the channel category information, the channel category information can be first quantified into a preset four - digit string, and then the string is split into pairs and summed to obtain a second string. For the trigger time information, determine the time stamp corresponding to the trigger time information. For example, the UTC time stamp corresponding to 15:00:00 on January 3, 2025 is 17362788800. Finally, by concatenating the first string, the second string, and the time stamp, a transaction event order number is obtained.

[0056] In an optional embodiment, the concatenation order between the first string, the second string, and the time stamp can be set according to actual requirements.

[0057] The complexity and accuracy of the transaction event order number are improved through the splitting and combination of the string.

[0058] Optionally, in the method for processing financial services provided in the embodiments of the present application, determining whether the transaction corresponding to the target transaction request is a duplicate transaction based on the transaction event order number includes: obtaining the historical transaction event order numbers corresponding to multiple historical transaction requests; determining whether there is a target historical transaction event order number identical to the transaction event order number among the multiple historical transaction event order numbers; if there is no target historical transaction event order number, it is determined that the transaction corresponding to the target transaction request is not a duplicate transaction.

[0059] In an optional embodiment, determining whether the transaction corresponding to the target transaction request is a duplicate transaction based on the transaction event order number includes the following steps: obtaining the historical transaction event order numbers corresponding to multiple historical transaction requests. It should be noted that a public module can be set to store the historical transaction event order numbers corresponding to the historical transaction requests. After receiving the transaction event order number, the backend server can obtain multiple historical transaction event order numbers by accessing the public module.

[0060] By comparing multiple historical transaction event order numbers with the transaction event order number to determine whether the transaction corresponding to the target transaction request is a duplicate transaction. For example, determining whether there is a target historical transaction event order number identical to the transaction event order number among the multiple historical transaction event order numbers. If there is no target historical transaction event order number identical to the transaction event order number, it is determined that the transaction corresponding to the target transaction request is not a duplicate transaction.

[0061] Through the transaction event order number, it is possible to identify and determine whether a transaction is repeated, avoiding customers from remitting money repeatedly and also avoiding financial losses of financial institutions.

[0062] Optionally, in the method for processing financial services provided in the embodiments of the present application, after determining whether there is a target historical transaction event number identical to the transaction event number among multiple historical transaction event numbers, the method further includes: if there is a target historical transaction event number, obtaining the historical transaction information corresponding to the target historical transaction event number, where the historical transaction information at least includes transaction amount information and transaction object information; obtaining the target transaction information corresponding to the target transaction request; determining whether the target transaction information is the same as the historical transaction information; if the target transaction information is the same as the historical transaction information, determining that the transaction corresponding to the target transaction request is a duplicate transaction.

[0063] In an optional embodiment, after determining whether there is a target historical transaction event number identical to the transaction event number among multiple historical transaction event numbers, if there is a target historical transaction event number identical to the transaction event number, it is necessary to further obtain the historical transaction information corresponding to the target historical transaction event number. For example, information such as the remittance account number and remittance amount, and further determine whether the transaction corresponding to the target transaction request is a duplicate transaction based on the historical transaction information, improving the accuracy of the determination.

[0064] After obtaining the transaction amount information and transaction object information, determine whether the target transaction information is the same as the historical transaction information. If the target transaction information is the same as the historical transaction information, it can be determined that the transaction corresponding to the target transaction request is a duplicate transaction.

[0065] By further determining whether the transaction corresponding to the target transaction request is a duplicate transaction through the transaction information, the accuracy of the determination can be effectively improved.

[0066] Optionally, in the method for processing financial services provided in the embodiments of the present application, in the case where it is determined that the transaction corresponding to the target transaction request is a duplicate transaction, the method further includes: obtaining the historical transaction result corresponding to the target historical transaction event number; feeding back the historical transaction result to the target object corresponding to the target transaction request.

[0067] In an optional embodiment, if the transaction corresponding to the target transaction request is a duplicate transaction, idempotent processing is performed, that is, obtaining the historical transaction result corresponding to the target historical transaction event number, and then feeding back the historical transaction result to the target object corresponding to the target transaction request. Through the above steps, when the repeatedly initiated message is exactly the same, it can be ensured that actually only one transaction occurs and there will be no multiple deductions, improving the security of funds.

[0068] Optionally, in the method for processing financial services provided in the embodiments of the present application, after determining whether the target transaction information is the same as the historical transaction information, the method further includes: if the target transaction information is different from the historical transaction information, it is determined that the target transaction request is abnormal; in the case where it is determined that the target transaction request is abnormal, a target signal is triggered to the target object corresponding to the target transaction request, where the target signal is used to instruct the target object to initiate a transaction request for the target financial service again.

[0069] In an alternative embodiment, after determining whether the target transaction information is the same as the historical transaction information, if the target transaction information is different from the historical transaction information, that is, there is a difference between the target transaction information and the historical transaction information, it is determined that the target transaction request is abnormal, that is, for some reasons, such as machine failure or algorithm problems, the generated transaction event number is abnormal, and a target signal is triggered to the target object corresponding to the target transaction request, so that the target object can initiate a transaction request for the target financial service again.

[0070] Through the transaction event number, when the repeatedly initiated message is exactly the same, it can ensure that only one actual transaction occurs and the customer will not be deducted multiple times. At the same time, after the customer normally submits a service request, the event number is used as the only identifier to locate a transaction, and it is necessary to ensure that it will not be produced repeatedly. However, due to some reasons, such as machine failure or algorithm problems, when the generated event number is abnormal and the event numbers generated by different customers' transactions are the same, this abnormal phenomenon can be accurately identified, avoiding the transaction being idempotent due to the repeated event number (that is, the subsequent transactions are based on the result of the first transaction), resulting in false success or false failure of the transaction and avoiding financial losses.

[0071] In a further embodiment, such as Figure 3Schematic diagram of the processing method of the financial service shown. A customer initiates a transfer transaction through the mobile phone channel. In a distributed scenario, the transaction randomly enters each of the backend servers in the background. After the backend server receives the message input from the mobile phone, it uses the transaction event order number as the unique index to query the database record in the common module through the remote service call method. The common module will return the information on whether there is such an event order number. If no record is returned, it means that this event order number has never entered the background system, and it can be considered a normal transaction to be processed. After the transaction ends, the processing result of this transaction is synchronously registered in the common module. If the common module returns a record, then further judge the newly incoming transaction information, such as whether the card number and amount are equal to the card number and amount returned by the common module. If all are equal, it is considered that this transaction is exactly the same and is treated as an idempotent operation, and the existing processing result in the common module is returned. If the card number and amount are not completely equal, an error is reported to notify the channel that an exception has occurred in this transaction and the event order number has appeared repeatedly, and this transaction is not allowed.

[0072] In an optional embodiment, it can be implemented through the Figure 4 flowchart shown to process the financial service. Judge whether the event order numbers are the same. If they are not the same, it is determined that the transaction is normal. If the event order numbers are the same, then further judge the newly incoming transaction information, such as whether the card number and amount are equal to the card number and amount of the historical transaction. If all are equal, it is considered that this transaction is exactly the same and is treated as an idempotent operation, and the existing processing result is returned. If the card number and amount are not completely equal, an error is reported to notify the channel that an exception has occurred in this transaction and the event order number has appeared repeatedly, and the transaction error is processed.

[0073] The processing method of the financial service provided by the embodiment of the present application, by receiving the target transaction request of the target financial service; obtaining the transaction event order number corresponding to the target transaction request, where the transaction event order number is determined based on the trigger time of the target transaction request; judging whether the transaction corresponding to the target transaction request is a duplicate transaction according to the transaction event order number; in the case of determining that the transaction corresponding to the target transaction request is not a duplicate transaction, handling the target financial service according to the target transaction request, solves the technical problem that duplicate transactions are likely to occur in the financial transaction service in the distributed scenario. In this solution, after receiving the target transaction request of the user, it is determined whether the transaction corresponding to the target transaction request is a duplicate transaction according to the transaction event order number corresponding to the target transaction request. In the case of determining that it is not a duplicate transaction, the target financial service is handled. The problem of accurately identifying and judging whether a transaction is repeated through the transaction event order number can be avoided for customers to conduct duplicate transactions, and thus the effect of improving the security of funds is achieved.

[0074] It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. And although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than here.

[0075] Embodiment 2

[0076] The embodiment of the present application also provides a processing device for financial services. It should be noted that the processing device for financial services in the embodiment of the present application can be used to execute the processing method for financial services provided by the embodiment of the present application. The following introduces the processing device for financial services provided by the embodiment of the present application.

[0077] According to the embodiment of the present application, there is also provided a device for implementing the above-mentioned processing method for financial services, as Figure 5 shown, the device includes: a receiving unit 501, a first obtaining unit 502, a first judging unit 503, and a handling unit 504.

[0078] The receiving unit 501 is configured to receive a target transaction request for a target financial service;

[0079] The first obtaining unit 502 is configured to obtain a transaction event number corresponding to the target transaction request, where the transaction event number is determined based on the triggering time of the target transaction request;

[0080] The first judging unit 503 is configured to judge whether the transaction corresponding to the target transaction request is a repeated transaction according to the transaction event number;

[0081] The handling unit 504 is configured to handle the target financial service according to the target transaction request when it is determined that the transaction corresponding to the target transaction request is not a repeated transaction.

[0082] The processing device for financial services provided by the embodiments of the present application receives a target transaction request for a target financial service through a receiving unit 501; a first obtaining unit 502 obtains a transaction event serial number corresponding to the target transaction request, where the transaction event serial number is determined based on the triggering time of the target transaction request; a first judging unit 503 judges whether the transaction corresponding to the target transaction request is a duplicate transaction according to the transaction event serial number; a handling unit 504, when it is determined that the transaction corresponding to the target transaction request is not a duplicate transaction, handles the target financial service according to the target transaction request, solving the technical problem that duplicate transactions are likely to occur in financial transaction services in a distributed scenario. In this solution, after receiving the target transaction request of the user, it is determined whether the transaction corresponding to the target transaction request is a duplicate transaction according to the transaction event serial number corresponding to the target transaction request. When it is determined that it is not a duplicate transaction, the target financial service is handled. The problem of whether a transaction is repeated can be accurately identified and judged through the transaction event serial number, avoiding duplicate transactions by customers, and thus achieving the effect of improving the security of funds.

[0083] Optionally, in the processing device for financial services provided by the embodiments of the present application, the first obtaining unit 502 includes: a first obtaining module for obtaining area number information and channel category information corresponding to the target transaction request; a second obtaining module for obtaining triggering time information corresponding to the target transaction request; a first determining module for obtaining a transaction event serial number according to the area number information, the channel category information, and the triggering time information.

[0084] Optionally, in the processing device for financial services provided by the embodiments of the present application, the first determining module includes: a first splitting sub-module for splitting the area number information to obtain a first character string; a second splitting sub-module for splitting the channel category information to obtain a second character string; a determining sub-module for determining a time stamp corresponding to the triggering time information; a splicing sub-module for splicing the first character string, the second character string, and the time stamp to obtain a transaction event serial number.

[0085] Optionally, in the processing device for financial services provided by the embodiments of the present application, the first judging unit 503 includes: a third obtaining module for obtaining historical transaction event serial numbers corresponding to a plurality of historical transaction requests; a judging module for judging whether there is a target historical transaction event serial number identical to the transaction event serial number among the plurality of historical transaction event serial numbers; a second determining module for determining that the transaction corresponding to the target transaction request is not a duplicate transaction if there is no target historical transaction event serial number.

[0086] Optionally, in the processing device for financial services provided in the embodiments of the present application, the device further includes: a second acquisition unit, configured to, after determining whether there is a target historical transaction event number identical to the transaction event number among a plurality of historical transaction event numbers, if there is a target historical transaction event number, acquire the historical transaction information corresponding to the target historical transaction event number, where the historical transaction information at least includes transaction amount information and transaction object information; a third acquisition unit, configured to acquire the target transaction information corresponding to the target transaction request; a second judgment unit, configured to judge whether the target transaction information is the same as the historical transaction information; a first determination unit, configured to, if the target transaction information is the same as the historical transaction information, determine that the transaction corresponding to the target transaction request is a duplicate transaction.

[0087] Optionally, in the processing device for financial services provided in the embodiments of the present application, the device further includes: a fourth acquisition unit, configured to, in the case where it is determined that the transaction corresponding to the target transaction request is a duplicate transaction, acquire the historical transaction result corresponding to the target historical transaction event number; a feedback unit, configured to feedback the historical transaction result to the target object corresponding to the target transaction request.

[0088] Optionally, in the processing device for financial services provided in the embodiments of the present application, the device further includes: a second determination unit, configured to, after judging whether the target transaction information is the same as the historical transaction information, if the target transaction information is not the same as the historical transaction information, determine that there is an abnormality in the target transaction request; a trigger unit, configured to, in the case where it is determined that there is an abnormality in the target transaction request, trigger a target signal to the target object corresponding to the target transaction request, where the target signal is used to instruct the target object to initiate a transaction request for the target financial service again.

[0089] It should be noted here that the above-mentioned receiving unit 501, first acquisition unit 502, first judgment unit 503, and handling unit 504 correspond to steps S201 to S204 in the embodiment. The instances and application scenarios implemented by the four units and the corresponding steps are the same, but are not limited to the content disclosed in the above-mentioned Embodiment 1. It should be noted that the above-mentioned module or unit may be a hardware component or a software component stored in a memory (for example, memory 105) and processed by one or more processors (for example, processors 102a, 102b,..., 102n). The above-mentioned module may also be a part of the device and may run in the computer terminal 10 provided in Embodiment 1.

[0090] Embodiment 3

[0091] Embodiments of the present application may provide an electronic device. Figure 6 It is a structural block diagram of an electronic device according to an embodiment of the present application. As Figure 6 shown, the electronic device may include: one or more ( Figure 6Only one processor 602, a memory 604, a storage controller, and a peripheral interface are shown, where the peripheral interface is connected to a radio frequency module, an audio module, and a display.

[0092] The memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the methods and devices in the embodiments of the present application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, that is, to implement the above methods. The memory may include a high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memories. In some instances, the memory may further include a memory remotely located relative to the processor, and these remote memories can be connected to the terminal through a network. Examples of the above network include but are not limited to the Internet, an enterprise intranet, a local area network, a mobile communication network, and combinations thereof.

[0093] The processor can call the information and application programs stored in the memory through a transmission device to perform the following steps: receiving a target transaction request for a target financial service; obtaining a transaction event number corresponding to the target transaction request, where the transaction event number is determined based on the trigger time of the target transaction request; judging whether the transaction corresponding to the target transaction request is a repeated transaction according to the transaction event number; and in the case of determining that the transaction corresponding to the target transaction request is not a repeated transaction, handling the target financial service according to the target transaction request.

[0094] The processor can call the information and application programs stored in the memory through a transmission device to perform the following steps: obtaining the transaction event number corresponding to the target transaction request includes: obtaining the region number information and channel category information corresponding to the target transaction request; obtaining the trigger time information corresponding to the target transaction request; and obtaining the transaction event number according to the region number information, channel category information, and trigger time information.

[0095] The processor can call the information and application programs stored in the memory through a transmission device to perform the following steps: obtaining the transaction event number according to the region number information, channel category information, and trigger time information includes: splitting the region number information to obtain a first string; splitting the channel category information to obtain a second string; determining the time stamp corresponding to the trigger time information; and performing a splicing process on the first string, the second string, and the time stamp to obtain the transaction event number.

[0096] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: based on the transaction event number, determine whether the transaction corresponding to the target transaction request is a duplicate transaction, including: obtaining historical transaction event numbers corresponding to multiple historical transaction requests; determining whether there is a target historical transaction event number that is the same as the transaction event number among the multiple historical transaction event numbers; if the target historical transaction event number does not exist, determining that the transaction corresponding to the target transaction request is not a duplicate transaction.

[0097] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: after determining whether there is a target historical transaction event number that is the same as the transaction event number among multiple historical transaction event numbers, the method also includes: if the target historical transaction event number exists, obtaining historical transaction information corresponding to the target historical transaction event number, wherein the historical transaction information at least includes transaction amount information and transaction object information; obtaining target transaction information corresponding to the target transaction request; determining whether the target transaction information is the same as the historical transaction information; if the target transaction information is the same as the historical transaction information, determining that the transaction corresponding to the target transaction request is a duplicate transaction.

[0098] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: when it is determined that the transaction corresponding to the target transaction request is a duplicate transaction, the method also includes: obtaining the historical transaction results corresponding to the target historical transaction event number; and feeding back the historical transaction results to the target object corresponding to the target transaction request.

[0099] The processor can call the information and application stored in the memory through the transmission device to perform the following steps: after determining whether the target transaction information is the same as the historical transaction information, the method also includes: if the target transaction information is not the same as the historical transaction information, determining that there is an abnormality in the target transaction request; when it is determined that there is an abnormality in the target transaction request, triggering a target signal to the target object corresponding to the target transaction request, wherein the target signal is used to instruct the target object to initiate a transaction request for the target financial service again.

[0100] It can be understood by those skilled in the art that Figure 6 The structure shown is for illustration only, and the electronic device may also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a PDA, a mobile Internet device (Mobile Internet Devices, MID), a PAD, or other terminal devices. Figure 6 The structure of the electronic device is not limited. Figure 6 More or fewer components (such as network interfaces, display devices, etc.) shown in, or having Figure 6 Different configurations are shown.

[0101] Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by a program instructing the relevant hardware of the terminal device. This program can be stored in a computer-readable storage medium, which can include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, an optical disc, etc.

[0102] Embodiment 4

[0103] An embodiment of the present application also provides a computer-readable storage medium. Optionally, in this embodiment, the above storage medium can be used to store the program code executed by the processing method of the financial service provided in the first embodiment above.

[0104] Optionally, in this embodiment, the above storage medium can be located in any one of the computer terminals in the computer terminal group in the computer network, or in any one of the mobile terminals in the mobile terminal group.

[0105] The present application also provides a computer program product, which is suitable for executing a program of the steps of the processing method of the financial service when executed on a data processing device.

[0106] The serial numbers of the above embodiments of the present application are only for description and do not represent the advantages or disadvantages of the embodiments.

[0107] In the above embodiments of the present application, the descriptions of the various embodiments have their own emphases. For the parts not detailed in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0108] In the several embodiments provided by the present application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point, the displayed or discussed coupling or direct coupling or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of the units or modules can be in an electrical or other form.

[0109] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place, or they can be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0110] In addition, each functional unit in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of a software functional unit.

[0111] If the above-mentioned integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, may be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The foregoing storage medium includes: various media such as USB flash drives, read-only memories (ROMs), random access memories (RAMs), mobile hard disks, magnetic disks, or optical discs that can store program codes.

[0112] The above are only the preferred embodiments of the present application. It should be noted that for those of ordinary skill in the art, without departing from the principle of the present application, several improvements and refinements can be made, and these improvements and refinements should also be regarded as the protection scope of the present application.

Claims

1. A method for processing financial services, characterized in that: include: Receiving a target transaction request of a target financial business; Obtaining a transaction event number corresponding to the target transaction request, wherein the transaction event number is determined based on a triggering time of the target transaction request; Determining whether the transaction corresponding to the target transaction request is a repeated transaction based on the transaction event number; When it is determined that the transaction corresponding to the target transaction request is not a duplicate transaction, the target financial service is processed according to the target transaction request.

2. The method according to claim 1, characterized in that Obtaining the transaction event number corresponding to the target transaction request includes: Obtaining the region code information and channel category information corresponding to the target transaction request; Obtaining trigger time information corresponding to the target transaction request; The transaction event number is obtained according to the region code information, the channel category information and the trigger time information.

3. The method according to claim 2, characterized in that According to the region code information, the channel category information and the trigger time information, obtaining the transaction event number includes: Splitting the area code information to obtain a first character string; Splitting the channel category information to obtain a second character string; Determine a timestamp corresponding to the trigger time information; The first character string, the second character string and the timestamp are concatenated to obtain the transaction event number.

4. The method according to claim 1, characterized in that Judging, based on the transaction event number, whether the transaction corresponding to the target transaction request is a repeated transaction includes: Get the historical transaction event numbers corresponding to multiple historical transaction requests; Determine whether there is a target historical transaction event number that is the same as the transaction event number among multiple historical transaction event numbers; If the target historical transaction event number does not exist, it is determined that the transaction corresponding to the target transaction request is not a duplicate transaction.

5. The method according to claim 4, characterized in that After determining whether there is a target historical transaction event number identical to the transaction event number among the plurality of historical transaction event numbers, the method further includes: If the target historical transaction event number exists, obtaining the historical transaction information corresponding to the target historical transaction event number, wherein the historical transaction information at least includes transaction amount information and transaction object information; Acquire target transaction information corresponding to the target transaction request; Determining whether the target transaction information is the same as the historical transaction information; If the target transaction information is the same as the historical transaction information, it is determined that the transaction corresponding to the target transaction request is a repeated transaction.

6. The method according to claim 5, characterized in that In the case where it is determined that the transaction corresponding to the target transaction request is a repeated transaction, the method further includes: Obtain the historical transaction result corresponding to the target historical transaction event number; Feedback the historical transaction results to the target object corresponding to the target transaction request.

7. The method according to claim 5, characterized in that After determining whether the target transaction information is the same as the historical transaction information, the method further includes: If the target transaction information is different from the historical transaction information, it is determined that there is an abnormality in the target transaction request; When it is determined that the target transaction request is abnormal, a target signal is triggered to a target object corresponding to the target transaction request, wherein the target signal is used to instruct the target object to initiate a transaction request for the target financial service again.

8. A financial service processing device, characterized in that: include: A receiving unit, configured to receive a target transaction request of a target financial service; A first acquisition unit, configured to acquire a transaction event number corresponding to the target transaction request, wherein the transaction event number is determined based on a triggering time of the target transaction request; A first judgment unit, configured to judge whether the transaction corresponding to the target transaction request is a repeated transaction according to the transaction event number; The processing unit is used to process the target financial business according to the target transaction request when it is determined that the transaction corresponding to the target transaction request is not a duplicate transaction.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored executable program, wherein when the executable program is run, the device where the computer-readable storage medium is located is controlled to execute the financial business processing method described in any one of claims 1 to 7.

10. An electronic device, characterized in that: include: A memory storing an executable program; A processor is used to run the program, wherein the program, when running, executes the method for processing financial business described in any one of claims 1 to 7.

Images