WO2019059847A1 - Serveur et procédé de gestion de compte - Google Patents

Serveur et procédé de gestion de compte Download PDF

Info

Publication number
WO2019059847A1
WO2019059847A1 PCT/SG2018/050483 SG2018050483W WO2019059847A1 WO 2019059847 A1 WO2019059847 A1 WO 2019059847A1 SG 2018050483 W SG2018050483 W SG 2018050483W WO 2019059847 A1 WO2019059847 A1 WO 2019059847A1
Authority
WO
WIPO (PCT)
Prior art keywords
account
user
server
transaction
relating
Prior art date
Application number
PCT/SG2018/050483
Other languages
English (en)
Inventor
Olaseni ALABEDE
Francis MONTET
Keisha Clark
Original Assignee
Mastercard Labs Kenya Holdings 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 Mastercard Labs Kenya Holdings Pte. Ltd. filed Critical Mastercard Labs Kenya Holdings Pte. Ltd.
Publication of WO2019059847A1 publication Critical patent/WO2019059847A1/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/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/322—Aspects of commerce using mobile devices [M-devices]
    • G06Q20/3223—Realising banking transactions through M-devices
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G06Q20/108—Remote banking, e.g. home banking
    • 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/385—Payment protocols; Details thereof using an alias or single-use codes
    • 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/401—Transaction verification
    • G06Q20/4014—Identity check for transactions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/02—Banking, e.g. interest calculation or account maintenance

Definitions

  • the present invention relates broadly, but not exclusively, to servers and methods for managing an account, especially for a user who does not have a bank account.
  • the servers and methods may be configured to collect information relevant to the customer (e.g., KYC data)
  • a server for managing an account for a user who does not own a bank account comprising:
  • At least one memory including computer program code
  • the at least one memory and the computer program code configured to, with the at least one processor, cause the server at least to: receive, from a user device, information relating to the user; generate the account in response to a verification of the received information;
  • the at least one memory and the computer program code is further configured with the at least one processor to:
  • the at least one memory and the computer program code is further configured with the at least one processor to:
  • the at least one memory and the computer program code is further configured with the at least one processor to:
  • the at least one memory and the computer program code is further configured with the at least one processor to:
  • At least one memory and the computer program code is further configured with the at least one processor to:
  • the at least one memory and the computer program code is further configured with the at least one processor to:
  • the at least one memory and the computer program code is further configured with the at least one processor to:
  • the at least one memory and the computer program code is further configured with the at least one processor to:
  • the at least one memory and the computer program code is further configured with the at least one processor to:
  • the device is the user device.
  • a computer-implemented method for managing an account for a user who does not own a bank account, the account suitable for non-credit transactions comprising: receiving, from a user device, information relating to the user;
  • the method further comprises generating an account identifier identifying the account and the user; and sending, to the user device, the generated account identifier in response to a user input.
  • the method further comprises receiving, from a device transaction details for a transaction between the user and a party, the transaction details indicating the generated account identifier.
  • the method further comprises receiving, from a device, details relating to a party of the transaction relating to thetrans action details.
  • the method further comprises updating, a database, in response to the receipt of the transaction details.
  • the method further comprises receiving, from the user device, a loan request, the loan request including the generated account identifier;
  • the method further comprises:
  • the method further comprises:
  • the method further comprises:
  • the method further comprises:
  • the device is the user device.
  • Figure 1 shows a block diagram of a transaction system 100 within which an account can be managed.
  • Figure 2 shows a flow chart illustrating a computer-implemented method for managing an account according to an example embodiment.
  • Figure 3 shows a schematic diagram of a computer system suitable for use in executing the method depicted in Figure 2.
  • Figure 4 shows an exemplary computing device to realize a server for the payment network server 108 shown in Figure 1.
  • Figures 5A-5D show schematic diagrams illustrating different aspects of the problem to which embodiments of the method and system of the present invention seek to solve.
  • Figure 6 shows typical profiles of a merchant according to an example embodiment.
  • Figures 7A-7B show schematic diagrams illustrating features of the system depicted in Figure 3 according to an example embodiment.
  • Figures 8A-8B show schematic diagrams illustrating the working of the system depicted in Figure 3 according to an example embodiment.
  • Figures 9A-9E show schematic diagrams illustrating a user interface of the system depicted in Figure 3 according to an example embodiment.
  • Figure 10 shows a schematic diagram illustrating a value chain of the system depicted in Figure 3 according to an example embodiment.
  • Figures 11A-11C show schematic diagrams illustrating benefits of the system depicted in Figure 3 according to an example embodiment.
  • Figures 12A-12B show schematic diagrams illustrating the different markets for implementation of the system depicted in Figure 3 according to an example embodiment.
  • Figure 13 shows a table illustrating the differences between similar systems and the system depicted in Figure 3 according to an example embodiment.
  • Figures 14A-14B show tables illustrating various estimated capital expenses of the system depicted in Figure 3 according to an example embodiment.
  • server for performing the operations of the methods.
  • server may be specially constructed for the required purposes, or may comprise a computer or other device selectively activated or reconfigured by a computer program stored in the computer.
  • the algorithms and displays presented herein are not inherently related to any particular computer or other server.
  • Various machines may be used with programs in accordance with the teachings herein.
  • the construction of more specialized server to perform the required method steps may be appropriate.
  • the structure of a computer will appear from the description below.
  • the present specification also implicitly discloses a computer program, in that it would be apparent to the person skilled in the art that the individual steps of the method described herein may be put into effect by computer code.
  • the computer program is not intended to be limited to any particular programming language and implementation thereof. It will be appreciated that a variety of programming languages and coding thereof may be used to implement the teachings of the disclosure contained herein.
  • the computer program is not intended to be limited to any particular control flow. There are many other variants of the computer program, which can use different control flows without departing from the spirit or scope of the invention.
  • the computer readable medium may include storage devices such as magnetic or optical disks, memory chips, or other storage devices suitable for interfacing with a computer.
  • the computer readable medium may also include a hard-wired medium such as exemplified in the Internet system, or wireless medium such as exemplified in the GSM mobile telephone system.
  • the computer program when loaded and executed on such a computer effectively results in a server that implements the steps of the preferred method.
  • 'server' may mean a single computing device or at least a computer network of interconnected computing devices which operate together to perform a particular function.
  • the server may be contained within a single hardware unit or be distributed among several or many different hardware units.
  • a user may refer to one who has an account identifier.
  • the account identifier may be linked to various financial institutions.
  • a user may sign up for a universal account so as to be linked to various financial institutions.
  • the user is also a customer who initiates a transaction with a supplier with whom the user uses an account relating to the account identifier to pay the supplier (or transfer an amount from the account).
  • the user is also a merchant with whom a customer has initiated a transaction to buy good and/or services from the user (or transfer an amount to the account).
  • the transaction is a payment transaction. In other words, effecting the transaction involves a payment between parties to the transaction.
  • FIG 1 illustrates a block diagram of a transaction system 100 within which transaction data can be received.
  • the system 100 comprises a transaction device 102 in communication with a merchant device 104.
  • the merchant device 104 may also be in direct communication with a payment network server 108, without having to communicate with the transaction device 102.
  • the merchant device 104 is in communication with an acquirer server 106.
  • the acquirer server 106 in turn, is in communication with the payment network server 108.
  • the payment network server 108 in turn, is in communication with an issuer server 110.
  • the transaction device 102 typically is associated with a customer (or supplier) who is a party to a transaction that occurs between the transaction device 102 and the merchant device 104 through a transaction.
  • the transaction device 102 may be a fixed (wired) computing device or a wireless (portable) computing device.
  • the transaction device 102 may be a handheld or portable or mobile device carried or used by the customer, or may refer to other types of electronic devices such as a personal computer, a land-line telephone or an interactive voice response (IVR) system and the like.
  • the mobile device may be a device, such as a mobile phone, a laptop computer, a personal digital computer (PDA), a mobile computer, a portable music player (such as an iPodTM and the like).
  • the merchant device 104 typically is associated with the merchant who is also a party to the transaction that occurs between the transaction device 102 and the merchant device 104 through the transaction.
  • the merchant device 104 may be a point-of-sale (POS) terminal, an automatic teller machine (ATM), a personal computer, a computer server (hosting a website, for example), an IVR system, a land-line telephone, or any type of mobile device such as a mobile phone, a personal digital assistant (PDA), a laptop computer, a tablet computer and the like.
  • POS point-of-sale
  • ATM automatic teller machine
  • PDA personal digital assistant
  • the acquirer server 106 generally is associated with an acquirer who may be an entity (e.g. a company or organization) which issues (e.g. establishes, manages, administers) a transaction credential or an account (e.g. a financial bank account). Examples of the acquirer include a bank and/or other financial institution (or lender). As stated in the above, the acquirer server 106 may include one or more computing devices that are used to establish communication with another server by exchanging messages with and/or passing information to the other server. In various embodiments below, the acquirer may be known as a financial institution referring to one who may loan funds to a merchant and the acquirer server 106 may be an other server.
  • the payment network server 108 typically is associated with a payment facilitator.
  • the payment network server 108 may be the Banknet® network operated by MasterCard®.
  • the payment facilitator e.g. MasterCard®
  • the payment facilitator may be an entity (e.g. a company or organization) who operates to process transactions, clear and settle funds for payments between two entities (e.g. two banks).
  • the payment network server 108 may include one or more computing devices that are used for processing transactions.
  • the payment facilitator e.g. MasterCard®
  • the payment facilitator may be an entity (e.g. a company or organization) which issues (e.g. establishes, manages, administers) a transaction credential or an account (e.g. a financial bank account) of the merchant.
  • the issuer server 110 generally is associated with an issuer and may include one or more computing devices that are used to perform a payment transaction.
  • the issuer may be an entity (e.g. a company or organization) which issues (e.g. establishes, manages, administers) a transaction credential or an account (e.g. a financial bank account).
  • An account may be associated with a plurality of transaction devices 102.
  • the acquirer may be known as a financial institution referring to one who may loan funds to a merchant and the acquirer server 106 may be another server.
  • the payment network server 108 may be configured to communicate with, or may include, a database (or a transaction database) 109.
  • the transaction database 109 stores data corresponding to a transaction (or transaction data). Examples of the data include Transaction ID, Merchant ID, Merchant Name, MCC / Industry Code, Industry Description, Merchant Country, Merchant Address, Merchant Postal Code, Aggregate Merchant ID and or other relevant information that is provided when the merchant signs up for an application program as a user. For example, data (“Merchant name" or "Merchant ID”) relating to the merchant, time and date for which the goods/ services relating to the transaction will be delivered are included in the database 109.
  • the database 109 may include a reliability score for each merchant (or user of an application program) indicating how reliable the user is.
  • One of the criteria to determine how reliable the user is whether or not the user has settled the transactions within a predetermined time period based on the timestamp indicating a time at which a payment for a loan is made. For example, if the merchant has paid an amount required to satisfy a loan repayment scheme.
  • the transaction device 102 is capable of wireless communication using a suitable protocol with the merchant device 104.
  • embodiments may be implemented using transaction devices 102 that are capable of communicating with Wi-Fi / Bluetooth- enabled merchant devices 104. It will be appreciated by a person skilled in the art that depending on the wireless communication protocol used, appropriate handshaking procedures may need to be carried out to establish communication between the transaction device 102 and the merchant device 104. For example, in the case of Bluetooth communication, discovery and pairing of the transaction device 102 and the merchant device 104 may be carried out to establish communication.
  • a transaction request message 112 is generated at the transaction device 102.
  • the transaction request message 112 is generated by the transaction device 102 in response to the customer (or a party) making a selection of a good and/or service to be purchased from the merchant.
  • the transaction request message 112 relates to a transaction between the customer and the merchant.
  • the transaction may be performed at a retail shop of the merchant.
  • the transaction device 102 may be fitted with a wireless communications interface such as a Near Field Communication (NFC) interface to enable the transaction device 102 to electronically communicate with the merchant device 104 to perform the transaction.
  • NFC is a set of standards to establish radio communication between devices by bringing them into close proximity such as only a few centimetres.
  • NFC standards cover communication protocols and data exchange formats, and are based on radio-frequency identification (RFID) technology. That is, the transaction device 102 may have image capturing capabilities and capture an image of a quick response (QR) code displayed on the merchant device 104.
  • the captured QR code includes an account identifier identifying the merchant and the merchant's account.
  • the merchant registers for an account on an application program executing on the merchant device.
  • the application program is one that is managed by the payment network server 108.
  • the merchant provides his information (e.g., name, a photograph, place of birth, contact number and date of birth) to the payment network server 108.
  • the payment network server 108 may verify the information which may be in a form of checking if the received information is complete or check if the received information corresponds to a user in a black-list.
  • the blacklist listing users with undesirable records who should not be permitted to register for an account.
  • the payment network server 108 may generate an account in response to a verification of the received information.
  • An account identifier will also be generated in response to a generation of the account.
  • the account identifier may include some or all of the information relating to the user and the user account, and may be saved in the database 109.
  • the account identifier refers to a number of digits (or characters) which identify a universal account issued by an institution (for example, MasterCardTM).
  • an account is linked to an account which is issued by an issuer pursuant to the MasterCard International Incorporated rules, and the account identifier may be a twelve to nineteen-digit string that identifies both the issuer (which may be based on the first few digits of the string, for example, the first five to ten digits) and the client account at the issuer.
  • the account identifier may also identify if the issuer is subscribed to a standardized Internet transaction protocols such as 3-D SecureTM Network.
  • the 3-D SecureTM Network is consistent with and underlies the authentication programs offered by card issuers (for example, SecureCodeTM by MasterCard) to authenticate client for merchant during a remote transaction such as those done over the Internet.
  • card issuers for example, SecureCodeTM by MasterCard
  • the account identifier is typically utilized to route and process transactions that involve the account or those it is linked to.
  • each transaction data relates to a transaction and identifies the party ( a customer or a supplier) and the merchant, generally by way of identifiers of each associated with the user and merchant respectively.
  • the transaction data may also identify the good and/or service to be purchased and a type or nature of the transaction.
  • the transaction data may further identify a value or price of the good and/or service (e.g., a transaction amount) and a location where the good and/or service will be delivered.
  • the transaction data may also indicate a time and date at which the transaction was initiated by the user.
  • the transaction data may also include inputs that are manually entered by the user (or a merchant) in response to a receipt of a non-credit amount.
  • the payment network server 108 is configured to process a request to sign up for the account and send a notification message to the merchant device 104 once it is determined that the account is set up.
  • the merchant device 104 may receive a short messaging service message to inform him about his account identifier.
  • the role of the payment network server 108 is to facilitate communication between the merchant device 104 and/or acquirer server 106, the issuer server 110(a) and/or the issuer server 110(b). Therefore, the payment network server 108 may serve as a means through which the merchant device 104 may communicate with a financial institution in a manner that requests and loans may be accepted and forwarded.
  • the payment network server 108 is further configured to perform additional operations.
  • the payment network server 108 may be configured to update the database 109 whenever a merchant registers for an account or pays his loans.
  • the payment network server 108 may also be configured to calculate a reliability score for each user based on the historical transactions (including repayment of loans) relating to the user.
  • the historical transactions may be a ledger or a record of transactions that have been carried out using the account.
  • Such a server may be used to implement the method 200 shown in Fig. 2.
  • Fig. 2 shows a flowchart illustrating a method 200 for managing an account with embodiments of the invention.
  • the method 200 can be used to the user to at least a financial institution. For various embodiments below, pairing of a user with an at least a financial institution with whom the user does not have an account.
  • the method 200 broadly includes:
  • step 202 receiving, from a user device, information relating to the user step 204: generating the account in response to a verification of the received information; step 206: sending, to the user device, details relating to the generated account, the generated account being to be used for amount to be transacted.
  • the method 200 may be performed by one or more purpose-built computing devices, such as the payment network server 108 that is coupled to one or more databases.
  • a request to sign up for an account may be initiated by a merchant and information relating to the user may be received.
  • the information may be at least one of a name, date of birth, place of birth and contact number of the merchant.
  • the account is generated in response to a verification of the received information. This may be a simple verification by checking if all the fields necessary for registration have been filled in. In other embodiments, the payment network server 108 may do a check with a database to confirm if the information is factual and accurate.
  • step 206 details relating to the generated account will be sent to the user device.
  • the generated account being one that can be used for transactions.
  • an account identifier is also generated, identifying the account and the user.
  • the account identifier is a QR code, including details of the account.
  • the account identifier may then be sent to the user device.
  • the QR code may be a static or a dynamic QR code.
  • a party a customer or a supplier
  • a transaction may be able to scan the QR code.
  • a mobile device e.g., a smartphone
  • it is possible for him to enter the details relating to the account e.g., via USSD
  • the method comprise receiving, from a device, transaction details for a cash transaction between the user and a party, the transaction details indicating the generated account identifier.
  • the device may be a user device or a device of the party (customer or a supplier).
  • the method comprises updating, a database, in response to the receipt of the transaction details.
  • the method comprises receiving, from the user device, a loan request, the loan request including the generated account identifier; retrieving, from the database, historical transaction details relating to historical transactions that have been completed relating to the generated account identifier over a predetermined period of time; and facilitating the loan request in response to a determination if the historical transactions satisfy a predetermined criteria.
  • the method comprises determining if the user has carry out a predetermined number of transactions within a predetermined period of time (e.g., a month) which is an indication of the user's situation.
  • the method comprises forwarding, to another server, the loan request, the other server relating to a financial institution indicated in the loan request.
  • the financial institution being one who subscribes to the service too.
  • the method comprises receiving, from the other server, a loan approval message informing that the loan request has been approved by the financial institution.
  • a loan approval message informing that the loan request has been approved by the financial institution.
  • an amount indicated in the loan request will be forwarded to the user.
  • the method may include receiving, from the user device, an amount indicated in the loan request; and updating, the database, with a timestamp indicating the time at which the amount is received.
  • the method comprises generating a reliability score for the user in response to the updated timestamp.
  • the method may comprise determining if the reliability score is equal to or more than an issuer threshold score indicated in a corresponding issuer registration.
  • the user is presented to the issuer if it is determined that the reliability score of the user is equal to or more than the issuer threshold score. In other words, the issuer is willing to process a loan transaction with the user.
  • Figure 3 depicts an exemplary computer / computing device 300, hereinafter interchangeably referred to as a computer system 300, where one or more such computing devices 300 may be used to facilitate execution of the above-described method.
  • one or more components of the computer system 300 may be used to realize the computer 302.
  • the following description of the computing device 300 is provided by way of example only and is not intended to be limiting.
  • the example computing device 300 includes a processor 304 for executing software routines. Although a single processor is shown for the sake of clarity, the computing device 300 may also include a multi-processor system.
  • the processor 304 is connected to a communication infrastructure 306 for communication with other components of the computing device 400.
  • the communication infrastructure 306 may include, for example, a communications bus, cross-bar, or network.
  • the computing device 300 further includes a main memory 308, such as a random access memory (RAM), and a secondary memory 310.
  • the secondary memory 310 may include, for example, a storage drive 312, which may be a hard disk drive, a solid state drive or a hybrid drive and/or a removable storage drive 314, which may include a magnetic tape drive, an optical disk drive, a solid state storage drive (such as a USB flash drive, a flash memory device, a solid state drive or a memory card), or the like.
  • the removable storage drive 314 reads from and/or writes to a removable storage medium 344 in a well-known manner.
  • the removable storage medium 344 may include magnetic tape, optical disk, nonvolatile memory storage medium, or the like, which is read by and written to by removable storage drive 314.
  • the removable storage medium 344 includes a computer readable storage medium having stored therein computer executable program code instructions and/or data.
  • the secondary memory 310 may additionally or alternatively include other similar means for allowing computer programs or other instructions to be loaded into the computing device 300.
  • Such means can include, for example, a removable storage unit 322 and an interface 340.
  • a removable storage unit 322 and interface 340 include a program cartridge and cartridge interface (such as that found in video game console devices), a removable memory chip (such as an EPROM or PROM) and associated socket, a removable solid state storage drive (such as a USB flash drive, a flash memory device, a solid state drive or a memory card), and other removable storage units 322 and interfaces 340 which allow software and data to be transferred from the removable storage unit 322 to the computer system 300.
  • the computing device 300 also includes at least one communication interface 324.
  • the communication interface 324 allows software and data to be transferred between computing device 300 and external devices via a communication path 326.
  • the communication interface 324 permits data to be transferred between the computing device 300 and a data communication network, such as a public data or private data communication network.
  • the communication interface 324 may be used to exchange data between different computing devices 300 which such computing devices 300 form part an interconnected computer network. Examples of a communication interface 324 can include a modem, a network interface (such as an Ethernet card), a communication port (such as a serial, parallel, printer, GPIB, IEEE 1394, RJ25, USB), an antenna with associated circuitry and the like.
  • the communication interface 324 may be wired or may be wireless.
  • Software and data transferred via the communication interface 324 are in the form of signals which can be electronic, electromagnetic, optical or other signals capable of being received by communication interface 324. These signals are provided to the communication interface via the communication path 326.
  • the computing device 300 further includes a display interface 302 which performs operations for rendering images to an associated display 330 and an audio interface 332 for performing operations for playing audio content via associated speaker(s) 334.
  • computer program product may refer, in part, to removable storage medium 344, removable storage unit 322, a hard disk installed in storage drive 312, or a carrier wave carrying software over communication path 326 (wireless link or cable) to communication interface 324.
  • Computer readable storage media refers to any non-transitory, non-volatile tangible storage medium that provides recorded instructions and/or data to the computing device 300 for execution and/or processing.
  • Examples of such storage media include magnetic tape, CD-ROM, DVD, Blu-rayTM Disc, a hard disk drive, a ROM or integrated circuit, a solid state storage drive (such as a USB flash drive, a flash memory device, a solid state drive or a memory card), a hybrid drive, a magneto -optical disk, or a computer readable card such as a SD card and the like, whether or not such devices are internal or external of the computing device 300.
  • a solid state storage drive such as a USB flash drive, a flash memory device, a solid state drive or a memory card
  • a hybrid drive such as a magneto -optical disk
  • a computer readable card such as a SD card and the like
  • Examples of transitory or non-tangible computer readable transmission media that may also participate in the provision of software, application programs, instructions and/or data to the computing device 300 include radio or infra-red transmission channels as well as a network connection to another computer or networked device, and the Internet or Intranets including e-mail transmissions and information recorded on Websites and the like.
  • the computer programs are stored in main memory 308 and/or secondary memory 310. Computer programs can also be received via the communication interface 324. Such computer programs, when executed, enable the computing device 300 to perform one or more features of embodiments discussed herein. In various embodiments, the computer programs, when executed, enable the processor 304 to perform features of the above-described embodiments. Accordingly, such computer programs represent controllers of the computer system 300.
  • Software may be stored in a computer program product and loaded into the computing device 400 using the removable storage drive 314, the storage drive 312, or the interface 340.
  • the computer program product may be downloaded to the computer system 300 over the communications path 326.
  • the software when executed by the processor 304, causes the computing device 300 to perform functions of embodiments described herein.
  • FIG. 3 It is to be understood that the embodiment of Figure 3 is presented merely by way of example. Therefore, in some embodiments one or more features of the computing device 300 may be omitted. Also, in some embodiments, one or more features of the computing device 300 may be combined together. Additionally, in some embodiments, one or more features of the computing device 300 may be split into one or more component parts.
  • the payment network server 108 may be generally described as a physical device comprising at least one processor 402 and at least one memory 404 including computer program code.
  • the at least one memory 404 and the computer program code are configured to, with the at least one processor 402, cause the physical device to perform the operations described in Figure 2.
  • An example of the payment network server 108 is shown in Figure 4.
  • the method of Figure 2 may be implemented as software and stored in a non-transitory fashion in the secondary memory 310 or the removable storage units 318, 322 of the computer device 300.
  • Figures 5A-5D show schematic diagrams illustrating different aspects of the problem to which embodiments of the method and system of the present invention seek to solve.
  • Figure 5A identifies that micro -merchants and micro small and medium enterprises (MSMEs), for example a grocery store owner or a food seller, who do not have adequate information and collateral to be able to obtain financial services from financial institutions.
  • MSMEs micro small and medium enterprises
  • Figures 5B, 5C and 5D further illustrate the breakdown of the number of such merchants and SMEs who are excluded from financial services.
  • Figure 6 shows typical profiles of a merchant according to an example embodiment.
  • an example of a typical micro merchant or MSME is Usman, who is a trader and Wanjiru, who is a farmer. Both are typical micro merchants who do not have a bank account and wishes to obtain a loan or subsidies from their respective Government and financial institutions.
  • Figures 7A-7B show schematic diagrams illustrating features of the system depicted in Figure 3 according to an example embodiment.
  • features of the system includes creating an identity profile, capturing and authenticating biometric data, building transaction history for alternative credit decision, making and receiving payments, providing insight, decision support and managing MSME profile information.
  • the system may create a plurality of identity profiles, capture and authenticate biometric data, identify and store a national identity, build transaction history, receive transactions, provide insight, decision support, managing MSME profile information and assist in decision making.
  • Figures 8A-8B show schematic diagrams illustrating the working of the system depicted in Figure 3 according to an example embodiment.
  • the system includes a server comprising an iDentify.me module, a mobile identity check module (IDCM), a payment transaction services module for virtual card number and a quick response payment module.
  • unions such as farmers union or traders union
  • agents such as farmers union or traders union
  • banks and peer-to-peer lenders may be on-boarded onto the system.
  • the system may be delivered to 28.5 million micro-merchants by partnering with Aggregators and Trade Unions. Aggregators will provide biometric know-your-customer details, virtual card numbers and quick response payment to receive payments and a ledger for transaction history.
  • the transaction history will be monetized whenever a lender queries the history in order to determine whether to lend money to the merchant or trader.
  • Figures 9A-9E show schematic diagrams illustrating a user interface of the system depicted in Figure 3 according to an example embodiment.
  • the user interface includes a picture of the merchant which may be a selfie taken by the merchant's user device, such as a mobile phone. The selfie may be taken by blinking at the camera of the user device.
  • the user interface may also include the name, place of birth, mobile number and a date of birth of the merchant. Additional details will include an ID number of the merchant if one exists and also a photo of the official document that has the ID.
  • the user device may display a welcome message to congratulate the merchant and to indicate that the merchant has a virtual walled and a quick response (QR) code to enable him to do better business as shown in Figure 9B.
  • the user interface may also include options for the merchant to display the virtual wallet QR code or to request a business loan.
  • the user interface shows the QR code on the merchant's user device together with his virtual wallet account number.
  • the user interface may indicate whether he has been approved for the loan.
  • the user interface may display the total monetary amount of the transactions as shown in Figure 9D.
  • the user interface may also indicate to the merchant that he is eligible to qualify for a loan based on the total monetary amount of the transactions.
  • the user device may not have a camera or touchscreen.
  • the user interface may include numbers for the various options to be selected by the merchant. For example, the merchant may want to view his profile by pressing the " 1" on the number- pad of his device. Other options may include receiving payments, making payments, finding a lender and/or request for assistance with the application.
  • the user interface may request the merchant to enter a virtual wallet merchant code of the supplier. Subsequently, the user interface may request the merchant to enter the amount he wishes to pay and after payment has been made, the user interface displays the profile of the merchant indicating his name, date of birth, place of birth, a monetary amount of the last transaction and any loan payments that have been made.
  • Figure 10 shows a schematic diagram illustrating a value chain of the system depicted in Figure 3 according to an example embodiment.
  • the value chain includes a card network of the system, for example MasterCard, and the parties involved in the system.
  • the parties may include MSMEs, partner banks, aggregators and lenders.
  • Figures 11A-11C show schematic diagrams illustrating benefits of the system depicted in Figure 3 according to an example embodiment.
  • the system may generate revenues of $481 million over a seven year period. This includes a profile residency fee of $62 million from the MSMEs, a transaction history check fee of $174 million, an authentication fee of $8.7 million for mobile identity check, a transaction switching fee of $62 million, a virtual card number payment transaction service and transaction processing fee of $87 million and an issuer/acquirer assessment fee of $87 million.
  • the table of Figure 11B shows the details of the various fees contributing to the revenue and its respective models, rates and duration.
  • Figure 11C show the various monetary amount of the revenue over a five year period and further illustrated using a chart.
  • Figures 12A-12B show schematic diagrams illustrating the different markets for implementation of the system depicted in Figure 3 according to an example embodiment.
  • the system may be implemented in sub Saharan Africa and Southern Africa in the first year. In the second year, the system may be implemented in North Africa and Middle East. In the third year and beyond, the system may be implemented in Asia, South East Asia and Latin America.
  • the system may be implemented in Africa (including West Africa, East Africa, Southern Africa and North Africa) in the first two years. The system may then be implemented in Middle East and South East Asia in the second to fourth year. Subsequently, the system may be implemented in Latin America and Asia from the fifth year onwards.
  • Figure 13 shows a table illustrating the differences between similar systems and the system depicted in Figure 3 according to an example embodiment.
  • the table of Figure 13 shows the advantages of the system implemented by the card network, i.e. MasterCard, against various other systems such as Kiva and Kopo Kopo. It can be seen from the Figure that the system does not require underwriting which may save time and costs and also includes reference check of the merchant to minimize risk.
  • Figures 14A-14B show tables illustrating various estimated capital expenses of the system depicted in Figure 3 according to an example embodiment.
  • various estimations for the required capital expenses are provided over a five year period and the various existing systems of the card network provider are used for the implementation of the current system.

Landscapes

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

Abstract

Selon un aspect, l'invention concerne un serveur de gestion d'un compte destiné à un utilisateur ne possédant pas de compte bancaire, le compte étant approprié pour des transactions en espèces sans crédit. Le serveur comprend : au moins un processeur; et au moins une mémoire contenant un code de programme informatique. Ladite au moins une mémoire et le code de programme informatique sont configurés pour, avec ledit au moins un processeur, amener au moins le serveur à : recevoir d'un dispositif utilisateur des informations relatives à l'utilisateur; générer le compte en réponse à une vérification des informations reçues; et envoyer au dispositif utilisateur des coordonnées relatives au compte généré, le compte généré étant destiné à être utilisé pour un montant en espèces devant faire l'objet d'une transaction.
PCT/SG2018/050483 2017-09-21 2018-09-21 Serveur et procédé de gestion de compte WO2019059847A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KE0273617 2017-09-21
KEKE/P/2017/002736 2017-09-21

Publications (1)

Publication Number Publication Date
WO2019059847A1 true WO2019059847A1 (fr) 2019-03-28

Family

ID=65809921

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SG2018/050483 WO2019059847A1 (fr) 2017-09-21 2018-09-21 Serveur et procédé de gestion de compte

Country Status (1)

Country Link
WO (1) WO2019059847A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7097487B1 (ja) 2021-09-09 2022-07-07 ＰａｙＰａｙ株式会社 電子決済システム、電子決済方法、およびプログラム

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120191596A1 (en) * 2011-01-26 2012-07-26 Gary Kremen Evaluating, monitoring, and controlling financial risks using stability scoring of information received from social networks and other qualified accounts
US20120310824A1 (en) * 2011-06-03 2012-12-06 Liberty Michael A Monetary transaction system
US20140310153A1 (en) * 2013-04-12 2014-10-16 Ebay Inc. Systems and methods for mobile device financing
CN105550928A (zh) * 2015-12-03 2016-05-04 城市商业银行资金清算中心 一种商业银行网络远程开户的系统及其方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120191596A1 (en) * 2011-01-26 2012-07-26 Gary Kremen Evaluating, monitoring, and controlling financial risks using stability scoring of information received from social networks and other qualified accounts
US20120310824A1 (en) * 2011-06-03 2012-12-06 Liberty Michael A Monetary transaction system
US20140310153A1 (en) * 2013-04-12 2014-10-16 Ebay Inc. Systems and methods for mobile device financing
CN105550928A (zh) * 2015-12-03 2016-05-04 城市商业银行资金清算中心 一种商业银行网络远程开户的系统及其方法

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7097487B1 (ja) 2021-09-09 2022-07-07 ＰａｙＰａｙ株式会社 電子決済システム、電子決済方法、およびプログラム
JP2023039762A (ja) * 2021-09-09 2023-03-22 ＰａｙＰａｙ株式会社 電子決済システム、電子決済方法、およびプログラム

Similar Documents

Publication Publication Date Title
US8589293B2 (en) Message routing using logically independent recipient identifiers
US10832533B2 (en) Receipt processing and access service
US20100274720A1 (en) Fraud and reputation protection using advanced authorization and rules engine
US20170193515A1 (en) Method for determining if a current wallet-based transaction initiated by a digital wallet user is fraudulent
US20130226682A1 (en) Person-to-person transaction identification of coupons and loyalty cards
US20100241535A1 (en) Account activity alert
MX2013000603A (es) Servicio de acceso a sistema de transferencia de dinero.
US20120173402A1 (en) Stored value exchange method and apparatus
US20190354978A1 (en) Server and method for managing an authorization amount over a plurality of payments
WO2017209831A1 (fr) Procédé et système de traitement efficace de transactions partagées
US20220318866A1 (en) Payment system and method
US20160012480A1 (en) Targeted Electronic Commerce Based on Historical Purchasing Data
US11244335B2 (en) Server and method for determining if an account in a transaction request is eligible for a promotion
US10817900B2 (en) Method and apparatus for determining an effectiveness of an electronic advertisement
WO2019059847A1 (fr) Serveur et procédé de gestion de compte
WO2021155693A1 (fr) Procédé et système de traitement de transaction
US20190325438A1 (en) System and method for completing a transaction initiated at a payment terminal
US11062322B2 (en) Server and method for hosting a ledger
US20190318325A1 (en) Server and method for sending a transaction receipt via a push notification
US11568381B2 (en) Apparatus and method for dynamic user/issuer pairing
US20190180339A1 (en) Server and method for managing a user pairing
US20170060875A1 (en) Method for customising a travel itinerary
US20160012425A1 (en) Systems and Methods for Processing Transactions Between Customers and Merchants
US20190180348A1 (en) Methods and systems for processing a transaction request
JOSE et al. Digital Wallets: Impact on the economy with reference to youth in Ernakulam city

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18857660

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18857660

Country of ref document: EP

Kind code of ref document: A1