US20130332347A1 - Monetary transaction system - Google Patents
Monetary transaction system Download PDFInfo
- Publication number
- US20130332347A1 US20130332347A1 US13/964,707 US201313964707A US2013332347A1 US 20130332347 A1 US20130332347 A1 US 20130332347A1 US 201313964707 A US201313964707 A US 201313964707A US 2013332347 A1 US2013332347 A1 US 2013332347A1
- Authority
- US
- United States
- Prior art keywords
- subscriber
- mobile wallet
- account
- agent
- transaction system
- Prior art date
- Legal status (The legal status 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 status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/085—Payment architectures involving remote charge determination or related payment systems
- G06Q20/0855—Payment architectures involving remote charge determination or related payment systems involving a third party
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/322—Aspects of commerce using mobile devices [M-devices]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/325—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks
- G06Q20/3255—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices using wireless networks using mobile network messaging services for payment, e.g. SMS
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/326—Payment applications installed on the mobile devices
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/405—Establishing or using transaction specific rules
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/101—Access control lists [ACL]
Definitions
- Mobile phones and other digital devices have become increasingly popular in recent years. Many mobile device users use their devices to perform countless different daily tasks. For instance, mobile devices allow users to check email, send and receive instant messages, check calendar items, take notes, set up reminders, browse the internet, play games or perform any number of different things using specialized applications or “apps”. These applications allow mobile devices to communicate with other computer systems and perform a wide variety of network-connected tasks previously not possible with a mobile device.
- Embodiments described herein are directed to monetary transaction system for conducting monetary transactions between transaction system subscribers and other entities.
- the monetary transaction system includes a mobile device configured to run a monetary transaction system application.
- the monetary transaction system also includes a monetary transaction system subscriber that has a profile with the system. The subscriber indicates, via the monetary transaction system application, one or more specified transactions that are to be performed using the monetary transaction system.
- the system further includes a monetary transaction system processor that performs the transactions specified by the subscriber. Performing these transactions includes communicating with a monetary transaction database to determine whether the transaction is permissible based on data indicated in the subscriber's profile.
- the monetary transaction system also includes at least one entity that is to be involved in the specified transaction, where the entity has a profile with the monetary transaction system.
- This entity may be a person, a retail store, an agent or other entity.
- the subscriber may have access to a bank account, or may be an “unbanked user” that does not have access to a bank account.
- the monetary transaction system may be used for many different tasks including enrolling a customer for a mobile wallet, adding a stored value account (either hosted by a mobile wallet platform or a third party), adding a bank or credit union account to a mobile wallet, adding a debit or credit card account to a mobile wallet, depositing funds in a mobile wallet, withdrawing funds from a mobile wallet, paying bills from a mobile wallet, topping up a prepaid mobile account through a mobile wallet, transferring funds through a mobile wallet (nationally or internationally), making in-store purchases using a mobile wallet, and various other tasks as described herein below.
- a stored value account either hosted by a mobile wallet platform or a third party
- adding a bank or credit union account to a mobile wallet
- adding a debit or credit card account to a mobile wallet
- depositing funds in a mobile wallet withdrawing funds from a mobile wallet
- paying bills from a mobile wallet paying bills from a mobile wallet
- topping up a prepaid mobile account through a mobile wallet transferring funds through a
- FIG. 1 illustrates a monetary transaction system architecture in which embodiments described herein may operate.
- FIG. 2 illustrates an alternate example embodiment of a monetary transaction system.
- FIG. 3 illustrates an example data flow for performing a subscriber deposit via a mobile wallet.
- FIG. 4 illustrates an example data flow for performing a subscriber withdrawal via a mobile wallet.
- FIGS. 5A and 5B illustrate example data flows for performing subscriber-to-subscriber and subscriber-to-non-subscriber eMoney transfers via a mobile wallet, respectively.
- FIGS. 6A and 6B illustrate example data flows for performing subscriber-to-subscriber and subscriber-to-non-subscriber international eMoney transfers via a mobile wallet, respectively.
- FIG. 7 illustrates an example data flow for performing a subscriber airtime purchase via a mobile wallet.
- FIG. 8 illustrates an example data flow for performing a subscriber-initiated bill pay via a mobile wallet.
- FIG. 9 illustrates an example data flow for performing a subscriber-initiated retail purchase via a mobile wallet.
- FIGS. 10A and 10B illustrate example data flows for requesting and repaying micro-loans via a mobile wallet, respectively.
- FIG. 11A illustrates an example data flow of a subscriber receiving a direct deposit via a mobile wallet.
- FIG. 11B illustrates an example data flow of a subscriber receiving a governmental welfare payment via a mobile wallet.
- FIG. 12A illustrates an example data flow of an agent administrator distributing eMoney via a mobile wallet.
- FIG. 12B illustrates an example data flow of an agent company making a deposit using a mobile wallet.
- FIG. 13 illustrates an example data flow of an agent company making a withdrawal using a mobile wallet.
- FIG. 14 illustrates an example data flow of a subscriber making a deposit at an agent branch using a mobile wallet.
- FIG. 15 illustrates an example data flow of a subscriber making a deposit with a non-agent using a mobile wallet.
- FIG. 16 illustrates an example data flow of a subscriber making a withdrawal with an agent using a mobile wallet.
- FIG. 17A illustrates an example data flow of a subscriber making a withdrawal from an ATM using a mobile wallet.
- FIG. 17B illustrates an example data flow of a subscriber-to-subscriber money transfer using a mobile wallet.
- FIG. 17C illustrates an example data flow of a subscriber-to-non-subscriber money transfer using a mobile wallet.
- FIG. 18A illustrates an example data flow of a subscriber-to-subscriber international money transfer using a mobile wallet.
- FIG. 18B illustrates an example data flow of a subscriber-to-non-subscriber international money transfer using a mobile wallet.
- FIG. 19A illustrates an example data flow of a subscriber-to-subscriber international money transfer using a mobile wallet.
- FIG. 19B illustrates an example data flow of a non-subscriber-to-subscriber international money transfer using a mobile wallet.
- Embodiments described herein are directed to monetary transaction system for conducting monetary transactions between transaction system subscribers and other entities.
- the monetary transaction system includes a mobile device configured to run a monetary transaction system application.
- the monetary transaction system also includes a monetary transaction system subscriber that has a profile with the system. The subscriber indicates, via the monetary transaction system application, one or more specified transactions that are to be performed using the monetary transaction system.
- the system further includes a monetary transaction system processor that performs the transactions specified by the subscriber. Performing these transactions includes communicating with a monetary transaction database to determine whether the transaction is permissible based on data indicated in the subscriber's profile.
- the monetary transaction system also includes at least one entity that is to be involved in the specified transaction, where the entity has a profile with the monetary transaction system.
- This entity may be a person, a retail store, an agent or other entity.
- the subscriber may have access to a bank account, or may be an “unbanked user” that does not have access to a bank account.
- the monetary transaction system may be used for many different tasks including enrolling a customer for a mobile wallet, adding a stored value account (either hosted by a mobile wallet platform or a third party), adding a bank or credit union account to a mobile wallet, adding a debit or credit card account to a mobile wallet, depositing funds in a mobile wallet, withdrawing funds from a mobile wallet, paying bills from a mobile wallet, topping up a prepaid mobile account through a mobile wallet, transferring funds through a mobile wallet (nationally or internationally), making in-store purchases using a mobile wallet, and various other tasks as described herein below.
- a stored value account either hosted by a mobile wallet platform or a third party
- adding a bank or credit union account to a mobile wallet
- adding a debit or credit card account to a mobile wallet
- depositing funds in a mobile wallet withdrawing funds from a mobile wallet
- paying bills from a mobile wallet paying bills from a mobile wallet
- topping up a prepaid mobile account through a mobile wallet transferring funds through a
- Embodiments of the mobile transaction system or “mobile wallet platform” described herein may comprise or utilize a special purpose or general-purpose computer including computer hardware, such as, for example, one or more processors and system memory, as discussed in greater detail below.
- Embodiments described herein also include physical and other computer-readable media for carrying or storing computer-executable instructions and/or data structures.
- Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer system.
- Computer-readable media that store computer-executable instructions in the form of data are computer storage media.
- Computer-readable media that carry computer-executable instructions are transmission media.
- embodiments described herein can comprise at least two distinctly different kinds of computer-readable media: computer storage media and transmission media.
- Computer storage media includes RAM, ROM, EEPROM, CD-ROM, solid state drives (SSDs) that are based on RAM, Flash memory, phase-change memory (PCM), or other types of memory, or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store desired program code means in the form of computer-executable instructions, data or data structures and which can be accessed by a general purpose or special purpose computer.
- RAM random access memory
- ROM read-only memory
- EEPROM electrically erasable programmable read-only memory
- CD-ROM Compact Disk Read Only Memory
- SSDs solid state drives
- PCM phase-change memory
- a “network” is defined as one or more data links and/or data switches that enable the transport of electronic data between computer systems and/or modules and/or other electronic devices.
- Transmission media can include a network which can be used to carry data or desired program code means in the form of computer-executable instructions or in the form of data structures and which can be accessed by a general purpose or special purpose computer. Combinations of the above should also be included within the scope of computer-readable media.
- program code means in the form of computer-executable instructions or data structures can be transferred automatically from transmission media to computer storage media (or vice versa).
- computer-executable instructions or data structures received over a network or data link can be buffered in RAM within a network interface module (e.g., a network interface card or “NIC”), and then eventually transferred to computer system RAM and/or to less volatile computer storage media at a computer system.
- a network interface module e.g., a network interface card or “NIC”
- NIC network interface card
- Computer-executable (or computer-interpretable) instructions comprise, for example, instructions which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions.
- the computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code.
- Embodiments described herein may also be practiced in distributed system environments where local and remote computer systems that are linked (either by hardwired data links, wireless data links, or by a combination of hardwired and wireless data links) through a network, each perform tasks (e.g. cloud computing, cloud services and the like).
- program modules may be located in both local and remote memory storage devices.
- cloud computing is defined as a model for enabling on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services).
- configurable computing resources e.g., networks, servers, storage, applications, and services.
- the definition of “cloud computing” is not limited to any of the other numerous advantages that can be obtained from such a model when properly deployed.
- cloud computing is currently employed in the marketplace so as to offer ubiquitous and convenient on-demand access to the shared pool of configurable computing resources.
- the shared pool of configurable computing resources can be rapidly provisioned via virtualization and released with low management effort or service provider interaction, and then scaled accordingly.
- a cloud computing model can be composed of various characteristics such as on-demand self-service, broad network access, resource pooling, rapid elasticity, measured service, and so forth.
- a cloud computing model may also come in the form of various service models such as, for example, Software as a Service (“SaaS”), Platform as a Service (“PaaS”), and Infrastructure as a Service (“IaaS”).
- SaaS Software as a Service
- PaaS Platform as a Service
- IaaS Infrastructure as a Service
- the cloud computing model may also be deployed using different deployment models such as private cloud, community cloud, public cloud, hybrid cloud, and so forth.
- a “cloud computing environment” is an environment in which cloud computing is employed.
- the functionally described herein can be performed, at least in part, by one or more hardware logic components.
- illustrative types of hardware logic components include Field-programmable Gate Arrays (FPGAs), Program-specific Integrated Circuits (ASICs), Program-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), and other types of programmable hardware.
- FPGAs Field-programmable Gate Arrays
- ASICs Program-specific Integrated Circuits
- ASSPs Program-specific Standard Products
- SOCs System-on-a-chip systems
- CPLDs Complex Programmable Logic Devices
- system architectures described herein can include a plurality of independent components that each contribute to the functionality of the system as a whole.
- This modularity allows for increased flexibility when approaching issues of platform scalability and, to this end, provides a variety of advantages.
- System complexity and growth can be managed more easily through the use of smaller-scale parts with limited functional scope.
- Platform fault tolerance is enhanced through the use of these loosely coupled modules.
- Individual components can be grown incrementally as business needs dictate. Modular development also translates to decreased time to market for new functionality. New functionality can be added or subtracted without impacting the core system.
- agent is used to refer to an individual with mobile financial services (mFS) transaction system tools and training to support specific mFS functions. These mFS functions include subscriber registration and activation, and the deposit and withdrawal of funds from the mFS transaction system. Agents are representatives of the mFS transaction system or “program”. Agents can be employees or contractors of the program provider, or other companies and organizations that partner with the program provider to provide these services themselves. Agents may be found in every facet of a typical economy, and may include large retailers, mobile network operators (MNO) airtime sales agents, gas stations, kiosks, or other places of business.
- MNO mobile network operators
- the mobile wallet platform includes a mobile wallet application, web interface or some other type of functionality that allows the user to interact with the mFS platform using their mobile device.
- the mobile wallet application may include a subscriber identity module (SIM) application, an Unstructured Supplementary Service Data (USSD) application, a smartphone application, a web application, a mobile web application, a Wireless Application Protocol (WAP) application, a Java 2 Platform, Micro Edition (J2ME) application, a tablet application or any other type of application or interface that provides tools for the agent to register, activate, and offer other services to the mFS subscriber.
- SIM subscriber identity module
- USB Unstructured Supplementary Service Data
- WAP Wireless Application Protocol
- J2ME Java 2 Platform, Micro Edition
- a mobile wallet application is a mobile wallet application installed on a SIM card.
- a USSD application is an application that implements USSD for various functionality including prepaid callback service, location-based content services, menu-based information services and other mobile wallet platform services.
- a web application is one that implements or uses the internet to provide mobile wallet platform functionality.
- a mobile web application is similar to a web application, but is tailored for mobile devices.
- a WAP application is one that uses the wireless application protocol to communicate with the mobile wallet platform to provide the platform's functionality.
- a J2ME application is an application developed in Java and is designed to provide mobile wallet functionality on a variety of different hardware.
- a tablet application is an application specifically designed for a touchscreen-based tablet that provides mobile wallet platform functionality for tablet devices, and as part of configuring the phone on the network. Any of these applications (or any combination thereof) may be provided on the user's mobile device. This functionality can also be made available on a retail point of sale (POS) system or web site.
- POS point of sale
- agent administrator refers to an individual with mFS program tools and training to administrate the allocation of funds to agent branches (e.g. retail locations).
- agents perform mFS transactions with subscribers, such as depositing and withdrawing money, the agents are adding and removing money from their own accounts. If there are insufficient funds in the agent's account to complete a transaction, additional money will need to be transferred from the agent company's master account to that agent branch account to cover that transaction.
- An agent administrator is responsible for these funds transfers.
- Any of the applications referred to above may be configured to provide tools used by the agent administrator to view the agent company balance, view the agent branch balances, and transfer funds into and out of agent branch mobile wallets. This functionality can also be made available on a website for easier access.
- agent administrator mobile wallet application refers to a software program or application installed on the agent administrator's terminal in the agent administrator's mobile device (such as a mobile phone or tablet). This software application provides the agent administrator the ability to securely perform agent administrator functions such as querying the agent company account balance or transferring funds into and out of agent branch accounts.
- the agent administrator's mobile wallet application may be installed on a global system for mobile communications (GSM) SIM card (or on any other type of SIM card), and may be accessed using a GSM mobile phone.
- GSM global system for mobile communications
- the agent administrator's application may also be installed on a code division multiple access (CDMA) mobile phone, a 3G, 4G, 4G LTE (Long Term Evolution) or other wireless carrier standard.
- CDMA code division multiple access
- the application may, additionally or alternatively, be installed directly on the agent administrator's mobile device.
- the application communicates with the mFS transaction system using binary and/or text short message service (SMS) messages.
- SMS short message service
- a wireless service provider or MNO provides the GSM SMS network infrastructure on which the mFS platform operates.
- the mFS platform application may utilize triple data encryption standard (3DES) encryption (or some other type of encryption), encrypted message signing, and password security on some or all of its communications with the mFS transaction system in order to ensure that the transactions are properly secured and authenticated.
- 3DES triple data encryption standard
- agent branch refers to any location where an agent provides support for subscriber services of the mFS platform. Funds are allocated by the agent administrator from the agent company's main account to each agent branch to fund the subscriber mFS functions such as depositing or withdrawing cash, in-store purchases, bill payments, prepaid airtime top-ups and money transfers. In some cases, multiple agents may work in a single branch. However, at least in some cases, monetary funds are allocated to from the agent company's main account on a per branch basis.
- agent branch account balance refers to the amount of money residing in a particular agent branch account at a given time. Funds can be deposited into the branch account by the agent administrator, or the funds can come from participating in subscriber mFS transactions such as depositing or withdrawing cash from the subscriber's mobile wallet accounts, or making retail purchases with the mobile wallet.
- Each agent branch is to maintain a balance in their branch account. This applies more strongly in countries where mFS program and financial services infrastructure is still developing. In cases where real-time processing of financial transactions including card processing is not practical, subscribers leverage the applications on their mobile phones to submit transactions and conduct business with retailers, businesses, and other subscribers.
- the mFS platform manages the balance of mobile wallet accounts for each subscriber as value is transferred from one mobile wallet to another (e.g. from a subscriber's mobile wallet to an agent's mobile wallet in payment for goods or services). This value is referred to herein as “eMoney”.
- mFS agents As subscribers conduct business with mFS agents, they deposit or withdraw cash from their mobile wallet accounts. Virtual or eMoney credits are transferred between the subscriber's mobile wallet account and the agent branch's account as a form of currency to support the transaction. As agents accept cash into their cash register by mFS subscribers, they transfer the equivalent amount of eMoney credits into the mFS subscriber's mobile wallet account. For instance, if an mFS subscriber gives an mFS agent $10 to deposit into the subscriber's mobile wallet account, the agent would place the cash into his register and transfer $10 from the agent branch's eMoney account into the subscriber's mobile wallet account. While the agent acquired $10 in his register, he transferred out $10 of eMoney credits from his branch eMoney account.
- pre-paid debit cards in countries with more developed economies, it may be beneficial to use program-issued pre-paid debit cards, pre-paid access accounts, stored value accounts or gift cards to conduct business along with the added convenience of card processing networks such as Cirrus, STAR, or Visa for POS and automated teller machine (ATM) functionality.
- Agents particularly those in retail outlets and kiosks, can still support subscribers with deposits, withdrawals, and other transfers, but in this case bank external card processors manage the mobile wallet and branch account balances and provide the real-time transfer of funds.
- agent branch ledger refers to a written (or electronic) ledger maintained by the mFS platform. Agent branch transactions are performed on the agent's and subscriber's mobile phones where an electronic record of the transaction is generated and stored on the mFS platform. These electronic transactions are then reconciled with agent branch ledgers to ensure the security and integrity of the transaction. Agent branch ledgers are printed or electronic transaction logs that are distributed to the agent branch locations in hard copy form to serve as a backup record to the electronic transactions.
- agent company refers to a business that registers to participate in the mFS program as a partner of the mFS program provider or owner.
- the agent company has one or more agent branches which conduct mFS business with mFS program subscribers.
- the agent company may be referred to as a distributor or retailer.
- agent company account balance refers to the sum of the funds deposited at a “partner bank” (defined below) by the agent company to fund the agent company's daily transactions.
- the funds in the agent company account are then distributed to agent branches by the agent company's agent administrator to conduct everyday business such as accepting cash deposits and cash withdrawals from mFS subscribers. This balance is sometimes referred to as the “agent company float”.
- agent manager is a supervisor of company agents for a given company.
- the agent manager has the training and tools to create, delete or modify agent accounts for a company, as well as monitor the transactions performed by agents.
- the agent manager may have a special application or an increased level of rights to access applications features not available to other users.
- the special application is a program installed on the agent manager's terminal. This application provides the agent manager the ability to securely perform agent manager functions such as registering and activating new agent accounts.
- the mFS agent manager application may be installed on any terminal or device. It communicates with the mFS platform using binary and/or text SMS messages.
- a wireless service provider or MNO provides the GSM SMS network infrastructure on which the mFS platform operates.
- the mFS platform mobile wallet applications may utilize 3DES encryption (or any other type of encryption), encrypted message signing, and password security on some or all of its communications with the mFS platform in order to ensure that the transactions are properly secured and authenticated.
- agent application refers to an application that provides all the tools necessary for an agent to register, activate, and offer other services to the mFS subscriber.
- the agent application is a program installed on the agent's SIM card or otherwise installed in the agent's mobile device's memory. This application provides the agent the ability to securely perform agent functions such as registering and activating new subscribers and depositing and withdrawing funds from mobile wallet accounts.
- the mFS agent application may be installed on a GSM SIM card or mobile phone and may be accessed using a GSM or CDMA mobile phone.
- a wireless service provider or MNO provides the data and SMS network infrastructure on which the mFS platform operates.
- mFS platform refers to an overall platform or ecosystem of different components that work together to provide the various functions described herein on a global scale. At least some of the various logic components include the following: the application.
- the “mobile wallet application” or “mFS application” manages the processing of incoming transactions regardless of their source. The application handles end-user authentication, transaction processing, subscriber profile management, and further manages interactions between the various platform components.
- the mFS platform further includes a transaction processor. This component is used when the mFS application is implemented in a country where real-time processing of financial transactions is not practical (or not possible).
- the transaction processor manages the balance of mobile wallet accounts, agent accounts, and the accounts of any other program participant.
- the transaction processor handles balance inquiries, credits, debits, and transaction roll-backs.
- the mFS platform further includes a rules engine that manages and applies the rules and policy that are defined for transactions as they are processed on the mFS platform. Rules impact transaction fees, limits, velocity limits, and commissions as well as program actor roles and permissions. Rules can be customized for each implementation.
- the mFS platform also includes an integration interface that manages the integration and interaction between external systems (i.e. external to the mFS platform) and the mFS platform. Connectivity to the wireless service provider's pre-paid airtime billing platform and the program partner bank, for example, are managed by the integration interface.
- the mFS platform further includes a transaction database that stores the data that supports the mFS platform. This includes subscriber profiles and subscription data, transaction data and logs, and application configuration and run-time data, among other types of data.
- Another component of the mFS platform is a handset support service that interfaces with the wireless service provider's SMS network to allow communication between the mobile wallet applications and the back-office systems via SMS messaging or some other form of data transfer.
- another component of the mFS platform is a web component that provides a web interface to the mFS program participants that allows the subscriber to perform the same functions in the web interface that they would have available through their applications.
- bill pay company refers to a business that signs-up to participate in the mFS transaction system. As a participant in the mFS transaction system, the company accepts payment from mFS mobile wallet accounts, either in the form of eMoney or through periodic settlements.
- financial transactions that take place in the mFS mobile wallet platform are funded through pre-paid mobile wallet accounts.
- Mobile wallet platform subscribers can deposit cash into their mobile wallet account through a process referred to herein as ‘cash-in’.
- the cash-in process is supported by mFS agents at agent branch locations. The agent accepts the cash from the subscriber and transfers the equivalent amount of eMoney to the subscriber's mobile wallet account. This process is similar to withdrawing cash from a bank account.
- financial transactions that take place in the mobile wallet platform are funded through pre-paid mobile wallet accounts.
- Mobile wallet platform subscribers can withdraw cash from their mobile wallet account through a process known as “cash-out”.
- the cash-out process is supported by mFS agents at agent branch locations.
- the subscriber transfers eMoney from their mobile wallet account to the agent's eMoney account.
- the agent Upon receiving the eMoney, the agent gives the subscriber cash from their branch cash register.
- Accounts managed on the mFS platform by the mFS eMoney transaction processor maintain the mobile wallet balance of mFS program participants including subscribers, agent branches, agent companies, and non-agent companies. eMoney is moved between Mobile Wallet accounts by the transaction processor based on mFS transaction processing. Only when transactions involving cash (i.e. depositing or withdrawing funds from the mFS program) or the movement of money from mFS participants to non-mFS program participants are funds moved from the master bank accounts.
- value is transferred from one account to the next as payment for services rendered or goods purchased.
- This value can be in the form of real currency or the electronic representation referred to herein as eMoney.
- eMoney is used in mFS implementations where the real-time processing of financial transactions including card processing is not practical.
- the mFS platform utilizes an internal transaction processor for managing the real-time balance of mobile wallet and agent accounts as value (eMoney) is transferred from one mobile wallet to another in payment for services.
- mFS agents As subscribers conduct business with mFS agents, they deposit or withdraw cash from their mobile wallet accounts. Virtual or eMoney credits are transferred between the subscriber mobile wallet accounts and the agent branch accounts as a form of currency to support the transaction. As agents accept cash into their cash register by mFS subscribers, they transfer the equivalent amount of eMoney credits into the mFS subscriber's mobile wallet account. For example, if an mFS subscriber gives an mFS agent $10 to deposit into the subscriber's mobile wallet account, the agent would place the cash into his or her register, and transfer $10 from the agent branch eMoney account into the subscriber's mobile wallet account. While the agent acquired $10 in his or her register, the agent transferred-out $10 of eMoney credits from his or her branch eMoney account. This will be explained in greater detail below.
- employers may wish to participate in the mFS program by allowing the direct deposit of paychecks into subscribers' mobile wallet accounts. Accordingly, each payday, the user's pay is directly transferred to the subscribers' mobile wallet.
- KYC knowledge your customer
- MFI micro-finance institution
- mFS program like the term “mFS platform” refers to the ecosystem of companies, service providers, and subscribers that participate in providing mobile financial services to their customers. In some embodiments, there may be one mFS program implementation per country. Each program includes a program owner and operator, a program platform, a partner wireless services provider or MNO, and a partner bank.
- mFS program master account refers to a bank account maintained by the mFS program partner bank to provide funds and float for the operation of the mFS platform.
- the master account can include sub-accounts for each of the agent branches and subscriber mobile wallets, giving the bank visibility into all transactions on a per-user basis.
- the mFS platform can also manage the balance of sub-accounts and interact with the bank's master account when funds need to be deposited or withdrawn from the account.
- MNO mobile network operator
- USSD unstructured supplementary service data
- wireless service provider a provider of mobile phone service including basic voice, SMS, unstructured supplementary service data (USSD) and data service, and may also be referred to as a “wireless service provider”.
- mobile wallet or “mobile wallet account” refers to a stored value account or prepaid access account (PPA) that allows the owner (or “subscriber”) to pay for goods and services on the mFS platform from his or her mobile wallet account.
- PPA prepaid access account
- the mobile wallet balance is maintained by the mFS platform and value is exchanged within the mFS program as eMoney.
- the mobile wallet utilizes funds from the subscriber's prepaid debit card and bank account to exchange value on the mFS platform.
- non-agent company refers to a mFS program participant who accepts payments from mFS subscribers but does not provide the same services as mFS agent companies. Payment is accepted either in the form of eMoney or through periodic settlements with the mFS platform provider. Examples of non-agent companies include bill pay providers and micro-finance lenders.
- non-mFS subscribers refers to unregistered users that participates in various use cases in the mFS program. Non-mFS subscribers can send money to or receive money from mFS subscribers through interaction with the mFS program agents or with international remittance providers.
- partner bank refers to the primary bank participating in the mFS program.
- the partner bank is responsible for holding the mFS program master accounts that hold the funds for all mFS services and transactions.
- a “PIN” refers to a numeric password that may be required to perform a transaction via the mobile wallet application.
- a “transaction processor” refers to an application or service that manages the mFS program account balances. The transaction processor determines the amount of funds or eMoney is in a particular account at any given time, and manages account balances. Mobile transaction system requests to credit, debit, or view the balance of a particular mobile wallet or program account are handled by the transaction processor (in conjunction with other components of the mobile wallet platform).
- sub-accounts refers to accounts that are maintained within the mFS platform or by an external card processor.
- a partner bank may elect to maintain a separate bank account for each subscriber and/or agent branch, or a single master account may be established that contains the funds for all of the subscriber mobile wallet and agent branch accounts (at least within a country or other geographical region). The balance of each individual user may be managed by the mFS transaction processor.
- the bank When using a master account, the bank is involved only in transactions that require the movement of funds external to the mFS program. For example, subscriber cash-in and cash-out transactions involve the addition and removal of cash from the mFS program and would consequently include a deposit or withdrawal from the master account. Retail purchases from participating mFS program retailers or the exchange of funds between mFS subscribers results in no net change in the mFS program balance and thus do not require involvement by the partner bank.
- the term “subscriber” refers to a participant of the mFS mobile wallet platform.
- the subscriber maintains a mobile wallet balance and performs transactions using the mFS application.
- An “unbanked subscriber” is a subscriber that does not have (or does not have access to) a bank account or credit union account.
- the application or “mobile wallet application” provides mobile wallet functionality to the (unbanked) subscriber.
- the mobile wallet application is installed on a mobile device in the device's memory, on a SIM card (such as a GSM SIM card) or is otherwise accessible to the mobile device.
- the mobile wallet application provides the subscriber the ability to securely perform subscriber functions such as making retail purchases, paying bills, or transferring money to other mFS subscribers and non-subscribers.
- the mobile wallet application communicates with the mFS platform using binary and text SMS messages, among other forms of wireless communication.
- a wireless service provider or MNO provides the GSM network infrastructure on which the mFS platform operates.
- FIG. 1 illustrates an example system architecture for a mobile wallet platform.
- Integration tier 101 is configured to manage mobile wallet sessions and maintain integrity of financial transactions.
- Integration tier 101 can also include a communication (e.g., Web services) API and/or other communication mechanisms to accept messages from channels 111 .
- Other mechanisms include, but are not limited to: International Standards Organization (“ISO”) 8583 for Point of Sale (“POS”) and Automated Teller Machines (“ATM”) devices and Advanced Message Queuing Protocol (“AMQP”) for queue based interfaces.
- ISO International Standards Organization
- POS Point of Sale
- ATM Automated Teller Machines
- AMQP Advanced Message Queuing Protocol
- Each of channels 111 can be integrated to one or more mechanisms for sending messages to integration tier 101 .
- Notification services 102 is configured to send various notifications through different notification channels 112 , such as, for example, Short Message Peer-to-Peer (“SSMP”) for Short Messaging Service (“SMS”) and Simple Mail Transfer Protocol (“SMTP”) for emails. Notification services 102 can be configured through a web services API.
- SSMP Short Message Peer-to-Peer
- SMS Short Messaging Service
- SMTP Simple Mail Transfer Protocol
- Service connectors 103 are a set of connectors configure to connect to 3rd party systems 113 . Each connector can be a separate module intended to integrate an external service to the system architecture.
- Business process services 104 are configured to implement business workflows, including executing financial transactions, auditing financial transactions, invoking third-party services, handling errors, and logging platform objects.
- Payment handler 105 is configured to wrap APIs of different payment processors, such as, for example, banking accounts, credit/debit cards or processor 121 . Payment handler 105 exposes a common API to facilitate interactions with many different kinds of payment processors.
- Security services 106 are configured to perform subscriber authentication.
- Authorization services 107 are configured to perform client authorization, such as, for example, using a database-based Access Control List (“ACL”) table.
- ACL Access Control List
- Database 108 is configured to manage customer accounts (e.g., storing customer accounts and properties), manage company accounts (e.g., storing company accounts and properties), manage transaction histories (e.g., storing financial transaction details), store customer profiles, storing dictionaries used by the mobile wallet platform, such as, for example, countries, currencies, etc., and managing money containers.
- Rules engine 109 is configured to gather financial transaction statistics and uses the statistics to provide transaction properties, such as, for example, fees and bonuses.
- Rules engine 109 is also configured to enforce business constraints, such as, for example, transactions and platform license constraints.
- Name matching engine 110 is configured to match different objects according to specified configuration rules. Matching engine 110 can be use to find similarities between names, addresses, etc.
- Transaction processor 121 is configured to manage financial accounts and transactions. The transaction processor 121 can be used to hold, load, withdraw and deposit funds to mobile wallet accounts. Transaction processor 121 can also be used as a common interface to a third party processor system. When used as a common interface, financial operations may be delegated to the external processor. A Clearing House subsystem of transaction processor 121 can be used to exchange the financial information with a bank.
- Components of a mobile wallet platform can be connected to one another over (or be part of) a system bus and/or a network.
- Networks can include a Local Area Network (“LAN”), a Wide Area Network (“WAN”), and even the Internet.
- LAN Local Area Network
- WAN Wide Area Network
- Accorindlgy, components of the mobile wallet platform can be “in the cloud”.
- mobile wallet platform components as well as any other connected computer systems and their components, can create message related data and exchange message related data (e.g., Internet Protocol (“IP”) datagrams and other higher layer protocols that utilize IP datagrams, such as, Transmission Control Protocol (“TCP”), Hypertext Transfer Protocol (“HTTP”), Simple Mail Transfer Protocol (“SMTP”), etc.) over the system bus and/or network.
- IP Internet Protocol
- TCP Transmission Control Protocol
- HTTP Hypertext Transfer Protocol
- SMTP Simple Mail Transfer Protocol
- the components depicted in FIG. 1 can interoperate to provide a number of financial and other services including but not limited to enrolling a customer for a mobile wallet, adding a stored value account (either hosted by a mobile wallet platform or a third party), adding a bank or credit union account to a mobile wallet, adding a debit or credit card account to a mobile wallet, depositing funds in a mobile wallet, withdrawing funds from a mobile wallet, paying bills from a mobile wallet, topping up a prepaid mobile account through a mobile wallet, transferring funds through a mobile wallet (nationally or internationally), making in-store purchases using a mobile wallet, and various other tasks as described herein below.
- These services will be described in greater detail below with regard to system FIGS. 1 and 2 , as well as FIGS. 3-19B .
- FIG. 2 depicts a monetary transaction system 200 similar to that described in FIG. 1 .
- the monetary transaction system 200 may provide a more simplified system structure in which each of the above services may be provided.
- the system includes a subscriber 205 .
- the subscriber may have access to a bank account, or may be an unbanked subscriber.
- the subscriber has a profile 211 with the monetary transaction system 210 .
- the profile includes the subscriber's KYC information, as well as any associated bank accounts, credit union accounts, bill pay accounts or other accounts.
- the subscriber has (or has access to) a mobile device 206 such as a phone or tablet.
- the mobile device runs the mobile wallet application (or mobile wallet application) 207 .
- the subscriber can indicate, using the mobile application 207 which transaction or other action he or she would like to perform.
- the indicated transaction 208 is sent to the mobile wallet platform 210 to be carried out by the platform.
- the transaction processor 216 (which may be similar to or the same as transaction processor 121 of FIG. 1 ) performs the transaction(s) specified by the (unbanked) subscriber 205 .
- the transaction processor may implement various other components to perform the transaction including memory 217 , (wireless) communication module 215 , rules engine 210 and/or transaction database 225 .
- Performing the specified transactions may include communicating with the monetary transaction database 225 to determine whether the transaction is permissible based on data indicated in the unbanked subscriber's profile (for instance, whether the subscriber has enough eMoney in his or her stored value account, or has enough money in his or her bank account). Rules engine 220 may also be consulted to determine whether the subscriber has exceeded a specified number of allowed transactions. Then, if funds are available, and the transaction is otherwise permissible, the monetary transaction system can transfer money or eMoney 221 to or from an entity such as a user or agent (e.g. entity 222 ) to or from an establishment such as a retail store or agent company (e.g. entity 223 ).
- entity such as a user or agent (e.g. entity 222 )
- an establishment such as a retail store or agent company (e.g. entity 223 ).
- the monetary transaction system 210 application provides a web interface that allows subscribers to perform the same functions provided by the monetary transaction system application.
- mobile wallet application 207 may provide a web interface that allows a user to enroll for a mobile wallet.
- the web interface (or the mobile wallet application itself) receives a subscriber-initiated transaction over one of a plurality of channels ( 111 from FIG. 1 ) connected to the monetary transaction system 210 .
- the web interface or mobile wallet application may prompt for and receive enrollment information (e.g. KYC information) for the (unbanked) subscriber 205 over at least one of the plurality of channels (e.g. web, point-of-sale (POS), interactive voice response (IVR, etc.).
- the web interface or mobile wallet application may then send activation instructions over the same or a different channel to activate the (unbanked) subscriber 205 and create a subscriber account for the (unbanked) subscriber.
- the monetary transaction system Once the subscriber has an account, the monetary transaction system generates a corresponding mobile wallet for the unbanked subscriber (available via the web interface and/or the mobile wallet application. The system then presents the (unbanked) subscriber's account data associated with the mobile wallet and/or a notification indicating that enrollment was successful to the subscriber. Accordingly, the mobile wallet application or the web interface may be used to provide user enrollment functionality. It should also be understood that either the mobile wallet application or the web interface may be used to provide substantially all of the mobile wallet functionality described herein.
- the mobile device 206 may be any type of plan-based phone or tablet, or prepaid phone or tablet. Many subscribers, such as unbanked subscribers, may primarily use prepaid phones.
- the mobile wallet application 207 may be installed on both plan-based phones and prepaid phones.
- the mobile wallet application may be installed on the device's SIM card, or on the device's main memory. Accordingly, the monetary transaction system 200 may be accessed and used via substantially any type of plan-based or prepaid mobile device.
- FIG. 3 shows three different graphics ( 301 - 303 ) and corresponding method steps ( 310 - 370 ) that illustrate an unbanked subscriber making a deposit using a mobile wallet (and, by extension, using the mobile wallet transaction system 210 ).
- the actions of each participant are shown and described. This will also, at least in some embodiments, include an illustration of money flow throughout the mobile wallet transaction system.
- the unbanked subscriber e.g. 205
- an agent branch location e.g. a retail store, gas station, or other location that has registered to be an agent branch.
- agent branch location e.g. a retail store, gas station, or other location that has registered to be an agent branch.
- agent branch location e.g. a retail store, gas station, or other location that has registered to be an agent branch.
- the subscriber informs the agent manager or agent that they want to deposit a certain amount of cash (in 301 ).
- the agent manager/agent takes the cash and notifies the mobile wallet transaction system of the deposit using their agent manager or agent application ( 302 ).
- the transaction system 210 then credits the subscriber's eMoney account ( 303 ).
- any location that has registered to accept eMoney payments from subscribers' mobile wallets can also accept cash deposits.
- the agent branch's eMoney balance is reduced because their actual money balance was increased by the amount of the deposit.
- the subscriber's mobile wallet account is credited with eMoney in the amount of the deposit. In this manner, a subscriber can deposit cash into their mobile wallet account (in the form of eMoney) at any retail location or other agent branch location.
- the agent manager receives the physical cash deposit into the subscriber's eMoney account via the agent manager or agent's application.
- the subscriber gives cash to agent manager or agent, and the mFS platform processes the request, updates the agent branch and subscriber's eMoney balances, logs the transaction, and sends details (such as eMoney account balances, transaction logs, etc.) to bank specified by the mobile wallet platform. These details may be sent instantaneously as transactions occur, or in batches at pre-determined intervals.
- the monetary transaction system 210 of FIG. 2 is implemented to deposit funds at an agent branch using a mobile wallet.
- the monetary transaction system 210 receives communication from an agent branch over one of a plurality of channels (e.g. 111 ) connected to the monetary transaction system (step 310 ).
- the agent communication indicates that the unbanked subscriber 205 desires to deposit a specified amount of funds into the unbanked subscriber's mobile wallet account.
- the transaction processor 216 then validates the status of the unbanked subscriber's mobile wallet account (step 320 ) and determines if the agent branch is authorized to receive deposited money (i.e. determine if it has pre-registered as an official agent branch) (step 330 ).
- the monetary transaction system may then use rules engine 220 to perform a limit check (to determine whether sufficient funds are available) and/or a velocity check (to determine whether the user has exceeded a specified number of (hourly, daily, or weekly) transactions) on the unbanked subscriber's mobile wallet account (step 340 ).
- the transaction system then credits the unbanked subscriber's mobile wallet account with the specified amount of funds (step 350 ) and returns a notification to the agent branch confirming the deposit (step 360 ) and returns another notification to the subscriber notifying the subscriber that the specified amount of funds was deposited in the their mobile wallet account (step 370 ). Any of channels 111 may be used to perform these communications.
- FIG. 4 shows three different graphics ( 401 - 403 ) and corresponding method steps ( 410 - 490 ) that illustrate an unbanked subscriber making a withdrawal using a mobile wallet (and, by extension, using the mobile wallet transaction system 210 ).
- the terms in the graphics include “$C” representing cash balance and “$E” representing eMoney balance.
- a subscriber submits a withdrawal request using their application ( 401 ).
- the subscriber may also enter information about the agent branch (e.g. name of establishment, name of agent, location or other information) that allows the monetary transaction system 210 to identify the agent branch.
- the transaction processor 216 may then determine whether the unbanked subscriber has enough eMoney to withdraw the requested amount. If he or she does have enough eMoney, then the subscriber's eMoney is deducted and that amount is transferred to the agent branch's eMoney account ( 402 ). Then, the agent branch gives the subscriber the requested amount of cash ( 403 ).
- any entity that has established itself as an agent branch can provide cash withdrawal to a mobile wallet subscriber (whether banked or unbanked).
- the agent's or agent manager's role is to verify the withdrawal request (e.g. via SMS on the agent's or agent manager's phone) and gives the cash to subscriber.
- the subscriber requests cash withdrawal from agent branch's eMoney account via the application, and receives physical cash from agent manager/agent.
- the mobile wallet platform processes the request, updates the agent branch's and subscriber's eMoney balances, logs the transaction, and sends transaction details to a specified bank at pre-determined intervals.
- the monetary transaction system 210 is implemented to withdraw funds at an agent branch using a mobile wallet.
- the communication module 215 receives a communication from an unbanked subscriber over one of a plurality of channels 111 connected to the monetary transaction system 210 (step 410 ).
- the communication indicates that the unbanked subscriber 205 desires to withdraw a specified amount of funds from the unbanked subscriber's mobile wallet account at the agent branch.
- the monetary transaction system 210 validates the status of the unbanked subscriber's mobile wallet account (step 420 ) and determines if the balance of the unbanked subscriber's mobile wallet account is sufficient to accommodate the requested withdrawal for the specified amount of funds (step 430 ).
- the transaction processor 216 performs one or more of a limit check (to verify sufficient funds) and a velocity check (to verify the subscriber hasn't exceeded specified transfer limits) on the unbanked subscriber's mobile wallet account (step 440 ).
- the monetary transaction system 210 then returns a secure, perishable withdrawal code to the subscriber 205 over at least one of the plurality of channels 111 connected to the monetary transaction system (step 450 ).
- the monetary transaction system 210 receives subsequent agent branch communication over at least one of the plurality of channels connected to the monetary transaction system indicating that the withdrawal code has been presented to the agent branch (step 460 ).
- the monetary transaction system 210 then debits the unbanked subscriber's mobile wallet account by the specified amount of funds (step 470 ), returns a notification to the agent branch confirming the withdrawal (step 480 ) and notifies the subscriber that the specified amount of funds was withdrawn from the unbanked subscriber's mobile wallet account over at least one of the channels 111 connected to the monetary transaction system (step 490 ). Accordingly, the monetary transaction system 210 may be used to allow subscribers to withdraw cash using their mobile wallet applications at any store or other entity registered as an agent branch.
- FIG. 5A depicts a subscriber-to-subscriber eMoney transfer.
- subscriber A enters some type of identification information identifying subscriber B (e.g. subscriber B's phone number) and an amount of money he or she wishes to transfer.
- the transaction processor 216 of the monetary transaction system 210 determines if there are sufficient funds to complete the transfer. If sufficient funds are available, the monetary transaction system 210 decrements subscriber A's account and credits subscriber B's account ( 502 ). The system then sends some kind of notification (e.g. SMS) to subscriber B indicating that a certain amount of money was transferred to their account. Subscriber A may also receive a notification that the transfer was successful.
- some kind of notification e.g. SMS
- eMoney may be transferred between two mFS platform subscribers, one or both of which may be unbanked.
- the monetary transaction system 210 processes the subscribers' requests, updates the subscribers' eMoney balances, logs the transactions, and sends transaction information to a specified bank when needed.
- FIG. 5B illustrates a subscriber-to-non-subscriber eMoney transfer.
- subscriber A wishes to send eMoney to another individual that is not a subscriber to the mFS platform.
- the transaction is initiated in the same fashion as the subscriber-to-subscriber transfer scenario.
- the monetary transaction system 210 cannot credit them with eMoney. Instead, the monetary transaction system 210 sends a notification (e.g. via SMS) to non-subscriber B with instructions for how to pick-up the transferred money, along with an authorization code ( 506 ).
- the monetary transaction system 210 puts a hold on subscriber A's account for the amount transferred. Subscriber B then has a specified number of days to pick up the cash before the hold expires and the amount is credited back to subscriber A's eMoney account by the monetary transaction system 210 .
- agent branch's manager or agent verifies the authorization code via an agent manager or agent mobile wallet application (that, in turn, accesses the mFS platform). Once the transfer has been validated, the agent gives the cash to non-subscriber B.
- the agent branch's mFS account is credited with the transfer amount ( 507 ) and the user leaves with the cash in hand ( 508 ).
- the mFS platform processes the transfer request, updates subscriber A's eMoney balance, logs the transaction, and sends transaction details to a platform-specified bank.
- FIG. 6A illustrates a subscriber-to-subscriber international eMoney transfer.
- This embodiment is, at least in some respects, similar to sending eMoney to an mFS subscriber domestically.
- the monetary transaction system 210 leverages one or more existing international money transfer organizations or “remittance companies” such as MoneyGram®.
- MoneyGram® is pre-integrated to the monetary transaction system 210 , but other international money transfer organizations may also be used.
- subscriber B may need to have an eMoney account with a foreign mFS program that is also affiliated with MoneyGram® or another international money transfer organization.
- subscriber A initiates the international eMoney transfer at 601 , the international money transfer organization (e.g. MoneyGram®) transfers the eMoney to subscriber B at 602 and subscriber B's eMoney balance is increased by the transferred amount.
- the international money transfer organization e.g. MoneyGram®
- subscriber A requests to send eMoney from his or her eMoney account via the mobile wallet application.
- the eMoney is transferred using an international money transfer organization, and subscriber B receives a notification (that may, for example, include a reference number, among other information) that their eMoney balance has increased by the transfer amount.
- the monetary transfer system 210 processes subscriber A's request, updates subscriber A's and subscriber B's eMoney balances, logs the transaction, and send transaction details to a mFS platform-specified bank.
- FIG. 6B illustrates a subscriber-to-non-subscriber international eMoney transfer.
- subscriber A wishes to send cash to subscriber B who is not an mFS program subscriber.
- the monetary transaction system 210 leverages various international money transfer organizations or remittance companies such as MoneyGram® to transfer the eMoney.
- Subscriber A initiates a typical eMoney transfer at 605 by providing non-subscriber B's identification information, as well as the amount to be transferred.
- the Monetary transaction system 210 recognizes the eMoney transfer is not destined for a domestic phone number and routes the request to the international money transfer organization (e.g. MoneyGram®) ( 606 ).
- the international money transfer organization e.g. MoneyGram®
- the international money transfer organization sends non-subscriber B a notification (e.g. via SMS) with instructions for how and where to pick up the money (in embodiments where MoneyGram® transfers the eMoney, the notification may include a MoneyGram® reference number (MGRN)) ( 607 ).
- Non-subscriber B can then show the MGRN to an agent at an agent branch ( 608 ) and then receive the cash ( 609 ).
- the monetary transaction system 210 then decrements subscriber A's eMoney account for the transferred amount.
- the monetary transfer system 210 thus processes subscriber A's transfer request, updates subscriber A's eMoney balance, logs the transaction, and sends transaction detail to a platform-specified bank. It should also be noted that an mFS subscriber may also receive money in a foreign country from either a subscriber or a non-subscriber in a similar manner.
- FIG. 7 illustrates a subscriber purchasing airtime using a mobile wallet.
- Mobile wallet platform subscribers may buy airtime by using their mobile wallet application 207 .
- the monetary transaction system 210 will reload their airtime account within the mobile network operator's (MNO's) systems.
- the subscriber requests to purchase airtime by entering the request via the mobile wallet application or via a mobile wallet web interface.
- the monetary transaction system 210 then decrements the subscriber's eMoney account ( 701 ), while crediting the mFS platform's eMoney account ( 702 ).
- the purchased airtime is then added to the subscriber's airtime balance ( 703 ).
- the monetary transaction system 210 processes the subscriber's request, updates the subscriber's eMoney balances as well as its own eMoney balance, logs the transaction, and sends transaction detail to a mFS platform-specified bank.
- the monetary transaction system 210 is implemented to top up a prepaid mobile account from a mobile wallet.
- the communication module 215 of the monetary transaction system 210 receives a subscriber communication over one of a plurality of channels 111 connected to the monetary transaction system (step 710 ).
- the subscriber communication indicates that an unbanked subscriber 205 desires to top up a prepaid mobile account by a specified amount using a specified payment method from the unbanked subscriber's mobile wallet.
- the transaction processor 216 validates the status of the selected payment method (step 720 ) and performs a limit check and/or a velocity check on the selected payment method (step 730 ).
- the monetary transaction system 210 then debits the specified payment method by the specified amount of funds (step 740 ) and processes the mobile top-up via a billing system integrator and/or an aggregator (step 750 ), and notifies the subscriber that the prepaid mobile account was topped up over at least one of the channels connected to the monetary transaction system (step 760 ).
- FIG. 8 illustrates an embodiment where a mFS subscriber pays a bill using a mobile wallet.
- the company that the subscriber wishes to pay needs to have signed-up to be part of the mFS platform.
- the mFS platform may publish a list of company names that have registered to be part of the mFS platform. This list of companies may include company IDs so that subscribers can know which company ID to enter in their mobile wallet application. Once the company ID is known, the subscriber can pay a bill by entering the company ID and the amount to be paid.
- the monetary transaction system 210 then decrements the subscriber's eMoney account ( 801 ) and credits the identified company's eMoney account ( 802 ).
- the monetary transaction system 210 processes the request, updates the bill pay company's and the subscriber's eMoney balances, logs the transaction, and sends transaction details to the mFS platform-specified bank.
- the monetary transaction system 210 is implemented to pay a bill from a mobile wallet.
- the communications module 215 of the monetary transaction system 215 receives a subscriber communication over a communication channel 111 connected to the monetary transaction system (step 810 ).
- the subscriber communication indicates that unbanked subscriber 205 desires to pay a bill for a specified amount using a specified payment method from the unbanked subscriber's mobile wallet (e.g. eMoney).
- the monetary transaction system 210 validates the status of the selected payment method (step 820 ) and performs a limit check and/or a velocity check on the selected payment method to ensure the eMoney transfer is permissible (step 830 ).
- the monetary transaction system then debits the specified payment method by the specified amount of funds (step 840 ), processes the bill payment via a direct biller connection or a bill pay aggregator (step 850 ), and notifies the unbanked subscriber that the bill was paid using a communication channel (e.g. SMS) connected to the monetary transaction system (step 860 ).
- a communication channel e.g. SMS
- a subscriber may use a mobile wallet to pay various bills including rent, utility, mortgage, phone, cable, medical and other bills.
- FIG. 9 illustrates a mobile wallet subscriber making a retail purchase.
- Mobile wallet subscribers can make retail purchases at agent branches directly from their mobile device.
- Agent branches are retail stores or other entities that have registered with the mFS system and are able to accept mobile wallet payments. Accordingly, a subscriber can select the items they wish to purchase, and indicate (via the mobile wallet application) to the agent branch that they wish to pay for the items.
- the mobile wallet application then communicates with the agent branch and the monetary transaction system to indicate the price of the transaction.
- the monetary transaction system 210 then debits the subscriber's eMoney account ( 901 ) and credits the agent branch's eMoney account ( 902 ).
- the agent branch receives confirmation that subscriber paid for the purchase.
- the subscriber may also receive a summary of the retail purchase and may be asked to confirm the purchase by entering a PIN.
- the monetary transaction system processes the purchase request, updates the agent branch and subscriber's eMoney balances, logs the transaction, and sends transaction details to a mFS platform-specified bank.
- the monetary transaction system 210 is implemented to make a purchase from a mobile wallet.
- the communications module 215 of the monetary transaction system 210 receives a communication from a subscriber over a communication channels 111 (step 910 ).
- the subscriber communication indicates that an unbanked subscriber 205 desires to purchase an item for a specified amount of funds using a specified payment method from the unbanked subscriber's mobile wallet.
- the monetary transaction system 210 then returns a secure, perishable purchase code to the unbanked subscriber over at least one of the channels connected to the monetary transaction system (step 920 ) and receives a subsequent agent branch communication over a channel indicating that the purchase code has been presented to an agent (branch) (step 930 ).
- the monetary transaction system 210 validates the status of the specified payment method (step 940 ), determines if the specified payment method can accommodate a purchase for the specified amount (step 950 ), performs a limit check and/or a velocity check on the selected payment method ( 960 ), debits the specified payment method by the specified amount of funds ( 970 ), returns a notification to the agent branch authorizing the purchase ( 980 ) and sends a receipt to the unbanked subscriber over a communication channel.
- the monetary transaction system 210 may thus be used to make a retail purchase using a mobile wallet.
- FIG. 10A illustrates a subscriber requesting a micro-loan.
- Financial institutions and potentially other mFS program participants may sign up to become money or eMoney lenders.
- Mobile wallet subscribers may be able to use their mobile wallets to request micro-loans from these approved lenders.
- the micro-loans are tracked by the monetary transaction system 210 , and repayment reminders, interest and commissions are managed by the monetary transaction system.
- the subscriber requests a micro-loan from a lender, indicating the amount in the request, as well as other information such as the repayment date and the commission (i.e. interest rate). Potential lenders then have a chance to counter the loan request with their own terms.
- the lender's eMoney account balance is debited for the specified amount ( 1001 ) and the subscriber's eMoney account is credited with the requested amount ( 1002 ).
- the monetary transaction system 210 processes the micro-loan requests, update the lender and subscriber's eMoney balances, sets up repayment schedules and reminders, logs the transaction, and sends transaction detail to a mFS bank. It should also be noted that while the term “micro-loan” is used herein, the loan may be for substantially any amount of money.
- FIG. 10B illustrates a subscriber repaying a micro-loan.
- the subscriber may repay the loan using functionality provided in the mobile wallet application or in a similar web interface. Repayments can be made in installments or in full depending on the rules of the micro-loan.
- the subscriber enters the amount they wish to repay and the loan ID.
- the subscriber's eMoney account is then debited for the specified amount ( 1005 ), while the lender's eMoney account is credited the specified amount ( 1006 ). Both the lender and the subscriber may receive confirmation that the loan has been repaid via SMS or some other communication channel.
- the mFS platform thus processes the subscriber's micro-loan repayment request, updates lender and subscriber's eMoney balances, updates repayment schedule and reminders, logs the transaction, and sends transaction details to a specified mFS platform bank.
- FIG. 11A illustrates a subscriber receiving a direct deposit from an employer or other entity. Subscribers to the mFS platform have the ability to receive any direct deposit into their eMoney account. Subscribers may be asked by their employers to provide account information in order to set up direct deposit. The employer then submits a direct deposit request using their existing processes (i.e the processes they use for a normal checking or savings bank account). Once the direct deposit is set up and a payday arrives, the employer's bank account is debited for the proper amount ( 1101 ) and the employer's mFS account is credited with that amount ( 1102 ).
- the mFS platform bank sweeps the employers direct deposit balance ( 1103 ) into a mFS platform master account ( 1104 ) and notifies the mFS platform of each account to be incremented (including the subscriber's mobile wallet (eMoney) account).
- the subscriber's eMoney account is then credited with the paycheck amount ( 1105 ) upon which the eMoney may be used to pay for goods, pay bills, top up airtime, transfer to other entities or for cash withdrawal.
- the subscriber does not need to have a bank account to participate in direct deposit.
- the employer's bank can communicate with the mFS platform's bank to perform the necessary steps in directly depositing the subscriber's paycheck in his or her eMoney mobile wallet account.
- the bank facilitates monetary deposit into the employer's bank account for direct deposit and performs an automated sweep of recent deposits from the employer's bank account into the mFS platform's master bank account.
- the bank also sends transaction details to the monetary transaction system 210 including transaction logs.
- the monetary transaction system receives a list of eMoney accounts that are to be credited directly from the employer (or bank), processes the list and requests to establish a direct deposit, updates subscriber's eMoney balance, log the transaction, and sends transaction details to the mFS platform bank.
- FIG. 11B illustrates a subscriber receiving a government social welfare payment directly into their eMoney account.
- subscribers may need to opt-in and register with the government program for which they choose to receive the payment via their mobile wallet. Once the funds have been received, the subscriber can use that eMoney for any goods or services, as described above.
- the government's welfare account deposits the money ( 1110 ) into the government's bank account for welfare payments ( 1111 ) and performs an automated sweep of recent deposits from the government's bank account ( 1112 ) into the mFS program's master bank account ( 1113 ).
- the bank then sends transaction details to the monetary transaction system 210 regarding the deposit.
- the subscriber receives a notification that the welfare payment has been credited to their eMoney account ( 1114 ).
- the mFS platform receives an indication of eMoney accounts that are to be credited from the government, processes the welfare payments, updates the subscriber's eMoney balance, logs the transactions, and sends transaction details to the mFS platform bank.
- FIG. 12A illustrates an agent administrator distributing eMoney to various recipients.
- An agent administrator as explained above, is a person who acts as an agent company's representative. The agent administrator deposits, withdraws, and distributes funds into and out of the agent company's bank account. When an agent administrator deposits cash into an agent company's bank account, it is credited as eMoney to the agent company's account.
- the agent administrator In order to provide the agent branches with eMoney, the agent administrator first moves the eMoney from the agent company's account ( 1201 ) to the branch accounts ( 1202 ). This is performed using the agent administrator's mobile wallet application or portal.
- the monetary transaction system 210 processes the administrator's eMoney transfer request, updates the agent company and agent branch eMoney balances, logs the transaction, and sends transaction details to the mFS platform bank.
- FIG. 12B illustrates an agent company deposit.
- the agent company has an eMoney account in the monetary transaction system 210 that may also include a corresponding bank account (that may be created automatically upon creation of the agent company's eMoney account).
- the agent administrator can make deposits into that account.
- FIG. 12B shows, once cash ( 1205 ) has been deposited into the bank account ( 1206 ), it is transferred to a mFS platform master account ( 1208 ) that includes all or a part of the mFS platform's funds.
- the agent company's bank account is decreased by the deposit amount ( 1207 ), while the agent company's eMoney account balance is correspondingly increased ( 1210 ).
- the agent company account is credited with eMoney.
- the agent company's bank facilitates a physical cash deposit into the agent company's bank account and performs an automated sweep ( 1209 ) of recent deposits from the agent company's bank account into the mFS platform's master bank account.
- the agent company's bank then sends transaction details to the monetary transaction system 210 .
- the agent administrator physically delivers the cash (or form of money such as a check or money order) to a bank branch for deposit.
- the monetary transfer system receives transaction details from the agent company's bank about recent transactions (including deposits, as shown in FIG. 12B .
- FIG. 13 illustrates an agent company withdrawal.
- the agent administrator requests a withdrawal using the agent administrator mobile wallet application.
- the monetary transaction system 210 then notifies the bank that a certain amount of eMoney is to be transferred from the master mFS account ( 1302 ) to the agent company bank account ( 1303 ).
- the agent administrator can withdraw the cash by traditional withdrawal means.
- the mFS master bank receives transaction details from the monetary transaction system 210 about recent transactions (recent withdrawals in this case).
- the mFS master bank performs an automated sweep ( 1304 ) of the mFS platform's master bank account to reflect the recent withdrawal request from agent the agent company ( 1301 ).
- the agent company's eMoney account is reduced by the amount of the withdrawal.
- the agent company also sends transaction details to the monetary transaction system 210 .
- the agent administrator can request withdrawal via the agent administrator mobile wallet application and physically withdrawal cash ( 1305 ) from the agent company's bank branch ( 1306 ).
- the mFS platform processes the agent company's withdrawal request, updates agent company and agent branch eMoney balances, logs the transaction, and sends transaction details to an mFS platform-specified bank.
- the monetary transaction system 210 provides similar functionality to consumers that have bank or credit union accounts. Although many different transactions are presented herein, many more and varied types of transactions may be processed by the monetary transaction system. In the following figures, “$C” refers to cash balance, “$DC” refers to a debit card (prepaid) balance and “$PIN” refers to a recharge PIN value.
- FIG. 14 describes a subscriber deposit at an agent branch.
- the subscriber has a registered and activated (prepaid) debit card at an agent branch location.
- the prepaid debit card is associated with the mobile wallet application in the subscriber's mobile device.
- the debit card is linked to the subscriber's account in the monetary transaction system 210 .
- To deposit cash onto the mobile wallet the subscriber informs the agent that they want to deposit a specified amount of cash ( 1401 ).
- the agent takes the cash and notifies the monetary transaction system 210 of the deposit using their point of sale (POS) system or the agent mobile wallet application ( 1402 ), and the monetary transaction system 210 credits the subscriber's mobile wallet account ( 1403 ).
- the funds collected at the cash register typically do not reach a bank account until the reconciliation and settlement of funds occurs between the agent and the mFS owner's bank.
- the subscriber's bank then receives a settlement report from the card processor and receives funds from the agent's bank.
- the agent or agent manager physically deposits the cash into the subscriber's mobile wallet account via their POS system or agent manager/agent mobile wallet application.
- the monetary transaction system processes the deposit request, increments the subscriber's mobile wallet balance within the card processor and logs the transaction.
- An external card processor increments the subscriber's mobile wallet balance and sends reports to the bank for settlement on a regular (e.g. nightly) basis.
- the monetary transaction system 210 is implemented to deposit funds into a bank or credit union account using a mobile wallet.
- the communications module 215 of the monetary transaction system 210 receives communication from an agent branch over a communication channel (step 1410 ).
- the agent communication indicates that a subscriber 205 desires to deposit a specified amount of funds into a bank or credit union account.
- the transaction processor 216 validates the status of the bank or credit union account (step 1420 ), determines if the agent branch is authorized to deposit money (step 1430 ), and performs a limit check and/or a velocity check on the bank or credit union account (step 1440 ).
- the monetary transaction system then credits the bank or credit union account with the specified amount of funds (step 1450 ), returns a notification to the agent branch confirming the deposit (step 1460 ) and notifies the subscriber that the specified amount of funds was deposited in the bank or credit union account using at least one of the communication channels connected to the monetary transaction system (step 1470 ). Accordingly, cash may be deposited into a bank or credit union account associated with a subscriber's mobile wallet.
- FIG. 15 illustrates a subscriber deposit that is performed with a non-agent.
- subscribers may have the ability to leverage other channels outside of agents to deposit funds onto their card.
- One deposit method is a PIN-based recharge that allows a subscriber to purchase a PIN worth the deposit value.
- the PIN can then be redeemed via an interactive voice response (IVR) system or via the subscriber's mobile wallet application.
- the mobile wallet application will allow the monetary transaction system 210 to deposit the funds onto the subscriber's card.
- the retailer's bank settles with the PIN card provider's bank and the PIN card provider's bank settles with the mFS platform's bank for the deposit.
- the subscriber gives cash to the agent ( 1501 ) which increases the agent company's physical cash ( 1502 ).
- the subscriber uses IVR or their SIM Application to recharge mobile wallet account using a PIN card ( 1503 ).
- an agent may provide the PIN card (i.e. the prepaid debit card) to the subscriber.
- the monetary transaction system 210 processes the subscriber deposit request, increments the subscriber's mobile wallet balance within the card processor and logs the transaction.
- An external card processor decreases the subscriber's PIN card balance ( 1504 ), increments the subscriber's mobile wallet balance ( 1505 ) and send reports to the mFS platform bank for settlement.
- FIG. 16 illustrates a subscriber withdrawal at an agent branch.
- a subscriber submits a withdrawal request using the mobile wallet application on their mobile device.
- the subscriber may also need to enter details about the agent branch that allows the monetary transaction system 210 to determine if the subscriber has sufficient funds on their debit card.
- the mFS platform then notifies the agent branch that it can give cash to the subscriber. If the subscriber has sufficient funds, the monetary transaction system 210 will decrement the subscriber's funds from their card ( 1601 ) and transfer it to the mobile wallet owner's account within the same card processor or bank.
- the agent branch ( 1602 ) then provides the withdrawn cash to the subscriber ( 1603 ).
- the subscriber requests a cash withdrawal from their own mobile wallet account via the mobile wallet application.
- the agent or agent manager verifies the withdrawal request via POS authorization or SMS received on agent's phone and, once verified, gives cash to the subscriber.
- the monetary transaction system 210 processes the subscriber's withdrawal request, decrements the subscriber's mobile wallet balance within the card processor and logs the transaction.
- An external card processor decrements the subscriber's mobile wallet balance and sends reports to the bank for settlement on a periodic basis.
- the monetary transaction system 210 is implemented to withdraw funds from a bank or credit union account using a mobile wallet.
- the communication module 215 of the monetary transaction system 210 receives a communication from a subscriber 205 over a communication channel 111 (step 1610 ).
- the subscriber communication indicates that subscriber 205 desires to withdraw a specified amount of funds from a bank or credit union account.
- the transaction processor validates the status of the bank or credit union account (step 1620 ), determines if the balance of the bank or credit union account is sufficient to accommodate the requested withdrawal for the specified amount of funds (step 1630 ) and performs a limit check and/or a velocity check on the bank or credit union account (step 1640 ).
- the monetary transaction system 210 then returns a secure, perishable withdrawal code to the subscriber 205 over at least one of the communication channels (step 1650 ) and receives a subsequent agent branch communication indicating that the withdrawal code has been presented to an agent (step 1660 ).
- the monetary transaction system 210 then debits the bank or credit union account by the specified amount of funds (step 1670 ), returns a notification to the agent branch confirming the withdrawal ( 1680 ) and notifies the subscriber that the specified amount of funds were withdrawn from the bank or credit union account using at least one of the communication channels connected to the monetary transaction system (step 1690 ). Accordingly, a subscriber can withdraw cash stored on their mobile wallet from an agent branch or a non-agent branch.
- FIG. 17A illustrates a subscriber withdrawal using an automated teller machine (ATM).
- ATM automated teller machine
- Subscribers in many countries have access to ATM machines and can use their mobile wallets to perform withdrawals using their (prepaid) debit card at most ATMs.
- Banks provide ATMs to their customers (typically at no charge) and to non-customers (typically for a small charge).
- the subscriber requests a cash withdrawal from the subscriber's mobile wallet via the subscriber's debit card that is associated with the mobile wallet.
- the bank providing the debit card may receive settlement reports from the card processor and may transfer and/or settle funds from subscriber's account to the ATM network bank.
- An extern card processor decrements the subscriber's mobile wallet balance ( 1701 ) and sends transaction reports to the bank for settlement.
- the ATM dispenses the withdrawn cash to the subscriber ( 1704 ).
- FIG. 17B illustrates a subscriber-to-subscriber money transfer.
- An mFS subscriber ( 1705 ) may send money to another mFS subscriber ( 1706 ).
- subscriber A enters information identifying subscriber B (e.g. a phone number, email address or other identifier).
- the monetary transaction system 210 determines if there are enough funds to complete the transaction, and if so, the monetary transaction system 210 decrements subscriber A's debit card and credits subscriber B's debit card.
- the subscriber accordingly, may request to send money from their own mobile wallet (i.e. money stored on a (prepaid) debit card) account via the subscriber mobile wallet application.
- their own mobile wallet i.e. money stored on a (prepaid) debit card
- the other subscriber receives a notification that the balance of the debit card associated with their mobile wallet has increased.
- the bank receives a settlement report from the debit card processor and transfers or settles funds from subscriber A's account to subscriber B's account (if necessary).
- the monetary transaction system 210 processes the transfer request, updates subscriber A's and subscriber B's debit cards that are associated with their mobile wallets and logs the transaction.
- the external card processor decrements subscriber A's debit card balance, increments subscriber B's debit card balance and sends transaction reports to the mFS platform bank for settlement.
- FIG. 17C illustrates subscriber-to-non-subscriber money transfers.
- subscriber A an mFS subscriber
- subscriber B wishes to send money to another subscriber (a non-mFS subscriber).
- the transaction is initiated in the same fashion as described above in FIG. 17B .
- the monetary transaction system 210 cannot credit them with money. Instead, the monetary transaction system 210 sends a communication (e.g. a SMS) to subscriber B ( 1708 ) with an authorization code and instructions for how to pick up the cash.
- the monetary transaction system 210 puts a hold on subscriber A's debit card for the amount transferred ( 1707 ).
- Subscriber B has a specified time period in which to pick up the cash before the hold expires and the amount is credited back to the debit card associated with subscriber A's mobile wallet account.
- the agent branch verifies the authorization code via POS or their agent mobile wallet application ( 1709 ) and gives the cash to the non-subscriber ( 1710 ). (In some countries, an agent network needs to be capable of giving cash to a subscriber based on the money transfer reference number).
- the mFS bank receives a settlement report from the card processor and transfer and settle funds from subscriber A's debit card to the agent's bank (if necessary).
- the monetary transaction system 210 processes the money transfer request, decrements subscriber A's mobile wallet balance within the card processor, generates a money transfer reference number, authorizes the reference number to be paid out by the agent and logs the transaction.
- An external card processor decrements subscriber A's mobile wallet balance and sends periodic transaction reports to the bank for settlement.
- money may be transferred from subscriber to subscriber and from subscriber to non-subscriber.
- FIG. 18A illustrates a subscriber-to-subscriber international money transfer.
- subscriber A wishes to send cash to subscriber B who resides in another country.
- the monetary transaction system 210 may use one or more international money transfer organizations or remittance companies such as MoneyGram® to transfer the money.
- Subscriber A initiates the international money transfer using his or her phone.
- Subscriber A's debit card account is decremented by the transfer amount ( 1801 ).
- the money is transferred between countries using an international money transfer organization ( 1802 ).
- subscriber B has an mFS eMoney account with a foreign mFS platform that is also affiliated with the selected international money transfer organization. That organization can then credit subscriber B's eMoney account directly ( 1803 ).
- subscriber A requests to send money from their debit card account via the subscriber mobile wallet application.
- Subscriber B receives a notification (including a MoneyGram® Reference Number (MGRN) (or other reference number when other international money transfer organizations are used) and instructions on how to access the eMoney) that their eMoney balance has increased.
- the mFS bank receives settlement reports from the debit card processor and transfers and/or settles funds from subscriber's account to the international organization's bank.
- the monetary transfer system 210 processes the transfer request, update subscriber A's and subscriber B's eMoney balances and logs the transaction.
- An external card processor decrements subscriber A's mobile wallet balance and sends periodic transaction reports to the bank for settlement.
- FIG. 18B illustrates a subscriber-to-non-subscriber international money transfer.
- subscriber A wishes to send cash to subscriber B who resides in another country.
- the monetary transaction system 210 uses an international money transfer organization ( 1806 ) to transfer the money between countries.
- the international money transfer organization debits subscriber A's debit card account ( 1805 ) and transfers that money to subscriber B.
- Subscriber B ( 1807 ) receives a notification (e.g. via SMS) with pick up instructions and a transfer ID number. Subscriber B can then go to an agent company ( 1808 ), show them the notification (including, perhaps an authorization code), and receive the transferred money ( 1809 ).
- an agent company 1808
- the embodiment of 19 A illustrates a transaction where a subscriber receives an international money transfer.
- Subscriber B ( 1901 ) initiates a money transfer using their mobile wallet application.
- the international money transfer organization ( 1902 ) debits subscriber B's eMoney account balance. This money is then transferred by the international money transfer organization to subscriber A.
- Subscriber A receives a notification along with a transfer ID number indicating that their debit card account has been credited with the transferred money ( 1903 ).
- FIG. 19B illustrates a non-subscriber-to-subscriber international money transfer.
- This scenario is very similar to that described in FIG. 19A from the mFS subscriber's perspective, except that their eMoney account is credited here, and their debit card account was credited in 19 A.
- the initiator, subscriber B ( 1905 ) does not have an mFS account and, as a result, takes their cash to an international money transfer organization (e.g. MoneyGram®) or other remittance company's agent ( 1906 ) to send it to subscriber A's mobile wallet eMoney account.
- an international money transfer organization e.g. MoneyGram®
- other remittance company's agent remittance company's agent
- the international money transfer organization ( 1907 ) then transfers the specified amount to subscriber A ( 1908 ) and subscriber A's mobile wallet eMoney account is credited with the amount of the transfer.
- Subscriber A may receive a transaction ID number, along with an indication that the transfer has occurred.
- the mFS bank may receive settlement reports from the card processor and settle funds from the international money transfer organization's bank to subscriber A's mobile wallet account.
- the monetary transaction system processes the money transfer request, updates subscriber A's mobile wallet balance within the card processor and logs the transaction.
- An external card processor increments subscriber A's mobile wallet balance and sends periodic transaction reports to the mFS bank for settlement.
- the monetary transaction system 210 is implemented to add a mobile wallet platform stored value account to a mobile wallet.
- the stored value account may include eMoney or other monetary credits.
- communication module 215 of monetary transaction system 210 may receive subscriber data for an unbanked subscriber 205 over a communication channel.
- the transaction processor may perform validation checks on the unbanked subscriber to validate that the unbanked subscriber is not exceeding a specified allowable number of accounts per subscriber.
- the monetary transaction system 210 may then send subscriber data to another entity (such as a third party verification system) for identification of the unbanked subscriber.
- the monetary transaction system 210 receives results from the third party verification system indicating that the subscriber data appropriately identifies the unbanked subscriber, creates a stored value account for the unbanked subscriber that maintains a recorded balance for the created stored value account, adds the stored value account to the unbanked subscriber's mobile wallet and notifies the unbanked subscriber of the addition of the stored value account over at least one communication channel connected to the mobile wallet platform.
- the monetary transaction system 210 is implemented to add a third party stored value account to a mobile wallet.
- the monetary transaction system 210 receives unbanked subscriber data, including account details, over a communication channel.
- the transaction processor 216 performs a validation check on the unbanked subscriber to validate that the unbanked subscriber is not exceeding a specified allowable number of accounts per subscriber. If the validation check is ok, the monetary transaction system 210 sends subscriber data to a third party verification system for identification of the unbanked subscriber.
- validating the status of the sender or the recipient includes performing a check on the specified sender or recipient to comply with the office of foreign assets control.
- the monetary transaction system 210 then receives results from the third party verification system indicating that the subscriber data appropriately identifies the unbanked subscriber, and submits the unbanked subscriber's account details to a third party account processor.
- the monetary transaction system 210 receives an indication from the third party account processor that third party account processor created a third party stored value account for the subscriber.
- the transaction processor maintains a link between the subscriber data and the third party stored value account and adds the third party stored value account to the unbanked subscriber's mobile wallet.
- the monetary transaction system 210 then notifies the unbanked subscriber of the addition of the third party stored value account over a communication channels connected to the monetary transaction system.
- the monetary transaction system 210 is implemented to add a bank or credit union account to a mobile wallet.
- the communication module 215 receives subscriber data, including bank or credit union account details, over a communication channel 111 .
- the transaction processor 216 performs validation checks on the subscriber to validate that the subscriber is not exceeding a specified allowable number of accounts per subscriber and sends subscriber data to a third party verification system for identification of the subscriber.
- the communication module then receives results from the third party verification system indicating that the subscriber data appropriately identifies the subscriber.
- the monetary transaction system 210 submits bank or credit union account details for validation by the transaction processor, receives an indication that the bank or credit union account details correspond to a valid bank or credit union account, maintains a link between the subscriber data and the bank or credit union account and notifies the subscriber of the bank or credit union account validation over a communication channel.
- the monetary transaction system is implemented to add a debit or credit card account to a mobile wallet.
- the communication module 215 receives subscriber data, including a debit or credit card account number, over a communication channel 111 connected to the monetary transaction system.
- the transaction processor performs validation checks on the subscriber to validate that the subscriber is not exceeding a specified allowable number of accounts per subscriber.
- the communication module sends subscriber data to a third party verification system for identification of the subscriber and receives results from the third party system indicating that the subscriber data appropriately identifies the subscriber.
- the monetary transaction system 210 securely stores the debit or credit card account number for access by the mobile wallet (e.g.
- Embodiments of the invention can adhere to Know Your Customer (KYC) rules in the US by performing Customer Identification Program (CIP) checks as required by the Bank Secrecy Act and US PATRIOT Act.
- KYC Customer Identification Program
- a minimum amount of information can be gathered about a customer, such as, for example, first name, last name, date of birth, government ID Type, government ID number and address.
- the CIP processes are designed to validate customer identity against government blacklists and assists in the prevention of money laundering and terrorist financing.
- a combination of non-documentary and documentary verification can be used to ensure beyond a reasonable doubt the identity of the customer.
- Non-documentary verification can occur through the presentment of the information that was collected from the user to an external third party, such as, for example, Lexis Nexis®. Documentary verification can occur if non-documentary verification fails, then the user is asked to present an unexpired government ID. Various differ forms of identification including driver's license, passport, alien identification (e.g., green card or work visa), and Mexican Consular identification card, can be accepted.
- an external third party such as, for example, Lexis Nexis®.
- Documentary verification can occur if non-documentary verification fails, then the user is asked to present an unexpired government ID.
- Various differ forms of identification including driver's license, passport, alien identification (e.g., green card or work visa), and Mexican Consular identification card, can be accepted.
- Embodiments of the invention can perform Anti-Money Laundering (AML) and combating the Financing of Terrorism (CFT) checks.
- AML and CFT checks can be performed using transaction monitoring methods to flag names and suspicious transactions for further investigation.
- the mobile wallet platform can perform AML and CFT checks on all electronic financial transactions to ensure that electronic funds are not being used for money laundering or terrorism.
- Transaction limits can be placed on user accounts. The transaction limits are fully configurable for each particular use case, channel and payment method that allows maximum flexibility to restrict higher risk use cases.
- Velocity checks can also be performed. Velocity Checks ensure that subscribers are not abusing the mobile wallet platform within the allowable limits.
Abstract
Description
- This application is a continuation of U.S. patent application Ser. No. 13/484,199, filed May 30, 2012, entitled “Monetary Transaction System”, which application claims priority to and the benefit of U.S. Provisional Application Ser. No. 61/522,099, filed on Aug. 10, 2011, entitled “Mobile Wallet Platform”, and also claims priority to and the benefit of U.S. Provisional Application Ser. No. 61/493,064, filed on Jun. 3, 2011, entitled “Mobile Wallet Platform”. All of the aforementioned applications are incorporated by reference herein in their entirety.
- Mobile phones and other digital devices have become increasingly popular in recent years. Many mobile device users use their devices to perform countless different daily tasks. For instance, mobile devices allow users to check email, send and receive instant messages, check calendar items, take notes, set up reminders, browse the internet, play games or perform any number of different things using specialized applications or “apps”. These applications allow mobile devices to communicate with other computer systems and perform a wide variety of network-connected tasks previously not possible with a mobile device.
- Embodiments described herein are directed to monetary transaction system for conducting monetary transactions between transaction system subscribers and other entities. In one embodiment, the monetary transaction system includes a mobile device configured to run a monetary transaction system application. The monetary transaction system also includes a monetary transaction system subscriber that has a profile with the system. The subscriber indicates, via the monetary transaction system application, one or more specified transactions that are to be performed using the monetary transaction system. The system further includes a monetary transaction system processor that performs the transactions specified by the subscriber. Performing these transactions includes communicating with a monetary transaction database to determine whether the transaction is permissible based on data indicated in the subscriber's profile.
- The monetary transaction system also includes at least one entity that is to be involved in the specified transaction, where the entity has a profile with the monetary transaction system. This entity may be a person, a retail store, an agent or other entity. The subscriber may have access to a bank account, or may be an “unbanked user” that does not have access to a bank account. Each of the terms included above will be described in greater detail below in conjunction with the drawings.
- The monetary transaction system may be used for many different tasks including enrolling a customer for a mobile wallet, adding a stored value account (either hosted by a mobile wallet platform or a third party), adding a bank or credit union account to a mobile wallet, adding a debit or credit card account to a mobile wallet, depositing funds in a mobile wallet, withdrawing funds from a mobile wallet, paying bills from a mobile wallet, topping up a prepaid mobile account through a mobile wallet, transferring funds through a mobile wallet (nationally or internationally), making in-store purchases using a mobile wallet, and various other tasks as described herein below.
- This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
- Additional features and advantages will be set forth in the description which follows, and in part will be apparent to one of ordinary skill in the art from the description, or may be learned by the practice of the teachings herein. Features and advantages of embodiments described herein may be realized and obtained by means of the instruments and combinations particularly pointed out in the appended claims. Features of the embodiments described herein will become more fully apparent from the following description and appended claims.
- To further clarify the above and other features of the embodiments described herein, a more particular description will be rendered by reference to the appended drawings. It is appreciated that these drawings depict only examples of the embodiments described herein and are therefore not to be considered limiting of its scope. The embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings in which:
-
FIG. 1 illustrates a monetary transaction system architecture in which embodiments described herein may operate. -
FIG. 2 illustrates an alternate example embodiment of a monetary transaction system. -
FIG. 3 illustrates an example data flow for performing a subscriber deposit via a mobile wallet. -
FIG. 4 illustrates an example data flow for performing a subscriber withdrawal via a mobile wallet. -
FIGS. 5A and 5B illustrate example data flows for performing subscriber-to-subscriber and subscriber-to-non-subscriber eMoney transfers via a mobile wallet, respectively. -
FIGS. 6A and 6B illustrate example data flows for performing subscriber-to-subscriber and subscriber-to-non-subscriber international eMoney transfers via a mobile wallet, respectively. -
FIG. 7 illustrates an example data flow for performing a subscriber airtime purchase via a mobile wallet. -
FIG. 8 illustrates an example data flow for performing a subscriber-initiated bill pay via a mobile wallet. -
FIG. 9 illustrates an example data flow for performing a subscriber-initiated retail purchase via a mobile wallet. -
FIGS. 10A and 10B illustrate example data flows for requesting and repaying micro-loans via a mobile wallet, respectively. -
FIG. 11A illustrates an example data flow of a subscriber receiving a direct deposit via a mobile wallet. -
FIG. 11B illustrates an example data flow of a subscriber receiving a governmental welfare payment via a mobile wallet. -
FIG. 12A illustrates an example data flow of an agent administrator distributing eMoney via a mobile wallet. -
FIG. 12B illustrates an example data flow of an agent company making a deposit using a mobile wallet. -
FIG. 13 illustrates an example data flow of an agent company making a withdrawal using a mobile wallet. -
FIG. 14 illustrates an example data flow of a subscriber making a deposit at an agent branch using a mobile wallet. -
FIG. 15 illustrates an example data flow of a subscriber making a deposit with a non-agent using a mobile wallet. -
FIG. 16 illustrates an example data flow of a subscriber making a withdrawal with an agent using a mobile wallet. -
FIG. 17A illustrates an example data flow of a subscriber making a withdrawal from an ATM using a mobile wallet. -
FIG. 17B illustrates an example data flow of a subscriber-to-subscriber money transfer using a mobile wallet. -
FIG. 17C illustrates an example data flow of a subscriber-to-non-subscriber money transfer using a mobile wallet. -
FIG. 18A illustrates an example data flow of a subscriber-to-subscriber international money transfer using a mobile wallet. -
FIG. 18B illustrates an example data flow of a subscriber-to-non-subscriber international money transfer using a mobile wallet. -
FIG. 19A illustrates an example data flow of a subscriber-to-subscriber international money transfer using a mobile wallet. -
FIG. 19B illustrates an example data flow of a non-subscriber-to-subscriber international money transfer using a mobile wallet. - Embodiments described herein are directed to monetary transaction system for conducting monetary transactions between transaction system subscribers and other entities. In one embodiment, the monetary transaction system includes a mobile device configured to run a monetary transaction system application. The monetary transaction system also includes a monetary transaction system subscriber that has a profile with the system. The subscriber indicates, via the monetary transaction system application, one or more specified transactions that are to be performed using the monetary transaction system. The system further includes a monetary transaction system processor that performs the transactions specified by the subscriber. Performing these transactions includes communicating with a monetary transaction database to determine whether the transaction is permissible based on data indicated in the subscriber's profile.
- The monetary transaction system also includes at least one entity that is to be involved in the specified transaction, where the entity has a profile with the monetary transaction system. This entity may be a person, a retail store, an agent or other entity. The subscriber may have access to a bank account, or may be an “unbanked user” that does not have access to a bank account. Each of the terms included above will be described in greater detail below in conjunction with the drawings.
- The monetary transaction system may be used for many different tasks including enrolling a customer for a mobile wallet, adding a stored value account (either hosted by a mobile wallet platform or a third party), adding a bank or credit union account to a mobile wallet, adding a debit or credit card account to a mobile wallet, depositing funds in a mobile wallet, withdrawing funds from a mobile wallet, paying bills from a mobile wallet, topping up a prepaid mobile account through a mobile wallet, transferring funds through a mobile wallet (nationally or internationally), making in-store purchases using a mobile wallet, and various other tasks as described herein below.
- The following discussion now refers to a number of methods and method steps or acts that may be performed. It should be noted, that although the method steps may be discussed in a certain order or illustrated in a flow chart as occurring in a particular order, no particular ordering is necessarily required unless specifically stated, or required because a step is dependent on another step being completed prior to the step being performed.
- Embodiments of the mobile transaction system or “mobile wallet platform” described herein may comprise or utilize a special purpose or general-purpose computer including computer hardware, such as, for example, one or more processors and system memory, as discussed in greater detail below. Embodiments described herein also include physical and other computer-readable media for carrying or storing computer-executable instructions and/or data structures. Such computer-readable media can be any available media that can be accessed by a general purpose or special purpose computer system. Computer-readable media that store computer-executable instructions in the form of data are computer storage media. Computer-readable media that carry computer-executable instructions are transmission media. Thus, by way of example, and not limitation, embodiments described herein can comprise at least two distinctly different kinds of computer-readable media: computer storage media and transmission media.
- Computer storage media includes RAM, ROM, EEPROM, CD-ROM, solid state drives (SSDs) that are based on RAM, Flash memory, phase-change memory (PCM), or other types of memory, or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store desired program code means in the form of computer-executable instructions, data or data structures and which can be accessed by a general purpose or special purpose computer.
- A “network” is defined as one or more data links and/or data switches that enable the transport of electronic data between computer systems and/or modules and/or other electronic devices. When information is transferred or provided over a network (either hardwired, wireless, or a combination of hardwired or wireless) to a computer, the computer properly views the connection as a transmission medium. Transmission media can include a network which can be used to carry data or desired program code means in the form of computer-executable instructions or in the form of data structures and which can be accessed by a general purpose or special purpose computer. Combinations of the above should also be included within the scope of computer-readable media.
- Further, upon reaching various computer system components, program code means in the form of computer-executable instructions or data structures can be transferred automatically from transmission media to computer storage media (or vice versa). For example, computer-executable instructions or data structures received over a network or data link can be buffered in RAM within a network interface module (e.g., a network interface card or “NIC”), and then eventually transferred to computer system RAM and/or to less volatile computer storage media at a computer system. Thus, it should be understood that computer storage media can be included in computer system components that also (or even primarily) utilize transmission media.
- Computer-executable (or computer-interpretable) instructions comprise, for example, instructions which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, or even source code. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the described features or acts described above. Rather, the described features and acts are disclosed as example forms of implementing the claims.
- Those skilled in the art will appreciate that various embodiments may be practiced in network computing environments with many types of computer system configurations, including personal computers, desktop computers, laptop computers, message processors, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile telephones, PDAs, tablets, pagers, routers, switches, and the like. Embodiments described herein may also be practiced in distributed system environments where local and remote computer systems that are linked (either by hardwired data links, wireless data links, or by a combination of hardwired and wireless data links) through a network, each perform tasks (e.g. cloud computing, cloud services and the like). In a distributed system environment, program modules may be located in both local and remote memory storage devices.
- In this description and the following claims, “cloud computing” is defined as a model for enabling on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services). The definition of “cloud computing” is not limited to any of the other numerous advantages that can be obtained from such a model when properly deployed.
- For instance, cloud computing is currently employed in the marketplace so as to offer ubiquitous and convenient on-demand access to the shared pool of configurable computing resources. Furthermore, the shared pool of configurable computing resources can be rapidly provisioned via virtualization and released with low management effort or service provider interaction, and then scaled accordingly.
- A cloud computing model can be composed of various characteristics such as on-demand self-service, broad network access, resource pooling, rapid elasticity, measured service, and so forth. A cloud computing model may also come in the form of various service models such as, for example, Software as a Service (“SaaS”), Platform as a Service (“PaaS”), and Infrastructure as a Service (“IaaS”). The cloud computing model may also be deployed using different deployment models such as private cloud, community cloud, public cloud, hybrid cloud, and so forth. In this description and in the claims, a “cloud computing environment” is an environment in which cloud computing is employed.
- Additionally or alternatively, the functionally described herein can be performed, at least in part, by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs), Program-specific Integrated Circuits (ASICs), Program-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), and other types of programmable hardware.
- Still further, system architectures described herein can include a plurality of independent components that each contribute to the functionality of the system as a whole. This modularity allows for increased flexibility when approaching issues of platform scalability and, to this end, provides a variety of advantages. System complexity and growth can be managed more easily through the use of smaller-scale parts with limited functional scope. Platform fault tolerance is enhanced through the use of these loosely coupled modules. Individual components can be grown incrementally as business needs dictate. Modular development also translates to decreased time to market for new functionality. New functionality can be added or subtracted without impacting the core system.
- Various terminology will be used herein to describe the monetary transaction system (also referred to as a “mobile wallet platform”, “mobile wallet program” or “mobile wallet transaction system”). The term “agent” is used to refer to an individual with mobile financial services (mFS) transaction system tools and training to support specific mFS functions. These mFS functions include subscriber registration and activation, and the deposit and withdrawal of funds from the mFS transaction system. Agents are representatives of the mFS transaction system or “program”. Agents can be employees or contractors of the program provider, or other companies and organizations that partner with the program provider to provide these services themselves. Agents may be found in every facet of a typical economy, and may include large retailers, mobile network operators (MNO) airtime sales agents, gas stations, kiosks, or other places of business.
- The mobile wallet platform includes a mobile wallet application, web interface or some other type of functionality that allows the user to interact with the mFS platform using their mobile device. The mobile wallet application may include a subscriber identity module (SIM) application, an Unstructured Supplementary Service Data (USSD) application, a smartphone application, a web application, a mobile web application, a Wireless Application Protocol (WAP) application, a
Java 2 Platform, Micro Edition (J2ME) application, a tablet application or any other type of application or interface that provides tools for the agent to register, activate, and offer other services to the mFS subscriber. - As used herein, a mobile wallet application is a mobile wallet application installed on a SIM card. A USSD application is an application that implements USSD for various functionality including prepaid callback service, location-based content services, menu-based information services and other mobile wallet platform services. A web application is one that implements or uses the internet to provide mobile wallet platform functionality. A mobile web application is similar to a web application, but is tailored for mobile devices. A WAP application is one that uses the wireless application protocol to communicate with the mobile wallet platform to provide the platform's functionality. A J2ME application is an application developed in Java and is designed to provide mobile wallet functionality on a variety of different hardware. A tablet application is an application specifically designed for a touchscreen-based tablet that provides mobile wallet platform functionality for tablet devices, and as part of configuring the phone on the network. Any of these applications (or any combination thereof) may be provided on the user's mobile device. This functionality can also be made available on a retail point of sale (POS) system or web site.
- The term “agent administrator” refers to an individual with mFS program tools and training to administrate the allocation of funds to agent branches (e.g. retail locations). As agents perform mFS transactions with subscribers, such as depositing and withdrawing money, the agents are adding and removing money from their own accounts. If there are insufficient funds in the agent's account to complete a transaction, additional money will need to be transferred from the agent company's master account to that agent branch account to cover that transaction. An agent administrator is responsible for these funds transfers. Any of the applications referred to above may be configured to provide tools used by the agent administrator to view the agent company balance, view the agent branch balances, and transfer funds into and out of agent branch mobile wallets. This functionality can also be made available on a website for easier access.
- The term “agent administrator mobile wallet application” refers to a software program or application installed on the agent administrator's terminal in the agent administrator's mobile device (such as a mobile phone or tablet). This software application provides the agent administrator the ability to securely perform agent administrator functions such as querying the agent company account balance or transferring funds into and out of agent branch accounts. The agent administrator's mobile wallet application may be installed on a global system for mobile communications (GSM) SIM card (or on any other type of SIM card), and may be accessed using a GSM mobile phone. The agent administrator's application may also be installed on a code division multiple access (CDMA) mobile phone, a 3G, 4G, 4G LTE (Long Term Evolution) or other wireless carrier standard. The application may, additionally or alternatively, be installed directly on the agent administrator's mobile device. The application communicates with the mFS transaction system using binary and/or text short message service (SMS) messages. A wireless service provider or MNO provides the GSM SMS network infrastructure on which the mFS platform operates.
- In some embodiments, the mFS platform application may utilize triple data encryption standard (3DES) encryption (or some other type of encryption), encrypted message signing, and password security on some or all of its communications with the mFS transaction system in order to ensure that the transactions are properly secured and authenticated.
- The term “agent branch” refers to any location where an agent provides support for subscriber services of the mFS platform. Funds are allocated by the agent administrator from the agent company's main account to each agent branch to fund the subscriber mFS functions such as depositing or withdrawing cash, in-store purchases, bill payments, prepaid airtime top-ups and money transfers. In some cases, multiple agents may work in a single branch. However, at least in some cases, monetary funds are allocated to from the agent company's main account on a per branch basis.
- The term “agent branch account balance” refers to the amount of money residing in a particular agent branch account at a given time. Funds can be deposited into the branch account by the agent administrator, or the funds can come from participating in subscriber mFS transactions such as depositing or withdrawing cash from the subscriber's mobile wallet accounts, or making retail purchases with the mobile wallet.
- Each agent branch is to maintain a balance in their branch account. This applies more strongly in countries where mFS program and financial services infrastructure is still developing. In cases where real-time processing of financial transactions including card processing is not practical, subscribers leverage the applications on their mobile phones to submit transactions and conduct business with retailers, businesses, and other subscribers. The mFS platform manages the balance of mobile wallet accounts for each subscriber as value is transferred from one mobile wallet to another (e.g. from a subscriber's mobile wallet to an agent's mobile wallet in payment for goods or services). This value is referred to herein as “eMoney”.
- As subscribers conduct business with mFS agents, they deposit or withdraw cash from their mobile wallet accounts. Virtual or eMoney credits are transferred between the subscriber's mobile wallet account and the agent branch's account as a form of currency to support the transaction. As agents accept cash into their cash register by mFS subscribers, they transfer the equivalent amount of eMoney credits into the mFS subscriber's mobile wallet account. For instance, if an mFS subscriber gives an mFS agent $10 to deposit into the subscriber's mobile wallet account, the agent would place the cash into his register and transfer $10 from the agent branch's eMoney account into the subscriber's mobile wallet account. While the agent acquired $10 in his register, he transferred out $10 of eMoney credits from his branch eMoney account.
- In some embodiments, in countries with more developed economies, it may be beneficial to use program-issued pre-paid debit cards, pre-paid access accounts, stored value accounts or gift cards to conduct business along with the added convenience of card processing networks such as Cirrus, STAR, or Visa for POS and automated teller machine (ATM) functionality. Agents, particularly those in retail outlets and kiosks, can still support subscribers with deposits, withdrawals, and other transfers, but in this case bank external card processors manage the mobile wallet and branch account balances and provide the real-time transfer of funds.
- The term “agent branch ledger” refers to a written (or electronic) ledger maintained by the mFS platform. Agent branch transactions are performed on the agent's and subscriber's mobile phones where an electronic record of the transaction is generated and stored on the mFS platform. These electronic transactions are then reconciled with agent branch ledgers to ensure the security and integrity of the transaction. Agent branch ledgers are printed or electronic transaction logs that are distributed to the agent branch locations in hard copy form to serve as a backup record to the electronic transactions.
- The term “agent company” refers to a business that registers to participate in the mFS program as a partner of the mFS program provider or owner. The agent company has one or more agent branches which conduct mFS business with mFS program subscribers. In some cases, the agent company may be referred to as a distributor or retailer.
- The term “agent company account balance” refers to the sum of the funds deposited at a “partner bank” (defined below) by the agent company to fund the agent company's daily transactions. The funds in the agent company account are then distributed to agent branches by the agent company's agent administrator to conduct everyday business such as accepting cash deposits and cash withdrawals from mFS subscribers. This balance is sometimes referred to as the “agent company float”.
- An “agent manager” is a supervisor of company agents for a given company. The agent manager has the training and tools to create, delete or modify agent accounts for a company, as well as monitor the transactions performed by agents. The agent manager may have a special application or an increased level of rights to access applications features not available to other users. The special application is a program installed on the agent manager's terminal. This application provides the agent manager the ability to securely perform agent manager functions such as registering and activating new agent accounts.
- The mFS agent manager application may be installed on any terminal or device. It communicates with the mFS platform using binary and/or text SMS messages. A wireless service provider or MNO provides the GSM SMS network infrastructure on which the mFS platform operates. The mFS platform mobile wallet applications may utilize 3DES encryption (or any other type of encryption), encrypted message signing, and password security on some or all of its communications with the mFS platform in order to ensure that the transactions are properly secured and authenticated.
- The term “agent application” refers to an application that provides all the tools necessary for an agent to register, activate, and offer other services to the mFS subscriber. The agent application is a program installed on the agent's SIM card or otherwise installed in the agent's mobile device's memory. This application provides the agent the ability to securely perform agent functions such as registering and activating new subscribers and depositing and withdrawing funds from mobile wallet accounts. The mFS agent application may be installed on a GSM SIM card or mobile phone and may be accessed using a GSM or CDMA mobile phone. A wireless service provider or MNO provides the data and SMS network infrastructure on which the mFS platform operates.
- The terms “mFS platform”, “mobile wallet platform” and “monetary transaction system” refer to an overall platform or ecosystem of different components that work together to provide the various functions described herein on a global scale. At least some of the various logic components include the following: the application. The “mobile wallet application” or “mFS application” manages the processing of incoming transactions regardless of their source. The application handles end-user authentication, transaction processing, subscriber profile management, and further manages interactions between the various platform components.
- The mFS platform further includes a transaction processor. This component is used when the mFS application is implemented in a country where real-time processing of financial transactions is not practical (or not possible). The transaction processor manages the balance of mobile wallet accounts, agent accounts, and the accounts of any other program participant. The transaction processor handles balance inquiries, credits, debits, and transaction roll-backs.
- The mFS platform further includes a rules engine that manages and applies the rules and policy that are defined for transactions as they are processed on the mFS platform. Rules impact transaction fees, limits, velocity limits, and commissions as well as program actor roles and permissions. Rules can be customized for each implementation. The mFS platform also includes an integration interface that manages the integration and interaction between external systems (i.e. external to the mFS platform) and the mFS platform. Connectivity to the wireless service provider's pre-paid airtime billing platform and the program partner bank, for example, are managed by the integration interface.
- The mFS platform further includes a transaction database that stores the data that supports the mFS platform. This includes subscriber profiles and subscription data, transaction data and logs, and application configuration and run-time data, among other types of data. Another component of the mFS platform is a handset support service that interfaces with the wireless service provider's SMS network to allow communication between the mobile wallet applications and the back-office systems via SMS messaging or some other form of data transfer. Still further, another component of the mFS platform is a web component that provides a web interface to the mFS program participants that allows the subscriber to perform the same functions in the web interface that they would have available through their applications.
- The term “bill pay company” refers to a business that signs-up to participate in the mFS transaction system. As a participant in the mFS transaction system, the company accepts payment from mFS mobile wallet accounts, either in the form of eMoney or through periodic settlements.
- At least in some embodiments, financial transactions that take place in the mFS mobile wallet platform are funded through pre-paid mobile wallet accounts. Mobile wallet platform subscribers can deposit cash into their mobile wallet account through a process referred to herein as ‘cash-in’. The cash-in process is supported by mFS agents at agent branch locations. The agent accepts the cash from the subscriber and transfers the equivalent amount of eMoney to the subscriber's mobile wallet account. This process is similar to withdrawing cash from a bank account.
- As mentioned above, in some embodiments, financial transactions that take place in the mobile wallet platform are funded through pre-paid mobile wallet accounts. Mobile wallet platform subscribers can withdraw cash from their mobile wallet account through a process known as “cash-out”. The cash-out process is supported by mFS agents at agent branch locations. The subscriber transfers eMoney from their mobile wallet account to the agent's eMoney account. Upon receiving the eMoney, the agent gives the subscriber cash from their branch cash register.
- Accounts managed on the mFS platform by the mFS eMoney transaction processor maintain the mobile wallet balance of mFS program participants including subscribers, agent branches, agent companies, and non-agent companies. eMoney is moved between Mobile Wallet accounts by the transaction processor based on mFS transaction processing. Only when transactions involving cash (i.e. depositing or withdrawing funds from the mFS program) or the movement of money from mFS participants to non-mFS program participants are funds moved from the master bank accounts.
- As subscribers, agents, and other mFS program participants conduct business in the mFS program, value is transferred from one account to the next as payment for services rendered or goods purchased. This value can be in the form of real currency or the electronic representation referred to herein as eMoney.
- Among other situations, eMoney is used in mFS implementations where the real-time processing of financial transactions including card processing is not practical. The mFS platform utilizes an internal transaction processor for managing the real-time balance of mobile wallet and agent accounts as value (eMoney) is transferred from one mobile wallet to another in payment for services.
- As subscribers conduct business with mFS agents, they deposit or withdraw cash from their mobile wallet accounts. Virtual or eMoney credits are transferred between the subscriber mobile wallet accounts and the agent branch accounts as a form of currency to support the transaction. As agents accept cash into their cash register by mFS subscribers, they transfer the equivalent amount of eMoney credits into the mFS subscriber's mobile wallet account. For example, if an mFS subscriber gives an mFS agent $10 to deposit into the subscriber's mobile wallet account, the agent would place the cash into his or her register, and transfer $10 from the agent branch eMoney account into the subscriber's mobile wallet account. While the agent acquired $10 in his or her register, the agent transferred-out $10 of eMoney credits from his or her branch eMoney account. This will be explained in greater detail below.
- In some embodiments, employers may wish to participate in the mFS program by allowing the direct deposit of paychecks into subscribers' mobile wallet accounts. Accordingly, each payday, the user's pay is directly transferred to the subscribers' mobile wallet.
- The term “know your customer” or “KYC” refers to information collected about an individual that identifies that individual. Such information is used to establish a mobile wallet account with the mobile wallet platform. Regulatory requirements in some countries require that new bank account creation must be preceded by a display of a valid government ID. These KYC regulations may vary from country to country. Accordingly, different KYC information may be requested from subscribers in different countries in order to establish a mobile wallet account.
- The term micro-finance institution (MFI) refers to a lender that issues small loans. MFls participating in the mFS program lend to mFS program subscribers and accept loan repayment either in the form of eMoney or settlements with the mFS platform provider.
- The term “mFS program”, like the term “mFS platform” refers to the ecosystem of companies, service providers, and subscribers that participate in providing mobile financial services to their customers. In some embodiments, there may be one mFS program implementation per country. Each program includes a program owner and operator, a program platform, a partner wireless services provider or MNO, and a partner bank.
- The term “mFS program master account” refers to a bank account maintained by the mFS program partner bank to provide funds and float for the operation of the mFS platform. Depending on the type of mFS implementation, the master account can include sub-accounts for each of the agent branches and subscriber mobile wallets, giving the bank visibility into all transactions on a per-user basis. The mFS platform can also manage the balance of sub-accounts and interact with the bank's master account when funds need to be deposited or withdrawn from the account.
- The term mobile network operator (MNO) refers to a provider of mobile phone service including basic voice, SMS, unstructured supplementary service data (USSD) and data service, and may also be referred to as a “wireless service provider”.
- The term “mobile wallet” or “mobile wallet account” refers to a stored value account or prepaid access account (PPA) that allows the owner (or “subscriber”) to pay for goods and services on the mFS platform from his or her mobile wallet account. When the mFS eMoney transaction processor is used, the mobile wallet balance is maintained by the mFS platform and value is exchanged within the mFS program as eMoney. When the mFS platform is integrated to an external card processor, the mobile wallet utilizes funds from the subscriber's prepaid debit card and bank account to exchange value on the mFS platform.
- The term “non-agent company” refers to a mFS program participant who accepts payments from mFS subscribers but does not provide the same services as mFS agent companies. Payment is accepted either in the form of eMoney or through periodic settlements with the mFS platform provider. Examples of non-agent companies include bill pay providers and micro-finance lenders.
- The term “non-mFS subscribers” refers to unregistered users that participates in various use cases in the mFS program. Non-mFS subscribers can send money to or receive money from mFS subscribers through interaction with the mFS program agents or with international remittance providers.
- The term “partner bank” refers to the primary bank participating in the mFS program. The partner bank is responsible for holding the mFS program master accounts that hold the funds for all mFS services and transactions. A “PIN” refers to a numeric password that may be required to perform a transaction via the mobile wallet application. A “transaction processor” refers to an application or service that manages the mFS program account balances. The transaction processor determines the amount of funds or eMoney is in a particular account at any given time, and manages account balances. Mobile transaction system requests to credit, debit, or view the balance of a particular mobile wallet or program account are handled by the transaction processor (in conjunction with other components of the mobile wallet platform).
- The term “sub-accounts” refers to accounts that are maintained within the mFS platform or by an external card processor. A partner bank may elect to maintain a separate bank account for each subscriber and/or agent branch, or a single master account may be established that contains the funds for all of the subscriber mobile wallet and agent branch accounts (at least within a country or other geographical region). The balance of each individual user may be managed by the mFS transaction processor.
- When using a master account, the bank is involved only in transactions that require the movement of funds external to the mFS program. For example, subscriber cash-in and cash-out transactions involve the addition and removal of cash from the mFS program and would consequently include a deposit or withdrawal from the master account. Retail purchases from participating mFS program retailers or the exchange of funds between mFS subscribers results in no net change in the mFS program balance and thus do not require involvement by the partner bank.
- The term “subscriber” refers to a participant of the mFS mobile wallet platform. The subscriber maintains a mobile wallet balance and performs transactions using the mFS application. An “unbanked subscriber” is a subscriber that does not have (or does not have access to) a bank account or credit union account. The application or “mobile wallet application” provides mobile wallet functionality to the (unbanked) subscriber. The mobile wallet application is installed on a mobile device in the device's memory, on a SIM card (such as a GSM SIM card) or is otherwise accessible to the mobile device. The mobile wallet application provides the subscriber the ability to securely perform subscriber functions such as making retail purchases, paying bills, or transferring money to other mFS subscribers and non-subscribers. The mobile wallet application communicates with the mFS platform using binary and text SMS messages, among other forms of wireless communication. A wireless service provider or MNO provides the GSM network infrastructure on which the mFS platform operates.
-
FIG. 1 illustrates an example system architecture for a mobile wallet platform.Integration tier 101 is configured to manage mobile wallet sessions and maintain integrity of financial transactions.Integration tier 101 can also include a communication (e.g., Web services) API and/or other communication mechanisms to accept messages fromchannels 111. Other mechanisms include, but are not limited to: International Standards Organization (“ISO”) 8583 for Point of Sale (“POS”) and Automated Teller Machines (“ATM”) devices and Advanced Message Queuing Protocol (“AMQP”) for queue based interfaces. Each ofchannels 111 can be integrated to one or more mechanisms for sending messages tointegration tier 101.Notification services 102 is configured to send various notifications throughdifferent notification channels 112, such as, for example, Short Message Peer-to-Peer (“SSMP”) for Short Messaging Service (“SMS”) and Simple Mail Transfer Protocol (“SMTP”) for emails.Notification services 102 can be configured through a web services API. -
Service connectors 103 are a set of connectors configure to connect to3rd party systems 113. Each connector can be a separate module intended to integrate an external service to the system architecture.Business process services 104 are configured to implement business workflows, including executing financial transactions, auditing financial transactions, invoking third-party services, handling errors, and logging platform objects.Payment handler 105 is configured to wrap APIs of different payment processors, such as, for example, banking accounts, credit/debit cards orprocessor 121.Payment handler 105 exposes a common API to facilitate interactions with many different kinds of payment processors. - Security services 106 are configured to perform subscriber authentication.
Authorization services 107 are configured to perform client authorization, such as, for example, using a database-based Access Control List (“ACL”) table. - Database 108 is configured to manage customer accounts (e.g., storing customer accounts and properties), manage company accounts (e.g., storing company accounts and properties), manage transaction histories (e.g., storing financial transaction details), store customer profiles, storing dictionaries used by the mobile wallet platform, such as, for example, countries, currencies, etc., and managing money containers.
Rules engine 109 is configured to gather financial transaction statistics and uses the statistics to provide transaction properties, such as, for example, fees and bonuses.Rules engine 109 is also configured to enforce business constraints, such as, for example, transactions and platform license constraints. - Name matching engine 110 is configured to match different objects according to specified configuration rules. Matching engine 110 can be use to find similarities between names, addresses, etc.
Transaction processor 121 is configured to manage financial accounts and transactions. Thetransaction processor 121 can be used to hold, load, withdraw and deposit funds to mobile wallet accounts.Transaction processor 121 can also be used as a common interface to a third party processor system. When used as a common interface, financial operations may be delegated to the external processor. A Clearing House subsystem oftransaction processor 121 can be used to exchange the financial information with a bank. - Components of a mobile wallet platform can be connected to one another over (or be part of) a system bus and/or a network. Networks can include a Local Area Network (“LAN”), a Wide Area Network (“WAN”), and even the Internet. Accorindlgy, components of the mobile wallet platform can be “in the cloud”. As such, mobile wallet platform components as well as any other connected computer systems and their components, can create message related data and exchange message related data (e.g., Internet Protocol (“IP”) datagrams and other higher layer protocols that utilize IP datagrams, such as, Transmission Control Protocol (“TCP”), Hypertext Transfer Protocol (“HTTP”), Simple Mail Transfer Protocol (“SMTP”), etc.) over the system bus and/or network.
- The components depicted in
FIG. 1 can interoperate to provide a number of financial and other services including but not limited to enrolling a customer for a mobile wallet, adding a stored value account (either hosted by a mobile wallet platform or a third party), adding a bank or credit union account to a mobile wallet, adding a debit or credit card account to a mobile wallet, depositing funds in a mobile wallet, withdrawing funds from a mobile wallet, paying bills from a mobile wallet, topping up a prepaid mobile account through a mobile wallet, transferring funds through a mobile wallet (nationally or internationally), making in-store purchases using a mobile wallet, and various other tasks as described herein below. These services will be described in greater detail below with regard to systemFIGS. 1 and 2 , as well asFIGS. 3-19B . -
FIG. 2 depicts amonetary transaction system 200 similar to that described inFIG. 1 . Themonetary transaction system 200 may provide a more simplified system structure in which each of the above services may be provided. The system includes asubscriber 205. The subscriber may have access to a bank account, or may be an unbanked subscriber. The subscriber has aprofile 211 with themonetary transaction system 210. The profile includes the subscriber's KYC information, as well as any associated bank accounts, credit union accounts, bill pay accounts or other accounts. The subscriber has (or has access to) amobile device 206 such as a phone or tablet. The mobile device runs the mobile wallet application (or mobile wallet application) 207. - The subscriber can indicate, using the
mobile application 207 which transaction or other action he or she would like to perform. The indicatedtransaction 208 is sent to themobile wallet platform 210 to be carried out by the platform. The transaction processor 216 (which may be similar to or the same astransaction processor 121 ofFIG. 1 ) performs the transaction(s) specified by the (unbanked)subscriber 205. The transaction processor may implement various other components to perform thetransaction including memory 217, (wireless)communication module 215,rules engine 210 and/or transaction database 225. - Performing the specified transactions may include communicating with the monetary transaction database 225 to determine whether the transaction is permissible based on data indicated in the unbanked subscriber's profile (for instance, whether the subscriber has enough eMoney in his or her stored value account, or has enough money in his or her bank account).
Rules engine 220 may also be consulted to determine whether the subscriber has exceeded a specified number of allowed transactions. Then, if funds are available, and the transaction is otherwise permissible, the monetary transaction system can transfer money or eMoney 221 to or from an entity such as a user or agent (e.g. entity 222) to or from an establishment such as a retail store or agent company (e.g. entity 223). - In some cases, the
monetary transaction system 210 application provides a web interface that allows subscribers to perform the same functions provided by the monetary transaction system application. For instance,mobile wallet application 207 may provide a web interface that allows a user to enroll for a mobile wallet. The web interface (or the mobile wallet application itself) receives a subscriber-initiated transaction over one of a plurality of channels (111 fromFIG. 1 ) connected to themonetary transaction system 210. The web interface or mobile wallet application may prompt for and receive enrollment information (e.g. KYC information) for the (unbanked)subscriber 205 over at least one of the plurality of channels (e.g. web, point-of-sale (POS), interactive voice response (IVR, etc.). The web interface or mobile wallet application may then send activation instructions over the same or a different channel to activate the (unbanked)subscriber 205 and create a subscriber account for the (unbanked) subscriber. - Once the subscriber has an account, the monetary transaction system generates a corresponding mobile wallet for the unbanked subscriber (available via the web interface and/or the mobile wallet application. The system then presents the (unbanked) subscriber's account data associated with the mobile wallet and/or a notification indicating that enrollment was successful to the subscriber. Accordingly, the mobile wallet application or the web interface may be used to provide user enrollment functionality. It should also be understood that either the mobile wallet application or the web interface may be used to provide substantially all of the mobile wallet functionality described herein.
- It should also be noted that the
mobile device 206 may be any type of plan-based phone or tablet, or prepaid phone or tablet. Many subscribers, such as unbanked subscribers, may primarily use prepaid phones. Themobile wallet application 207 may be installed on both plan-based phones and prepaid phones. The mobile wallet application may be installed on the device's SIM card, or on the device's main memory. Accordingly, themonetary transaction system 200 may be accessed and used via substantially any type of plan-based or prepaid mobile device. -
FIG. 3 shows three different graphics (301-303) and corresponding method steps (310-370) that illustrate an unbanked subscriber making a deposit using a mobile wallet (and, by extension, using the mobile wallet transaction system 210). In at least some of the embodiments described below, the actions of each participant are shown and described. This will also, at least in some embodiments, include an illustration of money flow throughout the mobile wallet transaction system. In the graphics, various terms are used as follows: $C=Cash Balance and $E=Electronic Money (eMoney) Balance. - At graphic 301, it is assumed that the unbanked subscriber (e.g. 205) has already registered and activated an eMoney account at an agent branch location (e.g. a retail store, gas station, or other location that has registered to be an agent branch). To deposit cash in order to get eMoney credit, the subscriber informs the agent manager or agent that they want to deposit a certain amount of cash (in 301). The agent manager/agent takes the cash and notifies the mobile wallet transaction system of the deposit using their agent manager or agent application (302). The
transaction system 210 then credits the subscriber's eMoney account (303). Accordingly, any location that has registered to accept eMoney payments from subscribers' mobile wallets can also accept cash deposits. The agent branch's eMoney balance is reduced because their actual money balance was increased by the amount of the deposit. The subscriber's mobile wallet account is credited with eMoney in the amount of the deposit. In this manner, a subscriber can deposit cash into their mobile wallet account (in the form of eMoney) at any retail location or other agent branch location. - Thus, the agent manager receives the physical cash deposit into the subscriber's eMoney account via the agent manager or agent's application. The subscriber gives cash to agent manager or agent, and the mFS platform processes the request, updates the agent branch and subscriber's eMoney balances, logs the transaction, and sends details (such as eMoney account balances, transaction logs, etc.) to bank specified by the mobile wallet platform. These details may be sent instantaneously as transactions occur, or in batches at pre-determined intervals.
- In one embodiment, the
monetary transaction system 210 ofFIG. 2 is implemented to deposit funds at an agent branch using a mobile wallet. Themonetary transaction system 210 receives communication from an agent branch over one of a plurality of channels (e.g. 111) connected to the monetary transaction system (step 310). The agent communication indicates that theunbanked subscriber 205 desires to deposit a specified amount of funds into the unbanked subscriber's mobile wallet account. Thetransaction processor 216 then validates the status of the unbanked subscriber's mobile wallet account (step 320) and determines if the agent branch is authorized to receive deposited money (i.e. determine if it has pre-registered as an official agent branch) (step 330). - The monetary transaction system may then use
rules engine 220 to perform a limit check (to determine whether sufficient funds are available) and/or a velocity check (to determine whether the user has exceeded a specified number of (hourly, daily, or weekly) transactions) on the unbanked subscriber's mobile wallet account (step 340). The transaction system then credits the unbanked subscriber's mobile wallet account with the specified amount of funds (step 350) and returns a notification to the agent branch confirming the deposit (step 360) and returns another notification to the subscriber notifying the subscriber that the specified amount of funds was deposited in the their mobile wallet account (step 370). Any ofchannels 111 may be used to perform these communications. -
FIG. 4 shows three different graphics (401-403) and corresponding method steps (410-490) that illustrate an unbanked subscriber making a withdrawal using a mobile wallet (and, by extension, using the mobile wallet transaction system 210). As above, the terms in the graphics include “$C” representing cash balance and “$E” representing eMoney balance. - To withdraw cash at an agent branch, a subscriber submits a withdrawal request using their application (401). The subscriber may also enter information about the agent branch (e.g. name of establishment, name of agent, location or other information) that allows the
monetary transaction system 210 to identify the agent branch. Thetransaction processor 216 may then determine whether the unbanked subscriber has enough eMoney to withdraw the requested amount. If he or she does have enough eMoney, then the subscriber's eMoney is deducted and that amount is transferred to the agent branch's eMoney account (402). Then, the agent branch gives the subscriber the requested amount of cash (403). In this manner, any entity that has established itself as an agent branch (including retail stores, gas stations, service providers, etc.) can provide cash withdrawal to a mobile wallet subscriber (whether banked or unbanked). The agent's or agent manager's role is to verify the withdrawal request (e.g. via SMS on the agent's or agent manager's phone) and gives the cash to subscriber. The subscriber requests cash withdrawal from agent branch's eMoney account via the application, and receives physical cash from agent manager/agent. The mobile wallet platform processes the request, updates the agent branch's and subscriber's eMoney balances, logs the transaction, and sends transaction details to a specified bank at pre-determined intervals. - In one embodiment, the
monetary transaction system 210 is implemented to withdraw funds at an agent branch using a mobile wallet. Thecommunication module 215 receives a communication from an unbanked subscriber over one of a plurality ofchannels 111 connected to the monetary transaction system 210 (step 410). The communication indicates that theunbanked subscriber 205 desires to withdraw a specified amount of funds from the unbanked subscriber's mobile wallet account at the agent branch. Themonetary transaction system 210 validates the status of the unbanked subscriber's mobile wallet account (step 420) and determines if the balance of the unbanked subscriber's mobile wallet account is sufficient to accommodate the requested withdrawal for the specified amount of funds (step 430). - The
transaction processor 216 performs one or more of a limit check (to verify sufficient funds) and a velocity check (to verify the subscriber hasn't exceeded specified transfer limits) on the unbanked subscriber's mobile wallet account (step 440). Themonetary transaction system 210 then returns a secure, perishable withdrawal code to thesubscriber 205 over at least one of the plurality ofchannels 111 connected to the monetary transaction system (step 450). Themonetary transaction system 210 receives subsequent agent branch communication over at least one of the plurality of channels connected to the monetary transaction system indicating that the withdrawal code has been presented to the agent branch (step 460). Themonetary transaction system 210 then debits the unbanked subscriber's mobile wallet account by the specified amount of funds (step 470), returns a notification to the agent branch confirming the withdrawal (step 480) and notifies the subscriber that the specified amount of funds was withdrawn from the unbanked subscriber's mobile wallet account over at least one of thechannels 111 connected to the monetary transaction system (step 490). Accordingly, themonetary transaction system 210 may be used to allow subscribers to withdraw cash using their mobile wallet applications at any store or other entity registered as an agent branch. -
FIG. 5A depicts a subscriber-to-subscriber eMoney transfer. To perform such a transfer, subscriber A (501) enters some type of identification information identifying subscriber B (e.g. subscriber B's phone number) and an amount of money he or she wishes to transfer. Thetransaction processor 216 of themonetary transaction system 210 determines if there are sufficient funds to complete the transfer. If sufficient funds are available, themonetary transaction system 210 decrements subscriber A's account and credits subscriber B's account (502). The system then sends some kind of notification (e.g. SMS) to subscriber B indicating that a certain amount of money was transferred to their account. Subscriber A may also receive a notification that the transfer was successful. Accordingly, eMoney may be transferred between two mFS platform subscribers, one or both of which may be unbanked. Themonetary transaction system 210 processes the subscribers' requests, updates the subscribers' eMoney balances, logs the transactions, and sends transaction information to a specified bank when needed. -
FIG. 5B illustrates a subscriber-to-non-subscriber eMoney transfer. In graphic 505, subscriber A wishes to send eMoney to another individual that is not a subscriber to the mFS platform. The transaction is initiated in the same fashion as the subscriber-to-subscriber transfer scenario. However, since non-subscriber B does not have a mobile wallet account, themonetary transaction system 210 cannot credit them with eMoney. Instead, themonetary transaction system 210 sends a notification (e.g. via SMS) to non-subscriber B with instructions for how to pick-up the transferred money, along with an authorization code (506). Themonetary transaction system 210 puts a hold on subscriber A's account for the amount transferred. Subscriber B then has a specified number of days to pick up the cash before the hold expires and the amount is credited back to subscriber A's eMoney account by themonetary transaction system 210. - When non-subscriber B goes to pick up the money at an agent branch, the agent branch's manager or agent verifies the authorization code via an agent manager or agent mobile wallet application (that, in turn, accesses the mFS platform). Once the transfer has been validated, the agent gives the cash to non-subscriber B. The agent branch's mFS account is credited with the transfer amount (507) and the user leaves with the cash in hand (508). The mFS platform processes the transfer request, updates subscriber A's eMoney balance, logs the transaction, and sends transaction details to a platform-specified bank.
-
FIG. 6A illustrates a subscriber-to-subscriber international eMoney transfer. This embodiment is, at least in some respects, similar to sending eMoney to an mFS subscriber domestically. In this case themonetary transaction system 210 leverages one or more existing international money transfer organizations or “remittance companies” such as MoneyGram®. In some embodiments, MoneyGram® is pre-integrated to themonetary transaction system 210, but other international money transfer organizations may also be used. Still further, at least in some embodiments, subscriber B may need to have an eMoney account with a foreign mFS program that is also affiliated with MoneyGram® or another international money transfer organization. - In
FIG. 6A , subscriber A initiates the international eMoney transfer at 601, the international money transfer organization (e.g. MoneyGram®) transfers the eMoney to subscriber B at 602 and subscriber B's eMoney balance is increased by the transferred amount. Thus, subscriber A requests to send eMoney from his or her eMoney account via the mobile wallet application. The eMoney is transferred using an international money transfer organization, and subscriber B receives a notification (that may, for example, include a reference number, among other information) that their eMoney balance has increased by the transfer amount. Themonetary transfer system 210 processes subscriber A's request, updates subscriber A's and subscriber B's eMoney balances, logs the transaction, and send transaction details to a mFS platform-specified bank. -
FIG. 6B illustrates a subscriber-to-non-subscriber international eMoney transfer. In this illustration, subscriber A wishes to send cash to subscriber B who is not an mFS program subscriber. Similar to the scenario described inFIG. 6A , themonetary transaction system 210 leverages various international money transfer organizations or remittance companies such as MoneyGram® to transfer the eMoney. Subscriber A initiates a typical eMoney transfer at 605 by providing non-subscriber B's identification information, as well as the amount to be transferred. TheMonetary transaction system 210 recognizes the eMoney transfer is not destined for a domestic phone number and routes the request to the international money transfer organization (e.g. MoneyGram®) (606). - The international money transfer organization sends non-subscriber B a notification (e.g. via SMS) with instructions for how and where to pick up the money (in embodiments where MoneyGram® transfers the eMoney, the notification may include a MoneyGram® reference number (MGRN)) (607). Non-subscriber B can then show the MGRN to an agent at an agent branch (608) and then receive the cash (609). The
monetary transaction system 210 then decrements subscriber A's eMoney account for the transferred amount. Themonetary transfer system 210 thus processes subscriber A's transfer request, updates subscriber A's eMoney balance, logs the transaction, and sends transaction detail to a platform-specified bank. It should also be noted that an mFS subscriber may also receive money in a foreign country from either a subscriber or a non-subscriber in a similar manner. -
FIG. 7 illustrates a subscriber purchasing airtime using a mobile wallet. Mobile wallet platform subscribers may buy airtime by using theirmobile wallet application 207. Themonetary transaction system 210 will reload their airtime account within the mobile network operator's (MNO's) systems. The subscriber requests to purchase airtime by entering the request via the mobile wallet application or via a mobile wallet web interface. Themonetary transaction system 210 then decrements the subscriber's eMoney account (701), while crediting the mFS platform's eMoney account (702). The purchased airtime is then added to the subscriber's airtime balance (703). Themonetary transaction system 210 processes the subscriber's request, updates the subscriber's eMoney balances as well as its own eMoney balance, logs the transaction, and sends transaction detail to a mFS platform-specified bank. - In one embodiment, the
monetary transaction system 210 is implemented to top up a prepaid mobile account from a mobile wallet. Thecommunication module 215 of themonetary transaction system 210 receives a subscriber communication over one of a plurality ofchannels 111 connected to the monetary transaction system (step 710). The subscriber communication indicates that anunbanked subscriber 205 desires to top up a prepaid mobile account by a specified amount using a specified payment method from the unbanked subscriber's mobile wallet. Thetransaction processor 216 validates the status of the selected payment method (step 720) and performs a limit check and/or a velocity check on the selected payment method (step 730). Themonetary transaction system 210 then debits the specified payment method by the specified amount of funds (step 740) and processes the mobile top-up via a billing system integrator and/or an aggregator (step 750), and notifies the subscriber that the prepaid mobile account was topped up over at least one of the channels connected to the monetary transaction system (step 760). -
FIG. 8 illustrates an embodiment where a mFS subscriber pays a bill using a mobile wallet. At least in some embodiments, the company that the subscriber wishes to pay needs to have signed-up to be part of the mFS platform. The mFS platform may publish a list of company names that have registered to be part of the mFS platform. This list of companies may include company IDs so that subscribers can know which company ID to enter in their mobile wallet application. Once the company ID is known, the subscriber can pay a bill by entering the company ID and the amount to be paid. Themonetary transaction system 210 then decrements the subscriber's eMoney account (801) and credits the identified company's eMoney account (802). Accordingly, in response to the subscriber's request to pay bill via their mobile wallet application, themonetary transaction system 210 processes the request, updates the bill pay company's and the subscriber's eMoney balances, logs the transaction, and sends transaction details to the mFS platform-specified bank. - In one embodiment, the
monetary transaction system 210 is implemented to pay a bill from a mobile wallet. Thecommunications module 215 of themonetary transaction system 215 receives a subscriber communication over acommunication channel 111 connected to the monetary transaction system (step 810). The subscriber communication indicates thatunbanked subscriber 205 desires to pay a bill for a specified amount using a specified payment method from the unbanked subscriber's mobile wallet (e.g. eMoney). Themonetary transaction system 210 validates the status of the selected payment method (step 820) and performs a limit check and/or a velocity check on the selected payment method to ensure the eMoney transfer is permissible (step 830). The monetary transaction system then debits the specified payment method by the specified amount of funds (step 840), processes the bill payment via a direct biller connection or a bill pay aggregator (step 850), and notifies the unbanked subscriber that the bill was paid using a communication channel (e.g. SMS) connected to the monetary transaction system (step 860). Thus, in this manner, a subscriber may use a mobile wallet to pay various bills including rent, utility, mortgage, phone, cable, medical and other bills. -
FIG. 9 illustrates a mobile wallet subscriber making a retail purchase. Mobile wallet subscribers can make retail purchases at agent branches directly from their mobile device. Agent branches, as explained above, are retail stores or other entities that have registered with the mFS system and are able to accept mobile wallet payments. Accordingly, a subscriber can select the items they wish to purchase, and indicate (via the mobile wallet application) to the agent branch that they wish to pay for the items. The mobile wallet application then communicates with the agent branch and the monetary transaction system to indicate the price of the transaction. Themonetary transaction system 210 then debits the subscriber's eMoney account (901) and credits the agent branch's eMoney account (902). The agent branch (and/or the agent manager or agent) receives confirmation that subscriber paid for the purchase. The subscriber may also receive a summary of the retail purchase and may be asked to confirm the purchase by entering a PIN. The monetary transaction system processes the purchase request, updates the agent branch and subscriber's eMoney balances, logs the transaction, and sends transaction details to a mFS platform-specified bank. - In one embodiment, the
monetary transaction system 210 is implemented to make a purchase from a mobile wallet. Thecommunications module 215 of themonetary transaction system 210 receives a communication from a subscriber over a communication channels 111 (step 910). The subscriber communication indicates that anunbanked subscriber 205 desires to purchase an item for a specified amount of funds using a specified payment method from the unbanked subscriber's mobile wallet. - The
monetary transaction system 210 then returns a secure, perishable purchase code to the unbanked subscriber over at least one of the channels connected to the monetary transaction system (step 920) and receives a subsequent agent branch communication over a channel indicating that the purchase code has been presented to an agent (branch) (step 930). Themonetary transaction system 210 validates the status of the specified payment method (step 940), determines if the specified payment method can accommodate a purchase for the specified amount (step 950), performs a limit check and/or a velocity check on the selected payment method (960), debits the specified payment method by the specified amount of funds (970), returns a notification to the agent branch authorizing the purchase (980) and sends a receipt to the unbanked subscriber over a communication channel. Themonetary transaction system 210 may thus be used to make a retail purchase using a mobile wallet. -
FIG. 10A illustrates a subscriber requesting a micro-loan. Financial institutions and potentially other mFS program participants may sign up to become money or eMoney lenders. Mobile wallet subscribers may be able to use their mobile wallets to request micro-loans from these approved lenders. The micro-loans are tracked by themonetary transaction system 210, and repayment reminders, interest and commissions are managed by the monetary transaction system. The subscriber requests a micro-loan from a lender, indicating the amount in the request, as well as other information such as the repayment date and the commission (i.e. interest rate). Potential lenders then have a chance to counter the loan request with their own terms. Once the lender approves the subscriber's request, the lender's eMoney account balance is debited for the specified amount (1001) and the subscriber's eMoney account is credited with the requested amount (1002). Themonetary transaction system 210 processes the micro-loan requests, update the lender and subscriber's eMoney balances, sets up repayment schedules and reminders, logs the transaction, and sends transaction detail to a mFS bank. It should also be noted that while the term “micro-loan” is used herein, the loan may be for substantially any amount of money. - Following on the embodiment described in
FIG. 10A ,FIG. 10B illustrates a subscriber repaying a micro-loan. The subscriber may repay the loan using functionality provided in the mobile wallet application or in a similar web interface. Repayments can be made in installments or in full depending on the rules of the micro-loan. The subscriber enters the amount they wish to repay and the loan ID. The subscriber's eMoney account is then debited for the specified amount (1005), while the lender's eMoney account is credited the specified amount (1006). Both the lender and the subscriber may receive confirmation that the loan has been repaid via SMS or some other communication channel. The mFS platform thus processes the subscriber's micro-loan repayment request, updates lender and subscriber's eMoney balances, updates repayment schedule and reminders, logs the transaction, and sends transaction details to a specified mFS platform bank. -
FIG. 11A illustrates a subscriber receiving a direct deposit from an employer or other entity. Subscribers to the mFS platform have the ability to receive any direct deposit into their eMoney account. Subscribers may be asked by their employers to provide account information in order to set up direct deposit. The employer then submits a direct deposit request using their existing processes (i.e the processes they use for a normal checking or savings bank account). Once the direct deposit is set up and a payday arrives, the employer's bank account is debited for the proper amount (1101) and the employer's mFS account is credited with that amount (1102). Then, once the funds have been received at the mFS platform bank, the mFS platform bank sweeps the employers direct deposit balance (1103) into a mFS platform master account (1104) and notifies the mFS platform of each account to be incremented (including the subscriber's mobile wallet (eMoney) account). The subscriber's eMoney account is then credited with the paycheck amount (1105) upon which the eMoney may be used to pay for goods, pay bills, top up airtime, transfer to other entities or for cash withdrawal. - The subscriber does not need to have a bank account to participate in direct deposit. The employer's bank can communicate with the mFS platform's bank to perform the necessary steps in directly depositing the subscriber's paycheck in his or her eMoney mobile wallet account. The bank facilitates monetary deposit into the employer's bank account for direct deposit and performs an automated sweep of recent deposits from the employer's bank account into the mFS platform's master bank account. The bank also sends transaction details to the
monetary transaction system 210 including transaction logs. The monetary transaction system receives a list of eMoney accounts that are to be credited directly from the employer (or bank), processes the list and requests to establish a direct deposit, updates subscriber's eMoney balance, log the transaction, and sends transaction details to the mFS platform bank. - In a similar manner, a subscriber may receive a government welfare payment directly on their mobile device.
FIG. 11B illustrates a subscriber receiving a government social welfare payment directly into their eMoney account. In some embodiments, subscribers may need to opt-in and register with the government program for which they choose to receive the payment via their mobile wallet. Once the funds have been received, the subscriber can use that eMoney for any goods or services, as described above. Once the direct deposit has been established and a payout has been initiated, the government's welfare account deposits the money (1110) into the government's bank account for welfare payments (1111) and performs an automated sweep of recent deposits from the government's bank account (1112) into the mFS program's master bank account (1113). The bank then sends transaction details to themonetary transaction system 210 regarding the deposit. The subscriber receives a notification that the welfare payment has been credited to their eMoney account (1114). The mFS platform receives an indication of eMoney accounts that are to be credited from the government, processes the welfare payments, updates the subscriber's eMoney balance, logs the transactions, and sends transaction details to the mFS platform bank. -
FIG. 12A illustrates an agent administrator distributing eMoney to various recipients. An agent administrator, as explained above, is a person who acts as an agent company's representative. The agent administrator deposits, withdraws, and distributes funds into and out of the agent company's bank account. When an agent administrator deposits cash into an agent company's bank account, it is credited as eMoney to the agent company's account. In order to provide the agent branches with eMoney, the agent administrator first moves the eMoney from the agent company's account (1201) to the branch accounts (1202). This is performed using the agent administrator's mobile wallet application or portal. In an agent administrator money transfer, themonetary transaction system 210 processes the administrator's eMoney transfer request, updates the agent company and agent branch eMoney balances, logs the transaction, and sends transaction details to the mFS platform bank. -
FIG. 12B illustrates an agent company deposit. The agent company has an eMoney account in themonetary transaction system 210 that may also include a corresponding bank account (that may be created automatically upon creation of the agent company's eMoney account). After the agent company's bank account has been set up, the agent administrator can make deposits into that account. AsFIG. 12B shows, once cash (1205) has been deposited into the bank account (1206), it is transferred to a mFS platform master account (1208) that includes all or a part of the mFS platform's funds. The agent company's bank account is decreased by the deposit amount (1207), while the agent company's eMoney account balance is correspondingly increased (1210). At this time, the agent company account is credited with eMoney. The agent company's bank facilitates a physical cash deposit into the agent company's bank account and performs an automated sweep (1209) of recent deposits from the agent company's bank account into the mFS platform's master bank account. The agent company's bank then sends transaction details to themonetary transaction system 210. The agent administrator physically delivers the cash (or form of money such as a check or money order) to a bank branch for deposit. The monetary transfer system receives transaction details from the agent company's bank about recent transactions (including deposits, as shown inFIG. 12B . -
FIG. 13 illustrates an agent company withdrawal. To make a cash withdrawal for an agent company, the agent administrator requests a withdrawal using the agent administrator mobile wallet application. Themonetary transaction system 210 then notifies the bank that a certain amount of eMoney is to be transferred from the master mFS account (1302) to the agent company bank account (1303). When the money is in the agent company bank account, the agent administrator can withdraw the cash by traditional withdrawal means. The mFS master bank receives transaction details from themonetary transaction system 210 about recent transactions (recent withdrawals in this case). The mFS master bank performs an automated sweep (1304) of the mFS platform's master bank account to reflect the recent withdrawal request from agent the agent company (1301). The agent company's eMoney account is reduced by the amount of the withdrawal. The agent company also sends transaction details to themonetary transaction system 210. The agent administrator can request withdrawal via the agent administrator mobile wallet application and physically withdrawal cash (1305) from the agent company's bank branch (1306). The mFS platform processes the agent company's withdrawal request, updates agent company and agent branch eMoney balances, logs the transaction, and sends transaction details to an mFS platform-specified bank. - Attention will now be turned to embodiments in which subscribers have bank accounts associated with their mobile wallets. The
monetary transaction system 210 provides similar functionality to consumers that have bank or credit union accounts. Although many different transactions are presented herein, many more and varied types of transactions may be processed by the monetary transaction system. In the following figures, “$C” refers to cash balance, “$DC” refers to a debit card (prepaid) balance and “$PIN” refers to a recharge PIN value. -
FIG. 14 describes a subscriber deposit at an agent branch. The subscriber has a registered and activated (prepaid) debit card at an agent branch location. The prepaid debit card is associated with the mobile wallet application in the subscriber's mobile device. As such, the debit card is linked to the subscriber's account in themonetary transaction system 210. To deposit cash onto the mobile wallet, the subscriber informs the agent that they want to deposit a specified amount of cash (1401). The agent takes the cash and notifies themonetary transaction system 210 of the deposit using their point of sale (POS) system or the agent mobile wallet application (1402), and themonetary transaction system 210 credits the subscriber's mobile wallet account (1403). The funds collected at the cash register typically do not reach a bank account until the reconciliation and settlement of funds occurs between the agent and the mFS owner's bank. - The subscriber's bank then receives a settlement report from the card processor and receives funds from the agent's bank. The agent or agent manager physically deposits the cash into the subscriber's mobile wallet account via their POS system or agent manager/agent mobile wallet application. The monetary transaction system processes the deposit request, increments the subscriber's mobile wallet balance within the card processor and logs the transaction. An external card processor increments the subscriber's mobile wallet balance and sends reports to the bank for settlement on a regular (e.g. nightly) basis.
- In one embodiment, the
monetary transaction system 210 is implemented to deposit funds into a bank or credit union account using a mobile wallet. Thecommunications module 215 of themonetary transaction system 210 receives communication from an agent branch over a communication channel (step 1410). The agent communication indicates that asubscriber 205 desires to deposit a specified amount of funds into a bank or credit union account. Thetransaction processor 216 validates the status of the bank or credit union account (step 1420), determines if the agent branch is authorized to deposit money (step 1430), and performs a limit check and/or a velocity check on the bank or credit union account (step 1440). The monetary transaction system then credits the bank or credit union account with the specified amount of funds (step 1450), returns a notification to the agent branch confirming the deposit (step 1460) and notifies the subscriber that the specified amount of funds was deposited in the bank or credit union account using at least one of the communication channels connected to the monetary transaction system (step 1470). Accordingly, cash may be deposited into a bank or credit union account associated with a subscriber's mobile wallet. -
FIG. 15 illustrates a subscriber deposit that is performed with a non-agent. In some economies, subscribers may have the ability to leverage other channels outside of agents to deposit funds onto their card. One deposit method is a PIN-based recharge that allows a subscriber to purchase a PIN worth the deposit value. The PIN can then be redeemed via an interactive voice response (IVR) system or via the subscriber's mobile wallet application. The mobile wallet application will allow themonetary transaction system 210 to deposit the funds onto the subscriber's card. The retailer's bank settles with the PIN card provider's bank and the PIN card provider's bank settles with the mFS platform's bank for the deposit. The subscriber gives cash to the agent (1501) which increases the agent company's physical cash (1502). The subscriber uses IVR or their SIM Application to recharge mobile wallet account using a PIN card (1503). In some cases, an agent may provide the PIN card (i.e. the prepaid debit card) to the subscriber. Themonetary transaction system 210 processes the subscriber deposit request, increments the subscriber's mobile wallet balance within the card processor and logs the transaction. An external card processor decreases the subscriber's PIN card balance (1504), increments the subscriber's mobile wallet balance (1505) and send reports to the mFS platform bank for settlement. -
FIG. 16 illustrates a subscriber withdrawal at an agent branch. To withdraw cash at an agent branch from a (prepaid) debit card, a subscriber submits a withdrawal request using the mobile wallet application on their mobile device. The subscriber may also need to enter details about the agent branch that allows themonetary transaction system 210 to determine if the subscriber has sufficient funds on their debit card. The mFS platform then notifies the agent branch that it can give cash to the subscriber. If the subscriber has sufficient funds, themonetary transaction system 210 will decrement the subscriber's funds from their card (1601) and transfer it to the mobile wallet owner's account within the same card processor or bank. The agent branch (1602) then provides the withdrawn cash to the subscriber (1603). - Accordingly, the subscriber requests a cash withdrawal from their own mobile wallet account via the mobile wallet application. The agent or agent manager verifies the withdrawal request via POS authorization or SMS received on agent's phone and, once verified, gives cash to the subscriber. The
monetary transaction system 210 processes the subscriber's withdrawal request, decrements the subscriber's mobile wallet balance within the card processor and logs the transaction. An external card processor decrements the subscriber's mobile wallet balance and sends reports to the bank for settlement on a periodic basis. - In one embodiment, the
monetary transaction system 210 is implemented to withdraw funds from a bank or credit union account using a mobile wallet. Thecommunication module 215 of themonetary transaction system 210 receives a communication from asubscriber 205 over a communication channel 111 (step 1610). The subscriber communication indicates thatsubscriber 205 desires to withdraw a specified amount of funds from a bank or credit union account. The transaction processor validates the status of the bank or credit union account (step 1620), determines if the balance of the bank or credit union account is sufficient to accommodate the requested withdrawal for the specified amount of funds (step 1630) and performs a limit check and/or a velocity check on the bank or credit union account (step 1640). - The
monetary transaction system 210 then returns a secure, perishable withdrawal code to thesubscriber 205 over at least one of the communication channels (step 1650) and receives a subsequent agent branch communication indicating that the withdrawal code has been presented to an agent (step 1660). Themonetary transaction system 210 then debits the bank or credit union account by the specified amount of funds (step 1670), returns a notification to the agent branch confirming the withdrawal (1680) and notifies the subscriber that the specified amount of funds were withdrawn from the bank or credit union account using at least one of the communication channels connected to the monetary transaction system (step 1690). Accordingly, a subscriber can withdraw cash stored on their mobile wallet from an agent branch or a non-agent branch. -
FIG. 17A illustrates a subscriber withdrawal using an automated teller machine (ATM). Subscribers in many countries have access to ATM machines and can use their mobile wallets to perform withdrawals using their (prepaid) debit card at most ATMs. Banks provide ATMs to their customers (typically at no charge) and to non-customers (typically for a small charge). The subscriber requests a cash withdrawal from the subscriber's mobile wallet via the subscriber's debit card that is associated with the mobile wallet. The bank providing the debit card may receive settlement reports from the card processor and may transfer and/or settle funds from subscriber's account to the ATM network bank. An extern card processor decrements the subscriber's mobile wallet balance (1701) and sends transaction reports to the bank for settlement. Accordingly, once the withdrawal request has been received and the external card processor (e.g. Visa® or MasterCard®) (1702) has debited the debit card account, the ATM (1703) dispenses the withdrawn cash to the subscriber (1704). -
FIG. 17B illustrates a subscriber-to-subscriber money transfer. An mFS subscriber (1705) may send money to another mFS subscriber (1706). To do so, subscriber A enters information identifying subscriber B (e.g. a phone number, email address or other identifier). Themonetary transaction system 210 determines if there are enough funds to complete the transaction, and if so, themonetary transaction system 210 decrements subscriber A's debit card and credits subscriber B's debit card. The subscriber, accordingly, may request to send money from their own mobile wallet (i.e. money stored on a (prepaid) debit card) account via the subscriber mobile wallet application. The other subscriber receives a notification that the balance of the debit card associated with their mobile wallet has increased. The bank receives a settlement report from the debit card processor and transfers or settles funds from subscriber A's account to subscriber B's account (if necessary). Themonetary transaction system 210 processes the transfer request, updates subscriber A's and subscriber B's debit cards that are associated with their mobile wallets and logs the transaction. The external card processor decrements subscriber A's debit card balance, increments subscriber B's debit card balance and sends transaction reports to the mFS platform bank for settlement. -
FIG. 17C illustrates subscriber-to-non-subscriber money transfers. In this embodiment, subscriber A (an mFS subscriber) wishes to send money to another subscriber (a non-mFS subscriber). The transaction is initiated in the same fashion as described above inFIG. 17B . However, since subscriber B does not have an mFS account, themonetary transaction system 210 cannot credit them with money. Instead, themonetary transaction system 210 sends a communication (e.g. a SMS) to subscriber B (1708) with an authorization code and instructions for how to pick up the cash. Themonetary transaction system 210 puts a hold on subscriber A's debit card for the amount transferred (1707). Subscriber B has a specified time period in which to pick up the cash before the hold expires and the amount is credited back to the debit card associated with subscriber A's mobile wallet account. The agent branch verifies the authorization code via POS or their agent mobile wallet application (1709) and gives the cash to the non-subscriber (1710). (In some countries, an agent network needs to be capable of giving cash to a subscriber based on the money transfer reference number). - The mFS bank receives a settlement report from the card processor and transfer and settle funds from subscriber A's debit card to the agent's bank (if necessary). The
monetary transaction system 210 processes the money transfer request, decrements subscriber A's mobile wallet balance within the card processor, generates a money transfer reference number, authorizes the reference number to be paid out by the agent and logs the transaction. An external card processor decrements subscriber A's mobile wallet balance and sends periodic transaction reports to the bank for settlement. Thus, as seen inFIGS. 17B and 17C , money may be transferred from subscriber to subscriber and from subscriber to non-subscriber. - Subscribers may similarly send money internationally to both subscribers and non-subscribers.
FIG. 18A illustrates a subscriber-to-subscriber international money transfer. In this embodiment, subscriber A wishes to send cash to subscriber B who resides in another country. As in the embodiments described above where money was transferred internationally, themonetary transaction system 210 may use one or more international money transfer organizations or remittance companies such as MoneyGram® to transfer the money. Subscriber A initiates the international money transfer using his or her phone. Subscriber A's debit card account is decremented by the transfer amount (1801). The money is transferred between countries using an international money transfer organization (1802). In this case, subscriber B has an mFS eMoney account with a foreign mFS platform that is also affiliated with the selected international money transfer organization. That organization can then credit subscriber B's eMoney account directly (1803). - Thus, subscriber A requests to send money from their debit card account via the subscriber mobile wallet application. Subscriber B receives a notification (including a MoneyGram® Reference Number (MGRN) (or other reference number when other international money transfer organizations are used) and instructions on how to access the eMoney) that their eMoney balance has increased. The mFS bank receives settlement reports from the debit card processor and transfers and/or settles funds from subscriber's account to the international organization's bank. The
monetary transfer system 210 processes the transfer request, update subscriber A's and subscriber B's eMoney balances and logs the transaction. An external card processor decrements subscriber A's mobile wallet balance and sends periodic transaction reports to the bank for settlement. -
FIG. 18B illustrates a subscriber-to-non-subscriber international money transfer. In this embodiment, subscriber A wishes to send cash to subscriber B who resides in another country. As above, themonetary transaction system 210 uses an international money transfer organization (1806) to transfer the money between countries. Once the transfer has been initiated by subscriber A, the international money transfer organization debits subscriber A's debit card account (1805) and transfers that money to subscriber B. Subscriber B (1807) receives a notification (e.g. via SMS) with pick up instructions and a transfer ID number. Subscriber B can then go to an agent company (1808), show them the notification (including, perhaps an authorization code), and receive the transferred money (1809). - Similar to the transaction described in
FIG. 18A , the embodiment of 19A illustrates a transaction where a subscriber receives an international money transfer. Subscriber B (1901) initiates a money transfer using their mobile wallet application. The international money transfer organization (1902) debits subscriber B's eMoney account balance. This money is then transferred by the international money transfer organization to subscriber A. Subscriber A receives a notification along with a transfer ID number indicating that their debit card account has been credited with the transferred money (1903). -
FIG. 19B illustrates a non-subscriber-to-subscriber international money transfer. This scenario is very similar to that described inFIG. 19A from the mFS subscriber's perspective, except that their eMoney account is credited here, and their debit card account was credited in 19A. The initiator, subscriber B (1905), does not have an mFS account and, as a result, takes their cash to an international money transfer organization (e.g. MoneyGram®) or other remittance company's agent (1906) to send it to subscriber A's mobile wallet eMoney account. The international money transfer organization (1907) then transfers the specified amount to subscriber A (1908) and subscriber A's mobile wallet eMoney account is credited with the amount of the transfer. Subscriber A may receive a transaction ID number, along with an indication that the transfer has occurred. The mFS bank may receive settlement reports from the card processor and settle funds from the international money transfer organization's bank to subscriber A's mobile wallet account. The monetary transaction system processes the money transfer request, updates subscriber A's mobile wallet balance within the card processor and logs the transaction. An external card processor increments subscriber A's mobile wallet balance and sends periodic transaction reports to the mFS bank for settlement. - Other functionality described above in relation to using an eMoney mobile wallet account may also apply to banked subscribers using a debit card associated with their mobile wallet. Such subscribers may buy airtime for their mobile device, pay bills, make retail purchases, receive direct deposits, and perform other functionality.
- In one embodiment, the
monetary transaction system 210 is implemented to add a mobile wallet platform stored value account to a mobile wallet. The stored value account may include eMoney or other monetary credits. In the embodiment,communication module 215 ofmonetary transaction system 210 may receive subscriber data for anunbanked subscriber 205 over a communication channel. The transaction processor may perform validation checks on the unbanked subscriber to validate that the unbanked subscriber is not exceeding a specified allowable number of accounts per subscriber. Themonetary transaction system 210 may then send subscriber data to another entity (such as a third party verification system) for identification of the unbanked subscriber. Themonetary transaction system 210 receives results from the third party verification system indicating that the subscriber data appropriately identifies the unbanked subscriber, creates a stored value account for the unbanked subscriber that maintains a recorded balance for the created stored value account, adds the stored value account to the unbanked subscriber's mobile wallet and notifies the unbanked subscriber of the addition of the stored value account over at least one communication channel connected to the mobile wallet platform. - In another embodiment, the
monetary transaction system 210 is implemented to add a third party stored value account to a mobile wallet. Themonetary transaction system 210 receives unbanked subscriber data, including account details, over a communication channel. Thetransaction processor 216 performs a validation check on the unbanked subscriber to validate that the unbanked subscriber is not exceeding a specified allowable number of accounts per subscriber. If the validation check is ok, themonetary transaction system 210 sends subscriber data to a third party verification system for identification of the unbanked subscriber. In some cases, validating the status of the sender or the recipient includes performing a check on the specified sender or recipient to comply with the office of foreign assets control. Themonetary transaction system 210 then receives results from the third party verification system indicating that the subscriber data appropriately identifies the unbanked subscriber, and submits the unbanked subscriber's account details to a third party account processor. Themonetary transaction system 210 receives an indication from the third party account processor that third party account processor created a third party stored value account for the subscriber. The transaction processor maintains a link between the subscriber data and the third party stored value account and adds the third party stored value account to the unbanked subscriber's mobile wallet. Themonetary transaction system 210 then notifies the unbanked subscriber of the addition of the third party stored value account over a communication channels connected to the monetary transaction system. - In another embodiment, the
monetary transaction system 210 is implemented to add a bank or credit union account to a mobile wallet. Thecommunication module 215 receives subscriber data, including bank or credit union account details, over acommunication channel 111. Thetransaction processor 216 performs validation checks on the subscriber to validate that the subscriber is not exceeding a specified allowable number of accounts per subscriber and sends subscriber data to a third party verification system for identification of the subscriber. The communication module then receives results from the third party verification system indicating that the subscriber data appropriately identifies the subscriber. Upon receiving these results, themonetary transaction system 210 submits bank or credit union account details for validation by the transaction processor, receives an indication that the bank or credit union account details correspond to a valid bank or credit union account, maintains a link between the subscriber data and the bank or credit union account and notifies the subscriber of the bank or credit union account validation over a communication channel. - In still another embodiment, the monetary transaction system is implemented to add a debit or credit card account to a mobile wallet. The
communication module 215 receives subscriber data, including a debit or credit card account number, over acommunication channel 111 connected to the monetary transaction system. The transaction processor performs validation checks on the subscriber to validate that the subscriber is not exceeding a specified allowable number of accounts per subscriber. The communication module sends subscriber data to a third party verification system for identification of the subscriber and receives results from the third party system indicating that the subscriber data appropriately identifies the subscriber. Themonetary transaction system 210 securely stores the debit or credit card account number for access by the mobile wallet (e.g. inmemory 217 or transaction database 225), adds the debit or credit card account number to the subscriber's mobile wallet, and notifies the subscriber of the addition of the debit or credit card account number. It should be noted that many other transactions can take place over the monetary transaction system, and that the embodiments described herein should not be read as limiting. - Embodiments of the invention can adhere to Know Your Customer (KYC) rules in the US by performing Customer Identification Program (CIP) checks as required by the Bank Secrecy Act and US PATRIOT Act. A minimum amount of information can be gathered about a customer, such as, for example, first name, last name, date of birth, government ID Type, government ID number and address. The CIP processes are designed to validate customer identity against government blacklists and assists in the prevention of money laundering and terrorist financing. A combination of non-documentary and documentary verification can be used to ensure beyond a reasonable doubt the identity of the customer.
- Non-documentary verification can occur through the presentment of the information that was collected from the user to an external third party, such as, for example, Lexis Nexis®. Documentary verification can occur if non-documentary verification fails, then the user is asked to present an unexpired government ID. Various differ forms of identification including driver's license, passport, alien identification (e.g., green card or work visa), and Mexican Consular identification card, can be accepted.
- Embodiments of the invention can perform Anti-Money Laundering (AML) and Combating the Financing of Terrorism (CFT) checks. AML and CFT checks can be performed using transaction monitoring methods to flag names and suspicious transactions for further investigation. The mobile wallet platform can perform AML and CFT checks on all electronic financial transactions to ensure that electronic funds are not being used for money laundering or terrorism. Transaction limits can be placed on user accounts. The transaction limits are fully configurable for each particular use case, channel and payment method that allows maximum flexibility to restrict higher risk use cases. Velocity checks can also be performed. Velocity Checks ensure that subscribers are not abusing the mobile wallet platform within the allowable limits.
- The present invention may be embodied in other specific forms without departing from its spirit or essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
Claims (1)
Priority Applications (8)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/964,707 US20130332347A1 (en) | 2011-06-03 | 2013-08-12 | Monetary transaction system |
US14/213,543 US20140201070A1 (en) | 2011-06-03 | 2014-03-14 | Monetary transaction system |
US14/928,105 US20160055583A1 (en) | 2011-06-03 | 2015-10-30 | Mobile global exchange platform |
US15/201,152 US9892386B2 (en) | 2011-06-03 | 2016-07-01 | Monetary transaction system |
US15/809,872 US11295281B2 (en) | 2011-06-03 | 2017-11-10 | Monetary transaction system |
US16/569,348 US11120413B2 (en) | 2011-06-03 | 2019-09-12 | Monetary transaction system |
US17/380,839 US20210350342A1 (en) | 2011-06-03 | 2021-07-20 | Monetary transaction system |
US17/584,064 US20220147969A1 (en) | 2011-06-03 | 2022-01-25 | Monetary transaction system |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201161493064P | 2011-06-03 | 2011-06-03 | |
US201161522099P | 2011-08-10 | 2011-08-10 | |
US13/484,199 US8538845B2 (en) | 2011-06-03 | 2012-05-30 | Monetary transaction system |
US13/964,707 US20130332347A1 (en) | 2011-06-03 | 2013-08-12 | Monetary transaction system |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/484,199 Continuation US8538845B2 (en) | 2011-06-03 | 2012-05-30 | Monetary transaction system |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/213,543 Continuation US20140201070A1 (en) | 2011-06-03 | 2014-03-14 | Monetary transaction system |
US14/928,105 Continuation-In-Part US20160055583A1 (en) | 2011-06-03 | 2015-10-30 | Mobile global exchange platform |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130332347A1 true US20130332347A1 (en) | 2013-12-12 |
Family
ID=47262416
Family Applications (8)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/484,199 Active US8538845B2 (en) | 2011-06-03 | 2012-05-30 | Monetary transaction system |
US13/964,707 Abandoned US20130332347A1 (en) | 2011-06-03 | 2013-08-12 | Monetary transaction system |
US14/213,543 Abandoned US20140201070A1 (en) | 2011-06-03 | 2014-03-14 | Monetary transaction system |
US15/201,152 Active US9892386B2 (en) | 2011-06-03 | 2016-07-01 | Monetary transaction system |
US15/809,872 Active 2034-01-19 US11295281B2 (en) | 2011-06-03 | 2017-11-10 | Monetary transaction system |
US16/569,348 Active US11120413B2 (en) | 2011-06-03 | 2019-09-12 | Monetary transaction system |
US17/380,839 Pending US20210350342A1 (en) | 2011-06-03 | 2021-07-20 | Monetary transaction system |
US17/584,064 Pending US20220147969A1 (en) | 2011-06-03 | 2022-01-25 | Monetary transaction system |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/484,199 Active US8538845B2 (en) | 2011-06-03 | 2012-05-30 | Monetary transaction system |
Family Applications After (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/213,543 Abandoned US20140201070A1 (en) | 2011-06-03 | 2014-03-14 | Monetary transaction system |
US15/201,152 Active US9892386B2 (en) | 2011-06-03 | 2016-07-01 | Monetary transaction system |
US15/809,872 Active 2034-01-19 US11295281B2 (en) | 2011-06-03 | 2017-11-10 | Monetary transaction system |
US16/569,348 Active US11120413B2 (en) | 2011-06-03 | 2019-09-12 | Monetary transaction system |
US17/380,839 Pending US20210350342A1 (en) | 2011-06-03 | 2021-07-20 | Monetary transaction system |
US17/584,064 Pending US20220147969A1 (en) | 2011-06-03 | 2022-01-25 | Monetary transaction system |
Country Status (6)
Country | Link |
---|---|
US (8) | US8538845B2 (en) |
EP (1) | EP2715632A4 (en) |
MX (1) | MX2013014209A (en) |
RU (1) | RU2620715C2 (en) |
SA (1) | SA112330567B1 (en) |
WO (1) | WO2013025273A1 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9208488B2 (en) | 2011-11-21 | 2015-12-08 | Mozido, Inc. | Using a mobile wallet infrastructure to support multiple mobile wallet providers |
WO2017006194A1 (en) * | 2015-07-07 | 2017-01-12 | DOWNER, Albert | System of payment made in real time |
US9892386B2 (en) | 2011-06-03 | 2018-02-13 | Mozido, Inc. | Monetary transaction system |
US10438196B2 (en) | 2011-11-21 | 2019-10-08 | Mozido, Inc. | Using a mobile wallet infrastructure to support multiple mobile wallet providers |
Families Citing this family (227)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140019352A1 (en) | 2011-02-22 | 2014-01-16 | Visa International Service Association | Multi-purpose virtual card transaction apparatuses, methods and systems |
US8762263B2 (en) | 2005-09-06 | 2014-06-24 | Visa U.S.A. Inc. | System and method for secured account numbers in proximity devices |
US20170011391A1 (en) * | 2006-09-24 | 2017-01-12 | Rfcyber Corp. | Method and apparatus for mobile payment |
US8121942B2 (en) | 2007-06-25 | 2012-02-21 | Visa U.S.A. Inc. | Systems and methods for secure and transparent cardless transactions |
US7739169B2 (en) | 2007-06-25 | 2010-06-15 | Visa U.S.A. Inc. | Restricting access to compromised account information |
US7937324B2 (en) | 2007-09-13 | 2011-05-03 | Visa U.S.A. Inc. | Account permanence |
US8219489B2 (en) | 2008-07-29 | 2012-07-10 | Visa U.S.A. Inc. | Transaction processing using a global unique identifier |
BRPI0921124A2 (en) | 2008-11-06 | 2016-09-13 | Visa Int Service Ass | system for authenticating a consumer, computer implemented method, computer readable medium, and server computer. |
US9715681B2 (en) | 2009-04-28 | 2017-07-25 | Visa International Service Association | Verification of portable consumer devices |
US8893967B2 (en) | 2009-05-15 | 2014-11-25 | Visa International Service Association | Secure Communication of payment information to merchants using a verification token |
US8602293B2 (en) | 2009-05-15 | 2013-12-10 | Visa International Service Association | Integration of verification tokens with portable computing devices |
US9105027B2 (en) | 2009-05-15 | 2015-08-11 | Visa International Service Association | Verification of portable consumer device for secure services |
US8534564B2 (en) | 2009-05-15 | 2013-09-17 | Ayman Hammad | Integration of verification tokens with mobile communication devices |
US7891560B2 (en) | 2009-05-15 | 2011-02-22 | Visa International Service Assocation | Verification of portable consumer devices |
US9038886B2 (en) | 2009-05-15 | 2015-05-26 | Visa International Service Association | Verification of portable consumer devices |
US10846683B2 (en) | 2009-05-15 | 2020-11-24 | Visa International Service Association | Integration of verification tokens with mobile communication devices |
US10140598B2 (en) | 2009-05-20 | 2018-11-27 | Visa International Service Association | Device including encrypted data for expiration date and verification value creation |
US10255591B2 (en) | 2009-12-18 | 2019-04-09 | Visa International Service Association | Payment channel returning limited use proxy dynamic value |
CA3045817A1 (en) | 2010-01-12 | 2011-07-21 | Visa International Service Association | Anytime validation for verification tokens |
US9424413B2 (en) | 2010-02-24 | 2016-08-23 | Visa International Service Association | Integration of payment capability into secure elements of computers |
US10255601B2 (en) | 2010-02-25 | 2019-04-09 | Visa International Service Association | Multifactor authentication using a directory server |
US9245267B2 (en) | 2010-03-03 | 2016-01-26 | Visa International Service Association | Portable account number for consumer payment account |
US9342832B2 (en) | 2010-08-12 | 2016-05-17 | Visa International Service Association | Securing external systems with account token substitution |
CN103765453B (en) | 2011-02-16 | 2018-08-14 | 维萨国际服务协会 | Snap mobile payment device, method and system |
US10586227B2 (en) | 2011-02-16 | 2020-03-10 | Visa International Service Association | Snap mobile payment apparatuses, methods and systems |
BR112013021057A2 (en) | 2011-02-22 | 2020-11-10 | Visa International Service Association | universal electronic payment devices, methods and systems |
US9280765B2 (en) | 2011-04-11 | 2016-03-08 | Visa International Service Association | Multiple tokenization for authentication |
US20120315979A1 (en) * | 2011-06-13 | 2012-12-13 | Slip Technologies, Llc | Wager slip exchange systems and methods |
US9582598B2 (en) | 2011-07-05 | 2017-02-28 | Visa International Service Association | Hybrid applications utilizing distributed models and views apparatuses, methods and systems |
US9355393B2 (en) | 2011-08-18 | 2016-05-31 | Visa International Service Association | Multi-directional wallet connector apparatuses, methods and systems |
US10121129B2 (en) | 2011-07-05 | 2018-11-06 | Visa International Service Association | Electronic wallet checkout platform apparatuses, methods and systems |
US9704155B2 (en) | 2011-07-29 | 2017-07-11 | Visa International Service Association | Passing payment tokens through an hop/sop |
US20130212399A1 (en) * | 2011-08-17 | 2013-08-15 | Geoffrey I. Cairns | Travel Vault |
US10825001B2 (en) | 2011-08-18 | 2020-11-03 | Visa International Service Association | Multi-directional wallet connector apparatuses, methods and systems |
US10242358B2 (en) | 2011-08-18 | 2019-03-26 | Visa International Service Association | Remote decoupled application persistent state apparatuses, methods and systems |
US9710807B2 (en) | 2011-08-18 | 2017-07-18 | Visa International Service Association | Third-party value added wallet features and interfaces apparatuses, methods and systems |
US9165294B2 (en) | 2011-08-24 | 2015-10-20 | Visa International Service Association | Method for using barcodes and mobile devices to conduct payment transactions |
US10223730B2 (en) | 2011-09-23 | 2019-03-05 | Visa International Service Association | E-wallet store injection search apparatuses, methods and systems |
DE202012100620U1 (en) | 2011-11-22 | 2012-06-13 | Square, Inc. | System for processing cardless payment transactions |
WO2013090797A1 (en) | 2011-12-14 | 2013-06-20 | Visa International Service Association | Online account access control by mobile device |
EP2798580A4 (en) * | 2011-12-29 | 2015-09-23 | Intel Corp | Method and system for managing multiple electronic user wallet data cards |
US10223710B2 (en) | 2013-01-04 | 2019-03-05 | Visa International Service Association | Wearable intelligent vision device apparatuses, methods and systems |
CN109508983A (en) | 2012-01-05 | 2019-03-22 | 维萨国际服务协会 | Data protection is carried out with conversion |
WO2013113004A1 (en) | 2012-01-26 | 2013-08-01 | Visa International Service Association | System and method of providing tokenization as a service |
AU2013214801B2 (en) | 2012-02-02 | 2018-06-21 | Visa International Service Association | Multi-source, multi-dimensional, cross-entity, multimedia database platform apparatuses, methods and systems |
AP2014007920A0 (en) | 2012-02-22 | 2014-09-30 | Visa Int Service Ass | Data security system using mobile communications device |
US10282724B2 (en) | 2012-03-06 | 2019-05-07 | Visa International Service Association | Security system incorporating mobile device |
US9741045B1 (en) | 2012-03-16 | 2017-08-22 | Square, Inc. | Ranking of merchants for cardless payment transactions |
US20130246296A1 (en) | 2012-03-19 | 2013-09-19 | @Pay LLC | Method for processing multimodal mobile donations via text message and email communication |
US20130297501A1 (en) | 2012-05-04 | 2013-11-07 | Justin Monk | System and method for local data conversion |
US9524501B2 (en) | 2012-06-06 | 2016-12-20 | Visa International Service Association | Method and system for correlating diverse transaction data |
WO2014008403A1 (en) | 2012-07-03 | 2014-01-09 | Visa International Service Association | Data protection hub |
US9846861B2 (en) | 2012-07-25 | 2017-12-19 | Visa International Service Association | Upstream and downstream data conversion |
US9256871B2 (en) | 2012-07-26 | 2016-02-09 | Visa U.S.A. Inc. | Configurable payment tokens |
US9665722B2 (en) | 2012-08-10 | 2017-05-30 | Visa International Service Association | Privacy firewall |
US20140052613A1 (en) | 2012-08-17 | 2014-02-20 | Square, Inc., A Delaware Corporation | Systems and methods for providing gratuities to merchants |
WO2014043278A1 (en) | 2012-09-11 | 2014-03-20 | Visa International Service Association | Cloud-based virtual wallet nfc apparatuses, methods and systems |
FR2996018A1 (en) * | 2012-09-27 | 2014-03-28 | France Telecom | DEVICE AND METHOD FOR MANAGING ACCESS TO A SET OF COMPUTER RESOURCES AND NETWORKS PROVIDED TO AN ENTITY BY A CLOUD COMPUTING SYSTEM |
US9990801B2 (en) * | 2012-09-28 | 2018-06-05 | Sightline Interactive LLC | Systems and methods for gaming account funding |
US10176478B2 (en) | 2012-10-23 | 2019-01-08 | Visa International Service Association | Transaction initiation determination system utilizing transaction data elements |
TW201419185A (en) * | 2012-11-08 | 2014-05-16 | Chien-Kang Yang | Mobile device, payment transaction system and payment transaction method |
US9911118B2 (en) | 2012-11-21 | 2018-03-06 | Visa International Service Association | Device pairing via trusted intermediary |
US10304047B2 (en) | 2012-12-07 | 2019-05-28 | Visa International Service Association | Token generating component |
AU2013370502A1 (en) * | 2012-12-28 | 2015-07-16 | Identrust, Inc. | Know your customer exchange system and method |
US10740731B2 (en) | 2013-01-02 | 2020-08-11 | Visa International Service Association | Third party settlement |
US9741051B2 (en) | 2013-01-02 | 2017-08-22 | Visa International Service Association | Tokenization and third-party interaction |
WO2014130826A2 (en) * | 2013-02-22 | 2014-08-28 | Mastercard International Incorporated | Systems, apparatus and methods for mobile companion prepaid card |
EP2770468A1 (en) * | 2013-02-25 | 2014-08-27 | Vodafone Holding GmbH | Method and system of performing a money transfer |
US10346501B2 (en) * | 2013-03-13 | 2019-07-09 | International Business Machines Corporation | Mobile enablement of existing web sites |
US9495679B2 (en) | 2013-03-15 | 2016-11-15 | @Pay Ip Holdings Llc | Automated application programming interface (API) system and method |
US11055710B2 (en) | 2013-05-02 | 2021-07-06 | Visa International Service Association | Systems and methods for verifying and processing transactions using virtual currency |
WO2014186635A1 (en) | 2013-05-15 | 2014-11-20 | Visa International Service Association | Mobile tokenization hub |
US10229400B2 (en) | 2013-06-07 | 2019-03-12 | Swoop Ip Holdings Llc | System and method for two-click validation |
US10878422B2 (en) | 2013-06-17 | 2020-12-29 | Visa International Service Association | System and method using merchant token |
KR102123494B1 (en) | 2013-07-15 | 2020-06-29 | 비자 인터네셔널 서비스 어소시에이션 | Secure remote payment transaction processing |
AU2014292980A1 (en) | 2013-07-24 | 2016-02-04 | Visa International Service Association | Systems and methods for interoperable network token processing |
AU2014294613B2 (en) | 2013-07-26 | 2017-03-16 | Visa International Service Association | Provisioning payment credentials to a consumer |
US10496986B2 (en) | 2013-08-08 | 2019-12-03 | Visa International Service Association | Multi-network tokenization processing |
CN114819961A (en) | 2013-08-08 | 2022-07-29 | 维萨国际服务协会 | Method and system for provisioning payment credentials for mobile devices |
WO2015023999A1 (en) | 2013-08-15 | 2015-02-19 | Visa International Service Association | Secure remote payment transaction processing using a secure element |
US11423371B2 (en) * | 2013-09-04 | 2022-08-23 | Raise Marketplace, Llc | Systems and methods for managing prepaid cards in a digital wallet, including transferring value from prepaid cards and managing user selected accounts |
US11423370B2 (en) * | 2013-09-04 | 2022-08-23 | Raise Marketplace, Llc | Systems and methods for transferring value to and managing user selected accounts |
US9906535B2 (en) * | 2013-09-10 | 2018-02-27 | Arthur P. GOLDBERG | Methods for rapid enrollment of users of a secure, shared computer system via social networking among people on a selective list |
US10817875B2 (en) | 2013-09-20 | 2020-10-27 | Visa International Service Association | Secure remote payment transaction processing including consumer authentication |
US20150095230A1 (en) * | 2013-09-27 | 2015-04-02 | Insperity Services, L.P. | Method, apparatus, and system for automated funding, including automated reallocation of funds |
US9978094B2 (en) | 2013-10-11 | 2018-05-22 | Visa International Service Association | Tokenization revocation list |
EP3078156A4 (en) | 2013-10-11 | 2017-07-12 | Visa International Service Association | Network token system |
US10515358B2 (en) | 2013-10-18 | 2019-12-24 | Visa International Service Association | Contextual transaction token methods and systems |
US10489779B2 (en) | 2013-10-21 | 2019-11-26 | Visa International Service Association | Multi-network token bin routing with defined verification parameters |
US10319013B2 (en) | 2013-10-28 | 2019-06-11 | Square, Inc. | Electronic ordering system |
US11803841B1 (en) | 2013-10-29 | 2023-10-31 | Block, Inc. | Discovery and communication using direct radio signal communication |
US10366387B2 (en) | 2013-10-29 | 2019-07-30 | Visa International Service Association | Digital wallet system and method |
AU2014353151B2 (en) | 2013-11-19 | 2018-03-08 | Visa International Service Association | Automated account provisioning |
KR20150065353A (en) * | 2013-12-05 | 2015-06-15 | 삼성전자주식회사 | Apparatas and method for paying using for membership card in an electronic device |
US9922322B2 (en) | 2013-12-19 | 2018-03-20 | Visa International Service Association | Cloud-based transactions with magnetic secure transmission |
US9972005B2 (en) | 2013-12-19 | 2018-05-15 | Visa International Service Association | Cloud-based transactions methods and systems |
US10433128B2 (en) | 2014-01-07 | 2019-10-01 | Visa International Service Association | Methods and systems for provisioning multiple devices |
US9846878B2 (en) | 2014-01-14 | 2017-12-19 | Visa International Service Association | Payment account identifier system |
US9256876B2 (en) * | 2014-02-03 | 2016-02-09 | Fmr Llc | Real-time spend management with savings goals |
US10108940B2 (en) * | 2014-03-25 | 2018-10-23 | Moneygram International, Inc. | Systems and methods for utilizing social media with money transfer transactions |
US10026087B2 (en) | 2014-04-08 | 2018-07-17 | Visa International Service Association | Data passed in an interaction |
US9942043B2 (en) | 2014-04-23 | 2018-04-10 | Visa International Service Association | Token security on a communication device |
US10346846B2 (en) | 2014-04-24 | 2019-07-09 | Swoop Ip Holdings Llc | SMS and social media dual authorization, management oversight, and non-password security in email based e-commerce |
US11615401B1 (en) | 2014-04-30 | 2023-03-28 | Wells Fargo Bank, N.A. | Mobile wallet authentication systems and methods |
US10997592B1 (en) | 2014-04-30 | 2021-05-04 | Wells Fargo Bank, N.A. | Mobile wallet account balance systems and methods |
US11610197B1 (en) | 2014-04-30 | 2023-03-21 | Wells Fargo Bank, N.A. | Mobile wallet rewards redemption systems and methods |
US11288660B1 (en) | 2014-04-30 | 2022-03-29 | Wells Fargo Bank, N.A. | Mobile wallet account balance systems and methods |
US11748736B1 (en) | 2014-04-30 | 2023-09-05 | Wells Fargo Bank, N.A. | Mobile wallet integration within mobile banking |
US11461766B1 (en) | 2014-04-30 | 2022-10-04 | Wells Fargo Bank, N.A. | Mobile wallet using tokenized card systems and methods |
US11574300B1 (en) | 2014-04-30 | 2023-02-07 | Wells Fargo Bank, N.A. | Mobile wallet systems and methods using trace identifier using card networks |
US9652770B1 (en) | 2014-04-30 | 2017-05-16 | Wells Fargo Bank, N.A. | Mobile wallet using tokenized card systems and methods |
AU2015253182B2 (en) | 2014-05-01 | 2019-02-14 | Visa International Service Association | Data verification using access device |
SG10202007850WA (en) | 2014-05-05 | 2020-09-29 | Visa Int Service Ass | System and method for token domain control |
US10026083B1 (en) | 2014-05-11 | 2018-07-17 | Square, Inc. | Tab for a venue |
US9760877B1 (en) * | 2014-05-21 | 2017-09-12 | Isaac S. Daniel | System and method for secure payment processing using subscriber identity module cards |
CN106465112A (en) | 2014-05-21 | 2017-02-22 | 维萨国际服务协会 | Offline authentication |
US11023890B2 (en) | 2014-06-05 | 2021-06-01 | Visa International Service Association | Identification and verification for provisioning mobile application |
US9780953B2 (en) | 2014-07-23 | 2017-10-03 | Visa International Service Association | Systems and methods for secure detokenization |
US10484345B2 (en) | 2014-07-31 | 2019-11-19 | Visa International Service Association | System and method for identity verification across mobile applications |
US10445739B1 (en) | 2014-08-14 | 2019-10-15 | Wells Fargo Bank, N.A. | Use limitations for secondary users of financial accounts |
US9775029B2 (en) | 2014-08-22 | 2017-09-26 | Visa International Service Association | Embedding cloud-based functionalities in a communication device |
US10140615B2 (en) | 2014-09-22 | 2018-11-27 | Visa International Service Association | Secure mobile device credential provisioning using risk decision non-overrides |
WO2016049636A2 (en) | 2014-09-26 | 2016-03-31 | Visa International Service Association | Remote server encrypted data provisioning system and methods |
US11257074B2 (en) | 2014-09-29 | 2022-02-22 | Visa International Service Association | Transaction risk based token |
US10015147B2 (en) | 2014-10-22 | 2018-07-03 | Visa International Service Association | Token enrollment system and method |
GB201419016D0 (en) | 2014-10-24 | 2014-12-10 | Visa Europe Ltd | Transaction Messaging |
US10325261B2 (en) | 2014-11-25 | 2019-06-18 | Visa International Service Association | Systems communications with non-sensitive identifiers |
US11620643B2 (en) | 2014-11-26 | 2023-04-04 | Visa International Service Association | Tokenization request via access device |
SG11201703526VA (en) | 2014-12-12 | 2017-05-30 | Visa Int Service Ass | Provisioning platform for machine-to-machine devices |
US10257185B2 (en) | 2014-12-12 | 2019-04-09 | Visa International Service Association | Automated access data provisioning |
US11699148B2 (en) | 2014-12-23 | 2023-07-11 | Swoop Ip Holdings Llc | Email address token integration |
US10187363B2 (en) | 2014-12-31 | 2019-01-22 | Visa International Service Association | Hybrid integration of software development kit with secure execution environment |
US10990974B1 (en) | 2015-01-15 | 2021-04-27 | Wells Fargo Bank, N.A. | Identity verification services and user information provision via application programming interface |
US10621658B1 (en) | 2015-01-15 | 2020-04-14 | Wells Fargo Bank, N.A. | Identity verification services with identity score through external entities via application programming interface |
US10937025B1 (en) | 2015-01-15 | 2021-03-02 | Wells Fargo Bank, N.A. | Payment services via application programming interface |
US10997654B1 (en) | 2015-01-15 | 2021-05-04 | Wells Fargo Bank, N.A. | Identity verification services through external entities via application programming interface |
US10096009B2 (en) | 2015-01-20 | 2018-10-09 | Visa International Service Association | Secure payment processing using authorization request |
US11551198B2 (en) | 2015-01-28 | 2023-01-10 | Swoop Ip Holdings Llc | Email-based e-commerce with near field communication |
US11250391B2 (en) | 2015-01-30 | 2022-02-15 | Visa International Service Association | Token check offline |
US11176554B2 (en) | 2015-02-03 | 2021-11-16 | Visa International Service Association | Validation identity tokens for transactions |
US10977657B2 (en) | 2015-02-09 | 2021-04-13 | Visa International Service Association | Token processing utilizing multiple authorizations |
US11853919B1 (en) | 2015-03-04 | 2023-12-26 | Wells Fargo Bank, N.A. | Systems and methods for peer-to-peer funds requests |
US20160267444A1 (en) * | 2015-03-11 | 2016-09-15 | Mark Mathenge Mutahi | Payments through Virtualization of a Physical Point of Sale (POS) Terminal and Money Transfer Using Mobile Device |
US10164996B2 (en) | 2015-03-12 | 2018-12-25 | Visa International Service Association | Methods and systems for providing a low value token buffer |
US10354246B1 (en) | 2015-03-18 | 2019-07-16 | Square, Inc. | Cash transaction machine |
SG11201708726PA (en) * | 2015-03-26 | 2017-11-29 | Einnovations Holdings Pte Ltd | System and method for facilitating remittance |
US10333921B2 (en) | 2015-04-10 | 2019-06-25 | Visa International Service Association | Browser integration with Cryptogram |
US9998978B2 (en) | 2015-04-16 | 2018-06-12 | Visa International Service Association | Systems and methods for processing dormant virtual access devices |
US10552834B2 (en) | 2015-04-30 | 2020-02-04 | Visa International Service Association | Tokenization capable authentication framework |
US10977640B2 (en) * | 2015-07-07 | 2021-04-13 | The Western Union Company | Systems and methods for implementing global money transfers |
WO2017066792A1 (en) | 2015-10-15 | 2017-04-20 | Visa International Service Association | Instant token issuance system |
US10367905B2 (en) * | 2015-10-22 | 2019-07-30 | The Western Union Company | Integration framework and user interface for embedding transfer services into applications |
US10664843B2 (en) | 2015-12-04 | 2020-05-26 | Visa International Service Association | Unique code for token verification |
US11144905B1 (en) * | 2015-12-21 | 2021-10-12 | Modopayments, Llc | Payment processing using electronic benefit transfer (EBT) system |
EP3400696B1 (en) | 2016-01-07 | 2020-05-13 | Visa International Service Association | Systems and methods for device push provisioning |
US11080696B2 (en) | 2016-02-01 | 2021-08-03 | Visa International Service Association | Systems and methods for code display and use |
US11501288B2 (en) | 2016-02-09 | 2022-11-15 | Visa International Service Association | Resource provider account token provisioning and processing |
US10313321B2 (en) | 2016-04-07 | 2019-06-04 | Visa International Service Association | Tokenization of co-network accounts |
CN109074578A (en) | 2016-04-19 | 2018-12-21 | 维萨国际服务协会 | System and method for executing push transaction |
US11025779B1 (en) | 2016-04-22 | 2021-06-01 | Wells Fargo Bank, N.A. | Automated payment reminders |
US10740750B2 (en) * | 2016-05-04 | 2020-08-11 | Paypal, Inc. | On-demand payment generation transaction systems |
US11250424B2 (en) | 2016-05-19 | 2022-02-15 | Visa International Service Association | Systems and methods for creating subtokens using primary tokens |
KR102508836B1 (en) | 2016-06-03 | 2023-03-10 | 비자 인터네셔널 서비스 어소시에이션 | Sub-token management system for connected devices |
US11068899B2 (en) | 2016-06-17 | 2021-07-20 | Visa International Service Association | Token aggregation for multi-party transactions |
WO2017223525A1 (en) | 2016-06-24 | 2017-12-28 | Visa International Service Association | Unique token authentication cryptogram |
US20180012240A1 (en) * | 2016-07-06 | 2018-01-11 | IRIO Inc. | System and method of communicating informational messages and monitoring receipt and use of messages |
SG11201808998RA (en) | 2016-07-11 | 2018-11-29 | Visa Int Service Ass | Encryption key exchange process using access device |
CA3026224A1 (en) | 2016-07-19 | 2018-01-25 | Visa International Service Association | Method of distributing tokens and managing token relationships |
US10970715B1 (en) | 2016-08-23 | 2021-04-06 | Wells Fargo Bank. N.A. | Systems and methods for multi-channel onboarding of a mobile wallet |
SG10201607027UA (en) * | 2016-08-23 | 2018-03-28 | Mastercard Asia Pacific Pte Ltd | A system and method for triggering an electronic payment between a first entity and a second entity |
US10509779B2 (en) | 2016-09-14 | 2019-12-17 | Visa International Service Association | Self-cleaning token vault |
US11568418B2 (en) * | 2016-09-30 | 2023-01-31 | Block, Inc. | Payment application based fund transfer |
US11468414B1 (en) | 2016-10-03 | 2022-10-11 | Wells Fargo Bank, N.A. | Systems and methods for establishing a pull payment relationship |
SG10201609915VA (en) * | 2016-11-25 | 2018-06-28 | Mastercard International Inc | System and method for use in performing an electronic transaction with a smart card |
SG11201903468RA (en) | 2016-11-28 | 2019-05-30 | Visa Int Service Ass | Access identifier provisioning to application |
US10440102B2 (en) | 2016-12-08 | 2019-10-08 | Bank Of America Corporation | Multicomputer processing of client device request data using centralized event orchestrator and dynamic endpoint engine |
US10216830B2 (en) | 2016-12-08 | 2019-02-26 | Bank Of America Corporation | Multicomputer processing of client device request data using centralized event orchestrator and link discovery engine |
US10264056B2 (en) | 2016-12-08 | 2019-04-16 | Bank Of America Corporation | Multicomputer processing of an event request from an event origination device with centralized event orchestration |
US10217087B2 (en) | 2016-12-08 | 2019-02-26 | Bank Of America Corporation | Multicomputer processing of client device request data using centralized event orchestrator |
US10298575B2 (en) | 2016-12-08 | 2019-05-21 | Bank Of America Corporation | Multicomputer processing of an event authentication request with centralized event orchestration |
US10310712B2 (en) | 2016-12-08 | 2019-06-04 | Bank Of America Corporation | Multicomputer processing of client device request data with centralized event orchestration |
US10296882B2 (en) | 2016-12-08 | 2019-05-21 | Bank Of America Corporation | Multicomputer processing of client device request data using centralized event orchestrator and link discovery engine |
US10303335B2 (en) | 2016-12-08 | 2019-05-28 | Bank Of America Corporation | Multicomputer processing of client device request data with centralized event orchestration |
US10915899B2 (en) | 2017-03-17 | 2021-02-09 | Visa International Service Association | Replacing token on a multi-token user device |
US10902418B2 (en) | 2017-05-02 | 2021-01-26 | Visa International Service Association | System and method using interaction token |
US11494765B2 (en) | 2017-05-11 | 2022-11-08 | Visa International Service Association | Secure remote transaction system using mobile devices |
US11138582B2 (en) * | 2017-06-14 | 2021-10-05 | The Toronto-Dominion Bank | Real-time execution of data exchanges between computing systems based on selectively allocated parameters |
US10491389B2 (en) | 2017-07-14 | 2019-11-26 | Visa International Service Association | Token provisioning utilizing a secure authentication system |
WO2019059847A1 (en) * | 2017-09-21 | 2019-03-28 | Mastercard Labs Kenya Holdings Pte. Ltd. | Server and method for managing an account |
US10572862B2 (en) * | 2017-09-26 | 2020-02-25 | Earned LLC | Credit management method and system |
US10530780B2 (en) | 2017-10-11 | 2020-01-07 | Bank Of America Corporation | Entity validation for resource distribution location |
US10817356B2 (en) * | 2017-10-11 | 2020-10-27 | Bank Of America Corporation | Entity resource distribution channel manipulation |
US11276055B1 (en) * | 2017-10-11 | 2022-03-15 | Wells Fargo Bank, N.A. | Cash delivery service |
US10579440B2 (en) | 2017-11-07 | 2020-03-03 | Bank Of America Corporation | Virtual resource control and distribution |
US10320662B1 (en) | 2017-11-17 | 2019-06-11 | Bank Of America Corporation | Centralized resource routing and distribution |
US20190156386A1 (en) * | 2017-11-20 | 2019-05-23 | Donovan Moxey | System and Method for a Location Aware Mobile Application Platform |
WO2019118173A1 (en) * | 2017-12-11 | 2019-06-20 | Global Mobile Finance, Inc. | Methodology and system for a blockchain-based mobile money gateway |
US11676126B1 (en) | 2017-12-28 | 2023-06-13 | Wells Fargo Bank, N.A. | Account open interfaces |
US11106515B1 (en) | 2017-12-28 | 2021-08-31 | Wells Fargo Bank, N.A. | Systems and methods for multi-platform product integration |
US11100492B2 (en) * | 2018-02-19 | 2021-08-24 | Peter Garrett | General purpose re-loadable card aggregation implementation |
US11295297B1 (en) | 2018-02-26 | 2022-04-05 | Wells Fargo Bank, N.A. | Systems and methods for pushing usable objects and third-party provisioning to a mobile wallet |
WO2019171163A1 (en) | 2018-03-07 | 2019-09-12 | Visa International Service Association | Secure remote token release with online authentication |
US11037114B2 (en) | 2018-03-22 | 2021-06-15 | Diebold Nixdorf, Incorporated | System and method for financial transactions |
US11775955B1 (en) | 2018-05-10 | 2023-10-03 | Wells Fargo Bank, N.A. | Systems and methods for making person-to-person payments via mobile client application |
US11074577B1 (en) | 2018-05-10 | 2021-07-27 | Wells Fargo Bank, N.A. | Systems and methods for making person-to-person payments via mobile client application |
US20190347652A1 (en) * | 2018-05-11 | 2019-11-14 | Global Mobile Finance, Inc. | Methodology and system for selecting nodes to execute chaincode in a blockchain environment with a mobile money gateway |
US11282053B1 (en) * | 2018-05-31 | 2022-03-22 | Pnc Global Transfers, Inc. | ATM-based electronic payment conversion systems, methods, and user interfaces |
US11256789B2 (en) | 2018-06-18 | 2022-02-22 | Visa International Service Association | Recurring token transactions |
EP3807830A4 (en) * | 2018-06-18 | 2022-03-16 | JPMorgan Chase Bank, N.A. | Systems and methods for distributed-ledger based intercompany netting |
SG11202101587SA (en) | 2018-08-22 | 2021-03-30 | Visa Int Service Ass | Method and system for token provisioning and processing |
CN113015992B (en) | 2018-11-14 | 2023-02-17 | 维萨国际服务协会 | Cloud token provisioning of multiple tokens |
CN109615374B (en) * | 2018-11-30 | 2023-05-02 | 中国银行股份有限公司 | Bank fund account engine processing method and system |
US11257069B2 (en) * | 2018-12-06 | 2022-02-22 | Wells Fargo Bank, N.A. | Systems and methods for an all-in-one mobile wallet with administrator portal |
US11093912B1 (en) | 2018-12-10 | 2021-08-17 | Wells Fargo Bank, N.A. | Third-party payment interfaces |
US11250462B2 (en) | 2019-04-18 | 2022-02-15 | Benjamin D. Smith | System and method for trading and tracking digitized coupons |
SG11202108626QA (en) | 2019-05-17 | 2021-09-29 | Visa Int Service Ass | Virtual access credential interaction system and method |
US11044246B1 (en) | 2019-06-21 | 2021-06-22 | Wells Fargo Bank, N.A. | Secure communications via third-party systems through frames |
US11823164B1 (en) | 2019-10-22 | 2023-11-21 | Wells Fargo Bank, N.A. | Using a third party as a source of cash |
JP7287243B2 (en) * | 2019-11-08 | 2023-06-06 | トヨタ自動車株式会社 | Wallet system and wallet program |
US11710107B2 (en) | 2019-11-13 | 2023-07-25 | Visa International Service Association | System and method for transaction settlement |
US11854002B2 (en) * | 2019-11-13 | 2023-12-26 | Misam Abidi | Systems and methods for converting physical cash into digital money at the point of sale |
RU2736166C1 (en) * | 2020-04-17 | 2020-11-12 | Общество с ограниченной ответственностью "МКС" | Method of identifying an online user and device thereof in an application |
ZA202004712B (en) * | 2020-07-07 | 2021-07-28 | Channel Tech Fze | Network usage product provisioning via a mobile wallet platform |
US11373239B1 (en) | 2020-09-30 | 2022-06-28 | Wells Fargo Bank, N.A. | Real-time currency exchange system |
US11765221B2 (en) | 2020-12-14 | 2023-09-19 | The Western Union Company | Systems and methods for adaptive security and cooperative multi-system operations with dynamic protocols |
WO2022137026A1 (en) * | 2020-12-23 | 2022-06-30 | STRÖH, Frederyk Andries Jacobus | A method and system for processing financial transactions for a customer |
EP4285304A1 (en) * | 2021-01-29 | 2023-12-06 | Crunchfish Digital Cash AB | Transfer of digital cash between mobile communication device and smart card |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050187873A1 (en) * | 2002-08-08 | 2005-08-25 | Fujitsu Limited | Wireless wallet |
Family Cites Families (460)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5221838A (en) | 1990-12-24 | 1993-06-22 | Motorola, Inc. | Electronic wallet |
US5422624A (en) | 1993-05-25 | 1995-06-06 | Intellectual Property Development Associates Of Connecticut, Inc. | Methods and apparatus for inputting messages, including advertisements, to a vehicle |
JPH098881A (en) | 1995-06-19 | 1997-01-10 | Sony Corp | Portable telephone set |
US5991749A (en) | 1996-09-11 | 1999-11-23 | Morrill, Jr.; Paul H. | Wireless telephony for collecting tolls, conducting financial transactions, and authorizing other activities |
TW355899B (en) | 1997-01-30 | 1999-04-11 | Qualcomm Inc | Method and apparatus for performing financial transactions using a mobile communication unit |
US6370571B1 (en) | 1997-03-05 | 2002-04-09 | At Home Corporation | System and method for delivering high-performance online multimedia services |
US6256614B1 (en) | 1997-04-17 | 2001-07-03 | Jeff H. Wecker | Internet system for producing electronic reward cards |
US5949044A (en) | 1997-06-13 | 1999-09-07 | Walker Asset Management Limited Partnership | Method and apparatus for funds and credit line transfers |
GB9719100D0 (en) | 1997-09-10 | 1997-11-12 | Tekton Communications Limited | A pre-payable communication device |
US6148405A (en) | 1997-11-10 | 2000-11-14 | Phone.Com, Inc. | Method and system for secure lightweight transactions in wireless data networks |
US6021397A (en) | 1997-12-02 | 2000-02-01 | Financial Engines, Inc. | Financial advisory system |
JP4176181B2 (en) | 1998-03-13 | 2008-11-05 | 富士通株式会社 | Electronic wallet management system, terminal device and computer-readable recording medium recording electronic wallet management program |
US6199762B1 (en) | 1998-05-06 | 2001-03-13 | American Express Travel Related Services Co., Inc. | Methods and apparatus for dynamic smartcard synchronization and personalization |
US6250557B1 (en) | 1998-08-25 | 2001-06-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Methods and arrangements for a smart card wallet and uses thereof |
FI981902A (en) | 1998-09-04 | 2000-03-05 | Sonera Oyj | Security module, security system and mobile station |
EP0986275B1 (en) | 1998-09-10 | 2009-09-09 | Swisscom AG | Method for purchasing goods or services with a mobile telephone |
US6175823B1 (en) | 1998-09-15 | 2001-01-16 | Amazon.Com, Inc. | Electronic gift certificate system |
US7248855B2 (en) | 1998-09-15 | 2007-07-24 | Upaid Systems, Ltd. | Convergent communications system and method with a rule set for authorizing, debiting, settling and recharging a mobile commerce account |
US9098958B2 (en) | 1998-09-15 | 2015-08-04 | U-Paid Systems, Ltd. | Convergent communications platform and method for mobile and electronic commerce in a heterogeneous network environment |
MXPA01004945A (en) | 1998-11-17 | 2003-03-10 | Prenet Corp | Electronic payment system utilizing intermediary account. |
US20010011248A1 (en) | 1999-01-29 | 2001-08-02 | Maria Azua Himmel | Method and apparatus for transmitting and tendering electronic cash using a phone wallet |
US6622015B1 (en) | 1999-01-29 | 2003-09-16 | International Business Machines | Method and apparatus for using electronic documents within a smart phone |
CA2369081C (en) | 1999-04-30 | 2012-02-07 | X.Com Corporation | System and method for electronically exchanging value among distributed users |
US6356908B1 (en) | 1999-07-30 | 2002-03-12 | International Business Machines Corporation | Automatic web page thumbnail generation |
US6965868B1 (en) | 1999-08-03 | 2005-11-15 | Michael David Bednarek | System and method for promoting commerce, including sales agent assisted commerce, in a networked economy |
US6873974B1 (en) | 1999-08-17 | 2005-03-29 | Citibank, N.A. | System and method for use of distributed electronic wallets |
US6487403B2 (en) | 1999-08-19 | 2002-11-26 | Verizon Laboratories Inc. | Wireless universal provisioning device |
US20040215491A1 (en) | 1999-08-23 | 2004-10-28 | Clark Paul T. | Providing comprehensive online health-related information and services |
US7461010B2 (en) | 1999-09-13 | 2008-12-02 | Khai Hee Kwan | Computer network method for conducting payment over a network by debiting and crediting telecommunication accounts |
EP1091328A2 (en) | 1999-10-07 | 2001-04-11 | Citicorp Development Center, Inc. | Method and system for providing an incentive to use an automated teller machine (ATM) |
GB9925227D0 (en) | 1999-10-25 | 1999-12-22 | Internet Limited | Data storage retrieval and access system |
EP1107198B1 (en) | 1999-11-30 | 2007-01-10 | Citibank, Na | System and method for performing an electronic transaction using a transaction proxy with an electronic wallet |
PL356777A1 (en) | 2000-01-28 | 2004-07-12 | Fundamo (Proprietary) Limited | Banking system with enhanced identification of financial accounts |
US8052042B2 (en) | 2000-02-05 | 2011-11-08 | Diebold Self-Services Systems Division Of Diebold, Incorporated | Automated banking system controlled responsive to data bearing records |
US7865414B2 (en) | 2000-03-01 | 2011-01-04 | Passgate Corporation | Method, system and computer readable medium for web site account and e-commerce management from a central location |
US7233926B2 (en) | 2000-03-07 | 2007-06-19 | Thomson Licensing | Electronic wallet system with secure inter-purses operations |
KR20020084237A (en) | 2000-03-22 | 2002-11-04 | 콸콤 인코포레이티드 | A method and system for wireless electronic commerce using a portable, wireless communication device having unique identifying information |
EP1269739A2 (en) | 2000-03-31 | 2003-01-02 | Siemens Aktiengesellschaft | Data transmission method and device |
JP2001297198A (en) | 2000-04-14 | 2001-10-26 | Sanwa Bank Ltd | Monetary processing system incorporated in portable telephone |
US20030132291A1 (en) | 2002-01-11 | 2003-07-17 | Metrologic Instruments, Inc. | Point of sale (POS) station having bar code reading system with integrated internet-enabled customer-kiosk terminal |
AU2001257280C1 (en) | 2000-04-24 | 2009-01-15 | Visa International Service Association | Online payer authentication service |
US8903737B2 (en) | 2000-04-25 | 2014-12-02 | Accenture Global Service Limited | Method and system for a wireless universal mobile product interface |
CA2337672A1 (en) | 2000-04-26 | 2001-10-26 | International Business Machines Corporation | Payment for network-based commercial transactions using a mobile phone |
US6714797B1 (en) | 2000-05-17 | 2004-03-30 | Nokia Corporation | System and method for the transfer of digital data to a mobile device |
JP2001344537A (en) | 2000-05-31 | 2001-12-14 | Ntt Docomo Inc | Electronic value system, communication terminal and server |
JP2001357164A (en) | 2000-06-14 | 2001-12-26 | Ntt Data Corp | Method and center for fund management |
WO2001097118A1 (en) | 2000-06-14 | 2001-12-20 | Takako Jogu | Settling method using mobile phone and mobile phone |
US6961858B2 (en) | 2000-06-16 | 2005-11-01 | Entriq, Inc. | Method and system to secure content for distribution via a network |
US6862575B1 (en) | 2000-08-17 | 2005-03-01 | Nokia Corporation | Electronic coupon system |
AU2001285023A1 (en) | 2000-08-17 | 2002-02-25 | Mobileum, Inc. | Method and system for wireless voice channel/data channel integration |
EP1180756A1 (en) | 2000-08-18 | 2002-02-20 | Siemens Aktiengesellschaft | Method and arrangement for the transaction of electronic money from a prepaid account |
EP1180749A1 (en) | 2000-08-18 | 2002-02-20 | Siemens Aktiengesellschaft | Method and system for transmitting an amount of electronic money from a credit memory |
US7110972B1 (en) | 2000-09-19 | 2006-09-19 | Icor Brokerage, Inc. | Method and system of managing credit for the electronic trading of financial instruments |
CA2329895A1 (en) | 2000-09-19 | 2002-03-19 | Soft Tracks Enterprises Ltd. | Merchant wallet server |
JP2002099716A (en) | 2000-09-25 | 2002-04-05 | Masanao Kuninobu | Electronic settlement system |
US7155411B1 (en) | 2000-09-28 | 2006-12-26 | Microsoft Corporation | Integrating payment accounts and an electronic wallet |
US7774231B2 (en) | 2000-09-29 | 2010-08-10 | Nokia Corporation | Electronic payment methods for a mobile device |
US6819219B1 (en) | 2000-10-13 | 2004-11-16 | International Business Machines Corporation | Method for biometric-based authentication in wireless communication for access control |
US7016532B2 (en) | 2000-11-06 | 2006-03-21 | Evryx Technologies | Image capture and identification system and process |
US7680324B2 (en) | 2000-11-06 | 2010-03-16 | Evryx Technologies, Inc. | Use of image-derived information as search criteria for internet and other search engines |
US8130242B2 (en) | 2000-11-06 | 2012-03-06 | Nant Holdings Ip, Llc | Interactivity via mobile image recognition |
US7565008B2 (en) | 2000-11-06 | 2009-07-21 | Evryx Technologies, Inc. | Data capture and identification system and process |
US8218873B2 (en) | 2000-11-06 | 2012-07-10 | Nant Holdings Ip, Llc | Object information derived from object images |
US7899243B2 (en) | 2000-11-06 | 2011-03-01 | Evryx Technologies, Inc. | Image capture and identification system and process |
WO2002039342A1 (en) | 2000-11-08 | 2002-05-16 | Matsushita Electric Industrial Co., Ltd. | Private electronic value bank system |
WO2002041601A2 (en) | 2000-11-16 | 2002-05-23 | Telefonaktiebolaget Lm Ericsson (Publ) | User authentication apparatus, controlling method thereof, and network system |
US6736322B2 (en) | 2000-11-20 | 2004-05-18 | Ecrio Inc. | Method and apparatus for acquiring, maintaining, and using information to be communicated in bar code form with a mobile communications device |
WO2002044892A2 (en) | 2000-11-28 | 2002-06-06 | 4Thpass Inc. | Method and system for maintaining and distributing wireless applications |
US20020069123A1 (en) | 2000-12-01 | 2002-06-06 | Mats Soderlind | Electronic commerce system |
US6950939B2 (en) | 2000-12-08 | 2005-09-27 | Sony Corporation | Personal transaction device with secure storage on a removable memory device |
US20020161708A1 (en) | 2001-02-01 | 2002-10-31 | Gero Offer | Method and apparatus for performing a cashless payment transaction |
KR20020065989A (en) | 2001-02-08 | 2002-08-14 | 스타브리지커뮤니케이션 주식회사 | A payment settlement method using payment code on screen of mobile communication terminal |
DE10119808A1 (en) | 2001-03-01 | 2002-09-12 | Chris Holland | Transaction method for providing goods or services involves vending machine comparing transaction codes transmitted to it and to customer from terminal at chargeable connection |
WO2002071354A2 (en) | 2001-03-02 | 2002-09-12 | Soft Tracks Enterprises Ltd. | System and method for facilitating an m-commerce transaction |
US20020141586A1 (en) | 2001-03-29 | 2002-10-03 | Aladdin Knowledge Systems Ltd. | Authentication employing the bluetooth communication protocol |
WO2002099598A2 (en) | 2001-06-07 | 2002-12-12 | First Usa Bank, N.A. | System and method for rapid updating of credit information |
US7236742B2 (en) | 2001-06-18 | 2007-06-26 | Brigham Young University | System and method for wireless data transfer for a mobile unit |
US7503480B2 (en) | 2001-07-10 | 2009-03-17 | American Express Travel Related Services Company, Inc. | Method and system for tracking user performance |
SG124290A1 (en) | 2001-07-23 | 2006-08-30 | Ntt Docomo Inc | Electronic payment method, system, and devices |
WO2003010951A1 (en) | 2001-07-24 | 2003-02-06 | Citibank, N.A. | Method and system for data management in electronic payments transactions |
WO2003012717A1 (en) | 2001-07-30 | 2003-02-13 | C-Sam, Inc. | System for distribution and use of virtual stored value cards |
US7054430B2 (en) | 2001-08-23 | 2006-05-30 | Paymentone Corporation | Method and apparatus to validate a subscriber line |
US7080049B2 (en) | 2001-09-21 | 2006-07-18 | Paymentone Corporation | Method and system for processing a transaction |
US7099850B1 (en) | 2001-09-21 | 2006-08-29 | Jpmorgan Chase Bank, N.A. | Methods for providing cardless payment |
US20040205618A1 (en) | 2001-11-19 | 2004-10-14 | Jean Sini | Runtime translator for mobile application content |
US6697839B2 (en) | 2001-11-19 | 2004-02-24 | Oracle International Corporation | End-to-end mobile commerce modules |
US7461028B2 (en) | 2001-11-27 | 2008-12-02 | Pitney Bowes Inc. | Method and system for authorizing use of a transaction card |
US7937305B1 (en) | 2001-12-28 | 2011-05-03 | The Pnc Financial Services Group, Inc. | Methods and systems for analyzing the status of an entity and its financial transactions |
US7729963B1 (en) | 2001-12-28 | 2010-06-01 | The Pnc Financial Services Group, Inc. | Methods and systems for processing and communicating financial transaction data |
KR20030068603A (en) | 2002-02-15 | 2003-08-25 | 나루시스템 주식회사 | Paying system using cellular phone and the method |
US20030195842A1 (en) | 2002-04-15 | 2003-10-16 | Kenneth Reece | Method and device for making secure transactions |
US7707120B2 (en) | 2002-04-17 | 2010-04-27 | Visa International Service Association | Mobile account authentication service |
US20040019561A1 (en) | 2002-05-07 | 2004-01-29 | Gabriela Isturiz | Electronic billing system utilizing a universal billing format data transmission |
US7363261B2 (en) | 2002-05-08 | 2008-04-22 | Regions Asset Company | Method, computer program product and system for verifying financial data |
US7149545B2 (en) | 2002-05-30 | 2006-12-12 | Nokia Corporation | Method and apparatus for facilitating over-the-air activation of pre-programmed memory devices |
US7039408B2 (en) | 2002-06-03 | 2006-05-02 | Interdigital Technology Corporation | Method and apparatus for interconnection of personal area networks (PANs) |
US7322043B2 (en) | 2002-06-20 | 2008-01-22 | Hewlett-Packard Development Company, L.P. | Allowing an electronic device accessing a service to be authenticated |
JP4058300B2 (en) | 2002-06-21 | 2008-03-05 | 株式会社日立製作所 | Portable information device |
AU2002368099A1 (en) | 2002-07-21 | 2004-02-09 | Partner Communications Company Ltd. | Prepaid charging system and method |
US20050071512A1 (en) | 2002-07-22 | 2005-03-31 | Donte Kim | System for Interfacing software programs |
US7188089B2 (en) | 2002-07-26 | 2007-03-06 | Way Systems, Inc. | System and method for securely storing, generating, transferring and printing electronic prepaid vouchers |
US7349871B2 (en) | 2002-08-08 | 2008-03-25 | Fujitsu Limited | Methods for purchasing of goods and services |
US7606560B2 (en) | 2002-08-08 | 2009-10-20 | Fujitsu Limited | Authentication services using mobile device |
US7784684B2 (en) | 2002-08-08 | 2010-08-31 | Fujitsu Limited | Wireless computer wallet for physical point of sale (POS) transactions |
US7801826B2 (en) | 2002-08-08 | 2010-09-21 | Fujitsu Limited | Framework and system for purchasing of goods and services |
US7353382B2 (en) | 2002-08-08 | 2008-04-01 | Fujitsu Limited | Security framework and protocol for universal pervasive transactions |
US7221939B2 (en) | 2002-08-16 | 2007-05-22 | Nokia Corporation | System, method, and apparatus for automatically selecting mobile device profiles |
JP4553565B2 (en) | 2002-08-26 | 2010-09-29 | パナソニック株式会社 | Electronic value authentication method, authentication system and device |
AU2002951198A0 (en) | 2002-09-03 | 2002-09-19 | Tynevale Pty Ltd | System and method for a wireless purchase request and payment for goods or services |
US7494055B2 (en) | 2002-09-17 | 2009-02-24 | Vivotech, Inc. | Collaborative negotiation techniques for mobile personal trusted device financial transactions |
US7937302B1 (en) | 2002-11-20 | 2011-05-03 | The Pnc Financial Services Group, Inc. | Methods and systems for monitoring, analyzing and reporting information in association with collateralized financial instruments |
WO2004053640A2 (en) | 2002-12-06 | 2004-06-24 | Way Systems, Inc. | System and method for mobile payment and fulfilment digital goods |
US7571140B2 (en) | 2002-12-16 | 2009-08-04 | First Data Corporation | Payment management |
GB0229765D0 (en) | 2002-12-20 | 2003-01-29 | Radicall Projects Ltd | Payment system |
US7370017B1 (en) | 2002-12-20 | 2008-05-06 | Microsoft Corporation | Redistribution of rights-managed content and technique for encouraging same |
EP1437693A1 (en) | 2003-01-08 | 2004-07-14 | Itsmobile Limited | A mobile telecommunications billing routing system and method |
EP1588335A1 (en) | 2003-01-22 | 2005-10-26 | Valista Limited | Cash based purchasing using mobile communication |
GB2398707B (en) | 2003-02-21 | 2005-03-30 | Schlumberger Holdings | Authentication method for enabling a user of a mobile station to access to private data or services |
US20040181531A1 (en) | 2003-03-12 | 2004-09-16 | Clark Becker | Speed pass system |
US20050080697A1 (en) | 2003-10-14 | 2005-04-14 | Foss Sheldon H. | System, method and apparatus for providing financial services |
US7389123B2 (en) | 2003-04-29 | 2008-06-17 | Sony Ericsson Mobile Communications Ab | Mobile apparatus with remote lock and control function |
US7100821B2 (en) | 2003-05-15 | 2006-09-05 | Mehran Randall Rasti | Charge card and debit transactions using a variable charge number |
US7110792B2 (en) | 2003-05-19 | 2006-09-19 | Einar Rosenberg | Apparatus and method for increased security of wireless transactions |
US20040248554A1 (en) | 2003-06-09 | 2004-12-09 | Khan Mohammad Ather | Method of paying from an account by a customer having a mobile user terminal, and a customer authenticating network |
US7089594B2 (en) | 2003-07-21 | 2006-08-08 | July Systems, Inc. | Application rights management in a mobile environment |
GB0319918D0 (en) | 2003-08-23 | 2003-09-24 | Ibm | Method system and device for mobile subscription content access |
US20050070265A1 (en) | 2003-09-29 | 2005-03-31 | Nokia Corporation | Method, terminal device and system for remote initiation of network applications within mobile communication environment |
US20050199709A1 (en) | 2003-10-10 | 2005-09-15 | James Linlor | Secure money transfer between hand-held devices |
EP1530177B1 (en) | 2003-11-07 | 2006-09-13 | Alcatel | Method for supporting cashless payment |
US7146159B1 (en) | 2003-12-23 | 2006-12-05 | Sprint Communications Company L.P. | Over-the-air card provisioning system and method |
HUE037253T2 (en) | 2004-01-27 | 2018-08-28 | Altivera L L C | Diagnostic radio frequency identification sensors and applications thereof |
WO2005086593A2 (en) | 2004-02-05 | 2005-09-22 | A Little World Private Limited | Inter-operable, multi-operator, multi-bank, multi-merchant mobile payment method and a system therefor |
EP1714424A4 (en) | 2004-02-05 | 2010-12-15 | Veritas Mobile Solutions Pte L | System and method for authenticating the identity of a user |
CA2495949A1 (en) | 2004-02-05 | 2005-08-05 | Simon Law | Secure wireless authorization system |
US7877605B2 (en) | 2004-02-06 | 2011-01-25 | Fujitsu Limited | Opinion registering application for a universal pervasive transaction framework |
US20050222961A1 (en) | 2004-04-05 | 2005-10-06 | Philippe Staib | System and method of facilitating contactless payment transactions across different payment systems using a common mobile device acting as a stored value device |
US7275685B2 (en) | 2004-04-12 | 2007-10-02 | Rearden Capital Corporation | Method for electronic payment |
US8333319B2 (en) | 2004-04-20 | 2012-12-18 | Quantum Corporation Of New York, Inc. | Remittance method and system for services |
US7240836B2 (en) | 2004-04-23 | 2007-07-10 | Virtual Fonlink, Inc. | Enhanced system and method for wireless transactions |
US7255264B2 (en) | 2004-04-24 | 2007-08-14 | De Leon Hilary Laing | Cellular phone-based automatic payment system |
US8762238B2 (en) | 2004-06-09 | 2014-06-24 | Syncada Llc | Recurring transaction processing system and approach |
US8016185B2 (en) | 2004-07-06 | 2011-09-13 | Visa International Service Association | Money transfer service with authentication |
CA2577333C (en) | 2004-08-18 | 2016-05-17 | Mastercard International Incorporated | Method and system for authorizing a transaction using a dynamic authorization code |
US20100044430A1 (en) | 2005-01-03 | 2010-02-25 | Yuh-Shen Song | Automated Remittance Network |
JP4917036B2 (en) | 2004-09-23 | 2012-04-18 | ジエマルト・エス・アー | System and method for communicating with a general purpose integrated circuit card in a mobile device using an internet protocol |
US20060136901A1 (en) | 2004-12-22 | 2006-06-22 | Sony Ericsson Mobile Communications Ab | Mobile financial transaction management system and method |
US7490775B2 (en) | 2004-12-30 | 2009-02-17 | Aol Llc, A Deleware Limited Liability Company | Intelligent identification of multimedia content for synchronization |
US8700729B2 (en) | 2005-01-21 | 2014-04-15 | Robin Dua | Method and apparatus for managing credentials through a wireless network |
US20060200427A1 (en) | 2005-03-01 | 2006-09-07 | Morrison Robert A | Systems and methods for securing transactions with biometric information |
US7628322B2 (en) | 2005-03-07 | 2009-12-08 | Nokia Corporation | Methods, system and mobile device capable of enabling credit card personalization using a wireless network |
JP2006261990A (en) | 2005-03-16 | 2006-09-28 | Fujitsu Ltd | Mobile terminal and remote lock program |
KR100659675B1 (en) | 2005-03-21 | 2006-12-21 | 김영수 | System and its method for transferring sender's money after sender's approving to receiver's transfer request |
US7729987B1 (en) | 2005-05-02 | 2010-06-01 | The Pnc Financial Services Group, Inc. | Enhanced demand deposit accounts |
US20060259055A1 (en) | 2005-05-13 | 2006-11-16 | Linvatec Corporation | Attachments for arthroscopic shaver handpieces |
US8430300B2 (en) | 2005-05-26 | 2013-04-30 | Codebroker, Llc | Using validity events to control the use of coupons containing barcodes in mobile devices that display the barcodes for reading by barcode readers |
US7347361B2 (en) | 2005-06-13 | 2008-03-25 | Robert Lovett | System, method and program product for account transaction validation |
US20060287004A1 (en) | 2005-06-17 | 2006-12-21 | Fuqua Walter B | SIM card cash transactions |
JP2007041954A (en) | 2005-08-04 | 2007-02-15 | Felica Networks Inc | Value information movement system and value information moving method |
EP1960953A4 (en) | 2005-08-22 | 2012-12-05 | Xchange Inc G | A method of converting virtual cash to cash and deducting from a mobile phone cash account |
EP2002388A4 (en) | 2005-08-22 | 2012-12-05 | Xchange Inc G | A method of cash-less, cardless purchase transaction using mobile phones |
EP2002387A4 (en) | 2005-08-22 | 2011-08-03 | Xchange Inc G | Person-to-person virtual cash transfer transaction using mobile phones |
WO2007024151A1 (en) | 2005-08-22 | 2007-03-01 | G-Xchange, Inc. | A method of converting cash into virtual cash and loading it to mobile phone cash account |
JP4890552B2 (en) | 2005-08-29 | 2012-03-07 | エブリックス・テクノロジーズ・インコーポレイテッド | Interactivity via mobile image recognition |
US7548915B2 (en) | 2005-09-14 | 2009-06-16 | Jorey Ramer | Contextual mobile content placement on a mobile communication facility |
US8090945B2 (en) | 2005-09-16 | 2012-01-03 | Tara Chand Singhal | Systems and methods for multi-factor remote user authentication |
US10032160B2 (en) | 2005-10-06 | 2018-07-24 | Mastercard Mobile Transactions Solutions, Inc. | Isolating distinct service provider widgets within a wallet container |
WO2007044500A2 (en) | 2005-10-06 | 2007-04-19 | C-Sam, Inc. | Transactional services |
US7677973B2 (en) | 2005-10-14 | 2010-03-16 | Leviathan Entertainment, Llc | Securing virtual contracts with credit |
US20070088852A1 (en) | 2005-10-17 | 2007-04-19 | Zohar Levkovitz | Device, system and method of presentation of advertisements on a wireless device |
US7819307B2 (en) * | 2005-10-27 | 2010-10-26 | Hewlett-Packard Development Company, L.P. | Method and system for managing monetary value on a mobile device |
US20070106564A1 (en) | 2005-11-04 | 2007-05-10 | Utiba Pte Ltd. | Mobile phone as a point of sale (POS) device |
US20100030651A1 (en) | 2005-11-04 | 2010-02-04 | Richard Victor Matotek | Mobile phone as a point of sale (POS) device |
TWI283122B (en) | 2005-11-29 | 2007-06-21 | Benq Corp | Method for securing a near field communication device of a mobile phone |
US20090248537A1 (en) | 2005-12-01 | 2009-10-01 | Shahriar Sarkeshik | Commercial transaction facilitation system |
US20070125838A1 (en) | 2005-12-06 | 2007-06-07 | Law Eric C W | Electronic wallet management |
US20070125840A1 (en) | 2005-12-06 | 2007-06-07 | Boncle, Inc. | Extended electronic wallet management |
US7689205B2 (en) | 2005-12-23 | 2010-03-30 | Morgan Stanley | Systems and methods for configuration of mobile computing devices |
US8290433B2 (en) | 2007-11-14 | 2012-10-16 | Blaze Mobile, Inc. | Method and system for securing transactions made through a mobile communication device |
US8275312B2 (en) | 2005-12-31 | 2012-09-25 | Blaze Mobile, Inc. | Induction triggered transactions using an external NFC device |
US8190087B2 (en) | 2005-12-31 | 2012-05-29 | Blaze Mobile, Inc. | Scheduling and paying for a banking transaction using an NFC enabled mobile communication device |
US8949146B2 (en) | 2005-12-31 | 2015-02-03 | Michelle Fisher | Method for purchasing tickets using a mobile communication device |
US8352323B2 (en) | 2007-11-30 | 2013-01-08 | Blaze Mobile, Inc. | Conducting an online payment transaction using an NFC enabled mobile communication device |
US20090132362A1 (en) | 2007-11-21 | 2009-05-21 | Mobile Candy Dish, Inc. | Method and system for delivering information to a mobile communication device based on consumer transactions |
US8693995B2 (en) | 2007-12-13 | 2014-04-08 | Michelle Fisher | Customized mobile applications for special interest groups |
US8019365B2 (en) | 2005-12-31 | 2011-09-13 | Michelle Fisher | Conducting a payment using a secure element and SMS |
US20070162471A1 (en) | 2006-01-09 | 2007-07-12 | Mats Samuelsson | Method and an apparatus to provide information to mobile applications |
US7657489B2 (en) | 2006-01-18 | 2010-02-02 | Mocapay, Inc. | Systems and method for secure wireless payment transactions |
CA2640620A1 (en) | 2006-01-30 | 2007-08-02 | Cpni Inc. | A system and method for authorizing a funds transfer or payment using a phone number |
WO2007092789A2 (en) | 2006-02-02 | 2007-08-16 | Mastercard International Incorporated | Implementing direct issuer - merchant relationships over a general purpose bankcard network |
US20070203850A1 (en) | 2006-02-15 | 2007-08-30 | Sapphire Mobile Systems, Inc. | Multifactor authentication system |
KR100822985B1 (en) | 2006-03-10 | 2008-04-17 | 주식회사 신한은행 | System for Processing Payment by Using Nickname |
BRPI0709074A2 (en) | 2006-03-21 | 2011-06-28 | Phone1 Inc | financial transactions using a communication device |
US7873573B2 (en) | 2006-03-30 | 2011-01-18 | Obopay, Inc. | Virtual pooled account for mobile banking |
CA2647602A1 (en) | 2006-03-30 | 2008-03-06 | Obopay Inc. | Mobile person-to-person payment system |
US20070244811A1 (en) | 2006-03-30 | 2007-10-18 | Obopay Inc. | Mobile Client Application for Mobile Payments |
US20070265984A1 (en) * | 2006-04-24 | 2007-11-15 | Prakash Santhana | Financial transaction using mobile devices |
US20070255353A1 (en) | 2006-04-27 | 2007-11-01 | Reinke James D | Fault tolerant co-axially wired sensors and methods for implementing same in an implantable medical device |
US7775437B2 (en) | 2006-06-01 | 2010-08-17 | Evryx Technologies, Inc. | Methods and devices for detecting linkable objects |
MY149658A (en) | 2006-06-12 | 2013-09-30 | Mobile Money Internat Sdn Bhd | Transaction server |
US7512567B2 (en) | 2006-06-29 | 2009-03-31 | Yt Acquisition Corporation | Method and system for providing biometric authentication at a point-of-sale via a mobile device |
US20080006685A1 (en) | 2006-07-06 | 2008-01-10 | Firethorn Holdings, Llc | Methods and Systems For Real Time Account Balances in a Mobile Environment |
KR20130055700A (en) | 2006-07-06 | 2013-05-28 | 퀄컴 인코포레이티드 | Methods and systems for financial transactions in a mobile environment |
US8160959B2 (en) | 2006-07-06 | 2012-04-17 | Firethorn Mobile, Inc. | Methods and systems for payment transactions in a mobile environment |
US8145568B2 (en) | 2006-07-06 | 2012-03-27 | Firethorn Mobile, Inc. | Methods and systems for indicating a payment in a mobile environment |
US8489067B2 (en) | 2006-07-06 | 2013-07-16 | Qualcomm Incorporated | Methods and systems for distribution of a mobile wallet for a mobile device |
US20080010191A1 (en) | 2006-07-06 | 2008-01-10 | Firethorn Holdings, Llc | Methods and Systems For Providing a Payment in a Mobile Environment |
US8121945B2 (en) | 2006-07-06 | 2012-02-21 | Firethorn Mobile, Inc. | Methods and systems for payment method selection by a payee in a mobile environment |
US8467766B2 (en) | 2006-07-06 | 2013-06-18 | Qualcomm Incorporated | Methods and systems for managing payment sources in a mobile environment |
US8510220B2 (en) | 2006-07-06 | 2013-08-13 | Qualcomm Incorporated | Methods and systems for viewing aggregated payment obligations in a mobile environment |
US9911114B2 (en) | 2006-07-06 | 2018-03-06 | Qualcomm Incorporated | Methods and systems for making a payment via a stored value card in a mobile environment |
RU2467501C2 (en) * | 2006-07-06 | 2012-11-20 | Файрторн Мобайл Инк. | Methods and systems for financial transactions in mobile communication environment |
US20080010204A1 (en) | 2006-07-06 | 2008-01-10 | Firethorn Holdings, Llc | Methods and Systems For Making a Payment Via a Paper Check in a Mobile Environment |
US20080011825A1 (en) | 2006-07-12 | 2008-01-17 | Giordano Claeton J | Transactions using handheld electronic devices based on unobtrusive provisioning of the devices |
US7711392B2 (en) | 2006-07-14 | 2010-05-04 | Research In Motion Limited | System and method to provision a mobile device |
US20080017704A1 (en) | 2006-07-24 | 2008-01-24 | First Data Corporation | Contactless Electronic Wallet Payment Device |
US7823772B2 (en) | 2006-08-09 | 2010-11-02 | Verizon Patent And Licensing Inc. | Transaction information mining |
US7822439B2 (en) | 2006-08-14 | 2010-10-26 | Sandisk Il Ltd. | System for sharing credentials |
US7886962B2 (en) | 2006-08-17 | 2011-02-15 | Verizon Patent And Licensing Inc. | Multi-function transaction device |
US7748618B2 (en) | 2006-08-21 | 2010-07-06 | Verizon Patent And Licensing Inc. | Secure near field transaction |
US8116734B2 (en) | 2006-08-22 | 2012-02-14 | Verizon Patent And Licensing Inc. | Party identification in a wireless network |
US7708194B2 (en) | 2006-08-23 | 2010-05-04 | Verizon Patent And Licensing Inc. | Virtual wallet |
US7469151B2 (en) | 2006-09-01 | 2008-12-23 | Vivotech, Inc. | Methods, systems and computer program products for over the air (OTA) provisioning of soft cards on devices with wireless communications capabilities |
US9076158B2 (en) | 2006-09-13 | 2015-07-07 | Google Inc. | Integrated system and method for managing electronic coupons |
US7527208B2 (en) | 2006-12-04 | 2009-05-05 | Visa U.S.A. Inc. | Bank issued contactless payment card used in transit fare collection |
WO2008048948A2 (en) | 2006-10-17 | 2008-04-24 | Solidus Networks, Inc. | A method of distributing information via mobile devices and enabling its use at a point of transaction |
AU2007312879B2 (en) | 2006-10-19 | 2011-10-20 | Jmango Ipr Holding Ltd | An interactive system and process |
US20080126929A1 (en) | 2006-11-29 | 2008-05-29 | Microsoft Corporation | Remote ui for smart devices |
US7979026B2 (en) | 2006-12-19 | 2011-07-12 | Broadcom Corporation | System and method for using a single antenna for active and passive radio functions |
US20080143487A1 (en) | 2006-12-19 | 2008-06-19 | Broadcom Corporation | System and method for enabling interrupts for rfid tags |
US8239325B2 (en) | 2007-01-18 | 2012-08-07 | Paymentone Corporation | Method and system to verify the identity of a user |
WO2008094894A1 (en) | 2007-01-29 | 2008-08-07 | Cook Incorporated | Artificial venous valve with discrete shaping members |
US8793184B2 (en) | 2007-02-12 | 2014-07-29 | Visa U.S.A. Inc. | Mobile payment services |
US9483757B2 (en) | 2007-02-16 | 2016-11-01 | Sony Corporation | Monetary information processing server and monetary information processing method |
JP2008205980A (en) * | 2007-02-22 | 2008-09-04 | Hitachi Ltd | Information transmission system, information transmission method and information display device |
US8566239B2 (en) | 2007-02-22 | 2013-10-22 | First Data Corporation | Mobile commerce systems and methods |
US20080208742A1 (en) | 2007-02-22 | 2008-08-28 | First Data Corporation | Provisioning of a device for mobile commerce |
US20080208743A1 (en) | 2007-02-22 | 2008-08-28 | First Data Corporation | Transfer of value between mobile devices in a mobile commerce system |
US20080208762A1 (en) | 2007-02-22 | 2008-08-28 | First Data Corporation | Payments using a mobile commerce device |
US20080208741A1 (en) | 2007-02-22 | 2008-08-28 | First Data Corporation | Account information lookup systems and methods in mobile commerce |
US8087060B2 (en) | 2007-03-16 | 2011-12-27 | James Mark Norman | Chaining information card selectors |
US8396793B2 (en) | 2007-04-06 | 2013-03-12 | Mastercard International Incorporated | Payment card based remittance methods and system |
US20080249928A1 (en) | 2007-04-06 | 2008-10-09 | Hill Dennis J | Payment card based remittance system with designation of recipient by mobile telephone number |
US20080249927A1 (en) | 2007-04-06 | 2008-10-09 | Rethorn Michael L | Remittance recipient/sender name on sender/recipient monthly statement |
US8548908B2 (en) | 2007-04-11 | 2013-10-01 | First Data Corporation | Mobile commerce infrastructure systems and methods |
US7562818B1 (en) | 2007-05-22 | 2009-07-21 | Sprint Communications Company L.P. | Mobile device having a transit card application |
WO2009014548A1 (en) | 2007-07-20 | 2009-01-29 | David Erickson | Electronic registration and transaction system |
US20090037326A1 (en) | 2007-07-30 | 2009-02-05 | Sriram Chitti | Virtual Card Selector for a Portable Electronic Device |
WO2009016540A2 (en) | 2007-08-01 | 2009-02-05 | Nxp B.V. | Mobile communication device and method for disabling applications |
US20090055322A1 (en) | 2007-08-23 | 2009-02-26 | Microsoft Corporation | Removable module in personal handheld devices for personal information exchange |
US20090063312A1 (en) | 2007-08-28 | 2009-03-05 | Hurst Douglas J | Method and System for Processing Secure Wireless Payment Transactions and for Providing a Virtual Terminal for Merchant Processing of Such Transactions |
US8041338B2 (en) | 2007-09-10 | 2011-10-18 | Microsoft Corporation | Mobile wallet and digital payment |
US20090081989A1 (en) | 2007-09-25 | 2009-03-26 | Christopher Andrew Wuhrer | System and method for financial transaction interoperability across multiple mobile networks |
EP2043016A1 (en) | 2007-09-27 | 2009-04-01 | Nxp B.V. | Method, system, trusted service manager, service provider and memory element for managing access rights for trusted applications |
US7707113B1 (en) | 2007-09-28 | 2010-04-27 | Sprint Communications Company L.P. | Method and system for setting levels of electronic wallet security |
US7575177B2 (en) | 2007-10-03 | 2009-08-18 | Mastercard International, Inc. | Dual use payment device |
US20090098854A1 (en) | 2007-10-11 | 2009-04-16 | Harexinfotech Inc. | Method of providing billing and payment service using settlement service function of mobile electronic wallet and system therefor |
US8565723B2 (en) | 2007-10-17 | 2013-10-22 | First Data Corporation | Onetime passwords for mobile wallets |
US20090106148A1 (en) | 2007-10-17 | 2009-04-23 | Christian Prada | Pre-paid financial system |
US8095113B2 (en) | 2007-10-17 | 2012-01-10 | First Data Corporation | Onetime passwords for smart chip cards |
US20100250436A1 (en) | 2007-10-17 | 2010-09-30 | The Western Union Company | Mobile customer service centers with a mobile pickup model |
US20090265272A1 (en) | 2007-10-17 | 2009-10-22 | The Western Union Company | Money transfers utilizing a unique receiver identifier |
HU230695B1 (en) | 2007-10-20 | 2017-09-28 | Andrá Vilmos | Method of preparing storing and method of storing single user access information into safe storage unit of a communication device |
US7774076B2 (en) | 2007-10-29 | 2010-08-10 | First Data Corporation | System and method for validation of transactions |
US20090108015A1 (en) | 2007-10-30 | 2009-04-30 | David Kreamer | Combination ATM/Vending Machine Kiosk |
US9098844B2 (en) | 2007-11-20 | 2015-08-04 | Wells Fargo Bank, N.A. | Mobile electronic wallet |
US7689508B2 (en) | 2007-11-20 | 2010-03-30 | Wells Fargo Bank N.A. | Mobile device credit account |
CN101939963B (en) | 2007-12-07 | 2016-11-16 | 法国电信公司 | For controlling the method for application, the security module being associated, mobile terminal and the server installed in the security module being associated with mobile terminal |
US20120029990A1 (en) | 2007-12-13 | 2012-02-02 | Blaze Mobile | Social Media Marketing Based on Transactions Using a Mobile Device and Associated Secure Element |
JP5150245B2 (en) | 2007-12-27 | 2013-02-20 | 株式会社東芝 | Semiconductor memory device |
US7958052B2 (en) | 2007-12-31 | 2011-06-07 | Mastercard International Incorporated | Methods and systems for cardholder initiated transactions |
US9947002B2 (en) | 2008-02-15 | 2018-04-17 | First Data Corporation | Secure authorization of contactless transaction |
DE102008011192A1 (en) | 2008-02-26 | 2009-08-27 | Wincor Nixdorf International Gmbh | Method and service calculator and system for the transaction of a sum of money |
US20090234751A1 (en) | 2008-03-14 | 2009-09-17 | Eric Chan | Electronic wallet for a wireless mobile device |
ES2436117T3 (en) | 2008-03-27 | 2013-12-27 | Motorola Mobility Llc | Method and apparatus for automatic selection of applications on an electronic device using multiple discovery administrators |
ATE554593T1 (en) | 2008-03-27 | 2012-05-15 | Motorola Mobility Inc | METHOD AND APPARATUS FOR AUTOMATIC NEAR FIELD COMMUNICATIONS APPLICATION SELECTION IN AN ELECTRONIC DEVICE |
US7967196B1 (en) | 2008-03-28 | 2011-06-28 | Sprint Communications Company L.P. | Electronic wallet ready to pay timer |
US20090281904A1 (en) | 2008-04-02 | 2009-11-12 | Pharris Dennis J | Mobile telephone transaction systems and methods |
US20120047070A1 (en) | 2008-04-02 | 2012-02-23 | Jennifer Pharris | ATM/KIOSK Cash Acceptance |
US20090288012A1 (en) | 2008-05-18 | 2009-11-19 | Zetawire Inc. | Secured Electronic Transaction System |
US20090299844A1 (en) | 2008-05-29 | 2009-12-03 | Kroger Personal Finance | Prepaid reloadable electronic transaction cards with loyalty program |
US8031207B2 (en) | 2008-06-04 | 2011-10-04 | Mastercard International, Inc. | Card image description format to economize on data storage |
US20090307140A1 (en) | 2008-06-06 | 2009-12-10 | Upendra Mardikar | Mobile device over-the-air (ota) registration and point-of-sale (pos) payment |
RU2488888C2 (en) | 2008-06-24 | 2013-07-27 | Эн-Экс-П Б.В. | Method of access to applications in secure mobile environment |
US9824366B2 (en) | 2008-07-08 | 2017-11-21 | First Data Corporation | Customer pre-selected electronic coupons |
US8662401B2 (en) | 2008-07-25 | 2014-03-04 | First Data Corporation | Mobile payment adoption by adding a dedicated payment button to mobile device form factors |
US20100048226A1 (en) | 2008-08-20 | 2010-02-25 | First Data Corporation | Managing mobile marketing offers |
US8116921B2 (en) | 2008-08-20 | 2012-02-14 | Autonomous Solutions, Inc. | Follower vehicle control system and method for forward and reverse convoy movement |
US20100049599A1 (en) | 2008-08-20 | 2010-02-25 | First Data Corporation | Filtering mobile marketing offers |
US20100057614A1 (en) | 2008-08-26 | 2010-03-04 | Qualcomm Incorporated | System and method for effecting real-time financial transactions between delayed-settlement financial accounts |
US9213973B2 (en) | 2008-08-29 | 2015-12-15 | First Data Corporation | Car wallet application |
US20100114739A1 (en) | 2008-09-03 | 2010-05-06 | David Johnston | Systems and methods for a comprehensive integrated and universal content selling and buying platform |
US8523053B2 (en) | 2008-09-03 | 2013-09-03 | First Data Corporation | Enabling consumer choice on contactless transactions when using a dual-branded payment instrument |
US10706402B2 (en) | 2008-09-22 | 2020-07-07 | Visa International Service Association | Over the air update of payment transaction data stored in secure memory |
WO2010037204A1 (en) | 2008-10-03 | 2010-04-08 | Consumer Mt Inc. | System and method for providing a universal electronic wallet |
MY163850A (en) | 2008-10-06 | 2017-10-31 | Vivotech Inc | Systems, methods, and computer readable media for payment and non-payment virtual card transfer between mobile devices |
KR101525872B1 (en) | 2008-11-06 | 2015-06-04 | 삼성전자주식회사 | Method for operating semiconductor memory system |
US8725574B2 (en) | 2008-11-17 | 2014-05-13 | Mastercard International Incorporated | Methods and systems for payment account issuance over a mobile network |
US20100125510A1 (en) | 2008-11-17 | 2010-05-20 | Smith Steven M | System and method of conducting transactions using a mobile wallet system |
US20100125495A1 (en) | 2008-11-17 | 2010-05-20 | Smith Steven M | System and method of providing a mobile wallet at a mobile telephone |
US8615466B2 (en) | 2008-11-24 | 2013-12-24 | Mfoundry | Method and system for downloading information into a secure element of an electronic device |
US8677463B2 (en) | 2008-12-05 | 2014-03-18 | At&T Intellectual Property I, Lp | System and method for managing multiple sub accounts within a subcriber main account in a data distribution system |
EP2197167B1 (en) | 2008-12-12 | 2017-07-12 | Vodafone Holding GmbH | Device and method for short range communication |
US9536238B2 (en) | 2008-12-31 | 2017-01-03 | Peter Garrett | Hand-held electronics device for aggregation of and management of personal electronic data |
ES2811030T3 (en) | 2009-02-14 | 2021-03-10 | Boloro Global Ltd | Secure billing and payment method using account or mobile phone number |
SG164294A1 (en) | 2009-02-17 | 2010-09-29 | Taggo Pte Ltd | An automated membership system |
US20100223110A1 (en) | 2009-03-02 | 2010-09-02 | Daniel Slavin | Method and System for Delivering Offers to Users of Electronic Privilege Cards |
US8428513B2 (en) | 2009-03-27 | 2013-04-23 | Motorola Mobility Llc | Methods, systems and apparatus for selecting an application in power-off mode |
US8799060B2 (en) | 2009-03-30 | 2014-08-05 | Transactis, Inc | Method for electronic coupon creation, deployment, transference, validation management, clearance, redemption and reporting system and and method for interactive participation of individuals and groups with coupons |
US8452608B2 (en) | 2009-05-11 | 2013-05-28 | James E. Smeeding | Wireless cellular systems and methods for prescription drug discounts and therapy delivery |
US8725122B2 (en) | 2009-05-13 | 2014-05-13 | First Data Corporation | Systems and methods for providing trusted service management services |
US8105208B2 (en) | 2009-05-18 | 2012-01-31 | Adidas Ag | Portable fitness monitoring systems with displays and applications thereof |
US8487771B2 (en) | 2009-05-21 | 2013-07-16 | Silverplus, Inc. | Personal health management device |
US9734496B2 (en) | 2009-05-29 | 2017-08-15 | Paypal, Inc. | Trusted remote attestation agent (TRAA) |
JP5204726B2 (en) | 2009-06-19 | 2013-06-05 | 日立建機株式会社 | Motor vehicle control device for work vehicle |
US8484563B2 (en) | 2009-06-26 | 2013-07-09 | Beezag Inc. | View confirmation for on-demand multimedia content |
CN201532668U (en) | 2009-08-12 | 2010-07-21 | 钒创科技股份有限公司 | E-wallet device |
US20110047016A1 (en) | 2009-08-20 | 2011-02-24 | Comcast Cable Communications, Llc | Distribution of e-coupons to user devices |
US20110057025A1 (en) | 2009-09-04 | 2011-03-10 | Paycode Systems, Inc. | Generation, management and usage of on-demand payment ids |
DE102009041002A1 (en) | 2009-09-10 | 2011-03-24 | Claussen, Joerg, Dipl.-Ing. | Method for personal, location-independent, cashless payment arrangement, involves determining money transfer from account of debtor to account of creditor from debtor account exclusively by new mobile radio unit |
US10454693B2 (en) | 2009-09-30 | 2019-10-22 | Visa International Service Association | Mobile payment application architecture |
US8447699B2 (en) | 2009-10-13 | 2013-05-21 | Qualcomm Incorporated | Global secure service provider directory |
US20110087529A1 (en) | 2009-10-14 | 2011-04-14 | Matthew Jason Angell | Methods and systems for creation and distribution of promotional materials and gathering of consumer data |
US8374916B2 (en) | 2009-10-27 | 2013-02-12 | At&T Mobility Ii Llc | Secure mobile-based financial transactions |
WO2011060662A1 (en) | 2009-11-20 | 2011-05-26 | 北京飞天诚信科技有限公司 | Method for earmarking two electronic purses |
CN102073958A (en) | 2009-11-25 | 2011-05-25 | 天津中兴软件有限责任公司 | System and method for implementing mobile payment |
US20110131421A1 (en) | 2009-12-02 | 2011-06-02 | Fabrice Jogand-Coulomb | Method for installing an application on a sim card |
AU2010249214C1 (en) * | 2009-12-15 | 2014-08-21 | Zonamovil, Inc. | Methods, apparatus, and systems for supporting purchases of goods and services via prepaid telecommunication accounts |
US8788418B2 (en) | 2010-03-02 | 2014-07-22 | Gonow Technologies, Llc | Portable E-wallet and universal card |
US9129199B2 (en) | 2010-03-02 | 2015-09-08 | Gonow Technologies, Llc | Portable E-wallet and universal card |
US9195926B2 (en) | 2010-03-02 | 2015-11-24 | Gonow Technologies, Llc | Portable e-wallet and universal card |
US9218557B2 (en) | 2010-03-02 | 2015-12-22 | Gonow Technologies, Llc | Portable e-wallet and universal card |
US8671055B2 (en) | 2010-03-02 | 2014-03-11 | Digital Life Technologies, Llc | Portable E-wallet and universal card |
US9129270B2 (en) | 2010-03-02 | 2015-09-08 | Gonow Technologies, Llc | Portable E-wallet and universal card |
SI23227A (en) | 2010-03-10 | 2011-05-31 | Margento R&D D.O.O. | Wireless mobile transaction system and procedure of carrying out transaction with mobile telephone |
US10062108B2 (en) | 2010-03-26 | 2018-08-28 | Eastnets Fz-Llc | Mobile remittance computer system and method |
US20110246284A1 (en) | 2010-04-01 | 2011-10-06 | Gary Chaikin | Systems and Methods for Adding Functionality to Merchant Sales and Facilitating Data Collection. |
US20130024223A1 (en) | 2010-04-05 | 2013-01-24 | Omnego Inc. | System and method for management of electronic wallet databases |
US8458088B2 (en) | 2010-04-08 | 2013-06-04 | The Western Union Company | Money transfer smart phone methods and systems |
US9400978B2 (en) | 2010-04-09 | 2016-07-26 | Paypal, Inc. | Methods and systems for selecting accounts and offers in payment transactions |
US8380177B2 (en) | 2010-04-09 | 2013-02-19 | Paydiant, Inc. | Mobile phone payment processing methods and systems |
US20110258026A1 (en) | 2010-04-14 | 2011-10-20 | Kevin Prince | Advertising viewing and referral incentive system |
CA2701061C (en) | 2010-04-19 | 2014-03-25 | Diversinet Corp. | Method and system for recovering a security credential |
US20110270744A1 (en) * | 2010-04-30 | 2011-11-03 | Ginger Baker | Mobile tangible value banking system |
US20110276417A1 (en) | 2010-05-05 | 2011-11-10 | Andrew Campbell | System for personalized payments via mobile and internet connected devices |
RU2621630C2 (en) | 2010-06-15 | 2017-06-06 | Давид Евгеньевич ЯН | Customer loyalty system in restaurant and retail networks using web-servers, mobile devices and terminals in the points of sale |
US8355670B2 (en) | 2010-06-22 | 2013-01-15 | At&T Mobility Ii Llc | Near field communication adapters |
US20110320294A1 (en) | 2010-06-23 | 2011-12-29 | Bank Of America Corporation | Active budget control |
US9536243B2 (en) | 2010-06-28 | 2017-01-03 | Mastercard International Incorporated | Methods, systems, and computer readable media for facilitating in-store or near-store ordering and payment of goods and services through a single-tap of a near field communication (NFC) device |
US9697651B2 (en) | 2010-06-28 | 2017-07-04 | Mastercard International Incorporated | Systems, methods, apparatuses, and computer program products for facilitating reservation for a parking space with a near field communication-enabled device |
US20110320345A1 (en) | 2010-06-29 | 2011-12-29 | Ebay, Inc. | Smart wallet |
US20120123841A1 (en) | 2010-06-29 | 2012-05-17 | Ebay, Inc. | Smart wallet |
US8660948B2 (en) | 2010-07-02 | 2014-02-25 | Qualcomm Incorporated | System and method for managing transactions with a portable computing device |
US8442914B2 (en) | 2010-07-06 | 2013-05-14 | Mastercard International Incorporated | Virtual wallet account with automatic-loading |
CA2915867C (en) | 2010-08-12 | 2018-03-13 | Shoon Ping Wong | Multi-commerce channel wallet for authenticated transactions |
US20120079521A1 (en) | 2010-09-23 | 2012-03-29 | Garg Sharad K | Incentivizing advertisement viewing and validating associated purchase |
US10929832B2 (en) | 2011-09-06 | 2021-02-23 | Barclays Execution Services Limited | Method and system for electronic wallet access |
US9558481B2 (en) | 2010-09-28 | 2017-01-31 | Barclays Bank Plc | Secure account provisioning |
US20120084203A1 (en) | 2010-09-30 | 2012-04-05 | The Western Union Company | System and method for secure transactions using device-related fingerprints |
US9047630B2 (en) | 2010-10-15 | 2015-06-02 | Cellco Partnership | Using a mobile device to make a transaction |
AU2011316955B2 (en) | 2010-10-20 | 2016-12-01 | Playspan Inc. | Flexible monetization service apparatuses, methods and systems |
US20120265685A1 (en) | 2010-11-17 | 2012-10-18 | Sequent Software Inc. | System and Method for Physical-World Based Dynamic Contactless Data Emulation in a Portable Communication Device |
US20120122447A1 (en) | 2010-11-17 | 2012-05-17 | Michael Craft | System and Method for On-Demand Diagnostics of a Device Utilizing Secure Data to Interact Wirelessly with One or More Third Party Systems |
US20120123935A1 (en) | 2010-11-17 | 2012-05-17 | David Brudnicki | System and Method for Physical-World Based Dynamic Contactless Data Emulation in a Portable Communication Device |
US8689297B2 (en) | 2010-11-19 | 2014-04-01 | Blackberry Limited | System, devices and method for secure authentication |
US8213470B2 (en) | 2010-11-24 | 2012-07-03 | Photop Technologies, Inc. | Intra-cavity frequency doubled microchip laser operating in TEM00 transverse mode |
US9292870B2 (en) | 2010-12-13 | 2016-03-22 | Qualcomm Incorporated | System and method for point of service payment acceptance via wireless communication |
WO2012083093A1 (en) | 2010-12-15 | 2012-06-21 | Visa International Service Association | Social media payment platform apparatuses, methods and systems |
US8646059B1 (en) | 2010-12-17 | 2014-02-04 | Google Inc. | Wallet application for interacting with a secure element application without a trusted server for authentication |
AU2011348061B2 (en) | 2010-12-23 | 2015-12-10 | Paypal, Inc. | Mobile phone atm processing methods and systems |
US20120166270A1 (en) | 2010-12-23 | 2012-06-28 | Apriva, Llc | System and device for facilitating mobile enrollment and participation in a loyalty campaign |
BR112013015893A2 (en) | 2010-12-23 | 2018-06-05 | Ebay Inc | method, system, and non-transient machine readable medium. |
US20120095855A1 (en) | 2010-12-28 | 2012-04-19 | Jacob Matthew Sterling | Systems and methods for buyer-initiated mobile payments without sensitive information exchange between buyer and seller |
US20120171992A1 (en) | 2010-12-30 | 2012-07-05 | Sk C&C | System and method for secure containment of sensitive financial information stored in a mobile communication terminal |
US8666895B2 (en) | 2011-01-31 | 2014-03-04 | Bank Of America Corporation | Single action mobile transaction device |
US8972286B2 (en) | 2011-01-31 | 2015-03-03 | Bank Of America Corporation | Transaction authorization system for a mobile commerce device |
US20120197787A1 (en) | 2011-01-31 | 2012-08-02 | Bank Of America Corporation | Mobile wallet experience for resolving conflicts between different financial institutions and payment vehicles |
US20120197691A1 (en) | 2011-01-31 | 2012-08-02 | Bank Of America Corporation | Mobile wallet payment vehicle preferences |
US8360329B2 (en) | 2011-01-31 | 2013-01-29 | Bank Of America Corporation | Mobile wallet with managed active and passive payment technology |
US8977251B2 (en) | 2011-01-31 | 2015-03-10 | Bank Of America Corporation | Transferring content to a mobile device |
US8195576B1 (en) | 2011-01-31 | 2012-06-05 | Bank Of America Corporation | Mobile transaction device security system |
WO2012106655A2 (en) | 2011-02-05 | 2012-08-09 | Visa International Service Association | Merchant-consumer bridging platform apparatuses, methods and systems |
US20120203632A1 (en) | 2011-02-07 | 2012-08-09 | Marc Blum | Tracking and summarizing purchase information |
US20120203610A1 (en) | 2011-02-08 | 2012-08-09 | Grigg David M | Payment using an emulated electronic coupon in a contactless payment environment |
US20120209688A1 (en) | 2011-02-15 | 2012-08-16 | Michelle Lamothe | Systems and methods for multi-platform transaction card access and management |
CN103765453B (en) | 2011-02-16 | 2018-08-14 | 维萨国际服务协会 | Snap mobile payment device, method and system |
US20130024364A1 (en) | 2011-02-22 | 2013-01-24 | Abhinav Shrivastava | Consumer transaction leash control apparatuses, methods and systems |
US20130024371A1 (en) | 2011-02-22 | 2013-01-24 | Prakash Hariramani | Electronic offer optimization and redemption apparatuses, methods and systems |
AU2012223415B2 (en) | 2011-02-28 | 2017-05-18 | Visa International Service Association | Secure anonymous transaction apparatuses, methods and systems |
CA2828582A1 (en) | 2011-03-02 | 2012-09-07 | Pxt Payments, Inc. | Mobile payment and point system and method |
WO2012122065A1 (en) | 2011-03-04 | 2012-09-13 | Visa International Service Association | Healthcare wallet payment processing apparatuses, methods and systems |
US9098846B2 (en) | 2011-03-04 | 2015-08-04 | Bank Of America Corporation | Contactless automated teller machine |
EP2684168A1 (en) | 2011-03-07 | 2014-01-15 | Giori, Roberto | System and method for providing and transferring fungible electronic money |
US20120232977A1 (en) | 2011-03-08 | 2012-09-13 | Bank Of America Corporation | Real-time video image analysis for providing targeted offers |
US8668498B2 (en) | 2011-03-08 | 2014-03-11 | Bank Of America Corporation | Real-time video image analysis for providing virtual interior design |
US8571888B2 (en) | 2011-03-08 | 2013-10-29 | Bank Of America Corporation | Real-time image analysis for medical savings plans |
US9773285B2 (en) | 2011-03-08 | 2017-09-26 | Bank Of America Corporation | Providing data associated with relationships between individuals and images |
US8922657B2 (en) | 2011-03-08 | 2014-12-30 | Bank Of America Corporation | Real-time video image analysis for providing security |
US8721337B2 (en) | 2011-03-08 | 2014-05-13 | Bank Of America Corporation | Real-time video image analysis for providing virtual landscaping |
US20120232983A1 (en) | 2011-03-11 | 2012-09-13 | McKesson Speciality Arizona Inc. | Method and apparatus for providing dynamically optimized incentives |
US20130057392A1 (en) | 2011-03-14 | 2013-03-07 | Roddy M. Bullock | Method and System for Disabling an Electronic Device |
KR102050909B1 (en) | 2011-03-25 | 2019-12-02 | 비자 인터네셔널 서비스 어소시에이션 | In-person one-tap purchasing apparatuses, methods and systems |
US20120310720A1 (en) | 2011-03-31 | 2012-12-06 | Nokia Corporation | Method and apparatus for processing coupons/purchases based on radio frequency memory tag detection |
CA2831890A1 (en) | 2011-04-01 | 2012-10-04 | Visa International Service Association | Restricted-use account payment administration apparatuses, methods and systems |
US10580049B2 (en) | 2011-04-05 | 2020-03-03 | Ingenico, Inc. | System and method for incorporating one-time tokens, coupons, and reward systems into merchant point of sale checkout systems |
US20120259732A1 (en) | 2011-04-07 | 2012-10-11 | Sanal Sasankan | Method and system for locating a product in a store using a mobile device |
US8725484B2 (en) | 2011-04-08 | 2014-05-13 | Physware, Inc. | Adaptive redundancy-extraction for 3D electromagnetic simulation of electronic systems |
US20120259686A1 (en) | 2011-04-11 | 2012-10-11 | Yurow A Pierre | Management Of Advertisements, Electronic Commerce, And Consumer Services |
US20120259698A1 (en) | 2011-04-11 | 2012-10-11 | Yurow A Pierre | Electronic Currency Management System |
US8635153B2 (en) | 2011-04-13 | 2014-01-21 | Visa International Service Association | Message routing using logically independent recipient identifiers |
US8849706B2 (en) | 2011-04-20 | 2014-09-30 | Christine King | Method for updating prices while shopping |
US9053478B2 (en) | 2011-05-03 | 2015-06-09 | Verifone, Inc. | Mobile commerce system |
US10949844B2 (en) | 2011-05-09 | 2021-03-16 | Intuit Inc. | Processing electronic payment involving mobile communication device |
US20120290472A1 (en) | 2011-05-10 | 2012-11-15 | Mullen Jeffrey D | Systems and devices for mobile payment acceptance |
US8412631B2 (en) | 2011-05-13 | 2013-04-02 | American Express Travel Related Services Company, Inc. | Cloud enabled payment processing system and method |
US8762742B2 (en) | 2011-05-16 | 2014-06-24 | Broadcom Corporation | Security architecture for using host memory in the design of a secure element |
US20120296720A1 (en) | 2011-05-17 | 2012-11-22 | Maritz Holdings Inc. | Mobile rewards redemption system and method |
US20120296722A1 (en) | 2011-05-18 | 2012-11-22 | Infosys Limited | Methods and system to perform wireless financial transactions |
US20120296708A1 (en) | 2011-05-18 | 2012-11-22 | NOW! Innovations | System and Method For Managing Payment Based Parking with Near Field Communication |
US20120296741A1 (en) | 2011-05-19 | 2012-11-22 | Verifone, Inc. | Cloud based electronic wallet |
US8847733B2 (en) | 2011-05-20 | 2014-09-30 | Mastercard International Incorporated | Methods, systems, and computer-readable storage media for managing risk using location, mobile, and user participating-based identity verification |
US20120302204A1 (en) | 2011-05-24 | 2012-11-29 | Pankaj Gupta | Telecom Information Management System |
US20120303503A1 (en) | 2011-05-26 | 2012-11-29 | First Data Corporation | Systems and Methods for Tokenizing Financial Information |
US20120310760A1 (en) | 2011-06-03 | 2012-12-06 | Simon Phillips | Mobile device automatic card account selection for a transaction |
US8538845B2 (en) | 2011-06-03 | 2013-09-17 | Mozido, Llc | Monetary transaction system |
CN103797500A (en) | 2011-06-03 | 2014-05-14 | 维萨国际服务协会 | Virtual wallet card selection apparatuses, methods and systems |
US20160055583A1 (en) | 2011-06-03 | 2016-02-25 | Mozido, Inc. | Mobile global exchange platform |
US20140006048A1 (en) | 2011-06-03 | 2014-01-02 | Michael A. Liberty | Monetary transaction system |
WO2013101297A1 (en) | 2011-06-07 | 2013-07-04 | Visa International Service Association | Payment privacy tokenization apparatuses, methods and systems |
US20120316950A1 (en) | 2011-06-10 | 2012-12-13 | Jeffrey Laporte | System and method for augmentation of retail pos data streams with transaction information |
US20120323664A1 (en) | 2011-06-16 | 2012-12-20 | Apple Inc. | Integrated coupon storage, discovery, and redemption system |
US20120323777A1 (en) | 2011-06-20 | 2012-12-20 | Liberty Michael A | Business to business mobile vault |
US20130030960A1 (en) | 2011-06-22 | 2013-01-31 | Cellco Partnership D/B/A Verizon Wireless | Alternative data plans |
US20130246141A1 (en) | 2011-06-22 | 2013-09-19 | Michael A. Liberty | Disruptively priced or free financial services or items in exchange for participation in opt in advertising |
WO2013009446A1 (en) | 2011-06-22 | 2013-01-17 | Mozido, Llc | Disruptively priced or free financial services or items in exchange for participation in opt in advertising |
US20120330792A1 (en) | 2011-06-22 | 2012-12-27 | Cellco Partnership D/B/A Verizon Wireless | Open data transport bundle marketplace exchange |
US20120330737A1 (en) | 2011-06-22 | 2012-12-27 | Liberty Michael A | Disruptively priced or free financial services or items in exchange for participation in opt in advertising |
US10121129B2 (en) | 2011-07-05 | 2018-11-06 | Visa International Service Association | Electronic wallet checkout platform apparatuses, methods and systems |
US20130013490A1 (en) | 2011-07-08 | 2013-01-10 | Bank Of America Corporation | Mobile apparatus with back-up payment system |
US8818868B2 (en) | 2011-07-15 | 2014-08-26 | Bank Of America Corporation | Foreign currency solution |
US9947010B2 (en) | 2011-07-15 | 2018-04-17 | Mastercard International Incorporated | Methods and systems for payments assurance |
US20130024377A1 (en) | 2011-07-20 | 2013-01-24 | Daryl Stong | Methods And Systems For Securing Transactions And Authenticating The Granting Of Permission To Perform Various Functions Over A Network |
US20130046645A1 (en) | 2011-08-16 | 2013-02-21 | Bank Of America Corporation | System and method for point of transaction authentication |
US20130046634A1 (en) | 2011-08-19 | 2013-02-21 | Bank Of America Corporation | Combining offers from multiple merchants based on the geographic proximity of the merchants |
US20130054412A1 (en) | 2011-08-22 | 2013-02-28 | American Express Travel Related Services Company, Inc. | Methods and systems for contactless payments for online ecommerce checkout |
US20130054441A1 (en) | 2011-08-23 | 2013-02-28 | Bhavik Kamdar | Methods and systems for trading in monetary equivalent instruments |
US10140620B2 (en) | 2011-09-15 | 2018-11-27 | Stephan HEATH | Mobile device system and method providing combined delivery system using 3D geo-target location-based mobile commerce searching/purchases, discounts/coupons products, goods, and services, or service providers-geomapping-company/local and socially-conscious information/social networking (“PS-GM-C/LandSC/I-SN”) |
US20130073458A1 (en) | 2011-09-19 | 2013-03-21 | Cardinalcommerce Corporation | Open wallet for electronic transactions |
US20130080236A1 (en) | 2011-09-26 | 2013-03-28 | First Data Corporation | Systems and Methods for Enrolling Consumers in Loyalty Programs |
US20130091012A1 (en) | 2011-10-05 | 2013-04-11 | Michael A. Liberty | Conferring health related services or items in exchange for participation in opt-in advertising |
US20160078493A1 (en) | 2011-10-05 | 2016-03-17 | Mozido | Conferring health related services or items in exchange for participation in opt-in advertising |
US9208488B2 (en) | 2011-11-21 | 2015-12-08 | Mozido, Inc. | Using a mobile wallet infrastructure to support multiple mobile wallet providers |
US10438196B2 (en) | 2011-11-21 | 2019-10-08 | Mozido, Inc. | Using a mobile wallet infrastructure to support multiple mobile wallet providers |
WO2013166174A1 (en) | 2012-05-02 | 2013-11-07 | Mozido, Llc | Disruptively priced or free financial services or items in exchange for participation in opt in advertising |
US8484133B1 (en) | 2012-05-18 | 2013-07-09 | MoviePass Inc. | Secure targeted personal buying/selling method and system |
AU2013266099A1 (en) | 2012-05-24 | 2015-01-22 | Paypal, Inc. | Method and systems for wallet enrollment |
US20150310489A1 (en) | 2012-07-09 | 2015-10-29 | Mohammed F. Hussain | Self service digital coupon, discount deal and weekly ad publishing and management method |
JP6075153B2 (en) | 2012-07-11 | 2017-02-08 | 富士通株式会社 | Processing server and transfer management method |
US20150039517A1 (en) | 2013-08-05 | 2015-02-05 | Mozido, Inc. | Cloud entertainment platform |
US20150073891A1 (en) | 2013-09-10 | 2015-03-12 | Telefonaktiebolaget L M Ericsson (Publ) | Method and System For Determining User Advertising Ratings |
US20150100398A1 (en) | 2013-10-08 | 2015-04-09 | International Business Machines Corporation | Method for Dynamic Coupon Pricing |
-
2012
- 2012-05-30 US US13/484,199 patent/US8538845B2/en active Active
- 2012-05-31 RU RU2013158871A patent/RU2620715C2/en active
- 2012-05-31 WO PCT/US2012/040131 patent/WO2013025273A1/en active Application Filing
- 2012-05-31 EP EP12824344.1A patent/EP2715632A4/en not_active Ceased
- 2012-05-31 MX MX2013014209A patent/MX2013014209A/en unknown
- 2012-06-03 SA SA112330567A patent/SA112330567B1/en unknown
-
2013
- 2013-08-12 US US13/964,707 patent/US20130332347A1/en not_active Abandoned
-
2014
- 2014-03-14 US US14/213,543 patent/US20140201070A1/en not_active Abandoned
-
2016
- 2016-07-01 US US15/201,152 patent/US9892386B2/en active Active
-
2017
- 2017-11-10 US US15/809,872 patent/US11295281B2/en active Active
-
2019
- 2019-09-12 US US16/569,348 patent/US11120413B2/en active Active
-
2021
- 2021-07-20 US US17/380,839 patent/US20210350342A1/en active Pending
-
2022
- 2022-01-25 US US17/584,064 patent/US20220147969A1/en active Pending
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20050187873A1 (en) * | 2002-08-08 | 2005-08-25 | Fujitsu Limited | Wireless wallet |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9892386B2 (en) | 2011-06-03 | 2018-02-13 | Mozido, Inc. | Monetary transaction system |
US11120413B2 (en) | 2011-06-03 | 2021-09-14 | Fintiv, Inc. | Monetary transaction system |
US11295281B2 (en) | 2011-06-03 | 2022-04-05 | Fintiv, Inc. | Monetary transaction system |
US9208488B2 (en) | 2011-11-21 | 2015-12-08 | Mozido, Inc. | Using a mobile wallet infrastructure to support multiple mobile wallet providers |
US10438196B2 (en) | 2011-11-21 | 2019-10-08 | Mozido, Inc. | Using a mobile wallet infrastructure to support multiple mobile wallet providers |
US11468434B2 (en) | 2011-11-21 | 2022-10-11 | Fintiv, Inc. | Using a mobile wallet infrastructure to support multiple mobile wallet providers |
WO2017006194A1 (en) * | 2015-07-07 | 2017-01-12 | DOWNER, Albert | System of payment made in real time |
Also Published As
Publication number | Publication date |
---|---|
WO2013025273A1 (en) | 2013-02-21 |
US11295281B2 (en) | 2022-04-05 |
SA112330567B1 (en) | 2015-09-13 |
US20120310824A1 (en) | 2012-12-06 |
US20180130036A1 (en) | 2018-05-10 |
US9892386B2 (en) | 2018-02-13 |
US20160314443A1 (en) | 2016-10-27 |
US11120413B2 (en) | 2021-09-14 |
US20140201070A1 (en) | 2014-07-17 |
EP2715632A4 (en) | 2014-11-05 |
RU2013158871A (en) | 2015-07-20 |
US20210350342A1 (en) | 2021-11-11 |
MX2013014209A (en) | 2015-01-12 |
US20200005257A1 (en) | 2020-01-02 |
RU2620715C2 (en) | 2017-05-29 |
US8538845B2 (en) | 2013-09-17 |
US20220147969A1 (en) | 2022-05-12 |
EP2715632A1 (en) | 2014-04-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11120413B2 (en) | Monetary transaction system | |
US11468434B2 (en) | Using a mobile wallet infrastructure to support multiple mobile wallet providers | |
US9208488B2 (en) | Using a mobile wallet infrastructure to support multiple mobile wallet providers | |
US20160055583A1 (en) | Mobile global exchange platform | |
US20120323777A1 (en) | Business to business mobile vault | |
US8504450B2 (en) | Mobile remittances/payments | |
US20170364898A1 (en) | Mobile payment system and method | |
US20140006048A1 (en) | Monetary transaction system | |
WO2007040693A2 (en) | System and method for carrying out a financial transaction | |
US20120330737A1 (en) | Disruptively priced or free financial services or items in exchange for participation in opt in advertising | |
US20130246141A1 (en) | Disruptively priced or free financial services or items in exchange for participation in opt in advertising | |
WO2018189597A1 (en) | Mobile bank account management systems | |
US20120221465A1 (en) | Clearinghouse system for monetary and non-monetary transfers of value | |
WO2013009446A1 (en) | Disruptively priced or free financial services or items in exchange for participation in opt in advertising | |
WO2013166174A1 (en) | Disruptively priced or free financial services or items in exchange for participation in opt in advertising | |
KR102472450B1 (en) | System for providing settlement instant payment service | |
WO2016073519A1 (en) | Mobile global exchange platform | |
KR20100107366A (en) | System and method for managing medical expenses settlement by installments using phone bill and recording medium | |
WO2022137026A1 (en) | A method and system for processing financial transactions for a customer | |
US20150039503A1 (en) | Mobile remittances/payments |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MOZIDO, LLC, TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:LIBERTY, MICHAEL A.;REEL/FRAME:031563/0644 Effective date: 20131107 |
|
AS | Assignment |
Owner name: MOZIDO, INC., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MOZIDO, LLC;REEL/FRAME:031769/0677 Effective date: 20131123 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: FINTIV, INC., TEXAS Free format text: CHANGE OF NAME;ASSIGNOR:MOZIDO, INC.;REEL/FRAME:051276/0649 Effective date: 20190418 |
|
AS | Assignment |
Owner name: FINTIV, INC., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FERNANDES, FELIPE;REEL/FRAME:051878/0855 Effective date: 20200203 |