CN112446780A

CN112446780A - Account management method and device, computer equipment and storage medium

Info

Publication number: CN112446780A
Application number: CN202011348502.5A
Authority: CN
Inventors: 姚红星; 何造宇
Original assignee: Ping An Puhui Enterprise Management Co Ltd
Current assignee: Ping An Puhui Enterprise Management Co Ltd
Priority date: 2020-11-26
Filing date: 2020-11-26
Publication date: 2021-03-05

Abstract

The present invention relates to the field of data processing technologies, and in particular, to an account management method, an account management apparatus, an account management device, and a storage medium. The account management method comprises the steps of obtaining sub-account opening requests which are triggered by a plurality of platforms and carry customer identifications; wherein the customer identification is indicative of a first account; responding to the account opening request of the sub-account, and creating a second account bound with the first account; responding to the fund account opening request, and creating a third account bound with the second account; the third account is used for managing the product credit line of each credit product; the third account comprises a plurality of funding accounts; and distributing the product credit line to each fund account according to a preset line proportion, so that each fund account corresponds to an account line. The invention also relates to the blockchain technology, wherein the first account, the second account and the third account are stored in the blockchain. The account management method can uniformly manage the multi-platform account system, and effectively improves the development efficiency and the expandability of account system management.

Description

Account management method and device, computer equipment and storage medium

Technical Field

The present invention relates to the field of data processing technologies, and in particular, to an account management method and apparatus, a computer device, and a storage medium.

Background

With the rapid development of the information age, the forms and business models of credit products in the financial field are also continuously expanded. At present, when a new credit product or a new business mode is online, a set of code programs needs to be redeveloped to realize the creation, maintenance and the like of an account, and the unified management of an account system cannot be realized. In addition, the current credit system is independent of other systems (such as a customer behavior information analysis system), so that account information (such as purchasing condition and repayment condition of loan products) of customers cannot be shared.

Disclosure of Invention

The embodiment of the invention provides an account management method, an account management device, computer equipment and a storage medium, and aims to solve the problem that unified management of a multi-platform account system cannot be realized in the prior art.

An account management method, comprising:

acquiring sub-account opening requests which are triggered by a plurality of platforms and carry customer identifications; wherein the customer identification is indicative of a first account;

responding to a sub-account opening request, and creating a second account bound with the first account; wherein the second account is a credit account for managing credit products; each credit product corresponds to a product credit line;

responding to a fund account opening request, and creating a third account bound with the second account; wherein the third account is used for managing the product credit line of each credit product; the third account comprises a plurality of funding accounts;

and distributing the product credit line to each fund account according to a preset line proportion, so that each fund account corresponds to an account line.

An account management apparatus comprising:

the sub-account opening request acquisition module is used for acquiring sub-account opening requests which are triggered by a plurality of platforms and carry customer identifications; wherein the customer identification is indicative of a first account;

the second account creating module is used for responding to a sub-account opening request and creating a second account bound with the first account; wherein the second account is a credit account for managing credit products; each credit product corresponds to a product credit line;

the third account creating module is used for responding to a fund account opening request and creating a third account bound with the second account; wherein the third account is used for managing the product credit line of each credit product; the third account comprises a plurality of funding accounts;

and the fund account amount distribution module is used for distributing the product credit amount to each fund account according to a preset amount proportion so that each fund account corresponds to an account amount.

A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the above account management method when executing the computer program.

A computer storage medium storing a computer program which, when executed by a processor, implements the steps of the above-described account management method.

In the account management method, the account management device, the computer equipment and the storage medium, a sub-account opening request which is triggered by a plurality of platforms and carries a customer identifier is obtained, a second account bound with the first account is created in response to the sub-account opening request, and then a third account bound with the second account is created in response to a fund account opening request; and finally, distributing the product credit line to each capital account according to a preset line proportion, enabling each capital account to correspond to an account line, and uniformly managing the accounts of a plurality of credit platforms (or service ends) of the customer through the three-layer account system, so that the credit platforms of different service types can share the account system, thereby realizing the purpose of expanding on the basis of the established account system without redeveloping a set of corresponding account programs when a new service module is online, and effectively improving the development efficiency and the expandability of account system management.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive labor.

FIG. 1 is a diagram of an application environment of an account management method according to an embodiment of the present invention;

FIG. 2 is a flow chart of a method of account management in one embodiment of the present invention;

FIG. 3 is a flow chart of a method of account management in one embodiment of the present invention;

FIG. 4 is a flow chart of a method of account management in one embodiment of the present invention;

FIG. 5 is a flow chart of a method of account management in one embodiment of the present invention;

FIG. 6 is a flow chart of a method of account management in one embodiment of the present invention;

FIG. 7 is a detailed flowchart of step S202 in FIG. 2;

FIG. 8 is a flow chart of a method of account management in one embodiment of the present invention;

FIG. 9 is a schematic diagram of an account management device according to an embodiment of the invention;

FIG. 10 is a schematic diagram of a computer device according to an embodiment of the invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The account management method can be applied to the application environment as shown in fig. 1, wherein the computer device communicates with the server through the network. The computer device may be, but is not limited to, various personal computers, laptops, smartphones, tablets, and portable wearable devices. The server may be implemented as a stand-alone server.

In an embodiment, as shown in fig. 2, an account management method is provided, which is described by taking the server in fig. 1 as an example, and includes the following steps:

s201: acquiring sub-account opening requests which are triggered by a plurality of platforms and carry customer identifications; wherein the customer identification is indicative of the first account.

The method can be applied to credit management systems of different financial institutions, so that the accounts of a plurality of credit platforms (or service terminals) can be uniformly managed by establishing a standard account system, a set of corresponding account programs do not need to be re-developed when a new service module is online, the method can be expanded on the basis of the established account system in the embodiment, and the development efficiency and the account system management expandability are effectively improved.

It is understood that, in this embodiment, a corresponding account system is created for each customer, and is used for managing accounts of different platforms. The account system comprises a first layer of account system, a second layer of account system and a third layer of account system. The first layer account system is used for managing the corresponding relation between the first account and the customer identification. The first account is a main account used for managing a plurality of platform accounts in an account system, and the main account can be bound with the accounts of a plurality of platforms so as to be managed in a unified mode. The customer identification is an identification in the financial institution that uniquely identifies the customer. The second tier account system is used in the account hierarchy to manage the correspondence between the second account and the credit product. The second account is a credit account for a plurality of credit products applied under the customer account, each credit product being uniquely identifiable by a product endorsement. The third layer account system is used for managing the corresponding relation between the third account and the product credit line.

It is emphasized that the account hierarchy may also be stored in a node of a blockchain in order to further ensure privacy and security of the account hierarchy.

In this embodiment, an account opening request triggered by a plurality of platforms can be responded in real time through an account opening interface corresponding to the exposed account management system. The account opening request comprises a sub-account opening request and a fund account opening request. The sub-account opening request is a request for triggering the server to create a second account for the customer. The fund account opening request is an opening request for triggering the server to create a third account of the client.

Specifically, the client can trigger a sub-account opening request by clicking a control for applying a certain credit product in promotion platforms of different product types, and the server calls an opening interface to execute an opening operation after acquiring the sub-account opening request.

S202: responding to the account opening request of the sub-account, and creating a second account bound with the first account; wherein the second account is a credit account for managing credit products; each credit product corresponds to a product credit line.

It can be understood that, under the condition that the customer is not logged in, the customer can send a sub-account opening request in different product officer platforms by clicking a credit product (such as a car fueling card) to be applied or other triggering modes, the server will firstly inquire whether a first account corresponding to the customer identification exists in the database, and if so, a second account bound with the first account is directly created; and if the client identifier does not exist, creating a first account for the user according to the client identifier, and then creating a second account bound with the first account.

Specifically, different products correspond to different product credit lines, and when the server responds to the account opening request of the sub-account, the server synchronizes product information in the platform, such as the product credit line, and generates a product credit signal of the product, so as to establish a corresponding relationship between the second account and the credit product. The product command signal may be generated according to a certain rule, which is not limited herein. The credit product corresponding to the second account may include a co-platform credit product.

S203: responding to the fund account opening request, and creating a third account bound with the second account; the third account is used for managing the product credit line of each credit product; the third account includes a plurality of funding accounts.

Specifically, after the second account is created, the customer can use the product within the range of the credit line of the product according to actual needs, and when the customer wants to use the product by cash withdrawal or online consumption, a fund account opening request is triggered. The third account in this embodiment may include different funding accounts, such as a cash account, a consumption account, and a mortgage account. The user can open an account by selecting one or more of the users according to actual needs, and the system can open an account in a default mode, which is not limited herein.

S204: and distributing the product credit line to each fund account according to a preset line proportion, so that each fund account corresponds to an account line.

Specifically, when the user selects to open two or more fund accounts, the server allocates the product credit line to each fund account according to a line proportion for management. Illustratively, if the product credit limit is 5000, the customer has opened a consumption account and a cash account, so that the credit limit is set according to a limit ratio, such as 2: 3, the amount of 2000 can be allocated to the consumption account for management, the amount of 3000 can be allocated to the cash account for management, and the remaining account amount of the corresponding account can be updated for each use of the client. The proportion of the amount can be preset or determined by evaluating the qualification of the client, and is not limited herein.

In this embodiment, the accounts of multiple credit platforms (or servers) of the customer are managed in a unified manner through the three-tier account system, so that when a new service module is online, a set of corresponding account program does not need to be re-developed, and the expansion can be performed on the basis of the account system established in this embodiment, thereby effectively improving the development efficiency and the expandability of account system management.

In an embodiment, as shown in fig. 3, before step 203, the account management method further includes the following steps:

s301: financial account information for a credit product is obtained.

The financial account information of each credit product can be displayed to the customer through the front end when the customer selects the credit product required to be used, so that the customer can select the financial account information. The financial account information includes a plurality of openable financial accounts. The openable fund account includes but is not limited to cash account, consumption account, mortgage account and the like.

Specifically, when the user needs to use a certain credit product applied by the user, the server pops up a display interface to the front end, which is used for prompting a plurality of fund accounts which can be opened by the customer, and the customer can select at least one needed fund account from the openable fund accounts displayed on the interface to open an account, for example, all fund names can be listed in a table for the user to check.

S302: acquiring an account opening demand table according to the financial account information; the account opening demand table comprises a plurality of fund accounts which are selected by the user and need to be opened.

The server can form a data table for recording the account opening requirements of the user after acquiring a plurality of fund accounts which are selected by the user and need to be opened, and then stores the financial account requirement table in the database.

In step S203, the method specifically includes:

s303: and creating a third account bound with the second account according to the account opening requirement table.

And the server simultaneously creates all fund accounts selected by the user according to the account opening requirement table. For example, the customer checks a cash account and a consumption account according to the front-end display interface, and the server opens two fund accounts, namely the cash account and the consumption account, after acquiring the financial demand form of the user.

It can be understood that if the third account is directly created when the customer creates the second account, and the customer does not use the product, the database may store invalid account data for a long time.

In an embodiment, as shown in fig. 4, after step S204, the account management method further includes the following steps:

s401: and receiving a login request which is triggered by the first platform and carries a client identifier and an account password.

S402: and judging whether a first account corresponding to the customer identifier exists in the database or not according to the customer identifier, and if so, verifying the account password.

Wherein the first platform refers to a promotion platform for credit products. Specifically, the client may trigger a login request in the first platform, and at this time, the server may verify whether the client identifier carried in the login request has a corresponding first account. If the account password exists, the fact that the customer creates the first account system in the credit system and belongs to the system customer is proved, and whether the account password is accurate or not can be further verified.

It can be understood that, since the account system of the customer is used for managing the accounts of the multiple platforms, and the first-layer account system of the account system is used for managing the corresponding relationship between the customer information and the first account, whether the customer has created the corresponding account system in the system can be verified by verifying whether the first account exists in the database, and if the corresponding account system exists, the database stores the account information such as the account password corresponding to the customer identifier.

Further, if the account is not found, the fact that the client does not create the first account system in the credit system is proved, the client belongs to a non-system client, the login page displayed at the front end is jumped to the registration page, the client can enter the registration information through the registration page to create the first account of the client, and after the creation is completed, the login credentials can be directly generated.

S403: and when the verification is passed, generating a login certificate corresponding to the client identifier.

The login credentials are used for proving that the client has created a corresponding first-layer account system and successfully logs in. The login authentication may be a long string encrypted by MD 5. Specifically, if the account password corresponding to the client identifier is consistent with the account password corresponding to the client identifier pre-stored in the database, the authentication is passed, and a login credential corresponding to the client identifier is generated and stored in the database.

S404: and receiving a login request which is triggered by the second platform and carries a client identifier.

S405: and logging in the second platform according to the login credentials.

Wherein the second platform may refer to a credit platform other than the first platform. Specifically, when the server receives a login request triggered by the second platform, the server can directly judge the login state of the client according to the login credential corresponding to the client identifier in the query database, and then can automatically log in to the second platform directly according to the login information (namely the client identifier and the password) corresponding to the login credential.

It is to be understood that the triggering condition of the login request may be triggered by the customer clicking on the credit product to be applied in the second platform or clicking on a control of the login function, which is not limited herein.

Illustratively, a client triggers a login request at the platform A, and when the client is verified as a system client, the login is successful and a login certificate is generated; and then, the client triggers a login request at the platform B, at the moment, the server can directly inquire whether a login certificate corresponding to the client identifier is stored in the database, and if the login certificate exists, the client logs in the platform B directly according to the login certificate.

In this embodiment, a unified account system is created to manage multiple accounts of the client, so that the purposes of one-time login and multiple times of multiplexing can be achieved in different platforms, and the user does not need to repeatedly input an account password for verification.

In an embodiment, as shown in fig. 5, the first account corresponds to a first account information table, the second account corresponds to a second account information table, and the third account corresponds to a third account information table; after step S202, the account management method further includes the following steps:

s501: and integrating the first account information table, the second account information table and the third account information table to obtain the account information table.

S502: and encrypting the account information table, and sharing the account information table to a plurality of third-party systems through synchronous interfaces.

The first account information table includes, but is not limited to, a customer identifier, an account password, a creation date of the first account, an account status of the first account, and the like. The second account information table includes, but is not limited to, a customer identification, a product credit, a credit product name, a product credit line, a second account creation date, a product application date, and an account status of the second account. The third account information table includes, but is not limited to, a customer identification, a product authorization, a funding account, a credit corresponding to the funding account, a credit usage date, a third account creation date, and an account status of the third account. The third-party system includes but is not limited to a customer behavior analysis system, a big data system and the like.

Specifically, each account system corresponds to one data table for storing different account information. The data tables are associated through a set external key, the first account information table, the product information table and the third account information table are integrated to obtain the account information table, for example, according to a preset account information summarizing template, a plurality of preset fields such as customer identification, account creation date, credit product name, amount use date and the like are preset in the template, fields and field attribute values which are the same as the preset fields in the first account information table, the second account information table and the third account information table are mapped to the account information summarizing template through the preset fields to obtain the account information table, and the account information table is encrypted to ensure the information safety of customers. And finally, synchronizing to a plurality of third systems through a pre-established synchronous interface so as to realize data sharing among different systems. It should be noted that the preset field may be set uniformly, or may be set correspondingly for different third-party systems.

In addition, account information of different platforms of a client can be uniformly managed in the embodiment, so that a subsequent third-party system does not need to be in butt joint with synchronous data of a plurality of platforms when acquiring behavior information of a certain client, the data synchronization time is effectively prolonged, and the resource occupancy rate of the third-party system is reduced.

It should be emphasized that, in order to further ensure the privacy and security of the account information table, the account information table may also be stored in a node of a block chain

In an embodiment, as shown in fig. 6, in step S501, performing an integration process on the first account information table, the second account information table, and the third account information table to obtain the account information table specifically includes the following steps:

s601: acquiring information to be synchronized required by a third-party system; the information to be synchronized corresponds to a plurality of fields to be synchronized.

The third-party system comprises but is not limited to a customer behavior analysis system, a big data system and the like; the information to be synchronized required by different third-party systems is different, for example, the fields to be synchronized required by the customer behavior analysis system include the customer identification in the first account information table, the credit product name in the second account information table, the product application date, the fund account in the third account information table, the quota corresponding to the fund account, the quota use date and the like, so as to analyze the customer behavior, for example, analyze the customer preference, make product recommendation and the like. And the fields to be synchronized required in the big data system are all fields stored in the first account information table, the second account information table and the third account information table, so that different data predictions and the like can be realized through the customer data.

S602: and creating a corresponding account information table according to the fields to be synchronized.

Specifically, after acquiring the fields to be synchronized required by each third-party system, the server may create a corresponding account information table according to the fields to be synchronized, so as to facilitate subsequent mapping processing.

S603: and mapping the attribute values corresponding to the table fields which are the same as the fields to be synchronized in the first account information table, the second account information table and the third account information table to the account information tables.

Specifically, the server maps the attribute values corresponding to the table fields, which are the same as the fields to be synchronized, in the first account information table, the second account information table and the third account information table to the account information table to obtain the account information table.

In step S502, the account information table is encrypted and shared to a plurality of third party systems through a synchronous interface, which specifically includes the following steps:

s604: and encrypting the account information table, and sharing the account information table to a corresponding third-party system through a synchronous interface.

Specifically, in order to ensure the security of the customer information, the encrypted account information table is synchronized to the corresponding third-party system by encrypting the account information table, so that the pertinence and the flexibility are stronger.

In an embodiment, as shown in fig. 7, the step S202, that is, in response to the sub-account opening request, creating the second account bound to the first account specifically includes the following steps:

s701: and responding to the account opening request of the sub-account, and reading the account state of the first account.

S702: when the account status is valid, the credit information of the credit product is synchronized.

S703: and creating a second account bound with the first account according to the credit information.

The server reads the account state of the first account before creating the second account, and when the account state is in an effective state, the credit information of the synchronous credit product in the corresponding platform is passed through. The credit product credit granting information includes but is not limited to a platform channel (used for representing a sub-account opening request triggered by a customer from which platform), a media source (telephone or internet), credit investigation, credit increase, a fund party and the like, after the server synchronizes the credit granting information, a second account bound to a first account is created, and meanwhile, the second account corresponds to a second account information table, the credit granting information is stored through the information table, and the part of data is conveniently synchronized to other platforms subsequently.

In an embodiment, as shown in fig. 8, after step S203, the account management method further includes the following steps:

s801: receiving transaction information which is sent by a settlement system and carries a client identifier; wherein the transaction information includes credit products, usage lines, target funds accounts, and transaction results.

After the third party account is created, the client can use the corresponding amount within the product credit amount range. Specifically, the server receives the transaction information sent by the settlement system in real time, and if the customer uses a certain credit product (which is uniquely identified by a product authorization signal), the server receives the transaction information sent by the settlement system, wherein the transaction information comprises a use limit, a target fund account and a transaction result. The using amount is the amount used by the client in the transaction. The target funding account is the type of funding account used for the transaction. The transaction result includes a transaction success or a transaction failure.

S802: and when the transaction result is that the transaction is successful, updating the remaining credit line corresponding to the credit product in the second account corresponding to the customer identifier and the remaining account line corresponding to the target fund account according to the using line.

Specifically, when the transaction result is that the transaction is successful, the server may update the product credit line corresponding to the second account and the account line of the target fund account according to the usage line, for example, the credit line of a certain credit product of the second account corresponding to a certain customer a is 5000, the account line corresponding to the consumption account is 3000, and the transaction information of the transaction is the usage line: 1000. the target fund account: consumption account, credit product: 1. and (3) transaction results: if the credit account is successful, the server will update the remaining credit line of the credit product 1 in the second account of the client a to 4000 and the remaining account line of the target fund account, i.e. the consumption account, to 2000 according to the two parameters.

It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

In an embodiment, an account management apparatus is provided, and the account management apparatus corresponds to the account management methods in the embodiments one to one. As shown in fig. 9, the account management device includes a sub-account opening request acquisition module 10, a second account creation module 20, a third account creation module 30, and a fund account amount allocation module 40. The functional modules are explained in detail as follows:

a sub-account opening request obtaining module 10, configured to obtain sub-account opening requests that are triggered by multiple platforms and carry client identifiers; wherein the customer identification is indicative of a first account.

The second account creating module 20 is configured to create a second account bound to the first account in response to the sub-account opening request; wherein the second account is a credit account for managing credit products; each credit product corresponds to a product credit line.

A third account creation module 30, configured to create a third account bound to the second account in response to the fund account opening request; wherein the third account is used for managing the product credit line of each credit product; the third account includes a plurality of funding accounts.

The fund account amount distribution module 40 is configured to distribute the product credit amount to each of the fund accounts according to a preset amount ratio, so that each of the fund accounts corresponds to an account amount.

Specifically, the account management device further comprises a financial account information acquisition module and an account opening requirement table acquisition module

And the financial account information acquisition module is used for acquiring the financial account information of the credit product.

And the account opening demand table acquisition module is used for acquiring the account opening demand table according to the financial account information. The account opening demand table comprises a plurality of fund accounts which are selected by the user and need to be opened.

And the third account creating module is used for creating a third account bound with the second account according to the account opening demand table.

Specifically, the account management device further includes a first login request obtaining module, a verification module, a login credential generating module, a second login request obtaining module, and a login module.

And the first login request acquisition module is used for receiving a login request which is triggered by the first platform and carries a client identifier and an account password.

And the verification module is used for judging whether a first account corresponding to the customer identification exists in a database or not according to the customer identification, and if so, verifying the account password.

And the login credential generation module is used for generating a login credential corresponding to the client identifier when the verification is passed.

And the second login request acquisition module is used for receiving a login request which is triggered by the second platform and carries the client identifier.

And the login module is used for logging in the second platform according to the login credentials.

Specifically, the first account corresponds to a first account information table, the second account corresponds to a second account information table, and the third account corresponds to a third account information table; the account management method device also comprises an account information table acquisition module and a sharing module.

And the account information table acquisition module is used for integrating the first account information table, the second account information table and the third account information table to obtain an account information table.

And the sharing module is used for encrypting the account information table and sharing the account information table to a plurality of third-party systems through synchronous interfaces.

Specifically, the account information table acquisition module comprises an information unit to be synchronized, an account information table acquisition unit and a mapping unit.

The information to be synchronized unit is used for acquiring information to be synchronized required by a third-party system; the information to be synchronized corresponds to a plurality of fields to be synchronized.

And the account information table acquisition unit is used for creating a corresponding account information table according to the field to be synchronized.

And the mapping unit is used for mapping the attribute values corresponding to the table fields which are the same as the fields to be synchronized in the first account information table, the second account information table and the third account information table to the account information tables.

The sharing module specifically includes: and the sharing unit is used for encrypting the account information table and sharing the account information table to a corresponding third-party system through a synchronous interface.

Specifically, the second account creation module includes an account status reading module, an information synchronization unit, and a second account creation unit.

And the account state reading unit is used for responding to the account opening request of the sub-account and reading the account state of the first account.

And the information synchronization unit is used for synchronizing the credit information of the credit product when the account state is an effective state.

And the second account creating unit is used for creating a second account bound with the first account according to the credit information.

Specifically, the account management device further comprises a transaction information receiving module and a limit updating module.

And the transaction information receiving module is used for receiving the transaction information which is sent by the settlement system and carries the client identification. Wherein the transaction information includes a credit product, a usage amount, a target funds account, and a transaction result.

And the limit updating module is used for updating the remaining credit limit corresponding to the credit product in the second account corresponding to the customer identification and the remaining account limit corresponding to the target fund account according to the using limit when the transaction result is that the transaction is successful.

For the specific definition of the account management device, reference may be made to the above definition of the account management method, which is not described herein again. The modules in the account management device can be wholly or partially implemented by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 10. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a computer storage medium and an internal memory. The computer storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the computer storage media. The database of the computer device is used to store data, such as an account information table, generated or obtained during execution of the account management method. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement an account management method.

In one embodiment, a computer device is provided, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the account management method in the above embodiments when executing the computer program, such as the steps S201-S204 shown in fig. 2 or the steps shown in fig. 3 to 8. Alternatively, the processor implements the functions of each module/unit in the embodiment of the account management apparatus when executing the computer program, for example, the functions of each module/unit shown in fig. 9, and are not described here again to avoid repetition.

In an embodiment, a computer storage medium is provided, where a computer program is stored on the computer storage medium, and when executed by a processor, the computer program implements the steps of the account management method in the foregoing embodiments, such as steps S201 to S204 shown in fig. 2 or steps shown in fig. 3 to fig. 8, which are not repeated herein for avoiding repetition. Alternatively, the computer program, when executed by the processor, implements the functions of each module/unit in the embodiment of the account management apparatus, for example, the functions of each module/unit shown in fig. 9, and are not described herein again to avoid repetition.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware related to instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

The block chain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules, so as to perform all or part of the functions described above.

The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present invention, and are intended to be included within the scope of the present invention.

Claims

1. An account management method, comprising:

responding to the account opening request of the sub-account, and creating a second account bound with the first account; wherein the second account is a credit account for managing credit products; each credit product corresponds to a product credit line;

2. The account management method of claim 1, wherein prior to the creating of the third account bound to the second account in response to the funding account opening request, the account management method further comprises:

acquiring financial account information of the credit product;

acquiring an account opening demand table according to the financial account information; the account opening demand table comprises a plurality of fund accounts which are selected by a user and need to be opened;

the creating a third account bound with the second account in response to the fund account opening request comprises:

and creating a third account bound with the second account according to the account opening requirement table.

3. The account management method of claim 1, wherein after creating a third account bound to the second account in response to the funding account opening request, the account management method further comprises:

receiving a login request which is triggered by a first platform and carries a client identifier and an account password;

judging whether a first account corresponding to the customer identification exists in a database or not according to the customer identification, and if so, verifying the account password;

when the verification is passed, generating a login certificate corresponding to the client identifier;

receiving a login request which is triggered by a second platform and carries the client identifier;

and logging in the second platform according to the login credentials.

4. The account management method of claim 1, wherein the first account corresponds to a first account information table, the second account corresponds to a second account information table, and the third account corresponds to a third account information table;

after creating a second account bound to the first account in response to the sub-account opening request, the account management method further includes:

integrating the first account information table, the second account information table and the third account information table to obtain an account information table;

and encrypting the account information table, and sharing the account information table to a plurality of third-party systems through synchronous interfaces.

5. The account management method according to claim 4, wherein the integrating the first account information table, the second account information table, and the third account information table to obtain the account information table comprises:

acquiring information to be synchronized required by a third-party system; the information to be synchronized corresponds to a plurality of fields to be synchronized;

creating a corresponding account information table according to the fields to be synchronized;

mapping attribute values corresponding to table fields, which are the same as the fields to be synchronized, in the first account information table, the second account information table and the third account information table to the account information tables;

the encrypting the account information table and sharing the account information table to a plurality of third-party systems through synchronous interfaces comprises the following steps:

and encrypting the account information table, and sharing the account information table to a corresponding third-party system through a synchronous interface.

6. The account management method of claim 1, wherein creating a second account bound to the first account in response to the sub-account opening request comprises:

responding to the account opening request of the sub-account, and reading the account state of the first account;

when the account state is an effective state, synchronizing the credit information of the credit product;

and creating a second account bound with the first account according to the credit information.

7. The account management method of claim 1, wherein after creating a third account bound to the second account in response to the funding account opening request, the account management method further comprises:

receiving transaction information which is sent by a settlement system and carries a client identifier; wherein the transaction information includes credit products, usage lines, target fund accounts, and transaction results;

and when the transaction result is that the transaction is successful, updating the remaining credit line corresponding to the credit product and the remaining account line corresponding to the target fund account in the second account corresponding to the customer identification according to the using line.

8. An account management apparatus, comprising:

9. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the steps of the account management method according to any of claims 1 to 7 are implemented when the computer program is executed by the processor.

10. A computer storage medium storing a computer program, wherein the computer program when executed by a processor implements the steps of the account management method according to any of claims 1 to 7.