Card data transaction processing method, apparatus and device

Abstract

The present application relates to the technical field of information processing, in particular to a card data transaction processing method, device and electronic equipment, the method comprising: in response to a real-time charging instruction sent by a charging device, detecting whether there is a historical suspicious order with the same card number as the real-time charging instruction in a preset server; if so, obtaining device end transaction information; then based on the server end transaction information and the device end transaction information of the historical suspicious order, determining the charging state of the historical suspicious order. In this way, by comparing the transaction information of the server end and the charging device end, the state of the suspicious order is quickly and accurately judged, the number of suspicious orders is reduced, and the transaction is more smoothly and safely carried out.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of information processing, and in particular to a card data transaction processing method, device and equipment. BACKGROUND

[0002] With the development of electronic information technology, electronic recharge cards such as public transportation recharge cards are increasingly widely used, making people's lives more convenient. For example, for the recharge of public transportation recharge cards, when a user recharges a public transportation card on a recharge device such as a mobile phone, the corresponding amount needs to be written into the mobile phone chip after successful payment. In this operation process, due to system or chip abnormalities, the amount may fail to be written, which will cause the user's money to be deducted, but the amount in the card is not recharged to the user, so there is an urgent need for a method for improving recharge identification and ensuring that the recharge is safely and smoothly performed. SUMMARY

[0003] To at least partially solve the above technical problems, the present application provides a card data transaction processing method, device and equipment.

[0004] In a first aspect, the present application provides a card data transaction processing method, comprising:

[0005] In response to a real-time recharge instruction sent by a recharge device, detecting whether there is a historical suspicious order with the same card number as the real-time recharge instruction in a preset server;

[0006] If there is, obtaining device-side transaction information, the device-side transaction information being transaction information saved in the recharge device for a successful recharge;

[0007] Based on server-side transaction information of the historical suspicious order and the device-side transaction information, determining a recharge state of the historical suspicious order, wherein the server-side transaction information is transaction information saved in the preset server.

[0008] Optionally, the obtaining of the device-side transaction information comprises:

[0009] Generating a control instruction based on applet technology;

[0010] Sending the control instruction to the recharge device, so that the recharge device returns the device-side transaction information to the preset server based on the control instruction;

[0011] Receiving the device-side transaction information.

[0012] Optionally, the device-side transaction information comprises a preset number of transaction order information.

[0013] The transaction order information includes at least one of the following: charging device information, a charging card number, a transaction counter value, a charging time, and a charging amount.

[0014] Optionally, the server-side transaction information of the historical doubtful order and the device-side transaction information are used to determine a charging state of the historical doubtful order.

[0015] If the device-side transaction information includes transaction order information consistent with the server-side transaction information of the historical doubtful order, the charging state of the historical doubtful order is modified to be a charging success.

[0016] If the device-side transaction information does not include transaction order information consistent with the server-side transaction information of the historical doubtful order, and a transaction counter value of the historical doubtful order in the preset server is less than a minimum counter value in all the device-side transaction information, the charging state of the historical doubtful order is determined to be doubtful.

[0017] If the device-side transaction information does not include transaction order information consistent with the server-side transaction information of the historical doubtful order, and a transaction counter value of the historical doubtful order in the preset server is greater than a minimum counter value in all the device-side transaction information, the charging state of the historical doubtful order is modified to be a charging failure.

[0018] Optionally, the method further includes:

[0019] If the device-side transaction information does not include transaction order information consistent with the server-side transaction information of the historical doubtful order, and all the counter values in the device-side transaction information are zero, the charging state of the historical doubtful order is modified to be a charging failure.

[0020] Optionally, the method further includes:

[0021] The charging state of the real-time charging order is determined to be doubtful or not.

[0022] The historical doubtful order with a charging state of a charging failure is recharged, and the real-time charging order with a charging state of not doubtful and a charging success is charged.

[0023] Optionally, the method further includes: the charging state of the historical doubtful order that is recharged and successfully charged is modified to be a charging success.

[0024] Optionally, the method further includes:

[0025] A target order in the preset server is determined to be a repeated order, the target order being an order with the same device information, card number, and counter information as the device-side transaction information, but a different order number.

[0026] In a second aspect, the embodiments of the present application further provide a data transaction processing device, comprising:

[0027] The detection module is configured to, in response to a real-time recharge instruction sent by the recharge device, detect whether a historical suspicious order with the same card number as the real-time recharge instruction exists in the preset server.

[0028] The acquisition module is configured to acquire device-side transaction information, which is transaction information of successful recharge stored in the recharge device.

[0029] The calculation module is configured to determine a recharge state of the historical suspicious order based on server-side transaction information of the historical suspicious order and the device-side transaction information, wherein the server-side transaction information is transaction information stored in the preset server.

[0030] In a third aspect, the present application further provides an electronic device, comprising a memory and a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is executed by the processor to implement the card data transaction processing method mentioned above.

[0031] The card data transaction processing method provided by the present application comprises: in response to a real-time recharge instruction sent by a recharge device, detecting whether a historical suspicious order with the same card number as the real-time recharge instruction exists in a preset server; if it exists, acquiring device-side transaction information; and then determining a recharge state of the historical suspicious order based on server-side transaction information of the historical suspicious order and the device-side transaction information. In this way, by comparing the transaction information of the server side and the recharge device side, the state of the suspicious order is quickly and accurately determined, the number of suspicious orders is reduced, and the transaction is more smoothly and safely carried out. BRIEF DESCRIPTION OF DRAWINGS

[0032] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and serve to explain the principles of the present application. Furthermore, the drawings and the text are not intended to limit the scope of the inventive concept in any way, but to illustrate the inventive concept for those skilled in the art by referring to specific embodiments.

[0033] Figure 1 A flowchart of the card data transaction processing method provided by the embodiments of the present application is shown in the figure;

[0034] Figure 2 A specific principle diagram for determining suspicious orders in the card data transaction processing method provided by the embodiments of the present application is shown in the figure;

[0035] Figure 3A flowchart of a card data transaction processing method provided by another embodiment of the present application is shown in the figure;

[0036] Figure 4 A recharge flowchart of a card data transaction processing method provided by the present application is shown in the figure;

[0037] Figure 5 A principle diagram of a recharge process of a card data transaction processing method provided by the present application is shown in the figure;

[0038] Figure 6 A structure diagram of a card data transaction processing device provided by an embodiment of the present application is shown in the figure;

[0039] Figure 7 A structure diagram of a card data transaction processing system provided by an embodiment of the present application is shown in the figure;

[0040] Figure 8 A structure diagram of an electronic device provided by an embodiment of the present application is shown in the figure. DETAILED DESCRIPTION

[0041] To make the objectives, technical solutions and advantages of the present application clearer, the technical solutions in the embodiments of the present application will be described below in a clear and complete manner with reference to the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the protection scope of the present application. In the case of no conflict, the embodiments described below and the features in the embodiments can be combined with each other.

[0042] Method embodiments:

[0043] Figure 1 A flowchart of a card data transaction processing method provided by an embodiment of the present application is shown in the figure, Figure 1 The card data transaction processing method provided by the present application can specifically include:

[0044] S101, in response to a real-time recharge instruction sent by a recharge device, detecting whether there is a historical suspicious order with the same card number as the real-time recharge instruction in a preset server.

[0045] Specifically, the real-time recharge instruction can be initiated by a user through a recharge device such as a mobile phone, and it can be understood that the real-time recharge instruction is used to recharge an electronic card such as a bus card of the user, so the instruction must contain information corresponding to the identity of the user, such as a recharge card number. After receiving the real-time recharge instruction sent by the user, the server of the preset system first determines the card number of the instruction, and then detects the transaction information of the card number in the server memory to determine whether there is a historical suspicious order identical to the card number in the transaction information, that is, a historical order that cannot be judged as a successful recharge or a failed recharge.

[0046] S102, if yes, obtaining the device-side transaction information.

[0047] The device-side transaction information is the transaction information of a successful recharge saved in the recharge device.

[0048] Specifically, the device-side transaction information is the transaction information saved in the internal chip or memory of the user's recharge device such as a mobile phone, including multiple transaction order information, and the number of orders can be pre-set, for example, the recent 10 transaction order information of the device side, wherein each transaction order information can include detailed information of the transaction order, such as the recharge device information, the recharge card number, the transaction counter value, the recharge time and the recharge amount.

[0049] It should be noted that the transaction information saved in the recharge device, that is, the device-side transaction information, generally only includes the transaction order of the successful transaction on the recharge device, so the above-mentioned device-side transaction information can be the transaction information of the successful recharge of the device side.

[0050] In actual application, the device-side transaction information can be obtained by issuing a control instruction to the recharge device and the like.

[0051] S103, determining the recharge state of the historical suspicious order based on the server-side transaction information of the historical suspicious order and the device-side transaction information.

[0052] The server-side transaction information is the transaction information saved in the preset server.

[0053] Specifically, after obtaining the device-side transaction information, the device-side transaction information is compared with the order information corresponding to the historical doubtful order stored in the server, so as to determine the recharge state of the historical doubtful order. Because the device-side transaction information is all successful transaction information, after determining the historical doubtful order based on the server-side transaction information, and comparing the detailed transaction information of the historical doubtful order in the server-side transaction information with the device-side transaction information, when there is transaction information corresponding to the historical doubtful order in the device-side transaction information, it can be determined that the recharge state of the historical doubtful order is successful; when there is no transaction information corresponding to the historical doubtful order in the device-side transaction information, it can be determined that the recharge state of the historical doubtful order is failed.

[0054] The card data transaction processing method provided in the application responds to the real-time recharge instruction sent by the recharge device, detects whether there is a historical doubtful order with the same card number as the real-time recharge instruction in the preset server, if there is, obtains device-side transaction information, and then determines the recharge state of the historical doubtful order based on the server-side transaction information of the historical doubtful order and the device-side transaction information. In this way, by comparing the transaction information of the server side and the recharge device side, the state of the doubtful order is quickly and accurately determined, the number of doubtful orders is reduced, and the transaction is more smoothly and safely carried out.

[0055] In some embodiments, in the card data transaction processing method provided in the application, the device-side transaction information can be obtained based on the applet technology.

[0056] In actual application, when the user initiates a recharge action, the payment channel is jumped to, and the user's money is deducted, at this time, the data is written into the chip by the applet related instruction in the recharge device such as a mobile phone, because it is self-operated in the mobile phone, if the network or process is interrupted at this time, the user and the server side cannot know whether the recharge is successful, resulting in interruption of the business process.

[0057] Therefore, in the application, after determining that there is a historical doubtful order, a corresponding control instruction can be generated by the applet technology and sent to the recharge device, so that the recharge device reads the file data in the chip based on the control instruction, and then returns the data corresponding to the control instruction to the server, so as to realize the server reading the file content in the chip of the recharge device.

[0058] The file data read based on the control instruction can be different file types determined for the use place of the public transportation card, for example, the recharge type of the public transportation card in the region, for example, for some cities with only online recharge such as Beijing, the 18 file in the mobile phone device can be read, and other cities such as Suzhou and Shenzhen can read 18 and 1F files.

[0059] Figure 2 The specific principle of determining the doubtful state in the card data transaction processing method provided by the embodiment of the application is shown in the following. Figure 2 As shown in the figure, based on the server-side transaction information of the historical doubtful order and the device-side transaction information, the recharging state of the historical doubtful order is determined, including: if there is order information consistent with the server-side transaction information of the historical doubtful order in the device-side transaction information, the recharging state of the historical doubtful order is modified to be successful; if there is no order information consistent with the server-side transaction information of the historical doubtful order in the device-side transaction information, and the transaction counter value of the historical doubtful order in the preset server is less than all the counter values in the device-side transaction information, the recharging state of the historical doubtful order is determined to be doubtful; if there is no order information consistent with the server-side transaction information of the historical doubtful order in the device-side transaction information, and the transaction counter value of the historical doubtful order in the preset server is greater than the smallest counter value in the device-side transaction information, the recharging state of the historical doubtful order is modified to be failed; if there is no order information consistent with the server-side transaction information of the historical doubtful order in the device-side transaction information, and all the counter values in the device-side transaction information are zero, the recharging state of the historical doubtful order is modified to be failed.

[0060] Specifically, for example, the obtained device-side transaction information includes the last 10 transaction order information, and each transaction order information can include a transaction card number, a transaction counter value, a transaction time and a stored amount (transaction amount).

[0061] Among them, the transaction counter value is increased by one after each transaction (both the server side and the recharging device side), so each transaction can be checked according to the transaction counter value.

[0062] For example, first, based on the 10 transaction records in the device-side transaction information obtained this time, the maximum counter value (cardseq) is obtained as the maximum counter value (maxCount), and the minimum cardseq is obtained as the minimum counter value (mincount), and cardseq (the stored transaction online transaction serial number before storage) + 1 is the current counter value count, and then the following judgment is made:

[0063] 1) When the server side determines that the historical doubtful order has order information consistent or matching with the information card number, the stored time, the amount, and the transaction counter value (which can be the online transaction serial number) in the device-side transaction record, it can be determined that the recharging state of the historical doubtful order is successful.

[0064] 2) When the server-side determined historical suspect order does not exist in the device-side transaction record information card number, circle time, amount, transaction counter value (may be online transaction serial number) consistent or matching order information, and count < mincount, it is indicated that the order record is covered, and it is impossible to determine whether the recharge is successful, and at this time, it is determined that the recharge state of the historical suspect order is still suspect.

[0065] 3) When the server-side determined historical suspect order does not exist in the device-side transaction record information card number, circle time, amount, transaction counter value (may be online transaction serial number) consistent or matching order information, and mincount <= count or mincount = maxcount = 0, it is indicated that it is not covered and no record, and at this time, it is determined that the recharge state of the historical suspect order is recharge failure.

[0066] In some embodiments, the transaction counter value mentioned above for calculation and judgment can be the connection transaction serial number before circle, or the online transaction serial number after successful transaction. In other embodiments, the obtained transaction information can be stored on the server side to facilitate subsequent faster calculation and completion of calculation and judgment. For example, the server-side recharge (recharge flow table) saved data (connection transaction serial number before circle) is called, and the online transaction serial number after successful transaction obtained from the recharge device side is saved in the recharge_record (recharge record table).

[0067] In other embodiments, an invalid (whether valid) field can also be added to the data in the recharge record table, 1 for valid and 0 for invalid. When making suspect judgment, only the valid records are queried, so that after unbinding, all information of the card is set to invalid, thereby preventing the problem of incorrect judgment caused by repeated card numbers, abnormal card migration, and avoiding the problem of incorrect test results caused by repeated use of card numbers in the test environment.

[0068] If the circle table (i.e. the table in the server side for saving the counter value used for calculation and judgment, including the transaction counter value in the server itself and the transaction counter value obtained from the recharge device) saves the online transaction serial number before transaction or the online transaction serial number after transaction, the above-mentioned online transaction serial number before transaction does not need to be added one.

[0069] In other embodiments of the present application, the device side can also detect and determine the recharge state of the real-time recharge instruction after receiving the real-time recharge instruction of the user.

[0070] Specifically, the recharging state of the real-time recharging order can be determined by the principle of determining the historical suspicious order, i.e., obtaining the device-side transaction information from the recharging device, and determining whether the real-time recharging order is suspicious based on the device-side transaction information. The way of obtaining the device-side transaction information and the principle of determining the recharging state of the real-time recharging order are the same as those in the above embodiment, and will not be described here again.

[0071] In actual application, as more and more public transport cities are accessed by the server side, the abnormal processing of the circle storage of public transport in each region is inconsistent, which leads to the problem that the suspicious order cannot be determined or the suspicious judgment result is incorrect, so the abnormal processing flow of the circle storage is re-standardized and unified to facilitate future maintenance, reduce the number of suspicious orders, and improve user experience. Therefore, in the present application, the suspicious order is determined by the data of both ends (the recharging device end and the server end), which can greatly reduce the number of suspicious orders and speed up the subsequent processing flow.

[0072] Figure 3 The flowchart of the card data transaction processing method provided by another embodiment of the present application is shown in FIG. 2. Figure 3 As shown in FIG. 2, the embodiment includes the following steps.

[0073] First, the transaction order is obtained, and it is determined whether the order is a suspicious order.

[0074] If the order is not a suspicious order, the normal order processing flow is directly entered, such as entering the recharging flow after recharging failure or ending the recharging and notifying the user after successful recharging.

[0075] If the order is a suspicious order, the suspicious order is determined again, the device-side transaction information is obtained by the above principle, the recharging state of the suspicious order is determined based on the device-side transaction information, when the recharging state is successful recharging, the recharging state of the order is modified to successful recharging, and when the recharging state is failed recharging, the recharging state of the order is modified to failed recharging, and the order is added to the refund queue.

[0076] The way of determining the suspicious order again can also be to take out the remote transaction credentials, such as the remote transaction counter value and the TAC of the remote transaction, from the Get signed Data instruction, to determine whether the transaction counters and TACs of the systems of both ends (the recharging device end and the server end) are consistent, if consistent, the recharging state of the suspicious order is modified to successful recharging, and if inconsistent, the recharging state of the order is modified to failed recharging, and the order is added to the refund queue.

[0077] On the basis of the above embodiment, the application can also re-charge the order finally confirmed as a failed order, such as re-charging the historical suspicious order whose final charging state is a charging failure after re-judging, and charging the real-time charging order whose charging state is not suspicious and charging is not successful. And the charging state of the order after re-charging and charging success is modified to charging success.

[0078] On the basis of the above embodiment, the card data transaction processing method provided by the application can also screen the orders in the server, and determine the target order screened as a repeated order, wherein the repeated order is an order with the same device information, card number and counter information in the device end transaction information, but different order numbers.

[0079] For example, the record with the same current cplc, card number and cardseq in the order information from the charging device, but different order numbers is found out from the server side recharge table, and is determined as a repeated order, and its state is set to failure and a notification is issued for subsequent processing of the charging system in communication connection with the system.

[0080] In some embodiments, this processing can only be done in the bus with 18 files in the applet (Beijing, Lingnandong, Suzhou, Shenzhen), because the transaction record of the applet with 18 files is easy to be covered by the consumption record, and the detection of the repeated order is set specifically, which can confirm the failed order in advance, thereby further improving the user experience.

[0081] In addition, on the basis of the above embodiment, the transaction information of the device end can be obtained in response to each real-time charging order, and stored in the server side. Therefore, when the charging state of the historical suspicious order cannot be determined in the real-time single acquisition of a preset number of device end order transaction information such as 10, the recharge_record (charging record table generated by obtaining the transaction information of the device end in response to each real-time charging order and storing it in the server side) generated by multiple acquisitions can also be detected to detect whether there is order information matching the historical suspicious order, so as to determine the charging state of the historical suspicious order. The judgment process is the same as the above judgment principle, that is, by querying the record in the recharge_record (cardseq is the transaction counter before the stored value table) through the card number, cardseq+1, including:

[0082] 1) If there is an order in the recharge_record with the same card number, stored value time and amount as the order information record in the server side of the historical suspicious order, the charging state of the historical suspicious order can be determined as success.

[0083] 2) If the record does not exist, the status remains "questionable" (the transaction may not have been uploaded to the server).

[0084] 3) If there are inconsistencies in the recorded time or amount, it can be judged as a failure.

[0085] Figure 4 A flowchart of the recharge process that includes the card data transaction processing method provided in this application, such as Figure 4 As shown, the recharge method may include:

[0086] First, the server receives the current recharge order and generates and issues an instruction to retrieve the 10 most recent top-up transaction records.

[0087] Then, the acquired data is saved to the recharge_record on the server side.

[0088] Next, check the server side to see if there are any historical suspicious orders, that is, determine if there was a previous suspicious order.

[0089] If there is a previous questionable order, then proceed through the above... Figure 3 The proposed solution involves assessing suspicious orders and proceeding to the next step once the recharge status is confirmed or no suspicious orders are found.

[0090] Check if there are any issues with the current order; if so, proceed based on the above. Figure 3 The scheme in the text determines the current recharge status of the order.

[0091] If the current order is not in question and the top-up was unsuccessful, or as described above... Figure 3 If the solution determines that the current order has failed to recharge, then the recharge will be performed, including obtaining the MAC2 of the recharge platform or directly obtaining the MAC value of the remote transaction.

[0092] If the current order is in doubt, as described above Figure 3 If the solution confirms that the recharge was successful, or if it is still impossible to determine whether the recharge was successful, the process will end directly.

[0093] The above process includes data interaction between the server and the recharge device. The recharge device needs to return data to the server based on control commands. If the network is disconnected or no result is returned after the server sends the command (at this time, the recharge status of the order is questionable), it can be retried, that is, the relevant command is resent until data is returned.

[0094] Figure 5 A schematic diagram illustrating the principle of the recharge process, including the card data transaction processing method provided in this application, is shown below. Figure 5 As shown, the entire process of recharging a public transport card is divided into two types. The first type of card requires a recharge platform to perform the corresponding operation. Figure 5(Part a) of the above, the second type of card does not require the recharge platform to perform corresponding operations. Figure 5 Part b of the document specifically includes:

[0095] For top-ups of the first type of card, the validity of the order is first determined. If the order is valid, after confirming the order retry logic, an instruction to retrieve card information is generated and sent to the top-up device for execution. The top-up device then returns the data result to the server. The system checks and confirms whether there was a previous questionable top-up transaction and confirms the status of the current top-up order. Then, it requests a top-up MAC2 from the card. After verifying and calculating the MAC2, the top-up platform generates a top-up instruction and sends it to the top-up device for execution. The top-up device completes the top-up, updates the order status to "top-up successful," and notifies the card and user to confirm the successful top-up.

[0096] For top-ups of the second type of card, the validity of the order is first determined. If the order is valid, after confirming the order retry logic, an instruction to retrieve card information is generated and sent to the top-up device for execution. The top-up device then returns the result to the server. The system checks and confirms whether there was a previous questionable top-up transaction and confirms the status of the current top-up order. Then, the remote top-up MAC is calculated, a top-up instruction is generated and sent to the top-up device for execution. The top-up device completes the top-up and updates the order status to "top-up successful." The system also notifies the cardholder and the user to confirm the successful top-up.

[0097] Device embodiments:

[0098] Based on the same inventive concept, this application also provides a card data transaction processing device. Figure 6 This is a schematic diagram of the structure of the card data transaction processing device provided in the embodiments of this application, as shown below. Figure 6 As shown, the device includes:

[0099] The detection module 61 is used to detect, in response to the real-time recharge instruction sent by the recharge device, whether there are any historical suspicious orders in the preset server that have the same card number as the real-time recharge instruction.

[0100] The acquisition module 62 is used to acquire device-side transaction information, which is the successful recharge transaction information stored in the recharge device;

[0101] The calculation module 63 is used to determine the recharge status of historical questionable orders based on server-side transaction information and device-side transaction information, wherein the server-side transaction information is the transaction information stored in a preset server.

[0102] The principle of the aforementioned card data transaction processing device has been described in detail in the section on card data transaction processing methods. You can refer to the section on card data transaction processing methods for understanding, so it will not be repeated here.

[0103] System embodiments:

[0104] Based on the same inventive concept, the application also provides a card data transaction processing system, Figure 7 is a structural schematic diagram of the card data transaction processing system provided by the application, as Figure 7 shown, the device comprises: a server 71, i.e. a core system, and a plurality of recharge devices 72.

[0105] The server 71 is in communication connection with a preset recharge platform 73 and a plurality of recharge devices 72, and is used for executing the card data transaction processing method mentioned in the above method embodiment.

[0106] Among them, the server 71 at least includes a memory, and the recharge device 72 at least includes a chip and a chip memory.

[0107] The principle of the above card data transaction processing system has been described in detail in the card data transaction processing method, and can be understood by referring to the card data transaction processing method, which will not be repeated here.

[0108] Electronic device embodiments:

[0109] Based on the same inventive concept, the application also provides an electronic device, Figure 8 is a structural schematic diagram of the electronic device provided by the application, as Figure 8 shown, the electronic device comprises a memory 81 and a processor 82, and a computer program stored in the memory 81 and executable on the processor 82, wherein the computer program is executed by the processor 82 to realize the card data transaction processing method provided in the above method embodiment.

[0110] The specific implementation of the electronic device provided by the application can refer to the implementation of the card data transaction processing method of any of the above embodiments, which will not be repeated here.

[0111] It can be understood that the same or similar parts in the above embodiments can be mutually referred to, and the contents not described in detail in some embodiments can be referred to the same or similar contents in other embodiments.

[0112] It should be noted that in the description of the application, the terms "first", "second" and the like are only used for descriptive purposes, and cannot be understood as indicating or implying relative importance. In addition, in the description of the application, unless otherwise specified, the meaning of "a plurality of" is at least two.

[0113] Any procedural or methodological descriptions in flow charts or otherwise described herein can be understood to represent modules, segments, or portions of code that include executable instructions for implementing the specific logical functions or steps, and the scope of preferred embodiments of the present application includes additional implementations in which the functions are performed in a different order, including substantially simultaneously, or in reverse order, as will be understood by those skilled in the art to which embodiments of the present application pertain.

[0114] It should be understood that portions of the present application can be implemented in hardware, software, firmware, or combinations thereof. In the above-described embodiments, multiple steps or methods can be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, and as in another embodiment, implementation can be in any one or a combination of the following technologies, which are all well known in the art: discrete logic circuitry having logic gates for implementing logic functions upon an application of data signals, application specific integrated circuits having appropriate combinational logic gates, programmable gate arrays (PGA), field programmable gate arrays (FPGA), and the like.

[0115] Those skilled in the art can understand that all or part of the steps carried out by the above-mentioned embodiments can be completed by programs instructing related hardware, and the programs can be stored in a computer readable storage medium, and when executed, include one or a combination of steps of the method embodiments.

[0116] In addition, each functional unit in each embodiment of the present application can be integrated in one processing module, or each unit can be physically present separately, or two or more units can be integrated in one module. The above-mentioned integrated module can be realized in the form of hardware or in the form of a software functional module. When the integrated module is realized in the form of a software functional module and sold or used as an independent product, it can also be stored in a computer readable storage medium.

[0117] The above-mentioned storage medium can be a read-only memory, a magnetic disk or an optical disk, etc.

[0118] In the description of the present specification, the description of the terms "one embodiment", "some embodiments", "an example", "a specific example", or "some examples" and the like means that the specific features, structures, materials or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. In the present specification, the illustrative description of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner.

[0119] Although the embodiments of the present application have been shown and described above, it is understood that the above-described embodiments are exemplary and are not to be construed as limiting the present application, and that variations, modifications, substitutions and changes can be made by those skilled in the art without departing from the scope of the present application.

Claims

1. A card data transaction processing method, characterized by, The application comprises: In response to the real-time recharge instruction sent by the recharge device, it is detected whether there is a historical suspicious order with the same card number as the real-time recharge instruction in the preset server; If there is, the device-side transaction information is obtained, which is the transaction information of successful recharge saved in the recharge device; Based on the server-side transaction information of the historical suspicious order and the device-side transaction information, the recharge status of the historical suspicious order is determined, wherein the server-side transaction information is the transaction information saved in the preset server; The device-side transaction information includes a preset number of transaction order information; the transaction order information includes at least one of the following: recharge device information, recharge card number, transaction counter value, recharge time and recharge amount; The determination of the recharge status of the historical suspicious order based on the server-side transaction information of the historical suspicious order and the device-side transaction information comprises: If there is transaction order information consistent with the server-side transaction information of the historical suspicious order in the device-side transaction information, the recharge status of the historical suspicious order is modified to successful recharge; If there is no transaction order information consistent with the server-side transaction information of the historical suspicious order in the device-side transaction information, and the transaction counter value of the historical suspicious order in the preset server is less than the minimum counter value in all the device-side transaction information, it is determined that the recharge status of the historical suspicious order is still suspicious; If there is no transaction order information consistent with the server-side transaction information of the historical suspicious order in the device-side transaction information, and the transaction counter value of the historical suspicious order in the preset server is greater than the minimum counter value in all the device-side transaction information, the recharge status of the historical suspicious order is modified to failed recharge.

2. The card data transaction processing method of claim 1, wherein, The obtaining of the device-side transaction information comprises: Generating a control instruction based on applet technology; Sending the control instruction to the recharge device, so that the recharge device returns the device-side transaction information to the preset server based on the control instruction; Receiving the device-side transaction information.

3. The card data transaction processing method of claim 2, wherein, Further comprising: If there is no transaction order information consistent with the server-side transaction information of the historical suspicious order in the device-side transaction information, and all the counter values in the device-side transaction information are zero, the recharge status of the historical suspicious order is modified to failed recharge.

4. The card data transaction processing method according to any one of claims 1 or 3, characterized by, Further comprising: Determining whether the recharge status of the real-time recharge order is suspicious; Re-recharging the historical suspicious order with failed recharge status, and recharging the real-time recharge order with non-suspicious and successful recharge status.

5. The card data transaction processing method of claim 4, wherein, Further comprising: The recharge status of the historical suspicious order after successful re-recharge is modified to successful recharge.

6. The card data transaction processing method of claim 1, wherein, Further comprising: The target order in the preset server is determined as a repeated order, which is an order with the same device information, card number and counter information as the device information in the device-side transaction information, but with different order numbers.

7. A card data transaction processing apparatus for performing the method according to any one of claims 1 to 6, characterized in that, Comprise The detection module is configured to, in response to a real-time recharge instruction sent by the recharge device, detect whether a historical suspicious order with a card number same as that of the real-time recharge instruction exists in the preset server; The acquisition module is configured to acquire device-side transaction information, which is transaction information of a successful recharge saved in the recharge device. The calculation module is configured to determine a recharge state of the historical suspicious order based on server-side transaction information of the historical suspicious order and the device-side transaction information, wherein the server-side transaction information is transaction information saved in the preset server. 8.An electronic device, comprising a memory and a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the card data transaction processing method according to any one of claims 1 to 6.

Images