Loan amount processing method, loan server and storage medium

Abstract

The invention provides a loan amount processing method, a loan server and a storage medium. And the loan server receives a quota allocation request from a first terminal device corresponding to the first subject, wherein the quota allocation request is used for requesting to allocate at least part of the available quota of the second subject to the first subject. The loan server generates an authorization task based on the quota allocation request, sends the authorization task to a second terminal device corresponding to a second subject, and receives an execution result of the authorization task from the second terminal device, and the authorization task is used for inquiring whether the second subject agrees to allocate the quota to the first subject. And furthermore, under the condition that the execution result represents agreement, the loan server determines a target quota which the second subject agrees to allocate to the first subject, allocates the target quota to a first loan account of the first subject, and reduces the target quota in available quota of the second subject.

Description

TECHNICAL FIELD

[0001] The present specification relates to the technical field of Internet, and particularly relates to a loan quota processing method, a loan server and a storage medium. BACKGROUND

[0002] During the operation process, enterprises often face the demand for loan financing. For example, for enterprises engaged in cross-border trade, due to the characteristics of cross-border trade such as long logistics time, long customs audit time, long trade risk audit time, etc., the enterprises engaged in cross-border trade have a long account period, which is prone to short-term capital shortage problems and cannot respond to market demand (such as advance stock preparation, etc.). In this case, these enterprises expect to finance from financial institutions to alleviate the above-mentioned capital flow problems. However, some enterprises (especially small and medium-sized enterprises or start-ups) are difficult to meet the credit evaluation standards of financial institutions due to low credit scores, resulting in loan applications being rejected.

[0003] To solve this problem, these actual loan enterprises usually seek help from third-party subjects (such as guarantee institutions, associated enterprises or large groups with good credit). For example, the third-party subject initiates a loan application to the financial institution with its credit qualification, and after the funds are approved, the third-party subject transfers the loan funds to the actual loan enterprise. The actual loan enterprise repays the funds to the third-party subject according to the agreement, and the third-party subject performs the repayment obligation to the financial institution. However, in the above-mentioned manner, the loan funds need to be transferred in sequence through multiple nodes (financial institution, third-party subject, actual loan enterprise), which has the problems of long transfer link and low loan efficiency. In addition, the financial institution cannot understand the loan behavior of the actual loan subject, which leads to the fact that the financial institution cannot effectively control and manage the loan funds.

[0004] The contents of the background art section are only for the purpose of enhancing the understanding of the background of the present disclosure and should not be considered as admitting that the contents provided in the background art section are prior art of the present disclosure. SUMMARY

[0005] The present specification provides a loan processing method, a loan server and a storage medium. In the case that the second subject authorizes, the quota in the quota pool can be allocated to the first subject, which not only can improve the loan efficiency of the first subject, but also helps the financial institution to effectively control and manage the funds.

[0006] In a first aspect, the present specification provides a processing method of a loan amount, applied to a loan server, the method comprising: receiving, from a first terminal device corresponding to a first principal, an amount allocation request, the amount allocation request being used to request allocation of at least part of an available amount of a second principal to the first principal; generating an authorization task based on the amount allocation request, wherein the authorization task is used to inquire whether the second principal agrees to allocate the amount to the first principal; sending the authorization task to a second terminal device corresponding to the second principal, and receiving an execution result of the authorization task from the second terminal device; and in the case that the execution result represents agreement, determining a target amount that the second principal agrees to allocate to the first principal, allocating the target amount to a first loan account of the first principal, and reducing the target amount in the available amount of the second principal.

[0007] In some embodiments, the second principal corresponds to at least one second loan account, and the at least one second loan account includes a target loan account of a sharing type; and the authorization task is used to inquire whether the second principal agrees to allocate an available amount in the target loan account to the first principal.

[0008] In some embodiments, the method further comprises: receiving, from the second terminal device, a loan request including at least qualification information corresponding to the second principal, the loan request being used to apply for a loan amount that can be shared with other principals; and in the case that it is determined based on the qualification information that the second principal satisfies a loan condition, determining a loan amount corresponding to the second principal, generating the target loan account for the second principal, setting the loan amount as an available amount of the target loan account, and setting a type of the target loan account as a sharing type.

[0009] In some embodiments, the loan request further includes trade voucher information between the second principal and at least one other principal; and after the target loan account is generated for the second principal, the method further comprises: binding the target loan account with the at least one other principal, so that the at least one other principal has an amount sharing right to the target loan account.

[0010] In some embodiments, generating the authorization task based on the amount allocation request comprises: determining whether the first principal has an amount sharing right to the target loan account; and in the case that the first principal has the amount sharing right to the target loan account, generating the authorization task based on the amount allocation request.

[0011] In some embodiments, the quota allocation request at least includes trade voucher information between the first principal and the second principal, and determining whether the first principal has the quota sharing permission for the target loan account includes: obtaining the trade voucher information from the quota allocation request, and determining a trade relationship closeness between the first principal and the second principal based on the trade voucher information; and determining whether the first principal has the quota sharing permission for the target loan account based on the trade relationship closeness.

[0012] In some embodiments, the target loan account is pre-bound with at least one candidate principal, and determining whether the first principal has the quota sharing permission for the target loan account includes: if the first principal is included in the at least one candidate principal, determining that the first principal has the quota sharing permission for the target loan account; or if the first principal is not included in the at least one candidate principal, determining that the first principal does not have the quota sharing permission for the target loan account.

[0013] In some embodiments, after the authorization task is generated, the method further includes: generating an access link corresponding to the authorization task, and sending the access link to the first terminal device, so that the first terminal device forwards the access link to the second terminal device; and sending the authorization task to a second terminal device corresponding to the second principal, including: in response to receiving an access request for the access link from the second terminal device, sending the authorization task to the second terminal device.

[0014] In some embodiments, after the access link corresponding to the authorization task is generated, the method further includes: setting a valid period range of the access link; and sending the authorization task to the second terminal device, including: in a case where the current time is within the valid period range, sending the authorization task to the second terminal device.

[0015] In some embodiments, the method further includes: in a case where the current time is outside the valid period range, sending first prompt information to the second terminal device, the first prompt information being used to prompt that the authorization task has expired.

[0016] In some embodiments, the quota allocation request includes a first quota requested by the first principal to be allocated, and the authorization task is used to inquire whether the second principal agrees to allocate the first quota to the first principal; and determining that the second principal agrees to allocate a target quota to the first principal includes: determining the first quota as the target quota.

[0017] In some embodiments, in a case where the execution result represents consent, the second subject agrees to allocate a second amount to the first subject in the execution result; and determining the target amount allocated to the first subject by the second subject comprises determining the second amount as the target amount.

[0018] In some embodiments, after allocating the target amount to the first loan account of the first subject, the method further comprises: receiving a spending request corresponding to the first loan account from the first terminal device; determining a first amount requested by the first subject for spending based on the spending request, and determining a spending account of the first subject; and transferring funds corresponding to the first amount to the spending account of the first subject, and reducing the corresponding amount in the available amount of the first loan account.

[0019] In some embodiments, after transferring funds corresponding to the first amount to the spending account of the first subject, the method further comprises: receiving a repayment request from the first terminal device; and based on the repayment request, deducting at least part of the funds from the repayment account of the first subject for repayment, and increasing the corresponding amount in the available amount of the first loan account based on the amount of the repayment funds.

