[ detailed description ] embodiments
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Fig. 1 is a flowchart illustrating a numerical processing method according to an embodiment of the present application. As shown in fig. 1, the method includes:
101. and sending a rule request message to a rule maintenance center.
102. And receiving the target conversion rule returned by the rule maintenance center according to the rule request message.
103. And performing numerical value conversion processing according to the target conversion rule.
The present embodiment provides a numerical processing method, which can be executed by a numerical processing apparatus. The numerical processing device may be a module or a part in charge of performing numerical conversion processing in various service systems, and is mainly used for executing the method flow provided by the embodiment to complete the numerical conversion processing.
In the present embodiment, the conversion rules are uniformly maintained and managed by the rule maintenance center. When the numerical value processing device needs to perform numerical value conversion processing, a rule request message is sent to the rule maintenance center to request a required conversion rule. The rule maintenance center receives a rule request message sent by the numerical value processing device, and determines a conversion rule needed by the numerical value processing device from at least one set of maintained conversion rules according to the rule request message. For convenience of description, the conversion rule required by the numerical processing apparatus is referred to as a target conversion rule, and the rule maintenance center returns the target conversion rule to the numerical processing apparatus after determining the target conversion rule. And the numerical value processing device receives a target conversion rule returned by the rule maintenance center according to the rule request message and performs numerical value conversion processing according to the target conversion rule.
Furthermore, the numerical value processing device can also develop services according to the numerical value after the numerical value conversion processing.
It should be noted that the value conversion process may be any value conversion process that needs to rely on a certain conversion rule, for example, long type value may be converted into int type value, or binary value may be converted into decimal value, or value may be converted from dollar currency to RMB currency, etc.
It should be noted that, depending on the service scenario and the service type, the flow of the numerical conversion process may be different, and the required conversion rule is also different. For the rule maintenance center, different conversion rules are respectively maintained for different service scenes and different service types. Based on this, the rule request message includes: a service scenario and a service type.
Based on the above, after receiving the rule request message, the rule maintenance center can analyze the rule request message to obtain a service scene and a service type; and according to the service scene and the service type, acquiring a conversion rule matched with the service scene and the service type from at least one set of maintained conversion rules as a target conversion rule, and returning the target conversion rule. And for the numerical processing device, after the rule request message is sent, the target conversion rule matched with the service scene and the service type and returned by the rule maintenance center is received.
As can be seen from the above, in the embodiment, the rule maintenance center maintains and manages the conversion rule in a unified manner, when the value conversion processing is required, the rule request message is sent to the rule maintenance center, the target conversion rule returned by the rule maintenance center according to the rule request message is received, and the value conversion processing is performed according to the received target conversion rule. Because the maintenance of the conversion rule is separated from the service system and is managed by the rule maintenance center in a unified way, the processing burden of the service system is reduced, and the service processing efficiency of the service system is improved.
In a scenario involving multi-currency payment clearing and refund, it is often necessary to perform a transfer operation. The rural cyber Source channel accessed by international payment at present is taken as an example for explanation: when a buyer pays through a cyber source channel, the buyer actually pays U.S. dollars, a payment treasure is used for guarantee transaction, finally the cyber source channel clears the payment treasure to be RMB calculated according to the corresponding exchange rate, and after the transaction is completed, the payment treasure deposits the corresponding amount of the RMB to the seller. The exchange process refers to exchange from dollar to RMB, in the process, the Payment is not only used for guarantee transaction, but also used for exchange operation, namely, the exchange accounting action is involved. The exchange operation is a specific numerical value conversion process, and the technical solution of the present application will be described in detail below by taking the exchange operation as an example. The execution subject of the following flow may be a business system, but is not limited thereto.
In a three-party payment system, the scenarios related to the exchange operation mainly include: a payment scenario, a refund scenario, and a repudiation scenario. The repudiation scenario refers to a situation where an illegal user has paid successfully, but a holding user such as a credit card or a payment account repudiates to accept the payment.
In this application, the exchange operation is divided into two types, one is a business exchange and one is a capital exchange. A complete exchange operation must involve both a business exchange and a funds exchange. Any exchange that only partially completes may be checked by the checking logic. The fund exchange mainly occurs in the reconciliation process of the business system and the three-party financial institution. The service exchange mainly occurs in the process that the service system carries out corresponding processing according to user operation initiated by a user. The user operation initiated by the user comprises a payment request sent by the user at a merchant website, or a refund application initiated by the user at the merchant website, or a payment refusal application initiated by the user at an issuer, and the like.
For example, in a specific payment scenario, when the business system receives a payment request sent by a user through a merchant website, it is determined that a corresponding payment amount needs to be deducted from a user account, a three-party financial channel is notified to deduct the payment amount from the user account into an account to be cleared of the business system (e.g., a payment treasured) and return a payment clearing result, and when the payment clearing result returned by the three-party financial channel is received, it may be determined whether an exchange operation needs to be performed, for example, when the currency paid by the user is different from the currency used for clearing by a three-party financial institution, the exchange operation needs to be performed. At this time, the service system sends a rule request message to the rule maintenance center, where a service scenario in the rule request message is a payment scenario, and accordingly, the exchange operation indicated by the service type in the rule request message includes: fund exchange and business exchange.
The rule maintenance center receives the rule request message sent by the service system, analyzes the rule request message, obtains the conversion rule of the service system request matched with the fund exchange and the service exchange in the payment scene, determines the target conversion rule matched with the fund exchange and the service exchange in the payment scene from at least one set of maintained conversion rules, and returns the target conversion rule to the service system. Accordingly, the target transformation rules herein include: in the payment scenario, the account and exchange logic involved in the fund exchange and the account and exchange logic involved in the business exchange.
Based on this, the service system performs numerical value conversion processing according to the target conversion rule as follows: and carrying out fund exchange processing according to the account and exchange logic related to the fund exchange, and carrying out service exchange processing according to the account and exchange logic related to the service exchange. Specifically, the business system performs reconciliation processing according to the payment clearing result, namely, the deduction details returned by the three-party financial channel are compared with the deduction details recorded by the business system (namely, the fund exchange process); if the two detail comparisons are consistent, a successful reconciliation is determined, indicating that the user's money has been received, the merchant is notified that there is no problem with the payment, the merchant is notified of the shipment, the payment amount is converted from the first currency to the second currency (e.g., from U.S. dollars to RMB) based on the current exchange rate, and the amount in the account involved in the transaction exchange (e.g., including the transit account and the merchant account) is decremented or incremented by the corresponding amount (i.e., the transaction exchange process).
The accounts involved in the fund transfer include accounts to be cleared, and the accounts to be cleared are mainly charged in a payment scene. The concept of the liquidation is that the third-party financial institution acknowledges receipt of a user-initiated recharge operation, but for various reasons has not transferred the money to the reserve payment account of the present business system (e.g., a tender). One reason is that there is a time difference between the system processing and the actual transfer time, and another reason is that the third party financial institution transfers the funds to the reserve account through another bank, which also requires processing time.
The accounts involved in the transaction exchange include transitional accounts, primarily transitional accounts in the same currency as the merchant account, such as U.S. dollar transitional accounts.
For example, in a specific refund scenario, taking an after-sale refund as an example, when the business system receives a refund request sent by a user through a merchant website, it is determined that a deduction needs to be made from a merchant account and the deducted money is returned to the user account, and at this time, if two different currencies are involved, it is determined that an exchange operation needs to be performed. When the exchange operation is required, the service system sends a rule request message to the rule maintenance center, wherein a service scene in the rule request message is a refund scene, and correspondingly, the exchange operation indicated by the service type in the rule request message comprises the following steps: fund exchange and business exchange.
The rule maintenance center receives the rule request message sent by the service system, analyzes the rule request message, obtains the conversion rule of the matching between the request of the service system and the fund exchange and the service exchange in the refund scene, determines the target conversion rule of the matching between the fund exchange and the service exchange in the refund scene from at least one set of maintained conversion rules, and returns the target conversion rule to the service system. Accordingly, the target transformation rules herein include: in a refund scenario, the account and exchange logic involved in the fund exchange and the account and exchange logic involved in the business exchange.
Based on this, the service system performs numerical value conversion processing according to the target conversion rule as follows: and carrying out fund exchange processing according to the account and exchange logic related to the fund exchange, and carrying out service exchange processing according to the account and exchange logic related to the service exchange. Specifically, the corresponding refund amount is transferred from the account of the merchant to the refund transition account of the first currency of the business system (such as a Payment treasure), the refund amount is converted from the first currency to the second currency, the refund amount of the second currency is transferred from the refund transition account of the first currency to the refund transition account of the second currency, the refund amount in the refund transition account of the second currency is transferred to the account of the user, the account of the user is the account of the second currency, and the business exchange process is completed. At this moment, the refund process is not finished, because the refund amount given to the user is directly transferred to the user account from the refund transitional account of the second currency, actually, a clearing process is needed for transferring the refund amount from the merchant account to the refund transitional account of the first currency, namely, only when a clearing result returned by the three-party financial structure is received, the refund amount is deducted from the merchant account and transferred to the refund transitional account of the first currency, then, the reconciliation is carried out, namely, the deduction details returned by the three-party financial channel are compared with the refund details recorded by the business system, when the comparison result is consistent, the reconciliation is determined to be successful, at this moment, the whole refund process is finished, and the clearing process is the refund fund remittance process.
The accounts involved in the fund exchange comprise accounts to be cleared, and in a refund scene, the accounts to be cleared for refund are mainly referred to. The accounts involved in the service exchange include transitional accounts, which mainly refer to transitional accounts of a first currency and transitional accounts of a second currency in a payment scene.
For example, in a specific rejection scenario, when the service system receives a rejection request sent by a user through an issuer, it determines that a deduction needs to be made from a claim account and returns the deduction to the user account, and if different currencies are involved, it determines that an exchange operation needs to be performed. When the exchange operation is needed, the service system sends a rule request message to the rule maintenance center, wherein a service scene in the rule request message is a payment refusing scene, and correspondingly, the exchange operation indicated by the service type in the rule request message comprises the following steps: fund exchange and business exchange.
The rule maintenance center receives the rule request message sent by the service system, analyzes the rule request message, obtains the conversion rule matched with the fund exchange and the service exchange in the service system request and the payment refusal scene, determines the target conversion rule matched with the fund exchange and the service exchange in the payment refund scene from at least one set of maintained conversion rules, and returns the target conversion rule to the service system. Accordingly, the target transformation rules herein include: in a refund scenario, the account and exchange logic involved in the fund exchange and the account and exchange logic involved in the business exchange.
Based on this, the service system performs numerical value conversion processing according to the target conversion rule as follows: and carrying out fund exchange processing according to the account and exchange logic related to the fund exchange, and carrying out service exchange processing according to the account and exchange logic related to the service exchange. Specifically, after receiving the rejection request, the user deducts money from the account for claim payment and returns the money to the user account, and then determines whether the service system claims or the merchant claims according to the result of disclaimer of the rejection, if the service system claims, the service system transfers money from the account for claim payment to the account for claim payment (the account for claim payment is the user account), and if the service system claims, the user transfers money from the account for claim payment to the account for claim payment.
The accounts involved in the fund transfer include accounts to be cleared, and in the refusal payment scene, the accounts to be cleared are mainly refused to be cleared. The accounts involved in the service exchange include transitional accounts, and in the rejection scenario, mainly account for claim payment, i.e. user account.
It can be seen from the above that, by using the method of the present application, each business system can be released from the shackle for maintaining the conversion rule, and pay attention to the business of the business system itself, and when exchange is needed, only the rule request message needs to be sent to the rule maintenance center, and the rule request message is returned by the rule maintenance center. In addition, the service system can control the whole exchange process and can also perform good registration and processing on places where loss and benefit are generated in the exchange.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
Fig. 2 is a schematic structural diagram of a numerical processing apparatus according to an embodiment of the present application. As shown in fig. 2, the apparatus includes: a sending module 21, a receiving module 22 and a conversion processing module 23.
A sending module 21, configured to send a rule request message to the rule maintenance center.
And the receiving module 22 is configured to receive the target conversion rule returned by the rule maintenance center according to the rule request message.
And a conversion processing module 23, configured to perform a numerical conversion process according to the target conversion rule received by the receiving module 22.
In an alternative embodiment, the numerical processing apparatus may further include: and the service processing module is configured to perform service on the value converted by the value conversion processing module 23.
In an optional embodiment, the rule request message includes: a service scenario and a service type. Based on this, the receiving module 22 is specifically configured to: and receiving a target conversion rule which is matched with the service scene and the service type and is returned by the rule maintenance center.
Optionally, the service scenario is a payment scenario, and the exchange service indicated by the service type includes: fund exchange and business exchange. Correspondingly, the target conversion rule includes: in the payment scenario, the account and exchange logic involved in the fund exchange and the account and exchange logic involved in the business exchange.
The conversion processing module 23 is specifically configured to:
and carrying out fund exchange processing according to the account and exchange logic related to the fund exchange, and carrying out service exchange processing according to the account and exchange logic related to the service exchange.
Optionally, the service scenario is a refund scenario, and the service types include: fund exchange and business exchange. Correspondingly, the target conversion rule includes: in a refund scenario, the account and exchange logic involved in the fund exchange and the account and exchange logic involved in the business exchange.
The conversion processing module 23 is specifically configured to:
and carrying out fund exchange processing according to the account and exchange logic related to the fund exchange, and carrying out service exchange processing according to the account and exchange logic related to the service exchange.
Optionally, the service scenario is a denial of service scenario, and the service types include: fund exchange and business exchange. Correspondingly, the target conversion rule includes: in the rejection scenario, the account and exchange logic involved in the fund exchange and the account and exchange logic involved in the business exchange.
The conversion processing module 23 is specifically configured to:
and carrying out fund exchange processing according to the account and exchange logic related to the fund exchange, and carrying out service exchange processing according to the account and exchange logic related to the service exchange.
The numerical processing device provided in this embodiment is matched with the rule maintenance center, and allows the rule maintenance center to maintain the conversion rules in a unified manner, based on which, when the numerical conversion processing needs to be performed, the numerical processing device sends a rule request message to the rule maintenance center, receives a target conversion rule returned by the rule maintenance center according to the rule request message, and performs the numerical conversion processing according to the received target conversion rule. Because the maintenance of the conversion rule is stripped and managed uniformly by the rule maintenance center, the processing burden of the numerical value processing device is reduced, and the service processing efficiency is improved.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device) or a processor (processor) to execute some steps of the methods according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit 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 technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.