CN113112344B - Service processing method, device, storage medium and computer program product - Google Patents
Service processing method, device, storage medium and computer program product Download PDFInfo
- Publication number
- CN113112344B CN113112344B CN202110432556.8A CN202110432556A CN113112344B CN 113112344 B CN113112344 B CN 113112344B CN 202110432556 A CN202110432556 A CN 202110432556A CN 113112344 B CN113112344 B CN 113112344B
- Authority
- CN
- China
- Prior art keywords
- repayment
- state
- service
- offset
- payment
- 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.)
- Active
Links
- 238000004590 computer program Methods 0.000 title claims abstract description 12
- 238000003672 processing method Methods 0.000 title abstract description 26
- 238000012545 processing Methods 0.000 claims abstract description 71
- 238000000034 method Methods 0.000 claims abstract description 54
- 230000001360 synchronised effect Effects 0.000 claims abstract description 48
- 238000012795 verification Methods 0.000 claims abstract description 29
- 230000008569 process Effects 0.000 claims abstract description 27
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 claims description 38
- 238000006467 substitution reaction Methods 0.000 claims description 15
- 238000010257 thawing Methods 0.000 claims description 8
- 230000008014 freezing Effects 0.000 claims description 6
- 238000007710 freezing Methods 0.000 claims description 6
- 238000010586 diagram Methods 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 230000000694 effects Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000001914 filtration Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/22—Payment schemes or models
- G06Q20/24—Credit schemes, i.e. "pay after"
-
- 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/12—Accounting
Abstract
The embodiment of the invention provides a business processing method, equipment, a storage medium and a computer program product, which adopt a synchronous thread to verify the state of a repayment list and user information related to a repayment request after the repayment request is received; if the verification is passed, modifying the repayment list state into a processing state, sending a repayment processing notification message to the terminal, and triggering an asynchronous thread; inquiring a service bill to be offset of a user by adopting an asynchronous thread, performing offset operation on the service bill to be offset according to a repayment request, and calling a reimbursement flow to perform reimbursement operation on the offset operation; and modifying the repayment state into a completion state, and sending a repayment completion notification message to the terminal. The repayment business process is divided into synchronous and asynchronous, verification operation is carried out through a synchronous thread, repayment offset operation and account reporting operation are carried out through an asynchronous thread, the time consumption of adopting the synchronous process is avoided being longer, a user repayment request is responded quickly, and system stability and user experience are improved.
Description
Technical Field
Embodiments of the present invention relate to the field of computers and internet technologies, and in particular, to a service processing method, a device, a storage medium, and a computer program product.
Background
With the continuous development of online consumption, credit payment is becoming more popular, and credit payment is a consumption mode of first consumption and then payment. The credit payment business mainly comprises transaction flows of consumption, repayment, refund and the like, and particularly when the consumption supports the stage, a plurality of stage orders are generated, including principal, commission, daily information, penalty information and the like. Repayment is a reverse operation of consumption that requires reimbursement.
At present, the general flow of the repayment service is particularly complex, and after the repayment system receives the repayment request of the user, a series of operation flows are required to be executed for the repayment request immediately until the repayment is successful, and then notification of a repayment result is returned to the user.
In the prior art, each operation in the repayment service flow adopts synchronous processing, the repayment flow consumes a long time, and the system response time-out and even downtime occur under the condition of high concurrency, so that the system stability and the user experience are poor; in addition, if the final success of repayment cannot be guaranteed, user data errors can be caused, and the availability of the system is low.
Disclosure of Invention
The embodiment of the invention provides a service processing method, equipment, a storage medium and a computer program product, which are used for ensuring the success of repayment service through synchronous threads and asynchronous threads and improving the system stability and user experience.
In a first aspect, an embodiment of the present invention provides a service processing method, including:
after receiving a repayment request sent by a terminal, checking a repayment list state and user information related to the repayment request by adopting a synchronous thread;
if the verification is passed, modifying the repayment list state into a processing state through the synchronous thread, sending a notification message in repayment processing to the terminal, and triggering an asynchronous thread;
inquiring a service list to be offset of a user by adopting the asynchronous thread, performing offset operation on the service list to be offset according to the repayment request, and calling a reimbursement flow to perform reimbursement operation on the offset operation;
and modifying the repayment state into a completion state through the asynchronous thread, and sending a notification message of repayment completion to the terminal.
In a second aspect, an embodiment of the present invention provides a service processing apparatus, including:
the synchronous processing unit is used for checking the state of the repayment list and the user information related to the repayment request by adopting a synchronous thread after receiving the repayment request sent by the terminal; if the verification is passed, modifying the repayment list state into a processing state through the synchronous thread, sending a notification message in repayment processing to the terminal, and triggering an asynchronous thread;
The asynchronous processing unit is used for inquiring a to-be-offset business bill of a user by adopting the asynchronous thread, performing offset operation on the to-be-offset business bill according to the repayment request, and calling a reimbursement flow to perform reimbursement operation on the offset operation; and modifying the repayment state into a completion state through the asynchronous thread, and sending a notification message of repayment completion to the terminal.
In a third aspect, an embodiment of the present invention provides an electronic device, including: at least one processor; a memory;
the memory stores computer-executable instructions;
the at least one processor executes computer-executable instructions stored by the memory, causing the at least one processor to perform the method as in the first aspect.
In a fourth aspect, embodiments of the present invention provide a computer-readable storage medium having stored therein computer-executable instructions that, when executed by a processor, implement a method as in the first aspect.
In a fifth aspect, embodiments of the present invention provide a computer program product comprising computer instructions which, when executed by a processor, implement a method as in the first aspect.
The business processing method, the equipment, the storage medium and the computer program product provided by the embodiment of the invention verify the repayment list state and the user information related to the repayment request by adopting the synchronous thread after receiving the repayment request sent by the terminal; if the verification is passed, modifying the repayment list state into a processing state through a synchronous thread, sending a notification message in repayment processing to a terminal, and triggering an asynchronous thread; inquiring a service list to be offset of a user by adopting an asynchronous thread, performing offset operation on the service list to be offset according to a repayment request, and calling a reimbursement flow to perform reimbursement operation on the offset operation; and modifying the repayment state into a completion state through an asynchronous thread, and sending a notification message of repayment completion to the terminal. The embodiment of the invention divides the repayment business process into two parts, namely synchronous and asynchronous, performs the verification operation through the synchronous thread, performs the relatively complex and complicated offset operation and the account reporting operation through the asynchronous thread, avoids the long time consumption of adopting the synchronous process, can rapidly respond to the repayment request of the user, improves the stability of the repayment business process, ensures the accuracy of the user data, and improves the stability and the user experience of the system.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure.
Fig. 1 is a schematic view of an application scenario of a service processing method according to an embodiment of the present invention;
FIG. 2 is a flowchart of a service processing method according to an embodiment of the present invention;
fig. 3 is a flowchart of a service processing method according to another embodiment of the present invention;
fig. 4 is a flowchart of a service processing method according to another embodiment of the present invention;
fig. 5 is a flowchart of a service processing method according to another embodiment of the present invention;
fig. 6 is a flowchart of a service processing method according to another embodiment of the present invention;
fig. 7 is a flowchart of a service processing method according to another embodiment of the present invention;
fig. 8 is a flowchart of a service processing method according to another embodiment of the present invention;
fig. 9 is a flowchart of a service processing method according to another embodiment of the present invention;
fig. 10 is a block diagram of a service processing device according to an embodiment of the present invention;
fig. 11 is a block diagram of an electronic device according to an embodiment of the present invention.
Specific embodiments of the present disclosure have been shown by way of the above drawings and will be described in more detail below. These drawings and the written description are not intended to limit the scope of the disclosed concepts in any way, but rather to illustrate the disclosed concepts to those skilled in the art by reference to specific embodiments.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
At present, the general flow of the repayment service is particularly complex, and the general flow of the repayment service is that a repayment request of a user is received, certificates and identity verification are carried out, bill information of the user is obtained, reimbursement is carried out, and notification of repayment results is synchronously returned. In the credit payment scenario, particularly in the staged payment scenario, the repayment process is more complex, the user transaction lock needs to be acquired to ensure that only one service can be executed for the same user at the same time, the service list which is checked out/not checked out by the user needs to be checked out, the service list is recorded and reimbursed in sequence, the account system is called for accounting, the user's credit is updated, the bill is updated, the loan list is updated, and the related service list is updated.
If these operations in the payment service flow are all synchronized, the following disadvantages exist: the repayment flow is long in time consumption, and the response of the system is overtime or even downtime under the condition of high concurrency, so that the stability of the system and the user experience are poor; because the repayment process needs to acquire transaction locks, a large number of updating operations are needed, an account system and a payment system are needed to be relied on, repayment is failed, repayment and reimbursement can be performed only after the payment is completed through the payment system, and if the repayment is not guaranteed to be successful finally, user data errors can be caused, and the availability of the system is low.
Aiming at the technical problems, the embodiment of the invention divides the repayment business process into two sub-processes, namely synchronous and asynchronous, executes repayment list state related to repayment request and verification operation of user information in synchronous threads, responds to users after verification, sends notification information in repayment processing to the users, triggers asynchronous threads, executes more complex and complicated operations in repayment business process, such as offset operation, account reporting operation and the like, can also execute payment substituting operation, update account system user quota, bill, loan list, related business list and the like, and finally modifies repayment state to be completed state through asynchronous threads after repayment is completed, and sends notification information of repayment completion to a terminal. The synchronous thread can rapidly respond to the user repayment request, the situation that the user needs to wait for the notification of the final repayment result all the time is avoided, the asynchronous thread is executed through the asynchronous thread, the asynchronous thread can be continued after the system is restored under the condition that the system response is overtime and even down, the whole repayment process cannot be blocked, the repayment success can be ensured, the accuracy of user data is ensured, and the system stability and user experience are improved.
The service processing method provided by the embodiment of the invention is suitable for an application scene as shown in fig. 1, and comprises a terminal 101 and a server 102, wherein the terminal can send a repayment request to the server 102, and the server 102 adopts a synchronous thread to carry out verification operation after receiving the repayment request, including but not limited to a repayment list state and user information related to the repayment request; if the verification is passed, modifying the repayment list state into a processing state through a synchronous thread, sending a notification message in repayment processing to the terminal 101, and triggering an asynchronous thread; inquiring a service list to be offset of a user by adopting an asynchronous thread, performing offset operation on the service list to be offset according to a repayment request, and calling a reimbursement flow to perform reimbursement operation on the offset operation; the repayment state is modified to a completion state by the asynchronous thread, and a notification message of repayment completion is sent to the terminal 101. Wherein the terminal 101 may not be limited to a smart phone, tablet, personal computer, wearable device, etc.; the server 102 may be a server or a server cluster, or may be a cloud server.
The following describes the technical scheme of the present invention and how the technical scheme of the present application solves the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present invention will be described below with reference to the accompanying drawings.
Fig. 2 is a flowchart of a service processing method according to an embodiment of the present invention. The embodiment provides a service processing method, the execution subject of which is electronic equipment such as a server side for service processing, and the method comprises the following specific steps:
s201, after receiving a repayment request sent by a terminal, checking a repayment list state and user information related to the repayment request by adopting a synchronous thread.
In this embodiment, a user may perform a payment operation on a terminal, and after receiving a payment request sent by the terminal, a server for payment service processing may use a synchronization thread to perform a payment list state and user information verification, where the user information verification includes, but is not limited to, login state verification, user account state verification, and so on.
In an alternative embodiment, as shown in fig. 3, the verification of the payment receipt status and the user information related to the payment request using the synchronization thread in S201 may include:
s2011, checking the login state of the user;
if the user is in the login state, S2012 is executed; if the user is in an unregistered state, the verification of the logging state fails, and the business processing flow is ended, namely, the subsequent other business processing flows are not performed;
S2012, checking the repayment order state;
if the repayment order state is the state to be processed, S2013 is executed; if the state of the repayment list is other states, responding according to the state of the repayment list, if the repayment list is inquired according to the payment list number, ending the service processing flow, and returning failure of inquiring the repayment list to the terminal; if the repayment list state is successful, ending the service processing flow and returning idempotent success to the terminal; if the repayment list is in the repayment processing state, returning the repayment list to the terminal;
s2013, checking the state of the user account;
if the user account is not present or is blocked (no authority is present), the user account status check fails, and the account status failure can be returned to the terminal; otherwise, the user account is in a normal state, and the verification is passed.
The verification operation of S2011-S2013 is executed by the synchronous thread, so that the validity of the repayment request can be ensured, a foundation is provided for the safety of the subsequent asynchronous thread, and the repayment request of the user can be responded quickly. And if any check is not passed, the business processing flow can be ended.
S202, if the verification is passed, modifying the repayment list state into a processing state through the synchronous thread, sending a notification message in repayment processing to the terminal, and triggering an asynchronous thread.
In this embodiment, through the above verification process, if verification is passed, the state of the payment form may be modified in the synchronous thread, the state of the payment form may be modified into the payment process, a notification message in the payment process may be sent to the terminal, and the asynchronous thread may be triggered, where the synchronous thread may end, without waiting for the result of the asynchronous thread all the time, and the payment request of the user may be responded quickly.
S203, inquiring a service list to be offset of a user by adopting the asynchronous thread, performing offset operation on the service list to be offset according to the repayment request, and calling a reimbursement flow to perform reimbursement operation on the offset operation.
In this embodiment, more complex operations in the payoff service may be performed in the asynchronous thread, including but not limited to a cancellation operation and a statement operation.
Specifically, the asynchronous thread may query the service ticket to be cancelled of the user according to the single number of the payment ticket, where the service ticket to be cancelled may include the service ticket to be cancelled that has been paid out, and may also include the service ticket to be cancelled that has not been paid out. More specifically, the service list to be cancelled may include at least one service list, such as principal stage list, stage handling bill, date bill, penalty bill, balance bill, etc., and since different types of service lists are stored in different service lists, the service list to be cancelled may be queried through a multithreading technology to increase query speed.
After the service ticket to be cancelled is acquired, a cancellation operation may be performed, where cancellation is a concept of accounting, that is, canceling the accounting originally recorded by the service ticket to be cancelled. Since the payment amount in the payment request may be equal to the amount of all the service orders to be cancelled, or may be less than the amount of all the service orders to be cancelled, or more than the amount of all the service orders to be cancelled, the cancellation operation of the service orders to be cancelled needs to be performed according to the payment request. Furthermore, after the offset operation, the account reporting operation needs to be completed on the user account, so that payment on the user account can be realized.
S204, modifying the repayment state into a completion state through the asynchronous thread, and sending a notification message of repayment completion to the terminal.
In this embodiment, the asynchronous thread may also modify the repayment status to a completion status finally, including but not limited to modifying the offset running status, the billing running status, the repayment bill status, the billing status, etc., and send a notification message of the repayment completion to the terminal, at which point the asynchronous thread may end.
The problem that the time consumption is long because the synchronous flow is adopted by the repayment business flow is avoided by executing complex and complicated offset operation and account reporting operation in the repayment business flow through the asynchronous thread, the synchronous flow is not required to wait for the final repayment result all the time, the asynchronous thread can be continued after the system is restored under the condition that the system response is overtime or even is down, the whole repayment flow is not blocked, and the accuracy of user data can be ensured to be successfully repayed.
According to the business processing method provided by the embodiment, after receiving the repayment request sent by the terminal, a synchronous thread is adopted to verify the repayment list state and the user information related to the repayment request; if the verification is passed, modifying the repayment list state into a processing state through a synchronous thread, sending a notification message in repayment processing to a terminal, and triggering an asynchronous thread; inquiring a service list to be offset of a user by adopting an asynchronous thread, performing offset operation on the service list to be offset according to a repayment request, and calling a reimbursement flow to perform reimbursement operation on the offset operation; and modifying the repayment state into a completion state through an asynchronous thread, and sending a notification message of repayment completion to the terminal. In the embodiment, the repayment service flow is divided into a synchronous part and an asynchronous part, the verification operation is executed through the synchronous thread, the relatively complex and complicated offset operation and the account reporting operation are executed through the asynchronous thread, the problem that the repayment service flow takes longer time due to the fact that the synchronous flow is adopted completely is avoided, the repayment request of a user can be responded quickly, in addition, the stability of the repayment service flow is improved, the accuracy of user data is guaranteed, and the stability and the user experience of the system are improved.
On the basis of any one of the embodiments, the service list to be cancelled is a plurality of service lists; the operation of canceling the service ticket to be cancelled according to the repayment request in S203 in the foregoing embodiment includes:
and according to the repayment amount of the repayment request and the preset service priority of the service list to be offset, sequentially performing offset operation on each service list to be offset.
In this embodiment, the service list to be cancelled may be plural, for example, may include at least two of the following service lists: the payment amount in the payment request may be less than the amount of all the service sheets to be cancelled, that is, only part of the service sheets to be cancelled may be cancelled, so that the service priorities of the service sheets to be cancelled, that is, the priority of the cancellation operation, may be preset in this embodiment, and the cancellation operation may be performed according to the payment amount and the preset service priorities of the service sheets to be cancelled, for example, the service sheets to be cancelled may be ordered in order from high to low according to the preset service priorities, and then the cancellation may be performed sequentially according to the ordering.
Optionally, on the basis of the foregoing embodiment, the sequentially performing a cancellation operation on each to-be-cancelled service list according to the payment amount of the payment request and the preset service priority of the to-be-cancelled service list may specifically include:
and traversing each service list to be cancelled in sequence according to the sequence of the preset service priority from high to low until the accumulated cancellation amount of the service list to be cancelled, which is subjected to cancellation operation, reaches the repayment amount or all the service lists to be cancelled are traversed.
In this embodiment, since the payment amount in the payment request may be less than the amount of all the service orders to be cancelled, that is, only a part of the service orders to be cancelled may be cancelled in the plurality of service orders to be cancelled, when the cancellation operation is performed by sequentially traversing each service order to be cancelled according to the order of the preset service priority from high to low, when traversing a certain service order to be cancelled, if the payment amount is used up, that is, the accumulated cancellation amount of the service order to be cancelled reaches the payment amount, the cancellation operation is ended.
For example, the preset service priority is from high to low, the amount of the service bill to be offset 1 is 10 yuan, the amount of the service bill to be offset 2 is 20 yuan, the amount of the service bill to be offset 3 is 30 yuan, if the repayment amount is 30 yuan, the service bill to be offset 1 is offset 10 yuan, then the service bill to be offset 2 is offset 20 yuan, the accumulated offset amount of the service bill which has undergone the offset operation at this time is 30 yuan, the payment amount is reached, the service bill to be offset 3 cannot continue to be offset, and the offset operation can be ended at this time; if the repayment amount is 40 yuan, the repayment of the service bill 3 to be reimbursed can be reimbursed for 10 yuan, and the accumulated reimbursement amount of the service bill subjected to the reimbursement operation is 40 yuan at the moment, so that the repayment amount is achieved.
In another case, if the repayment amount is equal to or greater than the amount of all the service orders to be cancelled, then all the service orders to be cancelled can be cancelled successfully, for example, in the above example, if the repayment amount is 60 yuan, then all the service orders to be cancelled can be cancelled successfully, and the repayment amount is not remained; and the repayment amount is 70 yuan, so that all the service sheets to be reimbursed can be reimbursed successfully, the repayment amount is 10 yuan, the rest 10 yuan is the repayment amount which is more returned by the user, and the repayment operation is needed to be adopted for reimbursement to the user.
In the above embodiment, the method further includes:
and if the service list to be cancelled is traversed, the accumulated cancellation amount of each service list to be cancelled is smaller than the repayment amount, and the asynchronous thread is adopted to call a repayment process to carry out repayment operation.
In this embodiment, if all the service units to be offset are traversed, the accumulated offset amount of each service unit to be offset is smaller than the repayment amount, which indicates that the user has multiple repayment conditions, and at this time, an asynchronous thread may be used to invoke a repayment procedure to perform a repayment operation, so as to refund multiple amounts to the user.
Specifically, as shown in fig. 4, the step of calling the substitution process by using the asynchronous thread to perform the substitution operation includes:
S301, creating a payment-replacing application form according to the accumulated cancellation amount of each service form to be cancelled and the repayment amount by adopting the asynchronous thread;
s302, performing account overflow payment freezing operation according to the payment application form, calling payment side equipment to carry out payment, and performing account overflow payment defrosting operation after successful payment.
In this embodiment, the payment application may be created after the cancellation operation is completed to determine a plurality of amounts according to the accumulated cancellation amount and the payment amount of each service order to be cancelled, so as to perform payment according to the reply application in the payment operation. Wherein the payment for the payment application may include, but is not limited to, a multi-payment amount, a payment order number, and the like.
When the payment is carried out, the payment request form can be inquired according to the payment request form, after the payment request form is inquired, if the payment request form is in a to-be-processed state, the account overflow payment freezing operation can be carried out according to the payment request form, wherein the overflow payment refers to more funds paid by a customer or funds stored in an account during the payment, the payment side equipment can be called for payment after the overflow payment is frozen, and the account overflow payment thawing operation can be carried out after the payment is completed.
More specifically, to ensure that S301-S302 successfully completes the payment, the payment request form status and the account overflow payment status may be monitored. Specifically, as shown in fig. 5, the process of executing S302 may include the following steps:
S311, inquiring the substitute payment application form according to the repayment single number, and filtering the substitute payment application form which is failed in state and replaced;
if the payment system is abnormal or the available balance of the overflowed payment account is insufficient in the payment replacing operation process, the payment replacing operation fails, the payment replacing operation calls the payment system, the number of the payment replacing application form needs to be sent, and the number of the application form cannot be reused after the failure, so that the state of the payment replacing application form can be modified to be failed, and a new payment replacing application form is created to replace the original payment replacing application form; and if the inquiry state is failed and the replaced substitute payment application form is replaced, the substitute payment application form is replaced by a new substitute payment application form. Therefore, when inquiring the substitute payment application form, the substitute payment application form with failed state and replaced can be filtered.
S312, judging the state of the substitution application form for the substitution application form which is not filtered;
if the state of the substitute payment application form is successful or empty, returning to success, ending the flow, and ensuring idempotent; if the state of the payment-for-purpose application form is failed, S313 is executed; if the state of the payment-substituted application form is to be processed, executing S314; if the state of the payment-substituted application form is thawing failure, executing S316;
S313, creating a new payment application form to replace the payment application form in a failure state;
after S313 is executed, S314 is continued based on the new payment application;
s314, calling account overflow payment freezing;
if the account overflows, pays, freezes and fails, return to failure, the flow is ended; otherwise, S315 is performed;
s315, calling payment side equipment to carry out substitution payment;
if the payment replacement fails, updating the state of the payment replacement application form as failure, returning to the failure, and ending the flow; otherwise, the payment is successful, execution 316;
s316, calling an account overflow payment defrosting operation;
if the account overflows, pays and thaws and fails, the state of the substitute payment application form is updated to be the thawing failure, otherwise, the state of the substitute payment application form is updated to be successful.
On the basis of any of the above embodiments, as shown in fig. 6, the step of calling the account reimbursement procedure to reimburse the cancellation operation in the above embodiment specifically includes:
s401, inquiring the billing pipelining state of the repayment request;
s402, if the billing running water state is a state to be checked out, relevant amount is summarized according to the billing running water state, and an account system is called to perform the checking out operation.
In this embodiment, after the execution of the cancellation operation is completed, it may be attempted to create an accounting running line, record information in the accounting process as a credential of the accounting operation, and further perform the accounting operation based on the accounting running line.
Specifically, to ensure that S401-S402 successfully completes billing, status monitoring may be performed, and specifically, as shown in fig. 7, the accounting operation may include the following procedures:
s411, inquiring the billing running water according to the repayment list number, and filtering out the billing running water which is failed in state and is replaced;
in this embodiment, if the account is checked out in the process of checking out, there may be an error in the accounting running water, the state of the accounting running water may be modified to be failed, and a new accounting running water is created to replace the original accounting running water. Thus, when the accounting running water is queried, the accounting running water whose status is failed and replaced can be filtered out.
S412, judging the state of billing running water for the billing running water which is not filtered;
if the state of the billing running water is successful, returning success, ending the flow, and ensuring idempotent; if the state of the accounting running water is failed, S413 is executed; if the state of the accounting running water is to be processed, executing S414;
s413, creating a new billing running water to replace the billing running water in the failure state;
after S313 is performed, based on the new billing pipelining, S414 is continued;
s414, summarizing the related amount according to the billing running water, and calling an account system to perform account reporting operation;
If the account is successfully reported, returning to the account successfully reported, otherwise, returning to the account failed, and ending the flow.
In addition, on the basis of the above embodiment, a cancellation stream may be created after the execution of the cancellation operation is completed, and the cancellation stream may be used to record information including, but not limited to, a payback number, a cancellation amount, a cancellation time, and the like, as a credential of the cancellation operation.
Based on any one of the foregoing embodiments, the modifying the repayment status to the completion status by the asynchronous thread in S204 may specifically include:
modifying the billing running water state, the repayment list state and the bill state into a completion state through the asynchronous thread; in addition, the offset stream state may also be modified to a completion state.
On the basis of any one of the above embodiments, if the execution of the offset operation fails in the offset process, the offset operation is periodically re-performed; if the execution of the account checking operation fails in the account checking process, the account checking operation is performed again at regular time; in addition, if the substitution operation fails to be executed in the substitution process, the substitution operation is performed again at regular time.
On the basis of any of the foregoing embodiments, as shown in fig. 8, S203 may specifically include:
S501, attempting to acquire a user transaction lock;
s502, after the user transaction lock is successfully obtained, inquiring a service list to be offset of the user by adopting the asynchronous thread.
In this embodiment, in order to ensure that only one service can be executed for the same user at the same time, and ensure the correctness of the service data of the user in the distributed scenario, when an asynchronous thread is triggered, the user transaction lock is tried to be acquired first, if the user transaction lock is acquired successfully, the subsequent service list to be offset of the user can be continuously executed, and the user transaction lock cannot be acquired again by other services of the user; if the acquisition of the user transaction lock fails, the attempt to acquire the user transaction lock can be periodically performed again. Further, after sending the notification message of payment completion to the terminal, the user transaction lock can be released, and at this time, other services can acquire the user transaction lock, so as to execute the service flow of acquiring the user transaction lock.
On the basis of any one of the above embodiments, this embodiment provides an asynchronous flow of a service processing method, as shown in fig. 9, which specifically includes the following steps:
s601, attempting to acquire a user transaction lock;
if the user transaction lock is successfully obtained, S602 is executed; if the acquisition of the user transaction lock fails, the attempt of acquiring the user transaction lock can be performed again at regular time;
S602, inquiring a service list to be offset of a user by adopting the asynchronous thread;
s603, according to the repayment amount of the repayment request and the preset service priority of the service list to be offset, sequentially conducting offset operation on each service list to be offset;
sequentially traversing each service list to be cancelled according to the sequence of the preset service priority from high to low until the accumulated cancellation amount of the service list to be cancelled which is subjected to cancellation operation reaches the repayment amount or all the service lists to be cancelled are traversed;
s604, attempting to create a cancellation stream, a billing stream and update a service ticket; if the accumulated cancellation amount of the business bill to be cancelled is smaller than the repayment amount, creating a payment application bill;
wherein, if the attempt to create the offset running water, the accounting running water is successful or the unique key conflict is made, S605 is executed; otherwise, timing retries; when the offset running water and the billing running water are created, the offset running water and the billing running water are created based on the repayment single number as the unique keys, namely, only one offset running water and one billing running water can exist in the same repayment single number at the same time, if the unique keys are found to conflict during the creation, the fact that other offset running water and billing running water exist at present is indicated, namely, the offset running water and the billing running water are created, and the S605 can be continuously executed;
S605, performing account reporting operation based on the created accounting running water;
if the account is successfully reported, S606 is executed; otherwise, executing the account reporting operation again at regular time;
s606, carrying out payment replacing operation based on the payment replacing application form;
if the substitution is successful, S607 is executed; otherwise, executing the substitution operation again at fixed time;
s607, updating and updating the offset running water state, the billing running water state, the repayment list state and the bill state to be the completion state; and sending a notification message of payment completion to the terminal;
s608, releasing the user transaction lock.
The principle and technical effects of the asynchronous flow in this embodiment can be referred to the above embodiments, and will not be described herein.
Fig. 10 is a block diagram of a service processing device according to an embodiment of the present invention. The service processing device provided in this embodiment may execute the processing flow provided in the method embodiment, as shown in fig. 10, where the service processing device 700 includes a synchronous processing unit 701 and an asynchronous processing unit 702.
The synchronization processing unit 701 is configured to verify, after receiving a payment request sent by a terminal, a payment list state and user information related to the payment request by using a synchronization thread; if the verification is passed, modifying the repayment list state into a processing state through the synchronous thread, sending a notification message in repayment processing to the terminal, and triggering an asynchronous thread;
The asynchronous processing unit 702 is configured to query a service ticket to be offset of a user by using the asynchronous thread, perform an offset operation on the service ticket to be offset according to the repayment request, and call a reimbursement flow to perform a reimbursement operation on the offset operation; and modifying the repayment state into a completion state through the asynchronous thread, and sending a notification message of repayment completion to the terminal.
On the basis of any one of the embodiments, the service list to be cancelled is a plurality of service lists; the asynchronous processing unit 702 is configured to, when performing a cancellation operation on the to-be-cancelled service ticket according to the repayment request:
and according to the repayment amount of the repayment request and the preset service priority of the service list to be offset, sequentially performing offset operation on each service list to be offset.
Based on any of the foregoing embodiments, when the asynchronous processing unit 702 sequentially performs a cancellation operation on each to-be-cancelled service ticket according to the payment amount of the payment request and the preset service priority of the to-be-cancelled service ticket, the processing unit is configured to:
and traversing each service list to be cancelled in sequence according to the sequence of the preset service priority from high to low until the accumulated cancellation amount of the service list to be cancelled, which is subjected to cancellation operation, reaches the repayment amount or all the service lists to be cancelled are traversed.
On the basis of any of the above embodiments, the asynchronous processing unit 702 is further configured to:
and if the service list to be cancelled is traversed, the accumulated cancellation amount of each service list to be cancelled is smaller than the repayment amount, and the asynchronous thread is adopted to call a repayment process to carry out repayment operation.
On the basis of any one of the above embodiments, when the asynchronous processing unit 702 uses the asynchronous thread to call a substitution flow to perform a substitution operation, the processing unit is configured to:
creating a payment-replacing application form according to the accumulated cancellation amount of each service form to be cancelled and the repayment amount by adopting the asynchronous thread;
and carrying out the account overflow payment freezing operation according to the payment application form, calling the payment side equipment to carry out payment instead, and carrying out the account overflow payment defrosting operation after successful payment.
On the basis of any one of the foregoing embodiments, when the asynchronous processing unit 702 invokes a declaration procedure to perform a declaration operation on the cancellation operation, the asynchronous processing unit is configured to:
inquiring the billing pipelining state of the repayment request;
and if the billing running water state is the to-be-billed state, summarizing the related amount according to the billing running water state, and calling an account system to perform the billing operation.
On the basis of any of the above embodiments, when the asynchronous processing unit 702 modifies the repayment state to the completion state by the asynchronous thread, the processing unit is configured to:
And modifying the billing pipelining state, the repayment list state and the bill state into the completion state through the asynchronous thread.
On the basis of any one of the above embodiments, when the asynchronous thread is adopted to query a service ticket to be cancelled of a user, the asynchronous processing unit 702 is configured to:
attempting to acquire a user transaction lock; after the user transaction lock is successfully obtained, inquiring a service list to be offset of the user by adopting the asynchronous thread;
the asynchronous processing unit 702 is further configured to, after sending a notification message of payment completion to the terminal:
releasing the user transaction lock.
On the basis of any of the above embodiments, the asynchronous processing unit 702 is further configured to:
if the execution of the offset operation fails, the offset operation is performed again at regular time; and/or
If the execution of the account reporting operation fails, the account reporting operation is performed again at regular time.
Based on any one of the foregoing embodiments, when the synchronization processing unit 701 uses a synchronization thread to verify the state of the payment form and the user information related to the payment request, the synchronization processing unit is configured to:
checking the login state of the user by adopting the synchronous thread;
if the user is in the login state, checking the repayment list state;
If the repayment list state is a to-be-processed state, checking the user account state;
if the user account state is normal, checking is passed.
The service processing device provided in the embodiment of the present invention may be specifically used to execute the method embodiments provided in fig. 2 to 9, and specific functions are not described herein.
After receiving a repayment request sent by a terminal, the service processing equipment provided by the embodiment of the invention adopts a synchronous thread to verify the repayment list state and user information related to the repayment request; if the verification is passed, modifying the repayment list state into a processing state through a synchronous thread, sending a notification message in repayment processing to a terminal, and triggering an asynchronous thread; inquiring a service list to be offset of a user by adopting an asynchronous thread, performing offset operation on the service list to be offset according to a repayment request, and calling a reimbursement flow to perform reimbursement operation on the offset operation; and modifying the repayment state into a completion state through an asynchronous thread, and sending a notification message of repayment completion to the terminal. In the embodiment, the repayment service flow is divided into a synchronous part and an asynchronous part, the verification operation is executed through the synchronous thread, the relatively complex and complicated offset operation and the account reporting operation are executed through the asynchronous thread, the problem that the repayment service flow takes longer time due to the fact that the synchronous flow is adopted completely is avoided, the repayment request of a user can be responded quickly, in addition, the stability of the repayment service flow is improved, the accuracy of user data is guaranteed, and the stability and the user experience of the system are improved.
Fig. 11 is a schematic structural diagram of an electronic device according to an embodiment of the present invention. The electronic device provided by the embodiment of the present invention may execute the processing flow provided by the embodiment of the service processing method, as shown in fig. 11, the electronic device 80 includes a memory 81, a processor 82, a computer program and a communication interface 83; wherein the computer program is stored in the memory 81 and configured to be executed by the processor 82 for the service processing method described in the above embodiment.
The electronic device of the embodiment shown in fig. 11 may be used to implement the technical solution of the above-mentioned embodiment of the service processing method, and its implementation principle and technical effects are similar, and are not described herein again.
In addition, the present embodiment also provides a non-transitory computer readable storage medium having stored thereon a computer program that is executed by a processor to implement the service processing method described in the above embodiments. The non-transitory computer readable storage medium may be a ROM, random-access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, etc.
In addition, the present embodiment further provides a computer program product, which includes computer instructions, where the computer instructions, when executed by a processor, implement the service processing method described in the foregoing embodiment.
In the several embodiments provided in the embodiments of the present invention, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown 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 may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in hardware plus software functional units.
The integrated units implemented in the form of software functional units described above may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium, and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform part of the steps of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional modules is illustrated, and in practical application, the above-described functional allocation may be performed by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to perform all or part of the functions described above. The specific working process of the above-described device may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
The above embodiments are only for illustrating the technical solution of the embodiments of the present invention, and are not limited thereto; although embodiments of the present invention have been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present invention.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (11)
1. A method for processing a service, comprising:
after receiving a repayment request sent by a terminal, checking a repayment list state and user information related to the repayment request by adopting a synchronous thread;
if the verification is passed, modifying the repayment list state into a processing state through the synchronous thread, sending a notification message in repayment processing to the terminal, and triggering an asynchronous thread;
attempting to acquire a user transaction lock; after the user transaction lock is successfully obtained, inquiring a to-be-offset business bill of the user by adopting the asynchronous thread, performing offset operation on the to-be-offset business bill according to the repayment request, and calling a reimbursement flow to perform reimbursement operation on the offset operation;
modifying the repayment state into a completion state through the asynchronous thread, and sending a notification message of repayment completion to the terminal;
the service list to be offset is a plurality of service lists; the operation of canceling the service ticket to be cancelled according to the repayment request comprises the following steps:
according to the repayment amount of the repayment request and the preset service priority of the service list to be offset, sequentially conducting offset operation on each service list to be offset;
if all the service units to be cancelled are traversed, the accumulated cancellation amount of each service unit to be cancelled is smaller than the repayment amount, and an alternative payment application form is created according to the accumulated cancellation amount of each service unit to be cancelled and the repayment amount by adopting the asynchronous thread;
And carrying out the account overflow payment freezing operation according to the payment application form, calling the payment side equipment to carry out payment instead, and carrying out the account overflow payment defrosting operation after successful payment.
2. The method according to claim 1, wherein the sequentially performing the cancellation operation on each to-be-cancelled service ticket according to the payment amount of the payment request and the preset service priority of the to-be-cancelled service ticket includes:
and traversing each service list to be cancelled in sequence according to the sequence of the preset service priority from high to low until the accumulated cancellation amount of the service list to be cancelled, which is subjected to cancellation operation, reaches the repayment amount or all the service lists to be cancelled are traversed.
3. The method of claim 1, wherein the invoking the checkout flow to checkout the reimbursement operation comprises:
inquiring the billing pipelining state of the repayment request;
and if the billing running water state is the to-be-billed state, summarizing the related amount according to the billing running water state, and calling an account system to perform the billing operation.
4. The method of claim 1, wherein modifying the repayment status to the completion status by the asynchronous thread comprises:
And modifying the billing pipelining state, the repayment list state and the bill state into the completion state through the asynchronous thread.
5. The method according to any one of claim 1 to 4, wherein,
after sending the notification message of payment completion to the terminal, the method further comprises:
releasing the user transaction lock.
6. The method according to any one of claims 1-4, further comprising:
if the execution of the offset operation fails, the offset operation is performed again at regular time; and/or
If the execution of the account reporting operation fails, the account reporting operation is performed again at regular time.
7. The method of any of claims 1-6, wherein verifying the payment instrument status and user information associated with the payment request using a synchronization thread comprises:
checking the login state of the user by adopting the synchronous thread;
if the user is in the login state, checking the repayment list state;
if the repayment list state is a to-be-processed state, checking the user account state;
if the user account state is normal, checking is passed.
8. A service processing apparatus, comprising:
the synchronous processing unit is used for checking the state of the repayment list and the user information related to the repayment request by adopting a synchronous thread after receiving the repayment request sent by the terminal; if the verification is passed, modifying the repayment list state into a processing state through the synchronous thread, sending a notification message in repayment processing to the terminal, and triggering an asynchronous thread;
The asynchronous processing unit is used for inquiring a to-be-offset business bill of a user by adopting the asynchronous thread, performing offset operation on the to-be-offset business bill according to the repayment request, and calling a reimbursement flow to perform reimbursement operation on the offset operation; modifying the repayment state into a completion state through the asynchronous thread, and sending a notification message of repayment completion to the terminal;
the service list to be offset is a plurality of service lists; the asynchronous processing unit is used for carrying out the offset operation on the to-be-offset business list according to the repayment request:
according to the repayment amount of the repayment request and the preset service priority of the service list to be offset, sequentially conducting offset operation on each service list to be offset;
the asynchronous processing unit is further configured to:
if all the service units to be cancelled are traversed, the accumulated cancellation amount of each service unit to be cancelled is smaller than the repayment amount, and the asynchronous thread is adopted to call a repayment process to carry out repayment operation;
when the asynchronous thread is adopted to call the substitution flow to carry out substitution operation, the asynchronous processing unit is used for:
creating a payment-replacing application form according to the accumulated cancellation amount of each service form to be cancelled and the repayment amount by adopting the asynchronous thread;
According to the payment request form, performing account overflow payment freezing operation, calling payment side equipment to perform payment, and performing account overflow payment defrosting operation after successful payment;
the asynchronous processing unit is used for inquiring a service list to be offset of a user by adopting the asynchronous thread, and is used for:
attempting to acquire a user transaction lock; and after the user transaction lock is successfully obtained, the asynchronous thread is adopted to inquire a service list to be offset of the user.
9. An electronic device, comprising: at least one processor; a memory;
the memory stores computer-executable instructions;
the at least one processor executing computer-executable instructions stored in the memory causes the at least one processor to perform the method of any one of claims 1-7.
10. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor implement the method of any of claims 1-7.
11. A computer program product comprising computer instructions which, when executed by a processor, implement the method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110432556.8A CN113112344B (en) | 2021-04-21 | 2021-04-21 | Service processing method, device, storage medium and computer program product |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110432556.8A CN113112344B (en) | 2021-04-21 | 2021-04-21 | Service processing method, device, storage medium and computer program product |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113112344A CN113112344A (en) | 2021-07-13 |
| CN113112344B true CN113112344B (en) | 2024-04-09 |
Family
ID=76719196
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110432556.8A Active CN113112344B (en) | 2021-04-21 | 2021-04-21 | Service processing method, device, storage medium and computer program product |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113112344B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113822660A (en) * | 2021-10-09 | 2021-12-21 | 京东科技控股股份有限公司 | Data processing method and device, electronic equipment and medium |
| CN114066648B (en) * | 2021-11-12 | 2022-07-26 | 粤港澳国际供应链(广州)有限公司 | Cross-service multi-service type data processing method and related equipment |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103297247A (en) * | 2013-07-05 | 2013-09-11 | 江苏省广电有线信息网络股份有限公司南京分公司 | Broadcasting and television branch business credit control management method and system for integration of three networks |
| CN109636369A (en) * | 2018-11-02 | 2019-04-16 | 深圳市快付通金融网络科技服务有限公司 | Fund account accounting processing method, apparatus, computer equipment and storage medium |
| CN111445327A (en) * | 2020-03-16 | 2020-07-24 | 腾讯科技（深圳）有限公司 | Data resource processing method and device, computer storage medium and electronic equipment |
| CN111667360A (en) * | 2020-06-19 | 2020-09-15 | 中信银行股份有限公司 | User limit information management method and device, electronic equipment and storage medium |
| CN111798228A (en) * | 2020-07-07 | 2020-10-20 | 北京三快在线科技有限公司 | Bill processing method, device, server and storage medium |
| CN112085358A (en) * | 2020-08-27 | 2020-12-15 | 上海云简软件科技有限公司 | Simple cost control management method for enterprise |
| CN112132565A (en) * | 2020-11-24 | 2020-12-25 | 支付宝(杭州)信息技术有限公司 | Payment method and device, electronic equipment and storage medium |
| CN112348491A (en) * | 2021-01-05 | 2021-02-09 | 树根互联技术有限公司 | Resource transaction detail determination method and device and server |
| CN112488690A (en) * | 2020-11-30 | 2021-03-12 | 银盛支付服务股份有限公司 | Real-time account distribution system, method, computer equipment and storage medium |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2012027694A2 (en) * | 2010-08-27 | 2012-03-01 | Visa International Service Association | Account number based bill payment platform apparatuses, methods and systems |
| US20150032622A1 (en) * | 2013-07-29 | 2015-01-29 | Mastercard International Incorporated | Online credit returns method and apparatus |
| US9582829B2 (en) * | 2014-05-06 | 2017-02-28 | Bank Of America Corporation | Dynamically modifying an application questionnaire |
| US20200265457A1 (en) * | 2019-02-20 | 2020-08-20 | Capital One Services, Llc | Systems and methods for rewards-based p2p funding |
-
2021
- 2021-04-21 CN CN202110432556.8A patent/CN113112344B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103297247A (en) * | 2013-07-05 | 2013-09-11 | 江苏省广电有线信息网络股份有限公司南京分公司 | Broadcasting and television branch business credit control management method and system for integration of three networks |
| CN109636369A (en) * | 2018-11-02 | 2019-04-16 | 深圳市快付通金融网络科技服务有限公司 | Fund account accounting processing method, apparatus, computer equipment and storage medium |
| CN111445327A (en) * | 2020-03-16 | 2020-07-24 | 腾讯科技（深圳）有限公司 | Data resource processing method and device, computer storage medium and electronic equipment |
| CN111667360A (en) * | 2020-06-19 | 2020-09-15 | 中信银行股份有限公司 | User limit information management method and device, electronic equipment and storage medium |
| CN111798228A (en) * | 2020-07-07 | 2020-10-20 | 北京三快在线科技有限公司 | Bill processing method, device, server and storage medium |
| CN112085358A (en) * | 2020-08-27 | 2020-12-15 | 上海云简软件科技有限公司 | Simple cost control management method for enterprise |
| CN112132565A (en) * | 2020-11-24 | 2020-12-25 | 支付宝(杭州)信息技术有限公司 | Payment method and device, electronic equipment and storage medium |
| CN112488690A (en) * | 2020-11-30 | 2021-03-12 | 银盛支付服务股份有限公司 | Real-time account distribution system, method, computer equipment and storage medium |
| CN112348491A (en) * | 2021-01-05 | 2021-02-09 | 树根互联技术有限公司 | Resource transaction detail determination method and device and server |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113112344A (en) | 2021-07-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3816910B1 (en) | Blockchain-based transaction processing method and apparatus, and electronic device | |
| US20210157800A1 (en) | Blockchain-based transaction processing methods, apparatuses, and electronic devices | |
| US11521275B2 (en) | Blockchain-based transaction processing method, apparatus, and electronic device | |
| CN110009338B (en) | Accounting method and device based on block chain and electronic equipment | |
| US11250395B2 (en) | Blockchain-based transaction processing methods and apparatuses and electronic devices | |
| CN113112344B (en) | Service processing method, device, storage medium and computer program product | |
| WO2011119223A1 (en) | System with multiple conditional commit databases | |
| EP3905172A1 (en) | Blockchain-based invoice voiding method and apparatus, and electronic device | |
| CN114253673A (en) | Transaction processing method and transaction processing device of distributed system | |
| CN109614263B (en) | Disaster tolerance data processing method, device and system | |
| CN109491765B (en) | Method and device for processing cross-domain service request | |
| CN110827001A (en) | Accounting event bookkeeping method, system, equipment and storage medium | |
| CN114066476A (en) | Method, device and storage medium for solving issue-first issue of distributed application transaction | |
| CN111367694B (en) | Event processing method, server and computer storage medium | |
| CN112099934A (en) | Batch processing method, system, computer equipment and storage medium | |
| CN108564424B (en) | Method for reducing errors in transaction information query and payment transaction system | |
| CN113919835A (en) | Business processing method, device, storage medium and computer program product | |
| CN111695901A (en) | Accounting voucher processing method, device, equipment and storage medium | |
| CN105574020B (en) | Database operation method and device | |
| CN111768293B (en) | Transaction information processing method, device, equipment and storage medium | |
| CN111582851B (en) | Platform money printing method and device based on big data, electronic equipment and storage medium | |
| CN107123051B (en) | Resource synchronization method and device | |
| CN115098528B (en) | Service processing method, device, electronic equipment and computer readable storage medium | |
| CN116226144A (en) | Data processing method and device, computer readable storage medium and electronic equipment | |
| CN114155092A (en) | Management method and management device for bank account, processor and electronic equipment |
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: 601, 6 / F, building 2, No. 18, Kechuang 11th Street, Daxing District, Beijing, 100176 Applicant after: Jingdong Technology Information Technology Co.,Ltd. Address before: 601, 6 / F, building 2, No. 18, Kechuang 11th Street, Beijing Economic and Technological Development Zone, Beijing 100176 Applicant before: Jingdong Shuke Haiyi Information Technology Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |