Mobile payment method and device and electronic equipment

Abstract

The invention discloses a mobile payment method and device and electronic equipment. The method comprises the following steps: receiving a recharging request of a target object; the recharging request is verified through a first verification mode, and under the condition that the recharging request passes the first verification mode, the recharging request is verified through a second verification mode, the first verification mode is used for ensuring that the same recharging request is not repeatedly submitted within a first preset time range, and the second verification mode is used for ensuring that the same recharging request is not repeatedly submitted within a second preset time range; the second verification mode is used for ensuring that the same recharge request is not subjected to repeated payment operation; under the condition that the recharge request passes the second verification mode, creating a recharge order; and receiving a payment result corresponding to the recharging order, and returning the payment result to a recharging interface where the target object is located. The technical problem of poor user experience caused by lack of a mobile payment function of a digital human customer service system in related technologies is solved.

Description

Technical Field

[0001] The present application relates to the field of financial payment technology, and in particular to a mobile payment method, device and electronic device. Background Art

[0002] Digital human (intelligent) customer service can transfer offline business scenarios to the Internet, helping users to handle business more conveniently and quickly. One of the important businesses is to help users recharge online and close accounts and withdraw remaining balances. These businesses all rely on the mobile payment system of the electronic channel interface. The current digital human (intelligent) customer service system temporarily lacks a complete payment system to meet user needs, such as collecting user information, securely recording user data, and transmitting it to the electronic channel platform to ensure that process data is not tampered with, and user money is not lost and is correct.

[0003] To address the above-mentioned problems, no effective solution has been proposed yet. Summary of the invention

[0004] The embodiments of the present application provide a mobile payment method, device and electronic device to at least solve the technical problem of poor user experience caused by the lack of mobile payment function in the digital human customer service system in the related technology.

[0005] According to one aspect of an embodiment of the present application, a mobile payment method is provided, which is applied to a digital human customer service system, including: receiving a recharge request from a target object; verifying the recharge request through a first verification method, and verifying the recharge request through a second verification method if the recharge request passes the first verification method, wherein the first verification method is used to ensure that the same recharge request will not be submitted repeatedly within a first preset time range, and the second verification method is used to ensure that the same recharge request will not be subjected to repeated payment operations; if the recharge request passes the second verification method, creating a recharge order; receiving a payment result corresponding to the recharge order, and returning the payment result to the recharge interface where the target object is located.

[0006] Optionally, before verifying the recharge request through the first verification method, the method also includes: determining request parameters of the recharge request, wherein the request parameters include at least user ID, recharge amount and recharge time; sorting the request parameters in a preset order to obtain a parameter string corresponding to the request parameters; encrypting the parameter string through a hash algorithm and a preset key to obtain a first signature corresponding to the recharge request.

[0007] Optionally, the method further includes: obtaining a second signature carried in the recharge request; and determining the legitimacy of the recharge request based on the first signature and the second signature.

[0008] Optionally, the recharge request is verified by a first verification method, including: obtaining a request identifier corresponding to the recharge request; determining the number of occurrences of the request identifier within a first preset time range; when the number of occurrences is greater than 1, determining that the recharge request has not passed the first verification method; when the number of occurrences is less than or equal to 1, determining that the recharge request has passed the first verification method.

[0009] Optionally, the recharge request is verified by a second verification method, including: determining a business processing status of the recharge request; when the business processing status indicates that the recharge request has been processed, determining that the recharge request has not passed the second verification method; when the business processing status indicates that the recharge request has not been processed, determining that the recharge request has passed the second verification method.

[0010] Optionally, the Digital Human Customer Service System communicates with the operator system via an electronic channel interface, which is an electronic channel interface that supports online business operations of the Digital Human Customer Service System.

[0011] Optionally, if the payment result has not been received within the second preset time range, the method also includes: generating a query request corresponding to the recharge order; sending the query request to the electronic channel interface, and receiving response information returned by the electronic channel interface; and determining the business processing result of the recharge order based on the response information.

[0012] According to another aspect of the embodiment of the present application, a mobile payment device is also provided, which is applied to a digital human customer service system, including: a receiving module, used to receive a recharge request from a target object; a verification module, used to verify the recharge request through a first verification method, and when the recharge request passes the first verification method, verify the recharge request through a second verification method, wherein the first verification method is used to ensure that the same recharge request will not be submitted repeatedly within a first preset time range, and the second verification method is used to ensure that the same recharge request will not be subjected to repeated payment operations; a creation module, used to create a recharge order when the recharge request passes the second verification method; a return module, used to receive a payment result corresponding to the recharge order, and return the payment result to the recharge interface where the target object is located.

[0013] According to another aspect of an embodiment of the present application, there is also provided an electronic device, including: a memory and a processor, wherein the memory is used to store program instructions; the processor is connected to the memory and is used to execute and implement the above-mentioned mobile payment method.

[0014] According to another aspect of the embodiments of the present application, a non-volatile storage medium is further provided, the non-volatile storage medium including a stored computer program, wherein the device where the non-volatile storage medium is located executes the above-mentioned mobile payment method by running the computer program.

[0015] According to another aspect of the embodiments of the present application, a computer program product is also provided, including computer instructions, which implement the above-mentioned mobile payment method when executed by a processor.

[0016] In an embodiment of the present application, the digital human customer service system receives a recharge request from a target object; verifies the recharge request through a first verification method, and when the recharge request passes the first verification method, verifies the recharge request through a second verification method, wherein the first verification method is used to ensure that the same recharge request will not be submitted repeatedly within a first preset time range, and the second verification method is used to ensure that the same recharge request will not be subjected to repeated payment operations; when the recharge request passes the second verification method, creates a recharge order; receives the payment result corresponding to the recharge order, and returns the payment result to the recharge interface where the target object is located, thereby achieving the purpose of realizing efficient and reliable mobile payment in the digital human customer service system, thereby achieving the technical effect of enhancing user experience and improving payment security, and further solving the technical problem of poor user experience caused by the lack of mobile payment function in the digital human customer service system in related technologies. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0018] Figure 1 is a hardware structure diagram of a computer terminal for implementing a mobile payment method according to an embodiment of the present application;

[0019] Figure 2 is a flow chart of a mobile payment method according to an embodiment of the present application;

[0020] Figure 3 It is a structural diagram of a mobile payment device according to an embodiment of the present application. DETAILED DESCRIPTION

[0021] In order to enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of this application.

[0022] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0023] The information collected in the embodiments of the present application is information and data authorized by the user or fully authorized by all parties, and the collection, storage, use, processing, transmission, provision, disclosure and application of the relevant data comply with the relevant laws, regulations and standards of the relevant regions, take necessary confidentiality measures, do not violate public order and good morals, and provide corresponding operation entrances for users to choose to authorize or reject automated decision-making results; if the user chooses to reject, the expert decision-making process will be entered.

[0024] First, some nouns or terms that appear in the process of explaining the embodiments of the present application are subject to the following explanations:

[0025] Mobile payment: also known as mobile payment, refers to a payment method in which users use mobile terminals such as mobile phones, personal digital assistants, and mobile PCs to consume goods or services. It uses wireless communication technology or mobile terminals to directly or indirectly send payment instructions to banks and financial institutions to achieve monetary payment and fund transfer.

[0026] In order to solve the problem that the digital human customer service system in the related art lacks mobile payment capabilities, the embodiment of the present application provides a mobile payment method, which can be run on Figure 1 In the computer terminal shown, the computer terminal is described below.

[0027] The mobile payment method embodiment provided in the embodiment of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Figure 1 The hardware structure block diagram of a computer terminal for implementing a mobile payment method is shown. Figure 1As shown, the computer terminal 10 may include one or more (102a, 102b, ..., 102n are used to illustrate) processors (the processor may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 104 for storing data, and a transmission module 106 for communication functions connected via a wired and / or wireless network. In addition, it may also include: a display, a keyboard, a cursor control device, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, and a BUS bus. Those skilled in the art can understand that Figure 1 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations are shown.

[0028] It should be noted that the one or more processors and / or other data processing circuits described above may generally be referred to herein as "data processing circuits". The data processing circuits may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. In addition, the data processing circuit may be a single independent processing module, or may be incorporated in whole or in part into any of the other components in the computer terminal 10. As described in the embodiments of the present application, the data processing circuit acts as a processor control (e.g., selection of a variable resistor terminal path connected to an interface).

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

[0030] The transmission module 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission module 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission module 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0031] The display may be, for example, a touch screen liquid crystal display (LCD) that enables a user to interact with a user interface of the computer terminal 10 .

