[go: up one dir, main page]

WO2016028167A1 - Procédé et appareil pour faciliter des paiements - Google Patents

Procédé et appareil pour faciliter des paiements Download PDF

Info

Publication number
WO2016028167A1
WO2016028167A1 PCT/NZ2015/050112 NZ2015050112W WO2016028167A1 WO 2016028167 A1 WO2016028167 A1 WO 2016028167A1 NZ 2015050112 W NZ2015050112 W NZ 2015050112W WO 2016028167 A1 WO2016028167 A1 WO 2016028167A1
Authority
WO
WIPO (PCT)
Prior art keywords
payment
payee
financial institution
code
controller
Prior art date
Application number
PCT/NZ2015/050112
Other languages
English (en)
Inventor
Bradley Joel MILNE
Original Assignee
Kaching Payments Limited
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 Kaching Payments Limited filed Critical Kaching Payments Limited
Publication of WO2016028167A1 publication Critical patent/WO2016028167A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/227—Payment schemes or models characterised in that multiple accounts are available, e.g. to the payer
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • G06Q20/027—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP] involving a payment switch or gateway
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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

Definitions

  • the invention relates to a method and apparatus for facilitating payments from a plurality of payers to a plurality of payees.
  • the invention relates to a method and apparatus for monitoring financial institution accounts for receipt of payments identified with a payment code, notifying the payee of the payment and transferring the payment into the payee's account.
  • a method for facilitating payments from a plurality of payers to a plurality of payees by a controller including the steps of the controller:
  • the notification is immediate.
  • the payment code includes a transaction code.
  • the payment code includes a merchant code.
  • the payment code includes a third party code.
  • the third party code is an online sale identifier.
  • the payment code is a transaction code.
  • the payment code is a merchant code.
  • the payment code is a third party code.
  • the third party code is an online sale identifier.
  • At least one of the plural ity of financial institution accounts is registered as a pre- registered payee.
  • the controller pre-registers at least one payee with at least two financial institutions.
  • the controller automates payee financial institution account verification.
  • the controller sends notification to the payee along with an identifier.
  • the controller using financial institution provided electronic systems transfers the payment to the payee financial institution account after a predetermined time period.
  • controller using financial institution provided electronic systems transfers the payment to the payee financial institution account immediately after notifying the payee that payment has been received.
  • the controller uses the payment amount to aid identification of the payee.
  • the controller for at least one payee aggregates payments having a payment code associated with the payee and pays using financial institution provided systems the aggregated amount to the payee financial institution account.
  • the controller notifies the payee by a communication method selected from one or more of the group consisting of email, mobile application, point of sale device, text message and automated telephone cal ls.
  • the payer financial institution account and the payee financial institution account are at different financial institutions.
  • the controller using financial institution provided electronic systems transfers the payment in a different currency from the currency in which the payment is received.
  • the controller further receives a request from a payee for a payment code to be associated with a payee, generates the payment code and associates the payment code with the payee.
  • the generated payment code is associated with a single payment and the payment code is retired once the payment has been received.
  • the request for a payment code includes the amount of the payment to be made using the generated code and wherein the controller stores the amount of the expected payment in association with the payment code.
  • payment includes payment in currency and currency includes virtual currency.
  • a memory coupled to the processor and capable of storing data, wherein the processor is configured to:
  • the notification is immediate.
  • the payment code includes a transaction code.
  • the payment code includes a merchant code.
  • the payment code includes a third party code.
  • the third party code is an online sale identifier.
  • the payment code is a transaction code.
  • the payment code is a merchant code.
  • the payment code is a third party code.
  • the third party code is an online sale identifier.
  • At least one of the pl urality of financial institution accounts is registered as a pre-registered payee.
  • the processor is further configured to pre-register at least one payee with at least two financial institutions.
  • the processor is further configured to automate payee financial institution account verification.
  • the processor is further configured to send notification to the payee along with an identifier.
  • the processor is further configured to transfer using financial institution provided electronic systems, the identified payment to the payee financial institution account after a predetermined time period.
  • the processor is further configured to transfer using financial institution provided electronic systems, the identified payment to the payee financial institution account immediately after notifying the payee that the identified payment has been received.
  • the processor is further configured to use the payment amount to aid identification of the payee.
  • the processor is further configured to, for at least one payee to aggregate payments having a payment code associated with the payee and pay using financial institution provided electronic systems the aggregated amount to the payee financial institution account.
  • the processor is further configured to notify the payee by a communication method selected from one or more of the group consisting of email, mobile application, point of sale device, text message and automated telephone calls.
  • payment is received from a payer financial institution account at the same financial institution as the monitored financial institution account that receives the payment.
  • the payer financial institution account and the payee financial institution account are at different financial institutions.
  • the processor is further configured to, using financial institution provided electronic systems transfer the payment in a different currency from the currency in which the payment is received.
  • the processor is further configured to receive a request from a payee for a payment code to be associated with a payee, generates the payment code and associates the payment code with the payee.
  • the generated payment code is associated with a single payment and the payment code is retired once the payment has been received.
  • the request for a payment code includes the amount of the payment to be made using the generated code and wherein the processor is further configured to store the amount of the expected payment in association with the payment code.
  • payment includes payment in currency and currency includes virtual currency.
  • currency includes virtual currency.
  • the terms “comprise”, “comprises” and “comprising” may, under varying jurisdictions, be attributed with either an exclusive or an inclusive meaning. For the purpose of this specification, and unless otherwise noted, these terms are intended to have an inclusive meaning - i.e. they will be taken to mean an incl usion of the listed components which the use directly references, and possibly also of other non-specified components or elements.
  • Figure 1 shows a flow diagram of a method for faci litating payments according to the present invention
  • Figure 2 shows a process diagram of the method of Figure 1 ;
  • Figure 3 shows the application architecture of an embodiment of the present invention
  • Figure 4 shows a process diagram of transaction code generation according to an embodiment of the present invention
  • Figure 5 shows a process diagram of transaction code usage according to an embodiment of the present invention
  • Figure 6 shows a flow diagram a method for facilitating payments according to the present invention, including integration with a payee's point of sale system;
  • Figure 7 shows an embodiment of the method of Figure 6
  • Figure 8 shows another embodiment of the method of Figure 6
  • Figure 9 shows an embodiment of a method for facilitating payments according to the present invention, including integration with a vending machine.
  • Figure 10 shows a block diagram of an apparatus according to the present invention.
  • the present invention is for facilitating payments from consumer payers to merchant payees.
  • this invention is suited to situations in which the payee is not able to, or does not wish to allow card-based payments, and the payer does not have cash on hand.
  • the present invention allows payees to be instantly notified when payers have successfully made payments into intermediate accounts, prior to actually receiving the money in the payees' own accounts.
  • the controller, system or apparatus of the present invention includes at least a processor 101 , one or more memory devices 102 or an interface for connection to one or more memory devices, input and output interfaces for connection to external devices in order to enable the system to receive and operate upon instructions from one or more users or external systems, a data bus for internal and external communications between the various components, and a suitable power supply.
  • the controller may include one or more communication devices 103 (wired or wireless) for communicating with external and internal devices, and one or more input/output devices, such as a display, pointing device, keyboard or printing device.
  • the controller may have access to a data store 102 including but not limited to a database.
  • Processor includes single and multi-cored processors and is to be understood to include multiple processors.
  • the processor 101 is arranged to perform the steps of a program stored as program instructions within the memory device.
  • the program instructions enable the various methods of performing the invention as described herein to be performed.
  • the program instructions may be developed or implemented using any suitable software programming language and toolkit, such as, for example, a C-based language.
  • the program instructions may be stored in any suitable manner such that they can be transferred to the memory device or read by the processor, such as, for example, being stored on a computer readable medium.
  • the computer readable medium may be any suitable medium, such as, for example, solid state memory, magnetic tape, a compact disc (CD-ROM or CD-R/W), memory card, flash memory, optical disc, magnetic disc or any other suitable computer readable medium.
  • the system is arranged to be in communication with external data storage systems, transactions systems or devices in order to retrieve the relevant data and carry out the relevant transactions.
  • system herein described includes one or more elements that are arranged to perform the various functions and methods as described.
  • the description is aimed at providing the reader with an example of a conceptual view of how various modules and/or engines that make up the elements of the system may be interconnected to enable the functions to be implemented. Further, the following portion of the description explains in system related detail how the steps of the described method may be performed.
  • the conceptual diagrams are provided to indicate to the reader how the various data elements are processed at different stages by the various different modules and/or engines.
  • a financial institution means an institution that provides financial services for its clients.
  • Financial institutions include depositary institutions that accept and manage monetary deposits, including but not limited to banks, credit units, trust companies and mortgage loan companies.
  • a financial institution may include one or more branches falling under the same financial institution. The branches collectively forming the financial institution.
  • the following are examples of financial institutions operating in New Zealand: ASB Bank Limited, Kiwibank Limited and Bank of New Zealand.
  • a "financial institution account” refers to an account at a financial institution.
  • the financial institution account may be a cheque, savings, credit or any other type of account offered by a financial institution.
  • accounts are represented by account numbers, which identify the financial institution, the branch of the financial institution, and a number associated with the beneficiary of the account, followed by a suffix indicating a specific account belonging to the beneficiary.
  • the suffix may indicate the type of account e.g. cheque or savings.
  • Account numbers are used to make and track payments between different accounts either within the same financial institution, or between different financial institutions.
  • payee financial institution accounts belong to the payees.
  • the present invention is for facilitating payments into these payee financial institution accounts.
  • a payee or merchant registers with a controller 12 in advance of receiving payments.
  • the control ler's administration web server 1 3 handles payee registration.
  • the controller 12 associates with each payee information on a payee financial institution account and at least one payment code.
  • the controller 12 may also associate various communication channels as detailed below with the various payees.
  • the information on a payee financial institution account includes any information that enables the controller 12 to enact a payment into the financial institution account. In most circumstances, this information will consist of or incl ude an account number.
  • the step of associating with each payee information on a payee financial institution account and at least one payment code may be fully or partially automated by the controller 12.
  • a payee may fill in an online form to sign-up for a service implementing the present invention.
  • a controller 12 may then automatically generate a payment code for example a merchant code which is l inked to the payee's financial institution account and provide this payment code to the payee.
  • Financial institution accounts, payment accounts, and the associations between these are stored in a database 1 1 associated with the controller 12.
  • the controller 12 may automate verification of the payee financial institution account. For example, the controller 12 may attempt to make a nominal payment, with a check payment code into the payee financial institution account provided by the payee, to confirm account number validity and ownership. The payee can then confirm ownership of their account by providing the check payment code to the controller 12, preferably via a web interface 1 3.
  • a payment code is any code which identifies a particular payment.
  • the payment code may represent a transaction code, merchant code, third party code, and/or an online sale identifier or any combination thereof.
  • the controller 12 receives a request from a payee for a payment code to be associated with the payee. In response to such a request, the controller 12 will then generate the payment code and associate the payment code with the payee. The controller 12 may associate such a generated payment code with a single payment and retire the code once the payment has been received. Later reuse of the single payment codes after a period of time is also anticipated.
  • a payee request for a generated payment code may also include an amount of the payment to be made using the generated code.
  • the controller 12 may store the amount for the expected payment in association with the payment code. This allows the controller 12 to cross-check payment codes against payment amounts and detect errors that may be made in payment.
  • a transaction code is a code which is unique for each transaction or sale for a given period of time. For example a transaction code may l ink to an identification number of a product being sold e.g. corresponding to a barcode ID number, event ticket number etc. Transaction codes may be predefined in this way, or they may be manually or automatically generated at the point of sale.
  • Transaction codes may be automatically generated by a payee's point of sale device or a payee's mobile application.
  • Figure 4 shows a process diagram showing automatic transaction code generation by the controller 12.
  • a merchant code is a code which uniquely identifies a merchant.
  • Merchant codes may be assigned and provided to payees when they sign up for a service implementing the method of this invention. For example the assignment of merchant codes may be automated by the controller 1 2 when merchants sign-up online.
  • a third party code is any code which is assigned by a third party not being the controller 12 or the payee.
  • this may be an online sale identifier, which is assigned by an online shop that is not necessarily owned by the payee.
  • Such online shops may include online auction sites or online shopping platforms.
  • controller 12 may use the payment amount to aid identification of the payee.
  • Figure 1 shows an embodiment of a method for facilitating payments according to the present invention.
  • Figure 2 shows a process diagram of the method of Figure 1 .
  • the payee provides the payer with a payment code 2, associated with the payee financial institution account which the payee would like to receive the payment in.
  • the payer makes a payment 3 into one of several financial institution accounts which are monitored by the controller 12.
  • the payer may make the payment by any suitable means, including telephone banking and internet banking.
  • the payer selects the monitored account from a list of preregistered payees provided by the payer's bank.
  • the payer identifies the payment using a payment code associated with the payee to which payment is being made.
  • the payer may enter the payment code in the "particulars", “code”, or “reference” section when entering payment details.
  • the payment is credited 4 to a financial institution account monitored by the controller 12.
  • a transaction monitor 19 of the controller 12 monitors a plurality of financial institution accounts for receipt of payments.
  • the transaction monitor 19 monitors the plurality of financial institution accounts through financial institution provided electronic systems for example, a bank- provided online-banking system.
  • the transaction monitor 1 9 may use a web- parsing engine 14 to access the financial institution's web application server 26 to monitor for receipt of payments.
  • an Application Program Interface engine 15 accesses the financial institution's transaction servers 27.
  • the controller 12 may access the financial institution provided electronic system in any suitable way, including bank-provided APIs.
  • the controller 12 monitors using transaction monitor 19 at least one financial institution account at multiple financial institutions. In the simplest case, the controller 12 monitors two or more accounts each of which are held at different financial institutions. Preferably, the controller 12 will monitor accounts at all of the major financial institutions between which transactions are carried out. For example, in a New Zealand context, the controller 12 may monitor financial institution accounts based in each of the major New Zealand banks. In the context of other countries or indeed multiple countries the banks located in those countries have accounts controlled and monitored by the controller 12.
  • the payment is received from a payer financial institution account at the same financial institution as the monitored financial institution account that receives the payment. For example, if a particular payer banks with bank A, the payer will make a payment into a monitored financial institution account held at bank A.
  • Intra-financial institution transfers are in most cases much faster than inter-financial institution transfers. Most intra-financial institution transfers between accounts are instantaneous, or near-instantaneous, and are transferred as cleared funds. Therefore, when a payer makes a payment into a monitored financial institution account at the same financial institution as the payer's own account, the controller 12 will receive the payment almost instantly, and can in turn notify the payee that it has received the payment almost instantly.
  • the present invention is extremely beneficial in situations where the payer's financial institution account is under a different financial institution from that of the payee's financial institution account. If the payer were to attempt to make a payment through financial institution provided systems, the payee would generally not receive the payment in the payee's account until later, usually the next business day, but in some cases within the next hour if the payer's bank processes payments hourly and the transaction is during the bank's service hours.
  • the present invention allows payees to have confidence that the payee has successfully made the payment.
  • the controller 12 detects 5 that a payment has been received, the controller 12 executes the following steps:
  • the controller 12 identifies the payee the payment is for based on the payment code 6. This is using the transaction code engine 20 and reconciliation engine 21 and the aforementioned stored associations between payees, information on payee financial institution accounts and payment codes. Thus the controller 12 is able to identify the payee using the payment codes referenced in the particulars for each received payment. The controller 12 can also use the payment code for other purposes, for example to verify a transaction. If the payment code is a transaction code which was generated by the controller 12 the controller can match received transaction codes against generated transaction codes.
  • Figure 5 shows a process diagram of possible payment transaction code usage. Payee Notification
  • the controller 12 then notifies the payee that the payment has been received 9. Preferably, the controller 12 notifies the payee immediately or as soon as possible after the controller 12 has identified the payee.
  • Notification can occur in any suitable way. Possible notification methods via the messaging interfaces 1 6 include but are not limited to email, a mobile application, notification via a point of sale device, text message, or automated telephone calls.
  • the controller 12 may include a push messaging interface 1 6 for issuing notifications to a mobile application, for example.
  • the controller 12 may notify the payee via more than one notification method.
  • the notifications may be simultaneous, or at different times.
  • the controller 12 may first send an immediate notification to the payee via text message, and at a later time for example at the end of a business day, send an email notification including all of the payments made during the day.
  • the invention is not limited in this respect.
  • the notification message may contain any suitable information. For example, it may include a timestamp, payment code and a payment amount.
  • the notification may include an identifier.
  • the identifier may be used for security purposes, to verify the authenticity of the notification.
  • the identifier may be a secret identifier only known by the payee and the controller 12, such that if the identifier is included in a notification the payee can be assured that the notification is genuine.
  • the identifier may be chosen by the payee and communicated to the controller 12 on sign-up, or alternatively it may be provided to the payee by the controller 12.
  • the controller 12 may provide mechanisms to change the identifier at regular intervals, or when requested by the payee.
  • the controller 12 may associate one or more communication channels and/or settings with each payee and store in a database 1 1 .
  • the payee When the payee receives notification of the payment from the control ler 1 2, they can be assured that the payment has been made, and can safely provide the goods and/or services 10 to the payer.
  • the control ler 12 transfers the payment into the payee's financial institution account 7.
  • the control ler 1 2 requests the transfer using financial institution provided electronic systems.
  • An example of such a financial institution provided electronic system is direct l i nks offered by some banks to their electronic systems over the internet via an FTP-server connection. Files can be automatically created at the control ler's end and uploaded directly into the FTP-server.
  • the bank's system picks up the files and sends a Money Transfer Schedule back to the control ler's folder on the FTP server, which confirms receipt of the file.
  • the bank systems then make the transfer 8.
  • the control ler 12 may request payment into the payee's financial institution as soon as the payee has been identified, simultaneously with payee notification, or immediately after notifying the payee.
  • An immediate transfer may be preferred so that the payee can receive the payment in the payee financial institution account as soon as possible.
  • control ler 12 may transfer the payment to the payee financial institution account after a predetermined time period. For example, the controller 1 2 may transfer the payment one hour after receiving the payment. This may be desirable to simplify the reversal of transaction errors, or to al low prompt refunds if the payer wishes to return the product and/or service.
  • the present invention may incl ude a mechanism by which the control ler 12 receives requests for refunds back into the payer's account, and enacts the refunds.
  • the controller 12 may transfer the payment into the payee financial institution account independently for each received payment.
  • the controller 12 may aggregate payments having a payment code associated with the payee and pay the aggregated amount to the payee financial institution account.
  • the controller 12 may receive numerous payments destined for a particular payee throughout the day.
  • the controller may receive these payments in multiple monitored financial institution accounts, from multiple financial institution accounts associated with financial institutions different payers.
  • the controller 12 may notify the payee immediately after each payment, but refrain from making the transfer.
  • the controller 12 may make an aggregate payment which includes all of the payments within that time period as a single transaction. Alternatively payments may be aggregated when a certain threshold aggregated payment sum is reached. The invention is not limited in this respect.
  • the result is that the payee receives convenient and instant notification that the payment has successfully been paid to an intermediate financial institution account prior to the payment being received in the payee's financial institution account.
  • the controller 12 may, using financial institution provided electronic systems transfer the payment in a different currency from the currency in which the payment is received. For example, the controller 12 may make a payment into a foreign payee bank account. The controller 12 make use of bank- provided electronic transfer platform to make an international money transfer.
  • a currency may be a conventional currency or a virtual currency.
  • Virtual currency is understood to mean a type of regulated or unregulated, digital money. Unregulated digital money is usually issued and control led by its developers, and used and accepted among the members of a specific virtual community.
  • Virtual currencies include but are not limited to crypto currencies such as Bitcoin.
  • the financial institution accounts monitored by the controller 12 are registered with the financial institutions as pre-registered payees.
  • Financial institutions in particular banks, often have mechanisms by which an account can be pre-registered to enable quicker and easier payment into the account.
  • Some financial institutions refer to these as "pre- assigned payees".
  • pre-registration might enable a payer to pay to the account by entering a simplified account name. Over bill payments or bank transfers, this replaces the need for payers to enter the account number, which is often a long series of digits which are cumbersome to enter and easy to mistype.
  • Pre-registered accounts may be browseable, or searchable by key-words. The use of pre-registered accounts significantly decreases the chance that a mistake will occur when the payer makes payment into the financial institution account, and makes it quicker and easier to pay to the financial institution account.
  • High-vol ume payees may wish to be pre-registered under their own names with two or more financial institutions. Payers can then search for or enter the payee's custom pre-registered payee name to direct payment into the payee's account. This may avoid the need for payers to enter payment codes which identify the particular merchant e.g. payment codes including merchant codes.
  • the controller 12 may pre-register such payees with at least two financial institutions. The pre-registration itself may be automated where the financial institution allow this to be done electronically, or alternatively the controller 12 may issue instructions to manually pre-register the payee under one or more monitored accounts.
  • Figure 6 shows a method for facilitating payments according to the present invention, including integration with a payee (merchant's) point of sale system 45.
  • a payee enters 30 a sale into the payee's POS (Point of Sale) system 45, and selects the method/apparatus of the present invention as the payment method 31 .
  • POS Point of Sale
  • the Point of Sale terminal apparatus or software implementation can, at time of sale, request from the controller's transaction code interface 1 7 via a wired or wireless internet connection a unique transaction code for the transaction 32.
  • This request would include a merchant identifier so the transaction code created can be stored in the controller database referenced against the given merchant.
  • the generated transaction code is returned 33 to the POS System which then communicates this code to the consumer 34.
  • This can be via a number of possible channels, including a terminal display screen and via a mobile application on the consumer's personal device. This latter form can be triggered by user action such as scanning a Q code or tapping the phone to the terminal for Near Field Communication (NFC) transfer, or wireless signalling such as Bluetooth beacon.
  • NFC Near Field Communication
  • the consumer then includes this transaction code when making the payment 35 and the payment is credited to a monitored financial institution account 36.
  • the transaction code engine 20 of the controller 12 When the transaction monitor 19 detects a new credit 37 and the reference matches an allocated transaction code 38, the transaction code engine 20 of the controller 12 first deactivates 43 the transaction code in the database 1 1 , then notifies the POS System 45 via a call-back mechanism that the payment is received 39.
  • Figure 7 shows an implementation of the method of Figure 6.
  • the POS System 45 is configured to interface with the controller 12.
  • FIG 8 shows another implementation of the method of Figure 6.
  • the POS System has a hardware device 46 positioned between an existing POS terminal device 45 and POS payment device (eg EFTPOS terminal) 47.
  • This device 46 emulates both devices' connections so it can be dropped in-place to existing configurations.
  • This payment channel device 46 is then responsible for initiating and completing the transaction when required and for transparently forwarding requests to the POS payment device when not required.
  • Figure 9 shows another implementation of integrating a POS system with the method of the present invention.
  • the POS system 45 is a vending machine.
  • a payer wishes to purchase an item, the payer credits the vending machine with an amount, using the method of the present invention.
  • the vending machine includes a merchant code, which the customer uses to make the payment. When the vending machine receives notification that payment has been successful, the customer can make their selection and purchase the item.
  • An alternative implementation may provide the vending machine with an interface to request and display transaction codes.
  • Payers can pay payees quickly and easily via a short reference code - this avoids the need to type in long account numbers which is cumbersome and prone to mistakes.
  • the invention also removes real or perceived risks associated with publicising financial institution account numbers.
  • the method of the present invention does not require intermediate accounts having a "float" of money and settlement between various intermediate accounts. Instead, payments flow directly from payer, to intermediate account, to payee.
  • the system under the present invention also provides a convenient way to refund payments. Payers can feel comfortable making payments under the present invention as they use their own banking systems which they known and trust.

Landscapes

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

Abstract

L'invention concerne un procédé et un appareil pour faciliter des paiements d'une pluralité de payeurs à une pluralité de bénéficiaires au moyen d'un dispositif de commande. Le procédé comprend les étapes consistant, pour le dispositif de commande, à : associer, à chaque bénéficiaire, des informations concernant un compte d'institution financière bénéficiaire et au moins un code de paiement. Le dispositif de commande surveille des comptes d'institution financière en ce qui concerne une réception de paiement et des codes de paiement et envoie une notification au bénéficiaire lors de la réception des paiements.
PCT/NZ2015/050112 2014-08-22 2015-08-17 Procédé et appareil pour faciliter des paiements WO2016028167A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
NZ629194 2014-08-22
NZ629194A NZ629194A (en) 2014-08-22 2014-08-22 A method and apparatus for facilitating payments

Publications (1)

Publication Number Publication Date
WO2016028167A1 true WO2016028167A1 (fr) 2016-02-25

Family

ID=55351015

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/NZ2015/050112 WO2016028167A1 (fr) 2014-08-22 2015-08-17 Procédé et appareil pour faciliter des paiements

Country Status (2)

Country Link
NZ (1) NZ629194A (fr)
WO (1) WO2016028167A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107818460A (zh) * 2016-09-13 2018-03-20 北京京东尚科信息技术有限公司 一种支付方法及装置
CN115760101A (zh) * 2022-12-02 2023-03-07 深圳市美的支付科技有限公司 收款系统、收款方法、计算机设备和计算机可读存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006031626A2 (fr) * 2004-09-13 2006-03-23 Ixept, Inc. Methodes et appareil d'alerte d'achat
WO2008124584A1 (fr) * 2007-04-06 2008-10-16 Mastercard International, Inc. Procédés et appareil pour des versements de fonds à des comptes sans carte de paiement à l'aide d'un système de carte de paiement
US20100169214A1 (en) * 2008-12-30 2010-07-01 Jamie Michael Nonni System and method to initiate funding of multiple merchant accounts
WO2010079216A1 (fr) * 2009-01-08 2010-07-15 Visa Europe Limited Système de paiement
WO2013126168A1 (fr) * 2012-02-23 2013-08-29 Mastercard International Incorporated Procédé et système pour faciliter des micro-paiements dans un système de transactions financières
US20130282581A1 (en) * 2012-04-18 2013-10-24 Infosys Limited Mobile device-based cardless financial transactions

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2006031626A2 (fr) * 2004-09-13 2006-03-23 Ixept, Inc. Methodes et appareil d'alerte d'achat
WO2008124584A1 (fr) * 2007-04-06 2008-10-16 Mastercard International, Inc. Procédés et appareil pour des versements de fonds à des comptes sans carte de paiement à l'aide d'un système de carte de paiement
US20100169214A1 (en) * 2008-12-30 2010-07-01 Jamie Michael Nonni System and method to initiate funding of multiple merchant accounts
WO2010079216A1 (fr) * 2009-01-08 2010-07-15 Visa Europe Limited Système de paiement
WO2013126168A1 (fr) * 2012-02-23 2013-08-29 Mastercard International Incorporated Procédé et système pour faciliter des micro-paiements dans un système de transactions financières
US20130282581A1 (en) * 2012-04-18 2013-10-24 Infosys Limited Mobile device-based cardless financial transactions

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107818460A (zh) * 2016-09-13 2018-03-20 北京京东尚科信息技术有限公司 一种支付方法及装置
CN115760101A (zh) * 2022-12-02 2023-03-07 深圳市美的支付科技有限公司 收款系统、收款方法、计算机设备和计算机可读存储介质

Also Published As

Publication number Publication date
NZ629194A (en) 2016-02-26

Similar Documents

Publication Publication Date Title
US12217228B2 (en) Systems and methods for point of sale deposits
US11501266B2 (en) Mobile agent point-of-sale (POS)
US9779396B2 (en) Method of making mobile payments to a recipient lacking a wireless or contactless terminal
US20070005467A1 (en) System and method for carrying out a financial transaction
US20030119554A1 (en) Method and arrangement for performing a cashless payment transaction
US20120078736A1 (en) On-demand generation of tender ids for processing third-party payments via merchant pos systems
US20150324767A1 (en) System and method for recovering refundable taxes
CN108027925B (zh) 一种使用二维码的无卡支付方法及其系统
US11676149B2 (en) Methods and systems for routing transactions between automated teller machines, points of sale, financial institutions, and software wallets
US11972405B2 (en) Systems and methods for point of sale deposits
KR20110019887A (ko) 모바일 카드/계좌 결제 시스템 및 이를 이용한 결제 방법
CN101990770A (zh) 移动电话支付业务系统中的虚拟支付账户数据
US20130013502A1 (en) Facilitation of Transactions Using a Transaction Code
WO2016076732A1 (fr) Procédés et systèmes de traitement de carte
US20200074438A1 (en) Mobile device payment system and method
US20140310166A1 (en) System and method for loading stored value accounts
US10915876B2 (en) Application program interface for conversion of stored value cards
JP2018014106A (ja) 取引記録との関連付けのための取引額の識別
JP2019036169A (ja) スマートフォンを利用したキャッシュアウトシステム
AU2020281086A1 (en) Payment Re-direction System and Topology and Programming Method
US20210326840A1 (en) Issuing a virtual value-bearing card associated with only non-personally identifying information from a kiosk
WO2016028167A1 (fr) Procédé et appareil pour faciliter des paiements
KR20060093575A (ko) 휴대폰을 이용한 결제 방법
EP2688025A1 (fr) Procédé de traitement d'une transaction de paiement par carte avec présentation de la carte
WO2020096524A1 (fr) Procédé et système de gestion d'un remboursement de taxe

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: 15833394

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: 15833394

Country of ref document: EP

Kind code of ref document: A1