WO2019137202A1 - 业务处理、扣款方法及装置 - Google Patents

业务处理、扣款方法及装置 Download PDF

Info

Publication number
WO2019137202A1
WO2019137202A1 PCT/CN2018/123462 CN2018123462W WO2019137202A1 WO 2019137202 A1 WO2019137202 A1 WO 2019137202A1 CN 2018123462 W CN2018123462 W CN 2018123462W WO 2019137202 A1 WO2019137202 A1 WO 2019137202A1
Authority
WO
WIPO (PCT)
Prior art keywords
account
type
notification message
processing
registered
Prior art date
Application number
PCT/CN2018/123462
Other languages
English (en)
French (fr)
Inventor
陈小虎
Original Assignee
阿里巴巴集团控股有限公司
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 阿里巴巴集团控股有限公司 filed Critical 阿里巴巴集团控股有限公司
Publication of WO2019137202A1 publication Critical patent/WO2019137202A1/zh

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
    • 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

Definitions

  • One or more embodiments of the present disclosure relate to the field of computer technologies, and in particular, to a service processing, a debiting method, and an apparatus.
  • the business system when performing business processing on an account, the business system usually periodically checks the account balance of the account. Specifically, in a certain query process, if the account balance satisfies the condition, the corresponding service processing is performed; otherwise, the above query process is continued until the service processing is successfully performed.
  • One or more embodiments of the present specification describe a service processing, debiting method, and apparatus that can enhance a user experience.
  • a service processing method including:
  • the account system monitors the operations performed by the user for the registered account, which refers to the account corresponding to the business system;
  • the notification message is used to indicate that the service system performs the registration account Corresponding business processing.
  • a service processing method including:
  • the service system receives a notification message sent by the account system, and the notification message is sent by the account system when monitoring that the user performs an operation for the corresponding registered account, and the type of the operation is a target operation type; the notification message includes Registered account;
  • a method of debiting including:
  • the type of the fund processing operation belongs to the fund inflow type, sending a fund change notification message to the debit payment service system, where the fund change notification message includes the registration account; and the fund change notification message is used to indicate The debit service system performs debit processing for the registered account.
  • a service processing apparatus including:
  • a monitoring unit configured to monitor an operation performed by the user on the registered account, where the registered account refers to an account corresponding to the business system;
  • a determining unit configured to determine a type of the operation when the monitoring unit monitors the operation
  • An obtaining unit configured to acquire a business system and a target operation type corresponding to the registered account
  • a determining unit configured to determine whether the type of the operation acquired by the acquiring unit belongs to the target operation type
  • a sending unit configured to: if the determining unit determines that the type of the operation belongs to the target operation type, send a notification message to the service system, where the notification message includes the registration account; the notification message is used to indicate The service system performs corresponding service processing on the registered account.
  • a service processing apparatus including:
  • a receiving unit configured to receive a notification message sent by the account system, where the notification message is sent by the account system when monitoring that the user performs an operation for the corresponding registered account, and the type of the operation is a target operation type;
  • the message includes the registered account;
  • a processing unit configured to perform corresponding service processing on the registered account.
  • a deduction device comprising:
  • a monitoring unit configured to monitor a fund processing operation performed by the user for the registered account, where the registered account refers to an account corresponding to the debit service system;
  • a determining unit configured to determine a type of the fund processing operation when the monitoring unit monitors the fund processing operation
  • An obtaining unit configured to acquire a debit service system corresponding to the registered account and a capital inflow type
  • a determining unit configured to determine whether the type of the capital processing operation belongs to the capital inflow type
  • a sending unit configured to: if the determining unit determines that the type of the fund processing operation belongs to the fund inflow type, send a fund change notification message to the debit payment service system, where the fund change notification message includes the registered account
  • the fund change notification message is used to instruct the debit service system to perform debit processing for the registered account.
  • the account system monitors operations performed by the user for the registered account.
  • the type of the operation is determined. If the type of the operation conforms to the operation type registered in the registered account, the notification message is sent to the business system corresponding to the registered account. After receiving the notification message, the service system performs corresponding service processing on the registered account. Thereby, it is possible to easily perform business processing in the case of cost saving.
  • FIG. 1 is a schematic diagram of an application scenario of a service processing method provided by the present specification
  • FIG. 2 is a flowchart of a service processing method according to an embodiment of the present disclosure
  • FIG. 3 is a flowchart of a service processing method according to another embodiment of the present disclosure.
  • FIG. 5 is a schematic diagram of a service processing apparatus according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic diagram of a service processing apparatus according to another embodiment of the present disclosure.
  • Figure 7 is a schematic view of the deduction device provided in the present specification.
  • the account system and the service system may be in the same local area network or may not be in the same local area network.
  • the communication between the account system and the business system belongs to intranet communication. That is, the communication data can be directly transmitted between the account system and the business system.
  • the communication between the account system and the business system belongs to cross-domain communication. That is, the communication data of both needs to pass through the gateway. For example, when the service system sends communication data to the account system, the communication data is first sent to the gateway. The above communication data is then forwarded by the gateway to the account system.
  • the account system is used to manage accounts for multiple users.
  • the account system is also used to record the correspondence between the registered account, the business system, and the target operation type.
  • the target operation type may refer to a type of operation performed by the user for the corresponding account (eg, a fund processing operation), which may be pre-defined by the account system and selected by the business system according to its own business.
  • the business system is used for corresponding business processing (eg, debits, etc.) for registered accounts in the account system. Specifically, it can register an account by sending a registration request to the account system. After the registration is successful, the above correspondence is recorded in the account system.
  • the account system can monitor the actions performed by the user for the registered account.
  • the type of the operation is determined. If the type of the operation conforms to the operation type registered in the registered account, the notification message is sent to the business system corresponding to the registered account. After receiving the notification message, the service system performs corresponding service processing on the registered account.
  • FIG. 2 is a flowchart of a service processing method according to an embodiment of the present disclosure.
  • the executive body of the method can be a device with processing capabilities: a server or system or device, such as the account system of FIG. As shown in FIG. 2, the method may specifically include:
  • step 210 the account system monitors the operations performed by the user for the registered account.
  • the above registered account may refer to an account corresponding to the business system.
  • the business system can send a registration request to the account system, which can include the account to be registered and the type of target operation.
  • the target operation type may be selected by the business system from a plurality of preset operation types according to its own business.
  • the preset operation type may be preset by the account system and notified to the business system. For example, assume that the default types of operations include: capital inflows, capital outflows, capital freezes, and funds thawing.
  • the target operation type that can be selected is the capital inflow type.
  • the account system may record the correspondence between the business system, the registered account, and the target operation type, and return a successful registration message to the business system.
  • the correspondence may be recorded in a registry as shown in Table 1.
  • Step 220 When the operation is monitored, the type of the operation is determined.
  • types of operations include, but are not limited to, capital inflows, capital outflows, capital freezes, and funds thawing.
  • the above types are pre-set by the account system.
  • the type of operation can be determined based on changes in the account balance.
  • the account system can compare the account balances of the registered accounts before and after the operation to determine the changes. Changes here include, but are limited to, increased account balances and reduced account balances. For example, when the account balance of the registered account increases, it can be determined that the type of the current operation is the capital inflow type.
  • Step 230 Obtain a business system corresponding to the registered account and a target operation type.
  • the acquired business system and the target operation type may be: the business system 1 and the capital inflow type, respectively.
  • step 240 it is determined whether the type of the operation belongs to the target operation type.
  • Step 250 If the type of the operation belongs to the target operation type, send a notification message to the service system.
  • the account system can directly send the above notification message to the business system. If the account system is not in the same local area network as the service system, the account system first sends the notification message to the gateway. The notification message is then sent by the gateway to the payment service system.
  • the above notification message may include a registered account.
  • the notification message may also include information such as account balance.
  • the account system can send a fund change notification message to the business system.
  • the service system may perform corresponding service processing (eg, deduction, etc.) for the registered account.
  • the service system may perform corresponding service processing across domains, or may perform corresponding service processing within the network.
  • the account system can perform normal processing in addition to the above notification message to the service system, for example, the accounting account is processed, and the description is not described in this specification.
  • the above notification message is sent if the account system determines that the type of operation belongs to the target operation type. When it does not belong, the account system does not send the above notification message, and only performs normal processing, such as fund transfer processing.
  • the service processing is completed by the cooperation of the service system and the account system, that is, the account system notifies the service system to perform the corresponding operation after monitoring that the user performs the operation according to the registration type for the registered account.
  • Business processing That is, the service system no longer actively initiates polling queries, but passively waits for notifications to perform business processing. This can reduce system cost and enhance user experience.
  • the debit business system does not actively deduct the payment, but has been waiting for the user to have the funds of the registration type.
  • the account system will add an additional action in addition to the account to inform the deduction business.
  • the debit payment service system will initiate the deduction action after receiving the message, and complete the deduction. That is, the above embodiment of the present specification associates the operation performed by the user on the registered account with the business process performed by the business system for the registered account, thereby more in line with the actual process.
  • FIG. 3 is a flowchart of a service processing method according to another embodiment of the present disclosure.
  • the execution body of the method may be a device having processing capabilities: a server or a system or device, such as the business system in FIG. As shown in FIG. 3, the method may specifically include:
  • Step 310 The service system receives the notification message sent by the account system.
  • the account system can monitor the actions performed by the user for the registered account.
  • the registered account here may refer to an account in which the account system records the corresponding business system and the target operation type in the registry.
  • the account system can obtain the corresponding target operation type from the above registry. If the type of the operation conforms to the target operation type, the notification message is sent to the corresponding service system.
  • the notification message can include a registered account.
  • information such as the account balance of the registered account may also be included.
  • Step 320 Perform corresponding business processing on the registered account.
  • the debit business system can perform debit processing for the registered account.
  • the debit payment service system performs a plurality of preset fund operation types (including but not limited to capital inflow according to the debit payment service).
  • the type of capital inflow is selected in the outflow of funds, the freezing of funds, and the thawing of funds.
  • a registration request is sent to the account system across domains or networks.
  • the registration request may include: an account to be registered and a type of capital inflow.
  • the account system records the corresponding relationship between the debit business system, the registered account, and the capital inflow type in the registry. After that, the account system returns a successful registration message to the debit payment service system across the domain or the network. After performing the steps of completing the above registration account, the following steps can be performed.
  • Step 410 Monitor the funds processing operation performed by the user for the account.
  • step 420 the account is a registered account. If not, step 430 is performed; if yes, step 440 is performed.
  • step 430 corresponding funds are processed for the account.
  • Step 440 determining the type of the capital processing operation.
  • Step 450 Obtain a debit service system and a fund inflow type corresponding to the registered account from the registry.
  • step 460 it is determined whether the type of the fund processing operation belongs to the capital inflow type. If not, step 470 is performed; if yes, step 480 is performed.
  • Step 470 the corresponding account processing is performed on the registered account.
  • Step 480 performing accounting processing on the registered account, and triggering a corresponding message sending event.
  • the fund change notification message may be sent to the corresponding debit payment service system.
  • the account system can directly send the above fund change notification message to the debit payment service system. If the account system and the debit service system are not in the same local area network, the account system first sends the fund change notification message to the gateway. Thereafter, the fund change notification message is sent by the gateway to the debit service system.
  • step 490 the debit service system triggers a chargeback event.
  • the debit payment service system After the chargeback event is triggered here, the debit payment service system initiates a deduction for the registered account in the account system across the domain, or initiates a charge within the network.
  • step 4100 the account system returns a message of successful deduction to the debit payment service system.
  • the deduction method provided by the above embodiment of the present specification does not repeatedly call the deduction, and only one deduction is required, which is a triggering scheme. That is, the debit business system and the account system cooperate, and when the account has funds flowing in, the information is notified to the debit business system, and the debit business system only comes to deduct the payment.
  • the biggest advantage of this method is that the system is single-time at an appropriate time. Make a deduction. This can solve the problem of multiplying the system cost as the user increases.
  • the user can basically deduct the money in the second step of the funds, thereby greatly improving the user experience.
  • an embodiment of the present specification further provides a service processing apparatus, as shown in FIG. 5, the apparatus includes:
  • the monitoring unit 501 is configured to monitor an operation performed by the user for the registered account, and the registered account refers to an account corresponding to the business system.
  • the determining unit 502 is configured to determine the type of the operation when the monitoring unit 501 monitors the operation.
  • the determining unit 502 is specifically configured to:
  • the obtaining unit 503 is configured to obtain a business system corresponding to the registered account and a target operation type.
  • the determining unit 504 is configured to determine whether the type of the operation acquired by the obtaining unit 503 belongs to the target operation type.
  • the sending unit 505 is configured to: if the determining unit 504 determines that the type of the operation belongs to the target operation type, send a notification message to the service system, where the notification message includes a registration account; and the notification message is used to instruct the service system to perform corresponding service processing on the registered account.
  • the device may further include:
  • the receiving unit 506 is configured to receive a registration request sent by the service system, where the registration request includes a registration account and a target operation type.
  • the recording unit 507 is configured to record a correspondence between the service system, the registration account, and the target operation type.
  • the sending unit 505 is further configured to return a message that the registration is successful to the service system.
  • the obtaining unit 503 can be specifically configured to:
  • the business system and the operation type corresponding to the registered account are obtained.
  • the monitoring unit 501 monitors an operation performed by the user for the registered account.
  • the determining unit 502 determines the type of the operation.
  • the obtaining unit 503 acquires the business system corresponding to the registered account and the target operation type.
  • the judging unit 504 judges whether the type of the operation belongs to the target operation type. If the type of operation belongs to the target operation type, the transmitting unit 505 transmits a notification message to the service system, the notification message including the registered account.
  • the notification message is used to instruct the business system to perform corresponding business processing for the registered account. Thereby, it is possible to easily perform business processing in the case of cost saving.
  • the foregoing service processing apparatus may be a module or unit in the account system shown in FIG. 1.
  • an embodiment of the present specification further provides a service processing apparatus, as shown in FIG. 6, the apparatus includes:
  • the receiving unit 601 is configured to receive a notification message sent by the account system, where the notification message is sent by the account system when monitoring that the user performs an operation for the corresponding registered account, and the type of the operation is the target operation type.
  • the notification message can include a registered account.
  • the processing unit 602 is configured to perform corresponding service processing on the registered account.
  • the device may further include:
  • the selecting unit 603 is configured to select a target operation type from a plurality of preset operation types.
  • the sending unit 604 is configured to send a registration request to the account system, where the registration request includes a registration account and a target operation type.
  • the registration request is used to instruct the account system to record the correspondence between the business system, the registered account, and the target operation type.
  • the receiving unit 601 is further configured to receive a message that the registration returned by the account system is successful.
  • the foregoing service processing apparatus may be a module or unit in the service system shown in FIG. 1.
  • an embodiment of the present disclosure further provides a deduction device, as shown in FIG. 7, the device includes:
  • the monitoring unit 701 is configured to monitor a fund processing operation performed by the user for the registered account, where the registered account refers to an account corresponding to the debit service system.
  • the determining unit 702 is configured to determine the type of the fund processing operation when the monitoring unit 701 monitors the fund processing operation.
  • the types of capital processing operations may include: capital inflows, capital outflows, capital freezes, and thawing of funds.
  • the obtaining unit 703 is configured to obtain a debit service system corresponding to the registered account and a capital inflow type.
  • the determining unit 704 is configured to determine whether the type of the capital processing operation belongs to the capital inflow type.
  • the sending unit 705 is configured to: if the determining unit 704 determines that the type of the fund processing operation belongs to the fund inflow type, send a fund change notification message to the debit payment service system, where the fund change notification message includes the registered account.
  • the fund change notification message is used to indicate that the debit payment service system performs debit processing for the registered account.
  • the above-mentioned debit device may be a module or unit in the aforementioned debit service system.
  • the functions described in this specification can be implemented in hardware, software, firmware, or any combination thereof.
  • the functions may be stored in a computer readable medium or transmitted as one or more instructions or code on a computer readable medium.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • Development Economics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Marketing (AREA)
  • Technology Law (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

一种业务处理、扣款方法及装置，在业务处理方法中，账户系统监控用户针对注册账户执行的操作（S210）；当监控到操作时，确定该操作的类型（S220）；获取所述注册账户对应的业务系统及目标操作类型（S230）；判断所述操作的类型是否属于所述目标操作类型（S240）；若操作的类型属于所述目标操作类型，则向所述业务系统发送通知消息（S250）。业务系统在接收到该通知消息之后，针对注册账户进行相应的业务处理。

Description

业务处理、扣款方法及装置 技术领域
本说明书一个或多个实施例涉及计算机技术领域，尤其涉及一种业务处理、扣款方法及装置。
背景技术
传统技术中，在针对账户进行业务处理时，业务系统通常会周期性查询该账户的账户余额。具体地，在某次查询过程中，如果账户余额满足条件，则进行相应的业务处理；否则继续上述查询过程，直至成功进行业务处理。
因此，需要提供一种能节约成本且更简单地业务处理的方案。
发明内容
本说明书一个或多个实施例描述了一种业务处理、扣款方法及装置，可以提升用户体验。
第一方面，提供了一种业务处理方法，包括：
账户系统监控用户针对注册账户执行的操作，所述注册账户是指与业务系统相对应的账户；
当监控到所述操作时，确定所述操作的类型；
获取所述注册账户对应的业务系统及目标操作类型；
判断所述操作的类型是否属于所述目标操作类型；
若所述操作的类型属于所述目标操作类型，则向所述业务系统发送通知消息，所述通知消息包括所述注册账户；所述通知消息用于指示所述业务系统针对所述注册账户进行相应的业务处理。
第二方面，提供了一种业务处理方法，包括：
业务系统接收账户系统发送的通知消息，所述通知消息是由账户系统在监控到用户针对对应的注册账户执行操作，且所述操作的类型为目标操作类型时发送的；所述通知消息包括所述注册账户；
对所述注册账户进行相应的业务处理。
第三方面，提供了一种扣款方法，包括：
监控用户针对注册账户执行的资金处理操作，所述注册账户是指与扣款业务系统相对应的账户；
当监控到所述资金处理操作时，确定所述资金处理操作的类型；
获取所述注册账户对应的扣款业务系统及资金流入类型；
判断所述资金处理操作的类型是否属于所述资金流入类型；
若所述资金处理操作的类型属于所述资金流入类型，则向所述扣款业务系统发送资金变动通知消息，所述资金变动通知消息包括所述注册账户；所述资金变动通知消息用于指示所述扣款业务系统针对所述注册账户进行扣款处理。
第四方面，提供了一种业务处理装置，包括：
监控单元，用于监控用户针对注册账户执行的操作，所述注册账户是指与业务系统相对应的账户；
确定单元，用于当所述监控单元监控到所述操作时，确定所述操作的类型；
获取单元，用于获取所述注册账户对应的业务系统及目标操作类型；
判断单元，用于判断所述获取单元获取的所述操作的类型是否属于所述目标操作类型；
发送单元，用于若所述判断单元判断所述操作的类型属于所述目标操作类型，则向所述业务系统发送通知消息，所述通知消息包括所述注册账户；所述通知消息用于指示所述业务系统针对所述注册账户进行相应的业务处理。
第五方面，提供了一种业务处理装置，包括：
接收单元，用于接收账户系统发送的通知消息，所述通知消息是由账户系统在监控到用户针对对应的注册账户执行操作，且所述操作的类型为目标操作类型时发送的；所述通知消息包括所述注册账户；
处理单元，用于对所述注册账户进行相应的业务处理。
第六方面，提供了一种扣款装置，包括：
监控单元，用于监控用户针对注册账户执行的资金处理操作，所述注册账户是指与 扣款业务系统相对应的账户；
确定单元，用于当所述监控单元监控到所述资金处理操作时，确定所述资金处理操作的类型；
获取单元，用于获取所述注册账户对应的扣款业务系统及资金流入类型；
判断单元，用于判断所述资金处理操作的类型是否属于所述资金流入类型；
发送单元，用于若所述判断单元判断所述资金处理操作的类型属于所述资金流入类型，则向所述扣款业务系统发送资金变动通知消息，所述资金变动通知消息包括所述注册账户；所述资金变动通知消息用于指示所述扣款业务系统针对所述注册账户进行扣款处理。
本说明书一个或多个实施例提供的业务处理、扣款方法及装置，账户系统监控用户针对注册账户执行的操作。当监控到操作时，确定该操作的类型。若该操作的类型符合注册账户预先注册的操作类型，则向注册账户对应的业务系统发送通知消息。业务系统在接收到该通知消息之后，针对注册账户进行相应的业务处理。由此，可以实现在节约成本的情况下，简单地进行业务处理。
附图说明
为了更清楚地说明本说明书实施例的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本说明书的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。
图1为本说明书提供的业务处理方法的应用场景示意图；
图2为本说明书一个实施例提供的业务处理方法流程图；
图3为本说明书另一个实施例提供的业务处理方法流程图；
图4为本说明书提供的扣款方法的信息交互图；
图5为本说明书一个实施例提供的业务处理装置示意图；
图6为本说明书另一个实施例提供的业务处理装置示意图；
图7为本说明书提供的扣款装置示意图。
具体实施方式
下面结合附图，对本说明书提供的方案进行描述。
本说明书提供的业务处理方法可以应用于如图1所示的场景中，图1中，账户系统与业务系统可以在同一局域网内，也可以不在同一局域网内。当在同一局域网内时，账户系统与业务系统之间的通信属于网内通信。也即账户系统与业务系统之间可以直接传输通信数据。当不在同一局域网内时，账户系统与业务系统之间的通信属于跨域通信。也即两者的通信数据需要经过网关。如，在业务系统向账户系统发送通信数据时，先将该通信数据发送至网关。之后由网关将上述通讯数据转发至账户系统。
图1中，账户系统用于管理多个用户的账户。当某个账户为注册账户时，账户系统还用于记录该注册账户、业务系统以及目标操作类型的对应关系。其中，目标操作类型可以是指用户针对对应的账户所执行操作(如，资金处理操作)的类型，其可以是由账户系统预先定义好并由业务系统根据自身业务所选取的。业务系统用于针对账户系统中的注册账户进行相应的业务处理(如，扣款等)。其具体可以通过向账户系统发送注册请求来注册某个账户。在注册成功后，账户系统中就会记录上述对应关系。
具体地，账户系统可以监控用户针对注册账户执行的操作。当监控到操作时，确定该操作的类型。若该操作的类型符合注册账户预先注册的操作类型，则向注册账户对应的业务系统发送通知消息。业务系统在接收到该通知消息之后，针对注册账户进行相应的业务处理。
图2为本说明书一个实施例提供的业务处理方法流程图。所述方法的执行主体可以为具有处理能力的设备：服务器或者系统或者装置，如，图1中的账户系统。如图2所示，所述方法具体可以包括：
步骤210，账户系统监控用户针对注册账户执行的操作。
上述注册账户可以是指与业务系统相对应的账户。在一种实现方式中，业务系统可以向账户系统发送注册请求，该注册请求可以包括待注册账户以及目标操作类型。该目标操作类型可以是由业务系统根据其自身业务，从多个预设的操作类型中选取的。此处，预设的操作类型可以是由账户系统预先设定好并通知给业务系统的。举例来说，假设预设的操作类型包括：资金流入、资金流出、资金冻结以及资金解冻。当业务系统自身业务为扣款业务时，因为扣款需要账户有钱，所以可以选取的目标操作类型为资金流入类型。
账户系统在接收到上述注册请求之后，可以记录业务系统、注册账户以及目标操作类型的对应关系，并向业务系统返回注册成功的消息。在一种实现方式中，可以在如表1所示的注册表中记录该对应关系。
表1
注册账户 业务系统 目标操作类型
账户名称1 业务系统1 资金流入
账户名称2 业务系统2 资金流出
账户名称3 业务系统3 资金冻结
账户名称4 业务系统4 资金解冻
... ... ...
步骤220，当监控到操作时，确定该操作的类型。
此处，操作的类型包括但不限于资金流入、资金流出、资金冻结以及资金解冻等。在一个例子中，上述类型是由账户系统预先设定好的。
在一种实现方式中，可以根据账户余额的变动情况，来确定该操作的类型。具体地，账户系统可以将操作执行前后注册账户的账户余额进行比较，来确定其变动情况。此处的变动情况包括但限于账户余额增多以及账户余额减少等。举例来说，当注册账户的账户余额增多时，可以确定当前操作的类型为资金流入类型。
步骤230，获取注册账户对应的业务系统及目标操作类型。
如表1所示，当注册账户为账户名称1时，获取的业务系统及目标操作类型分别可以为：业务系统1和资金流入类型。
步骤240，判断操作的类型是否属于目标操作类型。
步骤250，若操作的类型属于目标操作类型，则向业务系统发送通知消息。
可以理解的是，如果上述账户系统与业务系统在同一局域网内，比如，同属于支付宝平台中的模块。则账户系统可以直接向业务系统发送上述通知消息。而如果上述账户系统与业务系统不在同一局域网内，则账户系统先将该通知消息发送给网关。之后，由网关将该通知消息发送给款业务系统。
上述通知消息可以包括注册账户。此外，该通知消息还可以包括账户余额等信息。
举例来说，若操作的类型和目标操作类型均为资金流入类型，则账户系统可以向业 务系统发送资金变动通知消息。业务系统在接收到该通知消息之后，可以针对该注册账户进行相应的业务处理(如，扣款等)。同理，业务系统可以是跨域进行相应的业务处理，也可以是在网内进行相应的业务处理。
当然，在实际应用中，账户系统除了向业务系统发送上述通知消息之外，还可以进行正常处理，如，对注册账户进行入账处理等，本说明书对此不复赘述。
可以理解的是，上述通知消息是在账户系统判断操作的类型属于目标操作类型的情况下发送的。当不属于时，账户系统不发送上述通知消息，只进行正常处理，如，资金转移处理等。
综上，本说明书上述实施例中，业务处理是在业务系统和账户系统相互配合下完成的，即账户系统在监控到用户针对注册账户执行了符合注册类型的操作之后，才通知业务系统进行相应的业务处理。也即业务系统不再主动发起轮询式查询，而是被动等待通知进行业务处理。从而既可以减低系统成本，又能提升用户体验。
如，若注册账户需要扣款，扣款业务系统并不主动扣款，而是一直等待用户有符合注册类型的资金操作时，账户系统除了入账之外还会增加额外一个动作就是通知扣款业务系统用户资金到位，扣款业务系统收到消息才会发起扣款动作，完成扣款行为。也即本说明书上述实施例将用户对注册账户执行的操作与业务系统针对注册账户进行的业务处理相关联，从而更符合实际流程。
图3为本说明书另一个实施例提供的业务处理方法流程图。所述方法的执行主体可以为具有处理能力的设备：服务器或者系统或者装置，如，图1中的业务系统。如图3所示，所述方法具体可以包括：
步骤310，业务系统接收账户系统发送的通知消息。
具体地，账户系统可以监控用户针对注册账户执行的操作。此处的注册账户可以是指账户系统在注册表中记录了对应的业务系统及目标操作类型的账户。在监控到上述操作时，账户系统可以从上述注册表中获取对应的目标操作类型。若该操作的类型符合目标操作类型，则向对应的业务系统发送上述通知消息。
该通知消息可以包括注册账户。此外，还可以包括该注册账户的账户余额等信息。
步骤320，对注册账户进行相应的业务处理。
以业务系统为扣款业务系统为例来说，扣款业务系统可以针对注册账户进行扣款处 理。
下面结合图4，以业务系统为扣款业务系统，业务处理为扣款处理为例，对本说明书给出的方案作进一步详细描述：
需要说明的是，在执行图4所示的各步骤之前，可以先执行如下注册账户的步骤：扣款业务系统根据扣款业务，从多个预设的资金操作类型(包括但不限于资金流入、资金流出、资金冻结以及资金解冻等)中选取资金流入类型。跨域或者网内向账户系统发送注册请求。该注册请求可以包括：待注册账户以及资金流入类型。账户系统在注册表中，记录扣款业务系统、注册账户以及资金流入类型的对应关系。之后，账户系统跨域或者网内向扣款业务系统返回注册成功的消息。在执行完成上述注册账户的步骤之后，就可以执行如下步骤了。
步骤410，监控用户针对账户执行的资金处理操作。
步骤420，该账户是否为注册账户，如果否，则执行步骤430；如果是，则执行步骤440。
步骤430，对该账户进行相应的资金处理。
步骤440，确定该资金处理操作的类型。
步骤450，从注册表中获取该注册账户对应的扣款业务系统和资金流入类型。
步骤460，判断该资金处理操作的类型是否属于资金流入类型，如果否，则执行步骤470；如果是，则执行步骤480。
步骤470，对该注册账户进行相应的资金处理。
步骤480，对该注册账户进行入账处理，并触发相应的消息发送事件。
此处的消息发送事件被触发后，可以向对应的扣款业务系统发送资金变动通知消息。
可以理解的是，如果上述账户系统与扣款业务系统在同一局域网内，比如，同属于支付宝平台中的模块。则在消息发送事件被触发后，账户系统可以直接向扣款业务系统发送上述资金变动通知消息。而如果上述账户系统与扣款业务系统不在同一局域网内，则账户系统先将该资金变动通知消息发送给网关。之后，由网关将该资金变动通知消息发送给扣款业务系统。
步骤490，扣款业务系统触发扣款事件。
此处的扣款事件被触发后，扣款业务系统跨域针对账户系统中的注册账户发起扣款，或者在网内发起扣款。
步骤4100，账户系统向扣款业务系统返回扣款成功的消息。
综上，本说明书上述实施例提供的扣款方法不会再有多次调用扣款，只需做到一次扣款，是一种触发式的方案。也就是扣款业务系统和账户系统配合，在账户有资金流入的时候辐射消息通知扣款业务系统，扣款业务系统才过来扣款，这种做法最大的好处是在适当的时候单次对系统进行扣款。由此能解决系统成本随着用户增加而带来的成倍增加的问题。此外，通过上述扣款方法，用户基本可以在资金入账秒级扣除款项，由此可以极大地提升用户体验。
与上述业务处理方法对应地，本说明书一个实施例还提供的一种业务处理装置，如图5所示，该装置包括：
监控单元501，用于监控用户针对注册账户执行的操作，注册账户是指与业务系统相对应的账户。
确定单元502，用于当监控单元501监控到操作时，确定该操作的类型。
可选地，确定单元502具体可以用于：
确定注册账户的账户余额的变动情况。
根据账户余额的变动情况，确定操作的类型。
获取单元503，用于获取注册账户对应的业务系统及目标操作类型。
判断单元504，用于判断获取单元503获取的操作的类型是否属于目标操作类型。
发送单元505，用于若判断单元504判断操作的类型属于目标操作类型，则向业务系统发送通知消息，该通知消息包括注册账户；通知消息用于指示业务系统针对注册账户进行相应的业务处理。
可选地，该装置还可以包括：
接收单元506，用于接收业务系统发送的注册请求，该注册请求包括注册账户以及目标操作类型。
记录单元507，用于记录业务系统、注册账户以及目标操作类型的对应关系。
发送单元505，还用于向业务系统返回注册成功的消息。
获取单元503具体可以用于：
根据对应关系，获取注册账户对应的业务系统及操作类型。
本说明书上述实施例装置的各功能模块的功能，可以通过上述方法实施例的各步骤来实现，因此，本说明书一个实施例提供的装置的具体工作过程，在此不复赘述。
本说明书一个实施例提供的业务处理装置，监控单元501监控用户针对注册账户执行的操作。当监控到操作时，确定单元502确定该操作的类型。获取单元503获取注册账户对应的业务系统及目标操作类型。判断单元504判断操作的类型是否属于目标操作类型。若操作的类型属于目标操作类型，发送单元505向业务系统发送通知消息，该通知消息包括注册账户。通知消息用于指示业务系统针对注册账户进行相应的业务处理。由此，可以实现在节约成本的情况下，简单地进行业务处理。
需要说明的是，上述业务处理装置可以为图1所示的账户系统中的一个模块或者单元。
与上述业务处理方法对应地，本说明书一个实施例还提供的一种业务处理装置，如图6所示，该装置包括：
接收单元601，用于接收账户系统发送的通知消息，该通知消息是由账户系统在监控到用户针对对应的注册账户执行操作，且该操作的类型为目标操作类型时发送的。该通知消息可以包括注册账户。
处理单元602，用于对注册账户进行相应的业务处理。
可选地，该装置还可以包括：
选取单元603，用于从多个预设的操作类型中选取目标操作类型。
发送单元604，用于向账户系统发送注册请求，该注册请求包括注册账户和目标操作类型。该注册请求用于指示账户系统记录业务系统、注册账户以及目标操作类型的对应关系。
接收单元601，还用于接收账户系统返回的注册成功的消息。
本说明书上述实施例装置的各功能模块的功能，可以通过上述方法实施例的各步骤来实现，因此，本说明书一个实施例提供的装置的具体工作过程，在此不复赘述。
需要说明的是，上述业务处理装置可以为图1所示的业务系统中的一个模块或者单元。
与上述扣款方法对应地，本说明书一个实施例还提供的一种扣款装置，如图7所示，该装置包括：
监控单元701，用于监控用户针对注册账户执行的资金处理操作，注册账户是指与扣款业务系统相对应的账户。
确定单元702，用于当监控单元701监控到资金处理操作时，确定资金处理操作的类型。
其中，资金处理操作的类型可以包括：资金流入、资金流出、资金冻结以及资金解冻等。
获取单元703，用于获取注册账户对应的扣款业务系统及资金流入类型。
判断单元704，用于判断资金处理操作的类型是否属于资金流入类型。
发送单元705，用于若判断单元704判断资金处理操作的类型属于资金流入类型，则向扣款业务系统发送资金变动通知消息，资金变动通知消息包括注册账户。资金变动通知消息用于指示扣款业务系统针对注册账户进行扣款处理。
本说明书上述实施例装置的各功能模块的功能，可以通过上述方法实施例的各步骤来实现，因此，本说明书一个实施例提供的装置的具体工作过程，在此不复赘述。
需要说明的是，上述扣款装置可以为前述扣款业务系统中的一个模块或者单元。
本领域技术人员应该可以意识到，在上述一个或多个示例中，本说明书所描述的功能可以用硬件、软件、固件或它们的任意组合来实现。当使用软件实现时，可以将这些功能存储在计算机可读介质中或者作为计算机可读介质上的一个或多个指令或代码进行传输。
以上所述的具体实施方式，对本说明书的目的、技术方案和有益效果进行了进一步详细说明，所应理解的是，以上所述仅为本说明书的具体实施方式而已，并不用于限定本说明书的保护范围，凡在本说明书的技术方案的基础之上，所做的任何修改、等同替换、改进等，均应包括在本说明书的保护范围之内

Claims (14)

  1. 一种业务处理方法，其特征在于，包括：
    账户系统监控用户针对注册账户执行的操作，所述注册账户是指与业务系统相对应的账户；
    当监控到所述操作时，确定所述操作的类型；
    获取所述注册账户对应的业务系统及目标操作类型；
    判断所述操作的类型是否属于所述目标操作类型；
    若所述操作的类型属于所述目标操作类型，则向所述业务系统发送通知消息，所述通知消息包括所述注册账户；所述通知消息用于指示所述业务系统针对所述注册账户进行相应的业务处理。
  2. 根据权利要求1所述的方法，其特征在于，在所述监控用户针对注册账户执行的操作之前，还包括：
    接收所述业务系统发送的注册请求，所述注册请求包括所述注册账户以及所述目标操作类型；
    记录所述业务系统、所述注册账户以及所述目标操作类型的对应关系；
    向所述业务系统返回注册成功的消息；
    所述获取所述注册账户对应的业务系统及目标操作类型，包括：
    根据所述对应关系，获取所述注册账户对应的业务系统及目标操作类型。
  3. 根据权利要求1或2所述的方法，其特征在于，所述确定所述操作的类型，包括：
    确定所述注册账户的账户余额的变动情况；
    根据所述账户余额的变动情况，确定所述操作的类型。
  4. 一种业务处理方法，其特征在于，包括：
    业务系统接收账户系统发送的通知消息，所述通知消息是由账户系统在监控到用户针对对应的注册账户执行操作，且所述操作的类型为目标操作类型时发送的；所述通知消息包括所述注册账户；
    对所述注册账户进行相应的业务处理。
  5. 根据权利要求4所述的方法，其特征在于，在所述接收账户系统发送的通知消息之前，还包括：
    从多个预设的操作类型中选取所述目标操作类型；
    向所述账户系统发送注册请求，所述注册请求包括所述注册账户和所述目标操作类 型；所述注册请求用于指示所述账户系统记录所述业务系统、所述注册账户以及所述目标操作类型的对应关系；
    接收所述账户系统返回的注册成功的消息。
  6. 一种扣款方法，其特征在于，包括：
    监控用户针对注册账户执行的资金处理操作，所述注册账户是指与扣款业务系统相对应的账户；
    当监控到所述资金处理操作时，确定所述资金处理操作的类型；
    获取所述注册账户对应的扣款业务系统及资金流入类型；
    判断所述资金处理操作的类型是否属于所述资金流入类型；
    若所述资金处理操作的类型属于所述资金流入类型，则向所述扣款业务系统发送资金变动通知消息，所述资金变动通知消息包括所述注册账户；所述资金变动通知消息用于指示所述扣款业务系统针对所述注册账户进行扣款处理。
  7. 根据权利要求6所述的方法，其特征在于，所述资金处理操作的类型包括：资金流入、资金流出、资金冻结以及资金解冻。
  8. 一种业务处理装置，其特征在于，包括：
    监控单元，用于监控用户针对注册账户执行的操作，所述注册账户是指与业务系统相对应的账户；
    确定单元，用于当所述监控单元监控到所述操作时，确定所述操作的类型；
    获取单元，用于获取所述注册账户对应的业务系统及目标操作类型；
    判断单元，用于判断所述获取单元获取的所述操作的类型是否属于所述目标操作类型；
    发送单元，用于若所述判断单元判断所述操作的类型属于所述目标操作类型，则向所述业务系统发送通知消息，所述通知消息包括所述注册账户；所述通知消息用于指示所述业务系统针对所述注册账户进行相应的业务处理。
  9. 根据权利要求8所述的装置，其特征在于，还包括：
    接收单元，用于接收所述业务系统发送的注册请求，所述注册请求包括所述注册账户以及所述目标操作类型；
    记录单元，用于记录所述业务系统、所述注册账户以及所述目标操作类型的对应关系；
    所述发送单元，还用于向所述业务系统返回注册成功的消息；
    所述获取单元具体用于：
    根据所述对应关系，获取所述注册账户对应的业务系统及目标操作类型。
  10. 根据权利要求8或9所述的装置，其特征在于，所述确定单元具体用于：
    确定所述注册账户的账户余额的变动情况；
    根据所述账户余额的变动情况，确定所述操作的类型。
  11. 一种业务处理装置，其特征在于，包括：
    接收单元，用于接收账户系统发送的通知消息，所述通知消息是由账户系统在监控到用户针对对应的注册账户执行操作，且所述操作的类型为目标操作类型时发送的；所述通知消息包括所述注册账户；
    处理单元，用于对所述注册账户进行相应的业务处理。
  12. 根据权利要求11所述的装置，其特征在于，还包括：
    选取单元，用于从多个预设的操作类型中选取所述目标操作类型；
    发送单元，用于向所述账户系统发送注册请求，所述注册请求包括所述注册账户和所述目标操作类型；所述注册请求用于指示所述账户系统记录业务系统、所述注册账户以及所述目标操作类型的对应关系；
    所述接收单元，还用于接收所述账户系统返回的注册成功的消息。
  13. 一种扣款装置，其特征在于，包括：
    监控单元，用于监控用户针对注册账户执行的资金处理操作，所述注册账户是指与扣款业务系统相对应的账户；
    确定单元，用于当所述监控单元监控到所述资金处理操作时，确定所述资金处理操作的类型；
    获取单元，用于获取所述注册账户对应的扣款业务系统及资金流入类型；
    判断单元，用于判断所述资金处理操作的类型是否属于所述资金流入类型；
    发送单元，用于若所述判断单元判断所述资金处理操作的类型属于所述资金流入类型，则向所述扣款业务系统发送资金变动通知消息，所述资金变动通知消息包括所述注册账户；所述资金变动通知消息用于指示所述扣款业务系统针对所述注册账户进行扣款处理。
  14. 根据权利要求13所述的装置，其特征在于，所述资金处理操作的类型包括：资金流入、资金流出、资金冻结以及资金解冻。
PCT/CN2018/123462 2018-01-09 2018-12-25 业务处理、扣款方法及装置 WO2019137202A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810019653.2 2018-01-09
CN201810019653.2A CN108335192B (zh) 2018-01-09 2018-01-09 业务处理、扣款方法及装置

Publications (1)

Publication Number Publication Date
WO2019137202A1 true WO2019137202A1 (zh) 2019-07-18

Family

ID=62923847

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/123462 WO2019137202A1 (zh) 2018-01-09 2018-12-25 业务处理、扣款方法及装置

Country Status (3)

Country Link
CN (1) CN108335192B (zh)
TW (1) TW201931114A (zh)
WO (1) WO2019137202A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108335192B (zh) * 2018-01-09 2020-07-28 阿里巴巴集团控股有限公司 业务处理、扣款方法及装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104166935A (zh) * 2014-05-08 2014-11-26 贵阳银行股份有限公司 一种转账方法、系统及管理平台
CN104408611A (zh) * 2014-10-29 2015-03-11 中国建设银行股份有限公司 一种他行卡电子银行业务办理的方法和系统
CN105787733A (zh) * 2014-12-24 2016-07-20 阿里巴巴集团控股有限公司 一种业务信息处理方法及装置
CN106161528A (zh) * 2015-04-07 2016-11-23 阿里巴巴集团控股有限公司 一种业务处理方法和装置
CN107123038A (zh) * 2017-03-14 2017-09-01 北京小度信息科技有限公司 账务数据处理方法及装置
CN108335192A (zh) * 2018-01-09 2018-07-27 阿里巴巴集团控股有限公司 业务处理、扣款方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7946475B2 (en) * 2007-03-23 2011-05-24 Sony Corporation Financial server, IC card terminal, and financial information processing method
CN101515349A (zh) * 2009-02-25 2009-08-26 上海付费通信息服务有限公司 付费帐单管家管理方法及其系统
CN106301851A (zh) * 2015-06-02 2017-01-04 中兴通讯股份有限公司 扣费方法及系统
CN106503976A (zh) * 2015-09-08 2017-03-15 阿里巴巴集团控股有限公司 账户应用执行控制方法及系统

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104166935A (zh) * 2014-05-08 2014-11-26 贵阳银行股份有限公司 一种转账方法、系统及管理平台
CN104408611A (zh) * 2014-10-29 2015-03-11 中国建设银行股份有限公司 一种他行卡电子银行业务办理的方法和系统
CN105787733A (zh) * 2014-12-24 2016-07-20 阿里巴巴集团控股有限公司 一种业务信息处理方法及装置
CN106161528A (zh) * 2015-04-07 2016-11-23 阿里巴巴集团控股有限公司 一种业务处理方法和装置
CN107123038A (zh) * 2017-03-14 2017-09-01 北京小度信息科技有限公司 账务数据处理方法及装置
CN108335192A (zh) * 2018-01-09 2018-07-27 阿里巴巴集团控股有限公司 业务处理、扣款方法及装置

Also Published As

Publication number Publication date
TW201931114A (zh) 2019-08-01
CN108335192A (zh) 2018-07-27
CN108335192B (zh) 2020-07-28

Similar Documents

Publication Publication Date Title
WO2020156225A1 (zh) 基于区块链系统的业务处理方法、装置、介质及电子设备
US8126967B2 (en) Multiple aggregator support
US9027083B2 (en) Management of access identifiers
US10623887B2 (en) Contextual geo-location idling
KR20180052527A (ko) 전화번호의 소유권을 검증하고 소유권 재할당을 트래킹하기 위한 시스템들 및 방법들
US20210042756A1 (en) Blockchain-based Security Management Method, Related Device and Storage Medium
JP7108628B2 (ja) Ｏｃｓが非応答である間のオンライン課金機構
WO2022108632A1 (en) Closed-loop environment for efficient, accurate, and secure transaction processing
CN112288577B (zh) 分布式服务的交易处理方法、装置、电子设备和介质
US9710833B2 (en) Method and apparatus for enabling concurrent rating during a re-rating operation
WO2019137202A1 (zh) 业务处理、扣款方法及装置
US20220182305A1 (en) Request Processing System and Method Thereof
US9892383B2 (en) Transactional services platform
CN116384993A (zh) 基于云支付中心实现订单支付状态高一致性的方法与系统
US9325841B1 (en) Determining whether the local time where a mobile device is located is within a calling window of time
US11520802B2 (en) Systems and methods for data format conversion
US20220101321A1 (en) Systems and methods for processing resource transfer requests
CA2981391C (en) Contextual geo-location idling
JP2018181012A (ja) 業務連携システムおよび業務連携方法
US20240053999A1 (en) Reconciliation systems and methods for unbounded streams
OA19720A (en) Network usage product provisioning via a mobile wallet platform
US20240054484A1 (en) Reconciliation systems and methods for unbounded streams
OA20072A (en) Electronic voucher distribution account management.
US20220164740A1 (en) Occupancy prediction using real-time information
WO2022038431A1 (en) System and method for remote provision, disbursement and collection of secured loans

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18900108

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18900108

Country of ref document: EP

Kind code of ref document: A1