MONETARY TRANSACTION SYSTEM

• US 20160314443A1
• Filed: 07/01/2016
• Published: 10/27/2016
• Est. Priority Date: 06/03/2011
• Status: Active Grant

• Current Assignee: Fintiv, Inc.
• Original Assignee: Mozido, LLC (Fintiv, Inc.)
• Inventors: Liberty, Michael A.
• Granted Patent: US 9,892,386 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 9/546 Message passing systems or structures, e.g. queues
• CPC Class Codes: G06Q 20/0855 involving a third party
• CPC Class Codes: G06Q 20/10 specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
• CPC Class Codes: G06Q 20/322 Aspects of commerce using mobile devices [M-devices]
• CPC Class Codes: G06Q 20/3255 using mobile network messaging services for payment, e.g. SMS
• CPC Class Codes: G06Q 20/326 Payment applications installed on the mobile devices
• CPC Class Codes: G06Q 20/36 using electronic wallets or electronic money safes
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 20/405 Establishing or using transaction specific rules
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: H04L 63/101 Access control lists [ACL]

Abstract

Embodiments are directed to monetary transaction system for conducting monetary transactions between transaction system subscribers and other entities. In one scenario, the monetary transaction system includes a mobile device that runs a monetary transaction system application. The monetary transaction system also includes a subscriber that has a profile with the system. The subscriber indicates a transaction that is to be performed with the monetary transaction system. The system further includes a monetary transaction system processor that performs the transactions specified by the subscriber including 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.

Claims

1. A monetary transaction system for conducting monetary transactions between subscribers and other entities, the system comprising one or more of:

an integration tier operable to manage mobile wallet sessions and maintain the integrity of financial transactions, the integration tier also including a communication application programming interface (API) and other communication mechanisms to accept messages from channels;

notification services operable to send notifications through different notification channels including one or more of short message peer-to-peer, short-message services and simple mail transfer protocol emails;

a service connector layer comprised of a plurality of service connector modules operable to connect to third party systems, wherein each service connector module is deployed as a separate module intended to integrate an external service to at least a portion of system architecture;

business process services operable to implement business workflows, including at least one of executing financial transactions, auditing financial transactions, invoking third-party services, handling errors, and logging platform objects;

a payment handler service operable to use the APIs of different payment processors including one or more APIs of banks, credit and debit cards processors, bill payment processors;

the payment handler service using a common API wrapper to facilitate interactions with many different kinds of payment processors;

a security service operable to perform subscriber authentication;

an authorization service operable to perform client authorization using a database-based access control list table;

a database operable to store financial transaction details, store customer profiles, and manage money containers; and

a rules engine operable to gather financial transaction statistics and use the gathered statistics to enforce business constraints including transaction constraints;

a mobile device configured to run a monetary transaction system application;

a monetary transaction system subscriber that has a profile with the monetary transaction system the subscriber profile stored in the database of the monetary transaction system, wherein the subscriber indicates, via the monetary transaction system application, one or more specified transactions that are to be performed using the monetary transaction system;

a monetary transaction system processor that performs the one or more transactions specified by the subscriber, wherein performing the specified transactions includes communicating with the monetary transaction database to determine whether the transaction is permissible based on data indicated in the subscriber'"'"'s profile determination made by the rules engine of the monetary transaction system;

at least one entity that is to be involved in the specified transaction, the at least one entity having a profile with the monetary transaction system; and

wherein the monetary transaction system is implemented to deposit funds at an agent branch, funds deposited by subscriber at the agent branch using the mobile device configured to run a monetary transaction system application, including performing the following steps;

receiving communication from an agent branch over one of a plurality of channels connected to the monetary transaction system message received by an integration tier of the monetary transaction system, the agent communication indicating that the subscriber desires to deposit a specified amount of funds into the subscriber'"'"'s account;

validating the status of the subscriber'"'"'s account;

determining if the agent branch is authorized to receive deposited money;

performing one or more of a limit check and a velocity check on the subscriber'"'"'s account, the limit check determining whether sufficient funds are available to make the deposit amount, the velocity check determining whether the subscriber has exceeded a specified number of transactions within a specified time period;

crediting the subscriber'"'"'s account with the specified amount of funds from the agent branch that is authorized to receive the deposited money;

returning a notification to the agent branch confirming the deposit; and

notifying the subscriber that the specified amount of funds was deposited in the subscriber'"'"'s account over at least one of the plurality of channels connected to the monetary transaction system.

2. The monetary transaction system of claim 1, wherein the monetary transaction system application provides a web interface that allows subscribers to perform the same functions provided by the monetary transaction system application.

3. The monetary transaction system of claim 1, wherein the monetary transaction system application is provided on a prepaid or postpaid phone.

8. The monetary transaction system of claim 1, wherein a secure, perishable code is sent to the subscriber over at least one of the plurality of channels connected to the monetary transaction system.

4. A monetary transaction system for conducting monetary transactions between subscribers and other entities, the system comprising one or more of:

an integration tier operable to manage mobile wallet sessions and maintain the integrity of financial transactions, the integration tier also including a communication application programming interface (API) and other communication mechanisms to accept messages from channels;

notification services operable to send notifications through different notification channels including one or more of short message peer-to-peer, short-message services and simple mail transfer protocol emails;

a service connector layer comprised of a plurality of service connector modules operable to connect to third party systems, wherein each service connector module is deployed as a separate module intended to integrate an external service to at least a portion of system architecture;

business process services operable to implement business workflows, including at least one of executing financial transactions, auditing financial transactions, invoking third-party services, handling errors, and logging platform objects;

a payment handler service operable to use the APIs of different payment processors including one or more APIs of banks, credit and debit cards processors, bill payment processors;

the payment handler service using a common API wrapper to facilitate interactions with many different kinds of payment processors;

a security service operable to perform subscriber authentication;

an authorization service operable to perform client authorization using a database-based access control list table;

a database operable to store financial transaction details, store customer profiles, and manage money containers; and

a rules engine operable to gather financial transaction statistics and use the gathered statistics to enforce business constraints including transaction constraints;

a mobile device configured to run a monetary transaction system application;

a monetary transaction system subscriber that has a profile with the monetary transaction system the subscriber profile stored in the database of the monetary transaction system, wherein the subscriber indicates, via the monetary transaction system application, one or more specified transactions that are to be performed using the monetary transaction system;

a monetary transaction system processor that performs the one or more transactions specified by the subscriber, wherein performing the specified transactions includes communicating with the monetary transaction database to determine whether the transaction is permissible based on data indicated in the subscriber'"'"'s profile determination made by the rules engine of the monetary transaction system;

at least one entity that is to be involved in the specified transaction, the at least one entity having a profile with the monetary transaction system; and

wherein the monetary transaction system is implemented to withdraw funds at an agent branch using the mobile device configured to run a monetary transaction system application, including performing the following steps;

receiving a communication from the subscriber from the mobile device configured to run the monetary transaction system, the communication indicating that the subscriber desires to withdraw a specified amount of funds from the subscriber'"'"'s account at the agent branch;

validating the status of the subscriber'"'"'s account;

determining if the balance of the subscriber'"'"'s account is sufficient to accommodate the requested withdrawal for the specified amount of funds;

performing one or more of a limit check and a velocity check on the subscriber'"'"'s account, the limit check determining whether sufficient funds are available to make the deposit amount, the velocity check determining whether the subscriber has exceeded a specified number of transactions within a specified time period;

returning a secure, perishable code to the subscriber over at least one of the plurality of channels connected to the monetary transaction system;

receiving subsequent agent branch communication over at least one of the plurality of channels connected to the monetary transaction system, the agent branch communication indicating that the withdrawal code has been presented to the agent branch;

debiting the subscriber'"'"'s account by the specified amount of funds;

returning a notification to the agent branch confirming the withdrawal; and

notifying the subscriber that the specified amount of funds was withdrawn from the subscriber'"'"'s account over at least one of the channels connected to the monetary transaction system.

5. A monetary transaction system for conducting monetary transactions between subscribers and other entities, the system comprising one or more of:

an integration tier operable to manage mobile wallet sessions and maintain the integrity of financial transactions, the integration tier also including a communication application programming interface (API) and other communication mechanisms to accept messages from channels;

notification services operable to send notifications through different notification channels including one or more of short message peer-to-peer, short-message services and simple mail transfer protocol emails;

a service connector layer comprised of a plurality of service connector modules operable to connect to third party systems, wherein each service connector module is deployed as a separate module intended to integrate an external service to at least a portion of system architecture;

business process services operable to implement business workflows, including at least one of executing financial transactions, auditing financial transactions, invoking third-party services, handling errors, and logging platform objects;

a payment handler service operable to use the APIs of different payment processors including one or more APIs of banks, credit and debit cards processors, bill payment processors;

the payment handler service using a common API wrapper to facilitate interactions with many different kinds of payment processors;

a security service operable to perform subscriber authentication;

an authorization service operable to perform client authorization using a database-based access control list table;

a database operable to store financial transaction details, store customer profiles, and manage money containers; and

a rules engine operable to gather financial transaction statistics and use the gathered statistics to enforce business constraints including transaction constraints;

a mobile device configured to run a monetary transaction system application;

a monetary transaction system subscriber that has a profile with the monetary transaction system the subscriber profile stored in the database of the monetary transaction system, wherein the subscriber indicates, via the monetary transaction system application, one or more specified transactions that are to be performed using the monetary transaction system;

a monetary transaction system processor that performs the one or more transactions specified by the subscriber, wherein performing the specified transactions includes communicating with the monetary transaction database to determine whether the transaction is permissible based on data indicated in the subscriber'"'"'s profile determination made by the rules engine of the monetary transaction system;

at least one entity that is to be involved in the specified transaction, the at least one entity having a profile with the monetary transaction system; and

wherein the monetary transaction system is implemented to transfer funds using the mobile device configured to run a monetary transaction system application, including performing the following steps;

receiving subscriber communication from the mobile device configured to run the monetary transaction system, the subscriber communication indicating that the subscriber desires to transfer a specified amount of funds to specified recipient using a specified payment method from the subscriber'"'"'s account;

validating the status of the subscriber'"'"'s account;

performing at least one of a limit check and a velocity check on the selected payment method, the limit check determining whether sufficient funds are available to make the deposit amount, the velocity check determining whether the subscriber has exceeded a specified number of transactions within a specified time period;

validating the status of the specified recipient to ensure the specified recipient has a valid account;

debiting the subscriber'"'"'s account by the specified amount of funds;

transferring the specified amount of funds to the specified recipient over at least one of the plurality of channels connected to the monetary transaction system;

notifying the subscriber that the specified amount of funds was transferred to the specified recipient over at least one of the plurality of channels connected to the monetary transaction system.

6. The monetary transaction system of claim 5, wherein validating the status of the specified recipient comprises performing a check on the specified recipient to comply with the office of foreign assets control.

7. The monetary transaction system of claim 5, wherein the money is transferred internationally between the mobile wallets.