Detailed Description
In order to make those skilled in the art better understand the technical solutions in the embodiments of the present specification, the technical solutions in the embodiments of the present specification will be described in detail below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all the embodiments. All other embodiments that can be derived by one of ordinary skill in the art from the embodiments given herein are intended to be within the scope of protection.
The user of the bank or other financial institution, i.e. the actual cardholder or account holder, may issue a refusal payment to the financial institution, i.e. apply for refusal payment of a certain transaction amount on the bill, within a certain period of time after payment of the amount in the bank card or payment bank account (specifically subject to the specific provisions of the bank card organization, bank or other cooperating institution).
For example, if the bank card or the payment account of the user is stolen, the user can apply for refusing the transaction money correspondingly generated; for another example, after the user purchases a certain commodity with the bank card or the payment account, if the commodity provided by the merchant is considered to be inconsistent with the description, the user can apply for returning the goods and reject the payment of the transaction order.
After the user applies for the refusal payment, the acquirer or the financial institution generates the refusal payment task corresponding to the transaction order.
The present specification provides a method for processing a task refusal, which, as shown in fig. 1, may include the following steps:
s101, acquiring data of a task to be processed for refusing payment;
s102, checking whether the obtained data contains preset characteristics or not;
when the refusal payment task is processed, various judgments are carried out on the refusal payment applied by the user according to the corresponding transaction order. For example, whether the amount of refusal payment applied by the user is reasonable is judged; judging the responsible party of the generated loss, wherein if the user is stolen to swipe a bank card or an account due to the imperfect wind control measures of the financial institution, the responsible party is generally the financial institution, and if the merchant provides the commodities which are not in accordance with the description, the responsible party is generally the merchant; and so on.
Correspondingly, several features are generated in the pending task rejection data, such as: task identification (such as task number), decision attribute, application rejection amount, decision winning amount, amount undertaking party, task current state, etc.
When processing the refusal task, it needs to check whether the data of the refusal task is complete, i.e. whether the features are lacked. If the data is verified to lack one or more characteristics, corresponding prompt information can be displayed, such as information that the task number cannot be null, and the like, so as to be supplemented by an operator. In addition, some features can be automatically generated according to the existing features, so that the data is complete.
For example, some trade orders are merged orders generated by merging payments of multiple sub-orders, and the user may apply for rejecting only a part of the sub-orders, so that the rejection task data may further include sub-task identifiers (such as sub-task numbers). When checking whether the obtained data contains preset characteristics, whether a transaction order corresponding to the refusal payment task is a combined order of a plurality of sub-orders or not can be determined; and if so, checking whether the obtained data contains the subtask identification.
If the subtask identity is not included, the feature may be automatically generated and a feature value calculated. Specifically, a subtask identifier may be generated, and a value of a preset feature corresponding to the combined order in the obtained data is extracted; and calculating the value of the preset characteristic corresponding to the sub-order according to the extracted characteristic value and the transaction amount relation between the sub-order and the combined order.
After supplementing the modified data, the verification may be performed again until it is determined that the preset feature is no longer absent from the data, and the verification of other aspects may continue.
S103, if yes, extracting values of preset features in the obtained data, and checking whether the corresponding relation between the extracted feature values is correct and whether the corresponding relation is consistent with the feature values in the local data;
in addition to the integrity of the features, the values of the features in the data also need to satisfy the checking rules of correct correspondence, consistency with local data, and the like.
As described above, the data of the rejection task may include characteristics such as the determination attribute, the application rejection amount, the determination winning amount, and the like, and it may be checked whether the correspondence between these characteristic values is correct.
In this embodiment of the present specification, after extracting a value of a preset feature in the obtained data, a value of a determination attribute may be determined first, and if the value of the determination attribute is a full-amount victory, that is, it is determined that the requested rejected money amounts are both victory, it is checked whether the victory money amount is greater than 0, equal to the requested rejected money amount, or the like, and it is checked whether the loser money amount is equal to 0; if the value of the attribute is judged to be full, namely the applied rejection amount is judged to be both the rejection, whether the rejection amount is larger than 0, whether the rejection amount is equal to the applied rejection amount and the like is checked and judged, and whether the winning amount is equal to 0 is checked and judged; if the value of the judgment attribute is partial victory or partial victory, whether the amount of the victory or the amount of the victory is greater than 0 is checked; in addition, for the foregoing types of cases, it is possible to check whether the sum of the determination winning amount and the determination winning amount is equal to the application rejection amount.
As described above, the data of the task refusing may include features such as a task identifier and a subtask identifier, and the task and each task of the task may be identified in a correlated manner, so that it may be checked whether the corresponding relationship of feature values of the features such as the task identifier and the subtask identifier is correct, and it may be checked whether the subtask belongs to the task.
In addition, if a task comprises a plurality of subtasks, the sum of the values of the judgment winning amount and the judgment winning amount of each subtask can be checked to determine whether the sum is equal to the judgment winning amount and the judgment winning amount of the task. In addition, for the transaction related to multiple currencies, the numerical result of the exchange rate conversion may be influenced by the floating of the exchange rate, so when the corresponding relationship between the money values is judged, the calculation can be performed according to the exchange rate during the transaction or the current real-time exchange rate according to the preset rule, or whether the corresponding relationship between the values is in the preset range can be checked, and the range can be preset according to the floating range of the exchange rate.
If the corresponding relation of each characteristic value of the data is determined to be incorrect through inspection, corresponding prompt information can be displayed for an operator to modify. Of course, the characteristic value with error can be automatically judged and corrected.
The processing of the rejection task may include multiple processing stages, each processing stage may generate corresponding data to be stored locally, and when the rejection task data is checked, it is also necessary to check whether the values of some features are the same as the stored data feature values.
For example, after the repudiation task is generated, the task identifier of the task is stored locally, so that whether the task identifier and the subtask identifier are stored locally can be checked, and whether the task identifier and the subtask identifier are consistent with the characteristic value of local data or not is determined; for another example, whether the characteristic values of the application refusal payment amount, the amount undertaker and the like are consistent with the characteristic values of the local data can be checked; and so on.
If the characteristic values of the data are determined to be inconsistent with the local data through inspection, corresponding prompt information can be displayed for an operator to modify; and the inconsistent characteristic values can be automatically judged and corrected.
In this embodiment of the present specification, when it is checked that the value of the preset feature in the extracted data is inconsistent with the feature value of the local data, if the value of the feature of a certain amount is inconsistent, it may be further determined whether the transaction order corresponding to the rejection task is a multi-currency transaction; if so, the money amount may be changed due to the floating of the exchange rate, and the real-time exchange rate data (the transaction time or the current real-time exchange rate is called according to the preset calculation rule) may be called to recalculate the value of the preset feature in the obtained data. After recalculation, the data can be directly corrected according to the result, and can also be displayed for reference of an operator.
S104, if yes, determining that the refusal payment task data to be processed passes the inspection, and generating a refusal payment judgment result according to the extracted values of the application refusal payment amount, the judgment winning amount and the judgment winning amount;
if the check results in S102 and S103 are both yes, the data of the pending repudiation task can be determined to pass the check.
For the same order, multiple refusal payment judgments may exist according to the feedback of the user or the financial institution; or if the order is a combined order, corresponding payment refusal judgment may exist for each sub-order respectively; alternatively, if multiple currencies are designed for the order, other intermediate links may be involved in processing the rejection task.
Therefore, after the data of the refusal payment task passes the verification, the result of the refusal payment judgment of this time needs to be generated by integrating other judgment conditions of the same order according to the judgment condition of this time.
And S105, processing the transaction order corresponding to the payment refusal task according to the payment refusal judgment result.
In this embodiment of the present specification, the processing status of the tendered task and the corresponding transaction order may be updated according to the tendered decision result.
As described above, for the same order, there may be multiple refusals, subtasks corresponding to multiple sub-orders, or other intermediate links, and the state may be updated correspondingly according to the refusal payment determination result, for example, the current refusal payment state in the multiple refusals is updated to "completion determination".
In addition, after the user applies for rejecting payment in a certain transaction order, the order may be frozen, and after the rejection task generates a rejection judgment result, the order may be thawed, so that feedback such as refund is performed on the user according to the rejection judgment result.
The method for processing a rejected task provided in this specification will be described below with reference to a more specific example.
Assuming that the user uses the payment treasure to pay when shopping off line, the user payment bank acts as an issuer, and the merchant collects the money and bank acts as an acquirer. The transaction order comprises a plurality of commodities, namely a combined order, and then the user finds that 1 commodity is inconsistent with the description and requires a goods returning and chargeback process, so that the user applies for rejecting payment of part of the amount of the money to an issuer.
After the issuer receives the application, the issuing bank checks the transaction by the bank flow, and sends a payment refusing request to the acquirer, which freezes the transaction and sends the transaction to the payment treasured for payment refusing judgment. The payment treasures correspondingly generate a repudiation task and subtasks, carry out judgment processing such as repudiation amount and a undertaker, and carry out inspection after obtaining corresponding data.
FIG. 2 is a flow chart illustrating inspection of task declination data.
The checking process comprises whether the characteristics of the data are complete, whether the corresponding relation of each characteristic value is correct and whether the data are consistent with the local data. If the data is detected to be not in accordance with the conditions, an operator can be prompted to confirm the abnormal reason and modify the data, and then the data can be detected again; if the data is not checked to be not in accordance with the above condition, the data passes the check, and the subsequent processing procedure can be performed.
It should be understood that fig. 2 is only an illustration of the inspection flow, and the inspection steps may be executed in other sequences and in serial-parallel manners, and fig. 2 should not be construed as limiting the embodiment of the present disclosure.
After the data of the refusal payment task passes the inspection, JSON statements can be constructed and local data can be updated according to the characteristics of the money amount, the undertaker and the like in the data, and the state of the refusal payment task can be updated. And the refusal payment judgment result can be fed back to the acquiring bank, if the acquiring bank agrees to the judgment result of the refusal payment task, the transaction order is unfrozen, and the payment is refunded to the user according to the winning amount.
Therefore, by applying the scheme, the completeness, the correctness, the consistency and the like of the data of the refused payment task to be processed can be automatically checked, and the refused payment task is advanced according to the checked data, so that the labor and the time are saved, and the efficiency and the accuracy of the processing process are improved.
Corresponding to the above method embodiment, an embodiment of the present specification further provides a task refusal processing apparatus, and referring to fig. 3, the apparatus may include:
the data acquisition module 110 is used for acquiring the data of the pending repudiation task;
a feature checking module 120, configured to check whether the obtained data includes a preset feature; the preset features at least include: applying for a refusal payment amount, judging a victory sum and judging a loser sum of the refusal payment task; if so, extracting the values of the preset features in the obtained data, and checking whether the corresponding relation among the extracted feature values is correct and whether the extracted feature values are consistent with the feature values in the local data;
a result generating module 130, configured to generate a rejection determination result according to the extracted values of the application rejection amount, the determination winning amount, and the determination winning amount under the condition that it is determined that the to-be-processed rejection task data passes the inspection;
and the order processing module 140 is configured to process the transaction order corresponding to the rejection task according to the rejection determination result.
In a specific embodiment provided in this specification, the preset feature may further include: identifying a subtask;
the feature verification module 120 may be specifically configured to:
determining whether the transaction order corresponding to the refusing task is a combined order of a plurality of sub-orders;
and if so, checking whether the obtained data contains the subtask identification.
In an embodiment provided in this specification, the apparatus may further include a first modification module, which may be specifically configured to:
under the condition that the data obtained by verification does not contain the subtask identification, generating the subtask identification, and extracting the value of the preset characteristic corresponding to the combined order in the obtained data;
and calculating the value of the preset characteristic corresponding to the sub-order according to the extracted characteristic value and the transaction amount relation between the sub-order and the combined order.
In an embodiment provided in this specification, the apparatus may further include a second modification module, which may be specifically configured to:
under the condition that the extracted characteristic values are not consistent with the characteristic values in the local data, determining whether the transaction order corresponding to the refusing task is a multi-currency transaction or not;
if yes, the exchange rate data is called to recalculate the value of the preset characteristic in the obtained data.
In a specific embodiment provided in this specification, the order processing module 140 may be specifically configured to:
and updating the processing states of the refusal payment task and the corresponding transaction order according to the refusal payment judgment result.
The implementation process of the functions and actions of each module in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.
The embodiments of the present specification further provide a computer device, which at least includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method for processing the task refusal when executing the program. The method at least comprises the following steps:
the data acquisition module is used for acquiring the data of the to-be-processed task refusing;
the characteristic checking module is used for checking whether the obtained data contains preset characteristics or not; the preset features at least include: applying for a refusal payment amount, judging a victory sum and judging a loser sum of the refusal payment task; if so, extracting the values of the preset features in the obtained data, and checking whether the corresponding relation among the extracted feature values is correct and whether the extracted feature values are consistent with the feature values in the local data;
the result generation module is used for generating a refusal payment judgment result according to the extracted values of the application refusal payment amount, the judgment winning amount and the judgment winning amount under the condition that the refusal payment task data to be processed pass the inspection;
and the order processing module is used for processing the transaction order corresponding to the payment refusing task according to the payment refusing judgment result.
Fig. 4 is a schematic diagram illustrating a more specific hardware structure of a computing device according to an embodiment of the present disclosure, where the computing device may include: a processor 1010, a memory 1020, an input/output interface 1030, a communication interface 1040, and a bus 1050. Wherein the processor 1010, memory 1020, input/output interface 1030, and communication interface 1040 are communicatively coupled to each other within the device via bus 1050.
The processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, and is configured to execute related programs to implement the technical solutions provided in the embodiments of the present disclosure.
The Memory 1020 may be implemented in the form of a ROM (Read Only Memory), a RAM (Random Access Memory), a static storage device, a dynamic storage device, or the like. The memory 1020 may store an operating system and other application programs, and when the technical solution provided by the embodiments of the present specification is implemented by software or firmware, the relevant program codes are stored in the memory 1020 and called to be executed by the processor 1010.
The input/output interface 1030 is used for connecting an input/output module to input and output information. The i/o module may be configured as a component in a device (not shown) or may be external to the device to provide a corresponding function. The input devices may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output devices may include a display, a speaker, a vibrator, an indicator light, etc.
The communication interface 1040 is used for connecting a communication module (not shown in the drawings) to implement communication interaction between the present apparatus and other apparatuses. The communication module can realize communication in a wired mode (such as USB, network cable and the like) and also can realize communication in a wireless mode (such as mobile network, WIFI, Bluetooth and the like).
Bus 1050 includes a path that transfers information between various components of the device, such as processor 1010, memory 1020, input/output interface 1030, and communication interface 1040.
It should be noted that although the above-mentioned device only shows the processor 1010, the memory 1020, the input/output interface 1030, the communication interface 1040 and the bus 1050, in a specific implementation, the device may also include other components necessary for normal operation. In addition, those skilled in the art will appreciate that the above-described apparatus may also include only those components necessary to implement the embodiments of the present description, and not necessarily all of the components shown in the figures.
Embodiments of the present specification further provide a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the computer program implements the foregoing task refusal processing method. The method at least comprises the following steps:
the data acquisition module is used for acquiring the data of the to-be-processed task refusing;
the characteristic checking module is used for checking whether the obtained data contains preset characteristics or not; the preset features at least include: applying for a refusal payment amount, judging a winning amount and judging a losing amount of the refusal payment task; if so, extracting the values of the preset features in the obtained data, and checking whether the corresponding relation among the extracted feature values is correct and whether the extracted feature values are consistent with the feature values in the local data;
the result generation module is used for generating a refusal payment judgment result according to the extracted values of the application refusal payment amount, the judgment winning amount and the judgment winning amount under the condition that the refusal payment task data to be processed pass the inspection;
and the order processing module is used for processing the transaction order corresponding to the payment refusing task according to the payment refusing judgment result.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include transitory computer readable media (transmyedia) such as modulated data signals and carrier waves.
From the above description of the embodiments, it is clear to those skilled in the art that the embodiments of the present disclosure can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the embodiments of the present specification may be essentially or partially implemented in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the methods described in the embodiments or some parts of the embodiments of the present specification.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the apparatus embodiment, since it is substantially similar to the method embodiment, it is relatively simple to describe, and reference may be made to some descriptions of the method embodiment for relevant points. The above-described apparatus embodiments are merely illustrative, and the modules described as separate components may or may not be physically separate, and the functions of the modules may be implemented in one or more software and/or hardware when implementing the embodiments of the present disclosure. And part or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of the embodiment. One of ordinary skill in the art can understand and implement it without inventive effort.
The foregoing is only a specific embodiment of the embodiments of the present disclosure, and it should be noted that, for those skilled in the art, a plurality of modifications and decorations can be made without departing from the principle of the embodiments of the present disclosure, and these modifications and decorations should also be regarded as the protection scope of the embodiments of the present disclosure.