CN115187396A

CN115187396A - Transaction event order-adjusting method and device, electronic equipment and storage medium

Info

Publication number: CN115187396A
Application number: CN202210689497.7A
Authority: CN
Inventors: 王通礼
Original assignee: Ping An Bank Co Ltd
Current assignee: Ping An Bank Co Ltd
Priority date: 2022-06-16
Filing date: 2022-06-16
Publication date: 2022-10-14

Abstract

The application discloses a transaction event order-adjusting method and device, electronic equipment and a storage medium. The method comprises the following steps: acquiring transaction information of transaction events to be screened; screening the transaction events to be screened according to the transaction failure reasons in the transaction information to obtain order-adjusting events; generating a menu file corresponding to the menu adjusting event according to the transaction information of the menu adjusting event, and storing the menu adjusting event and the menu adjusting file corresponding to the menu adjusting event into a preset database; receiving a list adjusting request, acquiring a target list adjusting event corresponding to the list adjusting request, and sending a target list adjusting file corresponding to the target list adjusting event in the preset database to a target terminal corresponding to the list adjusting request. Therefore, the method can generate the order file in advance, and send the stored target order file to the target terminal, so that the time for waiting for generating the order file after a consumer or a card issuer initiates the order is saved, and the order processing efficiency is improved.

Description

Transaction event order-adjusting method and device, electronic equipment and storage medium

Technical Field

The application relates to the technical field of bank finance, in particular to a transaction event order-adjusting method, a transaction event order-adjusting device, electronic equipment and a storage medium.

Background

The bank card industry comprises a plurality of sub-industries such as card issuing, clearing, receipt and other peripheral services (such as card making and IT services), and integrates a plurality of businesses such as consumption, settlement, credit and the like, wherein the card organization mainly has the function of connecting a card issuing mechanism and an receipt mechanism to complete a series of complex fund clearing processes from the card issuing mechanism to the receipt mechanism. When a consumer conducts consumption transaction through a bank card, sometimes, due to reasons such as order cancellation, transaction failure occurs, and at the moment, the consumer can apply a transfer form to a card organization to determine the specific situation of the transaction.

However, at present, after applying for a ticket, a consumer needs to wait for a long time to obtain a ticket document, and the ticket transferring efficiency is poor.

Disclosure of Invention

The application provides a transaction event order adjusting method, a transaction event order adjusting device, electronic equipment and a storage medium, and aims to solve the problem that the order adjusting efficiency of the conventional transaction event order adjusting method is poor.

In a first aspect, the present application provides a transaction event invoicing method, comprising:

acquiring transaction information of transaction events to be screened;

screening the transaction events to be screened according to the transaction failure reasons in the transaction information to obtain order-adjusting events;

generating a menu file corresponding to the menu event according to the transaction information of the menu event, and storing the menu event and the menu file corresponding to the menu event into a preset database;

receiving a list adjusting request, acquiring a target list adjusting event corresponding to the list adjusting request, and sending a target list adjusting file corresponding to the target list adjusting event in the preset database to a target terminal corresponding to the list adjusting request.

In a possible implementation manner of the present application, the screening the transaction event to be screened according to the reason of the transaction failure in the transaction information to obtain a ticket dispatching event includes:

extracting a transaction object in the transaction information and a transaction failure reason in the transaction information;

determining a target object list containing the transaction object from a plurality of preset object lists;

and acquiring a target reason corresponding to the target object list, and taking the transaction event to be screened, of which the transaction failure reason is the same as the target reason, as a scheduling event.

In a possible implementation manner of the present application, the generating a order file corresponding to the order event according to the transaction information of the order event, and storing the order event and the order file corresponding to the order event in a preset database includes:

inquiring to obtain the environmental information of a preset order terminal;

and generating a receipt file according to a target file format in the environment information and the transaction information of the receipt event, and storing the receipt event and the receipt file corresponding to the receipt event into a preset database.

In a possible implementation manner of the present application, before generating a ticket document according to a target file format in the environment information and the transaction information of the ticket event, and storing the ticket event and the ticket document corresponding to the ticket event in a preset database, the method further includes:

extracting a target transaction object in the transaction information of the order transfer event;

acquiring a historical receipt file corresponding to the target transaction object and a processing result of the historical receipt file;

and if the number of the first preset results in the processing results is smaller than a preset number threshold, executing the step of generating a list adjusting file according to a target file format in the environment information and the transaction information of the list adjusting event, and storing the list adjusting event and the list adjusting file corresponding to the list adjusting event into a preset database.

In a possible implementation manner of the present application, after the generating a ticket document corresponding to the ticket event according to the transaction information of the ticket event, and storing the ticket event and the ticket document corresponding to the ticket event in a preset database, the method further includes:

receiving transaction evidence information, and acquiring a to-be-associated order file corresponding to the transaction evidence information in the preset database;

if the association evidence information of the to-be-associated order file does not exist in a preset evidence information table, associating the to-be-associated order file with the transaction evidence information, and updating the preset evidence information table;

and if the associated evidence information of the to-be-associated tone file exists in a preset evidence information table, outputting preset alarm information to a source terminal of the transaction evidence information.

In a possible implementation manner of the present application, the receiving a order transferring request and sending a target order file corresponding to the order transferring request in the order transferring file to a target terminal corresponding to the order transferring request includes:

receiving a list adjusting request, and acquiring a terminal identifier corresponding to the list adjusting request and a target list adjusting file corresponding to the list adjusting request;

and if the terminal identification is matched with the transaction object corresponding to the target order file, decrypting the target order file through a key corresponding to the terminal identification, and sending the decrypted target order file to a target terminal corresponding to the order request.

In a possible implementation manner of the present application, the obtaining transaction information of the transaction event to be screened includes:

acquiring an initial transaction event;

and according to the transaction place of the initial transaction event, selecting and obtaining the transaction event to be screened with the transaction place as the target place and the transaction information of the transaction event to be screened from the initial transaction event.

In a second aspect, the present application provides a transaction event ordering device, comprising:

the acquisition unit is used for acquiring the transaction information of the transaction event to be screened;

the screening unit is used for screening the transaction events to be screened according to the transaction failure reasons in the transaction information to obtain order-adjusting events;

the generating unit is used for generating a menu file corresponding to the menu event according to the transaction information of the menu event, and storing the menu event and the menu file corresponding to the menu event into a preset database;

and the sending unit is used for receiving the order-adjusting request, acquiring a target order-adjusting event corresponding to the order-adjusting request, and sending a target order-adjusting file corresponding to the target order-adjusting event in the preset database to a target terminal corresponding to the order-adjusting request.

In one possible implementation manner of the present application, the screening unit is further configured to:

and acquiring a target reason corresponding to the target object list, and taking the transaction event to be screened with the same transaction failure reason and the target reason as a scheduling event.

In one possible implementation manner of the present application, the generating unit is further configured to:

inquiring to obtain the environmental information of a preset order terminal;

acquiring a historical tone file corresponding to the target transaction object and a processing result of the historical tone file;

if the associated evidence information of the to-be-associated order document does not exist in a preset evidence information table, associating the to-be-associated order document with the transaction evidence information, and updating the preset evidence information table;

In a possible implementation manner of the present application, the sending unit is further configured to:

In a possible implementation manner of the present application, the obtaining unit is further configured to:

acquiring an initial transaction event;

In a third aspect, the present application further provides an electronic device, which includes a processor, a memory, and a computer program stored in the memory and operable on the processor, wherein the processor executes the steps of any of the transaction event ordering methods provided in the present application when the processor calls the computer program in the memory.

In a fourth aspect, the present application further provides a storage medium having a computer program stored thereon, where the computer program is executed by a processor to implement the steps of any one of the transaction event ordering methods provided in the present application.

To sum up, the transaction event ordering method provided by the embodiment of the present application includes: acquiring transaction information of transaction events to be screened; screening the transaction events to be screened according to the transaction failure reasons in the transaction information to obtain order-adjusting events; generating a menu file corresponding to the menu adjusting event according to the transaction information of the menu adjusting event, and storing the menu adjusting event and the menu adjusting file corresponding to the menu adjusting event into a preset database; receiving a list dispatching request, acquiring a target list dispatching event corresponding to the list dispatching request, and sending a target list dispatching file corresponding to the target list dispatching event in the preset database to a target terminal corresponding to the list dispatching request.

Therefore, in the transaction event order-adjusting method provided by the embodiment of the application, the transaction event to be screened can be screened in advance according to the transaction failure reason of the transaction event to be screened to obtain the order-adjusting event, the order-adjusting file corresponding to the order-adjusting event is generated and stored in advance, and then after receiving the order-adjusting request, the order-adjusting file does not need to be generated in real time, but the preset database can be directly read, and the stored target order-adjusting file is sent to the target terminal, so that the time for waiting for generation of the order-adjusting file after a consumer or an issuer initiates the order adjustment is saved, and the experience and the order-adjusting processing efficiency in the order-adjusting process are improved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a schematic application scenario diagram of a transaction event invoking method according to an embodiment of the present disclosure;

FIG. 2 is a schematic flow chart diagram of a transaction event order method provided in an embodiment of the present application;

FIG. 3 is a schematic flow chart diagram of another transaction event ordering method provided in an embodiment of the present application;

FIG. 4 is a schematic flow chart diagram of another transaction event order-taking method provided in the embodiment of the present application;

FIG. 5 is a schematic flow chart diagram illustrating a transaction event order method provided in an embodiment of the present application;

FIG. 6 is a schematic flow chart of updating the preset evidence information table provided in the embodiment of the present application;

fig. 7 is a schematic flowchart of sending the decrypted target tone file to the target terminal according to the embodiment of the present application;

FIG. 8 is a flow chart illustrating a process for obtaining transaction information of transaction events to be filtered according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of an embodiment of a transaction event order device provided in the embodiment of the present application;

fig. 10 is a schematic structural diagram of an embodiment of an electronic device provided in the embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

In the description of the embodiments of the present application, it should be understood that the terms "first", "second", and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or to implicitly indicate the number of technical features indicated. Thus, features defined as "first", "second", may explicitly or implicitly include one or more of the described features. In the description of the embodiments of the present application, "a plurality" means two or more unless specifically defined otherwise.

The following description is presented to enable any person skilled in the art to make and use the application. In the following description, details are set forth for the purpose of explanation. It will be apparent to one of ordinary skill in the art that the present application may be practiced without these specific details. In other instances, well-known processes have not been described in detail so as not to obscure the description of the embodiments of the present application with unnecessary detail. Thus, the present application is not intended to be limited to the embodiments shown, but is to be accorded the widest scope consistent with the principles and features disclosed in the embodiments herein.

The embodiment of the application provides a transaction event order-adjusting method and device, electronic equipment and a storage medium. The transaction event order-adjusting device can be integrated in an electronic device, and the electronic device can be a server or a terminal and the like.

The execution main body of the transaction event ordering method according to the embodiment of the present application may be the transaction event ordering device provided in the embodiment of the present application, or different types of electronic devices such as a server device, a physical host, or a User Equipment (UE) integrated with the transaction event ordering device, where the transaction event ordering device may be implemented in a hardware or software manner, and the UE may specifically be a terminal device such as a smart phone, a tablet computer, a notebook computer, a palm computer, a desktop computer, or a Personal Digital Assistant (PDA).

The electronic device may adopt a working mode of independent operation, or may also adopt a working mode of a device cluster.

Referring to fig. 1, fig. 1 is a schematic view of a scenario of a transaction event order system according to an embodiment of the present application. The transaction event ordering system may include an electronic device 101, and a transaction event ordering apparatus is integrated in the electronic device 101.

In addition, as shown in FIG. 1, the transaction event ordering system may also include a memory 102 for storing data, such as storing text data.

It should be noted that the scenario diagram of the transaction event scheduling system shown in fig. 1 is only an example, and the transaction event scheduling system and the scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application.

In the following, a description is started on a transaction event ordering method provided in an embodiment of the present application, in the embodiment of the present application, an electronic device is used as an execution subject, and for simplicity and convenience of description, the execution subject will be omitted in subsequent embodiments of the method, and the transaction event ordering method includes: acquiring transaction information of transaction events to be screened; screening the transaction events to be screened according to the transaction failure reasons in the transaction information to obtain order adjusting events; generating a menu file corresponding to the menu adjusting event according to the transaction information of the menu adjusting event, and storing the menu adjusting event and the menu adjusting file corresponding to the menu adjusting event into a preset database; receiving a list dispatching request, acquiring a target list dispatching event corresponding to the list dispatching request, and sending a target list dispatching file corresponding to the target list dispatching event in the preset database to a target terminal corresponding to the list dispatching request.

Referring to fig. 2, fig. 2 is a schematic flow chart diagram of a transaction event order-calling method according to an embodiment of the present application. It should be noted that, although a logical order is shown in the flow chart, in some cases, the steps shown or described may be performed in an order different than that shown or described herein. The transaction event invoking method may specifically include the following steps 201 to 204, wherein:

201. and acquiring the transaction information of the transaction event to be screened.

The transaction event may refer to an event generated after a consumer initiates a transaction by using a credit card, a deposit card, or the like. For example, a transaction event is generated when a consumer pays through a credit card at a merchant. In the embodiment of the present application, the transaction event may further refer to an event generated after the transaction is failed. The reasons for the transaction failure may include cancellation of the transaction by the consumer, cancellation of the transaction by the transaction object, cash back failure, repeated initiation of the transaction, and so on.

The transaction information for the transaction event may include consumption information when the consumer conducts the transaction. For example, the transaction information may include information about the transaction object of the consumer, the transaction amount, the reason for the failure of the transaction, and the like.

Wherein the transaction information of the transaction event may be stored in a background database of the card organization. When a consumer initiates a transaction and generates a transaction event, the transaction information of the transaction event is sent to a background database of the card organization, and in step 201, the electronic device reads the transaction information of the transaction event to be screened from the background database.

202. And screening the transaction events to be screened according to the transaction failure reasons in the transaction information to obtain order-adjusting events.

For the description of the reason of the transaction failure, reference may be made to the above description, which is not repeated herein.

The order-mixing event refers to an event that the consumer or the issuer possibly initiates order mixing in the transaction events. Due to various reasons for transaction failure, for some reasons, such as cancellation of transaction by the consumer, the consumer will not be confused about the reason for transaction failure, and further will not initiate a menu to view the transaction information corresponding to the transaction event. For another part of reasons, such as canceling the transaction by the transaction object, the consumer is easy to confuse the reason of the transaction failure, and may initiate a transaction order to view the transaction information corresponding to the transaction event, and for the transaction event whose reason of the transaction failure is these reasons, the transaction event may be set as the transaction order event. Or, for some reasons, such as repeated initiation of transaction, the issuer does not need to determine whether to initiate a denial payment according to the corresponding transaction information, and thus, for the corresponding transaction event, the issuer does not initiate a reconciliation. For another part of reasons, such as cash-back failure, the issuer may need to determine whether to initiate a repudiation according to the corresponding transaction information, and therefore, for the corresponding transaction event, the issuer may initiate a bill transfer. For ease of understanding, in the following, a call order is considered to be initiated by a consumer if not specifically stated.

