Method, apparatus and device for processing based on user cancellation

Abstract

The application provides a processing method, device and equipment based on user cancellation, which can be used in the financial field or other fields. The method comprises the following steps: in response to a cancellation processing request initiated by a first device, verifying the cancellation processing request; if it is determined that the verification of the cancellation processing request is passed, generating cancellation information corresponding to the cancellation processing request; if a periodic deduction request initiated by a second device is received, querying a cancellation list in response to the periodic deduction request initiated by the second device; if it is determined that the cancellation information in the cancellation list matches the merchant identifier and the user identifier carried by the periodic deduction request, it is determined that the transaction process corresponding to the periodic deduction request is rejected, and the first feedback information is sent to the second device. The method of the application guarantees the rights and interests of the customers and improves the satisfaction of the customers.

Description

Technical Field

[0001] This application relates to the financial field or other fields, and in particular to a method, apparatus, and device for processing user-based contract cancellation. Background Technology

[0002] With the development of information technology, banking transactions need to be processed through online systems. These online systems provide users with a recurring deduction service. After a recurring deduction agreement is established between the user's bank card and the merchant's device, the merchant's device can periodically send a recurring deduction request to the bank's server to request deductions from the user's bank card.

[0003] In existing technology, a user can request to cancel the service for recurring deduction transactions; the user's device initiates a cancellation request to the merchant's device; after receiving the cancellation request from the user's device, the merchant's device needs to process the cancellation based on the merchant's trigger, and then after the merchant agrees to the cancellation, the merchant's device sends the cancellation agreement information to the bank's server; only then can the bank's server stop automatically deducting money from the user's bank card.

[0004] However, in the existing technology, when a user requests to cancel the service of recurring deductions, if the merchant refuses to agree to the cancellation or the merchant misses the cancellation request initiated by the user, the bank's server will continue to deduct money from the user's bank card periodically, resulting in financial losses for the user. Summary of the Invention

[0005] This application provides a method, apparatus, and device for processing user cancellations, in order to solve the problem that the bank's server will still periodically deduct money from the user's bank card when the user requests to cancel the service for recurring deduction transactions.

[0006] Firstly, this application provides a method for handling user-terminated contracts, including:

[0007] In response to a cancellation request initiated by a first device, the cancellation request is verified; wherein, the cancellation request includes a merchant identifier and a user identifier, the cancellation request represents a request to unbind the user account corresponding to the user identifier from the merchant account corresponding to the merchant identifier, the first device is the user's device; the user identifier is a unique user identifier and / or the user's bank card number; the merchant identifier is the terminal number of a second device; the second device is the merchant's device;

[0008] If the verification of the cancellation request is successful, cancellation information corresponding to the cancellation request is generated.

[0009] If a scheduled deduction request initiated by a second device is received, the system responds by querying the cancellation list. The scheduled deduction request is initiated periodically based on a preset date and includes a merchant identifier and a user identifier. The cancellation list includes at least one cancellation message, indicating that the user account corresponding to the user identifier is unbound from the merchant account corresponding to the merchant identifier. The cancellation message includes both the merchant identifier and the user identifier.

[0010] If it is determined that there is a cancellation information in the cancellation list that matches both the merchant identifier and the user identifier carried in the periodic deduction request, then it is determined that the transaction process corresponding to the periodic deduction request will be rejected, and a first feedback information is sent to the second device; wherein, the first feedback information indicates that the user account corresponding to the user identifier in the periodic deduction request has been cancelled.

[0011] In one possible implementation, the cancellation request includes location information; the location information includes any one of the following: the geographical location information of the first device, the IP address information of the first device, and the International Mobile Equipment Identity (IMEI) of the first device.

[0012] In response to a cancellation request initiated by the first device, the cancellation request is verified, including:

[0013] In response to a cancellation request initiated by a first device, user login information corresponding to the first device is determined; wherein, the user login information includes the user identifier and location information corresponding to a historical moment, the historical moment being the moment when the first device issued a historical cancellation request or a historical contract processing request, the contract processing request being used to request a contract processing for periodic deductions;

[0014] If it is determined that the user login information includes the location information in the cancellation request, then the verification of the cancellation request is determined to be successful; if it is determined that the user login information does not include the location information in the cancellation request, then the verification of the cancellation request is determined to be unsuccessful. Alternatively, if it is determined that the user login information includes the location information in the cancellation request, and the number of times the location information in the cancellation request is included in the user login information is greater than a first preset number, then the verification of the cancellation request is determined to be successful; if it is determined that the user login information includes the location information in the cancellation request, and the number of times the location information is included in the cancellation request is less than or equal to the first preset number, then the verification of the cancellation request is determined to be unsuccessful.

[0015] In one possible implementation, in response to a cancellation request initiated by the first device, the cancellation request is verified, including:

[0016] In response to the cancellation request initiated by the first device, a verification request is sent to the first device;

[0017] The device receives verification information sent by the first device; wherein the verification information includes one or more of the following: user name, user bank card expiration date, facial information, and fingerprint information.

[0018] If it is determined that the received verification information is consistent with the pre-stored verification information, then the verification of the cancellation request is deemed successful.

[0019] If the received verification information is determined to be inconsistent with the pre-stored verification information, then the verification of the cancellation request is determined to be unsuccessful.

[0020] In one possible implementation, in response to a cancellation request initiated by the first device, the cancellation request is verified, including:

[0021] In response to the cancellation request initiated by the first device, the mobile phone number corresponding to the first device is determined;

[0022] Send a first verification code to the device with the mobile phone number corresponding to the first device;

[0023] If it is determined that a second verification code sent by a device to the mobile phone number is received within a first preset time period, and the second verification code is consistent with the first verification code, then it is determined that the verification of the cancellation request has passed.

[0024] If it is determined that the second verification code sent by the device of the mobile phone number is not received within the first preset time period, and / or the second verification code is inconsistent with the first verification code, then it is determined that the verification of the cancellation processing request fails.

[0025] In one possible implementation, before determining to refuse to execute the transaction process corresponding to the periodic deduction request if it is determined that there is a cancellation information in the cancellation list that matches both the merchant identifier and the user identifier carried in the periodic deduction request, the method further includes:

[0026] If it is determined that the contract information list includes contract information that corresponds to both the user identifier and the merchant identifier in the cancellation processing request, then the step of determining to refuse to execute the transaction process corresponding to the periodic deduction request is executed if it is determined that there is cancellation information in the cancellation list that matches both the merchant identifier and the user identifier carried in the periodic deduction request.

[0027] The contract information list includes contract information, which represents a contract between a user account corresponding to a user identifier and a merchant account corresponding to a merchant identifier. The contract information includes a merchant identifier and a user identifier.

[0028] In one possible implementation, after determining that the transaction process corresponding to the periodic deduction request should be rejected, the following is also included:

[0029] If a second scheduled deduction request is received after the second preset time period, the transaction process corresponding to the next scheduled deduction request will be rejected.

[0030] In one possible implementation, the method further includes:

[0031] If it is determined that there is a cancellation information in the cancellation list that does not match the merchant identifier and user identifier carried in the periodic deduction request, then the transaction process corresponding to the periodic deduction request will be executed.

[0032] In one possible implementation, verifying the cancellation request includes:

[0033] If it is determined that the number of times the first device initiates a contract termination request within the third preset time period is less than or equal to the second preset number, then the contract termination request currently initiated by the first device is verified.

[0034] In one possible implementation, the method further includes:

[0035] Receive a contract signing request sent by a first device; wherein the contract signing request includes a merchant identifier and a user identifier, and the contract signing request also includes contract signing verification information;

[0036] If the verification of the contract verification information in the contract request is successful, contract information is generated; wherein, the contract information represents a contract between the user account corresponding to the user identifier and the merchant account corresponding to the merchant identifier, and the contract information includes the merchant identifier and the user identifier.

[0037] In one possible implementation, the method further includes:

[0038] The cancellation information is stored in the first block of the blockchain; and the signing information is stored in the second block of the blockchain; wherein, the signing information represents a signing between the user account corresponding to the user identifier and the merchant account corresponding to the merchant identifier, and the signing information includes the merchant identifier and the user identifier.

[0039] Secondly, this application provides a processing apparatus based on user cancellation, comprising:

[0040] A verification unit is configured to verify a cancellation request initiated by a first device; wherein the cancellation request includes a merchant identifier and a user identifier, the cancellation request indicating a request to unbind the user account corresponding to the user identifier from the merchant account corresponding to the merchant identifier, the first device being the user's device; the user identifier being a unique user identifier and / or the user's bank card number; the merchant identifier being the terminal number of a second device; the second device being the merchant's device;

[0041] The first generation unit is used to generate termination information corresponding to the termination processing request if it is determined that the verification of the termination processing request is successful.

[0042] The query unit is configured to, upon receiving a periodic deduction request initiated by the second device, query a cancellation list in response to the periodic deduction request initiated by the second device; wherein the periodic deduction request is initiated periodically based on a preset date, and the periodic deduction request includes a merchant identifier and a user identifier; the cancellation list includes at least one cancellation information, the cancellation information indicating that the user account corresponding to the user identifier is unbound from the merchant account corresponding to the merchant identifier, and the cancellation information includes a merchant identifier and a user identifier;

[0043] The first determining unit is configured to, if it is determined that there is a cancellation information in the cancellation list that matches both the merchant identifier and the user identifier carried in the periodic deduction request, then determine to refuse to execute the transaction process corresponding to the periodic deduction request and send first feedback information to the second device; wherein, the first feedback information indicates that the user account corresponding to the user identifier in the periodic deduction request has been cancelled.

[0044] In one possible implementation, the cancellation request includes location information; the location information includes any one of the following: the geographical location information of the first device, the IP address information of the first device, and the International Mobile Equipment Identity (IMEI) of the first device.

[0045] The verification unit includes:

[0046] The first determining module is used to determine the user login information corresponding to the first device in response to the cancellation processing request initiated by the first device; wherein, the user login information includes the user identifier and location information corresponding to a historical time, the historical time being the time when the first device issued a historical cancellation processing request or a historical contract processing request, and the contract processing request being used to request a contract processing for periodic deductions.

[0047] The first processing module is configured to: if it is determined that the user login information includes the location information in the cancellation request, then determine that the verification of the cancellation request is successful; if it is determined that the user login information does not include the location information in the cancellation request, then determine that the verification of the cancellation request is unsuccessful; or, if it is determined that the user login information includes the location information in the cancellation request, and the number of times the location information in the cancellation request is included in the user login information is greater than a first preset number, then determine that the verification of the cancellation request is successful; if it is determined that the user login information includes the location information in the cancellation request, and the number of times the location information is included in the cancellation request is less than or equal to the first preset number, then determine that the verification of the cancellation request is unsuccessful.

[0048] In one possible implementation, the verification unit includes:

[0049] The first sending module is used to send a verification request to the first device in response to the cancellation processing request initiated by the first device;

[0050] The receiving module is used to receive verification information sent by the first device; wherein the verification information includes one or more of the following: user name, user bank card expiration date, facial information, and fingerprint information;

[0051] The second processing module is used to determine that the verification of the cancellation processing request is successful if it is determined that the received verification information is consistent with the pre-stored verification information.

[0052] The third processing module is used to determine that the verification of the cancellation request fails if it is determined that the received verification information is inconsistent with the pre-stored verification information.

[0053] In one possible implementation, the verification unit includes:

[0054] The second determining module is used to determine the mobile phone number corresponding to the first device in response to the cancellation processing request initiated by the first device;

[0055] The second sending module is used to send a first verification code to a device with a mobile phone number corresponding to the first device;

[0056] The fourth processing module is used to determine that the verification of the cancellation request is successful if it is determined that a second verification code sent by the device of the mobile phone number is received within a first preset time period and the second verification code is consistent with the first verification code;

[0057] The fifth processing module is used to determine that the verification of the cancellation request fails if it is determined that the second verification code sent by the device of the mobile phone number has not been received within a first preset time period, and / or the second verification code is inconsistent with the first verification code.

[0058] In one possible implementation, prior to the first determining unit, the following is also included:

[0059] The first processing unit is configured to, if it is determined that the contract information list includes contract information that corresponds to both the user identifier and the merchant identifier in the cancellation processing request, then execute the step of determining to refuse to execute the transaction process corresponding to the periodic deduction request if it is determined that there is cancellation information in the cancellation list that matches both the merchant identifier and the user identifier carried in the periodic deduction request.

[0060] The contract information list includes contract information, which represents a contract between a user account corresponding to a user identifier and a merchant account corresponding to a merchant identifier. The contract information includes a merchant identifier and a user identifier.

[0061] In one possible implementation, after the first determining unit, the following is further included:

[0062] The second processing unit is configured to refuse to execute the transaction process corresponding to the next periodic deduction request if it receives the next periodic deduction request after a second preset time period.

[0063] In one possible implementation, the device further includes:

[0064] The second determining unit is used to determine to execute the transaction process corresponding to the periodic deduction request if it is determined that there is a cancellation information in the cancellation list that does not match the merchant identifier and user identifier carried in the periodic deduction request.

[0065] In one possible implementation, the verification unit includes:

[0066] The third determining module is used to verify the current termination request initiated by the first device if it is determined that the number of times the termination processing request initiated by the first device is received within a third preset time period is less than or equal to a second preset number.

[0067] In one possible implementation, the device further includes:

[0068] A receiving unit is configured to receive a contract request sent by a first device; wherein the contract request includes a merchant identifier and a user identifier, and the contract request also includes contract verification information;

[0069] The second generation unit is used to generate contract information if the verification of the contract verification information in the contract request is successful; wherein the contract information represents a contract between the user account corresponding to the user identifier and the merchant account corresponding to the merchant identifier, and the contract information includes the merchant identifier and the user identifier.

[0070] In one possible implementation, the device further includes:

[0071] The first storage unit is used to store the cancellation information in the first block of the blockchain;

[0072] The second storage unit is used to store the contract information in the second block of the blockchain;

[0073] The contract information represents a contract between a user account corresponding to a user identifier and a merchant account corresponding to a merchant identifier. The contract information includes both the merchant identifier and the user identifier.

[0074] Thirdly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0075] The memory stores computer-executed instructions;

[0076] The processor executes computer execution instructions stored in the memory to implement the method provided in the first aspect above.

[0077] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method provided in the first aspect above.

[0078] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the method provided in the first aspect above.

[0079] The user-based cancellation processing method, apparatus, and device provided in this application involve a bank server responding to a cancellation processing request initiated by a first device. The server verifies the cancellation request to ensure its legality. If the server verifies the cancellation request, it generates cancellation information corresponding to the request, guaranteeing its legitimacy. If the bank server receives a recurring deduction request from a second device, it queries the cancellation list to confirm whether the user account corresponding to the user identifier and the merchant account corresponding to the merchant identifier in the recurring deduction request have been unbound. If the server determines that cancellation information in the cancellation list matches both the merchant identifier and user identifier carried in the recurring deduction request, it refuses to execute the transaction corresponding to the recurring deduction request and sends first feedback information to the second device, thus protecting customer rights and improving customer satisfaction. Attached Figure Description

[0080] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0081] Figure 1 This is a schematic diagram illustrating an application scenario of an embodiment of this application;

[0082] Figure 2 A flowchart illustrating a user-cancelled contract processing method provided in this application embodiment;

[0083] Figure 3 A flowchart illustrating another user-cancellation-based processing method provided in this application embodiment;

[0084] Figure 4 A schematic diagram of a processing device based on user cancellation provided in an embodiment of this application;

[0085] Figure 5 A schematic diagram of another processing device based on user cancellation provided in an embodiment of this application;

[0086] Figure 6 A schematic diagram of another processing device based on user cancellation provided in an embodiment of this application;

[0087] Figure 7 This application provides a schematic diagram of the structure of an electronic device.

[0088] Figure 8 This is a block diagram illustrating a terminal device according to an exemplary embodiment.

[0089] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0090] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0091] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with relevant laws, regulations and standards, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0092] It should be noted that the processing method, apparatus, and equipment based on user contract termination in this application can be used in the financial field or other fields, and can also be used in any field other than the financial field. The application field of the processing method, apparatus, and equipment based on user contract termination in this application is not limited.

[0093] With the development of information technology, banking transactions need to be processed through online systems. These online systems provide users with a recurring deduction service. After a recurring deduction agreement is established between the user's bank card and the merchant's device, the merchant's device can periodically send a recurring deduction request to the bank's server, requesting that funds be deducted from the user's bank card. Then, the bank's server automatically deducts the funds from the user's bank card based on the recurring deduction request from the merchant's device.

[0094] In one example, a user can request to cancel a service that automatically deducts payments from their account. The user's device sends a cancellation request to the merchant's device. Upon receiving the cancellation request, the merchant's device must process the cancellation based on the merchant's notification. After the merchant agrees to the cancellation, the merchant's device sends the cancellation confirmation to the bank's server. Only then can the bank's server prevent automatic deductions from the user's bank card.

[0095] However, in the above methods, if the merchant refuses to agree to the cancellation when the user requests to cancel the service of recurring deductions, or if the merchant misses the user's cancellation request, or if the merchant maliciously refuses to cancel, the bank's server will continue to deduct money from the user's bank card periodically. This can lead to disputes where the user requests a refund from the merchant, resulting in financial losses for the user and a poor user experience.

[0096] The processing method, apparatus, and equipment based on user contract cancellation provided in this application are intended to solve the above-mentioned technical problems of the prior art.

[0097] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0098] Figure 1 This is a schematic diagram illustrating an application scenario of an embodiment of this application, such as... Figure 1 As shown, the user's device is the first device 01, the merchant's device is the second device 02, and the bank's server is 03. The bank's server 03 can receive requests sent by the first device 01, and the bank's server 03 can also receive requests sent by the second device 02; based on the first device 01, the second device 02, and the bank's server 03, the solution of the embodiment of this application can be completed.

[0099] Figure 2 A flowchart illustrating a user-cancellation-based processing method provided in this application embodiment is shown below. Figure 2 As shown, the method includes:

[0100] S201. In response to the cancellation request initiated by the first device, verify the cancellation request; wherein, the cancellation request includes a merchant identifier and a user identifier, the cancellation request indicates that the user account corresponding to the user identifier is unbound from the merchant account corresponding to the merchant identifier, the first device is the user's device; the user identifier is the user's unique identifier, and / or the user's bank card number; the merchant identifier is the terminal number of the second device, the second device is the merchant's device.

[0101] For example, the executing entity in this embodiment can be a bank's server.

[0102] Based on the user's operation, the first device sends a cancellation request to the bank's server. Here, the first device is the user's device; the cancellation request represents a request to unbind the user account corresponding to the user identifier from the merchant account corresponding to the merchant identifier; the cancellation request includes both the merchant identifier and the user identifier; the user identifier is the user's unique identifier and / or the user's bank card number; the merchant identifier is the terminal number of the second device, which is the merchant's device.

[0103] After receiving the cancellation request from the first device, the bank's server verifies the legitimacy of the cancellation request initiated by the first device.

[0104] Using the aforementioned technical means, the bank's server can verify the legitimacy of the cancellation request initiated by the first device.

[0105] S202. If the verification of the termination request is successful, then the termination information corresponding to the termination request is generated.

[0106] For example, if the bank's server verifies that the cancellation request is legitimate, then the bank's server determines that the verification of the cancellation request has passed, and the bank's server generates cancellation information corresponding to the cancellation request. This cancellation information indicates that the user account corresponding to the user identifier is unbound from the merchant account corresponding to the merchant identifier, and the cancellation information includes both the merchant identifier and the user identifier.

[0107] S203. If a periodic deduction request initiated by the second device is received, then in response to the periodic deduction request initiated by the second device, the cancellation list is queried; wherein, the periodic deduction request is initiated at a time based on a preset date, and the periodic deduction request includes a merchant identifier and a user identifier; the cancellation list includes at least one cancellation information, the cancellation information indicating that the user account corresponding to the user identifier is unbound from the merchant account corresponding to the merchant identifier, and the cancellation information includes a merchant identifier and a user identifier.

[0108] For example, the second device automatically sends a recurring deduction request to the bank's server. Alternatively, the second device sends a recurring deduction request to the bank's server based on the merchant's actions. The recurring deduction request is initiated periodically based on a preset date and includes a merchant identifier and a user identifier. In one example, the second device automatically sends a recurring deduction request to the bank's server on the 1st of each month, where the recurring deduction request includes merchant identifier a and user identifier b. Alternatively, in another example, the second device sends a recurring deduction request to the bank's server on the 1st of each month based on the merchant's actions, where the recurring deduction request includes merchant identifier a and user identifier b.

[0109] After receiving a recurring deduction request from the second device, the bank's server checks the cancellation list to see if any cancellation information matches the merchant identifier and user identifier carried in the recurring deduction request. The cancellation list includes at least one cancellation message, indicating that the user account corresponding to the user identifier is unbound from the merchant account corresponding to the merchant identifier. The cancellation message includes both the merchant identifier and the user identifier. In one example, this application sets up a bank probe. After receiving the recurring deduction request from the second device, the bank's server uses the bank probe to check the cancellation list to see if any cancellation information matches the merchant identifier and user identifier carried in the recurring deduction request. The cancellation list includes four cancellation messages: Cancellation Message 1, Cancellation Message 2, Cancellation Message 3, and Cancellation Message 4. Cancellation Message 1 includes merchant identifier a and user identifier b; Cancellation Message 2 includes merchant identifier a and user identifier c; Cancellation Message 3 includes merchant identifier d and user identifier b; and Cancellation Message 4 includes merchant identifier d and user identifier e.

[0110] S204. If it is determined that there is cancellation information in the cancellation list that matches both the merchant identifier and the user identifier carried in the periodic deduction request, then it is determined that the transaction process corresponding to the periodic deduction request will be rejected, and a first feedback message will be sent to the second device; wherein, the first feedback message indicates that the user account corresponding to the user identifier in the periodic deduction request has been cancelled.

[0111] For example, if the bank's server determines that there is a cancellation information in the cancellation list that matches both the merchant identifier and the user identifier carried in the recurring deduction request, then the bank's server will refuse to execute the transaction process corresponding to the recurring deduction request and will send a feedback message to the second device. The first feedback message indicates that the user account corresponding to the user identifier in the recurring deduction request has been cancelled.

[0112] In one example, if the bank's server determines that there is a cancellation information 1 in the cancellation list that matches both the merchant identifier a and the user identifier b carried in the recurring deduction request, then the bank's server will refuse to execute the transaction process corresponding to the current recurring deduction request and send a first feedback message to the second device; wherein, the first feedback message indicates that the user account corresponding to the user identifier b in the recurring deduction request has been cancelled.

[0113] In this embodiment, the bank's server responds to the cancellation request initiated by the first device by verifying the request's legitimacy. If the server confirms the request passes verification, it generates cancellation information corresponding to the request, ensuring its legality. If the server receives a recurring deduction request from the second device, it queries the cancellation list to confirm whether the user account corresponding to the user identifier and the merchant account corresponding to the merchant identifier in the recurring deduction request have been unbound. If the server determines that there is cancellation information in the cancellation list that matches both the merchant identifier and user identifier carried in the recurring deduction request, it refuses to execute the transaction corresponding to the recurring deduction request and sends first feedback information to the second device, thus protecting customer rights and improving customer satisfaction.

[0114] Figure 3 A flowchart illustrating another user-cancellation-based processing method provided in this application embodiment is shown below. Figure 3 As shown, the method includes:

[0115] S301. Receive a contract signing request sent by the first device; wherein the contract signing request includes a merchant identifier and a user identifier, and also includes contract signing verification information.

[0116] For example, the executing entity in this embodiment can be a bank's server.

[0117] The online system provides users with a service for recurring deduction transactions. A recurring deduction agreement can be established between the user's bank card and the merchant's device.

[0118] When a user needs to establish a recurring payment agreement with a merchant, the user can sign up through the merchant's website. At this point, the user operates a primary device, which displays the merchant's website. The user then initiates a signing request through the merchant's website on the primary device, and the primary device generates a signing request. This signing request includes a merchant identifier, a user identifier, and signing verification information. The merchant identifier is the identifier of the merchant the user wants to sign up with, and the user identifier is the identifier of the current user. The signing verification information includes the user's identity document, facial image, fingerprint, personal information, etc. The primary device then sends the signing request to the bank's server.

[0119] Alternatively, the user can visit the merchant's customer service location and complete the contract signing there. In this case, the user operates their own primary device, which then generates a contract signing request; or, the user operates a primary device provided by the merchant, which in turn generates a contract signing request. The contract signing request includes a merchant identifier, a user identifier, and contract verification information. The merchant identifier is the identifier of the merchant the user wants to sign with, and the user identifier is the identifier of the current user. The contract verification information includes the user's identity document, facial image, fingerprint, personal information, etc. The primary device then sends the contract signing request to the bank's server.

[0120] Then the bank's server receives the signing request sent by the first device.

