Systems and methods for remote check-in

Systems and methods are provided for facilitating remote check-in and associated proxy shopping operations. A proxy customer of a merchant may be a friend of a remote customer that is making a purchase at the merchant on behalf of the remote customer. A beacon may alert the proxy customer to check-in to the merchant. The proxy customer may forward the alert to the remote customer. The remote customer may request remote check-in responsive to the alert. A payment provider or service provider may perform a remote check-in of the remote customer and a proxy check-in of the proxy customer. When the proxy customer wishes to make a proxy purchase for the remote user, the merchant may verify the proxy customer's identity and charge the payment provider. The payment provider may then transfer funds from remote customer's account to the merchant's account.

TECHNICAL FIELD

The present invention generally relates to electronic commerce and, more particularly, to systems and methods for remote check-in.

BACKGROUND

Consumers often visit stores, restaurants, and entertainment venues that offer services or products for the consumers. In some circumstances, a consumer will check in to a particular store, restaurant, or entertainment venue upon arrival at the store, restaurant, or entertainment venue to receive sales, discounts, or other advertisements. Additionally, a checked-in consumer is sometimes provided with the ability to complete a payment to the store, restaurant, or entertainment venue using an application on the consumer's mobile device. In this way, a consumer can be provided with customized service or offers and the ability to quickly and conveniently execute transactions. However, check-in services of this type are commonly only available to consumers who are physically co-located with the store, restaurant, or entertainment venue. This can be problematic for potential consumers for whom it is difficult or impossible to go to particular location and can result in the loss of availability of goods and services to the consumer and a related loss in sales for a merchant.

It would therefore be desirable to be able to provide systems and methods for facilitating remote check-in.

DETAILED DESCRIPTION

A service provider may include one or more locations where the service provider offers goods, products, services, or other items to users. In various embodiments, a service location may correspond to a merchant location offering products and/or services to the user.

Some users may visit a service location and check in with the service provider. A check-in of a user may be performed while the user is located at the service center using, for example, an electronic communication between a user device and a server of the service center (e.g., over a network such as the Internet), and/or electronic communication between the user device and a short range wireless beacon connection at the service center (e.g., a beacon associated with a payment provider or merchant). Checked-in users may receive in-person or electronic assistance in completing a transaction with the service provider, and/or may receive user-targeted offers, discounts, promotions, or other communications from the service provider. Transactions that the checked-in user may engage in may correspond to a payment for an item at a merchant, or may correspond to informational exchanges, updates, etc. that a service provider may offer (as examples).

Some users may check in to a service provider remotely using, for example, a proxy user at the service location. In various embodiments, a proxy user for a remote user may check-in at a service location on behalf of remote user. A proxy user (sometimes referred to herein as a proxy customer, a proxy shopper, or a local user) may be, according to an embodiment, a friend, a family member, an employee or any other associate of the remote user that is shopping and/or making a purchase at a merchant location on behalf of the remote user.

In one example usage scenario, a customer of a merchant that is located remotely from the merchant's location asks a friend to purchase an item for the customer at the merchant. When the customer's friend arrives at the merchant's location (e.g., a store), a beacon such as a payment provider beacon may alert the customer's friend to check-in using a mobile device of the friend. The customer's friend may forward the check-in alert to the customer (e.g., using Wi-Fi, cellular network or beacon communications technologies). The customer may accept a check-in offer associated with the forwarded check-in alert. The payment provider may perform a remote check-in operation for the customer (e.g., at a payment provider server and/or a merchant server) and perform a proxy check-in of the customer's friend to the merchant location on behalf of the customer. The merchant may, if desired, verify the customer friend's identity (e.g., using a photograph or other identifying information) and initiate a payment transaction for the customer by the customer's friend with the payment provider. The payment provider may then process the payment transaction by transferring funds from the customer's account to the merchant's account. In this way, a remote user can take advantage of the benefits of user check-in at various merchants and other service providers and a proxy user such as a friend, family member, employee, or other associate of the remote user can purchase products and/or services for the remote user using the remote user's funds for payment and without accessing any accounts of the proxy user.

Various locations provide short range wireless communications with a local user device such as a proxy user device, such as through Bluetooth Low Energy (BLE) beacon communications. A beacon may be disposed at a location and may communicate with the local user device to alert users such as proxy users and/or associated remote users of check-in services through their user device. The beacons may provide additional functionality, such as establishing a connection with a server entity to complete transactions, including check-in services. Additionally, the beacons may provide communication services to the local user device directly, including information stored on the beacons, and/or information from a device or server corresponding to the beacon.

The service location(s) may utilize short range wireless beacons to communicate with mobile user devices of the local users. The short range wireless beacons may employ BLE communications that emit a signal receivable by a local user device of a local user (e.g., a proxy user). The communication may include an identifier for the beacon. A local user device may passively monitor for BLE communications. When a local user device detects a BLE signal and verifies the identifier as belonging to a particular location such as a venue (e.g., a venue device and/or server), both the local user device and the beacon may ramp up in power and establish a connection. The connection may further enable the local user device and/or an associated remote user device of a remote user to communicate with a service provider device and/or server. The beacon may be connected to a networked device at the service location, or the beacon may include network functionality to communicate with the service provider server.

The service provider may access user information for the remote user and provide targeted assistance, products, and/or services to the local user based on the remote user information. In this way, a remote user and a service location may be able to take full advantage of the benefits of check-in services without the remote user travelling to the service location.

System100may include one or more users such as a local user102having a local user device180and a remote user104having a remote user device110, a service location130, a service provider server140, and a payment provider server160in communication over a network170. Local user102(e.g., a visitor to a service location) may utilize their corresponding local user device180to check-in to service provider server140. Service location130may correspond to a location that provides goods, products, item, and/or other services to a user including travel, medical, or other services. Service provider server140may correspond to a general server for multiple service locations (e.g. a server for a merchant chain) or may be specific to only service location130(e.g. a server for a hospital, airport, etc.).

Check-in of local users102may be accomplished through a wireless beacon132at service location130, through a social media application or website or by other check-in equipment. Local user102may be associated with remote user104. For example, local user102may be a registered proxy shopper for remote user104(e.g., registered with service provider server140and/or payment provider server160) or local user102may have contact information for remote user104for forwarding a check-in request. Local users such as local user102may check in for themselves or may check in as a proxy user for remote user104. Remote user104may check in to service provider server130and/or payment provider server160remotely via, for example, local user102. User information for local user102and/or remote user104(e.g., a purchase history or a check-in history at service location130or other services locations) may be obtained upon check-in.

Local user device180and remote user device110may be implemented using any appropriate hardware and software such as hardware and software configured for wired and/or wireless communication with wireless beacon132and/or service provider server140. For example, in various embodiments, either or both of local user device180and remote user device110may be implemented as a personal computer (PC), a smart phone, personal digital assistant (PDA), laptop computer, wristwatch with appropriate computer hardware resources, eyeglasses with appropriate computer hardware (e.g. GOOGLE GLASS®) and/or other types of computing devices capable of transmitting and/or receiving data, such as an IPAD® from APPLE®. Although user devices are shown, each user device may be managed or controlled by any suitable processing device.

Local user device180and remote user device110may each include a check-in application112, a service application120, other applications114, a database116, and a communication module118. Check-in application112, service application120, and other applications114may correspond to processes, procedures, and/or applications executable by a hardware processor, for example, a software program. In other embodiments, user device110may include additional or different software as required.

Check-in application112of local user device180may be used by local user102to establish a connection between that user device180and service location130, service provider server140, and/or payment provider server160for check-in such as proxy check-in of local user102. Check-in application112of remote user device110may be used by remote user104to establish a connection between that user device110and local user device180, service provider server140, and/or payment provider server160for check-in such as remote check-in of remote user104. A check-in application112may provide a general user device with the ability to function as a remote user device and/or a local user device as desired.

Check-in application112may correspond to an application available over the Internet for download from service provider server140and/or other server corresponding to service location130. Check-in application112may be set up to receive short range wireless communications with wireless beacon132at service location130to complete a check-in process. For example, service location130may include infrastructure with wireless beacon132to communicate with local user device180and complete the check-in process with service provider server140. Wireless beacon132may be configured to transmit an identifier for reception by local user device180.

Check-in application112may execute in the background of an operating system. Check-in application112of local user device180may be configured to establish connections, using communication module118of that user device180, with wireless beacon132at service location130.

Proxy check-in of local user102with service provider server140and/or payment provider server160may correspond to a process to log in to a user account of local user102with service provider server140and/or payment provider server160. In other embodiments, the proxy check-in may provide and/or verify the identity of local user102, including transmission of an identifier for local user102and/or local user device180. The check-in may be completed over network170with service provider server140and/or payment provider server160. In such embodiments, check-in application112may correspond more generally to a browser application configured to communicate with service provider server140and/or payment provider server160.

A connection between local user device180and wireless beacon132may be established with or without user input from user102. For example, wireless beacon132may broadcast a token, such as a universally unique identifier (UUID), for reception by local use device180. Check-in application112of local user device180may utilize communication module118of the local user device180to receive the token from wireless beacon132. If check-in application112acknowledges the UUID as identifying service location130, wireless beacon132, and/or service provider server140, check-in application112may transmit an identifier corresponding to user102and/or local user device180back to wireless beacon132. Check-in application112may utilize communication module118to communicate with wireless beacon132(e.g., over near field communication, Bluetooth, Bluetooth Low Energy, radio, infrared, or other connection). The identifier from local user device180may include, be transmitted with, concatenated with, or otherwise bundled with the identifier received from wireless beacon132.

Once a connection is established with wireless beacon132, local user device180may be checked-in with service provider server140if the user102of that device has not previously been checked-in and/or may be provided with one or more options for proxy check-in for a remote user. The check-in process may then associate that user102with wireless beacon132used to check-in that user102. In such embodiments, check-in application112of local user device180may utilize short range wireless communication with wireless beacon132, such as near field communication, Bluetooth, Bluetooth Low Energy, radio, infrared, or other connection. Where wireless beacon132corresponds generally to service location130, local user102may be associated with service location130. However, in other embodiments wireless beacon132may correspond to a location, item (i.e., a product or good), and/or service at service location130. Thus, local user102may be associated with that location, item, and/or service (e.g., a television sales section of a merchant, a departure area of an airport, a neonatal section of a hospital, etc.).

Local user102may be provided with the ability to check in and/or to forward a check-in alert to remote user104. Remote user device110may receive the check-in alert from local user102(e.g., directly or via service provider server140or payment provider server160). Check-in application112of remote user device110may provide the check-in alert to remote user104. Remote user104may use check-in application112of remote user device110to request remote check in. Remote user104may then be remotely checked in to service provider server140and/or payment provider server160.

Remote check-in of remote user104with service provider server140and/or payment provider server160may correspond to a process to log in to a user account of remote user104with service provider server140and/or payment provider server160. In other embodiments, the remote check-in may provide and/or verify the identity of remote user104, including transmission of an identifier for remote user104and/or remote user device110. The remote check-in may be completed over network170with service provider server140and/or payment provider server160. In some embodiments, check-in application112may correspond more generally to a browser application configured to communicate with service provider server140and/or payment provider server160.

The remote check-in process may then associate remote user104with service location130and/or local user102to check-in remote user104. Thus, remote user104may be associated with that location, item, and/or service (e.g., a television sales section of a merchant, a departure area of an airport, a neonatal section of a hospital, etc.) by proxy with local user102.

Check-in application112of remote user device110of a checked-in remote user may receive information (e.g., maps, processes to request assistance from the service provider, product and/or service offers, discounts, product information, etc.) from service provider server140. When remote user104is checked-in with service provider server140, service provider server140may have access to an identifier of remote user device110and may therefore transmit information to remote user device110using that identifier over network170.

Check-in application112of remote user device110may utilize communication module118of that device to pass user information for remote user104to service provider server140, including user assistance preferences, user calendar information, user relationship information, user email information, user social media information, identifiers of user104and/or user device110, a request for assistance, a request for a type of assistance, product preference information, service preference information, etc. Once check-in application112of remote user device110has completed a remote check-in with service provider server140, remote user104may be recognized or identified by service provider server140and local user102may receive targeted assistance, product offers and/or service offers for remote user104.

Service application120may be used, for example, to provide a convenient interface to permit users102and/or104to receive, request, and/or view targeted products and/or services. Service application120may correspond to an application specific to service location130and/or service provider server140, such as an application downloadable over network170and/or through wireless beacon132. However, in other embodiments, service application120may correspond more generally to any application configured to receive targeted assistance, product offers, and/or service offers, including a browser application.

Service application120may be configured to receive assistance, products offers, and/or service offers for service location130. Service application120may also be configured to display the information. For example, service application120may display general information for service location130, such as a map, merchant store offerings, remote-user-specific product or service locations, information desk locations, sales/coupons/rebates, or other general information. Additionally, service application120may use a location device and/or application of local user device180, such as a GPS device and application, to locate local user102at a specific location at service location130, and transmit the specific location to service provider server140for use in providing the targeted assistance, product offers and/or service offers to remote user104and/or to local user102for remote user104. In other embodiments, the location of local user102may be determined based on a communication between local user device180with wireless beacon132. In various embodiments, check-in application112and service application120of each user device may be incorporated in the same application so as to provide their respective features in one convenient application interface.

Each user device may include other applications114as may be desired in particular embodiments to provide features to that user device. For example, other applications114may include security applications for implementing client-side security features, programmatic client applications for interfacing with appropriate application programming interfaces (APIs) over network170, or other types of applications. Other applications114may also include email, texting, voice and IM applications that allow a user to send and receive emails, calls, texts, and other notifications through network170. In various embodiments, other applications114may include financial applications, such as banking, online payments, money transfer, or other applications. Other applications114may include browser and/or mapping applications where the functions are not provided by check-in application112and/or service application120. Other applications114may contain software programs, executable by a processor, including a graphical user interface (GUI) configured to provide an interface to the user.

Each user device may further include memory such as database116which may include, for example, identifiers such as operating system registry entries, cookies associated with check-in application112, service application120, and/or other applications114, identifiers associated with hardware, or other appropriate identifiers, such as identifiers used for payment/user/device authentication or identification of that user device and/or the associated user. Database116may include user device tokens and/or encryption keys, including a public key of service location130and/or service provider server140for wireless beacon132. Database116may include identifying information for tokens enabling check-in application112to identify wireless beacon132when receiving a corresponding token. In one embodiment, identifiers in database116may be used to associate a user device with a particular account maintained by the account provider. Database116may further include online account access information.

Each user device may include a communication module118adapted to communicate with wireless beacon132, service provider server140, and/or payment provider server160. In various embodiments, communication module118may include 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, infrared, Bluetooth, and near field communication devices. Communication module118may, in some circumstances, communicate directly with wireless beacon132without network170using short range wireless communications.

Service location130may correspond to a physical location visited by local user102that offers products and/or services such as targeted assistance, targeted products, and/or targets services for remote user104. For example, service location130may correspond to a merchant storefront, a shopping mall, an amusement park, a concert hall, a sports arena, a museum, a hospital, an airport, a train station, or other location that offers products and/or services. Service location130may include a plurality of locations within service location130, where each location includes a wireless beacon. For example, a location in service location130may correspond to an area of a store offering video games for sale. Wireless beacon132may check-in local user102and/or remote user104when user device180is in proximity to wireless beacon132. Thus, wireless beacon132may enable service provider server140to associate local user102and/or remote user104with service location130and/or a location within service location130. Service location130may be one of a plurality of locations corresponding to service provider server140. However, in other embodiments, service provider server140may correspond only to service location130. Service location130may include a wireless beacon132and a communication module134. In other embodiments, service location130may include additional or different software and devices as required.

Wireless beacon132may be maintained and/or operated, for example, by service location130and/or service provider server140. Wireless beacon132may be implemented using any appropriate hardware and software configured for wireless communication with local user device180. For example, in one embodiment, wireless beacon132may be implemented as a dongle device including a hardware processor and a communication module, for example, connected to device at service location130. Thus, wireless beacon132may be implemented as a device incorporated within or attached to a personal computer (PC), a smart phone, personal digital assistant (PDA), laptop computer, and/or other types of computing devices capable of transmitting and/or receiving data, such as an IPAD® from APPLE®. Wireless beacon132may also act as a stand-alone device including a processor, communication module, and/or network interface component configured to communicate with local user device180and/or service provider server140. Although a single beacon is described, a plurality of wireless beacons may be utilized and be location specific within service location130.

Wireless beacon132may include processes, procedures, and/or applications executable by a hardware processor, for example, a software program, configured to interact with local user device180. Wireless beacon132may include applications for transmitting requests to establish a connection between a user device and wireless beacon132. Thus, wireless beacon132may utilize a low energy short range wireless communication of wireless beacon132to transmit requests to establish a connection with local user device180, including an identifier such as a Universally Unique Identifier (UUID). If local user device180receives a request to establish the connection with wireless beacon132and responds with a user device identifier (potentially including the UUID and other information to effectuate a check-in such as a proxy check-in of local user device180), wireless beacon132may ramp up in power and create a connection between local user device180and wireless beacon132.

Wireless beacon132may transmit the request to establish the connection with wireless beacon132as a short range communication (e.g. a BLE protocol communication) including a “wake up” process for check-in application112of local user device180and/or a token for wireless beacon132or service provider server140. In other embodiments, the request and/or connection may utilize near field communication, radio communication, infrared communication, or Bluetooth communication. The request may be specific to local user device180by including information that is specific to the corresponding user102, such as a name, identifier, or user device identifier. The information specific to user102may be determined from a user account of local user102or other information previously provided to service provider server140. Thus, in certain embodiments, only a specific local user device180will pick up and authenticate the request.

After wireless beacon132receives a user device identifier from local user device180, wireless beacon132may determine that local user102is at or in proximity to service location130. Wireless beacon132may pass the user device identifier to service provider server140and/or payment provider server160to complete the proxy check-in process and associate user102with service location130. As shown inFIG. 1, wireless beacon132utilizes communication module134to pass the information to service provider server140. However, in other embodiments, wireless beacon132may utilize a network connection of wireless beacon132through a communication module of wireless beacon132. Additionally, wireless beacon132may keep a communication channel open between user device180and service provider server140for passing additional information, such as assistance requests, assistance preferences, product and/or service offers, transaction information, payment information, and/or identification information.

In various embodiments, service location130includes at least one communication module134adapted to communicate with local user device180, remote user device110, service provider server140, and/or payment provider server160. Communication module134may include 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, infrared, Bluetooth, and near field communication devices. Communication module134may communicate directly with user device110without network170using short range wireless communications.

Service provider server140may be maintained and/or operated, for example, by one or a plurality of service locations. Generally, service provider server140may be maintained by anyone or any entity that establishes and/or maintains a location with services offered to users. In this regard, service provider server140may include one or more applications, which may be configured to interact with user device110and180and/or service location130to complete check-in processes for user device110and user device180. Although only one service provider server is shown, a plurality of service provider servers may be utilized. In various embodiments, the check-in and assistance features of service provider server140may also be offered by payment provider server160. Thus, all or part of the described features and processes of service provider server140may be incorporated within payment provider server160.

Service provider server140may include a check-in application142, a service provider application150, a database146, and a network interface component148. Check-in application142and service provider application150may correspond to processes, procedures, and/or applications executable by a hardware processor, for example, a software program. In other embodiments, service provider server140may include additional or different software as required.

Check-in application142may correspond to processes to complete a check-in with remote user device110and/or local user device180. Thus, check-in application142may correspond to the server side application of service provider server140configured to transmit and/or receive check-in requests from user devices110and/or180and complete the check-in requests. A check-in request may include log-in information for a user account in database146. Check-in may be completed by verifying the account information. However, in embodiments where a user account has not been previously established and/or service provider server140does not offer user account services, check-in application142may receive other information for identifying users102and/or104, such as user names/identifiers, user device identifiers, an identifier for an account with another server (e.g., a payment account/payment account identifier with payment provider server160), or other information.

Once proxy check-in is completed between local user102and service provider server140and/or remote check-in is completed between remote user104and service provider server140, check-in application142may be utilized to associate local user102and/or remote user104with a location corresponding to wireless beacon132, such as service location130generally, or a sub-location of service location130corresponding to wireless beacon132. Additionally, check-in application142may check local user102and/or remote user104out of the location when local user102leaves the proximity of wireless beacon132. For example, when local user102leaves the proximity of wireless beacon132so that local user device180is no longer in communication with wireless beacon132, local user102and/or remote user104may be checked-out of the location.

Service provider server140may further include service provider application150configured to receive information corresponding to remote user104and/or local user102checked-in to wireless beacon132through service location130and provide targeted assistance, products and/or services to remote user104and/or to local user102on behalf of remote user104. In this regard, service provider application150may receive remote check-in information such as a remote user identifier and/or other information for remote user104. Utilizing this information, service provider application150may determine and provide product and/or service offers to for remote user104to local user102.

The information may also correspond to one or more user accounts of users102and/or104with another server, such as payment provider server160. In such embodiments, service provider server140may determine a user history or other user information for local user102and/or remote user104based on information received from payment provider server160. Payment provider server160may provide information about previous purchases/visits by local user102and/or remote user104at the same or similar locations to service location130or may provide other information.

In various embodiments, service provider server140may include other applications144as may be desired in particular embodiments to provide features to service provider server140. For example, other applications144may include security applications for implementing server-side security features, programmatic server applications for interfacing with appropriate application programming interfaces (APIs) over network170, or other types of applications. Other applications144may contain software programs, executable by a processor, including a graphical user interface (GUI), configured to provide an interface to a user.

Service provider server140may include a database146which may include, for example, identifiers such as operating system registry entries, cookies associated with check-in application142and/or service provider application150, identifiers associated with hardware of service provider server140, or other appropriate identifiers, such as identifiers used for payment/user/device authentication or identification. Database146may include identifiers and/or user accounts of user102and/or user104, which may comprise an identifier for user102, user104, user device110, and/or user device180. In various embodiments, identifiers in database146may be used by a payment or credit provider, such as payment provider server160, to associate user102and/or user104with a particular account maintained by payment provider server160. For example, an identifier for a payment account with payment provider server160may be stored with a user account, an identifier of remote user104, and/or an identifier of local user102in database146. In other embodiments, a user account stored in database146may include a shared identifier with the payment account with payment provider server160.

In various embodiments, service provider server140includes at least one network interface component148adapted to communicate with user devices110, service location130, and/or payment provider server160over network170. In various embodiments, network interface component148may include 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, infrared, Bluetooth, and near field communication devices

Payment provider server160may be maintained, for example, by an online payment service provider, which may provide user account and payment services on behalf of user102, user104, and/or other users. In this regard, payment provider server160may include one or more processing applications, which may provide payment for items using a user account with payment provider server160. In one example, payment provider server160may be provided by PAYPAL®, Inc. of San Jose, Calif., USA. However, in other embodiments, payment provider server160may be maintained by or include a merchant, financial services provider, and/or other service provider, which may provide user account services to user102and/or user104. Although payment provider server160is described as separate from service provider server140, it is understood that payment provider server160may include services offered by service provider server140and vice versa.

Payment provider server160may include a transaction processing application162, a database of user accounts164, and a network interface component166. Transaction processing application162may correspond to processes, procedures, and/or applications executable by a hardware processor, for example, a software program. In other embodiments, payment provider server160may include additional or different software as required.

Transaction processing application162may be configured to receive information from one or more of user device110, user device180, and/or service provider server140for processing and completion of financial transactions such as payment transactions. Transaction processing application162may include one or more applications to process financial transactions between user device110, user device180, and/or service provider server140. Financial transactions may include transactions that utilize information such as financial information corresponding to user debit card and/or credit card information, checking account information, a user account (e.g., payment account with payment provider server160), or other payment information. Transaction processing application162may complete a financial transaction for a purchase request by providing payment to service provider server140or to an account associated with service provider server140and/or service location130. In various embodiments, transaction processing application162may provide transaction histories, including receipts, to user devices110and/or180in order to provide proof of purchase for an item and/or service. Transaction processing application162may also provide the transaction histories to service location130for use in pick-up/delivery of the item and/or service.

Additionally, payment provider server160may include user accounts164. As previously discussed, local user102and/or remote user104may establish one or more user accounts with payment provider server160. User accounts164may include user information, such as a name, an address, a birthdate, payment and/or funding information, additional user financial information, proxy user information such as registered proxy information, and/or other desired user data. Information in user account164may be utilized by service provider server140to determine and provide targeted assistance, product offers, and/or services offers to local user102on behalf of remote user104.

In various embodiments, payment provider server160may include at least one network interface component166adapted to communicate with user device110, service location130, and/or service provider server140over network170. In various embodiments, network interface component166may 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.