The order-transferring process refers to a process of applying for transferring transaction information to a card organization when a consumer or an issuer disagrees with a transaction event.

As can be seen from the above description, when the electronic device filters the transaction event to be filtered, it may be determined whether the transaction failure reason is the preset reason, and if the transaction failure reason is the preset reason, the corresponding transaction event may be set as the order-adjusting event. For example, the transaction object cancel transaction and the transaction repeat initiation may be set as a preset reason, and if the transaction failure reason is that the transaction object cancels transaction or the transaction repeat initiation, the corresponding transaction event is set as a ticket order event.

203. And generating a list adjusting file corresponding to the list adjusting event according to the transaction information of the list adjusting event, and storing the list adjusting event and the list adjusting file corresponding to the list adjusting event into a preset database.

The order file may refer to a document file that contains transaction information for the order event. For example, a order file may refer to a POS receipt file that contains transaction information for the order event.

The preset database can be a background database of the card organization, after the order file corresponding to the order event is generated, the electronic equipment stores the order file into the background database of the card organization, and then when a consumer or a card issuing bank initiates the order, the electronic equipment can read the corresponding order file from the background database of the card organization without regeneration, so that the waiting time of the consumer or the card issuing bank can be saved, and the experience and the order adjusting efficiency during the order adjustment are improved.

204. Receiving a list dispatching request, acquiring a target list dispatching event corresponding to the list dispatching request, and sending a target list dispatching file corresponding to the target list dispatching event in the preset database to a target terminal corresponding to the list dispatching request.

The target terminal may be a terminal that issues a order adjustment request, and may be a smart phone, a personal computer, and the like, which is not limited in this embodiment of the application. For example, when a customer sends a order-adjusting request through a personal computer, the target terminal is the personal computer.

The order-changing request refers to a request generated when a consumer or an issuer initiates order-changing. For example, when a consumer initiates a ticket adjustment through a webpage, the consumer clicks the 'application ticket adjustment', and simultaneously generates a ticket adjustment request, if the consumer accesses the webpage through a personal computer, the personal computer generates the ticket adjustment request and then sends the ticket adjustment request to the electronic equipment, the electronic equipment obtains a target ticket adjustment event corresponding to the ticket adjustment request, queries a preset database, and sends a target ticket adjustment file corresponding to the target ticket adjustment event in the preset database to the personal computer, so that the user can confirm the transaction information of the target ticket adjustment event.

It can be seen that in the transaction event order-transferring method provided in the embodiment of the present application, the transaction event to be screened may be screened in advance according to the transaction failure reason of the transaction event to be screened, so as to obtain the order-transferring event, and the order-transferring file corresponding to the order-transferring event is generated and stored in advance, and then when step 204 is executed, the electronic device may directly read the preset database without generating the order-transferring file in real time, and send the stored target order-transferring file to the target terminal, so that the time for waiting for generating the order-transferring file after a customer or an issuer initiates an order-transferring is saved, and the experience and the order-transferring processing efficiency of the order-transferring process are improved.

To sum up, the transaction event ordering method provided by the embodiment of the present application includes: acquiring transaction information of transaction events to be screened; screening the transaction events to be screened according to the transaction failure reasons in the transaction information to obtain order-adjusting events; generating a menu file corresponding to the menu adjusting event according to the transaction information of the menu adjusting event, and storing the menu adjusting event and the menu adjusting file corresponding to the menu adjusting event into a preset database; receiving a list adjusting request, acquiring a target list adjusting event corresponding to the list adjusting request, and sending a target list adjusting file corresponding to the target list adjusting event in the preset database to a target terminal corresponding to the list adjusting request.

In some embodiments, the rule for screening the transaction event to be screened in step 202 may vary according to different transaction objects, so that the accuracy of screening may be improved, and the situation that the transaction event with a low probability of initiating order change is set as the order change event, which wastes computational resources and causes data redundancy in the preset database, is avoided. Referring to fig. 3, at this time, the step "screening the transaction event to be screened according to the transaction failure reason in the transaction information to obtain a scheduling event" includes:

301. and extracting a transaction object in the transaction information and a transaction failure reason in the transaction information.

The transaction object may refer to a merchant object when a consumer conducts a transaction. For example, after a merchant pays through a credit card, the transaction object in the generated transaction event is the merchant.

For the description of the reason for the transaction failure, reference may be made to the above description, which is not repeated herein.

302. And determining a target object list containing the transaction object from a plurality of preset object lists.

The preset object list refers to a merchant list. Illustratively, the preset object list may include a white list and a black list. The white list includes merchants without malicious transaction records such as malicious sales slips, malicious billing and the like, and the black list includes merchants with malicious transaction records such as malicious sales slips, malicious billing and the like. Therefore, the purpose of step 302 is to determine whether malicious records such as malicious sales slips, malicious invoices and the like exist in the transaction object. For example, if the white list includes an a merchant and a B merchant, and the black list includes a C merchant and a D merchant, when the transaction object is the a merchant, the target object list is the white list, and the electronic device may determine that the transaction object does not have malicious transaction records such as malicious bill of sale, malicious bill of credit, and the like. And when the transaction object is the C merchant, the target object list is a blacklist, and the electronic equipment can judge that the transaction object has malicious transaction records such as malicious bill of sale, malicious bill of credit and the like.

303. And acquiring a target reason corresponding to the target object list, and taking the transaction event to be screened with the same transaction failure reason and the target reason as a scheduling event.

The target reason is a reason for screening the transaction event to be screened, and if the reason for the transaction failure is the same as the target reason, it is indicated that the transaction event to be screened is an event that the order may be initiated by a consumer or an issuer, so the electronic device may use the transaction event to be screened as an order-mixing event.

For example, when the preset object list includes a white list and a black list, a reason related to the transaction object, such as "transaction object cancel transaction", may be used as a reason corresponding to the black list, and a reason unrelated to the transaction object, such as "transaction repeat initiation", may be used as a reason corresponding to the white list. If the target object list is a white list, the target reason can be the reason related to the transaction object, such as 'transaction object cancel transaction', and if the reason of transaction failure is the same as the target reason, the transaction event to be screened is taken as a scheduling event. If the target object list is a blacklist, the target reason can be the reason irrelevant to the transaction object, such as 'transaction repeated initiation', and the like, and if the reason of transaction failure is the same as the target reason, the transaction event to be screened is taken as a scheduling event.

The preset object lists and the corresponding reasons can be stored in a background database of the card organization, when the steps 301 to 303 are executed, the electronic device reads the preset object lists and the corresponding reasons from the background database, then determines a target object list from the preset object lists, and selects and obtains a menu adjusting event from the transaction events to be screened according to the target reasons corresponding to the target object list.

In some embodiments, when the electronic device generates the order file, the format of the order file may be determined according to a storage format of the background database of the card organization. Referring to fig. 4, at this time, the step "generating a menu file corresponding to the menu event according to the transaction information of the menu event, and storing the menu event and the menu file corresponding to the menu event in a preset database" includes:

401. and querying to obtain the preset environment information of the order terminal.

The order terminal refers to a terminal capable of issuing an order request. Illustratively, the order terminal may include all terminals capable of issuing order requests, such as a smart phone, a personal computer, and the like. It is understood that the target terminal is one of the tuning terminals.

The environment information of the tuning terminal may include a system version supported by the tuning terminal, an output format of the tuning terminal when outputting the tuning file, and the like, and the environment information of the tuning terminal may also be stored in a background database organized by the card, and when step 401 is executed, the electronic device reads the environment information of the tuning terminal from the background database.

402. And generating a receipt file according to a target file format in the environment information and the transaction information of the receipt event, and storing the receipt event and the receipt file corresponding to the receipt event into a preset database.

The target file format may be an output format of the order file when the order terminal outputs the order file. For example, when the order terminal outputs the order file, the order file is output in a Portable Document Format (PDF) Format, and the target file Format may be a PDF Format. For another example, when the scheduling terminal outputs the scheduling file, the scheduling terminal outputs the scheduling file in a Portable Network Graphics (PNG) format, and the destination file format may be the PNG format. It can be understood that, if the target file format is the PDF format, the format of the generated ticket file is the PDF format, and if the target file format is the PNG format, the format of the generated ticket file is the PNG format.

In some embodiments, before executing step 402, the electronic device may further determine, according to a historical order-transferring processing result of the target transaction object, whether a reason for transaction failure of the order-transferring event is an individual reason of the target transaction object, and when the reason for transaction failure of the order-transferring event is the individual reason of the target transaction object, determine that a possibility of subsequently generating an order-transferring requirement is low, and no order-transferring file is generated. Referring to fig. 5, at this time, before the step "generating a order file according to a target file format in the environment information and the transaction information of the order event, and storing the order event and the order file corresponding to the order event in a preset database", the method further includes:

501. and extracting a target transaction object in the transaction information of the order-transferring event.

For the description of the target transaction object, reference may be made to the above description, which is not repeated herein.

502. And acquiring a historical tone file corresponding to the target transaction object and a processing result of the historical tone file.

The historical tone file corresponding to the target transaction object refers to a generated tone file in which the transaction object is the target transaction object in the contained transaction information.

The history list file may also be stored in the preset database described above.

The processing result of the historical order file refers to the follow-up processing performed after a consumer or an issuer initiates an order and receives the historical order file. Wherein, the processing result of one history order file can be one of the results of payment refusal, re-transaction and the like. For example, after receiving the historical tone file, the consumer determines that there is no risk in the tone event corresponding to the historical tone file, and may initiate the transaction event again, and at this time, the processing result corresponding to the historical tone file may be a re-transaction.

503. And if the number of the first preset results in the processing results is smaller than a preset number threshold, executing the step of generating a list adjusting file according to a target file format in the environment information and the transaction information of the list adjusting event, and storing the list adjusting event and the list adjusting file corresponding to the list adjusting event into a preset database.

The first preset result may be a result that can determine that the transaction failure cause of the order transfer event is an individual cause of the target transaction object. For example, the first preset result may be the above-mentioned "re-transaction" because when the transaction failure of the order-changing event is due to an individual reason such as a failure of the payment system used by the target transaction object, the consumer generally does not think that the transaction is at risk, and therefore the transaction will be initiated again, and at this time, even if the transaction fails, the probability that the consumer will initiate the order-changing event is relatively low.

In the embodiment of the application, whether the transaction failure reason of the order transfer event is the individual reason of the target transaction object is judged by judging the number of the first preset results. For example, if the number of the first preset results is larger, it indicates that the number of times the consumer initiates the transaction again is larger, and the transaction failure cause of the order transfer event is an individual cause such as a failure of the payment system used by the target transaction object. If the number of the first preset results is smaller, the reason that the transaction failure of the order transfer event is not the individual reason of the target transaction object is described.

The preset quantity threshold is used for judging the quantity degree of the first preset result, and can be set according to the actual scene requirement. When the number of the first preset results is smaller than a preset number threshold, it can be judged that the transaction failure reason of the order-transferring event is not the individual reason of the target transaction object, and then the steps of generating an order-transferring file according to the target file format in the environment information and the transaction information of the order-transferring event, and storing the order-transferring event and the order-transferring file corresponding to the order-transferring event in a preset database can be executed. When the number of the first preset results is larger than or equal to the preset number threshold, the transaction failure reason of the order transfer event can be judged to be the individual reason of the target transaction object, at this time, the possibility that the consumer subsequently initiates the order transfer can be judged to be low, the preset database redundancy is avoided, the calculation power is saved, and the order transfer file is not generated.

In order to save time for manually associating the evidence file with the order file, in some embodiments, the electronic device may further associate the evidence file with the corresponding order file automatically after receiving the evidence file uploaded by the consumer, and perform an alarm when the evidence file is repeatedly uploaded by the consumer. Referring to fig. 6, at this time, after the step "generating a order file corresponding to the order event according to the transaction information of the order event, and storing the order event and the order file corresponding to the order event in a preset database", the method further includes:

601. and receiving transaction evidence information, and acquiring a to-be-associated order file corresponding to the transaction evidence information in the preset database.

Transaction evidence information refers to information contained in an evidence file uploaded by a consumer. For example, after acquiring a statement file containing a transaction failure reason that the consumer cancels the transaction, if there is an objection to the transaction failure reason, the consumer can upload an evidence file such as a payment bill of the consumer and the like for proving that the consumer does not cancel the transaction, at this time, the transaction evidence information is information contained in the evidence file, and after acquiring the evidence file uploaded by the user, the electronic device can use the information contained in the evidence file as transaction evidence information and use the statement file as a statement file to be associated corresponding to the transaction evidence information.

And 602A, if the associated evidence information of the to-be-associated order file does not exist in a preset evidence information table, associating the to-be-associated order file with the transaction evidence information, and updating the preset evidence information table.

The preset evidence information table may be a data table for storing evidence files. For example, the background database organized by the card may be partitioned to obtain a plurality of storage blocks, some of the storage blocks are used to store a tone file, and other storage blocks are used to store an evidence file, where the other storage blocks are a preset evidence information table.

The associated evidence information of the to-be-associated order file refers to an evidence file already associated with the to-be-associated order file in the preset evidence information table, that is, step 602A refers to a situation that a consumer uploads the evidence file associated with the to-be-associated order file for the first time, at this time, the electronic device may associate the to-be-associated order file with the transaction evidence information and update the preset evidence information table, and after the update, if the preset evidence information table is queried again, the associated evidence information of the to-be-associated order file is the transaction evidence information included in the evidence file uploaded by the consumer.

And 602B, if the associated evidence information of the to-be-associated order file exists in a preset evidence information table, outputting preset alarm information to a source terminal of the transaction evidence information.

The source terminal refers to a terminal for uploading transaction evidence information, and may be a smart phone, a personal computer, or the like, which is not limited in the embodiment of the present application.

It is understood that step 602B refers to a case where the customer does not upload the evidence file associated with the to-be-associated statement file for the first time, that is, the customer repeatedly uploads the evidence file, at this time, the electronic device may send a preset warning message, for example, "do not repeatedly upload" to the source terminal of the transaction evidence information.

In some embodiments, in order to protect the privacy of the consumer, the order file may be encrypted, and the decrypted order file may be sent to the terminal initiating the order request only when the terminal initiating the order request matches the consumer to which the order file corresponds. Referring to fig. 7, at this time, the step "receiving a order-tuning request, and sending a target order-tuning file corresponding to the order-tuning request in the order-tuning file to a target terminal corresponding to the order-tuning request" includes:

701. receiving a list adjusting request, and acquiring a target terminal identification corresponding to the list adjusting request and a target list adjusting file corresponding to the list adjusting request.

For the description of the order-adjusting request, reference may be made to the above description, which is not repeated herein.

The target terminal identifier corresponding to the order transferring request may refer to an identifier of a target terminal that sends the order transferring request, and the description of the target terminal may refer to the foregoing description and is not repeated in detail.

702. And if the target terminal identification is matched with the consumer corresponding to the target menu file, decrypting the target menu file through a key corresponding to the target terminal identification, and sending the decrypted target menu file to the target terminal corresponding to the menu request.

If the target terminal identification is matched with the consumer corresponding to the target order file, the order request is sent out by the consumer corresponding to the target order file, and the privacy of the consumer cannot be revealed when the decrypted target order file is sent to the target terminal, so that the decrypted target order file can be sent to the target terminal corresponding to the order request. And if the target terminal identification is not matched with the consumer corresponding to the target menu file, the menu request is not sent by the consumer corresponding to the target menu file, and at the moment, the privacy of the consumer may be leaked by sending the decrypted target menu file to the target terminal, so that the electronic equipment does not send the decrypted target menu file to the target terminal, or the electronic equipment can also carry out face recognition, fingerprint recognition and other verification through the target terminal so as to further confirm whether the menu request is sent by the consumer corresponding to the target menu file.

It should be noted that, in this embodiment of the application, the order file needs to be encrypted when the order file is generated, a key used for encryption may be preset by a consumer and associated with a terminal used by the consumer, and when step 702 is executed, the electronic device may decrypt according to the key corresponding to the terminal identifier.

Because the transaction places are different, the obtained information is different when the electronic equipment acquires the transaction information of the transaction events, and the transaction information of the transaction events occurring in part of the transaction places does not contain transaction failure reasons, when the electronic equipment acquires the transaction information of the transaction events to be screened, the corresponding transaction places can be located at the target places, and then the transaction events containing the transaction failure reasons in the transaction information are taken as the transaction events to be screened. Referring to fig. 8, at this time, the step of "obtaining transaction information of transaction events to be screened" includes:

801. an initial transaction event is obtained.

The initial transaction event may refer to all transaction events that have been generated. For example, the initial transaction event may refer to all transaction events contained in the preset database.

802. And according to the transaction place of the initial transaction event, selecting and obtaining the transaction event to be screened with the transaction place as the target place and the transaction information of the transaction event to be screened from the initial transaction event.

Illustratively, the target site may refer to an overseas site. For example, all places outside the country where the electronic device is located may be set as target places, and if the transaction place of the initial transaction event is outside the country where the electronic device is located, it is determined that the transaction place of the initial transaction event is the target place, and the initial transaction event is taken as the transaction event to be screened.

In order to better implement the transaction event order adjusting method in the embodiment of the present application, on the basis of the transaction event order adjusting method, an embodiment of the present application further provides a transaction event order adjusting device, as shown in fig. 9, which is a schematic structural diagram of an embodiment of the transaction event order adjusting device in the embodiment of the present application, and the transaction event order adjusting device 900 includes:

an obtaining unit 901, configured to obtain transaction information of a transaction event to be screened;

the screening unit 902 is configured to screen the transaction event to be screened according to the transaction failure reason in the transaction information to obtain a ticket dispatching event;

the generating unit 903 is configured to generate a order file corresponding to the order event according to the transaction information of the order event, and store the order event and the order file corresponding to the order event in a preset database;

a sending unit 904, configured to receive the order-tuning request, obtain a target order-tuning event corresponding to the order-tuning request, and send a target order-tuning file corresponding to the target order-tuning event in the preset database to a target terminal corresponding to the order-tuning request.

In a possible implementation manner of the present application, the screening unit 902 is further configured to:

In a possible implementation manner of the present application, the generating unit 903 is further configured to:

inquiring to obtain the environmental information of a preset order terminal;

and if the number of the first preset results in the processing results is smaller than a preset number threshold, executing the step of generating a menu file according to a target file format in the environment information and the transaction information of the menu event, and storing the menu event and the menu file corresponding to the menu event into a preset database.

receiving transaction evidence information, and acquiring a to-be-associated bill transfer file corresponding to the transaction evidence information in the preset database;

In a possible implementation manner of the present application, the sending unit 904 is further configured to:

In a possible implementation manner of the present application, the obtaining unit 901 is further configured to:

acquiring an initial transaction event;

In a specific implementation, the above units may be implemented as independent entities, or may be combined arbitrarily to be implemented as the same or several entities, and the specific implementation of the above units may refer to the foregoing method embodiments, which are not described herein again.

Since the transaction event order-transferring device can execute the steps in the transaction event order-transferring method in any embodiment, the beneficial effects that can be realized by the transaction event order-transferring method in any embodiment of the present application can be realized, which are detailed in the foregoing description and will not be described herein again.

In addition, in order to better implement the transaction event order method in the embodiment of the present application, based on the transaction event order method, an electronic device is further provided in the embodiment of the present application, referring to fig. 10, fig. 10 shows a schematic structural diagram of the electronic device in the embodiment of the present application, specifically, the electronic device provided in the embodiment of the present application includes a processor 1001, and when the processor 1001 is used for executing the computer program stored in the memory 1002, each step of the transaction event order method in any embodiment is implemented; alternatively, the processor 1001 is configured to implement the functions of the modules in the corresponding embodiment of fig. 9 when executing the computer program stored in the memory 1002.

Illustratively, a computer program may be partitioned into one or more modules/units, which are stored in the memory 1002 and executed by the processor 1001 to implement embodiments of the present application. One or more modules/units may be a series of computer program instruction segments capable of performing certain functions, the instruction segments being used to describe the execution of a computer program in a computer device.

The electronic device may include, but is not limited to, a processor 1001, a memory 1002. Those skilled in the art will appreciate that the illustrations are merely examples of electronic devices and are not meant to be limiting, and may include more or fewer components than those shown, or some components may be combined, or different components.

The Processor 1001 may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, discrete hardware component, etc. The general purpose processor may be a microprocessor or the processor may be any conventional processor or the like, the processor being the control center for the electronic device and various interfaces and lines connecting the various parts of the overall electronic device.

The memory 1002 may be used to store computer programs and/or modules, and the processor 1001 implements various functions of the computer device by running or executing the computer programs and/or modules stored in the memory 1002 and calling data stored in the memory 1002. The memory 1002 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, video data, etc.) created according to the use of the electronic device, etc. In addition, the memory may include high speed random access memory, and may also include non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), at least one magnetic disk storage device, a Flash memory device, or other volatile solid state storage device.

It can be clearly understood by those skilled in the art that, for convenience and simplicity of description, the specific working processes of the transaction event ordering device, the electronic device and the corresponding units thereof described above may refer to the description of the transaction event ordering method in any embodiment, and are not described herein again in detail.

It will be understood by those skilled in the art that all or part of the steps in the methods of the above embodiments may be performed by instructions or by instructions controlling associated hardware, and the instructions may be stored in a storage medium and loaded and executed by a processor.

For this reason, the embodiments of the present application provide a storage medium, where a computer program is stored on the storage medium, and the computer program is executed by a processor to perform the steps in the transaction event invoicing method in any embodiment of the present application, and specific operations may refer to descriptions of the transaction event invoicing method in any embodiment, and are not described herein again.

Wherein the storage medium may include: read Only Memory (ROM), random Access Memory (RAM), magnetic or optical disks, and the like.

The instructions stored in the storage medium may execute the steps in the transaction event order adjusting method in any embodiment of the present application, so that the beneficial effects that can be achieved by the transaction event order adjusting method in any embodiment of the present application may be achieved, which are described in detail in the foregoing description and will not be described herein again.

The transaction event order-adjusting method, the transaction event order-adjusting device, the storage medium and the electronic device provided by the embodiment of the application are introduced in detail, a specific example is applied in the description to explain the principle and the implementation of the application, and the description of the embodiment is only used for helping to understand the method and the core idea of the application; meanwhile, for those skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.

Claims

1. A transaction event ordering method, comprising:

acquiring transaction information of transaction events to be screened, wherein the transaction events can be events generated after a consumer initiates a transaction through at least one of a credit card and a deposit card;

screening the transaction events to be screened according to the transaction failure reasons in the transaction information to obtain order adjusting events;

generating a menu file corresponding to the menu event according to the transaction information of the menu event, and storing the menu event and the menu file corresponding to the menu event into a preset database, wherein the preset database is a background database organized by cards;

2. The method for dispatching orders for transaction events according to claim 1, wherein the screening the transaction events to be screened according to the reason for transaction failure in the transaction information to obtain the dispatching orders for the transaction events comprises:

3. The transaction event order taking method according to claim 1, wherein the generating of the order file corresponding to the order taking event according to the transaction information of the order taking event and the storing of the order taking event and the order file corresponding to the order taking event in a preset database include:

inquiring to obtain the environmental information of a preset order terminal;

4. The method for dispatching orders for transaction events according to claim 3, wherein before generating an order file according to a target file format in the environment information and the transaction information of the order event and storing the order event and the order file corresponding to the order event in a preset database, the method further comprises:

5. The transaction event order-calling method according to claim 1, wherein after the order file corresponding to the order event is generated according to the transaction information of the order event and the order file corresponding to the order event are stored in a preset database, the method further comprises:

and if the associated evidence information of the to-be-associated order file exists in a preset evidence information table, outputting preset alarm information to a source terminal of the transaction evidence information.

6. The method for scheduling transaction events according to claim 1, wherein the receiving a scheduling request and sending a target scheduling file corresponding to the scheduling request in the scheduling file to a target terminal corresponding to the scheduling request comprises:

receiving a list adjusting request, and acquiring a target terminal identification corresponding to the list adjusting request and a target list adjusting file corresponding to the list adjusting request;

and if the target terminal identification is matched with the consumer corresponding to the target menu file, decrypting the target menu file through a key corresponding to the target terminal identification, and sending the decrypted target menu file to the target terminal corresponding to the menu request.

7. The transaction event ordering method according to any of claims 1 to 6, wherein the obtaining of transaction information of the transaction event to be screened comprises:

acquiring an initial transaction event;

8. A transaction event ordering device, comprising:

the acquisition unit is used for acquiring transaction information of transaction events to be screened;

9. An electronic device comprising a processor, a memory, and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the transaction event invoicing method according to any of claims 1 to 7 when executing the computer program.

10. A storage medium having stored thereon a computer program which, when executed by a processor, carries out the steps of the transaction event invoicing method of any of claims 1 to 7.