CN113487303A - Account management method and device, computer equipment and storage medium - Google Patents
Account management method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN113487303A CN113487303A CN202110744584.3A CN202110744584A CN113487303A CN 113487303 A CN113487303 A CN 113487303A CN 202110744584 A CN202110744584 A CN 202110744584A CN 113487303 A CN113487303 A CN 113487303A
- Authority
- CN
- China
- Prior art keywords
- account
- platform
- request
- target
- transfer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/102—Bill distribution or payments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/22—Payment schemes or models
- G06Q20/227—Payment schemes or models characterised in that multiple accounts are available, e.g. to the payer
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/405—Establishing or using transaction specific rules
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
Abstract
The application relates to an account method, an account device, computer equipment and a storage medium. The method is applied to a first platform, the accounts are attributed to the first platform, the accounts comprise a first account and a second account, the first account and the second account are different in attributes, and the first account and the second account are associated; the method comprises the following steps: receiving a first request; according to the first request, acquiring a target account of the first request; if the target account of the first request is the first account of the first user, verifying whether the first request is legal, and if the first request is legal, operating the first account and the second account of the first user according to the first request; wherein the first request is generated by a second platform and forwarded by the second platform to the first platform, or the first request is generated by a second account of the first platform. The embodiment of the application can improve the safety and provide convenience for users.
Description
Technical Field
The present application relates to the field of data processing, and in particular, to an account management method and apparatus, a computer device, and a storage medium.
Background
An account is a representation of the digital age, i.e. the number that each person represents in a particular project, etc. Accounts can sometimes consist of chinese or english, even some symbols.
With the development of the internet, the demands of users become more complex, such as the need for browsing web pages, the need for processing funds, or the need for managing data, which results in that each person has only one account in a specific project and cannot meet the various demands of the users. But if one user has a plurality of accounts, the user needs to manage the plurality of accounts, and the user is not changed. In addition, if one user owns a plurality of accounts, the difficulty of managing the accounts by the administrator is increased.
Therefore, one main body has a single account or one main body has a plurality of accounts, which have advantages and disadvantages, are difficult to meet the requirements of users, and increase the management difficulty.
Disclosure of Invention
To solve the technical problem or at least partially solve the technical problem, the application provides an account management method, an account management apparatus, a computer device and a storage medium.
In a first aspect, the present application provides an account management method, which is applied to a first platform, wherein the account is attributed to the first platform, the account includes a first account and a second account, attributes of the first account and the second account are different, and the first account and the second account are associated;
the method comprises the following steps:
receiving a first request;
according to the first request, acquiring a target account of the first request;
if the target account of the first request is the first account of the first user, verifying whether the first request is legal, and if the first request is legal, operating the first account and the second account of the first user according to the first request;
wherein the first request is generated by a second platform and forwarded by the second platform to the first platform, or
The first request is generated by a second account of the first platform.
In the embodiment of the application, the first request comprises a user identification and a request category,
the obtaining of the target account of the first request according to the first request includes:
acquiring a first user from the users of the first platform according to the user identification;
acquiring account types according to the request types, wherein the account types comprise a first account and a second account;
the first account or the second account of the first user corresponding to the account type is used as a target account.
In this embodiment of the present application, the operating the first account and the second account of the first user includes:
acquiring a target platform in the first request;
obtaining a third account of the first user on the target platform, wherein the third account comprises virtual assets;
acquiring the operation in the first request;
and operating the virtual assets of the third account on the target platform according to the operation in the first request.
In this embodiment of the present application, the operating the virtual asset of the third account on the target platform includes:
enabling the target platform to judge whether the operation on the virtual assets of the third account is legal or not;
if the operation is legal, transferring the virtual assets of the third account of the target platform to a fourth account of the target platform;
and receiving the operation result of the transfer success or the transfer failure sent by the target platform.
In this embodiment of the present application, the operating the virtual asset of the third account on the target platform includes:
causing the target platform to send a first transfer request to a third platform, wherein the first transfer request is to transfer a virtual asset of a third account of the target platform into a fifth account of the third platform;
enabling the third platform to check whether the first transfer request is legal or not, and enabling the third platform to execute the first transfer request if the first transfer request is legal;
enabling the target platform to receive the operation result of the transfer success or the transfer failure sent by the third platform;
and receiving the operation result of the transfer success or the transfer failure forwarded by the target platform.
In this embodiment of the present application, the operating the virtual asset of the third account on the target platform includes:
causing the target platform to send a second transfer request to a fourth platform, the second transfer request being a transfer of the virtual asset from a sixth account of the fourth platform into a third account of the target platform;
enabling the fourth platform to check whether the second transfer request is legal, and enabling the fourth platform to execute the second transfer request if the second transfer request is legal;
enabling the target platform to receive the operation result of the transfer success or the transfer failure sent by the fourth platform;
and receiving the operation result of the transfer success or the transfer failure forwarded by the target platform.
In this embodiment of the application, if the target account of the first request is the second account of the first user, the second account of the first user is operated according to the first request.
In a second aspect, an account management apparatus is provided, the apparatus being applied to a first platform, the account being attributed to the first platform, the account including a first account and a second account, the first account and the second account having different attributes, the first account and the second account being associated;
the device comprises:
a receiving unit configured to receive a first request;
the account acquisition unit is used for acquiring a target account of the first request according to the first request;
the processing unit is used for verifying whether the first request is legal or not if the target account of the first request is the first account of the first user, and operating the first account and the second account of the first user according to the first request if the first request is legal;
wherein the first request is generated by a second platform and forwarded by the second platform to the first platform, or
The first request is generated by a second account of the first platform.
In a third aspect, 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 any of the above methods when executing the computer program.
In a fourth aspect, a computer-readable storage medium is provided, having stored thereon a computer program which, when being executed by a processor, carries out the steps of the method of any of the above.
The embodiment of the application provides an account management method, which is applied to a first platform, wherein the accounts belong to the first platform, the accounts comprise a first account and a second account, the attributes of the first account and the second account are different, and the first account is associated with the second account; the method comprises the following steps: receiving a first request; according to the first request, acquiring a target account of the first request; if the target account of the first request is the first account of the first user, verifying whether the first request is legal, and if the first request is legal, operating the first account and the second account of the first user according to the first request; wherein the first request is generated by a second platform and forwarded by the second platform to the first platform, or the first request is generated by a second account of the first platform. In the embodiment of the application, a first account and a second account are set, and the attributes of the first account and the second account are different, so that the specific content of management is also different. The first account and the second account are associated, and management of the plurality of accounts by a user is facilitated; the first account and the second account have different attributes, different data are managed respectively, certain mutual isolation exists between the data, and the safety of the system can be improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
FIG. 1 is a diagram illustrating an application environment of an account management method according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating an account management method according to an embodiment of the invention;
FIG. 3 is a diagram illustrating an application scenario of an account management method according to an embodiment of the present invention;
FIG. 4 is a block diagram illustrating an account management apparatus according to an embodiment of the present invention;
fig. 5 is a diagram showing an internal structure of a computer device in the embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. 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 application.
FIG. 1 is a diagram of an application environment of an account method in one embodiment. Referring to fig. 1, the account management method is applied to an account management system. The account management system includes a terminal 110 and a server 120. The terminal 110 and the server 120 are connected through a network. The terminal 110 may specifically be a desktop terminal or a mobile terminal, and the mobile terminal may specifically be at least one of a mobile phone, a tablet computer, a notebook computer, and the like. The server 120 may be implemented as a stand-alone server or a server cluster composed of a plurality of servers.
As shown in FIG. 2, in one embodiment, an account management method is provided. The embodiment is mainly illustrated by applying the method to the terminal 110 (or the server 120) in fig. 1. Referring to fig. 2, the account management method is applied to a first platform, the accounts are attributed to the first platform, the accounts comprise a first account and a second account, the attributes of the first account and the second account are different, and the first account and the second account are associated;
the account management method comprises the following steps:
step 230, if the target account of the first request is the first account of the first user, verifying whether the first request is legal, and if the first request is legal, operating the first account and the second account of the first user according to the first request;
wherein the first request is generated by a second platform and forwarded by the second platform to the first platform, or
The first request is generated by a second account of the first platform.
In the embodiment of the application, in the first platform, the same user may have two accounts, which are a first account and a second account, respectively, and the first account and the second account of the same user are associated, and the attributes of the first account and the second account are different.
In the embodiment of the application, the attributes of the accounts may be a management account and a virtual asset account, the first account may be a virtual asset account, and the second account may be a management account.
The virtual asset account may be used to process transactions related to the virtual asset, such as transfers of the virtual asset, and the like. The transfer of the virtual asset may be from the virtual asset account of the current user to the virtual asset account of the other user, or may be from the virtual asset account of the other user to the virtual asset account of the current user, or may be a mutual transfer between the virtual asset of the current user on the current platform and the virtual asset of the current user on the other platform.
In this embodiment, the management account may be management of user profiles, generation of a user request, and the like, and in this case, the first request may be generated by a second account of the first platform.
In an embodiment of the application, the first request is generated by a second platform and forwarded to the first platform by the second platform, or
The first request is generated by a second account of the first platform.
That is, in the present application, the first request may be generated by the present platform, or may be generated by another platform, that is, in the embodiment of the present application, the user may perform account management on the present platform, or may perform account management on another platform.
In this embodiment, the first request generated by the second account of the first platform may be management of the virtual asset, or may be all management except non-virtual asset management such as management of user profile and management of user account.
In the application, the virtual asset account corresponds to the management account, has different attributes, and has certain independence. In the present application, having a certain independence means that the two managed objects are different from each other and have a certain mutual isolation, and specifically, the login authority, the security verification, and the like of the two managed objects may be different from each other.
In the embodiment of the application, a first account and a second account are set, and the attributes of the first account and the second account are different, so that the specific content of management is also different. The first account and the second account are associated, and management of the plurality of accounts by a user is facilitated; the first account and the second account have different attributes, different data are managed respectively, certain mutual isolation exists between the data, and the safety of the system can be improved.
According to the method of the embodiment of the application, after the first request is received, the target account of the first request is obtained, and the target account of the first request can be the first account and/or the second account. The first account is a virtual asset account, so if the target account is the first account, it needs to be verified whether the first request is legitimate.
In the embodiment of the application, the first request comprises a user identification and a request category,
the obtaining of the target account of the first request according to the first request includes:
acquiring a first user from the users of the first platform according to the user identification;
acquiring account types according to the request types, wherein the account types comprise a first account and a second account;
the first account or the second account of the first user corresponding to the account type is used as a target account.
In the embodiment of the present application, the user identifier may be a user ID, or may be any other identifier that can distinguish different users. According to the user identification, a unique first user can be obtained.
As described above, the request categories may include management of user profiles, management of user accounts, or may be management of virtual assets. Thus, the target account is the first account if it is the management of the virtual asset, and the second account if it is all management other than the management of the non-virtual asset, such as the management of the user profile, the management of the user account, etc.
In this embodiment of the application, the target platform is included in the first request,
the verifying whether the first request is legal includes:
judging whether the second platform is a legal source platform of the first platform;
if the second platform is a legal source platform, judging whether the first user is a legal user of the first platform;
if the first user is a legal user of the first platform, judging whether the target platform is a legal target platform of the first platform;
and if the target platform is a legal target platform, confirming that the first request is legal.
Since the first request of the present application may be from the second platform, in order to improve security, it is necessary to verify whether the first request is legitimate.
In fact, if the first request is generated by the first platform, it is also required to verify whether the first request is legal, but it is not required to verify whether the second platform is a legal source platform, but it is still required to verify whether the first user is a legal user of the first platform, and verify whether the target platform is a legal target platform of the first platform.
In the embodiment of the present application, the valid source platform, the valid user, and the valid target platform may be verified by using a verification method in the prior art or a combination of multiple verification methods in the prior art, which is not described herein again.
In this embodiment of the present application, in step 230, the operating the first account and the second account of the first user includes:
acquiring a target platform in the first request;
obtaining a third account of the first user on the target platform, wherein the third account comprises virtual assets;
acquiring the operation in the first request;
and operating the virtual assets of the third account on the target platform according to the operation in the first request.
In this embodiment of the present application, the operating the virtual asset of the third account on the target platform includes:
enabling the target platform to judge whether the operation on the virtual assets of the third account is legal or not;
if the operation is legal, transferring the virtual assets of the third account of the target platform to a fourth account of the target platform;
and receiving the operation result of the transfer success or the transfer failure sent by the target platform.
In the embodiment of the application, the first account and the third account are both accounts of the first user, so that in the embodiment of the application, the transfer of virtual assets between different accounts of the same user in the same platform can be realized.
In this embodiment of the present application, the target platform may be the first platform, or may be another platform, and therefore in this embodiment of the present application, the transfer of the virtual asset between the same account of the same platform may be implemented, but may be the transfer of the virtual asset of the first platform, or may also be the transfer of the virtual asset of another platform.
In this embodiment of the present application, the determining, by the target platform, whether the operation on the virtual asset of the third account is legal includes:
enabling the target platform to judge whether the number of the virtual assets needing to be transferred is less than or equal to the current number of the virtual assets of the third account;
and if the quantity of the virtual assets to be transferred is less than or equal to the current quantity of the virtual assets of the third account, confirming that the operation on the virtual assets of the third account is legal.
In this embodiment of the present application, the operating the virtual asset of the third account on the target platform includes:
causing the target platform to send a first transfer request to a third platform, wherein the first transfer request is to transfer a virtual asset of a third account of the target platform into a fifth account of the third platform;
enabling the third platform to check whether the first transfer request is legal or not, and enabling the third platform to execute the first transfer request if the first transfer request is legal;
enabling the target platform to receive the operation result of the transfer success or the transfer failure sent by the third platform;
and receiving the operation result of the transfer success or the transfer failure forwarded by the target platform.
In the embodiment of the application, the first account is an account of a first user, the fifth account may be an account of the first user, and the fifth account may also be an account of another user; the target platform may be the first platform, or may be another platform; therefore, in the embodiment of the application, the virtual assets of the same user can be transferred among different platforms, and the virtual assets of different users can be transferred among different platforms. The different platforms may be the first platform and the other platforms, or may be the other two platforms.
In this embodiment of the present application, the operating the virtual asset of the third account on the target platform includes:
causing the target platform to send a second transfer request to a fourth platform, the second transfer request being a transfer of the virtual asset from a sixth account of the fourth platform into a third account of the target platform;
enabling the fourth platform to check whether the second transfer request is legal, and enabling the fourth platform to execute the second transfer request if the second transfer request is legal;
enabling the target platform to receive the operation result of the transfer success or the transfer failure sent by the fourth platform;
and receiving the operation result of the transfer success or the transfer failure forwarded by the target platform.
In the embodiment of the application, the virtual assets of the first user can be transferred out, or the virtual assets can be transferred into the first user.
In this embodiment of the application, if the first request is generated by the second platform, after receiving the operation result of the transfer success or the transfer failure forwarded by the target platform, the first platform may forward the operation result of the transfer success or the transfer failure to the second platform. If the first request is generated by a second account of the first platform, the operation result of transfer success or transfer failure can be forwarded to the second account, so that the second account is updated correspondingly.
In this embodiment of the application, if the target account of the first request is the second account of the first user, the second account of the first user is operated according to the first request.
As described above, the first request may be for management of the virtual asset, or may be for all but management of the non-virtual asset. The target account is the second account for all administration other than the administration of the non-virtual asset.
Specifically, the first request further comprises: the modification to the account is carried out by,
the operating the second account of the first user according to the first request includes:
if the first request is modification, then:
modifying a second account of the first user in accordance with the first request,
and updating the corresponding relation between the first account of the first user and the second account of the first user.
In the embodiment of the application, a first account and a second account are set, and the attributes of the first account and the second account are different, so that the specific content of management is also different. The first account and the second account are associated, and management of the plurality of accounts by a user is facilitated; the first account and the second account have different attributes, different data are managed respectively, certain mutual isolation exists between the data, and the safety of the system can be improved. In the embodiment of the application, the first account and the second account have different attributes, and the specific management contents are different, but the management of the virtual assets and the like of the same user on the same platform, the management of the virtual assets and the like of the same user on different platforms, the management of the virtual assets and the like of different users on different platforms can be realized, so that comprehensive service is provided for the user, and the user experience is improved.
FIG. 2 is a flowchart illustrating a method for account management in one embodiment. It should be understood that, although the steps in the flowchart of fig. 2 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a portion of the steps in fig. 2 may include multiple sub-steps or multiple stages that are not necessarily performed at the same time, but may be performed at different times, and the order of performance of the sub-steps or stages is not necessarily sequential, but may be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
Fig. 3 is a schematic diagram of an application scenario according to an embodiment of the present application, and as shown in fig. 3, a first platform of the present application is 310, and a management account and a virtual asset account are disposed on the first platform. The virtual asset account may also be a transaction management account and the management account may be an account management account.
The user initiates a transaction application at the second platform 320, which may be a transfer of the virtual asset of the first user of the third platform to the second user of the third platform 330.
The first platform 310 determines that the transaction account is operated after receiving the transaction application, and the transaction management account then effects the transfer of the virtual asset of the first user of the third platform 330 to the second user of the third platform 330 through interaction with the third platform 330.
If the user initiates an application at the first platform 310, the transaction application may be a transfer of the virtual asset of the first user of the third platform 330 to a second user of the third platform 330. After the user initiates, the account management account of the first user of the first platform 310 generates a transaction request, the generated request is executed by the transaction management account, and the transaction management account realizes the transfer of the virtual asset of the first user of the third platform 330 to the second user of the third platform 330 through the interaction with the third platform 330.
The transaction request is a transfer of the virtual asset from the first user, which in practice may be considered a "payment". In the embodiment of the application, the virtual asset can be transferred to the first user, and the transfer can be regarded as charging in practical application.
In the embodiment of the present application, the transfer of the virtual asset between the third platform and the fourth platform may also be realized, and the management of the virtual asset between the third platform and the fourth platform may be the transfer of the same user or the transfer of different users.
In one embodiment of the application, the second platform and the third platform can be internet transaction platforms, and the first platform can be a payment platform. The user can initiate a request on the payment platform, purchase goods from the merchant on the second platform or the third platform, transfer virtual resources in the account of the user, namely funds into the account of the merchant, and realize payment.
The second platform can also be a financial institution such as a bank, and a user can transfer own funds from the payment platform to the bank, namely, the funds are withdrawn; or can be transferred from the bank to the payment platform, namely the fund recharging is realized.
In the embodiment of the application, a first account and a second account are set, and the attributes of the first account and the second account are different, so that the specific content of management is also different. The first account and the second account are associated, and management of the plurality of accounts by a user is facilitated; the first account and the second account have different attributes, different data are managed respectively, certain mutual isolation exists between the data, and the safety of the system can be improved. In the embodiment of the application, the first account and the second account have different attributes, and the specific management contents are different, but the management of the virtual assets and the like of the same user on the same platform, the management of the virtual assets and the like of the same user on different platforms, the management of the virtual assets and the like of different users on different platforms can be realized, so that comprehensive service is provided for the user, and the user experience is improved.
As shown in fig. 4, an account management apparatus is further provided in an embodiment of the present application, where the apparatus is applied to a first platform, the account is attributed to the first platform, the account includes a first account and a second account, attributes of the first account and the second account are different, and the first account and the second account are associated;
the device comprises:
a receiving unit 410, configured to receive a first request;
an account obtaining unit 420, configured to obtain, according to the first request, a target account of the first request;
a processing unit 430, configured to verify whether the first request is legal if a target account of the first request is a first account of a first user, and operate a first account and a second account of the first user according to the first request if the first request is legal;
wherein the first request is generated by a second platform and forwarded by the second platform to the first platform, or
The first request is generated by a second account of the first platform.
In the embodiment of the application, the first request comprises a user identification and a request category,
the account obtaining unit 420 is further configured to:
acquiring a first user from the users of the first platform according to the user identification;
acquiring account types according to the request types, wherein the account types comprise a first account and a second account;
the first account or the second account of the first user corresponding to the account type is used as a target account.
In this embodiment of the application, the target platform is included in the first request,
the processing unit 430 is further configured to:
judging whether the second platform is a legal source platform of the first platform;
if the second platform is a legal source platform, judging whether the first user is a legal user of the first platform;
if the first user is a legal user of the first platform, judging whether the target platform is a legal target platform of the first platform;
and if the target platform is a legal target platform, confirming that the first request is legal.
In this embodiment of the application, the processing unit 430 is further configured to:
the operating the first account and the second account of the first user comprises:
acquiring a target platform in the first request;
obtaining a third account of the first user on the target platform, wherein the third account comprises virtual assets;
acquiring the operation in the first request;
and operating the virtual assets of the third account on the target platform according to the operation in the first request.
In this embodiment of the application, the processing unit 430 is further configured to:
the operating on the virtual assets of the third account on the target platform comprises:
enabling the target platform to judge whether the operation on the virtual assets of the third account is legal or not;
if the operation is legal, transferring the virtual assets of the third account of the target platform to a fourth account of the target platform;
and receiving the operation result of the transfer success or the transfer failure sent by the target platform.
In this embodiment of the application, the processing unit 430 is further configured to:
enabling the target platform to judge whether the number of the virtual assets needing to be transferred is less than or equal to the current number of the virtual assets of the third account;
and if the quantity of the virtual assets to be transferred is less than or equal to the current quantity of the virtual assets of the third account, confirming that the operation on the virtual assets of the third account is legal.
In this embodiment of the application, the processing unit 430 is further configured to:
causing the target platform to send a first transfer request to a third platform, wherein the first transfer request is to transfer a virtual asset of a third account of the target platform into a fifth account of the third platform;
enabling the third platform to check whether the first transfer request is legal or not, and enabling the third platform to execute the first transfer request if the first transfer request is legal;
enabling the target platform to receive the operation result of the transfer success or the transfer failure sent by the third platform;
and receiving the operation result of the transfer success or the transfer failure forwarded by the target platform.
In this embodiment of the application, the processing unit 430 is further configured to:
causing the target platform to send a second transfer request to a fourth platform, the second transfer request being a transfer of the virtual asset from a sixth account of the fourth platform into a third account of the target platform;
enabling the fourth platform to check whether the second transfer request is legal, and enabling the fourth platform to execute the second transfer request if the second transfer request is legal;
enabling the target platform to receive the operation result of the transfer success or the transfer failure sent by the fourth platform;
and receiving the operation result of the transfer success or the transfer failure forwarded by the target platform.
In this embodiment of the application, the processing unit 430 is further configured to:
and if the target account of the first request is the second account of the first user, operating the second account of the first user according to the first request.
In an embodiment of the present application, the first request further includes: a modification to an account, if the first request is a modification, the processing unit 430 is further configured to:
modifying a second account of the first user in accordance with the first request,
and updating the corresponding relation between the first account of the first user and the second account of the first user.
The embodiment of the application can improve the safety of the system, can realize the management of the virtual assets and the like of the same user on the same platform, the management of the virtual assets and the like of the same user on different platforms and the management of the virtual assets and the like of different users on different platforms, provides comprehensive services for the users and improves the user experience.
FIG. 5 is a diagram illustrating an internal structure of a computer device in one embodiment. The computer device may specifically be the terminal 110 (or the server 120) in fig. 1. As shown in fig. 5, the computer apparatus includes a processor, a memory, a network interface, an input device, and a display screen connected through a system bus. Wherein the memory includes a non-volatile storage medium and an internal memory. The non-volatile storage medium of the computer device stores an operating system and may also store a computer program that, when executed by the processor, causes the processor to implement the chart generation method. The internal memory may also have stored therein a computer program that, when executed by the processor, causes the processor to perform the chart generation method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
Those skilled in the art will appreciate that the architecture shown in fig. 5 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
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 following steps when executing the computer program: the method is applied to a first platform, the accounts are attributed to the first platform, the accounts comprise a first account and a second account, the first account and the second account are different in attributes, and the first account and the second account are associated; the method comprises the following steps: receiving a first request; according to the first request, acquiring a target account of the first request; if the target account of the first request is the first account of the first user, verifying whether the first request is legal, and if the first request is legal, operating the first account and the second account of the first user according to the first request; wherein the first request is generated by a second platform and forwarded by the second platform to the first platform, or the first request is generated by a second account of the first platform.
In an embodiment, the processor executes the computer program to implement the steps of the above method, which are not described herein again.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of: the method is applied to a first platform, the accounts are attributed to the first platform, the accounts comprise a first account and a second account, the first account and the second account are different in attributes, and the first account and the second account are associated; the method comprises the following steps: receiving a first request; according to the first request, acquiring a target account of the first request; if the target account of the first request is the first account of the first user, verifying whether the first request is legal, and if the first request is legal, operating the first account and the second account of the first user according to the first request; wherein the first request is generated by a second platform and forwarded by the second platform to the first platform, or the first request is generated by a second account of the first platform.
In an embodiment, the computer program, when executed by the processor, further implements the steps of the above method, which are not described herein again.
In one embodiment, a computer program product or computer program is provided that includes computer instructions stored in a computer-readable storage medium. The processor of the computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions to cause the computer device to perform the steps of: the method is applied to a first platform, the accounts are attributed to the first platform, the accounts comprise a first account and a second account, the first account and the second account are different in attributes, and the first account and the second account are associated; the method comprises the following steps: receiving a first request; according to the first request, acquiring a target account of the first request; if the target account of the first request is the first account of the first user, verifying whether the first request is legal, and if the first request is legal, operating the first account and the second account of the first user according to the first request; wherein the first request is generated by a second platform and forwarded by the second platform to the first platform, or the first request is generated by a second account of the first platform.
In an embodiment, the computer program product or the computer program when executed further implements the steps of the above method, which are not described herein again.
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 a computer program, which can be stored in a non-volatile computer-readable storage medium, and can include the processes of the embodiments of the methods described above when the program is executed. 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).
It is noted that, in this document, relational terms such as "first" and "second," and the like, may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The foregoing are merely exemplary embodiments of the present invention, which enable those skilled in the art to understand or practice the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. An account management method is applied to a first platform, the account is attributed to the first platform, the account comprises a first account and a second account, the attributes of the first account and the second account are different, and the first account and the second account are associated;
the method comprises the following steps:
receiving a first request;
according to the first request, acquiring a target account of the first request;
if the target account of the first request is the first account of the first user, verifying whether the first request is legal, and if the first request is legal, operating the first account and the second account of the first user according to the first request;
wherein the first request is generated by a second platform and forwarded by the second platform to the first platform, or
The first request is generated by a second account of the first platform.
2. The method of claim 1, the first request comprising a user identification and a request category,
the obtaining of the target account of the first request according to the first request includes:
acquiring a first user from the users of the first platform according to the user identification;
acquiring account types according to the request types, wherein the account types comprise a first account and a second account;
the first account or the second account of the first user corresponding to the account type is used as a target account.
3. The method of claim 1, wherein operating the first account and the second account of the first user comprises:
acquiring a target platform in the first request;
obtaining a third account of the first user on the target platform, wherein the third account comprises virtual assets;
acquiring the operation in the first request;
and operating the virtual assets of the third account on the target platform according to the operation in the first request.
4. The method of claim 3, wherein operating on the virtual asset of the third account on the target platform comprises:
enabling the target platform to judge whether the operation on the virtual assets of the third account is legal or not;
if the operation is legal, transferring the virtual assets of the third account of the target platform to a fourth account of the target platform;
and receiving the operation result of the transfer success or the transfer failure sent by the target platform.
5. The method of claim 3, wherein operating on the virtual asset of the third account on the target platform comprises:
causing the target platform to send a first transfer request to a third platform, wherein the first transfer request is to transfer a virtual asset of a third account of the target platform into a fifth account of the third platform;
enabling the third platform to check whether the first transfer request is legal or not, and enabling the third platform to execute the first transfer request if the first transfer request is legal;
enabling the target platform to receive the operation result of the transfer success or the transfer failure sent by the third platform;
and receiving the operation result of the transfer success or the transfer failure forwarded by the target platform.
6. The method of claim 3, wherein operating on the virtual asset of the third account on the target platform comprises:
causing the target platform to send a second transfer request to a fourth platform, the second transfer request being a transfer of the virtual asset from a sixth account of the fourth platform into a third account of the target platform;
enabling the fourth platform to check whether the second transfer request is legal, and enabling the fourth platform to execute the second transfer request if the second transfer request is legal;
enabling the target platform to receive the operation result of the transfer success or the transfer failure sent by the fourth platform;
and receiving the operation result of the transfer success or the transfer failure forwarded by the target platform.
7. The method of claim 1, wherein if the target account of the first request is a second account of the first user, operating the second account of the first user according to the first request.
8. An account management device is applied to a first platform, the account is attributed to the first platform and comprises a first account and a second account, the attributes of the first account and the second account are different, and the first account and the second account are associated;
the device comprises:
a receiving unit configured to receive a first request;
the account acquisition unit is used for acquiring a target account of the first request according to the first request;
the processing unit is used for verifying whether the first request is legal or not if the target account of the first request is the first account of the first user, and operating the first account and the second account of the first user according to the first request if the first request is legal;
wherein the first request is generated by a second platform and forwarded by the second platform to the first platform, or
The first request is generated by a second account of the first platform.
9. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the steps of the method of any of claims 1 to 7 are implemented when the computer program is executed by the processor.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110744584.3A CN113487303A (en) | 2021-07-01 | 2021-07-01 | Account management method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110744584.3A CN113487303A (en) | 2021-07-01 | 2021-07-01 | Account management method and device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113487303A true CN113487303A (en) | 2021-10-08 |
Family
ID=77939125
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110744584.3A Pending CN113487303A (en) | 2021-07-01 | 2021-07-01 | Account management method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113487303A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110258111A1 (en) * | 2010-04-19 | 2011-10-20 | Thanigaivel Ashwin Raj | Alias management and off-us dda processing |
| US20140244502A1 (en) * | 2013-02-22 | 2014-08-28 | Lucy Ma Zhao | Multi-platform in-application payment system |
| US20160328685A1 (en) * | 2013-12-30 | 2016-11-10 | Tencent Technology (Shenzhen) Company Limited | Resource reallocation method and server |
| US20190007519A1 (en) * | 2017-06-29 | 2019-01-03 | Bank Of America Corporation | System for sending digital requests for resource transfers |
| CN109472576A (en) * | 2018-09-12 | 2019-03-15 | 湖南搜云网络科技股份有限公司 | The processing method and processing device of digital asset, storage medium |
| CN111833066A (en) * | 2020-07-01 | 2020-10-27 | 中国建设银行股份有限公司 | Account authorization method, device and system |
| CN112446780A (en) * | 2020-11-26 | 2021-03-05 | 平安普惠企业管理有限公司 | Account management method and device, computer equipment and storage medium |
-
2021
- 2021-07-01 CN CN202110744584.3A patent/CN113487303A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20110258111A1 (en) * | 2010-04-19 | 2011-10-20 | Thanigaivel Ashwin Raj | Alias management and off-us dda processing |
| US20140244502A1 (en) * | 2013-02-22 | 2014-08-28 | Lucy Ma Zhao | Multi-platform in-application payment system |
| US20160328685A1 (en) * | 2013-12-30 | 2016-11-10 | Tencent Technology (Shenzhen) Company Limited | Resource reallocation method and server |
| US20190007519A1 (en) * | 2017-06-29 | 2019-01-03 | Bank Of America Corporation | System for sending digital requests for resource transfers |
| CN109472576A (en) * | 2018-09-12 | 2019-03-15 | 湖南搜云网络科技股份有限公司 | The processing method and processing device of digital asset, storage medium |
| CN111833066A (en) * | 2020-07-01 | 2020-10-27 | 中国建设银行股份有限公司 | Account authorization method, device and system |
| CN112446780A (en) * | 2020-11-26 | 2021-03-05 | 平安普惠企业管理有限公司 | Account management method and device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11106476B2 (en) | Helper software developer kit for native device hybrid applications | |
| CN110599276B (en) | Bill reimbursement method, device and equipment and computer storage medium | |
| US11640604B2 (en) | Automated blockchain address creation and transfers by uniform resource locator generation and execution | |
| US20160098791A1 (en) | Method, terminal and system for resetting payment password | |
| US11640482B2 (en) | System and method for providing trusted links between applications | |
| US9576288B1 (en) | Automatic approval | |
| CN112446780A (en) | Account management method and device, computer equipment and storage medium | |
| CN111210190B (en) | File signing method, device, computer equipment and storage medium | |
| CN107392582B (en) | Method and device for realizing resource transfer and method and device for realizing collection and payment | |
| CN108846741B (en) | Payment processing method and approval document processing method | |
| US20190122211A1 (en) | Method and device facilitating expansion of primary payment instruments | |
| US20190102778A1 (en) | Secure online transaction system and method therefor | |
| CN110333866B (en) | Method and device for generating receiving page and electronic equipment | |
| CN113487303A (en) | Account management method and device, computer equipment and storage medium | |
| CN112990902A (en) | Service processing method, device, computer equipment and storage medium | |
| CN113487406A (en) | Data processing method, data processing device, computer equipment and storage medium | |
| CN111061558A (en) | Method, device, computer equipment and storage medium for processing virtual resource data | |
| CN110796436A (en) | Process management system, method, device and readable medium for shared office | |
| WO2020056455A1 (en) | Transaction system | |
| US20200104228A1 (en) | Asynchronous self-proving transactions | |
| CN108573445A (en) | Financial risk control method and electronic equipment | |
| US11972029B2 (en) | System and method for providing trusted links between applications | |
| CN113469788B (en) | Multi-channel data processing method, device, computer equipment and storage medium | |
| CN111754324B (en) | Cloud ERP bank-enterprise docking processing method, system and processing ends | |
| US20230262037A1 (en) | Techniques for authenticating using uniquely assigned webpages |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |