Abstract: A transaction request is received. The transaction request includes a merchant identifier. The merchant identifier is for identifying a merchant. The merchant's banking details are appended to the transaction request. The transaction request, with the appended banking details, is transmitted to a user's bank. Confirmation is received that a transaction has been performed in accordance with the transaction request. A confirmation is transmitted to the merchant to indicate that the transaction has been performed.
1. A method comprising:
receiving a transaction request that includes a merchant identifier, said merchant identifier for identifying a merchant;
appending the merchant's banking details to the received transaction request;
transmitting the transaction request, including the merchant's banking details, to a user's bank;
receiving confirmation that a transaction has been performed in accordance with the transaction request; and
transmitting, to the merchant, a confirmation that the transaction has been performed.
2. The method of claim 1, wherein said step of receiving the transaction request includes receiving the transaction request from the user's bank.
3. The method of claim 1, wherein said step of receiving the transaction request includes receiving the transaction request from the user.
4. The method of claim 3, further comprising:
prior to said step of receiving the transaction request:
receiving, from the merchant, a request for a QR (quick response) code;
generating the requested QR code; and transmitting the generated QR code to the merchant.
5. The method of claim 4, wherein:
said request for the QR code contains said merchant identifier and a transaction amount for the transaction; and
the generated QR code encodes said merchant identifier and transaction amount.
6. The method of claim 1, wherein said transaction request includes said transaction amount.
7. The method of claim 1, further comprising:
> prior to said appending step, retrieving the merchant's banking details
from a directory.
8. A method comprising:
receiving a transaction request from a user, the transaction request • including a merchant identifier, said merchant identifier for identifying a merchant, the transaction request proposing a transaction;
appending the merchant's banking details to the received transaction request;
transmitting, to the user, a name that identifies the merchant;
receiving an indication from the user to complete the transaction;
in response to the indication, initiating a funds transfer in an EFT (electronic funds transfer) system; and
transmitting, to the merchant, a confirmation that the transaction has been performed.
9. The method of claim 8, wherein the step of receiving the indication
includes receiving, from the user, a transaction amount for the proposed transaction.
10. The method of claim 8, further comprising.
prior to said appending step, retrieving the merchant's banking details from a directory.
11. The method of claim 8, further comprising:
based on said merchant identifier, retrieving a transaction amount for the transaction.
12. The method of claim 11, wherein the merchant is a mass transit system.
13. A method comprising:
receiving merchant banking details, said merchant banking details pertaining to a bank account owned by a merchant;
transmitting, to a user, a name that identifies the merchant;
receiving an indication from the user to complete a transaction to benefit the merchant;
initiating a funds transfer in an EFT (electronic funds transfer) system to effect said transaction; and
transmitting, to a payment services provider, a confirmation that said transaction has been performed.
14. The method of claim 13, further comprising:
prior to said step of receiving merchant banking details:
receiving a transaction request from the user, the transaction request including a merchant identifier that identifies the merchant; and
transmitting the merchant identifier to the payment services provider.
15. The method of claim 13, wherein the merchant banking details are received from the payment services provider.
16. The method of claim 13, wherein said step of receiving the merchant banking details includes receiving, from the payment services provider, a transaction request pertaining to said transaction.
17. A method comprising:
requesting a QR (quick response) code from a remote computer operated by a payment services provider;
receiving the requested QR code from the remote computer;
displaying the received QR code on a display device; and
after the displaying step, receiving a confirmation that a transaction has been performed in accordance with data contained in the received QR code.
18. The method of claim 17, further comprising:
prior to the requesting step, receiving data that pertains to said transaction;
and wherein:
said requesting step includes transmitting a transaction amount > for the transaction.
19. The method of claim 18, further comprising:
prior to the requesting step, calculating the transaction amount based at least in part on the received data that pertains to said transaction. )
20. The method of claim 19, wherein the QR code encodes said transaction
amount and a merchant identifier that identifies a merchant that benefits from the
transaction.
| # | Name | Date |
|---|---|---|
| 1 | 202047011778.pdf | 2020-03-18 |
| 2 | 202047011778-STATEMENT OF UNDERTAKING (FORM 3) [18-03-2020(online)].pdf | 2020-03-18 |
| 3 | 202047011778-PROOF OF RIGHT [18-03-2020(online)].pdf | 2020-03-18 |
| 4 | 202047011778-POWER OF AUTHORITY [18-03-2020(online)].pdf | 2020-03-18 |
| 5 | 202047011778-FORM 1 [18-03-2020(online)].pdf | 2020-03-18 |
| 6 | 202047011778-FIGURE OF ABSTRACT [18-03-2020(online)].pdf | 2020-03-18 |
| 7 | 202047011778-DRAWINGS [18-03-2020(online)].pdf | 2020-03-18 |
| 8 | 202047011778-DECLARATION OF INVENTORSHIP (FORM 5) [18-03-2020(online)].pdf | 2020-03-18 |
| 9 | 202047011778-COMPLETE SPECIFICATION [18-03-2020(online)].pdf | 2020-03-18 |
| 10 | 202047011778-RELEVANT DOCUMENTS [08-07-2020(online)].pdf | 2020-07-08 |
| 11 | 202047011778-FORM 13 [08-07-2020(online)].pdf | 2020-07-08 |
| 12 | 202047011778-AMENDED DOCUMENTS [08-07-2020(online)].pdf | 2020-07-08 |
| 13 | 202047011778-FORM 3 [27-08-2020(online)].pdf | 2020-08-27 |
| 14 | 202047011778-FORM 18 [18-09-2021(online)].pdf | 2021-09-18 |
| 15 | 202047011778-FER.pdf | 2022-06-01 |
| 16 | 202047011778-PETITION UNDER RULE 137 [26-11-2022(online)].pdf | 2022-11-26 |
| 17 | 202047011778-OTHERS [26-11-2022(online)].pdf | 2022-11-26 |
| 18 | 202047011778-Information under section 8(2) [26-11-2022(online)].pdf | 2022-11-26 |
| 19 | 202047011778-FORM 3 [26-11-2022(online)].pdf | 2022-11-26 |
| 20 | 202047011778-FER_SER_REPLY [26-11-2022(online)].pdf | 2022-11-26 |
| 21 | 202047011778-COMPLETE SPECIFICATION [26-11-2022(online)].pdf | 2022-11-26 |
| 22 | 202047011778-CLAIMS [26-11-2022(online)].pdf | 2022-11-26 |
| 23 | 202047011778-US(14)-HearingNotice-(HearingDate-07-04-2025).pdf | 2025-03-12 |
| 24 | 202047011778-Correspondence to notify the Controller [02-04-2025(online)].pdf | 2025-04-02 |
| 25 | 202047011778-Written submissions and relevant documents [22-04-2025(online)].pdf | 2025-04-22 |
| 26 | 202047011778-Annexure [22-04-2025(online)].pdf | 2025-04-22 |
| 1 | SearchHistoryE_30-05-2022.pdf |