CN111429125A - Account management method and device, storage medium and electronic equipment - Google Patents

Account management method and device, storage medium and electronic equipment Download PDF

Info

Publication number
CN111429125A
CN111429125A CN202010186638.4A CN202010186638A CN111429125A CN 111429125 A CN111429125 A CN 111429125A CN 202010186638 A CN202010186638 A CN 202010186638A CN 111429125 A CN111429125 A CN 111429125A
Authority
CN
China
Prior art keywords
account
information
quota
service platform
request
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.)
Granted
Application number
CN202010186638.4A
Other languages
Chinese (zh)
Other versions
CN111429125B (en
Inventor
关成龙
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
JD Digital Technology Holdings Co Ltd
Original Assignee
JD Digital Technology Holdings Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by JD Digital Technology Holdings Co Ltd filed Critical JD Digital Technology Holdings Co Ltd
Priority to CN202010186638.4A priority Critical patent/CN111429125B/en
Publication of CN111429125A publication Critical patent/CN111429125A/en
Application granted granted Critical
Publication of CN111429125B publication Critical patent/CN111429125B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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/108—Remote banking, e.g. home banking
    • 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
    • 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/389—Keeping log of transactions for guaranteeing non-repudiation of a transaction
    • 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

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Strategic Management (AREA)
  • Theoretical Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Technology Law (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

The application provides an account management method, an account management device, a storage medium and an electronic device. The account management method provided by the embodiment of the application comprises the following steps: acquiring restriction agreement information sent by a service platform, wherein the restriction agreement information comprises account information and preset restriction information, and the preset restriction information is used for restricting the amount of an account; and determining a calling protocol according to the limiting agreement information so that the account quota management system responds to an account processing request initiated by the service platform according to the quota calling protocol, wherein the account processing request is used for changing the quota information corresponding to the account information in the service platform. The account management method provided by the embodiment of the application realizes the componentization of the account quota management system, so that when a service platform needs a service system with a quota function, the quota system does not need to be additionally developed, and a large amount of repeated development work performed by manpower and material resources is saved.

Description

Account management method and device, storage medium and electronic equipment
Technical Field
The present application relates to the field of data processing technologies, and in particular, to an account management method and apparatus, a storage medium, and an electronic device.
Background
Electronic payments are currently rapidly evolving with the constant development of internet technology, which means that more and more transactions are no longer conducted offline. In order to limit the payment, account limits are usually set, so that the limit is set for a specific account according to the risk management and control of a specific service or the service requirement of the specific service.
At present, the existing account quota management systems are generally highly coupled with business systems, and for each business system, a separate account quota management system needs to be independently developed. The primary quota function of an account quota management system typically requires the confirmation of a quota account and a range of quota. Specifically, the confirmation of the quota account may be a confirmation according to a specific business model, such as: user account number, user certificate number, user card number, use channel, etc. And for the determination of the limit range, the single-stroke amount limit, the daily stroke number, the daily stroke amount, the monthly stroke number, the annual stroke number, the lifetime money number, the stroke number and the money amount of the custom start and end time can be set independently according to different services.
However, in the process of implementing the present application, the inventor finds that, because account quota management systems need to be developed separately and integrally for different business systems, the business systems need to consume a large amount of manpower and material resources to perform repetitive development work when accessing the account quota management function.
Disclosure of Invention
The embodiment of the application provides an account management method, an account management device, a storage medium and electronic equipment, and aims to solve the problem that a business system needs to consume a large amount of manpower and material resources to perform repeated development work when accessing an account quota management function.
In a first aspect, an embodiment of the present application provides an account management method, which is applied to an account quota management system, and the method includes:
acquiring restriction agreement information sent by a service platform, wherein the restriction agreement information comprises account information and preset restriction information, and the preset restriction information is used for restricting the amount of an account;
and determining a calling protocol according to the restriction agreement information so that the account quota management system responds to an account processing request initiated by the service platform according to the calling protocol, wherein the account processing request is used for changing the quota information corresponding to the account information in the service platform.
In one possible design, after the determining to invoke the protocol according to the restriction agreement information, the method further includes:
acquiring a contract modification request sent by the service platform, wherein the contract modification request comprises new restriction agreement information;
and updating preset restriction information in the calling protocol according to the new restriction agreement information.
In a possible design, the account information is any one of the account information in the service platform, or all the account information in the service platform.
In one possible design, the account processing request includes any one or more of an accounting request, a reimbursement request, and a limit inquiry request.
In one possible design, after the determining to invoke the protocol according to the restriction agreement information, the method further includes:
acquiring the accounting request, wherein the accounting request comprises account information to be accounted and the amount of money to be accounted;
if a calling protocol corresponding to the account information to be billed exists, acquiring a residual amount corresponding to the account information to be billed;
if the amount to be booked is less than the remaining amount, sending bookkeeping failure information, wherein the bookkeeping failure information is used for indicating the service platform to stop payment operation;
and if the amount to be booked is larger than or equal to the remaining amount, sending bookkeeping success information, wherein the bookkeeping success information is used for indicating the service platform to continue the payment operation.
In one possible design, after the sending the accounting success information, the method further includes:
acquiring the offset request, wherein the offset request comprises account information to be offset and the amount of the offset to be offset;
and carrying out cancellation processing on the surplus limit corresponding to the account information to be cancelled according to the amount to be cancelled.
In one possible design, the invoking protocol includes time range information and restriction information corresponding to the time range information, where the restriction information corresponding to the time range information and the time range information is determined according to the restriction agreement information.
In one possible design, the calling protocol includes a plurality of layers of child nodes, and the plurality of layers of child nodes form a tree structure, wherein each layer of child node includes account information and preset restriction information;
when the account quota management system responds to the account processing request initiated by the service platform according to the calling protocol, selecting the minimum preset quota from a first leaf node to a root node in the calling protocol as a quota corresponding to the account processing request, wherein the first leaf node is a child node corresponding to the account processing request.
In one possible design, when the account processing request includes an accounting request, accounting processing is performed on a first child node and a root node corresponding to account information to be accounted and all child nodes between the first child node and the root node according to account information to be accounted and an amount to be accounted in the accounting request; or,
and when the account processing request comprises an accounting request, carrying out cancellation processing on a second child node and a root node corresponding to the account information to be cancelled and all child nodes between the second child node and the root node according to the account information to be cancelled and the amount to be cancelled and cancelled in the accounting request.
In one possible design, for each account processing request record, corresponding account processing record information is recorded, and the account processing record information includes an account processing request type identifier.
In a second aspect, an embodiment of the present application provides an account management apparatus, including:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring restriction agreement information sent by a service platform, the restriction agreement information comprises account information and preset restriction information, and the preset restriction information is used for restricting the amount of an account;
and the processing module is used for determining a calling protocol according to the restriction agreement information so that the account management system responds to an account processing request initiated by the service platform according to the calling protocol, and the account processing request is used for changing the quota information corresponding to the account information in the service platform.
In a possible design, the obtaining module is further configured to obtain a contract modification request sent by the service platform, where the contract modification request includes new restriction agreement information;
and the processing module is also used for updating the preset restriction information in the calling protocol according to the new restriction agreement information.
In a possible design, the account information is any one of the account information in the service platform, or all the account information in the service platform.
In one possible design, the account processing request includes any one or more of an accounting request, a reimbursement request, and a limit inquiry request.
In a possible design, the obtaining module is further configured to obtain the billing request, where the billing request includes information of an account to be billed and an amount to be billed;
the acquisition module is also used for acquiring the remaining amount corresponding to the account information to be billed;
the account management device further comprises:
the sending module is used for sending accounting failure information, and the accounting failure information is used for indicating the service platform to stop payment operation;
the sending module is further configured to send accounting success information, where the accounting success information is used to instruct the service platform to continue the payment operation.
In a possible design, the obtaining module is further configured to obtain the offset request, where the offset request includes account information to be offset and an offset amount to be offset;
and the processing module is also used for carrying out cancellation processing on the surplus limit corresponding to the account information to be cancelled according to the amount to be cancelled.
In one possible design, the invoking protocol includes time range information and restriction information corresponding to the time range information, where the restriction information corresponding to the time range information and the time range information is determined according to the restriction agreement information.
In one possible design, the multiple layers of child nodes form a tree structure, wherein each layer of child nodes includes account information and preset restriction information;
when the account quota management system responds to the account processing request initiated by the service platform according to the calling protocol, selecting the minimum preset quota from a first leaf node to a root node in the calling protocol as a quota corresponding to the account processing request, wherein the first leaf node is a child node corresponding to the account processing request.
In one possible design, when the account processing request includes an accounting request, accounting processing is performed on a first child node and a root node corresponding to account information to be accounted and all child nodes between the first child node and the root node according to account information to be accounted and an amount to be accounted in the accounting request; or,
and when the account processing request comprises an accounting request, carrying out cancellation processing on a second child node and a root node corresponding to the account information to be cancelled and all child nodes between the second child node and the root node according to the account information to be cancelled and the amount to be cancelled and cancelled in the accounting request.
In one possible design, for each account processing request record, corresponding account processing record information is recorded, and the account processing record information includes an account processing request type identifier.
In a third aspect, an embodiment of the present application further provides an electronic device, including:
a processor; and the number of the first and second groups,
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform any one of the possible account management methods of the first aspect via execution of the executable instructions.
In a fourth aspect, an embodiment of the present application further provides a storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements any one of the possible account management methods in the first aspect.
According to the account management method, the account limit management device, the storage medium and the electronic equipment, the account limit management system is modularized, when a service platform needs to access a limit function, the account limit management system can determine a limit calling protocol according to limit agreement information, so that the service platform can respond to an account processing request initiated by the service platform by calling an interface provided by the account limit management system, and the account limit management system can change limit information corresponding to account information in the service platform according to the account processing request. Therefore, different service platforms can share one account quota management system, when a new service platform needs a service system with a quota function, and the quota system does not need to be additionally developed, the account quota management system can respond to an account processing request initiated by the service platform according to a quota calling protocol in a mode of directly accessing the service platform into the account quota management system, and further repetitive development work which is performed by the service system and needs to consume a large amount of manpower and material resources when the service system is accessed into the account quota management function is avoided.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to these drawings without inventive exercise.
FIG. 1 is a schematic diagram of an application scenario of an account management method according to an example embodiment;
FIG. 2 is a schematic diagram of an application scenario of an account management method according to another example embodiment;
FIG. 3 is a flow diagram illustrating an account management method according to an example embodiment;
FIG. 4 is a flow diagram illustrating an account management method according to another example embodiment;
FIG. 5 is a diagram illustrating an exemplary architecture of a multi-level quota calling protocol in the embodiment of FIG. 4;
FIG. 6 is a flow diagram illustrating an account management method according to yet another example embodiment;
FIG. 7 is a schematic diagram illustrating an account management device according to an example embodiment;
fig. 8 is a schematic structural diagram of an electronic device shown in the present application according to an example embodiment.
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.
The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the above-described drawings (if any) are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
With the continuous development of internet technology, electronic payments are rapidly developed, which means that more and more transactions are no longer performed offline. In order to limit the payment, account limits are usually set, so that the limit is set for a specific account according to the risk management and control of a specific service or the service requirement of the specific service.
Currently, existing account management systems, for example: the account quota management system is generally highly coupled with the business systems, and a separate account quota management system needs to be independently developed for each business system. The primary quota function of an account quota management system typically requires the confirmation of a quota account and a range of quota. Specifically, the confirmation of the quota account may be a confirmation according to a specific business model, such as: user account number, user certificate number, user card number, use channel, etc. And for the determination of the limit range, the single-stroke amount limit, the daily stroke number, the daily stroke amount, the monthly stroke number, the annual stroke number, the lifetime money number, the stroke number and the money amount of the custom start and end time can be set independently according to different services.
However, since the account quota management system is required to be separately and integrally developed for different business systems. Therefore, in the prior art, for each service system requiring the quota function, when the service system is developed, a quota system needs to be integrally developed, and therefore, when the current service system accesses the account quota management function, a large amount of manpower and material resources need to be consumed to perform repeated development work.
In the existing account quota mode, when the quota account range is modified, the quota system which is developed in an integrated mode needs to be modified independently to update the function, when the service has hierarchy quota, the service needs to be called for many times, and if one account fails to be billed, the account which is successfully billed needs to be recovered. Moreover, there is no perfect statistical function, and the system operation condition cannot be monitored well.
In view of the above problems, embodiments of the present application provide an account management method, when a service platform needs to access a quota function, after a service platform and an account quota management system are established, an interface provided by the account quota management system is directly called, so that the account quota management system directly generates a quota calling protocol according to restriction agreement information, and provides a quota service for the service platform. Therefore, different service systems can share one set of account quota management system, and when a new service platform needs a service system with a quota function and the quota system does not need to be additionally developed, the account quota management system can respond to an account processing request initiated by the service platform according to a quota calling protocol by directly accessing the account quota management system. And repeated development work which is carried out by consuming a large amount of manpower and material resources when the business system is accessed to the account quota management function is avoided.
Fig. 1 is a schematic view of an application scenario of an account management method according to an example embodiment. As shown in fig. 1, in this embodiment, when a service platform (caller server 100) needs to access a quota function, a system access file may be generated first, and in the system access file, attribute information of the service platform (for example, an assigned platform number and a related function description of the system), service platform hierarchy information, service platform default configuration information, and a sample that can be used for testing the service platform may be included. After the account quota management system (the quota server 200) acquires the system access file generated by the service platform, the platform number may be configured for the service platform in the account quota management system, so as to establish a connection between the service platform and the account quota management system.
Fig. 2 is a schematic view of an application scenario of an account management method according to another exemplary embodiment of the present application. As shown in fig. 2, in order to implement the function of limiting specific services in the service platform, the terminal device (e.g., the personal computer 310 or the smart phone 320) may send the restriction agreement information to the service platform (the caller server 100). Illustratively, when the quota function for a specific service in the service platform is to be implemented, the limitation agreement information may be limitation contract information, and specifically, the limitation contract information includes account information and preset limitation information. Then, the service platform (caller server 100) sends the limit contract information to the account limit management system (limit server 200), so that the account limit management system determines a limit calling agreement according to the limit contract information, and the account limit management system responds to an account processing request initiated by the service platform according to the limit calling agreement, wherein the account processing request is used for changing the limit information corresponding to the account information in the service platform, and the account processing request can be, for example, a billing request, a reimbursement request and a limit inquiry request. When the account processing request is an accounting request, the account limit management system processes the accounting request according to the limit calling protocol so as to perform accounting processing in the account limit management system, and therefore line information corresponding to the account information in the service platform is updated.
It can be seen that, in the account management method provided in this embodiment, the account quota management system is modularized, and when the service platform needs to access the quota function, after the service platform and the account quota management system are established, the account quota management system directly generates a quota calling agreement according to the quota contract information by calling an interface provided by the account quota management system, so as to provide the quota service for the service platform. Therefore, different service systems can share one set of account quota management system, and when a new service platform needs a service system with a quota function and the quota system does not need to be additionally developed, the account quota management system can respond to an account processing request initiated by the service platform according to a quota calling protocol by directly accessing the account quota management system. And repeated development work which is carried out by consuming a large amount of manpower and material resources when the business system is accessed to the account quota management function is avoided.
Fig. 3 is a flowchart illustrating an account management method according to an example embodiment of the present application. As shown in fig. 3, the account management method provided in this embodiment includes:
step 101, acquiring the restriction agreement information sent by the service platform.
Specifically, the restriction agreement information sent by the service platform may be obtained, where the restriction agreement information includes account information and preset restriction information.
And step 102, determining a quota calling protocol according to the limitation agreement information.
And 103, responding to the account processing request initiated by the service platform according to the quota calling protocol.
After the account quota management system obtains the quota contract information, a quota calling agreement may be determined according to the quota contract information. The quota calling protocol may include account information on quota, the quota amount of an account corresponding to the account information, and a calling interface of the service platform calling the account quota management system, so that when the service platform initiates an account processing request, for example, when the service platform initiates an accounting request, an offsetting request, or a quota inquiring request, the account quota management system responds to the account processing request initiated by the service platform according to the quota calling protocol, thereby changing the quota information corresponding to the account information in the service platform.
After the quota calling agreement is determined according to the quota contract information, a contract modification request sent by the service platform can be obtained, wherein the contract modification request comprises new quota contract information, and the preset quota information in the calling agreement is updated according to the new quota contract information.
The account information may be any one or a plurality of account information in the service platform, or all account information in the service platform. It should be noted that the preset quota in the quota contract information may be configured in a unified manner or in a personalized manner. For example, a uniform limit amount can be configured for all accounts of a first service platform accessed by the account limit management system, and limit amounts corresponding to respective accounts of a second service platform accessed by the account limit management system can be individually configured.
In addition, it should be noted that the quota calling protocol may include time range information and quota information corresponding to each time range information, where the limitation information corresponding to the time range information and the time range information is determined according to the quota contract information. The limit information may be a limit number and a limit amount. The quota management system can determine the specific quota of the corresponding account according to the time range information and the quota information in the quota calling protocol. The time range information in the quota calling protocol and the quota information corresponding to each time range information may be modified according to service requirements, for example, the quota information may be determined and modified according to a credit investigation condition of the service platform on an account, or may be modified according to an adjustment request initiated by a user to the service platform. Specifically, for a single account, any one or any more of the following information may be included in the quota calling protocol: whether the single transaction amount and the single amount are started or not; whether daily transaction stroke number, daily transaction amount and daily transaction are controlled or not is judged; whether the monthly transaction pen data, the monthly transaction amount and the monthly transaction are controlled or not; the number of annual transaction strokes, the annual transaction amount, whether the annual transaction is controlled, the lifelong transaction stroke, the lifelong transaction amount, whether the lifelong transaction is controlled, the data of the transaction stroke in the user-defined time interval, the accumulated transaction amount in the user-defined event interval and whether the transaction in the user-defined interval is controlled; according to the requirement of the service, if the service pair quota is set as a fixed value, a default quota template function can be used for setting, wherein whether a certain item is enabled or not can be set; if not, the setting is no. And when the existing quota is modified, the modified record is recorded, so that the follow-up query problem can be conveniently used.
In this embodiment, by componentizing the account quota management system, when the service platform needs to access the quota function, the account quota management system may determine a quota call agreement according to the quota contract information, so that the service platform may respond to the account processing request initiated by the service platform by calling an interface provided by the account quota management system, and thus the account quota management system may change the quota information corresponding to the account information in the service platform according to the account processing request. Therefore, different service platforms can share one account quota management system, when a new service platform needs a service system with a quota function, and the quota system does not need to be additionally developed, the account quota management system can respond to an account processing request initiated by the service platform according to a quota calling protocol in a mode of directly accessing the service platform into the account quota management system, and further repetitive development work which is performed by the service system and needs to consume a large amount of manpower and material resources when the service system is accessed into the account quota management function is avoided. In addition, the time range information in the quota calling agreement can be determined through the quota contract information, and the quota information corresponding to each time range information can be determined according to the service requirement, so that the service platform or the user can be adapted to the change of the service requirement, and the quota in the account can be dynamically adjusted by configuring the parameters in the quota contract information.
Fig. 4 is a flowchart illustrating an account management method according to another example embodiment of the present application. As shown in fig. 4, the account management method provided in this embodiment includes:
step 201, obtaining the restriction agreement information sent by the service platform.
Step 202, determining a quota calling protocol according to the restriction agreement information.
And step 203, responding to the account processing request initiated by the service platform according to the quota calling protocol.
It should be noted that, the specific implementation manner of steps 201 to 203 in this embodiment may refer to the description in steps 101 to 103 in the embodiment shown in fig. 3, and is not described again here.
Step 204, obtaining the accounting request.
When the terminal equipment is in a consumption behavior, an accounting request needs to be initiated to the service platform, and the service platform calls a related interface of the account limit management system and organizes data according to a format required by the account limit management system, so that the account limit management system obtains the accounting request, wherein the accounting request comprises account information to be accounted and the amount of money to be accounted.
And step 205, if the quota calling agreement corresponding to the account information to be billed exists, acquiring the residual quota corresponding to the account information to be billed.
After the account quota management system obtains the accounting request and before accounting, whether a quota calling protocol corresponding to the account information to be accounted exists or not needs to be inquired according to the account information to be accounted. And if the quota calling protocol corresponding to the account information to be billed exists, acquiring the residual quota corresponding to the account information to be billed.
And step 206, judging whether the amount to be billed is larger than or equal to the remaining amount. If yes, go to step 207, and if no, go to step 208.
Step 207, transmitting accounting success information.
Step 208, transmitting accounting failure information.
And if the amount to be booked is less than the remaining amount, transmitting bookkeeping failure information, wherein the bookkeeping failure information is used for indicating the service platform to stop the payment operation, and if the amount to be booked is greater than or equal to the remaining amount, transmitting bookkeeping success information, and the bookkeeping success information is used for indicating the service platform to continue the payment operation.
It should be noted that the quota calling protocol may be in the form of a single node (corresponding to a single billing quota), or may include multiple nodes (corresponding to hierarchical quota billing). When the limit calling protocol comprises a plurality of layers of child nodes, the plurality of layers of child nodes form a tree structure, wherein each layer of child nodes comprises account information and preset limit information, when the account limit management system responds to an account processing request initiated by a service platform according to the limit calling protocol, the minimum preset limit from a first leaf node to a root node in the limit calling protocol is selected as a limit corresponding to the account processing request, and the first leaf node is a child node corresponding to the account processing request.
And when the account processing request comprises an accounting request, accounting processing is carried out on the first child node, the root node and all child nodes between the first child node and the root node corresponding to the account information to be accounted according to the account information to be accounted and the amount to be accounted in the accounting request.
The method can be used for abstracting a field with an example original value for different service accounts so as to identify a specific account, if the specific account is a multi-level account, a quota protocol maintains data in a tree structure, and a lower node records an ID of an upper node, wherein an example original value rule can be that a root node example original value + # symbol + a lower example original value + a # symbol + a lower example original value, until the specific account is added to a leaf node fig. 5 is a structural example diagram of the multi-level quota calling protocol in the embodiment of fig. 4, a service model is analyzed according to the specific service, an account and a hierarchy to which a limited account is abstracted for a single-level quota account, such as a parent payment service, a user ID. for a multi-level quota account, for example, a bank card payment multi-channel billing service, including three layers, a first layer with a specific card number ID, a second layer, a direct connection coding or a channel coding, a direct connection coding, a channel coding, a direct connection coding, a channel coding, or a channel coding, a channel.
And if the service is set differently for each quota account, the service is required to perform accounting processing after the quota calling protocol is set before quota utilization accounting is used. If the node is a hierarchy quota, different quotas can be set for nodes in different hierarchies, and the smallest limitation item from a leaf node to a root node is used in billing. For example: the current limit of the withholding channel 3 in the level 3 is 3 thousands, the limit of the bank card withholding payment in the level 2 is 4 thousands, and the current limit of the card number dimension in the level 1 is 5 thousands, when accounting is performed, the minimum limit item (the current limit of the withholding channel 3 in the level 3 is 3 thousands) from the leaf node (the withholding channel 3) to the root node (the card number dimension) is taken as the current limit.
In the accounting process of the embodiment, no matter single accounting or level limit accounting, the service platform only needs to transmit a transaction, and after the transaction includes key fields such as a service access limit platform number, a transaction amount, a limit instance original value and the like, the account limit management system can perform normal accounting. And the accounting is divided into inquiry and accounting after the inquiry and real-time accounting. For the first inquiry and the later accounting, when the page of the service is displayed, the comprehensive minimum sum and data of the account or the level account are inquired to the front end for service control according to the platform number, the original value of the quota instance and the like, and if the quota is enough, the accounting is carried out. And for real-time accounting, directly calling an accounting interface when the service system is limited in use, if the accounting interface is successful, normally ending the accounting, and if the service system is failed, calling an offset interface to carry out offset processing.
If the quota is a single-layer quota, directly inquiring a final set quota calling protocol, wherein if the quota calling protocol is not available, whether public default configuration exists or not can be inquired; and if the quota calling protocol exists, creating final protocol and quota account information.
If it is a level quota, the instance raw value is split according to the separator configured in the protocol (usually # number), and then each level final quota is queried. Inquiring data of the quota account list according to the final quota list; adding transaction amount and stroke number to each account data according to the account list data, wherein the date, the month, the year, the lifetime and the interval need to be increased, meanwhile, the clearing date needs to be updated to be the current date, the updating condition is that the stroke number needing to be controlled is added with 1 and is less than or equal to the limit stroke number, and the sum of the corresponding account amount and the transaction amount is less than or equal to the corresponding limit amount; and meanwhile, updating if the accounting date is more than or equal to the current date or if the accounting date is less than the current date, inserting the account running water into the account flow meter, and carrying out account accumulation zero clearing processing in corresponding daily, monthly, yearly and custom intervals according to whether the clearing time is the same as the accounting time, and simultaneously adding corresponding statistical records. Therefore, if the quota account is a hierarchical account, the service platform only needs to call the accounting once, and the system automatically records the accounting on other hierarchical accounts according to a transaction record, so that the service can conveniently expand the service quota according to the self quota. And after accounting, the statistical treatment is automatically carried out.
If the transaction is reimbursement, the sum and the number of strokes of the transaction are restored only on the premise of successful accounting of the original transaction. FIG. 6 is a flow chart diagram illustrating an account management method according to yet another example embodiment of the present application. As shown in fig. 6, the account management method provided in this embodiment includes:
step 301, acquiring the restriction agreement information sent by the service platform.
Step 302, determining a quota calling protocol according to the restriction agreement information.
And step 303, responding to the account processing request initiated by the service platform according to the quota calling protocol.
It should be noted that, the specific implementation manner of steps 301 to 303 in this embodiment may refer to the description in steps 101 to 103 in the embodiment shown in fig. 3, and is not described again here.
And step 304, acquiring a cancellation request.
And 305, carrying out cancellation processing on the surplus limit corresponding to the account information to be cancelled according to the amount to be cancelled.
The account quota management system acquires an offset request, the offset request comprises account information to be offset and amount to be offset, and offset processing is carried out on the surplus quota corresponding to the account information to be offset according to the amount to be offset.
And when the account processing request is an accounting request, carrying out cancellation processing on the second child node, the root node and all child nodes between the second child node and the root node corresponding to the account information to be cancelled according to the account information to be cancelled and the amount to be cancelled in the accounting request. Therefore, if the quota account is a hierarchical account, the service platform only needs to call the accounting once, and the system automatically records the accounting on other hierarchical accounts according to a transaction record, so that the service can conveniently expand the service quota according to the self quota. And after accounting, the statistical treatment is automatically carried out. If the trade is made, the date, month, year and lifetime of the original trade are returned automatically.
Further, on the basis of any of the above-described embodiments, the account processing record information includes the account processing request type identifier for each account processing request record corresponding to the account processing record information. Therefore, when the data after the accounting needs to be compared with other systems, the data is screened and subjected to the accounting processing through the account processing request type identifier.
Fig. 7 is a schematic structural diagram of an account management apparatus according to an example embodiment. As shown in fig. 7, the account management apparatus 400 according to the present embodiment includes:
an obtaining module 401, configured to obtain restriction agreement information sent by a service platform, where the restriction agreement information includes account information and preset restriction information, and the preset restriction information is used to restrict a limit of the account;
a processing module 402, configured to determine a calling protocol according to the restriction agreement information, so that the account management system responds to an account processing request initiated by the service platform according to the quota calling protocol, where the account processing request is used to change quota information corresponding to the account information in the service platform.
In a possible design, the obtaining module 401 is further configured to obtain a contract modification request sent by the service platform, where the contract modification request includes new restriction agreement information;
the processing module 402 is further configured to update preset restriction information in the calling protocol according to the new restriction agreement information.
In a possible design, the account information is any one of the account information in the service platform, or all the account information in the service platform.
In one possible design, the account processing request includes any one or more of an accounting request, a reimbursement request, and a limit inquiry request.
In a possible design, the obtaining module is further configured to obtain the billing request, where the billing request includes information of an account to be billed and an amount to be billed;
the acquisition module is also used for acquiring the remaining amount corresponding to the account information to be billed;
the account management apparatus 400 further includes:
a sending module 403, configured to send accounting failure information, where the accounting failure information is used to instruct the service platform to stop payment operation;
the sending module 403 is further configured to send accounting success information, where the accounting success information is used to instruct the service platform to continue the payment operation.
In a possible design, the obtaining module 401 is further configured to obtain the offset request, where the offset request includes information of an account to be offset and an amount to be offset;
the processing module 402 is further configured to offset the remaining amount corresponding to the account information to be offset according to the amount of money to be offset.
In one possible design, the invoking protocol includes time range information and restriction information corresponding to the time range information, where the restriction information corresponding to the time range information and the time range information is determined according to the restriction agreement information.
In one possible design, the multiple layers of child nodes form a tree structure, wherein each layer of child nodes includes account information and preset restriction information;
when the account quota management system responds to the account processing request initiated by the service platform according to the quota calling protocol, selecting the minimum preset quota from a first leaf node to a root node in the quota calling protocol as a quota corresponding to the account processing request, wherein the first leaf node is a child node corresponding to the account processing request.
In one possible design, when the account processing request includes an accounting request, accounting processing is performed on a first child node and a root node corresponding to account information to be accounted and all child nodes between the first child node and the root node according to account information to be accounted and an amount to be accounted in the accounting request; or,
and when the account processing request comprises an accounting request, carrying out cancellation processing on a second child node and a root node corresponding to the account information to be cancelled and all child nodes between the second child node and the root node according to the account information to be cancelled and the amount to be cancelled and cancelled in the accounting request.
In one possible design, for each account processing request record, corresponding account processing record information is recorded, and the account processing record information includes an account processing request type identifier.
It should be noted that the account management apparatus provided in the embodiment shown in fig. 7 may be used to execute the account management method provided in any of the above embodiments, and the specific implementation manner and the technical effect are similar and will not be described herein again.
Fig. 8 is a schematic structural diagram of an electronic device shown in the present application according to an example embodiment. As shown in fig. 8, the present embodiment provides an electronic device 500, including:
a processor 501; and the number of the first and second groups,
a memory 502 for storing executable instructions of the processor, which may also be a flash (flash memory);
wherein the processor 501 is configured to perform the steps of the above-described method via execution of the executable instructions. Reference may be made in particular to the description relating to the preceding method embodiment.
Alternatively, the memory 502 may be separate or integrated with the processor 501.
When the memory 502 is a device independent from the processor 501, the electronic device 50 may further include:
a bus 503 for connecting the processor 501 and the memory 502.
The present embodiment also provides a readable storage medium, in which a computer program is stored, and when at least one processor of the electronic device executes the computer program, the electronic device executes the methods provided by the above various embodiments.
The present embodiment also provides a program product comprising a computer program stored in a readable storage medium. The computer program can be read from a readable storage medium by at least one processor of the electronic device, and the execution of the computer program by the at least one processor causes the electronic device to implement the methods provided by the various embodiments described above.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should 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 or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims (13)

1. An account management method is applied to an account management system, and the method comprises the following steps:
acquiring restriction agreement information sent by a service platform, wherein the restriction agreement information comprises account information and preset restriction information, and the preset restriction information is used for restricting the amount of an account;
and determining a calling protocol according to the restriction agreement information so that the account management system responds to an account processing request initiated by the service platform according to the calling protocol, wherein the account processing request is used for changing the quota information corresponding to the account information in the service platform.
2. The account management method of claim 1, further comprising, after the determining to invoke a protocol according to the restriction agreement information:
acquiring a contract modification request sent by the service platform, wherein the contract modification request comprises new restriction agreement information;
and updating preset restriction information in the calling protocol according to the new restriction agreement information.
3. The account management method according to claim 1 or 2, wherein the account information is any account information in the service platform, or all account information in the service platform.
4. The account management method of claim 2, wherein the account processing request comprises any one or more of an accounting request, a reimbursement request, and a quota inquiry request.
5. The account management method of claim 4, further comprising, after said determining a calling protocol according to the restriction agreement information:
acquiring the accounting request, wherein the accounting request comprises account information to be accounted and the amount of money to be accounted;
if a calling protocol corresponding to the account information to be billed exists, acquiring a residual amount corresponding to the account information to be billed;
if the amount to be booked is less than the remaining amount, sending bookkeeping failure information, wherein the bookkeeping failure information is used for indicating the service platform to stop payment operation;
and if the amount to be booked is larger than or equal to the remaining amount, sending bookkeeping success information, wherein the bookkeeping success information is used for indicating the service platform to continue the payment operation.
6. The account management method of claim 4, further comprising, after the sending accounting success information:
acquiring the offset request, wherein the offset request comprises account information to be offset and the amount of the offset to be offset;
and carrying out cancellation processing on the surplus limit corresponding to the account information to be cancelled according to the amount to be cancelled.
7. The account management method according to any one of claims 1, 2 or 4 to 6, wherein the calling protocol comprises time range information and restriction information corresponding to the time range information, wherein the restriction information corresponding to the time range information and the time range information is determined according to the restriction agreement information.
8. The account management method according to any one of claims 1, 2 or 4 to 6, wherein the calling protocol comprises a plurality of layers of sub-nodes, the plurality of layers of sub-nodes form a tree structure, wherein each layer of sub-node comprises account information and preset limit information;
when the account quota management system responds to the account processing request initiated by the service platform according to the calling protocol, selecting the minimum preset quota from a first leaf node to a root node in the calling protocol as a quota corresponding to the account processing request, wherein the first leaf node is a child node corresponding to the account processing request.
9. The account management method according to claim 8, wherein when the account processing request includes an accounting request, accounting processing is performed on a first child node, a root node, and all child nodes between the first child node and the root node corresponding to account information to be accounted according to account information to be accounted and an amount to be accounted in the accounting request; or,
and when the account processing request comprises an accounting request, carrying out cancellation processing on a second child node and a root node corresponding to the account information to be cancelled and all child nodes between the second child node and the root node according to the account information to be cancelled and the amount to be cancelled and cancelled in the accounting request.
10. The account management method according to claim 9, wherein the account processing record information includes an account processing request type identifier for each account processing request record corresponding to the account processing record.
11. An account management apparatus, comprising:
the system comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is used for acquiring restriction agreement information sent by a service platform, the restriction agreement information comprises account information and preset restriction information, and the preset restriction information is used for restricting the amount of an account;
and the processing module is used for determining a calling protocol according to the restriction agreement information so that the account management system responds to an account processing request initiated by the service platform according to the calling protocol, and the account processing request is used for changing the quota information corresponding to the account information in the service platform.
12. An electronic device, comprising:
a processor; and
a memory for storing a computer program for the processor;
wherein the processor is configured to implement the account management method of any one of claims 1 to 10 by executing the computer program.
13. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the account management method of any one of claims 1 to 10.
CN202010186638.4A 2020-03-17 2020-03-17 Account management method and device, storage medium and electronic equipment Active CN111429125B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010186638.4A CN111429125B (en) 2020-03-17 2020-03-17 Account management method and device, storage medium and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010186638.4A CN111429125B (en) 2020-03-17 2020-03-17 Account management method and device, storage medium and electronic equipment

Publications (2)

Publication Number Publication Date
CN111429125A true CN111429125A (en) 2020-07-17
CN111429125B CN111429125B (en) 2024-04-19

Family

ID=71553494

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010186638.4A Active CN111429125B (en) 2020-03-17 2020-03-17 Account management method and device, storage medium and electronic equipment

Country Status (1)

Country Link
CN (1) CN111429125B (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113850577A (en) * 2021-09-24 2021-12-28 支付宝(杭州)信息技术有限公司 Resource account processing method and device

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108038683A (en) * 2017-12-08 2018-05-15 上海壹账通金融科技有限公司 Method of payment, payment system and readable storage medium storing program for executing based on two class accounts
CN108446975A (en) * 2018-03-28 2018-08-24 上海数据交易中心有限公司 A kind of quota control method and device
CN109377270A (en) * 2018-09-29 2019-02-22 湖南共睹互联网科技有限责任公司 Transaction ensures platform and its account management-control method, terminal and readable storage medium storing program for executing
CN110135984A (en) * 2019-04-04 2019-08-16 深圳壹账通智能科技有限公司 Exchange management method, device, computer equipment and storage medium

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108038683A (en) * 2017-12-08 2018-05-15 上海壹账通金融科技有限公司 Method of payment, payment system and readable storage medium storing program for executing based on two class accounts
CN108446975A (en) * 2018-03-28 2018-08-24 上海数据交易中心有限公司 A kind of quota control method and device
CN109377270A (en) * 2018-09-29 2019-02-22 湖南共睹互联网科技有限责任公司 Transaction ensures platform and its account management-control method, terminal and readable storage medium storing program for executing
CN110135984A (en) * 2019-04-04 2019-08-16 深圳壹账通智能科技有限公司 Exchange management method, device, computer equipment and storage medium

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113850577A (en) * 2021-09-24 2021-12-28 支付宝(杭州)信息技术有限公司 Resource account processing method and device

Also Published As

Publication number Publication date
CN111429125B (en) 2024-04-19

Similar Documents

Publication Publication Date Title
CN108427581A (en) System micro services method and terminal device
CN111580874B (en) System safety control method and system for data application and computer equipment
WO2020248883A1 (en) Debt collection method, system and apparatus
CN107862425B (en) Wind control data acquisition method, device and system and readable storage medium
CN110347545A (en) A kind of test method and device of business platform cache policy
CN110309099A (en) Interface managerial method, device, equipment and computer readable storage medium
CN110489139A (en) A kind of real-time data processing method and its relevant device based on micro services
CN110737425A (en) billing platform system application program establishing method and device
CN114282011B (en) Knowledge graph construction method and device, and graph calculation method and device
CN105302556A (en) Calculation realization method and system and server apparatus
CN114625344A (en) Application service generation system and service process configuration method
CN111429125B (en) Account management method and device, storage medium and electronic equipment
CN109857450A (en) A kind of verification service orchestration method and device
CN113268553A (en) Data auditing method, system, electronic equipment and storage medium
CN113360210A (en) Data reconciliation method and device, computer equipment and storage medium
CN110336872B (en) Method, device and system for acquiring third-party data
CN112101889A (en) Metadata-based business flow control method and device
CN110866813A (en) Intelligent accounting system for managing accountants
CN114721945A (en) Graph database-based distribution method and device, electronic equipment and storage medium
CN110971664B (en) Interface service management system
CN114722032A (en) Office automation system, method, computer device and storage medium
CN113592521A (en) Cost data management method, system, computer device and storage medium
CN114448776A (en) Link tracking method and device
CN113076297A (en) Data processing method, device and storage medium
CN112199371B (en) Data migration method, device, computer equipment and storage medium

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
CB02 Change of applicant information

Address after: Room 221, 2 / F, block C, 18 Kechuang 11th Street, Daxing District, Beijing, 100176

Applicant after: Jingdong Technology Holding Co.,Ltd.

Address before: Room 221, 2 / F, block C, 18 Kechuang 11th Street, Daxing District, Beijing, 100176

Applicant before: Jingdong Digital Technology Holding Co.,Ltd.

Address after: Room 221, 2 / F, block C, 18 Kechuang 11th Street, Daxing District, Beijing, 100176

Applicant after: Jingdong Digital Technology Holding Co.,Ltd.

Address before: Room 221, 2 / F, block C, 18 Kechuang 11th Street, Beijing Economic and Technological Development Zone, 100176

Applicant before: JINGDONG DIGITAL TECHNOLOGY HOLDINGS Co.,Ltd.

CB02 Change of applicant information
GR01 Patent grant
GR01 Patent grant