Language selection

Search

Patent 2994977 Summary

Third-party information liability

Some of the information on this Web page has been provided by external sources. The Government of Canada is not responsible for the accuracy, reliability or currency of the information supplied by external sources. Users wishing to rely upon this information should consult directly with the source of the information. Content provided by external sources is not subject to official languages, privacy and accessibility requirements.

Claims and Abstract availability

Any discrepancies in the text and image of the Claims and Abstract are due to differing posting times. Text of the Claims and Abstract are posted:

  • At the time the application is open to public inspection;
  • At the time of issue of the patent (grant).
(12) Patent: (11) CA 2994977
(54) English Title: NETWORK TRANSACTION-BASED REFILL METHOD AND DEVICE
(54) French Title: PROCEDE ET DISPOSITIF DE RECHARGE PAR TRANSACTION DE RESEAU
Status: Granted and Issued
Bibliographic Data
Abstracts

English Abstract

A network transaction-based refill method and device. The method comprises: receiving a refill request transmitted by a first terminal (101), where the refill request carries a paying account, a refill amount, and a receiving account; paying a fund of the refill amount in the paying account to the receiving account (102); freezing the fund of the refill amount received in the receiving account and generating a refill voucher corresponding to the refill amount (103); and transmitting the refill voucher to the first terminal (104).


French Abstract

L'invention concerne un procédé et un dispositif de recharge par transaction de réseau. Le procédé consiste à : recevoir une demande de recharge transmise par un premier terminal (101), la demande de recharge véhiculant un compte de paiement, un montant de recharge et un compte de réception; payer des fonds du montant de recharge du compte de paiement au compte de réception (102); bloquer les fonds du montant de recharge reçus sur le compte de réception et générer un bon de recharge correspondant au montant de recharge (103); et transmettre le bon de recharge au premier terminal (104).

Claims

Note: Claims are shown in the official language in which they were submitted.


Claims:
1. A computer implemented method for reloading funds based on network
transaction, the
method comprising:
receiving a reloading request delivered by a first terminal, wherein the
reloading request
includes a payment account, a reloading amount, and a payment collection
account,
wherein the payment collection account is a merchant's account;
transferring an amount of funds in the payment account to the payment
collection
account, wherein the transferred amount of funds is equal to the reloading
amount;
freezing the transferred amount of funds in the payment collection account
from the
payment account to generate a reloading certificate corresponding to the
reloading
amount for ensuring safety of customer funds before the network transaction is
completed; and
delivering the reloading certificate to the first terminal.
2. The method of claim 1, wherein the reloading request further includes a
payment settlement
condition.
3. The method of claim 1 further includes obtaining the reloading certificate
delivered by the
first terminal and a transaction certificate.
4. The method of claim 3, wherein the transaction certificate includes use of
funds.
5. The method of any one of claims 3 to 4, wherein the transaction certificate
further includes a
transaction amount.
itt
Date Recue/Date Received 2021-04-09

6. The method of any one of claims 1 to 5 further includes verifying whether
the reloading
certificate is valid.
7. The method of claim 6 further includes, where if the reloading
certificate is valid,
determining whether the use of funds is consistent with the payment settlement
condition.
8. The method of claim 7 further includes, where if the use of funds is
consistent with the
payment settlement condition, unfreezing the frozen amount of funds in the
payment
collection account.
9. The method of claim 8, wherein the frozen amount of funds is equal to the
transaction
amount.
10. The method of any one of claim 1 to 9 further includes:
generating a payment result message after releasing the frozen amount of
funds; and
delivering the payment result message to the first terminal.
11. The method of claim 10 further includes updating the reloading amount of
the reloading
certificate according to the transaction amount when the payment result
message is a
payment successful message.
12. The method of claim 11 further includes synchronizing content of the
updated remaining
amount to the first terminal to notice a user.
13. The method of any one of claims 3 to 12 further includes receiving the
reloading certificate
delivered by the first terminal and a fund withdrawal certificate.
14. The method of claim 13 wherein the fund withdrawal certificate includes a
withdrawal
amount.
11
Date Recue/Date Received 2021-04-09

15. The method of any one of claims 13 to 14, wherein the fund withdrawal
certificate further
includes a fund withdrawal condition.
16. The method of any one of claims 3 to 15 further includes verifying whether
the reloading
certificate is valid.
17. The method of claim 16 further includes, where if the reloading
certificate is valid, judging
whether the fund withdrawal condition satisfies a preset condition.
18. The method of claim 17 further includes, where if the fund withdrawal
condition satisfies the
preset condition, releasing the frozen amount of funds in the payment
collection account.
19. The method of claim 18, wherein the released amount of funds is equal to a
withdrawal
amount.
20. The method of any one of claims 3 to 19 further includes refunding the
released amount of
funds into the payment account.
21. The method of any one of claims 13 to 20 further includes updating the
reloading amount of
the reloading certificate according to the withdrawal amount after the fund is
returned to the
payment account.
22. The method of any one of claims 13 to 21 further includes synchronizing
the updated
reloading amount to the first terminal.
23. The method of any one of claims 1 to 22, wherein the first terminal is
held and controlled by
a buyer.
24. The method of any one of claims 1 to 23 wherein the payment amount
corresponds to a first
funds-management server.
12
Date Recue/Date Received 2021-04-09

25. The method of any one of claims 1 to 24 wherein the payment collection
account
corresponds to a second funds-management server.
26. The method of claim 25, wherein the first Funds-Management server is the
same server as
the second Funds-Management server.
27. The method of claim 25, wherein the first Funds-Management server is a
different server
from the second Funds-Management server.
28. The method of any one of claims 24 to 27, wherein the first Funds-
Management server is a
bank server.
29. The method of any one of claims 24 to 27, wherein the first Funds-
Management server is a
server for a financial institution.
30. The method of any one of claims 24 to 27, wherein the first Funds-
Management server is a
server for a third-party payment platform.
31. The method of any one of claims 25 to 27, wherein the second Funds-
Management server is
a bank server.
32. The method of any one of claims 25 to 27, wherein the second Funds-
Management server is
a server for a financial institution.
33. The method of any one of claims 25 to 27, wherein the second Funds-
Management server is
a server for a third-party payment platform.
34. The method of any one of claims 1 to 33, wherein the reloading certificate
includes the
reloading amount.
13
Date Recue/Date Received 2021-04-09

35. The method of any one of claims 1 to 34, wherein the reloading certificate
includes a
reloading time.
36. The method of any one of claims 1 to 35, wherein the reloading certificate
includes a
payment account number.
37. The method of any one of claims 1 to 36, wherein the reloading certificate
includes a
collection account number.
38. The method of any one of claims 1 to 37, wherein the reloading certificate
includes the
buyer's electronic signature.
39. A computer device for reloading funds based on network transaction, the
device comprising:
a request receiving module configured to receive a reloading request delivered
by a first
terminal, wherein the reloading request includes a payment account, a
reloading amount,
and a payment collection account, wherein the payment collection account is a
merchant's account;
a fund payment module configured to transfer an amount of funds in the payment
account
to the payment collection account, wherein the transferred amount of funds is
equal to
the reloading amount;
a certificate generating module configured to freeze the transferred amount of
funds in
the payment collection account from the payment account to generate a
reloading
certificate corresponding to the reloading amount for ensuring safety of
customer funds
before the network transaction is completed; and
an information delivering module configured to deliver the reloading
certificate to the
first terminal.
14
Date Recue/Date Received 2021-04-09

40. The device of claim 39, wherein the reloading request further includes a
payment settlement
condition.
41. The device of any one of claims 39 to 40 further includes a first
information acquisition
module.
42. The device of claim 41, wherein the first information acquisition module
is configured to
obtain the reloading certificate delivered by the first terminal and a
transaction certificate.
43. The device of claim 42, where the transaction certificate includes use of
funds.
44. The device of any one of claims 42 to 43, wherein the transaction
certificate further includes
a transaction amount.
45. The device of claim 41, wherein the first information acquisition module
is configured to
verify whether the reloading certificate is valid.
46. The device of claim 45, further includes a first fund releasing module.
47. The device of claim 46, wherein the first fund releasing module is
configured to, where if the
reloading certificate is valid, determine whether the use of funds is
consistent with the
payment settlement condition.
48. The device of claim 46, wherein the first fund releasing module is
configured to, where if
the use of funds is consistent with the payment settlement condition, unfreeze
the frozen
amount of funds in the payment collection account.
49. The device of claim 48, wherein the frozen amount of funds is equal to the
transaction
amount.
Date Recue/Date Received 2021-04-09

50. The device of any one of claim 39 to 49 further includes a first message
delivering module.
51. The device of claim 50, wherein the first message delivering module is
configured to:
generate a payment result message after releasing the frozen amount of funds;
and
deliver the payment result message to the first terminal.
52. The device of any one of claims 39 to 51 further includes a first updating
module.
53. The device of claim 52, wherein the first updating module is configured to
update the
reloading amount of the reloading certificate according to the transaction
amount when the
payment result message is a payment successful message.
54. The device of any one of claims 52 to 53, wherein the first updating
module is configured to
synchronize content of the updated remaining amount to the first terminal to
notice a user.
55. The device of any one of claims 41 to 51 further includes a second
information acquisition
module.
56. The device of claim 55, wherein the second information acquisition module
is configured to
receive the reloading certificate delivered by the first terminal and a fund
withdrawal
certificate.
57. The device of claim 56, wherein the fund withdrawal certificate includes a
withdrawal
amount.
58. The device of any one of claims 56 to 57, wherein the fund withdrawal
certificate further
includes a fund withdrawal condition.
59. The device of any one of claims 41 to 58 further includes a second
verification module.
16
Date Recue/Date Received 2021-04-09

60. The device of claim 59, wherein the second verification module is
configured to verify
whether the reloading certificate is valid.
61. The device of any one of claims 41 to 60 further includes a second funds
unfreezing module.
62. The device of claim 61, wherein the second funds unfreezing module is
configured to, where
if the reloading certificate is valid, judge whether the fund withdrawal
condition satisfies a
preset condition.
63. The device of claim 62, wherein the second funds unfreezing module is
configured to, where
if the fund withdrawal condition satisfies the preset condition, release the
frozen amount of
funds in the payment collection account.
64. The device of claim 63, wherein the released amount of funds is equal to a
withdrawal
amount.
65. The device of any one of claims 41 to 64 further includes a funding
withdrawal module.
66. The device of claim 65, wherein the funding withdrawal module is
configured to refund the
released amount of funds into the payment account.
67. The device of any one of claims 56 to 66 further includes a second
updating module.
68. The device of claim 67, wherein second updating module is configured to
update the
reloading amount of the reloading certificate according to the withdrawal
amount after the
fund is returned to the payment account.
69. The device of any one of claims 67 to 68, wherein second updating module
is configured to
synchronize the updated reloading amount to the first terminal.
17
Date Recue/Date Received 2021-04-09

70. The device of any one of claims 39 to 68, wherein the first terminal is
held and controlled by
a buyer.
71. The device of any one of claims 39 to 70 wherein the payment amount
corresponds to a first
funds-management server.
72. The device of any one of claims 39 to 71 wherein the payment collection
account
corresponds to a second funds-management server.
73. The device of any one of claims 39 to 69, wherein a first Funds-Management
server is the
same server as a second Funds-Management server.
74. The device of any one of claims 39 to 69, wherein a first Funds-Management
server is a
different server from a second Funds-Management server.
75. The device of any one of claims 73 to 74, wherein the first Funds-
Management server is a
bank server.
76. The device of any one of claims 73 to 74, wherein the first Funds-
Management server is a
server for a financial institution.
77. The device of any one of claims 73 to 74, wherein the first Funds-
Management server is a
server for a third-party payment platform.
78. The device of any one of claims 73 to 77, wherein the second Funds-
Management server is a
bank server.
79. The device of any one of claims 73 to 77, wherein the second Funds-
Management server is a
server for a financial institution.
18
Date Recue/Date Received 2021-04-09

80. The device of any one of claims 73 to 77, wherein the second Funds-
Management server is a
server for a third-party payment platform.
81. The device of any one of claims 39 to 80, wherein the reloading
certificate includes the
reloading amount.
82. The device of any one of claims 39 to 81, wherein the reloading
certificate includes a
reloading time.
83. The device of any one of claims 39 to 82, wherein the reloading
certificate includes a
payment account number.
84. The device of any one of claims 39 to 83, wherein the reloading
certificate includes a
collection account number.
85. The device of any one of claims 39 to 84, wherein the reloading
certificate includes the
buyer's electronic signature.
19
Date Recue/Date Received 2021-04-09

Description

Note: Descriptions are shown in the official language in which they were submitted.


CA 02994977 2018-02-07
WO 2017/012077 PCT/CN2015/084733
Network Transaction-Based Refill Method And Device
[1] [Technical Field]
[2] The present invention relates to the field of communications
technologies, and in
particular, to a method and device for recharging based on network
transactions.
[3] [Background Technology]
[4] E-commerce has gradually become the main trend of Internet economic
development,
online consumption has gradually become a way of life for people. In order to
make the
transaction more convenient and faster, the merchants generally use the
preferential
activities to attract customers to reload before spending. The traditional
method of
reloading, the customer has already put the money into the merchant's account
before it is
consumed, and the merchant can control the customer's money at will. Since
funds are not
under the control of customers, they cannot guarantee the safety of customer
funds.
[5] [Summary of the Invention]
[6] Based on this, it is necessary to provide a method and a device for
recharging based on
network transaction that can improve fund safety in view of the above
technical problem.
[7] A network transaction based recharge method, the method including:
[8] Receive a recharge request delivered by a first terminal, where the
recharge request carries
a payment account, a recharge amount and a payment account;
[9] Pay the funds in the payment account into the payment account;
[10] Freezing the funds of the recharging amount received in the remittance
account and
generating a recharging certificate corresponding to the recharging amount;
[11] The recharge certificate is delivered to the first terminal.
[12] A network transaction-based recharge device, the device including:
[13] The request receiving module is used to receive the recharge request
delivered by the first
terminal, and the recharge request carries the payment account, the amount of
the recharge
and the receivable account;
[14] A fund payment module is used to pay the amount of the charged amount
in the payment
account to the receiving account;
[15] A certificate generating module is used for freezing the funds of the
recharging amount
received in the remittance account and generating a recharging certificate
corresponding to
the recharging amount;
[16] An information delivering module is used to deliver the recharge
certificate to the first

CA 02994977 2018-02-07
WO 2017/012077 PCT/C N2015/084733
terminal.
[17] The above method and device for replenishing online transactions,
although the funds for
customer replenishment have been transferred from the payment account to the
merchant's
payment account, the funds are frozen in the payment account, and the service
provided by
the merchant is enjoyed by the customer before, businesses are unable to
control customer
recharge of funds, thus ensuring the safety of customer funds.
[18] [Brief Description]
[19] In order to specifically illustrate the examples of the invention or
the technical solutions in
the current technology, the following drawings, which are to be used in the
description of
the examples or the current technology, will be briefly described, and it will
be apparent
that the following accompanying drawings, which are merely exemplary of the
invention,
may be made by those of ordinary skill in the art in view of the accompanying
drawings, in
which the drawings of other examples may be obtained without departing from
the
inventive work.
[20] Figure 1 is a schematic flow chart of a method for recharging a web-
based transaction in
one example.
[21] Figure 2 is a flow chart of a method for recharging a web-based
transaction after the step of
delivering the recharge certificate to a first terminal in one example;
[22] Figure 3 is a schematic flow chart of a method for recharging a web-
based transaction in
another example;
[23] Figure 4 is an application scene diagram of a network transaction
based recharge method in
one example;
[24] Figure 5 is a schematic structural diagram of a network transaction-
based recharging
device in one example;
[25] Figure 6 is a schematic structural diagram of a network transaction
based recharging device
in another example;
[26] Figure 7 is a schematic structural diagram of a network transaction
based recharging device
in another example;
[27] Figure 8 is a schematic structural diagram of a network transaction
based recharging device
in another example;
[28] Figure 9 is a schematic structural diagram of a network transaction-
based recharging
device in another example.
[29] [Description of the Preferred Examples]
[30] In order to make the purpose, the technical solution and advantages of
the invention more
clearly understood, the following explanations further explain the invention
according to
2

CA 02994977 2018-02-07
WO 2017/012077 PCT/CN2015/084733
the attached drawings and examples. It is to be understood that the specific
examples
described herein are merely illustrative of the invention but not intended to
limit the
invention.
[31] As shown in Figure 1, in one example, it is provided a network
transaction-based
recharging method, which includes the following steps:
[32] Step 101: Receive a recharging request delivered by the first
terminal.
[33] The first terminal corresponds to a customer or a buyer, and the
customer may pre-charge
in the recharging system before consuming. In this example, the server is used
for
implementing the recharging function receives the recharging request delivered
by the first
terminal. Specifically, the server may be a bank-provided server or a server
provided by a
third-party payment platform. The customer completes the recharge task through
the first
terminal login recharge system. The recharge request carries the payment
account, the
recharge amount, and the payment account. A payment account is an account used
by a
customer to pay a rechargeable fund. A collection account is an account used
by a merchant
to obtain funds. The user selects the account type on the top-up interface and
fill in the
payment account, receiving account and recharge amount, and click the top-up
button to
complete the submitting of the top-up request.
[34] Step 102: Pay the funds in the payment account to the collection
account.
[35] The server allocates the funds in the receiving account equal to the
top up amount to the
receiving account. If the receiving account and the receiving account belong
to the same
type of account, there is only one server here. For example, if the payment
account and
collection account are CCB accounts, they belong to bank transfer, and the
server refers to
the server provided by CCB. If the receivable account is different from the
payment
account, it belongs to the cross bank transfer, the receivable account and the
payment
account have the corresponding server. For example, if the payment account is
China
Construction Bank and the receiving account is Agricultural Bank of China, the
corresponding server includes First Server corresponding to China Construction
Bank and
Second Server corresponding to Agricultural Bank of China. The server here is
not limited
to a bank-provided server, but also includes: a third-party payment platform
(for example,
Alipay). In one example, before step 102, the server also needs to verify the
user name and
password of the payment account to ensure the security of the funds.
[36] Step 103: Freeze the funds of the recharging amount received in the
receiving account and
generate the recharging certificate corresponding to the recharging amount.
Recharge
certificate are used to certify that the server has successfully frozen the
funds in the
payment account in the electronic receipt of the payment account. The recharge
certificate
3

CA 02994977 2018-02-07
=
WO 2017/012077 PCT/C
N2015/084733
contains various types of information such as recharge amount, recharge time,
payment
account number, collection account number and customer's electronic signature,
ect. The
frozen funds are not dominated by the merchant corresponding to the receiving
account.
[37] Step 104: Deliver the recharge certificate to the first terminal.
[38] After obtaining the recharge certificate from the first terminal, the
customer can complete
payment and settlement with the merchant. The message of successful recharging
includes
information such as a recharged user name and recharge amount. In an example,
the server
further delivers a message of successful recharging to the second terminal, so
that the
merchant can grasp the recharge status of the customer in time.
[39] The above method is used for replenishing online transactions,
although the funds for
customer replenishment have been transferred from the payment account to the
merchant's
payment account, the funds are frozen in the payment account, and the service
provided by
the merchant is enjoyed by the customer before, businesses are unable to
control customer
recharge of funds, thus ensuring the safety of customer funds.
[40] As shown in Figure 2, in an example, the recharge request further
carries a fund settlement
condition, where the recharge certificate includes the fund release condition;
and in step
104, the recharge certificate is delivered to the first terminal afterwards,
the provided
method for recharging based on network transaction further includes the
following steps:
[41] Step 201: Obtain recharge certificate and transaction certificate
delivered by the first
terminal.
[42] The transaction certificate is an electronic certificate generated by
the client through the
network transaction between the first terminal and the merchant through the
second
terminal. Funding solution conditions refers to the funds from the frozen
state to release
conditions need to meet the conditions. Customers in the process of recharging
can set the
conditions for payment of funds. For example, users often need to fly by
plane, and in the
process of recharging, they can set the fund settlement conditions to purchase
air tickets.
Payment can be completed only when a customer uses a charge certificate to buy
a ticket.
[43] Transaction certificate are electronic data used to prove that a
client and a merchant have
completed an online transaction and have recorded transaction details. The
transaction
electronic certificate contains the purpose of the fund and the transaction
amount. Wherein,
the use of funds refers to the types of clients and business networks parent.
The transaction
amount refers to the transaction costs of the Internet trading.
[44] Step 202: Verify whether the recharge certificate is valid. If so,
then go to Step 203, if not,
then the end. In order to prevent the recharge certificate from being forged
or used by the
client itself, the validity of the certificate recharge needs to be verified.
Specifically, the
4

CA 02994977 2018-02-07
WO 2017/012077 PCT/CN2015/084733
certificate may be validated by checking the user's electronic signature on
the certificate, if
yes, go to step 203.
[45] Step 203, it is determined whether the use of funds is consistent with
the settlement
conditions. If yes, go to step 204 and release the funds already frozen in the
receiving
account equal to the transaction amount. If not, then end.
[46] The server compares the use of funds with the conditions for the
settlement of funds to
determine whether the two are exactly the same. It is only when the two are
completely at
the same time that the fund releases. The purpose of doing so is to further
verify the
identity of the user of the funds and improve the security of the top-up
funds. After the
server releases the funds in the receiving account, the merchant can freely
control the funds
and realize the payment of the network transaction. The above method does not
require the
user to complete the transaction with the merchant network through the post-
bank
third-party payment platform, and the customer can pay more than once by
recharging,
which makes the payment more convenient and quicker and improves the payment
efficiency.
[47] Step 205: Generate a released payment result message, and deliver the
payment result
message to the first terminal.
[48] The server feedbacks the payment result message to the first terminal,
so that the customer
can know the payment result in time. If the payment is successful, the payment
result
message is a payment success message, indicating that the payment for the
network
transaction is completed. If the recharge amount of the certificate is less
than the
transaction amount or the payment fails due to other reasons, the generated
payment result
message is a payment failure message. Customers and businesses need to re-pay
the
settlement.
[49] In one example, the method further includes: when the payment result
message is a
payment successful message, updating the recharge amount of the recharge
certificate
according to the transaction amount, synchronizing the updated remaining
amount content
to the first terminal, and notifying the user
[50] Since the recharge amount of the certificate is used to pay the
expenses incurred by the
customer, the recharge amount will be reduced accordingly. The server updates
the
recharge amount in real time and returns the recharge amount to the first
terminal, so that
the customer can grasp the dynamic of their consumption in time. The user is
informed that
after the first terminal receives the updated remaining amount, the user may
be reminded in
the form of a ring tone and / or a vibration of how much money is left by
using the ring
and/or vibration mode.

CA 02994977 2018-02-07
WO 2017/012077 PCT/CN2015/084733
[51] As shown in Figure 3, in one example, the network transaction based
recharge method
further includes:
[52] Step 301: Receive a fund withdrawal certificate and a recharge
certificate delivered by the
first terminal.
[53] Step 302: Verify whether the recharge certificate is valid. If so,
then go to Step 303, if not,
then the end.
[54] Step 303: Determine whether the withdrawal condition of the fund
satisfies the preset
condition, if yes, proceed to step 304, otherwise, end.
[55] Step 304: Release the funds in the receiving account equal to the
amount withdrawn from
the frozen funds.
[56] Step 305, refund the unfrozen funds to the payment account.
[57] Funding withdrawal refers to the refund of the funds frozen in the
merchant's payment
account to the payment account that the customer uses to pay for the funds.
The purpose of
setting a funds withdrawal is to further protect the safety of customer funds,
to prevent the
risk of financial losses to the clients from dishonest merchants. Clients and
merchants may
agree that withdrawal of funds is unconditional and may be conditionally
withdrawn as
agreed by both parties. Funding withdrawal certificate includes the amount of
withdrawal
and withdrawal of funds.
[58] In this example, although the recharging funds are not in the
customer's receiving account,
the customer still has the right to withdraw the funds, which effectively
ensures the security
of the funds and at the same time, it can urge the merchants to provide the
clients with
better quality service, achieve the goal of double benefit.
[59] In one example, the method further includes: after the funds are
returned to the payment
account, succeeding, updating the recharging amount of the recharging document
according to the reimbursement amount, and synchronizing the updating result
to the first
terminal.
[60] When the withdrawal of funds is successful, the recharge amount of the
recharge certificate
is updated according to the withdrawal amount, and the update result is
delivered to the
first terminal. In this example, the result of the withdrawal of funds is
reflected by the
updated recharge amount, and the client can understand the processing result
of the server's
withdrawal in the first time.
[61] As shown in Figure 4, in an example, the User A obtains the recharge
certificate through
the first terminal 20 by recharging the server 10. The User A obtains the
transaction
certificate through the first terminal 20 and the merchant B through the
second terminal 30
for network transaction. The first terminal 20 delivers the top-up certificate
and the
6

CA 02994977 2018-02-07
=
WO 2017/012077 PCT/CN2015/084733
transaction certificate to the server 10 to complete the payment processing by
the server 10.
[62] When required, the purpose of the certificate is varied. The payment
of the online
transaction between the above example customer and the merchant is only for
the
convenience of understanding the technical solution of the present invention.
It does not
limit the application of recharge certificates. Here are a few examples of
recharging
certificates. For example, the payment certificate is used to process the
annual card of the
merchant. When the user consumes, he can partially pay the frozen funds for
payment. If
the user cancels the card, the remaining funds can be withdrawn at any time.
[63] As shown in Figure 5, a network-based recharge device is provided,
which includes the
following modules:
[64] The request receiving module 50 is used to receive the recharge
request delivered by the
first terminal, and the recharge request carries the payment account, the
amount of the
recharge and the receivable account.
[65] The fund payment module 51 is used to pay the fund of the
reimbursement amount in the
payment account to the collection account.
[66] The certificate generating module 52 is used to freeze funds of the
recharging amount
received in the receiving account and generate a recharging certificate
corresponding to the
recharging amount.
[67] The information delivering module 53 is used to deliver the recharge
certificate to the first
terminal.
[68] As shown in Figure 6, in an example, the recharge request further
carries a fund settlement
condition, and the recharge certificate includes the fund settlement
condition; and the
network transaction-based recharging device further includes:
[69] The first information acquisition module 60 is used to acquire a
recharge certificate
delivered by the first terminal and a transaction certificate, where the
transaction certificate
includes a fund usage and a transaction amount.
[70] The first verification module 61 is used to verify whether the
recharge certificate is valid.
[71] The first fund releasing module 62 is used to determine whether the
purpose of the fund is
consistent with the fund settlement condition when the result of the first
verification
module is positive, and if so, the amount of funds that has been frozen in the
frozen
collection account is equal to the amount of the transaction.
[72] The first message delivering module 63 is used to generate a releasing
payment result
message, and deliver the payment result message to the first terminal.
[73] As shown in Figure 7, in one example, the online transaction-based
recharging device
further includes:
7

[74] The first updating module 64 is used to update the recharging amount
of the recharging
document according to the transaction amount when the payment result message
is a
payment success message, and deliver the updated remaining amount to the first
terminal,
and notify the user.
[75] As shown in Figure 8, in one example, an online transaction-based
recharging device
provided further includes:
[76] The second information acquisition module 80 is used to receive the
redemption certificate
and the fund withdrawal certificate delivered by the first terminal, where the
fund
withdrawal certificate includes the withdrawal amount and the fund withdrawal
condition.
[77] The second verification module 81 is used to verify whether the
recharge certificate is
valid.
[78] The second funds unfreezing module 82 is used to further determine
whether the
withdrawal conditions of the funds satisfy the preset condition when the
verification result
of the second verification module is yes, and if yes, release the frozen funds
in the received
accounts withdrawal of the same amount of funds.
[79] Funding withdrawal module 83 is used for returning the defrosted funds
to the payment
account.
[80] As shown in Figure 9, in one example, an online transaction-based
recharging device
provided further includes:
[81] The second updating module 84 is used to update the recharging amount
of the recharging
certificate according to the reimbursement amount after the fund is returned
to the payment
account, and synchronize the updating result to the first terminal.
[82] A person of skill in the art considers the problems disclosed herein
and sought to be
solved by the present disclosure to be exclusively computer problems and
contemplates
only solutions to those problems that include essential computer elements.
Abstract ideas,
mere schemes, plans, rules, or mental processes that do not include computer
elements are
expressly excluded from this application.
[83] The ordinary technicians in the field can understand and implement all
or part of the
processes in the above mentioned method of the example which can be completed
by
means of a computer program that can be stored in a computer-readable storage
medium.
When the program is executing, it may include all the above-mentioned process
in the
example. Among them, the storage medium can be a magnetic disk, CD, a read-
only
memory (ROM) and other non-volatile storage media or random access memory
(RAM),
etc.
[84] The characteristics of technology in the above example can be
arbitrarily combined. In
8
Date Recue/Date Received 2020-07-14

order to simplify the description, it does not describe all the possible
combinations of the
various characteristics of technology in the above examples, however, as long
as the
combination of these characteristics of technology are not conflict, it should
be considered
in the scope of this Specification records.
[85] The above example only express several examples of the invention,
and its descriptions are
more specific and detailed, however, it cannot to be considered as a
limitation of the scope
of the invention patent. It should be noted that various modifications and
improvements
can be made by those skilled technicians in the field without departing from
the inventive
concept, which belonged to the protection scope of the invention. Therefore,
the protection
scope of patent in the invention should be subject to the attached claims.
9
Date Recue/Date Received 2020-07-14

Representative Drawing
A single figure which represents the drawing illustrating the invention.
Administrative Status

2024-08-01:As part of the Next Generation Patents (NGP) transition, the Canadian Patents Database (CPD) now contains a more detailed Event History, which replicates the Event Log of our new back-office solution.

Please note that "Inactive:" events refers to events no longer in use in our new back-office solution.

For a clearer understanding of the status of the application/patent presented on this page, the site Disclaimer , as well as the definitions for Patent , Event History , Maintenance Fee  and Payment History  should be consulted.

Event History

Description Date
Letter Sent 2021-10-05
Inactive: Grant downloaded 2021-10-05
Inactive: Grant downloaded 2021-10-05
Grant by Issuance 2021-10-05
Inactive: Cover page published 2021-10-04
Pre-grant 2021-08-17
Inactive: Final fee received 2021-08-17
Notice of Allowance is Issued 2021-08-06
Letter Sent 2021-08-06
Notice of Allowance is Issued 2021-08-06
Inactive: Q2 passed 2021-08-04
Inactive: Approved for allowance (AFA) 2021-08-04
Amendment Received - Response to Examiner's Requisition 2021-04-09
Amendment Received - Voluntary Amendment 2021-04-09
Examiner's Report 2021-02-18
Inactive: Report - No QC 2021-02-12
Amendment Received - Voluntary Amendment 2021-01-11
Amendment Received - Response to Examiner's Requisition 2021-01-11
Examiner's Report 2020-12-21
Inactive: Report - No QC 2020-12-18
Amendment Received - Voluntary Amendment 2020-11-24
Common Representative Appointed 2020-11-07
Examiner's Report 2020-08-28
Inactive: Report - No QC 2020-07-31
Letter sent 2020-07-17
Advanced Examination Determined Compliant - paragraph 84(1)(a) of the Patent Rules 2020-07-17
Letter Sent 2020-07-17
Inactive: COVID 19 - Deadline extended 2020-07-16
Request for Examination Requirements Determined Compliant 2020-07-14
Request for Examination Received 2020-07-14
All Requirements for Examination Determined Compliant 2020-07-14
Inactive: Advanced examination (SO) 2020-07-14
Amendment Received - Voluntary Amendment 2020-07-14
Inactive: Advanced examination (SO) fee processed 2020-07-14
Common Representative Appointed 2019-10-30
Common Representative Appointed 2019-10-30
Change of Address or Method of Correspondence Request Received 2019-01-31
Change of Address or Method of Correspondence Request Received 2018-10-15
Revocation of Agent Requirements Determined Compliant 2018-10-15
Appointment of Agent Requirements Determined Compliant 2018-10-15
Revocation of Agent Request 2018-10-15
Appointment of Agent Request 2018-10-15
Change of Address or Method of Correspondence Request Received 2018-07-12
Inactive: Cover page published 2018-04-05
Inactive: Notice - National entry - No RFE 2018-02-23
Inactive: First IPC assigned 2018-02-20
Letter Sent 2018-02-20
Inactive: IPC assigned 2018-02-20
Application Received - PCT 2018-02-20
National Entry Requirements Determined Compliant 2018-02-07
Application Published (Open to Public Inspection) 2017-01-26

Abandonment History

There is no abandonment history.

Maintenance Fee

The last payment was received on 2021-06-25

Note : If the full payment has not been received on or before the date indicated, a further fee may be required which may be one of the following

  • the reinstatement fee;
  • the late payment fee; or
  • additional fee to reverse deemed expiry.

Please refer to the CIPO Patent Fees web page to see all current fee amounts.

Fee History

Fee Type Anniversary Year Due Date Paid Date
MF (application, 2nd anniv.) - standard 02 2017-07-21 2018-02-07
Reinstatement (national entry) 2018-02-07
Registration of a document 2018-02-07
Basic national fee - standard 2018-02-07
MF (application, 3rd anniv.) - standard 03 2018-07-23 2018-07-06
MF (application, 4th anniv.) - standard 04 2019-07-22 2019-01-11
MF (application, 5th anniv.) - standard 05 2020-07-21 2020-01-08
Request for examination - standard 2020-08-10 2020-07-14
Advanced Examination 2020-07-14 2020-07-14
MF (application, 6th anniv.) - standard 06 2021-07-21 2021-06-25
Final fee - standard 2021-12-06 2021-08-17
MF (patent, 7th anniv.) - standard 2022-07-21 2022-06-22
MF (patent, 8th anniv.) - standard 2023-07-21 2023-06-14
MF (patent, 9th anniv.) - standard 2024-07-22 2023-12-15
Owners on Record

Note: Records showing the ownership history in alphabetical order.

Current Owners on Record
10353744 CANADA LTD.
Past Owners on Record
YI ZHANG
Past Owners that do not appear in the "Owners on Record" listing will appear in other documentation within the application.
Documents

To view selected files, please enter reCAPTCHA code :



To view images, click a link in the Document Description column. To download the documents, select one or more checkboxes in the first column and then click the "Download Selected in PDF format (Zip Archive)" or the "Download Selected as Single PDF" button.

List of published and non-published patent-specific documents on the CPD .

If you have any difficulty accessing content, you can call the Client Service Centre at 1-866-997-1936 or send them an e-mail at CIPO Client Service Centre.


Document
Description 
Date
(yyyy-mm-dd) 
Number of pages   Size of Image (KB) 
Representative drawing 2021-09-03 1 12
Claims 2018-02-07 3 127
Abstract 2018-02-07 2 80
Description 2018-02-07 9 454
Drawings 2018-02-07 7 131
Representative drawing 2018-03-28 1 25
Cover Page 2018-03-28 1 45
Claims 2020-07-14 10 293
Description 2020-07-14 9 472
Claims 2020-11-24 10 304
Claims 2021-01-11 10 303
Claims 2021-04-09 10 303
Cover Page 2021-09-03 1 42
Notice of National Entry 2018-02-23 1 193
Courtesy - Certificate of registration (related document(s)) 2018-02-20 1 103
Courtesy - Acknowledgement of Request for Examination 2020-07-17 1 432
Commissioner's Notice - Application Found Allowable 2021-08-06 1 570
International search report 2018-02-07 15 516
Patent cooperation treaty (PCT) 2018-02-07 1 60
National entry request 2018-02-07 9 375
Request for examination / Amendment / response to report / Advanced examination (SO) 2020-07-14 18 557
Courtesy - Advanced Examination Request - Compliant (SO) 2020-07-17 1 173
Examiner requisition 2020-08-28 5 230
Amendment / response to report 2020-11-24 29 976
Examiner requisition 2020-12-21 4 222
Amendment / response to report 2021-01-11 27 850
Examiner requisition 2021-02-18 4 173
Amendment / response to report 2021-04-09 15 451
Final fee 2021-08-17 3 61
Electronic Grant Certificate 2021-10-05 1 2,527