[0020] In some embodiments, after transferring funds corresponding to the first amount to the spending account of the first subject, the method further comprises at least one of the following: in a case where it is detected that the funds corresponding to the first amount are approaching a repayment deadline, sending second prompt information to the first terminal device, the second prompt information being used to prompt the first subject to make a repayment; in a case where it is detected that the funds corresponding to the first amount are approaching a repayment deadline, sending third prompt information to the second terminal device, the third prompt information being used to prompt the second subject to make a repayment, or to prompt the second subject to urge the first subject to make a repayment; in a case where it is detected that the funds corresponding to the first amount have reached a repayment deadline, deducting at least part of the funds from the repayment account of the first subject for repayment, and increasing the corresponding amount in the available amount of the first loan account based on the amount of the repayment funds; or in a case where it is detected that the funds corresponding to the first amount have reached a repayment deadline and the funds in the repayment account of the first subject are insufficient for repayment, deducting at least part of the funds from the repayment account of the second subject for repayment, and increasing the corresponding amount in the available amount of the first loan account based on the amount of the repayment funds.

[0021] In some embodiments, after receiving the execution result, the method further comprises: in a case where the execution result represents disagreement, sending fourth prompt information to the first terminal device, the fourth prompt information being used to prompt the first subject that the allocation of the amount has failed.

[0022] In a second aspect, the present specification also provides a loan server, comprising: at least one storage medium, storing at least one instruction set; and at least one processor, communicatively connected with the at least one storage medium, wherein the at least one processor reads the at least one instruction set when running, and executes the method according to any one of the above first aspect according to the indication of the at least one instruction set.

[0023] In a third aspect, the present specification also provides a computer-readable non-transitory storage medium, wherein the computer-readable non-transitory storage medium stores at least one instruction set, and the at least one instruction set is executed by at least one processor to implement the method according to any one of the above first aspect.

[0024] Other functions of the loan limit processing method, the loan server and the storage medium provided by the present specification will be partially listed in the following description. The creative aspects of the loan limit processing method, the loan server and the storage medium provided by the present specification can be fully explained by practicing or using the methods, devices and combinations described in the following detailed examples. BRIEF DESCRIPTION OF DRAWINGS

[0025] In order to more clearly illustrate the technical solutions in the embodiments of the present specification, the following will briefly introduce the drawings needed to be used in the embodiment description. Obviously, the drawings in the following description are only some embodiments of the present specification, and other drawings can also be obtained by those skilled in the art without creative labor.

[0026] Figure 1 A schematic diagram of a loan scenario provided by an embodiment of the present specification is shown; Figure 2 An architecture diagram of an implementation system of a loan scenario provided by an embodiment of the present specification is shown; Figure 3 A hardware structure schematic diagram of a computing device provided by an embodiment of the present specification is shown; Figure 4 A flowchart of a loan limit processing method provided by an embodiment of the present specification is shown; Figure 5 A schematic diagram of a set of interactive pages provided by an embodiment of the present specification is shown; Figure 6 A schematic diagram of another set of interactive pages provided by an embodiment of the present specification is shown; Figure 7 A schematic diagram of still another set of interactive pages provided by an embodiment of the present specification is shown; Figure 8A schematic diagram of credit allocation provided according to embodiments of the present specification is shown. DETAILED DESCRIPTION

[0027] The following description provides specific applications and requirements of the present specification, which is intended to enable a person skilled in the art to manufacture and use the contents of the present specification. Various local modifications of the disclosed embodiments are obvious to those skilled in the art, and the general principles defined herein can be applied to other embodiments and applications without departing from the spirit and scope of the present specification. Therefore, the present specification is not limited to the embodiments shown, but is consistent with the widest scope of the claims.

[0028] The terms used herein are only for the purpose of describing specific example embodiments, and are not limiting. For example, unless the context clearly indicates otherwise, as used herein, the singular forms "a", "an", and "the" can also include the plural forms. When used in the present specification, the terms "include", "contain" and / or "have" mean that the associated integers, steps, operations, elements and / or components exist, but do not exclude the presence of one or more other features, integers, steps, operations, elements, components and / or groups.

[0029] In the present specification, "X includes at least one of A, B or C" means that X includes at least A, or X includes at least B, or X includes at least C. That is, X can include only any one of A, B, C, or any combination of A, B, C, and other possible contents / elements. The combination of A, B, C can be A, B, C, AB, AC, BC, or ABC.

[0030] These features of the present specification and other features, as well as the operation and function of related elements of the structure, and the economy of combination and manufacture of components can be significantly improved in view of the following description. Referring to the drawings, all of which form part of the present specification. However, it should be clearly understood that the drawings are for illustrative and descriptive purposes only and are not intended to limit the scope of the present specification. It should also be understood that the drawings are not drawn to scale.

[0031] The flowchart used in the present specification shows the operation of system implementation according to some embodiments of the present specification. It should be clearly understood that the operations of the flowchart can not be implemented in sequence. On the contrary, the operations can be implemented in reverse order or simultaneously. In addition, one or more other operations can be added to the flowchart. One or more operations can be removed from the flowchart.

[0032] The technical solutions provided by the present specification are applicable to loan scenarios. The following describes the technical solutions provided by the present specification in conjunction with Figure 1The application scenarios applicable to the present specification are exemplified.

[0033] Figure 1 A schematic diagram of a loan scenario provided according to an embodiment of the present specification is shown, as Figure 1 indicated, the application scenario 100 can include a financial institution 150, a second principal 130, and at least one first principal 110 (for example, principal A, principal B, principal C, etc.).

[0034] Among them, the financial institution 150 refers to a lender that provides credit and loan services to the first principal 110 and the second principal 130. The financial institution 150 includes but is not limited to banks, securities companies, insurance companies, trust companies, payment institutions, fund management companies, financial leasing companies, etc.

[0035] The first principal 110 and the second principal 130 are both borrowers, and are the party that requests a loan from the financial institution 150. It should be noted that the first principal 110 and the second principal 130 can be individuals, enterprises, or even countries, etc., and the present specification does not limit this. When such principals apply for a loan from the financial institution, they become the object of evaluation. The financial institution evaluates the financial status, credit information, asset and liability information, income and expenditure of these principals to determine the specific credit conditions (such as interest rate, term, limit, etc.). In some embodiments, the second principal 130 can be a principal who meets the credit evaluation standards of the financial institution 150, and the first principal 110 can be a principal who does not meet the credit evaluation standards of the financial institution 150. In the present specification, the first principal 110 and the second principal 130 can both be referred to as loan principals, credit principals, borrower principals, etc.

[0036] Referring to Figure 1 , the second principal 130 can initiate a credit application to the financial institution 150 based on its credit qualification, and obtain a limit pool after being approved by the financial institution 150.

[0037] In some embodiments, the way the second principal 130 requests credit from the financial institution 150 can include but is not limited to the following ways: (1) Letter of credit. The letter of credit is a payment commitment tool that the second principal 130 applies to the financial institution 150 based on its good credit qualification. The financial institution 150 approves the letter of credit credit limit for the second principal 130 after approval. When a transaction occurs, the second principal 130 can designate the first principal 110 or other transaction counterparties as the beneficiary of the letter of credit. As long as the beneficiary submits documents in accordance with the terms of the letter of credit, the financial institution 150 assumes the payment responsibility and pays the corresponding amount to the beneficiary as agreed.

[0038] (2) Trade finance loan. The trade finance loan refers to that the second principal 130 (the buyer or the seller) applies for short-term financing to the financial institution 150 based on the real trade contract between the second principal 130 and the transaction counterparty. The financial institution 150 approves the credit limit according to the credit status, transaction background and repayment ability of the second principal 130 and other factors, and provides corresponding loan fund support to the second principal 130 within the credit limit after the credit approval.

[0039] (3) Accounts receivable factoring. The accounts receivable factoring refers to that the second principal 130 transfers the accounts receivable to the financial institution 150 to obtain early repayment. The financial institution 150 approves the corresponding factoring limit according to the quality of the accounts receivable, the credit status of the transaction counterparty and the credit level of the second principal 130, and provides financing support for the second principal 130 within the limit.

[0040] (4) Buyer credit. The buyer credit refers to that the financial institution 150 directly issues a loan to the buyer to pay the seller. That is, the second principal 130 as the buyer applies for short-term financing to the financial institution 150 to support the transaction based on the trade contract between the second principal 130 and the seller. The financial institution 150 allocates a special limit to the second principal 130 according to the credit status, transaction background and repayment ability of the second principal 130. Thus, the second principal 130 pays the seller by using the special limit. With reference to Figure 1 , the limit in the limit pool obtained by the second principal 130 can be shared by one or more first principals 110. In the case that the second principal 130 authorizes, the limit in the limit pool can be allocated to one or more first principals 110. For example, in combination with Figure 1 , the financial institution 150 can allocate a part of the credit limit in the limit pool to principal A, another part of the credit limit to principal B, and another part of the credit limit to principal C. On this basis, each first principal 110 can directly use funds from the financial institution 150 based on the limit allocated to the first principal 110. In some embodiments, the second principal 130 can also directly use funds from the financial institution 150 based on the limit in the credit limit pool.

[0041] Compared with the way that the second principal 130 first uses funds from the limit pool and then transfers the funds to the first principal 110, the technical solution provided in the specification can shorten the fund circulation path and improve the loan efficiency of the first principal 110. In addition, since the limit of the first principal 110 is allocated by the financial institution 150, and the first principal 110 directly uses funds from the financial institution 150, the financial institution 150 can understand the actual fund use behavior of the first principal 110, thereby being able to effectively manage and control the funds.

[0042] Figure 1In the illustrated scenario, the credit pool that the second principal 130 obtains through the credit granting process is a shared credit pool, and the credit in the credit pool can be shared and used by multiple first principals 110. If the shared credit pool solution is not adopted, the second principal 130 needs to help the first principal 110 apply for credit to the financial institution 150 every time the first principal 110 makes a request, and provide the credit obtained through the credit granting to the first principal 110. In the case where multiple first principals 110 seek help from the second principal 130, the second principal 130 needs to apply for credit to the financial institution 150 multiple times, and needs to submit transaction contracts, credit references, financial statements, and the like to the financial institution 150 every time the credit granting process is performed. In the case where the shared credit pool solution is adopted, the second principal 130 applies for credit to the financial institution 150 once, and obtains a credit pool that can be shared and used by multiple first principals 110, thereby avoiding repeated initiation of the credit granting process by the second principal 130 and avoiding multiple submission of proof materials by the second principal 130 to the financial institution 150.

[0043] It should be noted that the first principal 110 and the second principal 130 can have a trade relationship or can not have a trade relationship, and the trade relationship between the two is not limited. When the two have a trade relationship, the trade relationship can be a cross-border trade relationship or a non-cross-border trade relationship. In addition, when the two have a trade relationship, the direction of the trade relationship can be arbitrary, for example, the second principal 130 can sell goods or provide services to the first principal 110, or the first principal 110 can supply goods or perform a contract to the second principal 130. Figure 2 An architecture diagram of an implementation system 200 of the loan scenario 100 provided according to an embodiment of the present specification is shown. As shown in the figure, the implementation system 200 can include a loan server 160, a second terminal device 140, and at least one first terminal device 120. Figure 1

[0044] The first terminal device 120 refers to a terminal device corresponding to the first principal 110. For example, the first principal 110-A corresponds to the first terminal device 120-A, the first principal 110-B corresponds to the first terminal device 120-B, and the first principal 110-C corresponds to the first terminal device 120-C. The first principal 110 can submit a credit allocation request to the loan server 160 through the first terminal device 120 to request allocation of at least part of the available credit of the second principal 130 to the first principal 110. The first principal 110 can also view and manage the credit information allocated by the loan server 160 through the first terminal device 120.

[0045] ​The second terminal device 140 refers to a terminal device corresponding to the second principal 130. The second principal 130 can initiate a loan request to the loan server 160 through the second terminal device 140, so that the loan server 160 grants a certain loan limit (i.e., a shared limit pool) to the second principal 130. The second principal 130 can also view the loan limit obtained by the second principal 130 through the second terminal device 140, and manage the allocation and use of the loan limit. For example, the second principal 130 can also execute an authorization task through the second terminal device 140 to authorize the loan server 160 to allocate part of the shared limit pool to the first principal 110.

[0046] In this specification, the terminal device (the first terminal device 120, the second terminal device 140) can include a mobile device, a tablet computer, a notebook computer, a built-in device of a motor vehicle, or the like, or any combination thereof. In some embodiments, the mobile device can include a smart home device, a smart mobile device, a virtual reality device, an augmented reality device, or the like, or any combination thereof. In some embodiments, the smart home device can include a smart television, a desktop computer, or the like, or any combination thereof. In some embodiments, the smart mobile device can include a smartphone, a personal digital assistant, a game device, a navigation device, or the like, or any combination thereof. In some embodiments, the virtual reality device or the augmented reality device can include a virtual reality headset, a virtual reality glasses, a virtual reality handle, an augmented reality headset, an augmented reality glasses, an augmented reality handle, or the like, or any combination thereof. For example, the virtual reality device or the augmented reality device can include smart glasses, a head-mounted display, VR, or the like. In some embodiments, the built-in device in the motor vehicle can include an on-board computer, an on-board television, or the like.

[0047] In some embodiments, the terminal device can be installed with a client of a target application. The client can provide the first principal 110 or the second principal 130 with the ability and interface to interact with the loan server 160. In this case, the loan server 160 can be regarded as a server of the target application. The target application can be any application program that provides a loan service.

[0048] The loan server 160 refers to a server deployed by the financial institution 150 to support data processing and interaction of credit approval, loan issuance, quota management, and various financial services. The loan server 160 can be in communication connection with the first terminal device 120 and the second terminal device 140 respectively. The loan server 160 can receive a quota allocation request from the first terminal device 120. The quota allocation request is used to request to allocate at least part of the available quota of the second principal 130 to the first principal 110. After receiving the quota allocation request, the loan server 160 can generate an authorization task based on the quota allocation request. The authorization task is used to confirm with the second principal 130 whether to agree to allocate part of the available quota of the second principal 130 to the first principal 110. Subsequently, the loan server 160 can send the authorization task to the second terminal device 140 and receive the execution result of the authorization task from the second terminal device 140. In the case where the execution result represents an agreement, the loan server 160 can determine that the second principal 130 agrees to the target quota allocated to the first principal 110, and allocate the target quota to the first loan account of the first principal 110 and reduce the target quota in the available quota of the second principal 130.

[0049] The loan processing method described later in this specification can be executed on the loan server 160. At this time, the loan server 160 can store data or instructions for implementing the loan processing method and can execute or be used to execute the data or instructions. In some embodiments, the loan server 160 can include a hardware device with data information processing function and the necessary programs required to drive the hardware device to work.

[0050] In this specification, the first terminal device 120 and the loan server 160, and the second terminal device 140 and the loan server 160 can be connected through a network. The network can facilitate the exchange of information or data. In some embodiments, the network can be any type of wired or wireless network, or a combination thereof. For example, the network can include a cable network, a wired network, a fiber-optic network, a telecommunication communication network, an intranet, the Internet, a local area network (LAN), a wide area network (WAN), a wireless local area network (WLAN), a metropolitan area network (MAN), a public switched telephone network (PSTN), a Bluetooth network, a ZigBee network, a near-field communication (NFC) network, or a similar network. In some embodiments, the network can include one or more network access points. For example, the network can include wired or wireless network access points, such as base stations or Internet exchange points, through which one or more components of the first terminal device 130, the second terminal device 140, and the loan server 160 can connect to the network to exchange data or information.

[0051] It should be understood that, Figure 2The number of the first terminal device 120, the second terminal device 140, and the loan server 160 in the system is only illustrative. According to the implementation needs, there can be any number of the first terminal device 120, the second terminal device 140, and the loan server 160.

[0052] Figure 3 A hardware structure diagram of a computing device 300 is shown according to an embodiment of the present specification. The computing device 300 can be used as Figure 1 The loan server 150 in the system can execute the processing method of the loan limit described in the present specification.

[0053] As shown in Figure 3 The computing device 300 can include at least one storage medium 230 and at least one processor 220. In some embodiments, the computing device 300 can further include a communication port 250 and an internal communication bus 210. The computing device 300 can further include an I / O component 240.

[0054] The internal communication bus 210 can connect different system components. For example, the internal communication bus 210 can connect the storage medium 230, the processor 220, the communication port 250, and the I / O component 240, etc.

[0055] The I / O component 240 supports the input / output between the computing device 300 and other components.

[0056] The communication port 250 is used for data communication between the computing device 300 and the outside world. For example, the communication port 250 can be used for data communication between the computing device 300 and a wireless network. The communication port 250 can be a wired communication port or a wireless communication port.

[0057] The storage medium 230 can include a data storage device. The data storage device can be a computer-readable non-transitory storage medium or a computer-readable transitory storage medium. For example, the data storage device can include one or more of a disk 232, a read-only memory (ROM) 234, or a random access memory (RAM) 236. The storage medium 230 further includes at least one instruction set stored in the data storage device. The instruction set can include computer program code, which can include programs, routines, objects, components, data structures, procedures, modules, etc. The storage medium 230 stores at least one instruction set, which is computer program code. These instruction sets can instruct the processor to complete specific functions or steps when the instruction sets are called and executed by the processor, such as various methods and steps to be introduced later in the present application.

[0058] The at least one processor 220 can be communicatively connected with the at least one storage medium 230. When the computing device 300 is running, the at least one processor 220 reads the at least one set of instructions and performs the methods and steps provided in the present specification according to the instructions of the at least one set of instructions. The processor 220 can be in the form of one or more processors, and in some embodiments, the processor 220 can include one or more hardware processors, such as a microcontroller, a microprocessor, a reduced instruction set computer (RISC), an application specific integrated circuit (ASIC), an application specific instruction set processor (ASIP), a central processing unit (CPU), a graphics processing unit (GPU), a physics processing unit (PPU), a microcontroller unit, a digital signal processor (DSP), a field programmable gate array (FPGA), an advanced RISC machine (ARM), a programmable logic device (PLD), any circuit or processor capable of executing one or more functions, or the like, or any combination thereof.

[0059] For the sake of illustration only, the computing device 300 in the accompanying drawings shows only one processor 220. However, it should be noted that the computing device 300 in the present specification can also include multiple processors, and therefore, the operations and / or method steps disclosed in the present specification can be performed by one processor or jointly performed by multiple processors. For example, if the processor 220 of the computing device 300 is described in the present specification to perform step A and step B, it should be understood that step A and step B can also be performed jointly or separately by two different processors 220 (for example, a first processor performs step A, and a second processor performs step B, or the first and second processors jointly perform steps A and B).

[0060] Figure 4 A flowchart of a processing method P400 of a loan limit according to an embodiment of the present specification is shown. As before, the loan server can perform the processing method P400 of the loan limit described in the present specification. Specifically, the processor in the loan server can read the instruction set stored in its local storage medium, and then perform the processing method P400 of the loan limit of the present specification according to the provisions of the instruction set. As shown in the accompanying drawings, Figure 4 The processing method P400 of the loan limit can include S420-S480.

[0061] S420: The loan server receives a limit allocation request from a first terminal device corresponding to a first principal, the limit allocation request being used to request to allocate at least part of the available limit of a second principal to the first principal.

[0062] The available amount of the second principal refers to the remaining available amount of the loan amount that the loan server (a financial institution) has granted to the second principal. It is understood that before S420, the second principal has previously applied for a certain loan amount to the loan server.

[0063] When the first principal wants to share / use the available amount of the second principal, the first principal can initiate an amount allocation request through the first terminal device, so as to request the loan server to allocate at least part of the available amount of the second principal to the first principal.

[0064] In some embodiments, the amount allocation request can include one or more of the name of the second principal, the first amount of the requested allocation, the expected use period, the fund use, etc.

[0065] For example, Figure 5 A schematic diagram of a set of interactive pages provided according to an embodiment of the present specification is shown. The set of interactive pages can be the interactive pages of the first terminal device. As shown in Figure 5 The first terminal device shows page 510 to the first principal. Page 510 can display the current available amount of the first principal (for example, Figure 5 the current available amount of the first principal is 0 in the above), and can also display an entry (for example, the control "I want to use other people's amount") for requesting to use the amount of others. When the first principal clicks the control "I want to use other people's amount", the first terminal device shows page 520. In page 520, the first principal can input the name of the second principal (for example, Bbb), and can also input the first amount of the requested allocation (for example, 200,000), the use period (for example, three months), the fund use description (for example, to purchase goods), etc. Further, the first terminal device generates an amount allocation request when detecting that the first principal clicks the "submit" button in page 520, and sends the amount allocation request to the loan server through the network. Thus, the loan server receives the amount allocation request from the first terminal device.

[0066] S440: The loan server generates an authorization task based on the amount allocation request, the authorization task being used to inquire whether the second principal agrees to allocate the amount to the first principal.

[0067] In the present specification, in the case that the loan server receives the amount allocation request initiated by the first principal, the loan server needs to obtain the authorization of the second principal. Only in the case that the authorization of the second principal is obtained (i.e., the second principal agrees to share the amount of the first principal), the loan server can allocate the amount of the second principal to the first principal. Therefore, in S420, the loan server can generate an authorization task based on the amount allocation request, the authorization task being used to inquire whether the second principal agrees to allocate the amount to the first principal, or in other words, to inquire whether the second principal agrees to share the available amount of the second principal with the first principal.

[0068] Before S420, the second principal can correspond to one or more loan accounts, which are not limited in the specification. For the convenience of description, the loan account corresponding to the second principal is referred to as the second loan account in the following description. The second principal can correspond to at least one second loan account. In some embodiments, the authorization task generated by the loan server is used to inquire whether the second principal agrees to allocate the available quota of any second loan account to the first principal.

[0069] In some embodiments, the loan account can be divided into a shared type and a non-shared type (i.e., a private type). The shared type means that the quota of the loan account can be shared and used by the second principal and other principals. The non-shared type means that the quota of the loan account can only be used by the second principal and cannot be used by other principals. The at least one second loan account includes a target loan account of the shared type. The authorization task generated by the loan server is used to inquire whether the second principal agrees to allocate the available quota in the target loan account to the first principal.

[0070] In some embodiments, referring to Figure 4 Before S420, P400 can further include S410: the loan server performs a credit granting process to allocate a loan quota to the second principal. By performing S410, the loan server can generate a target loan account for the second principal and determine the loan quota of the target loan account. Details are described below.

[0071] For example, the second principal can initiate a loan request through a second terminal device. After detecting the loan request initiated by the second principal, the second terminal device sends the loan request to the loan server. The loan server receives the loan request from the second terminal device. The loan request is used to apply for a loan quota that can be shared with other principals.

[0072] The loan request at least includes qualification proof information corresponding to the second principal, such as identity proof, credit report, income and expense proof, asset status, and the like. These qualification proof information can be used by the loan server to verify the legality of the second principal and assess the repayment ability of the second principal, so as to determine whether the second principal meets the loan conditions.

[0073] After receiving the loan request, the loan server determines whether the second principal meets the loan conditions based on the qualification proof information. Specifically, the loan server analyzes and evaluates the qualification proof information submitted by the second principal in detail to obtain an evaluation result. The evaluation content includes but is not limited to credit score, income and expense level, debt situation, historical loan record, and asset proof, and the like. Then, the loan server determines whether the second principal meets the loan conditions based on the evaluation result.

[0074] In a case where the evaluation result indicates that the second principal does not meet the loan condition, the loan server can reject the loan request of the second principal or require the second principal to supplement materials.

[0075] In a case where the evaluation result indicates that the second principal meets the loan condition, the loan server can determine a loan amount corresponding to the second principal according to the aforementioned evaluation result. Further, the loan server generates a target loan account for the second principal, sets the available amount of the target loan account as the loan amount, and sets the type of the target loan account as a shared type. The setting of the type of the target loan account as the shared type means that the amount in the target loan account can be shared and used with other principals.

[0076] In some embodiments, the loan request initiated by the second principal can further include trade credential information between the second principal and at least one other principal. The trade credential information can include, but is not limited to, a purchase and sale contract, an order agreement, an invoice document, a logistics document, and other materials that can prove the existence of a real trading relationship between the two parties. Through the trade credential information, the loan server can know which principals have trade relations with the second principal. In this case, after generating the target loan account for the second principal, the loan server can further bind the target loan account with the at least one other principal, so that the at least one other principal has the sharing right of the amount in the target loan account.

[0077] For example, assuming that the loan request initiated by the second principal includes trade credential information between the second principal and principal A, the loan server binds the target loan account with principal A. In this case, principal A has the sharing right of the amount in the target loan account. Assuming that the loan request initiated by the second principal includes trade credential information between the second principal and principal A, principal B, and principal C, the loan server binds the target loan account with principal A, principal B, and principal C. In this case, principal A, principal B, and principal C all have the sharing right of the amount in the target loan account.

[0078] In some embodiments, after receiving the quota allocation request, the loan server can first obtain at least one second loan account of the second subject. Specifically, after receiving the quota allocation request, the loan server can query the at least one second loan account of the second subject from the internal account system according to the identification information of the second subject carried in the quota allocation request. The identification information of the second subject includes a subject ID, an ID number, and the like. Further, the loan server determines whether there is a target loan account of a sharing type in the at least one second loan account. If there is a target loan account of a sharing type, the loan server can generate an authorization task based on the relevant information of the target loan account (at this time, the authorization task is used to inquire whether the second subject agrees to allocate the available quota of the target loan account to the first subject). If there is no target loan account of a sharing type, the loan server can send prompt information to the first terminal device to prompt the first subject that the quota allocation fails, and the reason for the failure is that the second subject does not have a similar shared loan account.

[0079] In some embodiments, if there is a target loan account of a sharing type in the at least one second loan account, the loan server can further determine whether the first subject has the quota sharing right of the target loan account. In the case where the first subject has the quota sharing right of the target loan account, the loan server generates an authorization task based on the quota allocation request.

[0080] For example, the quota allocation request initiated by the first subject can also include trade voucher information between the first subject and the second subject. The trade voucher information includes, but is not limited to, a purchase and sale contract, a transaction order, an invoice record, logistics information, and the like. In this case, the loan server can obtain the trade voucher information from the quota allocation request and determine the trade relationship tightness between the first subject and the second subject based on the trade voucher information. For example, the loan server can comprehensively analyze the transaction frequency, the transaction amount, the cooperation duration, and the performance between the first subject and the second subject, thereby determining the trade relationship tightness between the first subject and the second subject. Further, the loan server can determine whether the first subject has the quota sharing right of the target loan account based on the trade relationship tightness. For example, when the trade relationship tightness is high, the loan server determines that the first subject has the quota sharing right of the target loan account; when the trade relationship tightness is low, the loan server determines that the first subject does not have the quota sharing right of the target loan account.

[0081] For example, the target loan account is pre-bound with at least one candidate subject (see the description above, the second subject can carry trade credential information between the second subject and at least one other subject in the loan request when initiating the loan request. In this case, the loan server binds the target loan account with the other subjects after generating the target loan account for the second subject). In this case, the loan server can check whether the first subject is included in the at least one candidate subject pre-bound with the target loan account, so as to determine whether the first subject has the quota sharing right for the target loan account. For example, if the first subject is included in the at least one candidate subject, the loan server determines that the first subject has the quota sharing right for the target loan account. If the first subject is not included in the at least one candidate subject, the loan server determines that the first subject does not have the quota sharing right for the target loan account.

[0082] S460: The loan server sends an authorization task to the second terminal device corresponding to the second subject, and receives an execution result of the authorization task from the second terminal device.

[0083] It should be noted that the specific content of the authorization task is not limited in the present specification. As an example, the authorization task can describe the quota requested to be used by the first subject, the fund use, the use period, and the like, and ask the second subject whether to agree to use. For example: subject Aaa (i.e., the first subject) requests to use a quota of 200,000 yuan, the use period is three months, and the fund use is to purchase goods, please confirm whether to agree.

[0084] The loan server sends the above authorization task to the second terminal device, so that the second terminal device displays the authorization task to the second subject. The second terminal device can determine the execution result according to the operation "agree" or "disagree" performed by the second subject on the authorization task, and send the execution result to the loan server. Thus, the loan server obtains the execution result of the authorization task.

[0085] In some embodiments, after generating the authorization task, the loan server can generate an access link corresponding to the authorization task. For example, the access link can be a uniform resource locator (URL) of the operation page of the authorization task. Further, the loan server sends the access link to the first terminal device. Under the operation of the first subject, the first terminal device can forward the access link to the second terminal device. The way in which the first terminal device sends the access link to the second terminal device can include but is not limited to message notification, short message, email or application push, etc.

[0086] Figure 6 Another set of interaction pages provided by an embodiment of the present specification is shown in the schematic diagram. The set of interaction pages can be the interaction pages of the first terminal device. As shown in the schematic diagram, the set of interaction pages can include a first interaction page 510, a second interaction page 520, and a third interaction page 530.Figure 6 As shown, the first terminal device displays a page 530 to the first principal. The page 530 displays the access link, and can also display a sending portal (e.g., the control "Send to Bbb") to the second principal. When the first principal clicks the control "Send to Bbb", the first terminal device displays a page 540. In the page 540, the first principal can select the name of the second principal (e.g., Bbb) in the friend list. Then, the page jumps to a page 550. In the page 550, the access link is sent to the conversation box between the first principal and the second principal. It is to be noted that the page 530, the page 540, and the page 550 can be pages of the same application, or can be pages of different applications. For example, in some embodiments, the page 530 can be a page of a first application that provides the loan capability, and the first application also provides the social capability, in which case the page 540 and the page 550 can also be pages of the first application. For another example, in some embodiments, the page 530 can be a page of a first application that provides the loan capability, and the page 540 and the page 550 can be pages of a second application that provides the social capability.

[0087] After receiving the access link, the second terminal device can display the access link, so that the second principal can click or open the access link in the second terminal device. After detecting the clicking or opening operation of the second principal, the second terminal device generates an access request for the access link, and sends the access request to the loan server through the secure communication channel. In response to receiving the access request for the access link from the second terminal device, the loan server sends an authorization task to the second terminal device. Thus, the second terminal device can display an operation page of the authorization task to the second principal, so that the second principal can perform an "agree" or "disagree" operation in the operation page.

[0088] Figure 7 A schematic diagram of another set of interaction pages provided according to an embodiment of the present specification is shown. The set of interaction pages can be interaction pages of the second terminal device. As shown, the second terminal device displays a page 610 to the second principal. The page 610 displays the access link, and can also display a sending portal (e.g., the control "Send to Bbb") to the first principal. When the second principal clicks the control "Send to Bbb", the second terminal device displays a page 620. In the page 620, the second principal can select the name of the first principal (e.g., Aaa) in the friend list. Then, the page jumps to a page 630. In the page 630, the access link is sent to the conversation box between the first principal and the second principal. It is to be noted that the page 610, the page 620, and the page 630 can be pages of the same application, or can be pages of different applications. For example, in some embodiments, the page 610 can be a page of a first application that provides the loan capability, and the first application also provides the social capability, in which case the page 620 and the page 630 can also be pages of the first application. For another example, in some embodiments, the page 610 can be a page of a first application that provides the loan capability, and the page 620 and the page 630 can be pages of a second application that provides the social capability. Figure 7As shown, the second terminal device displays a page 560 to the second principal. The page 560 can display a conversation box of the second principal and the first principal. The access link is displayed in the conversation box. The second principal clicks the access link, and the second terminal device displays a page 570. The page 570 displays authorization details. The authorization details include an applicant (e.g., Aaa), an application amount (e.g., 200,000), a use period (e.g., three months), a fund use (e.g., purchase of goods), and the like. In the page 570, the second principal clicks an "agree" button to agree to the allocation of the amount to the first principal. After the second terminal device detects that the second principal clicks the "agree" button, it is considered that the second principal has agreed to the amount allocation request of the first principal. Therefore, the second terminal device returns an "agree" execution result to the loan server. If the second principal clicks a "disagree" button, the second terminal device considers that the second principal disagrees to the amount allocation request of the first principal, and returns an "reject" or "additional information required" execution result to the loan server.

[0089] In some embodiments, after generating the access link corresponding to the authorization task, the loan server can also set a valid period range of the access link. The valid period range refers to a time period starting from the generation time of the access link. That is, the time period ends after the generation of the access link, and the access link will automatically expire and cannot be used to access the operation page of the authorization task. It should be noted that the present specification does not limit the value of the valid period range, which can be several minutes, several hours, or several days, etc.

[0090] In this case, the loan server determines whether the current time is within the valid period range of the access link in response to receiving an access request for the access link from the second terminal device. If the current time is within the valid period range, the loan server sends the authorization task to the second terminal device. If the current time is outside the valid period range, the loan server refuses to process the access request, that is, the loan server will not send the authorization task to the second terminal device. At this time, the loan server can send first prompt information to the second terminal device. The first prompt information is used to prompt that the authorization task has expired.

[0091] The above embodiments can effectively reduce the risk of hijacking or brute force cracking of the access link by limiting the valid period range of the access link, and can avoid unlimited waiting of the first principal.

[0092] S480: In the case where the execution result represents an agreement, the loan server determines that the second principal agrees to the target amount allocated to the first principal, allocates the target amount to the first principal's first loan account, and reduces the target amount in the second principal's available amount.

[0093] It can be understood that, in the case that the execution result represents consent, it indicates that the second subject agrees to share the quota with the first subject. In this case, the loan server can determine the target quota that the second subject agrees to allocate to the first subject. There are various ways to determine the target quota, and two possible examples are given below.

[0094] In some embodiments, the quota allocation request initiated by the first subject can include a first quota requested by the first subject to be allocated. The first quota represents the quota that the first subject hopes to share from the target loan account (quota pool). Accordingly, the authorization task generated by the loan server is used to inquire whether the second subject agrees to allocate the first quota to the first subject. In this case, if the execution result represents consent, it indicates that the second subject agrees to allocate the first quota to the first subject. Therefore, the loan server can determine the first quota as the target quota.

[0095] In some embodiments, in the case that the execution result represents consent, the second quota that the second subject agrees to allocate to the first subject can be included in the execution result. The second quota can be different from the first quota applied by the first subject to be allocated. For example, the first quota applied by the first subject to be allocated is 300,000, and the second quota that the second subject agrees to allocate to the first subject is 200,000. Of course, the second quota can also be the same as the first quota, which is not limited in this specification. In this case, the loan server can determine the second quota as the target quota.

[0096] After determining the target quota, the loan server allocates the target quota to the first loan account of the first subject. Accordingly, the loan server reduces the available quota of the target loan account of the second subject by the target quota. For example, Figure 8 A quota allocation schematic diagram provided according to an embodiment of the present specification is shown. As Figure 8 shown, it is assumed that before the execution of P400, the available quota of the target loan account of the second subject is 1,000,000, and the available quota of the first loan account of the first subject is 0. And it is assumed that the loan server determines the target quota to be 200,000 by executing the method P400. In this case, after the execution of P400, the available quota of the first loan account of the first subject is 200,000, and the available quota of the target loan account of the second subject is 800,000.

[0097] In the above embodiment, the loan server can allocate at least part of the available quota of the second subject to the first subject in the case that the loan server receives the quota allocation request initiated by the first subject and obtains the authorization of the second subject, so that the first subject can obtain the target quota without submitting the credit qualification information to the loan server, that is, even if the credit qualification of the first subject is low, the loan from the financial institution can be realized, and the loan demand of the low-credit subject can be met.

[0098] After the loan server allocates the target quota to the first principal, the first principal can initiate a fund disbursement process directly to the loan server through the first terminal device. The fund disbursement process is described below.

[0099] In some embodiments, the first principal initiates a disbursement request on the first terminal device for the first loan account. The loan server receives the disbursement request corresponding to the first loan account from the first terminal device. For example, the disbursement request includes the first amount requested by the first principal for disbursement, a disbursement account, etc. The disbursement account can be, but is not limited to, a bank account, an electronic wallet, or other payment account of the first principal. The loan server can determine the first amount requested by the first principal for disbursement from the disbursement request, and determine the disbursement account of the first principal. Further, the loan server can transfer the fund corresponding to the first amount to the disbursement account of the first principal, and reduce the corresponding quota in the available quota of the first loan account.

[0100] In the above embodiments, after obtaining the target quota, the first principal can directly initiate fund disbursement to the loan server within the target quota range, thereby eliminating the need for the second principal to disburse funds first and then transfer the disbursed funds to the first principal, shortening the fund circulation path, and improving the efficiency of the first principal in obtaining loan funds. In addition, since the loan server can directly perceive the fund disbursement process of the first principal, the financial institution can understand the actual fund use behavior of the first principal, thereby being able to effectively manage and control the fund.

[0101] After the first principal performs the fund disbursement operation, the first principal can repay the fund disbursement behavior. This repayment can be active repayment or passive repayment. The repayment process is described below.

[0102] In some embodiments, the first principal can actively repay. In this case, the first principal initiates a repayment request in the first terminal device for the first loan account. The repayment request includes, but is not limited to, a repayment amount, a repayment account, a repayment time, etc. The repayment amount can be equal to the first amount of disbursement, which corresponds to the full repayment scenario; the repayment amount can also be less than the first amount of disbursement, which corresponds to the partial repayment / batch repayment scenario, etc. The repayment account can be a bank account or an electronic wallet bound by the first principal, etc. The loan server receives the repayment request from the first terminal device, deducts at least part of the fund from the repayment account of the first principal for repayment based on the repayment request, and increases the corresponding quota in the available quota of the first loan account based on the amount of the repayment fund.

[0103] In some embodiments, in the case where the first principal does not actively repay, the loan server can perform a reminder process or an automatic deduction process. Then, the repayment process includes at least one of the following contents: (1) The loan server sends second prompt information to the first terminal device when detecting that the fund corresponding to the first amount is approaching the repayment deadline. The second prompt information is used to prompt the first principal to make a repayment.

[0104] (2) The loan server sends third prompt information to the second terminal device when detecting that the fund corresponding to the first amount is approaching the repayment deadline. The third prompt information is used to prompt the second principal to make a repayment, or to prompt the second principal to urge the first principal to make a repayment.

[0105] (3) The loan server deducts at least part of the fund in the repayment account of the first principal for a repayment when detecting that the fund corresponding to the first amount reaches the repayment deadline, and increases a corresponding quota in the available quota of the first loan account based on the amount of the repayment fund.

[0106] (4) The loan server deducts at least part of the fund in the repayment account of the second principal for a repayment when detecting that the fund corresponding to the first amount reaches the repayment deadline and the fund in the repayment account of the first principal is insufficient for a repayment, and increases a corresponding quota in the available quota of the first loan account based on the amount of the repayment fund.

[0107] In the above (1) or (3), the loan server can remind the first principal to make a repayment or automatically deduct the fund of the first principal for a repayment, which can reduce the fund risk. In the above (2) or (4), the loan server can also remind the second principal to make a repayment or automatically deduct the fund of the second principal for a repayment, that is, in the case that the first principal cannot make a repayment on time, the second principal with better credit quality can help the first principal to make a repayment, so as to further reduce the fund risk.

[0108] The above S480 describes a case where the execution result represents consent. In some embodiments, if the execution result represents disagreement, the loan server can send fourth prompt information to the first terminal device, and the fourth prompt information is used to prompt the first principal that the quota allocation fails. In this case, the first principal cannot share the available quota of the second principal. In some embodiments, the second prompt information can also include a failure reason, so that the first principal can understand the specific reason information of the quota allocation failure, thereby facilitating subsequent processing.

[0109] To sum up, the loan amount processing method provided in the specification, the loan server can allocate at least part of the available amount of the second subject to the first subject in the case of receiving the amount allocation request initiated by the first subject and obtaining the authorization of the second subject, so that the first subject can obtain the target amount without submitting the qualification certificate information to the loan server. That is, even if the credit qualification of the first subject is low, the loan from the financial institution can be realized, and the loan demand of the low-credit subject can be met. Since the target amount is directly allocated to the first subject by the financial institution, the first subject can directly initiate the fund use to the loan server within the target amount range, so as not to first use the fund by the second subject, and then transfer the used fund to the first subject, thereby shortening the fund circulation path and improving the efficiency of the first subject to obtain the loan fund. In addition, since the loan server can directly perceive the fund use process of the first subject, the financial institution can understand the actual fund use behavior of the first subject, so as to effectively manage and control the fund.

[0110] Another aspect of the present specification provides a computer-readable non-transitory storage medium storing at least one set of instructions for performing the processing of the loan amount. When the at least one set of instructions is executed by a processor, the at least one set of instructions directs the processor to implement the steps of the processing method P400 of the loan amount described in the present specification. In some possible implementation, various aspects of the present specification can also be implemented as a program product in the form of a computer readable medium including program code. When the program product is run on the computing device 300, the program code is used to cause the computing device 300 to perform the steps of the processing method P400 of the loan amount described in the present specification. The program product for implementing the above method can include program code in a portable compact disc read-only memory (CD-ROM) and can be run on the computing device 300. However, the program product of the present specification is not limited to this, and in the present specification, the readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system. The program product can take any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium may, for example, be but is not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination of the above. More specific examples of the readable storage medium include a portable disc, a hard disc, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. The computer readable storage medium can include a data signal propagating in a carrier wave as part of a baseband, in which the readable program code is borne. Such a propagating data signal can take various forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The readable storage medium can also be any readable medium that is not a storage medium and that can send, propagate or transmit the program for use by or in connection with an instruction execution system, apparatus or device. The program code contained on the readable storage medium can be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, and the like, or any suitable combination of the above. The program code for performing the operations of the present specification can be written in any combination of one or more programming languages, including an object-oriented programming language, such as Java, C++, and the like, and a conventional procedural programming language, such as the "C" programming language or similar programming languages. The program code can be executed entirely on the computing device 300, partially on the computing device 300, as an independent software package, partially on the computing device 300 and partially on a remote computing device, or entirely on a remote computing device.

[0111] The above described embodiments of the present specification have been described. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than the order in which they are recited and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous.

[0112] In light of the above detailed disclosure, those skilled in the art can appreciate that the foregoing detailed disclosure can be presented only in an exemplary manner and can not be limiting. Although not explicitly described herein, those skilled in the art will appreciate that the present specification contemplates various reasonable alterations, improvements and modifications to the embodiments. These alterations, improvements and modifications are intended to be suggested by the present specification and are within the spirit and scope of the exemplary embodiments of the present specification.

[0113] In addition, certain terms have been used in the present specification to describe embodiments of the present specification. For example, "one embodiment", "an embodiment" and / or "some embodiments" means that a particular feature, structure or characteristic described in connection with the embodiment can be included in at least one embodiment of the present specification. Therefore, it can be emphasized and should be understood that two or more references to "the embodiment" or "an embodiment" or "alternative embodiments" in various portions of the specification are not necessarily all referring to the same embodiment. Furthermore, particular features, structures or characteristics can be combined in any suitable manner in one or more embodiments of the present specification.

[0114] It should be understood that in the foregoing description of embodiments of the present specification, for the purpose of brevity, various features of the specification were grouped into several embodiments, figures or descriptions of the embodiments. However, this is not a requirement that the features be grouped together in the embodiments, and one skilled in the art can well understand that a part of the devices can be marked as a separate embodiment for understanding. That is, the embodiments of the present specification can also be understood as an integration of multiple sub-embodiments. And the content of each sub-embodiment is also true when less than all the features of a single foregoing disclosed embodiment.

[0115] Each patent, patent application, publication of a patent application, and other material, for example articles, books, specifications, publications, documents, things, and / or the like which can have been cited or referred to in this document, are incorporated by reference into the present document, and are hereby made part of the present document, for all purposes, to the same extent as if each individual publication or item had been individually cited or incorporated by reference. Additionally, where a definition or use of a term in this document is provided to overcome a definition or use of the term in an individually cited document that is incorporated by reference, the definition or use of the term in this document prevails.

[0116] Finally, it should be understood that the embodiments of the application disclosed herein are illustrative of the principles of the present specification. Other modifications that fall within the scope of the present specification can also be made. Accordingly, the present specification discloses embodiments only as examples. Substantially any arrangement, which is neither specifically described nor explicitly illustrated, can be substituted for the specific embodiments disclosed, without departing from the scope of the present specification. Accordingly, the present specification discloses embodiments only as examples.

Claims

1. A method for processing loan amounts, applied to a loan server, the method comprising: A quota allocation request is received from the first terminal device corresponding to the first subject, the quota allocation request being used to request that at least a portion of the available quota of the second subject be allocated to the first subject; An authorization task is generated based on the quota allocation request, wherein the authorization task is used to ask the second entity whether it agrees to allocate a quota to the first entity; Send the authorization task to the second terminal device corresponding to the second entity, and receive the execution result of the authorization task from the second terminal device; and If the execution result indicates agreement, the second entity agrees to allocate a target amount to the first entity, the target amount is allocated to the first entity's first loan account, and the target amount is reduced from the second entity's available credit limit.

2. The method according to claim 1, wherein, The second entity corresponds to at least one second loan account, and the at least one second loan account includes a target loan account of the shared type; The authorization task is used to inquire whether the second entity agrees to allocate the available credit limit in the target loan account to the first entity.

3. The method according to claim 2, wherein, The method further includes: The loan request is received from the second terminal device, the loan request including at least the qualification certificate information corresponding to the second entity, and the loan request is used to apply for a loan limit that can be shared with other entities; and If the second entity meets the loan conditions based on the qualification certificate information, the loan amount corresponding to the second entity is determined, the target loan account is generated for the second entity, the loan amount is used as the available amount of the target loan account, and the type of the target loan account is set to shared type.

4. The method according to claim 3, wherein, The loan request also includes: trade document information between the second entity and at least one other entity; After generating the target loan account for the second entity, the method further includes binding the target loan account to the at least one other entity, so that the at least one other entity has the right to share the credit limit of the target loan account.

5. The method according to claim 2, wherein, Generate an authorization task based on the quota allocation request, including: Determine whether the first entity has the authority to share the credit line of the target loan account; and If the first entity has the authority to share the credit limit of the target loan account, the authorization task is generated based on the credit limit allocation request.

6. The method according to claim 5, wherein, The credit limit allocation request includes at least: trade document information between the first entity and the second entity, and determining whether the first entity has credit limit sharing authority over the target loan account, including: The trade document information is obtained from the quota allocation request, and the closeness of the trade relationship between the first entity and the second entity is determined based on the trade document information; and Based on the closeness of the trade relationship, it is determined whether the first entity has the authority to share the credit line of the target loan account.

7. The method according to claim 5, wherein, The target loan account is pre-linked with at least one candidate entity. Determining whether the first entity has credit line sharing permissions for the target loan account includes: If the first entity is included among the at least one candidate entity, then the first entity is determined to have credit line sharing authority over the target loan account; or If the first entity is not among the at least one candidate entity, then it is determined that the first entity does not have the authority to share the credit line of the target loan account.

8. The method according to claim 1, wherein, After generating the authorization task, the method further includes: generating an access link corresponding to the authorization task and sending the access link to the first terminal device so that the first terminal device forwards the access link to the second terminal device; Sending the authorization task to the second terminal device corresponding to the second subject includes: in response to receiving an access request for the access link from the second terminal device, sending the authorization task to the second terminal device.

9. The method according to claim 8, wherein, After generating the access link corresponding to the authorized task, the method further includes: setting the validity period range of the access link; Sending the authorization task to the second terminal device includes: sending the authorization task to the second terminal device if the current time is within the validity period.

10. The method according to claim 9, wherein, The method further includes: when the current time is outside the validity period, sending a first prompt message to the second terminal device, the first prompt message being used to indicate that the authorized task has expired.

11. The method according to claim 1, wherein, The quota allocation request includes a first quota requested by the first entity, and the authorization task is used to ask the second entity whether it agrees to allocate the first quota to the first entity; Determining the target amount that the second entity agrees to allocate to the first entity includes: determining the first amount as the target amount.

12. The method according to claim 1, wherein, In cases where the execution result represents agreement, the execution result includes the second entity's agreement to allocate a second quota to the first entity; Determining the target amount that the second entity agrees to allocate to the first entity includes: determining the second amount as the target amount.

13. The method according to claim 1, wherein, After allocating the target amount to the first loan account of the first entity, the method further includes: Receive the withdrawal request corresponding to the first loan account from the first terminal device; Based on the withdrawal request, determine the first amount requested by the first entity and determine the withdrawal account of the first entity; and Funds corresponding to the first amount are transferred to the first entity's withdrawal account, and the corresponding amount is reduced from the available credit limit of the first loan account.

14. The method according to claim 13, wherein, After transferring the funds corresponding to the first amount to the first entity's withdrawal account, the method further includes: Receive repayment request from the first terminal device; and Based on the repayment request, at least a portion of the funds are deducted from the repayment account of the first entity for repayment, and a corresponding amount is added to the available credit limit of the first loan account based on the amount of repayment funds.

15. The method according to claim 13, wherein, After transferring the funds corresponding to the first amount to the first entity's withdrawal account, the method further includes at least one of the following: If it is detected that the funds corresponding to the first amount are nearing the repayment deadline, a second reminder message is sent to the first terminal device. The second reminder message is used to remind the first entity to make the repayment. If it is detected that the funds corresponding to the first amount are nearing the repayment deadline, a third reminder message is sent to the second terminal device. The third reminder message is used to remind the second entity to make the repayment, or to remind the second entity to urge the first entity to make the repayment. If the funds corresponding to the first amount are detected to have reached the repayment deadline, at least a portion of the funds will be deducted from the repayment account of the first entity for repayment, and the corresponding amount will be added to the available credit limit of the first loan account based on the amount of repayment funds. or If it is detected that the funds corresponding to the first amount have reached the repayment deadline and the funds in the repayment account of the first entity are insufficient to make the repayment, at least a portion of the funds shall be deducted from the repayment account of the second entity for repayment, and the corresponding amount shall be added to the available credit limit of the first loan account based on the amount of repayment funds.

16. The method according to claim 1, wherein, After receiving the execution result, the method further includes: If the execution result indicates disagreement, a fourth prompt message is sent to the first terminal device, which is used to notify the first entity that the quota allocation has failed.

17. A loan server, comprising: At least one storage medium storing at least one instruction set; as well as At least one processor is communicatively connected to the at least one storage medium, wherein the at least one processor reads the at least one instruction set during operation and executes the method as described in any one of claims 1-16 according to the instructions of the at least one instruction set.

18. A computer-readable non-transitory storage medium, wherein, The computer-readable non-transitory storage medium stores at least one set of instructions, which, when executed by at least one processor, implement the method as described in any one of claims 1-16.

Images