WO2023128872A2 - Serveur et procédé de partage d'un portefeuille numérique pour une transaction électronique - Google Patents

Serveur et procédé de partage d'un portefeuille numérique pour une transaction électronique Download PDF

Info

Publication number
WO2023128872A2
WO2023128872A2 PCT/SG2022/050937 SG2022050937W WO2023128872A2 WO 2023128872 A2 WO2023128872 A2 WO 2023128872A2 SG 2022050937 W SG2022050937 W SG 2022050937W WO 2023128872 A2 WO2023128872 A2 WO 2023128872A2
Authority
WO
WIPO (PCT)
Prior art keywords
transaction
secondary user
digital wallet
information
user
Prior art date
Application number
PCT/SG2022/050937
Other languages
English (en)
Other versions
WO2023128872A3 (fr
Inventor
Prateek Agarwal
Amit JAYEE
Siang Qin Marcus CHUA
Original Assignee
Gp Network Asia Pte. 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
Application filed by Gp Network Asia Pte. Ltd. filed Critical Gp Network Asia Pte. Ltd.
Publication of WO2023128872A2 publication Critical patent/WO2023128872A2/fr
Publication of WO2023128872A3 publication Critical patent/WO2023128872A3/fr

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/22—Payment schemes or models
    • G06Q20/229—Hierarchy of users of accounts
    • G06Q20/2295—Parent-child type, e.g. where parent has control on child rights
    • 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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/326—Payment applications installed on the mobile devices
    • G06Q20/3263—Payment applications installed on the mobile devices characterised by activation or deactivation of payment capabilities
    • 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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
    • G06Q20/367—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes
    • 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/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/405—Establishing or using transaction specific rules

Definitions

  • Various embodiments relate to a server and a method for sharing a digital wallet for an electronic transaction.
  • a digital wallet (also known as an “e-wallet”) may be a software program or an electronic device which allows one party to make electronic transactions with another party bartering digital currency units for goods and/or services.
  • e-wallet may be a software program or an electronic device which allows one party to make electronic transactions with another party bartering digital currency units for goods and/or services.
  • P2P peer-to-peer
  • KYC know-your-client
  • parents or employers may be hesitant to supplement more money to the recipients, as they do not have visibility of recipients’ transaction activities.
  • a server for sharing a digital wallet of a primary user for an electronic transaction comprises: a communication interface configured to receive a request to add an account of a secondary user to the digital wallet and information about one or more transaction controls for the secondary user from the primary user; and a processor arranged in data or signal communication with the communication interface to receive the request to add the account of the secondary user to the digital wallet and the information about the one or more transaction controls for the secondary user; wherein the processor is configured to create a linkage identifier which identifies a link between the account of the secondary user and the digital wallet, and store the information about the one or more transaction controls for the secondary user in relation to the linkage identifier, and where the communication interface receives a transaction request using the digital wallet from the secondary user, the processor is further configured to derive the linkage identifier from the transaction request, check the information about the one or more transaction controls relating to the linkage identifier, and decide whether to allow the transaction request based on the information about the one
  • the processor is configured to allow the transaction request if the transaction request satisfies one or more conditions in the information about the one or more transaction controls, and decline the transaction request if the transaction request does not satisfy the one or more conditions in the information about the one or more transaction controls.
  • the processor is further configured to provide an account of the primary user with information about a history of electronic transactions made by the secondary user using the digital wallet.
  • the processor is further configured to deactivate the linkage identifier.
  • the processor is further configured to delete the linkage identifier.
  • the processor is further configured to modify the information about the one or more transaction controls for the secondary user.
  • the information about the one or more transaction controls includes information about a monetary limit of electronic transactions which can be made by the secondary user using the digital wallet.
  • the processor is configured to add a transaction option using the digital wallet to the account of the secondary user.
  • a method for sharing a digital wallet of a primary user for an electronic transaction includes: receiving a request to add an account of a secondary user to the digital wallet and information about one or more transaction controls for the secondary user from the primary user; creating a linkage identifier which identifies a link between the account of the secondary user and the digital wallet; storing the information about the one or more transaction controls for the secondary user in relation to the linkage identifier; receiving a transaction request using the digital wallet from the secondary user; deriving the linkage identifier from the transaction request; checking the information about the one or more transaction controls relating to the linkage identifier; and deciding whether to allow the transaction request based on the information about the one or more transaction controls relating to the linkage identifier.
  • the method further includes: allowing the transaction request if the transaction request satisfies one or more conditions in the information about the one or more transaction controls; and declining the transaction request if the transaction request does not satisfy the one or more conditions in the information about the one or more transaction controls.
  • the method further includes: providing an account of the primary user with information about a history of electronic transactions made by the secondary user using the digital wallet.
  • the method further includes: receiving a request from the primary user to unlink the account of the secondary user from the digital wallet; and deactivating the linkage identifier.
  • the method further includes: receiving a request from the primary user to unlink the account of the secondary user from the digital wallet; and deleting the linkage identifier.
  • the method further includes: receiving a request from the primary user to modify the information about the one or more transaction controls for the secondary user; and modifying the information about the one or more transaction controls for the secondary user.
  • the information about the one or more transaction controls includes information about a monetary limit of electronic transactions which can be made by the secondary user using the digital wallet.
  • the method further includes: after the linkage identifier which identifies the link between the account of the secondary user and the digital wallet is created, adding a transaction option using the digital wallet to the account of the secondary user.
  • a data processing apparatus configured to perform the method of any one of the above embodiments is provided.
  • a computer program element comprising program instructions, which, when executed by one or more processors, cause the one or more processors to perform the method of any one of the above embodiments is provided.
  • a computer-readable medium comprising program instructions, which, when executed by one or more processors, cause the one or more processors to perform the method of any one of the above embodiments.
  • the computer-readable medium may include a non-transitory computer-readable medium.
  • a system for sharing a digital wallet for an electronic transaction comprises: a first electronic device belonging to a primary user holding the digital wallet; a second electronic device belonging to a secondary user; and a server.
  • the server comprises: a communication interface configured to receive a request to add an account of the secondary user to the digital wallet and information about one or more transaction controls for the secondary user from the first electronic device; and a processor arranged in data or signal communication with the communication interface to receive the request to add the account of the secondary user to the digital wallet and the information about the one or more transaction controls for the secondary user; wherein the processor is configured to create a linkage identifier which identifies a link between the account of the secondary user and the digital wallet, and store the information about the one or more transaction controls for the secondary user in relation to the linkage identifier, and where the communication interface receives a transaction request using the digital wallet from the second electronic device, the processor is further configured to derive the linkage identifier, check the information about the one or
  • FIG. 1 illustrates an infrastructure of a system including a server for sharing a digital wallet for an electronic transaction according to various embodiments.
  • FIG. 2 illustrates a block diagram of a server for sharing a digital wallet for an electronic transaction according to various embodiments.
  • FIG. 3 illustrates a flow diagram for a method for sharing a digital wallet for an electronic transaction according to various embodiments.
  • FIGS. 4 to 6 illustrate exemplary user interface screens of an electronic device of a primary user according to various embodiments.
  • FIGS. 7 and 8 illustrate exemplary user interface screens of an electronic device of a secondary user according to various embodiments.
  • Embodiments described in the context of one of a server and a method are analogously valid for the other of the server and method. Similarly, embodiments described in the context of a server are analogously valid for a method, and vice-versa.
  • the articles “a”, “an” and “the” as used with regard to a feature or element include a reference to one or more of the features or elements.
  • FIG. 1 illustrates an infrastructure of a system 200 including a server 100 for sharing a digital wallet 160 for an electronic transaction according to various embodiments.
  • the system 200 may include, but is not limited to, the server 100, one or more electronic devices 141, 151, one or more external servers 170, 180, and a network 190.
  • the digital wallet 160 may be a software program or an electronic device which allows one party to make an electronic transaction with another party bartering digital currency units for goods and/or services.
  • the network 190 may include, but is not limited to, a Local Area Network (LAN), a Wide Area Network (WAN), a Global Area Network (GAN), or any combination thereof.
  • the network 190 may provide a wireline communication, a wireless communication, or a combination of the wireline and wireless communication between the server 100 and the one or more electronic devices 141, 151, and between the server 100 and the one or more external servers 170, 180, for example, a financial institution server 170 and a merchant server 180.
  • the electronic devices 141, 151 may be arranged in data or signal communication with the server 100 via the network 190.
  • the electronic devices 141, 151 may include, but are not limited to, at least one of the following: a mobile phone, a tablet computer, a laptop computer, a desktop computer, a head-mounted display and a smart watch.
  • a first electronic device 141 may belong to a primary user 140 and a second electronic device 151 may belong to a secondary user 150 (also referred to as a “dependent user”).
  • the primary user 140 may be a user who holds the digital wallet 160 and is responsible for a spending accrued through a use of the digital wallet 160.
  • the primary user 140 may be any type of person or entity which may be able to hold the digital wallet 160 and be responsible for the spending accrued through the use of the digital wallet 160.
  • the primary user 140 may include, but is not limited to, a parent and/or an employer.
  • the primary user 140 may add an account of the secondary user 150 to the digital wallet 160 via the server 100, so that the secondary user 150 may make the electronic transaction using funds attributable to the digital wallet 160.
  • the primary user 140 may be responsible for spending accrued through the secondary user’s 150 use of the digital wallet 160.
  • the primary user 140 may wish to have control over the secondary user’s 150 electronic transactions.
  • the primary user 140 may set information about one or more transaction controls for the secondary user 150 to use the digital wallet 160.
  • the primary user 140 may set a monetary limit (e.g. a pertransaction limit, or a limit on total spend within a given period) for the use of the digital wallet 160 by the secondary user 150.
  • the primary user 140 may control and/or modify the information about the one or more transaction controls for the use of the digital wallet 160 by the secondary user 150.
  • the secondary user 150 may be a user that the primary user 140 allows to make electronic transactions using funds attributable to the digital wallet 160.
  • the secondary user 150 may be any type of person or entity allowed by the primary user 140 to make the electronic transactions using funds attributable to the digital wallet 160.
  • the secondary user 150 may be a person or entity which may be unable to receive credit under regulations/law.
  • the secondary user 150 may be a person or entity which may be unable to receive an approval from a financial institution, for example, a bank, for a line of credit.
  • the secondary user 150 may include, but is not limited to, a child, a student, and/or an employee.
  • the primary user 140 may add a plurality of accounts, each corresponding to one of the plurality of secondary users 150 to the digital wallet 160 via the server 100.
  • the server 100 may include a communication interface 110, a processor 120, and a memory 130 (as will be described with reference to FIG. 2).
  • the server 100 may communicate with the first electronic device 141 via the network 190.
  • the first electronic device 141 may receive a request from the primary user 140 to add the account of the secondary user 150 to the digital wallet 160.
  • the first electronic device 141 may send the request to the server 100 to add the account of the secondary user 150 to the digital wallet 160 via the network 190.
  • the first electronic device 141 may receive the information about the one or more transaction controls for the secondary user 150 from the primary user 140.
  • the first electronic device 141 may send the information about the one or more transaction controls for the secondary user 150 to the server 100 via the network 190.
  • the primary user 140 may input the information about the one or more transaction controls for the secondary user 150 in the course of inputting the request to add the account of the secondary user 150 to the digital wallet 160.
  • a user interface screen may be provided to the first electronic device 141 for the primary user 140 to input the information about the one or more transaction controls for the secondary user 150.
  • the server 100 may create a linkage identifier which identifies a link between the account of the secondary user 150 and the digital wallet 160.
  • the linkage identifier may be used as an identifier for electronic transactions made by the secondary user 150 using the digital wallet 160.
  • the linkage identifier may be used as a proxy for the primary user’s digital wallet 160 so that the secondary user 150 may use the linkage identifier to identify a payment method for electronic transactions.
  • the linkage identifier may be added as a payment method in a software application executing on the second electronic device 151.
  • the server 100 may store the information about the one or more transaction controls for the secondary user 150 in relation to the linkage identifier.
  • the server 100 may communicate with the second electronic device 151 via the network 190.
  • the second electronic device 151 may receive a transaction request using the digital wallet 160 from the secondary user 150.
  • the second electronic device 151 may send the transaction request using the digital wallet 160 to the server 100 via the network 190.
  • the server 100 may derive the linkage identifier from the transaction request. Thereafter, the server 100 may check the information about the one or more transaction controls relating to the linkage identifier. The server 100 may then decide whether to allow the transaction request based on the information about the one or more transaction controls relating to the linkage identifier.
  • the server 100 may allow the transaction request. For example, if the amount of the transaction request satisfies the monetary limit for the use of the digital wallet 160 by the secondary user 150, the server 100 may allow the transaction request. In another example, if the merchant at which the transaction is being performed, or the goods and/or services to be purchased, belongs in a category that is included in the one or more transaction controls, the server 100 may allow the transaction request. If the transaction request does not satisfy the one or more conditions in the information about the one or more transaction controls, the server 100 may decline the transaction request.
  • the server 100 may decline the transaction request.
  • the server 100 may decline the transaction request if the amount of the transaction request exceeds the monetary limit for the secondary user 150 set by the primary user 140.
  • the server 100 may decline the transaction request if the merchant at which the transaction is being performed, or the goods and/or services to be purchased, belongs in a category that is excluded by the one or more transaction controls.
  • the server 100 may communicate with the merchant server 180 via the network 190.
  • the server 100 may receive transaction information relating to the transaction request from the merchant server 180 via the network 190.
  • the second electronic device 151 may receive the transaction information from the merchant server 180 via the network 190, and then send the transaction request including the transaction information to the server 100 via the network 190.
  • the transaction information may include information about goods and/or services that the secondary user 150 is going to purchase using the digital wallet 160.
  • the information about goods and/or services may include, but is not limited to, information about name and price of the goods and/or services.
  • the server 100 may communicate with the financial institution server 170, for example, a bank server, via the network 190.
  • the server 100 may request the financial institution server 170 to withdraw the amount of the transaction request from the funds deposited in the digital wallet 160 to make payment to the merchant server 180.
  • the server 100 may include the financial institution server 170.
  • the server 100 may withdraw the amount of the transaction request from the funds deposited in the digital wallet 160 to make payment to the merchant server 180.
  • FIG. 2 illustrates a block diagram of a server 100 for sharing a digital wallet 160 for an electronic transaction according to various embodiments.
  • the server 100 may include a communication interface 110, a processor 120, and a memory 130.
  • the communication interface 110 may allow one or more electronic devices 141, 151 to communicate with the processor 120 of the server 100 via a network 190, as shown in FIG. 1.
  • the electronic devices 141, 151 may include, but is not limited to, a first electronic device 141 belonging to a primary user 140 who holds the digital wallet 160, and a second electronic device 151 belonging to a secondary user 150 who is allowed by the primary user 140 to make the electronic transaction using funds attributable to the digital wallet 160.
  • the communication interface 110 may transmit signals to the electronic devices 141, 151, and/or receive signals from the electronic devices 141, 151 via the network 190.
  • the communication interface 110 may allow one or more external servers 170, 180, for example, a financial institution server 170 and a merchant server 180, to communicate with the processor 120 of the server 100 via the network 190, as shown in FIG. 1.
  • the communication interface 110 may transmit signals to the external servers 170, 180 and/or receive signals from the external servers 170, 180 via the network 190.
  • the communication interface 110 may receive a request to add an account of the secondary user 150 to the digital wallet 160 from the primary user 140.
  • the first electronic device 141 may receive the request to add the account of the secondary user 150 to the digital wallet 160 from the primary user 140.
  • the first electronic device 141 may send the request to add the account of the secondary user 150 to the digital wallet 160 to the communication interface 110 via the network 190.
  • the communication interface 110 may receive information about one or more transaction controls for the secondary user 150 from the primary user 140.
  • the primary user 140 may assign a spending limit, for example, an amount per each electronic transaction or a total amount per month, to the secondary user 150.
  • the first electronic device 141 may receive the information about the one or more transaction controls for the secondary user 150 from the primary user 140.
  • the first electronic device 141 may send the information about the one or more transaction controls for the secondary user 150 to the communication interface 110 via the network 190.
  • the communication interface 110 may concurrently receive the request to add the account of the secondary user 150 to the digital wallet 160 and the information about the one or more transaction controls for the secondary user 150.
  • the primary user 140 may input the information about the one or more transaction controls for the secondary user 150 in the course of inputting the request to add the account of the secondary user 150 to the digital wallet 160.
  • the communication interface 110 may receive the request to add the account of the secondary user 150 to the digital wallet 160 first, and subsequently receive the information about the one or more transaction controls for the secondary user 150.
  • a user interface screen may be provided to the first electronic device 141 for the primary user 140 to input the information about the one or more transaction controls for the secondary user 150.
  • the processor 120 may include, but is not limited to, a microprocessor, an analogue circuit, a digital circuit, a mixed-signal circuit, a logic circuit, an integrated circuit, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), or any combination thereof. Any other kind of implementation of the respective functions, which will be described below in further detail, may also be understood as the processor 120.
  • CPU Central Processing Unit
  • GPU Graphics Processing Unit
  • DSP Digital Signal Processor
  • FPGA Field Programmable Gate Array
  • ASIC Application Specific Integrated Circuit
  • the processor 120 may be arranged in data or signal communication with the communication interface 110 to receive the request to add the account of the secondary user 150 to the digital wallet 160 of the primary user 140 and the information about the one or more transaction controls for the secondary user 150.
  • the processor 120 may receive concurrently the request to add the account of the secondary user 150 to the digital wallet 160 and the information about the one or more transaction controls for the secondary user 150 from the communication interface 110. In some other embodiments, the processor 120 may receive the request to add the account of the secondary user 150 to the digital wallet 160 first, and subsequently receive the information about the one or more transaction controls for the secondary user 150 from the communication interface 110.
  • the processor 120 may link the account of the secondary user 150 to the digital wallet 160 of the primary user 140 by a secured linkage process.
  • a multi-factor authentication may be required for the secured linkage process.
  • the primary user 140 may be required to input an identifier of the secondary user 150 and secured information for the multi-factor authentication for the secured linkage process.
  • the identifier may include, but is not limited to, a mobile number, an email address, an Identity Document (ID) card number, and ID (e.g. ID of a digital wallet application/program) of the secondary user 150.
  • the secured information may include, but is not limited to, a secured code.
  • the primary user 140 may input the mobile number of the secondary user 150, as the identifier of the secondary user 150.
  • the processor 120 may receive the mobile number of the secondary user 150 from the first electronic device 141 via the communication interface 110.
  • the processor 120 may then create and send the secured code, for example, a One-time Password (OTP) which is valid for a certain period of time, to the mobile number of the secondary user 150.
  • the second electronic device 151 to which the said mobile number is assigned may receive the OTP from the processor 120 via the communication interface 110.
  • the primary user 140 may then input the OTP sent to the second electronic device 151.
  • OTP One-time Password
  • the processor 120 may receive the OTP from the first electronic device 141 via the communication interface 110, and check if the OTP received from the first electronic device 141 is the same as the OTP sent to the second electronic device 151. If the OTP received from the first electronic device 141 is the same as the OTP sent to the second electronic device 151, the processor 120 may link the account of the secondary user 150 to the digital wallet 160 of the primary user 140. In another example, the primary user 140 may input the email address of the secondary user 150, as the identifier of the secondary user 150, and the processor 120 may create and send the secured code to the email address of the secondary user 150.
  • the secured information may include biometric information including, but not limited to, a fingerprint, a face recognition template, a voice recognition template, an iris recognition template, and a palm print of the secondary user 150.
  • the primary user 140 may input the mobile number of the secondary user 150 as the identifier of the secondary user 150 and select the fingerprint of the secondary user 150 as the secured information.
  • the processor 120 may request the second user 150 to scan his/her fingerprint, and the second user 150 may scan his/her fingerprint on a fingerprint sensor embedded in or connected to the second electronic device 151.
  • the second electronic device 151 may check if the scanned fingerprint matches fingerprint data of the second user 150 stored in the second electronic device 151. If the scanned fingerprint matches the fingerprint data of the second user 150 stored in the second electronic device 151, the processor 120 may link the account of the secondary user 150 to the digital wallet 160 of the primary user 140.
  • the secured information may be a combination of the secured code and any of the biometric information of the secondary user 150.
  • the processor 120 may link the account of the secondary user 150 to the digital wallet 160 of the primary user 140. In this manner, the digital wallet 160 of the primary user 140 may be linked securely to the account of the secondary user 150.
  • the processor 120 may create a linkage identifier which identifies the link between the account of the secondary user 150 and the digital wallet 160 of the primary user 140.
  • the linkage identifier may be a unique identifier which identifies the link between the account of the secondary user 150 and the digital wallet 160.
  • the linkage identifier may be used as an identifier for the electronic transaction made by the secondary user 150 using the digital wallet 160.
  • the linkage identifier may be different from an identifier of the digital wallet 160 which is used for the electronic transaction of the primary user 140.
  • an intermediate digital wallet and/or an additional digital wallet for the secondary user 150 is not created. Instead, the linkage identifier may be used as the identifier for the electronic transaction made by the secondary user 150 using the digital wallet 160.
  • a payment gateway (not shown) of the server 100 may charge the digital wallet 160 of the primary user 140, even though the charge is initiated from the account of the secondary user 150.
  • the memory 130 may store input data and/or output data temporarily or permanently.
  • the memory 130 may store program code which allows the server 100 to perform a method 300 (as will be described with reference to FIG. 3).
  • the program code may be embedded in a payment Software Development Kit (SDK).
  • SDK Payment Software Development Kit
  • the memory 130 may include an internal memory of the server 100 and/or an external memory.
  • the external memory may include, but is not limited to, an external storage medium, for example, a memory card, a flash drive, and a web storage.
  • the processor 120 may store the linkage identifier in the memory 130.
  • the processor 120 may store the information about the one or more transaction controls for the secondary user 150 in relation to the linkage identifier in the memory 130.
  • the communication interface 110 may receive a transaction request using the digital wallet 160 of the primary user 140 from the secondary user 150.
  • the second electronic device 151 may receive the transaction request using the digital wallet 160 from the secondary user 150.
  • the second electronic device 151 may send the transaction request using the digital wallet 160 to the communication interface 110 via the network 190.
  • the processor 120 may receive the transaction request using the digital wallet 160 from the communication interface 110. The processor 120 may then derive the linkage identifier from the transaction request. Thereafter, the processor 120 may check the information about the one or more transaction controls relating to the linkage identifier. For example, the processor 120 may access the memory 130 to check the information about the one or more transaction controls relating to the linkage identifier derived from the transaction request. The processor 120 may then decide whether to allow the transaction request based on the information about the one or more transaction controls relating to the linkage identifier saved in the memory 130.
  • the processor 120 may allow the transaction request. For example, if the amount of the transaction request satisfies the monetary limit for the use of the digital wallet 160 by the secondary user 150, the processor 120 may allow the transaction request. If the transaction request does not satisfy the one or more conditions in the information about the one or more transaction controls, the processor 120 may decline the transaction request. For example, if the amount of the transaction request exceeds the monetary limit, the processor 120 may decline the transaction request.
  • the processor 120 may provide an account of the primary user 140 with information about a history of the electronic transaction made by the secondary user 150 using the digital wallet 160.
  • the first electronic device 141 may display a user experience screen showing the information about the history of the electronic transaction made by the secondary user 150 using the digital wallet 160.
  • Such information may include, but is not limited to, merchant name, price and name of the goods and/or services that the secondary user 150 has purchased using the digital wallet 160.
  • the primary user 140 may track spending of the secondary user 150.
  • the primary user 140 may add a plurality of accounts each corresponding to the plurality of secondary users 150 to the digital wallet 160 using the server 100.
  • the first electronic device 141 may display a user experience screen showing the information about the history of the electronic transaction made by the plurality of secondary users 150 using the digital wallet 160. In this manner, in accordance with various embodiments, the primary user 140 may track spending of each of the linked secondary users 150.
  • the communication interface 110 may receive a request from the primary user 140 to unlink the account of the secondary user 150 from the digital wallet 160.
  • the first electronic device 141 may receive the request from the primary user 140 to unlink the account of the secondary user 150 from the digital wallet 160, and send the request to unlink the account of the secondary user 150 from the digital wallet 160 to the communication interface 110.
  • the communication interface 110 may then send the request to unlink the account of the secondary user 150 from the digital wallet 160 to the processor 120.
  • the processor 120 may receive the request to unlink the account of the secondary user 150 from the digital wallet 160 from the communication interface 110, and then unlink the account of the secondary user 150 from the digital wallet 160.
  • the unlinked secondary user 150 may no longer use the digital wallet 160 shared by the primary user 140.
  • the processor 120 may deactivate the linkage identifier which identifies the link between the account of the secondary user 150 and the digital wallet 160 of the primary user 140.
  • the processor 120 may record information about the deactivation of the linkage identifier in the memory 130. Later on, if the processor 120 receives a new request to link the account of the secondary user 150 to the digital wallet 160 from the communication interface 110, the processor 120 may activate the linkage identifier which identifies the link between the account of the secondary user 150 and the digital wallet 160 of the primary user 140.
  • the processor 120 may record information about the activation of the linkage identifier in the memory 130.
  • the processor 120 may delete the linkage identifier which identifies the link between the account of the secondary user 150 and the digital wallet 160 of the primary user 140 from the memory 130. Later on, if the processor 120 receives a new request to link the account of the secondary user 150 to the digital wallet 160 from the communication interface 110, the processor 120 may create a new linkage identifier which identifies a new link between the account of the secondary user 150 and the digital wallet 160 of the primary user 140. The processor 120 may record the new linkage identifier in the memory 130.
  • the communication interface 110 may receive a request from the primary user 140 to modify the information about the one or more transaction controls for the secondary user 150.
  • the first electronic device 141 may receive the request from the primary user 140 to modify the information about the one or more transaction controls for the secondary user 150, and send the request to modify the information about the one or more transaction controls for the secondary user 150 to the communication interface 110.
  • the communication interface 110 may then send the request to modify the information about the one or more transaction controls for the secondary user 150 to the processor 120.
  • the processor 120 may receive the request to modify the information about the one or more transaction controls for the secondary user 150 from the communication interface 110, and then modify the information about the one or more transaction controls for the secondary user 150.
  • the processor 120 may add a transaction option using the digital wallet 160 of the primary user 140 to the account of the secondary user 150.
  • the second electronic device 151 may display information about the digital wallet 160 of the primary user 140 as one of the available transaction options (payment methods). The secondary user 150 may then select the added transaction option to make the electronic transaction using the digital wallet
  • the primary user 140 may easily share the digital wallet 160 with the secondary user 150 and allow the secondary user 150 to use the digital wallet 160 seamlessly, without the need to seek consent from the primary user 140 each time.
  • the primary user 140 can assign a spending limit to the secondary user 150, the primary user 140 may avoid unexpected spending and have control over the secondary user’s 150 electronic transactions.
  • the secondary user 150 may make the electronic transaction using the digital wallet 160 of the primary user 150 without the need to ask the primary user 140 to transfer funds to the digital wallet or the bank account of the secondary user 150.
  • the account of the primary user 140 may gain reward points provided by the server 100 for the electronic transaction made by the secondary user 150 using the digital wallet 160.
  • FIG. 3 illustrates a flow diagram for a method 300 for sharing a digital wallet for an electronic transaction according to various embodiments. According to various embodiments, the method 300 for sharing the digital wallet for the electronic transaction is provided.
  • the method 300 may be implemented by the server 100 illustrated in FIGS. 1 and 2. In some embodiments, the method 300 may be carried out by the server 100 illustrated in FIGS. 1 and 2.
  • the method 300 may include a step 301 of receiving a request to add an account of a secondary user 150 to the digital wallet 160 of a primary user 140 and information about one or more transaction controls for the secondary user 150 from the primary user 140.
  • receiving the request to add the account of the secondary user 150 to the digital wallet 160 and receiving the information about the one or more transaction controls for the secondary user 150 may be performed as two subsequent steps.
  • receiving the request to add the account of the secondary user 150 to the digital wallet 160 and receiving the information about the one or more transaction controls for the secondary user 150 may be performed as a single step.
  • the method 300 may include a step 302 of creating a linkage identifier which identifies a link between the account of the secondary user 150 and the digital wallet 160 of the primary user 140.
  • the method 300 may include a step 303 of storing the information about the one or more transaction controls for the secondary user 150 in relation to the linkage identifier.
  • the method 300 may include a step 304 of receiving a transaction request using the digital wallet 160 of the primary user 140 from the secondary user 150.
  • the method 300 may include a step 305 of deriving the linkage identifier.
  • the linkage identifier may be derived from the transaction request.
  • the method 300 may include a step 306 of checking the information about the one or more transaction controls relating to the linkage identifier.
  • the method 300 may include a step 307 of deciding whether to allow the transaction request based on the information about the one or more transaction controls relating to the linkage identifier.
  • the method 300 may further include a step of allowing the transaction request if the transaction request satisfies one or more conditions in the information about the one or more transaction controls, and declining the transaction request if the transaction request does not satisfy the one or more conditions in the information about the one or more transaction controls.
  • FIGS. 4 to 6 illustrate exemplary user interface screens of an electronic device of a primary user 140 according to various embodiments.
  • the electronic device may include a first electronic device 141 belonging to the primary user 140 who holds a digital wallet 160.
  • FIG. 4 illustrates exemplary user interface screens 141a - 141d displayed by the first electronic device 141 of the primary user 140 showing a linkage process between the digital wallet 160 of the primary user 140 and an account of a secondary user 150.
  • the first electronic device 141 may display the user interface screen 141a for the primary user 140 to request for a link between the digital wallet 160 of the primary user 140 and the account of the secondary user 150.
  • the user interface screen 141a may be displayed by the first electronic device 141.
  • the first electronic device 141 may display an image object 401 (also referred to as an “icon” or a “button”) for linking the account of the secondary user 150 to the digital wallet 160 of the primary user 140 on the user interface screen 141a. If the primary user 140 selects the image object 401 on the user interface screen 141a, the first electronic device 141 may display the user interface screen 141b for the primary user 140 to input an identifier of the secondary user 150.
  • an image object 401 also referred to as an “icon” or a “button”
  • the first electronic device 141 may display the user interface screen 141b for the primary user 140 to input an identifier of the secondary user 150.
  • the primary user 140 may input a mobile number of the secondary user 150 into a space 403 on the user interface screen 141b, as the identifier of the secondary user 150.
  • the primary user 140 may then select an image object 404 for submitting the input mobile number to a server 100 illustrated in FIGS. 1 and 2.
  • the server 100 may receive the mobile number of the secondary user 150 from the first electronic device 141.
  • the server 100 for example, a processor 120, may then create and send a secured code, for example, a One-time Password (OTP), to the mobile number of the secondary user 150.
  • OTP One-time Password
  • a second electronic device 151 to which the said mobile number is assigned may receive the OTP from the server 100.
  • the primary user 140 may then input the OTP sent to the second electronic device 151 into a space 405 on the user interface screen 141c, and then select an image object 406 for submitting the input OTP to the server 100.
  • the server 100 may receive the OTP from the first electronic device 141, and check if the OTP received from the first electronic device 141 is the same as the OTP sent to the second electronic device 151. If the OTP received from the first electronic device 141 is the same as the OTP sent to the second electronic device 151, the server 100 may link the account of the secondary user 150 to the digital wallet 160 of the primary user 140.
  • the first electronic device 141 may then display the user interface screen 141d showing that the account of the secondary user 150 is successfully linked to the digital wallet 160 of the primary user 140.
  • FIG. 5 illustrates an exemplary user interface screen 141e displayed by the first electronic device 141 of the primary user 140 showing information about a plurality of secondary users 150 linked to the digital wallet 160 of the primary user 140.
  • the first electronic device 141 may display the user interface screen 141e showing information 408, 409 about each of the plurality of secondary users 150 linked to the digital wallet 160 of the primary user 140.
  • information 408, 409 may include, but is not limited to, a mobile number of each secondary user 150, name of each secondary user 150, a monthly transaction limit for each secondary user 150, and/or each transaction limit for each secondary user 150.
  • the primary user 140 may have a holistic view of the electronic transactions made by different secondary users 150 on the shared digital wallet
  • the first electronic device 141 may further display an image object 410 on the user interface screen 141e, for the primary user 140 to request for another link between the digital wallet 160 of the primary user 140 and an account of another secondary user.
  • FIG. 6 illustrates exemplary user interface screens 141f and 141g displayed by the first electronic device 141 of the primary user 140 showing an unlink process between the digital wallet 160 of the primary user 140 and the account of the secondary user 150.
  • the primary user 140 may select information 409 corresponding to one of the plurality of secondary users 150 from the user interface screen 141e of FIG. 5.
  • the first electronic device 141 may display the user interface screen 141 f showing detailed information about the selected secondary user linked to the digital wallet 160 of the primary user 140.
  • the detailed information may include, but is not limited to, a mobile number of the selected secondary user, a name of the selected secondary user, monthly spends of the selected secondary user, a monthly transaction limit for the selected secondary user, and/or each transaction limit for the selected secondary user.
  • the primary user 140 may display details of the monthly spends.
  • the primary user 140 may select an area 413 where the monthly transaction limit is displayed or an area 414 where the each transaction limit is displayed, to modify the monthly transaction limit or the per transaction limit for the selected secondary user, respectively.
  • the first electronic device 141 may further display information 415 about a history of the electronic transactions made by the selected secondary user using the digital wallet 160.
  • the first electronic device 141 may display an image object 416 for the primary user 140 to request to unlink the account of the selected secondary user from the digital wallet 160 of the primary user 140. If the primary user 140 selects the image object 416, the first electronic device 141 may display the user interface screen 141g. As shown in FIG. 6, the first electronic device 141 may display a pop-up window 417 on the user interface screen 141g for the primary user 140 to confirm the request to unlink.
  • the first electronic device 141 may send the request to unlink the account of the selected secondary user from the digital wallet 160 to the server 100, and then the server 100 may unlink the account of the selected secondary user from the digital wallet 160.
  • FIGS. 7 and 8 illustrate exemplary user interface screens of an electronic device of a secondary user 150 according to various embodiments.
  • the electronic device may include a second electronic device 151 belonging to the secondary user 150.
  • FIG. 7 illustrates exemplary user interface screens 151a - 151b displayed by the second electronic device 151 of the secondary user 150 showing an electronic transaction using a digital wallet 160 linked to an account of the secondary user 150.
  • the second electronic device 151 may display the user interface screen 151a for the secondary user 150 to make the electronic transaction for goods.
  • the second electronic device 151 may display information 419 about the selected goods and/or information 420 about a payment method on the user interface screen 151a.
  • the information 420 about the payment method may show information about a default payment method or a latest payment method.
  • the secondary user 150 may select an image object 421 for payment for the goods, the electronic transaction may be made by the payment method based on the displayed information 420.
  • the second electronic device 151 may display the user interface screen 151b, as shown in FIG. 7.
  • the second electronic device 151 may display a pop-up window 422 showing information about payment method options on the user interface screen 151b. If the secondary user 150 selects an image object 423 for selecting a payment using the digital wallet 160 of the primary user 140 and then selects an image object 424 for payment for the goods, the electronic transaction may be made using the digital wallet 160 of the primary user 140.
  • FIG. 8 illustrates exemplary user interface screens 151c - 15 Id displayed by the second electronic device 151 of the secondary user 150 showing the electronic transaction using the digital wallet 160 linked to the account of the secondary user 150.
  • the second electronic device 151 may display the user interface screen 151c for the secondary user 150 to make the electronic transaction for the goods.
  • the second electronic device 151 may display the information 419 about the selected goods and/or information 420 about the payment method on the user interface screen 151c.
  • the second electronic device 151 may display the user interface screen 15 Id, as shown in FIG. 8.
  • the second electronic device 151 may display a pop-up window 422 showing information about payment method options on the user interface screen 15 Id.
  • the pop-up window 422 may display information about the plurality of digital wallets 160, as the payment method options.
  • the information about the plurality of digital wallets 160 may include, but are not limited to, a name of each primary user 140, a monthly transaction limit assigned by each primary user 140, and/or each transaction limit assigned by each primary user 140. If the secondary user 150 selects an image object 423 for selecting a payment using one of the plurality of digital wallets 160, and then selects an image object 424 for payment for the goods, the electronic transaction may be made using the selected digital wallet.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Finance (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Health & Medical Sciences (AREA)
  • Child & Adolescent Psychology (AREA)
  • General Health & Medical Sciences (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Computer Security & Cryptography (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

Selon divers modes de réalisation, un serveur comprend : une interface de communication configurée pour recevoir une demande d'ajout d'un compte d'un utilisateur secondaire à un portefeuille numérique d'un utilisateur primaire et des informations concernant une ou plusieurs commandes de transaction pour l'utilisateur secondaire en provenance de l'utilisateur primaire ; et un processeur configuré pour créer un identifiant de liaison qui identifie une liaison entre le compte de l'utilisateur secondaire et le portefeuille numérique et stocker les informations concernant les commandes de transaction pour l'utilisateur secondaire relativement à l'identifiant de liaison, et l'interface de communication recevant une demande de transaction à l'aide du portefeuille numérique en provenance de l'utilisateur secondaire, le processeur étant configuré pour dériver l'identifiant de liaison, vérifier les informations concernant les commandes de transaction relatives à l'identifiant de liaison et décider s'il faut autoriser la demande de transaction sur la base des informations concernant les commandes de transaction relatives à l'identifiant de liaison.
PCT/SG2022/050937 2021-12-30 2022-12-28 Serveur et procédé de partage d'un portefeuille numérique pour une transaction électronique WO2023128872A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
SG10202114541V 2021-12-30
SG10202114541V 2021-12-30

Publications (2)

Publication Number Publication Date
WO2023128872A2 true WO2023128872A2 (fr) 2023-07-06
WO2023128872A3 WO2023128872A3 (fr) 2023-10-26

Family

ID=87000409

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SG2022/050937 WO2023128872A2 (fr) 2021-12-30 2022-12-28 Serveur et procédé de partage d'un portefeuille numérique pour une transaction électronique

Country Status (1)

Country Link
WO (1) WO2023128872A2 (fr)

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11599873B2 (en) * 2010-01-08 2023-03-07 Blackhawk Network, Inc. Systems and methods for proxy card and/or wallet redemption card transactions
US20140019352A1 (en) * 2011-02-22 2014-01-16 Visa International Service Association Multi-purpose virtual card transaction apparatuses, methods and systems
WO2013095486A1 (fr) * 2011-12-22 2013-06-27 Intel Corporation Portefeuille électronique multiutilisateurs et gestion de celui-ci
CN107609867A (zh) * 2017-09-28 2018-01-19 山西特信环宇信息技术有限公司 一种基于生物识别技术的电子钱包系统及操作方法
JP7505248B2 (ja) * 2020-05-07 2024-06-25 トヨタ自動車株式会社 情報処理システム、サーバ、およびプログラム

Also Published As

Publication number Publication date
WO2023128872A3 (fr) 2023-10-26

Similar Documents

Publication Publication Date Title
US11587062B1 (en) Mobile wallet for non-tokenized cards
US20230245099A1 (en) Third-party access to secure hardware
US10783517B2 (en) Third-party access to secure hardware
US20170068952A1 (en) System for electronic collection and display of account token usage and association
CN115115363A (zh) 适应性认证处理
US20190087822A1 (en) Systems and methods for onboarding merchants in real-time for payment processing
US20190370787A1 (en) System and methods for sharing a primary account number among cardholders
US10002387B2 (en) Pre-contracted, staged, currency exchange system
US10929822B2 (en) Graphical user interfaces for facilitating end-to-end transactions on computing devices
US20200327589A1 (en) Authorizing a transaction for a restricted item based on user data
US11669814B1 (en) Systems and methods for funds transfers via a federated directory
US20200160323A1 (en) Transaction system with account mapping
US20190197513A1 (en) Real time splitting of payments for travel
US11295297B1 (en) Systems and methods for pushing usable objects and third-party provisioning to a mobile wallet
US11468427B2 (en) Systems and methods for use in contactless communication
US20210248600A1 (en) System and method to secure payment transactions
WO2018125689A1 (fr) Accès de tierce partie à du matériel sécurisé
US20220300948A1 (en) Systems and methods for multiple account proportional transactions
US11790371B1 (en) Dynamic travel profile
US20210174436A1 (en) Single application for two different cards
WO2023128872A2 (fr) Serveur et procédé de partage d'un portefeuille numérique pour une transaction électronique
US20220343704A1 (en) Store channel prestaging and customer interaction
US11669895B1 (en) Digital banker application system
US11880811B2 (en) System and method for generating data transfer recommendations
US11727364B2 (en) Method and system for facilitating scheduled transactions