[0121] S302. If the verification of the contract verification information in the contract request is successful, contract information is generated; wherein, the contract information represents the contract between the user account corresponding to the user identifier and the merchant account corresponding to the merchant identifier, and the contract information includes the merchant identifier and the user identifier.

[0122] For example, the bank's server verifies the legality of the signing verification information in the signing request. This signing verification information includes user identification documents, user facial images, user fingerprints, user personal information, etc. If the signing verification information is legal, the bank's server successfully verifies the signing verification information in the signing request and generates signing information. This signing information represents a signing agreement between the user account corresponding to the user identifier and the merchant account corresponding to the merchant identifier, and includes both the merchant identifier and the user identifier. In one example, the bank's server verifies the legality of the signing verification information in the signing request, including verifying that the user identification documents are legal, the user facial image is complete and clear, the user fingerprint is complete and clear, and the user's personal information is complete, etc. If the signing verification information in the signing request is legal, the bank's server successfully verifies the signing verification information in the signing request and generates signing information. This signing information represents a signing agreement between the user account corresponding to the user identifier and the merchant account corresponding to the merchant identifier, and includes both the merchant identifier and the user identifier.

[0123] By following this procedure, the bank's server can ensure the legality of the contract information.

[0124] S303. Store the contract information in the second block of the blockchain; wherein, the contract information represents the contract signed between the user account corresponding to the user identifier and the merchant account corresponding to the merchant identifier, and the contract information includes the merchant identifier and the user identifier.

[0125] For example, the bank's server stores the contract information in the second block of the blockchain. This contract information represents a contract between a user account corresponding to a user identifier and a merchant account corresponding to a merchant identifier; the contract information includes both the merchant identifier and the user identifier.

[0126] Through this step, the bank's server stores the contract information, which can then be directly accessed by the bank's server.

[0127] S304. In response to the cancellation request initiated by the first device, if it is determined that the number of cancellation requests initiated by the first device within a third preset time period is less than or equal to a second preset number, then the cancellation request currently initiated by the first device is verified; wherein, the cancellation request includes a merchant identifier and a user identifier, the cancellation request indicates that the user account corresponding to the user identifier is requested to be unbound from the merchant account corresponding to the merchant identifier, the first device is the user's device; the user identifier is the user's unique identifier and / or the user's bank card number; the merchant identifier is the terminal number of the second device.

[0128] In one example, the cancellation request includes location information; the location information includes any of the following: the geographical location information of the first device, the IP address information of the first device, and the International Mobile Equipment Identity (IMEI) of the first device.

[0129] In one example, step S304 includes the following implementation methods:

[0130] In the first implementation of step S304, in response to the cancellation processing request initiated by the first device, the user login information corresponding to the first device is determined; wherein, the user login information includes the user identifier and location information corresponding to the historical time, the historical time being the time when the first device issued the historical cancellation processing request or the historical contract processing request, and the contract processing request being used to request the contract processing for periodic deduction.

[0131] If the user login information includes the location information from the cancellation request, the cancellation request is deemed to have passed verification; if the user login information does not include the location information from the cancellation request, the cancellation request is deemed to have failed verification. Alternatively, if the number of times the user login information includes the location information from the cancellation request is greater than a first preset number, the cancellation request is deemed to have passed verification; if the number of times the user login information includes the location information from the cancellation request is less than or equal to the first preset number, the cancellation request is deemed to have failed verification.

[0132] In a second implementation of step S304, in response to a cancellation request initiated by the first device, a verification request is sent to the first device. Verification information sent by the first device is received; this verification information includes one or more of the following: user name, user's bank card expiration date, facial information, and fingerprint information. If the received verification information matches the pre-stored verification information, the verification of the cancellation request is deemed successful. If the received verification information does not match the pre-stored verification information, the verification of the cancellation request is deemed unsuccessful.

[0133] In the third implementation of step S304, in response to the cancellation request initiated by the first device, the mobile phone number corresponding to the first device is determined. A first verification code is sent to the device corresponding to the mobile phone number of the first device. If it is determined that a second verification code sent by the device with the mobile phone number is received within a first preset time period, and the second verification code is consistent with the first verification code, then the verification of the cancellation request is determined to be successful. If it is determined that a second verification code sent by the device with the mobile phone number is not received within the first preset time period, and / or the second verification code is inconsistent with the first verification code, then the verification of the cancellation request is determined to be unsuccessful.

[0134] For example, the first device initiates a cancellation request to the bank's server based on the user's operation. Here, the first device is the user's device; the cancellation request represents a request to unbind the user account corresponding to the user identifier from the merchant account corresponding to the merchant identifier, and includes the merchant identifier, user identifier, and location information; the user identifier is the user's unique identifier and / or the user's bank card number; the merchant identifier is the terminal number of the second device; the location information includes any one of the following: the geographical location information of the first device, the IP address information of the first device, and the International Mobile Equipment Identity (IMEI) of the first device. The International Mobile Equipment Identity (IMEI) is a unique identifier for the device.

[0135] After receiving a cancellation request from the first device, the bank's server determines the number of cancellation requests it has received from the first device within a third preset time period. If the number of cancellation requests received from the first device within the third preset time period is less than or equal to a second preset number, then the bank verifies the cancellation request initiated by the first device. In one example, after receiving a cancellation request from the first device, the bank's server determines the number of cancellation requests received from the first device within a month. If the number of cancellation requests received from the first device within a month is less than or equal to two, then the bank verifies the cancellation request; if the number of cancellation requests received from the first device within a month is greater than two, then the bank does not verify the cancellation request and instead sends the cancellation request back to the first device without verification.

[0136] The following methods can be used to verify the cancellation request initiated by the first device.

[0137] The first method involves the first device sending a cancellation request to the bank's server based on the user's action. Upon receiving the cancellation request, the bank's server determines the user login information corresponding to the first device. This user login information includes the user's identifier and location information from a historical timeframe. The historical timeframe refers to the moment when the first device issued a previous cancellation request or a previous subscription request. The subscription request is used to request the signing of a periodic deduction agreement.

[0138] The bank's server analyzes the location information in the user's login information and the location information in the cancellation request. In one approach, if the bank's server determines that the user's login information includes the location information from the cancellation request, then the bank's server determines that the cancellation request has passed verification; if the bank's server determines that the user's login information does not include the location information from the cancellation request, then the bank's server determines that the cancellation request has failed verification. Alternatively, in another approach, if the bank's server determines that the user's login information includes the location information from the cancellation request more than a first preset number of times, then the bank's server determines that the cancellation request has passed verification; if the bank's server determines that the user's login information includes the location information from the cancellation request less than or equal to a first preset number of times, then the bank's server determines that the cancellation request has failed verification. In one example, the bank's server analyzes the location information in the user's login information and the location information in the cancellation request. If the bank's server determines that the user's login information includes the location information from the cancellation request, and the location information from the cancellation request is included in the user's login information more than twice, then the bank's server determines that the cancellation request has been verified. If the bank's server determines that the user's login information includes the location information from the cancellation request, and the location information from the cancellation request is included in the user's login information less than or equal to twice, then the bank's server determines that the cancellation request has not been verified.

[0139] The second method involves the first device sending a cancellation request to the bank's server based on the user's action. After receiving the cancellation request, the bank's server sends a verification request to the first device.

[0140] After receiving a verification request from the bank's server, the first device sends verification information to the bank's server based on the user's actions. This verification information includes one or more of the following: user's name, bank card expiration date, facial information, and fingerprint information. The bank's server receives the verification information sent by the first device. The bank's server analyzes the verification information sent by the first device against pre-stored verification information. If the bank's server determines that the received verification information matches the pre-stored verification information, then the bank's server determines that the verification of the cancellation request has passed; if the bank's server determines that the received verification information does not match the pre-stored verification information, then the bank's server determines that the verification of the cancellation request has failed. In one example, the first device sends verification information to the bank's server based on the user's actions. This verification information includes two items: user's name and facial information. The bank's server receives the verification information sent by the first device. If the user name and facial information sent by the first device match the user name and facial information pre-stored on the bank's server, the bank's server determines that the cancellation request has been successfully verified. If at least one of the two verification pieces of information does not match, the bank's server determines that the cancellation request has failed. Alternatively, in another example, the first device sends verification information to the bank's server. This verification information includes three items: user name, user's bank card expiration date, and facial information. The bank's server receives the verification information sent by the first device. If the user's name, bank card expiration date, and facial information sent by the first device match the three verification pieces of information pre-stored on the bank's server, then the bank's server determines that the cancellation request has been verified. If at least one of the three verification pieces of information sent by the first device does not match the three verification pieces of information pre-stored on the bank's server, then the bank's server determines that the cancellation request has not been verified.

[0141] The third method involves the first device sending a cancellation request to the bank's server based on the user's action. After receiving the cancellation request, the bank's server identifies the mobile phone number corresponding to the first device.

[0142] The bank's server sends a first verification code to the device with the mobile phone number. The device receives the first verification code from the bank's server and, based on the user's action, sends a second verification code to the bank's server. If the bank's server determines that it has received the second verification code from the device with the mobile phone number within a first preset time period, and that the second verification code matches the first verification code, then the bank's server determines that the cancellation request has been successfully verified. If the bank's server determines that it has not received the second verification code from the device with the mobile phone number within the first preset time period, and / or that the second verification code does not match the first verification code, then the bank's server determines that the cancellation request has failed to be verified. In one example, the bank's server sends verification code 10001 to a device with a mobile phone number. The device receives verification code 10001 from the bank's server. Based on the user's action, the first device sends verification code 10001 to the bank's server. If the bank's server receives verification code 10001 from the first device within one minute of sending the verification code, the bank's server determines that the cancellation request has been verified successfully. If the bank's server receives verification code 10001 from the first device more than one minute after sending the verification code, the bank's server determines that the cancellation request has failed. Alternatively, in another example, the bank's server sends verification code 10002 to a device with a mobile phone number. The device receives verification code 10002 from the bank's server. Based on the user's action, the first device sends verification code 10003 to the bank's server. If the bank's server receives verification code 10003 from the first device within one minute of sending the verification code, and / or more than one minute after, then the bank's server determines that the cancellation request has failed. Alternatively, in another example, the bank's server sends verification code 10004 to the device with the mobile phone number. The device with the mobile phone number receives the verification code 10004 sent by the bank's server. If the user does not send the verification code to the bank's server through the first device, and the bank's server does not receive the verification code 10004 sent by the first device within one minute after sending the verification code, then the bank's server determines that the verification of the cancellation request has failed.

[0143] This method avoids users frequently canceling and signing contracts, and the bank's server verifies the authenticity and legality of the cancellation processing request.

[0144] S305. If the verification of the termination request is successful, then the termination information corresponding to the termination request is generated.

[0145] For example, if the bank's server determines that the cancellation request has been verified, then the bank's server generates cancellation information corresponding to the cancellation request. This cancellation information indicates that the user account corresponding to the user identifier is unbound from the merchant account corresponding to the merchant identifier, and includes both the merchant identifier and the user identifier.

[0146] Through this process, the bank's server ensures the authenticity and legality of the cancellation processing request.

[0147] S306. Store the termination information in the first block of the blockchain.

[0148] For example, the bank's server stores the cancellation information in the first block of the blockchain. This cancellation information represents the unbinding of the user account corresponding to the user identifier from the merchant account corresponding to the merchant identifier. The cancellation information includes both the merchant identifier and the user identifier.

[0149] Through this step, the bank's server stores the cancellation information, which can then be directly accessed by the bank's server.

[0150] S307. If a periodic deduction request initiated by the second device is received, then in response to the periodic deduction request initiated by the second device, the cancellation list is queried; wherein, the periodic deduction request is initiated at a time based on a preset date, and the periodic deduction request includes a merchant identifier and a user identifier; the cancellation list includes at least one cancellation information, the cancellation information indicating that the user account corresponding to the user identifier is unbound from the merchant account corresponding to the merchant identifier, and the cancellation information includes a merchant identifier and a user identifier.

[0151] For example, the second device automatically sends a recurring deduction request to the bank's server. Alternatively, the second device sends a recurring deduction request to the bank's server based on the merchant's actions. The recurring deduction request is initiated periodically based on a preset date and includes a merchant identifier and a user identifier. In one example, the second device automatically sends a recurring deduction request to the bank's server on the 1st of each month, where the recurring deduction request includes merchant identifier a and user identifier b. Alternatively, in another example, the second device sends a recurring deduction request to the bank's server on the 1st of each month based on the merchant's actions, where the recurring deduction request includes merchant identifier a and user identifier b.

[0152] After receiving a recurring deduction request from a second device, the bank's server checks the cancellation list to see if any cancellation information matches the merchant identifier and user identifier carried in the recurring deduction request. The cancellation list includes at least one cancellation message, indicating that the user account corresponding to the user identifier is unbound from the merchant account corresponding to the merchant identifier. The cancellation message includes both the merchant identifier and the user identifier. In one example, after receiving the recurring deduction request from the second device, the bank's server checks the cancellation list to see if any cancellation information matches the merchant identifier and user identifier carried in the recurring deduction request. The cancellation list includes four cancellation messages: Cancellation Message 1, Cancellation Message 2, Cancellation Message 3, and Cancellation Message 4. Cancellation Message 1 includes merchant identifier a and user identifier b; Cancellation Message 2 includes merchant identifier a and user identifier c; Cancellation Message 3 includes merchant identifier d and user identifier b; and Cancellation Message 4 includes merchant identifier d and user identifier e.

[0153] By using this method, the bank's server can confirm whether the user account corresponding to the user identifier and the merchant account corresponding to the merchant identifier have been unbound in the periodic deduction request initiated by the second device.

[0154] S308. If it is determined that the contract information list includes contract information that corresponds to both the user identifier and the merchant identifier in the termination processing request, then proceed to step S309.

[0155] The contract information list includes contract information, which represents the contract signed between the user account corresponding to the user identifier and the merchant account corresponding to the merchant identifier. The contract information includes the merchant identifier and the user identifier.

[0156] For example, the second device automatically sends a recurring deduction request to the bank's server. Alternatively, the second device sends a recurring deduction request to the bank's server based on the merchant's actions. The recurring deduction request is initiated periodically based on a preset date and includes a merchant identifier and a user identifier.

[0157] After receiving the recurring deduction request from the second device, the bank's server checks its contract information list to see if it includes contract information corresponding to both the user identifier and merchant identifier in the cancellation request. The contract information list includes contract information indicating a contract between the user account corresponding to the user identifier and the merchant account corresponding to the merchant identifier. If the bank's server determines that the contract information list includes contract information corresponding to both the user identifier and merchant identifier in the cancellation request, then the bank's server executes step S309. If the bank's server determines that the contract information list does not include contract information corresponding to both the user identifier and merchant identifier in the cancellation request, then the bank's server refuses to execute the transaction process corresponding to the recurring deduction request and sends a second feedback message to the second device. This second feedback message indicates that there is no contract between the user account corresponding to the user identifier and the merchant account corresponding to the merchant identifier in the recurring deduction request.

[0158] In one example, the second device automatically sends a recurring deduction request to the bank's server on the 1st of each month. The recurring deduction request includes merchant identifier a and user identifier b.

[0159] After receiving the recurring deduction request from the second device, the bank's server checks its contract information list to see if it includes contract information corresponding to the user identifier and merchant identifier in the cancellation request. The contract list includes four contract information entries: Contract Information 1, Contract Information 2, Contract Information 3, and Contract Information 4. Contract Information 1 includes merchant identifier a and user identifier b; Contract Information 2 includes merchant identifier a and user identifier c; Contract Information 3 includes merchant identifier d and user identifier b; and Contract Information 4 includes merchant identifier d and user identifier e.

[0160] The bank's server determines that the contract information list includes contract information 1, which corresponds to both user identifier a and merchant identifier b in the cancellation processing request. The bank's server then executes step S309.

[0161] Alternatively, in another example, the second device, based on the merchant's actions, sends a recurring deduction request to the bank's server on the 1st of each month, wherein the recurring deduction request includes merchant identifier a and user identifier f.

[0162] After receiving the recurring deduction request from the second device, the bank's server checks its contract information list to see if it includes contract information corresponding to the user identifier and merchant identifier in the cancellation request. The contract list includes four contract information entries: Contract Information 1, Contract Information 2, Contract Information 3, and Contract Information 4. Contract Information 1 includes merchant identifier a and user identifier b; Contract Information 2 includes merchant identifier a and user identifier c; Contract Information 3 includes merchant identifier d and user identifier b; and Contract Information 4 includes merchant identifier d and user identifier e.

[0163] If the bank's server determines that the contract information list does not include the contract information corresponding to both user identifier 'a' and merchant identifier 'f' in the cancellation request, the bank's server will refuse to execute the transaction process corresponding to the recurring deduction request and will send a second feedback message to the second device. This second feedback message indicates that there is no contract between the user account corresponding to the user identifier in the recurring deduction request and the merchant account corresponding to the merchant identifier.

[0164] By using this method, the bank's server can verify whether the user account corresponding to the user identifier and the merchant account corresponding to the merchant identifier in the recurring deduction request initiated by the second device have previously signed a contract, thus ensuring the authenticity of the recurring deduction request.

[0165] S309. If it is determined that there is cancellation information in the cancellation list that matches both the merchant identifier and the user identifier carried in the periodic deduction request, then it is determined that the transaction process corresponding to the periodic deduction request will be rejected, and a first feedback message will be sent to the second device; wherein, the first feedback message indicates that the user account corresponding to the user identifier in the periodic deduction request has been cancelled.

[0166] For example, if the bank's server determines that there is cancellation information in the cancellation list that matches both the merchant identifier and the user identifier carried in the periodic deduction request, then the bank's server will refuse to execute the transaction process corresponding to the periodic deduction request and send a first feedback message to the second device; wherein, the first feedback message indicates that the user account corresponding to the user identifier in the periodic deduction request has been cancelled.

[0167] In one example, if the bank's server determines that there is a cancellation information 1 in the cancellation list that matches both the merchant identifier a and the user identifier b carried in the recurring deduction request, then the bank's server will refuse to execute the transaction process corresponding to the current recurring deduction request and send a first feedback message to the second device; wherein, the first feedback message indicates that the user account corresponding to the user identifier b in the recurring deduction request has been cancelled.

[0168] This approach safeguards customer rights and improves customer satisfaction.

[0169] S310. After the second preset time period, if the next periodic deduction request is received, the transaction process corresponding to the next periodic deduction request is rejected.

[0170] For example, after the second preset time period, if the second device automatically sends the next periodic deduction request to the bank's server, or if the second device sends the next periodic deduction request to the bank's server based on the merchant's operation, and the bank's server receives the next periodic deduction request sent by the second device, then the bank's server will refuse to execute the transaction process corresponding to the next periodic deduction request.

[0171] In one example, one month later, if the second device automatically sends a request for the next recurring deduction to the bank's server, where the recurring deduction request includes merchant identifier 'a' and user identifier 'b'; or, based on a merchant's action, the second device sends a request for the next recurring deduction to the bank's server, where the recurring deduction request includes merchant identifier 'a' and user identifier 'b'. Upon receiving the next recurring deduction request from the second device, the bank's server will refuse to execute the transaction process corresponding to the next recurring deduction request.

[0172] S311. If it is determined that there is cancellation information in the cancellation list that does not match the merchant identifier and user identifier carried in the periodic deduction request, then the transaction process corresponding to the periodic deduction request will be executed.

[0173] For example, if the bank's server determines that there is a cancellation information in the cancellation list that does not match the merchant identifier and user identifier carried in the recurring deduction request, then the bank's server will determine to execute the transaction process corresponding to the recurring deduction request. In one example, if the bank's server determines that there is no cancellation information in the cancellation list that matches both the merchant identifier 'a' and the user identifier 'b' carried in the recurring deduction request, then the bank's server will determine to execute the transaction process corresponding to the current recurring deduction request.

[0174] By using this method, the bank's server can confirm that in the recurring deduction request initiated by the second device, the user account corresponding to the user identifier and the merchant account corresponding to the merchant identifier are still in a contractual state, thus ensuring the legality of the transaction process corresponding to the recurring deduction request.

[0175] Figure 4 This application provides a schematic diagram of the structure of a processing device based on user cancellation, as shown in the embodiment of the present application. Figure 4 As shown, the device 400 includes three modules: a customer periodic transaction identification module 401, a customer periodic transaction cancellation merchant management module 402, and a customer periodic transaction cancellation merchant inspection module 403.

[0176] The customer recurring transaction identification module 401 is used by the bank's server to identify recurring deduction transactions initiated by a customer against their bank card. After a merchant initiates a recurring deduction transaction, the bank's server obtains information such as the bank card number, merchant name, merchant terminal number (which is a unique identifier for the contracted merchant), transaction date, and transaction amount. The bank's server stores this information in the recurring transaction data table. When a customer needs to set up a recurring transaction list, the bank's server transmits the customer's existing recurring deduction transaction information to the customer's recurring transaction cancellation merchant management module.

[0177] The Customer Recurring Transaction Cancellation Merchant Management Module 402 is used for recurring deduction transactions from a customer's bank card. Customers can add, modify, query, and delete data recorded in the recurring transaction cancellation merchant list data table. When a customer notifies the bank's server to check for recurring deduction transactions initiated by their bank card, and requests the server to either refuse or re-allow such transactions at a specific merchant, the customer enters information such as their bank card number, merchant name, merchant's unique terminal number, and blacklist activation flag. The bank's server records this information in the recurring transaction cancellation merchant list data table. The blacklist activation flag indicates that the customer needs to cancel their contract with the specific merchant, and the customer requests the bank's server not to execute the current deduction. After cancelling the contract with the specific merchant, the customer can re-sign with that merchant; at this time, the blacklist activation flag becomes invalid. The bank's servers limit customers to canceling their contracts only twice a month, and if a customer cancels a contract with a specific merchant, the customer is not allowed to renew the contract with that merchant on the same day.

[0178] The customer recurring transaction cancellation merchant check module 403 is used when the bank's server identifies a recurring deduction transaction. The bank's server uses information from the recurring deduction transaction to match data recorded in the recurring transaction cancellation merchant list data table. If a match is found, the bank's server rejects the current deduction transaction. This module, when the bank's server receives a recurring deduction transaction initiated by a merchant and identifies it, uses the bank card number and merchant's unique terminal number from the recurring deduction transaction to query the recurring transaction cancellation merchant list data table in the customer recurring transaction cancellation merchant management module. If a recurring deduction transaction matching the merchant's initiated recurring deduction transaction is found, and the blacklist activation flag is determined to be active, the bank's server will reject the current merchant's recurring deduction transaction. If no matching recurring deduction transaction is found, the bank's server will execute the current merchant's recurring deduction transaction.

[0179] Specifically, customers do not need to configure the merchant management module for recurring transaction cancellations every time; they can configure it only when needed. The bank's server needs to access the recurring transaction cancellation merchant list data table each time it executes the recurring transaction cancellation merchant list check module.

[0180] The apparatus provided in this embodiment can be referred to the method provided in the above embodiments. The technical process and effects are the same, and will not be described again.

[0181] Figure 5 A schematic diagram of another processing device based on user cancellation provided in this application embodiment is shown below. Figure 5 As shown, the device 500 includes:

[0182] Verification unit 501 is used to verify the cancellation processing request in response to the cancellation processing request initiated by the first device; wherein, the cancellation processing request includes a merchant identifier and a user identifier, the cancellation processing request indicates that the user account corresponding to the user identifier is unbound from the merchant account corresponding to the merchant identifier, the first device is the user's device; the user identifier is a unique user identifier and / or the user's bank card number; the merchant identifier is the terminal number of the second device; the second device is the merchant's device.

[0183] The first generation unit 502 is used to generate termination information corresponding to the termination request if it is determined that the verification of the termination processing request is successful.

[0184] The query unit 503 is used to query the cancellation list in response to a periodic deduction request initiated by the second device if a periodic deduction request is received. The periodic deduction request is initiated on a preset date and includes a merchant identifier and a user identifier. The cancellation list includes at least one cancellation information, which indicates that the user account corresponding to the user identifier is unbound from the merchant account corresponding to the merchant identifier. The cancellation information includes both the merchant identifier and the user identifier.

[0185] The first determining unit 504 is configured to determine that the transaction process corresponding to the periodic deduction request will be refused if the cancellation information in the cancellation list matches both the merchant identifier and the user identifier carried in the periodic deduction request, and to send first feedback information to the second device; wherein, the first feedback information indicates that the user account corresponding to the user identifier in the periodic deduction request has been cancelled.

[0186] The apparatus provided in this embodiment can be referred to the method provided in the above embodiments. The technical process and effects are the same, and will not be described again.

[0187] Figure 6 A schematic diagram of another processing device based on user cancellation provided in this application embodiment is shown below. Figure 6As shown, the device 600 includes:

[0188] The verification unit 601 is used to verify the cancellation processing request in response to the cancellation processing request initiated by the first device; wherein, the cancellation processing request includes a merchant identifier and a user identifier, the cancellation processing request indicates that the user account corresponding to the user identifier is unbound from the merchant account corresponding to the merchant identifier, the first device is the user's device; the user identifier is a unique identifier of the user, and / or, the user's bank card number; the merchant identifier is the terminal number of the second device; the second device is the merchant's device.

[0189] The first generation unit 602 is used to generate termination information corresponding to the termination request if it is determined that the verification of the termination processing request is successful.

[0190] The query unit 603 is used to query the cancellation list in response to a periodic deduction request initiated by the second device if a periodic deduction request is received from the second device. The periodic deduction request is initiated at regular intervals based on a preset date and includes a merchant identifier and a user identifier. The cancellation list includes at least one cancellation information, which indicates that the user account corresponding to the user identifier is unbound from the merchant account corresponding to the merchant identifier. The cancellation information includes both the merchant identifier and the user identifier.

[0191] The first determining unit 604 is configured to determine that the transaction process corresponding to the periodic deduction request will be refused if the cancellation information in the cancellation list matches both the merchant identifier and the user identifier carried in the periodic deduction request, and to send first feedback information to the second device; wherein the first feedback information indicates that the user account corresponding to the user identifier in the periodic deduction request has been cancelled.

[0192] In one example, the cancellation request includes location information; the location information includes any of the following: the geographical location information of the first device, the IP address information of the first device, and the International Mobile Equipment Identity (IMEI) of the first device.

[0193] Verification unit 601 includes:

[0194] The first determining module 6011 is used to determine the user login information corresponding to the first device in response to the cancellation processing request initiated by the first device; wherein, the user login information includes the user identifier and location information corresponding to the historical time, the historical time being the time when the first device issued the historical cancellation processing request or the historical signing processing request, and the signing processing request being used to request the signing processing of periodic deduction.

[0195] The first processing module 6012 is configured to determine that the verification of the cancellation request is successful if it is determined that the user login information includes the location information in the cancellation request, and to determine that the verification of the cancellation request is unsuccessful if it is determined that the user login information does not include the location information in the cancellation request; or, if the number of times the user login information includes the location information in the cancellation request is greater than a first preset number when it is determined that the user login information includes the location information in the cancellation request, and to determine that the verification of the cancellation request is successful if the number of times the user login information includes the location information in the cancellation request is less than or equal to the first preset number when it is determined that the user login information includes the location information in the cancellation request, and to determine that the verification of the cancellation request is unsuccessful.

[0196] In one example, verification unit 601 includes:

[0197] The first sending module 6013 is used to send a verification request to the first device in response to the cancellation processing request initiated by the first device.

[0198] The receiving module 6014 is used to receive verification information sent by the first device; wherein the verification information includes one or more of the following: user name, user bank card expiration date, facial information, and fingerprint information.

[0199] The second processing module 6015 is used to determine that the verification of the contract termination request is successful if the received verification information is consistent with the pre-stored verification information.

[0200] The third processing module 6016 is used to determine that the verification of the contract termination request fails if it is determined that the received verification information is inconsistent with the pre-stored verification information.

[0201] In one example, verification unit 601 includes:

[0202] The second determining module 6017 is used to determine the mobile phone number corresponding to the first device in response to the cancellation processing request initiated by the first device.

[0203] The second sending module 6018 is used to send the first verification code to the device with the mobile phone number corresponding to the first device.

[0204] The fourth processing module 6019 is used to determine that the verification of the cancellation processing request is successful if it is determined that a second verification code sent by a device with a mobile phone number is received within a first preset time period and the second verification code is consistent with the first verification code.

[0205] The fifth processing module 6020 is used to determine that the verification of the cancellation request fails if it is determined that the second verification code sent by the device with the mobile phone number has not been received within the first preset time period, and / or the second verification code is inconsistent with the first verification code.

[0206] In one example, prior to the first determining unit 604, the following is also included:

[0207] The first processing unit 605 is configured to, if it is determined that the contract information list includes contract information that corresponds to both the user identifier and the merchant identifier in the cancellation processing request, then execute the step of determining to refuse to execute the transaction process corresponding to the periodic deduction request if it is determined that there is cancellation information in the cancellation list that matches both the merchant identifier and the user identifier carried in the periodic deduction request.

[0208] The contract information list includes contract information, which represents the contract signed between the user account corresponding to the user identifier and the merchant account corresponding to the merchant identifier. The contract information includes the merchant identifier and the user identifier.

[0209] In one example, after the first determining unit 604, it also includes:

[0210] The second processing unit 606 is configured to refuse to execute the transaction process corresponding to the next periodic deduction request if it receives the next periodic deduction request after a second preset time period.

[0211] In one example, device 600 also includes:

[0212] The second determining unit 607 is used to determine to execute the transaction process corresponding to the periodic deduction request if there is a cancellation information in the cancellation list that does not match the merchant identifier and user identifier carried in the periodic deduction request.

[0213] In one example, verification unit 601 includes:

[0214] The third determining module 6021 is used to verify the current termination processing request initiated by the first device if it is determined that the number of times the termination processing request initiated by the first device is received within a third preset time period is less than or equal to a second preset number.

[0215] In one example, device 600 also includes:

[0216] The receiving unit 608 is used to receive a contract request sent by the first device; wherein the contract request includes a merchant identifier and a user identifier, and also includes contract verification information.

[0217] The second generation unit 609 is used to generate contract information if the verification of the contract verification information in the contract request is successful; wherein, the contract information represents a contract between the user account corresponding to the user identifier and the merchant account corresponding to the merchant identifier, and the contract information includes the merchant identifier and the user identifier.

[0218] In one example, device 600 also includes:

[0219] The first storage unit 610 is used to store the cancellation information in the first block of the blockchain.

[0220] The second storage unit 611 is used to store the contract information into the second block of the blockchain.

[0221] The contract information represents the contract signed between the user account corresponding to the user identifier and the merchant account corresponding to the merchant identifier. The contract information includes the merchant identifier and the user identifier.

[0222] The apparatus provided in this embodiment can be referred to the method provided in the above embodiments. The technical process and effects are the same, and will not be described again.

[0223] Figure 7 This application provides a schematic diagram of the structure of an electronic device, such as... Figure 7 As shown, the electronic device includes: a transmitter 701, a receiver 702, a memory 703, and a processor 704.

[0224] Memory 703 is used to store computer instructions.

[0225] The processor 704 is used to execute computer instructions stored in the memory 703 to implement the technical solution of any of the implementation methods provided in the foregoing embodiments.

[0226] Receiver 702 is used to receive instructions and data sent by other devices.

[0227] Transmitter 701 is used to send instructions and data to external devices.

[0228] Figure 8 This is a block diagram illustrating a terminal device according to an exemplary embodiment. The device may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, etc.

[0229] The device 800 may include one or more of the following components: a processing component 802, a memory 804, a power supply component 806, a multimedia component 808, an audio component 810, an input / output (I / O) interface 812, a sensor component 814, and a communication component 816.

[0230] Processing component 802 typically controls the overall operation of device 800, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 802 may include one or more processors 820 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 802 may include one or more modules to facilitate interaction between processing component 802 and other components. For example, processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.

[0231] Memory 804 is configured to store various types of data to support the operation of device 800. Examples of such data include instructions for any application or method operating on device 800, contact data, phonebook data, messages, pictures, videos, etc. Memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0232] Power supply component 806 provides power to various components of device 800. Power supply component 806 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power to device 800.

[0233] Multimedia component 808 includes a screen that provides an output interface between the device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 808 includes a front-facing camera and / or a rear-facing camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

[0234] Audio component 810 is configured to output and / or input audio signals. For example, audio component 810 includes a microphone (MIC) configured to receive external audio signals when device 800 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 804 or transmitted via communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.

[0235] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0236] Sensor assembly 814 includes one or more sensors for providing status assessments of various aspects of device 800. For example, sensor assembly 814 may detect the on / off state of device 800, the relative positioning of components such as the display and keypad of device 800, changes in the position of device 800 or a component of device 800, the presence or absence of user contact with device 800, the orientation or acceleration / deceleration of device 800, and temperature changes of device 800. Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 814 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0237] Communication component 816 is configured to facilitate wired or wireless communication between device 800 and other devices. Device 800 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 816 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 816 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0238] In an exemplary embodiment, the apparatus 800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.

[0239] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, which can be executed by a processor 820 of the device 800 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0240] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the methods provided in the above embodiments.

[0241] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the methods provided in the above embodiments.

[0242] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0243] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A processing method based on user cancellation, applied to a bank server, characterized in that, The method includes: The bank server responds to the cancellation request initiated by the first device by verifying the cancellation request; wherein, the cancellation request includes a merchant identifier and a user identifier, the cancellation request indicates a request to unbind the user account corresponding to the user identifier from the merchant account corresponding to the merchant identifier, the first device is the user's device; the user identifier is a unique user identifier and / or the user's bank card number; the merchant identifier is the terminal number of the second device; the second device is the merchant's device; If the bank server determines that the verification of the cancellation request is successful, it generates cancellation information corresponding to the cancellation request. If the bank server receives a scheduled deduction request initiated by the second device, it responds by querying the cancellation list. The scheduled deduction request is initiated periodically based on a preset date and includes a merchant identifier and a user identifier. The cancellation list includes at least one cancellation message, indicating that the user account corresponding to the user identifier is unbound from the merchant account corresponding to the merchant identifier. The cancellation message includes both the merchant identifier and the user identifier. If the bank server determines that there is a cancellation information in the cancellation list that matches both the merchant identifier and the user identifier carried in the periodic deduction request, it will refuse to execute the transaction process corresponding to the periodic deduction request and send a first feedback message to the second device; wherein, the first feedback message indicates that the user account corresponding to the user identifier in the periodic deduction request has been cancelled; The termination request includes location information; the location information includes any one of the following: the geographical location information of the first device, the IP address information of the first device, and the International Mobile Equipment Identity (IMEI) of the first device; In response to a cancellation request initiated by the first device, the cancellation request is verified, including: In response to a cancellation request initiated by a first device, user login information corresponding to the first device is determined; wherein, the user login information includes the user identifier and location information corresponding to a historical moment, the historical moment being the moment when the first device issued a historical cancellation request or a historical contract processing request, the contract processing request being used to request a contract processing for periodic deductions; If it is determined that the user login information includes the location information in the cancellation request, then the verification of the cancellation request is determined to be successful; if it is determined that the user login information does not include the location information in the cancellation request, then the verification of the cancellation request is determined to be unsuccessful. Alternatively, if it is determined that the user login information includes the location information in the cancellation request, and the number of times the location information in the cancellation request is included in the user login information is greater than a first preset number, then the verification of the cancellation request is determined to be successful; if it is determined that the user login information includes the location information in the cancellation request, and the number of times the location information is included in the cancellation request is less than or equal to the first preset number, then the verification of the cancellation request is determined to be unsuccessful.

2. The method of claim 1, wherein, In response to a cancellation request initiated by the first device, the cancellation request is verified, including: In response to the cancellation request initiated by the first device, a verification request is sent to the first device; The device receives verification information sent by the first device; wherein the verification information includes one or more of the following: user name, user bank card expiration date, facial information, and fingerprint information. If it is determined that the received verification information is consistent with the pre-stored verification information, then the verification of the cancellation request is deemed successful. If the received verification information is determined to be inconsistent with the pre-stored verification information, then the verification of the cancellation request is determined to be unsuccessful.

3. The method according to claim 1, characterized in that, In response to a cancellation request initiated by the first device, the cancellation request is verified, including: In response to the cancellation request initiated by the first device, the mobile phone number corresponding to the first device is determined; Send a first verification code to the device with the mobile phone number corresponding to the first device; If it is determined that a second verification code sent by a device to the mobile phone number is received within a first preset time period, and the second verification code is consistent with the first verification code, then it is determined that the verification of the cancellation request has passed. If it is determined that the second verification code sent by the device of the mobile phone number is not received within the first preset time period, and / or the second verification code is inconsistent with the first verification code, then it is determined that the verification of the cancellation processing request fails.

4. The method according to claim 1, characterized in that, Before the bank server determines that there is cancellation information in the cancellation list that matches both the merchant identifier and the user identifier carried in the recurring deduction request, and before deciding to refuse to execute the transaction process corresponding to the recurring deduction request, the process also includes: If it is determined that the contract information list includes contract information that corresponds to both the user identifier and the merchant identifier in the cancellation processing request, then the step of determining to refuse to execute the transaction process corresponding to the periodic deduction request is executed if it is determined that there is cancellation information in the cancellation list that matches both the merchant identifier and the user identifier carried in the periodic deduction request. The contract information list includes contract information, which represents a contract between a user account corresponding to a user identifier and a merchant account corresponding to a merchant identifier. The contract information includes a merchant identifier and a user identifier.

5. The method according to claim 1, characterized in that, After determining whether to refuse to execute the transaction corresponding to the periodic deduction request, the process also includes: If a second scheduled deduction request is received after the second preset time period, the transaction process corresponding to the next scheduled deduction request will be rejected.

6. The method according to any one of claims 1-5, characterized in that, The method further includes: If it is determined that there is a cancellation information in the cancellation list that does not match the merchant identifier and user identifier carried in the periodic deduction request, then the transaction process corresponding to the periodic deduction request will be executed.

7. The method according to any one of claims 1-5, characterized in that, Verification of the cancellation request includes: If it is determined that the number of times the first device initiates a contract termination request within the third preset time period is less than or equal to the second preset number, then the contract termination request currently initiated by the first device is verified.

8. The method according to any one of claims 1-5, characterized in that, The method further includes: Receive a contract signing request sent by a first device; wherein the contract signing request includes a merchant identifier and a user identifier, and the contract signing request also includes contract signing verification information; If the verification of the contract verification information in the contract request is successful, contract information is generated; wherein, the contract information represents a contract between the user account corresponding to the user identifier and the merchant account corresponding to the merchant identifier, and the contract information includes the merchant identifier and the user identifier.

9. The method according to any one of claims 1-5, characterized in that, The method further includes: The cancellation information is stored in the first block of the blockchain; and the signing information is stored in the second block of the blockchain; wherein, the signing information represents a signing between the user account corresponding to the user identifier and the merchant account corresponding to the merchant identifier, and the signing information includes the merchant identifier and the user identifier.

10. A processing device based on user cancellation, applied to a bank server, characterized in that, The device includes: A verification unit is used by the bank server to verify a cancellation request initiated by a first device; wherein the cancellation request includes a merchant identifier and a user identifier, the cancellation request indicating a request to unbind the user account corresponding to the user identifier from the merchant account corresponding to the merchant identifier, the first device being the user's device; the user identifier being a unique user identifier and / or the user's bank card number; the merchant identifier being a terminal number of a second device; the second device being the merchant's device; The first generation unit is used to generate cancellation information corresponding to the cancellation processing request if the bank server determines that the verification of the cancellation processing request is successful. The query unit is used to query the cancellation list in response to a recurring deduction request initiated by a second device if the bank server receives such a request. The recurring deduction request is initiated periodically based on a preset date and includes a merchant identifier and a user identifier. The cancellation list includes at least one cancellation message, which indicates that the user account corresponding to the user identifier is unbound from the merchant account corresponding to the merchant identifier. The cancellation message includes both the merchant identifier and the user identifier. The first determining unit is configured to, if the bank server determines that there is cancellation information in the cancellation list that matches both the merchant identifier and the user identifier carried in the periodic deduction request, then determine to refuse to execute the transaction process corresponding to the periodic deduction request and send first feedback information to the second device; wherein, the first feedback information indicates that the user account corresponding to the user identifier in the periodic deduction request has been cancelled; The termination request includes location information; the location information includes any one of the following: the geographical location information of the first device, the IP address information of the first device, and the International Mobile Equipment Identity (IMEI) of the first device; The verification unit includes a first determining module and a first processing module; The first determining module is used to determine the user login information corresponding to the first device in response to the cancellation processing request initiated by the first device; wherein, the user login information includes the user identifier and location information corresponding to a historical time, the historical time being the time when the first device issued a historical cancellation processing request or a historical contract processing request, and the contract processing request being used to request a contract processing for periodic deductions. The first processing module is configured to: if it is determined that the user login information includes the location information in the cancellation request, then determine that the verification of the cancellation request is successful; if it is determined that the user login information does not include the location information in the cancellation request, then determine that the verification of the cancellation request is unsuccessful; or, if it is determined that the user login information includes the location information in the cancellation request, and the number of times the location information in the cancellation request is included in the user login information is greater than a first preset number, then determine that the verification of the cancellation request is successful; if it is determined that the user login information includes the location information in the cancellation request, and the number of times the location information is included in the cancellation request is less than or equal to the first preset number, then determine that the verification of the cancellation request is unsuccessful.

11. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1-9.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-9.

Images