[go: up one dir, main page]

WO2017177253A1 - Système de gestion de communications, transactions financières et informations connexes - Google Patents

Système de gestion de communications, transactions financières et informations connexes Download PDF

Info

Publication number
WO2017177253A1
WO2017177253A1 PCT/AU2016/000132 AU2016000132W WO2017177253A1 WO 2017177253 A1 WO2017177253 A1 WO 2017177253A1 AU 2016000132 W AU2016000132 W AU 2016000132W WO 2017177253 A1 WO2017177253 A1 WO 2017177253A1
Authority
WO
WIPO (PCT)
Prior art keywords
instructions
dtf
information
account
network
Prior art date
Application number
PCT/AU2016/000132
Other languages
English (en)
Inventor
Simon Richard WEEKS
Original Assignee
Weeks Simon Richard
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 Weeks Simon Richard filed Critical Weeks Simon Richard
Priority to PCT/AU2016/000132 priority Critical patent/WO2017177253A1/fr
Publication of WO2017177253A1 publication Critical patent/WO2017177253A1/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/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
    • G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
    • G06Q20/326—Payment applications installed on the mobile devices
    • G06Q20/3265—Payment applications installed on the mobile devices characterised by personalisation for use
    • 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/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/321—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wearable devices

Definitions

  • This invention relates to telecommunications devices, computers and other electronic devices; software related to communications systems, non-cash payment systems, non-cash savings systems, lending systems, customer management technology, point of sale systems, inventory management systems, business analyti cs technology, customer rewards systems and healthcare claims; performed by and with these devices utilising telecommunications networks.
  • Communications systems enable users of these systems to send various forms of communication to each other.
  • Such forms include written communication such as typed text, recorded sound information such as spoken words, and visual communication such as photos and pre-recorded or streamed video.
  • These messages can be sent from electronic devices and computers to other electronic devices and computers utilising various forms of telecommunications technology including Near Field Communication ('NFC') technology, Bluetooth technology, wireless networks, general
  • Non-cash payment systems enable users of these systems to pay each other. These payments can be made using electronic devices or computers over
  • Savings and investment systems operated by financial institutions can enable users of these systems to save money into a financial institution account set up for the user by the user applying and receiving approval for an account with the financial institution, then manually depositing cash at the financial institution's branch, if applicable, or automatic teller machine, if applicable, or transferring funds to the financial institution by electronic funds transfer ('EFT').
  • 'EFT' electronic funds transfer
  • Peer-to-peer lenders use a similar system, method and process to commonly known financial institution lending system and process, but instead lend consumers' money from said fund and provide some investment returns to said consumers, instead of owners of the respective financial institutions in the case of lending by financial institutions.
  • POS Point Of Sale
  • Some businesses provide rewards to customers, that show loyalty to a respective business when customers purchase goods and/or services from said business, in a manner chosen by the business.
  • a system that helps a business manage customer rewards is known as a rewards program.
  • a rewards program can be managed with a piece of cardboard provided to a customer, where a business records how often a customer buys a certain good or service on the cardboard and provides a reward to a customer when the customer has purchased a sufficient quantity or purchase value of a good or service chosen and noted by said business on the cardboard.
  • a rewards program can also be managed on a magnetic strip card (the 'rewards card') that logs a customer's purchase history onto a computer memory facilitated by a computer program when the customer presents their rewards card or unique identifier associated with the rewards card and associated customer to said business, for registering a particular purchase transaction as a rewards related transaction.
  • Said business provides ongoing rewards, discounts or other benefits, or rewards when certain criteria are manifested, related to the customer's purchase history with said business.
  • non-cash payment systems making a purchase of a good or service can require the customer and business navigating a complex POS terminal. Thi s is a cumbersome process.
  • users of non-cash payment systems can be required to scan and upload or manually enter credit card or account numbers into the payment system before being able to make a payment. This is a time- consuming process.
  • users of traditional consumer facing EFT payment systems can be required to gather and manually enter the Bank-State-Branch and account numbers of a recipient entity in order for that recipient entity to be paid, as well as navigate the payment system software.
  • the user can go to an automatic teller machine and withdraw cash, then deliver this cash to the recipient user.
  • This is a time consuming and human energy-expending process.
  • NFC payment systems can require a user to select the account by and from which payment is to be made from. This extra time wastes power.
  • payments executed with non-cash payment systems can be delayed several days before the funds associated with the payment arrive in the account of the intended recipient entity. This can cause inaccuracy and confusion in record keeping due to the delay in the record of the transaction appearing on the corresponding account's transaction ledger, it can create an additional layer of complexity with inventory management and can create cash flow problems with the recipient entity who may be relying on the timely arrival of the corresponding funds.
  • non-cash payment systems such as NFC payment systems can rely on credit card payment systems infrastructure. Credit cards can enable users to spend more money than those users can earn or repay in a given time period, causing the user to enter into debt, with sufficient earnings to only service the minimum payments required to service the debt but not reduce it. This is known as a 'credit card debt cycle'.
  • existing payment systems may not provide the ability for a user to request payments from another entity. This makes it difficult for a mobile business to collect debts from persons who are avoiding payment if the operators of those businesses meet in person, those persons who are avoiding payment.
  • international payment systems can take several days to transfer funds, can require a user to visit a bank branch in person to process payment, or be required to transfer funds via EFT into the applicable
  • Point of Sale and customer management systems can be separate to payment systems. The separation of these systems requires a user of both systems to allocate more time to install, operate and maintain another piece of software which places additional cognitive demand on the user.
  • business intelligence software it can be a separate system to the aforementioned systems. This separation requires a user of these systems to allocate more time to install, operate and maintain another piece of software and places additional cognitive demand on the user.
  • rewards programs can be a separate system to the aforementioned systems, an additional facility and software for a business to use and manage, placing further time and cognitive demand on the user.
  • Rewards cards can be another item for a person to carry and remember to use, and another card for the business to use when processing a purchase related payment. This can place additional cognitive demand and time impost on these users and businesses.
  • healthcare claims can be a facilitated with a separate healthcare card and a separate payment system to the aforementioned systems, an additional facility and software for a business to use and manage, and a different card to use for patients related to healthcare claims, placing further time and cognitive demand on users of the system.
  • the aforementioned systems are generally separate from each other. This causes si gnificant deficiencies for users that use more than one of the aforementioned systems.
  • the System is an invention that improves the aforementioned systems and combines them into one system that provides further gains in efficiency and ease of use, giving a result that is novel and inventive.
  • FIG. 1A - 1 C illustrate the System in accordance with some embodiments.
  • FIG. 2A - 2B illustrate example processes of how requests are received and processed by the System and sent between some components of the System, in accordance with some embodiments.
  • FIG. 3 illustrates an example method for selecting recipients (users or other entities) for a plurality of applications in accordance with some embodiments.
  • FIG. 4 illustrates an example method for viewing user account related information in accordance with some embodiments.
  • FIG. 5 illustrates an example method for facilitating general communications between users or other entities in accordance with some embodiments.
  • FIG. 6A - 6F illustrate example methods for facilitating financial transactions in accordance with some embodiments.
  • FIG. 7 illustrates an example method for facilitating requests for payment in accordance with some embodiments.
  • FIG. 8 illustrates an example method related to the provision of invoices and receipts related to financial transactions in accordance with some embodiments.
  • FIG. 9A - 9B illustrate example methods related to settings and use of an interfacing object in accordance with some embodiments.
  • FIG. 10A - 10B illustrate example methods related to the facilitation of loans in accordance with some embodiments.
  • FIG. 1 1 A - 1 IB illustrate example methods related to inventory management and related financial transactions in accordance with some embodiments.
  • FIG. 12A - 12B illustrate example methods related to rewards from businesses to customers in accordance with some embodiments.
  • FIG. 13 illustrates an example method related to the facilitation of financial transactions related to healthcare claims in accordance with some embodiments.
  • first means "first,” “second,” etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another.
  • a first DTF could be termed a second DTF, and, similarly, a second DTF could be termed a first DTF, without departing from the scope of the various described embodiments.
  • the first DTF and the second DTF are both DTFs, but they are not the same DTF.
  • the System has a user device.
  • the user device is a desktop computer.
  • the user device is a portable computer (e.g. laptop computer, tablet computer).
  • the user device is a mobile phone (e.g. smart phone, personal digital assistant).
  • the user device is a payment terminal.
  • the user device is a wearable device such as a watch.
  • the user device is a virtual reality device.
  • the user device is an augmented reality device.
  • the system has one or more user devices.
  • the user device has biometric technology (e.g. finger print scanner, retinal scanner).
  • the user device has global proximity system ('GPS') technology.
  • the user device has Telecommunications Technology (TT) (e.g. communications radio technology, mobile phone communication technology such as SMS communications technology, 'wireless' technology, 'bluetooth' technology, 'multi-peer connectivity' technology, 'beacon' technology, 'ethernet' technology), making it capable of sending and receiving telecommunications related information or Internet related information.
  • TT Telecommunications Technology
  • the user device has voice control technology, enabling a user to instruct the user device to execute instructions given by the user's voice through a microphone built into the user device.
  • the user device has biometric technology, enabling an authorised user to access the System (e.g.
  • biometric technology enables an authorised user to instruct the user device.
  • the user device has one or more processors and memory that executes instructions and records information given to the user device.
  • the user device has an interface (e.g. a graphical user interface such as a visual display, a visual display that is a touch screen, a user-derived information inputting device such as a keyboard, computer mouse, 'voice control' technology, scanning technology (e.g. digital document scanner, image scanner, NFC tag scanner, QR code scanner, bar code scanner), photographic camera, biometric technology) that enables the user to exchange information (e.g.
  • the user device has software that enables the processor to execute instructions provided by the user.
  • the user device has system software that enables the processor to execute instructions provided by a computer program.
  • the user device has software, referred to as the User Application (UA) that, with the user device processor and memory, enables a user to provide information to the System or request the System to change information in the System, via the user device interface.
  • the UA with user device processor and memory enables a user to request to change settings of the UA.
  • the UA with user device processor prepares and executes instructions on behalf of an entity that has requested the System to perform a function (e.g. related to the registration of an entity as a user of the System, related to the authorisation of an entity to access the System).
  • prepares and executes instructions on behalf of a user that has requested the System to perform a function a user e.g. instructions related to general communications between users, instructions related to financial transactions between users, instructions related to a user's funds, instructions related to a user's personal or business information and System settings (e.g. settings related to default user accounts, system account top-ups, savings related settings, lending and borrowing settings, settings related to an interfacing object, settings related to
  • the UA with user device processor enables information to be displayed on the interface.
  • the UA enables the user device to send and receive Information between user devices and the Main System, or between user devices, by utilising TT, telecommunications networks or the Internet (collectively referred to as the 'Network').
  • the UA has an encryption system that is the System Encryption System (SES) that encrypts information, instructed to be sent via the Network, before it is sent via the Network, preventing non- authorised users, user devices, persons, computers or other devices from accessing said information; and decrypts encrypted information received via the Network, from an authorised user device or other computer system, to enable said information and any related instructions to be executed by the processor.
  • SES System Encryption System
  • the UA has an Electronic Shopping Cart (ESC) that enables the user device to add items to be purchased from a business via the user device interface (e.g. items with technology identification detected by the user device interface).
  • ESC Electronic Shopping Cart
  • the System has a computer system (referred to as the 'Main System').
  • the Main System has one or more computers.
  • the Main System computers have a coupling of one or more processors, software and memory.
  • the Main System computers form a network.
  • said network is a distributed network.
  • the Main System has an interface (e.g. a graphical user interface such as a visual display, an information inputting device such as a keyboard) that enables information to be provided to the Main System.
  • the Main System has TT, making it capable of sending and receiving telecommunications or Internet related information (e.g. communications radio technology, mobile phone
  • the Main System has software that enables a processor to execute instructions provided by a user device. In some embodiments, the Main System has software that enables a processor to execute instructions provided by another computer program. In some embodiments, the Main System has software that enables a processor to execute instructions provided by another computer.
  • the Main System has software that is the SES, an encryption system that encrypts mformation instructed to be sent via the Network, before it is sent via the Network, preventing non-authorised users, user devices, persons, computers or other devices from accessing said information; and decrypts encrypted information received via the Network, to enable said information and any related instructions to be executed by the processor.
  • the Main System has a coupling of software, hardware and memory that is the Data Management System ('DMS'), where non- financial information related to users, entities, related transactions and requests are recorded (e.g. user settings, user related identification information, entity related information, customer related information (e.g. transactions between a user and a user that is a business), business related information, rewards information).
  • 'DMS' Data Management System
  • the DMS is a distributed system.
  • the Main System has a coupling of software, hardware and memory that is a Rewards System (RS) that calculates and facilitates rewards related to transactions with a user that is a business and users that are customers of said business.
  • the RS is a distributed system.
  • the Main System has a coupling of software, hardware and memory that records financial transactions and related information, referred to as the System Account Ledger (SAL).
  • the SAL is a distributed ledger.
  • a user has one or more system accounts, managed by the Main System.
  • the Main System has a coupling of software, hardware and memory called the Account Management System (AMS) that manages system accounts and a network of accounts held at one or more Deposit Taking Facilities (DTFs), referred to as system-DTF accounts.
  • AMS is a distributed system.
  • system-DTF accounts hold funds referred to the AMS Reserve.
  • the AMS manages the AMS Reserve.
  • system-DTF accounts hold an aggregate of funds related to an aggregate of system account balances.
  • the Main System has a coupling of software, hardware and memory that is a Currency Exchange System (CES).
  • CES Currency Exchange System
  • the Main System a coupling of software, hardware and memory that is a credit system.
  • the Main system has a coupling of software, hardware and memory that is an Inventory Management System (IMS).
  • IMS Inventory Management System
  • the Main system has a coupling of software, hardware and memory that is a business intelligence system (BIS) and, with a series of algorithms forming part of said system, enables a user that is a business to analyse customer related information via the UA via the business 's user device.
  • the Main system has software, hardware and memory that is a rewards system, enabling a user that is a business, to manage and implement a rewards program via the UA via the business's user device interface.
  • the Main System has a coupling of software, hardware and memory that is the Electronic Shopping Cart System (ESCS) that enables the user device to add items to be purchased from a business via the user device interface.
  • the Main System has a coupling of software, hardware and memory that is the Claims Management System (CMS) that manages healthcare claims and related information.
  • the Main System has a coupling of software, hardware and memory that is a fraud detection system and, with a series of algorithms forming part of said system, enables the System to manage fraud related risk.
  • the System has one or more deposit-taking facilities (DTFs).
  • a DTF has one or more computers.
  • said DTF computers have a coupling of one or more processors, software and memory.
  • a DTF has an encryption system that is the SES, an encryption system that encrypts information, instructed to be sent via the Network, before it is sent via the Network, preventing non-authorised users, user devices, persons, computers or other devices from accessing said information; and decrypts encrypted information received via the Network, from an authorised user device or other computer system, to enable said information and any related instructions to be executed by the processor.
  • a DTF has TT.
  • a DTF has an interfacing object (e.g. a credit card, a debit card) that is compatible to use with non- System payment systems infrastructure (e.g.
  • the interfacing object has a plurality of technology that enables the interfacing object to interface with non-System payment systems, (e.g. NFC technology, magnetic stripe technology, EMV technology).
  • the interfacing object has identifiers that are compatible with non-System payment gateways.
  • a user device is enabled to be an interfacing object, utilising said non- System payment systems technology.
  • the interfacing object is linked to a user account (e.g. a system account, a DTF account, a credit card account, a debit card account).
  • financial transactions executed with the object, interfacing with other payment systems infrastructure are transactions that use funds from the user account linked to the interfacing object.
  • more than one account can be selected to be linked to the interfacing object.
  • one or more system accounts can be selected to be linked to the interfacing object.
  • one or more DTF accounts can be selected to be linked to the interfacing object.
  • one or more credit cards and related accounts can be selected to be linked to the interfacing object.
  • a user can select or change the user account linked to the interfacing object via the UA via the user device interface.
  • a method that encrypts information is initiated when the encryption of information is desirable (e.g. when sending information over the Network).
  • the method is referred to as method ⁇ '.
  • the method includes initiation of the SES by a user device processor with UA when a user device processor with UA requires the utilisation of an embodiment of the Main System and the utilisation of the embodiment is actualised via the Network.
  • the method includes initiation of the SES by the user device processor with UA when information is required to be sent to the Main System from a user device via the Network.
  • the method includes initiation of the SES at the Main System by a Main System processor with software when information is required to be sent to a user device from the Main System via the Network.
  • the method includes initiation of the SES at the Main System by a Main System processor with software, when information is required to be sent to an entity (e.g. from the Main System, from a user device, from a DTF) via the Network.
  • the method includes the SES encrypting information using a plurality of encryption methods (e.g. data tokenisation, codification, cryptographic algorithms) when information is provided to the SES.
  • the method includes decrypting information when information is received via the Network (e.g. by a user device, by the Main System, by a DTF, from an external entity via the Network).
  • a method that enables information to be sent via the Network is initiated by an entity (e.g. a user device, the Main System, a DTF, an information provider, individual).
  • entity e.g. a user device, the Main System, a DTF, an information provider, individual.
  • the method is referred to as method ' ⁇ '.
  • the method includes TT related to the entity (the 'sender') causing information (e.g.
  • the method includes TT related to the receiver receiving the information, via the Network.
  • a method that registers an entity as a user of the System is initiated at a user device.
  • the method is referred to as method 'C.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes an entity providing information (e.g. personal identification related information, user device identifiers, user device network addresses, biometric information, DTF accounts related information and other information; together referred to as 'Registration Information') into the UA to enable user registration.
  • the method includes the entity providing Registration Information, via the UA, via the user device interface.
  • the method includes the entity providing Registration Information using another user device computer program, via the UA, via the user device interface.
  • the method includes the entity requesting that same entity's DTF account related information as part of the provision of Registration Information via the UA, via the user device interface, from the corresponding DTF or an authorised information provider.
  • the method includes the user device processor with UA preparing instructions to send to a Main System processor with software to execute in relation to the requested information.
  • the method includes the user device sending the instructions related to the requested information via the Network.
  • the method includes the Main System receiving the instructions related to the requested infonnation via the Network.
  • the method includes a Main System processor with software preparing instructions related to the requested information to send to the DTF.
  • the method includes the potential Main System processor with software preparing instructions related to the requested information to send to an authorised information provider.
  • the method includes the Main System sending the instructions related to the requested information to the DTF via the Network.
  • the method includes the Main System sending the instructions related to the requested information to the authorised information provider via the Network.
  • the method includes the Main System recei ving the requested infonnation from the DTF via the Network.
  • the method includes the Main System receiving the requested information from the authorised information provider via the Network.
  • the method includes a Main System processor with software preparing instructions for the user device with U A to display the requested information on the user device interface.
  • the method includes a Main System processor sending the instructions and requested infonnation to the user device.
  • the method includes the user device receiving the instructions and requested information.
  • the method includes the user device processor with UA executing the instructions, including causing the requested information to be displayed on the user device interface.
  • the method includes the user device sending Registration Information to the Main System via the Network.
  • the method includes the Main System receiving the
  • the method includes a Main System processor creating an account for the Registration Information associated with the entity to be recorded in the DMS.
  • the method includes the Main System memory storing the Registration Infonnation in the DMS.
  • the method includes a Main System processor causing the AMS to create a system account for the entity.
  • the method includes a Main System processor with software preparing communication to be sent to the user device notifying the entity of its successful registration, if registration of the entity is successful, via the Network.
  • the method includes a Main System processor with software preparing instructions for the UA to provide the entity access to the System, if registration of the user is successful.
  • the method includes the Main System sending the communication and instructions to the user device via the Network.
  • the method includes the user device receiving the communication and instructions via the Network.
  • the method includes the user device processor with U A causing the communication to be displayed on the interface.
  • the method includes the user device processor with UA providing the entity access to the System, if regi stration of the entity is successful.
  • a method that enables an entity to be authorised to access to the System is initiated at a user device.
  • the method is referred to as method 'D'.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes an entity providing some information (e.g. personal information, user device identifiers, System security certificates, user device network addresses, biometric information, location by GPS, other security related information, together referred as the 'Security Information') via the UA, via the user device interface, used to verify the entity as registered to use the System.
  • the method includes some Security Information related to the person provided by the user device, used to verify the entity is registered to use the System.
  • the method includes the user device sending the Security Information to the Main System via the Network.
  • the method includes the Main System receiving the Security Information via the Network.
  • the method includes a Main System processor with software verifying whether the entity is authorised to use the System based on correlation between the Security Information and the Registration Information provided by the entity.
  • the method includes a Main System processor with software deciding whether said correlation is sufficient to provide the entity access to the System (the 'Authorisation Status').
  • the method includes a Main System processor with software preparing instructions for the user device processor in relation to the Authorisation Status.
  • the method includes recording the Authorisation Status and any associated user access related information to the System, in the DMS.
  • the method includes a Main System processor with software sending instructions related to the Authorisation Status to the user device via the Network.
  • the method includes the user device processor with UA causing the entity to have access to the System when said correlation is sufficient.
  • the user then becomes an 'authorised user'.
  • Instruction prepared by the user device processor with U A on behalf of an authorised user are authorised instructions.
  • the method includes the user device processor with UA denying the entity access to the System when said correlation is not sufficient.
  • a method that enables a user to select another user a method that is used in a plurality of System embodiments (e.g. general communications between users, financial transactions between users), is initiated at a user device.
  • the method is referred to as method ⁇ '.
  • the method is illustrated in FIG. 3.
  • the method includes the user requesting to select another user via the UA via the user device interface.
  • the method includes the UA via user device receiving information related to a select user or users.
  • the method includes the user device processor with UA preparing instructions for a Main System processor with software to execute, in relation to retrieval of possible users available to be selected.
  • the method includes the user device sending the instructions related to the retrieval, to the Main System via the Network.
  • the method includes the Main System receiving the instructions related to the retrieval from the user device, via the Network.
  • the method includes a Main System processor executing the instructions related to the retrieval, including causing the information related to the retrieval to be retrieved from the DMS.
  • the method includes a Main System processor preparing instructions for the user device processor with user apt execute related to the retrieved information.
  • the method includes the Main System sending the instructions and retrieved information to the user device, via the Network.
  • the method includes the user device receiving the instructions and retrieved information from the Main System, via the Network.
  • the method includes the user device processor with UA executing the instructions, including causing the retrieved information to be displayed on the user device interface.
  • the method includes user selecting another user via the UA via the user device interface.
  • the method includes selecting a plurality of other users via the UA via the user device interface.
  • a method that enables a user to select an entity that is not a registered user of the System a method that is used in a plurality of System embodiments (e.g. general communications between users, financial transactions between users), is initiated at a user device.
  • the method is referred to as method 'F'.
  • the method is illustrated in FIG. 3.
  • the method includes the UA via the user device interface receiving information that identifies the entity (e.g. name, a mobile phone number, an email address) via the UA, via the user device interface.
  • the method includes the UA with processor cross-checking contacts stored in user device memory.
  • the method includes the user device processor with UA preparing instructions for a Main System processor with software to execute, to confirm with the DMS that the identification information related to the non-user is not already recorded in the DMS, associated with a registered user or other entity that is not a registered user.
  • the method includes the user device sending the instructions related to said confirmation, to the Main System via the Network.
  • the method includes the Main System receiving the instructions related to the confinnation from the user device, via the Network.
  • the method includes a Main System processor executing the instructions, including an algorithm forming part of the DMS to complete said confirmation.
  • the method includes a Main System processor with software causing the AMS to create a system account for the entity, associating that same entity's identification information with the system account, if the DMS confirms the identification information is not already recorded in the DMS associated with a registered user or other entity.
  • the method includes a Main System processor with software storing the entity's identification information in the DMS, if the DMS confirms the identification information is not already recorded in the DMS associated with a registered user or other entity.
  • the method includes a Main System processor with software preparing instructions for the user device processor with U A, to notify the user if the identification information is already recorded in the DM S associated with a registered user or other entity.
  • the method includes the Main System sending the instructions and related information to the user device, via the Network.
  • the method includes the user device receiving the instructions and related information, via the Network.
  • the method includes the user device processor with UA executing the instructions, which notify the user if the identification information is already recorded in the DMS associated with a registered user or other entity, via the UA, via the user device interface, or in the alternative, enables the entity to be selected, via the UA via the user device interface.
  • the method includes selecting a plurality of entities via the U A via the user device interface.
  • a method that enables an authorised user to request and enable the Main System to perform a plurality of functions behalf of said authorised user is initiated at a user device.
  • the method is referred to as method G.
  • the method is illustrated in FIG. 2 A and 2B.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes requests related a single user (e.g. requests related to changes to a user's settings, requests related to selecting a user account, requests related to funds transfers between a user's system accounts and the user's other DTF accounts, requests related to currency exchanges).
  • the method includes requests related to authorised users of the System that are businesses, related to business related settings (e.g.
  • the method includes requests related to two users (e.g. general communications between users, financial transactions between users, requests related to two users that include currency exchanges, requests related to the IMS, requests related to the sale of items between users).
  • the method includes requests related to more than two users (e.g. when one user sends general communications to one or more other users, when one user financially transacts with more than one other user, when one user requests payment from more than one other user).
  • the method includes an authorised user requesting the System to perfomi a function for said user, via the UA, via the user device interface.
  • the method includes requesting to select a user (the 'recipient') when said function relates to more than one user, via the UA, via the user device interface.
  • the method includes a user device processor with UA preparing instructions related to said request and, with TT, sending the instruction ns to the Main System via the Network.
  • the method includes the Main System receiving the information via the Network.
  • the method includes a Main System processor with software preparing communication, including any associated instructions for the user device with UA to execute in relation to the completion of the instructions, to be sent to the user device related to the completion of the instructions.
  • the method includes the Main System with software recording the information related to the completion of the instructions in the DMS.
  • the method includes the Main System with software recording the information related to the completion of the instructions in the SAL when instructions relate to financial transactions that utilise system accounts.
  • the method includes the Main System sending the communication via the Network to the user device.
  • the method includes the user device with UA executing the instructions associated with the communication.
  • the method includes the user device processor with UA causing communication to be displayed on the user device interface, related to the completion of the instructions, as applicable.
  • a method that enables an authorised user to view DTF account related information in the System is initiated at a user device.
  • the method is referred to as method ' ⁇ '.
  • the method is illustrated in FIG. 4.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes executing method G when instructions are initiated at a user device, subject to the methodology noted in this paragraph.
  • the method includes the System enabling an authorised user to view DTF account related infonnation in the System from more than one DTF, via the UA, via the user device interface.
  • the method includes the System enabling an authorised user to view DTF account related information in the System from more than one DTF, simultaneously, via the UA, via the user device interface.
  • the method includes the user requesting DTF account related information via the UA, via the user device interface.
  • the method includes the user device processor with UA preparing instructions to send to a Main System processor with software to execute in relation to the requested information.
  • the method includes the user device sending the instructions to the Main System via the Network.
  • the method includes the Main System receiving the instructions.
  • the method includes a Main System processor with software preparing instructions for the associated DTF to execute, related to the requested information.
  • the method includes a Main System processor with software preparing instructions for an authorised infonnation provider to execute, related to the requested information.
  • the method includes the Main System sending the instructions to the DTF via the Network, related to the requested information.
  • the method includes the Main System sending the instructions to the authorised information provider via the Network, related to the requested infonnation.
  • the method includes the Main System receiving the infonnation from the DTF via the Network.
  • the method includes the Main System receiving the requested information from the authorised information provider via the Network.
  • the method includes a Main System processor with software preparing instructions for the user device with UA to display the requested information on the user device interface.
  • the method includes the Main System sending the instructions and requested information to the user device.
  • the method includes the user device receiving the instructions and requested information.
  • the method includes the user device processor with UA causing the information to be displayed on the user device interface. The method saves a user time by not having to enter account related details in order to view account related information.
  • a method that enables an authorised user to view system account related information is initiated at a user device.
  • the method is referred to as method T.
  • the method is illustrated in FIG. 4.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes executing method G when instructions are initiated at a user device.
  • the method includes the System enabling an authorised user to view system account related information from more than one system account, initiated via the UA, via the user device interface.
  • the method includes the System enabling an authorised user to view system account related information in the System from more than one system account simultaneously, initiated via the UA, via the user device interface.
  • the method includes the user requesting system account related information, via the UA, via the user device interface.
  • the method includes the user device processor with UA preparing instructions to send to a Main System processor with software to execute in relation to the requested information.
  • the method includes the user device sending the instructions to the Main System via the Network.
  • the method includes the Main System receiving the
  • the method includes a Main System processor with software causing the AMS to provide the requested information.
  • the method includes a Main System processor with software preparing instructions for the user device with UA to display the requested information on the user device interface.
  • the method includes the Main System sending the instructions and requested information to the user device.
  • the method includes the user device receiving the instructions and requested information.
  • the method includes the user device processor with UA causing the information to be displayed on the user device interface.
  • the method in combination with method H, saves a user time by enabling all user account related information to be viewed in one place, at the UA via a user device interface.
  • a method that enables general communications between users of the System or other entities is initiated at a user device.
  • the method is referred to as method 'J'.
  • the method is illustrated in FIG. 5.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes executing method G when instructions are initiated at a user device, subject to the methodology noted in this paragraph.
  • the method includes an authorised user selecting an entity to communicate with (the 'recipient'), via the UA, via the user device interface, according to methods E or F, depending on whether the recipient is a registered user of the System.
  • the method includes the authorised user providing information (e.g.
  • the method includes the user selecting whether the Message is to be deleted after the recipient has read the Message, selected via the UA via the user device interface, for recipients that are registered users.
  • the method includes the user device processor with UA preparing instructions for a Main System processor with software to execute, in relation to the Message.
  • the method includes the user device sending the Message to the Main System via the Network.
  • the method includes the Main System receiving the Message, via the Network.
  • the method includes a Main System processor with software preparing instructions associated with the Message for the recipient's user device processor with UA to execute, for recipients that are registered users.
  • the method includes a Main System processor with software storing the Message and related information in the DMS.
  • the method includes a Main System processor deleting the Message and related information from the DMS, when the user selects for the Message to be deleted after the recipient has read the Message, for recipients that are registered users.
  • the method includes the Main System sending the Message to the recipient user device via the Network.
  • the method includes the recipient user device receiving the Message, via the Network.
  • the method includes the recipient's user device processor with UA executing the instructions, including causing the Message to be displayed on the recipient's user device interface, for recipients that are registered users.
  • the method includes the recipient's UA deleting the Message after the recipient has read the Message, when the user has selected for the Message to be deleted after the recipient has read the Message, for recipients that are registered users.
  • the method includes a Main System processor with software sending the Message to the recipient's user device via the Network (e.g. via SMS technology, via email), for recipients that are not registered users.
  • a method that enables a user to exchange one currency for different currency is initiated at a user device.
  • the method is referred to as method 'K'.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes an authorised user selecting the currency to convert funds to, from the user's default currency, via the UA, via the user device interface.
  • the method includes the user providing the amount to be converted, via the UA, via the user device interface.
  • the method includes the user device with UA preparing instructions for a Main System processor with software to provide the corresponding currency exchange related information from the currency exchange system.
  • the method includes the user device sending the instructions to the Main System, via the Network.
  • the method includes the Main System receiving the instructions from the user device, via the Network.
  • the method includes the Main system processor with software executing the instructions, including causing the currency exchange related information to be provided from the currency exchange system.
  • the method includes the Main system processor with software preparing instructions for the user device with UA to execute, to display the currency exchange related information on the user device interface.
  • the method includes the Main System sending the instructions and currency exchange related information, via the Network.
  • the method includes the user device receiving the instructions and currency exchange related information from the Main System, via the Network.
  • the method includes the user device processor with UA executing the instructions, including causing the currency exchange related information to be displayed on the user device interface.
  • the method includes the user authorising proceeding with the currency exchange via the UA, via the user device interface.
  • the method includes the user device processor with UA preparing instructions for the Main System with processor to execute in relation to the currency exchange.
  • the method includes the user device sending the instructions to the Main System, via the Network.
  • the method includes the Main System recei ving the instructions from the user device, via the Network.
  • the method includes a Main System processor with software executing the instructions, including causing the currency exchange to be executed.
  • the method includes a Main System processor with software logging the currency exchange and related information in the SAL.
  • the method includes a Main System processor with software preparing instructions for the user device processor with UA to execute, including notifying the user of the successfully completed currency exchange and the available balance of exchange funds.
  • the method includes the Main System sending the instructions to the user device, via the Network.
  • the method includes the user device receiving the instructions from the Main System, via the Network.
  • the method includes the user device processor with software executing the instructions, including causing the notification to be displayed on the user device interface.
  • FT - S/S a method that enables financial transactions that are non-cash payments between users of the System, paying with funds held in system accounts, is initiated at a user device.
  • the method is referred to as method 'L'.
  • the method is illustrated in FIG. 6A - 6B.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes executing method G when instructions are initiated at a user device, subject to the methodology noted in this paragraph.
  • the method includes an authorised user requesting to make a payment, via the UA, via the user device interface.
  • the method includes the user selecting the user to receive the payment (the 'recipient') via the UA, via the user device interface, executed according to method E,
  • the method includes an authorised user selecting a system account to pay from via the user via the U A, via the user device interface.
  • the method includes viewing system account related information, executed according to method I.
  • the method includes the UA providing the user the option to select a system account for payment related transactions before the transaction has commenced (e.g. a user setting executed via the UA via the user device interface, that once set in the user settings, selects the selected system account as the default account used for payments, causing account selection for payment related transactions to be automatic, saving a user time).
  • the method includes the user requesting to select the system account, executed according to method G.
  • the method includes the UA providing the recipient the option to select a user account for payment related transactions before the transaction has commenced (e.g. a user setting executed via the UA via the user device interface that, once set in the user settings, selects the selected user account as the default account used for payments, causing consequential account selection related to payment transactions to be automatic, saving a user time).
  • the method includes the recipient providing instructions relating to the selection of the user account, executed according to method G.
  • the method includes the user providing an amount to be paid to the recipient, via the UA, via the user device interface.
  • the method includes the user device processor with UA preventing the payment from proceeding when an amount provided to be paid to the recipient, via the UA via the user device interface, exceeds the user's selected system account balance.
  • the method includes the UA providing the user the option to pay with a different currency from the System's default currency, via the UA via the user device interface.
  • the method includes executing method H, subject to the user authorising proceeding with the currency exchange.
  • the method includes the UA providing the user the option to send a Message to the recipient, provided via the UA, via the user device interface, to accompany the payment, executed according to method J.
  • the method includes the user device processor with U A preparing instructions related to the payment for a Main System processor with software to execute, when the user's nominated system account balance is greater than the amount the user provided to be paid to the recipient.
  • the method includes the user device sending the instructions to the Main System, via the Network.
  • the method includes a Main System processor with software causing the AMS to transfer funds from the user's system account to the recipient user's system account.
  • the method includes a Main System processor with the SAL recording the payment and related changes in users' system accounts in the SAL.
  • the method includes a Main System processor with software preparing instructions and communication related to the successful payment, for the applicable user device processors with UAs to execute.
  • the method includes the Main System sending communication related to the confirmation of successful payment and change in user account balances to the applicable user devices, via the Network.
  • the method includes a Main System processor sending the instructions and communication to the applicable user devices, via the Network.
  • the method includes applicable user devices' processors with UAs executing the instructions, including causing the communication to be displayed on the applicable user devices' interfaces.
  • the method includes the UA providing the recipient the option to send a Message to user, provided via the UA via the recipient's user device interface, executed according to method J.
  • the method includes the UA providing the recipient the option to send a receipt related to receiving the payment to the user, provided via the UA via the recipient's user device interface, executed according to method J.
  • the method enables a user that is a business receive payments without navigating complex POS systems.
  • the method enables users to financially transact efficiently without using credit cards and related payment systems, helping end credit card debt cycles, as applicable.
  • the method combined with other methods related to financial transactions noted in the Description, enables users to view user account related information and manage financial transactions with one system, saving the user time and cognitive energy.
  • a method that enables financial transactions that are non-cash payments between authorised users, paying from funds held in user DTF accounts to system accounts is initiated at a user device.
  • the method is illustrated in FIG. 6A - 6B.
  • the method is referred to as method M.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes executing method G when instructions are initiated at a user device, subject to the methodology noted in this paragraph.
  • the method includes an authorised user requesting to make a payment, via the UA, via the user device interface according to method G.
  • the method includes the user selecting the user to receive the payment (the 'recipient'), according to method E.
  • the method includes an authorised user selecting a DTF account to pay from via the user via the UA, via the user device interface.
  • the method includes viewing DTF account related information, executed according to method H.
  • the method includes the UA providing the user the option to select a DTF account for payment related transactions before the transaction has commenced (e.g. a user setting executed via the UA via the user device interface, that once set in the user settings, selects the selected DTF account as the default account used for payments, causing account selection for payment related transactions to be automatic, saving a user time).
  • the method includes the user requesting to select the system account, executed according to method G.
  • the method includes the UA providing the recipient the option to select a user account for payment related transactions before the transaction has commenced (e.g.
  • the method includes the recipient providing instructions relating to the selection of the user account, executed according to method G.
  • the method includes the user providing an amount to be paid to the recipient, via the U A, via the user device interface.
  • the method includes the user device processor with UA preventing the payment from proceeding when an amount provided to be paid to the recipient, via the UA via the user device interface, exceeds the user's selected system account balance.
  • the method includes the UA providing the user the option to pay with a different currency from the System's default currency, via the UA, via the user device interface.
  • the method includes executing method K, subject to the user authorising proceeding with the currency exchange.
  • the method includes the user device processor with UA preparing instructions for the Main system processor with software to execute in relation to the payment when the user provides an amount to be paid to the recipient to be paid to the recipient via the UA via the user device interface, that is less than or equal to the user's selected account's balance.
  • the method includes the UA providing the user the option to send a Message to the recipient, provided via the UA, via the user device interface, to accompany the payment, executed according to method J.
  • the method includes the user device sending the instructions related to the payment, to the Main System, via the Network.
  • the method includes the Main System receiving the instructions from the user device, via the Network.
  • the method includes a Main System processor with software causing an EFT to occur from the DTF to the deposit-taking facility, in relation to the payment, via the Network.
  • the method includes Main System processor with software causing the deposited funds to be allocated to the recipient's system account.
  • the method includes a Main System processor with software causing the SAL to record the payment and related changes in the recipient's system account.
  • the method includes a Main System processor with software preparing instructions and communication related to the confirmation of successful payment for the applicable user devices' processors with UAs to execute.
  • the method includes a Main System processor with software sending the instructions and communication to the applicable user devices, via the Network.
  • the method includes the applicable user devices receiving the instructions and communication from the Main System, via the Network.
  • the method includes the applicable user devices' processors with UAs executing the instructions, including causing the communication to be displayed on the user devices' interfaces.
  • the method includes the UA providing the recipient the option to send a Message to user, provided via the UA via the recipient's user device interface, executed according to method J.
  • the method includes the UA providing the recipient the option to send a receipt related to receiving the payment to the user, provided via the UA via the recipient's user device interface, executed according to method J.
  • the method enables users to financially transact efficiently without using credit cards and related payment systems, helping end credit card debt cycles, as applicable.
  • the method combined with other methods related to financial transactions noted in the Description, enables users to view user account related information and manage financial transactions with one system, saving the user time and cognitive energy.
  • a method that enables financial transactions that are non-cash payments between authorised users, paying from funds held in user system accounts to DTF accounts is initiated at a user device.
  • the method is referred to as method N.
  • the method is illustrated in FIG. 6A - 6B.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes executing method M, subject to the methodology noted in this paragraph.
  • the method includes an authorised user requesting to make a payment according to method G, via the UA, via the user device interface.
  • the method includes the user selecting the user to receive the payment (the 'recipient'), according to method E.
  • the method includes an authorised user selecting a system account to pay from via the user via the UA, via the user device interface.
  • the method includes viewing system account related information, executed according to method I.
  • the method includes the UA providing the user the option to select a system account for payment related transactions before the transaction has commenced (e.g. a user setting executed via the UA via the user device interface, that once set in the user settings, selects the selected system account as the default account used for payments, causing account selection for payment related transactions to be automatic, saving a user time).
  • the method includes the user requesting to select the system account, executed according to method G.
  • the method includes the UA providing the recipient the option to select a user account for payment related transactions before the transaction has commenced (e.g.
  • the method includes the recipient providing instructions relating to the selection of the user account, executed according to method G.
  • the method includes the user providing an amount to be paid to the recipient, via the UA, via the user device interface.
  • the method includes the user device processor with UA preventing the payment from proceeding when an amount provided to be paid to the recipient, via the UA via the user device interface, exceeds the user's selected system account balance.
  • the method includes the UA providing the user the option to pay with a different currency from the System's default currency, via the UA, via the user device interface.
  • the method includes executing method H, subject to the user authorising proceeding with the currency exchange.
  • the method includes the user device processor with UA preparing instructions for the Main system processor with software to execute in relation to the payment when the user provides an amount to be paid to the recipient via the UA via the user device interface, that is less than or equal to the user's selected account's balance.
  • the method includes the UA providing the user the option to send a Message to the recipient, provided via the UA, via the user device interface, to accompany the payment, executed according to method J.
  • the method includes the user device sending the instructions related to the payment, to the Main System, via the Network.
  • the method includes the Main System receiving the instructions from the user device, via the Network.
  • the method includes a Main System processor with software causing the deposit-taking facility to cause an EFT to occur related to the payment to the recipient's DTF account, crediting funds associated with the payment to that same DTF account.
  • the method includes Main System processor with software causing the SAL to record the payment and related changes in the user's system account.
  • the method includes a Main System processor with software preparing instructions and communication related to the confirmation of successful payment for the applicable user devices' processors with UAs to execute.
  • the method includes a Main System processor with software sending the instructions and communication to the applicable user devices, via the Network.
  • the method includes the applicable user devices receiving the instructions and communication from the Main System, via the Network.
  • the method includes the applicable user devices' processors with UAs executing the instructions, including causing the communication to be displayed on the applicable user devices' interfaces.
  • the method includes the UA providing the recipient the option to send a Message to user, provided via the UA via the recipient's user device interface, executed according to method J.
  • the method includes the UA providing the recipient the option to send a receipt related to receiving the payment to the user, provided via the UA via the recipient's user device interface, executed according to method J.
  • the method enables users to financially transact efficiently without using credit cards and related payment systems, helping end credit card debt cycles, as applicable.
  • the method combined with other methods related to financial transactions noted in the Description, enables users to view user account related information and manage financial transactions with one system, saving the user time and cognitive energy.
  • a method that enables financial transactions that are non-cash funds transfers between an authorised user's system accounts is initiated at a user device.
  • the method is referred to as method ⁇ '.
  • the method is illustrated in FIG. 6A - 6B.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes executing method G when instructions are initiated at a user device, subject to the methodology noted in this paragraph.
  • the method includes an authorised user requesting to transfer funds, via the UA, via the user device interface.
  • the method includes enabling the user to view that same user's DTF account related information according to method I.
  • the method includes the user selecting the system account to transfer funds from according to method G, via the UA, via the user device interface.
  • the method includes the user selecting the system account to transfer funds to, via the UA, via the user device interface.
  • the method includes the user providing an amount of funds to transfer, via the UA, via the user device interface.
  • the method includes the user device processor with UA preventing the transfer of funds from proceeding when the user provides an amount to be transferred via the UA via the user device interface, that exceeds the user's selected system account balance.
  • the method includes the UA providing the user the option to pay with a different currency from the System's default currency, via the UA, via the user device interface.
  • the method includes executing method K, subject to the user authorising proceeding with the currency exchange.
  • the method includes the user device processor with UA preparing instructions for the Main system processor with software to execute in relation to the transfer of funds, when the user provides an amount to be transferred via the UA via the user device interface, that is less than or equal to the user's selected account's account balance, to transfer funds from.
  • the method includes the user device sending the instructions to the Main System related to the transfer of funds, via the Network.
  • the method includes the Main System receiving the instructions from the user device, via the Network.
  • the method includes a Main System processor with software causing the AMS to execute the funds transfer.
  • the method includes a Main System processor with software causing the SAL to record the transfer of funds and related changes in the user's system accounts.
  • the method includes a Main System processor with software preparing instructions and communication related to the confinnation of the successful transfer of funds, for the user device processor with UA to execute.
  • the method includes a Main System processor with software sending the instructions and communication related to the successful transfer of funds to the user device via the Network.
  • the method includes the user device receiving the instructions and communication from the Main System, via the Network.
  • the method includes the user device processor with UA executing the instructions, including causing the communication to be displayed on the user device interface.
  • the method enables users to financially transact efficiently without using credit cards and related payment systems, helping end credit card debt cycles, as applicable.
  • the method combined with other methods related to financial transactions noted in the Description, enables users to view user account related information and manage financial transactions with one system, saving the user time and cognitive energy.
  • a method that enables financial transactions that are non-cash funds transfers between an authorised user's DTF accounts and that same user's system accounts is initiated at a user device.
  • the method is referred to as method P.
  • the method is illustrated in FIG. 6A - 6B.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes executing method M, subject to the methodology noted in this paragraph.
  • the method includes an authorised user requesting to transfer funds, via the UA, via the user device interface.
  • the method includes the System enabling the user to view that same user's DTF account related information according to method H.
  • the method includes the System enabling the user to view that same user's system account related information, according to method I.
  • the method includes the user selecting the DTF account to transfer funds from, via the UA, via the user device interface.
  • the method includes the user selecting the system account to transfer funds to, via the UA, via the user device interface.
  • the method includes the user providing an amount of funds to transfer, via the U A, via the user device interface.
  • the method includes the user device processor with U A preventing the transfer of funds from proceeding when an amount provided to be transferred, via the UA via the user device interface, exceeds the user's selected system account balance.
  • the method includes the UA providing the user the option to pay with a different currency from the System's default currency, via the UA, via the user device interface.
  • the method includes executing method K, subject to the user authorising proceeding with the currency exchange.
  • the method includes the user device processor with UA preparing instructions for the Main system processor with software to execute in relation to the transfer of funds, when the user provides an amount to be transferred via the UA via the user device interface, that is less than or equal to the user's selected account's account balance, to transfer funds from.
  • the method includes the user device sending the instructions to the Main System related to the transfer of funds, via the Network.
  • the method includes the Main System recei ving the instructions from the user device, via the Network.
  • the method includes a Main System processor with software causing an EFT to occur to the DTF account from the deposit-taking facility, in relation to the funds transfer, via the Network.
  • the method includes a Main System processor with software causing the SAL to record the transfer of funds and related changes in the user's system account.
  • the method includes a Main System processor with software preparing instructions and communication related to the confirmation of the successful transfer of funds, for the user device processor with UA to execute.
  • the method includes a Main System processor w ith software sending the instructions and communication related to the successful transfer of funds to the user device via the Network.
  • the method includes the user device receiving the instructions and communication from the Main System, via the Network.
  • the method includes the user device processor with UA executing the instructions, including causing the communication to be displayed on the user device interface.
  • the method enables users to financially transact efficiently without using credit cards and related payment systems, helping end credit card debt cycles, as applicable.
  • the method combined with other methods related to financial transactions noted in the Description, enables users to view user account related information and manage financial transactions with one system, saving the user time and cognitive energy.
  • a method that enables financial transactions that are non-cash funds transfers between an authorised user's system accounts and that same user's DTF accounts is initiated at a user device.
  • the method is referred to as method Q.
  • the method is illustrated in FIG. 6A - 6B.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes executing method P, subject to the methodology noted in this paragraph.
  • the method includes an authorised user requesting to transfer funds, via the UA, via the user device interface.
  • the method includes the System enabling the user to view that same user's DTF account related infonnation according to method H.
  • the method includes the System enabling the user to view that same user's system account related information, according to method I.
  • the method includes the user selecting the system account to transfer funds from, via the UA, via the user device interface.
  • the method includes the user selecting the DTF account to transfer funds to, via the UA, via the user device interface.
  • the method includes the user providing an amount of funds to transfer, via the UA, via the user device interface.
  • the method includes the user device processor with U A preventing the transfer of funds from proceeding when an amount provided to be transferred, via the UA via the user device interface, exceeds the user's selected system account balance.
  • the method includes the UA providing the user the option to pay with a different currency from the System's default currency, via the UA, via the user device interface.
  • the method includes executing method K, subject to the user authorising proceeding with the currency exchange.
  • the method includes the user device processor with UA preparing instructions for the Main system processor with software to execute in relation to the transfer of funds, when the user provides an amount to be transferred via the UA via the user device interface, that is less than or equal to the user's selected account's account balance, to transfer funds from.
  • the method includes the user device sending the instructions to the Main System related to the transfer of funds, via the Network.
  • the method includes the Main System receiving the instructions from the user device, via the Network.
  • the method includes a Main System processor with software causing an EFT to occur from the deposit-taking facility to the DTF account, in relation to the funds transfer, via the Network.
  • the method includes a Main System processor with software causing the SAL to record the transfer of funds and related changes in the user's system account.
  • the method includes a Main System processor with software preparing instractions and communication related to the confirmation of the successful transfer of funds, for the user device processor with UA to execute.
  • the method includes a Main System processor with software sending the instructions and communication related to the successful transfer of funds to the user device via the Network.
  • the method includes the user device receiving the instructions and communication from the Main System, via the Network.
  • the method includes the user device processor with UA executing the instructions, including causing the communication to be displayed on the user device interface.
  • the method enables users to financially transact efficiently without using credit cards and related payment systems, helping end credit card debt cycles, as applicable.
  • the method combined with other methods related to financial transactions noted in the Description, enables users to view user account related information and manage financial transactions with one system, saving the user time and cognitive energy.
  • a method that enables financial transactions that are payments from authorised users to entities that are not users of the System is initiated at a user device.
  • the method is referred to as method R.
  • the method is illustrated in FIG. 6A - 6B.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes executing method M, subject to the methodology noted in this paragraph.
  • the method includes the user requesting to make a payment, via the UA, via the UA, via the user device interface.
  • the method includes the user selecting an entity to receive the payment (the 'recipient') according to method F.
  • the method includes an authorised user selecting a system account to pay from via the user via the UA, via the user device interface.
  • the method includes viewing DTF account related information, executed according to method H.
  • the method includes the UA providing the user the option to select a DTF account for payment related transactions before the transaction has commenced (e.g. a user setting executed via the U A via the user device interface, that once set in the user settings, selects the selected DTF account as the default account used for payments, causing account selection for payment related transactions to be automatic, saving a user time).
  • the method includes the user selecting the DTF account, executed according to method G.
  • the method includes the UA providing the recipient the option to select a user account for payment related transactions before the transaction has commenced (e.g.
  • the method includes the recipient providing instructions relating to the selection of the user account, executed according to method G.
  • the method includes the user providing an amount to be paid to the recipient, via the UA, via the user device interface.
  • the method includes the user device processor with UA preventing the payment from proceeding when an amount provided to be transferred, via the UA via the user device interface, exceeds the user's selected system account balance.
  • the method includes the UA providing the user the option to pay with a different currency from the System's default currency, via the UA, via the user device interface.
  • the method includes executing method K, subject to the user authorising proceeding with the currency exchange.
  • the method includes the user device processor with U A preparing instructions for the Main system processor with software to execute in relation to the payment when the user provides an amount to be paid to the recipient via the UA via the user device interface, that is less than or equal to the user's selected account's balance.
  • the method includes the UA providing the user the option to send a Message to the recipient to accompany the payment, executed according to method J, via the UA, via the user device interface.
  • the method includes the user device sending the instructions related to the payment, to the Main System, via the Network.
  • the method includes the Main System receiving the instructions from the user device, via the Network.
  • the method includes the Main System's processor with software causing the SAL to transfer funds from the user's DTF account, via EFT via the Network, to the recipient's system account, when the user's account balance is greater than the amount the user provided to be paid to the recipient.
  • the method includes a Main System processor with the SAL recording the payment and related changes in the recipient's account balance in the SAL.
  • the method includes a Main System processor sending instructions related to communication to confirm the successful payment, to the user and recipient, via the Network.
  • the method includes the user device receiving the communication related to the confirmation of successful payment from the Main System, via the Network.
  • the method includes the user device processor with U A executing the instructions related to the communication, including causing the communication to be displayed on the user device interface.
  • the method includes a Main System processor with software sending communication to the recipient (e.g. an email, an SMS message) notifying them of the payment made to them by the user, via the Network.
  • the method includes the communication containing a web- based link that when actioned by the non-user using the device associated with the identification information, begins method C.
  • the method includes the Main System with processor providing instructions to the recipient's user device to display the identification information provided by the user automatically in the non-user's user device interface.
  • the method includes the Main System with processor providing instructions to the recipient's user device processor with UA to automatically display the communication related to the successful payment made to the recipient from the user, after method C is completed, on the recipient's user device interface.
  • the method includes the UA automatically providing the recipient the option to send a Message to user, provided via the UA via the recipient's user device interface, executed according to method J.
  • the method includes the UA automatically providing the recipient the option to send a receipt related to receiving the payment to the user, provided via the UA via the recipient's user device interface, executed according to method J.
  • the method enables users to financially transact efficiently without using credit cards and related payment systems, helping end credit card debt cycles, as applicable.
  • the method combined with other methods related to financial transactions noted in the Description, enables users to view user account related information and manage financial transactions with one system, saving the user time and cognitive energy.
  • a method that enables financial transactions that are payments from authorised users to entities that are not users of the System is initiated at a user device.
  • the method is illustrated in FIG. 6A - 6B.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes executing method , subject to the methodology noted in this paragraph.
  • the method includes the user requesting to make a payment, via the UA, via the UA, via the user device interface.
  • the method includes an authorised user selecting a system account to pay from via the user via the UA, via the user device interface.
  • the method includes viewing available system account related information, executed according to method I.
  • the method includes the UA providing the user the option to select a system account for payment related transactions before the transaction has commenced (e.g. a user setting executed via the UA via the user device interface, that once set in the user settings, selects the selected system account as the default account used for payments, causing account selection for payment related transactions to be automatic, saving a user time).
  • the method includes the user selecting the system account, executed according to method G.
  • the method includes the user selecting an entity to receive the payment (the 'recipient') according to method F.
  • the method includes the System enabling the user to view that same user's system account related information according to method I.
  • the method includes the user providing an amount to be paid to the recipient, via the UA, via the user device interface.
  • the method includes the user device processor with UA preventing the payment from proceeding when an amount provided to be transferred, via the UA via the user device interface, exceeds the user's selected system account balance.
  • the method includes the UA providing the user the option to pay with a different currency from the System's default currency, via the UA, via the user device interface.
  • the method includes executing method K, subject to the user authorising proceeding with the currency exchange.
  • the method includes the user device processor with U A preparing instructions for the Main system processor with software to execute in relation to the payment when the user provides an amount to be paid to the recipient via the UA via the user device interface, that is less than or equal to the user's selected account's balance.
  • the method includes the UA providing the user the option to send a Message to the recipient to accompany the payment, executed according to method J, via the UA, via the user device interface.
  • the method includes the user device sending the instructions related to the payment, to the Main System, via the Network.
  • the method includes the Main System recei ving the instructions from the user device, via the Network.
  • the method includes the user device processor with UA causing the Main System's processor with SAL to transfer funds from the user's system account to the recipient's system account when the user's account balance is greater than the amount the user provided to be paid to the recipient.
  • the method includes a Main System processor with the SAL recording the payment and related changes in the user and recipient's system accounts in the SAL.
  • the method includes a Main System processor sending instructions related to communication to confirm the successful payment, to the user and recipient, via the Network.
  • the method includes the user device receiving the communication related to the confirmation of successful payment from the Main System, via the Network.
  • the method includes the user device processor with UA executing the instructions related to the communication, causing the communication to be displayed on the user device interface.
  • the method includes a Main System processor with software sending communication to the recipient (e.g. an email, an SMS message) notifying them of the payment made to them by the user, via the Network.
  • the method includes the communication containing a link (e.g. an internet-based link) that, when actioned by the recipient, begins method C.
  • a link e.g. an internet-based link
  • the method includes the Main System with processor providing instructions to the recipient's user device to display the identification information provided by the user automatically in the recipient's user device interface.
  • the method includes the Main System with processor providing instructions to the recipient's user device processor with UA to automatically display the communication related to the successful payment made to the recipient from the user, after method C is completed, on the recipient's user device interface.
  • the method includes the UA automatically providing the recipient the option to send a Message to user, provided via the UA via the recipient's user device interface, executed according to method J.
  • the method includes the UA automatically providing the recipient the option to send a receipt related to receiving the payment to the user, provided via the UA via the recipient's user device interface, executed according to method J.
  • the method enables users to financially transact efficiently without using credit cards and related payment systems, helping end credit card debt cycles, as applicable.
  • the method combined with other methods related to financial transactions noted in the Description, enables users to view user account related information and manage financial transactions with one system, saving the user time and cognitive energy.
  • a method that enables financial transactions that are insta-transfers i.e. funds transfers that occur between user accounts at speeds that are only limited by the processing speeds of the respective embodiments of the System, not by processing speeds of external systems (e.g. delays caused by the transaction processing schedules of financial institutions, central bank processing windows, international payments processing windows, other pre-existing, commonly known inter-banking processing windows), whereby an insta-transfer is completed instantly, relative to pre-existing, common funds transfer methods) between user accounts related to the same DTF, is initiated at a user device.
  • the method is illustrated in FIG. 6A and 6E.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes the UA via the interface of a user device, receiving a request related to a financial transaction between user accounts related to the same DTF.
  • the method includes a processor with UA of said user device, preparing authorised instructions related to said request and, with TT, sending said instructions to the Main System via the Network.
  • the method includes the Main System receiving said instructions from said user device via the Network.
  • the method includes a Main System processor with software executing said instructions, causing a plurality of steps to occur, including:
  • an insta-transfer relates to a financial transaction from a system account to a DTF account, causing an intra-transfer (that is, an EFT performed within a DTF) from said system-DTF account, where said system account balance is held, to said DTF account;
  • a Main System processor with software prepares instructions for said DTF to execute and, with TT, sends those instructions to said DTF via the Network;
  • a DTF processor with software executes said instructions, causing an intra- transfer from a first DFT account to a second DTF account;
  • a Main System processor with software prepares instructions for said DTF to execute and, with TT, sends those instructions to said DTF via the Network;
  • a DTF processor with software executes said instructions, causing an intra- transfer from a DTF account to said system-DTF account, where said system account balance is held;
  • an algorithm forming part of the AMS assigns funds related to said insta- transfer to said system account.
  • the method includes a Main System processor with software generating a notification indicating successful completion of said instructions and, with TT, causes said notification to be sent to applicable user devices via the Network.
  • the method includes the UAs via the interface of the applicable user devices displaying said notification.
  • the method includes said request relating to one or more user devices.
  • the method includes viewing user account related information, executed according to methods .
  • the method includes default user accounts pre-selected as part of said request.
  • the method includes a Main System processor with software causing non-financial information related to said instructions to be recorded in the DMS.
  • the method includes a Main System processor with software causing financial transaction information related to said instructions to be recorded in the SAL.
  • the method includes a Main System processor with software causing the sending of purchased items to a physical address when said request relates to such a purchase, with said request including a request to send purchased items to a physical address, said address provided as part of said request, caused to be recorded in the DMS by a Main System processor with software, with associated sending costs calculated by an algorithm forming part of the ESCS, caused to be automatically activated when said request is received by the Main System.
  • the method includes an algorithm forming part of the Main System creating a receipt automatically after a payment is received and, with TT, providing said receipt to applicable user devices.
  • the method enables users to financially transact efficiently without using credit cards and related payment systems, helping end credit card debt cycles, as applicable.
  • the method combined with other methods related to financial transactions noted in the Description, enables users to view user account related information and manage financial transactions with one system, saving the user time and cognitive energy.
  • a method that enables financial transactions that are insta-transfers between user accounts related to different DTFs is initiated at a user device.
  • the method is illustrated in FIG. 6A and 6C.
  • FIG. 6F illustrates a network of DTFs, system-DTF accounts and the role of the AMS in facilitating insta- transfers across said network.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes the UA via the interface of a user device, receiving a request related to a financial transaction between user accounts related to different DTFs.
  • the method includes a processor with UA of said user device, preparing authorised instructions related to said request and, with TT, sending said instructions to the Main System via the Network.
  • the method includes the Main System receiving said instructions from said user device via the Network.
  • the method includes a Main System processor with software executing said instructions, causing a plurality of steps to occur, including:
  • a Main System processor with software preparing instructions for a first DTF to execute (the 'DTF instructions') and, with TT, sending prepared instructions to the first DTF via the Network;
  • a DTF processor with software executing the DTF instructions, causing a funds transfer from the first DTF account to the system-DTF account of a second DTF, where funds of said system account are held;
  • a Main System processor with software causing an algorithm forming part of the AMS to allocate funds equivalent to said funds transfer, from the AMS Reserve to said system account, whose funds are both held at the system-DTF account of the second DTF;
  • a Main System processor with software preparing instructions for a first DTF to execute (the 'DTF instructions') and, with TT, sending prepared instructions to the first DTF via the Network;
  • a DTF processor with software executing the DTF instructions, causing a funds transfer from the first DTF account to the system-DTF account of a second DTF, where funds of the second DTF account are held;
  • a Main System processor with software causing an intra-transfer of funds equivalent to said funds transfer, from the system-DTF account of the second DTF to said DTF account, also held at the second DTF;
  • a Main System processor with software causing a funds transfer from the system-DTF account at a first DTF, where funds of said system account are held, to the system-DTF account of a second DTF, where said DTF account is held;
  • a Main System processor with software causing an intra-transfer of funds equivalent to said funds transfer, from the system-DTF account of the second DTF to said DTF account, also held at the second DTF.
  • the method includes a Main System processor with software generating a notification indicating successful completion of said instructions and, with TT, causes said notification to be sent to applicable user devices via the Network.
  • the method includes the UAs via the interface of the applicable user devices displaying said notification.
  • the method includes said request relating to one or more user devices.
  • the method includes viewing user account related information, executed according to methods H and I, as applicable.
  • the method includes default user accounts pre-selected as part of said request.
  • the method includes a Main System processor with software causing non- financial information related to said instructions to be recorded in the DMS.
  • the method includes a Main System processor with software causing financial transaction information related to said instructions to be recorded in the SAL.
  • the method includes a M ain System processor with software causing the sending of purchased items to a physical address when said request relates to such a purchase, with said request including a request to send purchased items to a physical address, said address provided as part of said request, caused to be recorded in the DMS by a Main System processor with software, with associated sending costs calculated by an algorithm forming part of the ESCS, caused to be automatically activated when said request is received by the Main System.
  • the method includes an algorithm forming part of the Main System creating a receipt automatically after a payment is received and, with TT, providing said receipt to applicable user devices.
  • the method enables users to financially transact efficiently without using credit cards and related payment systems, helping end credit card debt cycles, as applicable.
  • the method combined with other methods related to financial transactions noted in the Description, enables users to view user account related information and manage financial transactions with one system, saving the user time and cognitive energy.
  • a method that enables financial transactions that are insta-transfers with a currency exchange, between user accounts related to different DTFs is initiated at a user device.
  • the method is illustrated in FIG. 6A and 6D.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes the UA via the interface of a user device, receiving a request related to a financial transaction requiring a currency exchange, between user accounts related to different DTFs.
  • the method includes a processor with UA of said user device, preparing authorised instructions related to said request and, with TT, sending said instructions to the Main System via the Network.
  • the method includes the Main System receiving said instructions from said user device via the Network.
  • the method includes a Main System processor with software executing said instructions, causing a plurality of steps to occur, including:
  • a processor with software causing an algorithm forming part of the C ES to calculate the amount of the first type of currency required to transfer a specified amount of the second type of currency, according to the information provided related to said requests;
  • a Main System processor with software preparing instructions for a first DTF to execute (the 'DTF instructions') and, with TT, sending prepared instructions to the first DTF via the Network;
  • a DTF processor with software executing the DTF instructions, causing an intra-transfer of the required amount of the first type of currency from the first DTF account to the system-DTF account of the first DTF, the first DTF's default currency being the first type of currency;
  • a Main System processor with software causing an algorithm forming part of the AMS to allocate funds, in the form of the second type of currency, in an amount calculated according to the CES algorithm, from the AMS Reserve to said system account, whose funds are both held at the system-DTF account of the second DTF;
  • a Main System processor with software preparing instructions for a first DTF to execute (the 'DTF instructions') and, with TT, sending prepared instructions to the first DTF via the Network;
  • a DTF processor with software executing the DTF instructions, causing an intra-transfer of the required amount of the first type of currency from the first DTF account to the system-DTF account of the first DTF, the first DTF's default currency being the first type of currency;
  • AMS Main System processor with software causing the AMS to allocate the required amount to the AMS Reserve held at the system-DTF account of the first DTF;
  • a Main System processor with software causing an intra-transfer to occur from the system-DTF account of the second DTF to the second DTF account, both held at the second DTF, the second DTF's default currency being the second type of currency, transferring said specified amount calculated according to the CES algorithm, utilising funds from the AMS Reserve at the system-DTF account of the second DTF;
  • a Main System processor with software causing the AMS to allocate the required amount of funds of the first type of currency, from said system account to the AMS Reserve, whose funds are both held at the first DTF, the first DTF's default currency being the first type of currency; a Main System processor with software causing an intra-transfer from the system-DTF account at the second DTF to said DTF account, both held at the second DTF, the second DTF's default currency being the second type of currency, transferring said specified amount calculated according to the CES algorithm, utilising funds from the AMS Reserve at the system-DTF account of the second DTF.
  • AMS Main System processor with software causing the AMS to allocate the required amount of funds, in the form of the first type of currency, from said system account to the AMS Reserve, whose funds are both held at the system-DTF account of the first DTF;
  • a Main System processor with software causing an algorithm forming part of the AMS to allocate funds, in the form of the second type of currency, in an amount calculated according to the CES algorithm, from the AMS Reserve to said system account, whose funds are both held at the system-DTF account of the second DTF.
  • the method includes a Main System processor with software generating a notification indicating successful completion of said instructions and, with TT, causes said notification to be sent to applicable user devices via the Network.
  • the method includes the UAs via the interface of the applicable user devices displaying said notification.
  • the method includes said request relating to one or more user devices.
  • the method includes viewing user account related information, executed according to methods H and I.
  • the method includes default user accounts pre-selected as part of said request.
  • the method includes a Main System processor with software causing non-financial information related to said instructions to be recorded in the DMS.
  • the method includes a Main System processor with software causing financial transaction information related to said instructions to be recorded in the SAL.
  • the method includes a Main System processor with software causing the sending of purchased items to a physical address when said request relates to such a purchase, with said request including a request to send purchased items to a physical address, said address provided as part of said request, caused to be recorded in the DMS by a Main System processor with software, with associated sending costs calculated by an algorithm forming part of the ESCS, caused to be automatically activated when said request is received by the Main System.
  • the method includes an algorithm forming part of the Main System creating a receipt automatically after a payment is received and, with TT, providing said receipt to applicable user devices.
  • the method enables users to financially transact efficiently without using credit cards and related payment systems, helping end credit card debt cycles, as applicable.
  • the method combined with other methods related to financial transactions noted in the Description, enables users to view user account related information and manage financial transactions with one system, saving the user time and cognitive energy.
  • the method enables international payments to be completed more than common international payment systems.
  • a method that enables authorised users, that have been provided an interfacing object by the System, to select or change the user account linked to the object is initiated at a user device.
  • the method is referred to as method 'S'.
  • the method is illustrated in FIG. 9A.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes the user viewing that same user's account related information, executed according to methods H and/or I.
  • the method includes the user selecting the account to be assigned to the object via the UA via the user device interface.
  • the method includes the user device processor with UA preparing instructions for a Main System processor with software to execute, in relation to the user account selection.
  • the method includes the user device sending the instructions to the Main System, via the Network.
  • the method includes the Main System receiving the instructions from the user device, via the Network.
  • the method includes a Main System processor with software selecting or changing the user account linked to the object in the DMS, corresponding to the user's initial instructions provided to the UA via the user device interface.
  • the method includes a Main System processor with software preparing instructions and communication for the user device processor with UA to execute, in relation to the successful user account selection or change.
  • the method includes the Main System sending the instructions and
  • the method includes the user device receiving the instructions and communication from the Main System, via the Network.
  • the method includes the user device processor with UA executing the instructions, including causing the communication to be displayed on the user device interface.
  • the method enables a user to only require one card to facilitate financial transactions using non-System payment system, for all user accounts, including credit card and debit card accounts associated to the user, linked to the System, instead of a common method of separate cards for each DTF a user has an account with.
  • a method that enables an authorised user that has been provided an interfacing object by the System, to pay for goods or services using the interfacing object with non-System payment systems is initiated at a non-System payment terminal.
  • the method is illustrated in FIG. 9B.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes the requestor initiating the request for payment via the UA, via the user device interface.
  • the method includes the user presenting the interfacing object to said terminal.
  • the method includes said terminal detecting the interfacing object via the technology said terminal utilises (e.g. NFC technology, magnetic stripe technology, EMV technology).
  • the method includes the user providing security information to said payment system related to the interfacing object.
  • the method includes said terminal and related software verifying the security information with the interfacing object, via the technology the payment tenninal utilises to communicate with the interfacing object.
  • the method includes said tenninal processing the payment according to said payment system's methodology, including causing said payment system to verify that the account linked to the interfacing object has sufficient funds to approve the payment, via the Network.
  • the method includes the Main System receiving the request to confirm there are sufficient funds corresponding to the user account linked to the interfacing object, via the Network.
  • the method includes a Main System processor with software confirming with the SAL or DTF via the Network, as applicable to the user account assigned to said interfacing object, that there are sufficient funds corresponding to said user account linked to the interfacing object.
  • the method includes the Main System sending a reply notification to said payment system via the Network (e.g. that there are sufficient funds in the user account linked to the interfacing object, that there are not sufficient funds in the user account linked to the interfacing object).
  • the method includes the user instructing to change said linked account via the UA via the user device interface, executed according to method S, when requested to by the user, executed according to method G.
  • the method includes an exchange of currency if the supplier of the goods or services requires payment in a different currency, executed according to method K.
  • the method includes the currency exchange method executed automatically (e.g. without the user manually providing the amount to be converted, with the user previously instructing the System to complete all currency exchanges automatically) when the user has previously requested the System to do so, via the UA via the user device interface.
  • the method enables a user to only require one card to facilitate financial transactions using non-System payment system, for all user accounts, including credit card and debit card accounts associated to the user, linked to the System, instead of a common method of separate cards for each DTF a user has an account with.
  • a method that enables an authorised user that has been provided an interfacing object by the System to pay for goods or services using said interfacing object with non-System payment systems is initiated at a payment gateway.
  • the method is illustrated in FIG. 9B.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes the requestor initiating the request for payment via the UA, via the user device interface.
  • the method includes the user providing the unique identifiers of the interfacing object to the payment gateway via the user device interface.
  • the method includes said payment gateway recognising aid interfacing object's unique identifiers.
  • the method includes the payment gateway verifying the processing the payment, including causing said payment system to verify that the account linked to the interfacing object has sufficient funds to approve the payment, via the Network.
  • the method includes the Main System receiving the request to confirm there are sufficient funds corresponding to the user account linked to said interfacing object, via the Network, executed according to method G.
  • the method includes a Main System processor with software confirming with the SAL or DTF via the Network, that there are sufficient funds corresponding to the user account linked to said interfacing object.
  • the method includes the Main System sending a reply
  • the method includes the Main System sending a reply notification to said payment system via the Network (e.g. that there are sufficient funds in the user account linked to the interfacing object, that there are not sufficient funds in the user account linked to the interfacing object).
  • the method includes the user instructing to change the linked account via the UA via the user device interface, executed according to method S, when requested to by the user.
  • the method includes an exchange of currency if the supplier of the goods or services requires payment in a different currency, executed according to method K.
  • the method includes the currency exchange method executing automatically (e.g.
  • the method includes said payment system completing the financial transaction according to said payment system
  • the method enables a user to only require one card to facilitate financial transactions using non-System payment system, for all user accounts associated to the user, including credit card and debit card accounts associated to the user, linked to the System, instead of a common method of separate cards for each DTF a user has an account with.
  • a method that enables an authorised user that has been provided an interfacing object by the System to withdraw funds from an Automatic Teller Machine (ATM) is initiated at an ATM.
  • the method includes executing a commonly known process and methodology of withdrawing funds from an ATM using an interfacing object (e.g. a credit card, a debit card).
  • the method includes an exchange of currency, executed according to method K if the ATM issues a different currency to those funds held in the user account linked to the interfacing object.
  • the method includes the currency exchange method executing automatically (e.g. without the user manually providing the amount to be converted, with the user previously instructing the System to complete all currency exchanges automatically) when the user has previously requested the System to do so, via the UA via the user device interface.
  • the method enables a user to only require one card to withdraw funds from an ATM, for all user accounts associated to the user, linked to the System, instead of a common method of separate cards for each DTF a user has an account with.
  • a method that enables an authorised user (the 'requestor') to request payments from another entity is initiated at a user device.
  • the method is referred to as method 'T'.
  • the method is illustrated in FIG. 7.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes the requestor initiating the request for payment via the UA, via the user device interface.
  • the method includes the requestor selecting the entity to request payment from (the 'payer'), executed according to methods E or F, depending on whether the payer is a registered user of the System .
  • the method includes the requestor selecting one or more payer via the UA, as applicable to the requirements of the requestor, via the UA via user device interface.
  • the method includes the requestor selecting a user account for funds to be paid into via the UA, via the user device interface.
  • the method includes the user viewing user account related information, executed according to methods H and/or I, depending on the type of user account.
  • the method includes the UA providing the requestor the option to select a user account for payment related transactions before the transaction has commenced (e.g. a user setting executed via the UA via the user device interface that, once set in the user settings, selects the selected user account as the default account used for payments, causing consequential account selection related to payment requests to be automatic, saving a user time).
  • the method includes the user selecting the user account, executed according to method G.
  • the method includes the user providing the amount requested to be paid via the UA, via the user device interface.
  • the method includes the requestor selecting how much the payer is requested to pay, as applicable to the requirements of the requestor, via the UA, via the user device interface.
  • the method includes the UA providing the requestor the option to send a Message to the payer, provided via the UA, via the user device interface, to accompany the payment, executed according to method J.
  • the method includes the UA providing the requestor the option to provide an invoice, when the request for payment is related to a business transaction, via the UA via the requestor's user device interface.
  • the method includes the user device processor with UA preparing instructions for a Main System processor with software to execute, related to the payment request.
  • the method includes the user device sending the instructions to the Main System, via the Network.
  • the method includes the Main System receiving the instructions from the user device, via the Network.
  • the method includes a Main System processor with software executing the instructions, including causing instructions and related communication to be prepared for the payer user device with UA to execute, related to the request for payment.
  • the method includes the Main System sending the instructions and related communication to the payer's user device, via the Network.
  • the method includes the payer's user device receiving the instructions and related communication from the Main System, via the Network, applicable for payers that are registered users of the System.
  • the method includes the payer's user device with UA executing the instructions, including causing the communication to be displayed on the payer's user device interface, when the payer is a registered user of the System.
  • the method includes the Main System sending communication (e.g.
  • the method includes the payer's user device receiving the communication via the Network for payers that are not registered users of the System.
  • the method includes the communication received by the payer's user device containing a 'call-to-action' instruction, for payers that are not registered users of the System.
  • the method includes the call-to-action instruction launching a computer program, when executed, on the payer's user device that enables payers to register as a user, according to the method C, for payers that are not registered users of the System.
  • the method includes the communication displayed on the user device interface containing a 'call-to-action' instruction (e.g.
  • the method includes the payer activating the instruction, via the payer's UA, via the payer's user device interface, that instructs the user device processor with UA to execute payment instructions for a Main System processor with software to execute, associated with the request for payment.
  • the method includes executing methods M or N, depending on the user accounts selected by the payer and requestor.
  • the method includes executing method D, before payment instructions are executed by the user device processor with UA.
  • the method includes the payer selecting the account from which to pay via the UA via the payer's user device interface.
  • the method includes the UA providing the payer the option to select one of the payer's user accounts for payment related transactions before the transaction has commenced (e.g.
  • the method includes the user selecting the user account, executed according to method G.
  • the method includes the UA providing the payer the option to send a Message to user, provided via the UA via the payer's user device interface, executed according to method J.
  • the method includes the UA providing the payer the option to send a receipt related to receiving the payment to the requestor, provided via the UA via the payer's user device interface, executed according to method J.
  • the method enables users a convenient way to collect debt.
  • a method that enables a user to save funds is initiated at a user device.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes executing method G when the user requests to save funds via the UA via the user device interface, subject to the methodology noted in this paragraph.
  • the method includes an authorised user requesting to save funds and providing information related to said request according to method G (e.g.
  • the method includes the user providing instructions related to saving a fixed amount (e.g.
  • the method includes the user providing instructions related to saving a regular amount related to payments made by the user (e.g.
  • the method includes the user providing instructions related to saving a regular amount related to funds received by the user (e.g.
  • selecting a user account whose funds received by the user are referenced by a Main System processor with software, related to saving funds in this manner (the 'receiving account'); selecting an amount that is less than the received funds, rounded down to an amount that is whole unit of currency, instructing that the difference between the received amount and the selected amount to be transferred from the receiving account to the selected user account, executed according to methods O, P or Q depending on the types of user account; providing a date when saving funds in this manner may conclude) via the UA, the user device interface.
  • the method includes the user instructing to save funds to another user's account (e.g.
  • the method includes the user device processor with UA preparing instructions for a Main System processor with software to execute related to saving funds, via the Network.
  • the method includes the user device sending the instructions related to saving funds to the Main System, via the Network.
  • the method includes the Main System receiving the instructions related to saving funds from the user device, via the Network.
  • the method includes a Main System processor with software executing the instructions, causing the DMS to record the settings associated with the savings rules.
  • the method includes a Main System processor with software executing the instructions, including causing the DMS to record the user instructions related to saving funds.
  • the method includes the Main System with software causing a transfer to occur, executed according to methods L, M or N depending on the types of user accounts, executed according to the schedule associated with the user's instructions related to saving funds.
  • the method includes the user requesting the account balance of the user account selected by the user to save funds into, executed according to methods H or I, depending on the type of user account.
  • the method includes the user requesting a report on the time to reach their savings goal, executed according to method G. The method enables a quicker and more convenient way for a user to set up and begin saving funds than some common methods.
  • a method that enables the facilitation of loans between users is initiated at a user device.
  • the method is illustrated in FIG. 10A.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes executing method G when users make requests related to the lending or borrowing of funds via the UA via the user device interface, subject to the methodology noted in this paragraph.
  • the method includes an authorised user requesting to borrow funds (a 'borrower') via the UA via the user device interface.
  • the method includes the borrower providing borrowing information related to the loan request (e.g.
  • the method includes the borrower's user device processor with UA preparing instructions related to the borrowing request, for the Main System with software to execute, via the borrower's UA via the user device interface and with TT, sending the instructions related to the borrowing request to the Main System, via the Network.
  • the method includes the Main System receiving the instructions related to the borrowing request from the borrower's user device, via the Network.
  • the method includes a Main System processor with software executing the instructions related to the borrowing request, including storing information related to the borrowing request in the DMS.
  • the method includes a Main System processor with software causing an algorithm forming part of the CS to confirm the creditworthiness of the borrower associated with the borrowing request and related borrowing information.
  • the method includes a Main System processor with software preparing instructions and communication to send to the lenders' user devices, to notify lenders of the borrowing request when the CS confirms that the borrower is creditworthy and, with TT, sending the instructions and related communication to the lenders' user devices to notify lenders of the borrowing request, via the Network.
  • the method includes the lenders' user devices receiving the instructions and communication from the Main System related to the borrowing request, via the Network.
  • the method includes the lenders' user device processors with UAs executing the instructions, including causing the communication related to the borrowing request to be displayed on the lenders' at the UA via the user device interfaces.
  • the method includes a Main System processor with software preparing instructions and
  • the method includes a borrower's user device processor with UA executing the instructions, including causing the communication notifying said borrower is not creditworthy, to be displayed at the UA via the user device interface.
  • the method includes an authorised user requesting to lend funds (a 'lender') via the UA via the user device interface.
  • the method includes the lender providing lending information related to the lender's request (e.g.
  • the method includes the lender's user device processor with UA preparing instructions related to the lending request for a Main System processor with software to execute, via the lender's UA via the user device interface and, with TT, sending the instructions related to the lending request to the Main System, via the Network.
  • the method includes the Main System receiving the instructions related to the lending request from the lender's user device, via the Network.
  • the method includes a Main System processor with software executing the instructions, including storing information related to the lender's requests in the DMS.
  • the method includes enabling a plurality of lenders making funds available to be loaned at any one time.
  • the method includes a Main System processor with software preparing instructions and communication to send to the lenders' user devices, to notify lenders of the borrowing request and, with TT, sending the instructions and related communication to the lenders' user devices to notify lenders of the borrowing request, via the Network.
  • the method includes the lenders' user devices receiving the instructions and communication from the Main System related to the borrowing request, via the Network.
  • the method includes the lenders' user device processors with UAs executing the instructions, including causing the communication related to the borrowing request to be displayed on the lenders' at the UA via the user device interfaces.
  • the method includes the communication containing a call-to-action instruction, enabling a lender to notify the borrower that the lender is interested in lending to the borrower (referred to as an 'expression of interest').
  • the method includes a lender executing the call-to-action instruction via the lender's user device interface which executes a plurality of functions depending on the lender's preferences (e.g.
  • the method includes the lender and borrower communicating with each other in order to agree on loan tenns (e.g. loan term, repayment amount, repayment frequency, associated fees and charges), executed according to method J.
  • the method includes the lender and borrower not agreeing on loan tenns, causing the processors with U As of the respective user devices to prepare instructions related to the re-notification of other lenders of the borrowing request and, with TT, send said instructions to the Main System to execute via the etwork, executed according to the method according to the first notification sent to lenders regarding the borrowing request, previously outlined in this paragraph.
  • the method includes the lender and borrower agreeing on loan terms, executed according to method J.
  • the method includes the borrower and lender user device processors with U As preparing instructions related to the settlement of the loan for a Main System processor with software to execute.
  • the method includes the lender and borrower user devices with use apps sending instructions related to the settlement to the Main System, via the Network.
  • the method includes the Main System receiving the instructions related to the settlement from the user devices, via the Network.
  • the method includes a Main System processor with software executing the instructions related to the settlement (e.g.
  • the method enables a quicker way for lenders to transfer funds to be loaned to borrowers, than common methods of using EFT methodology or withdrawing cash from an ATM.
  • the method enables a quicker way for lenders to be registered to lend, in comparison to some other peer to peer lending methods.
  • a method that enables lenders to lend elected funds to borrowers via a loan fund is initiated at a user device.
  • the method is illustrated in FIG. 10B.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes executing method G when the user provides requests related to the lending or borrowing of funds via the UA via the user device interface, subject to the methodology noted in this paragraph.
  • the method includes an authorised user requesting to borrow funds (a 'borrower') via the UA via the user device interface.
  • the method includes the borrower providing information related to the loan request (e.g.
  • the method includes the borrower's user device processor with UA preparing instructions related to the borrowing request, for the Main System with software to execute, via the borrower's UA via the user device interface.
  • the method includes the borrower's user device sending the instructions related to the borrowing request to the Main System, via the Network.
  • the method includes the Main System receiving the instructions related to the borrowing request from the borrower's user device, via the Network.
  • the method includes a Main System processor with software executing the instructions related to the borrowing request, including storing information related to the borrowing request in the DMS.
  • the method includes a Main System processor with software causing an algorithm forming part of the CS to confirm the creditworthiness of the borrower associated with the borrowing request and related borrowing information.
  • the method includes a Main System processor with software preparing instructions and communication to send to the lenders' user devices, to notify lenders of the borrowing request when the CS confirms that the borrower is creditworthy and, with TT, sending the instructions and related communication to the lenders' user devices to notify lenders of the borrowing request, via the Network.
  • the method includes the lenders' user devices receiving the instructions and communication from the Main System related to the borrowing request, via the Network.
  • the method includes the lenders' user device processors with UAs executing the instructions, including causing the communication related to the borrowing request to be displayed on the lenders' at the UA via the user device interfaces.
  • the method includes a Main System processor with software preparing instructions and
  • the method includes a borrower's user device processor with UA executing the instructions, including causing the communication notifying said borrower is not creditworthy, to be displayed at the UA via the user device interface.
  • the method includes an authorised user requesting to lend funds (a 'lender') via the UA via the user device interface.
  • the method includes the lender providing information related to the lender's request (e.g. providing an amount of funds the lender elects to lend to borrowers, nominating the user account where the funds to be loaned are recorded) via the UA via the user device interface.
  • the method includes the lender's user device processor with UA preparing instructions related to the lender's request for a Main System processor with software to execute, via the lender's UA via the user device interface.
  • the method includes the lender's user device sending the instructions related to the lender's request to the Main System, via the Network.
  • the method includes the Main System receiving the instructions related to the lender's request from the lender's user device, via the Network.
  • the method includes a Main System processor with software executing the instructions, including storing information related to the lender's requests in the DMS.
  • the method includes a Main System processor with software causing a funds transfer of the lender's elected funds from the nominated user account to a system account where lender elected funds selected to be loaned to borrowers are recorded (the 'loan fund'), executed according to methods L or M, depending on the type of user account.
  • the method includes a Main System processor with software causing the SAL to record a record of the transfer event.
  • the method includes a Main System processor with software causing an algorithm forming part of the CS to review the borrowing request, including whether to fulfil the borrowing request (e.g. accept the borrowing request, provide different loan terms for the borrower to accept, deny the borrowing request).
  • the method includes a Main System processor with software causing with executing the instructions related to the settlement when the borrowing request has been accepted by the credit system (e.g. causing the DMS to record the agreed loan terms; causing the currency exchange system to execute any related currency exchanges; setting up the repayment schedule according to the agreed loan terms, executing related repayments according to methods L or M depending on the type of user account nominated by the borrower).
  • the method includes a Main System processor with software causing the information related to the loan to be recorded in the DMS.
  • the method includes a Main System processor with software preparing instructions and related communication for the borrower's user device processor with software to execute, related to the CS's recommendation on loan terms.
  • the method includes the Main System sending the instructions and related communication to the borrower's user device, via the Network.
  • the method includes the borrower's user device with UA receiving the instructions and communication related to the CS's recommendation from the Main System, via the Network.
  • the method includes the borrower's user device processor with UA executing the instructions, including displaying the communication related to the CS's recommendation to the borrower via the borrower's user device interface (e.g. that the borrowing request has been accepted, providing the borrower different loan terms for the borrower to accept, that the borrowing request has been denied).
  • the method includes the communication displayed on the borrower's user device interface including a call-to-action instruction that, when executed, enables the borrower to accept the different loan terms, as applicable.
  • the method includes the user device processor with UA preparing instructions for a Main System processor with software to execute when the call-to-action instruction, related to the borrower accepting the different loan terms, is executed by the borrower via the user device interface.
  • the method includes the borrower user device with use app sending the instructions related to the settlement associated with the borrower accepting the different loan terms, to the Main System via the Network.
  • the method includes the Main System receiving the instructions related to the settlement from the user device, via the Network.
  • the method includes a Main System processor with software executing the instructions related to the settlement (e.g.
  • the method enables a quicker way for lenders to transfer funds to be loaned to borrowers, than common methods of using EFT methodology or withdrawing cash from an ATM.
  • the method enables a quicker way for lenders to be registered to lend, in comparison to some other peer to peer lending methods.
  • a method that enables an authorised user that is a business that manages an inventory, to manage that same business 's inventory using the IMS is initiated at a user device.
  • the method is referred to as method 'U'.
  • the method is illustrated in FIG. 1 1A.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes executing method G when the business provides instructions related to the IMS via the UA via the business's user device interface, subject to the methodology noted in this paragraph.
  • the method includes the business providing information related to the business's inventory (e.g. e.g.
  • the method includes the business's user device processor with UA preparing instructions to be executed by a Main System processor with software, causing the IMS to record the inventory information.
  • the method includes the business detecting an item having technology identification (e.g. a QR code, NFC tag, bar code, another item related to another type of identification technology) via the UA via the business's user device.
  • the method includes the business providing information related to the detected item via the UA via the business's user device interface (e.g. assigning to the detected item
  • the method includes the business instructing the System to add the detected item and related information to the IMS via the UA via the business's user device interface.
  • the method includes executing the instructions related to the adding of the item and related information according to method G, causing the IMS to record the detected item and related inventory information.
  • the method includes the business being able to detect and add more than one item and related information to the IMS. The method removes the need for a business to require a complex POS terminal, saving said business time and cognitive energy.
  • a method that enables authorised users that are customers to purchase an item that has technology identification e.g. a QR code, NFC tag, bar code, another item related to another type of identification technology
  • the method is illustrated in FIG. 1 1 B.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes executing method G when the customer provides instructions related to purchasing an item via the UA via the customer's user device interface, subject to the methodology noted in this paragraph.
  • the method includes more than one item having technology identification.
  • the method includes an authorised user that is a customer's user device detecting the item via the customer's user device interface.
  • the method includes the customer's user device enabled to detect more than one item via the customer's user device interface at any one time.
  • the method includes the customer selecting a detected item via the customer's UA via the user device interface.
  • the method includes the customer selecting more than one detected item, at the customer's discretion, via the UA via the customer's user device interface.
  • the method includes information related to the detection of items from the IMS via the Network.
  • the method includes the user requesting to pay for selected items via UA via the customer's user device interface.
  • the method includes the user paying for the selected item (or items), executed according to methods L, M or N, depending on the type of user account the customer elects for the payment to be transferred from and the type of account the business elects to have the payment transferred to.
  • the method includes the customer's user device processor with UA preparing other instructions related to the purchase, for a Main System processor with software to execute (e.g. notifying the IMS that the business's items have been selected and paid for by the customer, instructing the IMS to record changes in the business's inventory related to the purchased item (or items), causing an algorithm forming part of the Main System to provide a receipt to the customer related to the purchase).
  • the method removes the need for a business to have a complex POS terminal to manage purchases related to items with technology identification, saving said business time and cognitive energy.
  • a method that enables authorised users that are businesses to receive payments from customers via an interfacing object is initiated at a user device.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes executing method G when the business provides instructions related to customer purchases via the UA via the customer's user device interface, subject to the methodology noted in this paragraph.
  • the method includes the business providing information related to the payment to the UA via the business's user device interface (e.g. executing method U when a customer is purchasing an inventoried item, providing a price and description related to the purpose of the payment to the UA via the business's user device interface).
  • the method includes a customer of the business presenting an interfacing object to make payment to the business's user device.
  • the method includes the business's user device detecting the interfacing object via technology (e.g. NFC technology, magnetic stripe technology, EMV technology).
  • the method includes the business's user device processor with UA utilising other payment systems methods and processes (e.g. via the Network, directly with the interfacing object) to verify security information related to the interfacing object and process the payment (e.g. verify there are sufficient funds in the account linked to the interfacing object and proceed to transfer the payment amount from the linked account to the business's nominated user account).
  • a method that enables authorised users that are businesses to receive payments from authorised users that are customers via technology is initiated at a user device.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes executing method G when the business provides instructions related to customer purchases via the UA via the customer's user device interface, subject to the methodology noted in this paragraph.
  • the method includes the business providing information related to the payment to the UA via the business's user device interface (e.g. executing method U when a customer is purchasing an inventoried item, providing a price and description related to the purpose of the payment to the UA via the business's user device interface).
  • the method includes a customer presenting the user device to the business's user device.
  • the method includes the business's user device detecting the customer's user device via technology (e.g. NFC technology, magnetic stripe technology, EMV technology).
  • the method includes the user receiving a payment request via technology.
  • the method includes the customer executing the payment request according to method T.
  • the method includes the customer using the customer's user device's biometric technology to execute the call-to-action instruction associated with the payment request.
  • the method includes the customer selecting to automatically accept payment upon being detected by the business's user device, executed, by providing related instruction as part of the customer's user settings via the UA via the user device interface, according to method G.
  • the method includes executing payment according to methods L, M or N depending on the types of user accounts.
  • a method that enables authorised users that are businesses to manage and provide rewards to users that are customers is initiated at a user device.
  • the method is illustrated in FIG. 12A - 12B.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes executing method G when a business provides instructions related to customer purchases via the UA via the customer's user device interface, subject to the
  • the method includes a business providing information related to rewarding users that are customers ('rewards information') via the UA via the business's user device interface (e.g. rewarding a customer that purchases a specified number of a specified item, rewarding a customer that spends a specified amount on purchases with the business, setting specific rewards for customers that reach specified milestones, setting ongoing rewards that are points earned by customers that purchase with the business, where those points can be redeemed for items or services according to a scheme established by the business).
  • the method includes the business's user device receiving a request to link items to rewards information managed by the RS, to items in the business's inventory (e.g. those items managed according to method U) via the UA via the business's user device interface.
  • the method includes said business's user device processor with U A preparing instructions related to the rewards information for the RS to record, executed according to method G.
  • the method includes a Main System processor with software causing an algor ithm forming part of the RS to calculate rewards as a function of said rewards information and the relationship of said rewards information with financial transactions performed on the system between said customers and said business.
  • the method includes a Main System processor with software causing an algorithm forming part of the RS to provide rewards to said customers according to the calculations of an algorithm forming part of the RS.
  • the method includes one or more businesses linking to another business's rewards information via the UA via a business's user device interface by the Main System receiving authorised instructions from a first business's user device via the Network, said instructions initiated by a request for a first business to link customer related transactions to a second business's rewards information at the UA via the first business's user device interface, thereby linking the first business customer related transactions to a second business's rewards information for rewarding said customers, already managed by the RS, causing the RS to link the first business's transactions with customers and to provide rewards to the first business's customers, as a function of the second business's rewards information and calculations of an algorithm forming part of the RS, when said customers transact with the first business, subject to the approval of the first business.
  • the method enables businesses to manage rewards without a separate system and associated infrastructure, saving said businesses time and cognitive energy.
  • the method the removal of separate healthcare cards related to healthcare claims, saving patients time and cognitive energy.
  • a method that enables authorised users to facilitate transactions related to healthcare claims is initiated at a user device.
  • the method is illustrated in FIG. 13.
  • the method includes executing methods A and B when information is sent via the Network.
  • the method includes executing method G when users make requests related to healthcare claims via the UA via the user device interface, subject to the methodology noted in this paragraph.
  • the method includes a user device that is associated with a user that is a patient of a healthcare provider (e.g. a doctor, a dentist, physiotherapist, another category of registered healthcare professional), receiving a request to add patient ID information to the System (e.g. private health insurance membership number, public health system identification number) and receiving said information via the UA via said user device interface.
  • a healthcare provider e.g. a doctor, a dentist, physiotherapist, another category of registered healthcare professional
  • the method includes a processor with UA of said patient's user device preparing instructions related to the request to add patient ID information and, with TT, sending said instructions and related information to the Main System via the Network.
  • the method includes a user device that is associated with a user that is a healthcare provider, receiving a request to add healthcare provider ID information to the System (e.g. a provider number) and receiving said information, via the UA via said user device interface.
  • the method includes a processor with U A of said healthcare provider's user device preparing instructions related to the request to add healthcare provider ID information and, with TT, sending said instructions and related information to the Main System via the Network.
  • the method includes a user device that is associated with a user that is a healthcare insurer (e.g.
  • the method includes a processor with UA of said healthcare insurer's user device preparing instructions related to the request to add healthcare claims information and, with TT, sending said instructions and related information to the Main System via the Network.
  • the method includes, at the Main System, receiving said instructions and related information via the Network, from said patient's user device and, with a processor and software, causing patient ID information to be added to the CMS.
  • the method includes, at the Main System, receiving said instructions and related information via the Network, from said healthcare provider's user device and, with a processor and software, causing healthcare provider ID information to be added to the CMS.
  • the method includes, at the Main System, receiving said instructions and related information via the Network, from said healthcare insurer's user device and, with a processor and software, causing healthcare claims information to be added to the CMS.
  • the method includes said patient's user device receiving a payment request related to a healthcare claim, via the UA via the user device interface and receiving information related to said payment.
  • the method includes a processor with UA of said patient's user device preparing instructions related to the request to cause a financial transaction to occur and, with TT, sending said instructions and related information to the Main System via the Network.
  • the method includes the Main System receiving instructions and related information related to said payment request from said patient's user device via the Network.
  • the method includes a M ain System processor with software causing an algorithm forming part of the CM S to calculate the claim and related payments as a function of said patient ID information, healthcare provider ID information and healthcare claims information.
  • the method includes a Main System processor with software facilitating payment from the patient to said healthcare provider.
  • the method includes a Main System processor with software facilitating payment from said healthcare insurer to said healthcare provider.
  • the method includes a Main System processor with software causing non-financial information related to the execution of the method caused to be recorded in the CMS.
  • the method includes a Main System processor with software causing financial transaction information related to the execution of the method is caused to be recorded in the SAL.
  • the method includes using default user accounts selected for payments related to healthcare claims according to the user settings related to said patient, healthcare provider and healthcare insurer.
  • the method includes a plurality of healthcare insurers having related healthcare claims information recorded in the CMS.
  • the method includes a plurality of healthcare providers having healthcare provider ID information recorded in the CMS.
  • the method includes a plurality of patients having patient ID information recorded in the CMS.
  • the method includes an algorithm forming part of the CMS verifying the legitimacy of identification information of said patient and healthcare provider, before any steps related to said payment request are executed.
  • the method enables healthcare providers to manage healthcare claims without a separate system and associated infrastructure, saving said healthcare providers time and cognitive energy.
  • the method the removal of separate healthcare cards related to healthcare claims, saving patients time and cognitive energy.

Landscapes

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

Abstract

L'invention concerne des systèmes et procédés facilitant les transactions financières. Selon un mode de réalisation de l'invention, les systèmes et procédés se rapportent à l'exécution de transferts de fonds entre des utilisateurs. Pour agir sur un transfert de fonds, l'utilisateur interagit avec une application utilisateur sur un dispositif utilisateur, et l'application procède à l'envoi d'instructions relatives au transfert souhaité à une plateforme de transfert entre systèmes. La plateforme de transfert amorce le transfert de fonds en fonction du type de transaction, par exemple la plateforme de transfert peut émettre des instructions vers un ou plusieurs établissements de dépôt (DTF) tels qu'une banque, etc. pour transférer des fonds entre des comptes d'utilisateurs, c'est-à-dire effectuer des transferts interbancaires ou intrabancaires, ou pour transférer des fonds d'un DTF à un compte conservé par la plateforme de transfert, ou elle peut amorcer un transfert entre des comptes d'utilisateurs conservés par la plateforme, c'est-à-dire qu'elle amorce un transfert interbancaire entre des comptes de système des utilisateurs prenant part à la transaction.
PCT/AU2016/000132 2016-04-15 2016-04-15 Système de gestion de communications, transactions financières et informations connexes WO2017177253A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/AU2016/000132 WO2017177253A1 (fr) 2016-04-15 2016-04-15 Système de gestion de communications, transactions financières et informations connexes

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/AU2016/000132 WO2017177253A1 (fr) 2016-04-15 2016-04-15 Système de gestion de communications, transactions financières et informations connexes

Publications (1)

Publication Number Publication Date
WO2017177253A1 true WO2017177253A1 (fr) 2017-10-19

Family

ID=60041261

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/AU2016/000132 WO2017177253A1 (fr) 2016-04-15 2016-04-15 Système de gestion de communications, transactions financières et informations connexes

Country Status (1)

Country Link
WO (1) WO2017177253A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111512336A (zh) * 2017-10-13 2020-08-07 株式会社原点方案 兑换系统和汇款系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080319873A1 (en) * 1999-04-30 2008-12-25 Paypal, Inc., System and method for facilitating value exchanges
US20090119212A1 (en) * 2007-11-05 2009-05-07 Ebay Inc. Request money social networking applications
US20090319425A1 (en) * 2007-03-30 2009-12-24 Obopay, Inc. Mobile Person-to-Person Payment System
US20120173422A1 (en) * 2010-12-30 2012-07-05 Ebay Inc. Instant bank fund transfers

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080319873A1 (en) * 1999-04-30 2008-12-25 Paypal, Inc., System and method for facilitating value exchanges
US20090319425A1 (en) * 2007-03-30 2009-12-24 Obopay, Inc. Mobile Person-to-Person Payment System
US20090119212A1 (en) * 2007-11-05 2009-05-07 Ebay Inc. Request money social networking applications
US20120173422A1 (en) * 2010-12-30 2012-07-05 Ebay Inc. Instant bank fund transfers

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111512336A (zh) * 2017-10-13 2020-08-07 株式会社原点方案 兑换系统和汇款系统

Similar Documents

Publication Publication Date Title
US11687895B2 (en) Systems and methods for point of sale deposits
US10885515B1 (en) System and method for canceling a payment after initiating the payment using a proxy card
US11948140B1 (en) Interactive electronic notification
US11727452B1 (en) Invoice financing and repayment
US10332106B2 (en) Systems and methods for expedited automated merchant boarding
US11922495B1 (en) Automatically determining adverse action reason codes
US10346843B2 (en) Systems and methods for cost altering payment services
US20180308073A1 (en) Computerized system for resource deficiency triggered dynamic resource transfer
JP2023543377A (ja) 非接触支払のためのアプリケーション統合
CA3007992A1 (fr) Systeme et methode de traitement de transaction de jeton fonde sur l'emplacement
US11023873B1 (en) Resources for peer-to-peer messaging
US20160110696A1 (en) Bottom of the pyramid pay method and system
US20200160323A1 (en) Transaction system with account mapping
JP7160969B2 (ja) 金融商品取引システム、プログラム及び金融商品取引方法
JP7631551B2 (ja) 暗号通貨を使用した区分された支払い割り当てのための支払い作成プラットフォームと支払い処理プラットフォームとの統合
US11481763B2 (en) Systems and methods for expedited automated merchant boarding
US20200151687A1 (en) Method, System, and Computer Program Product for Processing a Cash Transaction
US20140201060A1 (en) Computer program, system, and method for providing a consumer with immediate access to funds via a hybridized secured line of credit
JP7326536B1 (ja) 情報処理装置、情報処理方法及び情報処理プログラム
CA3082632A1 (fr) Procedes et systemes pour fournir un portefeuille electronique pour la gestion d'elements multimedias cibles bases sur des transactions
KR102010013B1 (ko) 가상결제정보를 이용한 비대면 거래 및 정산 방법, 관리 서버
US11087324B2 (en) Pre-authorized secure resource allocation system
WO2017177253A1 (fr) Système de gestion de communications, transactions financières et informations connexes
US11461761B2 (en) System for conducting transactions independent of point of sale system
US20200265414A1 (en) Methods, systems and computer program products for split payment card account transactions

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 16898156

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 16898156

Country of ref document: EP

Kind code of ref document: A1