Enterprise account management method and device, equipment and medium

Abstract

The invention relates to the field of computers, in particular to an enterprise account management method and device, equipment and a medium, and the method comprises the steps: obtaining account opening application information of an enterprise account, and the account opening application information comprises enterprise information provided by an enterprise object for opening a business account; when the account opening application information passes verification, obtaining an associated account of the enterprise object in a third-party financial platform; based on the associated account, acquiring account information of the associated account from the third-party financial platform; and opening the enterprise account based on the account information of the associated account to realize online account opening of the enterprise account.

Description

Technical Field

[0001] This disclosure generally relates to the field of computers, and more specifically to a method, apparatus, device, and medium for managing enterprise accounts. Background Technology

[0002] Account opening service is one of the basic services provided by financial institutions to businesses. In this process, when relevant personnel of a business need to open an account on a financial institution's platform to conduct financial transactions, they must complete a series of verification and account opening procedures, including submitting account opening information and binding account agreements. This account opening process is relatively cumbersome, consumes significant system resources of the financial institution's platform, and has low efficiency in obtaining account opening information, resulting in low overall account opening efficiency. Summary of the Invention

[0003] In view of the above-mentioned defects or deficiencies in the prior art, it is desirable to provide a method, apparatus, device and medium for managing enterprise accounts, so as to realize online account opening for enterprise accounts.

[0004] In a first aspect, embodiments of this application provide a method for managing enterprise accounts, including: Obtain the account opening application information of the enterprise account, which includes the enterprise information provided by the enterprise for opening a business account; When the account opening application information is verified, the associated account of the enterprise in the third-party financial platform is obtained; Based on the associated account, obtain the account information of the associated account from the third-party financial platform; The enterprise account is activated based on the account information of the associated account.

[0005] Secondly, embodiments of this application provide a management device for enterprise accounts, including: The first acquisition module is used to acquire account opening application information for enterprise accounts, including enterprise information provided by the enterprise for opening a business account; The second acquisition module is used to acquire the associated account of the enterprise in the third-party financial platform when the account opening application information is verified. The third acquisition module is used to acquire account information of the associated account from the third-party financial platform based on the associated account; The activation module is used to activate the enterprise account based on the account information of the associated account.

[0006] Thirdly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the method described in embodiments of this application.

[0007] Fourthly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in embodiments of this application.

[0008] Fifthly, embodiments of this application provide a computer program product, including a computer program, characterized in that, when the computer program is executed by a processor, it implements the method described in embodiments of this application.

[0009] The enterprise account management method, apparatus, device, and medium provided in this application embodiment obtain enterprise account opening application information. Upon successful verification of the application information, it obtains the associated account of the enterprise on a third-party financial platform. Based on the associated account, it retrieves the account information of the associated account from the third-party financial platform and activates the enterprise account based on this information. Therefore, this application embodiment provides an online function for creating and activating enterprise accounts. Simultaneously, by utilizing the account information of the associated account obtained from an external third-party financial platform as the account information for activating the enterprise account, it significantly reduces the complexity of enterprise users filling in account information while ensuring the reliability of account information, improves the efficiency of activating enterprise accounts on financial institution platforms, and enhances the user experience.

[0010] Additional aspects and advantages of the invention will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. Attached Figure Description

[0011] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings: Figure 1 This paper illustrates the implementation environment architecture of the enterprise account management method provided in the embodiments of this application; Figure 2 A flowchart illustrating a method for managing enterprise accounts according to an embodiment of this application is shown; Figure 3 A flowchart illustrating a method for managing enterprise accounts according to another embodiment of this application is shown; Figure 4 A flowchart illustrating a method for managing enterprise accounts according to another embodiment of this application is shown; Figure 5 A flowchart illustrating a method for managing enterprise accounts according to another embodiment of this application is shown; Figure 6 A flowchart illustrating a method for managing enterprise accounts according to another embodiment of this application is shown; Figure 7This invention provides a schematic diagram of the structure of a corporate account management device according to an embodiment of the present application. Figure 8 A schematic diagram of the structure of a computer system suitable for implementing an electronic device or server according to embodiments of this application is shown. Detailed Implementation

[0012] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings.

[0013] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0014] For the specific implementation environment of the enterprise account management method proposed in this application, please refer to [link / reference needed]. Figure 1 . Figure 1 This diagram illustrates the implementation environment architecture of the enterprise account management method provided in this application embodiment.

[0015] like Figure 1 As shown, the implementation environment architecture includes: terminal device 101, financial institution platform server 102, and third-party financial platform server 103.

[0016] Terminal device 101 is used to run an application client and provide an interactive interface to the user. This interface displays application form templates, such as templates for filling out enterprise account opening applications. Terminal device 101 can be a desktop computer, laptop computer, smartphone, tablet computer, e-book reader, smart glasses, smartwatch, in-vehicle device, ultra-mobile personal computer (UMPC), netbook, cellular phone, personal digital assistant (PDA), augmented reality (AR), or virtual reality (VR) device, but is not limited to these.

[0017] The financial institution platform server 102 is used to communicate with the terminal device 101 and to provide response services to the application client, so that the application client can provide corresponding service information to be displayed on the display interface, such as alarm information and interception notifications for pre-verification.

[0018] The third-party financial platform server 103 communicates with the financial institution platform server 102 to provide the financial institution platform server 102 with account information of associated accounts.

[0019] Financial institution platform server 102 and third-party financial platform server 103 can be independent physical servers, server clusters or distributed systems composed of multiple physical servers, or cloud servers that provide basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms.

[0020] Terminal device 101 is directly or indirectly connected to financial institution platform server 102, and financial institution platform server 102 is directly or indirectly connected to third-party financial platform server 103, via wired or wireless communication. Optionally, the aforementioned wireless or wired network uses standard communication technologies and / or protocols. The network is typically the Internet, but can also be any network, including but not limited to any combination of Local Area Network (LAN), Metropolitan Area Network (MAN), Wide Area Network (WAN), mobile, wired or wireless network, private network, or virtual private network.

[0021] also, Figure 1 The number of terminal devices, financial institution servers, and third-party financial platform servers shown in the document is merely exemplary and may actually include other numbers of terminal devices, servers, and audit terminals. This application does not specifically limit this number.

[0022] The enterprise account management method proposed in this application can be implemented by an enterprise account management device, which can be installed on a terminal device or a server.

[0023] To further illustrate the technical solutions provided in the embodiments of this application, a detailed description is provided below in conjunction with the accompanying drawings and specific implementation methods. Although the embodiments of this application provide method operation instruction steps as shown in the following embodiments or drawings, the method may include more or fewer operation instruction steps based on conventional or non-creative effort. In steps where there is no logically necessary causal relationship, the execution order of these steps is not limited to the execution order provided in the embodiments of this application. In actual processing or when the device executes the method, it may be executed sequentially or in parallel according to the method shown in the embodiments or drawings.

[0024] It should be noted that the acquisition or use of data in the embodiments of this application requires the user's consent. The relevant data can only be obtained after the user's authorization and permission, and the acquisition or use of the data complies with the laws and regulations of the relevant regions.

[0025] Please refer to Figure 2 , Figure 2 A flowchart illustrating a method for managing enterprise accounts according to an embodiment of this application is shown. Figure 2 As shown, the method includes: Step 201: Obtain the account opening application information for the enterprise account, which includes the enterprise information provided by the enterprise for opening a business account.

[0026] It should be noted that the business account opened by the enterprise is the enterprise's account on the financial institution's platform, which can be a platform that provides financial product transactions and related services.

[0027] In some embodiments, the enterprise information provided by the enterprise for opening a business account may include, but is not limited to, basic enterprise information, financial investment information, related party information, and account opening document information, etc., and this application does not impose specific limitations. Among them, basic enterprise information includes, but is not limited to, enterprise name, registered address, responsible person information, business scope, company type, and license information; financial investment information includes, but is not limited to, balance sheet and profit statement; related party information includes, but is not limited to, shareholder information, director information, and senior management information of the enterprise; and account opening document information includes, but is not limited to, tax return, tax registration certificate, company registration certificate, company name change certificate, business registration certificate, company organization and articles of association, etc.

[0028] In one feasible embodiment, the account opening application information can be filled in multiple times. Specifically, obtaining the account opening application information for a corporate account includes: in response to an account opening application exit instruction, storing the obtained account opening application information; and pre-filling the information based on the obtained account opening application information when obtaining an account opening application instruction again.

[0029] In other words, when corporate users are filling out account opening application information, they can exit the form. At this time, the financial institution platform can store the account opening application information that the user has already filled out, and when it receives the account opening application instruction again, it can use the stored account opening application information to pre-fill it, thereby effectively reducing the repetitive operations that corporate users need to perform when filling out account opening application information, improving the efficiency of filling out account opening application information, and improving the user experience.

[0030] Step 202: When the account opening application information is verified, obtain the associated account of the enterprise in the third-party financial platform.

[0031] This includes verifying and approving account opening application information. Verification and approval of account opening application information may include, but is not limited to, confirming the authenticity and completeness of the enterprise information required to open a business account, and that the enterprise information complies with relevant laws, regulations and account opening requirements.

[0032] In one feasible embodiment, the enterprise information may also include risk disclosure information signed by the enterprise entity; the verification and approval of the enterprise information may further include verifying and approving the risk disclosure information signed by the enterprise entity to confirm that the enterprise information meets one of the necessary conditions of relevant laws and regulations and account opening requirements.

[0033] It should be understood that when enterprise information verification is successful, it means that the enterprise information provided by the enterprise account meets the initial requirements of authenticity, completeness, and compliance with relevant laws, regulations, and account opening requirements, and an enterprise account can be created and opened for it. Based on this, the associated accounts of the enterprise entity on the third-party financial platform can be obtained.

[0034] The third-party financial platform refers to a financial platform other than a financial institution platform. This platform can provide the same or similar financial services as the financial institution platform. The third-party financial platform authorizes the financial institution platform to obtain account information of related accounts from it. Related accounts on the third-party platform are accounts created and opened by the enterprise on the platform. In some feasible embodiments, related accounts on the third-party financial platform can also be personal accounts of related persons of the enterprise on the platform; this application does not impose specific limitations.

[0035] In one specific embodiment, after the account opening application information is verified, the financial institution platform can request a third-party financial platform to find the associated account corresponding to the enterprise object based on the enterprise object's enterprise information. Specifically, enterprise identity feature information can be generated based on the enterprise object's enterprise information, and this enterprise identity feature information can be sent to the third-party financial platform. This allows the third-party financial platform to search for a matching target object in its local enterprise objects based on the enterprise identity feature information, identify the account corresponding to the target object as an associated account, and return the account identifier of the associated account to the financial institution platform.

[0036] In one specific embodiment, after the enterprise information is verified, the financial institution platform can also send an account opening information email to the enterprise. The enterprise receives the account opening information email through the financial institution platform's client and fills in the associated account information in the third-party financial platform. Specifically, the account opening information email may contain a link to fill in the associated account information. By triggering the link in the account opening information email, the user fills in the account identifier of the associated account in the third-party financial platform, enabling the financial institution platform to obtain the associated account information of the enterprise in the third-party financial platform.

[0037] More specifically, after the account opening application information is verified, the relevant personnel of the enterprise can be contacted offline to confirm the verification of the enterprise information. An email containing a link to fill in the account information on the third-party financial platform can then be sent to the enterprise's contact personnel. This allows the contact personnel to fill in the enterprise's associated account on the third-party financial platform. Thus, by using the account opening information email and offline contact, sufficient verification of the enterprise's contact personnel is achieved, improving the authenticity and security of the associated account provided by the third-party financial platform.

[0038] Step 203: Based on the associated account, obtain the account information of the associated account from the third-party financial platform.

[0039] After obtaining the account identifier of the associated account, an account information retrieval request can be generated based on the account identifier. This request is then sent to a third-party financial platform, which in turn returns the account information of the associated account based on the retrieval request.

[0040] Furthermore, to ensure the confidentiality of account information, the first public key and the first platform private key of the financial institution platform can be obtained first. Based on the initial public key and the account identifier of the associated account, an account public key corresponding to the associated account can be generated. Based on the initial private key and the account public key, an account private key matching the account public key can be generated. Then, the platform configuration information of the financial institution platform can be obtained. Based on the platform configuration information, the account public key, and the account identifier, an account information acquisition request can be generated. The platform configuration information is used to uniquely identify the business category of the financial institution platform and to indicate the business service category that the enterprise account created based on the associated account of the third-party financial platform participates in on the financial institution platform.

[0041] Upon receiving an account information request, a third-party financial platform can obtain the corresponding account information based on the account identifier. Then, based on the platform configuration information of the financial institution platform, it determines the target business category identifier of the associated account on the financial institution platform. This target business category identifier is then used as associated data. The account information is encrypted using the target business category identifier and a second platform private key before being returned to the financial institution platform. After obtaining the encrypted account information, the financial institution platform can decrypt it using its own business category identifier and account private key. This process uses the business category identifier to distinguish between different financial institution platforms, ensuring that even when different encryption methods are applied to the same enterprise object (or associated account), the encrypted account information can only be decrypted by the corresponding financial institution platform and corresponds one-to-one with the enterprise object associated with the account, thus guaranteeing encryption isolation and data security.

[0042] Specifically, a third-party financial platform can generate a second platform public key and a second platform private key. Based on the second platform private key and the account public key, it generates shared information. Then, based on the shared information and the target business category identifier, it generates a derived key. This derived key is used to encrypt the account information, and finally, the second platform public key and the encrypted account information are returned to the financial institution platform. The financial institution platform can then generate shared information based on the second platform public key and the account private key, and generate a derived key based on the shared information and the target business category identifier. This derived key is then used to decrypt the account information to obtain the final account information.

[0043] It is understandable that the public-private key pairs of the first platform, the second platform, and the account are all generated using elliptic curve cryptography. Let the first platform's private key be denoted as 's', and the first platform's public key as 'S', where S = s·G, and G represents the preset elliptic curve base point. Similarly, let the second platform's private key be denoted as 'b', and the second platform's public key as 'B', where B = b·G, and G represents the preset elliptic curve base point. Furthermore, the account public key PK_id can be generated from the first platform's public key S and the associated account's ID using a preset key generation algorithm, i.e., PK_id = S + H(S,ID)G = (s + H(S,ID))·G. The corresponding account private key sk_id can be represented as: sk_id = s + H(S,ID). Shared information, represented by SS, is generated based on the second platform's private key and the account public key, specifically as follows: SS=b·PK_id=b·(sk_id·G)=(b·sk_id)·G; Correspondingly, the shared information generated based on the second platform's public key and the account's private key can be represented as: SS=sk_id·B=sk_id·(b·G)=(b·sk_id)·G; The shared information generated by the third-party financial platform using the private key of the second platform and the public key of the account is consistent with the shared information generated by the financial institution platform using the public key of the second platform and the private key of the account. The third-party financial platform generates a derived key using the public key of the account and the business category identifier, which is the same as the derived key generated by the financial institution platform using the private key of the account and the same business category identifier. This ensures that only the financial institution platform decrypts the data, and that the data received by financial institution platforms of different business service categories are isolated from each other, thus ensuring the confidentiality of account information.

[0044] Step 204: Activate the enterprise account based on the account information of the associated account.

[0045] It should be noted that the account information obtained from the third-party financial platform is for opening a corporate account on the financial institution's platform. It should be understood that if the company already has an associated account on the third-party financial platform, the account information obtained from that associated account is the same as the company's account. Therefore, after obtaining the associated account information from the third-party financial platform, the company account can be opened based on that information without requiring the user to fill in any account information. This improves the efficiency of account information submission for companies on financial institution platforms while ensuring the reliability of the account information.

[0046] Therefore, the enterprise account management method provided in this application embodiment obtains the enterprise account opening application information, obtains the associated account of the enterprise in a third-party financial platform when the account opening application information is verified, obtains the account information of the associated account from the third-party financial platform based on the associated account, and opens the enterprise account based on the account information of the associated account. Thus, this application embodiment provides an online function for creating and opening enterprise accounts, and at the same time, it uses the account information of the associated account obtained from an external third-party financial platform as the account information for opening the enterprise account. This greatly reduces the complexity of enterprise entities filling in account information while ensuring the reliability of account information, improves the efficiency of opening enterprise accounts on financial institution platforms, and enhances the user experience.

[0047] In one feasible embodiment, obtaining account information of a related account from a third-party financial platform based on the related account includes: generating an account information synchronization task based on verification information and the related account; in response to the account information synchronization task, sending an account information acquisition request to the third-party financial platform, the account information acquisition request including the account identifier of the related account, and receiving the account information of the related account returned by the third-party financial platform.

[0048] In other words, when the account opening application information is verified, a verification pass message is generated, which triggers an account information synchronization task, changing the status of the account information synchronization task to "pending completion" or "pending execution." After obtaining the associated account provided by the enterprise, a complete account information synchronization task is generated and its execution is triggered. In response to the account information synchronization task, an account information retrieval request is sent to the third-party financial platform. The account information retrieval request includes the account identifier of the associated account. The third-party financial platform responds to the account information retrieval request by querying and retrieving the account information of the associated account. Then, the third-party financial platform returns the queried and retrieved account information of the associated account to the financial institution platform, which receives the account information of the associated account returned by the third-party financial platform.

[0049] Therefore, the present application embodiment, based on the verification information and the associated account, generates an account information synchronization task, which can promptly obtain the account information for opening a corporate account through a third-party financial platform when the information provided by the enterprise meets the account opening conditions, thereby improving the response efficiency of opening a corporate account and enhancing the user experience.

[0050] In another feasible embodiment, account information of multiple associated accounts is obtained from a third-party financial platform at a preset frequency, and multiple corporate accounts associated with the associated accounts are updated based on the account information of the multiple associated accounts.

[0051] In other words, in this embodiment of the application, the financial institution platform also provides the function of periodically obtaining account information from a third-party financial platform. Specifically, the financial institution platform sends account information update requests from the third-party financial platform to the third-party financial platform at a preset frequency. In response to the account information update requests, the third-party financial institution platform sends account information of multiple associated accounts to the financial institution platform. Based on the received account information of the multiple associated accounts, the financial institution platform updates the multiple corporate accounts associated with the multiple associated accounts.

[0052] Optionally, the third-party financial platform stores the account identifiers of the associated accounts included in the account information retrieval request each time it receives an account information retrieval request. In the event of a subsequent account information update request, the platform retrieves the account information of the multiple associated accounts based on the previously stored account identifiers and sends the retrieved account information of the multiple associated accounts to the financial institution platform.

[0053] The preset frequency can be set according to the financial institution's need to update account information. For example, the preset frequency can be daily, which means that account information of multiple related accounts is obtained from a third-party financial platform at a fixed time every day.

[0054] Specifically, such as Figure 3As shown, the financial institution platform is configured with two mechanisms for obtaining account information from a third-party financial platform. In one mechanism, the financial institution platform responds to a scheduled task by sending an account information update request to the third-party financial platform. The third-party financial platform, in response to the update request, obtains account information for multiple associated accounts and returns this information to the financial institution platform. The financial institution platform receives the account information from the third-party financial platform and updates the multiple corporate accounts associated with those accounts. In another mechanism, the financial institution platform reviews the account opening application information provided by the enterprise to open a corporate account. After the review is approved, a verification pass message is generated, which triggers an account information synchronization task. This means that the status of the account information synchronization task is changed to a pending or pending state. After obtaining the associated account provided by the enterprise, a complete account information synchronization task is generated and its execution is triggered. In response to the account information synchronization task, an account information retrieval request is sent to the third-party financial platform. The account information retrieval request includes the account identifier of the associated account. The third-party financial platform responds to the account information retrieval request by querying and retrieving the account information of the associated account. Then, the third-party financial platform returns the queried and retrieved account information of the associated account to the financial institution platform. The financial institution platform receives the account information of the associated account returned by the third-party financial platform, saves the account information of the associated account, and after confirming that the account information of the associated account has been successfully synchronized, it proceeds with the steps of opening the corporate account.

[0055] Therefore, this application provides two different mechanisms for financial institution platforms to synchronize account information of associated accounts from third-party financial platforms. In the mechanism of synchronizing account information of associated accounts at a preset frequency, it can ensure that the account information stored in the financial institution platform is consistent with that of the third-party financial platform in a timely manner, thereby ensuring the information integrity and functional support of corporate accounts in the financial institution platform. In the mechanism of generating account information synchronization tasks based on associated accounts to obtain account information of associated accounts, it can quickly obtain account information of associated accounts of corporate accounts to be opened, improve the response speed of obtaining account information of associated accounts, and ensure the efficiency of opening corporate accounts. At the same time, because the account information synchronization task only obtains account information of associated accounts of corporate accounts to be opened, the third-party financial platform can return account information of associated accounts in a shorter time, further improving the response speed of obtaining account information of associated accounts.

[0056] In one feasible embodiment, opening a corporate account based on the account information of the associated account includes: generating an account opening task based on the account information of the associated account; executing the account opening task, and creating an account opening associated task when the account opening task is completed; the account opening associated task includes multiple independently executed account opening associated sub-tasks; and the opening of the corporate account is completed when the multiple account opening associated sub-tasks are completed.

[0057] It should be noted that, in this application example, the account opening task is the task of synchronizing the account information of the associated account to the corporate account. The account opening associated task refers to other independently executable associated tasks related to the account opening task, which includes multiple independently executable sub-tasks. These sub-tasks do not affect each other's execution, but they have a strict execution order with the account opening task. That is, after the account opening task is completed, multiple sub-tasks can be executed separately, simultaneously, or sequentially, depending on the execution capabilities of the financial institution's platform. This application does not impose specific limitations on this.

[0058] It should also be noted that both the account opening task and the associated subtasks are configured with a retry mechanism. If the task fails, multiple retries will be triggered. If the number of retries for any task reaches the maximum preset number, an alarm notification will be issued to notify the developers to access and investigate.

[0059] In one specific embodiment, such as Figure 4 As shown, the account opening associated subtasks include the task of sending an account opening success message, the task of reporting an account opening completion event, and the task of unlocking the device.

[0060] In one feasible embodiment, the account opening task includes: performing pre-verification of the account information of the associated account; creating a corporate account when the account information of the associated account passes the pre-verification; binding the corporate account to the associated account and configuring the status of the corporate account as opened; and synchronizing the information of the associated account to the corporate account.

[0061] It should be noted that the account opening task includes multiple sub-tasks that synchronize account information from associated accounts to the corporate account. In other words, the account opening task is a set of tasks obtained by clustering the sub-tasks that synchronize account information from multiple associated accounts to the corporate account. When executing the account opening task, the multiple account opening sub-tasks are executed sequentially or simultaneously according to the execution order among them.

[0062] The account opening sub-tasks include pre-verification of account information of associated accounts, creation of enterprise accounts, binding of enterprise accounts with associated accounts, configuration of enterprise account status as opened, and synchronization of account information of associated accounts to enterprise accounts.

[0063] It should be understood that pre-verification of account information for associated accounts includes multiple verification subtasks, each used to verify different items in the account information. Pre-verification includes both non-intercepting and intercepting verification items. If the associated account information does not meet the non-intercepting verification item requirement, an alarm is sent, and the non-intercepting verification item is confirmed to have passed verification; if the associated account information does not meet the intercepting verification item requirement, the intercepting verification item is confirmed to have failed verification.

[0064] In other words, "do not intercept verification items" means that verification items for the account opening task will not be intercepted even if the verification conditions are not met, while "intercept verification items" means that verification items for the account opening task should be intercepted when the verification conditions are not met. Optionally, "do not intercept verification items" refers to verification items that are not yet compatible between the financial institution platform and the third-party financial platform. Therefore, when a "do not intercept verification item" fails verification, only an alarm message is sent to notify the financial institution platform's review personnel, and the account opening task is not intercepted.

[0065] In one specific embodiment, such as Figure 5 As shown, the system obtains the account information of the associated account and performs pre-verification on the account information. Verification items that are not blocked include verification of the source of funds type and investment type. If the verification of the source of funds type and / or investment type fails, such as due to mismatch, an alarm message is issued. Verification items that are blocked include verification of account type, verification of the account opening status of the associated account, verification of the company name corresponding to the associated account, and verification of the email address corresponding to the associated account. If any of the blocked verification items fails, an alarm message is issued and the account opening task is terminated.

[0066] After the account information of the associated account passes the pre-verification, the following steps are executed in sequence: create a corporate account, bind the corporate account to the associated account, configure the status of the corporate account to be opened, synchronize the account information of the associated account to the corporate account, and create an account opening association task after the account information of the associated account to the corporate account is synchronized.

[0067] In one feasible implementation, when creating a corporate account, the transaction type of the corporate account can be determined based on the transaction type of the associated account, and a general transaction type can be created for the corporate account to meet the basic transaction needs of the corporate account.

[0068] Furthermore, linking a corporate account to an associated account enables corporate users to conduct transactions through the associated account linked to the corporate account. In other words, a financial institution's corporate account can achieve its transaction objectives by leveraging an associated account on a third-party financial platform.

[0069] It should be understood that after the account opening task is completed, the account information stored in the corporate account on the financial institution platform is consistent with the account information of the associated account on the third-party financial platform, and is kept consistent with the account information of the associated account on the third-party financial platform through regular tasks, so that corporate users can view the account information of the associated account on the third-party financial platform through the corporate account on the financial institution platform.

[0070] In one specific embodiment, such as Figure 6 As shown, the system obtains the user's account opening application information, determines the user's account type, and if the user is opening a personal account, executes the relevant policies for personal account opening. If the user is opening a corporate account, it obtains the corporate account opening application information. The corporate user fills in the applicant information, corporate information, and signs a risk disclosure in the account opening application information. The corporate user submits the account opening application, and the financial institution platform creates a verification task to verify whether the corporate information passes the verification. If the corporate information verification fails, the corporate account application is rejected, and a rejection message is sent to the corporate user. If the corporate information verification partially passes, supplementary information can be sent to the corporate user so that the user can resubmit the corporate information. If the corporate information verification passes, the system contacts the corporate user offline and sends an invitation email to obtain the associated account from the third-party financial platform. The system obtains the account information of the associated account from the third-party financial platform, creates the corporate account, binds the corporate account to the associated account, configures the status of the corporate account to be opened, synchronizes the account information of the associated account to the corporate account, sends an account opening success message, reports the account opening success, and activates the account lock.

[0071] It should be noted that although the operation of the method of the present invention is described in a specific order in the accompanying drawings, this does not require or imply that the operations must be performed in that specific order, or that all the operations shown must be performed in order to achieve the desired result.

[0072] Figure 7 A schematic diagram of the structure of a corporate account management device according to an embodiment of this application is shown. Figure 7 As shown, the enterprise account management device 10 includes: The first acquisition module 11 is used to acquire the account opening application information of the enterprise account, wherein the account opening application information includes the enterprise information provided by the enterprise for opening a business account; The second acquisition module 12 is used to acquire the associated account of the enterprise in the third-party financial platform when the account opening application information is verified. The third acquisition module 13 is used to acquire account information of the associated account from the third-party financial platform based on the associated account; The activation module 14 is used to activate the enterprise account based on the account information of the associated account.

[0073] In some embodiments, the third acquisition module 13 is specifically used for: Based on the verification information and the associated account, an account information synchronization task is generated. In response to the account information synchronization task, an account information retrieval request is sent to the third-party financial platform, the account information retrieval request including the account identifier of the associated account; Receive account information of the associated account returned by the third-party financial platform.

[0074] In some embodiments, the activation module 14 is specifically used for: Based on the account information of the associated account, an account opening task is generated; The account opening task is executed, and an account opening associated task is created upon completion of the account opening task; the account opening associated task includes multiple independently executed account opening associated sub-tasks. The opening of the enterprise account is completed when multiple account opening-related sub-tasks are completed.

[0075] In some embodiments, the activation module 14 is specifically used for: Pre-verification of the account information of the associated accounts; When the account information of the associated account passes the pre-verification, the enterprise account is created; Bind the enterprise account to the associated account, and configure the status of the enterprise account to be "opened"; Synchronize the information of the associated account to the enterprise account.

[0076] In some embodiments, the pre-verification includes non-intercepted verification items and intercepted verification items. When the account information of the associated account does not meet the non-intercepted verification items, an alarm message is sent and it is confirmed that the non-intercepted verification items have passed the verification. When the account information of the associated account does not meet the intercepted verification items, it is confirmed that the intercepted verification items have failed the verification.

[0077] In some embodiments, the third acquisition module 13 is further configured to: Account information of multiple associated accounts is obtained from the third-party financial platform at a preset frequency; Based on the account information of the multiple associated accounts, update the multiple enterprise accounts associated with the associated accounts.

[0078] In some embodiments, the first acquisition module 11 is specifically used for: In response to an account opening application exit instruction, the acquired account opening application information is stored; When the account opening application instruction is obtained again, it is pre-filled based on the account opening application information that has already been obtained.

[0079] It should be understood that the modules or modules described in the enterprise account management device 10 are similar to those in the reference. Figure 2 The steps in the described method correspond accordingly. Therefore, the operations and features described above for the method also apply to the enterprise account management device 10 and its included modules, and will not be repeated here. The enterprise account management device 10 can be pre-implemented in the browser or other security applications of an electronic device, or it can be loaded into the browser or its security applications of an electronic device through download or other means. The corresponding modules in the enterprise account management device 10 can cooperate with the modules in the electronic device to implement the solutions of the embodiments of this application.

[0080] The division of modules or units mentioned in the detailed description above is not mandatory. In fact, according to the embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0081] The following is for reference. Figure 8 , Figure 8 A schematic diagram of the structure of a computer system suitable for implementing the embodiments of this application is shown. like Figure 8 As shown, the computer system 800 includes a central processing unit (CPU) 801, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 802 or programs loaded from storage section 808 into random access memory (RAM) 803. RAM 803 also stores various programs and data required for the system's operating instructions. CPU 801, ROM 802, and RAM 803 are interconnected via bus 804. Input / output (I / O) interface 805 is also connected to bus 804.

[0082] The following components are connected to I / O interface 805: an input section 806 including a keyboard, mouse, etc.; an output section 807 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as a LAN card, modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to I / O interface 805 as needed. A removable medium 811, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 810 as needed so that computer programs read from it can be installed into storage section 808 as needed.

[0083] Specifically, according to embodiments of this application, the flowchart above refers to... Figure 2 The described process can be implemented as a computer software program. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowchart. In such an embodiment, the computer program contains program code for performing the methods shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via communication section 809, and / or installed from removable medium 811. When the computer program is executed by central processing unit (CPU) 801, it performs the functions defined in the system of this application.

[0084] It should be noted that the computer-readable medium shown in this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0085] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operational instructions of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two connected blocks may actually be executed substantially in parallel, or they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified functions or operational instructions, or using a combination of dedicated hardware and computer instructions.

[0086] The units or modules described in the embodiments of this application can be implemented in software or hardware. The described units or modules can also be housed in a processor; for example, a processor can be described as including a first acquisition module, a second acquisition module, a third acquisition module, and an activation module. The names of these units or modules do not necessarily limit the specific unit or module itself. For example, the first acquisition module can also be described as "acquiring account opening application information for a business account, wherein the account opening application information includes enterprise information provided by the enterprise for opening a business account."

[0087] In another aspect, this application also provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiments, or may exist independently and not assembled into the electronic device. The aforementioned computer-readable storage medium stores one or more programs that, when used by one or more processors, execute the enterprise account management method described in this application.

[0088] The above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of disclosure in this application is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the foregoing disclosed concept. For example, technical solutions formed by substituting the above features with (but not limited to) technical features with similar functions disclosed in this application.

Claims

1. A method for managing enterprise accounts, characterized in that, include: Obtain the account opening application information of the enterprise account, which includes the enterprise information provided by the enterprise for opening a business account; When the account opening application information is verified, the associated account of the enterprise in the third-party financial platform is obtained; Based on the associated account, obtain the account information of the associated account from the third-party financial platform; The enterprise account is activated based on the account information of the associated account.

2. The method for managing enterprise accounts according to claim 1, characterized in that, The step of obtaining account information of the associated account from the third-party financial platform based on the associated account includes: Based on the verification information and the associated account, an account information synchronization task is generated. In response to the account information synchronization task, an account information retrieval request is sent to the third-party financial platform, the account information retrieval request including the account identifier of the associated account; Receive account information of the associated account returned by the third-party financial platform.

3. The method for managing enterprise accounts according to claim 1, characterized in that, The process of activating the enterprise account based on the account information of the associated account includes: Based on the account information of the associated account, an account opening task is generated; The account opening task is executed, and an account opening associated task is created upon completion of the account opening task; the account opening associated task includes multiple independently executed account opening associated sub-tasks. The opening of the enterprise account is completed when multiple account opening-related sub-tasks are completed.

4. The method for managing enterprise accounts according to claim 3, characterized in that, The execution of the account opening task includes: Pre-verification of the account information of the associated accounts; When the account information of the associated account passes the pre-verification, the enterprise account is created; The enterprise account is bound to the associated account, and the account information of the associated account is synchronized to the enterprise account.

5. The method for managing enterprise accounts according to claim 4, characterized in that, The pre-verification includes not intercepting verification items and intercepting verification items, and the method further includes: If the account information of the associated account does not meet the non-interception verification items, an alarm message is sent, and the non-interception verification items are confirmed to have passed the verification. If the account information of the associated account does not meet the interception verification items, it is confirmed that the interception verification items have failed the verification.

6. The method for managing enterprise accounts according to claim 1, characterized in that, Also includes: Account information of multiple associated accounts is obtained from the third-party financial platform at a preset frequency; Based on the account information of the multiple associated accounts, update the multiple enterprise accounts associated with the associated accounts.

7. The method for managing enterprise accounts according to claim 1, characterized in that, The process of obtaining the enterprise account opening application information includes: In response to an account opening application exit instruction, the acquired account opening application information is stored; When the account opening application instruction is obtained again, it is pre-filled based on the account opening application information that has already been obtained.

8. A management device for enterprise accounts, characterized in that, include: The first acquisition module is used to acquire account opening application information for enterprise accounts, including enterprise information provided by the enterprise for opening a business account; The second acquisition module is used to acquire the associated account of the enterprise in the third-party financial platform when the account opening application information is verified. The third acquisition module is used to acquire account information of the associated account from the third-party financial platform based on the associated account; The activation module is used to activate the enterprise account based on the account information of the associated account.

9. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the enterprise account management method as described in any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by the processor, the program implements the enterprise account management method as described in any one of claims 1-7.

Images