US20130013509A1 - Method and system for processing micropayment transactions - Google Patents
Method and system for processing micropayment transactions Download PDFInfo
- Publication number
- US20130013509A1 US20130013509A1 US13/616,587 US201213616587A US2013013509A1 US 20130013509 A1 US20130013509 A1 US 20130013509A1 US 201213616587 A US201213616587 A US 201213616587A US 2013013509 A1 US2013013509 A1 US 2013013509A1
- Authority
- US
- United States
- Prior art keywords
- payer
- account
- payee
- micropayment
- purchase amount
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/22—Payment schemes or models
- G06Q20/29—Payment schemes or models characterised by micropayments
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/04—Payment circuits
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/12—Payment architectures specially adapted for electronic shopping systems
- G06Q20/123—Shopping for digital content
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3821—Electronic credentials
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/403—Solvency checks
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/403—Solvency checks
- G06Q20/4037—Remote solvency checks
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
- G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
Definitions
- micropayment transactions One problem with micropayment transactions is that the cost of obtaining payment from the user is high with respect to the purchase price.
- Current methods of obtaining payment include 1) repeated, single instance payments, 2) aggregating payments, 3) proprietary pre-paid accounts and 4) proprietary payment processing systems.
- payment aggregation does not lessen the cost of processing transactions for all consumers. While the per transaction cost of high-volume consumers is reduced, a low-volume consumer might only make one or two transactions within a billing period. As such, standard fee structures still make the cost of processing transactions for low-volume consumers prohibitive for the acquirer.
- payment aggregation causes the merchant to bear an increased risk for unprocessed transactions. For example, a consumer might only purchase a single item, but the merchant would not process the transaction until the end of the billing period, by which time the consumer's payment card may have exceeded its limit or have been compromised. The consumer can also lose granularity in his transaction statement because all transactions are aggregated into a single transaction.
- Proprietary pre-paid accounts are used for some pay-for-use services. Such accounts are typically used on a per-merchant basis. As such, the services are not generally compatible across business and/or geographic boundaries. Proprietary pre-paid accounts also require consumers to manage separate accounts for each merchant with which they are working and dedicate cash resources to each account.
- the present disclosure is directed to solving or overcoming one or more of the problems described above in the context of a broader, seamless payment solution in which micropayment is one of a plurality of payments facilitated. As such, much of the distinct functionality of the described methods and systems also has unique value to a broader range of payment types.
- a method of processing a micropayment transaction may include receiving a request for access to an item and a payer identifier from a payee website, requesting and verifying the payer password, determining whether one or more pre-defined account parameters pertaining to an account associated with the payer identifier are satisfied, if so, determining whether a required value for accessing the item is less than a pre-defined threshold, if so, determining whether an account associated with the payer identifier contains funds greater than or equal to the required value, and if so, permitting access to the item.
- a method of processing a transaction may include receiving a transaction value for a transaction, comparing the transaction value with a predefined threshold, processing the transaction using a first payment processing system if the transaction value is less than the predefined threshold, and processing the transaction using a second payment processing system if the transaction value is greater than the predefined threshold.
- the first payment processing system may include a micropayment processing system.
- a method of processing a transaction may include receiving information pertaining to a transaction, determining whether a payee has been previously verified by the micropayment processing system within a defined set of parameters, and, if so, processing the transaction without receiving payer-identifying information from the payer at the time of the current transaction.
- a method of processing a transaction may include receiving information pertaining to a transaction from the payee, information originally generated by the micropayment processing system and stored by the payee pertaining to the validity of the payer registration with the system, and verification of the payer's identity from the payer, and, if so, processing the transaction without receiving any payer-identifying information directly from the payer.
- FIG. 1 depicts a dataflow diagram for exemplary participants in a micropayment transaction according to an embodiment.
- FIG. 2 depicts a flow diagram for an exemplary process of processing a micropayment transaction according to an embodiment.
- FIG. 3 depicts a flow diagram for an exemplary settlement process for a micropayment processing system according to an embodiment.
- FIGS. 4A and 4B depict a flow diagram for an exemplary micropayment purchase from a payee website according to an embodiment.
- 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.
- FIG. 1 depicts a dataflow diagram for exemplary participants in a micropayment transaction according to an embodiment.
- the micropayment transaction processing system may include a payer 105 , a payee 110 , a micropayment processing server 115 , an acquirer bank 120 , an issuer bank 125 , a payer bank 130 , and a deposit access bank 135 to manage the float of value in the system.
- Exemplary communications between two parties are depicted by the lines in FIG. 1 and are described in more detail below in reference to FIGS. 2 and 3 .
- Communicating parties may communicate with each other via, for example, the Internet, and intranet and/or any other data network.
- Other communication methods such as a telephone, a PDA, a Blackberry, a gaming console, an interactive kiosk and the like may also be used within the scope of the present disclosure.
- FIG. 2 depicts a flow diagram for an exemplary process of processing a micropayment according to an embodiment.
- a payer 105 may shop at an online payee 110 and, for example, select 205 one or more goods and/or services for purchase from the payee. If the transaction is a micropayment transaction, a list of selectable payment methods may include an icon for a micropayment processing system 115 . The payer 105 may select the micropayment processing system 115 . The payer may initiate processing of the micropayment transaction by submitting 210 an identifier, such as, for example and without limitation, an email address, a “user ID,” a telephone number and/or any portion thereof.
- an identifier such as, for example and without limitation, an email address, a “user ID,” a telephone number and/or any portion thereof.
- a “cookie” or other persistent data located on the payer's network access device may relate to such an identifier. If the payer 105 has already established an account with the payment processing system 115 , the payer 105 may be directed to the system (or to a location within the payee's website 110 designed to receive information on behalf of the micropayment processing system) to provide 215 a password to authorize payment to the payee. As will be apparent to one with ordinary skill in the art, other authentication methods, such as, without limitation, biometric devices or cryptographic tokens, may be used to authenticate the payer to the micropayment processing system. If the payer has not already established an account with the micropayment processing system 115 , the payer 105 may be directed to a registration sub-system in order to initiate 220 an account setup routine.
- 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 .
- the micropayment processing system 115 may transfer 250 funds from any payer account to any payee account.
- 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 .
- FIG. 3 depicts a flow diagram for an exemplary settlement process for a micropayment processing system according to an embodiment.
- the acquirer bank 120 may deposit 305 funds into an account operated by the deposit access bank 135 .
- the deposit access bank 135 may manage the float (float occurs when an account in the system retains a positive balance of funds) and reconcile 310 payments for the micropayment processing system 115 .
- the deposit access bank 135 may settle 315 its account with each payee on, for example, a periodic basis. For example, the deposit access bank 135 may settle 315 its account with each payee on an hourly, daily, weekly or monthly basis. Other settlement periods may also be used within the scope of this disclosure.
- FIGS. 4A and 4B depict a flow diagram for an exemplary micropayment transaction performed on a payee website according to an embodiment.
- a payer may access the payee website via a user interface, such as a web browser.
- the user interface may display 402 an item or service for purchase to the payer with a message offering the option to pay for the item using a micropayment processing system and a selectable micropayment icon if the item or service has a value below a threshold.
- additional information may be displayed 402 , such as a link to an information page describing the micropayment processing system.
- the micropayment icon may be selected to initiate micropayment transaction processing.
- 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.
- 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.
- 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).
- 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.
- 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.
- the token may allow session-based authentication. In another embodiment, the token may be used without session-specific authentication.
- 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.
- 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.
- 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.
- 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.
- the micropayment transaction may fail 414 if the load transaction fails a second time. 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. It will be apparent to one of ordinary skill in the art that 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.
- 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.
- 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 .
- 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.
- 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.
- a determination as to the relationship between a transaction value and a threshold may be made 438 .
- 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 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.
- 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.
- 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.
- the payer may provide an alternate payment source.
- amounts to add to the account may be presented in a pull-down menu or similar method having pre-selected amounts.
- the screen may include a text entry field in which the payer may specify a particular amount.
- the micropayment processing system may submit 452 the load transaction for external authorization by the selected payment source. If 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.
- 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.
- the micropayment purchase process for such additional goods and/or services may skip to, for example, step 432 .
- 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.
- 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.
- the micropayment purchase process may skip to step 432 if the payee is a Trusted Merchant.
Abstract
Methods and systems for performing micropayment transactions over communication networks is provided. These methods and systems enable ubiquitous micropayments by providing a seamless payment solution in which micropayment is one of a plurality of payments facilitated. In an embodiment, the transaction value may be compared to a predefined threshold, and processed as a micropayment if said value is less than said threshold, and otherwise processed using a second processing system. In another embodiment, the transaction may be processed as a micropayment if the payee has previously been verified by the micropayment processing system. In a third embodiment, the transaction takes place using the payee's website.
Description
- This is a continuation of U.S. application Ser. No. 11/870,799, filed Oct. 11, 2007, which claims priority of Provisional Application No. 60/829,057, filed Oct. 11, 2006, all the above applications hereby incorporated by reference.
- As use of the Internet continues to expand, a fundamental change has occurred in the digital content marketplace. For example, the music industry has adopted a new digital form factor used by MP3 players and other digital music players. Pricing schemes for such content, buying behavior and the business model and priorities for the industry have drastically changed as a result of the digital music revolution. For example, digital music can often be purchased via the Internet on an individual song basis, where each song may cost approximately one dollar.
- Other industries are likewise re-evaluating future models in order to satisfy consumers and their anticipated purchasing behaviors. For example, software companies are evaluating new and more dynamic ways to package, distribute and price software, such as via the Internet. In many cases, using the Internet to distribute software to purchase subscriptions to Internet websites and the like will result in an increase in micropayment transactions (transactions having payments under approximately $5). It is projected that 30 billion micropayment transactions will take place globally by 2010.
- One problem with micropayment transactions is that the cost of obtaining payment from the user is high with respect to the purchase price. Current methods of obtaining payment include 1) repeated, single instance payments, 2) aggregating payments, 3) proprietary pre-paid accounts and 4) proprietary payment processing systems.
- Repeated, single instance payments occur when, for example, a credit card is charged once for each micropayment transaction. Acquirers cannot viably provide such a service to merchants because the cost of processing a transaction is too high relative to the transaction amount and standard fee structures. On the other hand, consumers are required to present too much data (i.e., full card details) relative to the size of the payment. Moreover, consumers can have concern regarding control over their data.
- Some merchants aggregate payments in an attempt to overcome these deficiencies. However, payment aggregation does not lessen the cost of processing transactions for all consumers. While the per transaction cost of high-volume consumers is reduced, a low-volume consumer might only make one or two transactions within a billing period. As such, standard fee structures still make the cost of processing transactions for low-volume consumers prohibitive for the acquirer. In addition, payment aggregation causes the merchant to bear an increased risk for unprocessed transactions. For example, a consumer might only purchase a single item, but the merchant would not process the transaction until the end of the billing period, by which time the consumer's payment card may have exceeded its limit or have been compromised. The consumer can also lose granularity in his transaction statement because all transactions are aggregated into a single transaction.
- Proprietary pre-paid accounts are used for some pay-for-use services. Such accounts are typically used on a per-merchant basis. As such, the services are not generally compatible across business and/or geographic boundaries. Proprietary pre-paid accounts also require consumers to manage separate accounts for each merchant with which they are working and dedicate cash resources to each account.
- Proprietary payment processing systems, in which each merchant's contract with a third party system to process payments, disadvantage consumers in substantially the same way as proprietary pre-paid accounts. In addition, merchants are required to make significant investments in infrastructure in order to develop such systems.
- It would be desirable to have methods and systems for enabling ubiquitous micropayments in order to expand online purchasing opportunities for merchants and consumers while also being commercially viable for the facilitating entities, e.g. issuers and acquirers.
- The present disclosure is directed to solving or overcoming one or more of the problems described above in the context of a broader, seamless payment solution in which micropayment is one of a plurality of payments facilitated. As such, much of the distinct functionality of the described methods and systems also has unique value to a broader range of payment types.
- Before the present methods are described, it is to be understood that this invention is not limited to the particular methodologies or protocols described, as these may vary. It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to limit the scope of the present disclosure, which will be limited only by the appended claims.
- It must be noted that as used herein and in the appended claims, the singular forms “a,” “an,” and “the” include plural reference unless the context clearly dictates otherwise. Thus, for example, reference to a “transaction” is a reference to one or more transactions and equivalents thereof known to those skilled in the art, and so forth. Unless defined otherwise, all technical and scientific terms used herein have the same meanings as commonly understood by one of ordinary skill in the art. Although any methods and materials similar or equivalent to those described herein can be used in the practice or testing of the present invention, the preferred methods, devices, and materials are now described. All publications mentioned herein are incorporated herein by reference. Nothing herein is to be construed as an admission that the invention is not entitled to antedate such disclosure by virtue of prior invention.
- In an embodiment, a method of processing a micropayment transaction may include receiving a request for access to an item and a payer identifier from a payee website, requesting and verifying the payer password, determining whether one or more pre-defined account parameters pertaining to an account associated with the payer identifier are satisfied, if so, determining whether a required value for accessing the item is less than a pre-defined threshold, if so, determining whether an account associated with the payer identifier contains funds greater than or equal to the required value, and if so, permitting access to the item.
- In an embodiment, a method of processing a transaction may include receiving a transaction value for a transaction, comparing the transaction value with a predefined threshold, processing the transaction using a first payment processing system if the transaction value is less than the predefined threshold, and processing the transaction using a second payment processing system if the transaction value is greater than the predefined threshold. The first payment processing system may include a micropayment processing system.
- In an embodiment, a method of processing a transaction may include receiving information pertaining to a transaction, determining whether a payee has been previously verified by the micropayment processing system within a defined set of parameters, and, if so, processing the transaction without receiving payer-identifying information from the payer at the time of the current transaction.
- In an embodiment, a method of processing a transaction may include receiving information pertaining to a transaction from the payee, information originally generated by the micropayment processing system and stored by the payee pertaining to the validity of the payer registration with the system, and verification of the payer's identity from the payer, and, if so, processing the transaction without receiving any payer-identifying information directly from the payer.
- Aspects, features, benefits and advantages of the present invention will be apparent with regard to the following description and accompanying drawings, of which:
-
FIG. 1 depicts a dataflow diagram for exemplary participants in a micropayment transaction according to an embodiment. -
FIG. 2 depicts a flow diagram for an exemplary process of processing a micropayment transaction according to an embodiment. -
FIG. 3 depicts a flow diagram for an exemplary settlement process for a micropayment processing system according to an embodiment. -
FIGS. 4A and 4B depict a flow diagram for an exemplary micropayment purchase from a payee website according to an embodiment. - 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.
-
FIG. 1 depicts a dataflow diagram for exemplary participants in a micropayment transaction according to an embodiment. As shown inFIG. 1 , the micropayment transaction processing system may include apayer 105, apayee 110, amicropayment processing server 115, anacquirer bank 120, anissuer bank 125, apayer bank 130, and adeposit access bank 135 to manage the float of value in the system. Exemplary communications between two parties are depicted by the lines inFIG. 1 and are described in more detail below in reference toFIGS. 2 and 3 . Communicating parties may communicate with each other via, for example, the Internet, and intranet and/or any other data network. Other communication methods, such as a telephone, a PDA, a Blackberry, a gaming console, an interactive kiosk and the like may also be used within the scope of the present disclosure. -
FIG. 2 depicts a flow diagram for an exemplary process of processing a micropayment according to an embodiment. As shown inFIG. 2 , apayer 105 may shop at anonline payee 110 and, for example, select 205 one or more goods and/or services for purchase from the payee. If the transaction is a micropayment transaction, a list of selectable payment methods may include an icon for amicropayment processing system 115. Thepayer 105 may select themicropayment processing system 115. The payer may initiate processing of the micropayment transaction by submitting 210 an identifier, such as, for example and without limitation, an email address, a “user ID,” a telephone number and/or any portion thereof. In an embodiment, a “cookie” or other persistent data located on the payer's network access device may relate to such an identifier. If thepayer 105 has already established an account with thepayment processing system 115, thepayer 105 may be directed to the system (or to a location within the payee'swebsite 110 designed to receive information on behalf of the micropayment processing system) to provide 215 a password to authorize payment to the payee. As will be apparent to one with ordinary skill in the art, other authentication methods, such as, without limitation, biometric devices or cryptographic tokens, may be used to authenticate the payer to the micropayment processing system. If the payer has not already established an account with themicropayment processing system 115, thepayer 105 may be directed to a registration sub-system in order to initiate 220 an account setup routine. - 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 themicropayment 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. Themicropayment processing system 115 may transmit 230 the transaction information supplied by thepayer 105 to theacquirer bank 120. Theacquirer bank 120 may facilitate an authorization procedure with a direct debit account or the card acquirer. If thepayer 105 is authorized, theacquirer bank 120 may confirm 235 the load of value to themicropayment processing system 115, which forwards 240 the confirmation to the payer. Otherwise, the micropayment process may terminate 245. In an alternate embodiment, thepayer 105 may be provided with one or more additional opportunities to provide proper authorizing information to themicropayment 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. Themicropayment processing system 115 may then notify 255 thepayer 105 and thepayee 110 that the transaction has successfully completed. Thepayer 105 may then be returned 260 to thepayee website 110. -
FIG. 3 depicts a flow diagram for an exemplary settlement process for a micropayment processing system according to an embodiment. As shown inFIG. 3 , theacquirer bank 120 may deposit 305 funds into an account operated by thedeposit access bank 135. Thedeposit access bank 135 may manage the float (float occurs when an account in the system retains a positive balance of funds) and reconcile 310 payments for themicropayment processing system 115. Thedeposit access bank 135 may settle 315 its account with each payee on, for example, a periodic basis. For example, thedeposit access bank 135 may settle 315 its account with each payee on an hourly, daily, weekly or monthly basis. Other settlement periods may also be used within the scope of this disclosure. -
FIGS. 4A and 4B depict a flow diagram for an exemplary micropayment transaction performed on a payee website according to an embodiment. As shown inFIGS. 4A and 4B , a payer may access the payee website via a user interface, such as a web browser. The user interface may display 402 an item or service for purchase to the payer with a message offering the option to pay for the item using a micropayment processing system and a selectable micropayment icon if the item or service has a value below a threshold. In an embodiment, additional information may be displayed 402, such as a link to an information page describing the micropayment processing system. In an embodiment, the micropayment icon may be selected to initiate micropayment transaction processing. - 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. It will be apparent to one of ordinary skill in the art that 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 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 selected payment source. If 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. - It will be appreciated that various of the above-disclosed and other features and functions, or alternatives thereof, may be desirably combined into many other different systems or applications. It will also be appreciated that various presently unforeseen or unanticipated alternatives, modifications, variations or improvements therein may be subsequently made by those skilled in the art which are also intended to be encompassed by the disclosed embodiments.
Claims (20)
1. A method comprising:
receiving, by a website associated with a payee, from a user interface associated with a payer, a request to make a purchase with a purchase amount;
comparing the purchase amount with a predefined threshold;
displaying, by the website on the user interface, different payment source options from which a selection is to be made, wherein if the purchase amount is less than the threshold then the payment source options include a micropayment option, and if the purchase amount is not less than the threshold then the payment source options do not include a micropayment option, the micropayment option relating to the purchase amount being transferred from a payer account associated with the payer and managed by a micropayment processing system to a payee account associated with the payee;
receiving, by the website from the user interface, a selection of the micropayment option; and
in response to receiving the selection of the micropayment option, sending a payment authorization request to the micropayment processing system.
2. The method of claim 1 further comprising:
receiving, by the micropayment processing system, the payment authorization request; and
transferring, by the micropayment processing system, the purchase amount from a prefunded payer account associated with the payer to a payee account associated with the payee.
3. The method of claim 2 further comprising the following steps performed by the micropayment processing system:
determining whether the payment authorization request satisfies at least one predefined account parameter that is specific to the payer account;
determining whether the purchase amount is less than the predefined threshold; and
approving the payment authorization request based on the payment authorization request satisfying the at least one predefined account parameter and the purchase amount being less than the predefined threshold.
4. The method of claim 3 wherein the at least one account parameter is selected from a payee payment limit, a total payment limit, a time limitation, and whether the payee has been blocked.
5. The method of claim 3 wherein the payer is a secondary payer, the account is associated with a primary payer other than the secondary payer, and the at least one parameter applies only to the secondary payer.
6. The method of claim 5 wherein the primary payer is a parent or guardian and the secondary payer is a child.
7. The method of claim 2 further comprising the following steps performed by the micropayment processing system:
determining whether the payer account has sufficient funds to pay the purchase amount;
in response to determining that the payer account does not have sufficient funds to pay the purchase amount:
displaying on the user interface an option to add funds to the account from a funding source,
receiving, from the user interface, a selection of the option to add funds to the account from the funding source,
receiving funds from the funding source so that the payer account will have sufficient funds to pay for the purchase, and
transferring the purchase amount from the payer account to the payee account.
8. The method of claim 7 wherein the funding source is a credit card or a debit card.
9. The method of claim 7 wherein the funding source is a bank account.
10. The method of claim 1 wherein the predefined threshold is associated with the payer.
11. The method of claim 1 wherein the predefined threshold is associated with the payee.
12. A method performed by a micropayment processing system, comprising:
receiving a payment authorization request from a website associated with a payee, the payment authorization request relating to a purchase requested by a payer using a user interface, and the payment authorization request requesting that the micropayment processing server transfer a purchase amount from a payer account associated with the payer to a payee account associated with the payee to pay for the purchase,
determining whether the payer account has sufficient funds to pay the purchase amount;
if the payer account does not have sufficient funds to pay the purchase amount, then
displaying on the user interface an option to add funds to the payer account from a funding source,
receiving, from the user interface, a selection of the option to add funds to the account from the funding source,
receiving the added funds from the funding source, and
transferring the purchase amount from the payer account to a payee account associated with the payee to pay for the purchase; and
if the payer account does have sufficient funds to pay the purchase amount, then
transferring the purchase amount from the payer account to the payee account to pay for the purchase without displaying the option to add funds to the payer account from the funding source.
13. The method of claim 12 wherein the funding source is a credit card or a debit card.
14. The method of claim 12 wherein the funding source is a bank account.
15. A transaction processing system comprising:
a website associated with a payee, the website configured to
receive, from a user interface associated with a payer, a request to make a purchase with a purchase amount,
compare the purchase amount with a predefined threshold,
display, on the user interface, different payment source options from which a selection is to be made, wherein if the purchase amount is less than the threshold then the payment source options include a micropayment option, and if the purchase amount is not less than the threshold then the payment source options do not include a micropayment option,
receive, from the user interface, a selection of the micropayment option; and
in response to receiving the selection of the micropayment option, send a payment authorization request to a micropayment processing system to transfer the purchase amount from a payer account associated with the payer to a payee account associated with the payee.
16. The transaction processing system of claim 15 further comprising:
the micropayment processing system, which includes a micropayment processing server configured to
receive the payment authorization request, and
transfer the purchase amount from the payer account to the payee account.
17. The transaction processing system of claim 16 wherein the micropayment processing server is further configured to
determine whether the payment authorization request satisfies at least one predefined account parameter that is specific to a prefunded payer account associated with the payer identifier,
determine whether the purchase amount is less than the predefined threshold,
determine whether the payer account has sufficient funds to pay the purchase amount, and
approve the payment authorization request based on the payment authorization request satisfying the at least one predefined account parameter, the purchase amount being less than the predefined threshold, and the payer account having sufficient funds to pay the purchase amount.
18. A micropayment processing system comprising:
a micropayment processing server configured to
receive a payment authorization request from a website associated with a payee, the payment authorization request relating to a purchase requested by a payer using a user interface, and the payment authorization request requesting that the micropayment processing server transfer a purchase amount from a payer account associated with the payer to a payee account associated with the payee to pay for the purchase,
determine whether the payer account has sufficient funds to pay the purchase amount;
if the payer account does not have sufficient funds, then
display, on a user interface associated with the payer, an option to add funds to the payer account from a funding source,
receive, from the user interface, a selection of the option to add funds to the account from the funding source,
receive the added funds from the funding source, and
transfer the purchase amount from the payer account to the payee account; and
if the payer account does have sufficient funds to pay the purchase amount, then
transfer the purchase amount from the payer account to the payee account to pay for the purchase without displaying the option to add funds to the payer account from the funding source.
19. The micropayment processing system of claim 18 wherein the funding source is a credit card or a debit card.
20. The micropayment processing system of claim 18 wherein the funding source is a bank account.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/616,587 US20130013509A1 (en) | 2006-10-11 | 2012-09-14 | Method and system for processing micropayment transactions |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US82905706P | 2006-10-11 | 2006-10-11 | |
US11/870,799 US8335745B2 (en) | 2006-10-11 | 2007-10-11 | Method and system for processing micropayment transactions |
US13/616,587 US20130013509A1 (en) | 2006-10-11 | 2012-09-14 | Method and system for processing micropayment transactions |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/870,799 Continuation US8335745B2 (en) | 2006-10-11 | 2007-10-11 | Method and system for processing micropayment transactions |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130013509A1 true US20130013509A1 (en) | 2013-01-10 |
Family
ID=39283630
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/870,799 Active 2029-09-29 US8335745B2 (en) | 2006-10-11 | 2007-10-11 | Method and system for processing micropayment transactions |
US13/616,587 Abandoned US20130013509A1 (en) | 2006-10-11 | 2012-09-14 | Method and system for processing micropayment transactions |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/870,799 Active 2029-09-29 US8335745B2 (en) | 2006-10-11 | 2007-10-11 | Method and system for processing micropayment transactions |
Country Status (10)
Country | Link |
---|---|
US (2) | US8335745B2 (en) |
EP (1) | EP2074726A4 (en) |
JP (1) | JP2010507151A (en) |
KR (1) | KR20090063254A (en) |
CN (1) | CN101554005A (en) |
AU (1) | AU2007307688B2 (en) |
BR (1) | BRPI0715571A2 (en) |
CA (1) | CA2666262A1 (en) |
TW (1) | TW200834446A (en) |
WO (1) | WO2008046012A2 (en) |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9443268B1 (en) | 2013-08-16 | 2016-09-13 | Consumerinfo.Com, Inc. | Bill payment and reporting |
US11049101B2 (en) * | 2017-03-21 | 2021-06-29 | Visa International Service Association | Secure remote transaction framework |
US11321707B2 (en) | 2016-03-22 | 2022-05-03 | Visa International Service Association | Adaptable authentication processing |
US11551190B1 (en) | 2019-06-03 | 2023-01-10 | Wells Fargo Bank, N.A. | Instant network cash transfer at point of sale |
US11928668B1 (en) | 2014-04-30 | 2024-03-12 | Wells Fargo Bank, N.A. | Mobile wallet using tokenized card systems and methods |
US11935045B1 (en) | 2014-04-30 | 2024-03-19 | Wells Fargo Bank, N.A. | Mobile wallet account provisioning systems and methods |
Families Citing this family (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8874477B2 (en) | 2005-10-04 | 2014-10-28 | Steven Mark Hoffberg | Multifactorial optimization system and method |
US20100223184A1 (en) * | 2006-10-11 | 2010-09-02 | Visa International Service Association | Sponsored Accounts For Computer-Implemented Payment System |
US10068220B2 (en) * | 2006-10-11 | 2018-09-04 | Visa International Service Association | Systems and methods for brokered authentication express seller links |
AU2007307688B2 (en) | 2006-10-11 | 2011-06-23 | Visa International Service Association | Method and system for processing micropayment transactions |
US7866551B2 (en) * | 2007-02-15 | 2011-01-11 | Visa U.S.A. Inc. | Dynamic payment device characteristics |
US20090070262A1 (en) * | 2007-09-12 | 2009-03-12 | Ebay Inc. | Ach-enabled micropayments |
US10008067B2 (en) | 2008-06-16 | 2018-06-26 | Visa U.S.A. Inc. | System and method for authorizing financial transactions with online merchants |
US8332314B2 (en) * | 2008-11-05 | 2012-12-11 | Kent Griffin | Text authorization for mobile payments |
US7827108B2 (en) * | 2008-11-21 | 2010-11-02 | Visa U.S.A. Inc. | System and method of validating a relationship between a user and a user account at a financial institution |
US20100293017A1 (en) * | 2009-05-18 | 2010-11-18 | Contenture, Inc. | Micropayment and website content control systems and methods |
US20220084103A1 (en) * | 2009-07-29 | 2022-03-17 | Paypal, Inc. | No authentication payment and seamless authentication |
US8280788B2 (en) * | 2009-10-29 | 2012-10-02 | Visa International Service Association | Peer-to-peer and group financial management systems and methods |
US8676639B2 (en) | 2009-10-29 | 2014-03-18 | Visa International Service Association | System and method for promotion processing and authorization |
US20110106674A1 (en) * | 2009-10-29 | 2011-05-05 | Jeffrey William Perlman | Optimizing Transaction Scenarios With Automated Decision Making |
US20110137748A1 (en) * | 2009-12-09 | 2011-06-09 | Yigal Baher | Systems and Methods for Virtual Credit Card Transactions |
US8281372B1 (en) * | 2009-12-18 | 2012-10-02 | Joel Vidal | Device, system, and method of accessing electronic mail |
US20130024300A1 (en) * | 2011-07-21 | 2013-01-24 | Bank Of America Corporation | Multi-stage filtering for fraud detection using geo-positioning data |
US8712914B2 (en) * | 2012-02-23 | 2014-04-29 | Mastercard International Incorporated | Method and system for facilitating micropayments in a financial transaction system |
US8639619B1 (en) | 2012-07-13 | 2014-01-28 | Scvngr, Inc. | Secure payment method and system |
US20140025571A1 (en) * | 2012-07-23 | 2014-01-23 | Its, Inc. | System and method for dual message consumer authentication value-based eft transactions |
US20140279554A1 (en) * | 2013-03-12 | 2014-09-18 | Seth Priebatsch | Distributed authenticity verification for consumer payment transactions |
US9081672B1 (en) | 2013-05-30 | 2015-07-14 | Richard Michael Nemes | Methods and apparatus for information storage and retrieval using a caching technique with external-chain hashing and dynamic resource-dependent data shedding |
US10489852B2 (en) * | 2013-07-02 | 2019-11-26 | Yodlee, Inc. | Financial account authentication |
US8770478B2 (en) | 2013-07-11 | 2014-07-08 | Scvngr, Inc. | Payment processing with automatic no-touch mode selection |
CN104574046B (en) * | 2013-10-29 | 2017-03-08 | 腾讯科技(深圳)有限公司 | A kind of payment system and the management method of pair pre- charge information |
SG10201500276VA (en) * | 2015-01-14 | 2016-08-30 | Mastercard Asia Pacific Pte Ltd | Method and system for making a secure payment transaction |
US10853592B2 (en) | 2015-02-13 | 2020-12-01 | Yoti Holding Limited | Digital identity system |
US10692085B2 (en) * | 2015-02-13 | 2020-06-23 | Yoti Holding Limited | Secure electronic payment |
US10594484B2 (en) | 2015-02-13 | 2020-03-17 | Yoti Holding Limited | Digital identity system |
CN104715373B (en) * | 2015-04-01 | 2018-04-20 | 京东方科技集团股份有限公司 | A kind of payment devices and method |
WO2017070469A1 (en) * | 2015-10-22 | 2017-04-27 | Align Commerce Corporation | System and method for payment processing using crypto currencies |
CN106503974B (en) * | 2017-01-04 | 2020-03-17 | 泰康保险集团股份有限公司 | Transaction data processing method and device |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030061111A1 (en) * | 2001-09-26 | 2003-03-27 | International Business Machines Corporation | Method and system for parent controlled e-commerce |
US20040029569A1 (en) * | 2001-12-26 | 2004-02-12 | Vivotech, Inc. | Micropayment financial transaction process utilizing wireless network processing |
US7337144B1 (en) * | 2000-09-28 | 2008-02-26 | Microsoft Corporation | Method and system for restricting the usage of payment accounts |
Family Cites Families (262)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3652795A (en) | 1970-11-25 | 1972-03-28 | Electrospace Corp | Telephone transaction system |
US4321672A (en) | 1979-11-26 | 1982-03-23 | Braun Edward L | Financial data processing system |
US4341951A (en) | 1980-07-02 | 1982-07-27 | Benton William M | Electronic funds transfer and voucher issue system |
US4454414A (en) | 1982-06-16 | 1984-06-12 | Vericard Corporation | Funds transfer system using optically coupled, portable modules |
USRE32985E (en) | 1982-07-09 | 1989-07-11 | Omron Tateisi Electronics Co. | Credit transaction processing system |
US4645873A (en) | 1985-01-23 | 1987-02-24 | Telecue Systems | Transactional telecommunication system |
US4713761A (en) | 1985-07-18 | 1987-12-15 | Pitney Bowes, Inc. | System for centralized processing of accounting and payment functions |
US4823264A (en) | 1986-05-27 | 1989-04-18 | Deming Gilbert R | Electronic funds transfer system |
US4750119A (en) | 1986-10-10 | 1988-06-07 | Tradevest, Inc. | Purchasing system with rebate feature |
US4866611A (en) | 1987-01-29 | 1989-09-12 | International Business Machines Corporation | Method for automatically reconciling entries on two copies of independently maintained electronic calendars |
US5025372A (en) | 1987-09-17 | 1991-06-18 | Meridian Enterprises, Inc. | System and method for administration of incentive award program through use of credit |
US4941090A (en) | 1989-01-27 | 1990-07-10 | Mccarthy Patrick D | Centralized consumer cash value accumulation system for multiple merchants |
US5010485A (en) | 1989-01-31 | 1991-04-23 | Jbh Ventures | Apparatus, system and method for creating credit vouchers usable at point of purchase stations |
US6044205A (en) | 1996-02-29 | 2000-03-28 | Intermind Corporation | Communications system for transferring information between memories according to processes transferred with the information |
US5132521A (en) | 1989-09-15 | 1992-07-21 | Smith Charles M | System and method for acquisition and encoding of ATM card data |
US5412730A (en) | 1989-10-06 | 1995-05-02 | Telequip Corporation | Encrypted data transmission system employing means for randomly altering the encryption keys |
US5220501A (en) | 1989-12-08 | 1993-06-15 | Online Resources, Ltd. | Method and system for remote delivery of retail banking services |
JPH03180968A (en) | 1989-12-08 | 1991-08-06 | Hitachi Ltd | Data base retrieving method and formated document outputting method using the retrieving method |
US5623547A (en) | 1990-04-12 | 1997-04-22 | Jonhig Limited | Value transfer system |
US5231571A (en) | 1990-08-14 | 1993-07-27 | Personal Financial Assistant, Inc. | Personal financial assistant computer method |
CA2059078C (en) | 1991-02-27 | 1995-10-03 | Alexander G. Fraser | Mediation of transactions by a communications system |
US6289322B1 (en) | 1998-03-03 | 2001-09-11 | Checkfree Corporation | Electronic bill processing |
US5383113A (en) | 1991-07-25 | 1995-01-17 | Checkfree Corporation | System and method for electronically providing customer services including payment of bills, financial analysis and loans |
GB9121995D0 (en) | 1991-10-16 | 1991-11-27 | Jonhig Ltd | Value transfer system |
US5453601A (en) | 1991-11-15 | 1995-09-26 | Citibank, N.A. | Electronic-monetary system |
US5640577A (en) | 1991-12-30 | 1997-06-17 | Davox Corporation | Data processing system with automated at least partial forms completion |
US5966698A (en) | 1992-10-15 | 1999-10-12 | Pollin; Robert E. | Automated payment system and method |
US5267314A (en) | 1992-11-17 | 1993-11-30 | Leon Stambler | Secure transaction system and method utilized therein |
US5326960A (en) | 1992-11-25 | 1994-07-05 | Tannenbaum David H | Currency transfer system and method |
US5350906A (en) | 1992-11-25 | 1994-09-27 | Brody Bill E | Currency transfer system and method using fixed limit cards |
US5351296A (en) | 1993-03-29 | 1994-09-27 | Niobrara Research & Development Corporation | Financial transmission system |
WO1994025913A2 (en) | 1993-04-30 | 1994-11-10 | Novadigm, Inc. | Method and apparatus for enterprise desktop management |
JPH0764911A (en) * | 1993-08-31 | 1995-03-10 | Sharp Corp | Individual authentication system |
US5465206B1 (en) | 1993-11-01 | 1998-04-21 | Visa Int Service Ass | Electronic bill pay system |
US5557516A (en) | 1994-02-04 | 1996-09-17 | Mastercard International | System and method for conducting cashless transactions |
AU2241195A (en) | 1994-04-06 | 1995-10-30 | Morgan Stanley Group Inc. | Data processing system and method for financial debt instruments |
US5537314A (en) | 1994-04-18 | 1996-07-16 | First Marketrust Intl. | Referral recognition system for an incentive award program |
US5799087A (en) | 1994-04-28 | 1998-08-25 | Citibank, N.A. | Electronic-monetary system |
US5649117A (en) | 1994-06-03 | 1997-07-15 | Midwest Payment Systems | System and method for paying bills and other obligations including selective payor and payee controls |
US5717989A (en) | 1994-10-13 | 1998-02-10 | Full Service Trade System Ltd. | Full service trade system |
US6058378A (en) | 1995-02-22 | 2000-05-02 | Citibank, N.A. | Electronic delivery system and method for integrating global financial services |
US6424249B1 (en) | 1995-05-08 | 2002-07-23 | Image Data, Llc | Positive identity verification system and method including biometric user authentication |
US5692132A (en) | 1995-06-07 | 1997-11-25 | Mastercard International, Inc. | System and method for conducting cashless transactions on a computer network |
US5742845A (en) | 1995-06-22 | 1998-04-21 | Datascape, Inc. | System for extending present open network communication protocols to communicate with non-standard I/O devices directly coupled to an open network |
US5794221A (en) | 1995-07-07 | 1998-08-11 | Egendorf; Andrew | Internet billing method |
US5659165A (en) | 1995-07-24 | 1997-08-19 | Citibank. N.A. | Customer-directed, automated process for transferring funds between accounts via a communications network |
US5699528A (en) | 1995-10-31 | 1997-12-16 | Mastercard International, Inc. | System and method for bill delivery and payment over a communications network |
US5745574A (en) | 1995-12-15 | 1998-04-28 | Entegrity Solutions Corporation | Security infrastructure for electronic transactions |
US6138107A (en) * | 1996-01-04 | 2000-10-24 | Netscape Communications Corporation | Method and apparatus for providing electronic accounts over a public network |
US5956391A (en) | 1996-02-09 | 1999-09-21 | Telefonaktiebolaget Lm Ericsson | Billing in the internet |
US5862325A (en) | 1996-02-29 | 1999-01-19 | Intermind Corporation | Computer-based communication system and method using metadata defining a control structure |
GB9604459D0 (en) | 1996-03-01 | 1996-05-01 | Isr Logistics Ltd | An apparatus for the control of inventory |
US5850442A (en) | 1996-03-26 | 1998-12-15 | Entegrity Solutions Corporation | Secure world wide electronic commerce over an open network |
US5832463A (en) | 1996-03-28 | 1998-11-03 | Electronic Data Systems Corporation | Automated system and method for checkless check transaction |
US6044360A (en) | 1996-04-16 | 2000-03-28 | Picciallo; Michael J. | Third party credit card |
US5815657A (en) | 1996-04-26 | 1998-09-29 | Verifone, Inc. | System, method and article of manufacture for network electronic authorization utilizing an authorization instrument |
US7167924B1 (en) | 1996-06-10 | 2007-01-23 | Diebold, Incorporated | Financial transaction processing system and method |
US5884288A (en) | 1996-07-01 | 1999-03-16 | Sun Microsystems, Inc. | Method and system for electronic bill payment |
US5794259A (en) | 1996-07-25 | 1998-08-11 | Lextron Systems, Inc | Apparatus and methods to enhance web browsing on the internet |
US6029150A (en) | 1996-10-04 | 2000-02-22 | Certco, Llc | Payment and transactions in electronic commerce system |
KR100213188B1 (en) | 1996-10-05 | 1999-08-02 | 윤종용 | Apparatus and method for user authentication |
US5790790A (en) | 1996-10-24 | 1998-08-04 | Tumbleweed Software Corporation | Electronic document delivery system in which notification of said electronic document is sent to a recipient thereof |
US6192407B1 (en) | 1996-10-24 | 2001-02-20 | Tumbleweed Communications Corp. | Private, trackable URLs for directed document delivery |
USRE40220E1 (en) | 1996-12-31 | 2008-04-08 | Lml Patent Corp. | Check writing point of sale system |
US6164528A (en) | 1996-12-31 | 2000-12-26 | Chequemark Patent, Inc. | Check writing point of sale system |
US5893120A (en) | 1997-01-02 | 1999-04-06 | Nemes; Richard Michael | Methods and apparatus for information storage and retrieval using a hashing technique with external chaining and on-the-fly removal of expired data |
US5963647A (en) | 1997-02-14 | 1999-10-05 | Citicorp Development Center, Inc. | Method and system for transferring funds from an account to an individual |
US5884312A (en) | 1997-02-28 | 1999-03-16 | Electronic Data Systems Corporation | System and method for securely accessing information from disparate data sources through a network |
US7324972B1 (en) | 1997-03-07 | 2008-01-29 | Clickshare Service Corporation | Managing transactions on a network: four or more parties |
JP3877188B2 (en) | 1997-04-10 | 2007-02-07 | 株式会社ウェブマネー | Electronic currency system |
US6012048A (en) | 1997-05-30 | 2000-01-04 | Capital Security Systems, Inc. | Automated banking system for dispensing money orders, wire transfer and bill payment |
US5903881A (en) | 1997-06-05 | 1999-05-11 | Intuit, Inc. | Personal online banking with integrated online statement and checkbook user interface |
US6012045A (en) | 1997-07-01 | 2000-01-04 | Barzilai; Nizan | Computer-based electronic bid, auction and sale system, and a system to teach new/non-registered customers how bidding, auction purchasing works |
US20010056405A1 (en) | 1997-09-11 | 2001-12-27 | Muyres Matthew R. | Behavior tracking and user profiling system |
US5960411A (en) | 1997-09-12 | 1999-09-28 | Amazon.Com, Inc. | Method and system for placing a purchase order via a communications network |
US5974430A (en) | 1997-09-30 | 1999-10-26 | Unisys Corp. | Method for dynamically embedding objects stored in a web server within HTML for display by a web browser |
US6226624B1 (en) | 1997-10-24 | 2001-05-01 | Craig J. Watson | System and method for pre-authorization of individual account remote transactions |
US5918217A (en) | 1997-12-10 | 1999-06-29 | Financial Engines, Inc. | User interface for a financial advisory system |
US6915271B1 (en) | 1998-03-11 | 2005-07-05 | The Product Engine, Inc. | Method and system for delivering redeeming dynamically and adaptively characterized promotional incentives on a computer network |
US7747523B2 (en) | 1998-03-30 | 2010-06-29 | Cohen Morris E | Internet-based financial vehicles |
US6421729B1 (en) | 1998-04-14 | 2002-07-16 | Citicorp Development Center, Inc. | System and method for controlling transmission of stored information to internet websites |
US5966696A (en) | 1998-04-14 | 1999-10-12 | Infovation | System for tracking consumer exposure and for exposing consumers to different advertisements |
US6173272B1 (en) | 1998-04-27 | 2001-01-09 | The Clearing House Service Company L.L.C. | Electronic funds transfer method and system and bill presentment method and system |
EP1097425A1 (en) * | 1998-06-19 | 2001-05-09 | Protx Limited | Verified payment system |
US7370114B1 (en) | 1998-09-11 | 2008-05-06 | Lv Partners, L.P. | Software downloading using a television broadcast channel |
FR2783623B1 (en) * | 1998-09-18 | 2003-05-09 | France Telecom | METHOD FOR MANAGING AN ELECTRONIC TRANSACTION BY CHIP CARD, TERMINAL AND CHIP CARD IMPLEMENTING THIS METHOD |
CN1319219A (en) | 1998-09-22 | 2001-10-24 | 西门子公司 | Method and system for paying for goods or services |
US7533064B1 (en) | 1998-10-07 | 2009-05-12 | Paypal Inc. | E-mail invoked electronic commerce |
US6499042B1 (en) | 1998-10-07 | 2002-12-24 | Infospace, Inc. | Selective proxy approach to filling-in forms embedded in distributed electronic documents |
US6092053A (en) | 1998-10-07 | 2000-07-18 | Cybercash, Inc. | System and method for merchant invoked electronic commerce |
US6360205B1 (en) | 1998-10-30 | 2002-03-19 | Trip.Com, Inc. | Obtaining and utilizing commercial information |
US20010014878A1 (en) | 1998-11-09 | 2001-08-16 | Nilotpal Mitra | Transaction method and apparatus |
US7937325B2 (en) | 1998-12-08 | 2011-05-03 | Yodlee.Com, Inc. | Interactive bill payment center |
US6327578B1 (en) | 1998-12-29 | 2001-12-04 | International Business Machines Corporation | Four-party credit/debit payment protocol |
US6330550B1 (en) | 1998-12-30 | 2001-12-11 | Nortel Networks Limited | Cross-media notifications for e-commerce |
US6490601B1 (en) | 1999-01-15 | 2002-12-03 | Infospace, Inc. | Server for enabling the automatic insertion of data into electronic forms on a user computer |
US7334184B1 (en) | 1999-03-10 | 2008-02-19 | American Express Travel Related Services Company, Inc. | Method for online information sharing for completing electronic forms |
US6467684B2 (en) | 1999-03-02 | 2002-10-22 | Netvisions, Inc. | Pre-paid card system for purchasing products or services |
JP4185204B2 (en) * | 1999-03-09 | 2008-11-26 | 株式会社東芝 | Payment apparatus, computer-readable storage medium storing program, and online shopping system |
AU4501600A (en) | 1999-04-30 | 2000-11-17 | X.Com Corporation | System and method for electronically exchanging value among distributed users |
US6609113B1 (en) | 1999-05-03 | 2003-08-19 | The Chase Manhattan Bank | Method and system for processing internet payments using the electronic funds transfer network |
US6227447B1 (en) | 1999-05-10 | 2001-05-08 | First Usa Bank, Na | Cardless payment system |
US7068832B1 (en) | 1999-05-11 | 2006-06-27 | The Chase Manhattan Bank | Lockbox imaging system |
US7194437B1 (en) | 1999-05-14 | 2007-03-20 | Amazon.Com, Inc. | Computer-based funds transfer system |
KR100582814B1 (en) | 1999-05-25 | 2006-05-23 | 세이프페이 오스트레일리아 피티와이 리미티드 | Method and system for handling network transactions |
JP2004500615A (en) | 1999-05-28 | 2004-01-08 | ザ・コカ−コーラ・カンパニー | Method and apparatus for network-based electronic transaction surrogate control |
US7350139B1 (en) | 2000-06-16 | 2008-03-25 | American Express Travel Related Services Company, Inc. | System and method for utilizing a drag and drop technique to complete electronic forms |
US7606760B2 (en) | 1999-06-18 | 2009-10-20 | Echarge Corporation | Method and apparatus for ordering goods, services and content over an internetwork using a virtual payment account |
US7249097B2 (en) | 1999-06-18 | 2007-07-24 | Echarge Corporation | Method for ordering goods, services, and content over an internetwork using a virtual payment account |
US7058817B1 (en) | 1999-07-02 | 2006-06-06 | The Chase Manhattan Bank | System and method for single sign on process for websites with multiple applications and services |
US7366702B2 (en) | 1999-07-30 | 2008-04-29 | Ipass Inc. | System and method for secure network purchasing |
US6873974B1 (en) | 1999-08-17 | 2005-03-29 | Citibank, N.A. | System and method for use of distributed electronic wallets |
US7093761B2 (en) | 2001-09-24 | 2006-08-22 | E2Interactive, Inc. | System and method for distributing stored-value cards |
US7343351B1 (en) | 1999-08-31 | 2008-03-11 | American Express Travel Related Services Company, Inc. | Methods and apparatus for conducting electronic transactions |
US7216292B1 (en) | 1999-09-01 | 2007-05-08 | Microsoft Corporation | System and method for populating forms with previously used data values |
US7260724B1 (en) | 1999-09-20 | 2007-08-21 | Security First Corporation | Context sensitive dynamic authentication in a cryptographic system |
US6748367B1 (en) | 1999-09-24 | 2004-06-08 | Joonho John Lee | Method and system for effecting financial transactions over a public network without submission of sensitive information |
US7127427B1 (en) | 1999-10-05 | 2006-10-24 | Andrew Casper | Secure transaction processing system and method |
US6589290B1 (en) | 1999-10-29 | 2003-07-08 | America Online, Inc. | Method and apparatus for populating a form with data |
US6332134B1 (en) | 1999-11-01 | 2001-12-18 | Chuck Foster | Financial transaction system |
US7966259B1 (en) | 1999-12-09 | 2011-06-21 | Amazon.Com, Inc. | System and methods for facilitating transactions on, and personalizing web pages of, third party web sites |
US7610233B1 (en) | 1999-12-22 | 2009-10-27 | Accenture, Llp | System, method and article of manufacture for initiation of bidding in a virtual trade financial environment |
AU3086101A (en) | 2000-01-05 | 2001-07-16 | American Express Travel Related Services Company, Inc. | Smartcard internet authorization system |
US7395241B1 (en) | 2000-01-19 | 2008-07-01 | Intuit Inc. | Consumer-directed financial transfers using automated clearinghouse networks |
US7376621B1 (en) | 2000-01-26 | 2008-05-20 | Paybyclick Corporation | Method and apparatus for conducting electronic commerce transactions using electronic tokens |
US7177838B1 (en) | 2000-01-26 | 2007-02-13 | Paybyclick Corporation | Method and apparatus for conducting electronic commerce transactions using electronic tokens |
US7328189B2 (en) | 2000-01-26 | 2008-02-05 | Paybyclick Corporation | Method and apparatus for conducting electronic commerce transactions using electronic tokens |
AU2001236812A1 (en) | 2000-02-09 | 2001-08-20 | Internetcash.Com | Method and system for making anonymous electronic payments on the world wide web |
AUPQ564400A0 (en) | 2000-02-16 | 2000-03-09 | Ong, Yong Kin (Michael) | Electronic credit card-ecc |
US8949608B2 (en) | 2000-02-18 | 2015-02-03 | Vasco Data Security, Inc. | Field programmable smart card terminal and token device |
AU2001243319A1 (en) | 2000-02-28 | 2001-09-12 | Sprarkcharge, Inc. | System, and method for prepaid anonymous and pseudonymous credit card type transactions |
WO2001067355A2 (en) | 2000-03-07 | 2001-09-13 | American Express Travel Related Services Company, Inc. | System for facilitating a transaction |
US7379919B2 (en) | 2000-04-11 | 2008-05-27 | Mastercard International Incorporated | Method and system for conducting secure payments over a computer network |
CA2305249A1 (en) | 2000-04-14 | 2001-10-14 | Branko Sarcanin | Virtual safe |
US7827115B2 (en) | 2000-04-24 | 2010-11-02 | Visa International Service Association | Online payer authentication service |
US20020002495A1 (en) | 2000-05-19 | 2002-01-03 | Npax, Inc. | Integrated pharmaceutical accounts management system and method |
US7249095B2 (en) | 2000-06-07 | 2007-07-24 | The Chase Manhattan Bank, N.A. | System and method for executing deposit transactions over the internet |
US7426530B1 (en) | 2000-06-12 | 2008-09-16 | Jpmorgan Chase Bank, N.A. | System and method for providing customers with seamless entry to a remote server |
US7702580B1 (en) | 2000-06-13 | 2010-04-20 | Fannie Mae | System and method for mortgage loan pricing, sale and funding |
AU7196801A (en) | 2000-07-10 | 2002-01-21 | Paypal Inc | System and method for verifying a financial instrument |
GB2367411C (en) | 2000-07-10 | 2007-12-12 | Garry Harold Gibson | Pyment system |
WO2002005192A1 (en) | 2000-07-11 | 2002-01-17 | Citicorp Credit Services, Inc. | Method and system for on-line payments |
US7546275B1 (en) | 2000-07-20 | 2009-06-09 | International Business Machines Corporation | Decentralized electronic certified payment |
US7257581B1 (en) | 2000-08-04 | 2007-08-14 | Guardian Networks, Llc | Storage, management and distribution of consumer information |
AU2001285422A1 (en) | 2000-08-11 | 2002-02-25 | John J. Loy | Trade receivable processing method and apparatus |
US7206768B1 (en) | 2000-08-14 | 2007-04-17 | Jpmorgan Chase Bank, N.A. | Electronic multiparty accounts receivable and accounts payable system |
US7346577B1 (en) | 2000-08-28 | 2008-03-18 | Javien Digital Payment Solutions, Inc. | Third-party billing system and method |
JP2002099852A (en) * | 2000-09-25 | 2002-04-05 | Isola Barrier Free Co Ltd | Settlement method and settlement system |
US20020052841A1 (en) | 2000-10-27 | 2002-05-02 | Guthrie Paul D. | Electronic payment system |
US7729925B2 (en) | 2000-12-08 | 2010-06-01 | Sony Corporation | System and method for facilitating real time transactions between a user and multiple entities |
US20020073027A1 (en) | 2000-12-11 | 2002-06-13 | Hui Helen Shan-Shan | Mobile payment system |
US7130817B2 (en) | 2000-12-15 | 2006-10-31 | First Data Corporation | Electronic gift linking |
JP2002197390A (en) | 2000-12-25 | 2002-07-12 | Nec Corp | Transaction intermediary system and transaction intermediary method |
US20020120582A1 (en) | 2001-02-26 | 2002-08-29 | Stephen Elston | Method for establishing an electronic commerce account |
US7809650B2 (en) | 2003-07-01 | 2010-10-05 | Visa U.S.A. Inc. | Method and system for providing risk information in connection with transaction processing |
US20020128917A1 (en) | 2001-03-06 | 2002-09-12 | Electronic Data Systems Corporation | Method and apparatus for processing financial transactions |
US7292999B2 (en) | 2001-03-15 | 2007-11-06 | American Express Travel Related Services Company, Inc. | Online card present transaction |
US7020645B2 (en) | 2001-04-19 | 2006-03-28 | Eoriginal, Inc. | Systems and methods for state-less authentication |
AU2002256770A1 (en) * | 2001-05-02 | 2002-11-11 | Virtual Access Limited | Secure payment method and system |
US7502833B2 (en) | 2001-05-11 | 2009-03-10 | International Business Machines Corporation | Method for dynamically integrating remote portlets into portals |
US7249092B2 (en) | 2001-05-29 | 2007-07-24 | American Express Travel Related Services Company, Inc. | System and method for facilitating a subsidiary card account with controlled spending capability |
US20020184147A1 (en) | 2001-06-05 | 2002-12-05 | Boulger Gordon D. | System for paying invoices |
US7174302B2 (en) | 2001-06-11 | 2007-02-06 | Evolution Benefits, Inc. | System and method for processing flexible spending account transactions |
US7533063B2 (en) | 2001-06-14 | 2009-05-12 | Silicon Storage Technology, Inc. | Smart memory card wallet |
JP2003016367A (en) | 2001-06-29 | 2003-01-17 | Oki Electric Ind Co Ltd | Prepaid electronic money-associated system and its control program |
US7543738B1 (en) | 2001-07-10 | 2009-06-09 | American Express Travel Related Services Company, Inc. | System and method for secure transactions manageable by a transaction account provider |
US7266840B2 (en) | 2001-07-12 | 2007-09-04 | Vignette Corporation | Method and system for secure, authorized e-mail based transactions |
US20040128508A1 (en) | 2001-08-06 | 2004-07-01 | Wheeler Lynn Henry | Method and apparatus for access authentication entity |
AU2002326635A1 (en) | 2001-08-15 | 2003-03-03 | Shea Writer | Methods for verifying cardholder authenticity and for creating billing address database |
US7099850B1 (en) | 2001-09-21 | 2006-08-29 | Jpmorgan Chase Bank, N.A. | Methods for providing cardless payment |
AU2002340138A1 (en) | 2001-10-09 | 2003-04-22 | Joanna Sandorffy | System and method for conducting a financial transaction using a communication device |
US6670569B2 (en) | 2001-11-08 | 2003-12-30 | First Data Corporation | Mail handling equipment and methods |
US7523182B2 (en) | 2001-11-27 | 2009-04-21 | Isochron, Inc. | Method and system for predicting the services needs of remote point of sale devices |
US7461028B2 (en) | 2001-11-27 | 2008-12-02 | Pitney Bowes Inc. | Method and system for authorizing use of a transaction card |
US20030101134A1 (en) | 2001-11-28 | 2003-05-29 | Liu James C. | Method and system for trusted transaction approval |
CA2364142A1 (en) | 2001-11-30 | 2003-05-30 | Ibm Canada Limited-Ibm Canada Limitee | Authorizing multiple categories of card based financial transactions |
US6901387B2 (en) | 2001-12-07 | 2005-05-31 | General Electric Capital Financial | Electronic purchasing method and apparatus for performing the same |
US7805376B2 (en) | 2002-06-14 | 2010-09-28 | American Express Travel Related Services Company, Inc. | Methods and apparatus for facilitating a transaction |
US7159180B2 (en) | 2001-12-14 | 2007-01-02 | America Online, Inc. | Proxy platform integration system |
US20030135434A1 (en) * | 2002-01-14 | 2003-07-17 | Ravi Jain | System and method for micro-payments |
EP1483713A4 (en) | 2002-02-14 | 2005-04-06 | Zachary Pessin | Apparatus and method of a distributed capital system |
US7092913B2 (en) | 2002-02-26 | 2006-08-15 | Cannon Jr Thomas Calvin | System for inexpensively executing online purchases |
US7131571B2 (en) | 2002-03-26 | 2006-11-07 | First Data Corporation | Alternative payment devices using electronic check processing as a payment mechanism |
US7487127B2 (en) | 2002-03-27 | 2009-02-03 | First Data Corporation | Merchant cash payment systems and methods |
US7496952B2 (en) | 2002-03-28 | 2009-02-24 | International Business Machines Corporation | Methods for authenticating a user's credentials against multiple sets of credentials |
US20030197061A1 (en) | 2002-04-23 | 2003-10-23 | Linda Din | Shopping system |
CA2485109A1 (en) | 2002-05-10 | 2003-11-20 | Ecardless Bancorp, Ltd. | Purchasing on the internet using verified order information and bank payment assurance |
US7519560B2 (en) | 2002-05-24 | 2009-04-14 | Jpmorgan Chase Bank, N.A. | System and method for electronic authorization of batch checks |
US7437327B2 (en) | 2002-05-24 | 2008-10-14 | Jp Morgan Chase Bank | Method and system for buyer centric dispute resolution in electronic payment system |
US7472171B2 (en) | 2002-06-21 | 2008-12-30 | Jpmorgan Chase Bank, National Association | Method and system for determining receipt of a delayed cookie in a client-server architecture |
US7251656B2 (en) | 2002-07-26 | 2007-07-31 | Checkfree Corporation | Electronic payments using multiple unique payee identifiers |
US7280981B2 (en) | 2002-08-27 | 2007-10-09 | Visa U.S.A. Inc. | Method and system for facilitating payment transactions using access devices |
US20050044385A1 (en) | 2002-09-09 | 2005-02-24 | John Holdsworth | Systems and methods for secure authentication of electronic transactions |
US20040103057A1 (en) | 2002-11-26 | 2004-05-27 | Worldpass Corporation | System and method for processing a long distance communication using a debit account |
US7346587B2 (en) | 2002-12-06 | 2008-03-18 | Aol Llc | Intelligent method of order completion in an e-commerce environment based on availability of stored billing information |
US7571140B2 (en) | 2002-12-16 | 2009-08-04 | First Data Corporation | Payment management |
US8204806B2 (en) | 2002-12-23 | 2012-06-19 | United Services Automobile Association (Usaa) | System and method of processing account information over a computer network |
US6871288B2 (en) | 2003-02-21 | 2005-03-22 | Ronald K. Russikoff | Computerized password verification system and method for ATM transactions |
US20040236692A1 (en) | 2003-04-11 | 2004-11-25 | Kerry Sellen | Authorization approved transaction |
US7392536B2 (en) | 2003-06-18 | 2008-06-24 | Microsoft Corporation | System and method for unified sign-on |
US7483845B2 (en) | 2003-06-24 | 2009-01-27 | Nokia Corporation | Methods, system, and computer readable medium for user data entry, at a terminal, for communication to a remote destination |
US6932268B1 (en) | 2003-06-30 | 2005-08-23 | Checkfree Corporation | Dual mode credit card based payment technique |
US7761374B2 (en) | 2003-08-18 | 2010-07-20 | Visa International Service Association | Method and system for generating a dynamic verification value |
US20050199709A1 (en) | 2003-10-10 | 2005-09-15 | James Linlor | Secure money transfer between hand-held devices |
EA009978B1 (en) | 2004-01-06 | 2008-04-28 | Епасспорте, Н.В. | Method of managing prepaid accounts |
US7337953B2 (en) | 2004-02-06 | 2008-03-04 | Early Warning Services, Llc. | Negotiable instrument authentication systems and methods |
US7873572B2 (en) * | 2004-02-26 | 2011-01-18 | Reardon David C | Financial transaction system with integrated electronic messaging, control of marketing data, and user defined charges for receiving messages |
US7577599B2 (en) | 2004-03-12 | 2009-08-18 | First Data Corporation | Method and system for processing electronic payment transactions |
US7584153B2 (en) | 2004-03-15 | 2009-09-01 | Qsecure, Inc. | Financial transactions with dynamic card verification values |
US7580898B2 (en) | 2004-03-15 | 2009-08-25 | Qsecure, Inc. | Financial transactions with dynamic personal account numbers |
US7580857B2 (en) | 2004-04-16 | 2009-08-25 | First Data Corporation | Methods and systems for online transaction processing |
US7660779B2 (en) | 2004-05-12 | 2010-02-09 | Microsoft Corporation | Intelligent autofill |
US20060190300A1 (en) | 2004-05-19 | 2006-08-24 | Fairpay Solutions, Inc. | Post payment provider agreement process |
US7219832B2 (en) | 2004-06-17 | 2007-05-22 | First Data Corporation | ATM machine and methods with currency conversion capabilities |
EP1769457A4 (en) * | 2004-06-25 | 2011-11-02 | Heartland Payment Systems Inc | Payment processing method and system |
US7694135B2 (en) | 2004-07-16 | 2010-04-06 | Geotrust, Inc. | Security systems and services to provide identity and uniform resource identifier verification |
KR100781301B1 (en) | 2004-08-05 | 2007-11-30 | 주식회사 모빌리언스 | Payment system and its method for supporting user verification in VoIP configuration |
US7175074B2 (en) | 2004-08-25 | 2007-02-13 | Checkfree Services Corporation | Methods and apparatus for processing electronic checks |
US8027918B2 (en) * | 2004-08-30 | 2011-09-27 | Google Inc. | Micro-payment system architecture |
US20060089906A1 (en) | 2004-10-21 | 2006-04-27 | Michael Rowley | Method for securing a payment transaction over a public network |
US20060131390A1 (en) | 2004-12-16 | 2006-06-22 | Kim Mike I | Method and system for providing transaction notification and mobile reply authorization |
TWI250435B (en) * | 2004-12-24 | 2006-03-01 | Ind Tech Res Inst | Method of copyright publication and trade for stepwise digital content |
JP2006236045A (en) * | 2005-02-25 | 2006-09-07 | Vodafone Kk | Ic card function information output method, and mobile communication terminal apparatus |
US7258268B2 (en) | 2005-02-28 | 2007-08-21 | Moneygram International, Inc. | Method and apparatus for money transfer |
US8887233B2 (en) | 2005-04-08 | 2014-11-11 | Netapp, Inc. | Cookie-based acceleration of an authentication protocol |
US7347361B2 (en) | 2005-06-13 | 2008-03-25 | Robert Lovett | System, method and program product for account transaction validation |
US20060294005A1 (en) | 2005-06-23 | 2006-12-28 | David Drepak | Universal e-money brokerage service and method |
WO2007023486A2 (en) | 2005-08-22 | 2007-03-01 | P.C.S.M. Ltd. | Secure internet e-commerce |
CA2624981C (en) | 2005-10-06 | 2017-06-13 | C-Sam, Inc. | Three-dimensional transaction authentication |
US7568631B2 (en) | 2005-11-21 | 2009-08-04 | Sony Corporation | System, apparatus and method for obtaining one-time credit card numbers using a smart card |
US7664699B1 (en) | 2005-12-21 | 2010-02-16 | Symantec Corporation | Automatic generation of temporary credit card information |
US7877353B2 (en) | 2006-03-13 | 2011-01-25 | Ebay Inc. | Peer-to-peer trading platform with relative reputation-based item search and buddy rating |
US20070255662A1 (en) | 2006-03-30 | 2007-11-01 | Obopay Inc. | Authenticating Wireless Person-to-Person Money Transfers |
US7500606B2 (en) | 2006-04-14 | 2009-03-10 | Harexinfotech, Inc. | Method of settling signatureless payment of bank card sales slip in mobile terminal, and system therefor |
US7552467B2 (en) | 2006-04-24 | 2009-06-23 | Jeffrey Dean Lindsay | Security systems for protecting an asset |
WO2007127411A2 (en) * | 2006-04-28 | 2007-11-08 | Efunds Corporation | Methods and systems for opening and funding a financial account online |
US8041640B2 (en) | 2006-05-02 | 2011-10-18 | Compucredit Intellectual Property Holdings Corp. Ii | Method and system for account verification |
CN101467173A (en) | 2006-05-09 | 2009-06-24 | 票务专家公司 | Apparatus for access control and processing |
US7540408B2 (en) | 2006-06-22 | 2009-06-02 | Hip Consult Inc. | Apparatus and method for facilitating money or value transfer |
US20080015985A1 (en) | 2006-07-11 | 2008-01-17 | Armand Abhari | System and process for expedited payment through online banking/payment channel |
US20080247629A1 (en) | 2006-10-10 | 2008-10-09 | Gilder Clark S | Systems and methods for check 21 image replacement document enhancements |
AU2007307688B2 (en) | 2006-10-11 | 2011-06-23 | Visa International Service Association | Method and system for processing micropayment transactions |
US7716596B2 (en) | 2006-11-08 | 2010-05-11 | International Business Machines Corporation | Dynamic input field protection |
US9251637B2 (en) | 2006-11-15 | 2016-02-02 | Bank Of America Corporation | Method and apparatus for using at least a portion of a one-time password as a dynamic card verification value |
US20080162295A1 (en) | 2006-12-29 | 2008-07-03 | Ebay Inc. | Method and system for payment authentication |
US20080177796A1 (en) | 2007-01-19 | 2008-07-24 | Eldering Charles A | Method of Distributing Contact Information to Merchant Websites |
CA2578893A1 (en) | 2007-02-15 | 2008-08-15 | Ibm Canada Limited - Ibm Canada Limitee | System and method for processing payment options |
US20080208762A1 (en) | 2007-02-22 | 2008-08-28 | First Data Corporation | Payments using a mobile commerce device |
US10853855B2 (en) | 2007-05-20 | 2020-12-01 | Michael Sasha John | Systems and methods for automatic and transparent client authentication and online transaction verification |
TW200845690A (en) | 2007-05-14 | 2008-11-16 | David Chiu | Business protection system in internet |
US20090006646A1 (en) | 2007-06-26 | 2009-01-01 | Data Frenzy, Llc | System and Method of Auto Populating Forms on Websites With Data From Central Database |
US7849014B2 (en) | 2007-08-29 | 2010-12-07 | American Express Travel Related Services Company, Inc. | System and method for facilitating a financial transaction with a dynamically generated identifier |
AU2008316230B2 (en) | 2007-10-24 | 2013-10-31 | Securekey Technologies Inc. | Method and system for effecting secure communication over a network |
US7567920B2 (en) | 2007-11-01 | 2009-07-28 | Visa U.S.A. Inc. | On-line authorization in access environment |
US7949579B2 (en) | 2007-12-07 | 2011-05-24 | Jpmorgan Chase Bank, N.A. | System and method for associating financial transaction data with a user's project data |
US10262303B2 (en) | 2007-12-28 | 2019-04-16 | Mastercard International Incorporated | Methods and systems for applying a rewards program promotion to payment transactions |
US8214288B2 (en) | 2007-12-28 | 2012-07-03 | Ebay Inc. | System and method of a passphrase account identifier for use in a network environment |
US7922082B2 (en) | 2008-01-04 | 2011-04-12 | M2 International Ltd. | Dynamic card validation value |
US20090182675A1 (en) | 2008-01-04 | 2009-07-16 | Brody Edward | Method and system for conducting electronic commerce over a network using a shadow credit card number |
US20090182674A1 (en) | 2008-01-14 | 2009-07-16 | Amol Patel | Facilitating financial transactions with a network device |
US20090216676A1 (en) | 2008-02-21 | 2009-08-27 | Anup Kumar Mathur | Integrated mobile transaction system and methods thereof |
US20090259547A1 (en) | 2008-04-11 | 2009-10-15 | Brian Clopp | Affiliate and cross promotion systems and methods |
-
2007
- 2007-10-11 AU AU2007307688A patent/AU2007307688B2/en active Active
- 2007-10-11 CA CA002666262A patent/CA2666262A1/en not_active Abandoned
- 2007-10-11 EP EP07853964A patent/EP2074726A4/en not_active Ceased
- 2007-10-11 WO PCT/US2007/081124 patent/WO2008046012A2/en active Application Filing
- 2007-10-11 KR KR1020097007478A patent/KR20090063254A/en not_active Application Discontinuation
- 2007-10-11 JP JP2009532582A patent/JP2010507151A/en active Pending
- 2007-10-11 US US11/870,799 patent/US8335745B2/en active Active
- 2007-10-11 BR BRPI0715571-9A patent/BRPI0715571A2/en not_active IP Right Cessation
- 2007-10-11 CN CNA2007800453404A patent/CN101554005A/en active Pending
- 2007-10-11 TW TW096137958A patent/TW200834446A/en unknown
-
2012
- 2012-09-14 US US13/616,587 patent/US20130013509A1/en not_active Abandoned
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7337144B1 (en) * | 2000-09-28 | 2008-02-26 | Microsoft Corporation | Method and system for restricting the usage of payment accounts |
US20030061111A1 (en) * | 2001-09-26 | 2003-03-27 | International Business Machines Corporation | Method and system for parent controlled e-commerce |
US20040029569A1 (en) * | 2001-12-26 | 2004-02-12 | Vivotech, Inc. | Micropayment financial transaction process utilizing wireless network processing |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9443268B1 (en) | 2013-08-16 | 2016-09-13 | Consumerinfo.Com, Inc. | Bill payment and reporting |
US11928668B1 (en) | 2014-04-30 | 2024-03-12 | Wells Fargo Bank, N.A. | Mobile wallet using tokenized card systems and methods |
US11935045B1 (en) | 2014-04-30 | 2024-03-19 | Wells Fargo Bank, N.A. | Mobile wallet account provisioning systems and methods |
US11321707B2 (en) | 2016-03-22 | 2022-05-03 | Visa International Service Association | Adaptable authentication processing |
US11049101B2 (en) * | 2017-03-21 | 2021-06-29 | Visa International Service Association | Secure remote transaction framework |
US11551190B1 (en) | 2019-06-03 | 2023-01-10 | Wells Fargo Bank, N.A. | Instant network cash transfer at point of sale |
US11948134B1 (en) | 2019-06-03 | 2024-04-02 | Wells Fargo Bank, N.A. | Instant network cash transfer at point of sale |
Also Published As
Publication number | Publication date |
---|---|
WO2008046012A2 (en) | 2008-04-17 |
AU2007307688B2 (en) | 2011-06-23 |
EP2074726A4 (en) | 2011-06-01 |
AU2007307688A1 (en) | 2008-04-17 |
BRPI0715571A2 (en) | 2013-07-02 |
US8335745B2 (en) | 2012-12-18 |
JP2010507151A (en) | 2010-03-04 |
EP2074726A2 (en) | 2009-07-01 |
CN101554005A (en) | 2009-10-07 |
US20080091619A1 (en) | 2008-04-17 |
TW200834446A (en) | 2008-08-16 |
KR20090063254A (en) | 2009-06-17 |
WO2008046012A3 (en) | 2008-11-06 |
CA2666262A1 (en) | 2008-04-17 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8335745B2 (en) | Method and system for processing micropayment transactions | |
US10984403B2 (en) | Systems and methods for brokered authentification express seller links | |
US7904385B2 (en) | Systems and methods for facilitating budgeting transactions | |
US7280981B2 (en) | Method and system for facilitating payment transactions using access devices | |
US8234212B2 (en) | Systems and methods for facilitating transactions with interest | |
US8103584B2 (en) | Systems and methods for authorizing an allocation of an amount between transaction accounts | |
US7979349B2 (en) | Systems and methods for adjusting crediting limits to facilitate transactions | |
US7941372B2 (en) | Systems and methods for receiving an allocation of an amount between transaction accounts | |
US8275704B2 (en) | Systems and methods for authorizing an allocation of an amount between transaction accounts | |
US7908214B2 (en) | Systems and methods for adjusting loan amounts to facilitate transactions | |
US7899744B2 (en) | Systems and methods for approval of an allocation | |
US7996307B2 (en) | Systems and methods for facilitating transactions between different financial accounts | |
US8458086B2 (en) | Allocating partial payment of a transaction amount using an allocation rule | |
US7962406B2 (en) | Systems and methods for facilitating transactions | |
US8103585B2 (en) | Systems and methods for suggesting an allocation | |
US20120078791A1 (en) | Method and system for facilitating payment transactions using access devices | |
US20090048887A1 (en) | Systems and Methods for Facilitating Transactions Involving an Intermediary | |
US20090048885A1 (en) | Systems and Methods for Facilitating Cost-Splitting Transactions | |
US20090048968A1 (en) | Systems and Methods for Facilitating Transactions with Different Account Issuers | |
US20090048886A1 (en) | Systems and Methods for Facilitating Gifting Transactions | |
EP3308337A1 (en) | Systems and methods for extending credit to small/medium-sized enterprises |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: VISA INTERNATIONAL SERVICE ASSOCIATION, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PERLMAN, JEFFREY W.;KEARNEY, MICHAEL J.;LEE, TIMOTHY M.;AND OTHERS;SIGNING DATES FROM 20071005 TO 20071010;REEL/FRAME:029419/0349 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |