A quick payment agreement signing method and system, and computer-readable storage medium

Abstract

The present application relates to the field of Internet financial technology, and provides a method and system for signing a quick payment agreement, and a computer-readable storage medium, wherein the method includes: the issuing bank APP receives the card number and partner institution selected by the customer for signing, and selects a signing method that does not require jumping to the partner institution APP during the signing of the quick payment agreement; the issuing bank service end receives the customer information and partner institution name uploaded by the issuing bank APP; the issuing bank service end completes the pre-signing with the clearing institution and the partner institution service end, and displays the partner institution's account number to the customer through the issuing bank APP; the issuing bank service end completes the signing with the clearing institution and the partner institution service end. The above scheme solves the problem that the existing signing process is cumbersome due to the need to jump to the partner institution APP for signing, and the high requirements for user equipment, and achieves the technical effect of simply and efficiently realizing the signing of a quick payment agreement.

Description

Technical Field

[0001] The present application belongs to the field of Internet financial technology, and in particular, relates to a quick payment agreement signing method and system, and a computer-readable storage medium. Background Art

[0002] Cardless quick payment is a common payment method used today. Bank customers sign a deduction authorization agreement with the target contracting institution and the issuing bank in advance. When bank customers make electronic payments in the payment scenarios and rules agreed upon in the agreement, they no longer need to enter their bank card passwords. This payment method avoids the need for users to enter passwords every time they make a payment, protects personal privacy and account security, and improves the electronic payment experience of bank customers.

[0003] In order to realize cardless quick payment, it is necessary to sign a cardless quick payment agreement. The signing of the existing cardless quick payment agreement is generally initiated from the issuing bank APP. After selecting the target signing institution and signing card number on the issuing bank APP, the signing information is sent to the target signing institution via the clearing institution and jumped to the target signing institution APP for signing.

[0004] This contract signing method requires users to download the target contract signing agency's APP. If the target contract signing agency APP is not downloaded and installed, then the contract signing cannot be carried out. That is, the entire contract signing process requires the participation of the target contract signing agency APP, which is quite restrictive. And when the target contract signing agency APP has multiple accounts, the account currently logged in to the target contract signing agency APP is awakened, and it is impossible to freely switch to the account of the agency that needs to be signed.

[0005] With regard to the existing problem of requiring the target signing institution's APP to participate in the signing of the cardless quick payment agreement, no effective solution has been proposed yet. Summary of the invention

[0006] The purpose of this application is to provide a quick payment agreement signing method and system, and a computer-readable storage medium, which can solve the problem that the existing signing process is cumbersome and has high requirements on user equipment due to the need to jump to the partner organization APP for signing.

[0007] The present application provides a quick payment agreement signing method and system, and a computer-readable storage medium that are implemented as follows:

[0008] A method for signing a quick payment agreement, comprising:

[0009] The issuing bank APP receives the card number and partner institution selected by the customer, and selects a signing method that does not require jumping to the partner institution APP during the signing of the quick payment agreement;

[0010] The issuing bank service end receives the customer information and the name of the partner institution uploaded by the issuing bank APP;

[0011] The issuing bank service end completes the pre-signing with the clearing agency and the partner agency service end, and displays the partner agency's account number to the customer through the issuing bank APP;

[0012] The issuing bank APP receives the selected operation of the partner institution's account and transmits it to the issuing bank's service end;

[0013] The issuing bank service end completes the contract with the clearing agency and the partner agency service end.

[0014] In one embodiment, the issuing bank service end completes the pre-signing with the clearing institution and the partner institution service end, and displays the partner institution's account number to the customer through the issuing bank APP, including:

[0015] The issuing bank server obtains customer information through the issuing bank APP;

[0016] The issuing bank's server calls the pre-signing module to perform pre-signing;

[0017] The issuing bank service end encrypts the customer information and the partner institution information and transmits it to the clearing institution, which then transparently transmits it to the partner institution service end;

[0018] The partner institution's service end matches the customer's account in the partner institution based on the customer information;

[0019] The partner institution service transmits the account matching result information to the issuing bank service end through the clearing institution;

[0020] The account matching results are displayed to the customer through the issuing bank’s APP.

[0021] In one embodiment, the issuing bank service end calls the pre-contract module to perform pre-contract verification, including:

[0022] The issuing bank service end queries the special institution information registration table to determine whether the partner institution supports the signing mode without jumping to the partner institution APP during the signing of the quick payment agreement;

[0023] If support is confirmed, query the basic information registration form of the partner organization to determine whether the institution information of the partner organization is stored;

[0024] If the information of the partner organization is confirmed to be stored, compliance verification will be performed;

[0025] If the verification is passed, query the pre-contract information registration table to determine whether the pre-contract record exists;

[0026] If it exists, then pre-contract verification is performed;

[0027] If the verification is passed, the pre-signing status is updated to pre-signing successful.

[0028] In one embodiment, the pre-contract verification process includes: controlling the maximum number of pre-contracts on the day, verifying customer certificate information, and verifying customer card information.

[0029] In one embodiment, the compliance verification process includes: field non-empty verification, document type verification, card type verification, institution and card type verification, blacklist and quick payment switch verification.

[0030] In one embodiment, the issuing bank service end completes the contract with the clearing institution and the partner institution service end, including:

[0031] The issuing bank service end obtains the customer's contract information and calls the contract signing module to sign the contract;

[0032] The issuing bank service end assembles the customer's contract information, the customer's selected partner account information and partner institution information, and sends it to the clearing institution;

[0033] The issuing bank APP displays a successful contract signing interface;

[0034] The clearing institution transmits the client agreement information message to the corresponding partner institution service end according to the partner institution information;

[0035] The partner agency service receives and parses the customer agreement information message and the account information of the partner selected by the customer to sign the contract, and registers the customer agreement into the database.

[0036] In one embodiment, calling the signing module to sign the contract includes:

[0037] The issuing bank service end queries the special institution information registration table to determine whether the partner institution information is stored in the special institution information registration table;

[0038] If it is confirmed that the information exists, query the basic information registration form of the partner institution to determine whether the partner institution information exists on the issuing bank's service end;

[0039] If it is confirmed that there is a problem, conduct compliance verification.

[0040] If the verification is passed, query the pre-contract information registration table to determine whether the pre-contract record exists;

[0041] If it exists, the contract verification process is performed;

[0042] If the verification is passed, query the contract information registration table to determine whether the contract record exists;

[0043] If it exists, update the data in the contract information registration table; if it does not exist, add the contract data to the contract information registration table;

[0044] Update the pre-contract status in the pre-contract information registration form to successful contract signing.

[0045] In one embodiment, the contract verification process includes: verifying customer ID information, verifying customer card information, and verifying customer mobile phone number.

[0046] A method for signing a quick payment agreement, comprising:

[0047] When the contract signing mode selected is a contract signing mode without jumping to the partner institution APP during the process of signing the quick payment agreement, the issuing bank service end receives the customer information and the partner institution name uploaded by the issuing bank APP;

[0048] The issuing bank service end completes the pre-signing with the clearing agency and the partner agency service end, and displays the partner agency's account number to the customer through the issuing bank APP;

[0049] The issuing bank service end receives the customer's selection operation of the partner institution's account through the issuing bank APP;

[0050] The issuing bank service end completes the contract with the clearing agency and the partner agency service end.

[0051] In one embodiment, the issuing bank service end completes the pre-signing with the clearing institution and the partner institution service end, and displays the partner institution's account number to the customer through the issuing bank APP, including:

[0052] The issuing bank server obtains customer information through the issuing bank APP;

[0053] The issuing bank service end calls the pre-signing module to perform pre-signing;

[0054] The issuing bank service end encrypts the customer information and the partner institution information and transmits it to the clearing institution, which then transparently transmits it to the partner institution service end;

[0055] The issuing bank service end receives the customer's account number in the partner institution matched by the partner institution service end according to the customer information;

[0056] The issuing bank service end displays the account matching result to the customer through the issuing bank APP.

[0057] In one embodiment, the issuing bank service end calls the pre-contract module to perform pre-contract verification, including:

[0058] The issuing bank service end queries the special institution information registration table to determine whether the partner institution supports the signing mode without jumping to the partner institution APP during the signing of the quick payment agreement;

[0059] If support is confirmed, query the basic information registration form of the partner organization to determine whether the institution information of the partner organization is stored;

[0060] If the information of the partner organization is confirmed to be stored, compliance verification will be performed;

[0061] If the verification is passed, query the pre-contract information registration table to determine whether the pre-contract record exists;

[0062] If it exists, then pre-contract verification is performed;

[0063] If the verification is passed, the pre-signing status is updated to pre-signing successful.

[0064] In one embodiment, the pre-contract verification process includes: controlling the maximum number of pre-contracts on the day, verifying customer certificate information, and verifying customer card information.

[0065] In one embodiment, the compliance verification process includes: field non-empty verification, document type verification, card type verification, institution and card type verification, blacklist and quick payment switch verification.

[0066] A quick payment agreement signing system includes: a client, an issuing bank APP, an issuing bank service end, a clearing institution, and a partner institution service end, wherein:

[0067] The client, the issuing bank APP, the issuing bank service end, the clearing institution, and the partner institution service end interact to complete the signing of the quick payment agreement;

[0068] Among them, the issuing bank service end and the partner institution service end support the preset agreement signing mode, wherein the preset agreement signing mode is a signing mode that does not require jumping to the partner institution APP during the process of signing the quick payment agreement.

[0069] An electronic device comprises a processor and a memory for storing instructions executable by the processor, wherein the steps of the above method are implemented when the processor executes the instructions.

[0070] A computer-readable storage medium stores computer instructions, which implement the steps of the above method when executed.

[0071] The quick payment agreement signing method and system, and computer-readable storage medium provided in the present application provide a signing mode in which there is no need to jump to the partner institution APP during the signing process of the quick payment agreement. In this way, when signing the quick payment agreement, the signing can be achieved only through the client, the issuing bank APP, the issuing bank service end, the clearing agency, and the partner institution service end, without the participation of the partner institution APP. In this way, even if the user has not installed the partner institution APP, the signing can be achieved, which solves the problem of the existing need to jump to the partner institution APP for signing, resulting in a cumbersome signing process and high requirements for user equipment, and achieves the technical effect of simply and efficiently signing a quick payment agreement. BRIEF DESCRIPTION OF THE DRAWINGS

[0072] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0073] Figure 1 This is the architecture diagram of the quick payment agreement signing system provided by this application;

[0074] Figure 2 It is a method flow chart of the quick payment agreement signing method provided by this application;

[0075] Figure 3 This is a schematic diagram of the quick payment agreement signing interaction provided by this application;

[0076] Figure 4 It is a schematic diagram of the pre-contracting process provided by this application;

[0077] Figure 5 This is a schematic diagram of the contract signing process provided by this application;

[0078] Figure 6 It is an architectural diagram of the computer terminal provided in this application. DETAILED DESCRIPTION

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

[0080] In view of the problem that the existing contract signing method requires users to download the target contract signing agency's APP, if the target contract signing agency APP is not downloaded and installed, then the contract cannot be signed. In this example, a quick payment agreement signing system is provided, such as Figure 1 As shown, it may include: a client 101, an issuing bank APP 102, an issuing bank service 103, a clearing agency 104, and a partner agency service 105, wherein: the client, the issuing bank APP, the issuing bank service, the clearing agency, and the partner agency service interact to complete the signing of the quick payment agreement; the issuing bank service and the partner agency service support a preset agreement signing mode, wherein the preset agreement signing mode is a signing mode in which there is no need to jump to the partner agency APP during the signing of the quick payment agreement.

[0081] That is, during the contract signing process, a contract signing mode is provided in which there is no need to jump to the partner institution APP during the process of signing a quick payment agreement. In this way, when signing a quick payment contract, the contract can be signed only through the client, the issuing bank APP, the issuing bank server, the clearing agency, and the partner institution server, without the participation of the partner institution APP. In this way, even if the user has not installed the partner institution APP, the contract can be signed. This solves the problem of the existing need to jump to the partner institution APP for signing, which leads to a cumbersome signing process and high requirements for user equipment, and achieves the technical effect of simply and efficiently signing a quick payment agreement.

[0082] Figure 2 It is a method flow chart of an embodiment of the quick payment agreement signing method provided by the present application. Although the present application provides method operation steps or device structures as shown in the following embodiments or drawings, more or fewer operation steps or module units may be included in the method or device based on routine or no creative labor. In the steps or structures where there is no necessary causal relationship logically, the execution order of these steps or the module structure of the device is not limited to the execution order or module structure described in the embodiments of the present application and shown in the drawings. When the method or module structure described is applied to an actual device or terminal product, it can be connected according to the method or module structure shown in the embodiment or drawings for sequential execution or parallel execution (for example, a parallel processor or a multi-threaded processing environment, or even a distributed processing environment).

[0083] Specifically, Figure 2 As shown, in this example, a quick payment agreement signing method is provided, which may include the following steps:

[0084] Step 201: The issuing bank APP receives the card number and partner institution selected by the customer, and selects a signing method that does not require jumping to the partner institution APP during the signing of the quick payment agreement;

[0085] Step 202: The issuing bank service end receives the customer information and the name of the partner institution uploaded by the issuing bank APP;

[0086] Step 203: The issuing bank service end completes the pre-signing with the clearing institution and the partner institution service end, and displays the partner institution's account number to the customer through the issuing bank APP;

[0087] Among them, the issuing bank service end completes the pre-signing with the clearing institution and the partner institution service end, and displays the partner institution's account to the customer through the issuing bank APP, which may include: the issuing bank service end obtains customer information through the issuing bank APP; the issuing bank service end calls the pre-signing module to perform pre-signing; the issuing bank service end encrypts the customer information and the partner institution information and transmits it to the clearing institution, which is transparently transmitted to the partner institution service end; the partner institution service end matches the customer's account in the partner institution based on the customer information; the partner institution service transparently transmits the account matching result information to the issuing bank service end through the clearing institution; and displays the account matching result to the customer through the issuing bank APP.

[0088] For example, the issuing bank APP can upload customer information and call the pre-contract module of the issuing bank server, where the uploaded customer information may include: name, ID type, ID number, bank card number, and mobile phone number. The issuing bank server calls the pre-contract module for verification, and the issuing bank server assembles the encrypted customer information and partner institution information together to assemble a message and send it to the clearing agency, where the customer information includes: name, ID type, ID number, bank card number, and mobile phone number. After receiving the message, the clearing agency transmits the message information to the partner institution based on the partner institution information in the message. The partner institution server parses the customer information message, obtains the customer information, and matches the customer's account number at the partner institution based on the mobile phone number:

[0089] A. If there is a corresponding account, determine whether the identity information (name, ID type, ID number) is consistent.

[0090] A.1. If the identity information is consistent, the account number of the customer's partner institution will be returned;

[0091] A.2. If the identity information is inconsistent, an error message will be returned saying "the mobile number is already in use by someone else".

[0092] B. If there is no corresponding account, an error message "No valid account found" will be returned.

[0093] Through the above method, account matching can be achieved in the pre-contract stage, and the matched accounts can be returned to the customer for selection. For example, if two accounts are matched, both accounts can be presented to the customer, and the customer can choose according to needs.

[0094] The issuing bank server calls the pre-contract module to perform pre-contract verification, which may include:

[0095] S1: The issuing bank service end queries the special institution information registration table to determine whether the partner institution supports the signing mode without jumping to the partner institution APP during the signing of the quick payment agreement;

[0096] S2: If support is confirmed, query the basic information registration form of the partner organization to determine whether the organization information of the partner organization is stored;

[0097] S3: When it is determined that the institution information of the partner institution is stored, a compliance verification process is performed;

[0098] Among them, the compliance verification processing may include: field non-empty verification, document type verification, card type verification, institution and card type verification, blacklist and quick payment switch verification.

[0099] S4: If the verification is passed, query the pre-contract information registration table to determine whether the pre-contract record exists;

[0100] S5: If it exists, perform pre-contract verification processing;

[0101] Among them, the pre-contract verification process may include: controlling the maximum number of pre-contracts on the day, verifying customer certificate information, and verifying customer card information.

[0102] S6: If the verification is passed, the pre-signing status is updated to pre-signing success.

[0103] Step 204: The issuing bank APP receives the selection operation of the partner institution's account and transmits it to the issuing bank service end;

[0104] Step 205: The issuing bank service end completes the contract with the clearing agency and the partner agency service end.

[0105] Among them, the issuing bank service end completes the contract with the clearing agency and the partner agency service end, which may include: the issuing bank service end obtains the customer's contract information and calls the contract module to sign the contract; the issuing bank service end assembles the customer's contract information, the partner account information and the partner agency information selected by the customer, and sends them to the clearing agency; the issuing bank APP displays the contract success interface; the clearing agency transmits the customer agreement information message to the corresponding partner agency service end based on the partner agency information; the partner agency service receives and parses the customer agreement information message and the partner account information selected by the customer to sign the contract, and registers the customer agreement into the database.

[0106] Specifically, calling the signing module to sign a contract may include:

[0107] S1: The issuing bank service end queries the special institution information registration table to determine whether the partner institution information is stored in the special institution information registration table;

[0108] S2: If it is confirmed that the information exists, query the basic information registration form of the partner institution to determine whether the partner institution information exists on the issuing bank's service end;

[0109] S3: If it is determined that the problem exists, conduct compliance verification.

[0110] S4: If the verification is passed, query the pre-contract information registration table to determine whether the pre-contract record exists;

[0111] S5: If it exists, then perform contract verification processing;

[0112] Among them, the contract verification process may include: verifying customer ID information, verifying customer card information, and verifying customer mobile phone number.

[0113] S6: If the verification is passed, query the contract information registration table to determine whether the contract record exists;

[0114] S7: If it exists, update the data in the contract information registration table; if it does not exist, add the contract data to the contract information registration table;

[0115] S8: Update the pre-contract status in the pre-contract information registration table to successful contract signing.

[0116] For example: query the special institution information registration table to determine whether the submitted partner institution information is stored in the table. If it does not exist, the access is not passed and an error is returned: the institution does not support the contract signing of this type of business for the time being; if it exists, the access is passed, query the partner institution basic information registration table to determine whether the contract signing institution information exists in the issuing bank. If it does not exist, an error is returned: the basic information of the institution does not exist; if it exists, a compliance check is performed, wherein the compliance check includes: field non-empty check, certificate type check, card type check, institution and card type check, blacklist and quick payment switch check. If the compliance check fails, a corresponding error is returned; if the compliance check passes, the pre-contract information registration table is queried according to the contract information to make a judgment: if there is no pre-contract record or there is a pre-contract record but the pre-contract status is failed, an error "pre-contract failed, please re-contract" is reported; if there is a pre-contract record and the pre-contract status is successful, a contract verification is performed to verify the customer's certificate information, card information and mobile phone number. If the contract verification fails, the pre-contract status is updated to pre-contract failure; if the contract verification passes, it is determined whether there is a record in the contract information registration table. If there is a record, the data in the contract table is updated; if there is no record, the contract data is added to the contract information registration table. The pre-contract status in the pre-contract information registration table is updated to contract success.

[0117] The above method is described below in conjunction with a specific embodiment. However, it should be noted that this specific embodiment is only for better illustrating the present application and does not constitute an improper limitation on the present application.

[0118] This example mainly solves the problem that bank customers cannot sign contracts when the target signing institution APP is not installed on their devices. It proposes a method for signing a cardless quick payment agreement without jumping to the target institution APP, and can support customers to freely switch to the institution account they want to sign when signing.

[0119] In this example, a signing system is provided, including: bank customers, issuing bank APP, issuing bank server, clearing agency, and partner agency server.

[0120] The issuing bank and the partner institution that is willing to support this contract mode (signing a cardless quick payment agreement without jumping to the target institution's APP) reach an agreement in advance, and the partner institution provides an interface for the issuing bank to call, so as to support the issuing bank to query the customer's account opened in the partner institution based on the customer information. During the query process, the issuing bank service end and the partner institution service end call according to the pre-agreed call specifications, and the issuing bank server sends the customer information, where the sent customer information may include: name, mobile phone number, ID type, ID number, and the partner service end returns the customer's account number in the partner institution and the query results to the issuing bank service end. During the message transmission process between the issuing bank service end and the partner institution service end, both parties encrypt and decrypt the message according to the pre-agreed public key and private key to ensure the security of information transmission.

[0121] Based on the above signing system, you can Figure 3 The interactive process shown is used to sign the contract:

[0122] Step 1: The customer selects the card number and partner institution they want to sign on the issuing bank’s APP, triggers the signing operation, and chooses the signing mode without jumping to the APP.

[0123] Step 2: The issuing bank APP uploads customer information and calls the pre-signing module on the issuing bank's server. The uploaded customer information may include: name, ID type, ID number, bank card number, and mobile phone number.

[0124] Step 3: The issuing bank server calls the pre-signing module for verification.

[0125] Step 4: The issuing bank server assembles the encrypted customer information and partner institution information into a message and sends it to the clearing institution. The customer information includes: name, ID type, ID number, bank card number, and mobile phone number.

[0126] Step 5: After receiving the message, the clearing agency transmits the message information to the partner agency according to the partner agency information in the message.

[0127] Step 6: The partner organization server parses the customer information message, obtains the customer information, and matches the customer's account number at the partner organization based on the mobile phone number:

[0128] A. If there is a corresponding account, determine whether the identity information (name, ID type, ID number) is consistent.

[0129] A.1. If the identity information is consistent, the account number of the customer's partner institution will be returned;

[0130] A.2. If the identity information is inconsistent, an error message will be returned saying "the mobile number is already in use by someone else".

[0131] B. If there is no corresponding account, an error message "No valid account found" will be returned.

[0132] Step 7: The partner organization assembles and encrypts the corresponding return information (the customer's partner organization account number / error information) and sends it to the clearing organization.

[0133] Step 8: The clearing agency transmits the returned information message to the issuing bank.

[0134] Step 9: The issuing bank server parses the returned information message to determine whether the query of the customer's partner institution account is successful.

[0135] A. If the query is successful, the issuing bank's APP will display the customer's partner institution account number.

[0136] B. If the query is unsuccessful, the issuing bank’s APP will display the error information in the returned message.

[0137] Step 10: The customer selects the account of the partner institution with which he wants to sign a contract on the issuing bank’s APP.

[0138] Step 11: The issuing bank server sends the customer's contract information to the issuing bank server and calls the contract module on the issuing bank server for verification.

[0139] Step 12: The issuing bank server assembles the customer agreement information, the customer's selected partner account information and the partner institution information and sends them to the clearing agency.

[0140] Step 13: The issuing bank’s APP displays the successful signing interface to the customer.

[0141] Step 14: The clearing institution transmits the customer agreement information message to the corresponding partner institution based on the partner institution information.

[0142] Step 15, the partner organization receives and parses the customer agreement information message and the partner account information selected by the customer to sign the contract and registers the customer agreement into the database.

[0143] Among them, the above-mentioned pre-signing module can be as follows Figure 4 The pre-signing operation is performed according to the following process:

[0144] Step 1, query the special organization information registration table as described in Table 1 below to determine whether the submitted partner organization information is stored in the table.

[0145] Table 1 Special institution information registration form

[0146] Field Name Chinese name Field Description CORPNO Institution Number The partner institution's unique identifier at the issuing bank ISSUPPORT Whether to support this contract mode 0-Not supported, 1-Supported

[0147] If it exists, the access is passed and proceed to Step 2.

[0148] If it does not exist, access will be denied and an error will be returned: This institution does not currently support signing of this type of business.

[0149] Step 2: Query the basic information of the partner organization in Table 2 below to determine whether the contracting organization information exists in the issuing bank.

[0150] Table 2 Basic information registration form of partner organization

[0151] Field Name Chinese name Field Description CORPNO Institution Number The partner institution's unique identifier at the issuing bank IDTYPE_CTRL Document type control Contract certificate type control CARDTYPE_CTRL Card type control Contract card type control BLACKLIST_CTRL Blacklist control Blacklist SWITCH_CTRL Quick payment switch control Whether to support quick payment MAX_SIGN_TIMES Maximum number of pre-signings on the day Maximum number of pre-signings per card per day MAX_SEND_TIMES Maximum number of verification code sending times per day Maximum number of verification code sending times per card per day MAX_ERR_TIMES Maximum number of incorrect verification code entries on the day Maximum number of incorrect verification code inputs per card per day

[0152] If it does not exist, an error message will be returned: The basic information of the organization does not exist.

[0153] If it exists, proceed to Step 3.

[0154] Step 3, perform compliance verification, where the compliance verification may include: field non-empty verification, document type verification, card type verification, institution and card type verification, blacklist and quick payment switch verification.

[0155] If the compliance check fails, a corresponding error is returned.

[0156] If the compliance check passes, proceed to Step 4.

[0157] Step 4: query the pre-contract information registration table shown in Table 3 below according to the contract information to determine whether there is a corresponding pre-contract record.

[0158] Table 3 Pre-contract information registration form

[0159]

[0160]

[0161] If it exists, proceed to Step 5.

[0162] If it does not exist, create a new pre-contract record in the pre-contract information registration table and proceed to Step 4.

[0163] Step 5, perform pre-contract verification processing, wherein the pre-contract verification processing includes: controlling the maximum number of pre-contracts on the day, and verifying the customer's ID information and card information.

[0164] If the pre-contract verification fails, the pre-contract status is updated to pre-contract failure.

[0165] If the pre-contract verification passes, the pre-contract status is updated to pre-contract success.

[0166] In the pre-contracting process, compared with the original contracting method, a new step is added before Step 1 to determine whether the contracting institution supports this contracting mode, thereby distinguishing the contracting mode in this example from the original contracting mode. In addition, since the customer initiates the contracting from the issuing bank APP, the identity authentication link has been completed by default, so there is no need for identity authentication during the contracting process, and there is no need to verify the SMS verification code. Therefore, in the process of Step 4 pre-contracting verification processing, the control of the maximum number of verification code sending times, the verification of the mobile phone number, and the sending of the SMS verification code are deleted.

[0167] The above signing module can be Figure 5 As shown, the signing operation is performed according to the following process:

[0168] Step 1, query the special organization information registration table in Table 1 above to determine whether the submitted partner organization information is stored in the table.

[0169] If it exists, the access is passed and proceed to Step 2.

[0170] If it does not exist, access will be denied and an error will be returned: This institution does not currently support signing of this type of business.

[0171] Step 2, query the basic information registration form of the partner organization in Table 2 above to determine whether the contracting organization information exists in the issuing bank.

[0172] If it does not exist, an error message will be returned: The basic information of the organization does not exist.

[0173] If it exists, proceed to Step 3.

[0174] Step 3, perform compliance verification, where the compliance verification includes: field non-empty verification, document type verification, card type verification, institution and card type verification, blacklist and quick payment switch verification.

[0175] If the compliance check fails, a corresponding error is returned.

[0176] If the compliance check passes, proceed to Step 4.

[0177] Step 4: Check the pre-contract information registration form based on the contract information in Table 3 above to make a judgment:

[0178] If there is no pre-contract record or there is a pre-contract record but the pre-contract status is failed, an error message will be displayed: "Pre-contract failed, please pre-contract again."

[0179] If there is a pre-contract record and the pre-contract status is successful, proceed to Step 5.

[0180] Step 5: Conduct contract verification to verify the customer’s ID information, card information and mobile phone number.

[0181] If the contract verification fails, the pre-contract status is updated to pre-contract failure.

[0182] If the contract verification passes, proceed to Step 6.

[0183] Step 6, determine whether there is a record in the contract information registration table shown in Table 4 below.

[0184] Table 4 Contract Information Registration Form

[0185] Field Name Chinese name Field Description TRXID serial number Generated by the issuing bank, unique CUST_ACC Contract card number Contract customer's contract card number CUST_NAME Customer Name Name of contracted customer CUST_ID_TYPE Document type Type of customer ID CUST_ID_NO ID number Contracting customer ID number CUST_PHONE Contract phone number Mobile phone number of the contracting customer STATUS Contract Status Successful contract signing, failed contract signing KJNO Quick Agreement Number The issuing bank generates a

[0186] If there is a record, update the data in the contract table.

[0187] If there is no record, add the contract data to the contract information registration table.

[0188] Step 7, update the pre-contract status in the pre-contract information registration form to successful contract signing.

[0189] In the contract signing process, compared with the original contract signing method, a new step is added before Step 1 to determine whether the contract signing institution supports this contract signing mode, thereby distinguishing the contract signing mode in this example from the original contract signing mode. In addition, since there is no need to verify the SMS verification code, in the Step 4 contract signing verification process, the control of the validity of the SMS verification code, the control of the maximum number of verification code inputs, and the control of verification code matching are deleted.

[0190] In this case, a method and system for signing a cardless quick payment agreement without jumping to the target institution APP is proposed, which can solve the problem that bank customers cannot sign contracts when the target contracting institution APP is not installed on their mobile devices, and supports customers to freely switch the account of the institution they want to sign when signing. In this case, for the purpose of improving the convenience of cardless quick signing, the issuing bank actively queries and displays the customer's account number at the target contracting institution. After the customer selects the account number, the issuing bank completes the signing in the background and notifies the contracting institution, which effectively reduces the interaction between bank customers and multiple systems and improves the efficiency of business handling.

[0191] The method embodiments provided in the above embodiments of the present application can be executed on a mobile terminal, a computer terminal or a server, wherein the client and the issuing bank APP can be a computer terminal or a mobile terminal, and the issuing bank service end, the clearing institution, and the partner institution service end can be a server.

[0192] Taking running on electronic devices as an example, Figure 6This is a hardware structure diagram of an electronic device for a quick payment agreement signing method provided by this application. Figure 6 As shown, the electronic device 10 may include one or more (only one is shown in the figure) processors 02 (the processor 02 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA), a memory 04 for storing data, and a transmission module 06 for communication functions. It can be understood by those skilled in the art that Figure 6 The structure shown is only for illustration and does not limit the structure of the above electronic device. Figure 6 More or fewer components as shown, or with Figure 6 Different configurations are shown.

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

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

[0195] The electronic device mentioned above may be located at the service end of the card issuing bank. Specifically, the following operations may be performed:

[0196] S1: When the selected contract signing mode is a contract signing mode without jumping to the partner institution APP during the process of signing the quick payment agreement, receiving the customer information and the partner institution name uploaded by the issuing bank APP;

[0197] S2: Complete the pre-signing agreement with the clearing agency and the partner agency service end, and display the partner agency's account number to the customer through the issuing bank's APP;

[0198] S3: Receive the customer's selection of the partner institution's account through the issuing bank's APP;

[0199] S4: Complete the contract signing with the clearing agency and the partner agency service end.

[0200] In one embodiment, the issuing bank service end completes the pre-signing with the clearing institution and the partner institution service end, and displays the partner institution's account to the customer through the issuing bank APP, which may include: the issuing bank service end obtains customer information through the issuing bank APP; the issuing bank service end calls the pre-signing module to perform pre-signing; the issuing bank service end encrypts the customer information and the partner institution information and transmits them to the clearing institution, which is transparently transmitted to the partner institution service end; the issuing bank service end receives the customer's account in the partner institution matched by the partner institution server according to the customer information; the issuing bank service end displays the account matching result to the customer through the issuing bank APP.

[0201] In one embodiment, the issuing bank service end calls the pre-contract module to perform pre-contract verification, which may include: the issuing bank service end queries the special institution information registration table to determine whether the partner institution supports the contract signing mode without jumping to the partner institution APP during the quick payment agreement signing process; if it is determined to be supported, query the partner institution basic information registration table to determine whether the institution information of the partner institution is stored; if it is determined that the institution information of the partner institution is stored, perform compliance verification; if the verification passes, query the pre-contract information registration table to determine whether the pre-contract record exists; if it exists, perform pre-contract verification; if the verification passes, update the pre-contract status to successful pre-contract.

[0202] In one embodiment, the pre-contract verification process may include, but is not limited to, at least one of the following: controlling the maximum number of pre-contracts on the day, verifying customer certificate information, and verifying customer card information.

[0203] In one embodiment, the compliance verification process may include but is not limited to at least one of the following: field non-empty verification, document type verification, card type verification, institution and card type verification, blacklist and quick payment switch verification.

[0204] In one embodiment, the issuing bank service end completes the contract signing with the clearing agency and the partner agency service end, which may include: the issuing bank service end obtains the customer's contract signing information, and calls the contract signing module to sign the contract; the issuing bank service end assembles the customer's contract signing information, the customer's selected partner account information and the partner agency information, and sends them to the clearing agency; the issuing bank APP displays the contract signing success interface; the clearing agency transmits the customer agreement information message to the corresponding partner agency service end based on the partner agency information; the partner agency service receives and parses the customer agreement information message and the partner account information selected by the customer to sign the contract, and registers the customer agreement into the database.

[0205] In one embodiment, calling the contract signing module to sign a contract may include: the issuing bank service end queries the special institution information registration table to determine whether the partner institution information is stored in the special institution information registration table; if it is determined to exist, query the partner institution basic information registration table to determine whether the partner institution information exists on the issuing bank service end; if it is determined to exist, perform compliance verification processing; if the verification passes, query the pre-contract information registration table to determine whether the pre-contract record exists; if it exists, perform contract signing verification processing; if the verification passes, query the contract signing information registration table to determine whether the contract signing record exists; if it exists, update the data in the contract signing information registration table; if it does not exist, add contract signing data to the contract signing information registration table; update the pre-contract signing status in the pre-contract signing information registration table to successful contract signing.

[0206] In one embodiment, the contract signing verification process may include: verifying customer ID information, verifying customer card information, and verifying customer mobile phone number.

[0207] The embodiments of the present application also provide a specific implementation of an electronic device capable of implementing all the steps in the quick payment agreement signing method in the above embodiments, wherein the electronic device specifically includes the following contents: a processor, a memory, a communication interface, and a bus; wherein the processor, the memory, and the communication interface communicate with each other through the bus; the processor is used to call a computer program in the memory, and when the processor executes the computer program, all the steps in the quick payment agreement signing method in the above embodiments are implemented. For example, when the processor executes the computer program, the following steps are implemented:

[0208] Step 1: When the contract signing mode selected is a contract signing mode without jumping to the partner institution APP during the process of signing the quick payment agreement, the issuing bank service end receives the customer information and the partner institution name uploaded by the issuing bank APP;

[0209] Step 2: The issuing bank service end completes the pre-signing with the clearing agency and the partner agency service end, and displays the partner agency's account number to the customer through the issuing bank APP;

[0210] Step 3: The issuing bank service end receives the customer's selection of the partner institution's account through the issuing bank APP;

[0211] Step 4: The issuing bank service end completes the contract with the clearing agency and the partner agency service end.

[0212] From the above description, it can be seen that the embodiment of the present application provides a signing mode in which there is no need to jump to the partner institution APP during the process of signing a quick payment agreement. In this way, when signing a quick payment agreement, the contract can be signed only through the client, the issuing bank APP, the issuing bank service, the clearing agency, and the partner institution service. The participation of the partner institution APP is not required. In this way, even if the user has not installed the partner institution APP, the contract can be signed. This solves the problem of the existing need to jump to the partner institution APP for signing, which leads to a cumbersome signing process and high requirements for user equipment, and achieves the technical effect of simply and efficiently signing a quick payment agreement.

[0213] The embodiments of the present application also provide a computer-readable storage medium capable of implementing all the steps in the quick payment agreement signing method in the above embodiments. The computer-readable storage medium stores a computer program. When the computer program is executed by a processor, all the steps in the quick payment agreement signing method in the above embodiments are implemented. For example, when the processor executes the computer program, the following steps are implemented:

[0214] Step 1: When the contract signing mode selected is a contract signing mode without jumping to the partner institution APP during the process of signing the quick payment agreement, the issuing bank service end receives the customer information and the partner institution name uploaded by the issuing bank APP;

[0215] Step 2: The issuing bank service end completes the pre-signing with the clearing agency and the partner agency service end, and displays the partner agency's account number to the customer through the issuing bank APP;

[0216] Step 3: The issuing bank service end receives the customer's selection of the partner institution's account through the issuing bank APP;

[0217] Step 4: The issuing bank service end completes the contract with the clearing agency and the partner agency service end.

[0218] From the above description, it can be seen that the embodiment of the present application provides a signing mode in which there is no need to jump to the partner institution APP during the process of signing a quick payment agreement. In this way, when signing a quick payment agreement, the contract can be signed only through the client, the issuing bank APP, the issuing bank service, the clearing agency, and the partner institution service. The participation of the partner institution APP is not required. In this way, even if the user has not installed the partner institution APP, the contract can be signed. This solves the problem of the existing need to jump to the partner institution APP for signing, which leads to a cumbersome signing process and high requirements for user equipment, and achieves the technical effect of simply and efficiently signing a quick payment agreement.

[0219] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the hardware + program embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0220] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0221] Although the present application provides method operation steps as described in the embodiments or flowcharts, more or fewer operation steps may be included based on conventional or non-creative labor. The order of steps listed in the embodiments is only one way of executing the order of many steps and does not represent the only execution order. When the actual device or client product is executed, it can be executed in the order of the method shown in the embodiments or the drawings or in parallel (for example, in a parallel processor or multi-threaded processing environment).

[0222] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a vehicle-mounted human-computer interaction device, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0223] Although the present specification embodiment provides the method operation steps as described in the embodiment or flow chart, more or less operation steps may be included based on conventional or non-creative means. The order of steps listed in the embodiment is only one way in the order of execution of many steps, and does not represent a unique execution order. When the device or terminal product in practice is executed, it can be executed in sequence or in parallel (such as a parallel processor or a multi-threaded processing environment, or even a distributed data processing environment) according to the method shown in the embodiment or the accompanying drawings. The term "include", "comprise" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, product or equipment including a series of elements not only includes those elements, but also includes other elements not clearly listed, or also includes elements inherent to such process, method, product or equipment. In the absence of more restrictions, it is not excluded that there are other identical or equivalent elements in the process, method, product or equipment including the elements.

[0224] For the convenience of description, the above devices are described in various modules according to their functions. Of course, when implementing the embodiments of this specification, the functions of each module can be implemented in the same or more software and / or hardware, or the module implementing the same function can be implemented by a combination of multiple sub-modules or sub-units. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0225] Those skilled in the art also know that, in addition to implementing the controller in a purely computer-readable program code, the controller can be made to implement the same function in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers by logically programming the method steps. Therefore, such a controller can be considered as a hardware component, and the devices for implementing various functions included therein can also be considered as structures within the hardware component. Or even, the devices for implementing various functions can be considered as both software modules for implementing the method and structures within the hardware component.

[0226] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0227] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0228] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0229] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0230] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0231] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0232] Those skilled in the art will appreciate that the embodiments of this specification may be provided as methods, systems or computer program products. Therefore, the embodiments of this specification may take the form of complete hardware embodiments, complete software embodiments or embodiments combining software and hardware. Moreover, the embodiments of this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0233] The present specification embodiments may be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The present specification embodiments may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules may be located in local and remote computer storage media, including storage devices.

[0234] Each embodiment in this specification is described in a progressive manner, and the same and similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. In the description of this specification, the description of the reference terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the embodiment of this specification. In this specification, the schematic representation of the above terms does not necessarily target the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner. In addition, in the absence of contradiction, a person skilled in the art can combine and combine the different embodiments or examples described in this specification and the features of different embodiments or examples.

[0235] The above is only an example of the embodiment of the present specification and is not intended to limit the embodiment of the present specification. For those skilled in the art, the embodiment of the present specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the embodiment of the present specification shall be included in the scope of the claims of the embodiment of the present specification.

Claims

1. A method for signing a quick payment agreement, characterized in that: include: The issuing bank APP receives the card number and partner institution selected by the customer, and selects a signing method that does not require jumping to the partner institution APP during the signing of the quick payment agreement; The issuing bank service end receives the customer information and the name of the partner institution uploaded by the issuing bank APP; The issuing bank service end completes the pre-signing with the clearing agency and the partner agency service end, and displays the partner agency's account number to the customer through the issuing bank APP; The issuing bank APP receives the selected operation of the partner institution's account and transmits it to the issuing bank's service end; The issuing bank service end signs a contract with the clearing agency and the partner agency service end; Among them, before the issuing bank APP receives the card number and partner institution selected by the customer for signing, and selects the signing method as a signing mode in which no jump to the partner institution APP is required during the signing of the quick payment agreement, it also includes: judging whether the partner institution supports the signing method in which no jump to the partner institution APP is required during the signing of the quick payment agreement; Among them, the customer information uploaded by the issuing bank APP includes: name, ID type, ID number, bank card number, and mobile phone number. Correspondingly, the issuing bank service end completes the pre-contracting contract with the clearing agency and the partner agency service end, including: the issuing bank service end calls the pre-contracting module for verification, the issuing bank service end assembles the encrypted customer information and the partner agency information together to assemble a message and sends it to the clearing agency. After receiving the message, the clearing agency transmits the message information to the partner agency according to the partner agency information in the message. The partner agency service end parses the customer information message, obtains the customer information, and matches the customer's account in the partner agency according to the mobile phone number.

2. The method according to claim 1, characterized in that: The issuing bank service end completes the pre-signing with the clearing agency and the partner agency service end, and displays the partner agency's account number to the customer through the issuing bank APP, including: The issuing bank server obtains customer information through the issuing bank APP; The issuing bank's server calls the pre-signing module to perform pre-signing; The issuing bank service end encrypts the customer information and the partner institution information and transmits it to the clearing institution, which then transparently transmits it to the partner institution service end; The partner institution's service end matches the customer's account in the partner institution based on the customer information; The partner institution service transmits the account matching result information to the issuing bank service end through the clearing institution; The account matching results are displayed to the customer through the issuing bank’s APP.

3. The method according to claim 2, characterized in that The issuing bank server calls the pre-contract module to perform pre-contract verification, including: The issuing bank service end queries the special institution information registration table to determine whether the partner institution supports the signing mode without jumping to the partner institution APP during the signing of the quick payment agreement; If support is confirmed, query the basic information registration form of the partner organization to determine whether the institution information of the partner organization is stored; If the information of the partner organization is confirmed to be stored, compliance verification will be performed; If the verification is passed, query the pre-contract information registration table to determine whether the pre-contract record exists; If it exists, then pre-contract verification is performed; If the verification is passed, the pre-signing status is updated to pre-signing successful.

4. The method according to claim 3, characterized in that The pre-contract verification process includes: controlling the maximum number of pre-contracts on the day, verifying customer ID information, and verifying customer card information.

5. The method according to claim 3, characterized in that: Compliance verification processing includes: field non-empty verification, document type verification, card type verification, institution and card type verification, blacklist and quick payment switch verification.

6. The method according to claim 1, characterized in that The issuing bank service end signs a contract with the clearing agency and the partner agency service end, including: The issuing bank service end obtains the customer's contract information and calls the contract signing module to sign the contract; The issuing bank service end assembles the customer's contract information, the customer's selected partner account information and partner institution information, and sends it to the clearing institution; The issuing bank APP displays a successful contract signing interface; The clearing institution transmits the client agreement information message to the corresponding partner institution service end according to the partner institution information; The partner agency service receives and parses the customer agreement information message and the account information of the partner selected by the customer to sign the contract, and registers the customer agreement into the database.

7. The method according to claim 6, characterized in that Call the signing module to sign, including: The issuing bank service end queries the special institution information registration table to determine whether the partner institution information is stored in the special institution information registration table; If it is confirmed that the information exists, query the basic information registration form of the partner institution to determine whether the partner institution information exists on the issuing bank's service end; If it is confirmed that there is a problem, conduct compliance verification. If the verification is passed, query the pre-contract information registration table to determine whether the pre-contract record exists; If it exists, the contract verification process is performed; If the verification is passed, query the contract information registration table to determine whether the contract record exists; If it exists, update the data in the contract information registration table; if it does not exist, add the contract data to the contract information registration table; Update the pre-contract status in the pre-contract information registration form to successful contract signing.

8. The method according to claim 7, characterized in that The contract verification process includes: verifying customer ID information, verifying customer card information, and verifying customer mobile phone number.

9. An electronic device, comprising a processor and a memory for storing processor-executable instructions, wherein the processor implements the steps of the method according to any one of claims 1 to 8 when executing the instructions.

10. A computer-readable storage medium having computer instructions stored thereon, wherein the instructions, when executed, implement the steps of the method according to any one of claims 1 to 8.

Images