US20140372313A1 - Systems and methods for mobile transactions - Google Patents
Systems and methods for mobile transactions Download PDFInfo
- Publication number
- US20140372313A1 US20140372313A1 US14/470,616 US201414470616A US2014372313A1 US 20140372313 A1 US20140372313 A1 US 20140372313A1 US 201414470616 A US201414470616 A US 201414470616A US 2014372313 A1 US2014372313 A1 US 2014372313A1
- Authority
- US
- United States
- Prior art keywords
- user
- service provider
- mobile device
- information
- network
- 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/108—Remote banking, e.g. home banking
-
- 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
- G06Q20/1085—Remote banking, e.g. home banking involving automatic teller machines [ATMs]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/32—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using wireless devices
- G06Q20/322—Aspects of commerce using mobile devices [M-devices]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
-
- 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
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/02—Banking, e.g. interest calculation or account maintenance
Definitions
- the present invention generally relates to network transactions and more particularly to facilitating mobile transactions with cash based funding.
- a user navigates through selectable pages of service provider sites to view information resources, process financial transactions, and/or communicate with other users.
- cellular phones have been adapted to navigate communication networks, such as the Internet.
- Systems and methods disclosed herein facilitate financial transactions via a mobile communication device, such as a cellular phone, with cash based funding via a kiosk device, such as a machine having a receptacle adapted to accept monetary funds, such as cash, as a physical input.
- a user may fund an account by depositing cash into a kiosk, machine, or in person at a store or other physical location. After depositing the cash, the user may proceed with monetary fund transfers into and out of an account related to the user using the mobile communication device (e.g., cellular phone).
- a system for facilitating financial transactions over a network includes a first component adapted to communicate with a user via a kiosk device and a mobile communication device over the network and a second component adapted to access an account related to the user.
- the second component is adapted to deposit funds into the account based on a cash deposit request received from the user at the kiosk device.
- the second component is adapted to transfer funds from the account to one or more other accounts based on a fund transfer request received from the user via the mobile communication device.
- user identification information may be passed with the cash deposit request from the kiosk device to the second component via the network and the first component, wherein the user identification information is used by the second component to verify an identify of the user and access the account related to the user.
- user identification information may be passed with the fund transfer request from the mobile communication device to the second component via the network and the first component, wherein the user identification information is used by the second component to verify an identify of the user and access the account related to the user.
- the kiosk device comprises an automated user interface, such as a computer, adapted to interface with the network and communicate with the second component via the network and the first component.
- the kiosk device may include a user interface application adapted to allow the user to communicate with the second component via the first component and the network and a receptacle adapted to receive cash from the user for deposit in the account.
- the mobile communication device comprises a cellular phone adapted to communicate with the second component via the network and the first component.
- the system comprises a server adapted to interface with the network and communicate with the kiosk device and the mobile communication device via the network.
- a method for facilitating financial transactions over a network includes communicating with a user via a kiosk device over the network and a mobile communication device over the network and accessing an account related to the user.
- the method includes depositing funds into the account based on a cash deposit request received from the user at the kiosk device.
- the method includes transferring funds from the account to one or more other accounts based on a fund transfer request received from the user via the mobile communication device.
- the method may include receiving a login request from the user via the kiosk device and verifying an identity of the user, wherein user identification information is passed with the cash deposit request from the kiosk device.
- the method may include receiving a login request from the user via the mobile communication device and verifying an identity of the user, wherein user identification information is passed with the fund transfer request from the mobile communication device.
- FIG. 1 shows a block diagram of a system adapted to facilitate financial transactions over a network, in accordance with an embodiment of the present disclosure.
- FIGS. 2A-2B show various client-side methods for facilitating financial transactions over a network, in accordance with embodiments of the present disclosure.
- FIGS. 3A-3B show various server-side methods for facilitating financial transactions over a network, in accordance with embodiments 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.
- One or more embodiments of the present disclosure relate to facilitating financial transactions via a mobile communication device, such as a cellular phone, with cash based funding via a kiosk device, such as a machine that accepts monetary funds, such as cash, as a physical input.
- a user may fund an account by depositing cash into a kiosk, machine, or in person at a store or other physical location. After depositing the cash, the user may proceed with transfers into and out of an account related to the user using a mobile communication device (e.g., a cellular phone).
- a user profile may be created using the data obtained from cellular phone activity.
- One or more embodiments of the present disclosure enable people in communities without access to services of a banking institution to use the financial services of an online service provider via mobile communion devices including cellular phones.
- the user is able to fund an account with the online service provider by depositing cash into a kiosk device or machine at a physical location, which may be accomplished in various ways, such as the user directly depositing cash in the kiosk device or machine, or giving the cash to a cashier in a store or shop to deposit the cash in the kiosk device or machine.
- the user may then use the funds in the account to transact business via the user's cellular phone, such as transferring cash to other accounts related to the user and/or other accounts unrelated to the user.
- These transactions may be used by the online service provider to create a user profile based on the activity from the cellular phone.
- FIG. 1 shows one embodiment of a block diagram of a system 100 adapted to facilitate mobile transactions over a network 160 with cash based funding.
- the system 100 includes at least one kiosk device 120 , at least one mobile device 132 , and at least one service provider server 180 in communication over the network 160 .
- the network 160 may be implemented as a single network or a combination of multiple networks.
- the network 160 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 comprise a wireless telecommunications network (e.g., mobile cellular phone network) adapted to communicate with other communication networks, such as the Internet.
- the kiosk device 120 may be implemented using any appropriate combination of hardware and/or software configured for wired and/or wireless communication over the network 160 .
- the kiosk device 120 may be implemented as a wired and/or wireless communication device (e.g., an automated user interface device) for a user 102 (e.g., a client or customer) to communicate with the network 160 , such as the Internet and/or mobile network.
- the kiosk device 120 may be referred to as a user device, client device or a customer device without departing from the scope of the present disclosure.
- the kiosk device 120 in one embodiment, comprises a machine (e.g., automated teller machine (ATM)) adapted to directly accept monetary funds (e.g., cash) from a person, such as the user 102 .
- ATM automated teller machine
- the kiosk device 120 may be used by an operator, in person, at a store or other physical location, wherein the operator may receive monetary funds from the user 102 for deposit into the kiosk device 120 .
- the kiosk device 120 includes a cash receptacle (not shown) to receive cash for deposit in an account related to the user 102 .
- the user 102 is able to input data and information into an input component (e.g., a keyboard) of the kiosk device 120 to provide user information with a transaction request, such as a cash deposit request.
- the user information may include user identification information, user account number, and a user password, which is described in greater detail herein.
- the kiosk device 120 includes one or more user interface applications 122 , which may be used by the user 102 to conduct financial transactions over the network 160 .
- the user interface application 122 may be implemented as an ATM application to deposit cash into an account over the network 160 .
- the user interface application 122 comprises a software program, such as a graphical user interface (GUI), executable by a processor that is configured to interface and communicate with the one or more service provider servers 180 via the network 160 .
- GUI graphical user interface
- the kiosk device 120 may include one or more other applications 124 to provide additional features to the user 102 .
- these other applications 124 may include security applications for implementing client-side security features, programmatic client applications for interfacing with appropriate application programming interfaces (APIs) over the network 160 or various other types of generally known programs and/or applications.
- APIs application programming interfaces
- the kiosk device 120 may include at least one network interface component (NIC) 128 adapted to communicate with the network 160 .
- the network interface component 128 may comprise a DSL (e.g., Digital Subscriber Line) modem, a PSTN (Public Switched Telephone Network) modem, an Ethernet device, a broadband device, a satellite device and/or various other types of wired and/or wireless network communication devices including microwave, radio frequency (RF), and infrared (IR) communication devices.
- DSL Digital Subscriber Line
- PSTN Public Switched Telephone Network
- the kiosk device 120 may include one or more kiosk identifiers 130 , which may be implemented as operating system registry entries, cookies associated with the user interface application 122 , identifiers associated with hardware of the kiosk device 120 , and/or various other appropriate identifiers.
- the kiosk identifier 130 may include attributes related to the kiosk device 120 , such as identification information (e.g., a kiosk serial number, a location address, Global Positioning System (GPS) coordinates, a network identification number, etc.) and network information (e.g., network owner, network provider, network administrator, network security information, etc.).
- identification information e.g., a kiosk serial number, a location address, Global Positioning System (GPS) coordinates, a network identification number, etc.
- network information e.g., network owner, network provider, network administrator, network security information, etc.
- the kiosk identifier 130 may be passed with network traffic data and information to the service provider server 180 , and the kiosk identifier 130 may be used by the service provider server 180 to associate one or more network transactions of the user 102 with one or more particular user account maintained by the service provider server 180 .
- the mobile communication device 132 may be utilized by the user 102 to interact with the service provider server 180 over the network 160 .
- the user 102 may conduct financial transactions (e.g., account transfers) with the service provider server 180 via the mobile communication device 132 .
- the mobile communication device 132 may include at least one of a wireless cellular phone, personal digital assistant (PDA), satellite phone, etc.
- PDA personal digital assistant
- the mobile communication device 132 may be integrated as part of a client device (not shown), such as a personal computer, without departing from the scope of the present disclosure.
- a user profile may be created using data and information obtained from cell phone activity over the network 160 .
- Cell phone activity transactions may be used by the service provider server 180 to create at least one user profile for the user 102 based on activity from the mobile communication device 132 (e.g., cell phone).
- the user profile may be updated with each financial and/or information transaction (e.g., payment transaction, purchase transaction, etc.) achieved through use of the mobile communication device 132 . In various aspects, this may include the type of transaction and/or the location information from the mobile communication device 132 .
- the profile may be used for recognizing patterns of potential fraud, setting transaction limits on the user, etc.
- the mobile communication device 132 may include a user identifier as one or more attributes related to the user 102 , such as personal information (e.g., a user name, password, photograph image, biometric id, address, social security number, phone number, email address, etc.) and banking information (e.g., banking institution, credit card issuer, user account numbers, security information, etc.).
- personal information e.g., a user name, password, photograph image, biometric id, address, social security number, phone number, email address, etc.
- banking information e.g., banking institution, credit card issuer, user account numbers, security information, etc.
- the user identifier may be passed with network traffic data of the user 102 to the service provider server 180 , and the user identifier may be used by the service provider server 180 to associate the user 102 with a user account maintained by the service provider server 180 .
- the user 102 is able to input data and information into an input component (e.g., a keyboard) of the mobile communication device 132 to provide user information with a transaction request, such as a fund transfer request.
- the user information may include user identification information, user account number, and a user password, which is described in greater detail herein.
- the service provider server 180 may be maintained by an online service provider, which is adapted to provide processing for financial transactions on behalf of the user 102 .
- the service provider server 180 includes at least one processing application 182 , which may be adapted to interact with the kiosk device 120 and the mobile communication device 132 via the network 160 to facilitate financial transactions.
- the service provider server 180 may be provided by PayPal, Inc. of San Jose, Calif., USA.
- the service provider server 180 may be configured to maintain a plurality of user accounts in an account database 184 , each of which may include account information 186 associated with individual users, including the user 102 .
- account information 186 may include balance information, fund transfer information, deposit information, etc.
- account information 186 may include identification information and/or private financial information of the user 102 , such as account numbers, identifiers, passwords, phone numbers, credit card information, banking information, or other types of financial information, which may be used to facilitate online transactions between the user 102 of the kiosk device 120 and the service provider server 180 . It should be appreciated that the methods and systems described herein may be modified to accommodate users that may or may not be associated with at least one existing user account.
- the service provider server 180 may include at least one network interface component (NIC) 188 adapted to communicate with the network 160 including the network interface component 128 of the kiosk device 120 and the mobile communication device 132 .
- the network interface component 128 may comprise a DSL (e.g., Digital Subscriber Line) modem, a PSTN (Public Switched Telephone Network) modem, an Ethernet device, a broadband device, a satellite device and/or various other types of wired and/or wireless network communication devices including microwave, radio frequency (RF), and infrared (IR) communication devices.
- DSL Digital Subscriber Line
- PSTN Public Switched Telephone Network
- the service provider server 180 may include one or more databases 190 (e.g., internal and/or external databases) for storing and tracking information related to financial transactions between particular users, such as the user 102 , and the service provider server 180 .
- the databases 190 may provide an historical survey of financial transactions between the user 102 and the service provider 180 .
- the processing application 182 may be configured to track, log, store, and access financial transaction information and provide this information to the processing application 182 for analysis and maintenance.
- the kiosk device 120 , the mobile communication device 132 and the service provider server 180 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 102 may interface with the kiosk device 120 and/or the mobile communication device 132 via the network 160 to facilitate financial transactions with the service provider server 180 , which is discussed in greater detail herein.
- FIG. 2A shows one embodiment of a method 200 for facilitating financial transactions via the network 160 with cash based funding.
- the user 102 may run the user interface application 122 on the kiosk device 120 to access at least one resource provider site via the service provider server 180 to view account information 186 related to the user 102 . Access to the service provider site may be made available to the user 102 by the service provider server 180 , wherein the service provider server 180 uses the processing application 182 to interact with the user 102 via the server provider site.
- the method 200 involves the user 102 interacting with the kiosk device 120 to login to the service provider server 180 (block 210 ). In one example, this may involve the user 102 accessing a service provider site via the kiosk device 120 , which is adapted to communicate with the server provider server 180 via the network 160 . The user 102 may provide an identification number and password to login to the service provider server 180 . In one aspect, the kiosk device 120 serves as a gateway to the network 160 for cash based funding of an account related to the user 102 .
- the user 102 accesses a user account in the account database 184 of the server provider server 180 (block 214 ). In one example, this may involve the user 102 selecting an appropriate user account after login.
- the user 102 may select a financial transaction for processing, such as a cash deposit into the kiosk device 120 (block 218 ). In one example, this may involve the user 102 inserting cash into the kiosk device 120 when prompted by the kiosk device 120 (block 222 ).
- the user 102 obtains a transaction receipt from the kiosk device 120 (block 226 ). In one example, the transaction receipt indicates the amounted of cash deposited and the date and time of the cash deposit.
- FIG. 2B shows one embodiment of a method 250 for facilitating financial transactions over the network 160 with the mobile communication device 132 .
- the user 102 may use the mobile communication device 132 to access at least one service provider site via the service provider server 180 to process financial transactions and view account information 186 related to the user 102 .
- Access to the service provider site may be made available to mobile communication device 132 of the user 102 by the service provider server 180 , wherein the service provider server 180 uses the processing application 182 to interact with the user's mobile communication device 132 via the server provider site.
- the method 250 involves the user 102 interacting with the mobile communication device 132 to login to the service provider server 180 (block 260 ). In one example, this may involve the user 102 accessing a service provider site via the mobile communication device 132 , which is adapted to communicate with the server provider server 180 via the network 160 . The user 102 may provide an identification number and password to login to the service provider server 180 . Next, the user 102 accesses a user account in the account database 184 of the server provider server 180 (block 264 ). In one example, this may involve the user 102 selecting an appropriate user account after login.
- the user 102 may select a financial transaction for processing, such as a monetary fund transfer from the accessed user account to one or more other accounts (block 268 ). In various examples, this may involve the user 102 transferring monetary funds from the user account to one or more other accounts related and/or unrelated to the user 102 (block 272 ).
- the mobile communication device 132 serves as a gateway to the network 160 for monetary fund transfers between accounts specified by the user 102 .
- the user 102 obtains a transaction receipt from the service provider server 180 (block 276 ).
- the transaction receipt may be in the form of a text message and/or email, and the transaction receipt indicates the amount of monetary funds transferred, the account numbers involved in the monetary fund transfers, and the date and time of the monetary fund transfers.
- FIG. 3A shows one embodiment of a method 300 for facilitating financial transactions via the network 160 with cash based funding.
- the service provider server 180 interacts with the kiosk device 120 to process financial transactions related to the user 102 (e.g., cash deposits into a user account). Access to the service provider server 180 may be provided to the user 102 over the network 160 via the kiosk device 120 , wherein the service provider server 180 may utilize the processing application 182 to interact with the user 102 via the kiosk device 120 .
- the service provider server 180 receives a login request via the kiosk device 120 (block 310 ), verifies the identity of the user 102 (block 314 ), and accesses at least one account related to the user 102 in the account database 184 (block 316 ).
- the user 102 interacts with the kiosk device 120 to provide an identification number and password to the kiosk device 120 for login to the service provider server 180 via the network 160 .
- the service provider server 180 receives the identification number and password with the login request and verifies the identity of the user 102 , for example, by comparing the identification number and password provided by the user 102 with the login request via the kiosk device 120 with an identification number and password stored as part of an account related to the user 102 in the account database 184 . Next, the service provider server 180 locates and accesses at least one user account related to the user 102 based on the identification information provided by the user 102 as passed with the login request via the kiosk device 120 .
- the service provider server 180 may determine whether the user 102 is an existing user having an established user account 184 , for example, by checking a user account list in the account database 184 . If the user 102 does not have an established user account, then the service provider server 180 may prompt the user 102 to establish a user account 184 with the service provider sever 180 by providing user identification and financial information 186 via the kiosk device 120 .
- the service provider server 180 receives a transaction request for a monetary fund deposit (e.g., cash deposit) from the user 102 via the kiosk device (block 318 ).
- the service provider server 180 processes the transaction request for the cash deposit (block 322 ).
- the service provider server 180 accesses the user account related to the user 102 and credits the user account with the user deposited cash funds as received by the kiosk device 120 .
- the service provider server 180 verifies the cash deposit (block 326 ).
- the service provider server 180 may communicate with the kiosk device 120 to verify (e.g., authenticate) that the indicated amount of cash deposited by the user 102 was actually received and counted by the kiosk device 120 .
- the service provider server 180 updates the user account associated to the user 102 to reflect the cash deposit (block 330 ). It should be appreciated by those skilled in the art that the service provider server 180 may cancel the online information transaction at any point in the process if it is determined that the user 102 enters wrong information or the user 102 is trying to access information with criminal intent.
- FIG. 3B shows one embodiment of a method 350 for facilitating financial transactions over the network 160 with the mobile communication device 132 .
- the service provider server 180 interacts with the mobile communication device 132 to process financial transactions related to the user 102 (e.g., monetary fund transfers between user accounts and/or other accounts). Access to the service provider server 180 may be provided to the user 102 over the network 160 via the mobile communication device 132 , wherein the service provider server 180 may utilize the processing application 182 to interact with the user 102 via the mobile communication device 132 .
- the service provider server 180 receives a login request via the mobile communication device 132 (block 360 ), verifies the identity of the user 102 (block 364 ), and accesses at least one account related to the user 102 in the account database 184 (block 366 ).
- the user 102 interacts with the mobile communication device 132 to provide an identification number and password to the mobile communication device 132 for login to the service provider server 180 via the network 160 .
- the service provider server 180 receives the identification number and password with the login request and verifies the identity of the user 102 , for example, by comparing the identification number and password provided by the user 102 with the login request via the kiosk device 120 with an identification number and password stored as part of an account related to the user 102 in the account database 184 . Next, the service provider server 180 locates and accesses at least one user account related to the user 102 based on the identification information provided by the user 102 as passed with the login request via the mobile communication device 132 .
- the service provider server 180 may determine whether the user 102 is an existing user having an established user account 184 , for example, by checking a user account list in the account database 184 . If the user 102 does not have an established user account, then the service provider server 180 may prompt the user 102 to establish a user account 184 with the service provider sever 180 by providing user identification and financial information 186 via the mobile communication device 132 .
- the service provider server 180 receives a transaction request for a monetary fund transfer between accounts from the user 102 via the mobile communication device 132 (block 368 ).
- the service provider server 180 processes the transaction request for the monetary fund transfer (block 372 ).
- the service provider server 180 accesses the user account related to the user 102 and debits the user account for credit to another user account or some other account indicated by the user 102 .
- the service provider server 180 verifies that the monetary funds have been transferred as requested by the user 102 (block 376 ).
- the service provider server 180 may communicate with other financial organizations to verify (e.g., authenticate) that the indicated amount of monetary funds transferred was actually received and credited to the proper accounts.
- verification of monetary fund transfer may occur within the service provider server 180 if the accounts are in the account database 184 .
- the service provider server 180 updates the user account associated to the user 102 to reflect the monetary fund transfer (block 380 ). It should be appreciated by those skilled in the art that the service provider server 180 may cancel the online information transaction at any point in the process if it is determined that the user 102 enters wrong information or the user 102 is trying to access information with criminal intent.
- FIG. 4 is a block diagram of a computer system 400 suitable for implementing one or more embodiments of the present disclosure, including the kiosk device 120 , the mobile communication device 132 , and the service provider server 180 .
- the kiosk device 140 may comprise a stand-alone computing device, such as an interactive computer terminal
- the mobile communication device 132 may comprise a mobile cellular phone, personal computer (PC), laptop, PDA, etc. adapted for wireless communication
- the service processing device 180 may comprise a network computing device, such as a server.
- the devices 120 , 132 , 180 may be implemented as computer system 400 in a manner as follows.
- computer system 400 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, such as the network interface components 128 , 188 as discussed in reference to FIG.
- 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, such as the network interface components 128 , 188 as discussed in reference to FIG.
- disk drive component 410 may comprise a database having one or more disk drive components.
- computer system 400 performs specific operations by processor 404 executing one or more sequences of one or more instructions contained in system memory component 404 .
- 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 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 computer system 400 .
- a plurality of computer systems 400 coupled by communication link 420 e.g., network 160 of FIG. 1 , LAN, WLAN, PTSN, or various other wired or wireless 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.
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Finance (AREA)
- Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Technology Law (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
Description
- This application is a continuation of co-pending U.S. patent application Ser. No. 12/339,794, filed Dec. 19, 2008, which is hereby incorporated by reference in its entirety.
- 1. Technical Field
- The present invention generally relates to network transactions and more particularly to facilitating mobile transactions with cash based funding.
- 2. Related Art
- In many online environments, a user navigates through selectable pages of service provider sites to view information resources, process financial transactions, and/or communicate with other users. In the recent past, cellular phones have been adapted to navigate communication networks, such as the Internet.
- Generally, in some parts of the world, there are communities of people that use cash to exchange goods and services instead of using banking institutions and services for these types of financial transactions. However, some of these communities use cellular phones.
- Presently, there is a need to provide the service of a banking institution to those that transact business with cash. As such, there is need to combine the service of banking with the common use of cellular phones.
- Systems and methods disclosed herein, in accordance with one or more embodiments, facilitate financial transactions via a mobile communication device, such as a cellular phone, with cash based funding via a kiosk device, such as a machine having a receptacle adapted to accept monetary funds, such as cash, as a physical input. In various implementations, a user may fund an account by depositing cash into a kiosk, machine, or in person at a store or other physical location. After depositing the cash, the user may proceed with monetary fund transfers into and out of an account related to the user using the mobile communication device (e.g., cellular phone).
- In accordance with an embodiment of the present disclosure, a system for facilitating financial transactions over a network includes a first component adapted to communicate with a user via a kiosk device and a mobile communication device over the network and a second component adapted to access an account related to the user. The second component is adapted to deposit funds into the account based on a cash deposit request received from the user at the kiosk device. The second component is adapted to transfer funds from the account to one or more other accounts based on a fund transfer request received from the user via the mobile communication device.
- In various implementations, user identification information may be passed with the cash deposit request from the kiosk device to the second component via the network and the first component, wherein the user identification information is used by the second component to verify an identify of the user and access the account related to the user. Similarly, user identification information may be passed with the fund transfer request from the mobile communication device to the second component via the network and the first component, wherein the user identification information is used by the second component to verify an identify of the user and access the account related to the user.
- In various implementations, the kiosk device comprises an automated user interface, such as a computer, adapted to interface with the network and communicate with the second component via the network and the first component. The kiosk device may include a user interface application adapted to allow the user to communicate with the second component via the first component and the network and a receptacle adapted to receive cash from the user for deposit in the account. The mobile communication device comprises a cellular phone adapted to communicate with the second component via the network and the first component. The system comprises a server adapted to interface with the network and communicate with the kiosk device and the mobile communication device via the network.
- In accordance with an embodiment of the present disclosure, a method for facilitating financial transactions over a network includes communicating with a user via a kiosk device over the network and a mobile communication device over the network and accessing an account related to the user. The method includes depositing funds into the account based on a cash deposit request received from the user at the kiosk device. The method includes transferring funds from the account to one or more other accounts based on a fund transfer request received from the user via the mobile communication device.
- In various implementations, the method may include receiving a login request from the user via the kiosk device and verifying an identity of the user, wherein user identification information is passed with the cash deposit request from the kiosk device. The method may include receiving a login request from the user via the mobile communication device and verifying an identity of the user, wherein user identification information is passed with the fund transfer request from the mobile communication device.
- These and other features and advantages of the present disclosure will be more readily apparent from the detailed description of the embodiments set forth below taken in conjunction with the accompanying drawings.
-
FIG. 1 shows a block diagram of a system adapted to facilitate financial transactions over a network, in accordance with an embodiment of the present disclosure. -
FIGS. 2A-2B show various client-side methods for facilitating financial transactions over a network, in accordance with embodiments of the present disclosure. -
FIGS. 3A-3B show various server-side methods for facilitating financial transactions over a network, in accordance with embodiments 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.
- One or more embodiments of the present disclosure relate to facilitating financial transactions via a mobile communication device, such as a cellular phone, with cash based funding via a kiosk device, such as a machine that accepts monetary funds, such as cash, as a physical input. In various implementations, a user may fund an account by depositing cash into a kiosk, machine, or in person at a store or other physical location. After depositing the cash, the user may proceed with transfers into and out of an account related to the user using a mobile communication device (e.g., a cellular phone). In one aspect, a user profile may be created using the data obtained from cellular phone activity.
- One or more embodiments of the present disclosure enable people in communities without access to services of a banking institution to use the financial services of an online service provider via mobile communion devices including cellular phones. The user is able to fund an account with the online service provider by depositing cash into a kiosk device or machine at a physical location, which may be accomplished in various ways, such as the user directly depositing cash in the kiosk device or machine, or giving the cash to a cashier in a store or shop to deposit the cash in the kiosk device or machine. Once the user has funded an account via cash deposit, the user may then use the funds in the account to transact business via the user's cellular phone, such as transferring cash to other accounts related to the user and/or other accounts unrelated to the user. These transactions may be used by the online service provider to create a user profile based on the activity from the cellular phone.
-
FIG. 1 shows one embodiment of a block diagram of asystem 100 adapted to facilitate mobile transactions over anetwork 160 with cash based funding. As shown inFIG. 1 , thesystem 100 includes at least onekiosk device 120, at least onemobile device 132, and at least oneservice provider server 180 in communication over thenetwork 160. - The
network 160, in one embodiment, may be implemented as a single network or a combination of multiple networks. For example, in various embodiments, thenetwork 160 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 comprise a wireless telecommunications network (e.g., mobile cellular phone network) adapted to communicate with other communication networks, such as the Internet. - The
kiosk device 120, in various embodiments, may be implemented using any appropriate combination of hardware and/or software configured for wired and/or wireless communication over thenetwork 160. In various examples, thekiosk device 120 may be implemented as a wired and/or wireless communication device (e.g., an automated user interface device) for a user 102 (e.g., a client or customer) to communicate with thenetwork 160, such as the Internet and/or mobile network. It should be appreciated that, in various embodiments, thekiosk device 120 may be referred to as a user device, client device or a customer device without departing from the scope of the present disclosure. - The
kiosk device 120, in one embodiment, comprises a machine (e.g., automated teller machine (ATM)) adapted to directly accept monetary funds (e.g., cash) from a person, such as theuser 102. In one implementation, thekiosk device 120 may be used by an operator, in person, at a store or other physical location, wherein the operator may receive monetary funds from theuser 102 for deposit into thekiosk device 120. As such, thekiosk device 120 includes a cash receptacle (not shown) to receive cash for deposit in an account related to theuser 102. In another implementation, theuser 102 is able to input data and information into an input component (e.g., a keyboard) of thekiosk device 120 to provide user information with a transaction request, such as a cash deposit request. The user information may include user identification information, user account number, and a user password, which is described in greater detail herein. - The
kiosk device 120 includes one or moreuser interface applications 122, which may be used by theuser 102 to conduct financial transactions over thenetwork 160. For example, theuser interface application 122 may be implemented as an ATM application to deposit cash into an account over thenetwork 160. In one implementation, theuser interface application 122 comprises a software program, such as a graphical user interface (GUI), executable by a processor that is configured to interface and communicate with the one or moreservice provider servers 180 via thenetwork 160. - The
kiosk device 120, in various embodiments, may include one or moreother applications 124 to provide additional features to theuser 102. For example, theseother applications 124 may include security applications for implementing client-side security features, programmatic client applications for interfacing with appropriate application programming interfaces (APIs) over thenetwork 160 or various other types of generally known programs and/or applications. - The
kiosk device 120, in one embodiment, may include at least one network interface component (NIC) 128 adapted to communicate with thenetwork 160. In various examples, thenetwork interface component 128 may comprise a DSL (e.g., Digital Subscriber Line) modem, a PSTN (Public Switched Telephone Network) modem, an Ethernet device, a broadband device, a satellite device and/or various other types of wired and/or wireless network communication devices including microwave, radio frequency (RF), and infrared (IR) communication devices. - The
kiosk device 120, in one embodiment, may include one ormore kiosk identifiers 130, which may be implemented as operating system registry entries, cookies associated with theuser interface application 122, identifiers associated with hardware of thekiosk device 120, and/or various other appropriate identifiers. Thekiosk identifier 130 may include attributes related to thekiosk device 120, such as identification information (e.g., a kiosk serial number, a location address, Global Positioning System (GPS) coordinates, a network identification number, etc.) and network information (e.g., network owner, network provider, network administrator, network security information, etc.). In various implementations, thekiosk identifier 130 may be passed with network traffic data and information to theservice provider server 180, and thekiosk identifier 130 may be used by theservice provider server 180 to associate one or more network transactions of theuser 102 with one or more particular user account maintained by theservice provider server 180. - The
mobile communication device 132, in one embodiment, may be utilized by theuser 102 to interact with theservice provider server 180 over thenetwork 160. For example, theuser 102 may conduct financial transactions (e.g., account transfers) with theservice provider server 180 via themobile communication device 132. In various implementations, themobile communication device 132 may include at least one of a wireless cellular phone, personal digital assistant (PDA), satellite phone, etc. In one aspect, it should be appreciated by those skilled in the art that themobile communication device 132 may be integrated as part of a client device (not shown), such as a personal computer, without departing from the scope of the present disclosure. - In various implementations, a user profile may be created using data and information obtained from cell phone activity over the
network 160. Cell phone activity transactions may be used by theservice provider server 180 to create at least one user profile for theuser 102 based on activity from the mobile communication device 132 (e.g., cell phone). The user profile may be updated with each financial and/or information transaction (e.g., payment transaction, purchase transaction, etc.) achieved through use of themobile communication device 132. In various aspects, this may include the type of transaction and/or the location information from themobile communication device 132. As such, the profile may be used for recognizing patterns of potential fraud, setting transaction limits on the user, etc. - The
mobile communication device 132, in one embodiment, may include a user identifier as one or more attributes related to theuser 102, such as personal information (e.g., a user name, password, photograph image, biometric id, address, social security number, phone number, email address, etc.) and banking information (e.g., banking institution, credit card issuer, user account numbers, security information, etc.). In various implementations, the user identifier may be passed with network traffic data of theuser 102 to theservice provider server 180, and the user identifier may be used by theservice provider server 180 to associate theuser 102 with a user account maintained by theservice provider server 180. - In various implementations, the
user 102 is able to input data and information into an input component (e.g., a keyboard) of themobile communication device 132 to provide user information with a transaction request, such as a fund transfer request. The user information may include user identification information, user account number, and a user password, which is described in greater detail herein. - The
service provider server 180, in various embodiments, may be maintained by an online service provider, which is adapted to provide processing for financial transactions on behalf of theuser 102. Theservice provider server 180 includes at least oneprocessing application 182, which may be adapted to interact with thekiosk device 120 and themobile communication device 132 via thenetwork 160 to facilitate financial transactions. In one example, theservice provider server 180 may be provided by PayPal, Inc. of San Jose, Calif., USA. - The
service provider server 180, in one embodiment, may be configured to maintain a plurality of user accounts in anaccount database 184, each of which may includeaccount information 186 associated with individual users, including theuser 102. For example, accountinformation 186 may include balance information, fund transfer information, deposit information, etc. In another example, accountinformation 186 may include identification information and/or private financial information of theuser 102, such as account numbers, identifiers, passwords, phone numbers, credit card information, banking information, or other types of financial information, which may be used to facilitate online transactions between theuser 102 of thekiosk device 120 and theservice provider server 180. It should be appreciated that the methods and systems described herein may be modified to accommodate users that may or may not be associated with at least one existing user account. - The
service provider server 180, in various embodiments, may include at least one network interface component (NIC) 188 adapted to communicate with thenetwork 160 including thenetwork interface component 128 of thekiosk device 120 and themobile communication device 132. In various implementations, thenetwork interface component 128 may comprise a DSL (e.g., Digital Subscriber Line) modem, a PSTN (Public Switched Telephone Network) modem, an Ethernet device, a broadband device, a satellite device and/or various other types of wired and/or wireless network communication devices including microwave, radio frequency (RF), and infrared (IR) communication devices. - The
service provider server 180, in various embodiments, may include one or more databases 190 (e.g., internal and/or external databases) for storing and tracking information related to financial transactions between particular users, such as theuser 102, and theservice provider server 180. For example, thedatabases 190 may provide an historical survey of financial transactions between theuser 102 and theservice provider 180. As such, in one implementation, theprocessing application 182 may be configured to track, log, store, and access financial transaction information and provide this information to theprocessing application 182 for analysis and maintenance. - In various embodiments, the
kiosk device 120, themobile communication device 132 and theservice provider server 180 may be associated with a particular link (e.g., a link, such as a URL (Uniform Resource Locator) to an IP (Internet Protocol) address). In this regard, theuser 102 may interface with thekiosk device 120 and/or themobile communication device 132 via thenetwork 160 to facilitate financial transactions with theservice provider server 180, which is discussed in greater detail herein. -
FIG. 2A shows one embodiment of amethod 200 for facilitating financial transactions via thenetwork 160 with cash based funding. In one implementation, theuser 102 may run theuser interface application 122 on thekiosk device 120 to access at least one resource provider site via theservice provider server 180 to viewaccount information 186 related to theuser 102. Access to the service provider site may be made available to theuser 102 by theservice provider server 180, wherein theservice provider server 180 uses theprocessing application 182 to interact with theuser 102 via the server provider site. - Referring to
FIG. 2A , themethod 200 involves theuser 102 interacting with thekiosk device 120 to login to the service provider server 180 (block 210). In one example, this may involve theuser 102 accessing a service provider site via thekiosk device 120, which is adapted to communicate with theserver provider server 180 via thenetwork 160. Theuser 102 may provide an identification number and password to login to theservice provider server 180. In one aspect, thekiosk device 120 serves as a gateway to thenetwork 160 for cash based funding of an account related to theuser 102. - Next, the
user 102 accesses a user account in theaccount database 184 of the server provider server 180 (block 214). In one example, this may involve theuser 102 selecting an appropriate user account after login. Next, theuser 102 may select a financial transaction for processing, such as a cash deposit into the kiosk device 120 (block 218). In one example, this may involve theuser 102 inserting cash into thekiosk device 120 when prompted by the kiosk device 120 (block 222). Next, theuser 102 obtains a transaction receipt from the kiosk device 120 (block 226). In one example, the transaction receipt indicates the amounted of cash deposited and the date and time of the cash deposit. -
FIG. 2B shows one embodiment of amethod 250 for facilitating financial transactions over thenetwork 160 with themobile communication device 132. In one implementation, theuser 102 may use themobile communication device 132 to access at least one service provider site via theservice provider server 180 to process financial transactions andview account information 186 related to theuser 102. Access to the service provider site may be made available tomobile communication device 132 of theuser 102 by theservice provider server 180, wherein theservice provider server 180 uses theprocessing application 182 to interact with the user'smobile communication device 132 via the server provider site. - Referring to
FIG. 2B , themethod 250 involves theuser 102 interacting with themobile communication device 132 to login to the service provider server 180 (block 260). In one example, this may involve theuser 102 accessing a service provider site via themobile communication device 132, which is adapted to communicate with theserver provider server 180 via thenetwork 160. Theuser 102 may provide an identification number and password to login to theservice provider server 180. Next, theuser 102 accesses a user account in theaccount database 184 of the server provider server 180 (block 264). In one example, this may involve theuser 102 selecting an appropriate user account after login. - Next, the
user 102 may select a financial transaction for processing, such as a monetary fund transfer from the accessed user account to one or more other accounts (block 268). In various examples, this may involve theuser 102 transferring monetary funds from the user account to one or more other accounts related and/or unrelated to the user 102 (block 272). In one aspect, themobile communication device 132 serves as a gateway to thenetwork 160 for monetary fund transfers between accounts specified by theuser 102. - Next, the
user 102 obtains a transaction receipt from the service provider server 180 (block 276). In various examples, the transaction receipt may be in the form of a text message and/or email, and the transaction receipt indicates the amount of monetary funds transferred, the account numbers involved in the monetary fund transfers, and the date and time of the monetary fund transfers. -
FIG. 3A shows one embodiment of amethod 300 for facilitating financial transactions via thenetwork 160 with cash based funding. In one implementation, theservice provider server 180 interacts with thekiosk device 120 to process financial transactions related to the user 102 (e.g., cash deposits into a user account). Access to theservice provider server 180 may be provided to theuser 102 over thenetwork 160 via thekiosk device 120, wherein theservice provider server 180 may utilize theprocessing application 182 to interact with theuser 102 via thekiosk device 120. - Referring to
FIG. 3A , theservice provider server 180 receives a login request via the kiosk device 120 (block 310), verifies the identity of the user 102 (block 314), and accesses at least one account related to theuser 102 in the account database 184 (block 316). In one implementation, theuser 102 interacts with thekiosk device 120 to provide an identification number and password to thekiosk device 120 for login to theservice provider server 180 via thenetwork 160. Theservice provider server 180 receives the identification number and password with the login request and verifies the identity of theuser 102, for example, by comparing the identification number and password provided by theuser 102 with the login request via thekiosk device 120 with an identification number and password stored as part of an account related to theuser 102 in theaccount database 184. Next, theservice provider server 180 locates and accesses at least one user account related to theuser 102 based on the identification information provided by theuser 102 as passed with the login request via thekiosk device 120. - Optionally, the
service provider server 180 may determine whether theuser 102 is an existing user having an establisheduser account 184, for example, by checking a user account list in theaccount database 184. If theuser 102 does not have an established user account, then theservice provider server 180 may prompt theuser 102 to establish auser account 184 with the service provider sever 180 by providing user identification andfinancial information 186 via thekiosk device 120. - Next, after login and account verification, the
service provider server 180 receives a transaction request for a monetary fund deposit (e.g., cash deposit) from theuser 102 via the kiosk device (block 318). Next, theservice provider server 180 processes the transaction request for the cash deposit (block 322). In one example, theservice provider server 180 accesses the user account related to theuser 102 and credits the user account with the user deposited cash funds as received by thekiosk device 120. Next, theservice provider server 180 verifies the cash deposit (block 326). In one example, theservice provider server 180 may communicate with thekiosk device 120 to verify (e.g., authenticate) that the indicated amount of cash deposited by theuser 102 was actually received and counted by thekiosk device 120. Next, theservice provider server 180 updates the user account associated to theuser 102 to reflect the cash deposit (block 330). It should be appreciated by those skilled in the art that theservice provider server 180 may cancel the online information transaction at any point in the process if it is determined that theuser 102 enters wrong information or theuser 102 is trying to access information with criminal intent. -
FIG. 3B shows one embodiment of amethod 350 for facilitating financial transactions over thenetwork 160 with themobile communication device 132. In one implementation, theservice provider server 180 interacts with themobile communication device 132 to process financial transactions related to the user 102 (e.g., monetary fund transfers between user accounts and/or other accounts). Access to theservice provider server 180 may be provided to theuser 102 over thenetwork 160 via themobile communication device 132, wherein theservice provider server 180 may utilize theprocessing application 182 to interact with theuser 102 via themobile communication device 132. - Referring to
FIG. 3B , theservice provider server 180 receives a login request via the mobile communication device 132 (block 360), verifies the identity of the user 102 (block 364), and accesses at least one account related to theuser 102 in the account database 184 (block 366). In one implementation, theuser 102 interacts with themobile communication device 132 to provide an identification number and password to themobile communication device 132 for login to theservice provider server 180 via thenetwork 160. Theservice provider server 180 receives the identification number and password with the login request and verifies the identity of theuser 102, for example, by comparing the identification number and password provided by theuser 102 with the login request via thekiosk device 120 with an identification number and password stored as part of an account related to theuser 102 in theaccount database 184. Next, theservice provider server 180 locates and accesses at least one user account related to theuser 102 based on the identification information provided by theuser 102 as passed with the login request via themobile communication device 132. - Optionally, the
service provider server 180 may determine whether theuser 102 is an existing user having an establisheduser account 184, for example, by checking a user account list in theaccount database 184. If theuser 102 does not have an established user account, then theservice provider server 180 may prompt theuser 102 to establish auser account 184 with the service provider sever 180 by providing user identification andfinancial information 186 via themobile communication device 132. - Next, after login and account verification, the
service provider server 180 receives a transaction request for a monetary fund transfer between accounts from theuser 102 via the mobile communication device 132 (block 368). Next, theservice provider server 180 processes the transaction request for the monetary fund transfer (block 372). In one example, theservice provider server 180 accesses the user account related to theuser 102 and debits the user account for credit to another user account or some other account indicated by theuser 102. Next, theservice provider server 180 verifies that the monetary funds have been transferred as requested by the user 102 (block 376). In one example, theservice provider server 180 may communicate with other financial organizations to verify (e.g., authenticate) that the indicated amount of monetary funds transferred was actually received and credited to the proper accounts. In another example, verification of monetary fund transfer may occur within theservice provider server 180 if the accounts are in theaccount database 184. Next, theservice provider server 180 updates the user account associated to theuser 102 to reflect the monetary fund transfer (block 380). It should be appreciated by those skilled in the art that theservice provider server 180 may cancel the online information transaction at any point in the process if it is determined that theuser 102 enters wrong information or theuser 102 is trying to access information with criminal intent. -
FIG. 4 is a block diagram of acomputer system 400 suitable for implementing one or more embodiments of the present disclosure, including thekiosk device 120, themobile communication device 132, and theservice provider server 180. In various implementations, the kiosk device 140 may comprise a stand-alone computing device, such as an interactive computer terminal, themobile communication device 132 may comprise a mobile cellular phone, personal computer (PC), laptop, PDA, etc. adapted for wireless communication, and theservice processing device 180 may comprise a network computing device, such as a server. Thus, it should be appreciated that thedevices computer system 400 in a manner as follows. - In accordance with various embodiments of the present disclosure,
computer system 400 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, such as thenetwork interface components FIG. 1 ), 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 404. 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
computer system 400. In various other embodiments of the present disclosure, a plurality ofcomputer systems 400 coupled by communication link 420 (e.g.,network 160 ofFIG. 1 , LAN, WLAN, PTSN, or various other wired or wireless 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)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/470,616 US20140372313A1 (en) | 2008-12-19 | 2014-08-27 | Systems and methods for mobile transactions |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/339,794 US8930272B2 (en) | 2008-12-19 | 2008-12-19 | Systems and methods for mobile transactions |
US14/470,616 US20140372313A1 (en) | 2008-12-19 | 2014-08-27 | Systems and methods for mobile transactions |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/339,794 Continuation US8930272B2 (en) | 2008-12-19 | 2008-12-19 | Systems and methods for mobile transactions |
Publications (1)
Publication Number | Publication Date |
---|---|
US20140372313A1 true US20140372313A1 (en) | 2014-12-18 |
Family
ID=42267472
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/339,794 Active 2031-11-15 US8930272B2 (en) | 2008-12-19 | 2008-12-19 | Systems and methods for mobile transactions |
US14/470,616 Abandoned US20140372313A1 (en) | 2008-12-19 | 2014-08-27 | Systems and methods for mobile transactions |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/339,794 Active 2031-11-15 US8930272B2 (en) | 2008-12-19 | 2008-12-19 | Systems and methods for mobile transactions |
Country Status (3)
Country | Link |
---|---|
US (2) | US8930272B2 (en) |
CN (1) | CN102257527B (en) |
WO (1) | WO2010071715A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150014411A1 (en) * | 2013-07-10 | 2015-01-15 | Xerox Corporation | Transaction card for workflow execution |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8285640B2 (en) * | 2008-07-23 | 2012-10-09 | Ebay, Inc. | System and methods for facilitating fund transfers over a network |
US20170155605A1 (en) * | 2009-01-15 | 2017-06-01 | Nsixty, Llc | Video communication system and method for using same |
US11210674B2 (en) * | 2010-11-29 | 2021-12-28 | Biocatch Ltd. | Method, device, and system of detecting mule accounts and accounts used for money laundering |
US8527414B2 (en) * | 2011-01-14 | 2013-09-03 | Bank Of America Corporation | Offsetting future account discrepancy assessments |
WO2012099885A1 (en) * | 2011-01-18 | 2012-07-26 | Ebay Inc. | Techniques to access a cloud-based wallet using a basic handset |
US8874467B2 (en) * | 2011-11-23 | 2014-10-28 | Outerwall Inc | Mobile commerce platforms and associated systems and methods for converting consumer coins, cash, and/or other forms of value for use with same |
US8676709B2 (en) * | 2012-07-31 | 2014-03-18 | Google Inc. | Merchant category codes in a proxy card transaction |
US10313264B2 (en) | 2014-05-28 | 2019-06-04 | Apple Inc. | Sharing account data between different interfaces to a service |
USD748196S1 (en) | 2014-08-27 | 2016-01-26 | Outerwall Inc. | Consumer operated kiosk for sampling products |
US20170024734A1 (en) * | 2015-07-21 | 2017-01-26 | Mastercard International Incorporated | Systems and Methods for Processing Transactions to Payment Accounts |
Citations (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020052754A1 (en) * | 1998-09-15 | 2002-05-02 | Joyce Simon James | Convergent communications platform and method for mobile and electronic commerce in a heterogeneous network environment |
US20030185361A1 (en) * | 1997-07-22 | 2003-10-02 | British Telecommunications | Fraud monitoring system |
US20030216964A1 (en) * | 2002-04-02 | 2003-11-20 | Maclean Trevor Robert | Apparatus and method of distributing and tracking the distribution of incentive points |
US20040014457A1 (en) * | 2001-12-20 | 2004-01-22 | Stevens Lawrence A. | Systems and methods for storage of user information and for verifying user identity |
US6748367B1 (en) * | 1999-09-24 | 2004-06-08 | Joonho John Lee | Method and system for effecting financial transactions over a public network without submission of sensitive information |
US20050086168A1 (en) * | 2003-10-17 | 2005-04-21 | Alvarez David R. | Systems and methods for money sharing |
US20050097051A1 (en) * | 2003-11-05 | 2005-05-05 | Madill Robert P.Jr. | Fraud potential indicator graphical interface |
US20060136332A1 (en) * | 2004-10-01 | 2006-06-22 | Robert Ziegler | System and method for electronic check verification over a network |
US20070011104A1 (en) * | 2003-03-21 | 2007-01-11 | Ebay Inc. | Payment transactions via substantially instant communication system |
US20070125839A1 (en) * | 2005-12-07 | 2007-06-07 | John Royce-Winston | System and method for creating digital currency |
US20070168283A1 (en) * | 2003-10-17 | 2007-07-19 | Nexxo Financial Corporation | Self-service money remittance with an access card |
US20070199053A1 (en) * | 2006-02-13 | 2007-08-23 | Tricipher, Inc. | Flexible and adjustable authentication in cyberspace |
US20070219928A1 (en) * | 2006-03-16 | 2007-09-20 | Sushil Madhogarhia | Strategy-driven methodology for reducing identity theft |
US20080203150A1 (en) * | 2006-04-07 | 2008-08-28 | John Royce-Winston | System and method for creating digital currency |
US20090076934A1 (en) * | 2007-09-19 | 2009-03-19 | Hamed Shahbazi | Personalized customer transaction system |
US7529710B1 (en) * | 2004-06-10 | 2009-05-05 | Valid Systems | Monitoring transactions by non-account holder |
US7568615B2 (en) * | 2005-08-24 | 2009-08-04 | E-Cash Financial, Inc. | Electronic transfer of hard currency |
US7571140B2 (en) * | 2002-12-16 | 2009-08-04 | First Data Corporation | Payment management |
US20090254479A1 (en) * | 2008-04-02 | 2009-10-08 | Pharris Dennis J | Transaction server configured to authorize payment transactions using mobile telephone devices |
US20090265260A1 (en) * | 2008-04-22 | 2009-10-22 | Christian Aabye | Prepaid chip card exception processing |
US7610040B2 (en) * | 2003-02-21 | 2009-10-27 | Swisscom Mobile Ag | Method and system for detecting possible frauds in payment transactions |
US20100145818A1 (en) * | 2002-09-30 | 2010-06-10 | Ifedayo Udiani | Electronic Credit/Debit Cardless Payment Processing System and Method PSM |
US20100211507A1 (en) * | 2008-09-22 | 2010-08-19 | Christian Aabye | Over the air update of payment transaction data stored in secure memory |
Family Cites Families (34)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5915023A (en) * | 1997-01-06 | 1999-06-22 | Bernstein; Robert | Automatic portable account controller for remotely arranging for transfer of value to a recipient |
US20030217005A1 (en) * | 1996-11-27 | 2003-11-20 | Diebold Self Service Systems, Division Of Diebold, Incorporated | Automated banking machine system and method |
US7004385B1 (en) * | 2003-04-01 | 2006-02-28 | Diebold Self-Service Systems Division Of Diebold, Incorporated | Currency dispensing ATM with RFID card reader |
US7445146B2 (en) * | 1998-04-17 | 2008-11-04 | Diebold, Incorporated | Card activated cash dispensing automated banking machine system and method |
US7946480B2 (en) * | 1998-04-17 | 2011-05-24 | Diebold Self-Service Systems, Division Of Diebold, Incorporated | Transaction dependent on ATM receiving user input of the security code sent during transaction to account'S designated mobile phone |
GB9814451D0 (en) * | 1998-07-04 | 1998-09-02 | Ncr Int Inc | Cash transaction verification and crediting apparatus |
FI105965B (en) * | 1998-07-07 | 2000-10-31 | Nokia Networks Oy | Authentication in telecommunications networks |
WO2001052170A1 (en) * | 2000-01-13 | 2001-07-19 | Citicorp Development Center, Inc. | A method and system for accessing financial information using wireless devices |
EP1134705A3 (en) * | 2000-02-18 | 2003-08-20 | NRC International Inc. | Self service terminal |
US20010051920A1 (en) * | 2000-06-07 | 2001-12-13 | Joao Raymond Anthony | Financial transaction and/or wireless communication device authorization, notification and/or security apparatus and method |
EP1180750A1 (en) * | 2000-08-18 | 2002-02-20 | Siemens Aktiengesellschaft | Method and system for transmitting an amount of electronic money from a credit memory |
US7418427B1 (en) * | 2000-10-04 | 2008-08-26 | Diebold, Incorporated | Automated banking machine system and method |
GB0027922D0 (en) * | 2000-11-15 | 2001-01-03 | Haidar Mahmoud N Y | Electronic payment and associated systems |
WO2003046784A1 (en) * | 2001-11-29 | 2003-06-05 | Niel Eben Viljoen | Method and system for operating a banking service |
US20030177028A1 (en) * | 2002-03-07 | 2003-09-18 | John Cooper | Method and apparatus for remotely altering an account |
JPWO2003081495A1 (en) * | 2002-03-25 | 2005-07-28 | 富士通株式会社 | Automated cash transaction system |
US7416112B2 (en) * | 2006-04-05 | 2008-08-26 | Diebold Self-Service Systems Division Of Diebold, Incorporated | Automated banking machine system and method |
WO2004092993A1 (en) * | 2003-04-09 | 2004-10-28 | Gtech Rhode Island Corporation | Electronic payment system |
US20050065876A1 (en) * | 2003-05-12 | 2005-03-24 | Pulkit Kumar | Airbank, pay to anyone from the mobile phone |
US20050097046A1 (en) * | 2003-10-30 | 2005-05-05 | Singfield Joy S. | Wireless electronic check deposit scanning and cashing machine with web-based online account cash management computer application system |
US20060100961A1 (en) * | 2004-10-15 | 2006-05-11 | Texas Instruments Incorporated | Automated teller machine, a personal wireless device and methods of transferring funds therebetween |
KR100670779B1 (en) * | 2004-10-22 | 2007-01-17 | 한국전자통신연구원 | Automated teller machine having an accessing point and method for providing financial service using the same |
US7175073B2 (en) * | 2005-03-02 | 2007-02-13 | International Business Machines Corporation | Secure cell phone for ATM transactions |
US20060212407A1 (en) * | 2005-03-17 | 2006-09-21 | Lyon Dennis B | User authentication and secure transaction system |
US7628325B2 (en) * | 2005-11-08 | 2009-12-08 | At&T Intellectual Property I, Lp | Systems, methods and computer program products for wirelessly preprocessing a transaction while in a queue for a point-of-transaction |
US20070174082A1 (en) * | 2005-12-12 | 2007-07-26 | Sapphire Mobile Systems, Inc. | Payment authorization using location data |
US20070203835A1 (en) * | 2006-02-27 | 2007-08-30 | Yigang Cai | Automated teller service using wireless telephony |
WO2007109559A2 (en) * | 2006-03-21 | 2007-09-27 | Phone1, Inc. | Financial transactions using a communication device |
US8249965B2 (en) * | 2006-03-30 | 2012-08-21 | Obopay, Inc. | Member-supported mobile payment system |
EP2050053A1 (en) * | 2006-07-24 | 2009-04-22 | Roberto Salemi | Goods/ information distribution method by an atm terminal without using a debit/credit card |
US8045956B2 (en) * | 2007-01-05 | 2011-10-25 | Macronix International Co., Ltd. | System and method of managing contactless payment transactions using a mobile communication device as a stored value device |
US20090164371A1 (en) * | 2007-11-20 | 2009-06-25 | M Commerce Data Systems, Inc. | Mobile Financial Transaction Method |
WO2010003239A1 (en) * | 2008-07-09 | 2010-01-14 | Xtreme Mobility Inc. | Secure wireless deposit system and method |
US20100057614A1 (en) * | 2008-08-26 | 2010-03-04 | Qualcomm Incorporated | System and method for effecting real-time financial transactions between delayed-settlement financial accounts |
-
2008
- 2008-12-19 US US12/339,794 patent/US8930272B2/en active Active
-
2009
- 2009-10-29 CN CN200980151234.3A patent/CN102257527B/en not_active Expired - Fee Related
- 2009-10-29 WO PCT/US2009/062638 patent/WO2010071715A1/en active Application Filing
-
2014
- 2014-08-27 US US14/470,616 patent/US20140372313A1/en not_active Abandoned
Patent Citations (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030185361A1 (en) * | 1997-07-22 | 2003-10-02 | British Telecommunications | Fraud monitoring system |
US20020052754A1 (en) * | 1998-09-15 | 2002-05-02 | Joyce Simon James | Convergent communications platform and method for mobile and electronic commerce in a heterogeneous network environment |
US6748367B1 (en) * | 1999-09-24 | 2004-06-08 | Joonho John Lee | Method and system for effecting financial transactions over a public network without submission of sensitive information |
US20040014457A1 (en) * | 2001-12-20 | 2004-01-22 | Stevens Lawrence A. | Systems and methods for storage of user information and for verifying user identity |
US20030216964A1 (en) * | 2002-04-02 | 2003-11-20 | Maclean Trevor Robert | Apparatus and method of distributing and tracking the distribution of incentive points |
US20100145818A1 (en) * | 2002-09-30 | 2010-06-10 | Ifedayo Udiani | Electronic Credit/Debit Cardless Payment Processing System and Method PSM |
US7571140B2 (en) * | 2002-12-16 | 2009-08-04 | First Data Corporation | Payment management |
US7610040B2 (en) * | 2003-02-21 | 2009-10-27 | Swisscom Mobile Ag | Method and system for detecting possible frauds in payment transactions |
US20070011104A1 (en) * | 2003-03-21 | 2007-01-11 | Ebay Inc. | Payment transactions via substantially instant communication system |
US20050086168A1 (en) * | 2003-10-17 | 2005-04-21 | Alvarez David R. | Systems and methods for money sharing |
US20070168283A1 (en) * | 2003-10-17 | 2007-07-19 | Nexxo Financial Corporation | Self-service money remittance with an access card |
US8204829B2 (en) * | 2003-10-17 | 2012-06-19 | Nexxo Financial Corporation | Systems and methods for money sharing |
US20050097051A1 (en) * | 2003-11-05 | 2005-05-05 | Madill Robert P.Jr. | Fraud potential indicator graphical interface |
US7529710B1 (en) * | 2004-06-10 | 2009-05-05 | Valid Systems | Monitoring transactions by non-account holder |
US20060136332A1 (en) * | 2004-10-01 | 2006-06-22 | Robert Ziegler | System and method for electronic check verification over a network |
US7568615B2 (en) * | 2005-08-24 | 2009-08-04 | E-Cash Financial, Inc. | Electronic transfer of hard currency |
US20070125839A1 (en) * | 2005-12-07 | 2007-06-07 | John Royce-Winston | System and method for creating digital currency |
US20070199053A1 (en) * | 2006-02-13 | 2007-08-23 | Tricipher, Inc. | Flexible and adjustable authentication in cyberspace |
US20070219928A1 (en) * | 2006-03-16 | 2007-09-20 | Sushil Madhogarhia | Strategy-driven methodology for reducing identity theft |
US20080203150A1 (en) * | 2006-04-07 | 2008-08-28 | John Royce-Winston | System and method for creating digital currency |
US20090076934A1 (en) * | 2007-09-19 | 2009-03-19 | Hamed Shahbazi | Personalized customer transaction system |
US20090254479A1 (en) * | 2008-04-02 | 2009-10-08 | Pharris Dennis J | Transaction server configured to authorize payment transactions using mobile telephone devices |
US20090265260A1 (en) * | 2008-04-22 | 2009-10-22 | Christian Aabye | Prepaid chip card exception processing |
US20100211507A1 (en) * | 2008-09-22 | 2010-08-19 | Christian Aabye | Over the air update of payment transaction data stored in secure memory |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150014411A1 (en) * | 2013-07-10 | 2015-01-15 | Xerox Corporation | Transaction card for workflow execution |
Also Published As
Publication number | Publication date |
---|---|
CN102257527B (en) | 2016-08-24 |
US20100161487A1 (en) | 2010-06-24 |
WO2010071715A1 (en) | 2010-06-24 |
US8930272B2 (en) | 2015-01-06 |
CN102257527A (en) | 2011-11-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8930272B2 (en) | Systems and methods for mobile transactions | |
US12033145B2 (en) | Systems and methods for facilitating account verification over a network | |
US20230059316A1 (en) | Systems and methods for performing financial transactions using active authentication | |
US10885574B2 (en) | System and method for location based mobile commerce | |
US11694200B2 (en) | Secure account creation | |
US8285640B2 (en) | System and methods for facilitating fund transfers over a network | |
US10255597B2 (en) | System and method for automatically filling webpage fields | |
US9679294B2 (en) | In-store card activation | |
US20130262303A1 (en) | Secure transactions with a mobile device | |
US20170109750A1 (en) | Systems and methods for facilitating card verification over a network | |
US20160042328A1 (en) | Systems and methods for facilitating sharing of expenses over a network | |
US8494962B2 (en) | Method and system for secure mobile remittance | |
US11348150B2 (en) | Systems and methods for facilitating card verification over a network | |
US11868977B1 (en) | Payment services via application programming interface | |
US20230021963A1 (en) | Systems and methods for facilitating card verification over a network | |
EP4150542A1 (en) | Account rebalancing daemon for use with secure digital asset custodians |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: EBAY INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PATEL, AMOL;VERNON, FREDERIK MALCOLM;SIGNING DATES FROM 20081216 TO 20081217;REEL/FRAME:035010/0203 |
|
AS | Assignment |
Owner name: PAYPAL, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:EBAY INC.;REEL/FRAME:036171/0221 Effective date: 20150717 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STCV | Information on status: appeal procedure |
Free format text: NOTICE OF APPEAL FILED |
|
STCV | Information on status: appeal procedure |
Free format text: APPEAL BRIEF (OR SUPPLEMENTAL BRIEF) ENTERED AND FORWARDED TO EXAMINER |
|
STCV | Information on status: appeal procedure |
Free format text: EXAMINER'S ANSWER TO APPEAL BRIEF MAILED |
|
STCV | Information on status: appeal procedure |
Free format text: ON APPEAL -- AWAITING DECISION BY THE BOARD OF APPEALS |
|
STCV | Information on status: appeal procedure |
Free format text: BOARD OF APPEALS DECISION RENDERED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISION |