Business processing method and device, electronic equipment and computer readable medium
By performing verification and authorization identification generation of user identification, wallet identification and entity identification in the wallet service, the problem of insufficient security during the transmission process is solved, and the security of transactions and user rights protection is achieved.
Patent Information
- Application Number
- CN202411200656.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-29
- Publication Date
- 2024-12-06
AI Technical Summary
When using wallet services, customer passwords cannot be secure during transmission, and they cannot fully trust the protection of passwords by interbank cooperation institutions.
By responsive to the wallet call request, obtaining the user ID, wallet ID and entity ID, performing the origin verification and secondary confirmation process, generating an authorization ID, and initiating a transaction request based on the authorization ID, ensuring the security of the password during the transmission process.
It effectively ensures the security of user passwords during the transmission process, ensures transaction security, and avoids password leakage and unauthorized transactions.
Smart Images

Figure CN119090640A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of computer technology, and in particular to a business processing method, device, electronic device and computer-readable medium. Background Art
[0002] When clients of interbank cooperative institutions provide wallet services to customers on the preset institution's application, they need to call the API of the interbank ecosystem to implement it. If a password is used to verify the customer's identity, the customer performs business operations on the system of the interbank institution, and the password needs to be transmitted through the cooperative bank. This results in the customer's password being exposed to the interbank cooperative institutions. Because the protection of the customer's password by the interbank cooperative institutions cannot be fully trusted, the security of the customer's password during the transmission process cannot be guaranteed. Summary of the invention
[0003] In view of this, the embodiments of the present application provide a business processing method, device, electronic device and computer-readable medium, which can solve the existing problem that the security of the customer password cannot be guaranteed during the transmission process when using wallet services.
[0004] To achieve the above objective, according to one aspect of an embodiment of the present application, a service processing method is provided, including:
[0005] In response to the wallet call request, obtain the corresponding user identifier, wallet identifier and entity identifier;
[0006] Performing an origin verification process based on the user identification and the wallet identification, and in response to the verification being successful, performing a secondary confirmation process;
[0007] In response to the second confirmation being passed, executing an authorization binding process to bind the user ID, the wallet ID, and the entity ID, thereby generating an authorization ID;
[0008] Initiate a transaction request based on the user ID, wallet ID and authorization ID.
[0009] Optionally, after initiating a transaction request based on the user identifier, wallet identifier and authorization identifier, the method is further configured to:
[0010] The verification program is called to verify the corresponding secondary confirmation information and user identification based on the transaction request. In response to the verification being successful, validity period data corresponding to the authorization identification is generated and returned.
[0011] Optionally, the business processing method is further configured to:
[0012] In response to the unbinding authorization request, obtain the corresponding unbinding user identifier, unbinding wallet identifier and unbinding authorization identifier;
[0013] A binding relationship verification process is performed based on the unbinding authorization identifier. In response to successful verification, the binding relationship between the unbinding user identifier, the unbinding wallet identifier and the unbinding authorization identifier is released, and the unbinding result data is returned.
[0014] Optionally, after initiating a transaction request based on the user identifier, wallet identifier and authorization identifier, the method is further configured to:
[0015] The verification program is called to obtain validity period data corresponding to the authorization identifier, and in response to the validity period data corresponding to expiration, the processing of the transaction request is terminated.
[0016] Optionally, a secondary confirmation process is performed, configured to:
[0017] Sending a first SMS verification code to a user terminal corresponding to the user identifier;
[0018] Get the second SMS verification code input by the user, and determine whether the first SMS verification code and the second SMS verification code are consistent. If so, the second confirmation is passed, otherwise the second confirmation fails.
[0019] Optionally, generate an authorization token, configured as:
[0020] Assembling the user identifier, the wallet identifier and the entity identifier to generate an assembled identifier;
[0021] Calculate the hash value corresponding to the assembly identifier, and then determine the hash value as the authorization identifier.
[0022] Optionally, performing an origin verification process based on the user identification and the wallet identification is configured to:
[0023] Determine the user identifier bound to the wallet identifier, match the bound user identifier with the user identifier, and in response to a successful match, determine that the verification is successful.
[0024] In addition, the present application also provides a service processing device, including:
[0025] An acquisition unit, configured to acquire corresponding user identification, wallet identification and entity identification in response to a wallet call request;
[0026] A verification unit configured to perform an origin verification process based on the user identification and the wallet identification, and in response to passing the verification, perform a secondary confirmation process;
[0027] An authorization identification generating unit is configured to execute an authorization binding process in response to the passing of the second confirmation to bind the user identification, the wallet identification and the entity identification, and then generate an authorization identification;
[0028] The transaction request initiating unit is configured to initiate a transaction request based on the user identifier, the wallet identifier and the authorization identifier.
[0029] Optionally, the verification unit is further configured to:
[0030] The verification program is called to verify the corresponding secondary confirmation information and user identification based on the transaction request. In response to the verification being successful, validity period data corresponding to the authorization identification is generated and returned.
[0031] Optionally, the device further includes a deauthorization binding unit configured to:
[0032] In response to the unbinding authorization request, obtain the corresponding unbinding user identifier, unbinding wallet identifier and unbinding authorization identifier;
[0033] A binding relationship verification process is performed based on the unbinding authorization identifier. In response to successful verification, the binding relationship between the unbinding user identifier, the unbinding wallet identifier and the unbinding authorization identifier is released, and the unbinding result data is returned.
[0034] Optionally, the verification unit is further configured to:
[0035] The verification program is called to obtain validity period data corresponding to the authorization identifier, and in response to the validity period data corresponding to expiration, the processing of the transaction request is terminated.
[0036] Optionally, the verification unit is further configured to:
[0037] Sending a first SMS verification code to a user terminal corresponding to the user identifier;
[0038] Get the second SMS verification code input by the user, and determine whether the first SMS verification code and the second SMS verification code are consistent. If so, the second confirmation is passed, otherwise the second confirmation fails.
[0039] Optionally, the authorization identification generation unit is further configured to:
[0040] Assembling the user identifier, the wallet identifier and the entity identifier to generate an assembled identifier;
[0041] Calculate the hash value corresponding to the assembly identifier, and then determine the hash value as the authorization identifier.
[0042] Optionally, the verification unit is further configured to:
[0043] Determine the user identifier bound to the wallet identifier, match the bound user identifier with the user identifier, and in response to a successful match, determine that the verification is successful.
[0044] In addition, the present application also provides a business processing electronic device, including: one or more processors; a storage device for storing one or more programs, when the one or more programs are executed by one or more processors, the one or more processors implement the business processing method as described above.
[0045] In addition, the present application also provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, the business processing method as described above is implemented.
[0046] To achieve the above objective, according to another aspect of the embodiments of the present application, a computer program product is provided.
[0047] A computer program product according to an embodiment of the present application includes a computer program, and when the program is executed by a processor, the business processing method provided by the embodiment of the present application is implemented.
[0048] One embodiment of the above invention has the following advantages or beneficial effects: the present application obtains the corresponding user identification, wallet identification and entity identification by responding to the wallet call request; performs the origin verification process based on the user identification and wallet identification, and performs the secondary confirmation process in response to the verification passing; performs the authorization binding process in response to the secondary confirmation passing to bind the user identification, wallet identification and entity identification, and then generates the authorization identification; initiates the transaction request based on the user identification, wallet identification and authorization identification. Thus, the security of the user password in the transmission process can be guaranteed and the transaction security can be guaranteed.
[0049] The further effects of the above-mentioned non-conventional optional manner will be described below in conjunction with the specific implementation manner. BRIEF DESCRIPTION OF THE DRAWINGS
[0050] The accompanying drawings are used to better understand the present application and do not constitute an improper limitation on the present application.
[0051] Figure 1 is a schematic diagram of the main process of a business processing method according to an embodiment of the present application;
[0052] Figure 2 is a schematic diagram of the main process of a business processing method according to an embodiment of the present application;
[0053] Figure 3 It is a schematic diagram of the authorization process of a business processing method according to an embodiment of the present application;
[0054] Figure 4 is a schematic diagram of a deauthorization process of a business processing method according to an embodiment of the present application;
[0055] Figure 5This is a schematic diagram of an API authorization verification process of a business processing method according to an embodiment of the present application;
[0056] Figure 6 It is a schematic diagram of the execution logic flow when multiple peer cooperation institutions exist according to a business processing method of an embodiment of the present application;
[0057] Figure 7 is a schematic diagram of main units of a service processing device according to an embodiment of the present application;
[0058] Figure 8 is an exemplary system architecture diagram to which the embodiments of the present application can be applied;
[0059] Fig. 9 It is a structural diagram of a computer system of a terminal device or server suitable for implementing an embodiment of the present application. DETAILED DESCRIPTION
[0060] The following is an explanation of the exemplary embodiments of the present application in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding, which should be considered as merely exemplary. Therefore, those of ordinary skill in the art should recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description. It should be noted that in the technical solution of the present application, the collection, analysis, use, transmission, storage and other aspects of user personal information involved are in compliance with the provisions of relevant laws and regulations, are used for legal and reasonable purposes, are not shared, leaked or sold outside of these legal uses, and are subject to supervision and management by regulatory authorities. Necessary measures should be taken for user personal information to prevent illegal access to such personal information data, ensure that persons who have access to personal information data comply with the provisions of relevant laws and regulations, and ensure the security of user personal information. Once these user personal information data are no longer needed, the risk should be minimized by restricting or even prohibiting data collection and / or deleting data.
[0061] When used, including in certain related applications, user privacy is protected by de-identifying data, such as by removing specific identifiers when used, controlling the amount or specificity of data stored, controlling how data is stored, and / or other methods of de-identification.
[0062] Figure 1 is a schematic diagram of the main process of a business processing method according to an embodiment of the present application, such as Figure 1 As shown, the business processing method includes:
[0063] Step S101, in response to a wallet call request, obtaining corresponding user identification, wallet identification and entity identification.
[0064] In this embodiment, the execution subject of the business processing method (for example, it can be a server) can detect whether a wallet call request is received by wired connection or wireless connection. When the execution subject detects the wallet call request, it can obtain the user identifier, wallet identifier and entity identifier carried in the request. Among them, the user identifier can be used to represent the number or user name of the user who calls the wallet. The wallet identifier is used to represent the number or wallet name of the user who calls the wallet. The entity identifier is used to represent the number or name of the third-party organization accessed through the peer ecosystem.
[0065] Step S102, performing an origin verification process based on the user identification and the wallet identification, and in response to the verification being passed, performing a secondary confirmation process.
[0066] The origin verification process is used to verify whether the wallet call request is initiated by the user bound to the wallet, so as to ensure the security of the wallet call.
[0067] Specifically, the origin verification process is performed based on the user identifier and the wallet identifier, including: determining the user identifier bound to the wallet identifier, matching the bound user identifier with the user identifier, and determining that the verification is passed in response to a successful match.
[0068] For example, the user identifier bound to the wallet (such as the user number or user name bound to the wallet) and the user identifier corresponding to the wallet call request (such as the user number or user name bound to the wallet) are matched and verified. When the match is successful, it is determined that the origin verification has passed, that is, the user who initiated the wallet call request and the user bound to the wallet are the same user.
[0069] Step S103, in response to the second confirmation being passed, executing the authorization binding process to bind the user ID, wallet ID and entity ID, and then generating an authorization ID.
[0070] The secondary confirmation can be verified by email or instant software verification message, or it can be verified by SMS. The embodiment of the present application does not specifically limit the method used for the secondary confirmation. After the secondary confirmation is passed, it can be further determined that the user who initiated the wallet call request and the user bound to the wallet are the same user. The execution subject can execute the process of binding the user identification, wallet identification and entity identification, and then generate an authorization identification based on the bound user identification, wallet identification and entity identification.
[0071] Specifically, generating an authorization identifier includes: assembling a user identifier, a wallet identifier, and an entity identifier to generate an assembly identifier; calculating a hash value corresponding to the assembly identifier, and then determining the hash value as the authorization identifier.
[0072] For example, the execution subject can obtain the demand data corresponding to the user identification, determine the priority of the user identification, wallet identification and entity identification based on the demand data, assemble the user identification, wallet identification and entity identification according to the priority (the higher priority is assembled first, and the lower priority is assembled later) to obtain the assembly identification. Call the hash algorithm to convert the assembly identification into the corresponding hash value, and determine the converted hash value as the authorization identification.
[0073] Step S104, initiating a transaction request based on the user ID, wallet ID and authorization ID.
[0074] When it is determined that the wallet call request is initiated by the user bound to the wallet, the execution subject can initiate a transaction request based on the bound user ID, wallet ID and authorization ID.
[0075] Specifically, the business processing method also includes: in response to the unbinding authorization request, obtaining the corresponding unbinding user identifier, unbinding wallet identifier and unbinding authorization identifier; executing the binding relationship verification process based on the unbinding authorization identifier, and in response to successful verification, unbinding the binding relationship between the unbinding user identifier, the unbinding wallet identifier and the unbinding authorization identifier, and returning the unbinding result data.
[0076] After receiving the user's request to unbind the authorization binding, the execution subject can obtain the user ID to be unbound, the wallet ID to be unbound, and the authorization ID to be unbound. Then, the execution subject can verify whether the binding has been performed before based on the authorization ID to be unbound. If so, the verification is successful, and the binding relationship between the user ID to be unbound, the wallet ID to be unbound, and the authorization ID to be unbound is unbound, and the data of success or failure of unbinding is obtained and returned.
[0077] Specifically, after initiating a transaction request based on the user identifier, wallet identifier and authorization identifier, the method further includes: calling a verification program to obtain validity period data corresponding to the authorization identifier, and terminating the processing of the transaction request in response to the validity period data corresponding to expiration.
[0078] When processing the request to release the authorization binding, the execution subject first verifies whether the corresponding authorization identifier has been bound in the past. If so, it continues to verify the validity, that is, calling the verification program to obtain the validity data corresponding to the authorization identifier, determine the corresponding validity start time and the corresponding validity end time. When the current time is not between the validity start time and the validity end time, it indicates that the validity data has expired, and the processing of the transaction request is terminated; when the current time is between the validity start time and the validity end time, it indicates that the validity data has not expired, and the binding relationship corresponding to the wallet identifier and the entity identifier is released for the corresponding user.
[0079] This embodiment obtains the corresponding user ID, wallet ID and entity ID by responding to the wallet call request; performs the origin verification process based on the user ID and wallet ID, and performs the secondary confirmation process in response to the verification passing; performs the authorization binding process in response to the secondary confirmation passing to bind the user ID, wallet ID and entity ID, and then generates the authorization ID; initiates the transaction request based on the user ID, wallet ID and authorization ID. Thus, the security of the user password in the transmission process and the transaction security can be guaranteed.
[0080] Figure 2 is a main flow chart of a business processing method according to an embodiment of the present application, such as Figure 2 As shown, the business processing method includes:
[0081] Step S201, in response to a wallet call request, obtaining corresponding user identification, wallet identification and entity identification.
[0082] Step S202, performing an origin verification process based on the user identification and the wallet identification, and in response to the verification being passed, performing a secondary confirmation process.
[0083] Specifically, executing the secondary confirmation process includes: sending a first SMS verification code to the user terminal corresponding to the user identifier; obtaining a second SMS verification code input by the user, and determining whether the first SMS verification code and the second SMS verification code are consistent. If so, the secondary confirmation passes, otherwise the secondary confirmation fails.
[0084] When the secondary confirmation method is to confirm via SMS, the execution subject can call the SMS sending program to send a first SMS verification code, such as 0335, to the user terminal corresponding to the user identifier. After the user terminal receives the SMS verification code, it can input the received SMS verification code into the verification code input box. The SMS verification code input by the user is the second SMS verification code, such as 0335 or 0334. The first SMS verification code and the second SMS verification code are compared to determine whether they are consistent. If the second SMS verification code is 0335, the first SMS verification code and the second SMS verification code are consistent, and the secondary confirmation is passed. If the second SMS verification code is 0334, the first SMS verification code and the second SMS verification code are inconsistent, and the secondary confirmation is not passed.
[0085] Step S203, in response to the second confirmation being passed, executing the authorization binding process to bind the user ID, wallet ID and entity ID, and then generating an authorization ID.
[0086] Step S204, initiating a transaction request based on the user ID, wallet ID and authorization ID.
[0087] Step S205, calling the verification program to verify the corresponding secondary confirmation information and user identification based on the transaction request, and in response to the verification being successful, generating and returning validity period data corresponding to the authorization identification.
[0088] For example, after receiving the wallet call request, the execution subject can verify the secondary confirmation information, such as the SMS verification code, and verify the user ID in the obtained user information. When the secondary confirmation information and the user ID are both verified, that is, the SMS verification code of the secondary confirmation information is successfully verified, and the user ID is also the user ID of the user bound to the wallet corresponding to the wallet call request, the validity period generation model can be called to generate the corresponding validity period data based on the authorization identifier and return it. The execution subject can also determine the type of the authorization identifier to determine the validity period data corresponding to the authorization identifier based on the type. Specifically, determining the validity period data corresponding to the authorization identifier based on the type includes:
[0089] The type is matched with the type data in the type database to determine the matching type data from the type database, and the validity period data corresponding to the matching type data is determined as the validity period data corresponding to the authorization identifier. Thus, a more accurate verification can be performed based on the determined validity period data, thereby making the relevant transactions more secure.
[0090] Figure 3 It is a schematic diagram of the authorization process of the business processing method according to an embodiment of the present application. Inter-industry cooperation institution: a third-party institution accessed through the inter-industry ecosystem. Authorization identification, such as authorization code: the authorization binding identification established by the customer wallet and the inter-industry cooperation institution in the inter-industry ecosystem. The customer can only initiate wallet-related transactions to the inter-industry ecosystem through this institution after the inter-industry cooperation institution initiates wallet authorization. When the customer of the inter-industry cooperation institution uses the wallet through the inter-industry ecosystem, the customer first needs to initiate authorization on the side of the inter-industry cooperation institution. The inter-industry cooperation institution sends the authorization binding relationship to the inter-industry ecosystem for verification. The inter-industry ecosystem will initiate a second confirmation of the SMS verification code to the customer to ensure that it was initiated by the customer himself. After receiving the SMS verification code, the customer submits again to confirm the binding relationship. The execution subject of the embodiment of the present application may include inter-industry cooperation institutions and inter-industry ecosystems, and related business processing is performed by calling inter-industry cooperation institutions and inter-industry ecosystems.
[0091] For example, Figure 3As shown, the wallet user submits a wallet authorization binding application to the interbank cooperation institution. The interbank cooperation institution calls the wallet authorization binding interface to send the customer information and wallet information for identity authentication. The interbank ecosystem performs identity authentication and sends a text message verification code to the wallet user. Then, the interbank cooperation institution returns a message that the authorization text message verification code has been sent to the interbank cooperation institution. The interbank cooperation institution sends a notification to the wallet user to inform the customer that the authorization text message verification code has been sent. The customer receives the text message verification code, fills in the text message verification code, and submits the wallet authorization binding application to the interbank cooperation institution again. The interbank cooperation institution calls the wallet authorization binding interface for text message verification + authorization binding. The interbank ecosystem verifies the text message verification and generates an authorization Token, that is, generates an authorization code, and returns an authorization binding success message to the interbank cooperation institution. The message may include the authorization Token, the authorization start date, and the authorization end date. The interbank cooperation institution returns an authorization binding success message to the wallet user.
[0092] For example, the authorization binding process is as follows:
[0093] 1. Obtain the SMS verification code for authorization binding
[0094] 1) The customer initiates the wallet authorization binding application, and the application is first sent to the backend system of the peer cooperation institution.
[0095] 2) After receiving the customer's application, the peer cooperation institution calls the peer ecosystem to initiate wallet third-party authorization binding, and the request includes customer information and wallet information.
[0096] 3) The peer ecosystem verifies the customer information after receiving the request, and sends a confirmation SMS verification code to the customer after successful verification.
[0097] 2. Complete authorization binding
[0098] 4) The customer receives the SMS verification code and submits the authorization binding application again after completing the input.
[0099] 5) After receiving the customer's request, the interbank cooperative institution will once again initiate the customer wallet authorization binding to the interbank ecosystem, submit the customer information, wallet information and SMS verification code. After the interbank ecosystem completes the verification, an authorization binding relationship will be established between the customer and the cooperative institution.
[0100] After receiving the authorization binding confirmation from the customer and verifying it successfully, the interbank ecosystem will establish a binding relationship between the customer and the interbank partner and return the binding authorization code to the interbank partner. The interbank partner will save the authorization binding code after receiving it. For all subsequent transactions initiated by the customer through this partner, the partner must also carry the customer's authorization code to initiate transactions to the interbank ecosystem.
[0101] After receiving the request, the interbank ecosystem verifies the SMS verification code and customer information. After successful verification, it generates a binding authorization code and sets the validity period of the authorization code and returns it to the interbank partner. The interbank partner stores the customer's authorization code and returns the authorization binding success to the customer. The customer can initiate the cancellation of the authorization binding relationship at any time at the interbank partner. After the authorization binding relationship is cancelled, the customer can no longer initiate wallet-related services through this institution.
[0102] Figure 4 FIG. 1 is a schematic diagram of a deauthorization process of a service processing method according to an embodiment of the present application. Figure 4 As shown, the process of unbinding authorization is as follows:
[0103] 1) Customers can submit wallet deauthorization binding applications to peer cooperative institutions. The applications will first be sent to the backend system of the peer cooperative institution.
[0104] 2) After receiving the customer's application, the peer cooperation institution calls the wallet deauthorization interface of the peer ecosystem to initiate the unbinding of wallet authorization, and the request includes customer information, wallet information and wallet authorization token (ie, authorization code).
[0105] 3) The interbank ecosystem first verifies the authorization code, verifies whether it is the binding relationship between the customer and the current interbank institution and verifies the validity based on the authorization code, and then verifies the customer information and wallet information. After all verifications are successful, the authorization binding relationship between the customer and the current interbank institution is released, and the customer is notified that the authorization binding relationship has been released.
[0106] Figure 5 FIG. 1 is a schematic diagram of an API authorization verification process of a business processing method according to an embodiment of the present application. Figure 5 As shown in the figure, when a customer initiates a wallet-related business on the system of a peer partner institution, the partner institution needs to carry the customer's authorization code to initiate a transaction to the peer ecosystem. The peer ecosystem will first verify the validity of the authorization code, including whether it is a binding relationship with the current initiating institution, the validity period of the authorization code, and whether it has expired. Only after the verification is passed can the relevant wallet transaction be truly initiated. Failure of verification means that the customer has not authorized the institution, and it is impossible to initiate a wallet transaction to the peer ecosystem through the institution. The customer needs to complete the authorization binding first to ensure the security of the customer's transaction.
[0107] The API authorization verification process is as follows:
[0108] 1) When a customer initiates a wallet-related transaction request on the APP of a peer-to-peer partner institution, the request is submitted to the backend system of the peer-to-peer partner institution.
[0109] 2) After receiving the customer's request, the interbank cooperative institution obtains the necessary transfer information and the customer wallet authorization code when the customer authorizes, and calls the wallet-related transaction interface of the interbank ecosystem together with the customer's request information to initiate a transaction request.
[0110] 3) After receiving the request, the interbank ecosystem performs authorization code validity verification, business parameter verification, and business processing. Specifically, it first verifies whether the authorization code is the binding relationship and validity period between the customer and the current interbank cooperation channel, and continues business processing after successful verification. If the authorization code verification fails, no business processing will be performed, and an error message will be directly returned. Then, the interbank ecosystem returns the processing information to the interbank cooperation institution, and the interbank cooperation institution sends a notification to the wallet user to inform the customer of the processing result.
[0111] Figure 6 It is a schematic diagram of the execution logic flow when multiple inter-bank cooperative institutions exist according to the business processing method of an embodiment of the present application. At the same time, a customer may have wallet services in multiple inter-bank cooperative institutions (for example, inter-bank cooperative institution A and inter-bank cooperative institution B). The inter-bank ecosystem adopts the method of authorization isolation between institutions to solve this situation. The customer needs to complete the authorization for each inter-bank cooperative institution separately before performing wallet-related business operations in the corresponding institution. For example, when a user needs to use the wallet function in inter-bank cooperative institution A (or B), it is necessary to call the inter-bank ecosystem to perform a separate authorization verification based on the identification of institution A (or B) and the authorization code A (or B). Only after the separate authorization verification is passed can the wallet function be used in inter-bank cooperative institution A (or B). Similarly, when the customer releases the binding relationship with the inter-bank cooperative institution, it is also necessary to perform the release operation for each institution separately. Thereby, each inter-bank cooperative institution that has related wallet services with the same customer does not affect each other when using the wallet function, thereby improving transaction security.
[0112] In the embodiment of the present application, when the customer operates the wallet to process business, he no longer needs to enter the password for verification, which ensures that the customer's password information will not be exposed to the peer cooperation institution, nor will it be leaked during the interface transmission process. The wallet operated by the customer is not opened by the peer cooperation institution. The customer authorizes the peer cooperation institution by himself. At the same time, the peer ecosystem will authorize and verify all wallet transactions of the peer cooperation institution to ensure that all transactions initiated by the peer institution have been authorized by the customer. When a customer has wallet business in multiple peer institutions, he must authorize each peer institution separately, which ensures that the authorization is independent when the customer operates his wallet in different institutions. When the customer of the peer cooperation institution uses wallet-related services on the system of the institution, the authorization verification scheme used will not expose the customer's password information to the peer cooperation institution, and it also ensures that it is the customer's own behavior. The execution subject of the scheme of the embodiment of the present application involves the three parties of the client of the peer cooperation institution, the peer cooperation institution and the peer ecosystem. When a customer initiates a wallet service at a peer partner institution, he must initiate authorization binding to the peer ecosystem through the peer partner institution. The peer ecosystem establishes an authorization binding relationship between the customer and the partner institution to authorize the partner institution to provide wallet-related business functions to the customer. After the peer partner institution sends the customer's business request to the peer ecosystem, the customer's right to know and the security of the transaction are guaranteed by verifying the authenticity and validity of the authorization code. Customers can have wallet services at multiple partner institutions that have been connected to the peer ecosystem at the same time. The peer ecosystem ensures the uniqueness of customer authorization by isolating the institution codes between each institution. Customers authorize and deauthorize each institution independently. By allowing the customer to initiate authorization themselves, the peer ecosystem establishes a binding relationship between the customer and the peer partner institution to ensure that customer transactions initiated through the institution have been authorized by the customer. It also prevents the peer partner institution from obtaining and operating the customer's wallet information without the customer's consent. The customer's authorization code is independent for different peer partners. The customer must re-initiate authorization binding when operating a wallet at different peer partners. Customers can cancel the binding relationship with the peer partner at any time. After the binding relationship is canceled, customers cannot initiate related business through this institution, and the peer partner has no authority to operate the customer's wallet information. The cancellation of authorization of any peer institution will not have any impact on the customer's wallet business in other peer institutions.
[0113] Figure 7 Schematic diagram of the main units of the service processing device according to an embodiment of the present application. Figure 7 As shown, the business processing device 700 includes an acquisition unit 701 , a verification unit 702 , an authorization identification generation unit 703 and a transaction request initiation unit 704 .
[0114] The acquisition unit 701 is configured to acquire the corresponding user identifier, wallet identifier and entity identifier in response to the wallet call request.
[0115] The verification unit 702 is configured to perform an origin verification process based on the user identification and the wallet identification, and in response to the verification being passed, perform a secondary confirmation process.
[0116] The authorization identification generating unit 703 is configured to execute the authorization binding process in response to the passing of the second confirmation to bind the user identification, the wallet identification and the entity identification, and then generate the authorization identification.
[0117] The transaction request initiating unit 704 is configured to initiate a transaction request based on the user identifier, the wallet identifier and the authorization identifier.
[0118] In some embodiments, the verification unit 702 is further configured to: call a verification program to verify the corresponding secondary confirmation information and user identification based on the transaction request, and in response to successful verification, generate and return validity period data corresponding to the authorization identification.
[0119] In some embodiments, the service processing device further includes Figure 7 The unbinding authorization unit not shown in the figure is configured to: in response to the unbinding authorization request, obtain the corresponding unbinding user identifier, unbinding wallet identifier and unbinding authorization identifier; perform a binding relationship verification process based on the unbinding authorization identifier, and in response to successful verification, unbind the binding relationship between the unbinding user identifier, unbinding wallet identifier and unbinding authorization identifier, and return unbinding result data.
[0120] In some embodiments, the verification unit 702 is further configured to: call a verification program to obtain validity period data corresponding to the authorization identifier, and terminate the processing of the transaction request in response to the validity period data corresponding to expiration.
[0121] In some embodiments, the verification unit 702 is further configured to: send a first SMS verification code to a user terminal corresponding to the user identifier; obtain a second SMS verification code entered by the user, and determine whether the first SMS verification code and the second SMS verification code are consistent, if so, the second confirmation is passed, otherwise the second confirmation fails.
[0122] In some embodiments, the authorization identifier generation unit 703 is further configured to: assemble the user identifier, the wallet identifier, and the entity identifier to generate an assembly identifier; calculate a hash value corresponding to the assembly identifier, and then determine the hash value as the authorization identifier.
[0123] In some embodiments, the verification unit 702 is further configured to: determine the user identifier bound to the wallet identifier, match the bound user identifier with the user identifier, and determine that the verification is successful in response to a successful match.
[0124] It should be noted that the business processing method and the business processing device of the present application have a corresponding relationship in terms of specific implementation content, so the repeated content will not be described again.
[0125] Figure 8 An exemplary system architecture 800 to which the service processing method or service processing device according to the embodiment of the present application can be applied is shown.
[0126] like Figure 8 As shown, system architecture 800 may include terminal devices 801, 802, 803, a network 804, and a server 805. Network 804 is used to provide a medium for communication links between terminal devices 801, 802, 803 and server 805. Network 804 may include various connection types, such as wired, wireless communication links, or optical fiber cables, etc.
[0127] Users can use terminal devices 801, 802, and 803 to interact with server 805 through network 804 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 801, 802, and 803, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social platform software, etc. (only examples).
[0128] The terminal devices 801 , 802 , and 803 may be various electronic devices having a service processing screen and supporting web browsing, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, and the like.
[0129] Server 805 can be a server that provides various services, such as a background management server that provides support for wallet call requests received by users using terminal devices 801, 802, and 803 (only as an example). The background management server can respond to the wallet call request and obtain the corresponding user identification, wallet identification, and entity identification; perform the origin verification process based on the user identification and wallet identification, and perform the secondary confirmation process in response to the verification passing; perform the authorization binding process in response to the secondary confirmation passing to bind the user identification, wallet identification, and entity identification, and then generate an authorization identification; initiate a transaction request based on the user identification, wallet identification, and authorization identification. This can ensure the security of the user password during the transmission process and the transaction security.
[0130] It should be noted that the business processing method provided in the embodiment of the present application is generally executed by the server 805 , and accordingly, the business processing device is generally set in the server 805 .
[0131] It should be understood that Figure 8The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.
[0132] Reference below Fig. 9 , which shows a schematic diagram of the structure of a computer system 900 of a terminal device suitable for implementing an embodiment of the present application. Fig. 9 The terminal device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0133] like Fig. 9 As shown, the computer system 900 includes a central processing unit (CPU) 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage part 908 into a random access memory (RAM) 903. In the RAM 903, various programs and data required for the operation of the computer system 900 are also stored. The CPU 901, the ROM 902, and the RAM 903 are connected to each other through a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.
[0134] The following components are connected to the I / O interface 905: an input section 906 including a keyboard, a mouse, etc.; an output section 907 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 908 including a hard disk, etc.; and a communication section 909 including a network interface card such as a LAN card, a modem, etc. The communication section 909 performs communication processing via a network such as the Internet. A drive 910 is also connected to the I / O interface 905 as needed. A removable medium 911, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 910 as needed, so that a computer program read therefrom is installed into the storage section 908 as needed.
[0135] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 909, and / or installed from the removable medium 911. When the computer program is executed by the central processing unit (CPU) 901, the above-mentioned functions defined in the system of the present application are executed.
[0136] It should be noted that the computer-readable medium shown in the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. Computer-readable storage media may include, for example, but are not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.
[0137] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the above-mentioned module, program segment or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0138] The units involved in the embodiments described in the present application may be implemented by software or hardware. The units described may also be set in a processor, for example, it may be described as: a processor includes an acquisition unit, a verification unit, an authorization identification generation unit, and a transaction request initiation unit. The names of these units do not, in some cases, constitute limitations on the units themselves.
[0139] As another aspect, the present application also provides a computer-readable medium, which may be included in the device described in the above embodiment; or it may exist independently without being assembled into the device. The above computer-readable medium carries one or more programs. When the above one or more programs are executed by a device, the device responds to a wallet call request, obtains the corresponding user identification, wallet identification and entity identification; executes an origin verification process based on the user identification and wallet identification, and executes a secondary confirmation process in response to the verification passing; executes an authorization binding process in response to the secondary confirmation passing to bind the user identification, wallet identification and entity identification, and then generates an authorization identification; initiates a transaction request based on the user identification, wallet identification and authorization identification.
[0140] The computer program product of the present application includes a computer program, and when the computer program is executed by a processor, the business processing method in the embodiment of the present application is implemented.
[0141] According to the technical solution of the embodiment of the present application, the security of the user password during the transmission process can be guaranteed and the transaction security can be guaranteed.
[0142] The above specific implementations do not constitute a limitation on the protection scope of this application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may occur depending on design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of this application should be included in the protection scope of this application.
Claims
1. A business processing method, characterized in that: include: In response to the wallet call request, obtain the corresponding user identifier, wallet identifier and entity identifier; Performing an origin verification process based on the user identifier and the wallet identifier, and in response to the verification being successful, performing a secondary confirmation process; In response to the second confirmation being passed, executing an authorization binding process to bind the user identifier, the wallet identifier, and the entity identifier, thereby generating an authorization identifier; A transaction request is initiated based on the user identifier, the wallet identifier, and the authorization identifier.
2. The method according to claim 1, characterized in that After initiating the transaction request based on the user identifier, the wallet identifier and the authorization identifier, the method further includes: A verification program is called to verify the corresponding secondary confirmation information and user identification based on the transaction request, and in response to the verification being successful, validity period data corresponding to the authorization identification is generated and returned.
3. The method according to claim 1, characterized in that The method further comprises: In response to the unbinding authorization request, obtain the corresponding unbinding user identifier, unbinding wallet identifier and unbinding authorization identifier; A binding relationship verification process is performed based on the unbinding authorization identifier. In response to successful verification, the binding relationship between the unbinding user identifier, the unbinding wallet identifier and the unbinding authorization identifier is released, and unbinding result data is returned.
4. The method according to claim 2, characterized in that: After initiating the transaction request based on the user identifier, the wallet identifier and the authorization identifier, the method further includes: A verification program is called to obtain validity period data corresponding to the authorization identifier, and in response to the validity period data corresponding to expiration, the processing of the transaction request is terminated.
5. The method according to claim 1, characterized in that: The performing of the secondary confirmation process includes: Sending a first SMS verification code to a user terminal corresponding to the user identifier; Obtain the second SMS verification code input by the user, and determine whether the first SMS verification code and the second SMS verification code are consistent. If so, the second confirmation is passed, otherwise the second confirmation fails.
6. The method according to claim 1, characterized in that The generating of the authorization identifier comprises: Assembling the user identifier, the wallet identifier and the entity identifier to generate an assembled identifier; A hash value corresponding to the assembly identifier is calculated, and the hash value is then determined as the authorization identifier.
7. The method according to claim 1, characterized in that The performing of the origin verification process based on the user identifier and the wallet identifier includes: Determine a user identifier bound to the wallet identifier, match the bound user identifier with the user identifier, and determine that the verification is successful in response to a successful match.
8. A service processing device, characterized in that: include: An acquisition unit, configured to acquire corresponding user identification, wallet identification and entity identification in response to a wallet call request; a verification unit configured to perform an origin verification process based on the user identifier and the wallet identifier, and in response to passing the verification, perform a secondary confirmation process; an authorization identification generating unit, configured to execute an authorization binding process in response to the passing of the secondary confirmation, so as to bind the user identification, the wallet identification and the entity identification, and then generate an authorization identification; The transaction request initiating unit is configured to initiate a transaction request based on the user identifier, the wallet identifier and the authorization identifier.
9. The device according to claim 8, characterized in that The verification unit is further configured to: A verification program is called to verify the corresponding secondary confirmation information and user identification based on the transaction request, and in response to the verification being successful, validity period data corresponding to the authorization identification is generated and returned.
10. The device according to claim 8, characterized in that The device also includes a deauthorization binding unit configured to: In response to the unbinding authorization request, obtain the corresponding unbinding user identifier, unbinding wallet identifier and unbinding authorization identifier; A binding relationship verification process is performed based on the unbinding authorization identifier. In response to successful verification, the binding relationship between the unbinding user identifier, the unbinding wallet identifier and the unbinding authorization identifier is released, and unbinding result data is returned.
11. The device according to claim 9, characterized in that The verification unit is further configured to: A verification program is called to obtain validity period data corresponding to the authorization identifier, and in response to the validity period data corresponding to expiration, the processing of the transaction request is terminated.
12. The device according to claim 8, characterized in that The verification unit is further configured to: Sending a first SMS verification code to a user terminal corresponding to the user identifier; Obtain the second SMS verification code input by the user, and determine whether the first SMS verification code and the second SMS verification code are consistent. If so, the second confirmation is passed, otherwise the second confirmation fails.
13. The device according to claim 8, characterized in that The authorization identification generating unit is further configured to: Assembling the user identifier, the wallet identifier and the entity identifier to generate an assembled identifier; A hash value corresponding to the assembly identifier is calculated, and the hash value is then determined as the authorization identifier.
14. A business processing electronic device, characterized in that: include: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1 to 7.
15. A computer readable medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.
16. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.
