CN106897924B - Network resource transfer method, fund transfer method, payment method and device - Google Patents
Network resource transfer method, fund transfer method, payment method and device Download PDFInfo
- Publication number
- CN106897924B CN106897924B CN201610717716.2A CN201610717716A CN106897924B CN 106897924 B CN106897924 B CN 106897924B CN 201610717716 A CN201610717716 A CN 201610717716A CN 106897924 B CN106897924 B CN 106897924B
- Authority
- CN
- China
- Prior art keywords
- fund
- repayment
- resource
- transferred
- target
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
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
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Finance (AREA)
- Marketing (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The application discloses a network resource transfer method, a fund transfer method, a payment method and a payment device. The network resource transfer method comprises the following steps: receiving confirmation information of resource transfer and determining a target account according to the confirmation information; freezing network resources to be transferred; and when receiving a resource transfer instruction aiming at the target account, unfreezing the network resource and transferring the network resource to the target account. After the network resource to be transferred is determined, the network resource is frozen, the frozen network resource is unfrozen and transferred to a target account only when a resource transfer instruction aiming at the target account confirmed by a user is received, and the network resource cannot be transferred due to freezing when resource transfer instructions aiming at other accounts are received, so that the problem in the prior art is solved.
Description
Technical Field
The present application relates to the field of computer financial technologies, and in particular, to a network resource transfer method, a fund transfer method, a payment method, and a payment device.
Background
With the development of information technology, people need to use network resources (such as virtual currency, QQ currency, etc.) when processing various transactions through a network. Because network resources are relatively scarce, the situation of network resource shortage may occur in the transaction processing process, and therefore, it is very important to acquire the network resources through resource transfer.
At present, in the transfer process of network resources, a server that processes the resource transfer service, after receiving information that a resource transfer party confirms transfer, places a resource transfer party included in the confirmation information into a "confirmation record table", and within a specified time window, a monitoring unit of the server monitors a resource pool corresponding to the resource transfer party, and when a network resource is monitored in the resource pool, the monitoring unit initiates a resource transfer instruction to instruct the server to transfer the network resource to the resource transfer party in the "confirmation record table".
In practical application, with the rapid increase of the traffic volume of network resource transfer, after receiving the confirmation information of transferring network resources from the resource transfer-out party to the resource transfer-in party, the server may also receive the confirmation information of transferring network resources from the resource transfer-out party to other resource transfer-in parties within a specified time window, and at this time, a plurality of resource transfer-in parties in the "confirmation record table" are in progress. When a network resource is detected in the resource pool, the resource transfer instruction initiated by the monitoring unit may transfer the network resource to different resource transfer parties due to a plurality of resource transfer parties in the "confirmation record table". Therefore, in this resource transfer method, when there are multiple resource transferring parties in the "confirmation record table", it may not be possible to transfer the network resource to a certain specified resource transferring party according to the needs of the resource transferring party.
Disclosure of Invention
In order to solve the problems in the prior art, embodiments of the present application provide a network resource transfer method, a fund transfer method, a payment method, and an apparatus.
The embodiment of the application provides a method for transferring network resources, which comprises the following steps:
receiving confirmation information of resource transfer and determining a target account according to the confirmation information;
freezing network resources to be transferred;
and when receiving a resource transfer instruction aiming at the target account, unfreezing the network resource and transferring the network resource to the target account.
Preferably, when determining the target account according to the confirmation information, the method further includes: determining a resource value of the required network resource according to the confirmation information; then the process of the first step is carried out,
before freezing the network resource to be transferred, the method further comprises:
matching the resource value of the network resource to be transferred with the resource value of the required network resource;
and if the matching is successful, freezing the network resources to be transferred.
Preferably, when a plurality of target accounts and resource values corresponding to the respective target accounts are determined based on the confirmation information,
the matching of the resource value of the network resource to be transferred and the resource value of the required network resource specifically includes:
matching the resource value of the network resource to be transferred with the sum of the resource values corresponding to the target accounts; and the number of the first and second groups,
the thawing and transferring the network resources to be transferred into the target account specifically comprises the following steps:
unfreezing the network resource to be transferred;
splitting the network resources to be transferred into corresponding sub-network resources according to the resource values corresponding to the target accounts;
and transferring each sub-network resource to the corresponding target account.
Preferably, when the network resource to be transferred is frozen, the method further comprises: and generating a unfreezing code for unfreezing the network resource.
Preferably, the freezing of the network resource to be transferred specifically includes: and setting the network resources to be transferred into states of non-transferable, non-mortgage and non-subscriber.
The embodiment of the application also provides a fund transfer method, which comprises the following steps:
receiving confirmation information of fund transfer and determining a target fund account and a required fund amount according to the confirmation information;
matching the amount of the fund to be transferred with the required fund amount;
if the matching is successful, freezing the fund to be transferred;
when a fund transfer instruction aiming at the target fund account is received, the fund to be transferred is unfrozen and is transferred into the target fund account.
The embodiment of the application also provides a payment method, which comprises the following steps:
receiving repayment confirmation information and determining a repayment target account and a required repayment fund limit according to the confirmation information;
matching the amount of the repayment fund with the required repayment fund amount;
if the matching is successful, the repayment fund is frozen;
when a repayment instruction aiming at the repayment target account is received, unfreezing the repayment fund and transferring the repayment fund into the repayment target account.
Preferably, the method further comprises: and determining the funds injected into the designated account by the repayment user as repayment funds.
Preferably, the receiving payment confirmation information is specifically:
receiving payment confirmation information input by a payment user through a designated page; or the like, or, alternatively,
receiving payment confirmation information input by a payment user through a specified data transmission interface; or the like, or, alternatively,
and receiving a repayment file which is uploaded by a repayment user and used for confirming the repayment.
Preferably, the instructions to transfer the funds to the target funds account are received upon arrival of a payment time point.
An embodiment of the present application further provides a fund transfer device, including: a first determination unit, a first matching unit, a first freezing unit, and a funds transfer unit, wherein:
the first determination unit is used for receiving confirmation information of fund transfer and determining a target fund account and a required fund amount according to the confirmation information;
the first matching unit is used for matching the amount of the fund to be transferred with the required fund amount;
the first freezing unit freezes the fund to be transferred if the matching is successful;
and the fund transfer unit unfreezes the fund to be transferred and transfers the fund to the target fund account when receiving the fund transfer instruction aiming at the target fund account.
The embodiment of the present application further provides a payment device, and the device includes: second confirm unit, second matching unit, second freezing unit and repayment unit, wherein:
the second determining unit is used for receiving repayment confirmation information and determining a repayment target account and a required repayment fund limit according to the confirmation information;
the second matching unit is used for matching the amount of the repayment fund with the required repayment fund amount;
the second freezing unit is used for freezing the repayment fund if the matching is successful;
and the repayment unit is used for unfreezing the repayment fund and transferring the repayment fund into the repayment target account when receiving a repayment instruction aiming at the repayment target account.
The embodiment of the application adopts at least one technical scheme which can achieve the following beneficial effects:
after the network resource to be transferred is determined, the network resource is frozen, the frozen network resource is unfrozen and transferred to a target account only when a resource transfer instruction aiming at the target account confirmed by a user is received, and the network resource cannot be transferred due to freezing when resource transfer instructions aiming at other accounts are received, so that the problem in the prior art is solved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a schematic flowchart illustrating a specific implementation of a network resource transfer method according to an embodiment of the present application;
FIG. 2 is a schematic flow chart illustrating an implementation of a fund transfer method according to an embodiment of the present disclosure;
FIG. 3 is a schematic diagram of page validation provided by an embodiment of the present application;
fig. 4 is a schematic flowchart of a specific implementation of a payment method according to an embodiment of the present application;
fig. 5 is a schematic view of a payment method according to an embodiment of the present application;
FIG. 6 is a schematic illustration of a repayment fund transfer of a repayment method according to an embodiment of the present application;
FIG. 7 is a diagram illustrating an exemplary embodiment of a funds-transfer device according to the present disclosure;
fig. 8 is a diagram illustrating a specific structure of a payment apparatus according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail and completely with reference to the following specific embodiments of the present application and the accompanying drawings. It should be apparent that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The technical solutions provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings.
Example 1
As described above, with the development of information technology, people usually need to perform network resource transfer during daily business processing. In the current network resource transfer method, after receiving the information that the resource transfer-out party confirms the transfer, the server puts the resource transfer-in party contained in the confirmation information into a confirmation record table, and monitors the resource pool within a specified time window, and when the resource pool is found to have network resources, the server transfers the network resources to the resource transfer-in party according to the resource transfer instruction of the monitoring unit.
However, with the rapid increase of the traffic volume of the network resource transfer, after the server receives the confirmation information of transferring the network resource to the resource transfer party from the resource transfer-out party, the server may also receive the confirmation information of transferring the network resource to other resource transfer parties within the specified time window, and at this time, the "confirmation record table" includes a plurality of resource transfer parties. When the network resource is monitored in the resource pool, the server may receive different resource transfer instructions to instruct to transfer the network resource to different resource transfer parties due to the fact that a plurality of resource transfer parties exist in the 'confirmation record table'. Therefore, in this resource transfer method, when there are multiple resource transferring parties in the "confirmation record table", it may not be possible to transfer the network resource to a certain specified resource transferring party according to the needs of the resource transferring party.
For example, the server receives the confirmation information that the first user transfers the network resource to the second user in 6/5, and puts the second user into a "confirmation record table", wherein the specified time window is 3 days; and then, the server receives the confirmation information of transferring the network resource from the first user to the third user again in 6 th month, and also puts the third user into a confirmation record table, wherein the confirmation record table comprises the second user and the third user. When the user No. 6/month and 7 places the network resource into the resource pool, the server may receive an instruction to transfer the network resource to the second user and transfer the network resource to the second user, or may receive an instruction to transfer the network resource to the third user and transfer the network resource to the third user, so that a phenomenon of contending for the network resource occurs. At this time, if the first user wishes to transfer the network resource of number 7 to the second user, the resource transfer method of the prior art may cause a transfer error.
In order to solve the problems in the prior art, embodiments of the present application provide a method for transferring network resources, where the method is implemented by a user server. As shown in fig. 1, the steps of the method include:
step S11: and receiving confirmation information of resource transfer and determining a target account according to the confirmation information.
The server may receive confirmation of the transfer of the resource, typically after the user confirms the transfer of the network resource, and may determine the target account, typically based on the confirmation. In addition, after the user confirms the transfer of the network resource to the target account, the server typically also places the target account in a confirmation log.
For example, the user a needs to transfer the network resource to the user B, and after the user a confirms the transfer service, the server receives confirmation information of the resource transfer, and analyzes the confirmation information to determine an account (i.e., a target account) corresponding to the user B.
Step S12: determining the network resources to be transferred.
In the actual network resource transfer process, a user usually has multiple accounts at the same time according to needs, and a specific account is used for transferring the network resource, and the network resource transferred to the specific account by the user can be determined as the network resource to be transferred.
In particular, with the advent of the APP for transferring network resources, a user usually registers a plurality of login accounts (accounts corresponding to login accounts), and each login account is applied to a different purpose. The network resources can be transferred by using a certain login account, and the network resources transferred to the resource pool corresponding to the login account by the user can be determined as the network resources to be transferred. Generally, after the server puts the target account into the confirmation record table according to the information confirmed by the user to be transferred, the server also monitors the corresponding network resource pool, and when the network resource is monitored to exist in the resource pool, the network resource is determined as the network resource to be transferred.
Step S13: and freezing the network resources to be transferred.
As used herein, freezing the network resource to be transferred may be setting the network resource to be transferred to a state of non-transferable, non-mortgage and non-subscriber. In addition, when the network resource to be transferred is frozen, a unfreezing code for unfreezing the network resource can be generated, and when needed, the network resource can be unfrozen through the unfreezing code.
Step S14: and when receiving a resource transfer instruction aiming at the target account, unfreezing the network resource and transferring the network resource to the target account.
Usually, when a certain time point arrives or according to the active trigger of the user, the server can receive a resource transfer instruction for the target account, so as to unfreeze the frozen network resource and transfer the frozen network resource into the target account.
It should be noted that, in practical applications, after a user confirms that a network resource is transferred, a server may monitor a login account (serving as a resource pool) used by the user to transfer the network resource, and when a network resource is monitored in the resource pool, a plurality of resource transfer instructions are generally received, and the resource transfer instructions are respectively directed to each account in a confirmation record table, so that after receiving the resource transfer instruction, the server needs to determine whether the resource transfer instruction is directed to a target account.
The resource transfer instruction may generally include a second account and a target account, and when the matching is successful, it indicates that the received resource transfer instruction is directed to the target account, and the network resource may be thawed and transferred to the target account according to the resource transfer instruction, and when the matching is failed, it indicates that the received resource transfer instruction is not directed to the target account, and at this time, because the network resource is frozen, it is impossible to transfer the network resource to the second account.
Thus, step S14 may be embodied as step S141,
step S141: and matching a second account in the resource transfer instruction with the target account when the resource transfer instruction is received, and unfreezing the network resource to be transferred and transferring the network resource to the target account if the matching is successful.
By adopting the method for transferring network resources provided in embodiment 1 of the present application, after determining the network resources to be transferred, the network resources are frozen, and only when receiving a resource transfer instruction for a target account confirmed by a user, the frozen network resources are thawed and transferred to the target account.
For example, the user needs to transfer the network resource to account 1, and after confirming that the network resource is transferred to account 1, the confirmation record table includes account 1 and account 2. At this time, the user injects the network resource into the resource pool, freezes the network resource, and after the server receives the instruction of transferring the network resource to the account 2, the transfer cannot be completed because the network resource is frozen; only after receiving a resource transfer instruction for account 1 can the network resource be defrosted and transferred to account 1.
It should be noted that, in practical applications, when a user confirms to transfer a network resource to another user, the user also needs to confirm a resource value of the network resource to be transferred, that is, when the server determines a target account according to confirmation information of transferring the network resource, the server may also determine the resource value of the network resource according to the confirmation information.
Then, between step S12 and step S13, the resource value of the network resource to be transferred may be matched with the resource value of the required network resource, when the matching is successful, step S13 is executed, when the matching is failed, a prompt message may be sent to the user, and then the network resource is frozen or not frozen according to the selection of the user.
In addition, when a plurality of target accounts are determined according to the confirmation information and different resource values correspond to the target accounts, matching the resource value of the network resource to be transferred with the resource value of the required network resource may be performed by matching the resource value of the network resource to be transferred with the sum of the resource values corresponding to the target accounts, freezing the network resource to be transferred when the matching is successful, and after the network resource to be transferred is thawed, splitting the network resource to be transferred into corresponding sub-network resources according to the resource values corresponding to the target accounts, and transferring the sub-network resources to the corresponding target accounts.
For example, according to the confirmation information of transferring the network resource by the user, it is determined that the network resource is transferred to the account X and the account Y, where the resource value of transferring the network resource to the account X is a, and the resource value of transferring the network resource to the account Y is b, then the resource value of the required network resource is (a + b), the resource value of the network resource to be transferred is matched with (a + b), and the network resource is frozen after the matching is successful; after unfreezing, the network resource is divided into a sub-network resource X '(with a resource value of a) and a sub-network resource Y' (with a resource value of b), and the sub-network resource X 'and the sub-network resource Y' are transferred to the account X and the account Y, respectively.
The present embodiment 1 is described in the order of step S11 to step S14, but in practical use, it is not always necessary to perform the description in this order. For example, steps S12 and S13 may be performed first, and then step S11 may be performed; steps S12 and S11 may be performed first, and then step S13 may be performed; and may be implemented in other ways, which do not affect the performance of the present application.
Example 2
In order to more clearly illustrate the network resource transfer method provided in embodiment 1, embodiment 2 provides an embodiment of the method in a specific application scenario of fund transfer, and in this embodiment, the network resource may be specifically a fund. A method of funds transfer as provided in example 2, as shown in fig. 2, comprising the steps of:
step S21: and receiving confirmation information of the fund transfer and determining a target fund account and a required fund amount according to the confirmation information.
After the user confirms the transfer of funds, the server receives confirmation of the transfer of funds and may typically determine the target funds account based on the confirmation. The user may be a company, a financial institution, an individual, etc., and for a financial institution, a bank, a fund, an insurance, etc. may be included. The target fund account can be a bank account, a fund account corresponding to a login account number of the financing APP, an insurance account, a fund account and the like.
In practical applications, the user may confirm the fund transfer in various ways, and there may be several preferred schemes:
the first preferred scheme is as follows: and page confirmation, namely confirming by inputting confirmation information in a specified page by a user, as shown in fig. 3.
The designated page can be a designated repayment page, and after a corresponding button in the designated repayment page is triggered, the fund transfer to other users can be confirmed. The page confirmation mode can be confirmed by logging in a specified page through a mobile phone terminal, can also be confirmed by logging in the specified page through a computer terminal, and can also be confirmed by logging in the specified page through other computing equipment (PAD and the like).
The preferred scheme II is as follows: and interface confirmation, namely inputting confirmation information by a user through a corresponding data transmission interface for confirmation.
The data transmission interface corresponds to the user, and may be a data transmission interface dedicated to the user.
In practical applications, for large-scale financial institutions such as banks and insurance, corresponding data transmission interfaces may be allocated to the financial institutions in order to enhance the security of the confirmation process, and different financial institutions may confirm through their corresponding data transmission interfaces.
The preferable scheme is three: and confirming the file, namely uploading a corresponding confirmation file by the user for confirmation.
Typically, the user may determine to make the transfer of funds by uploading a confirmation file. After receiving the confirmation files, the server analyzes the files to determine the target fund account and the fund amount to be transferred into the target account.
Of course, after the user confirms that the funds are transferred to the target account, the server may place the target account into a confirmation record table, where the fund accounts recorded in the confirmation record table are all the fund accounts to which the user confirms that the funds are transferred, each fund account corresponds to a time window, and the time window is a time window within which the user will complete the corresponding fund transfer process, and generally, the time window may be set to 3 days or 5 days, and the like.
As described above, the target fund account and the required fund amount are determined according to the confirmation information, and since the confirmation information generally includes the transferred object (i.e., the target fund account) and the amount of the transferred fund, the target fund account and the required fund amount can be determined.
It should be noted that, when a financial institution transfers funds, it is usually determined that a transfer is to be made to a financing requirement (purchase or repay to the financing requirement), the financing requirement is associated with a target fund account, and after the transfer to the financing requirement, the funds flow to the associated target fund account.
For example, a bank purchases a financing requirement A issued by company B for financing project funds, so that the financing requirement A is associated with an account (target fund account) of company B in the background, and after the bank determines to transfer funds to the financing requirement A, the server can determine the target fund account associated with the financing requirement A and the funds to be transferred through confirmation information.
Step S22: determining the funds to be transferred.
In practical applications, with the advent of the APP for funds transfer, a user will usually register a plurality of login accounts, each of which is applied to a different purpose. The account can be specially used for transferring funds, and the funds transferred into the login account by the user can be determined as the funds to be transferred.
For example, a payroll may be used for transferring funds, a financial institution may register a special financial account (referred to as an institution intermediary) with the payroll for transferring funds during financial transactions, and funds deposited by the financial institution into the institution intermediary may be determined as funds to be transferred.
Step S23: the amount of money to be transferred is matched with the required amount of money, and when the matching is successful, step S24 is performed.
Step S24: the funds to be transferred are frozen.
Determining the fund transferred into the designated account by the user as repayment fund
As used herein, freezing the funds to be transferred refers to setting the funds in a non-transferable, non-mortgage, and non-default state.
After determining the funds to be transferred, the amount of the funds to be transferred may be matched with the required amount of funds, and when the matching is successful, the funds to be transferred may be frozen.
For example, the financial institution deposits 10 ten thousand yuan (fund to be transferred) into the intermediary of the institution, determines the information of the transfer through the financial institution, determines the required fund amount (fund amount for the fund transfer) to be 10 ten thousand yuan, matches the amount of the fund to be transferred with the required fund amount, and freezes 10 ten thousand yuan of the fund to be transferred when the matching is successful.
In practical applications, when the funds to be transferred are frozen, a thawing code for thawing the funds to be transferred can also be generated, and the funds to be transferred can be thawed through the thawing code when needed.
Of course, when the matching between the funds to be transferred and the required funds amount fails, the matching failure may be caused by a surplus of the funds to be transferred or less than the required funds amount, and the funds may be selected not to be frozen according to a specific application scenario, or may be frozen according to needs.
For example, the financial institution repays the financing demand, if the amount of the fund deposited into the intermediate user of the institution by the financial institution is less than the required fund amount, the matching is failed, and the fund can be selected not to be frozen due to insufficient fund; if the amount of the fund deposited by the financial institution to the intermediary of the institution is larger than the required fund amount, the fund can be selectively frozen so as to prevent the fund from being called by other financing requirements. Of course, in other application scenarios, when the matching fails, the selection can be performed according to the requirement.
In addition, when the matching fails, prompt information can be sent to the user to prompt the user that the deposited funds to be transferred are not matched with the fund amount to be transferred.
Step S25: when a funds transfer instruction for the target funds account is received, the funds are thawed and transferred to the target funds account.
After freezing the funds to be transferred, the server will receive instructions to transfer the funds to the target funds account, typically upon arrival at the point in time of the transfer. The time point is usually related to the time window, and may be a time point within the time window set by the user.
For example, the user 3/month 4 determines to perform the fund transfer, the time window is 3 days (i.e. it is required to complete the fund transfer at the latest 24 o ' clock of 3/month 6), the transfer time point may be 24 o ' clock of 3/month 6, 17 o ' clock of 3/month 6, or may be set to a certain time point in the time window according to the needs of the user (for example, the user is set to 10 am of 3/month 6).
When the time point arrives, the server receives a fund transfer instruction initiated according to the target fund account in the confirmation record table, and the server is instructed to unfreeze the fund to be transferred and transfer the fund to the target fund account. Of course, in practical application, the server may receive the instruction to transfer the funds according to the active trigger of the user. When the funds to be transferred are defrosted, the funds to be transferred can be defrosted according to the generated defreezing code.
It should be noted that, in practical applications, after a user confirms to perform a fund transfer, a server may monitor a login account (serving as a resource pool) used by the user to transfer the fund, and when it is monitored that the resource pool has the fund, a plurality of fund transfer instructions are generally received, and the fund transfer instructions are respectively directed to each account in the confirmation record table, so that after receiving the fund transfer instruction, the server needs to determine whether the fund transfer instruction is directed to a target fund account.
The fund transfer instruction may generally include a second fund account and a target fund account, and when the matching is successful, it indicates that the received fund transfer instruction is directed to the target fund account, the frozen fund may be thawed and transferred to the target fund account according to the fund transfer instruction, and when the matching is unsuccessful, it indicates that the received fund transfer instruction is not directed to the target fund account, and at this time, since the fund to be transferred is frozen, the fund cannot be transferred to the second fund account.
Therefore, step S25 may be embodied as step S251,
step S251: and matching a second fund account in the fund transfer instruction with the target fund account when the fund transfer instruction is received, and unfreezing the fund to be transferred and transferring the fund to the target fund account if the matching is successful.
By adopting the method provided by the embodiment 2, after the amount of the fund to be transferred is successfully matched with the required fund amount, the fund to be transferred is frozen, even if the server receives an instruction for transferring the fund to be transferred to other fund accounts except the target fund account, the fund transfer process cannot be completed, and only after the instruction for transferring the fund to be transferred to the target fund account is received, the fund can be unfrozen and the fund transfer is completed, so that the problems in the prior art are solved.
For example, the server receives confirmation information that the user A transfers funds to the user B in 6 months and 5 days, and puts the user B into a confirmation record table, wherein the specified time window is 3 days; and then, the server receives confirmation information of transferring the funds from the user A to the user C again in 6 th month and places the user C into a confirmation record table, wherein the confirmation record table comprises the user B and the user C (assuming that the transferred fund amount degrees are the same), and the 6 th month and 7 th user A places the funds into a designated fund account (resource pool) for transferring to the user B.
In the prior art, the server does not freeze the fund, so that the network resource may be transferred to the user C when receiving an instruction to transfer the fund to the user C, or the network resource may be transferred to the user B when receiving an instruction to transfer the fund to the user B, and the fund cannot be transferred to a specific user. In addition, in practical application, since No. 7 is the deadline for transferring the funds to the user B, if the funds are transferred to the user C, the funds may be transferred to the user B for an overdue period, which brings default risks to the user a.
By adopting the method, the server freezes the fund placed into the fund pool by the user A in 6 th and 7 th, and in the time window, even if an instruction for transferring the fund to the user C is received, the fund cannot be transferred, and only if the instruction for transferring the fund to the user B is received, the fund can be unfrozen and transferred to the user B, so that the problems in the prior art are solved.
Users such as financial institutions often encounter situations where payments to financing needs or other users are required during the actual funds transfer process. Therefore, the fund transfer method of embodiment 2 may also be specifically a repayment method, as shown in fig. 4, where the repayment method specifically includes the following steps:
step S31: and receiving repayment confirmation information and determining a repayment target account and a required repayment fund limit according to the confirmation information.
The server receives the payment confirmation information in step S31, which may be the same as the manner in which the server receives the confirmation information of the fund transfer in step S21, and the server may generally receive the payment confirmation information (corresponding to page confirmation) input by the payment user through the designated page; or, the receiving repayment user inputs repayment confirmation information (corresponding interface confirmation) through the appointed data transmission interface; or receiving a payment file (corresponding file confirmation) which is uploaded by the payment user and confirms payment.
The payment user here refers to a user who makes a payment, and the payment user may be a company, a financial institution, or an individual. For example, if financial institution A makes a payment to user B, then financial institution A is the payment user.
The financial institution can also pay to a certain financing demand when paying, the confirmation information of the payment user generally comprises the information of the financing demand, and a payment target account associated with the financing demand and the required payment amount can be determined through the information of the financing demand.
For example, the bank pays a financing demand A, the confirmation information of the bank confirming the payment comprises the information of the financing demand A, and the information of the financing demand A is associated with a payment target account and a payment amount needing to be paid to the payment target account. In addition, in practical applications, there may be a plurality of repayment target accounts, and the repayment amount of each repayment target account is usually different.
Step S32: and determining repayment funds.
Funds transferred by the repayment user into the designated account may be determined as repayment funds.
For example, funds transferred by the financial institution to the intermediary of the payroll may be determined as repayment funds.
Step S33: matching the amount of the repayment fund with the required repayment fund amount, and executing the step S34 when the matching is successful.
Step S34: the repayment funds are frozen.
Freezing the repayment funds refers to setting the repayment funds in a non-transferable, non-mortalable, and non-houseable state. When the repayment funds are frozen, a corresponding unfreezing code may also be generated.
When a plurality of repayment target accounts are provided, each repayment target account corresponds to different repayment amounts respectively, and the required repayment fund amount is the sum of each repayment amount. The matching of the amount of the repayment fund with the required repayment fund amount is to match the amount of the repayment fund with the sum of the repayment amounts respectively corresponding to the repayment target accounts.
For example, the user a and the user b purchase the financing requirement issued by the insurance company c, the insurance company c needs to pay for the financing requirement after the financing requirement expires, and the information of the financing requirement is included in the information of payment confirmation of the insurance company c, and is associated with (the account of) the user a and (the account of) the user b.
Of course, when the matching fails, the repayment fund can be frozen or not frozen according to specific situations. And after the matching fails, prompt information of the matching failure can be sent to the user.
Step S35: when a fund transfer instruction aiming at the repayment target account is received, unfreezing the repayment fund and transferring the repayment fund into the repayment target account.
Generally, when the repayment time point arrives, the server receives an instruction for transferring the repayment funds to the repayment target account, so that the repayment funds are unfrozen and transferred to the repayment target account. Of course, the repayment funds can also be defrosted through the corresponding defreezing code.
Similar to the aforementioned time points, the payment time point here is also usually related to the time window, or may be set by the user himself, and at a certain time point in the time window, which is not described herein again.
In addition, when the financial institution repays the financing demand, because the financing demand is usually associated with a plurality of investor accounts, after the repayment fund is thawed, the repayment fund can be divided into a plurality of corresponding funds, and the corresponding funds are respectively transferred to the corresponding investor accounts.
In practical applications, after a repayment user confirms to make a repayment, a server monitors a login account (as a resource pool) used by the repayment user for repayment, and when it is monitored that funds exist in the resource pool, a plurality of repayment instructions are generally received, and the repayment instructions are respectively directed to each repayment account in a confirmation record table, so that after receiving the repayment instruction, the server needs to determine whether the repayment instruction is directed to a repayment target account.
Generally, after receiving a repayment instruction, a server may match a repayment instruction including a second repayment account with a repayment target account, and when the matching is successful, it indicates that the received repayment instruction is directed to the repayment target account, the frozen repayment fund may be thawed according to the repayment instruction and transferred to the repayment target account, and when the matching is unsuccessful, it indicates that the received repayment instruction is not directed to the repayment target account, and at this time, because the repayment fund is frozen, the fund cannot be transferred to the second repayment account.
Thus, step S35 may be embodied as step S351,
step S351: and when a repayment instruction is received, matching a second repayment account in the repayment instruction with the repayment target account, and if the repayment instruction is successfully matched with the repayment target account, unfreezing the repayment fund and transferring the repayment fund into the repayment target account.
In this embodiment, the payment method is developed in the order of step S31 to step S35, but in practical applications, the payment method may be executed in another order. For example, the repayment user may transfer the repayment funds to the designated account and then make a determination on the repayment, and the server may perform step S32 and then perform step S31. Therefore, the payment method provided by the embodiment of the present application is only exemplified here, and the method by changing the sequence of the steps is also within the protection scope of the present application.
The repayment method provided by the application can be realized in a hardware mode and can also be realized in a software mode. The following is an example description of each functional module of the server when the server performs payment service processing.
In general, the server can be functionally divided into the following modules: the device comprises a confirmation module, a monitoring module, a freezing module and a repayment operation module.
The system comprises a confirming module, a page repayment confirming submodule, an interface repayment confirming submodule and a file repayment confirming submodule, wherein the confirming module is used for receiving corresponding repayment confirming information after a user confirms repayment, and confirming a repayment target account and a required repayment fund amount according to the confirming information; the monitoring module is used for placing the repayment target account into the confirmation record table and monitoring the fund in the fund pool, and can carry out real-time monitoring when monitoring the fund in the fund pool, and also can set a certain monitoring period (for example, 5 minutes) for carrying out periodic monitoring; the freezing module is used for matching the amount of the fund with the repayment fund amount determined by the confirming module when the monitoring module finds that the fund is in the fund pool, and freezing the fund after the matching is successful; and the repayment operation module unfreezes the fund and transfers the fund into the repayment target account after receiving a repayment instruction aiming at the repayment target account.
In addition, in practical application, the modules or the sub-modules can be mutually split and combined to form a new service module according to needs.
For example, the page repayment confirmation submodule, the interface repayment confirmation submodule and the freezing module in the confirmation module are combined into a first repayment module, and the first repayment module may function as: 1. initiating page payment or interface payment under the condition that a user confirms through a page or an interface; 2. matching and freezing the fund; 3. when the monitoring module monitors that the fund pool has funds, calling a repayment operation module to repay the funds; and the number of the first and second groups,
the file repayment confirmation submodule is used as a second repayment module, and the repayment file is checked and the repayment operation module is called to initiate file repayment under the condition that the user confirms through the repayment file;
the monitoring module and the payment operation module may be the same as described above.
For further explanation of the repayment method provided by the application, the application scenario of repayment from financing demand by financial institution through application APP can be combined for explanation. In this application scenario, the repayment user is a financial institution, and the institution intermediary is an account used by the financial institution in the APP for repayment, as shown in fig. 5, which is a schematic diagram of each step.
Step S41: the financial institution sends repayment confirmation information to the server through the APP;
the repayment confirmation information is used for confirming the repayment to the financing requirement; the server, upon receiving the payment confirmation message, indicates that the financial institution will pay for the financing requirement within a specified time window (typically 3 days). And, the server may determine the corresponding financing requirement and the amount of the required repayment fund according to the repayment confirmation information, and of course, the financing requirement is associated with a repayment target account (including an investor account 1, an investor account 2, an investor account N, and the like) for purchasing the financing requirement.
Step S42: the financial institution injects repayment fund to the institution intermediate user;
the server is able to determine funds in the institution intermediary as repayment funds, which may be described generally as a "fund pool" in the institution intermediary image.
Step S43: matching the amount of the repayment fund in the institution intermediate house with the amount of the required repayment fund, and freezing the repayment fund in the institution intermediate house when the matching is successful.
Step S44: and at a repayment time point, the server receives a repayment instruction to the financing requirement, and instructs to thaw the fund in the institution intermediate account and repay the fund to the investor account.
Step S45: the server defrosts the funds on the intermediate users of the institutions and transfers the corresponding funds to the accounts of the investors.
As shown in fig. 6, the fund transfer process is from step S41 to step S45. The financial institution injects the fund (repayment fund) into the fund pool, freezes the fund in the fund pool, so that the fund is unfrozen and the transfer is realized after the server receives the transfer to the repayment target account (the investor account 1, the investor account N and the like).
Example 3
Based on the same inventive concept as embodiment 2, embodiment 3 of the present application provides a money transfer apparatus. As shown in fig. 7, the apparatus 70 includes: a first determination unit 701, a first matching unit 702, a first freezing unit 703 and a funds-transfer unit 704, wherein:
a first determining unit 701, configured to receive confirmation information of fund transfer and determine a target fund account and a required fund amount according to the confirmation information;
a first matching unit 702, which matches the amount of funds to be transferred with the required fund amount;
the first freezing unit 703, if match succeed, freeze the fund to be transferred;
and a fund transfer unit 704 for unfreezing and transferring the fund to be transferred into the target fund account when receiving the fund transfer instruction aiming at the target fund account.
With the device 70 provided in embodiment 3 of the present application, since the device 70 employs the same inventive concept as embodiment 2, the problems of the prior art can be solved. In addition, in practical applications, the apparatus may be combined with specific hardware devices to achieve other implementation effects. For example, the servers are provided in the form of a distributed system, the first determination unit 701, the first matching unit 702, the first freezing unit 703, and the fund transfer unit 704 are respectively arranged in different servers in the distributed system, and fund transfer is performed by mutual coordination of the distributed system, so that the processing efficiency is higher compared with the case where each functional unit is provided in the same server.
Example 4
The fund transfer device can be used in a payment application scenario, and therefore embodiment 4 of the present application provides a payment device. As shown in fig. 8, the payment apparatus 80 includes: a second determination unit 801, a second matching unit 802, a second freezing unit 803, and a payment unit 804, wherein:
a second determining unit 801, receiving payment confirmation information and determining a payment target account and a required payment fund amount according to the confirmation information;
the second matching unit 802 matches the amount of the repayment fund with the required repayment fund amount;
a second freezing unit 803, which freezes the repayment fund if the matching is successful;
a repayment unit 804, which unfreezes the repayment fund and transfers the repayment fund into the repayment target account when receiving a repayment instruction for the repayment target account
The payment apparatus 80 provided in embodiment 4 of the present application can obviously solve the problem in the prior art in the application scenario of payment, and is not described here again.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in the process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The above are merely examples of the present application and are not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (10)
1. A method for transferring network resources is characterized by comprising the following steps:
receiving confirmation information of resource transfer, and determining a plurality of target accounts and resource values corresponding to the target accounts according to the confirmation information, wherein the confirmation information is confirmation information of transferring network resources from a resource transferring-out direction to a resource transferring-in direction;
matching the resource value of the network resource to be transferred with the sum of the resource values corresponding to the target accounts;
freezing network resources to be transferred when the matching is successful, wherein the network resources to be transferred comprise network resources transferred into a resource pool;
when the matching fails, if the resource value of the network resource to be transferred is smaller than the sum of the resource values corresponding to the target accounts, the network resource to be transferred is not frozen, and if the resource value of the network resource to be transferred is larger than the sum of the resource values corresponding to the target accounts, the network resource to be transferred is frozen;
when a resource transfer instruction aiming at the target account is received, unfreezing the network resource and transferring the network resource into the target account;
wherein, the unfreezing and transferring the network resource into the target account specifically comprises the following steps:
matching a second account included in the resource transfer instruction with a target account;
when the matching is successful, unfreezing the network resources to be transferred according to the resource transfer instruction;
splitting the network resources to be transferred into corresponding sub-network resources according to the resource values corresponding to the target accounts;
and transferring each sub-network resource to the corresponding target account.
2. The method of claim 1, wherein when freezing network resources to be transferred, the method further comprises: and generating a unfreezing code for unfreezing the network resource.
3. The method of claim 1, wherein the freezing of the network resources to be transferred specifically comprises: and setting the network resources to be transferred into states of non-transferable, non-mortgage and non-subscriber.
4. A method of transferring funds, comprising:
receiving confirmation information of fund transfer and determining a plurality of target fund accounts and fund amount required by each target fund account according to the confirmation information, wherein the confirmation information is the confirmation information of fund transfer from a fund transfer-out party to a fund transfer-in party;
matching the amount of the fund to be transferred with the sum of fund amounts required by each target fund account;
if the matching is successful, freezing the fund to be transferred, wherein the fund to be transferred comprises the fund transferred into the resource pool;
when the matching fails, if the resource value of the network resource to be transferred is smaller than the sum of the resource values corresponding to the target accounts, the network resource to be transferred is not frozen, and if the resource value of the network resource to be transferred is larger than the sum of the resource values corresponding to the target accounts, the network resource to be transferred is frozen;
when a fund transfer instruction aiming at the target fund account is received, unfreezing fund to be transferred and transferring the fund to the target fund account;
the step of unfreezing the funds to be transferred and transferring the funds to the target fund account specifically comprises the following steps:
matching a second account included in the fund transfer instruction with a target fund account;
when the matching is successful, the fund to be transferred is unfrozen according to the fund transfer instruction;
dividing the funds to be transferred into a plurality of corresponding funds according to the fund amount required by each target fund account;
and transferring the split funds to the corresponding target fund account.
5. A method of repayment, comprising:
receiving repayment confirmation information and determining a plurality of repayment target accounts and repayment fund amounts required by the repayment target accounts according to the confirmation information, wherein the confirmation information is confirmation information of fund transfer from a fund transfer direction to a fund transfer party;
matching the sum of the repayment fund with the sum of the repayment fund amount required by each repayment target account;
if the matching is successful, the repayment fund is frozen, and the repayment fund comprises fund transferred into the resource pool;
when the matching fails, if the resource value of the network resource to be transferred is smaller than the sum of the resource values corresponding to the target accounts, the network resource to be transferred is not frozen, and if the resource value of the network resource to be transferred is larger than the sum of the resource values corresponding to the target accounts, the network resource to be transferred is frozen;
when a repayment instruction aiming at the repayment target account is received, unfreezing the repayment fund and transferring the repayment fund into the repayment target account;
the step of unfreezing the repayment fund and transferring the repayment fund into the repayment target account specifically comprises the following steps:
matching a second account included in the resource transfer instruction with a target account;
when the matching is successful, unfreezing the repayment fund according to the resource transfer instruction;
dividing the repayment fund into a plurality of corresponding fund shares according to the repayment fund amount required by each repayment target account;
and transferring the split funds to the corresponding repayment target account.
6. The method of claim 5, wherein the method further comprises: and determining the funds injected into the designated account by the repayment user as repayment funds.
7. The method of claim 5, wherein receiving payment confirmation information is embodied as:
receiving payment confirmation information input by a payment user through a designated page; or the like, or, alternatively,
receiving payment confirmation information input by a payment user through a specified data transmission interface; or the like, or, alternatively,
and receiving a repayment file which is uploaded by a repayment user and used for confirming the repayment.
8. The method of claim 5, wherein the instruction to transfer the funds to the target funds account is received upon arrival of a payment time point.
9. A funds-transfer apparatus, comprising: a first determination unit, a first matching unit, a first freezing unit, and a funds transfer unit, wherein:
the first determination unit is used for receiving confirmation information of fund transfer and determining a plurality of target fund accounts and fund amount required by each target fund account according to the confirmation information, wherein the confirmation information is the confirmation information of fund transfer from a fund transfer-out direction to a fund transfer party;
the first matching unit is used for matching the amount of the fund to be transferred with the sum of fund amounts required by each target fund account;
the first freezing unit freezes the fund to be transferred if the matching is successful, wherein the fund to be transferred comprises the fund transferred into the resource pool; when the matching fails, if the resource value of the network resource to be transferred is smaller than the sum of the resource values corresponding to the target accounts, the network resource to be transferred is not frozen, and if the resource value of the network resource to be transferred is larger than the sum of the resource values corresponding to the target accounts, the network resource to be transferred is frozen;
the fund transfer unit unfreezes the fund to be transferred and transfers the fund to the target fund account when receiving a fund transfer instruction aiming at the target fund account;
wherein the funds-transfer unit is to:
matching a second account included in the resource transfer instruction with a target account;
when the matching is successful, the fund to be transferred is unfrozen according to the resource transfer instruction;
dividing the funds to be transferred into a plurality of corresponding funds according to the fund amount required by each target fund account;
and transferring the split funds to the corresponding target fund account.
10. A payment device, comprising: second confirm unit, second matching unit, second freezing unit and repayment unit, wherein:
the second determining unit is used for receiving repayment confirmation information and determining a plurality of repayment target accounts and repayment fund amounts required by the repayment target accounts according to the confirmation information, wherein the confirmation information is confirmation information of fund transfer from a fund transfer party to a fund transfer party;
the second matching unit is used for matching the sum of the repayment fund and the sum of the repayment fund amount required by each repayment target account;
the second freezing unit is used for freezing the repayment fund if the matching is successful, wherein the repayment fund comprises fund transferred into the resource pool; when the matching fails, if the resource value of the network resource to be transferred is smaller than the sum of the resource values corresponding to the target accounts, the network resource to be transferred is not frozen, and if the resource value of the network resource to be transferred is larger than the sum of the resource values corresponding to the target accounts, the network resource to be transferred is frozen;
the repayment unit is used for unfreezing the repayment fund and transferring the repayment fund into the repayment target account when receiving a repayment instruction aiming at the repayment target account;
wherein the repayment unit is used for:
matching a second account included in the resource transfer instruction with a target account;
when the matching is successful, unfreezing the repayment fund according to the resource transfer instruction;
dividing the repayment fund into a plurality of corresponding fund shares according to the repayment fund amount required by each repayment target account;
and transferring the split funds to the corresponding repayment target account.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610717716.2A CN106897924B (en) | 2016-08-24 | 2016-08-24 | Network resource transfer method, fund transfer method, payment method and device |
| CN202210115769.2A CN114549156A (en) | 2016-08-24 | 2016-08-24 | Network resource transfer method, fund transfer method, repayment method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610717716.2A CN106897924B (en) | 2016-08-24 | 2016-08-24 | Network resource transfer method, fund transfer method, payment method and device |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210115769.2A Division CN114549156A (en) | 2016-08-24 | 2016-08-24 | Network resource transfer method, fund transfer method, repayment method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106897924A CN106897924A (en) | 2017-06-27 |
| CN106897924B true CN106897924B (en) | 2021-12-10 |
Family
ID=59191625
Family Applications (2)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210115769.2A Pending CN114549156A (en) | 2016-08-24 | 2016-08-24 | Network resource transfer method, fund transfer method, repayment method and device |
| CN201610717716.2A Active CN106897924B (en) | 2016-08-24 | 2016-08-24 | Network resource transfer method, fund transfer method, payment method and device |
Family Applications Before (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210115769.2A Pending CN114549156A (en) | 2016-08-24 | 2016-08-24 | Network resource transfer method, fund transfer method, repayment method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (2) | CN114549156A (en) |
Families Citing this family (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109802916B (en) * | 2017-11-16 | 2022-04-15 | 财付通支付科技有限公司 | Resource transfer method, system, server and computer readable storage medium |
| CN108038684A (en) * | 2017-12-28 | 2018-05-15 | 泰康保险集团股份有限公司 | A kind of method of payment, device, medium and electronic equipment |
| CN110009320B (en) * | 2018-01-04 | 2024-04-16 | 财付通支付科技有限公司 | Resource conversion method, device, system, storage medium and computer equipment |
| CN110473109B (en) * | 2018-05-11 | 2022-10-28 | 腾讯科技（深圳）有限公司 | Resource data processing method and device, computer readable medium and electronic equipment |
| CN109064072A (en) * | 2018-09-20 | 2018-12-21 | 阿里巴巴集团控股有限公司 | The method, apparatus and electronic equipment of risk control |
| CN109345221A (en) * | 2018-09-25 | 2019-02-15 | 阿里巴巴集团控股有限公司 | The checking method and device of resource circulation |
| CN109544333A (en) * | 2018-10-22 | 2019-03-29 | 阿里巴巴集团控股有限公司 | Resource borrows or lends money method and apparatus |
| CN111610897B (en) * | 2019-02-22 | 2023-05-02 | 阿里巴巴集团控股有限公司 | Asset transfer prompting method and device and electronic equipment |
| CN110517156B (en) * | 2019-08-26 | 2023-05-19 | 创新先进技术有限公司 | Man-machine interaction method, system and equipment for guarantee service |
| CN111045568B (en) * | 2019-12-20 | 2021-05-14 | 腾讯科技（深圳）有限公司 | Virtual article processing method, device, equipment and storage medium based on block chain |
| CN111383098A (en) * | 2020-03-25 | 2020-07-07 | 中国建设银行股份有限公司 | Resource distribution method and device |
| CN111582849A (en) * | 2020-03-30 | 2020-08-25 | 苏宁金融科技(南京)有限公司 | Resource conversion method, device, storage medium and computer equipment |
| CN111652623A (en) * | 2020-05-29 | 2020-09-11 | 支付宝(杭州)信息技术有限公司 | Frozen account unfreezing data processing method, device and equipment |
| CN112001595B (en) * | 2020-07-23 | 2023-06-30 | 苏州达家迎信息技术有限公司 | Resource splitting method and device |
| CN112258187A (en) * | 2020-11-23 | 2021-01-22 | 中国银联股份有限公司 | Resource transfer method, server, exchange device, system and storage medium |
| CN112862430B (en) * | 2021-01-19 | 2024-05-21 | 浙江网商银行股份有限公司 | Resource issuing processing method and device |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103985033A (en) * | 2014-06-11 | 2014-08-13 | 开鑫贷融资服务江苏有限公司 | Method for implementing internet payment and internet payment platform |
| CN105205716A (en) * | 2015-10-28 | 2015-12-30 | 平安科技（深圳）有限公司 | Credit card repayment method and device |
| CN105868973A (en) * | 2016-04-15 | 2016-08-17 | 腾讯科技（深圳）有限公司 | Event resource handling method and event resource handling device |
Family Cites Families (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2002074002A (en) * | 2000-08-30 | 2002-03-12 | Ogaki Kyoritsu Bank Ltd | Loan repayment method and loan repayment system |
| CN101567070A (en) * | 2008-04-24 | 2009-10-28 | 中国银联股份有限公司 | Method and system for processing transaction data and payment system |
| US20130030971A1 (en) * | 2011-07-27 | 2013-01-31 | Reich & Tang Deposit Solutions, L.L.C. | Systems and methods for allocating funds between multiple banking products |
| US20160042449A1 (en) * | 2013-02-05 | 2016-02-11 | Cachet Financial Solutions Inc. | Micro lending method and apparatus |
| CN104751266B (en) * | 2013-12-31 | 2018-07-06 | 腾讯科技（深圳）有限公司 | Data processing method, value-added server and system |
| US20150379488A1 (en) * | 2014-06-27 | 2015-12-31 | Clear Path Financial | Automated proactive electronic resource allocation processing system |
| CA2993677C (en) * | 2014-08-06 | 2021-08-10 | 10353744 Canada Ltd. | Interbank payment system and interbank payment method |
| CN105589658B (en) * | 2014-11-13 | 2020-11-03 | 菜鸟智能物流控股有限公司 | Resource processing method, system and server, and warehouse management method and device |
| CN104915882A (en) * | 2015-05-29 | 2015-09-16 | 深圳市银信网银科技有限公司 | Loan repaying processing method and system |
| CN105554072A (en) * | 2015-12-07 | 2016-05-04 | 深圳市银信网银科技有限公司 | Data interaction processing method and device and on-line money borrowing method |
-
2016
- 2016-08-24 CN CN202210115769.2A patent/CN114549156A/en active Pending
- 2016-08-24 CN CN201610717716.2A patent/CN106897924B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103985033A (en) * | 2014-06-11 | 2014-08-13 | 开鑫贷融资服务江苏有限公司 | Method for implementing internet payment and internet payment platform |
| CN105205716A (en) * | 2015-10-28 | 2015-12-30 | 平安科技（深圳）有限公司 | Credit card repayment method and device |
| CN105868973A (en) * | 2016-04-15 | 2016-08-17 | 腾讯科技（深圳）有限公司 | Event resource handling method and event resource handling device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106897924A (en) | 2017-06-27 |
| CN114549156A (en) | 2022-05-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106897924B (en) | Network resource transfer method, fund transfer method, payment method and device | |
| US20210287215A1 (en) | Resource transfer system | |
| US11321783B2 (en) | Method and device for data processing based on blockchain | |
| TWI756498B (en) | Fallback processing method and device for asset transfer, and electronic equipment | |
| CN110214334B (en) | Applying a distributed ledger to network payments as a financial transaction settlement and reconciliation | |
| US11367072B2 (en) | Private networks and content requests in a resource transfer system | |
| CN108876606B (en) | Asset transfer method and device and electronic equipment | |
| US9773237B2 (en) | Synchronous split payment transaction management | |
| US11481771B2 (en) | One way functions in a resource transfer system | |
| WO2018204548A1 (en) | Ledger management systems and methods | |
| JP6818034B2 (en) | Temporary consensus network within the resource transfer system | |
| CN109285069B (en) | Resource transfer method, device and server | |
| US11392944B2 (en) | Transfer costs in a resource transfer system | |
| CN110572457B (en) | Resource application method and device based on block chain, electronic equipment and storage medium | |
| CN111639125A (en) | Resource circulation method and device based on block chain | |
| CN110659993A (en) | Resource management method and device based on block chain network | |
| CN111986025A (en) | Loan transaction processing method and system based on block chain | |
| CN109754321B (en) | Data processing method and device, medium and terminal thereof | |
| WO2017060816A1 (en) | Private networks and content requests in a resource transfer system | |
| CN114118987B (en) | Cross-border money transfer method and device based on block chain and electronic equipment | |
| CN115293918A (en) | Cloud communication asset inter-row re-insurance method and system based on block chain | |
| CN113282671A (en) | Claims settlement method and device based on block chain and electronic equipment | |
| CN110264173B (en) | Block chain based bilateral service settlement method and node device | |
| CN114581227A (en) | Resource processing method, device and system | |
| CN114219617A (en) | Trusted payment method, device, computer equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20200923 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman, British Islands Applicant after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman, British Islands Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20200923 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman, British Islands Applicant after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20220411 Address after: Room 602, No. 618, Wai Road, Huangpu District, Shanghai 200010 Patentee after: Ant fortune (Shanghai) Financial Information Service Co.,Ltd. Address before: Ky1-9008 business centre, 27 Hospital Road, Georgetown, grand caiman, UK Patentee before: Innovative advanced technology Co.,Ltd. |