CA2987291C - Cross-funds management server-based payment system, and method, device and server therefor - Google Patents

Cross-funds management server-based payment system, and method, device and server therefor Download PDF

Info

Publication number
CA2987291C
CA2987291C CA2987291A CA2987291A CA2987291C CA 2987291 C CA2987291 C CA 2987291C CA 2987291 A CA2987291 A CA 2987291A CA 2987291 A CA2987291 A CA 2987291A CA 2987291 C CA2987291 C CA 2987291C
Authority
CA
Canada
Prior art keywords
funds
management server
merchant
server
client
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
Application number
CA2987291A
Other languages
French (fr)
Other versions
CA2987291A1 (en
Inventor
Yi Zhang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
10353744 Canada Ltd
Original Assignee
10353744 Canada Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority to CA3058558A priority Critical patent/CA3058558C/en
Priority to CA3058530A priority patent/CA3058530A1/en
Priority to CA3058529A priority patent/CA3058529C/en
Priority to CA3058595A priority patent/CA3058595C/en
Priority to CA3058598A priority patent/CA3058598C/en
Priority to CA3058560A priority patent/CA3058560C/en
Priority to CA3058553A priority patent/CA3058553C/en
Priority to CA3058527A priority patent/CA3058527C/en
Application filed by 10353744 Canada Ltd filed Critical 10353744 Canada Ltd
Priority to CA3058591A priority patent/CA3058591C/en
Publication of CA2987291A1 publication Critical patent/CA2987291A1/en
Application granted granted Critical
Publication of CA2987291C publication Critical patent/CA2987291C/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/16—Payments settled via telecommunication systems

Abstract

Disclosed are a cross-funds management server-based payment system, and a method, device and server therefor, belonging to the field of e-commerce. The method comprises: a second funds management server receives payment request information sent by a client end; the sum of a funds balance and a credit overdraft limit of the client end is compared with a payment amount, and it is determined whether an electronic commitment payment certificate can be opened; if so determined, the second funds management server respectively freezes the funds balance and the credit overdraft limit within a client end account, the funds balance and the credit overdraft limit corresponding to the payment amount; the electronic commitment payment certificate for the second funds management server to commit to pay funds according to an agreed condition is generated, and the electronic commitment payment certificate is sent to a merchant end to perform a credit commitment payment on behalf of the client end, and synchronised to an information centre server. Using the technical solution of the present invention to supervise both parties in a transaction reduces financial risk, and ensures the interests of both parties in the transaction.

Description

I

Title: CROSS-FUNDS MANAGEMENT SERVER-BASED PAYMENT SYSTEM, AND
METHOD, DEVICE AND SERVER THEREFOR
[1] [Technical Field]
[2] This invention refers to e-commerce field, especially, it is a cross funds server-based payment system and its method, device and server.
[3] [Background Technology]
[4] E-commerce has become increasingly widely used in a variety of commercial trade activities, the so-called e-commerce is a business operation model that based on the browser and server applications helps consumer realize online shopping, online transactions between merchants and online electronic payments, as well as a variety of business activities, trading activities, financial activities and related integrated service activities in the commercial trade, and in the Internet open network environment.
[5] At present, many banks or enterprises have provided a network of payment services, allowing customers to operate computers, mobile phones and other terminal equipment to achieve network payment, the way of the network payment provides customers with a great convenience. But in the process of network payment, the payment is conducted by directly using the existing funds in the debit cards or credit card, or allocating the credit limit of the existing funds or credit card to the third party as a guarantee for the transaction, once the merchant does not provide goods or service, or disputes occur, the financial security is difficult to be guaranteed. Thus, the need for new payment systems, methods, devices and servers at this stage to reduce the risk of user funds and to protect the interests of buyers and sellers.
[6] [Summary of the invention]
[7] In view of the above, the technical problem to be solved by the present invention is to provide a payment system, and its payment method, device and server based on a cross Funds-Management server to reduce the risk of user funds, and to protect the interests of buyers and sellers.
[8] The technical solution of the present invention to solve the above-mentioned technical problems is as follows:
[9] A payment system based on a cross Funds-Management server comprising at least one client, at least one merchant, information centre and client connected to the second Funds-Management server and the first Funds-Management server connected to the I

merchant, and the first Funds-Management server and second Funds-Management server respectively connected with the information centre server, wherein:
[10] The said client for sending payment request information including at least the payment amount to the said second Funds-Management server;
[11] The said Merchant for receiving the electronic commitment payment certificate sent by the second Funds-Management server;
[12] The method comprises: the second Funds-Management server is used for receiving payment request information sent by the second Funds-Management server;
comparing the sum of the request information of the client and the funds balance with the payment amount to determine whether an electronic commitment payment certificate can be created ; if possible, the second Funds-Management server will freeze the funds balance and credit overdraft limit within the said client and account, making the freezing funds exceeds or equals to the payment amount; generating the electronic commitment payment certificate of the second Funds-Management server to commit to pay funds according to the agreed condition, and sending the electronic commitment payment certificate to the Merchant to make a credit commitment payment on behalf of the client, and synchronize the electronic commitment payment certificate to the information centre server;
[13] The first Funds-Management server is configured to store the electronic payment document information transmitted by the second Funds-Management server and allocate the received payment amount to the Merchant and account based on the electronic payment document information;
[14] The information centre server for storing and supervising the electronic commitment payment certificate information.
[15] According to another aspect of the present invention, there is a payment method based on a cross Funds-Management server, the method comprises the steps of:
[16] The second Funds-Management server receives the payment request information sent by the client, wherein the payment request information includes at least the payment amount;
[17] Comparing the sum of the fund balance and the credit overdraft limit to determine whether an electronic commitment payment certificate can be generated to make a credit commitment payment;
[18] If possible, the second Funds-Management server will freeze the funds balance and credit overdraft limit within the said client and account, making the freezing funds exceeds or equals to the payment amount; generating the electronic commitment payment certificate of the second Funds-Management server to commit to pay funds according to the agreed condition, and sending the electronic commitment payment certificate to the merchant to I

make a credit commitment payment on behalf of the client, and synchronize the electronic commitment payment certificate to the information centre server.
[19] A payment device based on the cross Funds-Management server, the said device comprising a receiving module, a judging module and a processing module, wherein.
[20] The receiving module is configured to receive payment request information delivered by the terminal which is connected to the second Funds-Management server, wherein the payment request information includes a payment amount;
[21] A judgement module configured to compare the sum of the client fund balance and the credit overdraft amount and the payment amount to determine whether or not an electronic commitment payment document can be issued;
[22] A processing module configured to freeze the balance of funds and the amount of credit overdrafts in the client account when the payment is allowed so that the total amount of the freezing is greater than or equal to the payment amount; generating an electronic commitment payment certificate, and deliver it to the merchant connected to the first Funds-Management server, and synchronize the electronic commitment payment certificate to the information centre server.
[23] A server based on the cross Funds-Management server, which comprising a payment device according to any one of above claim.
[24] The present invention provides a payment system based on different Funds-Management server and its method, device and server, supervises the information of the buyers and sellers through the Funds-Management server and the information centre server, and the regulatory function is merged into the bank or other institutions with payment ability;
meanwhile, freezes the client account funds balance, generates electronic payment certificates and synchronize the information centre server for real-time monitoring, reduces the risk of funds to protect the interests of the buyers and the sellers; this program makes full use of the risk control centre function of the credit centre of the Funds-Management server and the information centre server, facilitates the security of on-line transactions and guarantees transaction funds with a more optimized credit mechanism, provides credit media for both parties to the transaction, and reduces the risk of funds through the supervision of funds to protect the interests of both parties. In addition, it brings convenience to the customer by adding loan functions, which also enriches businesses of banks or other institutions with credit payment ability.
[25] [Brief Description]
[26] Figure 1 is a schematic diagram of the payment system based on the cross Funds-Management server provided by the Example of the present invention;

I
[27] Figure 2 is a flow chart of the payment method based on the cross Funds-Management server provided by Example 2 of the present invention;
[28] Figure 3 is a flow chart of the payment method based on the cross Funds-Management server provided by Example 3 of the present invention;
[29] Figure 4 is a block diagram of a payment device based on the cross Funds-Management server provided by the Example 4 of the present invention;
[30] Figure 5 is a block diagram of a payment system based on a cross Funds-Management server provided by the Example 5 of the present invention.
[31] [Description of the Preferred Examples]
[32] The present invention will be described in further detail with reference to the accompanying drawings and the accompanying example, in which the technical problems, technical solutions and advantages to be solved by the present invention will become more apparent. It is to be understood that the specific examples described herein are merely illustrative of the invention and are not intended to limit the invention.
[33] Example 1
[34] As shown in Figure 1, an example of the present invention provides a cross Funds-Management server payment system comprising at least one client 10, at least one merchant 20, information centre 50 and first Funds-Management 30 and second Funds-Management 40 which is interconnected with each other, wherein:
[35] The client 10 is connected with server 40 of the second Funds-Management server for transmitting the payment request information to the second Funds-Management server 40, and the payment request information includes the payment amount.
[36] Specifically, the client 10 is suitable for the payer (buyer), including the account information of mobile phone, personal computer, PAD, and other intelligent devices, the account information of the client 10 is filled in when the customer registers and stored in the database of the Funds-Management service and (or) the information centre server, the account information of the client 10 includes customer ID, an account opening bank, account name, a bank account number, and a credit balance, and may also include the customer's shipping address. The payment request information is the information that the customer has written and confirmed shipping address information after the customer purchases the specific goods/services. According to the pre-set rules, price of the goods/services, and conunercial Merchants of the goods/services, the client 10 generates data package; the packet will be transmitted to the second Funds-Management server 40.
The payment request information includes at least the payment amount, and may include the Merchant information and the product information. Among them, the Merchant information can be directly the Merchant's receiving account, it can also uniquely identify the Merchant information (for an example, Merchant ID), by the Funds-Management server 40 on the unique identification of the merchant from the database to find the corresponding bank account information. In the specific application, the account information of the Merchant 20 should be kept confidential with respect to the client 10, so the Merchant information is preferably the Merchant ID, and the second Funds-Management server 40 inquires the Merchant's receiving account by using the corresponding relationship between the Merchant ID and its receiving account number. In other words, the client 10 only needs to inform the second Funds-Management server 40 to which Merchant and which goods to pay the amount of funds, the second Funds-Management server 40 will be able to call out the Merchant account to implement the appropriate payment operation.
[37] The Merchant 20 is connected to the first Funds-Management server 30 for receiving the electronic commitment payment certificate transmitted by the second Funds-Management server 40.
[38] Specifically, the Merchant 20 is adapted to the recipient (Merchant), and the Merchant includes but not limited to devices such as servers, and POS machines and so on.
Merchants include but not limited to manufacturers, agents, logistics companies, etc. The merchant information is also registered in the database of the Funds-Management server and (or) the information centre server, and the merchant information includes, but not limited to merchant ID, merchant name, merchant opening bank, merchant account name, and merchant bank account number. The Merchant 20 receives the electronic commitment payment voucher transmitted from the second Funds-Management server 40, and extracts the merchandise information and the goods receipt information in the electronic commitment payment voucher information to designate the merchandise transmission destination.
[39] The second Funds-Management server 40 receiving payment request information sent by a client 10; comparing the sum of a funds balance and a credit overdraft limit of the client 10 with a payment amount to determine whether an electronic commitment payment certificate can be created; if possible, the Funds-Management server respectively freezing the funds balance and the credit overdraft limit within a client and account, the funds balance and the credit overdraft limit corresponding to the payment amount;
generating the electronic commitment payment certificate for the second Funds-Management server 40 to commit to pay funds according to an agreed condition, and sending the electronic commitment payment certificate to a merchant 20 to make a credit commitment payment I

on behalf of the client and synchronize to the information centre server 50.
[40] Specifically, the second Funds-Management server 40 receives the packet of the payment request information and analyses it according to the reset rule to obtain the relevant payment information including but not limited to the Merchant information, the merchandise information, and the payment amount And other necessary information, that is, to which Merchant which goods to pay the amount of money. The second Funds-Management server 40 inquires whether the balance of the bank funds and the credit overdraft amount of the client account is sufficient for the current settlement, and if it is insufficient, the payment is terminated and, if sufficient, the balance of the payment amount and the amount of credit overdraft, So that the total amount of the freeze is greater than or equal to the amount of the payment, until the merchant confirms the delivery or the customer confirms the receipt after the transfer operation.
[41] It is understandable that the amount of funds to be frozen and the corresponding amount of credit overdrafts are included in the following cases:
[42] 1. Only the balance of the funds in the client account is frozen so that the total amount of the freeze is greater than or equal to the amount paid.
[43] 2. Only to freeze the amount of credit overdraft, so that the total amount of frozen greater than or equal to the amount of the payment.
[44] 3. Respectively, to freeze the balance of funds of the client account and credit overdraft limit, so that the total amount of frozen greater than or equal to the amount of the payment.
[45] The information centre server 50 is respectively connected to the Funds-Management server 30 and second Funds-Management server 40 for storing and supervising the electronic commitment payment certificate information of the client 10 and the merchant 20.
[46] Specifically, both the client 10 and the merchant 20 can obtain the electronic commitment payment certificate information to the information centre server 50 via the Internet for subsequent processing, such as the correctness of the dual channel authentication information using the data. The second Funds-Management server 40 may further determine whether or not the payment operation is made in accordance with the state of the electronic commitment to pay the certificate information, that is, the payment of the balance of the funds and the amount of the credit overdraft, credit limit.
[47] In the present example, the second Funds-Management server 40 may be connected to the plurality of clients 10 and via the Internet at the same time. The first Funds-Management server 30 may be connected to a plurality of Merchant terminals 20 and via the Internet at the same time. That is, the server where the Merchant 20 is located is not on the same I I

server as the server where the client 10 is located. The second Funds-Management server 40 and the first Funds-management server 30 can be a single server in the physical sense, or it can work in parallel for multiple servers in the physical sense, such as multiple physical servers. According to the different traffic, the resources of the server are automatically allocated to realize the Funds-Management. The second Funds-Management server 40 and the first Funds-Management server 30 includes but is not limited to servers in institutions such as banks, businesses, and so on. In the practical applications, it can be understood as the same bank's cluster Funds-Management server, but not limited to banks, but also the Internet to support the flow of funds in other institutions.
Through the Funds-Management server and information centre server, the seller and seller of information are regulated, and the regulatory functions are merged into the bank or other institutions with credit ability to pay.
[48] Example 2
[49] As shown in Figure 2, an example of the present invention provides a payment method based on a cross Funds-Management server for use in a Funds-Management server, which method comprises the following steps:
[50] S201, the client transmits the payment request information to the second Funds-Management server, and the payment request information includes the payment amount.
[51] Specifically, the payment request information received by the second Funds-Management server includes Merchant information, product information and payment amount, and it may also include the client information (for an example, client ID). Among them, the merchant information can be merchants' account number, and it can also be the only identification of the merchant information (such as merchant ID), to find the corresponding bank account information based on the unique identification of the business from the database by the second Funds-Management server. In the specific application, the account information of the Merchant should be kept confidential with respect to the client .so the Merchant information is preferably the Merchant ID, and the second Funds-Management server inquires the Merchant's receiving account by using the corresponding relationship between the Merchant ID and its receiving account number. In other words, the client only needs to inform the second Funds-Management server to which Merchant and which goods to pay the amount of funds, the second Funds-Management server will be able to call out the Merchant account to implement the appropriate payment operation.
[52] S202, the second Funds-Management server receives the client to send the payment request information;

I
[53] S203, inquiring the sum of the funds balance of the client account and the amount of the credit overdraft, comparing the sum of the funds balance and the amount of the credit overdraft with the payment amount, if the sum is greater than or equal to the amount, it is sufficient; if the sum is less than the amount, it is insufficient. When the funds balance and credit overdraft limit is sufficient, executing the Step S204, otherwise terminating, not to pay;
[54] S204, the second Funds-Management server to freeze the client account within the amount of payment corresponding to the balance of funds and credit overdraft capacity; understand that the amount of the corresponding payment of the corresponding amount of funds balance and credit overdraft capacity, including the following circumstances:
[55] 1. Only the balance of the funds in the client account is frozen so that the total amount of the frozen is greater than or equal to the payment amount.
[56] 2. Only to freeze the amount of credit overdraft limit, so that the total amount of frozen are greater than or equal to the amount of the payment.
[57] 3. Respectively, to freeze the balance of funds of the client account and credit overdraft limit, so that the total amount of frozen greater than or equal to the amount of the payment.
[58] S205, the second Funds-Management server generates the electronic commitment payment certificate based on the payment request information and the freezing information and transmits the electronic commitment payment certificate to the Merchant;
[59] Specifically, since the payment request information is sent by the buyer to the second Funds-Management server through the client's operation, the payment information is objectively confirmed by the customer and authorized by the bank. The second Funds-Management server freezes the corresponding funds and generates an electronic commitment payment certificate based on the payment information, and the Merchant provides the corresponding merchandise/service according to the electronic commitment payment certificate.
[60] S206, the second Funds-Management server sends the electronic payment certificate to the merchant and synchronizes to the information centre and first Funds-Management server.
Specifically, this Step sends the generated electronic certificate information to the information centre server so that the information centre server performs subsequent tracking.
[61] S207, the second Funds-Management server receives the payment information;
[62] S208, the second Funds-Management server allocates the funds corresponding to the freezing amount to the first Funds-Management server;
[63] S209, the first Funds-Management server transfers the received payment amount to the account of the Merchant.
[64] The payment method provided by the example of the present invention receives the payment request information of the client through the second Funds-Management server, determines whether the payment is permitted based on the sum of the funds balance and the payment amount of the client account, and by freezing the funds balance and the credit overdraft limit of the client account to generate electronic commitment payment certificate and synchronizes it to the information centre to supervise in real-time, which can reduce the risk of funds and protect the interests of the buyers and the sellers.
[65] Example 3
[66] As shown in Figure 3, an example of the present invention provides a payment method of the funds credit loan limit, applied in the same Funds-Management servers as shown in Figure 1, which is comprised of the steps as follows:
[67] S301, the client sends the payment request information to the second Funds-Management server, and the payment request information includes at least the payment amount.
[68] And the payment request information is composed of a plurality of data packets, including at least the Merchant information, the product information and the payment amount. You can also include client information (such as client ID). Among them, the merchant information can be directly merchants receiving account number, you can also uniquely identify the merchant information (such as business ID), and fmd the corresponding bank account information by Funds-Management server based on the unique identification of the merchant from the database. In the specific application, the account information of the merchant should be kept confidential with respect to the client, so the merchant information is preferably the merchant ID, and the Funds-Management server inquires the merchant's receiving account by using the correspondence relationship between the merchant ID and its receiving account. In other words, the client only need to inform the Funds-Management server to which merchant and which goods to pay the amount of funds, the Funds-Management server will be able to call out the account of the implementation of the corresponding payment operation.
[69] The way the client sends payment request information to the second Funds-Management server can be done in the existing way, such as using a digital signature or a digital envelope. A digital signature is a data that the user encrypts a hash of the original data with own private key. The information recipient obtains the hash digest by decrypting the digital signature attached to the original information using the public key of the sender of the information and confirms whether the original information is made by comparing with the hash digest generated by the original data received by the information recipient tampered I

I

with. This ensures that the data transmission is undeniable. Digital envelopes use password technology to ensure that only the recipient of the specified information can read the contents of the information. Digital envelopes used in a single-key password system and public key password system. The information sender first encrypts the information with the randomly generated symmetric password, and then encrypts the symmetric password with the public key of the receiver. The symmetric password encrypted by the public key is called the digital envelope. In the transmission of information, the information receiver shall decrypt the information, you must first use their own private key to decrypt the digital envelope, get a symmetric password, in order to use the symmetric password to decrypt the information obtained. This ensures the authenticity and integrity of the data transmission.
[70] S302, the Funds-Management server receives the payment request information sent by the client.
[71] Specifically, the payment request information received by the second Funds-Management server includes Merchant information, product information and payment amount, and it may also include the client information (for an example, client ID). Among them, the merchant information can be merchants' account number, and it can also be the only identification of the merchant information (such as merchant ID), to find the corresponding bank account information based on the unique identification of the business from the database by the second Funds-Management server. In the specific application, the account information of the Merchant should be kept confidential with respect to the client .so the Merchant information is preferably the Merchant ID, and the second Funds-Management server inquires the Merchant's receiving account by using the corresponding relationship between the Merchant ID and its receiving account number. In other words, the client only needs to inform the second Funds-Management server to which Merchant and which goods to pay the amount of funds, the second Funds-Management server will be able to call out the Merchant account to implement the appropriate payment operation.
[72] S303, inquiring the sum of the funds balance of the client account and the amount of the credit overdraft, comparing the sum of the funds balance and the amount of the credit overdraft with the payment amount, if the sum is greater than or equal to the amount, it is sufficient; if the sum is less than the amount, it is insufficient. When the balance of funds and credit overdraft is sufficient, executing Step S305, or executing steps;
[73] S304 asks the client whether to issue credit loan limit; if it is needed, executing Step S305, or terminating the process;
[74] S305, judging whether the credit loan limit is sufficient; the sufficient can be understood in several cases:

I
[75] 1. If the sum of the original funds balance of the client account and the amount of the credit overdraft limit as well as the credit loan limit are greater than or equal to the amount of the payment amount, the credit loan limit is considered to be sufficient; and conversely, it is insufficient;
[76] 2. When the credit loan limit is greater than or equal to the amount of the payment amount, the credit loan limit is considered to be sufficient and, conversely, insufficient.
[77] Specifically, the credit loan limit can be the amount specified by the client, or it can default to the amount of the current payment. For example, when the price of a product selected by the customer is 1,500 Yuan (payment amount), if the customer account funds balance and credit overdraft limit only 900 Yuan, you need credit loan limit of 600 Yuan in order to meet the allowable payment to pay the act. Of course, the using of another way, such as the direct application for credit loan limit of 1,500 Yuan, to pay, is also feasible.
[78] S306, the second Funds-Management server to freeze the client account within the balance of funds and credit overdraft limit and credit loan limit, so that the total amount of frozen are greater than or equal to the amount of the payment, it can be specifically divided into the following forms:
[79] 1. Only the balance of the funds in the client account is frozen so that the total amount of the frozen is greater than or equal to the payment amount.
[80] 2. Only the credit loan limit is frozen so that the total amount of the greater than or equal to the payment amount.
[81] 3. Only to freeze the amount of credit overdraft limit, so that the total amount of frozen are greater than or equal to the amount of the payment.
[82] 4. Respectively, to freeze the balance of funds and credit overdraft limit of the client's account, making the total amount of frozen greater than or equal to the amount of the payment.
[83] 5. Respectively, to freeze part of the balance of funds and credit loan limit of the client's account, making the total amount of frozen greater than or equal to the amount of the payment.
[84] 6. Respectively, to freeze part of the credit loan limit and credit overdraft limit of the client's account, making the total amount of frozen greater than or equal to the amount of the payment.
[85] 7. Respectively, to freeze part of the credit loan limit and credit overdraft limit of the client's account, as well as the funds balance, making the total amount of frozen greater than or equal to the amount of the payment.
[86] S307, the second Funds-Management server generates the electronic commitment payment I

certificate according to the payment request information and the freezing information;
[87] Specifically, since the payment request information is sent by the buyer to the second Funds-Management server through the client's operation, the payment information is objectively confirmed by the customer and authorized by the bank. The second Funds-Management server will freeze the corresponding the funds balance, credit overdraft limit or credit loan limit; meanwhile, it will generate an electronic commitment payment certificate based on the payment information, and the Merchant will provide the corresponding goods/services according to the electronic commitment payment certificate.
[88] S308, the second Funds-Management server delivers the electronic payment certificate to the merchant and synchronizes to the information centre and first Funds-Management server. Specifically, this Step sends the generated electronic certificate information to the information centre server so that the information centre server performs subsequent tracking.
[89] S309, the second Funds-Management server receives the payment information; it should be noted that In Step S408, the Merchant sends and receives the payment information to the Funds-Management server only as an example, and in practice, the client, a logistics server, or other entity that is aware of the delivery status to send payment information to the Funds-Management server.
[90] S310, the second Funds-Management server allocates the funds corresponding to the freezing amount to the first Funds-Management server; it is understood that there will be a corresponding matching fund allocation scheme according to the different freezing methods in Step S306, and the funds allocated to the account of the Merchant.
[91] S311, the first Funds-Management server transfers the received payment amount to the account of the Merchant
[92] Finally, the process is ended.
[93] The example of the present invention, on the basis of the second example, not only facilitates the buyer, but also greatly enriches the business of the bank or other institution with the credit payment ability by increasing the credit loan limit function;
In addition, by increasing the information centre can keep Buyers and sellers' electronic commitment certificate to track synchronization, the flow of commodity and the flow of funds trajectory can be effective combined to protect the interests of both buyers and sellers effectively.
[94] Example 4
[95] As shown in Figure 4, an example of the present invention provides a payment device including a receiving module 301, a judgement module 302, and a processing module 303, wherein:

I I
[96] The receiving module 301 is configured to receive payment request information delivered by the first Funds-Management server, wherein the payment request information includes a payment amount.
[97] Specifically, the payment request information received by the receiving module 301 includes Merchant information, product information and payment amount, and may include the client information (for an example, client ID). Among them, the merchant information can be merchants receiving account, and the merchant information can also be uniquely identified (such as business ID). In the particular application, the account information of the merchant should be kept confidential from the client, so the merchant information should be the merchant ID, that is, the client simply informs which merchandise of which merchant is paid by how much, then the device call out of the merchant account number to implement the corresponding payment operation.
[98] The judgement module 302 is configured to determine whether to pay based on the client' account fund balance and the credit overdraft limit as well as the payment amount.
[99] As a preferred scheme, the judgement module 302 is specifically configured to inquiry the client's account funds balance and the credit overdraft limit; and determined whether the funds balance and the credit overdraft limit of the client account are greater than or equal to the payment amount, if possible, it is allowed to pay. In this way, firstly to determine the payment ability of the sum of the funds balance and the credit overdraft limit, and priority to the use of account' funds balance and credit overdraft limit payment method, which can save the payment cycle to protect the interests of businesses. And the bank account or the credit card account may be notified by the client to the device in the payment request information, or the device may inquire from the database based on the client information and obtain the funds corresponding to the account funds balance or credit overdraft limit.
Only when the sum of the client's funds balance and credit overdraft limit are greater than or equal to the payment amount, it means that customers have the ability to pay and in this time it can be allowed to have payment behaviour.
[100] As another preferred example, the judgement module 302 is also configured to ask the client whether credit loan limit is to be issued when the sum of the fund balance and the credit overdraft limit of the client account is less than the payment amount;
if it needs credit loan limit, then the client account to issue credit loan limit and allow the payment; if not, then terminate the payment. In addition, it not only to facilitate the buyer, but also greatly enrich the bank or other institutions with credit ability to pay the business. When using a Funds-Management server to obtain a bank account or credit card account based on the Funds-Management server, a customer may have multiple accounts, and a mixed t I

payment method may also be used. For example, when the price of a commodity selected by the customer is 1,500 Yuan (the payment amount), the sum of the funds balance and the credit overdraft limit is only 900 Yuan, then the amount of money that the customer can use to pay is a total of 900 Yuan, which will not be able to pay; If the client account has credit loan limit amount of 600 Yuan, so the application of credit loan limit is 600 Yuan, then they have a 1,500 Yuan of using, can be implemented to be the payment behaviour.
[101] The processing module 303 configured to freeze the balance of funds, the credit overdrafts limit and credit loan limit in the client account when the payment is allowed so that the total amount of the freezing is greater than or equal to the payment amount;
generating an electronic commitment payment certificate, and deliver it to the merchant connected to the second Funds-Management server, and synchronize the electronic commitment payment certificate to the information centre server.
[102] Preferably, the processing module 303 further includes a freeze unit 3031, a certificate generation unit 3032, and a synchronization unit 3033, wherein:
[103] The freezing unit 3031 is configured to freeze the balance of the funds and the credit overdraft limit and the credit loan limit in the client account when the payment is allowed so that the total amount of the freezing are greater than or equal to the payment amount;
[104] The credential generation unit 3032 is configured to generate an electronic commitment payment certificate;
[105] The synchronization unit 3033 is configured to transmit the electronic commitment payment certificate information to the merchant.
[106] In addition, the processing module 303 may include a transfer unit, configured to receive the payment information, synchronize the payment information to the information centre server, and allocate the corresponding frozen funds to the merchant account in the Funds-Management server.
[107] It is important to note that the technical features of the above-described method examples 2 and 3 are applicable in the present apparatus and are not repeated here.
[108] In addition, the present invention also provides a Funds-Management server including the payment device in the fourth example, which is not repeated here.
[109] The payment method and server provided by the example of the present invention receives the payment request information of the client, determines whether the payment is permitted based on the sum of the funds balance and the credit overdraft limit of the client account, and by freezing the funds balance and the credit overdraft limit of the client account to generate electronic commitment payment certificate and synchronize the it to the information centre server to supervise in real-time, which can reduce the risk of funds and protect the interests of the buyers and the sellers. In addition, by increasing the loan function, not only to facilitate the buyer, but also greatly enrich the bank or other institutions with credit ability to pay the business.
[110] Example 5
[111] As shown in Figure 5, a preferred payment method provided by the example of the present invention based on a cross Funds-Management server, which includes client 10, the second Funds-Management server 40 connected to merchant 20 and client 10, merchant 20 connected to the Funds-Management server 30, and the information centre 50 connected to the first Funds-Management server 30 and second Funds-Management server 40 respectively. Among them:
[112] The information centre server 50 is used to store and supervise the electronic commitment payment certificate information.
[113] The client 10 includes a payment request module 101 configured to send payment request information to the second Funds-Management server 40, and the payment request information includes Merchant information, product information, and payment amount.
[114] The merchant 20 includes a certificate receiving module 201 and a certificate updating module 202, wherein the certificate receiving module 201 is configured to receive the electronic commitment payment certificate sent by the fund managing server 40.
[115] The second Funds-Management server 40 includes a receiving module 301, a judgement module 302, and a processing module 303, wherein:
[116] The receiving module 301 is configured to receive payment request information delivered by the client connected to second Funds-Management server 40;
[117] The judgement module 302 is configured to compare the sum of the client' funds balance and the credit overdraft limit and the payment amount to determine whether the electronic commitment payment document can be issued;
[118] As a preferred example, the judgement module 302 is configured to determine whether the funds balance and the credit overdraft limit of the client account is greater than or equal to the amount of the payment, and if so, the payment is allowed; Greater than or equal to the payment amount, if possible, then allow payment, or to further determine whether the client's account loan amount is greater than or equal to the payment amount, if so, allow to pay.
[119] The processing module 303 is configured to freeze the limit corresponding to the payment amount in the client account when payment is allowed, and generate an electronic commitment payment certificate to deliver the electronic commitment payment certificate information to the merchant 30 connected to the first Funds-Management server 30, and synchronized to the information centre server 50.
[120] As a preferred example, the receiving module 301 of the second Funds-Management server 40 is also responsible for receiving the payment information; the processing module 303 also includes a transferring module, synchronizes the payment information to the information centre server 50, which is configured to transfer equal funds to the account of the merchant 20 after receiving the payment information.
[121] Specifically, since the payment request information is sent by the buyer to the second Funds-Management server 40 through the client 10, the payment information is objectively obtained by the client 10 confirming and authorizing the bank to pay. The second Funds-Management server 40 respectively freezes the corresponding balance of funds and the amount of credit overdraft limit, and generates an electronic commitment payment certificate based on the payment information. The electronic commitment payment certificate information includes but is not limited to commodity information, payment amount (frozen funds or credit overdraft limit or credit loan limit), delivery address and validity period, the form is not limited to text, pictures, graphics and so on. The electronic commitment payment certificate is the certificate of the receiving fund of the Merchant 20, and the Merchant 20 provides the corresponding merchandise/service based on the electronic commitment payment certificate.
[122] The general technicians of this field can understand and implement all or parts of steps in the aforesaid examples that can complete the procedure by controlling relevant hardware, and the said procedure can be stored in a readable storage media of a computer such as ROM/RAM, disk and light disk.
[123] The preferred examples of the present invention have been described above with reference to the accompanying drawings, which are not to limit the scope of the present invention. It will be apparent to those skilled in the field that various modifications, equivalents, and improvements may be made without departing from the scope and spirit of the invention.

Claims (278)

Claims:
1. A
payment system for protecting both a client and a merchant in e-commerce transactions, the system comprising:
a client device;
a merchant device;
an information center server;
a first funds-management server; and a second funds-management server;
wherein the client device is configured to send a payment request for an e-commerce transaction to the second funds-management server, wherein the payment request includes a payment amount;
wherein the second funds-management server is configured to:
receive the payment request sent by the client device; and compare the amount in the payment request with an account balance and an overdraft limit of a client account;
when the amount in the payment request is less than the account balance and the overdraft limit added together the second funds-management server is further configured to:

freeze a freeze amount, within the client account, from the account balance and the overdraft limit, wherein the freeze amount is not less than the payment amount;
generate an electronic certificate, wherein the electronic certificate is configured to commit to pay the amount according to an agreed condition;
send the electronic certificate to the merchant device to make a credit commitment payment on behalf of the client; and synchronize the electronic certificate to the information center server;
wherein the merchant device is configured to receive the electronic certificate from the second funds-management server and wherein the merchant device is connected to the first funds-management server;
wherein the first funds-management server is configured to allocate the amount into a merchant account; and wherein the information center server is configured to store the electronic certificate.
2. The system of claim I wherein the first funds-management server is a single physical server.
3. The system of claim I wherein the first funds-management server is a single bank server.
4. The system of claim I wherein the first funds-management server is a single cluster server.
5. The system of claim I wherein the first funds-management server is a single cluster bank server.
6. The system of claim 1 wherein the second funds-management server is a single physical server.
7. The system of claim 1 wherein the second funds-management server is a single bank server.
8. The system of claim 1 wherein the second funds-management server is a single cluster server.
9. The system of claim 1 wherein the second funds-management server is a single cluster bank server.
10. The system of any one of claims 1-9 wherein the client device is configured for use by a buyer.
11. The system of any one of claims 1-9 wherein the client device is configured for use by a payer.
12. The system of any one of claims 1-11 wherein the client device is a mobile phone.
13. The system of any one of claims 1-11 wherein the client device is a computer.
14. The system of any one of claims 1-11 wherein the client device is a personal computer.
15. The system of any one of claims 1-11 wherein the client device is a PDA.
16. The system of any one of claims 1-11 wherein the client device is associated with client account information.
17. The system of claim 16 wherein the client account information includes a customer ID.
18. The system of any one of claims 16-17 wherein the client account information includes an account opening bank.
19. The system of any one of claims 16-18 wherein the client account information includes an account name.
20. The system of any one of claims 16-19 wherein the client account information includes a bank account number.
21. The system of any one of claims 16-20 wherein the client account information includes a credit balance.
22. The system of any one of claims 16-21 wherein the client account information includes a customer shipping address.
23. The system of any one of claims 1-22 wherein the payment request includes a shipping address.
24. The system of any one of claims 1-23 wherein the payment request includes shipping information.
25. The system of any one of claims 1-24 wherein the payment request includes goods information.
26. The system of any one of claims 1-25 wherein the payment request includes services information.
27. The system of any one of claims 1-26 wherein the payment request includes a data package.
28. The system of any one of claims 1-27 wherein the payment request includes merchant information.
29. The system of any one of claims 1-28 wherein the payment request includes product information.
30. The system of claim 28 wherein the merchant information includes a merchant receiving account.
31. The system of claim 28 wherein the merchant information includes a merchant identifier.
32. The system of any one of claims 1-31 wherein the merchant device is configured for use by a merchant.
33. The system of any one of claims 1-31 wherein the merchant device is a server.
34. The system of any one of claims 1-31 wherein the merchant device is a POS machine.
35. The system of any one of claims 1-31 wherein the merchant device is configured for use by a manufacturer.
36. The system of any one of claims 1-31 wherein the merchant device is configured for use by an agent.
37. The system of any one of claims 1-31 wherein the merchant device is configured for use by a logistics company.
38. The system of any one of claims 1-37 wherein the client device is connected to the Internet.
39. The system of any one of claims 1-38 wherein the merchant device is connected to the Internet.
40. The system of any one of claims 1-39 wherein the first funds-management server is connected to the Internet.
41. A client device comprising:
a computer processor; and a memory storage device;
wherein the client device is communicatively connected to a merchant device, an information center server, a first funds-management server and a second funds-management server;
wherein the client device is configured to send a payment request for an e-commerce transaction to the second funds-management server, wherein the payment request includes a payment amount;
wherein the second funds-management server is configured to:
receive the payment request sent by the client device; and compare the amount in the payment request with an account balance and an overdraft limit of a client account;
when the amount in the payment request is less than the account balance and the overdraft limit added together the second funds-management server is further configured to:

freeze a freeze amount, within the client account, from the account balance and the overdraft limit, wherein the freeze amount is not less than the payment amount;
generate an electronic certificate, wherein the electronic certificate is configured to commit to pay the amount according to an agreed condition;
send the electronic certificate to the merchant device to make a credit commitment payment on behalf of the client; and synchronize the electronic certificate to the information center server;
wherein the merchant device is configured to receive the electronic certificate from the second funds-management server and wherein the merchant device is connected to the first funds-management server;
wherein the first funds-management server is configured to allocate the amount into a merchant account; and wherein the information center server is configured to store the electronic certificate.
42. The client device of claim 41 wherein the first funds-management server is a single physical server.
43. The client device of claim 41 wherein the first funds-management server is a single bank server.
44. The client device of claim 41 wherein the first funds-management server is a single cluster server.
45. The client device of claim 41 wherein the first funds-management server is a single cluster bank server.
46. The client device of claim 41 wherein the second funds-management server is a single physical server.
47. The client device of claim 41 wherein the second funds-management server is a single bank server.
48. The client device of claim 41 wherein the second funds-management server is a single cluster server.
49. The client device of claim 41 wherein the second funds-management server is a single cluster bank server.
50. The client device of any one of claims 41-49 wherein the client device is configured for use by a buyer.
51. The client device of any one of claims 41-49 wherein the client device is configured for use by a payer.
52. The client device of any one of claims 4 1-5 1 wherein the client device is a mobile phone.
53. The client device of any one of claims 41-51 wherein the client device is a computer.
54. The client device of any one of claims 41-51 wherein the client device is a personal computer.
55. The client device of any one of claims 41-51 wherein the client device is a PDA.
56. The client device of any one of claims 41-51 wherein the client device is associated with client account information.
57. The client device of claim 56 wherein the client account information includes a customer ID.
58. The client device of any one of claims 56-57 wherein the client account information includes an account opening bank.
59. The client device of any one of claims 56-58 wherein the client account information includes an account name.
60. The client device of any one of claims 56-59 wherein the client account information includes a bank account number.
61. The client device of any one of claims 56-60 wherein the client account information includes a credit balance.
62. The client device of any one of claims 56-61 wherein the client account information includes a customer shipping address.
63. The client device of any one of claims 41-62 wherein the payment request includes a shipping address.
64. The client device of any one of claims 41-63 wherein the payment request includes shipping information.
65. The client device of any one of claims 41-64 wherein the payment request includes goods information.
66. The client device of any one of claims 41-65 wherein the payment request includes services information.
67. The client device of any one of claims 41-66 wherein the payment request includes a data package.
68. The client device of any one of claims 41-67 wherein the payment request includes merchant information.
69. The client device of any one of claims 41-68 wherein the payment request includes product information.
70. The client device of claim 68 wherein the merchant information includes a merchant receiving account.
71. The client device of claim 68 wherein the merchant information includes a merchant identifier.
72. The client device of any one of claims 41-71 wherein the merchant device is configured for use by a merchant.
73. The client device of any one of claims 41-71 wherein the merchant device is a server.
74. The client device of any one of claims 41-71 wherein the merchant device is a POS
machine.
75. The client device of any one of claims 41-71 wherein the merchant device is configured for use by a manufacturer.
76. The client device of any one of claims 41-71 wherein the merchant device is configured for use by an agent.
77. The client device of any one of claims 41-71 wherein the merchant device is configured for use by a logistics company.
78. The client device of any one of claims 41-77 wherein the client device is connected to the Internet.
79. The client device of any one of claims 41-78 wherein the merchant device is connected to the Internet.
80. The client device of any one of claims 41-79 wherein the first funds-management server is connected to the Internet.
81. A merchant device comprising:
a computer processor; and a memory storage device;
wherein the merchant device is communicatively connected to a client device, an information center server, a first funds-management server and a second funds-management server;
wherein the client device is configured to send a payment request for an e-commerce transaction to the second funds-management server, wherein the payment request includes a payment amount;
wherein the second funds-management server is configured to:
receive the payment request sent by the client device; and compare the amount in the payment request with an account balance and an overdraft limit of a client account;
when the amount in the payment request is less than the account balance and the overdraft limit added together the second funds-management server is further configured to:
freeze a freeze amount, within the client account, from the account balance and the overdraft limit, wherein the freeze amount is not less than the payment amount;
generate an electronic certificate, wherein the electronic certificate is configured to commit to pay the amount according to an agreed condition;
send the electronic certificate to the merchant device to make a credit commitment payment on behalf of the client; and synchronize the electronic certificate to the information center server;
wherein the merchant device is configured to receive the electronic certificate from the second funds-management server and wherein the merchant device is connected to the first funds-management server;
wherein the first funds-management server is configured to allocate the amount into a merchant account; and wherein the information center server is configured to store the electronic certificate.
82.
The merchant device of claim 81 wherein the first funds-management server is a single physical server.
83. The merchant device of claim 81 wherein the first funds-management server is a single bank server.
84. The merchant device of claim 81 wherein the first funds-management server is a single cluster server.
85. The merchant device of claim 81 wherein the first funds-management server is a single cluster bank server.
86. The merchant device of claim 81 wherein the second funds-management server is a single physical server.
87. The merchant device of claim 81 wherein the second funds-management server is a single bank server.
88. The merchant device of claim 81 wherein the second funds-management server is a single cluster server.
89. The merchant device of claim 81 wherein the second funds-management server is a single cluster bank server.
90. The merchant device of any one of claims 81-89 wherein the client device is configured for use by a buyer.
91. The merchant device of any one of claims 81-89 wherein the client device is configured for use by a payer.
92. The merchant device of any one of claims 81-91 wherein the client device is a mobile phone.
93. The merchant device of any one of claims 81-91 wherein the client device is a computer.
94. The merchant device of any one of claims 8 1-9 1 wherein the client device is a personal computer.
95. The merchant device of any one of claims 8 1-9 1 wherein the client device is a PDA.
96. The merchant device of any one of claims 81-91 wherein the client device is associated with client account information.
97. The merchant device of claim 96 wherein the client account information includes a customer ID.
98. The merchant device of any one of claims 96-97 wherein the client account information includes an account opening bank.
99. The merchant device of any one of claims 96-98 wherein the client account information includes an account name.
100. The merchant device of any one of claims 96-99 wherein the client account information includes a bank account number.
101. The merchant device of any one of claims 96-100 wherein the client account information includes a credit balance.
102. The merchant device of any one of claims 96-101 wherein the client account information includes a customer shipping address.
103. The merchant device of any one of claims 81-102 wherein the payment request includes a shipping address.
104. The merchant device of any one of claims 8 1- 103 wherein the payment request includes shipping information.
105. The merchant device of any one of claims 81-104 wherein the payment request includes goods infomiation.
106. The merchant device of any one of claims 81-105 wherein the payment request includes services information.
107. The merchant device of any one of claims 81-106 wherein the payment request includes a data package.
108. The merchant device of any one of claims 81-107 wherein the payment request includes merchant information.
109. The merchant device of any one of claims 81-108 wherein the payment request includes product information.
110. The merchant device of claim 108 wherein the merchant information includes a merchant receiving account.
111. The merchant device of claim 108 wherein the merchant information includes a merchant identifier.
112. The merchant device of any one of claims 81-111 wherein the merchant device is configured for use by a merchant.
113. The merchant device of any one of claims 81-111 wherein the merchant device is a server.
114. The merchant device of any one of claims 81-111 wherein the merchant device is a POS
machine.
115. The merchant device of any one of claims 81-111 wherein the merchant device is configured for use by a manufacturer.
116. The merchant device of any one of claims 81-111 wherein the merchant device is configured for use by an agent.
117. The merchant device of any one of claims 81-111 wherein the merchant device is configured for use by a logistics company.
118. The merchant device of any one of claims 81-117 wherein the client device is connected to the Internet.
119. The merchant device of any one of claims 81-118 wherein the merchant device is connected to the Internet.
120. The merchant device of any one of claims 81-119 wherein the first funds-management server is connected to the Internet.
121. An information center server comprising:
a computer processor; and a memory storage device;
wherein the information center server is communicatively connected to a merchant device, a client device, a first funds-management server and a second funds-management server;

wherein the client device is configured to send a payment request for an e-commerce transaction to the second funds-management server, wherein the payment request includes a payment amount;
wherein the second funds-management server is configured to:
receive the payment request sent by the client device; and compare the amount in the payment request with an account balance and an overdraft limit of a client account;
when the amount in the payment request is less than the account balance and the overdraft limit added together the second funds-management server is further configured to:
freeze a freeze amount, within the client account, from the account balance and the overdraft limit, wherein the freeze amount is not less than the payment amount;
generate an electronic certificate, wherein the electronic certificate is configured to commit to pay the amount according to an agreed condition;
send the electronic certificate to the merchant device to make a credit commitment payment on behalf of the client; and synchronize the electronic certificate to the information center server;
wherein the merchant device is configured to receive the electronic certificate from the second funds-management server and wherein the merchant device is connected to the first funds-management server;

wherein the first funds-management server is configured to allocate the amount into a merchant account; and wherein the information center server is configured to store the electronic certificate.
122. The information center server of claim 121 wherein the first funds-management server is a single physical server.
123. The information center server of claim 121 wherein the first funds-management server is a single bank server.
124. The information center server of claim 121 wherein the first funds-management server is a single cluster server.
125. The information center server of claim 121 wherein the first funds-management server is a single cluster bank server.
126. The information center server of claim 121 wherein the second funds-management server is a single physical server.
127. The information center server of claim 121 wherein the second funds-management server is a single bank server.
128. The information center server of claim 121 wherein the second funds-management server is a single cluster server.
129. The information center server of claim 121 wherein the second funds-management server is a single cluster bank server.
130. The information center server of any one of claims 121-129 wherein the client device is configured for use by a buyer.
131. The information center server of any one of claims 121-129 wherein the client device is configured for use by a payer.
132. The information center server of any one of claims 121-131 wherein the client device is a mobile phone.
133. The information center server of any one of claims 121-131 wherein the client device is a computer.
134. The information center server of any one of claims 121-131 wherein the client device is a personal computer.
135. The information center server of any one of claims 121-131 wherein the client device is a PDA.
136. The information center server of any one of claims 121-131 wherein the client device is associated with client account information.
137. The information center server of claim 136 wherein the client account information includes a customer ID.
138. The information center server of any one of claims 136-137 wherein the client account information includes an account opening bank.
139. The information center server of any one of claims 136-138 wherein the client account information includes an account name.
140. The information center server of any one of claims 136-139 wherein the client account information includes a bank account number.
141. The information center server of any one of claims 136-140 wherein the client account information includes a credit balance.
142. The information center server of any one of claims 136-141 wherein the client account information includes a customer shipping address.
143. The information center server of any one of claims 121-142 wherein the payment request includes a shipping address.
144. The information center server of any one of claims 121-143 wherein the payment request includes shipping information.
145. The information center server of any one of claims 121-144 wherein the payment request includes goods information.
146. The information center server of any one of claims 121-145 wherein the payment request includes services information.
147. The information center server of any one of claims 121-146 wherein the payment request includes a data package.
148. The information center server of any one of claims 121-147 wherein the payment request includes merchant information.
149. The information center server of any one of claims 121-148 wherein the payment request includes product infomiati on.
150. The information center server of claim 148 wherein the merchant information includes a merchant receiving account.
151. The information center server of claim 148 wherein the merchant information includes a merchant identifier.
152. The information center server of any one of claims 121-151 wherein the merchant device is configured for use by a merchant.
153. The information center server of any one of claims 121-151 wherein the merchant device is a server.
154. The information center server of any one of claims 121-151 wherein the merchant device is a POS machine.
155. The information center server of any one of claims 121-151 wherein the merchant device is configured for use by a manufacturer.
156. The information center server of any one of claims 121-151 wherein the merchant device is configured for use by an agent.
157. The information center server of any one of claims 121-151 wherein the merchant device is configured for use by a logistics company.
158. The information center server of any one of claims 121-157 wherein the client device is connected to the Internet.
159. The information center server of any one of claims 121-158 wherein the merchant device is connected to the Internet.
160. The information center server of any one of claims 121-159 wherein the first funds-management server is connected to the Internet.
161. A first funds-management server comprising:

a computer processor; and a memory storage device;
wherein the first funds-management server is communicatively connected to a client device, an information center server, a merchant device and a second funds-management server;
wherein the client device is configured to send a payment request for an e-commerce transaction to the second funds-management server, wherein the payment request includes a payment amount;
wherein the second funds-management server is configured to:
receive the payment request sent by the client device; and compare the amount in the payment request with an account balance and an overdraft limit of a client account;
when the amount in the payment request is less than the account balance and the overdraft limit added together the second funds-management server is further configured to:
freeze a freeze amount, within the client account, from the account balance and the overdraft limit, wherein the freeze amount is not less than the payment amount;
generate an electronic certificate, wherein the electronic certificate is configured to commit to pay the amount according to an agreed condition;

send the electronic certificate to the merchant device to make a credit commitment payment on behalf of the client; and synchronize the electronic certificate to the information center server;
wherein the merchant device is configured to receive the electronic certificate from the second funds-management server and wherein the merchant device is connected to the first funds-management server;
wherein the first funds-management server is configured to allocate the amount into a merchant account; and wherein the information center server is configured to store the electronic certificate.
162. The first funds-management server of claim 161 wherein the first funds-management server is a single physical server.
163. The first funds-management server of claim 161 wherein the first funds-management server is a single bank server.
164. The first funds-management server of claim 161 wherein the first funds-management server is a single cluster server.
165. The first funds-management server of claim 161 wherein the first funds-management server is a single cluster bank server.
166. The first funds-management server of claim 161 wherein the second funds-management server is a single physical server.
167. The first funds-management server of claim 161 wherein the second funds-management server is a single bank server.
168. The first funds-management server of claim 161 wherein the second funds-management server is a single cluster server.
169. The first funds-management server of claim 161 wherein the second funds-management server is a single cluster bank server.
170. The first funds-management server of any one of claims 161-169 wherein the client device is configured for use by a buyer.
171. The first funds-management server of any one of claims 161-169 wherein the client device is configured for use by a payer.
172. The first funds-management server of any one of claims 161-171 wherein the client device is a mobile phone.
173. The first funds-management server of any one of claims 161-171 wherein the client device is a computer.
174. The first funds-management server of any one of claims 161-171 wherein the client device is a personal computer.
175. The first funds-management server of any one of claims 161-171 wherein the client device is a PDA.
176. The first funds-management server of any one of claims 161-171 wherein the client device is associated with client account information.
177. The first funds-management server of claim 176 wherein the client account information includes a customer ID.
178. The first funds-management server of any one of claims 176-177 wherein the client account infomiation includes an account opening bank.
179. The first funds-management server of any one of claims 176-178 wherein the client account information includes an account name.
180. The first funds-management server of any one of claims 176-179 wherein the client account information includes a bank account number.
181. The first funds-management server of any one of claims 176-180 wherein the client account information includes a credit balance.
182. The first funds-management server of any one of claims 176-181 wherein the client account information includes a customer shipping address.
183. The first funds-management server of any one of claims 161-182 wherein the payment request includes a shipping address.
184. The first funds-management server of any one of claims 161-183 wherein the payment request includes shipping information.
185. The first funds-management server of any one of claims 161-184 wherein the payment request includes goods information.
186. The first funds-management server of any one of claims 161-185 wherein the payment request includes services information.
187. The first funds-management server of any one of claims 161-186 wherein the payment request includes a data package.
188. The first funds-management server of any one of claims 161-187 wherein the payment request includes merchant information.
189. The first funds-management server of any one of claims 161-188 wherein the payment request includes product information.
190. The first funds-management server of claim 188 wherein the merchant information includes a merchant receiving account.
191. The first funds-management server of claim 188 wherein the merchant information includes a merchant identifier.
192. The first funds-management server of any one of claims 161-191 wherein the merchant device is configured for use by a merchant.
193. The first funds-management server of any one of claims 161-191 wherein the merchant device is a server.
194. The first funds-management server of any one of claims 161-191 wherein the merchant device is a POS machine.
195. The first funds-management server of any one of claims 161-191 wherein the merchant device is configured for use by a manufacturer.
196. The first funds-management server of any one of claims 161-191 wherein the merchant device is configured for use by an agent.
197. The first funds-management server of any one of claims 161-191 wherein the merchant device is configured for use by a logistics company.
198. The first funds-management server of any one of claims 161-197 wherein the client device is connected to the Internet.
199. The first funds-management server of any one of claims 161-198 wherein the merchant device is connected to the Internet.
200. The first funds-management server of any one of claims 161-199 wherein the first funds-management server is connected to the Internet.
201. A second funds-management server comprising:
a computer processor; and a memory storage device;
wherein the second funds-management server is communicatively connected to a client device, an information center server, a first funds-management server and a merchant device;
wherein the client device is configured to send a payment request for an e-commerce transaction to the second funds-management server, wherein the payment request includes a payment amount;
wherein the second funds-management server is configured to:
receive the payment request sent by the client device; and compare the amount in the payment request with an account balance and an overdraft limit of a client account;

when the amount in the payment request is less than the account balance and the overdraft limit added together the second funds-management server is further configured to:
freeze a freeze amount, within the client account, from the account balance and the overdraft limit, wherein the freeze amount is not less than the payment amount;
generate an electronic certificate, wherein the electronic certificate is configured to commit to pay the amount according to an agreed condition;
send the electronic certificate to the merchant device to make a credit commitment payment on behalf of the client; and synchronize the electronic certificate to the information center server;
wherein the merchant device is configured to receive the electronic certificate from the second funds-management server and wherein the merchant device is connected to the first funds-management server;
wherein the first funds-management server is configured to allocate the amount into a merchant account;
wherein the information center server is configured to store the electronic certificate.
202. The second funds-management server of claim 201 wherein the first funds-management server is a single physical server.
203. The second funds-management server of claim 201 wherein the first funds-management server is a single bank server.
204. The second funds-management server of claim 201 wherein the first funds-management server is a single cluster server.
205. The second funds-management server of claim 201 wherein the first funds-management server is a single cluster bank server.
206. The second funds-management server of claim 201 wherein the second funds-management server is a single physical server.
207. The second funds-management server of claim 201 wherein the second funds-management server is a single bank server.
208. The second funds-management server of claim 201 wherein the second funds-management server is a single cluster server.
209. The second funds-management server of claim 201 wherein the second funds-management server is a single cluster bank server.
210. The second funds-management server of any one of claims 201-209 wherein the client device is configured for use by a buyer.
211. The second funds-management server of any one of claims 201-209 wherein the client device is configured for use by a payer.
212. The second funds-management server of any one of claims 201-211 wherein the client device is a mobile phone.
213. The second funds-management server of any one of claims 201-211 wherein the client device is a computer.
214. The second funds-management server of any one of claims 201-211 wherein the client device is a personal computer.
215. The second funds-management server of any one of claims 201-211 wherein the client device is a PDA.
216. The second funds-management server of any one of claims 201-211 wherein the client device is associated with client account information.
217. The second funds-management server of claim 216 wherein the client account information includes a customer ID.
218. The second funds-management server of any one of claims 216-217 wherein the client account infomiation includes an account opening bank.
219. The second funds-management server of any one of claims 216-218 wherein the client account information includes an account name.
220. The second funds-management server of any one of claims 216-219 wherein the client account information includes a bank account number.
221. The second funds-management server of any one of claims 216-220 wherein the client account information includes a credit balance.
222. The second funds-management server of any one of claims 216-221 wherein the client account information includes a customer shipping address.
223. The second funds-management server of any one of claims 201-222 wherein the payment request includes a shipping address.
224. The second funds-management server of any one of claims 201-223 wherein the payment request includes shipping information.
225. The second funds-management server of any one of claims 201-224 wherein the payment request includes goods information.
226. The second funds-management server of any one of claims 201-225 wherein the payment request includes services information.
227. The second funds-management server of any one of claims 201-226 wherein the payment request includes a data package.
228. The second funds-management server of any one of claims 201-227 wherein the payment request includes merchant information.
229. The second funds-management server of any one of claims 201-228 wherein the payment request includes product information.
230. The second funds-management server of claim 228 wherein the merchant information includes a merchant receiving account.
231. The second funds-management server of claim 228 wherein the merchant information includes a merchant identifier.
232. The second funds-management server of any one of claims 201-231 wherein the merchant device is configured for use by a merchant.
233. The second funds-management server of any one of claims 201-231 wherein the merchant device is a server.
234. The second funds-management server of any one of claims 20 1-23 1 wherein the merchant device is a POS machine.
235. The second funds-management server of any one of claims 201-231 wherein the merchant device is configured for use by a manufacturer.
236. The second funds-management server of any one of claims 201-231 wherein the merchant device is configured for use by an agent.
237. The second funds-management server of any one of claims 201-231 wherein the merchant device is configured for use by a logistics company.
238. The second funds-management server of any one of claims 201-237 wherein the client device is connected to the Internet.
239. The second funds-management server of any one of claims 201-238 wherein the merchant device is connected to the Internet.
240. The second funds-management server of any one of claims 201-239 wherein the first funds-management server is connected to the Internet.
241. A network payment method for protecting both a client and a merchant in e-commerce transactions, the method comprising:
receiving, at a funds-management server, a payment request for an e-commerce transaction from a client device, wherein the payment request includes a payment amount;
comparing the payment amount to an account balance and an overdraft limit of a client account;

when the payment amount is less than the account balance and the overdraft limit added together the method further comprises:
freezing a freeze amount, within the client account, from the account balance and the overdraft limit, wherein the freeze amount is not less than the payment amount;
generating an electronic certificate, wherein the electronic certificate is configured to commit to pay the amount according to an agreed condition; and sending the electronic certificate to the merchant device to make a credit commitment payment on behalf of the client.
242. The method of claim 241 further comprising:
inquiring, from the funds-management server to the client device whether a credit loan is to be issued when the payment amount is not less than the account balance and the overdraft limit added together.
243. The method of claim 242 further comprising:
issuing the credit loan from the funds-management server.
244. The method of claim 241 further comprising:
transmitting the payment request from the client device to a second funds-management server.
245. The method of any one of claims 241-244 wherein the payment request includes customer information.
246. The method of any one of claims 241-245 wherein the payment request includes merchant information.
247. The method of any one of claims 241-246 wherein the payment request includes product information.
248. The method of claim 246 wherein the merchant information includes a merchant receiving account.
249. The method of claim 246 wherein the merchant information includes a merchant identifier.
250. The method of claim 241 wherein the funds-management server is a single physical server.
251. The method of claim 241 wherein the funds-management server is a single bank server.
252. The method of claim 241 wherein the funds-management server is a single cluster server.
253. The method of claim 241 wherein the funds-management server is a single cluster bank server.
254. The method of any one of claims 241-253 wherein the payment request includes a shipping address.
255. The method of any one of claims 241-254 wherein the payment request includes shipping information.
256. The method of any one of claims 241-255 wherein the payment request includes goods information.
257. The method of any one of claims 241-256 wherein the payment request includes services information.
258. The method of any one of claims 241-257 wherein the payment request includes a data package.
259. The method of claim 244 wherein the funds-management server is further configured to synchronize the electronic certificate to an information center server.
260. The method of claim 244 wherein the funds-management server is further configured to allocate the freeze funds to a merchant account.
261. A payment device comprising:
a receiving module;
a judgement module;
a processing module;
wherein the receiving module is configured to receive a payment request for an e-commerce transaction delivered by a terminal, wherein the terminal is connected to a second funds-management server and wherein the payment request includes a payment amount;
wherein the judgement module is configured to compare the payment amount to an account balance and an overdraft limit of a client account to determine whether an electronic certificate is generable; and wherein when the electronic certificate is generable the processing module is configured to:
freeze a freeze amount, within the client account, from the account balance and the overdraft limit, wherein the freeze amount is not less than the payment amount;
generate the electronic certificate;
deliver the electronic certificate to a merchant terminal connected to a first funds-management server; and synchronize the electronic certificate to an information center server.
262. The payment device of claim 261 further comprises a freeze unit.
263. The payment device of claim 262 wherein the freeze unit is configured to freeze the freeze amount from the account balance and the overdraft limit, wherein the freeze amount is not less than the payment amount.
264. The payment device of claim 263 wherein the payment device further comprises a certificate generation unit.
265. The payment device of claim 264 wherein the certificate generation unit is configured to generate the electronic certificate.
266. The payment device of claim 265 wherein the payment device further comprises a synchronization unit.
267. The payment device of claim 266 wherein the synchronization unit is configured to transmit the electronic certificate to the merchant terminal.
268. The payment device of claim 267 wherein the synchronization unit is further configured to synchronize the electronic certificate to the information center server.
269. The payment device of claim 268 wherein the processing module is further configured to:
receive the payment request; and allocate an amount contained in the payment request to a funds-management server.
270. The payment device of any one of claims 261-269 wherein the payment device is hosted on a server.
271. The payment device of any one of claims 261-270 wherein the payment request includes a shipping address.
272. The payment device of any one of claims 261-271 wherein the payment request includes shipping information.
273. The payment device of any one of claims 261-272 wherein the payment request includes goods information.
274. The payment device of any one of claims 261-273 wherein the payment request includes services information.
275. The payment device of any one of claims 261-274 wherein the payment request includes a data package.
276. The payment device of any one of claims 261-275 wherein the payment request includes customer information.
277. The payment device of any one of claims 261-276 wherein the payment request includes merchant information.
278. The payment device of any one of claims 261-277 wherein the payment request includes product infomiation.
CA2987291A 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor Active CA2987291C (en)

Priority Applications (9)

Application Number Priority Date Filing Date Title
CA3058529A CA3058529C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058595A CA3058595C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058598A CA3058598C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058560A CA3058560C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058558A CA3058558C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058527A CA3058527C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058530A CA3058530A1 (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058591A CA3058591C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058553A CA3058553C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment method

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
CN201510218467.8A CN106204005A (en) 2015-04-30 2015-04-30 Based on across the payment system of fund server and method of payment, device and server
CN201510218467.8 2015-04-30
PCT/CN2015/080078 WO2016173044A1 (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor

Related Child Applications (9)

Application Number Title Priority Date Filing Date
CA3058553A Division CA3058553C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment method
CA3058558A Division CA3058558C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058530A Division CA3058530A1 (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058595A Division CA3058595C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058560A Division CA3058560C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058527A Division CA3058527C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058598A Division CA3058598C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058591A Division CA3058591C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058529A Division CA3058529C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor

Publications (2)

Publication Number Publication Date
CA2987291A1 CA2987291A1 (en) 2016-11-03
CA2987291C true CA2987291C (en) 2021-03-30

Family

ID=57198044

Family Applications (11)

Application Number Title Priority Date Filing Date
CA3058527A Active CA3058527C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058529A Active CA3058529C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3185375A Pending CA3185375A1 (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058530A Pending CA3058530A1 (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058560A Active CA3058560C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058558A Active CA3058558C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA2987291A Active CA2987291C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058591A Active CA3058591C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058553A Active CA3058553C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment method
CA3058598A Active CA3058598C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058595A Active CA3058595C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor

Family Applications Before (6)

Application Number Title Priority Date Filing Date
CA3058527A Active CA3058527C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058529A Active CA3058529C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3185375A Pending CA3185375A1 (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058530A Pending CA3058530A1 (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058560A Active CA3058560C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058558A Active CA3058558C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor

Family Applications After (4)

Application Number Title Priority Date Filing Date
CA3058591A Active CA3058591C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058553A Active CA3058553C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment method
CA3058598A Active CA3058598C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor
CA3058595A Active CA3058595C (en) 2015-04-30 2015-05-28 Cross-funds management server-based payment system, and method, device and server therefor

Country Status (3)

Country Link
CN (1) CN106204005A (en)
CA (11) CA3058527C (en)
WO (1) WO2016173044A1 (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108038684A (en) * 2017-12-28 2018-05-15 泰康保险集团股份有限公司 A kind of method of payment, device, medium and electronic equipment
CN108038771B (en) * 2018-01-04 2021-08-10 四川隧唐科技股份有限公司 Bulk oil product transaction method and system
CN110232627A (en) * 2018-03-06 2019-09-13 上海秦苍信息科技有限公司 Introduce fund management-control method, system and the electronic equipment of the external sources of finance
CN113034273A (en) * 2021-05-25 2021-06-25 浙江网商银行股份有限公司 Resource processing method and system

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101071520A (en) * 2006-05-09 2007-11-14 上海浦东发展银行 Method for concurrently realizing credit and debit functions on identical bank card
US8150764B2 (en) * 2008-04-04 2012-04-03 Metabank System, program product, and method to authorize draw for retailer optimization
CN103413241A (en) * 2013-07-12 2013-11-27 广州银联网络支付有限公司 Bank reception and payment system

Also Published As

Publication number Publication date
CA3185375A1 (en) 2016-11-03
CA3058591C (en) 2023-11-07
CA3058529A1 (en) 2016-11-03
CA3058598A1 (en) 2016-11-03
CA3058527C (en) 2023-03-07
CA3058595C (en) 2021-09-28
CA3058527A1 (en) 2016-11-03
CA3058530A1 (en) 2016-11-03
CA3058553C (en) 2022-07-19
CA3058558C (en) 2023-05-02
CA3058529C (en) 2022-03-15
CA2987291A1 (en) 2016-11-03
CA3058591A1 (en) 2016-11-03
CA3058558A1 (en) 2016-11-03
CA3058560C (en) 2023-02-07
CA3058553A1 (en) 2016-11-03
CA3058560A1 (en) 2016-11-03
WO2016173044A1 (en) 2016-11-03
CA3058595A1 (en) 2016-11-03
CN106204005A (en) 2016-12-07
CA3058598C (en) 2023-01-31

Similar Documents

Publication Publication Date Title
CA2987291C (en) Cross-funds management server-based payment system, and method, device and server therefor
CA2988813A1 (en) Cross-funds management server-based payment system, and method, device and server therefor
CA2987296A1 (en) Payment system based on shared funds-management server, and method, device and server therefor
CA2986838A1 (en) Payment system based on shared funds-management server, and method, device and server therefor
CA2988809C (en) Cross-funds management server-based payment system, and method, device and server therefor
CA2988807A1 (en) Management across funds server-based payment system, and method, device and server
CA2987295C (en) Payment system based on shared funds-management server, and method, device and server therefor
CA3055645C (en) Payment system based on shared funds-management server, and method, device and server therefor
CA2988804A1 (en) Payment system based on shared funds-management server, and method, device and server therefor
CA3055644C (en) Payment system based on shared funds-management server, and method, device and server therefor
CA2987802A1 (en) Cross-funds server-based payment system, and payment method, device and server therefor
CA2987803A1 (en) Cross-funds management server-based payment system, and method, device and server therefor
CA2987800A1 (en) Payment system based on shared funds-management server, and method, device and server therefor
CA2987660A1 (en) Payment system based on shared funds-management server, and method, device and server therefor
CA2987442C (en) Payment system based on shared funds-management server, and method, device and server therefor

Legal Events

Date Code Title Description
EEER Examination request

Effective date: 20190618