U.S. Patent No. 9,892,386 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,
`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;
`
`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;
`
`database services operable to store financial transaction
`details, store customer profiles, and manage money
`containers;
`
` a
`
` payment handler service operable to use APIs of
`different payment processors including one or more APIs
`of banks, credit and debit cards processors, bill payment
`processors;
`
` a
`
` rules engine operable to gather financial transaction
`statistics and use the gathered financial transaction
`statistics to enforce constraints including transaction
`constraints;
`
`to perform subscriber
`
` a
`
` security service operable
`authentication;
`
`
`IPR2022-00976
`Fintiv Ex. 2008 | Page 1 of 8
`
`
`
`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,
`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;
`
`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;
`
`database services operable to store financial transaction
`details, store customer profiles, and manage money
`containers;
`
` a
`
` payment handler service operable to use APIs of
`different payment processors including one or more APIs
`of banks, credit and debit cards processors, bill payment
`processors;
`
` a
`
` rules engine operable to gather financial transaction
`statistics and use the gathered financial transaction
`statistics to enforce constraints including transaction
`constraints;
`
`to perform subscriber
`
` a
`
` security service operable
`authentication;
`
`
`IPR2022-00976
`Fintiv Ex. 2008 | Page 1 of 8
`
`
`
`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: wherein the at least one
`entity is the agent;
`
`wherein the monetary transaction system is implemented
`to deposit funds at an agent branch,
`
`the funds being deposited by a subscriber at the agent
`branch using a mobile device configured to run a monetary
`transaction system application, the monetary transaction
`system performing the following steps:
`
`receiving a communication message from the mobile
`device over one of a plurality of channels connected to the
`monetary transaction system, the communication message
`being received by an API associated with the integration
`tier of the monetary transaction system,
`
`the communication message 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, wherein
`validating the status of the subscriber's account comprises
`communicating from the integration tier to the database
`services to query attributes of the subscriber's account;
`
`committing a pending transaction through the business
`process
`services, wherein
`the
`integration
`tier
`communicates a transaction commitment request to the
`business process services;
`
`receiving a confirmation from the business process
`services that the pending transaction has been committed;
`sending, through the notification services, a receipt
`notification to the mobile device; and
`
`
`IPR2022-00976
`Fintiv Ex. 2008 | Page 2 of 8
`
`
`
`upon receiving a confirmation of commitment from the
`business process services, committing
`the pending
`transaction to the database services; and
`wherein committing the pending transaction further
`comprises the following steps as orchestrated by the
`business process services:
`
`ensuring, via the database services, that the subscriber has
`an active account;
`
`validating, through communication with the security
`services, one or more of a PIN number and an access
`control list;
`
`applying with the rules engine, velocity rules;
`
`creating with the database services a new pending
`transaction history record;
`
`holding funds from the agent account balance using the
`payment handler,
`
`loading the funds to the subscriber account using the
`payment handler; and
`
`the database services, a pending
`updating, using
`transaction history record to reflect the funds.
`
`2. 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;
`
`
`IPR2022-00976
`Fintiv Ex. 2008 | Page 3 of 8
`
`
`
`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;
`
`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
`
`to perform subscriber
`
` security service operable
`authentication;
`
`database services operable to store financial transaction
`details, store customer profiles, and manage money
`containers;
`
` a
`
` mobile device configured to run a monetary transaction
`system application;
`
` a
`
` payment handler service operable to use APIs of
`different payment processors including one or more APIs
`of banks, credit and debit cards processors, bill payment
`processors;
`
` a
`
` rules engine operable to gather financial transaction
`statistics and use the gathered financial transaction
`statistics
`to enforce business constraints
`including
`transaction constraints;
`
` a
`
`to perform subscriber
`
` security service operable
`authentication;
`
`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, wherein the at least one
`entity is the agent;
`
`
`IPR2022-00976
`Fintiv Ex. 2008 | Page 4 of 8
`
`
`
`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;
`
`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 message from the mobile
`device over one of a plurality of channels connected to the
`monetary transaction system, the communication message
`being received by an API associated with the integration
`tier of
`the monetary
`transaction
`system,
`the
`communication message indicating that the subscriber
`desires to withdraw a specified amount of funds from an
`account associated with the subscriber,
`
`the communication comprising a secure, perishable code;
`
`determining that the transaction is valid and in progress,
`wherein determining
`that
`the
`transaction
`is valid
`comprises validating the secure, perishable code and
`communicating from the integration tier to the database
`services to query attributes of the subscriber's account;
`
`committing a pending transaction through the business
`process
`services, wherein
`the
`integration
`tier
`communicates a transaction commitment request to the
`business process services;
`
`receiving a confirmation from the business process
`services that a pending transaction has been committed;
`sending, through the notification services, a receipt
`notification to the mobile device; and
`
`
`IPR2022-00976
`Fintiv Ex. 2008 | Page 5 of 8
`
`
`
`upon receiving a confirmation of commitment from the
`business process services, committing
`the pending
`transaction to the database services; and
`
`wherein committing the pending transaction further
`comprises the following steps as orchestrated by the
`business process services:
`
`ensuring, via the database services, that the subscriber has
`an active account;
`
`validating, through communication with the security
`services, one or more of a PIN number and an access
`control list;
`
`applying with the rules engine, velocity rules;
`
`creating with the database services a new pending
`transaction history record;
`
`holding funds from the agent account balance using the
`payment handler;
`
`loading the funds to the subscriber account using the
`payment handler; and
`
`the database services, a pending
`updating using
`transaction history record to reflect the funds.
`
`3. 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;
`
`IPR2022-00976
`Fintiv Ex. 2008 | Page 6 of 8
`
`
`
`
`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;
`
`database services operable to store financial transaction details, store
`customer profiles, and manage money containers;
`
` 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
`
` payment handler service operable to use APIs of different payment
`processors including one or more APIs of banks, credit and debit cards
`processors, bill payment processors;
`
` a
`
` rules engine operable to gather financial transaction statistics and use the
`gathered financial transaction statistics to enforce business constraints
`including transaction constraints;
`
` security service operable to perform subscriber authentication;
`
` a
`
`
`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; wherein the
`at least one entity is the agent;
`
`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 a communication message from the mobile device over one of a
`plurality of channels connected to the monetary transaction system, the
`communication message being received by an API associated with the
`integration tier of the monetary transaction system, the communication
`
`IPR2022-00976
`Fintiv Ex. 2008 | Page 7 of 8
`
`
`
`message indicating that the subscriber desires to transfer a specified amount
`of funds from the subscriber's account to a recipient;
`
`validating the status of the subscriber's account, wherein validating the status
`of the subscriber's account comprises communicating from the integration tier
`to the database services to query attributes of the subscriber's account;
`
`committing a pending transaction through the business process services,
`wherein the integration tier communicates a transaction commitment request
`to the business process services;
`
`receiving a confirmation from the business process services that a pending
`transaction has been committed;
`
`sending, through the notification services, a receipt notification to the mobile
`device; and
`
`upon receiving a confirmation of commitment from the business process
`services, committing the pending transaction to the database services; and
`
`wherein committing the pending transaction further comprises the following
`steps as orchestrated by the business process services:
`
`ensuring, via the database services, that the subscriber has an active account;
`
`validating, through communication with the security services, one or more of
`a PIN number and an access control list;
`
`applying with the rules engine, velocity rules;
`
`creating with the database services a new pending transaction history record;
`holding funds from the agent account balance using the payment handler;
`
`loading the funds to the subscriber account using the payment handler; and
`
`updating, using the database services, a pending transaction history record to
`reflect the funds.
`
`
`
`IPR2022-00976
`Fintiv Ex. 2008 | Page 8 of 8
`
`
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
Still Working On It
This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.
Give it another minute or two to complete, and then try the refresh button.
A few More Minutes ... Still Working
It can take up to 5 minutes for us to download a document if the court servers are running slowly.
Thank you for your continued patience.
This document could not be displayed.
We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.
Your account does not support viewing this document.
You need a Paid Account to view this document. Click here to change your account type.
Your account does not support viewing this document.
Set your membership
status to view this document.
With a Docket Alarm membership, you'll
get a whole lot more, including:
- Up-to-date information for this case.
- Email alerts whenever there is an update.
- Full text search for other cases.
- Get email alerts whenever a new case matches your search.
One Moment Please
The filing “” is large (MB) and is being downloaded.
Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.
Your document is on its way!
If you do not receive the document in five minutes, contact support at support@docketalarm.com.
Sealed Document
We are unable to display this document, it may be under a court ordered seal.
If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.
Access Government Site
