CN113112344A - Business processing method, device, storage medium and computer program product - Google Patents
Business processing method, device, storage medium and computer program product Download PDFInfo
- Publication number
- CN113112344A CN113112344A CN202110432556.8A CN202110432556A CN113112344A CN 113112344 A CN113112344 A CN 113112344A CN 202110432556 A CN202110432556 A CN 202110432556A CN 113112344 A CN113112344 A CN 113112344A
- Authority
- CN
- China
- Prior art keywords
- repayment
- state
- payment
- offset
- service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000004590 computer program Methods 0.000 title claims abstract description 13
- 238000003672 processing method Methods 0.000 title abstract description 27
- 238000000034 method Methods 0.000 claims abstract description 81
- 238000012545 processing Methods 0.000 claims abstract description 71
- 230000008569 process Effects 0.000 claims abstract description 54
- 230000001360 synchronised effect Effects 0.000 claims abstract description 54
- 238000012795 verification Methods 0.000 claims abstract description 31
- 238000004080 punching Methods 0.000 claims description 12
- 238000006467 substitution reaction Methods 0.000 claims description 11
- 230000008014 freezing Effects 0.000 claims description 8
- 238000007710 freezing Methods 0.000 claims description 8
- 230000001960 triggered effect Effects 0.000 abstract description 3
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 description 14
- 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
- 230000000694 effects Effects 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
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000008570 general process Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000010257 thawing Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- 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 service processing method, equipment, a storage medium and a computer program product, wherein after a repayment request is received, a synchronous thread is adopted to verify a repayment bill state and user information related to the repayment request; if the verification is passed, the state of the repayment bill is modified into a processing state, a notification message in the repayment processing is sent to the terminal, and an asynchronous thread is triggered; adopting an asynchronous thread to inquire a business sheet to be offset of a user, carrying out offset operation on the business sheet to be offset according to a repayment request, and calling an accounting flow to carry out accounting 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 service process is divided into synchronous and asynchronous processes, the verification operation is executed through the synchronous thread, the reimbursement cancellation operation and the payment operation are executed through the asynchronous thread, the phenomenon that the time consumption is long when the synchronous process is adopted is avoided, the repayment request of a user is responded quickly, and the system stability and the user experience are improved.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers and internet, in particular to a service processing method, service processing equipment, a storage medium and a computer program product.
Background
With the continuous development of online consumption, credit payment is more and more popular, and the credit payment is a consumption mode of first consumption and later payment. The credit payment service mainly comprises transaction processes of consumption, payment, refund and the like, and particularly, when the consumption supports staging, a plurality of staging lists including principal, commission charge, daily interest, penalty and the like are generated. Repayment is the reverse operation of consumption, requiring a cost strike-off.
At present, the general process of the payment service is particularly complex, and after receiving a payment request of a user, a payment system needs to immediately execute a series of operation processes for the payment request until the payment is successful, and then returns a notification of a payment result to the user.
In the prior art, each operation in a repayment service process adopts synchronous processing, the repayment process is long in time consumption, and particularly, the system response overtime and even downtime conditions occur under the high concurrency condition, so that the system stability and the user experience are poor; in addition, if the payment cannot be guaranteed to be successful finally, user data errors can be caused, and the system availability is low.
Disclosure of Invention
Embodiments of the present invention provide a service processing method, a service processing device, a storage medium, and a computer program product, which are used to ensure success of a payment service through a synchronous thread and an asynchronous thread, and improve system stability and user experience.
In a first aspect, an embodiment of the present invention provides a service processing method, including:
after a repayment request sent by a terminal is received, verifying a repayment bill state and user information related to the repayment request by adopting a synchronous thread;
if the verification is passed, modifying the state of the payment list into a processing state through the synchronous thread, sending a notification message in payment processing to the terminal, and triggering an asynchronous thread;
inquiring a business sheet to be offset of a user by adopting the asynchronous thread, carrying out offset operation on the business sheet to be offset according to the repayment request, and calling an accounting flow to carry out accounting operation on the offset operation;
and modifying the repayment state into a completion state through the asynchronous thread, and sending a notification message of the completion of the repayment to the terminal.
In a second aspect, an embodiment of the present invention provides a service processing device, including:
the synchronous processing unit is used for verifying the repayment bill state 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 state of the payment list into a processing state through the synchronous thread, sending a notification message in payment processing to the terminal, and triggering an asynchronous thread;
the asynchronous processing unit is used for inquiring a business form to be offset of a user by adopting the asynchronous thread, carrying out offset operation on the business form to be offset according to the repayment request and calling an accounting flow to carry out accounting operation on the offset operation; and modifying the repayment state into a completion state through the asynchronous thread, and sending a notification message of the completion of the repayment to the terminal.
In a third aspect, an embodiment of the present invention provides an electronic device, including: at least one processor; and a memory;
the memory stores computer-executable instructions;
the at least one processor executing the computer-executable instructions stored by the memory causes the at least one processor to perform a method as in the first aspect.
In a fourth aspect, the present invention provides a computer-readable storage medium, in which computer-executable instructions are stored, and when a processor executes the computer-executable instructions, the method according to the first aspect is implemented.
In a fifth aspect, an embodiment of the present invention provides a computer program product, which includes computer instructions that, when executed by a processor, implement the method according to the first aspect.
According to the service processing method, the service processing equipment, the service processing storage medium and the computer program product, after a repayment request sent by a terminal is received, a synchronous thread is adopted to verify a repayment bill state and user information related to the repayment request; if the verification is passed, modifying the state of the payment list into a processing state through a synchronous thread, sending a notification message in payment processing to the terminal, and triggering an asynchronous thread; adopting an asynchronous thread to inquire a business sheet to be offset of a user, carrying out offset operation on the business sheet to be offset according to a repayment request, and calling an accounting flow to carry out accounting operation on the offset operation; and modifying the repayment state into a completion state through the asynchronous thread, and sending a notification message of the completion of the repayment to the terminal. According to the embodiment of the invention, the repayment business process is divided into a synchronous part and an asynchronous part, the synchronous thread is used for executing the verification operation, and the asynchronous thread is used for executing more complex and fussy reimbursement operation and account reporting operation, so that the longer time consumption of the synchronous process is avoided, the user repayment request can be quickly responded, the stability of the repayment business process is improved, the accuracy of user data is ensured, and the system stability and the user experience are improved.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present 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.
With the foregoing drawings in mind, certain embodiments of the disclosure have been shown and described in more detail below. These drawings and written description are not intended to limit the scope of the disclosed concepts in any way, but rather to illustrate the concepts of the disclosure to those skilled in the art by reference to specific embodiments.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
At present, the common flow of the repayment service is particularly complex, and the common flow of the repayment service is to receive a repayment request of a user, perform credential and identity verification, acquire user bill information, perform offset, and synchronously return a notification of a repayment result. In a credit payment scenario, particularly in a staged payment scenario, a repayment process is more complex, a user transaction lock needs to be acquired to ensure that only one service can be executed for the same user at the same time, an account system needs to be called to inquire a service bill which is paid out/not paid out by the user for reimbursement, record reimbursement running water, call an account system for bookkeeping to update user amount, update a bill, update a loan bill and update related service bills, and particularly, when the user has a more (more repayment amount than a due amount) scenario, a payment system needs to be called to perform a replacement payment operation.
If these operations in the payment business process are all processed synchronously, there are the following disadvantages: the repayment process takes long time, particularly, the system response overtime and even downtime condition occurs under the high concurrency condition, and the system stability and the user experience are poor; because the repayment process needs to acquire a transaction lock, a large amount of updating operation is needed, and the repayment process needs to depend on an account system and a payment system, the repayment process fails, the repayment is carried out only by completing deduction through the payment system, if the repayment cannot be guaranteed to be finally successful, user data errors can be caused, and the system availability is low.
Aiming at the technical problem, the embodiment of the invention divides the repayment business process into a synchronous sub-process and an asynchronous sub-process, executes the repayment request related repayment bill state and the user information verification operation in the synchronous thread, responds to the user after the verification is passed, sends the notification message in the repayment process to the user, triggers the asynchronous thread, executes the more complex and complicated operations in the repayment business process through the asynchronous thread, such as the reimbursement operation, the account reporting operation and the like, and also can execute the payment withholding operation, update the account system user amount, the bill, the loan bill, the related business bill and the like, finally modifies the repayment state into the completion state through the asynchronous thread after the repayment is completed, and sends the repayment completion notification message to the terminal. The repayment request of the user can be responded quickly through the synchronous thread, the situation that the user needs to wait for the notification of the final repayment result all the time is avoided, the asynchronous thread executes complex operation, the asynchronous thread can be continuously executed after the system is recovered under the condition that the response of the system is overtime or even down, the whole repayment process cannot be blocked, the success of the repayment can be ensured, the accuracy of user data is ensured, and the stability of the system and the user experience are improved.
The service processing method provided by the embodiment of the invention is suitable for the application scenario shown in fig. 1, and includes a terminal 101 and a server 102, where the terminal can send a repayment request to the server 102, and the server 102 performs a verification operation by using a synchronous thread after receiving the repayment request, including but not limited to a repayment order state and user information related to the repayment request; if the verification is passed, modifying the state of the payment list into a processing state through a synchronous thread, sending a notification message in payment processing to the terminal 101, and triggering an asynchronous thread; adopting an asynchronous thread to inquire a business sheet to be offset of a user, carrying out offset operation on the business sheet to be offset according to a repayment request, and calling an accounting flow to carry out accounting operation on the offset operation; and modifying the payment state into a completion state through the asynchronous thread, and sending a notification message of payment completion to the terminal 101. Wherein the terminal 101 may not be limited to a smartphone, a tablet, a personal computer, a 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 solutions of the present invention and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated 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 provided in the embodiment of the present invention. The embodiment provides a service processing method, an execution main body of which is an electronic device such as a server and the like for service processing, and the service processing method specifically comprises the following steps:
s201, after receiving a repayment request sent by a terminal, verifying a repayment bill 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 perform verification on a payment receipt state and user information by using a synchronous thread, where the user information verification includes, but is not limited to, login state verification, user account state verification, and the like.
In an alternative embodiment, as shown in fig. 3, the verifying the repayment order status and the user information related to the repayment request by using the synchronous thread in S201 may include:
s2011, checking the login state of the user;
if the user is in the login state, executing S2012; if the user is in the unregistered state, the login state verification fails, and the service processing flow is ended, namely other subsequent service processing flows are not performed;
s2012, verifying the state of the payment bill;
if the payment bill state is a pending state, executing S2013; if the state of the repayment bill is other states, responding according to the state of the repayment bill, if the repayment bill is inquired according to the number of the payment bill, ending the service processing flow, and returning the failure of inquiring the repayment bill to the terminal; if the repayment bill state is successful, ending the service processing flow and returning success of idempotent to the terminal; if the payment list is in the state of payment processing, returning the payment list to the terminal for processing;
s2013, verifying the user account state;
if the user account does not exist or is not allowed to enter (has no authority), the verification of the user account state fails, and the account state failure can be returned to the terminal; otherwise, the user account status is normal, and the verification is passed.
The verification operation of the S2011-S2013 is executed through the synchronous thread, so that the legality of the repayment request can be ensured, a basis is provided for the safety of a subsequent asynchronous thread, and the repayment request of a user can be responded quickly. And if any check fails, the business processing flow can be ended.
And S202, if the verification is passed, modifying the state of the payment list into a processing state through the synchronous thread, sending a notification message in the payment processing to the terminal, and triggering the asynchronous thread.
In this embodiment, through the above verification process, if the verification passes, the payment receipt status may be modified in the synchronous thread, the payment receipt status is modified into the payment processing, a notification message in the payment processing is sent to the terminal, and the asynchronous thread is triggered, at this time, the synchronous thread may end, and the user's payment request may be quickly responded without waiting for the result of the asynchronous thread all the time.
S203, inquiring the business sheet to be offset of the user by adopting the asynchronous thread, carrying out offset operation on the business sheet to be offset according to the repayment request, and calling an accounting flow to carry out accounting operation on the offset operation.
In this embodiment, the asynchronous thread may perform more complex operations in the payment service, including but not limited to an offset operation and an accounting operation.
Specifically, the asynchronous thread may query the to-be-cancelled business order of the user according to the order number of the payment order, where the to-be-cancelled business order may include a paid-out to-be-cancelled business order, and may also include a non-paid-out to-be-cancelled business order. More specifically, the service order to be distributed may include at least one service order, such as a principal installment order, a daily order, a penalty order, a forward order, and the like, and since different types of service orders are stored in different service tables, the service order to be distributed may be queried through a multi-thread technique, so as to increase the query speed.
After the business order to be punched and sold is obtained, punching and selling operation can be executed, wherein punching and selling is a concept of accounting, namely, accounts originally recorded by the business order to be punched and sold are offset. Because the repayment amount in the repayment request may be equal to the amount of all the service orders to be offset, may be less than the amount of all the service orders to be offset, or more than the amount of all the service orders to be offset, the offset operation of the service orders to be offset needs to be performed according to the repayment request. Further, after the reimbursement operation, the reimbursement of the user account can be realized only by completing the account-posting operation on the user account.
S204, the repayment state is modified to be a completion state through the asynchronous thread, and a notification message of the completion of the repayment is sent to the terminal.
In this embodiment, the asynchronous thread may finally modify the payment status to a completed status, including but not limited to modifying the reimbursement flow status, the billing flow status, the payment receipt status, the billing status, and the like, and send a notification message of the completion of the payment to the terminal, at which point the asynchronous thread may end.
The asynchronous thread executes complex and tedious reimbursement operation and account-reporting operation in the repayment business process, so that the problem of long consumed time caused by the fact that the repayment business process adopts a synchronous process completely can be avoided, the synchronous process is not required to wait for a final repayment result all the time, the asynchronous thread can be continuously executed after the system is recovered under the condition that the system response is overtime or even down, the whole repayment process cannot be blocked, and the success of repayment can be ensured, and the accuracy of user data can be ensured.
In the service processing method provided by this embodiment, after a repayment request sent by a terminal is received, a synchronization thread is used to verify a repayment order state and user information related to the repayment request; if the verification is passed, modifying the state of the payment list into a processing state through a synchronous thread, sending a notification message in payment processing to the terminal, and triggering an asynchronous thread; adopting an asynchronous thread to inquire a business sheet to be offset of a user, carrying out offset operation on the business sheet to be offset according to a repayment request, and calling an accounting flow to carry out accounting operation on the offset operation; and modifying the repayment state into a completion state through the asynchronous thread, and sending a notification message of the completion of the repayment to the terminal. According to the embodiment, the repayment business process is divided into a synchronous part and an asynchronous part, the verification operation is executed through a synchronous thread, the complicated and tedious reimbursement operation and the account reporting operation are executed through an asynchronous thread, the situation that the time consumption is long due to the fact that the repayment business process is completely adopted by the synchronous process is avoided, the user repayment request can be responded quickly, the stability of the repayment business process is improved, the accuracy of user data is guaranteed, and the system stability and the user experience are improved.
On the basis of any one of the above embodiments, the service list to be cancelled is multiple; in the above embodiment, the canceling operation of the to-be-cancelled business form according to the repayment request in S203 includes:
and sequentially carrying out cancellation operation on each service bill to be cancelled according to the repayment amount of the repayment request and the preset service priority of the service bill to be cancelled.
In this embodiment, there may be a plurality of service tickets to be revoked, and for example, the service tickets may include at least two of the following service tickets: the repayment amount in the repayment request may be less than the amount of all the service orders to be amortized, that is, only part of the service orders to be amortized may be amortized, so in this embodiment, the service priorities of the service orders may be preset, that is, the priority of the amortization operation is equivalent to the priority of the amortization operation, and then the amortization operation is performed according to the repayment amount and the preset service priority of each service order to be amortized, for example, the service orders to be amortized may be sorted according to the preset service priority from high to low, and then the amortization is performed in sequence according to the sorting.
Optionally, on the basis of the above embodiment, the performing, in sequence, an offset operation on each service ticket to be offset according to the repayment amount of the repayment request and the preset service priority of the service ticket to be offset may specifically include:
and according to the sequence of the preset service priority from high to low, sequentially traversing each service sheet to be offset to carry out offset operation until the accumulated offset amount of the service sheets to be offset, which have been subjected to offset operation, reaches the repayment amount or all the service sheets to be offset are completely passed through.
In this embodiment, because the repayment amount in the repayment request may be less than the amount of all the service tickets to be offset, that is, only some service tickets to be offset may be offset, when traversing each service ticket to be offset in sequence according to the preset service priority from high to low to perform the offsetting operation, when traversing a certain service ticket to be offset, if the repayment amount is used up, that is, the accumulated offsetting amount of the service ticket to be offset reaches the repayment amount, the offsetting operation is ended.
For example, the preset service priority is from high to low, the sum of the to-be-punched and sold service list 1 is 10 yuan, the sum of the to-be-punched and sold service list 2 is 20 yuan, and the sum of the to-be-punched and sold service list 3 is 30 yuan, if the repayment sum is 30 yuan, the to-be-punched and sold service list 1 is punched and sold 10 yuan, then the to-be-punched and sold service list 2 is punched and sold 20 yuan, the accumulated punching and selling sum of the service list which has been punched and sold at this time is 30 yuan, the repayment sum is reached, the to-be-punched and sold service list 3 cannot continue to be punched and sold, and the punching and selling operation can be ended; if the repayment amount is 40 yuan, 10 yuan can be further offset for the business bill to be offset 3, the accumulated offset amount of the business bill which is subjected to offset operation is 40 yuan at the moment, and the repayment amount is reached.
In another case, if the repayment amount is equal to or greater than the amount of all the service tickets to be offset, all the service tickets to be offset can be successfully offset, for example, in the above example, if the repayment amount is 60 yuan, all the service tickets to be offset can be successfully offset, and the repayment amount is not left; and if the repayment amount is 70 yuan, all the business orders to be cancelled can be cancelled and cancelled successfully, the repayment amount is 10 yuan, the remaining 10 yuan is the more repayment amount of the user, and the user needs to be refunded by adopting a payment operation.
In the above embodiment, the method further comprises:
and if all the service lists to be offset are completely passed through and the accumulated offset sum of each service list to be offset is smaller than the repayment sum, calling a payment substitution flow by adopting the asynchronous thread to perform payment substitution operation.
In this embodiment, if all the service tickets to be offset are completed, and the accumulated offset amount of each service ticket to be offset is smaller than the repayment amount, it indicates that the user has multiple repayment situations, and at this time, the asynchronous thread may be adopted to call the repayment flow to perform the repayment operation, and the multiple repayment amount is returned to the user.
Specifically, as shown in fig. 4, the invoking of the payment-instead flow by the asynchronous thread to perform the payment-instead operation includes:
s301, establishing a payment-on-behalf application form according to the accumulated reimbursement amount of each service form to be reimbursed and the repayment amount by adopting the asynchronous thread;
s302, carrying out account overflowed payment freezing operation according to the payment requisition form, calling payment side equipment to carry out payment for others, and carrying out account overflowed payment unfreezing operation after successful payment for others.
In this embodiment, the reimbursement application form may be created after the reimbursement operation is completed and the accumulated reimbursement amount of each to-be-reimbursed service form may be determined, so that the reimbursement may be performed according to the reply application form during the reimbursement operation. The payment-on-behalf form may include, but is not limited to, a sum of more money and a number of a payment order.
During the payment-on-behalf operation, the payment-on-behalf application form can be inquired according to the repayment order number, after the payment-on-behalf application form is inquired, if the state of the payment-on-behalf application form is a pending state, the account payment-on-behalf freezing operation can be performed according to the payment-on-behalf application form, wherein the payment-on-behalf refers to funds which are paid by the customer more during the repayment or funds stored in the account, the payment-on-behalf freezing operation can be performed by using the payment-side equipment after the payment-on-behalf freezing operation is performed, and the account payment-on-behalf unfreezing operation can be performed after the payment-.
More specifically, in order to ensure that the payment by credit is successfully completed in S301-S302, the status of the payment by credit application form and the status of the payment by credit payment by account can be monitored. Specifically, as shown in fig. 5, the process of executing S302 may include the following steps:
s311, inquiring the alternative payment application form according to the repayment bill number, and filtering out the alternative payment application form which is in failure and is replaced;
if the payment system is abnormal or the available balance of the overflowed payment account is insufficient in the payment operation process, the payment operation is failed, the payment system is called by the payment operation, the application form number needs to be uploaded, and the application form number cannot be reused after the failure, so that the state of the payment application form can be modified to be failed, a new payment application form is created, and the original payment application form is replaced; and if the replaced alternative payment application form with the failed state is inquired, the alternative payment application form is replaced by the new alternative payment application form. Therefore, when inquiring the depreciation application form, the depreciation application form which is failed and replaced can be filtered.
S312, judging the state of the filtered alternative payment application form;
if the state of the payment request form is successful or null, the success is returned, the process is ended, and the idempotent is ensured; if the status of the payment request form is failure, executing S313; if the status of the payment request form is pending, executing S314; if the state of the payment-for-replacement application form is unfreezing failure, executing S316;
s313, creating a new depreciation application form, and replacing the depreciation application form in a failure state;
after the step S313 is executed, the step S314 is continuously executed based on the new delivery request form;
s314, calling account overflowed payment freezing;
if the account overflowed payment freezing fails, returning to failure, and ending the process; otherwise, go to S315;
s315, calling payment side equipment to carry out payment for others;
if the payment generation fails, updating the state of the payment generation application form as failure, returning to failure, and ending the process; otherwise, the payment is successfully made, and 316 is executed;
s316, invoking an account overflowed payment unfreezing operation;
and if the account is in the over-payment state, updating the state of the payment-withholding application form into thawing failure, or else, updating the state of the payment-withholding application form into success.
On the basis of any of the foregoing embodiments, as shown in fig. 6, the invoking an account-posting flow in S203 in the foregoing embodiments performs an account-posting operation on the reimbursement operation, which specifically includes:
s401, inquiring the accounting running state of the repayment request;
and S402, if the accounting running state is the to-be-reported state, carrying out related sum collection according to the accounting running, and calling an account system to carry out account reporting operation.
In this embodiment, after the reimbursement operation is completed, an attempt may be made to create an accounting flow, record information in an accounting process as a voucher for the accounting operation, and further perform the accounting operation based on the accounting flow, and when the accounting flow is in a pending accounting state, sum the amounts of accounts receivable, the amount of real-time receipts, the amount of users, and the like based on the accounting flow, and call the account for the accounting operation.
Specifically, in order to ensure that S401-S402 complete accounting successfully, monitoring of the status may be performed, and specifically, as shown in fig. 7, the accounting operation may include the following processes:
s411, inquiring the accounting running water according to the repayment single number, and filtering out the accounting running water with a failed state and replaced states;
in this embodiment, if the account is failed to be reported in the account reporting operation process, the accounting flow may have errors, the state of the accounting flow may be modified to fail, and a new accounting flow is created to replace the original accounting flow. Thus, when querying the billing pipeline, the billing pipeline with the status of failed and replaced can be filtered out.
S412, judging the state of the accounting running water for the accounting running water which is not filtered out;
if the state of the bookkeeping running water is successful, returning to be successful, ending the process, and ensuring the idempotent; if the status of the accounting flow is failure, executing S413; if the state of the accounting flow is pending, executing S414;
s413, creating a new accounting flow and replacing the accounting flow in the failure state;
after the step S313 is executed, based on the new accounting flow, the step S414 is continuously executed;
s414, collecting related amounts according to the accounting streamline, and calling an account system to perform an accounting operation;
if the account is successfully reported, the account is successfully returned, otherwise, the account is unsuccessfully returned, and the process is ended.
In addition, on the basis of the above embodiment, the offset flow can be created after the offset operation is completed, and is used for recording information including but not limited to a repayment order number, an offset amount, an offset time and the like as a proof of the offset operation.
On the basis of any of the foregoing embodiments, the modifying the repayment state into the completion state through the asynchronous thread in S204 may specifically include:
modifying the billing running state, the repayment bill state and the bill state into a completion state through the asynchronous thread; in addition, the punching flow state can be modified into a finished state.
On the basis of any embodiment, if the execution of the punching operation fails in the punching process, the punching operation is performed again at regular time; if the execution of the account-reporting operation fails in the account-reporting process, the account-reporting operation is carried out again at regular time; in addition, if the execution of the substitute payment operation fails in the substitute payment process, the substitute payment operation is carried out again at regular time.
On the basis of any of the foregoing embodiments, as shown in fig. 8, the querying, by using the asynchronous thread, the to-be-revoked service ticket of the user in S203 may specifically include:
s501, attempting to acquire a user transaction lock;
and S502, after the user transaction lock is successfully acquired, inquiring the service list to be cancelled and cancelled 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 service data of the user in a distributed scenario, an attempt is made to acquire a user transaction lock when an asynchronous thread is triggered, and if the user transaction lock is successfully acquired, a subsequent inquiry of a to-be-reimbursed service ticket of the user can be continuously executed, and other services of the user cannot acquire the user transaction lock any more; if the user transaction lock acquisition fails, the attempt to acquire the user transaction lock can be performed again at regular time. Further, after the notification message of payment completion is sent to the terminal, the user transaction lock can be released, and at this time, other services can acquire the user transaction lock, so that a service process for acquiring the user transaction lock is executed.
On the basis of any of the foregoing embodiments, this embodiment provides an asynchronous flow of a service processing method, as shown in fig. 9, and includes the following specific steps:
s601, trying to acquire a user transaction lock;
if the user transaction lock is successfully acquired, executing S602; if the user transaction lock acquisition fails, the user transaction lock acquisition can be tried again at regular time;
s602, inquiring a business list to be cancelled and cancelled of a user by adopting the asynchronous thread;
s603, sequentially carrying out cancellation operation on each service bill to be cancelled according to the repayment amount of the repayment request and the preset service priority of the service bill to be cancelled;
sequentially traversing all the service sheets to be offset according to the sequence of the preset service priority from high to low to carry out offset operation until the accumulated offset amount of the service sheets to be offset, which are subjected to offset operation, reaches the repayment amount or all the service sheets to be offset are completely passed through;
s604, trying to create an impulse and marketing streamline, accounting streamline and updating a business list; if the accumulated offset amount of the service bill to be offset is smaller than the repayment amount, establishing a depreciation application bill;
wherein, if the creation of the offset flow, the accounting flow or the unique key conflict is attempted, S605 is executed; otherwise, retry regularly; when the sales rushing and marketing running water and the accounting running water are created, the creation is carried out based on the repayment single number as the unique key, namely, only one sales rushing and marketing running water and one accounting running water can exist in the same repayment single number in the same time, if the unique key conflict is found during the creation, the fact that other sales rushing and accounting running water exist currently is also shown, namely the sales rushing and marketing running water and the accounting running water are already created, and S605 can be continuously executed;
s605, performing an account reporting operation based on the established accounting running water;
if the account is successfully posted, executing S606; otherwise, the accounting operation is re-executed at regular time;
s606, carrying out depreciation operation based on the depreciation request sheet;
if the payment is successful, executing S607; otherwise, the substitute payment operation is executed again at regular time;
s607, updating the distribution flow state, the accounting flow state, the repayment bill state and the bill state to be the completion state; sending a notification message of payment completion to the terminal;
and S608, releasing the user transaction lock.
The principle and technical effect of the asynchronous flow of this embodiment can refer to the above embodiments, and are not described herein again.
Fig. 10 is a structural 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, the service processing device 700 includes a synchronous processing unit 701 and an asynchronous processing unit 702.
The synchronous processing unit 701 is used for verifying a repayment bill state and user information related to a repayment request by adopting a synchronous thread after receiving the repayment request sent by a terminal; if the verification is passed, modifying the state of the payment list into a processing state through the synchronous thread, sending a notification message in payment processing to the terminal, and triggering an asynchronous thread;
the asynchronous processing unit 702 is configured to query a to-be-flushed-out business form of a user by using the asynchronous thread, perform flushing-out operation on the to-be-flushed-out business form according to the repayment request, and call an accounting flow to perform accounting operation on the flushing-out operation; and modifying the repayment state into a completion state through the asynchronous thread, and sending a notification message of the completion of the repayment to the terminal.
On the basis of any one of the above embodiments, the service list to be cancelled is multiple; when the asynchronous processing unit 702 performs the cancellation operation on the service ticket to be cancelled according to the repayment request, it is configured to:
and sequentially carrying out cancellation operation on each service bill to be cancelled according to the repayment amount of the repayment request and the preset service priority of the service bill to be cancelled.
On the basis of any of the above embodiments, when the asynchronous processing unit 702 performs the cancellation operation on each service ticket to be cancelled in sequence according to the repayment amount of the repayment request and the preset service priority of the service ticket to be cancelled, the asynchronous processing unit is configured to:
and according to the sequence of the preset service priority from high to low, sequentially traversing each service sheet to be offset to carry out offset operation until the accumulated offset amount of the service sheets to be offset, which have been subjected to offset operation, reaches the repayment amount or all the service sheets to be offset are completely passed through.
On the basis of any of the above embodiments, the asynchronous processing unit 702 is further configured to:
and if all the service lists to be offset are completely passed through and the accumulated offset sum of each service list to be offset is smaller than the repayment sum, calling a payment substitution flow by adopting the asynchronous thread to perform payment substitution operation.
On the basis of any of the above embodiments, when the asynchronous thread is used to call a payment assistant flow to perform a payment assistant operation, the asynchronous processing unit 702 is configured to:
adopting the asynchronous thread to create a payment-on-behalf application form according to the accumulated reimbursement amount of each service form to be reimbursed and the repayment amount;
and carrying out account overfeeding payment freezing operation according to the payment requisition form, calling payment side equipment to carry out payment substitution, and carrying out account overfeeding payment unfreezing operation after successful payment substitution.
On the basis of any of the foregoing embodiments, when invoking an accounting flow to perform an accounting operation on the offset operation, the asynchronous processing unit 702 is configured to:
inquiring the accounting flow state of the repayment request;
and if the accounting running state is the to-be-reported state, carrying out related sum collection according to the accounting running and calling an account system to carry out account reporting operation.
On the basis of any of the above embodiments, when the asynchronous processing unit 702 modifies the repayment status into the completion status through the asynchronous thread, it is configured to:
and modifying the billing running state, the repayment bill state and the bill state into a completion state through the asynchronous thread.
On the basis of any of the above embodiments, when the asynchronous processing unit 702 queries the to-be-flushed service ticket of the user by using the asynchronous thread, the asynchronous processing unit is configured to:
attempting to acquire a user transaction lock; after the user transaction lock is successfully acquired, inquiring a to-be-cancelled business list of the user by adopting the asynchronous thread;
after sending the notification message of payment completion to the terminal, the asynchronous processing unit 702 is further configured to:
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 punching operation fails, the punching operation is carried out again at regular time; and/or
And if the execution of the account-posting operation fails, periodically re-performing the account-posting operation.
On the basis of any of the above embodiments, when the synchronous processing unit 701 verifies the state of the payment receipt and the user information related to the payment request by using the synchronous thread, the synchronous 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, verifying the state of the payment receipt;
if the repayment bill state is a to-be-processed state, checking the user account state;
and if the user account state is normal, the verification is passed.
The service processing device provided in the embodiment of the present invention may be specifically configured to execute the method embodiments provided in fig. 2 to 9, and specific functions are not described herein again.
According to the service processing equipment provided by the embodiment of the invention, after a repayment request sent by a terminal is received, a synchronous thread is adopted to verify a repayment bill state and user information related to the repayment request; if the verification is passed, modifying the state of the payment list into a processing state through a synchronous thread, sending a notification message in payment processing to the terminal, and triggering an asynchronous thread; adopting an asynchronous thread to inquire a business sheet to be offset of a user, carrying out offset operation on the business sheet to be offset according to a repayment request, and calling an accounting flow to carry out accounting operation on the offset operation; and modifying the repayment state into a completion state through the asynchronous thread, and sending a notification message of the completion of the repayment to the terminal. According to the embodiment, the repayment business process is divided into a synchronous part and an asynchronous part, the verification operation is executed through a synchronous thread, the complicated and tedious reimbursement operation and the account reporting operation are executed through an asynchronous thread, the situation that the time consumption is long due to the fact that the repayment business process is completely adopted by the synchronous process is avoided, the user repayment request can be responded quickly, the stability of the repayment business process is improved, the accuracy of user data is guaranteed, and the system stability and the user experience 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 in the embodiment of the present invention may execute the processing flow provided in 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 a computer program is stored in the memory 81 and is configured to be executed by the processor 82 for performing the service processing method described in the above embodiments.
The electronic device in the embodiment shown in fig. 11 may be configured to execute the technical solution of the foregoing service processing method embodiment, and the implementation principle and the technical effect are similar, which are not described herein again.
In addition, the present embodiment also provides a non-transitory computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the service processing method described in the foregoing embodiment. The non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
In addition, the present embodiment also provides a computer program product, which includes computer instructions, and when the computer instructions are executed by a processor, the service processing method described in the foregoing embodiment is implemented.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. 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 invention 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 described in the embodiments of the present invention. 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.
It is obvious to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be performed by different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to perform all or part of the above described functions. For the specific working process of the device described above, reference may be made to the corresponding process in the foregoing method embodiment, which is not described herein again.
The above embodiments are only used for illustrating the technical solutions 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, those skilled in the art will understand that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present 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 variations, 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 will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (14)
1. A method for processing a service, comprising:
after a repayment request sent by a terminal is received, verifying a repayment bill state and user information related to the repayment request by adopting a synchronous thread;
if the verification is passed, modifying the state of the payment list into a processing state through the synchronous thread, sending a notification message in payment processing to the terminal, and triggering an asynchronous thread;
inquiring a business sheet to be offset of a user by adopting the asynchronous thread, carrying out offset operation on the business sheet to be offset according to the repayment request, and calling an accounting flow to carry out accounting operation on the offset operation;
and modifying the repayment state into a completion state through the asynchronous thread, and sending a notification message of the completion of the repayment to the terminal.
2. The method of claim 1, wherein the to-be-flushed service list is plural; the canceling operation of the business order to be cancelled according to the repayment request comprises the following steps:
and sequentially carrying out cancellation operation on each service bill to be cancelled according to the repayment amount of the repayment request and the preset service priority of the service bill to be cancelled.
3. The method according to claim 2, wherein the sequentially canceling the service tickets to be cancelled according to the repayment amount of the repayment request and the preset service priority of the service tickets to be cancelled comprises:
and according to the sequence of the preset service priority from high to low, sequentially traversing each service sheet to be offset to carry out offset operation until the accumulated offset amount of the service sheets to be offset, which have been subjected to offset operation, reaches the repayment amount or all the service sheets to be offset are completely passed through.
4. The method of claim 3, further comprising:
and if all the service lists to be offset are completely passed through and the accumulated offset sum of each service list to be offset is smaller than the repayment sum, calling a payment substitution flow by adopting the asynchronous thread to perform payment substitution operation.
5. The method of claim 4, wherein said invoking a payment process with said asynchronous thread to perform a payment process comprises:
adopting the asynchronous thread to create a payment-on-behalf application form according to the accumulated reimbursement amount of each service form to be reimbursed and the repayment amount;
and carrying out account overfeeding payment freezing operation according to the payment requisition form, calling payment side equipment to carry out payment substitution, and carrying out account overfeeding payment unfreezing operation after successful payment substitution.
6. The method of claim 1, wherein invoking the reimbursement process to reimburse the reimbursement operation comprises:
inquiring the accounting flow state of the repayment request;
and if the accounting running state is the to-be-reported state, carrying out related sum collection according to the accounting running and calling an account system to carry out account reporting operation.
7. The method of claim 1, wherein modifying the repayment status to a completion status by the asynchronous thread comprises:
and modifying the billing running state, the repayment bill state and the bill state into a completion state through the asynchronous thread.
8. The method according to any one of claims 1-7, wherein said querying the user's pending cancellation business form using the asynchronous thread comprises:
attempting to acquire a user transaction lock;
after the user transaction lock is successfully acquired, inquiring a to-be-cancelled business list of the user by adopting the asynchronous thread;
after sending the notification message of payment completion to the terminal, the method further comprises:
releasing the user transaction lock.
9. The method according to any one of claims 1-7, further comprising:
if the execution of the punching operation fails, the punching operation is carried out again at regular time; and/or
And if the execution of the account-posting operation fails, periodically re-performing the account-posting operation.
10. The method according to any one of claims 1-7, wherein the verifying the repayment order status and the user information related to the repayment request by the synchronous thread comprises:
checking the login state of the user by adopting the synchronous thread;
if the user is in the login state, verifying the state of the payment receipt;
if the repayment bill state is a to-be-processed state, checking the user account state;
and if the user account state is normal, the verification is passed.
11. A traffic processing device, comprising:
the synchronous processing unit is used for verifying the repayment bill state 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 state of the payment list into a processing state through the synchronous thread, sending a notification message in payment processing to the terminal, and triggering an asynchronous thread;
the asynchronous processing unit is used for inquiring a business form to be offset of a user by adopting the asynchronous thread, carrying out offset operation on the business form to be offset according to the repayment request and calling an accounting flow to carry out accounting operation on the offset operation; and modifying the repayment state into a completion state through the asynchronous thread, and sending a notification message of the completion of the repayment to the terminal.
12. An electronic device, comprising: at least one processor; and a memory;
the memory stores computer-executable instructions;
the at least one processor executing the computer-executable instructions stored by the memory causes the at least one processor to perform the method of any one of claims 1-10.
13. A computer-readable storage medium having computer-executable instructions stored thereon which, when executed by a processor, implement the method of any one of claims 1-10.
14. A computer program product comprising computer instructions, characterized in that the computer instructions, when executed by a processor, implement the method of any of claims 1-10.
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 true CN113112344A (en) | 2021-07-13 |
| CN113112344B 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) |
Cited By (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 |
| CN114066648A (en) * | 2021-11-12 | 2022-02-18 | 粤港澳国际供应链(广州)有限公司 | Cross-service multi-service type data processing method and related equipment |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120136780A1 (en) * | 2010-08-27 | 2012-05-31 | Khalid El-Awady | Account number based bill payment platform apparatuses, methods and systems |
| CN103297247A (en) * | 2013-07-05 | 2013-09-11 | 江苏省广电有线信息网络股份有限公司南京分公司 | Broadcasting and television branch business credit control management method and system for integration of three networks |
| US20150032622A1 (en) * | 2013-07-29 | 2015-01-29 | Mastercard International Incorporated | Online credit returns method and apparatus |
| US20150324908A1 (en) * | 2014-05-06 | 2015-11-12 | Bank Of America Corporation | Dynamically modifying an application questionnaire |
| 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 |
| US20200265421A1 (en) * | 2019-02-20 | 2020-08-20 | Capital One Services, Llc | Systems and methods for payment collection from third party source |
| 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 |
-
2021
- 2021-04-21 CN CN202110432556.8A patent/CN113112344B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120136780A1 (en) * | 2010-08-27 | 2012-05-31 | Khalid El-Awady | Account number based bill payment platform apparatuses, methods and systems |
| CN103297247A (en) * | 2013-07-05 | 2013-09-11 | 江苏省广电有线信息网络股份有限公司南京分公司 | Broadcasting and television branch business credit control management method and system for integration of three networks |
| US20150032622A1 (en) * | 2013-07-29 | 2015-01-29 | Mastercard International Incorporated | Online credit returns method and apparatus |
| US20150324908A1 (en) * | 2014-05-06 | 2015-11-12 | Bank Of America Corporation | Dynamically modifying an application questionnaire |
| CN109636369A (en) * | 2018-11-02 | 2019-04-16 | 深圳市快付通金融网络科技服务有限公司 | Fund account accounting processing method, apparatus, computer equipment and storage medium |
| US20200265421A1 (en) * | 2019-02-20 | 2020-08-20 | Capital One Services, Llc | Systems and methods for payment collection from third party source |
| 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 |
Cited By (3)
| 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 |
| CN114066648A (en) * | 2021-11-12 | 2022-02-18 | 粤港澳国际供应链(广州)有限公司 | Cross-service multi-service type data processing method and related equipment |
| CN114066648B (en) * | 2021-11-12 | 2022-07-26 | 粤港澳国际供应链(广州)有限公司 | Cross-service multi-service type data processing method and related equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113112344B (en) | 2024-04-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110009338B (en) | Accounting method and device based on block chain and electronic equipment | |
| US20120185378A1 (en) | System and Method for Adaptive Selection of Bank Card for Payment | |
| CN107358524B (en) | Method for leveling funds among multiple account management lines in same currency | |
| CN103136276A (en) | System, method and device of verification of data | |
| CN110910230A (en) | Accounting method, accounting system and storage medium | |
| CN113112344A (en) | Business processing method, device, storage medium and computer program product | |
| CN109491765B (en) | Method and device for processing cross-domain service request | |
| CN110659887A (en) | Automatic transaction processing system and method based on block chain | |
| CN109859043A (en) | A kind of exchange settlement method and trade clearing system | |
| CN102622821A (en) | Method, device and system for supporting large amount of self-service withdrawal | |
| WO2015135322A1 (en) | Self-service terminal service emergency method and site server | |
| CN103218449B (en) | Form is operation exception disposal route and system in the daytime | |
| CN109614263B (en) | Disaster tolerance data processing method, device and system | |
| CN115439224B (en) | Method, system and equipment for counting large inventory | |
| CN110634066A (en) | Method, device and equipment for determining settlement interest | |
| CN110827001A (en) | Accounting event bookkeeping method, system, equipment and storage medium | |
| CN113919835A (en) | Business processing method, device, storage medium and computer program product | |
| CN112099934A (en) | Batch processing method, system, computer equipment and storage medium | |
| CN106971339B (en) | Service processing method and device | |
| CN114971637A (en) | Risk early warning method, device, equipment and medium | |
| CN111429125B (en) | Account management method and device, storage medium and electronic equipment | |
| CN111461798B (en) | Big data-based ticket business processing method, device, medium and equipment for individual user | |
| CN112561672A (en) | Accounting data processing system, method, device, equipment and computer readable medium | |
| CN110084692A (en) | A kind of bookkeeping methods and device | |
| CN111061573A (en) | Resource transfer method, device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information |
Address after: 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 |