Patent Grant
10068220
The present disclosure relates generally to computer-implemented systems and methods for electronic commerce and more specifically to electronic commerce user account management.
Electronic commerce, commonly known as electronic marketing, e-commerce, or eCommerce, consists of the buying and selling of products or services over electronic systems such as the Internet and other computer networks. The amount of trade conducted electronically has grown extraordinarily with widespread Internet usage. Commerce conducted in this manner utilizes a complex web of innovations in electronic funds transfer, supply chain management, Internet marketing, online transaction processing, electronic data interchange (EDI), inventory management systems, automated data collection systems, and many others. Modern electronic commerce typically uses the World Wide Web at least at some point in the transaction's lifecycle, although it can encompass a wider range of technologies such as e-mail as well.
A large percentage of electronic commerce is conducted entirely electronically for virtual items such as access to premium content on a website. Additionally, much electronic commerce involves the transportation of physical items in some way. Online retailers are sometimes known as e-tailers and online retail is sometimes known as e-tail. Almost all big retailers have electronic commerce presence on the World Wide Web.
With the continued increase in competition on the web, product, content, and service providers must strive to not only produce the best products, content, and services, but they must also compete to offer the most intuitive and fast mechanisms for providing their wares to interested consumers.
In accordance with the teachings provided herein, systems and methods are described for providing a transaction authorization for a transaction requested by a user to a merchant system. An example method includes the steps of receiving at a funds facilitation system a transaction authorization request from the merchant system, the transaction authorization request including a merchant identification and information identifying an account holder that initiated the transaction authorization request from the merchant system; comparing the merchant identification with merchant data stored in the funds facilitation system to determine if the merchant system has been categorized by the funds facilitation system as a trusted merchant; and based on a determination that the merchant system has been categorized as a trusted merchant, transmitting an electronic communication from the funds facilitation system to the merchant system to approve the transaction authorization request without the funds facilitation system receiving any additional authentication information from the account holder. In certain embodiments, the method may further include the step of accessing a remote user system associated with the account holder to verify that an identification-related cookie issued by the funds facilitation system is stored on the remote user system, the cookie including information to confirm the account holder's authorization to categorize the merchant system as a trusted merchant, and wherein transmission of the electronic communication approving the transaction authorization request without requiring additional authentication information is further based on a successful verification of the cookie.
In another example method, a transaction authorization may be provided from a funds facilitation system that requires a funds facilitation user authentication, where the transaction authorization is provided to a trusted merchant system without requiring user input of any funds facilitation user authentication information in excess of merchant authentication information required by the merchant system. The method may include receiving a transaction authorization request from the merchant system, where the transaction authorization request contains a merchant ID, a merchant user ID, and a transaction amount. A funds facilitation system user ID may be identified based on the merchant ID and the merchant user ID, and satisfaction of the funds facilitation user authentication is determined based on the merchant system associated with the merchant ID having a trusted status with the funds facilitation system and the existence of a funds facilitation system user ID that is associated with both the merchant ID and the merchant user ID. A transaction authorization message or a transaction denial message may be provided to the merchant system based on account information associated with the funds facilitation system user ID and the transaction amount.
As a further example, a computer-implemented system for providing a transaction authorization for a transaction requested by a user to a merchant system, where the transaction authorization is provided from a funds facilitation system that requires a funds facilitation user authentication, where the transaction authorization is provided to a trusted merchant system without requiring user input of any funds facilitation user authentication information in excess of merchant authentication information required by the merchant system may include a processor and a computer-readable storage medium containing instructions. When executed on the processor, the instructions cause the processor to perform operations that may include receiving a transaction authorization request from the merchant system, where the transaction authorization request contains a merchant ID, a merchant user ID, and a transaction amount. A funds facilitation system user ID may be identified based on the merchant ID and the merchant user ID, and satisfaction of the funds facilitation user authentication is determined based on the merchant system associated with the merchant ID having a trusted status with the funds facilitation system and the existence of a funds facilitation system user ID that is associated with both the merchant ID and the merchant user ID. A transaction authorization message or a transaction denial message may be provided to the merchant system based on account information associated with the funds facilitation system user ID and the transaction amount. In certain embodiments, the instructions may further cause the processor to access a remote user system to verify that an identification-related cookie issued by the funds facilitation system is stored on the remote user system, the cookie including information to confirm the user's authorization of the trusted status of the merchant system, and wherein satisfaction of the funds facilitation user authentication is further based on a successful verification of the cookie.
As an additional example, a computer-readable storage medium or mediums may be encoded with instructions that when executed, cause a computer to perform a method of providing a transaction authorization for a transaction requested by a user to a merchant system, where the transaction authorization is provided from a funds facilitation system that requires a funds facilitation user authentication, where the transaction authorization is provided to a trusted merchant system without requiring user input of any funds facilitation user authentication information in excess of merchant authentication information required by the merchant system. The method may include receiving a transaction authorization request from the merchant system, where the transaction authorization request contains a merchant ID, a merchant user ID, and a transaction amount. A funds facilitation system user ID may be identified based on the merchant ID and the merchant user ID, and satisfaction of the funds facilitation user authentication is determined based on the merchant system associated with the merchant ID having a trusted status with the funds facilitation system and the existence of a funds facilitation system user ID that is associated with both the merchant ID and the merchant user ID. A transaction authorization message or a transaction denial message may be provided to the merchant system based on account information associated with the funds facilitation system user ID and the transaction amount.
Another example method for processing an electronic payment transaction between a merchant system and a funds facilitation system may include the following steps: receiving at the merchant system, authentication information that identifies an account holder with the merchant system; receiving at the merchant system, a transaction request that specifies payment from the funds facilitation system; comparing the authentication information with account information stored in a database associated with the merchant system to identify a merchant user identification associated with the account holder; generating a transaction authorization request that includes the merchant user identification and that also includes a merchant identification, the merchant identification being an identification associated with the merchant system in the funds facilitation system; transmitting the transaction authorization request from the merchant system to the funds facilitation system so that the funds facilitation system can compare the merchant identification with merchant data stored in the funds facilitation system to determine if the merchant system has been categorized by the funds facilitation system as a trusted merchant, and based on a determination that the merchant system has been categorized as a trusted merchant, transmit an electronic communication from the funds facilitation system to the merchant system to approve the transaction authorization request without the funds facilitation system receiving any additional authentication information from the account holder; receiving the electronic communication from the funds facilitation system at the merchant system; and based upon receipt of the electronic communication, the merchant system approving the transaction request.
Another example method of processing an electronic payment transaction with a merchant system may include the steps of: receiving at a funds facilitation system a first transaction authorization request from the merchant system, the first transaction authorization request including information identifying an account holder that initiated the first transaction authentication request from the merchant system; in association with the first transaction authorization request, receiving authentication information from the account holder to verify the identity of the account holder in relation to an account with the funds facilitation system; based on a successful verification of the authentication information, generating cookie information associated with the account holder and the merchant system and storing the cookie information at a remote user system of the account holder; in response to the first transaction authorization request and the successful verification of the authentication information, transmitting a first electronic communication from the funds facilitation system to the merchant system to approve the first transaction authorization request; receiving at the funds facilitation system a subsequent transaction authorization request from the merchant system, the subsequent transaction authorization request including information identifying the account holder that initiated the subsequent transaction authentication request from the merchant system; in response to the subsequent transaction authorization request, verifying that the cookie information is stored at the remote user system of the account holder and is valid; and based on a successful verification that the cookie information is stored at the remote user system and is valid, transmitting a subsequent electronic communication from the funds facilitation system to the merchant system to approve the subsequent transaction authorization request without the funds facilitation system again receiving the authentication information from the account holder.
The details of one or more embodiments of the invention are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the invention will become apparent from the description, the drawings, and the claims.
FIGS. 4A1, 4A2 and 4B depict a flow diagram for an exemplary micropayment purchase from a payee website.
A payer is an entity that engages in a value transfer, such as an individual or a small business. The payer participates in a transaction with a payee, usually by purchasing a good or service from the payee and/or by exchanging items, services or other value with the payee.
A payee is a second entity that engages in a value transfer. A payee participates in a transaction with a payer, usually by providing a good or service to the payer in exchange for value and/or by exchanging items, services or other value with the payer.
A transaction is a flow of value between entities, such as a payer and a payee.
A micropayment transaction is a transaction in which the value to be transferred is less than a threshold value, such as, for example and without limitation, approximately five dollars.
Upon completion of the account setup routine or once the password is entered or the payer is otherwise authenticated to the micropayment processing system if an account had previously been established, a determination may be made as to whether sufficient value is present to complete the transaction. If not, the payer 105 may select a value source from which funds are received 225 by the micropayment processing system 115. In an embodiment, funds may be received 225 from, for example and without limitation, credit card, debit card, a direct debit from a bank account via, for example, Automated Clearing House (ACH), direct deposit or the like, over the counter to an agent, and/or from a deposited amount. The micropayment processing system 115 may transmit 230 the transaction information supplied by the payer 105 to the acquirer bank 120. The acquirer bank 120 may facilitate an authorization procedure with a direct debit account or the card acquirer. If the payer 105 is authorized, the acquirer bank 120 may confirm 235 the load of value to the micropayment processing system 115, which forwards 240 the confirmation to the payer. Otherwise, the micropayment process may terminate 245. In an alternate embodiment, the payer 105 may be provided with one or more additional opportunities to provide proper authorizing information to the micropayment processing system 115.
Once sufficient value is present to complete the transaction, the micropayment processing system 115 may transfer 250 funds from any payer account to any payee account. In an embodiment, a payer account and a payee account may be attributes of the same account. The micropayment processing system 115 may then notify 255 the payer 105 and the payee 110 that the transaction has successfully completed. The payer 105 may then be returned 260 to the payee website 110.
Determinations may be made 404 as to whether the payer has previously registered with the micropayment processing system and whether the payee is a Trusted Merchant. In an embodiment, a payee may be required to submit to a qualifying process to be considered a Trusted Merchant. A payer may further be required to select a payee from a list of payees that have been qualified as Trusted Merchants in order for the payee to be a Trusted Merchant for that payer.
In an embodiment, a payer may elect to have a verification code or token stored as part of the payer's registered profile with a Trusted Merchant. The payer may make this request when interfacing with the Trusted Merchant or with the micropayment processing system (e.g. through Internet Banking or an interface facilitated to the micropayment processing system independent of a transaction by the Trusted Merchant). Upon receipt of a cardholder request, the micropayment processing system may provide a verification code or token to the Trusted Merchant for storage as part of the registered payer's profile. In an embodiment, the verification code or token may be generated in response to the payer's request so that it only verifies transactions by the payer made at the specified Trusted Merchant, may be provided to the Trusted Merchant in a fully encrypted form, and may only be decryptable by the micropayment processing system. In an embodiment, the token may allow session-based authentication. In another embodiment, the token may be used without session-specific authentication. When the payer performs a transaction with the Trusted Merchant, the payee may submit a payment authorization request accompanied by the payer's verification code or token to the micropayment processing system. The micropayment processing system may decrypt the verification code or otherwise verify a token upon receipt of the payment authorization request and provide an appropriate payment authorization response with all necessary data elements. The payee website may receive the payment authorization response and process the response as appropriate. In an embodiment, if the payer has previously registered, the Trusted Merchant may engage in a transaction with the registered payer without resubmitting identifying information for the parties, such as a password, an email address or the like.
If the payer has not previously been registered, a registration screen may be displayed 406 requesting profile information from the payer. For example, the payer may provide a name, address, telephone number, and/or the like. Once the payer provides 408 the requested information, a payment selection screen may then be displayed 410. The payment selection screen may enable the payer to select a payment type, such as a Visa®-branded credit card, the source details for the selected payment type and a load amount. In an embodiment, one or more selections for a load amount may be displayed via a pull-down menu. The micropayment processing system may submit 412 the load transaction to an external authorization service. If the transaction is not authorized, the micropayment processing system may display 410 the payment selection screen again. In an embodiment, if the load transaction fails a second time, the micropayment transaction may fail 414. If the load transaction is authorized, the micropayment payment system may display 416 a load confirmation screen, which requests, for example, a password and selections and answers for, for example, three security questions. In other examples, additional or alternate information may be requested from the user within the scope of this disclosure. In addition, an alternate number of security questions, other security verification methodologies and/or load transaction failures may also be included within the scope of this disclosure.
If the payer successfully completes the registration process or if the payer is determined to be registered, but the payee is not a Trusted Merchant, in step 404, the micropayment processing system may display 418 a purchase amount, a name for the payee and a description of the item for purchase. The system may further display 418, for example, a text entry field in which the payer is requested to enter an identifier, such as an email address, and a password corresponding to the entered identifier. A determination may then be made 420 as to whether the entered password corresponds to the identifier. If not, the micropayment processing system may display 422 one or more security questions pre-selected by the payer during the registration process. In an embodiment, the displayed security question may be selected randomly from the pre-selected security questions. The payer's answer to the displayed security question may be compared 424 with the answer provided during registration. If an improper answer is provided, a denial message may be transmitted 426 to the payee. The payee website may then display 428 a message requesting an alternate form of payment from the payer. If the proper answer is provided, the user may reconfigure and confirm 430 the password for the account and alternately select new security questions and responses. The process may then return to step 418.
If the entered password is determined 420 to correspond to the identifier or if the payer is registered and the payee is a Trusted Merchant in step 404, one or more further determinations may be made. For example, a determination may be made 432 as to whether the transaction amount falls within user-defined account parameters. Such parameters may include, for example and without limitation, whether the payee has been allowed and/or blocked, whether a total value limit is satisfied, whether the transaction satisfies value limits for the payee and/or whether the transaction satisfies time limitations for the account. Other account parameters may be defined within the scope of this disclosure on, for example, a per-payer, per-payee and/or per-account basis. Moreover, for transactions made by payers other than the primary payer for an account, a determination may be made 434 as to whether the primary payer has permitted the transaction. For example, a parent may set a limitation on transactions that a child performs using the account, such as the type, dollar amount or the like for such transactions. If any user-defined account parameters and/or primary payer parameter is not satisfied for a transaction, the payee website may display 436 a denial message to the payer and request that an alternate form of payment be selected.
If all parameters are satisfied, a determination as to the relationship between a transaction value and a threshold may be made 438. For example, if the transaction value is greater than and/or equal to a pre-defined threshold, a payment screen may be displayed 440 to the payer. The payment screen may include, for example and without limitation, one or more default payment sources and details, such as a masked account number, for each source. The payer may select a source and the transaction may be submitted 442 for external authorization. If the issuing system of selected payment source authorizes 444 the transaction, a screen may optionally be displayed 446 to the payer listing, for example, the purchase amount, the payee name, a description of the purchased goods and/or services and the like. The payer may submit the payment without providing additional information.
If the transaction value is less than and/or equal to a pre-defined threshold, a micropayment processing system may be selected for processing the transaction. The micropayment processing system may determine 448 whether sufficient funds remain in the payer's account. If not, the micropayment processing system may display 450 a screen requesting that the payer add additional funds to the account from a default payment source, such as a credit card, a bank account, or the like. In an embodiment, the screen may present the default payment source with masked information, such as the last four digits of a credit card number, bank account number, or the like. In an embodiment, the payer may provide an alternate payment source. In an embodiment, amounts to add to the account may be presented in a pull-down menu or similar method having pre-selected amounts. In an embodiment, the screen may include a text entry field in which the payer may specify a particular amount. Once the payer specifies an amount to add to the account, the micropayment processing system may submit 452 the load transaction for external authorization by the issuing system of the selected payment source. If the issuing system of the selected payment source authorizes 444 the transaction, a screen may optionally be displayed 446 to the payer listing, for example, the purchase amount, the payee name, a description of the purchased goods and/or services and the like. The payer may submit the payment without providing additional information.
If sufficient funds remain in the account or are added to the account, a transaction confirmation may be provided 454 to the payee website. The payee website, upon receipt of the confirmation from the micropayment processing system, may display 456 a confirmation message to the payer and permit 458 access to the goods and/or services. In an embodiment, if the payer desires 460 to purchase additional goods and/or services, the micropayment purchase process for such additional goods and/or services may skip to, for example, step 432. In an embodiment, the micropayment purchase process may skip to step 432 only if the additional goods and/or services are sought to be purchased during a single access session. In an embodiment, a payer may be required to provide a password again if, for example, a payer does not make a purchase within a pre-defined time period of a previous purchase, a payer has accessed a different website or the like. Alternately, the micropayment purchase process may skip to step 432 if the payee is a Trusted Merchant.
The computer-implemented environment further includes a funds facilitation system 1108. The funds facilitation system 1108 may be configured for identifying the availability of funds in a user account, acquiring funding for a user account, disbursing funding to a merchant to pay for a merchant performing a transaction, for determining whether a merchant should or should not perform a transaction, as well as other operations. The funds facilitation system 1108 is hosted on one or more servers through one or more networks 1106.
In an example operation, a user 1102 accesses a web page hosted on the merchant system 1104 via the one or more networks 1106. For example, the web page may list a number of book titles that are available for download from the merchant system in exchange for a payment from the user. The user 1102 indicates his desire to download one of the listed books by clicking a button on the web page that initiates a transaction request to the merchant system 1104.
Upon receipt of the transaction request, the merchant system 1104 prepares a transaction authorization request for authorization of and facilitating payment for the transaction requested by the user 1102. The merchant system 1104 may access one or more data stores 1110 to acquire a merchant identification (ID) 1112 identifying the merchant system 1104. The merchant system 1104 may further access the one or more data stores 1110 to access a merchant user identification (ID) 1114 associated with the user 1102 that provided the transaction request. The merchant user ID 1114 associated with the user 1102 may be identified based on a prior user identification at the merchant system 1104, such as the user 1102 providing a username and password combination. The merchant system 1104 packages the merchant ID 1112 the merchant user ID 1114 as well as a transaction amount associated with the transaction requested by the user 1102 into a transaction authorization request that is transmitted to the funds facilitation system 1108 via the one or more networks 1106.
The funds facilitation system 1108 receives the transaction authorization request from the merchant system 1104 and accesses one or more data stores 1116 responsive to the funds facilitation system 1108 to identify a funds facilitation system user ID 1118 associated with the merchant user ID included in the transaction authorization request. The funds facilitation system user ID 1118 accessed by the funds facilitation system 1108 provides a link to user account data 1120 for the user 1102 that provided the transaction request. The user account data 1120 may include data related to one or more accounts related to the user 1102 including prepaid accounts, stored value accounts, credit accounts, debit accounts, or the like. In one embodiment, the stored value accounts may be useful for conducting low value transactions. In another embodiment, the account may be a credit, debit, or other account, or an alias for such an account that may be more appropriate for higher value transactions. The funds facilitation system 1108 may determine the viability of the transaction described in the transaction authorization request from the merchant system 1104 based on the provided transaction amount, a funds available value from the user account data 1120, as well as other user account settings and data and other criteria.
If the funds facilitation system 1108 determines that the proper criteria for a transaction approval are met, the funds facilitation system 1108 may transfer the transaction amount from the user's account to the merchant and provide a transaction authorization to the merchant system 1104. Upon receipt of a transaction authorization from the funds facilitation system 1108, the merchant system 1104 may make the book title available for immediate download by the user 1102 with the knowledge that compensation for the transaction has been provided to the merchant.
While the above example describes providing a digital book to a user 1102 in response to a transaction request, the system 1100 may be utilized in a multitude of other scenarios. For example, instead of providing immediate digital content, the merchant may instead mail a physical product to the user 1102 or perform a service, such as a healthcare service, for the user 1102 upon receipt of a transaction authorization.
The funds facilitation system 1108 may comprise one or more servers containing software operations or routines for creating and maintaining accounts for the users 1102; for enabling the users 1102 to conduct transactions with one or more websites; for enabling users 1102 to initiate dispute proceedings with one or more websites and to automate the communications related to the dispute and the resolution of the dispute; to initiate and transmit alerts to users, websites, and or system administrators based upon pre-defined and/or customizable parameters; to configure and apply fees to transactions; and to conduct reporting as may be relevant to the merchant systems 1104, the funds facilitation system 1108 and/or the users 1102. Furthermore, the one or more servers of the funds facilitation system may additionally contain software operations or routines related to managing the accounts (such as by updating billing addresses, delivery addresses, user preferences, and the like); for enabling users to authorize and manage recurring payments or to pre-authorize payments; for enabling users to pre-authorize or prohibit (i.e., blacklist) websites and/or transactions; and/or for enabling users to manage accounts and conduct transactions using mobile electronic devices or any other electronic device such as internet-connected gaming consoles, a digital set-top box, or similar devices.
Upon receipt of the transaction request 1210 from the user 1202, the merchant system seeks data from a funds facilitation system 1206 as to whether the merchant should provide the transaction identified in the transaction request 1210. The merchant system 1204 seeks such authorization via a transaction authorization request 1212. A transaction authorization request 1212 includes a merchant ID that identifies the merchant associated with the merchant system 1204, a merchant user ID that identifies the user 1202 of the merchant system 1204 and a cost or transaction amount associated with the transaction that the user has requested. The transaction authorization request 1212 may further include a transaction description, a merchant transaction ID, a date/time that the transaction request 1210 was received, a date/time that the transaction authorization request was generated, a redirection URL for redirecting a user interface following the transaction, as well as other data. The transaction authorization request 1212 may be signed by the merchant system 1204 to authenticate the source of the request 1210 to the funds facilitation system 1206.
The funds facilitation system 1206 receives the transaction authorization request 1212 and determines whether the transaction requested by the user 1202 should be authorized and facilitates the transfer of funds from the user to the merchant providing the services upon authorization of the request. One or more accounts associated with the user 1202 may be associated with the funds facilitation system 1206. The funds facilitation system 1206 may be an actual account provider or may have access to information regarding one or more of the user's accounts and access to facilitate transfers regarding one or more of the user's account. For example, a funds facilitation system 1206 may be associated with a stored value account for a user, where a user is able to store a sum of money for easy, secure access in making online purchases. An example stored value account could allow a user 1202 to retain up to $1,000 in an online account from which the user 1202 may direct payments to be made for digital music downloads. The funds facilitation system 1206 may also have data acquisition capabilities regarding credit available for one or more of the user's credit cards and funds balances for a user's checking and savings accounts. The funds facilitation system 1206 may also be able to access funds or credits associated with user accounts or initiate transactions with those accounts to facilitate payment of merchants from which transactions are requested.
The data relating one or more accounts to a user 1202 and for facilitating transactions among the accounts may be user provided. The user 1202 may create an account with the funds facilitation system 1206 and associate one or more accounts with the user's funds facilitation system account. The user 1202 may also provide needed access to and data regarding the associated accounts to enable transactions using the one or more accounts. The funds facilitation system 1206 may provide a number of other functionalities to the user 1202 including enabling the user to conduct transactions with one or more websites; enabling users to initiate dispute proceedings with one or more websites and to automate the communications related to the dispute and the resolution of the dispute; initiating and transmitting alerts to users, websites, and or system administrators based upon pre-defined and/or customizable parameters; and conducting reporting as may be relevant to the users. Furthermore, the funds facilitation system 1206 may additionally contain software operations or routines related to managing the accounts (such as by updating billing addresses, delivery addresses, user preferences, and the like); for enabling users 1202 to authorize and manage recurring payments or to pre-authorize payments; for enabling users to pre-authorize or prohibit (i.e., blacklist) websites and/or transactions; and/or for enabling users 1202 to manage accounts and conduct transactions using mobile electronic devices or any other electronic device such as internet-connected gaming consoles, a digital set-top box, or similar devices. Users may access a funds facilitation system account by providing funds facilitation system account authentication information such as a username and password combination to a funds facilitation system web page or portal.
Upon receipt of a transaction authorization request 1212, the funds facilitation system 1206 may determine a funds facilitation system user ID based on the merchant ID and merchant user ID included in the transaction authorization request. For example, the funds facilitation system 1206 may know that user number “0123456” of merchant system “98765” is associated with funds facilitation system user “123.” The funds facilitation system 1206 may be informed of this association between merchant accounts and funds facilitation system user accounts via a user linking the accounts, as will be discussed in further detail with respect to
The funds facilitation system may require additional authentication from the user 1202 to facilitate the requested transaction depending on the relationship between the merchant system 1204 and the funds facilitation system 1206. If the merchant system 1204 is considered a trusted merchant system, the funds facilitation system 1206 may recognize the merchant system's authentication of the user 1202 as being sufficient for ensuring that the request is in fact from the user 1202. If the merchant system 1204 does not have a trusted system relationship with the funds facilitation system 1206, then the funds facilitation system 1206 may request additional user authentication information. For example, the funds facilitation system 1206 may request that the user provide their funds facilitation system username and/or password before authorizing the requested transaction. In this manner, fraudulent transactions may be reduced by requiring additional verifications for transactions involving non-trusted merchant systems, while transactions involving trusted merchant systems may be streamlined, enabling easier user transactions.
Upon identification and validation of the user 1202 by the funds facilitation system 1206, the funds facilitation system 1206 makes a determination as to whether the requested transaction should be authorized. For example, if a stored value account is associated with the user's funds facilitation system account, the stored value account is identified as the default payment account, and the stored value account contains sufficient funds for making a purchase of the transaction amount, then the funds facilitation system may authorize the transaction and facilitate transfer of the transaction amount from the stored value account to the merchant. If the stored value account contains insufficient funds, then the transaction may be denied, or the merchant system 1204 may be instructed to provide an interface to the user 1202 to identify an additional funding source or to refill the stored value account. The funds facilitation system 1206 communicates the authorization decision to the merchant system 1204 via a transaction authorization 1214. The transaction authorization 1214 may contain the merchant user ID for the user 1202, a transaction identifier value, a transaction authorization message, as well as other data.
Upon receipt of a transaction authorization 1214 from the funds facilitation system 1206, the merchant system may then fulfill the transaction as appropriate. For example, if the transaction request 1210 is for a digital music download, the merchant system may provide transaction fulfillment 1216 by providing a link to download the requested song. If the transaction request 1210 is for a physical product or service, then an indication may be provided to the user 1202 that the merchant will perform the requested transaction.
Following user authorization, the transaction authorization request 1604 is provided to a transaction authorization decision engine 1610 which accesses a data store 1612 to identify a funds facilitation system user ID associated with the merchant ID and merchant user ID provided in the transaction authorization request 1604. After identifying a funds facilitation system user ID for the user making the transaction request, the user's account info 1614 may be accessed. Based on the account info 1614 and the transaction amount recited in the transaction authorization request 1604, a transaction decision 1616 is rendered by the transaction authorization decision engine 1610 and output to the merchant system. For example, if the transaction amount is less than a high-value threshold and a stored value account identified in the account info 1614 contains insufficient funds to pay the transaction amount, then the transaction authorization decision engine 1610 may send a message (e.g., an additional funds needed message to the client or a transaction denied message to the merchant), as the transaction decision 1616. If the user provides authorization or information to make sufficient funds available, the transaction may still be approved, and the funds facilitation system 1602 may then execute the transfer of funds from the user's stored value account to an account associated with the merchant.
A trust level 1 merchant, also referred to as an express-session merchant, may enable a user 1710 to perform multiple transactions with the merchant system 1704 during a single session, while only entering funds facilitation system authentication information a single time during the session and without requiring any authentication directly with the merchant system. In such a session with a trust level 1 merchant, the merchant creates a temporary anonymous user ID for the user which is stored by the merchant system and provided to the funds facilitation system and is used in a token issued by the funds facilitation system to the merchant system and then provided by the merchant system to the funds facilitation system in subsequent transaction requests during the single session.
A trust level 2 merchant, also referred to as an express-seller merchant, may enable a user 1710 to perform multiple transactions with the merchant system 1706 during multiple sessions, while only entering funds facilitation system authentication system information a single time after first successfully authenticating themselves with the express seller merchant system authentication system. In such a session with a trust level 2 merchant, the merchant provides to the funds facilitation system the specific user ID which is associated with the user's authenticated profile on the merchant system and is used in a token issued by the funds facilitation system to the merchant system and then provided by the merchant system to the funds facilitation system in subsequent transaction requests during any future session with the merchant system where the user has first authenticated themselves to the merchant system.
Either an express-session or an express-seller relationship may be further secured, for example, by storing an identification cookie on the user's browser after the user successfully enters authentication information (e.g., a username and password) for the funds facilitation system. For instance, an express-session or express-seller link cookie may be generated by the funds facilitation system 1708 and stored on the user's browser upon successful authentication, and then the funds facilitation system 1708 may access the user's browser to verify the cookie for subsequent transactions with the express-session or express-seller merchant 1704, 1706.
Upon receipt of the transaction request 1810 from the user 1802, the express-seller merchant system sends a transaction authorization request 1812 to the funds facilitation system 1806 to determine whether the merchant should provide the transaction identified in the transaction request 1810. The transaction authorization request 1812 may include a merchant ID that identifies the merchant associated with the express-seller merchant system 1804, a merchant user ID that identifies the user 1802 of the express-seller merchant system 1804 and a cost or transaction amount associated with the transaction that the user has requested. The transaction authorization request 1812 may further include a transaction description, a merchant transaction ID, a date/time that the transaction request 1810 was received, a date/time that the transaction authorization request was generated, a redirection URL for redirecting a user interface following the transaction, as well as other data. In addition, the transaction authorization request 1812 may be signed by the express-seller merchant system 1804 to authenticate the source of the request 1812 to the funds facilitation system 1806.
Upon receipt of a transaction authorization request 1812, the funds facilitation system 1806 may determine a funds facilitation system user ID based on the merchant ID and merchant user ID included in the transaction authorization request. The funds facilitation system 1806 may be informed of this association between merchant accounts and funds facilitation system user accounts via a user linking the accounts, as will be discussed in further detail with respect to
If no express-seller link cookie is identified on the user system 1802, or if the identified link cookie is not valid, then the user 1802 may be required to provide funds facilitation authentication information 1816 to the funds facilitation system 1806 for further authentication of the user's account with the funds facilitation system 1806. For example, an express-seller link cookie, although valid for multiple sessions, may become invalid after a pre-determined time period or for other reasons. In addition, if no link cookie is identified or if the identified link cookie is no longer valid, the funds facilitation system 1806 may, upon successful authentication 1816, generate a new express-seller link cookie 1818 and store the link cookie on the user system 1802.
Upon identification and validation of the user 1802 by the funds facilitation system 1806, the funds facilitation system 1806 makes a determination as to whether the requested transaction should be authorized. For example, if a default payment account associated with the user's funds facilitation system account contains insufficient funds, then the transaction may be denied, or the merchant system 1804 may be instructed to provide a graphical user interface to the user 1802 to identify an additional funding source or to refill the stored value account. The funds facilitation system 1806 communicates the authorization decision to the express-seller merchant system 1804 via a transaction authorization 1820. The transaction authorization 1820 may contain the merchant user ID for the user 1802, a transaction identifier value, a transaction authorization message, as well as other data.
Upon receipt of a transaction authorization 1820 from the funds facilitation system 1806, the merchant system may then fulfill the transaction as appropriate.
Upon receipt of the initial transaction request 1832 from the user 1802, the express-session merchant system 1806 creates a temporary anonymous user ID for the session, and sends a transaction authorization request 1834 along with the temporary user ID to the funds facilitation system 1806 to determine whether the merchant should provide the transaction identified in the transaction request 1832. The transaction authorization request 1832 may include a merchant ID that identifies the merchant associated with the express-session merchant system 1830, the temporary anonymous user ID, and a cost or transaction amount associated with the transaction that the user has requested. The transaction authorization request 1832 may further include a transaction description, a merchant transaction ID, a date/time that the transaction request 1832 was received, a date/time that the transaction authorization request was generated, a redirection URL for redirecting a user interface following the transaction, as well as other data. In addition, the transaction authorization request 1834 may be signed by the express-session merchant system 1830 to authenticate the source of the request 1834 to the funds facilitation system 1806.
Upon receipt of an initial transaction authorization request 1834, the funds facilitation system 1806 may require the user 1802 to provide funds facilitation authentication information 1836 to the funds facilitation system 1806 to authenticate the user's account with the funds facilitation system 1806. Upon identification and validation of the user 1802 by the funds facilitation system 1806, the funds facilitation system 1806 generates an express-session link cookie 1838 and causes the cookie 1838 to be stored at the user system 1802. The express-session link cookie 1838 is only valid for the duration of a single session between the user system 1802 and the merchant system 1830, and enables multiple transactions by the user 1802 with the express-session merchant system 1830 during a single session, while only entering funds facilitation system authentication information 1836 a single time during the session. For security, an express-session link cookie 1838 may also be encrypted.
After successful identification and validation, the funds facilitation system 1806 makes a determination as to whether the requested transaction should be authorized. For example, if a default payment account associated with the user's funds facilitation system account contains insufficient funds, then the transaction may be denied, or the merchant system 1830 may be instructed to provide a graphical user interface to the user 1802 to identify an additional funding source or to refill the stored value account. The funds facilitation system 1806 communicates the authorization decision to the express-session merchant system 1830 via a transaction authorization 1840. The transaction authorization 1840 may contain the merchant user ID for the user 1802, a transaction identifier value, a transaction authorization message, as well as other data. Upon receipt of a transaction authorization 1840 from the funds facilitation system 1806, the merchant system 1830 may then fulfill the transaction as appropriate, as shown at reference 1842.
At reference 1844, a subsequent transaction request is submitted by the user 1802 to the merchant 1830 during the same session. Upon receipt of the subsequent transaction request 1844 from the user 1802, the express-session merchant system 1830 sends a transaction authorization request 1846 along with the temporary user ID created for the session to the funds facilitation system 1806 to determine whether the merchant should provide the transaction identified in the transaction request 1844. The funds facilitation system 1806 may then access the user system 1802 to determine if a valid express-session link cookie is stored on the user system 1802.
Upon successful identification of a valid express-session link cookie 1838, the funds facilitation system 1806 makes a determination as to whether the subsequent requested transaction should be authorized, for example based on whether the user's account contains sufficient funds. The funds facilitation system 1806 communicates the authorization decision to the express-session merchant system 1830 via a transaction authorization 1850, and the merchant system 1830 may then fulfill the subsequent transaction as appropriate, as shown at reference 1852.
After identifying a funds facilitation system user ID and authenticating the user, the user's account info 1912 may be accessed. Based on the account info 1912 and the transaction amount recited in the transaction authorization request 1904, a transaction decision 1914 is rendered by the transaction authorization decision engine 1906 and output to the merchant system. For example, if the transaction amount is less than a high-value threshold and a stored value account identified in the user's account info 1912 contains sufficient funds to pay the transaction amount, then the transaction authorization decision engine 1906 will send a transaction authorization as the transaction decision 1914. The funds facilitation system 1902 may then execute a transfer of funds from the user's stored value account to an account associated with the merchant.
Residing within computer system 2412 is a main processor 2424 which is comprised of a host central processing unit 2426 (CPU). Software applications 2427, such as the method of the present invention, may be loaded from, for example, disk 2428 (or other device), into main memory 2429 from which the software application 2427 may be run on the host CPU 2426. One or more processor 2424 operates in conjunction with a memory subsystem 2430. The memory subsystem 2430 is comprised of the main memory 2429, which may be comprised of a number of memory components, and a memory and bus controller 2432 which operates to control access to the main memory 2429. The main memory 2429 and controller 2432 may be in communication with a graphics system 2434 through a bus 2436. Other buses may exist, such as a PCI bus 2437, which interfaces to I/O devices or storage devices, such as disk 2428 or a CDROM, or to provide network access.
Embodiments of the subject matter and the functional operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer-readable medium for execution by, or to control the operation of, data processing apparatus.
The computer-readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter generating a machine-readable propagated signal, or a combination of one or more of them. The term “data processing apparatus” encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them, A propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.
A computer program (also known as a program, software, software application, script, or code), can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., on or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
The processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer need not have such devices. Moreover, a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio player, a Global Positioning System (GPS) receiver, to name just a few. Computer-readable media suitable for storing computer program instructions and data include all forms of nonvolatile memory, media, and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
To provide for interaction with a user, embodiments of the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) to LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any from, including acoustic, speech, or tactile input.
Embodiments of the subject matter described in this specification can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet.
The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
While this specification contains many specifics, these should not be construed as limitations on the scope of the invention or of what may be claimed, but rather as descriptions of features specific to particular embodiments of the invention. Certain features that are described in this specification in the context or separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed o a subcombination or variation of a subcombination.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.
Thus, particular embodiments of the invention have been described. Other embodiments are within the scope of the following claims. For example, the actions recited in the claims can be performed in a different order and still achieve desirable results.
This application is a continuation-in-part of U.S. patent application Ser. No. 11/870,799, titled “Method and System for Processing Micropayment Transactions,” filed on Oct. 11, 2007, which claims priority from U.S. Provisional Patent Application No. 60/829,057, filed on Oct. 11, 2006. This application also claims priority from U.S. Provisional Patent Application No. 61/256,095, titled “Systems and Methods for Brokered Authentication Express Seller Links,” filed on Oct. 29, 2009. The entirety of these priority applications are incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3652795 | Wolf et al. | Mar 1972 | A |
| 4321672 | Braun et al. | Mar 1982 | A |
| 4341951 | Benton | Jul 1982 | A |
| 4454414 | Benton | Jun 1984 | A |
| 4645873 | Chomet | Feb 1987 | A |
| 4713761 | Sharpe et al. | Dec 1987 | A |
| 4750119 | Cohen et al. | Jun 1988 | A |
| 4823264 | Deming | Apr 1989 | A |
| RE32985 | Nagata et al. | Jul 1989 | E |
| 4866611 | Cree et al. | Sep 1989 | A |
| 4941090 | McCarthy | Jul 1990 | A |
| 5010485 | Bigari | Apr 1991 | A |
| 5025372 | Burton et al. | Jun 1991 | A |
| 5132521 | Smith et al. | Jul 1992 | A |
| 5220501 | Lawlor et al. | Jun 1993 | A |
| 5231571 | D'Agostino | Jul 1993 | A |
| 5326960 | Tannenbaum | Jul 1994 | A |
| 5329589 | Fraser et al. | Jul 1994 | A |
| 5350906 | Brody et al. | Sep 1994 | A |
| 5351296 | Sullivan | Sep 1994 | A |
| 5383113 | Kight et al. | Jan 1995 | A |
| 5412730 | Jones | May 1995 | A |
| 5440634 | Jones et al. | Aug 1995 | A |
| 5450537 | Hirai et al. | Sep 1995 | A |
| 5453601 | Rosen | Sep 1995 | A |
| 5455407 | Rosen | Oct 1995 | A |
| 5537314 | Kanter | Jul 1996 | A |
| 5557516 | Hogan | Sep 1996 | A |
| 5581764 | Fitzgerald et al. | Dec 1996 | A |
| 5623547 | Jones et al. | Apr 1997 | A |
| 5640577 | Scharmer | Jun 1997 | A |
| 5659165 | Jennings et al. | Aug 1997 | A |
| 5692132 | Hogan | Nov 1997 | A |
| 5699528 | Hogan | Dec 1997 | A |
| 5717989 | Tozzoli et al. | Feb 1998 | A |
| 5742845 | Wagner | Apr 1998 | A |
| 5745574 | Muftic | Apr 1998 | A |
| 5790790 | Smith et al. | Aug 1998 | A |
| 5793302 | Stambler | Aug 1998 | A |
| 5794259 | Kikinis | Aug 1998 | A |
| 5799087 | Rosen | Aug 1998 | A |
| 5815657 | Williams et al. | Sep 1998 | A |
| 5832463 | Funk | Nov 1998 | A |
| 5850442 | Muftic | Dec 1998 | A |
| 5862325 | Reed et al. | Jan 1999 | A |
| 5873072 | Kight et al. | Feb 1999 | A |
| 5884288 | Chang et al. | Mar 1999 | A |
| 5884312 | Dustan et al. | Mar 1999 | A |
| 5890140 | Clark et al. | Mar 1999 | A |
| 5893120 | Nemes | Apr 1999 | A |
| 5903881 | Schrader et al. | May 1999 | A |
| 5920629 | Rosen | Jul 1999 | A |
| 5946667 | Tull et al. | Aug 1999 | A |
| 5953423 | Rosen | Sep 1999 | A |
| 5956391 | Melen et al. | Sep 1999 | A |
| 5956700 | Landry | Sep 1999 | A |
| 5960411 | Hartman et al. | Sep 1999 | A |
| 5963647 | Downing et al. | Oct 1999 | A |
| 5966696 | Giraud | Oct 1999 | A |
| 5966698 | Pollin | Oct 1999 | A |
| 5974148 | Stambler | Oct 1999 | A |
| 5974430 | Mutscher, III et al. | Oct 1999 | A |
| 6012041 | Brewer et al. | Jan 2000 | A |
| 6012044 | Maggioncalda et al. | Jan 2000 | A |
| 6012045 | Barzilai et al. | Jan 2000 | A |
| 6012048 | Gustin et al. | Jan 2000 | A |
| 6029150 | Kravitz | Feb 2000 | A |
| 6032133 | Hilt et al. | Feb 2000 | A |
| 6067621 | Yu et al. | May 2000 | A |
| 6088717 | Reed et al. | Jul 2000 | A |
| 6092053 | Boesch et al. | Jul 2000 | A |
| 6138107 | Elgamal | Oct 2000 | A |
| 6173272 | Thomas et al. | Jan 2001 | B1 |
| 6192407 | Smith et al. | Feb 2001 | B1 |
| 6226624 | Watson et al. | May 2001 | B1 |
| 6227447 | Campisano | May 2001 | B1 |
| 6289322 | Kitchen et al. | Sep 2001 | B1 |
| 6317729 | Camp et al. | Nov 2001 | B1 |
| 6327578 | Linchan | Dec 2001 | B1 |
| 6330550 | Brisebois et al. | Dec 2001 | B1 |
| 6332134 | Foster | Dec 2001 | B1 |
| 6341724 | Campisano | Jan 2002 | B2 |
| 6351739 | Egendorf | Feb 2002 | B1 |
| 6360205 | Iyengar et al. | Mar 2002 | B1 |
| 6421729 | Paltenghe et al. | Jul 2002 | B1 |
| 6424249 | Houvener | Jul 2002 | B1 |
| 6467684 | Fite et al. | Oct 2002 | B2 |
| 6487599 | Smith et al. | Nov 2002 | B1 |
| 6490601 | Markus et al. | Dec 2002 | B1 |
| 6499042 | Markus | Dec 2002 | B1 |
| 6547129 | Nichols et al. | Apr 2003 | B2 |
| 6609113 | O'Leary et al. | Aug 2003 | B1 |
| 6748367 | Lee | Jun 2004 | B1 |
| 6757710 | Reed | Jun 2004 | B2 |
| 6850996 | Wagner | Feb 2005 | B2 |
| 6871288 | Russikoff | Mar 2005 | B2 |
| 6873974 | Schutzer | Mar 2005 | B1 |
| 6907476 | Wagner | Jun 2005 | B2 |
| 6915271 | Meyer et al. | Jul 2005 | B1 |
| 6932268 | McCoy et al. | Aug 2005 | B1 |
| 6963843 | Takatsu et al. | Nov 2005 | B1 |
| 7006993 | Cheong et al. | Feb 2006 | B1 |
| 7062706 | Maxwell et al. | Jun 2006 | B2 |
| 7089208 | Levchin et al. | Aug 2006 | B1 |
| 7092913 | Cannon, Jr. | Aug 2006 | B2 |
| 7099850 | Mann, II et al. | Aug 2006 | B1 |
| 7103571 | Shigemi et al. | Sep 2006 | B2 |
| 7127427 | Casper | Oct 2006 | B1 |
| 7159180 | Ward | Jan 2007 | B2 |
| 7175074 | Mejias et al. | Feb 2007 | B2 |
| 7177838 | Ling | Feb 2007 | B1 |
| 7216292 | Snapper et al. | May 2007 | B1 |
| 7231372 | Prange et al. | Jun 2007 | B1 |
| 7249097 | Hutchison et al. | Jul 2007 | B2 |
| 7249099 | Ling | Jul 2007 | B2 |
| 7251656 | Keown et al. | Jul 2007 | B2 |
| 7254569 | Goodman et al. | Aug 2007 | B2 |
| 7257581 | Steele et al. | Aug 2007 | B1 |
| 7260724 | Dickinson et al. | Aug 2007 | B1 |
| 7324972 | Oliver et al. | Jan 2008 | B1 |
| 7328189 | Ling | Feb 2008 | B2 |
| 7334184 | Simons | Feb 2008 | B1 |
| 7337144 | Blinn et al. | Feb 2008 | B1 |
| 7337953 | Sgambati et al. | Mar 2008 | B2 |
| 7343351 | Bishop et al. | Mar 2008 | B1 |
| 7346577 | Williams et al. | Mar 2008 | B1 |
| 7346587 | Goldstein et al. | Mar 2008 | B2 |
| 7347361 | Lovett | Mar 2008 | B2 |
| 7350139 | Simons | Mar 2008 | B1 |
| RE40220 | Nichols et al. | Apr 2008 | E |
| 7366702 | David | Apr 2008 | B2 |
| 7366703 | Gray et al. | Apr 2008 | B2 |
| 7376621 | Ling | May 2008 | B1 |
| 7379919 | Hogan et al. | May 2008 | B2 |
| 7392536 | Jamieson et al. | Jun 2008 | B2 |
| 7395241 | Cook et al. | Jul 2008 | B1 |
| 7412420 | Holdsworth | Aug 2008 | B2 |
| 7415443 | Hobson et al. | Aug 2008 | B2 |
| 7426530 | Rosko et al. | Sep 2008 | B1 |
| 7437327 | Lam et al. | Oct 2008 | B2 |
| 7437757 | Holdsworth | Oct 2008 | B2 |
| 7444672 | Ellmore | Oct 2008 | B2 |
| 7447662 | Gibson | Nov 2008 | B2 |
| 7458507 | Fillinger et al. | Dec 2008 | B2 |
| 7461028 | Wronski, Jr. | Dec 2008 | B2 |
| 7461265 | Ellmore | Dec 2008 | B2 |
| 7461776 | Steiger, Jr. | Dec 2008 | B2 |
| 7463946 | Smith et al. | Dec 2008 | B2 |
| 7471818 | Price et al. | Dec 2008 | B1 |
| 7472171 | Miller et al. | Dec 2008 | B2 |
| 7483845 | Vetelainen | Jan 2009 | B2 |
| 7487127 | Weichert et al. | Feb 2009 | B2 |
| 7496952 | Edwards, Jr. et al. | Feb 2009 | B2 |
| 7500606 | Park et al. | Mar 2009 | B2 |
| 7502833 | Schaeck | Mar 2009 | B2 |
| 7512552 | Karas et al. | Mar 2009 | B2 |
| 7519560 | Lam et al. | Apr 2009 | B2 |
| 7523182 | Godwin | Apr 2009 | B2 |
| 7533063 | Kianian | May 2009 | B2 |
| 7533064 | Boesch | May 2009 | B1 |
| 7533828 | Ong | May 2009 | B2 |
| 7536354 | deGroeve et al. | May 2009 | B1 |
| 7540408 | Levine et al. | Jun 2009 | B2 |
| 7543738 | Saunders et al. | Jun 2009 | B1 |
| 7546272 | Loy | Jun 2009 | B2 |
| 7546275 | Herzberg et al. | Jun 2009 | B1 |
| 7548988 | Philyaw et al. | Jun 2009 | B2 |
| 7552467 | Lindsay | Jun 2009 | B2 |
| 7568631 | Gibbs et al. | Aug 2009 | B2 |
| 7571140 | Weichert et al. | Aug 2009 | B2 |
| 7577599 | Sanchez et al. | Aug 2009 | B2 |
| 7580857 | VanFleet et al. | Aug 2009 | B2 |
| 7580898 | Brown et al. | Aug 2009 | B2 |
| 7581257 | O'Hara | Aug 2009 | B1 |
| 7584153 | Brown et al. | Sep 2009 | B2 |
| 7590595 | Pessin | Sep 2009 | B2 |
| 7606760 | Hutchison et al. | Oct 2009 | B2 |
| 7610233 | Leong et al. | Oct 2009 | B1 |
| 7627523 | Symonds et al. | Dec 2009 | B1 |
| 7627531 | Breck et al. | Dec 2009 | B2 |
| 7657531 | Bisbee et al. | Feb 2010 | B2 |
| 7660779 | Goodman et al. | Feb 2010 | B2 |
| 7664699 | Powell | Feb 2010 | B1 |
| 7680679 | Patricelli et al. | Mar 2010 | B1 |
| 7694135 | Rowan et al. | Apr 2010 | B2 |
| 7698221 | Blinn et al. | Apr 2010 | B2 |
| 7702580 | Voth et al. | Apr 2010 | B1 |
| 7707105 | O'Neil | Apr 2010 | B2 |
| 7711621 | Huang et al. | May 2010 | B2 |
| 7716596 | Cao et al. | May 2010 | B2 |
| 7729925 | Maritzen et al. | Jun 2010 | B2 |
| 7761374 | Sahota et al. | Jul 2010 | B2 |
| 8402555 | Grecia | Mar 2013 | B2 |
| 8533860 | Grecia | Sep 2013 | B1 |
| 8887308 | Grecia | Nov 2014 | B2 |
| 20010014878 | Mitra et al. | Aug 2001 | A1 |
| 20010032182 | Kumar et al. | Oct 2001 | A1 |
| 20010039535 | Tsiounis et al. | Nov 2001 | A1 |
| 20010054148 | Hoornaert et al. | Dec 2001 | A1 |
| 20010056405 | Muyres et al. | Dec 2001 | A1 |
| 20020002495 | Ullman | Jan 2002 | A1 |
| 20020004772 | Templeton et al. | Jan 2002 | A1 |
| 20020016769 | Barbara et al. | Feb 2002 | A1 |
| 20020046341 | Kazaks et al. | Apr 2002 | A1 |
| 20020052841 | Guthrie et al. | May 2002 | A1 |
| 20020059141 | Davies et al. | May 2002 | A1 |
| 20020073027 | Hui et al. | Jun 2002 | A1 |
| 20020083011 | Kobayashi | Jun 2002 | A1 |
| 20020120582 | Elston et al. | Aug 2002 | A1 |
| 20020184147 | Boulger | Dec 2002 | A1 |
| 20030014633 | Gruber | Jan 2003 | A1 |
| 20030061111 | Dutta et al. | Mar 2003 | A1 |
| 20030074328 | Schiff et al. | Apr 2003 | A1 |
| 20030097331 | Cohen | May 2003 | A1 |
| 20030101134 | Liu et al. | May 2003 | A1 |
| 20030101137 | Wronski, Jr. | May 2003 | A1 |
| 20030110136 | Wells et al. | Jun 2003 | A1 |
| 20030135434 | Jain | Jul 2003 | A1 |
| 20030183689 | Swift et al. | Oct 2003 | A1 |
| 20030197061 | Din | Oct 2003 | A1 |
| 20030212642 | Weller et al. | Nov 2003 | A1 |
| 20030233334 | Smith | Dec 2003 | A1 |
| 20040029569 | Khan et al. | Feb 2004 | A1 |
| 20040039694 | Dunn et al. | Feb 2004 | A1 |
| 20040044621 | Huang et al. | Mar 2004 | A1 |
| 20040093303 | Picciallo | May 2004 | A1 |
| 20040103057 | Melbert et al. | May 2004 | A1 |
| 20040118914 | Smith et al. | Jun 2004 | A1 |
| 20040122770 | Craig et al. | Jun 2004 | A1 |
| 20040128508 | Wheeler et al. | Jul 2004 | A1 |
| 20040236692 | Sellen et al. | Nov 2004 | A1 |
| 20050005094 | Jamieson et al. | Jan 2005 | A1 |
| 20050086169 | Wells et al. | Apr 2005 | A1 |
| 20050097049 | Writer et al. | May 2005 | A1 |
| 20050131816 | Britto et al. | Jun 2005 | A1 |
| 20050147225 | Mallick et al. | Jul 2005 | A1 |
| 20050149455 | Bruesewitz et al. | Jul 2005 | A1 |
| 20050192896 | Hutchison et al. | Sep 2005 | A1 |
| 20050199709 | Linlor | Sep 2005 | A1 |
| 20050211763 | Sgambati et al. | Sep 2005 | A1 |
| 20050246293 | Ong | Nov 2005 | A1 |
| 20050278544 | Baxter | Dec 2005 | A1 |
| 20060080238 | Nielsen et al. | Apr 2006 | A1 |
| 20060089906 | Rowley | Apr 2006 | A1 |
| 20060131390 | Kim | Jun 2006 | A1 |
| 20060143122 | Sines et al. | Jun 2006 | A1 |
| 20060143690 | Lin et al. | Jun 2006 | A1 |
| 20060149671 | Nix et al. | Jul 2006 | A1 |
| 20060190300 | Drucker | Aug 2006 | A1 |
| 20060230265 | Krishna | Oct 2006 | A1 |
| 20060294005 | Drepak | Dec 2006 | A1 |
| 20070011093 | Tree | Jan 2007 | A1 |
| 20070136211 | Brown et al. | Jun 2007 | A1 |
| 20070198432 | Pitroda et al. | Aug 2007 | A1 |
| 20070214259 | Ahmed et al. | Sep 2007 | A1 |
| 20070255662 | Tumminaro | Nov 2007 | A1 |
| 20070260536 | Stone | Nov 2007 | A1 |
| 20070276944 | Samovar et al. | Nov 2007 | A1 |
| 20070288323 | Halevy | Dec 2007 | A1 |
| 20070291741 | Hwang | Dec 2007 | A1 |
| 20080015985 | Abhari et al. | Jan 2008 | A1 |
| 20080091600 | Egnatios et al. | Apr 2008 | A1 |
| 20080091619 | Perlman et al. | Apr 2008 | A1 |
| 20080110983 | Ashfield | May 2008 | A1 |
| 20080162295 | Bedier | Jul 2008 | A1 |
| 20080177796 | Eldering | Jul 2008 | A1 |
| 20080201769 | Finn | Aug 2008 | A1 |
| 20080208762 | Arthur et al. | Aug 2008 | A1 |
| 20080228653 | Holdsworth | Sep 2008 | A1 |
| 20080243666 | Rowan | Oct 2008 | A1 |
| 20080255991 | Wang | Oct 2008 | A1 |
| 20080288405 | John | Nov 2008 | A1 |
| 20080289022 | Chiu | Nov 2008 | A1 |
| 20080306877 | Mandeles et al. | Dec 2008 | A1 |
| 20090006646 | Duarte | Jan 2009 | A1 |
| 20090063345 | Erikson | Mar 2009 | A1 |
| 20090094148 | Gilder et al. | Apr 2009 | A1 |
| 20090121016 | Hammad et al. | May 2009 | A1 |
| 20090150265 | Keld | Jun 2009 | A1 |
| 20090157531 | Bui | Jun 2009 | A1 |
| 20090171778 | Powell | Jul 2009 | A1 |
| 20090171844 | Olliphant et al. | Jul 2009 | A1 |
| 20090173782 | Muscato | Jul 2009 | A1 |
| 20090182674 | Patel et al. | Jul 2009 | A1 |
| 20090182675 | Brody | Jul 2009 | A1 |
| 20090210347 | Sarcanin | Aug 2009 | A1 |
| 20090216676 | Mathur et al. | Aug 2009 | A1 |
| 20090259547 | Clopp | Oct 2009 | A1 |
| 20090292642 | Han | Nov 2009 | A1 |
| 20100318801 | Roberge et al. | Dec 2010 | A1 |
| Number | Date | Country |
|---|---|---|
| 640855 | Sep 1993 | AU |
| 07064911 | Mar 1995 | JP |
| 2002099852 | Apr 2002 | JP |
| 2004537088 | Dec 2004 | JP |
| 9613814 | May 1996 | WO |
| 0205224 | Jan 2002 | WO |
| 2002005224 | Jan 2002 | WO |
| 02079922 | Oct 2002 | WO |
| Entry |
|---|
| Pilon, Mary, “PayPal Makes a Bid for Student Banking”, downloaded from http://blogs.wsj.com/digits/2009/08/14/paypal-makes-a-bid-for-student-banking/tab/article, 3 pp. (Aug. 14, 2009). |
| Posting Payments, http://msdn.microsoft.com/en-us/library/aa480428(v=MSDN.10).aspx, 1998 (MSDN). |
| Apr. 2003 Report of the Auditor General of Canada, Apr. 2003 Report—Chapter 2 (Post Pay). |
| Young, Lee W., Jan. 3, 2011 International Search Report with Written Opinion from PCT Application No. PCT/US2010/054531 (9 pp.). |
| English Summary of Japanese Office Action for corresponding Japanese Application No. 2009-532582 dated Sep. 18, 2012 (6 pages). |
| Japanese Patent Office, Office Action for Japanese Application No. 2009-532582, dated Sep. 18, 2012 (6 pages). |
| European Patent Office, Extended European Search Report, dated May 4, 2011, for Application No. 07853964.0 (4 pages). |
| Ramachandran, Mani, Jul. 13, 2010 Office Action from Australian Patent Application No. 2007307688 (2 pages). |
| International Search Report for PCT/US07/81124, dated Sep. 5, 2008 (1 page). |
| International Search Report for PCT/US2001/021725, dated Aug. 29, 2002 (2 pages). |
| Petition for Inter Partes Review of U.S. Pat. No. 8,887,308 Challenging Claim 1 Under 35 U.S.C. §312 and 37 C.F.R. §42.104, dated Mar. 3, 2016, before the USPTO Patent Trial and Appeal Board, IPR 2016-00602, 58 pages. |
| Petition for Inter Partes Review of U.S. Pat. No. 8,402,555 Challenging Claims 1-26 Under 35 U.S.C. §312 and 37 C.F.R. §42.104, dated Mar. 22, 2016, before the USPTO Patent Trial and Appeal Board, IPR 2016-00789, 65 pages. |
| Petition for Inter Partes Review of U.S. Pat. No. 8,533,860 Challenging Claims 1-30 Under 35 U.S.C. §312 and 37 C.F.R. §42.104, dated Feb. 17, 2016, before the USPTO Patent Trial and Appeal Board, IPR 2016-00600, 65 pages. |
| Corrected Petition for Inter Partes Review of U.S. Pat. No. 8,533,860 Challenging Claims 1-30 Under 35 U.S.C. §312 and 37 C.F.R. §42.104, dated Mar. 14, 2016, before the USPTO Patent Trial and Appeal Board, IPR 2016-00600, 65 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20100257102 A1 | Oct 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60829057 | Oct 2006 | US | |
| 61256095 | Oct 2009 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11870799 | Oct 2007 | US |
| Child | 12778468 | US |
