US20130018798A1 - System and Methods for Facilitating Fund Transfers Over a Network - Google Patents
System and Methods for Facilitating Fund Transfers Over a Network Download PDFInfo
- Publication number
- US20130018798A1 US20130018798A1 US13/622,851 US201213622851A US2013018798A1 US 20130018798 A1 US20130018798 A1 US 20130018798A1 US 201213622851 A US201213622851 A US 201213622851A US 2013018798 A1 US2013018798 A1 US 2013018798A1
- Authority
- US
- United States
- Prior art keywords
- user
- account
- service provider
- user account
- recipient
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/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/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
- G06Q20/102—Bill distribution or payments
-
- 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
- G06Q20/108—Remote banking, e.g. home banking
Definitions
- the present invention generally relates to network transactions and, more particularly, to facilitating fund transfers over a network.
- a user In electronic banking and commerce, a user typically accesses accounts and conducts financial transactions through electronic communications with online service providers over communication networks, such as the Internet.
- online service providers over communication networks, such as the Internet.
- the user steps through a series of steps to verify identity and a funding source. These steps ensure that an account where funds are being transferred out of or into is indeed an account associated with the user and not an unauthorized account.
- Conventional techniques include inputting and verifying user provided information, such as account numbers, routing information, and billing address, which can often be cumbersome and time-consuming for the user.
- These conventional techniques may include the user typing in bank information, such as an account number and a routing number.
- the online service provider may deposit a small amount of funds (e.g., 2 cents) into the user's bank account, typically a few days after the information is entered. The user then periodically checks the user's account to verify whether any small deposits have been received. Once received, the user accesses the online service provider to confirm the deposit to the account.
- FIG. 1 shows a block diagram of a system adapted to facilitate fund transfers over a network, in accordance with an embodiment of the present disclosure.
- FIG. 2 shows one embodiment of a method for facilitating user-side fund transfers over a network, in accordance with an embodiment of the present disclosure.
- FIG. 3 shows one embodiment of a method for facilitating server-side processing of fund transfers over a network, in accordance with an embodiment of the present disclosure.
- FIG. 4 is a block diagram of a computer system suitable for implementing one or more embodiments of the present disclosure.
- a system for facilitating financial transactions by a service provider over a network includes a network interface, a memory, and one or more processors.
- the network interface communicates with a financial institution over the network.
- the financial institution has a first user account belonging to a user.
- the memory stores machine-readable instructions for execution by the one or more processors.
- the one or more processors execute the instructions to receive a fund transfer request from the financial institution on behalf of the user.
- the fund transfer request includes user information that is related to the first user account.
- the one or more processors also verify that the user has an existing account with the service provider based on the user information related to the first user that is passed with the fund transfer request.
- the one or more processors further process the fund transfer request to receive funds from the financial institution associated with the first user account and to deposit the received funds in the existing account of the user with the service provider on behalf of the user.
- a method for facilitating financial transactions by a service provider over a network includes receiving by a network server of the service provider a fund transfer request from a financial institution on behalf of a user.
- the financial institution has a first user account belonging to the user.
- the fund transfer request includes user information that is related to the first user account.
- the method also includes verifying that the user has an existing account with the service provider based on the user information related to the first user that is passed with the funds transfer request.
- the method further includes processing the fund transfer request by receiving funds from the financial institution associated with the first user account and depositing the received funds in the existing user account on behalf of the user.
- a non-transitory computer readable medium having computer readable code for instructing a processor to perform a method to facilitate financial transaction over a network includes communicating with a financial institution over the network.
- the financial institution has a first user account belonging to a user.
- the method also includes receiving a fund transfer request from the financial institution on behalf of the user.
- the fund transfer request includes user information that is related to the first user account.
- the method further includes verifying that the user has an existing account with the service provider based on the user information related to the first user that is passed with the funds transfer request.
- the method further includes processing the fund transfer request by receiving funds from the financial institution associated with the first user account and depositing the received funds in the existing user account on behalf of the user.
- FIG. 1 shows one embodiment of a system 100 for facilitating financial transactions including fund transfers over a network, such as the Internet.
- System 100 includes a user 120 (e.g., a client or customer) adapted to interface with a financial institution 140 (e.g., a bank or credit union) and a service provider 160 (e.g., a network based financial transaction service provider) over a network.
- a financial institution 140 e.g., a bank or credit union
- service provider 160 e.g., a network based financial transaction service provider
- the user 120 in one embodiment, is able to establish a user account 144 with the financial institution 140 , such as a bank, wherein the user 120 may deposit monetary funds in the user account 144 .
- the financial institution 140 is adapted to provide the user 120 with access to the user account 144 and to a bill payment service 142 via the network.
- the user 120 may request network based transactions, such as fund transfers (e.g., deposits and/or debits) between accounts, over the network in a manner as described in greater detail herein.
- the financial institution 140 may provide the user 120 with some form of payment media, such as an electronic payment resource, that is linked to the user account 144 . In this instance, the user 120 may utilize the payment media to access funds in the user account 144 .
- the user 120 may utilize the bill payment service 142 to transfer funds from the user account 144 of the financial institution to a user account 164 of the service provider 160 via the network.
- the bill payment service 142 is adapted to process the fund transfer between the user 120 and the service provider 160 via the network.
- the bill payment service 142 may communicate with a clearing house to debit the user account 144 of the financial institution 140 in accordance with an amount specific to the fund transfer and credit the user account 164 of the service provider 160 over the network.
- the user 120 in one embodiment, is able to establish one or more user accounts (e.g., the user account 164 ) with the service provider 160 , wherein the user 120 may deposit monetary funds in the user account 164 either directly or from the user account 144 of the financial institution 140 .
- the service provider 160 is adapted to provide the user 120 with access to the user account 164 via the network.
- the service provider 160 may provide the user 120 with some form of electronic payment resource that is linked to the user account 164 . As such, in this instance, the user 120 may utilize the electronic payment resource to access funds in the user account 164 .
- a link 150 may be established between the user account 144 of the financial institution 140 and one or more other accounts with other financial institutions and/or network based service providers, such as the service provider 160 .
- the user 120 may provide an e-mail address to the service provider 160 as a unique identifier (i.e., a user identity verifier) so that the link 150 may be established between the user account 144 of the financial institution 140 and the user account 164 of the service provider 160 .
- an e-mail address may be utilized by the user 120 to establish the user account 164 with the service provider 160 , wherein the link 150 between the user accounts 144 , 164 is an e-mail address related to the user 120 .
- fund transfers may be processed seamlessly between the user accounts 144 , 164 of the financial institution 140 and the service provider 160 , respectively.
- the unique identifier i.e., the user identity verifier
- the unique identifier may comprise an e-mail address, telephone number, and/or various other types of easily remembered addresses and/or numbers related to the user 120 , without departing from the scope of the present disclosure.
- additional security verification may be obtained by the service provider 160 to further verify the identity of the user 120 and provide further security for verifying the link between the two accounts.
- the user accounts 144 , 164 are considered linked, the user 120 is presumed to be the same person having permission to access both user accounts 144 , 164 .
- the user 120 may be prompted with an option to link the information related to the user accounts 144 , 164 , wherein the user 120 may be prompted by the service provider 160 to provide at least one of a full name, address, telephone number, date of birth, and at least part of a social security number to link the user accounts 144 , 164 .
- the user 120 may be prompted to verify random deposit information.
- the service provider 160 may transfer nominal funds (e.g., a penny or a dollar) to the user account 144 with the financial institution 140 , and the user 120 may be prompted to verify information related to the nominal fund transfer, such as the amount deposited into the user account 144 and when the deposit occurred.
- the user 120 may be prompted to login to the user account 144 after a nominal fund transfer has been completed by the service provider 160 to verify the nominal fund transfer.
- bank information related to the user 120 may be utilized to establish the user account 164 with the service provider 160 .
- personal and/or banking information related to the user account 144 with the financial institution 140 should be protected until the service provider 160 verifies that the user 120 wants to share or link the bank information related to the user account 144 with the user account 164 .
- the user 120 may allow or grant permission to the service provider 160 to transfer funds from the user account 164 of the service provider 160 to another user account of the service provider 160 , such as a recipient account 166 related to a recipient 130 (e.g., another user, client, or customer having a user account with the service provider 160 ).
- a processing component 162 of the service provider 160 is adapted to process the fund transfer between the user account 164 and the recipient account 166 .
- the service provider 160 may directly transfer funds between the user account 164 and the recipient account 166 .
- the service provider 160 may directly debit the user account 164 and directly credit the recipient account 166 because both of the accounts 164 , 166 are established with the service provider 160 .
- the service provider may use a clearing house to debit the user account 164 in accordance with an amount specific to the fund transfer and credit the recipient account 166 over the network.
- the service provider 160 may optionally process the fund transfer through a clearing house even though the accounts 164 , 166 are established with the service provider 160 .
- a clearing house resolves financial transactions through validation, delivery, and settlement.
- the clearing house may comprise an agency or institution having a system for settling indebtedness between members of that system through which accounts may be debited and/or credited of monetary funds.
- one or more fund transfers between the user 120 , the recipient 130 , the financial institution 140 , and the service provider 160 may take place over the network, such as a single network or a combination of multiple networks.
- the network may include the Internet and/or one or more intranets, landline networks, wireless networks, and/or other appropriate types of communication networks.
- the network may include a wireless telecommunications network (e.g., cellular phone network) adapted to interface and communicate with other communication networks, such as the Internet.
- the user 120 , the recipient 130 , the financial institution 140 , and the service provider 160 may be associated with a particular link (e.g., a link, such as a URL (Uniform Resource Locator) to an IP (Internet Protocol) address).
- a link such as a URL (Uniform Resource Locator) to an IP (Internet Protocol) address.
- the user 120 may utilize a network interface device, such as a personal computer (i.e., PC), a wireless telephone (e.g., cellular phone), a personal digital assistant (i.e., PDA), a notebook computer, and/or various other generally known types of wired and/or wireless computing devices, to communicate and interface with the financial institution 140 and/or the service provider 160 to access respective user accounts 144 , 164 via any appropriate combination of hardware and/or software configured for wired and/or wireless communication over the network.
- the user 120 may utilize a network interface application (e.g., a network browser application) to communicate and interface with the financial institution 140 and/or the service provider 160 to access user accounts 144 , 164 , respectively, via the network.
- a network interface application e.g., a network browser application
- the user 120 may use a web browser to access the user accounts 144 , 164 over the Internet.
- the user device may include other applications as may be desired in one or more embodiments of the present disclosure to provide additional features available to the user 120 .
- these other applications may include security applications for implementing user-side security features, programmatic client applications for interfacing with appropriate application programming interfaces (APIs) over the network, and/or various other types of generally known programs and/or software applications.
- APIs application programming interfaces
- these other applications may interface with the network interface application for improved efficiency and convenience.
- the user device may include at least one user identifier, which may be implemented, e.g., as operating system registry entries, cookies associated with the network interface application, identifiers associated with hardware of the user device, and/or various other appropriate identifiers.
- the user identifier may include one or more attributes and/or parameters associated with the user, such as personal information related to the user (e.g., one or more user names, passwords, photograph images, biometric ids, addresses, phone numbers, etc.) and banking information (e.g., one or more banking institutions, credit card issuers, user account numbers, security data and information, etc.).
- the user identifier may be passed with a login request and/or fund transfer request to the financial institution 140 and/or the service provider 160 via the network, and the user identifier may be used by the financial institution 140 and/or the service provider 160 to associate the user 120 with user accounts 144 , 164 , respectively.
- the recipient 130 may utilize a network interface device, such as a PC, a wireless telephone, a PDA, a notebook computer, and/or various other generally known types of wired and/or wireless computing devices, to communicate and interface with the service provider 160 to access the recipient account 166 via any appropriate combination of hardware and/or software configured for wired and/or wireless communication over the network.
- the recipient 130 may utilize a network interface application to communicate and interface with the service provider 160 to access the recipient account 166 via the network.
- the recipient 130 may use a web browser to access the recipient account 166 over the Internet.
- the recipient 130 may have a recipient account with the financial institution 140 , without departing from the scope of the present disclosure. As such, the recipient 130 would also be able to access a recipient account with the financial institution 140 over the network.
- the financial institution 140 and/or the service provider 160 may maintain one or more servers on the network for processing financial transactions including fund transfers over the network.
- each of the one or more servers for the financial institution 140 and/or the service provider 160 may include one or more databases for storing information related to the bill payment service 142 , the user accounts 144 , 164 , and the recipient account 166 , respectively.
- Each of the one or more servers for the financial institution 140 and/or the service provider 160 may include some form of network interface application configured to provide access to the bill payment service 142 , the user accounts 144 , 164 , and the recipient account 166 , respectively, over the network to the user 120 and the recipient 130 , respectively.
- the user 120 may interact with the network interface application through a browser application over the network to access one or more of the user accounts 144 , 164 .
- the service provider 160 in one embodiment, is adapted to process financial transitions including fund transfers over the network on behalf of the user 120 and/or the recipient 130 .
- the service provider 160 may utilize some form of fund transfer and settlement application configured to interact with the user 120 and/or the recipient 130 to facilitate fund transfers.
- the service provider 160 may be provided by PayPal, Inc. of San Jose, Calif., USA.
- the service provider 160 may be configured to maintain a plurality of accounts (e.g., user account 164 and recipient account 166 ), each of which may include account information associated with user 120 and/or the recipient 130 .
- account information may include private financial information of the user 120 and/or the recipient 130 , such as one or more account numbers, passwords, credit card information, banking information, or other types of financial information, which may be used to facilitate financial transactions including fund transfers over the network.
- the system 100 described herein may be modified to accommodate users and/or recipients that may or may not be associated with at least one existing account, without departing from the scope of the present disclosure.
- the user 120 and/or the recipient 130 may have identity attributes stored with the financial institution 140 and/or the service provider 160 , and the user 120 and/or the recipient 130 may have credentials to authenticate or verify identity with the financial institution 140 and/or the service provider 160 .
- user attributes may include personal information and/or banking information, as previously described.
- the user attributes may be passed to the financial institution 140 and/or the service provider 160 as part of a login, account access request, fund transfer request, and/or payment request, and the user attributes may be utilized by the financial institution 140 and/or the service provider 160 to associate the user 120 and/or the recipient 130 with the user accounts 144 , 164 , respectively, which are maintained by the financial institution 140 and/or the service provider 160 , respectively.
- the financial institution 140 and/or the service provider 160 may be associated with at least one identifier, which may be included as part of a financial transaction including a fund transfer.
- the identifier may include one or more attributes and/or parameters related to the financial institution 140 and/or the service provider 160 , such as business and/or banking information.
- the identifier for the financial institution 140 may be passed to the service provider 160 when the user 120 requests a fund transfer from the financial institution 140 to the service provider 160 .
- the identifier may be used by the service provider 160 to identify and/or verify the user account 144 in reference to the financial institution 140 .
- the processing component 162 of the service provider 160 may utilize a processing module to process fund transfers between accounts, such as the user accounts 144 , 164 and the recipient account 166 .
- the processing module is adapted to assist with resolving financial transactions including fund transfers through validation, delivery, and settlement.
- the processing component 162 in conjunction with the processing module may be adapted to resolve fund transfers between the user 120 and the recipient 130 , wherein the accounts 144 , 164 , 166 may be directly and/or automatically debited and/or credited of monetary funds in a manner as accepted by the banking industry.
- FIG. 2 shows one embodiment of a method 200 for facilitating one or more user-side fund transfers over a network.
- the user 120 interfaces and communicates with the financial institution 140 and/or the service provider 160 via the network to request fund transfers from, e.g., the user account 144 of the financial institution 140 to the user account 164 of the service provider 160 and/or from, e.g., the user account 164 of the service provider 160 to the recipient account 166 of the service provider 160 .
- the method 200 provides a process of account verification by utilizing the bill payment service 142 (or some other similar service) of the user's financial institution 140 , which simplifies account verification for the user while maintaining security and reliability.
- the user 120 provides a login request to the financial institution 140 (block 210 ) to access the user account 144 (block 214 ). Then, when the user 120 attempts to access the bill payment service 142 , the financial institution 140 determines (block 218 ) whether the user 120 is a current user of the bill payment service 142 by, e.g., verifying access privileges for the user 120 based on information stored with the user account 144 .
- the user 120 may proceed to access the bill payment service 142 (block 226 ). Otherwise, the user 120 may be prompted to enroll in the bill payment service 142 (block 222 ) to gain access privileges for the bill payment service 142 and then proceed to access the bill payment service 142 (block 226 ).
- the user 120 may add the service provider 160 as a biller or payee (block 230 ) to link 150 the user account 144 of the financial institution 140 to the user account 164 of the service provider 160 .
- the link 150 may be established between the user account 144 of the financial institution 140 and the user account 164 of the service provider 160 .
- the user 120 may provide an e-mail address to the service provider 160 as a user identity verifier so that the link 150 may be established between the user account 144 of the financial institution 140 and the user account 164 of the service provider 160 .
- additional security verification may be obtained by the service provider 160 to further verify the identity of the user 120 and provide further security for verifying the link between the two accounts. The additional security verification is described in greater detail herein.
- the link 150 between the user accounts 144 , 164 is an e-mail address related to the user 120 . Accordingly, an e-mail address may be utilized by the user 120 to establish the user account 164 with the service provider 160 . After linking user accounts 144 , 164 via, e.g., an e-mail address, fund transfers may be processed seamlessly between the user accounts 144 , 164 of the financial institution 140 and the service provider 160 , respectively.
- the user 120 may request a fund transfer from the user account 144 of the financial institution 140 to the user account 164 of the service provider 160 (block 234 ).
- the user 120 adds the service provider 160 as a payee by, e.g., entering user identity information, such as one or more of an e-mail address, payee name, and/or an account number.
- the user 120 then transfers a nominal amount, such as $1, to the service provider 160 through the bill payment service 142 and enters the user's identity information (e.g., an e-mail address of the user 120 for the service provider 160 ) in a memo field of the fund transfer request.
- the bill payment service 142 then transfers the requested funds to the service provider 160 by, e.g., sending an electronic check or a receipt of the electronic check to the service provider 160 , which includes the user's account number and routing number associated with the user account 144 of the financial institution 140 .
- the electronic check or receipt of the electronic check may comprise an electronic document or a physical document.
- the service provider 160 may use information from the document, including a billing address, to verify and/or establish the user's account 164 with the service provider 160 .
- the service provider 160 may transfer the same funds or another amount of funds back to the user's financial institution 140 .
- the user 120 may simply create and/or access the user account 164 with the service provider 160 by simply signing up the service provider 160 as payee through the bill payment service 142 of the financial institution 140 instead of providing specific account information including account numbers, checking deposits, etc.
- additional security verification may be obtained by the service provider 160 to further verify the identity of the user 120 and provide further security for verifying the link between the two accounts.
- Using the bill payment service 142 to transfer funds from the user account 144 of the financial institution 140 to the user account 164 or recipient account 166 of the service provider 160 may be achieved with email account information related to the user 120 .
- email account information related to the user 120 .
- a presumption may be made that the user 120 is the same person having permission to access both user accounts 144 , 164 .
- the user 120 may be prompted with an option to link the information related to the user accounts 144 , 164 .
- the user 120 may be prompted by the service provider 160 to provide at least one of a full name, address, telephone number, date of birth, and at least part of a social security number to link the user accounts 144 , 164 .
- the user 120 may be prompted to verify random deposit information.
- the service provider 160 may transfer random nominal funds (e.g., a random two-digit fund transfer, such as 34 cents or 78 cents) to the user account 144 with the financial institution 140 , and the user 120 may be prompted to verify information related to the nominal fund transfer, such as the amount deposited into the user account 144 and when the deposit occurred.
- random nominal funds e.g., a random two-digit fund transfer, such as 34 cents or 78 cents
- the service provider 160 may prompt the user 120 to login to the user account 144 via the service provider server after a fund transfer has been completed to verify or validate the fund transfer.
- the service provider 160 would then review information in both user accounts 144 , 164 to obtain and match information related to the fund transfer between the user accounts 144 , 164 .
- the obtained and matched information may include the dollar amount, the date, the memo field (e.g., email address), and/or the actual transaction identification number for the fund transfer.
- the service provider 160 may review the fund transfer initiated by the user account 164 and prompt the user 120 to login to the user account 144 via the service provider 160 so that the service provider 160 may troll (e.g., with or without user action) both user accounts 144 , 164 to verify or validate information from the fund transfer between the user accounts 144 , 164 .
- bank information related to the user 120 may be utilized to establish the secondary account (i.e., the user account 164 ) with the service provider 160 .
- the secondary account i.e., the user account 164
- personal and/or banking information related to the first account (i.e., the user account 144 ) with the financial institution 140 should be protected until the service provider 160 verifies that the user 120 wants to share or link the bank information related to the first account (i.e., user account 144 ) with the secondary account (i.e., user account 164 ).
- a reason for the additional security verification is that, if funds are transferred to another person's account (e.g., the recipient account 166 related to the recipient 130 ), through the bill payment service 142 , any personal and/or banking information related to the user 120 should be protected from disclosure to the recipient 130 .
- the user 120 may add the service provider 160 and the recipient 130 as a biller or payee (block 238 ).
- the user 120 may request a fund transfer from the user account 144 of the financial institution 140 to the recipient account 166 of the service provider 160 (block 238 ).
- the user 120 may transfer funds to the recipient account 166 if the recipient 130 has an existing recipient account 166 with the service provider 160 .
- the user 120 may transfer funds to the recipient 130 via the service provider 160 even though the recipient 130 does not have an established account with the service provider 160 .
- the service provider 160 may obtain identity information from the recipient 130 to create and/or establish an account for the recipient 130 , such as the recipient account 166 . Accordingly, the service provider 160 may simply add more users to its service roster. In one aspect, if a user (e.g., the user 120 and/or the recipient 130 ) has an established account, the method 200 achieves a person-to-person payment network with the service provider 160 and the bill payment service 142 of the financial institution 140 serving as intermediaries.
- a user e.g., the user 120 and/or the recipient 130
- the method 200 achieves a person-to-person payment network with the service provider 160 and the bill payment service 142 of the financial institution 140 serving as intermediaries.
- the method 200 utilizes inherent features of an online banking account with the bill payment service 142 (or other similar service) such that information needed by the service provider 160 to verify an existing account or to create and verify a new account are automatically provided by the user 120 simply accessing the user's account 144 and the bill payment service 142 of the user's financial institution 140 .
- the electronic payment resource e.g., an electronic check
- the bill payment service 142 includes user information (e.g., user name, billing address, account number, and routing number)
- user information e.g., user name, billing address, account number, and routing number
- a new account may be easily created by the user 120 simply by sending a small amount of monetary funds to the service provider 160 through the bill payment service 142 of the user's financial institution 140 .
- the service provider 160 may send a message to an e-mail address related to the user 120 to inform the user 120 that the account (e.g., the user account 164 ) is active and accessible via the network.
- FIG. 3 shows one embodiment of a method 300 for facilitating one or more server-side fund transfers over a network.
- the service provider 160 interfaces and communicates with the user 120 and/or the financial institution 140 via the network to process fund transfers from, e.g., the user account 144 of the financial institution 140 to the user account 164 of the service provider 160 and/or from, e.g., the user account 164 of the service provider 160 to the recipient account 166 of the service provider 160 .
- the method 300 provides a process of account verification by utilizing the bill payment service 142 (or some other similar service) of the user's financial institution 140 , which simplifies account verification for the user and the service provider 160 while maintaining security and reliability.
- the service provider 160 receives a fund transfer request from the user 120 via the bill payment service 142 of the financial institution 140 (block 310 ).
- the service provider 160 is adapted to extract an e-mail address related to the user 120 from a memo field of the fund transfer request.
- the e-mail address may be utilized by the service provider 160 to establish and/or verify the user account 164 and/or to establish the link 150 between the user account 144 of the financial institution 140 and the user account 164 of the service provider 160 .
- the user 120 may provide an e-mail address to the service provider 160 in the fund transfer request as a user identity verifier to establish and/or verify the user account 164 and/or to establish the link 150 between the user accounts 144 , 164 of the financial institution 140 and the service provider 160 , respectively.
- an e-mail address related to the user 120 may be utilized by the service provider 160 to establish and/or verify the user account 164 with the service provider 160 and/or establish the link 150 between the user accounts 144 , 164 of the financial institution 140 and the service provider 160 , respectively.
- fund transfers may be processed seamlessly between the user accounts 144 , 164 of the financial institution 140 and the service provider 160 , respectively.
- the link 150 between the user accounts 144 , 164 is an e-mail address related to the user 120 .
- the unique identifier may comprise an e-mail address, telephone number, and/or various other types of easily remembered addresses and/or numbers related to the user 120 , without departing from the scope of the present disclosure.
- the service provider 160 is adapted to utilize the e-mail address and/or the telephone number related to the user 120 as an improved security measure to verify and/or establish one or more accounts related to the user 120 .
- the service provider 160 determines (block 314 ) whether the user 120 is an existing user having an account with service provider 160 based on information passed with the fund transfer request, such as an e-mail address related to the user 120 .
- the service provider 160 utilizes an e-mail address related to the user 120 to determine if the user 120 has an existing account, such as the user account 164 . If the user 120 has an existing or established account (e.g., the user account 164 ) with the service provider 160 , then the service provider 160 verifies access privileges (block 318 ) for the user 120 based on information stored with the user account 164 .
- the user 120 may be prompted to establish an account (block 322 ) with the service provider 160 to gain access to the user account 164 .
- the service provider 160 utilizes an e-mail address related to the user 120 to verify and/or establish the user account 164 .
- the service provider 160 may process the fund transfer request (block 326 ).
- the service provider 160 may process the fund transfer request by, e.g., linking the user account 164 of the service provider 160 to the user account 144 of the financial institution 140 .
- the link 150 facilitates seamless fund transfers between the user accounts 144 , 164 of the financial institution 140 and the service provider 160 , respectively.
- the service provider 160 may process a fund transfer request on behalf of the user 120 by, e.g., receiving funds from the user account 144 of the financial institution 140 and crediting the funds to the user account 164 of the service provider 160 .
- receiving funds from the user account 144 of the financial institution 140 and crediting the funds to the user account 164 of the service provider 160 .
- the user 120 may add the service provider 160 as a payee by providing user identity information, such as an e-mail address, payee name, and/or an account number, to the bill payment service 142 .
- the service provider 160 may receive a nominal amount of funds, such as $1, from the user's financial institution 140 through the bill payment service 142 and receive the user's identity information (e.g., an e-mail address of the user 120 related to the service provider 160 ) in a memo field of the fund transfer request.
- the service provider 160 may then receive the requested funds and then credit or deposit the received funds in the user account 164 .
- the funds may be received in the form of an electronic check or a receipt of the electronic check, which may include the user's account number and routing number associated with the user account 144 of the financial institution 140 .
- the electronic check or receipt of the electronic check may comprise an electronic or physical document.
- the service provider 160 may use information from the electronic or physical document, including a billing address of the user 120 , to verify and/or establish the user's account 164 .
- the service provider 160 may transfer the received funds or another amount of funds back to the user's account 144 with the financial institution 140 .
- the service provider 160 may simply create and/or verify the user account 164 by simply reviewing information related to the user 120 provided as part of the fund transfer request from the bill payment service 142 of the financial institution 140 .
- additional security verification may be obtained by the service provider 160 to further verify the identity of the user 120 and provide further security for verifying the link between the two accounts.
- Using the bill payment service 142 to transfer funds from the user account 144 of the financial institution 140 to the user account 164 or recipient account 166 of the service provider 160 may be achieved with email account information related to the user 120 .
- the service provider 160 may prompt the user 120 with an option to link the information related to the user accounts 144 , 164 . Accordingly, the service provider 160 may prompt the user 120 to provide at least one of a full name, address, telephone number, date of birth, and at least part of a social security number to link the user accounts 144 , 164 .
- the user 120 may be prompted to verify random deposit information.
- the service provider 160 may transfer random nominal funds (e.g., a random two-digit fund transfer, such as 34 cents or 78 cents) to the user account 144 with the financial institution 140 , and the user 120 may be prompted to verify information related to the nominal fund transfer, such as the amount deposited into the user account 144 and when the deposit occurred.
- random nominal funds e.g., a random two-digit fund transfer, such as 34 cents or 78 cents
- the service provider 160 may prompt the user 120 to login to the user account 144 via the service provider server after a fund transfer has been completed to verify or validate the fund transfer.
- the service provider 160 would then review information in both user accounts 144 , 164 to obtain and match information related to the fund transfer between the user accounts 144 , 164 .
- the obtained and matched information may include the dollar amount, the date, the memo field (e.g., email address), and/or the actual transaction identification number for the fund transfer.
- the service provider 160 may review the fund transfer initiated by the user account 164 and prompt the user 120 to login to the user account 144 via the service provider 160 so that the service provider 160 may troll (e.g., with or without user knowledge) both user accounts 144 , 164 to verify or validate information from the fund transfer between the user accounts 144 , 164 .
- bank information related to the user 120 may be utilized to establish the secondary account (i.e., the user account 164 ) with the service provider 160 .
- the secondary account i.e., the user account 164
- personal and/or banking information related to the first account (i.e., the user account 144 ) with the financial institution 140 should be protected until the service provider 160 verifies that the user 120 wants to share or link the bank information related to the first account (i.e., user account 144 ) with the secondary account (i.e., user account 164 ).
- a reason for the additional security verification is that, if funds are transferred to another person's account (e.g., the recipient account 166 related to the recipient 130 ), through the bill payment service 142 , any personal and/or banking information related to the user 120 should be protected from disclosure to the recipient 130 .
- the service provider 160 may obtain recipient information from the fund transfer request (block 330 ) as provided by the user 120 . Then, the service provider 160 determines (block 334 ) whether the recipient 130 is an existing user/recipient having an account (e.g., the recipient account 166 ) with service provider 160 based on information passed with the fund transfer request. If the recipient 130 has an established account (e.g., the recipient account 166 ) with the service provider 160 , then the service provider 160 verifies the recipient account 166 (block 342 ) for the recipient 130 based on information stored with the recipient account 164 . Otherwise, the service provider 160 may establish an account (block 338 ) for the recipient 130 on behalf of the user 120 even though the recipient 130 does not have an existing account.
- the recipient 130 has an established account (e.g., the recipient account 166 ) with the service provider 160 . If the recipient 130 has an established account (e.g., the recipient account 166 ) with the service provider 160 , then the service provider 160 verifies the recipient account
- the service provider 160 may process the fund transfer request (block 346 ).
- the service provider 160 may process a fund transfer request on behalf of the user 120 by, e.g., receiving funds from the user account 144 of the financial institution 140 and crediting the funds to the recipient account 166 of the service provider 160 .
- the service provider 160 may process a fund transfer request on behalf of the user 120 by, e.g., debiting funds from the user account 164 of the service provider 160 and crediting the funds to the recipient account 166 of the service provider 160 .
- the user 120 may add the service provider 160 and the recipient 130 as a payee.
- the user 120 may request a fund transfer from the user account 144 of the financial institution 140 to the recipient account 166 of the service provider 160 .
- the user 120 may transfer funds to the recipient account 166 if the recipient 130 has an existing recipient account 166 with the service provider 160 .
- the user 120 may transfer funds to the recipient 130 via the service provider 160 even though the recipient 130 does not have an established account with the service provider 160 .
- the service provider 160 may obtain identity information from the recipient 130 to grant the recipient 130 access to the recipient account 166 .
- the service provider 160 may simply add more users including the recipient 130 to its service roster.
- the method 300 achieves a person-to-person payment network with the service provider 160 and the bill payment service 142 of the financial institution 140 serving as intermediaries.
- the method 300 utilizes inherent features of an online banking account with the bill payment service 142 (or other similar service) such that the service provider 160 automatically utilizes information passed with a fund transfer request to verify an existing account or to create and verify a new account.
- the electronic payment resource e.g., an electronic check
- the bill payment service 142 includes recipient information (e.g., recipient name, billing address, account number, and routing number)
- recipient information e.g., recipient name, billing address, account number, and routing number
- a new account for the recipient 130 may be created by the service provider 160 simply by utilizing the recipient information passed with the fund transfer request.
- funds may be deposited in the recipient account 166 by the service provider 160 on behalf of the user 120 .
- the service provider 160 may send a message to an e-mail address related to the user 120 to inform the user 120 that the recipient account 166 is active and the fund transfer has been processed.
- FIG. 4 is a block diagram of a computer system 400 suitable for implementing one or more embodiments of the present disclosure.
- the user device may comprise a personal computing device (e.g., a personal computer, laptop, cell phone, PDA, etc.) capable of communicating with the network
- the financial institution 140 may utilize a network computing device (e.g., a network server) capable of communicating with the network
- the service provider 160 may utilize a network computing device (e.g., a network server) capable of communicating with the network.
- each of the devices utilized by the user 120 , the financial institution 140 , and the service provider 160 may be implemented as computer system 400 in a manner as follows.
- computer system 400 such as a personal computer and/or a network server, includes a bus 402 or other communication mechanism for communicating information, which interconnects subsystems and components, such as processing component 404 (e.g., processor, micro-controller, digital signal processor (DSP), etc.), system memory component 406 (e.g., RAM), static storage component 408 (e.g., ROM), disk drive component 410 (e.g., magnetic or optical), network interface component 412 (e.g., modem or Ethernet card), display component 414 (e.g., CRT or LCD), input component 416 (e.g., keyboard), and cursor control component 418 (e.g., mouse or trackball).
- processing component 404 e.g., processor, micro-controller, digital signal processor (DSP), etc.
- system memory component 406 e.g., RAM
- static storage component 408 e.g., ROM
- disk drive component 410 e.g., magnetic or optical
- network interface component 412
- computer system 400 performs specific operations by processor 404 executing one or more sequences of one or more instructions contained in system memory component 406 .
- Such instructions may be read into system memory component 406 from another computer readable medium, such as static storage component 408 or disk drive component 410 .
- static storage component 408 or disk drive component 410 may be another computer readable medium.
- hard-wired circuitry may be used in place of or in combination with software instructions to implement the present disclosure.
- Non-volatile media includes optical or magnetic disks, such as disk drive component 410
- volatile media includes dynamic memory, such as system memory component 406
- transmission media includes coaxial cables, copper wire, and fiber optics, including wires that comprise bus 402 .
- transmission media may take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications.
- Computer readable media includes, for example, floppy disk, flexible disk, hard disk, magnetic tape, any other magnetic medium, CD-ROM, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, RAM, PROM, EPROM, FLASH-EPROM, any other memory chip or cartridge, carrier wave, or any other medium from which a computer is adapted to read.
- execution of instruction sequences to practice the present disclosure may be performed by the computer system 400 .
- a plurality of computer systems 400 coupled by communication link 420 to the network e.g., such as a LAN, WLAN, PTSN, and/or various other wired or wireless networks, including telecommunications, mobile, and cellular phone networks
- the network e.g., such as a LAN, WLAN, PTSN, and/or various other wired or wireless networks, including telecommunications, mobile, and cellular phone networks
- Computer system 400 may transmit and receive messages, data, information and instructions, including one or more programs (i.e., application code) through communication link 420 and communication interface 412 .
- Received program code may be executed by processor 404 as received and/or stored in disk drive component 410 or some other non-volatile storage component for execution.
- various embodiments provided by the present disclosure may be implemented using hardware, software, or combinations of hardware and software.
- the various hardware components and/or software components set forth herein may be combined into composite components comprising software, hardware, and/or both without departing from the spirit of the present disclosure.
- the various hardware components and/or software components set forth herein may be separated into sub-components comprising software, hardware, or both without departing from the scope of the present disclosure.
- software components may be implemented as hardware components and vice-versa.
- Software in accordance with the present disclosure, such as program code and/or data, may be stored on one or more computer readable mediums. It is also contemplated that software identified herein may be implemented using one or more general purpose or specific purpose computers and/or computer systems, networked and/or otherwise. Where applicable, the ordering of various steps described herein may be changed, combined into composite steps, and/or separated into sub-steps to provide features described herein.
Abstract
In accordance with embodiments of the present disclosure, systems and methods for facilitating financial transactions over a network include communicating with a financial institution over the network, wherein the financial institution includes a first user account related to a user. The systems and methods include receiving a fund transfer request from the financial institution on behalf of the user and establishing a second user account related to the user based on user information passed with the fund transfer request. The systems and methods include processing the fund transfer request by linking the first user account to the second user account based on the user information passed with the fund transfer request, receiving funds from the financial institution associated with the first user account, and depositing the received funds in the second user account on behalf of the user.
Description
- This application claims priority to and benefit of U.S. Provisional Patent Application Ser. No. 61/083,004, filed on Jul. 23, 2008. This application is also a continuation application of U.S. patent application Ser. No. 12/415,669, filed on Mar. 31, 2009. The contents of both applications are hereby incorporated by reference in their entirety.
- The present invention generally relates to network transactions and, more particularly, to facilitating fund transfers over a network.
- In electronic banking and commerce, a user typically accesses accounts and conducts financial transactions through electronic communications with online service providers over communication networks, such as the Internet. Typically, when potential users sign up or use a service for processing payments and fund transfers through the Internet, the user steps through a series of steps to verify identity and a funding source. These steps ensure that an account where funds are being transferred out of or into is indeed an account associated with the user and not an unauthorized account.
- Conventional techniques include inputting and verifying user provided information, such as account numbers, routing information, and billing address, which can often be cumbersome and time-consuming for the user. These conventional techniques may include the user typing in bank information, such as an account number and a routing number. In one instance, the online service provider may deposit a small amount of funds (e.g., 2 cents) into the user's bank account, typically a few days after the information is entered. The user then periodically checks the user's account to verify whether any small deposits have been received. Once received, the user accesses the online service provider to confirm the deposit to the account.
- Unfortunately, these conventional techniques are time consuming and effort intensive and typically require the user to perform several steps and navigation events for deposit verification and settlement. As such, there currently exists a need to improve a user's experience during financial transactions including fund transfers over a network.
-
FIG. 1 shows a block diagram of a system adapted to facilitate fund transfers over a network, in accordance with an embodiment of the present disclosure. -
FIG. 2 shows one embodiment of a method for facilitating user-side fund transfers over a network, in accordance with an embodiment of the present disclosure. -
FIG. 3 shows one embodiment of a method for facilitating server-side processing of fund transfers over a network, in accordance with an embodiment of the present disclosure. -
FIG. 4 is a block diagram of a computer system suitable for implementing one or more embodiments of the present disclosure. - Embodiments of the present disclosure and their advantages are best understood by referring to the detailed description that follows. It should be appreciated that like reference numerals are used to identify like elements illustrated in one or more of the figures, wherein showings therein are for purposes of illustrating embodiments of the present disclosure and not for purposes of limiting the same.
- In accordance with one or more embodiments of the present disclosure, a system for facilitating financial transactions by a service provider over a network is disclosed. The system includes a network interface, a memory, and one or more processors. The network interface communicates with a financial institution over the network. The financial institution has a first user account belonging to a user. The memory stores machine-readable instructions for execution by the one or more processors. The one or more processors execute the instructions to receive a fund transfer request from the financial institution on behalf of the user. The fund transfer request includes user information that is related to the first user account. The one or more processors also verify that the user has an existing account with the service provider based on the user information related to the first user that is passed with the fund transfer request. The one or more processors further process the fund transfer request to receive funds from the financial institution associated with the first user account and to deposit the received funds in the existing account of the user with the service provider on behalf of the user.
- In accordance with one or more embodiments of the present disclosure, a method for facilitating financial transactions by a service provider over a network is disclosed. The method includes receiving by a network server of the service provider a fund transfer request from a financial institution on behalf of a user. The financial institution has a first user account belonging to the user. The fund transfer request includes user information that is related to the first user account. The method also includes verifying that the user has an existing account with the service provider based on the user information related to the first user that is passed with the funds transfer request. The method further includes processing the fund transfer request by receiving funds from the financial institution associated with the first user account and depositing the received funds in the existing user account on behalf of the user.
- In accordance with one or more embodiments of the present disclosure, a non-transitory computer readable medium having computer readable code for instructing a processor to perform a method to facilitate financial transaction over a network is disclosed. The method includes communicating with a financial institution over the network. The financial institution has a first user account belonging to a user. The method also includes receiving a fund transfer request from the financial institution on behalf of the user. The fund transfer request includes user information that is related to the first user account. The method further includes verifying that the user has an existing account with the service provider based on the user information related to the first user that is passed with the funds transfer request. The method further includes processing the fund transfer request by receiving funds from the financial institution associated with the first user account and depositing the received funds in the existing user account on behalf of the user.
- Refer now to the figures wherein the drawings are for purposes of illustrating embodiments of the present disclosure only, and not for purposes of limiting the same.
FIG. 1 shows one embodiment of asystem 100 for facilitating financial transactions including fund transfers over a network, such as the Internet.System 100 includes a user 120 (e.g., a client or customer) adapted to interface with a financial institution 140 (e.g., a bank or credit union) and a service provider 160 (e.g., a network based financial transaction service provider) over a network. - The
user 120, in one embodiment, is able to establish auser account 144 with thefinancial institution 140, such as a bank, wherein theuser 120 may deposit monetary funds in theuser account 144. Thefinancial institution 140 is adapted to provide theuser 120 with access to theuser account 144 and to abill payment service 142 via the network. In one aspect, theuser 120 may request network based transactions, such as fund transfers (e.g., deposits and/or debits) between accounts, over the network in a manner as described in greater detail herein. In another aspect, thefinancial institution 140 may provide theuser 120 with some form of payment media, such as an electronic payment resource, that is linked to theuser account 144. In this instance, theuser 120 may utilize the payment media to access funds in theuser account 144. - In one implementation, the
user 120 may utilize thebill payment service 142 to transfer funds from theuser account 144 of the financial institution to auser account 164 of theservice provider 160 via the network. Thebill payment service 142 is adapted to process the fund transfer between theuser 120 and theservice provider 160 via the network. In one aspect, thebill payment service 142 may communicate with a clearing house to debit theuser account 144 of thefinancial institution 140 in accordance with an amount specific to the fund transfer and credit theuser account 164 of theservice provider 160 over the network. - The
user 120, in one embodiment, is able to establish one or more user accounts (e.g., the user account 164) with theservice provider 160, wherein theuser 120 may deposit monetary funds in theuser account 164 either directly or from theuser account 144 of thefinancial institution 140. Theservice provider 160 is adapted to provide theuser 120 with access to theuser account 164 via the network. In one aspect, theservice provider 160 may provide theuser 120 with some form of electronic payment resource that is linked to theuser account 164. As such, in this instance, theuser 120 may utilize the electronic payment resource to access funds in theuser account 164. - In one aspect, a
link 150 may be established between theuser account 144 of thefinancial institution 140 and one or more other accounts with other financial institutions and/or network based service providers, such as theservice provider 160. For example, theuser 120 may provide an e-mail address to theservice provider 160 as a unique identifier (i.e., a user identity verifier) so that thelink 150 may be established between theuser account 144 of thefinancial institution 140 and theuser account 164 of theservice provider 160. Accordingly, an e-mail address may be utilized by theuser 120 to establish theuser account 164 with theservice provider 160, wherein thelink 150 between the user accounts 144, 164 is an e-mail address related to theuser 120. After linking user accounts 144, 164 via, e.g., an e-mail address, fund transfers may be processed seamlessly between the user accounts 144, 164 of thefinancial institution 140 and theservice provider 160, respectively. It should be appreciated that, in various embodiments, the unique identifier (i.e., the user identity verifier) may comprise an e-mail address, telephone number, and/or various other types of easily remembered addresses and/or numbers related to theuser 120, without departing from the scope of the present disclosure. - In another aspect, for security concerns, additional security verification may be obtained by the
service provider 160 to further verify the identity of theuser 120 and provide further security for verifying the link between the two accounts. When the user accounts 144, 164 are considered linked, theuser 120 is presumed to be the same person having permission to access both user accounts 144, 164. However, after a nominal fund transfer takes place, theuser 120 may be prompted with an option to link the information related to the user accounts 144, 164, wherein theuser 120 may be prompted by theservice provider 160 to provide at least one of a full name, address, telephone number, date of birth, and at least part of a social security number to link the user accounts 144, 164. Theuser 120 may be prompted to verify random deposit information. For example, theservice provider 160 may transfer nominal funds (e.g., a penny or a dollar) to theuser account 144 with thefinancial institution 140, and theuser 120 may be prompted to verify information related to the nominal fund transfer, such as the amount deposited into theuser account 144 and when the deposit occurred. In another example, theuser 120 may be prompted to login to theuser account 144 after a nominal fund transfer has been completed by theservice provider 160 to verify the nominal fund transfer. - In one embodiment, bank information related to the
user 120 may be utilized to establish theuser account 164 with theservice provider 160. However, personal and/or banking information related to theuser account 144 with thefinancial institution 140 should be protected until theservice provider 160 verifies that theuser 120 wants to share or link the bank information related to theuser account 144 with theuser account 164. - In one implementation, the
user 120 may allow or grant permission to theservice provider 160 to transfer funds from theuser account 164 of theservice provider 160 to another user account of theservice provider 160, such as arecipient account 166 related to a recipient 130 (e.g., another user, client, or customer having a user account with the service provider 160). Aprocessing component 162 of theservice provider 160 is adapted to process the fund transfer between theuser account 164 and therecipient account 166. In one aspect, theservice provider 160 may directly transfer funds between theuser account 164 and therecipient account 166. In this instance, theservice provider 160 may directly debit theuser account 164 and directly credit therecipient account 166 because both of theaccounts service provider 160. In another aspect, the service provider may use a clearing house to debit theuser account 164 in accordance with an amount specific to the fund transfer and credit therecipient account 166 over the network. In this instance, theservice provider 160 may optionally process the fund transfer through a clearing house even though theaccounts service provider 160. - In one embodiment, a clearing house (not shown) resolves financial transactions through validation, delivery, and settlement. As such, the clearing house may comprise an agency or institution having a system for settling indebtedness between members of that system through which accounts may be debited and/or credited of monetary funds.
- In one embodiment, one or more fund transfers between the
user 120, therecipient 130, thefinancial institution 140, and theservice provider 160 may take place over the network, such as a single network or a combination of multiple networks. For example, in various embodiments, the network may include the Internet and/or one or more intranets, landline networks, wireless networks, and/or other appropriate types of communication networks. In another example, the network may include a wireless telecommunications network (e.g., cellular phone network) adapted to interface and communicate with other communication networks, such as the Internet. As such, in one aspect, theuser 120, therecipient 130, thefinancial institution 140, and theservice provider 160 may be associated with a particular link (e.g., a link, such as a URL (Uniform Resource Locator) to an IP (Internet Protocol) address). - The
user 120, in one embodiment, may utilize a network interface device, such as a personal computer (i.e., PC), a wireless telephone (e.g., cellular phone), a personal digital assistant (i.e., PDA), a notebook computer, and/or various other generally known types of wired and/or wireless computing devices, to communicate and interface with thefinancial institution 140 and/or theservice provider 160 to access respective user accounts 144, 164 via any appropriate combination of hardware and/or software configured for wired and/or wireless communication over the network. For instance, theuser 120 may utilize a network interface application (e.g., a network browser application) to communicate and interface with thefinancial institution 140 and/or theservice provider 160 to access user accounts 144, 164, respectively, via the network. As such, in one example, theuser 120 may use a web browser to access the user accounts 144, 164 over the Internet. - The user device, in various embodiments, may include other applications as may be desired in one or more embodiments of the present disclosure to provide additional features available to the
user 120. In one example, these other applications may include security applications for implementing user-side security features, programmatic client applications for interfacing with appropriate application programming interfaces (APIs) over the network, and/or various other types of generally known programs and/or software applications. In still other examples, these other applications may interface with the network interface application for improved efficiency and convenience. - The user device, in one embodiment, may include at least one user identifier, which may be implemented, e.g., as operating system registry entries, cookies associated with the network interface application, identifiers associated with hardware of the user device, and/or various other appropriate identifiers. The user identifier may include one or more attributes and/or parameters associated with the user, such as personal information related to the user (e.g., one or more user names, passwords, photograph images, biometric ids, addresses, phone numbers, etc.) and banking information (e.g., one or more banking institutions, credit card issuers, user account numbers, security data and information, etc.). In various aspects, the user identifier may be passed with a login request and/or fund transfer request to the
financial institution 140 and/or theservice provider 160 via the network, and the user identifier may be used by thefinancial institution 140 and/or theservice provider 160 to associate theuser 120 withuser accounts - In one embodiment, as with the
user 120, therecipient 130 may utilize a network interface device, such as a PC, a wireless telephone, a PDA, a notebook computer, and/or various other generally known types of wired and/or wireless computing devices, to communicate and interface with theservice provider 160 to access therecipient account 166 via any appropriate combination of hardware and/or software configured for wired and/or wireless communication over the network. For instance, therecipient 130 may utilize a network interface application to communicate and interface with theservice provider 160 to access therecipient account 166 via the network. As such, in this instance, therecipient 130 may use a web browser to access therecipient account 166 over the Internet. Even though not shown, it should be appreciated that therecipient 130 may have a recipient account with thefinancial institution 140, without departing from the scope of the present disclosure. As such, therecipient 130 would also be able to access a recipient account with thefinancial institution 140 over the network. - In one embodiment, the
financial institution 140 and/or theservice provider 160 may maintain one or more servers on the network for processing financial transactions including fund transfers over the network. In this instance, each of the one or more servers for thefinancial institution 140 and/or theservice provider 160 may include one or more databases for storing information related to thebill payment service 142, the user accounts 144, 164, and therecipient account 166, respectively. Each of the one or more servers for thefinancial institution 140 and/or theservice provider 160 may include some form of network interface application configured to provide access to thebill payment service 142, the user accounts 144, 164, and therecipient account 166, respectively, over the network to theuser 120 and therecipient 130, respectively. For example, theuser 120 may interact with the network interface application through a browser application over the network to access one or more of the user accounts 144, 164. - The
service provider 160, in one embodiment, is adapted to process financial transitions including fund transfers over the network on behalf of theuser 120 and/or therecipient 130. In this instance, theservice provider 160 may utilize some form of fund transfer and settlement application configured to interact with theuser 120 and/or therecipient 130 to facilitate fund transfers. In one example, theservice provider 160 may be provided by PayPal, Inc. of San Jose, Calif., USA. - The
service provider 160, in one embodiment, may be configured to maintain a plurality of accounts (e.g.,user account 164 and recipient account 166), each of which may include account information associated withuser 120 and/or therecipient 130. For example, account information may include private financial information of theuser 120 and/or therecipient 130, such as one or more account numbers, passwords, credit card information, banking information, or other types of financial information, which may be used to facilitate financial transactions including fund transfers over the network. In various implementations, thesystem 100 described herein may be modified to accommodate users and/or recipients that may or may not be associated with at least one existing account, without departing from the scope of the present disclosure. - In one embodiment, the
user 120 and/or therecipient 130 may have identity attributes stored with thefinancial institution 140 and/or theservice provider 160, and theuser 120 and/or therecipient 130 may have credentials to authenticate or verify identity with thefinancial institution 140 and/or theservice provider 160. In one aspect, user attributes may include personal information and/or banking information, as previously described. In various aspects, the user attributes may be passed to thefinancial institution 140 and/or theservice provider 160 as part of a login, account access request, fund transfer request, and/or payment request, and the user attributes may be utilized by thefinancial institution 140 and/or theservice provider 160 to associate theuser 120 and/or therecipient 130 with the user accounts 144, 164, respectively, which are maintained by thefinancial institution 140 and/or theservice provider 160, respectively. - In one embodiment, the
financial institution 140 and/or theservice provider 160 may be associated with at least one identifier, which may be included as part of a financial transaction including a fund transfer. The identifier may include one or more attributes and/or parameters related to thefinancial institution 140 and/or theservice provider 160, such as business and/or banking information. In one example, the identifier for thefinancial institution 140 may be passed to theservice provider 160 when theuser 120 requests a fund transfer from thefinancial institution 140 to theservice provider 160. In this instance, the identifier may be used by theservice provider 160 to identify and/or verify theuser account 144 in reference to thefinancial institution 140. - In one embodiment, the
processing component 162 of theservice provider 160 may utilize a processing module to process fund transfers between accounts, such as the user accounts 144, 164 and therecipient account 166. In one implementation, the processing module is adapted to assist with resolving financial transactions including fund transfers through validation, delivery, and settlement. For example, theprocessing component 162 in conjunction with the processing module may be adapted to resolve fund transfers between theuser 120 and therecipient 130, wherein theaccounts -
FIG. 2 shows one embodiment of amethod 200 for facilitating one or more user-side fund transfers over a network. The following description ofFIG. 2 and thecorresponding method 200 references thesystem 100 ofFIG. 1 . Referring toFIG. 1 , theuser 120 interfaces and communicates with thefinancial institution 140 and/or theservice provider 160 via the network to request fund transfers from, e.g., theuser account 144 of thefinancial institution 140 to theuser account 164 of theservice provider 160 and/or from, e.g., theuser account 164 of theservice provider 160 to therecipient account 166 of theservice provider 160. - In one implementation, the
method 200 provides a process of account verification by utilizing the bill payment service 142 (or some other similar service) of the user'sfinancial institution 140, which simplifies account verification for the user while maintaining security and reliability. Referring toFIG. 2 , theuser 120 provides a login request to the financial institution 140 (block 210) to access the user account 144 (block 214). Then, when theuser 120 attempts to access thebill payment service 142, thefinancial institution 140 determines (block 218) whether theuser 120 is a current user of thebill payment service 142 by, e.g., verifying access privileges for theuser 120 based on information stored with theuser account 144. If theuser 120 has been granted access privileges for thebill payment service 142, then theuser 120 may proceed to access the bill payment service 142 (block 226). Otherwise, theuser 120 may be prompted to enroll in the bill payment service 142 (block 222) to gain access privileges for thebill payment service 142 and then proceed to access the bill payment service 142 (block 226). - Once the
user 120 is granted access to thebill payment service 142 of the user's financial institution 140 (block 226), theuser 120 may add theservice provider 160 as a biller or payee (block 230) to link 150 theuser account 144 of thefinancial institution 140 to theuser account 164 of theservice provider 160. - As previously described, the
link 150 may be established between theuser account 144 of thefinancial institution 140 and theuser account 164 of theservice provider 160. In one aspect, theuser 120 may provide an e-mail address to theservice provider 160 as a user identity verifier so that thelink 150 may be established between theuser account 144 of thefinancial institution 140 and theuser account 164 of theservice provider 160. In one aspect, additional security verification may be obtained by theservice provider 160 to further verify the identity of theuser 120 and provide further security for verifying the link between the two accounts. The additional security verification is described in greater detail herein. - As such, in one embodiment, the
link 150 between the user accounts 144, 164 is an e-mail address related to theuser 120. Accordingly, an e-mail address may be utilized by theuser 120 to establish theuser account 164 with theservice provider 160. After linking user accounts 144, 164 via, e.g., an e-mail address, fund transfers may be processed seamlessly between the user accounts 144, 164 of thefinancial institution 140 and theservice provider 160, respectively. - Next, the
user 120 may request a fund transfer from theuser account 144 of thefinancial institution 140 to theuser account 164 of the service provider 160 (block 234). In one implementation, theuser 120 adds theservice provider 160 as a payee by, e.g., entering user identity information, such as one or more of an e-mail address, payee name, and/or an account number. Theuser 120 then transfers a nominal amount, such as $1, to theservice provider 160 through thebill payment service 142 and enters the user's identity information (e.g., an e-mail address of theuser 120 for the service provider 160) in a memo field of the fund transfer request. Thebill payment service 142 then transfers the requested funds to theservice provider 160 by, e.g., sending an electronic check or a receipt of the electronic check to theservice provider 160, which includes the user's account number and routing number associated with theuser account 144 of thefinancial institution 140. - In one aspect, the electronic check or receipt of the electronic check may comprise an electronic document or a physical document. The
service provider 160 may use information from the document, including a billing address, to verify and/or establish the user'saccount 164 with theservice provider 160. In one example, theservice provider 160 may transfer the same funds or another amount of funds back to the user'sfinancial institution 140. As such, in this instance, theuser 120 may simply create and/or access theuser account 164 with theservice provider 160 by simply signing up theservice provider 160 as payee through thebill payment service 142 of thefinancial institution 140 instead of providing specific account information including account numbers, checking deposits, etc. - In another aspect, additional security verification may be obtained by the
service provider 160 to further verify the identity of theuser 120 and provide further security for verifying the link between the two accounts. Using thebill payment service 142 to transfer funds from theuser account 144 of thefinancial institution 140 to theuser account 164 orrecipient account 166 of theservice provider 160 may be achieved with email account information related to theuser 120. However, for security concerns, when the user accounts 144, 164 are considered linked, a presumption may be made that theuser 120 is the same person having permission to access both user accounts 144, 164. Thus, in one embodiment, after an initial fund transfer takes place (block 234), theuser 120 may be prompted with an option to link the information related to the user accounts 144, 164. Accordingly, theuser 120 may be prompted by theservice provider 160 to provide at least one of a full name, address, telephone number, date of birth, and at least part of a social security number to link the user accounts 144, 164. Theuser 120 may be prompted to verify random deposit information. For example, theservice provider 160 may transfer random nominal funds (e.g., a random two-digit fund transfer, such as 34 cents or 78 cents) to theuser account 144 with thefinancial institution 140, and theuser 120 may be prompted to verify information related to the nominal fund transfer, such as the amount deposited into theuser account 144 and when the deposit occurred. - In another example, the
service provider 160 may prompt theuser 120 to login to theuser account 144 via the service provider server after a fund transfer has been completed to verify or validate the fund transfer. Theservice provider 160 would then review information in both user accounts 144, 164 to obtain and match information related to the fund transfer between the user accounts 144, 164. For example, the obtained and matched information may include the dollar amount, the date, the memo field (e.g., email address), and/or the actual transaction identification number for the fund transfer. In other words, theservice provider 160 may review the fund transfer initiated by theuser account 164 and prompt theuser 120 to login to theuser account 144 via theservice provider 160 so that theservice provider 160 may troll (e.g., with or without user action) both user accounts 144, 164 to verify or validate information from the fund transfer between the user accounts 144, 164. - Accordingly, bank information related to the
user 120 may be utilized to establish the secondary account (i.e., the user account 164) with theservice provider 160. However, in one aspect, personal and/or banking information related to the first account (i.e., the user account 144) with thefinancial institution 140 should be protected until theservice provider 160 verifies that theuser 120 wants to share or link the bank information related to the first account (i.e., user account 144) with the secondary account (i.e., user account 164). In one aspect, a reason for the additional security verification is that, if funds are transferred to another person's account (e.g., therecipient account 166 related to the recipient 130), through thebill payment service 142, any personal and/or banking information related to theuser 120 should be protected from disclosure to therecipient 130. - Moreover, since the
user 120 is granted access to thebill payment service 142 of the user's financial institution 140 (block 226), theuser 120 may add theservice provider 160 and therecipient 130 as a biller or payee (block 238). Next, theuser 120 may request a fund transfer from theuser account 144 of thefinancial institution 140 to therecipient account 166 of the service provider 160 (block 238). As such, in one implementation, theuser 120 may transfer funds to therecipient account 166 if therecipient 130 has an existingrecipient account 166 with theservice provider 160. However, in another implementation, theuser 120 may transfer funds to therecipient 130 via theservice provider 160 even though therecipient 130 does not have an established account with theservice provider 160. In this instance, when therecipient 130 attempts to access funds from theservice provider 160, theservice provider 160 may obtain identity information from therecipient 130 to create and/or establish an account for therecipient 130, such as therecipient account 166. Accordingly, theservice provider 160 may simply add more users to its service roster. In one aspect, if a user (e.g., theuser 120 and/or the recipient 130) has an established account, themethod 200 achieves a person-to-person payment network with theservice provider 160 and thebill payment service 142 of thefinancial institution 140 serving as intermediaries. - As described herein, the
method 200 utilizes inherent features of an online banking account with the bill payment service 142 (or other similar service) such that information needed by theservice provider 160 to verify an existing account or to create and verify a new account are automatically provided by theuser 120 simply accessing the user'saccount 144 and thebill payment service 142 of the user'sfinancial institution 140. In one aspect, since the electronic payment resource (e.g., an electronic check) from thebill payment service 142 includes user information (e.g., user name, billing address, account number, and routing number), a new account may be easily created by theuser 120 simply by sending a small amount of monetary funds to theservice provider 160 through thebill payment service 142 of the user'sfinancial institution 140. Once an account is verified, theservice provider 160 may send a message to an e-mail address related to theuser 120 to inform theuser 120 that the account (e.g., the user account 164) is active and accessible via the network. -
FIG. 3 shows one embodiment of amethod 300 for facilitating one or more server-side fund transfers over a network. The following description ofFIG. 3 andcorresponding method 300 references thesystem 100 ofFIG. 1 . Referring toFIG. 1 , theservice provider 160 interfaces and communicates with theuser 120 and/or thefinancial institution 140 via the network to process fund transfers from, e.g., theuser account 144 of thefinancial institution 140 to theuser account 164 of theservice provider 160 and/or from, e.g., theuser account 164 of theservice provider 160 to therecipient account 166 of theservice provider 160. - In one implementation, the
method 300 provides a process of account verification by utilizing the bill payment service 142 (or some other similar service) of the user'sfinancial institution 140, which simplifies account verification for the user and theservice provider 160 while maintaining security and reliability. Referring toFIG. 3 , theservice provider 160 receives a fund transfer request from theuser 120 via thebill payment service 142 of the financial institution 140 (block 310). - In one embodiment, the
service provider 160 is adapted to extract an e-mail address related to theuser 120 from a memo field of the fund transfer request. The e-mail address may be utilized by theservice provider 160 to establish and/or verify theuser account 164 and/or to establish thelink 150 between theuser account 144 of thefinancial institution 140 and theuser account 164 of theservice provider 160. As such, in one aspect, theuser 120 may provide an e-mail address to theservice provider 160 in the fund transfer request as a user identity verifier to establish and/or verify theuser account 164 and/or to establish thelink 150 between the user accounts 144, 164 of thefinancial institution 140 and theservice provider 160, respectively. Accordingly, an e-mail address related to theuser 120 may be utilized by theservice provider 160 to establish and/or verify theuser account 164 with theservice provider 160 and/or establish thelink 150 between the user accounts 144, 164 of thefinancial institution 140 and theservice provider 160, respectively. After linking the user accounts 144, 164 via, e.g., an e-mail address, fund transfers may be processed seamlessly between the user accounts 144, 164 of thefinancial institution 140 and theservice provider 160, respectively. In accordance with one or more embodiments, thelink 150 between the user accounts 144, 164 is an e-mail address related to theuser 120. - It should be appreciated that, in various embodiments, the unique identifier (i.e., the user identity verifier) may comprise an e-mail address, telephone number, and/or various other types of easily remembered addresses and/or numbers related to the
user 120, without departing from the scope of the present disclosure. It should also be appreciated that using an e-mail address and/or a telephone number related to theuser 120 for account identity verification makes the matching and/or creation of another user account (i.e., theuser account 164 with the service provider 160) much easier, simpler, and safer. As such, theservice provider 160 is adapted to utilize the e-mail address and/or the telephone number related to theuser 120 as an improved security measure to verify and/or establish one or more accounts related to theuser 120. - Next, the
service provider 160 determines (block 314) whether theuser 120 is an existing user having an account withservice provider 160 based on information passed with the fund transfer request, such as an e-mail address related to theuser 120. Preferably, theservice provider 160 utilizes an e-mail address related to theuser 120 to determine if theuser 120 has an existing account, such as theuser account 164. If theuser 120 has an existing or established account (e.g., the user account 164) with theservice provider 160, then theservice provider 160 verifies access privileges (block 318) for theuser 120 based on information stored with theuser account 164. Otherwise, theuser 120 may be prompted to establish an account (block 322) with theservice provider 160 to gain access to theuser account 164. Preferably, theservice provider 160 utilizes an e-mail address related to theuser 120 to verify and/or establish theuser account 164. - Once the
user account 164 is verified and/or established, then theservice provider 160 may process the fund transfer request (block 326). In one aspect, theservice provider 160 may process the fund transfer request by, e.g., linking theuser account 164 of theservice provider 160 to theuser account 144 of thefinancial institution 140. Thelink 150 facilitates seamless fund transfers between the user accounts 144, 164 of thefinancial institution 140 and theservice provider 160, respectively. In one implementation, theservice provider 160 may process a fund transfer request on behalf of theuser 120 by, e.g., receiving funds from theuser account 144 of thefinancial institution 140 and crediting the funds to theuser account 164 of theservice provider 160. As previously described in reference tomethod 200 ofFIG. 2 , theuser 120 may add theservice provider 160 as a payee by providing user identity information, such as an e-mail address, payee name, and/or an account number, to thebill payment service 142. As part of the fund transfer request, theservice provider 160 may receive a nominal amount of funds, such as $1, from the user'sfinancial institution 140 through thebill payment service 142 and receive the user's identity information (e.g., an e-mail address of theuser 120 related to the service provider 160) in a memo field of the fund transfer request. Theservice provider 160 may then receive the requested funds and then credit or deposit the received funds in theuser account 164. In one example, the funds may be received in the form of an electronic check or a receipt of the electronic check, which may include the user's account number and routing number associated with theuser account 144 of thefinancial institution 140. - In one aspect, as previously described, the electronic check or receipt of the electronic check may comprise an electronic or physical document. The
service provider 160 may use information from the electronic or physical document, including a billing address of theuser 120, to verify and/or establish the user'saccount 164. In one implementation, theservice provider 160 may transfer the received funds or another amount of funds back to the user'saccount 144 with thefinancial institution 140. As such, in this instance, theservice provider 160 may simply create and/or verify theuser account 164 by simply reviewing information related to theuser 120 provided as part of the fund transfer request from thebill payment service 142 of thefinancial institution 140. - In another aspect, additional security verification may be obtained by the
service provider 160 to further verify the identity of theuser 120 and provide further security for verifying the link between the two accounts. Using thebill payment service 142 to transfer funds from theuser account 144 of thefinancial institution 140 to theuser account 164 orrecipient account 166 of theservice provider 160 may be achieved with email account information related to theuser 120. However, for security concerns, after an initial fund transfer takes place, theservice provider 160 may prompt theuser 120 with an option to link the information related to the user accounts 144, 164. Accordingly, theservice provider 160 may prompt theuser 120 to provide at least one of a full name, address, telephone number, date of birth, and at least part of a social security number to link the user accounts 144, 164. In addition, theuser 120 may be prompted to verify random deposit information. For example, theservice provider 160 may transfer random nominal funds (e.g., a random two-digit fund transfer, such as 34 cents or 78 cents) to theuser account 144 with thefinancial institution 140, and theuser 120 may be prompted to verify information related to the nominal fund transfer, such as the amount deposited into theuser account 144 and when the deposit occurred. - In another example, the
service provider 160 may prompt theuser 120 to login to theuser account 144 via the service provider server after a fund transfer has been completed to verify or validate the fund transfer. Theservice provider 160 would then review information in both user accounts 144, 164 to obtain and match information related to the fund transfer between the user accounts 144, 164. For example, the obtained and matched information may include the dollar amount, the date, the memo field (e.g., email address), and/or the actual transaction identification number for the fund transfer. In other words, theservice provider 160 may review the fund transfer initiated by theuser account 164 and prompt theuser 120 to login to theuser account 144 via theservice provider 160 so that theservice provider 160 may troll (e.g., with or without user knowledge) both user accounts 144, 164 to verify or validate information from the fund transfer between the user accounts 144, 164. - Accordingly, bank information related to the
user 120 may be utilized to establish the secondary account (i.e., the user account 164) with theservice provider 160. However, in one aspect, personal and/or banking information related to the first account (i.e., the user account 144) with thefinancial institution 140 should be protected until theservice provider 160 verifies that theuser 120 wants to share or link the bank information related to the first account (i.e., user account 144) with the secondary account (i.e., user account 164). In one aspect, a reason for the additional security verification is that, if funds are transferred to another person's account (e.g., therecipient account 166 related to the recipient 130), through thebill payment service 142, any personal and/or banking information related to theuser 120 should be protected from disclosure to therecipient 130. - Next, the
service provider 160 may obtain recipient information from the fund transfer request (block 330) as provided by theuser 120. Then, theservice provider 160 determines (block 334) whether therecipient 130 is an existing user/recipient having an account (e.g., the recipient account 166) withservice provider 160 based on information passed with the fund transfer request. If therecipient 130 has an established account (e.g., the recipient account 166) with theservice provider 160, then theservice provider 160 verifies the recipient account 166 (block 342) for therecipient 130 based on information stored with therecipient account 164. Otherwise, theservice provider 160 may establish an account (block 338) for therecipient 130 on behalf of theuser 120 even though therecipient 130 does not have an existing account. - Once the
recipient account 166 is verified and/or established, then theservice provider 160 may process the fund transfer request (block 346). In one implementation, theservice provider 160 may process a fund transfer request on behalf of theuser 120 by, e.g., receiving funds from theuser account 144 of thefinancial institution 140 and crediting the funds to therecipient account 166 of theservice provider 160. In another implementation, theservice provider 160 may process a fund transfer request on behalf of theuser 120 by, e.g., debiting funds from theuser account 164 of theservice provider 160 and crediting the funds to therecipient account 166 of theservice provider 160. - As previously described in reference to
method 200 ofFIG. 2 , theuser 120 may add theservice provider 160 and therecipient 130 as a payee. As such, theuser 120 may request a fund transfer from theuser account 144 of thefinancial institution 140 to therecipient account 166 of theservice provider 160. Theuser 120 may transfer funds to therecipient account 166 if therecipient 130 has an existingrecipient account 166 with theservice provider 160. Theuser 120 may transfer funds to therecipient 130 via theservice provider 160 even though therecipient 130 does not have an established account with theservice provider 160. In this instance, when therecipient 130 attempts to access funds from theservice provider 160, theservice provider 160 may obtain identity information from therecipient 130 to grant therecipient 130 access to therecipient account 166. Accordingly, theservice provider 160 may simply add more users including therecipient 130 to its service roster. In one aspect, themethod 300 achieves a person-to-person payment network with theservice provider 160 and thebill payment service 142 of thefinancial institution 140 serving as intermediaries. - As described herein, the
method 300 utilizes inherent features of an online banking account with the bill payment service 142 (or other similar service) such that theservice provider 160 automatically utilizes information passed with a fund transfer request to verify an existing account or to create and verify a new account. In one aspect, since the electronic payment resource (e.g., an electronic check) from thebill payment service 142 includes recipient information (e.g., recipient name, billing address, account number, and routing number), a new account for therecipient 130 may be created by theservice provider 160 simply by utilizing the recipient information passed with the fund transfer request. As such, funds may be deposited in therecipient account 166 by theservice provider 160 on behalf of theuser 120. Once an account is verified, theservice provider 160 may send a message to an e-mail address related to theuser 120 to inform theuser 120 that therecipient account 166 is active and the fund transfer has been processed. -
FIG. 4 is a block diagram of acomputer system 400 suitable for implementing one or more embodiments of the present disclosure. In various implementations, the user device may comprise a personal computing device (e.g., a personal computer, laptop, cell phone, PDA, etc.) capable of communicating with the network, thefinancial institution 140 may utilize a network computing device (e.g., a network server) capable of communicating with the network, and theservice provider 160 may utilize a network computing device (e.g., a network server) capable of communicating with the network. It should be appreciated that each of the devices utilized by theuser 120, thefinancial institution 140, and theservice provider 160 may be implemented ascomputer system 400 in a manner as follows. - In accordance with various embodiments of the present disclosure,
computer system 400, such as a personal computer and/or a network server, includes abus 402 or other communication mechanism for communicating information, which interconnects subsystems and components, such as processing component 404 (e.g., processor, micro-controller, digital signal processor (DSP), etc.), system memory component 406 (e.g., RAM), static storage component 408 (e.g., ROM), disk drive component 410 (e.g., magnetic or optical), network interface component 412 (e.g., modem or Ethernet card), display component 414 (e.g., CRT or LCD), input component 416 (e.g., keyboard), and cursor control component 418 (e.g., mouse or trackball). In one implementation,disk drive component 410 may comprise a database having one or more disk drive components. - In accordance with embodiments of the present disclosure,
computer system 400 performs specific operations byprocessor 404 executing one or more sequences of one or more instructions contained insystem memory component 406. Such instructions may be read intosystem memory component 406 from another computer readable medium, such asstatic storage component 408 ordisk drive component 410. In other embodiments, hard-wired circuitry may be used in place of or in combination with software instructions to implement the present disclosure. - Logic may be encoded in a computer readable medium, which may refer to any medium that participates in providing instructions to
processor 404 for execution. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. In various implementations, non-volatile media includes optical or magnetic disks, such asdisk drive component 410, volatile media includes dynamic memory, such assystem memory component 406, and transmission media includes coaxial cables, copper wire, and fiber optics, including wires that comprisebus 402. In one example, transmission media may take the form of acoustic or light waves, such as those generated during radio wave and infrared data communications. - Some common forms of computer readable media includes, for example, floppy disk, flexible disk, hard disk, magnetic tape, any other magnetic medium, CD-ROM, any other optical medium, punch cards, paper tape, any other physical medium with patterns of holes, RAM, PROM, EPROM, FLASH-EPROM, any other memory chip or cartridge, carrier wave, or any other medium from which a computer is adapted to read.
- In various embodiments of the present disclosure, execution of instruction sequences to practice the present disclosure may be performed by the
computer system 400. In various other embodiments of the present disclosure, a plurality ofcomputer systems 400 coupled bycommunication link 420 to the network (e.g., such as a LAN, WLAN, PTSN, and/or various other wired or wireless networks, including telecommunications, mobile, and cellular phone networks) may perform instruction sequences to practice the present disclosure in coordination with one another. -
Computer system 400 may transmit and receive messages, data, information and instructions, including one or more programs (i.e., application code) throughcommunication link 420 andcommunication interface 412. Received program code may be executed byprocessor 404 as received and/or stored indisk drive component 410 or some other non-volatile storage component for execution. - Where applicable, various embodiments provided by the present disclosure may be implemented using hardware, software, or combinations of hardware and software. Also, where applicable, the various hardware components and/or software components set forth herein may be combined into composite components comprising software, hardware, and/or both without departing from the spirit of the present disclosure. Where applicable, the various hardware components and/or software components set forth herein may be separated into sub-components comprising software, hardware, or both without departing from the scope of the present disclosure. In addition, where applicable, it is contemplated that software components may be implemented as hardware components and vice-versa.
- Software, in accordance with the present disclosure, such as program code and/or data, may be stored on one or more computer readable mediums. It is also contemplated that software identified herein may be implemented using one or more general purpose or specific purpose computers and/or computer systems, networked and/or otherwise. Where applicable, the ordering of various steps described herein may be changed, combined into composite steps, and/or separated into sub-steps to provide features described herein.
- The foregoing disclosure is not intended to limit the present disclosure to the precise forms or particular fields of use disclosed. As such, it is contemplated that various alternate embodiments and/or modifications to the present disclosure, whether explicitly described or implied herein, are possible in light of the disclosure. Having thus described embodiments of the present disclosure, persons of ordinary skill in the art will recognize that changes may be made in form and detail without departing from the scope of the present disclosure. Thus, the present disclosure is limited only by the claims.
Claims (20)
1. A system for facilitating financial transactions over a network, the system comprising:
a network interface of a service provider configured to communicate with a financial institution over the network, wherein the financial institution has a first user account for a user;
a memory configured to store a plurality of machine-readable instructions; and
one or more processors configured to execute the machine-readable instructions to
receive a fund transfer request from the financial institution on behalf of the user, wherein the fund transfer request includes user information related to the first user account,
verify that the user has an existing user account with the service provider based on the user information related to the first user account passed with the fund transfer request, and
process the fund transfer request to receive funds from the financial institution associated with the first user account and deposit the received funds in the existing user account on behalf of the user.
2. The system of claim 1 , wherein the one or more processors are further configured to link the first user account of the financial institution to the existing user account of the service provider based on the user information related to the first user account passed with the fund transfer request.
3. The system of claim 2 , wherein the one or more processors are further configured to request identification information from the user to verify the link between the first user account of the financial institution and the existing user account of the service provider.
4. The system of claim 1 , wherein the user information related to the first user account comprises an e-mail address of the user.
5. The system of claim 1 , wherein the user information related to the first user account comprises a device identifier of a device associated with the user.
6. The system of claim 1 , wherein the user information related to the first user account comprises a billing address of the user.
7. The system of claim 1 , wherein the one or more processors are further configured to transfer a nominal fund from the existing user account of the service provider to the first user account of the financial institution, request the user to login to the first user account from the service provider, and validate the transfer of the nominal fund.
8. The system of claim 1 , wherein the one or more processors are further configured to
obtain recipient information of a recipient from the fund transfer request as provided by the user,
verify that the recipient has an existing recipient account with the service provider based on the recipient information, and
process the fund transfer request to receive funds from the financial institution associated with the first user account and deposit the received funds in the existing recipient account on behalf of the recipient.
9. The system of claim 1 , wherein the one or more processors are further configured to
obtain recipient information of a recipient from the fund transfer request as provided by the user,
verify that the recipient has an existing recipient account with the service provider based on the recipient information, and
process the fund transfer request to debit funds from the existing user account with the service provider and deposit the funds in the existing recipient account on behalf of the recipient.
10. The system of claim 1 , wherein the one or more processors are further configured to allow the user to login to the first user account from the service provider.
11. A method for facilitating financial transactions over a network, the method comprising:
receiving by a network server of a service provider a fund transfer request over the network from a financial institution on behalf of a user, wherein the financial institution has a first user account for the user, and wherein the fund transfer request includes user information related to the first user account;
verifying that the user has an existing user account with the service provider based on the user information related to the first user account passed with the fund transfer request; and
processing the fund transfer request by receiving funds from the financial institution associated with the first user account and depositing the received funds in the existing user account on behalf of the user.
12. The method of claim 11 , wherein said processing the fund transfer request further comprises linking the first user account of the financial institution to the existing user account of the service provider based on the user information related to the first user account passed with the fund transfer request.
13. The method of claim 12 , further comprising requesting by the network server identifier information from the user to verify the link between the first user account of the financial institution and the existing user account of the service provider.
14. The method of claim 11 , wherein the user information related to the first user account comprises an e-mail address of the user.
15. The method of claim 11 , wherein the user information related to the first user account comprises a device identifier of a device associated with the user.
16. The method of claim 11 , wherein the user information related to the first user account comprises a billing address of the user.
17. The method of claim 11 , further comprising transferring by the network server a nominal fund from the existing user account of the service provider to the first user account of the financial institution, requesting the user to login to the first user account from the service provider, and validating said transferring of the nominal fund.
18. The method of claim 11 , further comprising:
obtaining by the network server recipient information of a recipient from the fund transfer request as provided by the user;
verifying that the recipient has an existing recipient account with the service provider based on the recipient information; and
processing the fund transfer request by receiving funds from the financial institution associated with the first user account and depositing the received funds in the existing recipient account on behalf of the recipient.
19. The method of claim 11 , further comprising:
obtaining by the network server recipient information of a recipient from the fund transfer request as provided by the user;
verifying that the recipient has an existing recipient account with the service provider based on the recipient information; and
processing the fund transfer request by debiting funds from the existing user account with the service provider and depositing the funds in the existing recipient account on behalf of the recipient.
20. A non-transitory computer readable medium having computer readable code for instructing a processor to perform a method to facilitate financial transaction over a network, the method comprising:
communicating with a financial institution over the network, the financial institution having a first user account for a user;
receiving a fund transfer request from the financial institution on behalf of the user, wherein the fund transfer request includes user information related to the first user account;
verifying that the user has an existing user account with the service provider based on the user information related to the first user account passed with the fund transfer request; and
processing the fund transfer request by receiving funds from the financial institution associated with the first user account and depositing the received funds in the existing user account on behalf of the user.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/622,851 US20130018798A1 (en) | 2008-07-23 | 2012-09-19 | System and Methods for Facilitating Fund Transfers Over a Network |
US14/802,968 US20150324769A1 (en) | 2008-07-23 | 2015-07-17 | System and methods for facilitating fund transfers over a network |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US8300408P | 2008-07-23 | 2008-07-23 | |
US12/415,669 US8285640B2 (en) | 2008-07-23 | 2009-03-31 | System and methods for facilitating fund transfers over a network |
US13/622,851 US20130018798A1 (en) | 2008-07-23 | 2012-09-19 | System and Methods for Facilitating Fund Transfers Over a Network |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/415,669 Continuation US8285640B2 (en) | 2008-07-23 | 2009-03-31 | System and methods for facilitating fund transfers over a network |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/802,968 Continuation US20150324769A1 (en) | 2008-07-23 | 2015-07-17 | System and methods for facilitating fund transfers over a network |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130018798A1 true US20130018798A1 (en) | 2013-01-17 |
Family
ID=41569509
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/415,669 Active 2029-12-08 US8285640B2 (en) | 2008-07-23 | 2009-03-31 | System and methods for facilitating fund transfers over a network |
US13/622,851 Abandoned US20130018798A1 (en) | 2008-07-23 | 2012-09-19 | System and Methods for Facilitating Fund Transfers Over a Network |
US14/802,968 Abandoned US20150324769A1 (en) | 2008-07-23 | 2015-07-17 | System and methods for facilitating fund transfers over a network |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/415,669 Active 2029-12-08 US8285640B2 (en) | 2008-07-23 | 2009-03-31 | System and methods for facilitating fund transfers over a network |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/802,968 Abandoned US20150324769A1 (en) | 2008-07-23 | 2015-07-17 | System and methods for facilitating fund transfers over a network |
Country Status (1)
Country | Link |
---|---|
US (3) | US8285640B2 (en) |
Cited By (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150227900A1 (en) * | 2012-08-23 | 2015-08-13 | Gcs International, Ltd. | Business to business invoice generation and payment system and method using mobile phones |
WO2015191452A1 (en) * | 2014-06-13 | 2015-12-17 | Mastercard International Incorporated | Payment network with service provider directory function |
US10262364B2 (en) | 2007-12-14 | 2019-04-16 | Consumerinfo.Com, Inc. | Card registry systems and methods |
US10325258B2 (en) | 2013-07-03 | 2019-06-18 | Mastercard International Incorporated | Systems and methods for account processing validation |
US10325314B1 (en) | 2013-11-15 | 2019-06-18 | Consumerinfo.Com, Inc. | Payment reporting systems |
US10366450B1 (en) | 2012-11-30 | 2019-07-30 | Consumerinfo.Com, Inc. | Credit data analysis |
US10482532B1 (en) | 2014-04-16 | 2019-11-19 | Consumerinfo.Com, Inc. | Providing credit data in search results |
US10621657B2 (en) | 2008-11-05 | 2020-04-14 | Consumerinfo.Com, Inc. | Systems and methods of credit information reporting |
US10628448B1 (en) | 2013-11-20 | 2020-04-21 | Consumerinfo.Com, Inc. | Systems and user interfaces for dynamic access of multiple remote databases and synchronization of data based on user rules |
US10642999B2 (en) | 2011-09-16 | 2020-05-05 | Consumerinfo.Com, Inc. | Systems and methods of identity protection and management |
US10671749B2 (en) | 2018-09-05 | 2020-06-02 | Consumerinfo.Com, Inc. | Authenticated access and aggregation database platform |
US10685398B1 (en) | 2013-04-23 | 2020-06-16 | Consumerinfo.Com, Inc. | Presenting credit score information |
US10798197B2 (en) | 2011-07-08 | 2020-10-06 | Consumerinfo.Com, Inc. | Lifescore |
US10929925B1 (en) | 2013-03-14 | 2021-02-23 | Consumerlnfo.com, Inc. | System and methods for credit dispute processing, resolution, and reporting |
US11012491B1 (en) | 2012-11-12 | 2021-05-18 | ConsumerInfor.com, Inc. | Aggregating user web browsing data |
US11113759B1 (en) | 2013-03-14 | 2021-09-07 | Consumerinfo.Com, Inc. | Account vulnerability alerts |
US11157872B2 (en) | 2008-06-26 | 2021-10-26 | Experian Marketing Solutions, Llc | Systems and methods for providing an integrated identifier |
US11200620B2 (en) | 2011-10-13 | 2021-12-14 | Consumerinfo.Com, Inc. | Debt services candidate locator |
US20220027891A1 (en) * | 2019-04-04 | 2022-01-27 | Comenity Llc | Adding a credit account to a mobile wallet to make a transaction when the physical card associated with the credit account is unavailable |
US11238656B1 (en) | 2019-02-22 | 2022-02-01 | Consumerinfo.Com, Inc. | System and method for an augmented reality experience via an artificial intelligence bot |
US11315179B1 (en) | 2018-11-16 | 2022-04-26 | Consumerinfo.Com, Inc. | Methods and apparatuses for customized card recommendations |
US11356430B1 (en) | 2012-05-07 | 2022-06-07 | Consumerinfo.Com, Inc. | Storage and maintenance of personal data |
US11941065B1 (en) | 2019-09-13 | 2024-03-26 | Experian Information Solutions, Inc. | Single identifier platform for storing entity data |
Families Citing this family (52)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7146338B2 (en) | 2001-06-28 | 2006-12-05 | Checkfree Services Corporation | Inter-network financial service |
US20080288400A1 (en) | 2007-04-27 | 2008-11-20 | Cashedge, Inc. | Centralized Payment Method and System for Online and Offline Transactions |
US8447669B2 (en) | 2008-08-26 | 2013-05-21 | Visa U.S.A. Inc. | System and method for implementing financial assistance programs |
US7860772B2 (en) * | 2008-09-30 | 2010-12-28 | Ebay, Inc. | Funding on-line accounts |
US20100274687A1 (en) * | 2009-04-27 | 2010-10-28 | Bank Of America Corporation | Customer-defined account management rules for improved linked financial institution account management |
US20110213707A1 (en) * | 2010-03-01 | 2011-09-01 | Fiserv, Inc. | Systems and methods for facilitating person-to-person payments |
WO2012054786A1 (en) | 2010-10-20 | 2012-04-26 | Playspan Inc. | Flexible monetization service apparatuses, methods and systems |
US20120136781A1 (en) * | 2010-11-30 | 2012-05-31 | Ebay, Inc. | Real-time payments through financial institution |
US10204327B2 (en) | 2011-02-05 | 2019-02-12 | Visa International Service Association | Merchant-consumer bridging platform apparatuses, methods and systems |
US9953334B2 (en) | 2011-02-10 | 2018-04-24 | Visa International Service Association | Electronic coupon issuance and redemption apparatuses, methods and systems |
BR112013021059A2 (en) | 2011-02-16 | 2020-10-27 | Visa International Service Association | Snap mobile payment systems, methods and devices |
US10586227B2 (en) | 2011-02-16 | 2020-03-10 | Visa International Service Association | Snap mobile payment apparatuses, methods and systems |
BR112013021057A2 (en) | 2011-02-22 | 2020-11-10 | Visa International Service Association | universal electronic payment devices, methods and systems |
US9773212B2 (en) | 2011-02-28 | 2017-09-26 | Visa International Service Association | Secure anonymous transaction apparatuses, methods and systems |
WO2012122060A1 (en) | 2011-03-04 | 2012-09-13 | Visa International Service Association | Cloud service facilitator apparatuses, methods and systems |
WO2012155081A1 (en) | 2011-05-11 | 2012-11-15 | Visa International Service Association | Electronic receipt manager apparatuses, methods and systems |
WO2012167202A2 (en) | 2011-06-03 | 2012-12-06 | Visa International Service Association | Virtual wallet card selection apparatuses, methods and systems |
US9582598B2 (en) | 2011-07-05 | 2017-02-28 | Visa International Service Association | Hybrid applications utilizing distributed models and views apparatuses, methods and systems |
WO2013006725A2 (en) | 2011-07-05 | 2013-01-10 | Visa International Service Association | Electronic wallet checkout platform apparatuses, methods and systems |
US9355393B2 (en) | 2011-08-18 | 2016-05-31 | Visa International Service Association | Multi-directional wallet connector apparatuses, methods and systems |
US10438176B2 (en) | 2011-07-17 | 2019-10-08 | Visa International Service Association | Multiple merchant payment processor platform apparatuses, methods and systems |
US10318941B2 (en) | 2011-12-13 | 2019-06-11 | Visa International Service Association | Payment platform interface widget generation apparatuses, methods and systems |
US10242358B2 (en) | 2011-08-18 | 2019-03-26 | Visa International Service Association | Remote decoupled application persistent state apparatuses, methods and systems |
US9710807B2 (en) | 2011-08-18 | 2017-07-18 | Visa International Service Association | Third-party value added wallet features and interfaces apparatuses, methods and systems |
US10825001B2 (en) | 2011-08-18 | 2020-11-03 | Visa International Service Association | Multi-directional wallet connector apparatuses, methods and systems |
US9117225B2 (en) | 2011-09-16 | 2015-08-25 | Visa International Service Association | Apparatuses, methods and systems for transforming user infrastructure requests inputs to infrastructure design product and infrastructure allocation outputs |
US10223730B2 (en) | 2011-09-23 | 2019-03-05 | Visa International Service Association | E-wallet store injection search apparatuses, methods and systems |
WO2013090611A2 (en) | 2011-12-13 | 2013-06-20 | Visa International Service Association | Dynamic widget generator apparatuses, methods and systems |
US9953378B2 (en) | 2012-04-27 | 2018-04-24 | Visa International Service Association | Social checkout widget generation and integration apparatuses, methods and systems |
US10223710B2 (en) | 2013-01-04 | 2019-03-05 | Visa International Service Association | Wearable intelligent vision device apparatuses, methods and systems |
US11308227B2 (en) | 2012-01-09 | 2022-04-19 | Visa International Service Association | Secure dynamic page content and layouts apparatuses, methods and systems |
US10262148B2 (en) | 2012-01-09 | 2019-04-16 | Visa International Service Association | Secure dynamic page content and layouts apparatuses, methods and systems |
AU2013214801B2 (en) | 2012-02-02 | 2018-06-21 | Visa International Service Association | Multi-source, multi-dimensional, cross-entity, multimedia database platform apparatuses, methods and systems |
DE102012205904A1 (en) * | 2012-04-11 | 2013-10-17 | Deutsche Post Ag | Secure generation of a user account in a service server |
US10102512B1 (en) * | 2013-03-19 | 2018-10-16 | Wilmington Savings Fund Society, Fsb | Systems and methods for financial data transfer |
US20150052005A1 (en) * | 2013-08-15 | 2015-02-19 | Mastercard International Incorporated | Internet site authentication with payments authorization data |
US20150134507A1 (en) * | 2013-11-12 | 2015-05-14 | Bank Of America Corporation | Electronic documents for person to person payment |
US11507931B1 (en) | 2014-07-31 | 2022-11-22 | Block, Inc. | Payout payment platform |
US9990613B1 (en) * | 2014-12-12 | 2018-06-05 | Square, Inc. | Bill payment using direct funds transfer |
US11216468B2 (en) | 2015-02-08 | 2022-01-04 | Visa International Service Association | Converged merchant processing apparatuses, methods and systems |
PL3073670T3 (en) * | 2015-03-27 | 2021-08-23 | Black Gold Coin, Inc. | A system and a method for personal identification and verification |
US10163083B2 (en) | 2015-04-13 | 2018-12-25 | Bank Of America Corporation | Account activity management system |
CA2997379A1 (en) * | 2015-10-15 | 2017-04-20 | Visa International Service Association | Instant token issuance system |
US10902394B2 (en) * | 2016-08-17 | 2021-01-26 | Paypal, Inc. | One line in-context user interface |
USD837227S1 (en) | 2016-09-12 | 2019-01-01 | Square, Inc. | Display screen with graphical user interface for a mobile device |
US20180075444A1 (en) | 2016-09-12 | 2018-03-15 | Square, Inc. | Processing a mobile payload |
US10776772B2 (en) | 2016-09-30 | 2020-09-15 | Middleware, Inc. | Automated digital method and system of providing or sharing access |
US11257066B2 (en) | 2016-09-30 | 2022-02-22 | Middleware, Inc. | Automated digital method and system of providing or sharing access |
US11182754B2 (en) * | 2018-08-28 | 2021-11-23 | Jpmorgan Chase Bank, N.A. | Methods for synthetic monitoring of systems |
CN109460981B (en) * | 2018-10-23 | 2021-06-25 | 腾讯科技(深圳)有限公司 | Message interaction method and device, storage medium and electronic device |
US11113678B2 (en) * | 2019-12-17 | 2021-09-07 | Capital One Services, Llc | Systems configured to manage user-related external party-activity software objects by using machine-readable indicia and methods of use thereof |
US20230267444A1 (en) * | 2022-02-18 | 2023-08-24 | Bank Of America Corporation | Proximity-based device pairing system via acoustic communication for secure resource transfer |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6189787B1 (en) * | 1997-07-10 | 2001-02-20 | Robert E. Dorf | Multifunctional card system |
US6202079B1 (en) * | 1995-06-03 | 2001-03-13 | International Business Machines Corporation | Synchronization procedure in a routing node |
JP2001282996A (en) * | 2000-03-29 | 2001-10-12 | Hitachi Ltd | Automatic account establishment system at the time of receiving slip |
US20030233318A1 (en) * | 2001-11-26 | 2003-12-18 | King Douglas W. | Systems and methods for fund transfers |
US20060173779A1 (en) * | 2004-12-31 | 2006-08-03 | U.S. Payments, Llc | System, method, and computer program product for receiving and processing payments |
US20070061270A1 (en) * | 2005-09-12 | 2007-03-15 | Teranet Enterprises Inc. | Closing funds management system |
US20070100748A1 (en) * | 2005-10-19 | 2007-05-03 | Sanjeev Dheer | Multi-channel transaction system for transferring assets between accounts at different financial institutions |
US20080015987A1 (en) * | 2006-06-30 | 2008-01-17 | Bharathi Ramavarjula | Managing transaction accounts |
US20090307140A1 (en) * | 2008-06-06 | 2009-12-10 | Upendra Mardikar | Mobile device over-the-air (ota) registration and point-of-sale (pos) payment |
US20100161487A1 (en) * | 2008-12-19 | 2010-06-24 | Ebay Inc. | Systems and methods for mobile transactions |
US8571980B1 (en) * | 2005-06-01 | 2013-10-29 | Stragent, Llc | System, method and computer program product for transferring money |
Family Cites Families (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6182131B1 (en) * | 1998-07-17 | 2001-01-30 | International Business Machines Corporation | Data processing system, method, and program product for automating account creation in a network |
CA2910997A1 (en) * | 1999-04-30 | 2000-11-09 | Paypal, Inc. | System and method for electronically exchanging value among distributed users |
US7243082B1 (en) * | 1999-06-30 | 2007-07-10 | Kyklos Entertainment S.R.L. | Method and apparatus for generating a sale offer to selected individuals over electronic network systems |
US7031939B1 (en) * | 2000-08-15 | 2006-04-18 | Yahoo! Inc. | Systems and methods for implementing person-to-person money exchange |
US7383223B1 (en) * | 2000-09-20 | 2008-06-03 | Cashedge, Inc. | Method and apparatus for managing multiple accounts |
US7191151B1 (en) * | 2001-08-23 | 2007-03-13 | Paypal, Inc. | Instant availability of electronically transferred funds |
US20030080185A1 (en) * | 2001-10-26 | 2003-05-01 | Werther Ellen R. | Money transfer method and system |
CA2476502C (en) * | 2002-02-15 | 2016-10-11 | Coinstar, Inc. | Methods and systems for exchanging and/or transferring various forms of value |
US20030163418A1 (en) * | 2002-02-27 | 2003-08-28 | Audrey Marks | Third party real-time multi-payment and remittance system |
US6876979B2 (en) * | 2002-08-12 | 2005-04-05 | Paybyclick Corporation | Electronic commerce bridge system |
US7457778B2 (en) * | 2003-03-21 | 2008-11-25 | Ebay, Inc. | Method and architecture for facilitating payment to e-commerce merchants via a payment service |
US7320068B2 (en) * | 2003-06-05 | 2008-01-15 | Microsoft Corporation | Systems and methods to migrate a user profile when joining a client to a server and/or domain |
US7386518B2 (en) * | 2003-12-16 | 2008-06-10 | Pitney Bowes Inc. | Method and system for facilitating transactions |
US7756780B2 (en) * | 2006-02-16 | 2010-07-13 | Compucredit Intellectual Property Holdings Corp. Ii | Method and system for balance transfer operations |
US7860790B2 (en) * | 2007-06-04 | 2010-12-28 | Visa U.S.A. Inc. | Systems and methods for automatic migration of a consumer between financial accounts |
CA2730175A1 (en) * | 2008-07-09 | 2010-01-14 | Xtreme Mobility Inc. | Secure wireless deposit system and method |
-
2009
- 2009-03-31 US US12/415,669 patent/US8285640B2/en active Active
-
2012
- 2012-09-19 US US13/622,851 patent/US20130018798A1/en not_active Abandoned
-
2015
- 2015-07-17 US US14/802,968 patent/US20150324769A1/en not_active Abandoned
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6202079B1 (en) * | 1995-06-03 | 2001-03-13 | International Business Machines Corporation | Synchronization procedure in a routing node |
US6189787B1 (en) * | 1997-07-10 | 2001-02-20 | Robert E. Dorf | Multifunctional card system |
JP2001282996A (en) * | 2000-03-29 | 2001-10-12 | Hitachi Ltd | Automatic account establishment system at the time of receiving slip |
US20030233318A1 (en) * | 2001-11-26 | 2003-12-18 | King Douglas W. | Systems and methods for fund transfers |
US20060173779A1 (en) * | 2004-12-31 | 2006-08-03 | U.S. Payments, Llc | System, method, and computer program product for receiving and processing payments |
US8571980B1 (en) * | 2005-06-01 | 2013-10-29 | Stragent, Llc | System, method and computer program product for transferring money |
US20070061270A1 (en) * | 2005-09-12 | 2007-03-15 | Teranet Enterprises Inc. | Closing funds management system |
US20070100748A1 (en) * | 2005-10-19 | 2007-05-03 | Sanjeev Dheer | Multi-channel transaction system for transferring assets between accounts at different financial institutions |
US20080015987A1 (en) * | 2006-06-30 | 2008-01-17 | Bharathi Ramavarjula | Managing transaction accounts |
US20090307140A1 (en) * | 2008-06-06 | 2009-12-10 | Upendra Mardikar | Mobile device over-the-air (ota) registration and point-of-sale (pos) payment |
US20100161487A1 (en) * | 2008-12-19 | 2010-06-24 | Ebay Inc. | Systems and methods for mobile transactions |
Cited By (42)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10614519B2 (en) | 2007-12-14 | 2020-04-07 | Consumerinfo.Com, Inc. | Card registry systems and methods |
US10878499B2 (en) | 2007-12-14 | 2020-12-29 | Consumerinfo.Com, Inc. | Card registry systems and methods |
US10262364B2 (en) | 2007-12-14 | 2019-04-16 | Consumerinfo.Com, Inc. | Card registry systems and methods |
US11379916B1 (en) | 2007-12-14 | 2022-07-05 | Consumerinfo.Com, Inc. | Card registry systems and methods |
US11769112B2 (en) | 2008-06-26 | 2023-09-26 | Experian Marketing Solutions, Llc | Systems and methods for providing an integrated identifier |
US11157872B2 (en) | 2008-06-26 | 2021-10-26 | Experian Marketing Solutions, Llc | Systems and methods for providing an integrated identifier |
US10621657B2 (en) | 2008-11-05 | 2020-04-14 | Consumerinfo.Com, Inc. | Systems and methods of credit information reporting |
US11665253B1 (en) | 2011-07-08 | 2023-05-30 | Consumerinfo.Com, Inc. | LifeScore |
US10798197B2 (en) | 2011-07-08 | 2020-10-06 | Consumerinfo.Com, Inc. | Lifescore |
US10642999B2 (en) | 2011-09-16 | 2020-05-05 | Consumerinfo.Com, Inc. | Systems and methods of identity protection and management |
US11790112B1 (en) | 2011-09-16 | 2023-10-17 | Consumerinfo.Com, Inc. | Systems and methods of identity protection and management |
US11087022B2 (en) | 2011-09-16 | 2021-08-10 | Consumerinfo.Com, Inc. | Systems and methods of identity protection and management |
US11200620B2 (en) | 2011-10-13 | 2021-12-14 | Consumerinfo.Com, Inc. | Debt services candidate locator |
US11356430B1 (en) | 2012-05-07 | 2022-06-07 | Consumerinfo.Com, Inc. | Storage and maintenance of personal data |
US20150227900A1 (en) * | 2012-08-23 | 2015-08-13 | Gcs International, Ltd. | Business to business invoice generation and payment system and method using mobile phones |
US11012491B1 (en) | 2012-11-12 | 2021-05-18 | ConsumerInfor.com, Inc. | Aggregating user web browsing data |
US11863310B1 (en) | 2012-11-12 | 2024-01-02 | Consumerinfo.Com, Inc. | Aggregating user web browsing data |
US10366450B1 (en) | 2012-11-30 | 2019-07-30 | Consumerinfo.Com, Inc. | Credit data analysis |
US10963959B2 (en) | 2012-11-30 | 2021-03-30 | Consumerinfo. Com, Inc. | Presentation of credit score factors |
US11308551B1 (en) | 2012-11-30 | 2022-04-19 | Consumerinfo.Com, Inc. | Credit data analysis |
US11651426B1 (en) | 2012-11-30 | 2023-05-16 | Consumerlnfo.com, Inc. | Credit score goals and alerts systems and methods |
US11113759B1 (en) | 2013-03-14 | 2021-09-07 | Consumerinfo.Com, Inc. | Account vulnerability alerts |
US10929925B1 (en) | 2013-03-14 | 2021-02-23 | Consumerlnfo.com, Inc. | System and methods for credit dispute processing, resolution, and reporting |
US11769200B1 (en) | 2013-03-14 | 2023-09-26 | Consumerinfo.Com, Inc. | Account vulnerability alerts |
US11514519B1 (en) | 2013-03-14 | 2022-11-29 | 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 |
US10325258B2 (en) | 2013-07-03 | 2019-06-18 | Mastercard International Incorporated | Systems and methods for account processing validation |
US10325314B1 (en) | 2013-11-15 | 2019-06-18 | Consumerinfo.Com, Inc. | Payment reporting systems |
US10628448B1 (en) | 2013-11-20 | 2020-04-21 | Consumerinfo.Com, Inc. | Systems and user interfaces for dynamic access of multiple remote databases and synchronization of data based on user rules |
US11461364B1 (en) | 2013-11-20 | 2022-10-04 | Consumerinfo.Com, Inc. | Systems and user interfaces for dynamic access of multiple remote databases and synchronization of data based on user rules |
US10482532B1 (en) | 2014-04-16 | 2019-11-19 | Consumerinfo.Com, Inc. | Providing credit data in search results |
WO2015191452A1 (en) * | 2014-06-13 | 2015-12-17 | Mastercard International Incorporated | Payment network with service provider directory function |
US11399029B2 (en) | 2018-09-05 | 2022-07-26 | Consumerinfo.Com, Inc. | Database platform for realtime updating of user data from third party sources |
US11265324B2 (en) | 2018-09-05 | 2022-03-01 | Consumerinfo.Com, Inc. | User permissions for access to secure data at third-party |
US10671749B2 (en) | 2018-09-05 | 2020-06-02 | Consumerinfo.Com, Inc. | Authenticated access and aggregation database platform |
US10880313B2 (en) | 2018-09-05 | 2020-12-29 | Consumerinfo.Com, Inc. | Database platform for realtime updating of user data from third party sources |
US11315179B1 (en) | 2018-11-16 | 2022-04-26 | Consumerinfo.Com, Inc. | Methods and apparatuses for customized card recommendations |
US11238656B1 (en) | 2019-02-22 | 2022-02-01 | Consumerinfo.Com, Inc. | System and method for an augmented reality experience via an artificial intelligence bot |
US11842454B1 (en) | 2019-02-22 | 2023-12-12 | Consumerinfo.Com, Inc. | System and method for an augmented reality experience via an artificial intelligence bot |
US20220027891A1 (en) * | 2019-04-04 | 2022-01-27 | Comenity Llc | Adding a credit account to a mobile wallet to make a transaction when the physical card associated with the credit account is unavailable |
US11941609B2 (en) * | 2019-04-04 | 2024-03-26 | Bread Financial Payments, Inc. | Adding a credit account to a mobile wallet to make a transaction when the physical card associated with the credit account is unavailable |
US11941065B1 (en) | 2019-09-13 | 2024-03-26 | Experian Information Solutions, Inc. | Single identifier platform for storing entity data |
Also Published As
Publication number | Publication date |
---|---|
US20150324769A1 (en) | 2015-11-12 |
US20100023450A1 (en) | 2010-01-28 |
US8285640B2 (en) | 2012-10-09 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8285640B2 (en) | System and methods for facilitating fund transfers over a network | |
US11301851B2 (en) | Systems and methods for facilitating account verification over a network | |
US20180330342A1 (en) | Digital asset account management | |
US20160042328A1 (en) | Systems and methods for facilitating sharing of expenses over a network | |
US20170132615A1 (en) | Block chain alias for person-to-person payments | |
US8494962B2 (en) | Method and system for secure mobile remittance | |
US20220051218A1 (en) | Virtual currency secured physical currency transmission system | |
AU2011207602B2 (en) | Verification mechanism | |
US8930272B2 (en) | Systems and methods for mobile transactions | |
JP2002117361A (en) | Electronic account settlement method and electronic account settlement system | |
US20210295335A1 (en) | Secure access-based resource delegation | |
US20120310828A1 (en) | Instant bank account verification through debit card network | |
US20210049560A1 (en) | Method for providing data security using one-way token | |
US20100280944A1 (en) | Paperless checking transactions | |
US11436067B1 (en) | Systems for requesting and/or transmitting user data within resource transfer event messaging | |
US20140006271A1 (en) | Cross-network electronic payment processing system and method | |
US11663591B2 (en) | Facilitation of real-time payment network transactions |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: EBAY INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SCIPIONI, GERMAN;REEL/FRAME:030589/0816 Effective date: 20090331 |
|
AS | Assignment |
Owner name: PAYPAL, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:EBAY INC.;REEL/FRAME:036170/0140 Effective date: 20150717 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |