US20090106118A1 - Payment using funds pushing - Google Patents
Payment using funds pushing Download PDFInfo
- Publication number
- US20090106118A1 US20090106118A1 US11/962,733 US96273307A US2009106118A1 US 20090106118 A1 US20090106118 A1 US 20090106118A1 US 96273307 A US96273307 A US 96273307A US 2009106118 A1 US2009106118 A1 US 2009106118A1
- Authority
- US
- United States
- Prior art keywords
- account
- amount
- paid
- party
- email address
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
-
- 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/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
- G06Q30/00—Commerce
- G06Q30/06—Buying, selling or leasing transactions
- G06Q30/0601—Electronic shopping [e-shopping]
Abstract
Apparatus, systems, and methods may operate to present, via a networked client coupled to a first financial entity, a graphical user interface including an account associated with a first party, an amount to be paid, and an email address associated with a second party. Further activities may include receiving an indication from the graphical user interface to transfer, via a selected payment processor, the amount to be paid from the account associated with the first party and held by the first financial entity to an account linked to the email address. The amount to be paid may then be pushed from the account held by the first financial entity directly to the selected payment processor. Additional apparatus, systems, and methods are disclosed.
Description
- This disclosure claims the benefit of the filing date of U.S. Provisional Patent Application Ser. No. 60/981,402, filed on Oct. 19, 2007, and titled “Payment Using Funds Pushing.” It is commonly assigned to the assignee of the instant application, eBay, Inc., and is incorporated herein by reference in its entirety.
- The Internet and the World Wide Web (“Web”) have changed the landscape of information delivery and affected numerous aspects of life, including electronic commerce and entertainment. One area that has benefited from this technological development is the ability for individuals to buy and sell products over the Internet. The resulting growth of electronic commerce has encouraged many businesses to join hands in doing business and in sharing customers and their information. The overlapping businesses, partnerships in conducting business, referrals, mutual distribution of resources, and sharing of users and user information has created a network of applications, servers, and Websites which has created various technical challenges, complexities, and insecurities.
- Some embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings in which:
-
FIG. 1 is a high level diagram illustrating payment using funds pushing according to various embodiments of the invention. -
FIG. 2 is a simplified diagram illustrating an example graphical user interface according to various embodiments of the invention. -
FIG. 3 is a block diagram illustrating another example of a graphical user interface according to various embodiments of the invention. -
FIG. 4 is a block diagram of apparatus and systems according to various embodiments of the invention. -
FIG. 5 is a flow diagram illustrating methods according to various embodiments of the invention. -
FIG. 6 is a flow diagram illustrating additional methods according to various embodiments of the invention. -
FIG. 7 is a block diagram illustrating a client-server architecture to facilitate payment using funds pushing according to various embodiments of the invention. -
FIG. 8 is a block diagram of a machine in the example form of a computer system according to various embodiments of the invention. - The inventors have discovered that there is a demand from consumers for substantially-instantaneous settlement when funds are moved between various entities. For example, conventional mechanisms include the use of the Automated Clearing House (ACH) to transfer funds from a bank to a vendor. Faster methods, such as credit card payment, often result in relatively steep fees for service.
- To address these challenges, among others, the inventors have discovered a mechanism for pushing funds directly from a financial entity, such as a bank, to a payment processor (e.g., PayPal, Inc. a subsidiary of eBay Inc. of San Jose, Calif.), based on an email address. If the owner of the email address has another financial entity account linked to the email address, then the funds can be immediately swept by the payment processor into the linked account.
- For the purposes of this document, the term “agent” shall be taken to include, but not be limited to, a person or a machine (e.g. Automated Teller Machine (ATM)) that is capable of taking some kind of identification (e.g., driver license, passport, other valid identification cards, or biometric identification) to verify the identity of a customer.
- For the purposes of this document, the term “email account” shall be taken to include, but not be limited to, an account associated with an email address. An email account may be distinguished from a normal account in several ways, including the manner in which the account may be accessed.
- For the purposes of this document, the term “normal account” shall be taken to include, but not be limited to, any account other than a mobile account.
- Some embodiments described herein enable a user to remit an amount from his/her financial entity account to one or more mobile phone numbers associated with one or more second parties (e.g., persons who may or may not have any bank accounts). The second party may be notified of the amount and the identification of the remitting party. The second party may spend any part of the received amount by transferring that portion to another account (e.g., a second party's account or a third party's account in the same financial entity or at other financial institutions or banks), receiving cash at an agent, or shopping at a vendor's business.
- Some embodiments may include receiving a request, at a financial entity and from a first party, to remit an amount (e.g. $100) from an account associated with the first party, to an account linked to an email address associated with a second party; and notifying (e.g., by calling or by sending a message such as a text message) the second party of the amount to be remitted and the identity (e.g., name and phone number or email address) of the first party.
- In some embodiments, the financial entity, having an established banking relationship with the payment processor, can push funds directly into an account held either within the financial entity by the payment processor, or by the payment processor itself. The request by the first party may be made to the financial entity using a wired or wireless terminal, including a cellular telephone, or by online via the Internet.
-
FIG. 1 is a high level diagram illustrating payment using funds pushing according to various embodiments of the invention. Here it can be seen that asystem 100 for pushing funds may operate to receive a request 140 to push funds at a first financial entity, perhaps at a firstfinancial entity server 106. The request 140 may be initiated by a first party (e.g., a person having ownership of an account held by the first financial entity), making use of aclient terminal 116 with a graphical user interface (GUI) 102. One example of such a request might embody the terms “$25” (an amount) and “payee@homepage.com” (an email address associated with a second party). - Responsive to receiving the request, the first financial entity may then push the amount to the paid (here “$25”) from the account associated with the first party directly to a selected payment processor as part of
activity 142. If the email address of the second party is linked to an account at a second financial entity, the payment processor, perhaps taking the form of apayment processor server 109, may act to push the funds to the account at the second financial entity, which may take the form of a secondfinancial entity server 111. - A
message 146 may be sent to anotherclient terminal 108, which may take the form of a cellular telephone in some embodiments, informing the second party of: the fact that a request has been made, the identity of the first party initiating the request, the identity of the first financial entity pushing the funds, the amount of funds requested to be transferred, that the funds have been successfully pushed to the payment processor, and/or that the funds have been successfully pushed to the second financial entity. - The
message 146 may also be used to inform the second party that there is no account at a second financial entity linked to the email address, and that such a link can be made. The second party may go on to establish such a link, and later request that the funds be swept from a holding account at the payment processor to the linked account. - In some embodiments, one or more banks selected by the payment processor may be offered to the second party as part of a list in the
message 146, so that when a bank is selected from the list, as part of alink request 144, an account is created substantially simultaneously at the selected bank, and the funds are then pushed into the newly-created account. The first party account may comprise a bank account, a credit/debit account, a brokerage account, and other types of accounts. - In some embodiments, the first party may visit a website associated with the first financial entity to login and complete a request form to initiate payment. After receiving the request, the first financial entity may push the requested funds to the payment processor, and then the funds may be pushed from the payment processor directly to a second financial entity having an account linked to the email address.
-
FIG. 2 is a simplified diagram illustrating an examplegraphical user interface 200 according to various embodiments of the invention Thisinterface 200 is one of many that are possible. In the particular example ofFIG. 2 , a sample web page that might be seen by an account owner that has logged into his bank account on the Internet is shown. Here, the “PAY NOW”option 204 has been selected, calling up the PAYNOW PAGE 208. This selection permits the account owner (e.g., a first party) to select aparticular account 212 that can be used to send apayment amount 216 to another account that is linked to a specifiedemail address 220. To push the funds from the account to apayment processor 222 that can make the fund transfer, and eventually, to the party that is to receive payment (e.g., a second party associated with the email address 220), the account owner might simply click on the PAYNOW widget 224. - In some embodiments, a
message field 228 in theGUI 200 may be used to inform the account owner that the transfer of funds has been completed. Other fields in theGUI 200 may be used to provide alternatives, such as anOTHER ACCOUNTS field 232, to select a particular account to use for payment, and a PAY NOWADDRESSES field 236 to select email addresses, such as from an address book, to be paid. While not shown inFIG. 2 , those of ordinary skill in the art will realize that multiple email addresses may be specified so that thepayment amount 216 can be sent to multiple addressees at the same time. In this case, atotal amount field 240 may be used to reflect the total amount of funds to be paid/pushed. -
FIG. 3 is a block diagram illustrating another example of agraphical user interface 300 according to various embodiments of the invention. Thisinterface 300 is one of many that are possible. In the particular example ofFIG. 3 , a sample web page that might be seen by an account owner that has logged into his bank account on the Internet is shown. Here, the “AGGREGATE PAY”option 344 has been selected, calling up the BIG BANK AGGREGATE PAY PAGE 348. This selection permits the account owner (e.g., a first party) to select several accounts 352 (e.g., accounts shown to be held by BIG BANK, LITTLE BANK, and BROKER) in the aggregate pay nowwindow 354 that can be used to send apayment amount 316 to another account that is linked to a specifiedemail address 320. To push the funds from the selectedaccounts 352 to apayment processor 322 that can make the fund transfer, and eventually, to the party that is to receive payment (e.g., a second party associated with the email address 320), the account owner might simply click on the PAYNOW widget 324. - When using the aggregate pay function,
multiple accounts 352 from a variety of financial entities can be used to make a payment. The order of funds withdrawal can be specified with the payorder indicator windows 356, so that when thetotal payment amount 340 is greater than the balance of funds in the first account indicated in the pay order indicator windows 356 (e.g., the first account held by BROKER has $500.00 on hand, while the total payment amount is $550.00), additional funds may be aggregated from other accounts (e.g., the second in order, which is the BIG BANK account that has $100.00), and the necessary funds to make up the needed payment can be provided. Theaccounts 352 used for aggregation can be added and removed as desired, and other accounts may be selected (e.g., the CREDIT UNION account shown in the OTHER ACCOUNTS field 332 window 360). - In some embodiments, a
message field 328 in theGUI 300 may be used to inform the account owner that the transfer of funds has been completed. Other fields in theGUI 300 may be used to provide alternatives, such as an OTHER ACCOUNTSfield 332, to add or remove a particular account to use for payment, and a PAY NOW ADDRESSESfield 336 to select email addresses, such as from an address book, to be paid. While not shown inFIG. 3 , those of ordinary skill in the art will realize that multiple email addresses may be specified so that thepayment amount 316 can be sent to multiple addressees at the same time. Thetotal amount field 340 can be used to reflect the total amount of funds to be paid/pushed. -
FIG. 4 is a block diagram ofapparatus 402 andsystems 410 according to various embodiments of the invention. Theapparatus 402 can take many forms, such as an automated teller machine (ATM), a cellular telephone, a desktop computer terminal with Internet access, etc. - In some embodiments, the
apparatus 402 may comprise one or moreuser input devices 408, such as avoice recognition processor 416, akeypad 420, atouchscreen 424, a thumbwheel, a button, etc. Theapparatus 402 may include apayment module 428 to receive arequest 414 initiated by theuser input device 408 to push an amount to be paid from an account associated with a first party and held by the first financial entity directly to an account linked to an email address associated with a second party via a selected payment processor. Theapparatus 402 may further comprise acellular telephone transceiver 406 to transmit a message associated with therequest 414, wherein the message is to be sent to the email address. Thus, an account owner at the first financial entity might use his cell phone to push funds directly from his bank to the payment processor, and send a message at the time the funds are moved to the payment processor. - Other embodiments may be realized. For example, a
system 410 may comprise one or more of theapparatus 402. Thus, asystem 410 may comprise afirst client terminal 402 having auser input device 408, aclient module 432, and apayment module 428 to receive arequest 414 initiated by theuser input device 408. - The
system 410 may further include aserver 430 having afunds transfer module 438 associated with an account associated with a first party and held by a first financial entity. Therequest 414 may be to push an amount to be paid from the account associated with the first party directly to an account linked to an email address associated with a second party via a selected payment processor. Thefunds transfer module 438 may be used to effect the direct transfer of the amount to be paid to the selected payment processor responsive to receiving therequest 414. Thus, aclient terminal 402 and abank server 430 may cooperate to push funds, in contrast with the conventional process of “pulling” funds from the bank account into a payment processor by making a request from a payment processor (e.g., PayPal payment processing service request) to a bank in order to move the funds from the bank to the payment processor. - In some embodiments, the
system 410 comprises asecond client terminal 450 associated with the selected payment processor and communicatively coupled to theserver 430, perhaps via a wired orwireless network 418, including a global computer network, such as the Internet. An ATM may be used to house theuser input device 408 in some instances. -
FIG. 5 is a flowdiagram illustrating methods 511 according to various embodiments of the invention. For example, a computer-implementedmethod 511 may begin with receiving a request to purchase an item presented by an online marketplace atblock 513, and continue on to block 517 with determining the amount to be paid from a purchase price associated with the item. Thus, an online purchase might serve to initiate the funds-push process. In many cases, manual activity by a bank customer may serve to provide a request for payment, and in some instances, a request can also be made to set up periodic payments, e.g. $600 each month for rent to the landlord's email address, and so forth. Many variations are possible. - In most embodiments the
method 511 includes, atblock 521, receiving a request at a first financial entity from a first party to transfer an amount to be paid from an account associated with the first party and held by the first financial entity, to an account linked to an email address associated with a second party via a selected payment processor. In some cases, the request atblock 521 may be made when there are insufficient funds in the first party account. - Thus, the
method 511 may include determining the sufficiency of funds in the account associated with the first party to pay the amount to be paid atblock 525. If it is determined that the funds are insufficient to pay the amount to be paid atblock 525, then themethod 511 may include aggregating a total amount of available funds from other financial entities until the total amount is sufficient to pay the amount to be paid. - To accomplish the aggregation of funds, several methods may be employed. The first may be to manually aggregate funds, as shown in
FIG. 3 , where the account owner selects financial entities to supply the funds, and perhaps, the order in which funds are to be applied. - A second method might include auto-aggregation to make up for the shortfall. In this case, the
method 511 may include sending queries to aggregate information including a plurality of available transfer amounts associated with a corresponding plurality of financial entities (including the first financial entity) atblock 529, and then displaying the plurality of available transfer amounts as part of a single display page prior to pushing the amount to be paid atblock 531. Thus, inquiries can be made to gather information on money available to pay out from other accounts, and the available funds from several financial institutions can be displayed at once. - When available funds are sufficient to pay the amount requested, then the
method 511 may include pushing the amount to be paid from the account associated with the first party directly to the selected payment processor atblock 533. - The first party and first financial entity are thus the parties that pay, and the second party is the party that is paid. Essentially, using a payment processor, one can transfer money from an account at a first financial entity to an account at a second financial entity by using no more than an email address associated with the second financial entity account as the sole identifier. As a matter of contrast, the ACH network does not identify account holders by their email address, even though it may act as a processor to transfer funds between individuals holding accounts in different entities.
- A financial entity can server as a funding source for a transaction when funds are transferred. A payment processor transfers money between two accounts, but is not a source of funds. For example, the PayPal payment processing service operates to transfer money between two accounts it holds, and in the process, requests funds to be pulled from a bank account associated with the first account. In various embodiments, a bank, as a financial entity, serves as the ultimate source of funds, and can push them to a payment processor directly, without receiving a request from the payment processor to pull them.
- In some embodiments, the
method 511 includes determining whether an account is linked to the email address atblock 551. If a link does not exist (e.g., there is no bank account linked to the email address), themethod 511 may include creating, by the selected payment processor, an account linked to the email address as a holding account responsive to receiving the amount to be paid, and then holding the amount to be paid in the holding account atblock 541. Themethod 511 may then continue on to block 545 with sending a request, to the second party, to link an account held by a second financial entity (e.g., another bank) to the email address. That is, themethod 511 may include sending a message to the email address requesting the second party to establish an account associated with a second financial entity to link to the email address. Thus, if there is no bank account linked to the email address, a request can be made to get one. Once the link is made, themethod 511 may include receiving a notification that the account associated with the second financial entity has been established atblock 549. - If the determination is made at
block 551 that an account is linked to the specified email address, then themethod 511 may include pushing the amount to be paid from the selected payment processor directly to the account linked to the email address atblock 555. In some cases, themethod 511 may include, responsive to receiving the notification atblock 549, automatically sweeping the amount to be paid from the selected payment processor directly to the account associated with the second financial entity. The auto-sweep operation may even operate to sweep funds into a credit card account. Themethod 511 may conclude atblock 559 with notifying the second party of the amount to be paid by sending an email message to the email address. -
FIG. 6 is a flow diagram illustratingadditional methods 611 according to various embodiments of the invention. In some embodiments, a computer-implementedmethod 611 may begin atblock 613 with presenting, via a networked client coupled to a first financial entity, a graphical user interface (GUI) including an account associated with a first party, an amount to be paid, and an email address associated with a second party. Themethod 611 may continue on to block 617 with presenting a single payment widget as part of the GUI (e.g., a “pay now” button). - In most embodiments, the
method 611 may include, atblock 621, receiving an indication from the GUI to transfer, via a selected payment processor, the amount to be paid from the account associated with the first party and held by the first financial entity to an account linked to the email address. A few examples of many possible GUIs are shown inFIGS. 2 and 3 . - If a shortfall of funds exists in the primary payment account, as determined at
block 625, themethod 611 may include accessing an account held by another financial entity responsive to receiving the (transfer) indication atblock 627, and transferring an initial amount less than the amount to be paid from the account held by the other financial entity to the account held by the first financial entity atblock 629. This initial amount will most likely be an amount sufficient to make up the shortfall in the primary account, but can also be a greater amount, or a lesser amount (if further accounts are to be accessed and other transfers are made, until the aggregate amount is sufficient to pay the total amount requested). - As noted previously, when a request from the payment processor to the first financial entity had been made prior to the funds being transferred to the payment processor, then the funds would have been “pulled” into the financial processor. However, as a matter of contrast, in most embodiments, the
method 611 includes pushing the amount to be paid from the account held by the first financial entity (e.g., comprising a bank) directly to the selected payment processor atblock 633. That is, the funds are “pushed” to the payment processor directly from the first financial entity, without a request to pull funds being initiated by the payment processor. - As noted previously, if there is no link established between the specified email address and an account, as determined at
block 637, themethod 611 may include holding the funds pushed to the payment processor in a holding account atblock 645, sending a request to the second party to create a link between the email address and an account at a second financial entity (e.g., comprising a bank, brokerage, credit union, or credit card account) atblock 645, and then receiving notification that the link has been created atblock 649. - Once it is determined that an account is linked to the specified email address, the
method 611 may include pushing the amount to be paid from the selected payment processor directly to a credit card account linked to the email address atblock 655. In some cases, themethod 611 may also include automatically sweeping the amount to be paid from the selected payment processor to the account linked to the email address atblock 655. Themethod 611 may conclude with notifying the second party of the amount to be paid by sending a message to the email address and/or sending the message to a mobile phone number associated with the email address. The message may be used to notify the second party (e.g., payee) that he has been paid, or that he will be paid if he creates an account link, for example. - In some embodiments, an email registry can be used as an adjunct to payment processors for each of the
methods - The
methods - One of ordinary skill in the art will understand the manner in which a software program can be launched from a computer-readable medium in a computer-based system to execute the functions defined in the software program. Various programming languages may be employed to create one or more software programs designed to implement and perform the methods disclosed herein. The programs may be structured in an object-orientated format using an object-oriented language such as Java or C++. Alternatively, the programs can be structured in a procedure-orientated format using a procedural language, such as assembly or C. The software components may communicate using a number of mechanisms well known to those skilled in the art, such as application program interfaces or interprocess communication techniques, including remote procedure calls. The teachings of various embodiments are not limited to any particular programming language or environment.
- Thus, other embodiments may be realized, including a machine-readable medium (e.g., the
memories 434 ofFIG. 4 ) encoded with instructions for directing a machine to perform operations comprising any of the methods described herein. For example, some embodiments may include a machine-readable medium encoded with instructions for directing a client terminal or server to perform a variety of operations. Such operations may include any of the activities presented in conjunction with themethods -
FIG. 7 is a block diagram illustrating a client-server architecture to facilitate payment using funds pushing according to various embodiments of the invention. Thesystem 700, having a client-server architecture used for mobile remittance and/or payments. A financial platform, in the example form of a network-basedfinancial system 702, provides server-side functionality, via a network 780 (e.g., the Internet) to one or more clients.FIG. 7 illustrates, for example, a web client 706 (e.g., a browser, such as the Internet Explorer browser developed by Microsoft Corporation of Redmond, Wash.), and aprogrammatic client 708 executing onrespective client machines web client 706 andprogrammatic client 708 may include a mobile device. - Turning specifically to the network-based
financial system 702, an Application Program Interface (API)server 714 and aweb server 716 are coupled to, and provide programmatic and web interfaces respectively to, one ormore application servers 718. Theapplication servers 718 host one or morefinancial applications 720 and payment applications 722 (e.g., similar to or identical to thefunds transfer module 438 ofFIG. 4 ). Theapplication servers 718 are, in turn, shown to be coupled to one ormore database servers 724 that facilitate access to one ormore databases 726, such as registries that include links between email addresses, phone numbers, and/or financial entity accounts. - The
financial applications 720 provide a number of financial functions and services to users that access the network-basedfinancial system 702. Thepayment applications 722 facilitate payments to accounts associated with email addresses. - Further, while the
system 700 shown inFIG. 7 employs a client-server architecture, the present application is of course not limited to such an architecture, and could equally well find application in a distributed, or peer-to-peer, architecture system. The various financial andpayment applications - The
web client 706, it will be appreciated, may access the various financial andpayment applications web server 716. Similarly, theprogrammatic client 708 accesses the various services and functions provided by the financial andpayment applications API server 714. Theprogrammatic client 708 may, for example, be a payment module (e.g., similar to or identical to thepayment module 428 ofFIG. 4 ) to enable a user to request transfer of money from one or more of his/her accounts to one or more email addresses and to perform batch-mode communications between theprogrammatic client 708 and the network-basedfinancial system 702.Client applications 732 andsupport applications 734 may perform similar or identical functions. - Thus, the network-based
financial system 702 may provide a number of payment mechanisms whereby a user may request a payment from one or more of his/her accounts to a one or more email addresses. Thefinancial applications 720 may include one or more account management applications which support and provide services related to various user accounts in a financial entity (e.g. a bank). The various account management applications may also provide a number of features such as supervising account transfers, holding account balances, and keeping tracking of and reporting transactions to relevant applications. - The
financial applications 720 may also include dispute resolution applications to provide mechanisms whereby disputes arising between transacting parties may be resolved. For example, the dispute resolution applications may provide guided procedures whereby the parties are guided through a number of steps in an attempt to settle a dispute. In the event that the dispute cannot be settled via the guided procedures, the dispute may be escalated to a customer service agent for thefinancial system 702, third party mediator, or arbitrator. -
FIG. 8 is a block diagram, illustrating a diagrammatic representation ofmachine 900 in the example form of a computer system within which a set of instructions for causing the machine to perform any one or more of the methodologies discussed herein may be executed. Themachine 900 may also be similar to or identical to theclient terminal 402,server 430, orterminal 450 ofFIG. 4 . - In alternative embodiments, the
machine 900 may operate as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, themachine 900 may operate in the capacity of a server or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. - The
machine 900 may be a server computer, a client computer, a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein. - The
example computer system 900 may include a processor 902 (e.g., a central processing unit (CPU), a graphics processing unit (GPU) or both), amain memory 904 and astatic memory 906, all of which communicate with each other via abus 908. Thecomputer system 900 may further include a video display unit 910 (e.g., liquid crystal displays (LCD) or cathode ray tube (CRT)). Thecomputer system 900 also may include an alphanumeric input device 912 (e.g., a keyboard), a cursor control device 914 (e.g., a mouse), adisk drive unit 916, a signal generation device 918 (e.g., a speaker) and anetwork interface device 920. - The
disk drive unit 916 may include a machine-readable medium 922 on which is stored one or more sets of instructions (e.g., software 924) embodying any one or more of the methodologies or functions described herein. Thesoftware 924 may also reside, completely or at least partially, within themain memory 904 and/or within theprocessor 902 during execution thereof by thecomputer system 900, themain memory 904 and theprocessor 902 also constituting machine-readable media. Thesoftware 924 may further be transmitted or received over anetwork 926 via thenetwork interface device 920, which may comprise a wired and/or wireless interface device. - While the machine-
readable medium 922 is shown in an example embodiment to be a single medium, the term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present invention. The term “machine-readable medium” shall accordingly be taken to include tangible media that include, but are not limited to, solid-state memories and optical and magnetic media. - Using the apparatus, systems, and methods disclosed herein may provide a novel mechanism for making payments using funds pushing. Thus, instead of initiating a request to transfer funds from a payment processor to a financial entity to “pull” the funds into the payment processor, the request may be initiated elsewhere, so that the funds can be “pushed” directly from the financial entity to the payment processor. More immediate transfer of funds, and increased user satisfaction, may result.
- The accompanying drawings that form a part hereof, show by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.
- Such embodiments of the inventive subject matter may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.
- The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1.72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.
Claims (25)
1. A computer-implemented method, comprising:
receiving a request at a first financial entity from a first party to transfer an amount to be paid from an account associated with the first party and held by the first financial entity, to an account linked to an email address associated with a second party via a selected payment processor; and
pushing the amount to be paid from the account associated with the first party directly to the selected payment processor.
2. The computer-implemented method of claim 1 , comprising:
pushing the amount to be paid from the selected payment processor directly to the account linked to the email address.
3. The computer implemented method of claim 1 , comprising:
sending queries to aggregate information including a plurality of available transfer amounts associated with a corresponding plurality of financial entities, including the first financial entity.
4. The computer implemented method of claim 1 , comprising:
displaying the plurality of available transfer amounts as part of a single display page prior to pushing the amount to be paid.
5. The computer implemented method of claim 1 , wherein the account linked to the email address is a holding account created by the selected payment processor responsive to receiving the amount to be paid, comprising:
holding the amount to be paid in the holding account.
6. The computer implemented method of claim 1 , comprising:
sending a request, to the second party, to link an account held by a second financial entity to the email address.
7. The computer implemented method of claim 1 , comprising:
receiving a request to purchase an item presented by an online marketplace; and
determining the amount to be paid from a purchase price associated with the item.
8. The computer implemented method of claim 1 , comprising:
notifying the second party of the amount to be paid by sending an email message to the email address.
9. A computer-implemented method, comprising:
presenting, via a networked client coupled to a first financial entity, a graphical user interface including an account associated with a first party, an amount to be paid, and an email address associated with a second party;
receiving an indication from the graphical user interface to transfer, via a selected payment processor, the amount to be paid from the account associated with the first party and held by the first financial entity to an account linked to the email address; and
pushing the amount to be paid from the account held by the first financial entity directly to the selected payment processor.
10. The computer-implemented method of claim 9 , comprising:
notifying the second party of the amount to be paid by at least one of sending a message to the email address and sending the message to a mobile phone number associated with the email address.
11. The computer-implemented method of claim 9 , comprising:
accessing an account held by another financial entity responsive to receiving the indication and transferring an initial amount less than the amount to be paid from the account held by the other financial entity to the account held by the first financial entity.
12. The computer-implemented method of claim 9 , wherein presenting comprises:
presenting a single payment widget as part of the graphical user interface.
13. The computer-implemented method of claim 9 , wherein the first financial entity comprises a bank.
14. The computer-implemented method of claim 9 , comprising:
pushing the amount to be paid from the selected payment processor directly to a credit card account linked to the email address.
15. The computer-implemented method of claim 9 , comprising:
automatically sweeping the amount to be paid from the selected payment processor to the account linked to the email address.
16. An apparatus, comprising:
a user input device;
a client module to communicatively couple to a server at a first financial entity; and
a payment module to receive a request initiated by the user input device to push an amount to be paid from an account associated with a first party and held by the first financial entity directly to an account linked to an email address associated with a second party via a selected payment processor.
17. The apparatus of claim 16 , wherein the user input device comprises at least one of a keypad, a thumbwheel, a touch screen, a button, and a voice recognition processor.
18. The apparatus of claim 16 , comprising:
a cellular telephone transceiver to transmit a message associated with the request, wherein the message is to be sent to the email address.
19. A system, comprising:
a first client terminal having a user input device, a client module, and a payment module to receive a request initiated by the user input device; and
a server having a funds transfer module associated with an account associated with a first party and held by a first financial entity, wherein the request is to push an amount to be paid from the account associated with the first party directly to an account linked to an email address associated with a second party via a selected payment processor, and wherein the funds transfer module is to effect the direct transfer of the amount to be paid to the selected payment processor responsive to receiving the request.
20. The system of claim 19 , comprising:
a second client terminal associated with the selected payment processor and communicatively coupled to the server.
21. The system of claim 19 , comprising:
an automated teller machine to house the user input device.
22. A machine-readable medium comprising instructions, which when executed by one or more processors, cause the one or more processors to perform the following operations:
receive a request at a first financial entity from a first party to transfer an amount to be paid from an account associated with the first party and held by the first financial entity, to an account linked to an email address associated with a second party via a selected payment processor; and
push the amount to be paid from the account associated with the first party directly to the selected payment processor.
23. The machine-readable medium of claim 22 , wherein the instructions, when executed by the one or more processors, cause the one or more processors to perform the following operations:
determine sufficiency of funds in the account associated with the first party to pay the amount to be paid; and
if the funds are insufficient to pay the amount to be paid, aggregate a total amount of available funds from other financial entities until the total amount is sufficient to pay the amount to be paid.
24. The machine-readable medium of claim 22 , wherein the instructions, when executed by the one or more processors, cause the one or more processors to perform the following operations:
send a message to the email address requesting the second party to establish an account associated with a second financial entity to link to the email address.
25. The machine-readable medium of claim 24 , wherein the instructions, when executed by the one or more processors, cause the one or more processors to perform the following operations:
receive a notification that the account associated with the second financial entity has been established; and
responsive to receiving the notification, automatically sweeping the amount to be paid from the selected payment processor directly to the account associated with the second financial entity.
Priority Applications (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/962,733 US20090106118A1 (en) | 2007-10-19 | 2007-12-21 | Payment using funds pushing |
PCT/US2008/009188 WO2009054871A1 (en) | 2007-10-19 | 2008-07-30 | Payment using funds pushing |
CA2702403A CA2702403A1 (en) | 2007-10-19 | 2008-07-30 | Payment using funds pushing |
AU2008317493A AU2008317493B2 (en) | 2007-10-19 | 2008-07-30 | Payment using funds pushing |
EP08794864A EP2201514A4 (en) | 2007-10-19 | 2008-07-30 | Payment using funds pushing |
US15/726,989 US10922694B2 (en) | 2007-10-19 | 2017-10-06 | Automatic teller machine (ATM) electronic push requests |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US98140207P | 2007-10-19 | 2007-10-19 | |
US11/962,733 US20090106118A1 (en) | 2007-10-19 | 2007-12-21 | Payment using funds pushing |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/726,989 Continuation US10922694B2 (en) | 2007-10-19 | 2017-10-06 | Automatic teller machine (ATM) electronic push requests |
Publications (1)
Publication Number | Publication Date |
---|---|
US20090106118A1 true US20090106118A1 (en) | 2009-04-23 |
Family
ID=40564425
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/962,733 Abandoned US20090106118A1 (en) | 2007-10-19 | 2007-12-21 | Payment using funds pushing |
US15/726,989 Active 2028-08-24 US10922694B2 (en) | 2007-10-19 | 2017-10-06 | Automatic teller machine (ATM) electronic push requests |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/726,989 Active 2028-08-24 US10922694B2 (en) | 2007-10-19 | 2017-10-06 | Automatic teller machine (ATM) electronic push requests |
Country Status (5)
Country | Link |
---|---|
US (2) | US20090106118A1 (en) |
EP (1) | EP2201514A4 (en) |
AU (1) | AU2008317493B2 (en) |
CA (1) | CA2702403A1 (en) |
WO (1) | WO2009054871A1 (en) |
Cited By (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110307389A1 (en) * | 2010-06-15 | 2011-12-15 | Opensky Project, Inc. | Method and System for Distributed Point of Sale Transactions |
WO2012027585A3 (en) * | 2010-08-25 | 2012-04-19 | American Cash Exchange, Inc. | Authorization of cash delivery |
US20120216175A1 (en) * | 2011-02-18 | 2012-08-23 | Bank Of America Corporation | Customizable financial institution application interface |
WO2012138432A1 (en) * | 2011-02-24 | 2012-10-11 | Hardiek Scott J | System and method for facilitating value exchange transactions between distributed users |
US20150277712A1 (en) * | 2014-03-31 | 2015-10-01 | Branch Banking And Trust Company | Web page action guidance system |
US20150379644A1 (en) * | 2014-06-30 | 2015-12-31 | The Toronto-Dominion Bank | Systems and methods for identifying and remedying account error events in networked computer systems |
US20180349881A1 (en) * | 2017-06-02 | 2018-12-06 | Apple Inc. | Split transaction execution |
US20180365894A1 (en) * | 2017-06-14 | 2018-12-20 | Anand Babu Chitavadigi | System and method for interactive multimedia and multi-lingual guided tour/panorama tour |
US10922694B2 (en) | 2007-10-19 | 2021-02-16 | Paypal, Inc. | Automatic teller machine (ATM) electronic push requests |
US11232445B2 (en) * | 2018-08-30 | 2022-01-25 | Bank Of America Corporation | Intelligent dynamic authentication and event processing system |
US20230073485A1 (en) * | 2019-02-28 | 2023-03-09 | Stripe, Inc. | Push payment decision routing |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CA2910997A1 (en) | 1999-04-30 | 2000-11-09 | Paypal, Inc. | System and method for electronically exchanging value among distributed users |
Citations (35)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5159592A (en) * | 1990-10-29 | 1992-10-27 | International Business Machines Corporation | Network address management for a wired network supporting wireless communication to a plurality of mobile users |
US5175416A (en) * | 1989-10-06 | 1992-12-29 | Mansvelt Andre Peter | Funds transfer system |
US5677955A (en) * | 1995-04-07 | 1997-10-14 | Financial Services Technology Consortium | Electronic funds transfer instruments |
US5742668A (en) * | 1994-09-19 | 1998-04-21 | Bell Communications Research, Inc. | Electronic massaging network |
US5778178A (en) * | 1995-11-13 | 1998-07-07 | Arunachalam; Lakshmi | Method and apparatus for enabling real-time bi-directional transactions on a network |
US5790790A (en) * | 1996-10-24 | 1998-08-04 | Tumbleweed Software Corporation | Electronic document delivery system in which notification of said electronic document is sent to a recipient thereof |
US5893080A (en) * | 1995-07-25 | 1999-04-06 | Bottomline Technologies, Inc. | Disbursement system and method |
US5903874A (en) * | 1996-06-27 | 1999-05-11 | Mci Communications Corporation | System and method for electronic coupon management |
US5903880A (en) * | 1996-07-19 | 1999-05-11 | Biffar; Peter C. | Self-contained payment system with circulating digital vouchers |
US5915023A (en) * | 1997-01-06 | 1999-06-22 | Bernstein; Robert | Automatic portable account controller for remotely arranging for transfer of value to a recipient |
US5937396A (en) * | 1996-12-04 | 1999-08-10 | Konya; Arpad | System for ATM/ATM transfers |
US5963647A (en) * | 1997-02-14 | 1999-10-05 | Citicorp Development Center, Inc. | Method and system for transferring funds from an account to an individual |
US6029151A (en) * | 1996-12-13 | 2000-02-22 | Telefonaktiebolaget L M Ericsson | Method and system for performing electronic money transactions |
US6032133A (en) * | 1993-11-01 | 2000-02-29 | Visainternational Service Association | Electronic bill pay system |
US6058382A (en) * | 1996-09-12 | 2000-05-02 | Hitachi, Ltd. | Electronic money holding device utilizing an automatic payment method |
US6070150A (en) * | 1996-10-18 | 2000-05-30 | Microsoft Corporation | Electronic bill presentment and payment system |
US6069896A (en) * | 1996-10-15 | 2000-05-30 | Motorola, Inc. | Capability addressable network and method therefor |
US6076068A (en) * | 1992-09-17 | 2000-06-13 | Ad Response Micromarketing Corporation | Coupon delivery system |
US6192407B1 (en) * | 1996-10-24 | 2001-02-20 | Tumbleweed Communications Corp. | Private, trackable URLs for directed document delivery |
US6212556B1 (en) * | 1995-11-13 | 2001-04-03 | Webxchange, Inc. | Configurable value-added network (VAN) switching |
US6223168B1 (en) * | 1995-07-25 | 2001-04-24 | Bottomline Technologies, Inc. | Automatic remittance delivery system |
US6260024B1 (en) * | 1998-12-02 | 2001-07-10 | Gary Shkedy | Method and apparatus for facilitating buyer-driven purchase orders on a commercial network system |
WO2001063520A1 (en) * | 2000-02-22 | 2001-08-30 | Insun Yun | Method and system for maximizing credit card purchasing power and minimizing interest costs over the internet |
US20010037315A1 (en) * | 2000-04-21 | 2001-11-01 | Saliba Bassam A. | System and method for secure distribution of information via eMail |
US6324526B1 (en) * | 1999-01-15 | 2001-11-27 | D'agostino John | System and method for performing secure credit card purchases |
US6330544B1 (en) * | 1997-05-19 | 2001-12-11 | Walker Digital, Llc | System and process for issuing and managing forced redemption vouchers having alias account numbers |
US6338050B1 (en) * | 1998-11-16 | 2002-01-08 | Trade Access, Inc. | System and method for providing and updating user supplied context for a negotiations system |
US20020032651A1 (en) * | 1996-12-04 | 2002-03-14 | Embrey Mark C. | Method and apparatus for making payments and delivering payment information |
US6553346B1 (en) * | 1996-09-04 | 2003-04-22 | Priceline.Com Incorporated | Conditional purchase offer (CPO) management system for packages |
US6609113B1 (en) * | 1999-05-03 | 2003-08-19 | The Chase Manhattan Bank | Method and system for processing internet payments using the electronic funds transfer network |
US6694300B1 (en) * | 1997-03-21 | 2004-02-17 | Walker Digital, Llc | Method and apparatus for providing supplementary product sales to a customer at a customer terminal |
US20060195398A1 (en) * | 2005-02-04 | 2006-08-31 | Sanjeev Dheer | Method and apparatus for processing payment requests |
WO2007053123A2 (en) * | 2005-11-04 | 2007-05-10 | Veritas Mobile Solutions Pte. Ltd. | System and method to facilitate online funds transfer to a mobile phone subscriber |
US20090089211A1 (en) * | 2007-10-02 | 2009-04-02 | Patricia Morse | System and method for person to person fund transfer |
US20090132423A1 (en) * | 2007-11-15 | 2009-05-21 | Ebay Inc. | Send money plug in for web mails |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CA2059078C (en) | 1991-02-27 | 1995-10-03 | Alexander G. Fraser | Mediation of transactions by a communications system |
GB2328310B (en) | 1996-05-15 | 1999-12-08 | Ho Keung Tse | Electronic transaction apparatus and method therefor |
US20030217005A1 (en) * | 1996-11-27 | 2003-11-20 | Diebold Self Service Systems, Division Of Diebold, Incorporated | Automated banking machine system and method |
KR20000050092A (en) * | 2000-05-15 | 2000-08-05 | 차지혁 | Method of remittance by e-mail & e-mail remittance system |
KR20010008292A (en) * | 2000-11-21 | 2001-02-05 | 신복영 | The banking trade system utilizing the e-mail account and its trading method |
CA2332656A1 (en) * | 2001-01-26 | 2002-07-26 | Certapay Inc. | Online payment transfer and identity management system and method |
US20090106118A1 (en) | 2007-10-19 | 2009-04-23 | Ebay Inc | Payment using funds pushing |
AU2012200569B2 (en) | 2007-10-19 | 2013-09-19 | Paypal, Inc. | Payment using funds pushing |
US20090106188A1 (en) | 2007-10-22 | 2009-04-23 | Jun Takahashi | Image processor, stored document management method, and stored document management system |
-
2007
- 2007-12-21 US US11/962,733 patent/US20090106118A1/en not_active Abandoned
-
2008
- 2008-07-30 CA CA2702403A patent/CA2702403A1/en not_active Abandoned
- 2008-07-30 AU AU2008317493A patent/AU2008317493B2/en active Active
- 2008-07-30 WO PCT/US2008/009188 patent/WO2009054871A1/en active Application Filing
- 2008-07-30 EP EP08794864A patent/EP2201514A4/en not_active Ceased
-
2017
- 2017-10-06 US US15/726,989 patent/US10922694B2/en active Active
Patent Citations (36)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5175416A (en) * | 1989-10-06 | 1992-12-29 | Mansvelt Andre Peter | Funds transfer system |
US5159592A (en) * | 1990-10-29 | 1992-10-27 | International Business Machines Corporation | Network address management for a wired network supporting wireless communication to a plurality of mobile users |
US6076068A (en) * | 1992-09-17 | 2000-06-13 | Ad Response Micromarketing Corporation | Coupon delivery system |
US6032133A (en) * | 1993-11-01 | 2000-02-29 | Visainternational Service Association | Electronic bill pay system |
US5742668A (en) * | 1994-09-19 | 1998-04-21 | Bell Communications Research, Inc. | Electronic massaging network |
US5677955A (en) * | 1995-04-07 | 1997-10-14 | Financial Services Technology Consortium | Electronic funds transfer instruments |
US6223168B1 (en) * | 1995-07-25 | 2001-04-24 | Bottomline Technologies, Inc. | Automatic remittance delivery system |
US5893080A (en) * | 1995-07-25 | 1999-04-06 | Bottomline Technologies, Inc. | Disbursement system and method |
US5987500A (en) * | 1995-11-13 | 1999-11-16 | Pi-Net International, Inc. | Value-added network system for enabling real-time, by-directional transactions on a network |
US6212556B1 (en) * | 1995-11-13 | 2001-04-03 | Webxchange, Inc. | Configurable value-added network (VAN) switching |
US5778178A (en) * | 1995-11-13 | 1998-07-07 | Arunachalam; Lakshmi | Method and apparatus for enabling real-time bi-directional transactions on a network |
US5903874A (en) * | 1996-06-27 | 1999-05-11 | Mci Communications Corporation | System and method for electronic coupon management |
US5903880A (en) * | 1996-07-19 | 1999-05-11 | Biffar; Peter C. | Self-contained payment system with circulating digital vouchers |
US6553346B1 (en) * | 1996-09-04 | 2003-04-22 | Priceline.Com Incorporated | Conditional purchase offer (CPO) management system for packages |
US6058382A (en) * | 1996-09-12 | 2000-05-02 | Hitachi, Ltd. | Electronic money holding device utilizing an automatic payment method |
US6069896A (en) * | 1996-10-15 | 2000-05-30 | Motorola, Inc. | Capability addressable network and method therefor |
US6070150A (en) * | 1996-10-18 | 2000-05-30 | Microsoft Corporation | Electronic bill presentment and payment system |
US5790790A (en) * | 1996-10-24 | 1998-08-04 | Tumbleweed Software Corporation | Electronic document delivery system in which notification of said electronic document is sent to a recipient thereof |
US6192407B1 (en) * | 1996-10-24 | 2001-02-20 | Tumbleweed Communications Corp. | Private, trackable URLs for directed document delivery |
US5937396A (en) * | 1996-12-04 | 1999-08-10 | Konya; Arpad | System for ATM/ATM transfers |
US20020032651A1 (en) * | 1996-12-04 | 2002-03-14 | Embrey Mark C. | Method and apparatus for making payments and delivering payment information |
US6029151A (en) * | 1996-12-13 | 2000-02-22 | Telefonaktiebolaget L M Ericsson | Method and system for performing electronic money transactions |
US5915023A (en) * | 1997-01-06 | 1999-06-22 | Bernstein; Robert | Automatic portable account controller for remotely arranging for transfer of value to a recipient |
US5963647A (en) * | 1997-02-14 | 1999-10-05 | Citicorp Development Center, Inc. | Method and system for transferring funds from an account to an individual |
US6694300B1 (en) * | 1997-03-21 | 2004-02-17 | Walker Digital, Llc | Method and apparatus for providing supplementary product sales to a customer at a customer terminal |
US6330544B1 (en) * | 1997-05-19 | 2001-12-11 | Walker Digital, Llc | System and process for issuing and managing forced redemption vouchers having alias account numbers |
US6338050B1 (en) * | 1998-11-16 | 2002-01-08 | Trade Access, Inc. | System and method for providing and updating user supplied context for a negotiations system |
US6260024B1 (en) * | 1998-12-02 | 2001-07-10 | Gary Shkedy | Method and apparatus for facilitating buyer-driven purchase orders on a commercial network system |
US6324526B1 (en) * | 1999-01-15 | 2001-11-27 | D'agostino John | System and method for performing secure credit card purchases |
US6609113B1 (en) * | 1999-05-03 | 2003-08-19 | The Chase Manhattan Bank | Method and system for processing internet payments using the electronic funds transfer network |
WO2001063520A1 (en) * | 2000-02-22 | 2001-08-30 | Insun Yun | Method and system for maximizing credit card purchasing power and minimizing interest costs over the internet |
US20010037315A1 (en) * | 2000-04-21 | 2001-11-01 | Saliba Bassam A. | System and method for secure distribution of information via eMail |
US20060195398A1 (en) * | 2005-02-04 | 2006-08-31 | Sanjeev Dheer | Method and apparatus for processing payment requests |
WO2007053123A2 (en) * | 2005-11-04 | 2007-05-10 | Veritas Mobile Solutions Pte. Ltd. | System and method to facilitate online funds transfer to a mobile phone subscriber |
US20090089211A1 (en) * | 2007-10-02 | 2009-04-02 | Patricia Morse | System and method for person to person fund transfer |
US20090132423A1 (en) * | 2007-11-15 | 2009-05-21 | Ebay Inc. | Send money plug in for web mails |
Cited By (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10922694B2 (en) | 2007-10-19 | 2021-02-16 | Paypal, Inc. | Automatic teller machine (ATM) electronic push requests |
US20110307389A1 (en) * | 2010-06-15 | 2011-12-15 | Opensky Project, Inc. | Method and System for Distributed Point of Sale Transactions |
US9715690B2 (en) | 2010-08-25 | 2017-07-25 | American Cash Exchange, Inc. | Authorization of cash delivery |
WO2012027585A3 (en) * | 2010-08-25 | 2012-04-19 | American Cash Exchange, Inc. | Authorization of cash delivery |
US9026991B2 (en) * | 2011-02-18 | 2015-05-05 | Bank Of America Corporation | Customizable financial institution application interface |
US20120216175A1 (en) * | 2011-02-18 | 2012-08-23 | Bank Of America Corporation | Customizable financial institution application interface |
WO2012138432A1 (en) * | 2011-02-24 | 2012-10-11 | Hardiek Scott J | System and method for facilitating value exchange transactions between distributed users |
US20150277712A1 (en) * | 2014-03-31 | 2015-10-01 | Branch Banking And Trust Company | Web page action guidance system |
US20220318780A1 (en) * | 2014-03-31 | 2022-10-06 | Truist Bank | Web page action guidance system |
US10726410B2 (en) * | 2014-03-31 | 2020-07-28 | Truist Bank | Web page action guidance system |
US11887096B2 (en) * | 2014-03-31 | 2024-01-30 | Truist Bank | Web page action guidance system |
US11042865B2 (en) * | 2014-03-31 | 2021-06-22 | Truist Bank | Web page action guidance system |
US11620627B2 (en) * | 2014-03-31 | 2023-04-04 | Truist Bank | Web page action guidance system |
US11443294B2 (en) * | 2014-03-31 | 2022-09-13 | Truist Bank | Web page action guidance system |
US20150379644A1 (en) * | 2014-06-30 | 2015-12-31 | The Toronto-Dominion Bank | Systems and methods for identifying and remedying account error events in networked computer systems |
US20150379485A1 (en) * | 2014-06-30 | 2015-12-31 | The Toronto-Dominion Bank | Systems and methods for identifying and remedying account error events in networked computer systems |
US20180349881A1 (en) * | 2017-06-02 | 2018-12-06 | Apple Inc. | Split transaction execution |
US20180365894A1 (en) * | 2017-06-14 | 2018-12-20 | Anand Babu Chitavadigi | System and method for interactive multimedia and multi-lingual guided tour/panorama tour |
US10796484B2 (en) * | 2017-06-14 | 2020-10-06 | Anand Babu Chitavadigi | System and method for interactive multimedia and multi-lingual guided tour/panorama tour |
US11232445B2 (en) * | 2018-08-30 | 2022-01-25 | Bank Of America Corporation | Intelligent dynamic authentication and event processing system |
US20230073485A1 (en) * | 2019-02-28 | 2023-03-09 | Stripe, Inc. | Push payment decision routing |
Also Published As
Publication number | Publication date |
---|---|
US20180039991A1 (en) | 2018-02-08 |
EP2201514A1 (en) | 2010-06-30 |
AU2008317493B2 (en) | 2011-11-03 |
EP2201514A4 (en) | 2011-01-05 |
US10922694B2 (en) | 2021-02-16 |
CA2702403A1 (en) | 2009-04-30 |
WO2009054871A1 (en) | 2009-04-30 |
AU2008317493A1 (en) | 2009-04-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10922694B2 (en) | Automatic teller machine (ATM) electronic push requests | |
US20190197503A1 (en) | Release of funds based on criteria | |
US20160132884A1 (en) | Real-time payments through financial institution | |
US20160155103A1 (en) | Utilizing an electronic payment system to implement rebate programs | |
US9123039B2 (en) | System and method of a passphrase account identifier for use in a network environment | |
US8504450B2 (en) | Mobile remittances/payments | |
US20160335624A1 (en) | Mobile device nfc-based detection and merchant payment system | |
US20090265252A1 (en) | Money pooling with electronic invoice | |
KR20130135890A (en) | Deferred payment and selective funding and payments | |
KR20030011070A (en) | Method and system for maximizing credit card purchasing power and minimizing interest costs over the internet | |
US8655780B2 (en) | Person-to-person payments: contextual spending | |
US20140012726A1 (en) | System and method that facilitates transactions between physical gold holdings and commercial payment systems | |
US20200286053A1 (en) | Tokenized data having split payment instructions for multiple accounts in a chain transaction | |
US20110153493A1 (en) | Dynamic limit funding source | |
AU2012200569B2 (en) | Payment using funds pushing | |
AU2013100977A4 (en) | Deferred payment and selective funding and payments | |
US20150039503A1 (en) | Mobile remittances/payments |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: EBAY INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PELEGERO, RENE M.;BALASUBRAMANIAN, GIRISH;MAHADEVAN, ROHAN;REEL/FRAME:020831/0261;SIGNING DATES FROM 20080310 TO 20080320 |
|
AS | Assignment |
Owner name: PAYPAL, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:EBAY INC.;REEL/FRAME:036163/0596 Effective date: 20150717 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |