WO2016131084A1 - Système de paiement de factures - Google Patents

Système de paiement de factures Download PDF

Info

Publication number
WO2016131084A1
WO2016131084A1 PCT/AU2016/000049 AU2016000049W WO2016131084A1 WO 2016131084 A1 WO2016131084 A1 WO 2016131084A1 AU 2016000049 W AU2016000049 W AU 2016000049W WO 2016131084 A1 WO2016131084 A1 WO 2016131084A1
Authority
WO
WIPO (PCT)
Prior art keywords
bill
user
payment
bills
biller
Prior art date
Application number
PCT/AU2016/000049
Other languages
English (en)
Inventor
Aristotelis GEORGOPOULOS
Randy PRADO
Original Assignee
Ezitechnologies Pty 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
Priority claimed from AU2015900570A external-priority patent/AU2015900570A0/en
Application filed by Ezitechnologies Pty Ltd filed Critical Ezitechnologies Pty Ltd
Publication of WO2016131084A1 publication Critical patent/WO2016131084A1/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/327—Short range or proximity payments by means of M-devices
    • G06Q20/3276—Short range or proximity payments by means of M-devices using a pictured code, e.g. barcode or QR-code, being read by the M-device
    • 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/04—Payment circuits
    • G06Q20/047—Payment circuits using payment protocols involving electronic receipts
    • 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/102—Bill distribution or payments
    • 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/327—Short range or proximity payments by means of M-devices
    • G06Q20/3278—RFID or NFC payments by means of M-devices

Definitions

  • the present invention relates to a computerised device, system, method computer program and data signal arranged to capture and manage the payment of bills.
  • Electronic payment has come to encompass any type of electronic funds transfer, including Point of Sale terminals in retail stores (and the associated charge/credit card system) through to e-commerce systems— broadly any payment system which is accessed and utilised via the Internet or a telecommunications network. Fundamentally, however, most electronic payment systems require the consumer to either attend a specific location (e.g. a Post Office) to pay a bill, or log onto one of several specific interface (e.g. an online banking portal to use 'BPay' that is separate of 'BPay') to pay a bill.
  • a specific location e.g. a Post Office
  • an online banking portal to use 'BPay' that is separate of 'BPay'
  • the present invention provides:
  • a system for collecting, storing and enabling payment of bills including a networked computational device arranged to receive information relating to a bill and transfer information regarding the bill to a processor;
  • processor is arranged to process and store in a database information relating to the bill
  • processor is arranged to pay at least a portion of the bill when instructed to by an authorised user of the networked computational device.
  • the networked computational device is arranged to receive information relating to a bill through at least the following methods:
  • the system can capture bills of digital and hard copy text format it is possible to capture and store essentially all a user's bills into the system. This allows a user to use only one portal to receive, manage and pay bills. This improves the efficiency and management of a user's bills.
  • the digital format is XRBL.
  • the registered user to use the system, the registered user must nominate at least one source of finance for the system to access and provide funds from.
  • the bills can be paid through the source of finance, where the source of finance is at least one of a credit facility, debit facility, reward system or fund transfer system.
  • the source of finance can be facilities offered via the system.
  • the source of finance can be facilities offered via a third party.
  • the bill can be transferred to a second user registered with the system for payment of the bill.
  • selected proportions of the bill can be transferred to at least one second user registered with the system for payment of the bill.
  • the bill is transferred by the user providing a request to the second user with a digital link; wherein the digital link provides access to the bill for review and payment.
  • the system includes a bill management system, wherein the bill management system is arranged to apply rules to selected bills received and stored.
  • stored bills are managed by accounting software.
  • the system includes a biller register; wherein digital bills received from a biller on the biller register are automatically stored to the system.
  • bills received from an entity on the biller register are paid according to predetermined rules.
  • bills received from an entity not on the biller register must be processed by the user.
  • funds can be directly transferred between two or more users registered with the system within the system.
  • a biller registered with the system can have their bill paid via direct transfer within the system.
  • stored bills can be grouped according to due date, amount, biller, or subject matter.
  • the present invention provides a computer program, including at least one instruction capable of being executed by a computing system, which implements a system in accordance with any one of the preceding Claims.
  • Figure 1 is an example computing system which is capable of operating a device, system, method and/or computer program in accordance with an embodiment of the present invention
  • Figure 2 a schematic representation of a system of the present invention
  • Figure 3 is a schematic diagram illustrating the process of a user registering with a payment system of the present invention
  • Figure 4 is a schematic representation of a schematic representation of the bill payment process of the system of Figure 2;
  • Figure 5 is a schematic representation of a first bill processing method of the system of the present invention;
  • Figure 6 is a schematic representation of a second bill processing method of the system of the present invention.
  • Figure 7 is a schematic representation of a bill sharing function of the system of Figure 4.
  • Figure 8 is a schematic representation of the bill payment process of the system of Figure 2;
  • Figure 9 is a schematic representation of a bill payment process of the system of Figure 4.
  • Figure 10 is a schematic representation of a bill payment process of the system of Figure 4.
  • Figure 1 1 is a schematic representation of a bill payment process of the system of Figure 2;
  • Figure 12 is a schematic representation of a money transfer process of the present invention.
  • Figure 13 is a schematic representation of a payment option applicable to the system of the present invention.
  • Figure 14 is a schematic representation of a payment option applicable to the system of the present invention.
  • Figure 15 is a schematic representation of a Point of Sale payment option applicable to the system of the present invention.
  • Figure 16 is a schematic representation of the system of the present invention interfacing with an accounting reporting application
  • Figure 17 is a schematic representation of different applications interfacing with the system of the present invention
  • Figures 18 to 20 are screenshots illustrating screens utilised by a user (consumer) when interacting with an embodiment of the present invention.
  • FIG. 1 there is shown an example computing system which is capable of facilitating transactions in accordance with an embodiment of the present invention.
  • FIG. 1 there is shown a schematic diagram of a computing system, which in this embodiment is a server 100 suitable for use with an embodiment of the present invention.
  • the server 100 may be used to execute application and/or system services such as a system and method for facilitating the transfer of value (i.e. an electronic financial transaction) in accordance with an embodiment of the present invention.
  • the server 100 may comprise suitable components necessary to receive, store and execute appropriate computer instructions.
  • the components may include a processor 102, read only memory (ROM) 104, random access memory (RAM) 106, an input/output devices such as disc drives 108, remote or connected input devices 1 10 (such as a mobile computing device, a smartphone or a 'desktop' personal computer), and one or more communications link(s) 1 14.
  • the server 100 includes instructions that may be installed in ROM 104, RAM 106 or disc drives 1 12 and may be executed by the processor 102.
  • At least one of a plurality of communications link 1 14 may be connected to an external computing network through a telecommunications network.
  • the device may include a database 1 16 which may reside on the storage device 1 12. It will be understood that the database may reside on any suitable storage device, which may encompass solid state drives, hard disc drives, optical drives or magnetic tape drives.
  • the database 1 16 may reside on a single physical storage device or may be spread across multiple storage devices.
  • the server 100 includes a suitable operating system 1 18 which may also reside on a storage device or in the ROM of the server 100. The operating system is arranged to interact with the database and with one or more computer programs to cause the server to carry out the steps, functions and/or procedures in accordance with the embodiments of the invention described herein.
  • the invention relates to a computing device and system arranged to interact with one or more remote devices via a communications network arranged to receive, process and pay bills in a number of formats in addition to allowing the transfer of funds between entities registered to the system.
  • the system also allows for entities registered within the system to transfer or divide the responsibility for paying a bill between different registered entities.
  • the system in one embodiment, comprises a server including a database arranged to receive, store and manage billing information processed by the processor.
  • the database is arranged to receive and transmit information via the communications network from the one or more remote devices.
  • the method facilitates the capture of bills in digital format, in hard copy such as printed format or hand written format, in manually entered format and storing the details of billers and historical billing information.
  • the method also facilitates the transfer of value between two or more entities registered with the system via one or more remote devices and a centralized database. This transfer can serve the purpose of paying the bill or can transfer the bill to another entity or a plurality of registered entities to divert or share the responsibility for the bill.
  • the centralized database receives details of the bill from either the recipient of the bill (the user) or from the biller.
  • the centralized database receives instructions to effect payment to the biller through preprogrammed rules or through direct instruction from the user or other authorized registered entity.
  • the billing information or instructions to effect payment may be sent in the form of a data signal which includes, in part or in whole, encoded information which provides one or more commands to the centralized database and/or the remote devices, to implement the aforementioned method.
  • the database is arranged to contain various types of information.
  • the database is arranged to hold information regarding a store of value for the one or more entities. Definitions
  • ⁇ Ezibills the computing system that receives, processes, stores and pays bills.
  • ⁇ User the person or system that receives and pays a bill or instructs the transfer of bills or funds through the Ezibills system.
  • ⁇ 2 nd User an entity registered in the Ezibills system that can receive communications, transfers, full or partial bill responsibility through the Ezibills system
  • NFC Near Field Communication
  • Radio-Frequency Identification (RFID) Chip a chip that stores information that can be transferred through radio waves.
  • QR Code a matrix barcode that stores information.
  • FIG. 2 there is shown a broad schematic diagram of a system 103, for the capture, processing and storage of particular of a bill sufficient to enable payment of the bill in accordance with an embodiment of the present invention. It will be understood that in the ensuing description, the system 103 will be referred to as the "Ezibills system”.
  • the Ezibills system 103 is arranged to capture, process and receive digital bills or physical bills that are typed or hand written. To capture digital bills, at billing step 101 , the biller produces and sends an electronic bill in extensible Business Reporting Language (XBRL) format to the user, directly through the Ezibills system 103.
  • XBRL extensible Business Reporting Language
  • the Ezibills system processes and stores the bill details so they can be displayed to a user through a digital presentation module 109.
  • the Ezibills system 103 allows multiple bills to be stored, and grouped according to the manner in which a user wished to view them. For example, the bills can be grouped in accordance to the due date of the bill. Alternatively the bills can be grouped by the amount of the subject matter to which the bills relate.
  • the use of XBRL allows the information of the bill to be broken down and grouped as noted above.
  • the Ezibills system 103 uses the Agile Unified Process (AUP) software development methodology to deliver the whole project, with work activities organized according to a tailored version of those provided by IEEE Standard Developing Software Live Cycle Processes (IEEE 1074-1998).
  • AUP Agile Unified Process
  • the architecture of the Ezibills system 103 uses Object Oriented Programming (OOP) methods and tools for analysis, design and implementation.
  • OOP Object Oriented Programming
  • the development team follows Object Modelling Technique (OMT) defining every process and functionality required by the application.
  • the user scans a QR code, NFC chip, RFID chip or otherwise to capture the bill particulars. Once captured at step 107, the captured details are transferred to the Ezibills system 103 for processing and storage so they can be displayed to a user through the digital presentation module 109.
  • the bill is a physical bill with no electronic coding, for example a typed or hand written bill
  • the bill is scanned or photographed and the image file is converted into electronic format through an Optical Character Recognition (OCR) program.
  • OCR Optical Character Recognition
  • the bill particulars are transferred to the Ezibills system 103 for processing and storage so they can be displayed to a user through the digital presentation module 109.
  • a registration process 1 1 1 is shown for enabling a user to register for use with the Ezibills 103 system.
  • a user accesses the Ezibills software application through an input device 1 10 and enters email details at step 1 15 that are used to test that the user is active through the nominated email address.
  • a verifying email is sent to the nominated email address. If the email address is verified a link to a registration form is sent to the nominated email address at step 1 18.
  • the user fills out the fields of the registration form required for registration. These fields include title, name, email, password and password confirmation, addresses, date of birth, contact phone numbers. Once the fields are completed the user submits the form at step 123.
  • the details of the fields of the registration form are verified against trusted sources, such as for example certified registers. If the details are verified the user is issued with access permissions to the Ezibills 103 system at step 129 and a user specific account is created in the Ezibills system at step 131 . If the details are unable to be verified the user is redirected back to the registration form to enter new details into the fields.
  • trusted sources such as for example certified registers.
  • Ezibills account is generated at step 131 , the user then enters financial details of their account such as if it is a personal or business account, Details of bank or other financial institutions that will be responsible for providing funds, these could be Ezibills related financial institutions or external financial institutions, and settings on how to manage incoming bills with the financial institutions when they are received.
  • the Bill can be uploaded to the Ezibills 103 system through OCR 402, directly uploaded as a digital transfer 204 using technology such as, but not being limited to, XBRL, or manually entered by the user.
  • the Ezibills system 103 is linked to either Ezibills financial institutions for payment or to third party services to provide the finance required to pay the bills uploaded to the Ezibills system. Examples of the these financial institutions are bank accounts, credit cards, Foreign exchange or Fund of Funds.
  • the system 103 stores the details of the bill for later treatment.
  • FIG. 5 the steps of the Ezibills System 103 involved with a digital upload and payment of a bill are illustrated where the Biller has been registered by the user. Where a biller sends a digital bill and they are registered by the user into the users Ezibills 103 account the biller issues a bill 226. The issued bill 226 is transferred at transfer step 228 to the Ezibills system 103 through digital transfer 204 to have the Bill and its details uploaded as bill file 230.
  • the user can enter the Ezibills system 103 and view the bill at viewing step 212. Through the Ezibills system 103, the user can pay the bill through a nominated fund source at payment instruction step 214. Alternatively, if the payment management system 224 is set up to automatically pay bills the payment management system 224 transfers the bill to payment instruction step 214. Ezibills processes the payment instruction 214 at processing step 218 and the bill is paid to the bill issuer or nominated party at remittance step 222. After the bill is paid, a record of the payment 232 is sent to the biller and stored in the system.
  • FIG. 6 the steps involved with an upload and payment of a bill where the Biller is not registered with the user in the Ezibill 103 system.
  • the biller sends a bill 200 to the user in bill transfer step 201 .
  • This can be digitally or as a hard copy.
  • the user uploads the bill at step 201 using OCR techniques 402, manual processing, the use of a QR code or NFC chip and reader.
  • the bill is processed by the computing system at processing step 202.
  • Ezibills system 103 When the user enters the Ezibills system 103 they view the bill at viewing step 204. Through the Ezibills system 103, the user can pay the bill through a nominated fund source, at payment step 214. Ezibills processes the payment step at processing step 218 and the bill is paid to the bill issuer or nominated party at remittance step 222.
  • a bill sharing function 235 is illustrated.
  • a user sets up the Ezibills system 103 so that at least one 2 nd user registered with Ezibills are linked to their user account.
  • bill selection step 135 a bill stored in a user's Ezibills 103 system is chosen by the user.
  • the user selects an option within the Ezibills 103 system to share the bill at share selection step 137.
  • share selection step 137 the user elects selected 2 nd users to share the bill with and the proportion of the bill that they wish to share with each of the selected 2 nd users.
  • the shared bill is then sent to the selected third parties at bill sharing step 139 through FacebookTM, SMS, email or other digital method and a message 141 is sent to the selected third parties with details of the proposed sharing and means to open, consider and pay the bill.
  • the user views the bill through a link in the message at bill viewing step 143.
  • the selected portion of the bill can then be paid through the link by the selected third party.
  • the bill is able to be transferred via email, SMS or otherwise without knowledge of the 2 nd users bank details.
  • Bill uploading 203 where the user uploads the bill, the user logs into the Ezibills 103 system to upload a bill at step 201 .
  • the bill is uploaded into the system, accessibly by the user in upload step 204.
  • the biller sends the electronic bill to the Ezibills 103 system at electronic transfer step 208.
  • the biller and bill is verified by the Ezibills 103 system at step 206. After verification, the bill is uploaded and stored in the system for future use in upload step 304.
  • the bills are able to be accessed at a late date to be grouped with or compared against other bills.
  • Bill Sharing 205 if bill sharing is required the user selects a bill to bill share at step 210. The bill is sent to selected 2 nd users at sharing step 208. The selected 2 nd users reviews their allocated proportion of the bill at step 208 and the amount and status of the bill as apportioned between parties is updated at step 208. Once these steps have taken place a verification of the shared bill being sent is sent to the user at verification step 310.
  • Bill Payment 207 When the user or a selected third party wishes to pay the bill or a portion of it, they log into the Ezibill 103 system and view the bill at bill viewing step 212. The user or selected 2 users elects to pay the bill and directs payment to the system at payment direction step 214. The system presents the payment direction to the selected payment mode at presentment step 216. The Ezibills system 103 reviews the instructed method of payment at review step 220 and pays the bill to the biller to one of the nominated funding sources at payment step 218. The user is sent notification at step 314 and the biller is then sent a notification 222 that the payment has taken place.
  • FIG. 9 an overview of the Ezibills 103 system is shown.
  • the user selects a bill stored in the system 103 at bill selection step 122.
  • the user opts to pay the bill at payment selection step 124.
  • the Ezibills system 103 reviews its internal database to identify if the selected bill is registered under a bill management process at review step 126. If the bill is registered under the bill management process it is dealt with according to preprogrammed rules of the system at step 128. If the bill is not registered under a bill management process the system displays to the user payments options at step 130.
  • the user can elect to pay the bill through an internal Ezibills payment facility 134, or through an external fund source 132, such as a bank, credit card or otherwise.
  • the user selects to pay using an internal Ezibills payment facility 134 they have a number of choices.
  • the user can elect to pay the bill through a rewards system 136, a debit system 140, a credit system 142 or can transfer 138 the bill to a 2 nd user biller or multiple 2nd user billers who is/are a part of the Ezibills system.
  • the rewards system 136 for bill payment is illustrated.
  • a user collects rewards through using the Ezibills system 103.
  • the user selects rewards as the payment option at selection option 145.
  • the system reviews the rewards held by the user at rewards review step 147. If the user does not have sufficient rewards to pay for the bill the rewards system sends a signal to Ezibills 103 system at step 149 and the bill is not paid with rewards. If the user does have sufficient rewards to pay for the bill the rewards module pays the bills and sends a signal to Ezibills 103 at step 151 and updates the internal rewards level at with update signal 153.
  • Figure 1 1 shows the option of payment through an external fund source 132.
  • the user selects a payment method that is not registered with the Ezibills 103 system at selection step 155 and enter the other payment account details on enter page 157. If the other payment account details are rejected or the payment is rejected a rejection signal 159 is sent to the system 103 rejecting the payment. If the other payment account details are accepted an acceptance signal 161 is sent to the system and the Ezibills system 103 updates its database to reflect the status of the payment.
  • Figure 12 shows the transfer sub module 138 of the payment module 134 where the user transfers funds to a 2 nd user or multiple second users.
  • the user sends a transfer selection signal 165 that indicates they wish to transfer funds to or multiple 2 nd users.
  • the user selects the mode by which a transfer request will be made.
  • the details step 169 requires details of the 2 nd user or multiple second users to be entered.
  • Financial account information can be added for the 2 nd user or multiple 2 nd users at step 171 .
  • a reference for the transfer is generated at reference step 173.
  • a request for transfer to the 2 nd user or multiple 2 nd users is made at step 175.
  • the request is sent via Facebook 179, SMS 177 or email 181 without bankind details of the 2 nd user or multiple 2 nd users. If a 2 nd user is the biller, funds are directly transferred to the 2 nd user at bill transfer 185.
  • the recipient receives 187 the request in a message.
  • the message contains a link 189 to the Ezibills system 103 to enable the transfer of funds.
  • the 2 nd user provides the reference produced at step 173 for verification. If the user has not provided financial account information at step 171 , the 2 nd user provides it at step 143. If the provided account is an Ezibills account the funds are transferred to the Ezibills account at transfer step 183. IF not the user provides the alternate financial account details 145 and the funds are transferred 147.
  • Figure 13 shows the credit sub module 140 of the payment module 134.
  • the user selects a specific bill 160 that is registered with the Ezibills 103 system.
  • the user enters their selected credit card and sends this information through credit selection signal 162.
  • the user sends a selected credit verification signal 164. If the verification signal 164 is accepted the system 103 checks that all required fields are entered with a checking signal 166. If the checking signal 166 is validated a credit card number validation signal 170 is sent to validate the credit card number. If the credit card number validation signal 170 is validated the system 103 sends a transfer signal 172 to have funds for the bill transferred to the biller.
  • Figure 14 shows the debit sub module 142 of the payment module 134.
  • the system 103 checks that all required fields are entered with a checking signal 148. If the checking signal 148 is validated a debit card number validation signal 150 is sent to validate the debit card number. If the debit card number validation signal 150 is validated the system 103 sends a funds level verification signal 168 to verify there are sufficient fund to meet the bill. If the funds level verification signal 168 is verified the system 103 sends a transfer signal 152 to have funds for the bill transferred to the biller.
  • Figure 15 shows a point of sale function 180 of the Ezibills 103 system.
  • the user can present a NFC enabled computer device to pay through Ezibills.
  • the user presents the device and through NFC tools 186 downloads the transaction details to the Ezibills system 103.
  • the point of sale is a 2 nd user of the Ezibills system, a direct transfer can occur at transfer step 188.
  • the user wishes to pay through an Ezibills payment financial tool 134 it does so at step 190 and 194. If payment is to be through an external financial instrument 132 it does so through step 192 and 196.
  • Figure 16 shows the interface of the Ezibills 103 system with an Accounting application 198 for the purposes of preparing accounts reports.
  • the incoming transaction data from the Ezibills system 103 is interfaced with accounting software such as Xero to store and manage the details of transactions.
  • Figure 17 shows the Ezibills 103 system interacting with its modules ezitransfer 138, point of sale 180, bill capture 136, Ezibills financial institutes 134, and the journal function 198.
  • Figure 18 is a screen shot from a page of the Ezibills 103 system showing the management of several bills.
  • Figure 19 is a screenshot from a page of the Ezibills 103 system showing the management of several bills.
  • Figure 20 is a screen shot from a page of the Ezibills 103 system showing options for a user to enter bills.
  • the embodiments and broader inventive concept provide a number of advantages. Firstly, all bills can be captured and managed by the Ezibills 103 system. In contrast to the current system, existing systems do not capture and manage bills. They typically provide a third party processing of bills portal that enables bills to be entered and paid by a user.
  • the system provides the ability to link the payment of bills in the Ezibills 103 system to a number of payment methods in the one interface.
  • Existing systems that enable the payment of bills require that a user interacts with a variety of interfaces to pay with a variety of methods.
  • the system provides the capability to spread the responsibility for a bill over a number of entities.
  • the embodiments and broader invention described herein are provided via an ⁇ ', namely a software application arranged to operate on a mobile device, such as a smartphone.
  • the embodiments and broader invention may also be encoded in firmware or integrated into an operating system for a device, as required for any particular use.
  • a dedicated Point of Sale terminal may be utilized to display the QR code in accordance with an embodiment of the invention.
  • the use of hardware devices may provide particular advantages, such as the ability to better secure communication channels and/or the ability to perform transactions more quickly (which may be important in a busy environment). Such variations are encompassed by the broader inventive concept described herein.
  • an application programming interface API
  • ADK application development kit
  • a series of libraries for use by a developer, for the creation of software applications which are to be used on any one or more computing platforms or devices, such as a terminal or personal computer operating system or a portable computing device, such as a smartphone or a tablet computing system operating system, or within a larger server structure, such as a 'data farm' or within a larger transaction processing system.
  • API application programming interface
  • ADK application development kit
  • libraries for use by a developer, for the creation of software applications which are to be used on any one or more computing platforms or devices, such as a terminal or personal computer operating system or a portable computing device, such as a smartphone or a tablet computing system operating system, or within a larger server structure, such as a 'data farm' or within a larger transaction processing system.
  • program modules include routines, programs, objects, components and data files that perform or assist in the performance of particular functions
  • functionality of the software application may be distributed across a number of routines, programs, objects or components to achieve the same functionality as the embodiment and the broader invention claimed herein.
  • Such variations and modifications are within the purview of those skilled in the art.
  • any appropriate computing system architecture may be utilised. This includes standalone computers, network computers and dedicated computing devices (such as field-programmable gate arrays).

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Finance (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

L'invention concerne un système destiné à collecter, à stocker et à permettre le paiement de factures, comprenant: un dispositif informatique en réseau disposé pour recevoir des informations se rapportant à la facture d'un utilisateur inscrit du système et transférer des informations concernant la facture à un processeur, le processeur étant disposé pour traiter et stocker dans une base de données des informations se rapportant à la facture; et le processeur étant disposé pour payer au moins une partie de la facture lorsqu'il en reçoit l'instruction de la part d'un utilisateur autorisé du dispositif informatique en réseau; le dispositif informatique en réseau étant disposé pour recevoir des informations se rapportant à une facture par au moins les procédés suivants: prendre une image d'une facture et convertir les renseignements de la facture capturée dans l'image en texte numérique à l'aide d'une technologie OCR; lire un code QR ou à barres; utiliser des fonctionnalités de lecture NFC pour lire une puce NFC contenant les renseignements de la facture; par saisie manuelle; en recevant une facture sous format numérique.
PCT/AU2016/000049 2015-02-19 2016-02-19 Système de paiement de factures WO2016131084A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
AU2015900570A AU2015900570A0 (en) 2015-02-19 A computing device, system, method, computer program and data signal arranged to facilitate payments
AU2015900570 2015-02-19

Publications (1)

Publication Number Publication Date
WO2016131084A1 true WO2016131084A1 (fr) 2016-08-25

Family

ID=56691905

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/AU2016/000049 WO2016131084A1 (fr) 2015-02-19 2016-02-19 Système de paiement de factures

Country Status (2)

Country Link
TW (1) TW201643782A (fr)
WO (1) WO2016131084A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
IT201700110188A1 (it) * 2017-10-03 2019-04-03 Ppro S R L Un metodo per controllare e gestire elettronicamente pagamenti e archiviazioni dati
WO2020181339A1 (fr) * 2019-03-14 2020-09-17 Billi Technologies Pte. Ltd. Système et procédé de transfert de fonds numériques et de paiement de factures
EP4116907A1 (fr) * 2021-07-09 2023-01-11 Evo Merchant Services, LLC Système de paiement sans friction

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI767140B (zh) * 2019-09-03 2022-06-11 兆豐國際商業銀行股份有限公司 交易系統

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070145138A1 (en) * 2000-01-03 2007-06-28 Tripletail Ventures, Inc. Method for data interchange
US20140195416A1 (en) * 2013-01-10 2014-07-10 Bill.Com, Inc. Systems and methods for payment processing
US20140379584A1 (en) * 2013-06-25 2014-12-25 FraudFree Finance, LLC Anti-fraud financial transaction method

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070145138A1 (en) * 2000-01-03 2007-06-28 Tripletail Ventures, Inc. Method for data interchange
US20140195416A1 (en) * 2013-01-10 2014-07-10 Bill.Com, Inc. Systems and methods for payment processing
US20140379584A1 (en) * 2013-06-25 2014-12-25 FraudFree Finance, LLC Anti-fraud financial transaction method

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
IT201700110188A1 (it) * 2017-10-03 2019-04-03 Ppro S R L Un metodo per controllare e gestire elettronicamente pagamenti e archiviazioni dati
WO2020181339A1 (fr) * 2019-03-14 2020-09-17 Billi Technologies Pte. Ltd. Système et procédé de transfert de fonds numériques et de paiement de factures
EP4116907A1 (fr) * 2021-07-09 2023-01-11 Evo Merchant Services, LLC Système de paiement sans friction

Also Published As

Publication number Publication date
TW201643782A (zh) 2016-12-16

Similar Documents

Publication Publication Date Title
US20200175496A1 (en) Systems and methods for facilitating fund transfer
US20180197167A1 (en) System and method for person-to-person payments
US20110196797A1 (en) Wireless payment and barter platform
JP6980113B2 (ja) オンライン支払プロセスにおけるデータ処理方法および装置
US20140101048A1 (en) System and Method for Enrollment of Payment Transaction Services
US20140279453A1 (en) Bill Payment Using Check Image
US20120078736A1 (en) On-demand generation of tender ids for processing third-party payments via merchant pos systems
UA118854C2 (uk) Спосіб та система для перевірки фінансових операцій щодо електронних грошових переказів
US11321709B1 (en) System and method for conducting secure financial transactions
WO2016179012A1 (fr) Procédés et systèmes de paiement de facture sur la base de messages
BRPI0710021A2 (pt) sistema de pagamento individualizado móvel
CN101990676A (zh) 移动电话交易系统和方法
US20160379204A1 (en) Multi-biller payment systems and methods
WO2016131084A1 (fr) Système de paiement de factures
CN112116482B (zh) 基于区块链的融资数据处理方法及装置
US20120173436A1 (en) Method and system for authorizing, authenticating, implementing, brokering data transfers, and collecting fees for data transfers among distributed electronic devices and servers
US20080201261A1 (en) System and method for electronic payment processing
US20220147955A1 (en) System and method for digital funds transfer and bill payment
AU2021104965A4 (en) Methods, Systems and Software Platform for facilitating charitable donation payments within one or more digital donation devices
US20230072087A1 (en) Multifunctional user device
US20130075466A1 (en) Method and system of rapidly cashing a check and loading the proceeds onto a consumer electronic access device via a mobile smart device
US9047637B1 (en) Method and system for converting printed checks into pre-paid debit card funds
RU105766U1 (ru) Интеллектуальная сеть микрофинансирования
US11094006B1 (en) System for communicating with a financial institution to manage disbursements over a communication network
TWM609176U (zh) 授權系統

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

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

Country of ref document: EP

Kind code of ref document: A1