Transaction event order placement method and device, electronic equipment and storage medium

Abstract

This application discloses a method, apparatus, electronic device, and storage medium for requesting transaction events. The method includes: acquiring transaction information of transaction events to be screened; screening the transaction events to be screened based on the transaction failure reasons in the transaction information to obtain request events; generating a request file corresponding to the request event based on the transaction information of the request event, and storing the request event and the request file corresponding to the request event in a preset database; receiving a request request, acquiring the target request event corresponding to the request request, and sending the target request file corresponding to the target request event in the preset database to the target terminal corresponding to the request request. Therefore, this method can pre-generate request files and send the stored target request files to the target terminal, saving the time spent by consumers or card issuers waiting for the request file to be generated after initiating a request, thus improving the efficiency of request processing.

Description

Technical Field

[0001] This application relates to the field of banking and financial technology, specifically to a method, apparatus, electronic device, and storage medium for requesting transaction events. Background Technology

[0002] The bank card industry encompasses multiple sub-sectors, including card issuance, clearing, acquiring, and other related services (such as card production and IT services). It integrates various businesses such as consumption, settlement, and credit. Card organizations primarily connect card issuers and acquirers, facilitating the complex fund clearing process from card issuer to acquirer. When consumers conduct transactions using bank cards, transactions may sometimes fail due to order cancellations or other reasons. In such cases, consumers can request a transaction review from the card organization to clarify the specific circumstances of the transaction.

[0003] However, currently, consumers have to wait a long time to obtain the request documents after applying for a request, resulting in poor efficiency. Summary of the Invention

[0004] This application provides a method, apparatus, electronic device, and storage medium for order retrieving during transaction events, aiming to solve the problem of poor retrieving efficiency in current order retrieving methods for transaction events.

[0005] Firstly, this application provides a method for requesting order details in a transaction event, including:

[0006] Retrieve transaction information for the transaction events to be filtered;

[0007] Based on the reasons for transaction failure in the transaction information, the transaction events to be screened are filtered to obtain the order adjustment events;

[0008] Based on the transaction information of the order adjustment event, generate the order adjustment file corresponding to the order adjustment event, and store the order adjustment event and the order adjustment file corresponding to the order adjustment event in a preset database;

[0009] Receive a request for a service request, obtain the target service request event corresponding to the request, and send the target service request file corresponding to the target service request event in the preset database to the target terminal corresponding to the request.

[0010] In one possible implementation of this application, the step of filtering the transaction events to be screened based on the transaction failure reasons in the transaction information to obtain the order rescheduling events includes:

[0011] Extract the transaction object from the transaction information, and the reason for the transaction failure from the transaction information;

[0012] Determine a target object list containing the transaction object from multiple preset object lists;

[0013] Obtain the target reasons corresponding to the target object list, and select the transaction events whose transaction failure reasons are the same as the target reasons as the order adjustment events.

[0014] In one possible implementation of this application, the step of generating a request file corresponding to the request event based on the transaction information of the request event, and storing the request event and the request file corresponding to the request event in a preset database, includes:

[0015] The system retrieves the environment information of the preset call terminal.

[0016] Based on the target file format in the environmental information and the transaction information of the order adjustment event, an order adjustment file is generated, and the order adjustment event and the order adjustment file corresponding to the order adjustment event are stored in a preset database.

[0017] In one possible implementation of this application, before generating a request file based on the target file format in the environmental information and the transaction information of the request event, and storing the request event and the request file corresponding to the request event in a preset database, the method further includes:

[0018] Extract the target transaction object from the transaction information of the order adjustment event;

[0019] Obtain the historical order transfer file corresponding to the target transaction object, and the processing result of the historical order transfer file;

[0020] If the number of the first preset results in the processing results is less than a preset number threshold, then the steps of generating a transaction file based on the target file format in the environment information and the transaction information of the transaction event, and storing the transaction event and the transaction file corresponding to the transaction event in a preset database are executed.

[0021] In one possible implementation of this application, after generating a request file corresponding to the request event based on the transaction information of the request event, and storing the request event and the request file corresponding to the request event in a preset database, the method further includes:

[0022] Receive transaction evidence information and obtain the transaction inquiry file to be associated with the transaction evidence information in the preset database;

[0023] If the pre-set evidence information table does not contain the associated evidence information for the transaction file to be associated, then the transaction file to be associated and the transaction evidence information are associated, and the pre-set evidence information table is updated.

[0024] If the preset evidence information table contains the associated evidence information of the transaction order file to be associated, then the preset alarm information is output to the source terminal of the transaction evidence information.

[0025] In one possible implementation of this application, receiving the request and sending the target request file corresponding to the request in the request file to the target terminal corresponding to the request includes:

[0026] Accept the request for a service request, obtain the terminal identifier corresponding to the request for a service request, and the target service request file corresponding to the request for a service request;

[0027] If the terminal identifier matches the transaction object corresponding to the target order file, the target order file is decrypted using the key corresponding to the terminal identifier, and the decrypted target order file is sent to the target terminal corresponding to the order request.

[0028] In one possible implementation of this application, obtaining the transaction information of the transaction events to be filtered includes:

[0029] Obtain the initial transaction event;

[0030] Based on the transaction location of the initial transaction event, select from the initial transaction events a filterable transaction event with the transaction location as the target location, and obtain the transaction information of the filterable transaction event.

[0031] Secondly, this application provides a transaction event order reconciliation device, comprising:

[0032] The acquisition unit is used to acquire transaction information of the transaction events to be filtered.

[0033] The filtering unit is used to filter the transaction events to be filtered according to the reasons for transaction failure in the transaction information to obtain the order adjustment events;

[0034] The generation unit is used to generate a transaction file corresponding to the transaction event based on the transaction information of the transaction event, and to store the transaction event and the transaction file corresponding to the transaction event in a preset database.

[0035] The sending unit is used to receive a request for ...

[0036] In one possible implementation of this application, the filtering unit is further used for:

[0037] Extract the transaction object from the transaction information, and the reason for the transaction failure from the transaction information;

[0038] Determine a target object list containing the transaction object from multiple preset object lists;

[0039] Obtain the target reasons corresponding to the target object list, and select the transaction events whose transaction failure reasons are the same as the target reasons as the order adjustment events.

[0040] In one possible implementation of this application, the generating unit is further configured to:

[0041] The system retrieves the environment information of the preset call terminal.

[0042] Based on the target file format in the environmental information and the transaction information of the order adjustment event, an order adjustment file is generated, and the order adjustment event and the order adjustment file corresponding to the order adjustment event are stored in a preset database.

[0043] In one possible implementation of this application, the generating unit is further configured to:

[0044] Extract the target transaction object from the transaction information of the order adjustment event;

[0045] Obtain the historical order transfer file corresponding to the target transaction object, and the processing result of the historical order transfer file;

[0046] If the number of the first preset results in the processing results is less than a preset number threshold, then the steps of generating a transaction file based on the target file format in the environment information and the transaction information of the transaction event, and storing the transaction event and the transaction file corresponding to the transaction event in a preset database are executed.

[0047] In one possible implementation of this application, the generating unit is further configured to:

[0048] Receive transaction evidence information and obtain the transaction inquiry file to be associated with the transaction evidence information in the preset database;

[0049] If the pre-set evidence information table does not contain the associated evidence information for the transaction file to be associated, then the transaction file to be associated and the transaction evidence information are associated, and the pre-set evidence information table is updated.

[0050] If the preset evidence information table contains the associated evidence information of the transaction order file to be associated, then the preset alarm information is output to the source terminal of the transaction evidence information.

[0051] In one possible implementation of this application, the sending unit is further configured to:

[0052] Accept the request for a service request, obtain the terminal identifier corresponding to the request for a service request, and the target service request file corresponding to the request for a service request;

[0053] If the terminal identifier matches the transaction object corresponding to the target order file, the target order file is decrypted using the key corresponding to the terminal identifier, and the decrypted target order file is sent to the target terminal corresponding to the order request.

[0054] In one possible implementation of this application, the acquiring unit is further configured to:

[0055] Obtain the initial transaction event;

[0056] Based on the transaction location of the initial transaction event, select from the initial transaction events a filterable transaction event with the transaction location as the target location, and obtain the transaction information of the filterable transaction event.

[0057] Thirdly, this application also provides an electronic device, which includes a processor, a memory, and a computer program stored in the memory and executable on the processor. When the processor calls the computer program in the memory, it executes the steps in any of the transaction event order retrieving methods provided in this application.

[0058] Fourthly, this application also provides a storage medium storing a computer program, which, when executed by a processor, implements the steps in any of the transaction event order rescheduling methods provided in this application.

[0059] In summary, the transaction event request method provided in this application includes: obtaining transaction information of transaction events to be screened; filtering the transaction events to be screened according to the transaction failure reasons in the transaction information to obtain request events; generating a request file corresponding to the request event according to the transaction information of the request event, and storing the request event and the request file corresponding to the request event in a preset database; receiving a request request, obtaining the target request event corresponding to the request request, and sending the target request file corresponding to the target request event in the preset database to the target terminal corresponding to the request request.

[0060] As can be seen, in the transaction event request method provided in this application embodiment, the transaction events to be screened can be pre-screened according to the reasons for transaction failure of the transaction events to be screened, and request events can be obtained. Request files corresponding to the request events can be pre-generated and stored. Then, after receiving a request request, there is no need to generate request files in real time. Instead, the preset database can be read directly and the pre-stored target request file can be sent to the target terminal. This saves the time that consumers or card issuers spend waiting for the request file to be generated after initiating a request, and improves the user experience and processing efficiency of the request process. Attached Figure Description

[0061] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0062] Figure 1 This is a schematic diagram illustrating an application scenario of the transaction event order reversal method provided in this application embodiment;

[0063] Figure 2 This is a flowchart illustrating a transaction event order rescheduling method provided in this application embodiment;

[0064] Figure 3 This is another flowchart illustrating the transaction event order reversal method provided in the embodiments of this application;

[0065] Figure 4 This is another flowchart illustrating the transaction event order reversal method provided in the embodiments of this application;

[0066] Figure 5 This is another flowchart illustrating the transaction event order reversal method provided in the embodiments of this application;

[0067] Figure 6 This is a flowchart illustrating an example of updating a preset evidence information table provided in this application embodiment;

[0068] Figure 7 This is a schematic diagram of a process for sending a decrypted target call file to a target terminal, provided in an embodiment of this application.

[0069] Figure 8 This is a schematic diagram of a process for obtaining transaction information of transaction events to be filtered, provided in an embodiment of this application.

[0070] Figure 9 This is a schematic diagram of an embodiment of the transaction event order reconciliation device provided in this application.

[0071] Figure 10 This is a schematic diagram of an embodiment of the electronic device provided in this application. Detailed Implementation

[0072] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0073] In the description of the embodiments of this application, it should be understood that the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, features defined with "first" and "second" may explicitly or implicitly include one or more of the stated features. In the description of the embodiments of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0074] To enable any person skilled in the art to implement and use this application, the following description is provided. In this description, details are set forth for purposes of explanation. It should be understood that those skilled in the art will recognize that this application can be implemented without using these specific details. In other instances, well-known processes will not be described in detail to avoid obscuring the description of the embodiments of this application with unnecessary detail. Therefore, this application is not intended to be limited to the embodiments shown, but is consistent with the broadest scope of the principles and features disclosed in the embodiments of this application.

[0075] This application provides a method, apparatus, electronic device, and storage medium for requesting order details related to a transaction event. The transaction event requesting apparatus can be integrated into an electronic device, which may be a server or a terminal, etc.

[0076] The execution subject of the transaction event order adjustment method in this application embodiment can be the transaction event order adjustment device provided in this application embodiment, or different types of electronic devices such as server equipment, physical host, or user equipment (UE) that integrate the transaction event order adjustment device. The transaction event order adjustment device can be implemented in hardware or software. The UE can be a terminal device such as a smartphone, tablet computer, laptop computer, handheld computer, desktop computer, or personal digital assistant (PDA).

[0077] The electronic device can operate independently or in a cluster.

[0078] See Figure 1 , Figure 1 This is a schematic diagram of a scenario for the transaction event reconciliation system provided in this application embodiment. The transaction event reconciliation system may include an electronic device 101, which integrates a transaction event reconciliation device.

[0079] In addition, such as Figure 1 As shown, the transaction event order adjustment system may also include a memory 102 for storing data, such as text data.

[0080] It should be noted that, Figure 1 The schematic diagram of the transaction event reconciliation system shown is merely an example. The transaction event reconciliation system and scenario described in this application are intended to more clearly illustrate the technical solutions of this application and do not constitute a limitation on the technical solutions provided in this application. As those skilled in the art will know, with the evolution of the transaction event reconciliation system and the emergence of new business scenarios, the technical solutions provided in this invention are also applicable to similar technical problems.

[0081] The following describes the transaction event order adjustment method provided in this application embodiment. In this application embodiment, an electronic device is used as the execution subject. For simplicity and ease of description, the execution subject will be omitted in the subsequent method embodiments. The transaction event order adjustment method includes: obtaining transaction information of transaction events to be screened; filtering the transaction events to be screened according to the transaction failure reasons in the transaction information to obtain order adjustment events; generating an order adjustment file corresponding to the order adjustment event according to the transaction information of the order adjustment event, and storing the order adjustment event and the order adjustment file corresponding to the order adjustment event in a preset database; receiving an order adjustment request, obtaining the target order adjustment event corresponding to the order adjustment request, and sending the target order adjustment file corresponding to the target order adjustment event in the preset database to the target terminal corresponding to the order adjustment request.

[0082] Reference Figure 2 , Figure 2 This is a flowchart illustrating a transaction event order reconciliation method provided in an embodiment of this application. It should be noted that although the logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here. Specifically, the transaction event order reconciliation method may include the following steps 201-204, wherein:

[0083] 201. Obtain transaction information for the transaction events to be filtered.

[0084] A transaction event can refer to an event that occurs after a consumer initiates a transaction using a credit card, debit card, or similar method. For example, a transaction event occurs when a consumer makes a payment using a credit card at a store. In this embodiment, a transaction event can further refer to an event that occurs after a transaction fails. Reasons for transaction failure can include the consumer canceling the transaction, the transaction recipient canceling the transaction, a failed cashback offer, or a duplicate transaction, etc.

[0085] Transaction information for a transaction event can include consumer spending details at the time of the transaction. For example, transaction information may include details such as the consumer's trading partner, transaction amount, and reason for transaction failure.

[0086] The transaction information of the transaction event can be stored in the card organization's back-end database. When a consumer initiates a transaction and a transaction event is generated, the transaction information of the transaction event is sent to the card organization's back-end database. During step 201, the electronic device reads the transaction information of the transaction event to be filtered from the back-end database.

[0087] 202. Based on the reasons for transaction failure in the transaction information, filter the transaction events to be screened to obtain the order adjustment events.

[0088] The reasons for the transaction failure can be found above, and will not be elaborated upon here.

[0089] A transaction request event refers to any of the aforementioned transaction events that might be initiated by either the consumer or the issuing bank. Since there are various reasons for transaction failure, for some reasons, such as the consumer canceling the transaction, the consumer will not be confused about the reason for the failure and will therefore not initiate a transaction request to view the corresponding transaction information. However, for other reasons, such as the counterparty canceling the transaction, the consumer is likely to be confused about the reason for the failure and may therefore initiate a transaction request to view the corresponding transaction information. Transaction events with failures due to these reasons can be designated as transaction request events. Alternatively, for some reasons, such as duplicate transactions, the issuing bank does not need to determine whether to initiate a chargeback based on the corresponding transaction information, and therefore will not initiate a transaction request for these events. For other reasons, such as failed cashback, the issuing bank may need to determine whether to initiate a chargeback based on the corresponding transaction information, and therefore may initiate a transaction request for these events. For ease of understanding, unless otherwise specified, the following text assumes that the transaction request is initiated by the consumer.

[0090] In this context, "transaction request" refers to the process by which a consumer or card issuer requests transaction information from a card organization when they have objections to a transaction.

[0091] As explained above, when filtering transaction events, electronic devices can determine whether the reason for transaction failure is a preset reason. If the reason for transaction failure is a preset reason, the corresponding transaction event can be set as a rescheduling event. For example, the reasons for transaction cancellation or duplicate transaction can be set as preset reasons. If the reason for transaction failure is transaction cancellation or duplicate transaction, the corresponding transaction event will be set as a rescheduling event.

[0092] 203. Based on the transaction information of the order adjustment event, generate the order adjustment file corresponding to the order adjustment event, and store the order adjustment event and the order adjustment file corresponding to the order adjustment event in a preset database.

[0093] A transaction record file can refer to a document file containing transaction information related to a transaction record event. For example, a transaction record file can refer to a POS machine document file containing transaction information related to a transaction record event.

[0094] The default database can refer to the card organization's backend database. After generating the transaction request file corresponding to the transaction request event, the electronic device stores it in the card organization's backend database. Then, when the consumer or the card issuer initiates a transaction request, the electronic device can read the corresponding transaction request file from the card organization's backend database without having to regenerate it. This can save the waiting time for consumers or card issuers and improve the user experience and efficiency of the transaction request process.

[0095] 204. Receive a request for a service request, obtain the target service request event corresponding to the request for a service request, and send the target service request file corresponding to the target service request event in the preset database to the target terminal corresponding to the request for a service request.

[0096] The target terminal can refer to the terminal that sends the order request, which can be a smartphone, personal computer, etc., and this application embodiment does not limit this. For example, when a consumer sends an order request through a personal computer, the target terminal is that personal computer.

[0097] A transaction request is a request generated when a consumer or card issuer initiates a transaction request. For example, when a consumer initiates a transaction request through a webpage, a request is generated the same time they click "Apply for Transaction Request". If the consumer accesses the webpage through a personal computer, after the request is generated, the personal computer sends the request to an electronic device. The electronic device retrieves the target transaction request event corresponding to the request, queries a pre-set database, and sends the target transaction request file corresponding to the target transaction request event in the pre-set database to the personal computer so that the user can confirm the transaction information of the target transaction request event.

[0098] As can be seen, in the transaction event request method provided in this application embodiment, the transaction events to be screened can be pre-screened according to the reasons for transaction failure of the transaction events to be screened, and request events can be obtained. Request files corresponding to the request events can be pre-generated and stored. Therefore, when executing step 204, the electronic device does not need to generate request files in real time, but can directly read the preset database and send the pre-stored target request file to the target terminal. This saves the time that consumers or card issuers spend waiting for request files to be generated after initiating a request, and improves the user experience and processing efficiency of the request process.

[0099] In summary, the transaction event request method provided in this application includes: obtaining transaction information of transaction events to be screened; filtering the transaction events to be screened according to the transaction failure reasons in the transaction information to obtain request events; generating a request file corresponding to the request event according to the transaction information of the request event, and storing the request event and the request file corresponding to the request event in a preset database; receiving a request request, obtaining the target request event corresponding to the request request, and sending the target request file corresponding to the target request event in the preset database to the target terminal corresponding to the request request.

[0100] As can be seen, in the transaction event request method provided in this application embodiment, the transaction events to be screened can be pre-screened according to the reasons for transaction failure of the transaction events to be screened, and request events can be obtained. Request files corresponding to the request events can be pre-generated and stored. Then, after receiving a request request, there is no need to generate request files in real time. Instead, the preset database can be read directly and the pre-stored target request file can be sent to the target terminal. This saves the time that consumers or card issuers spend waiting for the request file to be generated after initiating a request, and improves the user experience and processing efficiency of the request process.

[0101] In some embodiments, the rules for filtering transaction events in step 202 above can vary depending on the different transaction objects, thus improving the accuracy of filtering and avoiding setting transaction events with low probability of initiating order requests as order request events, which would waste computing resources and lead to data redundancy in the preset database. (Reference) Figure 3 At this point, the step "based on the transaction failure reasons in the transaction information, filter the transaction events to be screened to obtain the order adjustment events" includes:

[0102] 301. Extract the transaction object from the transaction information and the reason for the transaction failure from the transaction information.

[0103] The transaction object can refer to the merchant object when a consumer makes a transaction. For example, after a consumer makes a payment to a merchant using a credit card, the transaction object in the generated transaction event is that merchant.

[0104] The reasons for the transaction failure can be found above, and will not be elaborated upon here.

[0105] 302. Determine a list of target objects containing the transaction object from multiple preset object lists.

[0106] The preset target list refers to a list of merchants. For example, the preset target list may include a whitelist and a blacklist. The whitelist includes merchants without malicious transaction records such as malicious order cancellations or malicious order boosting, while the blacklist includes merchants with such records. Therefore, the purpose of step 302 is to determine whether the transaction target has malicious transaction records such as malicious order cancellations or malicious order boosting. For example, if the whitelist includes merchants A and B, and the blacklist includes merchants C and D, then when the transaction target is merchant A, the target list is the whitelist, and the electronic device can determine that the transaction target does not have malicious transaction records such as malicious order cancellations or malicious order boosting. However, when the transaction target is merchant C, the target list is the blacklist, and the electronic device can determine that the transaction target has malicious transaction records such as malicious order cancellations or malicious order boosting.

[0107] 303. Obtain the target reasons corresponding to the target object list, and take the transaction events that are to be screened with the same transaction failure reason as the target reason as the order adjustment event.

[0108] The target reason refers to the reason used to filter the transaction events to be filtered. If the reason for the transaction failure is the same as the target reason, it means that the transaction event to be filtered is an event that may be initiated by the consumer or the card issuer for a transaction request. Therefore, the electronic device can use the transaction event to be filtered as a transaction request event.

[0109] For example, when the preset target list includes a whitelist and a blacklist, reasons related to the transaction target, such as "transaction target cancels transaction," can be used as reasons corresponding to the blacklist, while reasons unrelated to the transaction target, such as "transaction duplicated," can be used as reasons corresponding to the whitelist. If the target target list is a whitelist, the target reason can be reasons related to the transaction target, such as "transaction target cancels transaction." If the transaction failure reason is the same as the target reason, the transaction event to be filtered will be used as a request event. If the target target list is a blacklist, the target reason can be reasons unrelated to the transaction target, such as "transaction duplicated," and if the transaction failure reason is the same as the target reason, the transaction event to be filtered will be used as a request event.

[0110] The list of each preset object and the corresponding reason can be stored in the card organization's backend database. When executing steps 301-303, the electronic device reads the list of each preset object and the corresponding reason from the backend database, then determines the list of target objects from the list of preset objects, and selects the order adjustment event from the transaction events to be screened according to the target reason corresponding to the list of target objects.

[0111] In some embodiments, when generating a request form, the electronic device may also determine the format of the request form based on the storage format of the card organization's backend database. (See reference) Figure 4 At this point, the step "based on the transaction information of the order adjustment event, generate the order adjustment file corresponding to the order adjustment event, and store the order adjustment event and the order adjustment file corresponding to the order adjustment event in a preset database" includes:

[0112] 401. Query the environment information of the preset call terminal.

[0113] A request terminal refers to a terminal capable of issuing request requests. For example, a request terminal can include smartphones, personal computers, and any other terminal capable of issuing request requests. It is understood that the target terminal described above is one type of request terminal.

[0114] The environmental information of the order request terminal may include the system version supported by the order request terminal, the output format when the order request terminal outputs the order request file, etc. The environmental information of the order request terminal can also be stored in the card organization's backend database. When executing step 401, the electronic device reads the environmental information of the order request terminal from the backend database.

[0115] 402. Based on the target file format in the environmental information and the transaction information of the order adjustment event, generate an order adjustment file, and store the order adjustment event and the order adjustment file corresponding to the order adjustment event in a preset database.

[0116] The target file format refers to the output format of the request form file when the request form terminal outputs it. For example, if the request form terminal outputs the request form file using the Portable Document Format (PDF), then the target file format can be PDF. As another example, if the request form terminal outputs the request form file using the Portable Network Graphics (PNG) format, then the target file format can be PNG. It's understandable that if the target file format is PDF, then the generated request form file will be in PDF format; if the target file format is PNG, then the generated request form file will be in PNG format.

[0117] In some embodiments, before executing step 402, the electronic device may also determine, based on the historical order processing results of the target transaction object, whether the transaction failure reason of the order request event is due to an individual reason of the target transaction object. If the transaction failure reason of the order request event is due to an individual reason of the target transaction object, it is determined that the possibility of subsequent order request requests is low, and no further order request file is generated. (Reference) Figure 5 At this point, before the step "generate a request file based on the target file format in the environment information and the transaction information of the request event, and store the request event and the request file corresponding to the request event in a preset database", the method further includes:

[0118] 501. Extract the target transaction object from the transaction information of the order adjustment event.

[0119] The description of the target transaction object can be found above, and will not be repeated here.

[0120] 502. Obtain the historical transaction file corresponding to the target transaction object, and the processing result of the historical transaction file.

[0121] The historical transaction file corresponding to the target transaction object refers to the generated transaction file containing transaction information where the transaction object is the target transaction object.

[0122] Historical call records can also be stored in the aforementioned preset database.

[0123] The processing result of historical transaction records refers to the subsequent processing taken after a consumer or issuing bank initiates a transaction request and receives the historical transaction record. The processing result of a single historical transaction record can be one of several outcomes, such as a chargeback or a re-transaction. For example, if a consumer receives a historical transaction record and determines that the transaction event corresponding to that record does not pose a risk, they can initiate another transaction event. In this case, the processing result for that historical transaction record can be a re-transaction.

[0124] 503. If the number of the first preset results in the processing results is less than the preset number threshold, then the step of generating a transfer file according to the target file format in the environment information and the transaction information of the transfer event, and storing the transfer event and the transfer file corresponding to the transfer event in the preset database is executed.

[0125] The first preset result can be a result that determines the reason for the transaction failure of the order request event is due to an individual reason of the target transaction object. For example, the first preset result can be the aforementioned "retransaction", because when the reason for the transaction failure of the order request event is due to an individual reason such as a malfunction in the payment system used by the target transaction object, consumers usually do not consider the transaction to be risky, so they will initiate the transaction again. At this time, even if the transaction fails, the probability of the consumer initiating an order request is relatively low.

[0126] In this embodiment, the number of first preset results is used to determine whether the transaction failure of the order request event is due to an individual cause of the target transaction object. For example, if the first preset result is "re-transaction" as mentioned above, a large number of first preset results indicates that the consumer has initiated the transaction many times, and the transaction failure of the order request event is due to an individual cause such as a malfunction in the payment system used by the target transaction object. If the number of first preset results is small, it indicates that the transaction failure of the order request event is not due to an individual cause of the target transaction object.

[0127] A preset quantity threshold is used to determine the magnitude of the first preset result, and can be set according to actual scenario requirements. When the number of the first preset results is less than the preset quantity threshold, it can be determined that the transaction failure of the order request event is not due to an individual reason of the target transaction object. Therefore, the steps of generating an order request file based on the target file format in the environment information and the transaction information of the order request event, and storing the order request event and its corresponding order request file in the preset database, can be executed. When the number of the first preset results is greater than or equal to the preset quantity threshold, it can be determined that the transaction failure of the order request event is due to an individual reason of the target transaction object. In this case, it can be determined that the likelihood of the consumer initiating a subsequent order request is low. To avoid redundancy in the preset database and save computing power, an order request file may not be generated.

[0128] After obtaining the order confirmation document, consumers can upload supporting evidence related to the order confirmation incident to protect their rights. To save time in manually associating evidence with the order confirmation document, in some embodiments, the electronic device can automatically associate the uploaded evidence with the corresponding order confirmation document and issue an alarm when the consumer uploads evidence repeatedly. (Reference) Figure 6 At this point, after the step "generate a request file corresponding to the request event based on the transaction information of the request event, and store the request event and the request file corresponding to the request event in a preset database", the method further includes:

[0129] 601. Receive transaction evidence information and obtain the transaction file to be associated corresponding to the transaction evidence information in the preset database.

[0130] Transaction evidence information refers to the information contained in evidence files uploaded by consumers. For example, if a consumer obtains a transaction request file containing the reason for transaction failure as "the consumer canceled the transaction," and disagrees with the reason for the failure, they can upload their own payment receipts or other evidence files to prove that they did not cancel the transaction. In this case, the transaction evidence information is the information contained in that evidence file. After obtaining the evidence file uploaded by the user, the electronic device can use the information contained in the evidence file as transaction evidence information and treat the transaction request file as the corresponding request file to be associated with the transaction evidence information.

[0131] 602A. If the pre-set evidence information table does not contain the associated evidence information of the transaction file to be associated, then the transaction file to be associated and the transaction evidence information are associated, and the pre-set evidence information table is updated.

[0132] The preset evidence information table can be a data table used to store evidence files. For example, the card organization's backend database can be divided into multiple storage blocks. Some of these storage blocks can be used to store inquiry files, while the other storage blocks can be used to store evidence files. In this case, the other storage blocks constitute the preset evidence information table.

[0133] The associated evidence information of the pending order file refers to the evidence file that has been associated with the pending order file in the preset evidence information table. That is, step 602A refers to the situation where the consumer uploads the evidence file associated with the pending order file for the first time. At this time, the electronic device can associate the pending order file with the transaction evidence information and update the preset evidence information table. After the update, if the preset evidence information table is queried again, the associated evidence information of the pending order file will be the transaction evidence information contained in the evidence file uploaded by the consumer.

[0134] 602B. If the preset evidence information table contains the associated evidence information of the transaction file to be associated, then the preset alarm information is output to the source terminal of the transaction evidence information.

[0135] The source terminal refers to the terminal that uploads transaction evidence information, which can be a smartphone, personal computer, etc. This application embodiment does not limit this.

[0136] Understandably, step 602B refers to the situation where the consumer uploads the evidence file associated with the transaction order file for the first time, i.e., the consumer uploads the evidence file repeatedly. In this case, the electronic device can send a preset alarm message, such as "Do not upload repeatedly", to the terminal that is the source of the transaction evidence information.

[0137] In some embodiments, to protect consumer privacy, the order request file can be encrypted, and the decrypted order request file will only be sent to the terminal that initiated the order request if the terminal matching the consumer corresponding to the order request file is used. (See reference) Figure 7 At this point, the step "receive a request for a service call and send the target service call file corresponding to the request for a service call in the service call file to the target terminal corresponding to the request for a service call" includes:

[0138] 701. Accept the request for a service request, and obtain the target terminal identifier corresponding to the request for a service request, as well as the target service request file corresponding to the request for a service request.

[0139] The explanation of the order request can be found above, and will not be repeated here.

[0140] The target terminal identifier corresponding to the request for a call can refer to the identifier of the target terminal that issued the request. For an explanation of the target terminal, please refer to the above text. Detailed explanation will not be repeated here.

[0141] 702. If the target terminal identifier matches the consumer corresponding to the target request file, the target request file is decrypted using the key corresponding to the target terminal identifier, and the decrypted target request file is sent to the target terminal corresponding to the request.

[0142] If the target terminal identifier matches the consumer corresponding to the target request file, it means the request was sent by the consumer corresponding to the target request file. In this case, sending the decrypted target request file to the target terminal will not leak the consumer's privacy, so the decrypted target request file can be sent to the target terminal corresponding to the request. However, if the target terminal identifier does not match the consumer corresponding to the target request file, it means the request was not sent by the consumer corresponding to the target request file. In this case, sending the decrypted target request file to the target terminal may leak the consumer's privacy. Therefore, the electronic device should not send the decrypted target request file to the target terminal. Alternatively, the electronic device can also perform facial recognition, fingerprint recognition, or other verification through the target terminal to further confirm whether the request was sent by the consumer corresponding to the target request file.

[0143] It should be noted that in this embodiment of the application, the request file needs to be encrypted when generating the request file. The encryption key can be preset by the consumer and associated with the terminal it uses. When executing step 702, the electronic device can decrypt the request file according to the key corresponding to the terminal identifier.

[0144] Because electronic devices obtain different transaction information when acquiring transaction events depending on the transaction location, the information for some transaction events occurring at certain locations may not include the reason for transaction failure. Therefore, when acquiring transaction information for events to be filtered, electronic devices can select transaction events whose corresponding transaction location is at the target location and whose transaction information includes the reason for transaction failure as the events to be filtered. (Reference) Figure 8 At this point, the step "obtain transaction information for the transaction events to be filtered" includes:

[0145] 801. Obtain the initial transaction event.

[0146] The initial transaction event can refer to all transaction events that have been generated. For example, the initial transaction event can refer to all transaction events contained in the aforementioned preset database.

[0147] 802. Based on the transaction location of the initial transaction event, select from the initial transaction events a target transaction event and obtain the transaction information of the target transaction event.

[0148] For example, the target location can refer to a location outside the country where the electronic device is located. For instance, all locations outside the country where the electronic device is located can be set as target locations. If the transaction location of the initial transaction event is outside the country where the electronic device is located, then the transaction location of the initial transaction event is determined to be the target location, and the initial transaction event is selected as a transaction event to be filtered.

[0149] To better implement the transaction event order reconciliation method in the embodiments of this application, based on the transaction event order reconciliation method, the embodiments of this application also provide a transaction event order reconciliation device, such as... Figure 9 The diagram shown is a structural schematic of one embodiment of the transaction event order adjustment device in this application. The transaction event order adjustment device 900 includes:

[0150] The acquisition unit 901 is used to acquire transaction information of the transaction events to be filtered;

[0151] The filtering unit 902 is used to filter the transaction events to be filtered according to the transaction failure reasons in the transaction information to obtain the order adjustment events;

[0152] The generation unit 903 is used to generate a transaction file corresponding to the transaction event based on the transaction information of the transaction event, and to store the transaction event and the transaction file corresponding to the transaction event in a preset database.

[0153] The sending unit 904 is used to receive a request for ...

[0154] In one possible implementation of this application, the filtering unit 902 is further configured to:

[0155] Extract the transaction object from the transaction information, and the reason for the transaction failure from the transaction information;

[0156] Determine a target object list containing the transaction object from multiple preset object lists;

[0157] Obtain the target reasons corresponding to the target object list, and select the transaction events whose transaction failure reasons are the same as the target reasons as the order adjustment events.

[0158] In one possible implementation of this application, the generating unit 903 is further configured to:

[0159] The system retrieves the environment information of the preset call terminal.

[0160] Based on the target file format in the environmental information and the transaction information of the order adjustment event, an order adjustment file is generated, and the order adjustment event and the order adjustment file corresponding to the order adjustment event are stored in a preset database.

[0161] In one possible implementation of this application, the generating unit 903 is further configured to:

[0162] Extract the target transaction object from the transaction information of the order adjustment event;

[0163] Obtain the historical order transfer file corresponding to the target transaction object, and the processing result of the historical order transfer file;

[0164] If the number of the first preset results in the processing results is less than a preset number threshold, then the steps of generating a transaction file based on the target file format in the environment information and the transaction information of the transaction event, and storing the transaction event and the transaction file corresponding to the transaction event in a preset database are executed.

[0165] In one possible implementation of this application, the generating unit 903 is further configured to:

[0166] Receive transaction evidence information and obtain the transaction inquiry file to be associated with the transaction evidence information in the preset database;

[0167] If the pre-set evidence information table does not contain the associated evidence information for the transaction file to be associated, then the transaction file to be associated and the transaction evidence information are associated, and the pre-set evidence information table is updated.

[0168] If the preset evidence information table contains the associated evidence information of the transaction order file to be associated, then the preset alarm information is output to the source terminal of the transaction evidence information.

[0169] In one possible implementation of this application, the sending unit 904 is further configured to:

[0170] Accept the request for a service request, obtain the terminal identifier corresponding to the request for a service request, and the target service request file corresponding to the request for a service request;

[0171] If the terminal identifier matches the transaction object corresponding to the target order file, the target order file is decrypted using the key corresponding to the terminal identifier, and the decrypted target order file is sent to the target terminal corresponding to the order request.

[0172] In one possible implementation of this application, the acquiring unit 901 is further configured to:

[0173] Obtain the initial transaction event;

[0174] Based on the transaction location of the initial transaction event, select from the initial transaction events a filterable transaction event with the transaction location as the target location, and obtain the transaction information of the filterable transaction event.

[0175] In practice, each of the above units can be implemented as an independent entity or can be arbitrarily combined to be implemented as the same or several entities. For the specific implementation of each of the above units, please refer to the previous method embodiments, which will not be repeated here.

[0176] Since the transaction event order adjustment device can execute the steps in the transaction event order adjustment method in any embodiment, it can achieve the beneficial effects that the transaction event order adjustment method in any embodiment of this application can achieve, as detailed in the preceding description, and will not be repeated here.

[0177] Furthermore, to better implement the transaction event order reconciliation method in the embodiments of this application, based on the transaction event order reconciliation method, the embodiments of this application also provide an electronic device, see below. Figure 10 , Figure 10This illustration shows a structural diagram of an electronic device according to an embodiment of this application. Specifically, the electronic device provided in this embodiment includes a processor 1001. The processor 1001 executes a computer program stored in a memory 1002 to implement each step of the transaction event order reversal method in any embodiment; or, the processor 1001 executes a computer program stored in a memory 1002 to implement, for example... Figure 9 The functions of each module in the corresponding embodiment.

[0178] For example, a computer program may be divided into one or more modules / units, one or more of which are stored in memory 1002 and executed by processor 1001 to complete the embodiments of this application. One or more modules / units may be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program in a computer device.

[0179] The electronic device may include, but is not limited to, processor 1001 and memory 1002. Those skilled in the art will understand that the illustrations are merely examples of an electronic device and do not constitute a limitation on the electronic device. It may include more or fewer components than illustrated, or combine certain components, or use different components.

[0180] Processor 1001 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor. The processor is the control center of the electronic device, connecting various parts of the electronic device through various interfaces and lines.

[0181] The memory 1002 can be used to store computer programs and / or modules. 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 by calling the data stored in the memory 1002. The memory 1002 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device (such as audio data, video data, etc.). In addition, the memory may include high-speed random access memory, and may also include non-volatile memory, such as hard disk, RAM, plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0182] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the transaction event order adjustment device, electronic device and its corresponding units described above can be referred to the description of the transaction event order adjustment method in any embodiment, and will not be repeated here.

[0183] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be accomplished by instructions, or by instructions controlling related hardware. These instructions can be stored in a storage medium and loaded and executed by a processor.

[0184] Therefore, this application provides a storage medium storing a computer program. When the computer program is executed by a processor, it performs the steps in the transaction event order rescheduling method in any embodiment of this application. For specific operations, please refer to the description of the transaction event order rescheduling method in any embodiment, which will not be repeated here.

[0185] The storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0186] Since the instructions stored in the storage medium can execute the steps in the transaction event order rescheduling method in any embodiment of this application, the beneficial effects that the transaction event order rescheduling method in any embodiment of this application can achieve can be realized, as detailed in the preceding description, and will not be repeated here.

[0187] The foregoing has provided a detailed description of a transaction event order reconciliation method, apparatus, storage medium, and electronic device provided in the embodiments of this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method for adjusting orders based on transaction events, characterized in that, include: Obtain transaction information for the transaction events to be filtered, where a transaction event refers to an event that occurs after a consumer initiates a transaction through at least one of a credit card or debit card; Based on the reasons for transaction failure in the transaction information, the transaction events to be screened are filtered to obtain the order adjustment events; Based on the transaction information of the order adjustment event, an order adjustment file corresponding to the order adjustment event is generated, and the order adjustment event and the order adjustment file corresponding to the order adjustment event are stored in a preset database, wherein the preset database refers to the card organization's back-end database; Receive a request for a call, obtain the target call event corresponding to the request, and send the target call file corresponding to the target call event in the preset database to the target terminal corresponding to the request. The step of filtering the transaction events to be screened based on the transaction failure reasons in the transaction information to obtain the order rescheduling events includes: Extract the transaction object from the transaction information, and the reason for the transaction failure from the transaction information; Determine a target object list containing the transaction object from multiple preset object lists; Obtain the target reasons corresponding to the target object list, and select the transaction events whose transaction failure reasons are the same as the target reasons as the order adjustment events; The multiple preset object lists include whitelists and blacklists; The step of generating a request file corresponding to the request event based on the transaction information of the request event, and storing the request event and the request file corresponding to the request event in a preset database includes: The system retrieves the environment information of the preset call terminal. Extract the target transaction object from the transaction information of the order adjustment event; Obtain the historical order transfer file corresponding to the target transaction object, and the processing result of the historical order transfer file; If the number of the first preset results in the processing results is less than the preset number threshold, a transfer order file is generated according to the target file format in the environmental information and the transaction information of the transfer order event, and the transfer order event and the transfer order file corresponding to the transfer order event are stored in the preset database.

2. The transaction event order reversal method according to claim 1, characterized in that, After generating a request file corresponding to the request event based on the transaction information of the request event, and storing the request event and the request file corresponding to the request event in a preset database, the method further includes: Receive transaction evidence information and obtain the transaction inquiry file to be associated with the transaction evidence information in the preset database; If the pre-set evidence information table does not contain the associated evidence information for the transaction file to be associated, then the transaction file to be associated and the transaction evidence information are associated, and the pre-set evidence information table is updated. If the preset evidence information table contains the associated evidence information of the transaction order file to be associated, then the preset alarm information is output to the source terminal of the transaction evidence information.

3. The transaction event order reversal method according to claim 1, characterized in that, The steps of receiving a request for a service call, obtaining the target service call event corresponding to the request for a service call, and sending the target service call file corresponding to the target service call event in the preset database to the target terminal corresponding to the request for a service call include: Accept the request for a service request, obtain the target terminal identifier corresponding to the request for a service request, and the target service request file corresponding to the request for a service request; If the target terminal identifier matches the consumer corresponding to the target request file, the target request file is decrypted using the key corresponding to the target terminal identifier, and the decrypted target request file is sent to the target terminal corresponding to the request.

4. The transaction event order reversal method according to any one of claims 1-3, characterized in that, The process of obtaining transaction information for the transaction events to be filtered includes: Obtain the initial transaction event; Based on the transaction location of the initial transaction event, select from the initial transaction events a filterable transaction event with the transaction location as the target location, and obtain the transaction information of the filterable transaction event.

5. A transaction event order reconciliation device, characterized in that, include: The acquisition unit is used to acquire transaction information of transaction events to be filtered. A transaction event refers to an event that occurs after a consumer initiates a transaction through at least one of a credit card or a debit card. The filtering unit is used to filter the transaction events to be filtered according to the reasons for transaction failure in the transaction information to obtain the order adjustment events; The generation unit is used to generate a transaction file corresponding to the transaction event based on the transaction information of the transaction event, and to store the transaction event and the transaction file corresponding to the transaction event in a preset database. The sending unit is used to receive a request for ... target request for a request for a request for a request for a target request for a request for a request for a request for a request for a request for a request for a request for a request for a request for a request for a request for a request for a request for a The filtering unit is further used for: Extract the transaction object from the transaction information, and the reason for the transaction failure from the transaction information; Determine a target object list containing the transaction object from multiple preset object lists; Obtain the target reasons corresponding to the target object list, and select the transaction events whose transaction failure reasons are the same as the target reasons as the order adjustment events; The multiple preset object lists include whitelists and blacklists; The generation unit is also used for: The system retrieves the environment information of the preset call terminal. Extract the target transaction object from the transaction information of the order adjustment event; Obtain the historical order transfer file corresponding to the target transaction object, and the processing result of the historical order transfer file; If the number of the first preset results in the processing results is less than the preset number threshold, a transfer order file is generated according to the target file format in the environmental information and the transaction information of the transfer order event, and the transfer order event and the transfer order file corresponding to the transfer order event are stored in the preset database.

6. An electronic device, characterized in that, The electronic device includes a processor, a memory, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps in the transaction event rescheduling method as described in any one of claims 1 to 4.

7. A storage medium, characterized in that, The storage medium stores a computer program, which, when executed by a processor, implements the steps of the transaction event order adjustment method according to any one of claims 1 to 4.

Images