Network170may be implemented as a single network or a combination of multiple networks. For example, in various embodiments, network170may include the Internet or one or more intranets, landline networks, wireless networks, and/or other appropriate types of networks. Thus, network170may correspond to small scale communication networks, such as a private or local area network, or a larger scale network, such as a wide area network or the Internet, accessible by the various components of system100.

When local user102arrives at service location130, wireless beacon132may detect the presence of local user device180and, responsive to the detection, local user102may be provided with various options for check-in such a proxy check-in to service location130.FIG. 2shows an example of check-in options that may be provided to a user such as a local user at a service location using a local user device of the local user.

As shown inFIG. 2, check-in options such as local user check-in option202and proxy check-in options206may be provided to a user on a user device such as local user device180. Check-in options202and206may be provided in a window such as check-in window200on a display of local user device180. For example, window200may be a pop-up window generated by an application such as check-in application112of user device180(seeFIG. 1). However, this is merely illustrative. If desired, window200may be a portion of a service provider website that the local user has logged into or may be otherwise generated on a display of local user device180as would be understood by one skilled in the art.

Local user check-in option202may be an option for the local user to request their own check-in to the location. Local user check-in option202may include a check-in icon such as a virtual CHECK IN button204. The local user may request check-in by selecting the CHECK IN button204(e.g., using a finger or other instrument on a touch screen or using a mouse-controlled or touchpad-controlled cursor). CHECK IN button204may cause a service provider server, a payment provider server, or an application running on local user device180to check the local user in to the location.

Proxy check-in options206may include one or more options for proxy check in for one or more associated remote users. In the example ofFIG. 2, proxy check-in options206include text (e.g., “PROXY CHECK IN FOR:”) prompting the local user to determine whether they would like to check in as a proxy user for one or more remote users such as a remote user USER A, a remote user USER B, or other remote users. Proxy check-in options206may include a virtual proxy check in button208corresponding to each remote user for which the proxy user can check in. Remote users such as USER A and/or USER B may be users that have previously designated the user of device180as a proxy shopper or may be suggested remote users by a service provider server or a payment provider server (as examples). The local user of local user device180may select one or more of buttons208(e.g., using a finger or other instrument on a touch screen or using a mouse-controlled or touchpad-controlled cursor). Selecting, for example, a button208associated with USER A may forward a check-in alert to that user (e.g., directly from the local user or by requesting that a service provider server or a payment provider server forward the check-in alert).

Responsive to receiving a check-in forward request when the local user selects a button208, a service provider server or payment provider server may provide the associated remote user with options for remote check-in.FIG. 3shows an example of check-in options that may be provided to a user such as a remote user using a remote user device of the remote user.

As shown inFIG. 3, a remote user may be provided with a remote check-in alert that includes, for example, a proxy user location alert and one or more remote check-in options on a device such as remote user device110. Proxy user location alert304and check-in option306may be provided in a window such as check-in window302on a display of remote user device110. For example, window302may be a pop-up window generated by an application such as check-in application112of user device110(seeFIG. 1). However, this is merely illustrative. If desired, window302may be a portion of a service provider website that the remote user has logged into or may be otherwise generated on a display of remote user device110as would be understood by one skilled in the art.

Proxy user location alert304may include an alert informing the remote user that a proxy user such as a proxy shopper is at a service location such as SERVICE LOCATION A (e.g., a merchant location). The alert may be a visual, audio, mechanical, or other alert and may include for example, text such as “YOUR PROXY SHOPPER IS AT SERVICE LOCATION A.”

Remote check-in option306may include text (e.g., “WOULD YOU LIKE TO:”) prompting the user of remote user device110to determine whether they would like to remotely check in using, for example, a check-in icon such as a virtual REMOTE CHECK IN button308. Remote check-in may be requested by the remote user by selecting the REMOTE CHECK IN button308(e.g., using a finger or other instrument on a touch screen or using a mouse-controlled or touchpad-controlled cursor). REMOTE CHECK IN button204may cause service provider server, payment provider server, or an application running on remote user device110to remotely check the remote user in to the location and/or to proxy check-in the local user to the location.

FIG. 4is a flowchart of an exemplary process to provide remote user check-in and associated proxy shopping operations for a remote user by a system of the type described herein, according to an embodiment.

At step400, a local user may be detected at a location (e.g., a service center location). The local user may be detected based on communication between a local user device and a wireless beacon at the location or based on check-in information transmitted to a service provider server or payment provider server from the local user device when the local user is located at the location. The local user device may be in communication with the beacon when the local user device is in proximity to the beacon. The local user device and the beacon may be in communication using one of near field communication, radio communication, infrared communication, Bluetooth communication, and Bluetooth low energy communication.

At step402, a check-in alert may be provided to the detected local user to check in to the location. The check-in alert may include a local user check-in option and/or one or more proxy check-in options to check in as a proxy user for a remote user. The check-in alert may be generated and provided to the detected location user in response to detecting the local user.

At step404, a check-in forward request may be receive from the local user to forward a check-in alert to a remote user. The check-in forward request may be received when the local user selects a proxy check-in option using the local user device.

At step406, a remote check-in alert may be provided to the remote user. The remote check-in alert may be provided to the remote user directly from the local user device or from a service provider server or a payment provider server responsive to receiving the check-in forward request from the local user.

At step408, a remote check-in request may be received from the remote user. The remote check-in request may be a request from the remote user to remotely check in to the location and may be received when the remote user selects a remote check-in option using the remote user device.

At step410, proxy check-in of the local user may be completed. Proxy check-in of the local user may include checking the local user into the location as a proxy user such as a proxy shopper for the remote user. Proxy check-in of the local user may include providing information, product offers, service offers or other assistance to the local user on behalf of the remote user (e.g., offering a product for the remote user to the local user).

At step412, remote check-in of the remote user may be completed. Remote check-in of the remote user may include checking the remote user into the location even though the remote user is located away from the location. Remote check-in of the remote user may include providing information about the location, available product information, product offers, service offers or other assistance to the remote user for purchase by the local user on behalf of the remote user using a payment account of the remote user. In various embodiments, a remotely checked-in user may actively participate in a shopping process by communication with the local user. However, this is merely illustrative. In some embodiments, the proxy shopper may have the ability to shop on behalf of the remote user without active input from the remote user.

At step414, a proxy purchase request may be received from the local user for the remote user. For example, the local user may have identified a product that the remote user desires (e.g., based on direct communication with the remote user before or after the check-in operations, based on a list of the remote user, based on recommendations for the remote user, and/or based on personal knowledge of the local user about the remote user). The proxy purchase request may be received when, for example, the local user attempts to pay for a product or a service at the location.

At step416, local user identification data such as a photograph or other identifying information of the local user may be provided (e.g., by a service provider server or a payment provider server) to the service location for verification by the service location that the proxy user is authorized to make purchases on behalf of the remote user.

At step418, identity confirmation of the local user may be received (e.g., from the service location when the service location verifies the identity of the local user using the provided local user identification data).

At step420, funds may be transferred (e.g., by a payment provider server) from a remote user account of the remote user to a location account (e.g., a service provider account such as a merchant account) associated with the location. In this way, a system may facilitate a purchase of a product or service by the local user for the remote user.

One or more of the processes and steps described in connection withFIG. 4may be performed in any suitable order, omitted, and/or repeated any suitable number of times for facilitating remote check-in and associated proxy shopping processes.

Computer system500includes a bus502or other communication mechanism for communicating information data, signals, and information between various components of computer system500. Components include an input/output (I/O) component504that processes a user action, such as selecting keys from a keypad/keyboard, selecting one or more buttons, image, or links, and/or moving one or more images, etc., and sends a corresponding signal to bus502. I/O component504may also include an output component, such as a display511and a cursor control513(such as a keyboard, keypad, mouse, etc.). An optional audio input/output component505may also be included to allow a user to use voice for inputting information by converting audio signals. Audio I/O component505may allow the user to hear audio. A transceiver or network interface506transmits and receives signals between computer system500and other devices, such as another user device, a merchant device, or a service provider server via network170. In one embodiment, the transmission is wireless, although other transmission mediums and methods may also be suitable. One or more processors512, which can be a micro-controller, digital signal processor (DSP), or other processing component, processes these various signals, such as for display on computer system500or transmission to other devices via a communication link518. Processor(s)512may also control transmission of information, such as cookies or IP addresses, to other devices.