US Patent No. 8249986 - Prepared by Attorney David Tran for Paypal/eBay and filed by Schwegman (SLWK)
Brief description: A funds transfer module(s) 230 may include a verification/approval module(s) 231. The verification/approval module(s) 231 may be configured to verify whether the secondary account may transact given limits placed within the primary account holder management modules 240. Further, the verification/approval module(s) 231 may be configured to permit the primary account holder to approve transactions with the respect to the secondary account holder. The primary account holder may set up a secure channel for authorizing payment to/from the secondary account holder, transactions involving the secondary account holder, communications to/from the secondary account holder, and secondary account viewing. The primary account holder may set up reporting with regard to the secure channel and may set up blocks as discussed herein. Transactions may be subject to verification by the primary account holder based on configured rules. In one configured rule, communications and transactions may be established by viral sign-up, for example, account holders (primary and/or secondary) may invite communication and transactions with third parties. If a third party has not been invited, no communications or transactions with the account holder(s) may be permitted. Verification and approval module(s) 231 may include analysis of transfers to and from the secondary account, according to parameters set by the primary account holder. Transactions may be approved/disapproved automatically per the monitoring and approval(s) table 316 (saved entries) or they may be approved/disapproved individually, for instance. In instances where the primary account holder set to approve certain or all transactions, the transfer occurs upon such approval. The verification module(s) 231 may communicate with a third party application 138 executing on a third party server 140 to determine if an offer by the third party still exists, if the price of the offer has changed, and/or to determine if the product is in stock, for example. The third party may receive, from the payment module(s) and/or verification module(s): order information, shipment information, and an associated payment and/or payment confirmation. The third party application 138 may receive and process the order, send a virtual receipt to the payment module(s) 132, and forward the order to the client user (either or both the primary and secondary account holders), as set by the primary account holder. For services and/or donations, the third party may receive a requested order and the payment confirmation, exclusive of the user contact information, such as a shipment address. In an additional embodiment, the service provider or charity may receive client user contact information and may send a receipt to the client user. In particular, the verification module(s) may access a database associated with the third party server or associated with the database server(s) 134. A secondary account holder management module 262 may be configured to enable privacy for transactions associated with the secondary account with respect to the primary account. In one example, the secondary account holder may control what the primary account holder may view concerning the secondary account. For instance, the secondary account holder may transfer in funds from an outside funding source into the account and make a purchase, both of which may be unknown to the primary account holder. The secondary account may include an independent source portion and a dependent source portion. The dependent source portion of the secondary account may be subject to control by the primary account holder management module and the secondary account holder management module. However, the independent source portion of the secondary account may be subject to control only by the secondary account holder management module. A source of the independent source portion may include funds earned by the secondary account holder. The secondary account holder management module may be configured to enable privacy for transactions associated with the independent source portion with respect to the primary account holder management module. The secondary account holder management module may be configured to enable privacy for transactions associated with the dependent source portion with respect to the primary account holder management module.