WO2011053718A1 - Sponsored accounts for computer-implemented payment system - Google Patents
Sponsored accounts for computer-implemented payment system Download PDFInfo
- Publication number
- WO2011053718A1 WO2011053718A1 PCT/US2010/054533 US2010054533W WO2011053718A1 WO 2011053718 A1 WO2011053718 A1 WO 2011053718A1 US 2010054533 W US2010054533 W US 2010054533W WO 2011053718 A1 WO2011053718 A1 WO 2011053718A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- account
- sponsored
- primary
- payer
- holder
- Prior art date
Links
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/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/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
-
- 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/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
- the present disclosure relates generally to computer-implemented systems and methods for making electronic payments.
- Electronic commerce commonly known as electronic marketing, e-commerce, or eCommerce, consists of the buying and selling of products or services over electronic systems such as the Internet and other computer networks.
- the amount of trade conducted electronically has grown extraordinarily with widespread Internet usage.
- Commerce conducted in this manner utilizes a complex web of innovations in electronic funds transfer, supply chain management, Internet marketing, online transaction processing, electronic data interchange (EDI), inventory management systems, automated data collection systems, and many others.
- Modern electronic commerce typically uses the World Wide Web at least at some point in the transaction's lifecycle, although it can encompass a wider range of technologies such as e-mail as well.
- a system may include an account processor to execute software instructions for creating and managing electronic payment accounts and an accounts database to store account data from the account processor.
- the account processor may be configured to create a primary account and a sponsored account in the accounts database.
- the primary account may be associated with a primary account holder who has access to the primary account to add and remove funds.
- the sponsored account may be associated with both the primary account holder and a sponsored account holder, where the primary account holder has access to the sponsored account to transfer funds between the primary account and the sponsored account in order to add and remove funds from the sponsored account, and the sponsored account holder has access to the sponsored account for making transactions using funds in the sponsored account.
- a method of creating an electronic payment account may include the steps of: receiving at an account processor a request to create a new electronic payment account, the request including account profile information relating to an applicant; and determining from the account profile information if the applicant is over a predetermined minimum age for opening a primary account. If the applicant is over the predetermined minimum age, then a primary account may be opened for the applicant using the account profile information.
- the account processor may: automatically direct the applicant to a graphical user interface for requesting a sponsored account; receive via the graphical user interface information identifying a sponsor; request approval for the sponsored account from the sponsor; and upon receiving approval from the sponsor, create a sponsored account for the applicant and linking the sponsored account to a primary account associated with the sponsor, wherein the sponsor is given access to the sponsored account to transfer funds from the primary account to the sponsored account and the applicant is given access to the sponsored account for making purchases using funds in the sponsored account.
- FIG. 1 depicts a dataflow diagram for exemplary participants in a micropayment transaction.
- FIG. 2 depicts a flow diagram for an exemplary process of processing a micropayment transaction.
- FIG. 3 depicts a flow diagram for an exemplary settlement process for a micropayment processing system.
- FIGs. 4A1 , 4A2 and 4B depict a flow diagram for an exemplary micropayment purchase from a payee website.
- Fig. 5 shows a block diagram of an example electronic payment system.
- Fig. 6 shows a block diagram of an example primary and sponsored account system.
- Fig. 7 shows an example flow chart depicting a method to setup a sponsored account.
- Fig. 8 shows a second example flow chart depicting a method to setup a sponsored account.
- Fig. 8A shows an example of a graphical user interface for providing information for opening a sponsored account.
- Fig. 8B shows an example of a notification transmitted to an identified user for completing a sponsored account registration.
- Fig. 9 shows an example graphical user interface for entering an e-mail address.
- Fig. 10 shows an example graphical user interface for selecting to sign-in or create an account.
- Fig. 11 shows an example graphical user interface webpage for a sponsored account.
- Fig. 12 shows a portion of an example graphical user interface webpage for a primary account.
- Fig. 13 shows an example graphical user interface for a Sponsored Account Summary webpage.
- Fig. 14 shows an example graphical user interface for displaying trusted level 2 sellers associated with a sponsored account.
- Fig. 15 shows an example of a graphical user interface for the View Details of the sponsored account webpage.
- Fig. 16 shows an example graphical user interface page for topping up sponsored accounts.
- Fig. 17 shows an example graphical user interface showing the confirmation message for the transferred funds.
- Fig. 18 shows an example graphical user interface page for scheduling periodic top-ups to the sponsored accounts.
- Fig. 19 illustrates an example graphical user interface for selecting which funding source to use for the periodic top-up.
- Figs. 20A and 20B show an example graphical user interface page for editing the periodic top-up.
- Fig. 22 shows an example notification explaining that the user has insufficient funds.
- Fig. 23 shows an example graphical user interface page for closing a sponsored account.
- Fig. 24 shows an example graphical user interface for confirming an account closure.
- Figs. 25A and 25B show an example graphical user interface for viewing the read-only information of a sponsored account and for reopening the account.
- Fig. 26 shows an example graphical user interface for closing the account from the sponsored account.
- Fig. 27 shows an example notification to the sponsor about the sponsored account closure.
- Fig. 28 shows an example e-mail notification to the sponsor about the sponsored account closure.
- Fig. 29 shows an example of a notification that a sponsored account has been reactivated.
- Fig. 30 shows an example notification to the sponsored account holder that a sponsored account has been reactivated.
- Figs. 31-47 illustrate another example method and example user interfaces for opening a sponsored account.
- Fig. 48 illustrates exemplary hardware on which the various embodiments of the sponsored account system may be practiced.
- 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 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. 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. 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 1 15 may transmit 230 the transaction information supplied by the payer 105 to the acquirer bank 120.
- 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.
- 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.RTM.-branded credit card, the source details for the selected payment type and a load amount.
- 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 is authorized, the micropayment payment system may display 416 a load confirmation screen, which requests, for example, a password and selections and answers for, for example, three security questions. In other examples, additional or alternate information may be requested from the user within the scope of this disclosure. In addition, an alternate number of security questions, other security verification methodologies and/or load transaction failures may also be included within the scope of this disclosure.
- 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.
- 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. 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.
- 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. [0060] 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.
- 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.
- Figs. 5-48 illustrate examples of systems and methods for providing sponsored accounts for a computer-implemented payment system.
- a sponsored account system may be used to provide users that are not eligible or are unwilling to directly hold electronic payment accounts with a way to purchase items with electronic payments.
- a sponsored account system may be used for other purposes, such as for gifts or payments to other users, even those that are eligible for their own electronic payment accounts.
- the sponsored account system may be used in other situations, such as employee-employer situations, wherein the primary account holder desires to have a measure of control over the sponsored account holder's purchases.
- Fig. 5 shows a block diagram of an example transaction processing system 1000.
- System 1000 can be a computer-implemented environment wherein one or more users 1050 can interact with one or more websites 1100 through a network 1200.
- the user may wish to engage in a financial transaction with the website, may wish to receive access to restricted information or functionality available via the website, or may wish to engage in similar or related interactions with the websites.
- the user establishes one or more primary and sponsored accounts in an accounts database 1160 with the account processor 1 150 via the network 1200.
- the user may establish the one or more accounts with the account processor prior to visiting the websites or may be redirected from the website to the account processor for purposes of establishing one or more accounts.
- the one or more primary and sponsored accounts may be used to conduct a financial transaction with a website.
- the one or more primary and sponsored accounts may be used to purchase goods and/or services from the website.
- the user 1050 may navigate to the website 1100 to initiate a financial transaction, such as the purchase of goods or services.
- the primary account holder selects one of the one or more external funding sources maintained with the account processor 1 150 to be used as part of the financial transaction, and the primary account holder is then authenticated to the website via the account processor.
- the sponsored account does not require any outside funding sources to make a purchase.
- the one or more external funding sources may be prepaid accounts, stored value accounts, credit accounts, debit accounts, or the like.
- the prepaid accounts may be useful for conducting low value transactions in a manner which increases profitability for the seller.
- the account may be a credit, debit or other account, or an alias for such an account that may be more appropriate for higher valued transactions.
- the sponsored account is funded only by funds received from the primary account.
- the one or more accounts may alternately be health care related accounts that enable the user to access health care related information on the website, to conduct health care related transactions, or to otherwise manage and/or acquire health care related products and/or services.
- the one or more accounts may enable the user to access any type of restricted access information or functionality on the website and/or to engage in a transaction related to such restricted access.
- the account processor 1150 may comprise one or more servers containing software operations or routines for creating and maintaining accounts for the users; for enabling the users to conduct transactions with one or more websites; for enabling users to initiate dispute proceedings with one or more websites and to automate the communications related to the dispute and the resolution of the dispute; to initiate and transmit alerts to users, websites, and or system administrators based upon pre-defined and/or customizable parameters; to configure and apply fees to all transactions; and to conduct reporting as may be relevant to the websites, the account processor and/or the users.
- the one or more servers , of the account processor may additionally contain software operations or routines related to managing the accounts (such as by updating billing addresses, delivery addresses, user preferences, and the like); for enabling users to authorize and manage recurring payments or to pre-authorize payments; for enabling users to pre-authorize (i.e., whitelist) or prohibit (i.e., blacklist) websites and/or transactions; and/or for enabling users to manage accounts and conduct transactions using mobile electronic devices or any other electronic device such as internet-connected gaming consoles, a digital set-top box, or similar devices.
- the accounts database 1160 may comprise one or more memory devices. In certain examples, the accounts database 1160 may be comprised of a plurality of disbursed memory devices. In another example, the accounts database 1160 may include one or more memory devices that are included within the same one or more servers as the account processor 1150.
- Fig. 6 shows example data structures for sponsored accounts 1500, 1590 that are sponsored by a primary account 1400.
- a user having a primary account 1400 which is funded by an external funding source 2100, can sponsor one or more sponsored accounts 1500, 1590 for use by others, such as children, friends, relatives, employees, etc.
- the system of primary 1400 and sponsored accounts 1500, 1590 are hosted on a website, and the account data 1410, 1430, 1450, 1530, 1550 are stored in an accounts database, such as a database associated with the website. From the primary 1400 and sponsored accounts 1500, 1590 the users are able to make purchases from merchant websites 2180, 2200, 2300. The setup, operation, and closing of the sponsored accounts is discussed herein.
- Fig. 7 shows an example of a method to setup a sponsored account.
- a computing apparatus e.g., a website receives (step 2310) a request from a user of a primary account to open a sponsored account.
- the request may specifically identify the user of the second account and an address to contact the user of the second account, such as an email address, a mobile phone number, an instant messaging identifier, etc.
- Funds may then be transferred to the second account via the first account (step 2320).
- the computing apparatus transmits (step 2330) a message containing an activation code to the user of the second account.
- the computing apparatus When the computing apparatus receives (step 2350) a request to activate the second account using the activation code, the computing apparatus prompts (step 2370) the user to authenticate via an authentication broker (e.g., a website). If the user does not already have an account with the authentication broker, the user may establish one at this time. The method may also require entry of some type of secret information known to both parties, such as the email address or mobile phone number of the primary account holder (step 2380). Once the user is authenticated by the authentication broker and the secret information has been successfully entered, the computing apparatus associates (step 2390) the second account with a credential provided by the authentication broker. Subsequently, the user of the second account can access the second account via authenticating with the authentication broker. Funds may then be transferred to the second account via the first account (step 2410).
- an authentication broker e.g., a website. If the user does not already have an account with the authentication broker, the user may establish one at this time. The method may also require entry of some type of secret information
- the primary account holder requests that a sponsored account be created, and provides information necessary to open the account (step 3030). For example, the primary account holder can input the request on a website user interface, and provide information for opening the sponsored account for an identified user.
- the information may include the name and email address of the identified user, a mobile phone number, an instant messaging identifier, etc., of the identified user.
- the primary account holder may also write an optional message to the identified user to be sent with the notification.
- the system will check if the identified user's contact information is already registered with the system (e.g. for another sponsored account or for a primary account). In one example if the contact information is already registered, the primary account holder will be notified and prompted to try submitting the information again.
- Fig. 8A shows an example of a graphical user interface for implementing step 3030.
- the primary account user selects "Sponsored Accounts" from a navigation menu.
- the user selects "Add New Sponsored Account” from a separate sub-menu.
- a form is then displayed where the user enters an e-mail address for the sponsored account user, re-enters the e-mail, enters the first name and last name of the sponsored account user, enters an optional "Message to sponsored accounts," and then clicks a "Send invitation” button to initiate the sponsored account notification.
- a computer takes the information provided in the previous step and sends a notification to the user who was identified to receive the sponsored account (step 3050).
- the notification may be an e-mail, SMS, or other electronic communication.
- the notification includes instructions and information, such as an activation code, to complete registration of the account.
- a link to a website user interface for accessing the account that incorporates the activation code may be included in the notification.
- the notification may also include instructions for denying the offer of the sponsored account, such as a link to delete the account.
- the primary account holder may resend the notification in the future.
- the graphical user interface may present the resend option to the primary account holder at a later time.
- any funds that have been transferred from the primary account to the sponsored account will be returned to the primary account and the primary account holder will receive an email notifying them that the sponsored account was denied.
- the primary account holder has the option to transfer funds from the primary account to the new sponsored account (step 3070) as soon as the notification is sent, or as soon as it is received by the identified user.
- the primary account holder can also set up automatic fund transfers from the primary to the sponsored account at certain intervals or dates in the future.
- the sponsored account is not opened until the identified user follows the instructions to complete the registration of the sponsored account.
- the primary account holder may be required to wait to perform the fund transfer until another time; for example, until the sponsored account holder has registered as discussed below.
- Fig. 8B shows an example of the notification received by the identified user, including a link to complete the registration and a link to delete the sponsored account.
- the identified user can then follow the instructions contained in the notification, such as clicking on a link provided to the website user interface, for accessing the account electronically.
- the identified user may be required to enter verification information in the website user interface that identifies the notification and/or the user that sent the notification (step 3120).
- the verification information may be an activation code and/or an e-mail address.
- the verification information such as an activation code, may be contained in a link present in the notification.
- the activation code embedded in the link is based on a hash of the primary account holder's e-mail address and account ID. A computer may automatically verify this activation code before allowing the registration process to continue.
- the e-mail address of the primary account holder may be required to be entered by the identified user as an additional security hurdle to the verification code.
- Fig. 9 shows an example graphical user interface for entering the appropriate e-mail address.
- the identified user may sign in with a user ID and password from an already established electronic account, or they may register for an account (step 3140).
- the account may be specific to the primary/sponsored account system or may be a general internet account, such as an OPEN ID account.
- the website will check for a cookie from the general internet account, and if found, it will accept the logged in session state, thereby eliminating the need to log-in again.
- Fig. 10 shows a graphical user interface for selecting to sign-in or create an account.
- step 3120 the verification page of step 3120 is presented after the identified user has logged in (step 3140).
- the identified user may enter additional remaining details in a user profile (step 3160), such as setting up a password to make purchases.
- Profile information includes an e-mail address and name, which may be pre-populated from the information entered by the primary account holder, but can be modified or confirmed by the identified user. Terms and conditions may be presented for acceptance at this step.
- the identified user finishes the registration process by submitting all the profile information; for example, by clicking on a Create Account button in a graphical user interface. The identified user thus becomes the sponsored account holder.
- the identified user can complete the registration at a later time, simply by following the instructions in the notification starting at step 3100, such as by clicking again on the link in the invitation email they received. In one example, attempts to close or navigate away from the registration website will result in a notification of how the registration process may be restarted if the user abandons it.
- the funding and operation of the sponsored accounts 1500, 1590, and the primary account 1400 will be discussed.
- the primary account 1400 stores funding source data 1410, such as information about a credit card account, a debit card account, a bank account, etc.
- the sponsor uses the funding source 2100 as identified by the funding source data 1410 to replenish the primary account 1400 when the balance 1430 of the primary account 1400 is low or insufficient for a purchase.
- a user of the primary account 1400 may directly use the external funding sources 2100 identified by the funding source data 1410 to make purchases.
- the example sponsored accounts 1500, 1590 do not have funding source data 1410.
- the sponsored accounts 1500, 1590 obtain funds via the primary account 1400.
- the sponsored accounts 1500, 1590 are restricted from having funding source data 1410 of their own. In situations where the sponsored account holders are children, the sponsored account holders may not be eligible for funding sources 2100 of their own to provide funding source data 1410. In one example, the sponsored accounts 1500, 1590 are also not eligible to receive funds from any peer-to-peer transactions.
- the account 1400 of the sponsor stores the funding source data 1410, such as information about a credit card, a debit card, a bank account, etc.
- the sponsor may use the funding source 2100 as identified by the funding source data 1410 to replenish the account 1400 when the balance 1430 of the account 1400 is low or insufficient for a purchase.
- a user of the account 1400 may directly use the funding sources 2100 identified by the funding source data 1410 to make purchases.
- the sponsored accounts are under the control of the primary account.
- the primary account holder or sponsor may use the primary account 1400 to manage the sponsored accounts 1500, 1590.
- management tools are provided to the sponsor, including the ability to: view the transaction data 1550 in the sponsored account 1500, view the balance 1530 of the sponsored account 1500, withdraw funds from the sponsored account 1500, schedule regular deposits to the sponsored account 1500, top up the account 1500 (i.e., making a deposit, or bringing the balance 1530 of the sponsored account 1500 to a predetermined level), etc.
- the system may block the sponsor from accessing certain information in the sponsored account 1400, such as the transaction data 1550.
- sponsored accounts 1500, 1590 can only have funds decremented through purchases or through sponsor-initiated transfer from the sponsored account 1500, 1590 to the primary account 1400.
- Sponsored accounts can only be used for transactions from the balance 1530, no pass-through transactions (i.e., transactions funded by a third-party financial instrument) are allowed. That is, no external funding sources 2100 may be used to make transactions.
- a sponsored account holder does not have access to the information stored in the primary account 1400, such as the balance 1430 and transaction data 1450, etc.
- the total balances of the primary account 1400 and all sponsored accounts 1500, 1590 under that primary account 1400 are treated as a single balance for the purpose of risk-based account maximum balance restrictions and other legal and regulatory purposes.
- a primary account 1400 is supplied with funds from funding sources 2100 such as checking, savings, or credit card accounts. These funding options are accessible to the sponsor through a graphical user interface, for example a "manage funds" webpage that allows the sponsor to transfer funds into and out of the primary account 1400.
- the sponsored account 1500 does not have the option to import additional funds from external accounts, but receives its funds solely from the primary account 1400.
- the sponsored account 1500 cannot make withdrawals from the balance 1530, such as via transfers to external accounts.
- the sponsored account 1500 does not even have an option to associate external accounts with the sponsored account 1500, such as via the "manage funds" webpage that is available in the primary account.
- Fig. 11 shows an example graphical user interface webpage for the sponsored account 1500.
- the account summary page shows a transaction history reflecting the stored transaction data 1550 for the sponsored account 1500.
- Options are provided for adjusting the date range of the transaction history, and selecting the transaction type and status.
- An account balance is also presented on this page, in addition to information regarding regular account deposits or top-ups. In the example of Fig. 11 a deposit of $20 will be made every Thursday.
- Navigation menu items are also provided for "Express Sellers" (i.e., Trusted Level 2 sellers), and "Edit Profile.” In the "Edit Profile” menu the user may make changes to their profile information.
- An example of profile information is the information that was entered at step 3160 of the registration process.
- sponsor accounts cannot have their own sponsored accounts.
- Fig. 12 shows a portion of an example graphical user interface webpage for the primary account 1500.
- the sponsor is presented the names of the sponsored account holders, the status of the sponsored accounts 1500, 1590 (active, inactive, or closed), and the account balance of each account 1530.
- the inactive account 1590 has not yet been activated by the above-described registration procedure.
- the total sponsored account balance is also presented.
- the sponsor can select any sponsored account name to view the specific sponsored account summary page.
- Fig. 13 shows an example graphical user interface for the Sponsored Account Summary page, which includes the transaction history formulated from the transaction data 1550.
- the transaction history is identical to that presented to the sponsored account holder in the sponsored account graphical user interface.
- Fig. 14 shows an example of a graphical user interface for displaying the trusted level 2 sellers (e.g., express sellers).
- Fig. 15 shows an example of a graphical user interface for the View Details webpage. From the View Details page, the user can click on "Go to Summary" to return to the Sponsored Account Summary.
- Sponsored accounts 1500, 1590 can have account suspensions applied to them independent of the primary account 1400, such as, for failing to comply with terms of service, account non-use, etc. However, any primary account suspension automatically applies to all sponsored accounts 1500, 1590 under the primary account 1500.
- the graphical user interface shows menu options labeled “Top Up” and “Set up Regular Top-Up.” These options are how the sponsored accounts 1500, 1590 are funded whether they are active or not activated yet.
- Fig. 1 shows an example graphical user interface page titled "Top up my sponsored accounts," which is accessed by clicking on the "Top Up" menu item shown in Figs. 12 or 13.
- the sponsor enters the amount to transfer to each of one or more sponsored accounts 1500, 1590.
- the sponsor is able to see the total fund transfers as well as the funds available in the primary account 1400 before the transfer, and what will be available in the primary account 1400 after the transfers. Should the total to be transferred exceed the funds available in the primary account 1400, an insufficient funds message is displayed as the amounts are entered, prompting the sponsor to either reduce the amount to be transferred or to top-up the primary account 1400 from one of the external funding sources 2100 before proceeding.
- the primary account holder can also enter an optional message to the sponsored account holder(s) that will be displayed in the "Description" field of the line item for the top-up in the transaction history.
- Fig. 17 shows a graphical user interface showing the confirmation message for the transferred funds.
- Fig. 18 shows an example graphical user interface page titled “Regularly top-up my sponsored accounts," which is accessed by clicking on the "Set-up Regular Top Up” menu item shown in Fig. 12. From this page, primary account holders select the desired frequency and date of the deposits; for example, weekly and day of week or monthly and day of month. The amount to transfer to each sponsored account 1500, 1590 is also selected on this page. As in the one time top-up option, the primary account holder can also enter an optional message to the sponsored account holder(s) that will be displayed in the "Description" field of the line item for the top-up in the transaction history.
- An option is also provided to the primary account holder to automatically top-up their own account if sufficient funds are not available for the sponsored account automatic transfers on the transfer day.
- the primary account holder is given the option to choose which funding source 2100 to use.
- Fig. 19 illustrates a graphical user interface for selecting which funding source 2100 to use for the periodic top-up.
- bank accounts are not available in this selection because these funds need to be available immediately.
- the associated top-up is a minimum amount, such as $20, or the difference between the transfer amount and the account balance, whichever is greater.
- the primary account holder enters a password and clicks on the item "Transfer Funds Now," resulting in a confirmation message on the Primary Accounts Summary page.
- the regular top-up is reflected on the primary account holder's view of each sponsored account 1500, 1590 as well as on the sponsored account holder's main account summary page (See Fig. 13).
- the scheduled top-up to sponsored accounts can be edited by clicking on the "Edit regular top-up" link on the Sponsored Accounts account summary page (Fig. 13) or by clicking on the Set up Regular Top-up item in the left-hand navigation menu under Sponsored Accounts (Fig. 12).
- Fig. 20 shows an example graphical user interface page for editing the periodic top-up.
- the sponsor can delete the regular top-up to sponsored accounts by clicking on the "Delete this regular top-up" button. In this example this option requires entry of the password and will immediately cancel the standing order.
- the sponsor can also make modifications to the settings, which will also require entry of the password prior to clicking on the "save” button. Editing and saving the new settings will overwrite the previous standing order with the new order settings. After completing the above, the user will see a confirmation message.
- the sponsor may retrieve funds from one or more sponsored accounts 1500, 1590.
- the sponsor selects "Transfer Money from Sponsored Accounts" under the Sponsored Accounts menu, as shown in Fig. 12.
- Fig. 21 shows an example graphical user interface page for transferring money from sponsored accounts 1500, 1590.
- the sponsor enters an amount to transfer up to the balance 1530 in each sponsored account 1500, 1590, and funds available before and after the transfer are displayed. If the amount entered exceeds the sponsored account balance 1530, then an error message appears.
- the sponsor can then enter an optional message to the sponsored account holder(s) that will be displayed in the "Description" field of the line item for the transfer of funds in the transaction history.
- the sponsor enters the password and clicks on "Retrieve Funds Now.” Funds are immediately removed from the sponsored account 1500, 1590 and are added to the available balance in the primary account 1400.
- the sponsored accounts holders may make electronic purchases from internet websites.
- the sponsored accounts 1500, 1590 may only make purchases if there is a sufficient balance 1530 in the account 1500, 1590 for the purchase price.
- No external funding sources 2100 are allowed to the sponsored accounts 1500, 1590 to supplement the balance 1530 or make pass-through transactions.
- a page such as the page shown in Fig. 22, will be displayed that will explain that the user has insufficient funds. This page will not provide any options for the user to complete the transaction because a sponsored account does not have any external funding sources 2100.
- This page does, however, provide link options to either return the sponsored account holder to the seller site, which will result in an "insufficient funds" message being posted back to the seller, or to go to the user's sponsored account page, e.g. the page shown in Fig 13.
- the user may be required to enter a password for each transaction.
- Trust Level 0 the user can establish a trusted session with the merchant's website 2200, wherein a password is input one time, but need not be input again as long as the session is active. While the trusted session is active, keyboardless transactions may be made.
- an express seller merchant 2300 the user can establish a trusted relationship with the merchant's website 2300, wherein a password is input one time, and then does not need to be entered again for multiple sessions. As long as the user is logged into a merchant account with which an express seller has a relationship, a password does not need to be entered at all to make a purchase from an express seller merchant website 2300, such as a keyboardless transaction purchase.
- links to express seller merchant websites 2300 are accessed through the sponsored account graphical user interface. For example, see Fig. 11, which shows an "Express Sellers" menu tab that when selected would display links to express seller merchant websites 2300.
- Both primary accounts 1 00 and sponsored accounts 1500, 1590 may make purchases from standard (trust level 0), first and second trust level merchant websites 2180, 2200, 2300.
- the user experience for express seller merchant websites 2300 is identical to that for a primary account 1400, except the sponsored account holder will be allowed to enroll for express seller relationships without any external funding sources 2100 (unlike primary accounts, which may be required to have a funding source).
- restrictions can be set for any merchant.
- the sponsor may specify any merchant - standard, express session and/or the express seller merchants 2180, 2200, 2300, that the sponsored account may make purchases from.
- the sponsor may restrict the sponsored account from making purchases from certain standard, express session and/or express seller merchants 2180, 2200, 2300.
- the primary account holder may also be provided with the option to limit the merchant websites 2180, 2200, 2300 that the sponsored accounts 1500, 1590 can make purchases from to merchant websites that have express seller status.
- the sponsored account may be closed in three ways: by the sponsor, by the closing of the primary account 1400, and by the sponsored account holder.
- the sponsor may also use the sponsor account 1400 to close one or more sponsored accounts 1500, 1590, and to reactivate the sponsored account 1500, 1590 after closing the sponsored account 1500, 1590.
- the user of the sponsored account 1500 cannot make purchases using the funds in the sponsored account balance 1530.
- the sponsored account 1500, 1590 is closed all funds remaining in the account 1 00, 1590 are transferred back to the primary account 1400.
- Fig. 24 shows an example graphical user interface for confirming the account closure. After confirmation of the account closure, the system will send an e-mail to the sponsored account holder notifying them that the sponsor has closed the sponsored account 1500. In addition, the sponsor will also receive a confirmation email that the sponsored account 1500 has been closed.
- a sponsor's read-only access to a closed sponsored account 1500 also provides the sponsor with the option to re-activate the sponsored account or permanently close the sponsored account. See, for example, Fig. 25, which shows an example graphical user interface for viewing the read-only information on the sponsored account 1500 and for reactivating the account. Reactivation in one example would restore the sponsored account 1500 to active status, provide an option to re-fund the sponsored account 1500, and cause a notification e-mail to be sent to the sponsored account holder. Permanently closing the account would prevent any further user access to the sponsored account 1500.
- the primary account balance 1430 is distributed to the sponsor, for example, by a check.
- the sponsored account holder can also close the sponsored account 1500.
- the sponsored account holder can click on "Close Account” in the left-hand navigation menu to initiate closing the account.
- a sponsored account holder closes a sponsored account 1500, it is automatically changed to "Read-only" status for a period of time, and the closed sponsored account may be accessed as described above.
- the system upon confirming closure of the sponsored account 1500, all recurring transfers are cancelled and any funds remaining in the sponsored account 1500 are immediately transferred to the primary account 1400.
- the system notifies the sponsor and/or the sponsored account holder of the sponsored account closure. For example, the system may display a message on the sponsored account summary page and/or send an e-mail ⁇ see, e.g., Figs. 27 and 28).
- the sponsor may permanently close the sponsored account 1500 or reactivate the sponsored account 1500 as described above. However, in one example, if the account is reactivated by the sponsor, the account set up process would begin again, or in another example, a consent from the sponsored account holder would be required to reactivate the account.
- Another alternative embodiment allows the sponsor to reactivate the sponsored account 1500 immediately and without any consent from the sponsored account holder and presents the sponsor with a confirmation of this (see, e.g., Fig. 29).
- the system sends a notification, such as an e-mail to the sponsored account holder indicating that the sponsor has reactivated the account and confirming that the sponsored account holder can login with the username and password previously used (see, e.g., Fig. 30).
- a notification such as an e-mail to the sponsored account holder indicating that the sponsor has reactivated the account and confirming that the sponsored account holder can login with the username and password previously used (see, e.g., Fig. 30).
- a sponsored account 1500, 1590 can be upgraded to a new primary user account.
- a sponsored account may be upgraded for a number of reasons. For example, when the sponsored account holder is a minor, the account may be upgraded to a primary account when the minor reaches the age of majority. The primary account holder may pre- authorize the upgrade based on a certain date in the future, a birth date of the sponsored account holder, or the primary account holder may authorize the upgrade for immediate effect. The system may then present the upgraded account holder with options for applying for and retaining external funding sources 2100.
- the sponsor must close and delete the sponsored account before the sponsored account holder can initiate registration of a Primary Account using the same identifier, such as an email address.
- Fig. 31 is a flow diagram illustrating another example method 4000 for opening a sponsored account.
- a request is made to register a new electronic payment account.
- the new account request may include account profile information for the applicant, including information indicating the applicant's age.
- an age verification is performed at step 4040 to determine the age of the applicant. If the applicant is of legal age (e.g., 18 years), then a standard account registration process proceeds at step 4060. If the applicant is not of legal age (e.g., under 18 years), then the method proceeds to step 4080.
- the underage applicant may submit a request for a sponsored account.
- An example user interface e.g., web page
- a potential sponsor e.g., a person over the age of 18 such as a parent or guardian
- the request may be initiated by entering the potential sponsor's name, email address and a free-text message into fields provided on the user interface and then clicking on a "continue" button.
- the applicant may be required to verify his or her email address before the sponsored account request is transmitted.
- a verification code may be emailed to the applicant, and the applicant may be required to enter the verification code before the sponsored account request is processed, as illustrated in Fig. 33.
- the applicant may be linked to an account summary web page, as illustrated in Fig. 34.
- the potential sponsor may accept or deny the request to sponsor an account. If the potential sponsor already has an electronic payment account, then when they sign-in to their account, a message may be provided to indicate that one or more sponsored account requests are pending, as illustrated in Fig. 36. In the example shown in Fig. 36, the potential sponsor is also provided with a link to a sponsored accounts page, an example of which is illustrated in Fig. 37.
- the potential sponsor may select the name of the person requesting sponsorship to be linked to another page, as illustrated in Fig. 38, where they can view the message from the requestor, the profile details registered by the requestor, and choose to accept or reject the sponsorship request.
- the potential sponsor may also be provided with links for requesting more information about sponsored accounts or the security features of a sponsored account.
- step 4160 upon acceptance of the request for sponsorship (step 4160), the account is activated and the sponsor can transfer funds to the sponsored account in step 4200.
- An email may also be sent to the new sponsored account holder to confirm that the sponsorship request has been accepted.
- An example notification that sponsorship has been accepted is illustrated in Fig. 39.
- the prospective sponsored account holder may be able to sign into their pending account, for example to check the status of a pending request, to delete the pending account, to send a new sponsorship request, or to make an electronic inquiry with the electronic payment service.
- a message may be provided to show the status of the pending request, as illustrated in the example of Fig. 41.
- the user may be provided with an option to click on a "delete my account" link, as illustrated in Fig. 41, to direct the user to another page for closing the pending account, as illustrated in the example of Fig. 42.
- Fig. 41 the user may be provided with an option to click on a "delete my account" link, as illustrated in Fig. 41, to direct the user to another page for closing the pending account, as illustrated in the example of Fig. 42.
- the user is directed to enter their account password and then click on a "yes, close it" button to close the pending account.
- the user may, for example, be directed to a new web page that confirms that the account has been closed, as illustrated in the example shown in Fig. 43.
- the account may be temporarily suspended. For example, the user may receive a message as illustrated in Fig. 45 indicating that no new sponsorship requests may be sent at the current time. While the account is suspended, the "send new sponsor request" link may be hidden from the user and other functionality of the pending sponsored account may be disabled.
- a set period of time e.g. 24 hours
- the pending sponsored account may also provide the user with the ability to enter a query to the electronic payment service, as illustrated in the example shown in Fig. 47. While the account is pending, this may, for example, be limited to general and feedback queries and the ability to view pending and closed queries.
- Fig. 48 illustrates exemplary hardware 5010 on which the various embodiments of the sponsored account system may be practiced.
- the hardware described in Fig. 48 is exemplary hardware for the user site (1050) of Fig. 5.
- the hardware 5010 may be a personal computer system comprised of a computer 5012 having as input devices keyboard 5014, mouse 5016, and microphone 5018. Output devices such as a monitor 5020 and speakers 5022 may also be provided.
- the reader will recognize that other types of input and output devices may be provided and that the present invention is not limited by the particular hardware configuration.
- Embodiments of the subject matter and the functional operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them.
- Embodiments of the subject matter described in this specification can be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer-readable medium for execution by, or to control the operation of, data processing apparatus.
- the computer-readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more of them.
- data processing apparatus encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers.
- the apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them,
- a propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.
- a computer program (also known as a program, software, software application, script, or code), can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment,
- a computer program does not necessarily correspond to a file in a file system.
- a program can be stored in a portion of a file that holds other programs or data (e.g., on or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code).
- a computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.
- the processes and logic flows described in this specification can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output.
- the processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
- processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer.
- a processor will receive instructions and data from a read-only memory or a random access memory or both.
- the essential elements of a computer are a processor for performing instructions and one or more memory devices for storing instructions and data.
- a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.
- mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.
- a computer need not have such devices.
- a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio player, a Global Positioning System (GPS) receiver, to name just a few.
- Computer-readable media suitable for storing computer program instructions and data include all forms of nonvolatile memory, media, and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
- the processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.
- embodiments of the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) to LCD (liquid crystal display) monitor, for displaying information to the user and a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer.
- a display device e.g., a CRT (cathode ray tube) to LCD (liquid crystal display) monitor
- keyboard and a pointing device e.g., a mouse or a trackball
- Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any from, including acoustic, speech, or tactile input.
- Embodiments of the subject matter described in this specification can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back-end, middleware, or front-end components.
- the components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet.
- LAN local area network
- WAN wide area network
- the computing system can include clients and servers.
- a client and server are generally remote from each other and typically interact through a communication network.
- the relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
Abstract
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
BR112012009786-5A BR112012009786A2 (en) | 2009-10-29 | 2010-10-28 | computer-implemented payment system, method for creating an electronic payment account, method for processing a transaction between a secondary payer and a payee to store data for access by an account processor in an electronic payment system. |
AU2010313414A AU2010313414A1 (en) | 2009-10-29 | 2010-10-28 | Sponsored accounts for computer-implemented payment system |
RU2012116912/08A RU2579979C2 (en) | 2009-10-29 | 2010-10-28 | Sponsored accounts for computer-implemented payment system |
CN2010800601569A CN102667837A (en) | 2009-10-29 | 2010-10-28 | Sponsored accounts for computer-implemented payment system |
CA2778984A CA2778984A1 (en) | 2009-10-29 | 2010-10-28 | Sponsored accounts for computer-implemented payment system |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US25613609P | 2009-10-29 | 2009-10-29 | |
US61/256,136 | 2009-10-29 | ||
US12/778,479 | 2010-05-12 | ||
US12/778,479 US20100223184A1 (en) | 2006-10-11 | 2010-05-12 | Sponsored Accounts For Computer-Implemented Payment System |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011053718A1 true WO2011053718A1 (en) | 2011-05-05 |
Family
ID=43922547
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2010/054533 WO2011053718A1 (en) | 2009-10-29 | 2010-10-28 | Sponsored accounts for computer-implemented payment system |
Country Status (7)
Country | Link |
---|---|
US (1) | US20100223184A1 (en) |
CN (1) | CN102667837A (en) |
AU (2) | AU2010313414A1 (en) |
BR (1) | BR112012009786A2 (en) |
CA (1) | CA2778984A1 (en) |
RU (1) | RU2579979C2 (en) |
WO (1) | WO2011053718A1 (en) |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2020209990A1 (en) * | 2019-04-12 | 2020-10-15 | Mastercard International Incorporated | Systems and methods for use in facilitating network transactions |
US11568395B2 (en) | 2018-02-28 | 2023-01-31 | Mastercard International Incorporated | Systems and methods for use in facilitating network transactions |
Families Citing this family (81)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7866551B2 (en) | 2007-02-15 | 2011-01-11 | Visa U.S.A. Inc. | Dynamic payment device characteristics |
US9990674B1 (en) | 2007-12-14 | 2018-06-05 | Consumerinfo.Com, Inc. | Card registry systems and methods |
US10008067B2 (en) * | 2008-06-16 | 2018-06-26 | Visa U.S.A. Inc. | System and method for authorizing financial transactions with online merchants |
US8312033B1 (en) | 2008-06-26 | 2012-11-13 | Experian Marketing Solutions, Inc. | Systems and methods for providing an integrated identifier |
US8060424B2 (en) | 2008-11-05 | 2011-11-15 | Consumerinfo.Com, Inc. | On-line method and system for monitoring and reporting unused available credit |
US9715681B2 (en) | 2009-04-28 | 2017-07-25 | Visa International Service Association | Verification of portable consumer devices |
US8326759B2 (en) * | 2009-04-28 | 2012-12-04 | Visa International Service Association | Verification of portable consumer devices |
US9105027B2 (en) | 2009-05-15 | 2015-08-11 | Visa International Service Association | Verification of portable consumer device for secure services |
US9038886B2 (en) | 2009-05-15 | 2015-05-26 | Visa International Service Association | Verification of portable consumer devices |
US8534564B2 (en) | 2009-05-15 | 2013-09-17 | Ayman Hammad | Integration of verification tokens with mobile communication devices |
US10846683B2 (en) | 2009-05-15 | 2020-11-24 | Visa International Service Association | Integration of verification tokens with mobile communication devices |
US8893967B2 (en) | 2009-05-15 | 2014-11-25 | Visa International Service Association | Secure Communication of payment information to merchants using a verification token |
US7891560B2 (en) * | 2009-05-15 | 2011-02-22 | Visa International Service Assocation | Verification of portable consumer devices |
US8602293B2 (en) | 2009-05-15 | 2013-12-10 | Visa International Service Association | Integration of verification tokens with portable computing devices |
US8812395B2 (en) | 2009-09-03 | 2014-08-19 | Virtual Piggy, Inc. | System and method for virtual piggybank |
CA2772382C (en) * | 2009-09-03 | 2015-09-29 | Virtual Piggy, Inc. | System and method for virtual piggybank |
AU2010289347B2 (en) * | 2009-09-03 | 2015-01-15 | Virtual Piggy, Inc. | Parent match |
BR112012008150A2 (en) * | 2009-09-03 | 2016-03-01 | Virtual Piggy Inc | system and method for checking the age of an internet user |
US8332325B2 (en) * | 2009-11-02 | 2012-12-11 | Visa International Service Association | Encryption switch processing |
US10255591B2 (en) | 2009-12-18 | 2019-04-09 | Visa International Service Association | Payment channel returning limited use proxy dynamic value |
US9424413B2 (en) | 2010-02-24 | 2016-08-23 | Visa International Service Association | Integration of payment capability into secure elements of computers |
US8140403B2 (en) | 2010-03-23 | 2012-03-20 | Amazon Technologies, Inc. | User profile and geolocation for efficient transactions |
CN103154987A (en) * | 2010-10-13 | 2013-06-12 | 诺基亚公司 | Method and apparatus for performing transactions via a sponsor account |
US8788411B2 (en) * | 2010-12-13 | 2014-07-22 | Ebay Inc. | RFID payment system |
US20120278233A1 (en) * | 2011-04-26 | 2012-11-01 | Virtual Piggy, Inc. | Virtual piggybank having dashboard and debit card |
US20120278202A1 (en) * | 2011-04-26 | 2012-11-01 | Virtual Piggy, Inc. | Virtual piggybank having quick connect |
US9965768B1 (en) | 2011-05-19 | 2018-05-08 | Amazon Technologies, Inc. | Location-based mobile advertising |
US9483606B1 (en) | 2011-07-08 | 2016-11-01 | Consumerinfo.Com, Inc. | Lifescore |
US20130060679A1 (en) * | 2011-09-06 | 2013-03-07 | Rawllin International Inc. | Third-party payments for electronic commerce |
US8515870B2 (en) * | 2011-09-06 | 2013-08-20 | Rawllin International Inc. | Electronic payment systems and supporting methods and devices |
US9106691B1 (en) | 2011-09-16 | 2015-08-11 | Consumerinfo.Com, Inc. | Systems and methods of identity protection and management |
US8738516B1 (en) | 2011-10-13 | 2014-05-27 | Consumerinfo.Com, Inc. | Debt services candidate locator |
US8762230B2 (en) * | 2011-11-02 | 2014-06-24 | Virtual Piggy, Inc. | System and method for virtual piggy bank wish-list |
US20130191898A1 (en) * | 2012-01-04 | 2013-07-25 | Harold H. KRAFT | Identity verification credential with continuous verification and intention-based authentication systems and methods |
US10282724B2 (en) | 2012-03-06 | 2019-05-07 | Visa International Service Association | Security system incorporating mobile device |
US20130282576A1 (en) * | 2012-04-24 | 2013-10-24 | Timothy Kinsey | Banking Security Feature |
US9853959B1 (en) | 2012-05-07 | 2017-12-26 | Consumerinfo.Com, Inc. | Storage and maintenance of personal data |
US20140053252A1 (en) * | 2012-08-14 | 2014-02-20 | Opera Solutions, Llc | System and Method for Secure Document Distribution |
US9654541B1 (en) | 2012-11-12 | 2017-05-16 | Consumerinfo.Com, Inc. | Aggregating user web browsing data |
US9916621B1 (en) | 2012-11-30 | 2018-03-13 | Consumerinfo.Com, Inc. | Presentation of credit score factors |
US8972296B2 (en) * | 2012-12-31 | 2015-03-03 | Ebay Inc. | Dongle facilitated wireless consumer payments |
US10102570B1 (en) | 2013-03-14 | 2018-10-16 | Consumerinfo.Com, Inc. | Account vulnerability alerts |
US9406085B1 (en) | 2013-03-14 | 2016-08-02 | Consumerinfo.Com, Inc. | System and methods for credit dispute processing, resolution, and reporting |
US10685398B1 (en) | 2013-04-23 | 2020-06-16 | Consumerinfo.Com, Inc. | Presenting credit score information |
US9830673B2 (en) * | 2013-04-26 | 2017-11-28 | Roche Diabetes Care, Inc. | System portal control for a diabetes management system |
JP6098400B2 (en) * | 2013-07-01 | 2017-03-22 | 富士ゼロックス株式会社 | Information processing apparatus and program |
US10325314B1 (en) | 2013-11-15 | 2019-06-18 | Consumerinfo.Com, Inc. | Payment reporting systems |
US9477737B1 (en) | 2013-11-20 | 2016-10-25 | Consumerinfo.Com, Inc. | Systems and user interfaces for dynamic access of multiple remote databases and synchronization of data based on user rules |
CN105830107A (en) | 2013-12-19 | 2016-08-03 | 维萨国际服务协会 | Cloud-based transactions methods and systems |
US9922322B2 (en) | 2013-12-19 | 2018-03-20 | Visa International Service Association | Cloud-based transactions with magnetic secure transmission |
US10176542B2 (en) * | 2014-03-24 | 2019-01-08 | Mastercard International Incorporated | Systems and methods for identity validation and verification |
US9892457B1 (en) | 2014-04-16 | 2018-02-13 | Consumerinfo.Com, Inc. | Providing credit data in search results |
US10846694B2 (en) | 2014-05-21 | 2020-11-24 | Visa International Service Association | Offline authentication |
US9775029B2 (en) | 2014-08-22 | 2017-09-26 | Visa International Service Association | Embedding cloud-based functionalities in a communication device |
US10187363B2 (en) | 2014-12-31 | 2019-01-22 | Visa International Service Association | Hybrid integration of software development kit with secure execution environment |
US10304101B2 (en) * | 2015-02-17 | 2019-05-28 | Mastercard International Incorporated | Age verification through mobile wallet method and apparatus |
US20160247132A1 (en) * | 2015-02-25 | 2016-08-25 | Ebay Inc. | Affiliated individual identification and account recoupment |
US20160292753A1 (en) * | 2015-03-30 | 2016-10-06 | Mastercard International Incorporated | Systems and Methods for Generating Donations From Payment Account Transactions |
CN106302305A (en) * | 2015-05-11 | 2017-01-04 | 阿里巴巴集团控股有限公司 | A kind of transaction methods and system |
CN105069618A (en) * | 2015-07-23 | 2015-11-18 | 北京盛世光明软件股份有限公司 | Student payment system and application method thereof |
US10068210B2 (en) | 2015-09-25 | 2018-09-04 | Everi Payments Inc. | Casino cash system, apparatus and method utilizing integrated circuit cards |
US10496968B2 (en) | 2015-09-25 | 2019-12-03 | Everi Payments Inc. | Financial terminal that automatically reconfigures into different financial processing terminal types |
US20170116604A1 (en) | 2015-10-21 | 2017-04-27 | Mastercard International Incorporated | Systems and Methods for Identifying Payment Accounts to Segments |
WO2017095833A1 (en) * | 2015-11-30 | 2017-06-08 | Erik Voorhees | Systems and methods for improving security in blockchain-asset exchange |
US20170177891A1 (en) * | 2015-12-22 | 2017-06-22 | Google Inc. | Systems and methods of selection and approval of media content and applications |
US10679214B2 (en) * | 2016-03-09 | 2020-06-09 | Mastercard International Incorporation | Method and system for electronic distribution of controlled tokens |
CN106383638B (en) * | 2016-08-26 | 2021-09-03 | 维沃移动通信有限公司 | Payment mode display method and mobile terminal |
US10380662B2 (en) * | 2016-08-30 | 2019-08-13 | Ncr Corporation | Pre-verification processing |
CN109102266B (en) * | 2017-06-20 | 2022-05-17 | 腾讯科技(深圳)有限公司 | Account value transferring method and device |
US11562362B1 (en) | 2018-01-23 | 2023-01-24 | Wells Fargo Bank, N.A. | Systems and methods for a virtual identity card |
JP7403104B2 (en) * | 2018-04-19 | 2023-12-22 | ヴィチェーン ファウンデーション リミテッド | blockchain transaction processing |
CN109272342A (en) | 2018-08-06 | 2019-01-25 | 阿里巴巴集团控股有限公司 | Method for processing business and device, electronic equipment |
US20200074541A1 (en) | 2018-09-05 | 2020-03-05 | Consumerinfo.Com, Inc. | Generation of data structures based on categories of matched data items |
US11315179B1 (en) | 2018-11-16 | 2022-04-26 | Consumerinfo.Com, Inc. | Methods and apparatuses for customized card recommendations |
CN109191092A (en) * | 2018-12-06 | 2019-01-11 | 深兰人工智能芯片研究院(江苏)有限公司 | Multi-user's payment transaction cooperative processing method and system |
CA3052735C (en) | 2018-12-28 | 2021-06-22 | Alibaba Group Holding Limited | Smart contract whitelists |
RU2019104354A (en) * | 2019-02-15 | 2020-08-17 | Дмитрий Петрович Цивилёв | Method of providing a gift certificate using a physical medium with an electronic code |
US11238656B1 (en) | 2019-02-22 | 2022-02-01 | Consumerinfo.Com, Inc. | System and method for an augmented reality experience via an artificial intelligence bot |
US20200364690A1 (en) * | 2019-05-17 | 2020-11-19 | Joseph Grant Brazier, III | Financial and socio-emotional management system and process |
US11941065B1 (en) | 2019-09-13 | 2024-03-26 | Experian Information Solutions, Inc. | Single identifier platform for storing entity data |
US20240095694A1 (en) * | 2022-09-21 | 2024-03-21 | Step Mobile, Inc. | Dynamically guiding users to request valid payments |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020046341A1 (en) * | 2000-02-28 | 2002-04-18 | Alex Kazaks | System, and method for prepaid anonymous and pseudonymous credit card type transactions |
US20030097331A1 (en) * | 1998-03-30 | 2003-05-22 | Cohen Morris E. | Systems for financial and electronic commerce |
US20040039694A1 (en) * | 2001-05-29 | 2004-02-26 | American Express Travel Related Services Company, Inc. | System and method for facilitating a subsidiary card account with controlled spending capability |
US20040093303A1 (en) * | 1996-04-16 | 2004-05-13 | Picciallo Michael J. | Third party debit card |
Family Cites Families (96)
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 |
US4454414A (en) * | 1982-06-16 | 1984-06-12 | Vericard Corporation | Funds transfer system using optically coupled, portable modules |
US4645873A (en) * | 1985-01-23 | 1987-02-24 | Telecue Systems | Transactional telecommunication system |
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 |
US5025372A (en) * | 1987-09-17 | 1991-06-18 | Meridian Enterprises, Inc. | System and method for administration of incentive award program through use of credit |
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 |
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 |
US5640577A (en) * | 1991-12-30 | 1997-06-17 | Davox Corporation | Data processing system with automated at least partial forms completion |
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 |
US5745574A (en) * | 1995-12-15 | 1998-04-28 | Entegrity Solutions Corporation | Security infrastructure for electronic transactions |
US5862325A (en) * | 1996-02-29 | 1999-01-19 | Intermind Corporation | Computer-based communication system and method using metadata defining a control structure |
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 |
US6192407B1 (en) * | 1996-10-24 | 2001-02-20 | Tumbleweed Communications Corp. | Private, trackable URLs for directed document delivery |
US6164528A (en) * | 1996-12-31 | 2000-12-26 | Chequemark Patent, Inc. | Check writing point of sale system |
USRE40220E1 (en) * | 1996-12-31 | 2008-04-08 | Lml Patent Corp. | 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 |
US7324972B1 (en) * | 1997-03-07 | 2008-01-29 | Clickshare Service Corporation | Managing transactions on a network: four or more parties |
RU2117328C1 (en) * | 1998-02-12 | 1998-08-10 | Акционерное общество закрытого типа "Степ Ап" | Method for remote bank services |
US7533064B1 (en) * | 1998-10-07 | 2009-05-12 | Paypal Inc. | E-mail invoked electronic commerce |
US7334184B1 (en) * | 1999-03-10 | 2008-02-19 | American Express Travel Related Services Company, Inc. | Method for online information sharing for completing electronic forms |
US6227447B1 (en) * | 1999-05-10 | 2001-05-08 | First Usa Bank, Na | Cardless payment system |
US7194437B1 (en) * | 1999-05-14 | 2007-03-20 | Amazon.Com, Inc. | Computer-based funds transfer system |
WO2000073934A2 (en) * | 1999-05-28 | 2000-12-07 | The Coca-Cola Company | Method and apparatus for surrogate control of network-based electronic transactions |
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 |
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 |
US7366703B2 (en) * | 2000-01-05 | 2008-04-29 | American Express Travel Related Services Company, Inc. | Smartcard internet authorization system |
US7328189B2 (en) * | 2000-01-26 | 2008-02-05 | Paybyclick Corporation | Method and apparatus for conducting electronic commerce transactions using electronic tokens |
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 |
AUPQ564400A0 (en) * | 2000-02-16 | 2000-03-09 | Ong, Yong Kin (Michael) | Electronic credit card-ecc |
US7379919B2 (en) * | 2000-04-11 | 2008-05-27 | Mastercard International Incorporated | Method and system for conducting secure payments over a computer network |
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 |
US7702580B1 (en) * | 2000-06-13 | 2010-04-20 | Fannie Mae | System and method for mortgage loan pricing, sale and funding |
US7430537B2 (en) * | 2000-07-10 | 2008-09-30 | Paypal, Inc. | System and method for verifying a financial instrument |
US8452704B2 (en) * | 2000-07-11 | 2013-05-28 | Citicorp Credit Services, Inc. | Method and system for on-line payments |
US7454376B1 (en) * | 2000-07-21 | 2008-11-18 | Argenbright Stephen G | Online investment trust creation and management |
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 |
US7337144B1 (en) * | 2000-09-28 | 2008-02-26 | Microsoft Corporation | Method and system for restricting the usage of payment accounts |
US20020052841A1 (en) * | 2000-10-27 | 2002-05-02 | Guthrie Paul D. | Electronic payment system |
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 |
US7020645B2 (en) * | 2001-04-19 | 2006-03-28 | Eoriginal, Inc. | Systems and methods for state-less authentication |
DE60221988T2 (en) * | 2001-05-02 | 2008-05-15 | Virtual Access Ltd. | SECURED PAYMENT METHOD AND SYSTEM |
US7502833B2 (en) * | 2001-05-11 | 2009-03-10 | International Business Machines Corporation | Method for dynamically integrating remote portlets into portals |
US7174302B2 (en) * | 2001-06-11 | 2007-02-06 | Evolution Benefits, Inc. | System and method for processing flexible spending account transactions |
US7266840B2 (en) * | 2001-07-12 | 2007-09-04 | Vignette Corporation | Method and system for secure, authorized e-mail based transactions |
WO2003017049A2 (en) * | 2001-08-15 | 2003-02-27 | Shea Writer | Methods for verifying cardholder authenticity and for creating billing address database |
US20030041111A1 (en) * | 2001-08-27 | 2003-02-27 | Delaney Beth M.P. | System for emailing images with audio as a separate file |
US20030061111A1 (en) * | 2001-09-26 | 2003-03-27 | International Business Machines Corporation | Method and system for parent controlled e-commerce |
AU2002340138A1 (en) * | 2001-10-09 | 2003-04-22 | Joanna Sandorffy | System and method for conducting a financial transaction using a communication device |
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 |
US6901387B2 (en) * | 2001-12-07 | 2005-05-31 | General Electric Capital Financial | Electronic purchasing method and apparatus for performing the same |
US7159180B2 (en) * | 2001-12-14 | 2007-01-02 | America Online, Inc. | Proxy platform integration system |
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 |
US7519560B2 (en) * | 2002-05-24 | 2009-04-14 | Jpmorgan Chase Bank, N.A. | System and method for electronic authorization of batch checks |
CN2544351Y (en) * | 2002-08-15 | 2003-04-09 | 中国工商银行 | One Card two auounts bank card processor |
US7280981B2 (en) * | 2002-08-27 | 2007-10-09 | Visa U.S.A. Inc. | Method and system for facilitating payment transactions using access devices |
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 |
US8204806B2 (en) * | 2002-12-23 | 2012-06-19 | United Services Automobile Association (Usaa) | System and method of processing account information over a computer network |
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 |
KR100439437B1 (en) * | 2003-12-18 | 2004-07-09 | 주식회사 교원나라 | Bank transaction system for linked accounts via common account |
US7660779B2 (en) * | 2004-05-12 | 2010-02-09 | Microsoft Corporation | Intelligent autofill |
CN1758290B (en) * | 2004-07-02 | 2010-08-18 | 招商银行股份有限公司 | Supplementary card system of bank debit card and treatment method thereof |
US7694135B2 (en) * | 2004-07-16 | 2010-04-06 | Geotrust, Inc. | Security systems and services to provide identity and uniform resource identifier verification |
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 |
US7347361B2 (en) * | 2005-06-13 | 2008-03-25 | Robert Lovett | System, method and program product for account transaction validation |
US7664699B1 (en) * | 2005-12-21 | 2010-02-16 | Symantec Corporation | Automatic generation of temporary credit card information |
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 |
WO2007127411A2 (en) * | 2006-04-28 | 2007-11-08 | Efunds Corporation | Methods and systems for opening and funding a financial account online |
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 |
BRPI0715571A2 (en) * | 2006-10-11 | 2013-07-02 | Visa Int Service Ass | Method for processing a micropayman transmission, Method for processing a transaction between a payer and a trusted payee, and Method by which a trusted payee can engage in a transaction with a registered payer |
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 |
CN101216928A (en) * | 2007-01-05 | 2008-07-09 | 谭伏根 | A membership card of card-to-card foundation transferring and management and settlement system |
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 |
US7567920B2 (en) * | 2007-11-01 | 2009-07-28 | Visa U.S.A. Inc. | On-line authorization in access environment |
-
2010
- 2010-05-12 US US12/778,479 patent/US20100223184A1/en not_active Abandoned
- 2010-10-28 BR BR112012009786-5A patent/BR112012009786A2/en not_active Application Discontinuation
- 2010-10-28 AU AU2010313414A patent/AU2010313414A1/en not_active Abandoned
- 2010-10-28 WO PCT/US2010/054533 patent/WO2011053718A1/en active Application Filing
- 2010-10-28 RU RU2012116912/08A patent/RU2579979C2/en active
- 2010-10-28 CN CN2010800601569A patent/CN102667837A/en active Pending
- 2010-10-28 CA CA2778984A patent/CA2778984A1/en not_active Abandoned
-
2016
- 2016-05-06 AU AU2016202922A patent/AU2016202922A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040093303A1 (en) * | 1996-04-16 | 2004-05-13 | Picciallo Michael J. | Third party debit card |
US20030097331A1 (en) * | 1998-03-30 | 2003-05-22 | Cohen Morris E. | Systems for financial and electronic commerce |
US20020046341A1 (en) * | 2000-02-28 | 2002-04-18 | Alex Kazaks | System, and method for prepaid anonymous and pseudonymous credit card type transactions |
US20040039694A1 (en) * | 2001-05-29 | 2004-02-26 | American Express Travel Related Services Company, Inc. | System and method for facilitating a subsidiary card account with controlled spending capability |
Cited By (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11568395B2 (en) | 2018-02-28 | 2023-01-31 | Mastercard International Incorporated | Systems and methods for use in facilitating network transactions |
WO2020209990A1 (en) * | 2019-04-12 | 2020-10-15 | Mastercard International Incorporated | Systems and methods for use in facilitating network transactions |
Also Published As
Publication number | Publication date |
---|---|
RU2012116912A (en) | 2013-12-10 |
BR112012009786A2 (en) | 2020-09-01 |
CA2778984A1 (en) | 2011-05-05 |
AU2010313414A1 (en) | 2012-05-17 |
AU2016202922A1 (en) | 2016-05-26 |
US20100223184A1 (en) | 2010-09-02 |
RU2579979C2 (en) | 2016-04-10 |
CN102667837A (en) | 2012-09-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10984403B2 (en) | Systems and methods for brokered authentification express seller links | |
US20100223184A1 (en) | Sponsored Accounts For Computer-Implemented Payment System | |
JP5351887B2 (en) | Method, system, computer readable medium, server, and computer machine for performing a transaction | |
US11676136B1 (en) | Payment vehicle with on and off function | |
US8762275B2 (en) | Systems and methods providing multiple account holder functionality | |
JP6698025B2 (en) | System and method for money management | |
US8589297B2 (en) | Prepaid value account with reversion to purchaser systems and methods | |
US8676639B2 (en) | System and method for promotion processing and authorization | |
JP6080133B2 (en) | System and method for electronic purchase party verification and credit assessment | |
US8335745B2 (en) | Method and system for processing micropayment transactions | |
US20100063903A1 (en) | Hierarchically applied rules engine ("hare") | |
US20140372297A1 (en) | Related party payment system | |
US20120179558A1 (en) | System and Method for Enhancing Electronic Transactions | |
US20110106674A1 (en) | Optimizing Transaction Scenarios With Automated Decision Making | |
WO2012116221A1 (en) | Demand deposit account payment system | |
US20150026037A1 (en) | System, method and apparatus to provide a multi-channel retail layaway service using physical retail point-of-sale and on-line virtual payment systems | |
US20110078042A1 (en) | System and method for facilitating electronic commerce with controlled spending over a network | |
US20200211013A1 (en) | Intelligent recommendations for dynamic policies used in real-time transactions | |
US11922445B1 (en) | Using native and non-native events to control funding/actions on various connected digital platforms |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 10827482 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010313414 Country of ref document: AU |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2778984 Country of ref document: CA |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 3773/DELNP/2012 Country of ref document: IN |
|
ENP | Entry into the national phase |
Ref document number: 2010313414 Country of ref document: AU Date of ref document: 20101028 Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2012116912 Country of ref document: RU |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 10827482 Country of ref document: EP Kind code of ref document: A1 |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112012009786 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 112012009786 Country of ref document: BR Kind code of ref document: A2 Effective date: 20120426 |