[0032] It should be noted that, in some optional embodiments, the above Figure 1 The computer terminal shown may include hardware elements (including circuits), software elements (including computer code stored on a computer-readable medium), or a combination of hardware elements and software elements. It should be noted that Figure 1 This is merely one example of a particular embodiment and is intended to illustrate the types of components that may be present in the computer terminal described above.

[0033] In the above-mentioned operating environment, an embodiment of the present application provides an embodiment of a mobile payment method. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0034] Figure 2 is a flow chart of a mobile payment method according to an embodiment of the present application, such as Figure 2 As shown, the method is applied to a digital human customer service system and includes the following steps:

[0035] Step S202: receiving a recharge request from a target object.

[0036] In the above step S202, the Digital Human Customer Service System will provide a recharge interface for the target object (user) to input the recharge amount and other information, then obtain the recharge request initiated by the user and start the mobile payment process, wherein the user's recharge request data may include the user's identity ID, recharge amount, recharge time and the digital signature corresponding to the recharge request, etc.

[0037] Step S204, verifying the recharge request by a first verification method, and verifying the recharge request by a second verification method if the recharge request passes the first verification method, wherein the first verification method is used to ensure that the same recharge request will not be submitted repeatedly within a first preset time range, and the second verification method is used to ensure that the same recharge request will not be subjected to repeated payment operations.

[0038] In the above step S204, the first verification method is anti-re-verification, which is used to ensure that the same recharge request will not be submitted repeatedly within a preset time range, such as checking whether the unique identifier (such as order number or user behavior identifier) ​​in the recharge request already exists in the cache or database; if the recharge request is repeated, an error message is returned, and if the recharge request is new, the next step of verification is performed. The second verification method is idempotent verification, which is used to ensure that the user's recharge request will not be executed multiple times and to ensure the idempotence of the payment operation, such as through distributed locks or other mechanisms to detect that in any case, the same recharge request will only be processed once; if the recharge request has been processed, a corresponding prompt message is returned, and if the recharge request has not been processed, the next step of payment operation is performed.

[0039] Step S206: When the recharge request passes the second verification method, a recharge order is created.

[0040] In the above step S206, when the user's recharge request passes the first verification method and the second verification method, a corresponding recharge order is generated for subsequent payment processing and tracking, such as creating a new recharge order record in the database to record the user's recharge behavior, including user information, order information, order status, etc.

[0041] Step S208, receiving the payment result corresponding to the recharge order, and returning the payment result to the recharge interface where the target object is located.

[0042] In the above step S208, the Digihuman customer service system can obtain the asynchronous notification result (i.e. the above payment result) generated by the operator system corresponding to the recharge order through the electronic channel interface, such as payment status (payment success or payment failure), transaction details and updated account balance, and feedback to the user. If the returned payment result has not been received within the preset time range, the payment status of the recharge order can be actively queried through the electronic channel interface.

[0043] It should be noted that the Digital Human Customer Service System communicates with the operator system through the electronic channel interface, which is an electronic channel interface that supports the online business operations of the Digital Human Customer Service System.

[0044] In the embodiment of the present application, the electronic channel interface refers to the electronic channel interface, which is an interface service provided by the operator system to facilitate users to handle business through the Internet or other electronic means. The electronic channel interface can support various online business operations, such as inquiry, recharge, payment, ordering services, handling business, etc. In the above mobile payment business process, the electronic channel interface is used to establish a communication connection between the digital human customer service system and the operator system, including:

[0045] 1. Order creation: After the user initiates a recharge request through the Digital Human Customer Service System and it is verified, it will communicate with the telecom operator's system through the electric channel interface to create a recharge order.

[0046] 2. Obtaining the business acceptance status: After the order is created, the Digital Human Customer Service System will obtain the business acceptance status through the electronic channel interface call.

[0047] 3. Asynchronous result notification: The Digihuman customer service system can receive the asynchronous notification result (i.e. the payment result mentioned above) returned by the DianChannel platform to understand the result of the recharge operation.

[0048] 4. Active result query: If no asynchronous result notification is received from the DianChannel platform within a certain time frame, the Digital Human Customer Service System can actively query the recharge results through the DianChannel interface.

[0049] The use of the electronic channel interface enables the digital human customer service system to provide users with a seamless online service experience, while also ensuring the automation and high efficiency of business processing.

[0050] Through the above steps S202 to S208, the purpose of realizing efficient and reliable mobile payment in the Digital Human customer service system is achieved, thereby achieving the technical effect of enhancing user experience and improving payment security, thereby solving the technical problem of poor user experience caused by the lack of mobile payment function in the Digital Human customer service system in the related art. The following is a detailed description.

[0051] Optionally, before verifying the recharge request through the first verification method, the method also includes: determining request parameters of the recharge request, wherein the request parameters include at least user ID, recharge amount and recharge time; sorting the request parameters in a preset order to obtain a parameter string corresponding to the request parameters; encrypting the parameter string through a hash algorithm and a preset key to obtain a first signature corresponding to the recharge request.

[0052] Furthermore, a second signature carried by the recharge request is obtained; and the legitimacy of the recharge request is determined based on the first signature and the second signature.

[0053] In the embodiment of the present application, the HmacSHA256 algorithm can be used to perform signature verification on the user's recharge request to ensure the integrity and authenticity of the recharge request and prevent the recharge request from being tampered with or forged during transmission. The specific process can be as follows:

[0054] 1. Determine the request parameters:

[0055] A key shared by the server and the client, namely the preset key, is predetermined for use in the signing and verification process. Further, request parameters corresponding to the recharge request are determined, such as user ID, recharge amount, and recharge time.

[0056] 2. Parameter processing:

[0057] All request parameters are sorted in a preset order (such as alphabetical order) to ensure the consistency of the signature, regardless of the order in which the parameters are submitted. The sorted parameters and their values ​​are concatenated into a string in the "parameter = parameter value" mode to form a parameter string. Usually, the parameters are connected with the & symbol.

[0058] 3. Encryption processing:

[0059] Append the concatenated parameter string to the preset key, or use the key to perform specific processing on it. Specifically, if the key length exceeds the block size (64 bytes) of the HmacSHA256 algorithm, perform SHA256 hash processing on the key and use the result as the key. If the key length is less than the block size, fill the end of the key with zeros until the block size is reached. Further, use the processed key to perform an XOR operation with two fixed ASCII values ​​to generate two keys: key1 (for internal use) and key2 (for external use), where key1 is the XOR result of the key and 0x3636...36 (each byte is 0x36), and key2 is the XOR result of the key and 0x5c5c...5c (each byte is 0x5c).

[0060] 4. Signature generation:

[0061] Internal hash: Use key1 to hash the entire signature string (using the SHA256 hash algorithm); External hash: Use key2 to hash the hash value obtained in the previous step again. The final hash value is the first signature above. Usually, this value will be encoded using Base64 to facilitate transmission as a string in the HTTP request.

[0062] In the embodiment of the present application, when the user initiates a recharge request, a digital signature corresponding to the recharge request will be generated, i.e., the above-mentioned second signature. It should be noted that the generation process of the second signature is similar to the generation process of the above-mentioned first signature, which will not be repeated here, and the signature verification is performed before entering the business layer of the digital human customer service system to ensure the security of data transmission.

[0063] Furthermore, by comparing the first signature generated by the above-mentioned Digital Human Customer Service System with the second signature carried by the recharge request, the legitimacy of the recharge request can be verified. For example, if the first signature is consistent with the second signature, it means that the recharge request has not been tampered with during the transmission process, indicating that the recharge request has passed the preliminary legitimacy verification and the subsequent recharge process can be executed. Through the above verification, the Digital Human Customer Service System can ensure that only legitimate and untampered requests can be further processed, thereby ensuring the security of the system and the authenticity of the data.

[0064] In the above step S204, the recharge request is verified by the first verification method, including: obtaining a request identifier corresponding to the recharge request; determining the number of occurrences of the request identifier within a first preset time range; when the number of occurrences is greater than 1, determining that the recharge request has not passed the first verification method; when the number of occurrences is less than or equal to 1, determining that the recharge request has passed the first verification method.

[0065] In the embodiment of the present application, the first verification method (anti-re-verification) is a key mechanism to ensure system stability and data consistency. The first verification method can ensure that the same business operation will not be processed repeatedly, avoiding errors or resource waste caused by repeated operations. The specific process can be as follows:

[0066] First, when a user initiates a recharge request, the Digihuman customer service system will generate a unique request identifier (such as an order number or user behavior identifier) ​​to identify this recharge operation.

[0067] Secondly, the Digital Human Customer Service System will check whether the request identifier already exists in the database or cache within the preset time range (i.e., the first preset time range mentioned above), that is, query the number of times the request indicates the occurrence in the database or cache. If the number of occurrences of the request identifier in the database or cache is greater than 1, it means that the operation has been processed, and the system will reject the request and return the corresponding error message (such as "the operation already exists"), that is, the recharge request has not passed the first verification method. If the number of occurrences of the request identifier in the database or cache is less than or equal to 1, it means that the operation has not been processed, and the system will add this unique identifier to the database or cache and continue to process the business logic, that is, the recharge request has passed the first verification method.

[0068] Finally, to prevent request identifiers from occupying storage resources in the database or cache, an expiration time can be set for these request identifiers, which will be automatically deleted after the expiration. It should be noted that during the execution of the business logic, if any error or interruption is encountered, the system needs to ensure that this unique request identifier will not be processed again.

[0069] Further, the recharge request is verified by a second verification method, including: determining a business processing status of the recharge request; when the business processing status indicates that the recharge request has been processed, determining that the recharge request has not passed the second verification method; when the business processing status indicates that the recharge request has not been processed, determining that the recharge request has passed the second verification method.

[0070] In the embodiment of the present application, the second verification method (idempotent verification) is another key mechanism to ensure system stability and data consistency. The first verification method can ensure that the same business operation, no matter how many times it is executed, has the same result and will not affect the system status. The specific process can be as follows:

[0071] First, before processing the business logic, the Digihuman customer service system will determine the business processing status of the recharge request, that is, check whether the user's recharge request operation has been completed. If it has been completed, the system will directly return the recharge payment result and will no longer execute the recharge request repeatedly; if it has not been completed, the system will continue to execute the recharge request operation. After the recharge request operation is completed, the system will update the business processing status of the recharge request and mark it as completed. It should be noted that during the execution of the recharge request operation, the system will ensure the atomicity of the operation, that is, the recharge request operation is either fully executed or not executed at all, and there will be no intermediate state.

[0072] At the same time, for repeated recharge requests that may arrive during the recharge request operation, the Digital Human Customer Service System will directly return the result based on the business processing status of the recharge request without executing the same business logic again. In addition, in order to ensure the traceability of the operation, the system can record the operation log, including the unique identification of the operation, operation time, operation results and other information.

[0073] In the distributed system of Digital Human Customer Service, in order to prevent multiple nodes from processing the same operation at the same time, distributed locks can be used to ensure the idempotence of the operation. For example, when a node starts processing an operation, it acquires a distributed lock; when other nodes try to process the same operation, they cannot acquire the lock and will wait or directly return the processing result of the previous node.

[0074] By implementing the above-mentioned anti-revalidation and idempotence validation, the Digital Human customer service system can ensure the consistency of user operations and the accuracy of business data, and maintain the stability and reliability of the Digital Human customer service system even in high concurrency or unstable network conditions.

[0075] In the above step S208, if the payment result has not been received within the second preset time range, a query request corresponding to the recharge order can also be generated; the query request is sent to the electronic channel interface, and the response information returned by the electronic channel interface is received; and the business processing result of the recharge order is determined based on the response information.

[0076] In the embodiment of the present application, after the digital customer service system completes the recharge operation request, the payment result will not be obtained immediately, but the payment result will be returned asynchronously by the electronic channel interface. This result may be received at an uncertain future time point due to factors such as network delay and the processing time of the digital human customer service system.

[0077] Therefore, if the asynchronous payment result is not received within the set time (i.e., within the second preset time range mentioned above), the Digital Human Customer Service System can proactively query the operation result through the query interface provided by the electronic channel to ensure the integrity of the business process and the accuracy of the data. Specifically, the Digital Human Customer Service System will generate a corresponding query request based on the recharge order, and send the query request to the electronic channel interface; then, wait for the feedback from the electronic channel interface, and receive the response information returned by the electronic channel interface; then, parse the response information, extract the query results, and perform corresponding processing based on the query results, such as updating the order status, notifying the user, etc. This process ensures that even if the asynchronous operation does not return the result in time, the system can guarantee the continuity of the business and the final consistency of the data.

[0078] In the embodiment of the present application, by deploying three payment services and using a load balancing mechanism and a failover mechanism, the practicality and stability of the digital human customer service system can be improved, ensuring the stable operation of the payment service and maintaining the mobile payment service even in the event of certain server failures.

[0079] In addition, by introducing the online payment system of Digital Human Customer Service, the number of users of Digital Human Customer Service has increased by more than 10,000, and the service usage has reached more than 500,000. It has provided users with more convenience, improved the security and efficiency of mobile payment, promoted the popularization and innovation of financial services, and promoted the development of the digital economy. It has not only brought users a better payment experience and service quality, but also injected new vitality and impetus into the development of the entire social economy.

[0080] In summary, in the embodiment of the present application, the mobile payment of the digital human customer service system enables consumers to complete payment operations anytime and anywhere through mobile terminals such as smart phones, without carrying cash or bank cards, thereby improving the efficiency of payment. Merchants can receive payments faster, thereby accelerating the return and circulation of funds. At the same time, mobile payment can also reduce manual operations and the use of paper documents, reducing transaction costs and time costs. In addition, the HmacSHA256 algorithm is used to perform signature verification, anti-re-verification, and idempotent verification operations, which ensures the legitimacy and data consistency of the user's recharge request, enhances the payment security of the digital human customer service system, and further ensures the user's financial security.

[0081] According to an embodiment of the present application, a mobile payment device is provided. It should be noted that the mobile payment device of the embodiment of the present application can be used to execute the mobile payment method provided in the embodiment of the present application. The mobile payment device provided in the embodiment of the present application is introduced below.

[0082] Figure 3 is a structural diagram of a mobile payment device provided according to an embodiment of the present application. Figure 3 As shown, the device is applied to a digital human customer service system, including:

[0083] A receiving module 30, configured to receive a recharge request from a target object;

[0084] a verification module 32, configured to verify the recharge request by a first verification method, and if the recharge request passes the first verification method, verify the recharge request by a second verification method, wherein the first verification method is used to ensure that the same recharge request is not submitted repeatedly within a first preset time range, and the second verification method is used to ensure that the same recharge request is not subjected to repeated payment operations;

[0085] A creation module 34, configured to create a recharge order if the recharge request passes the second verification method;

[0086] The return module 36 is used to receive the payment result corresponding to the recharge order and return the payment result to the recharge interface where the target object is located.

[0087] Through the receiving module 30, verification module 32, creation module 34 and return module 36 in the above-mentioned mobile payment device, the purpose of realizing efficient and reliable mobile payment in the digital human customer service system is achieved, thereby achieving the technical effect of enhancing user experience and improving payment security, and further solving the technical problem of poor user experience caused by the lack of mobile payment function in the digital human customer service system in related technologies.

[0088] In the mobile payment device provided in the embodiment of the present application, the verification module is also used to determine the request parameters of the recharge request, wherein the request parameters include at least a user ID, a recharge amount and a recharge time; sort the request parameters in a preset order to obtain a parameter string corresponding to the request parameters; encrypt the parameter string through a hash algorithm and a preset key to obtain a first signature corresponding to the recharge request.

[0089] In the mobile payment device provided in the embodiment of the present application, the verification module is also used to obtain a second signature carried by the recharge request; and determine the legitimacy of the recharge request based on the first signature and the second signature.

[0090] In the mobile payment device provided in the embodiment of the present application, the verification module is also used to obtain a request identifier corresponding to the recharge request; determine the number of occurrences of the request identifier within a first preset time range; when the number of occurrences is greater than 1, determine that the recharge request has not passed the first verification method; when the number of occurrences is less than or equal to 1, determine that the recharge request has passed the first verification method.

[0091] In the mobile payment device provided in the embodiment of the present application, the verification module is also used to determine the business processing status of the recharge request; when the business processing status indicates that the recharge request has been processed, it is determined that the recharge request has not passed the second verification method; when the business processing status indicates that the recharge request has not been processed, it is determined that the recharge request has passed the second verification method.

[0092] In the mobile payment device provided in the embodiment of the present application, the creation module is also used to generate a query request corresponding to the recharge order when no payment result has been received within the second preset time range; send the query request to the electronic channel interface and receive response information returned by the electronic channel interface; determine the business processing result of the recharge order based on the response information.

[0093] An embodiment of the present application also provides an electronic device, including: a memory and a processor, wherein the memory is used to store program instructions; the processor is connected to the memory and is used to execute and implement the above-mentioned mobile payment method.

[0094] It should be noted that the above electronic equipment is used to execute Figure 2 The mobile payment method shown, therefore the relevant explanations and instructions in the above mobile payment method are also applicable to the electronic device and will not be repeated here.

[0095] An embodiment of the present application also provides a non-volatile storage medium, which includes a stored computer program, wherein the device where the non-volatile storage medium is located executes the above-mentioned mobile payment method by running the computer program.

[0096] It should be noted that the above non-volatile storage medium is used to execute Figure 2 The mobile payment method shown, therefore the relevant explanations in the above mobile payment method are also applicable to the non-volatile storage medium, and will not be repeated here.

[0097] An embodiment of the present application also provides a computer program product, including computer instructions, which implement the above-mentioned mobile payment method when executed by a processor.

[0098] It should be noted that the above-mentioned computer program product is used to execute Figure 2 The mobile payment method shown, therefore the relevant explanations and instructions in the above mobile payment method are also applicable to the computer program product and will not be repeated here.

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

[0100] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0101] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only schematic. For example, the division of the units can be a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0102] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

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

[0104] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, disk or optical disk and other media that can store program codes.

[0105] The above is only a preferred implementation of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A mobile payment method, characterized in that: Applied to Digital Human Customer Service System, including: Receive a recharge request from a target object; Verifying the recharge request by a first verification method, and if the recharge request passes the first verification method, verifying the recharge request by a second verification method, wherein the first verification method is used to ensure that the same recharge request is not repeatedly submitted within a first preset time range, and the second verification method is used to ensure that the same recharge request is not subjected to repeated payment operations; If the recharge request passes the second verification method, creating a recharge order; Receive the payment result corresponding to the recharge order, and return the payment result to the recharge interface where the target object is located.

2. The method according to claim 1, characterized in that: Before verifying the recharge request by using the first verification method, the method further includes: Determine request parameters of the recharge request, wherein the request parameters include at least a user ID, a recharge amount, and a recharge time; Sorting the request parameters in a preset order to obtain a parameter character string corresponding to the request parameters; The parameter character string is encrypted using a hash algorithm and a preset key to obtain a first signature corresponding to the recharge request.

3. The method according to claim 2, characterized in that The method further comprises: Obtaining a second signature carried by the recharge request; The legitimacy of the recharge request is determined based on the first signature and the second signature.

4. The method according to claim 1, characterized in that: Verifying the recharge request by a first verification method includes: Obtaining a request identifier corresponding to the recharge request; Determining the number of occurrences of the request identifier within the first preset time range; When the number of occurrences is greater than 1, determining that the recharge request fails the first verification method; When the number of occurrences is less than or equal to 1, it is determined that the recharge request passes the first verification method.

5. The method according to claim 1, characterized in that Verifying the recharge request by a second verification method includes: Determining a service processing status of the recharge request; When the service processing status indicates that the recharge request has been processed, determining that the recharge request has not passed the second verification method; When the service processing status indicates that the recharge request has not been processed, it is determined that the recharge request passes the second verification method.

6. The method according to claim 1, characterized in that The digital human customer service system communicates with the operator system through an electronic channel interface, and the electronic channel interface is an electronic channel interface that supports the online business operations of the digital human customer service system.

7. The method according to claim 6, characterized in that If the payment result has not been received within the second preset time range, the method further includes: Generate a query request corresponding to the recharge order; Sending the query request to the electrical channel interface, and receiving response information returned by the electrical channel interface; The business processing result of the recharge order is determined according to the response information.

8. A mobile payment device, characterized in that: Applied to Digital Human Customer Service System, including: A receiving module, used for receiving a recharge request from a target object; a verification module, configured to verify the recharge request by a first verification method, and verify the recharge request by a second verification method if the recharge request passes the first verification method, wherein the first verification method is used to ensure that the same recharge request is not submitted repeatedly within a first preset time range, and the second verification method is used to ensure that the same recharge request is not subjected to repeated payment operations; A creation module, configured to create a recharge order if the recharge request passes the second verification method; The return module is used to receive the payment result corresponding to the recharge order and return the payment result to the recharge interface where the target object is located.

9. An electronic device, characterized in that: include: A memory and a processor, wherein the memory is used to store program instructions; The processor is connected to the memory and is used to execute the mobile payment method described in any one of claims 1 to 7.

10. A non-volatile storage medium, characterized in that: The non-volatile storage medium includes a stored computer program, wherein the device where the non-volatile storage medium is located executes the mobile payment method described in any one of claims 1 to 7 by running the computer program.

11. A computer program product comprising computer instructions, characterized in that: When the computer instructions are executed by the processor, the mobile payment method described in any one of claims 1 to 7 is implemented.

Images