Abstract: Embodiments provide techniques, including systems and methods, for determining matches of requestors and providers based on a dynamic provider eligibility model. For example, a request matching model uses an estimated arrival time for a requestor and estimated travel times for available providers to a pickup location to determine eligible providers for matching to a ride request. The matching model determines those providers that are far enough away from the request location to allow the requestor time to arrive at the pickup location without matching providers that are too far away, causing delay for the requestor and lowering the efficiency of the system by taking provider system resources from other service areas and increasing provider downtime upon matching. Additionally, embodiments provide more efficient matching processing leading to fewer canceled matched requests, fewer requests for a successful match, and fewer system resources necessary to meet requestor demand.

Abstract: A system for casual driver ride sharing includes an interface and processor. The interface is to receive a request for a ride from a user, wherein the request includes GPS information for the user. The processor is to determine compatibility between the typical route information and the request for the ride; determine a ranked list based at least in part on the compatibility; and provide a ride offer to a driver of the one or more casual drivers based at least in part on the ranked list.

Abstract: Embodiments provide techniques, including systems and methods, for determining matches of requestors and providers based on a dynamic provider eligibility model. For example, a request matching model uses an estimated arrival time for a requestor and estimated travel times for available providers to a pickup location to determine eligible providers for matching to a ride request. The matching model determines those providers that are far enough away from the request location to allow the requestor time to arrive at the pickup location without matching providers that are too far away, causing delay for the requestor and lowering the efficiency of the system by taking provider system resources from other service areas and increasing provider downtime upon matching. Additionally, embodiments provide more efficient matching processing leading to fewer canceled matched requests, fewer requests for a successful match, and fewer system resources necessary to meet requestor demand.

Abstract: A system for casual driver ride sharing includes an interface and processor. The interface is to receive a request for a ride from a user, wherein the request includes GPS information for the user. The processor is to determine compatibility between the typical route information and the request for the ride; determine a ranked list based at least in part on the compatibility; and provide a ride offer to a driver of the one or more casual drivers based at least in part on the ranked list.

Abstract: Embodiments provide techniques, including systems and methods, for determining matches of requestors and providers based on a dynamic provider eligibility model. For example, a request matching model uses an estimated arrival time for a requestor and estimated travel times for available providers to a pickup location to determine eligible providers for matching to a ride request. The matching model determines those providers that are far enough away from the request location to allow the requestor time to arrive at the pickup location without matching providers that are too far away, causing delay for the requestor and lowering the efficiency of the system by taking provider system resources from other service areas and increasing provider downtime upon matching. Additionally, embodiments provide more efficient matching processing leading to fewer canceled matched requests, fewer requests for a successful match, and fewer system resources necessary to meet requestor demand.

Abstract: A system for casual driver ride sharing includes an interface and processor. The interface is to receive a request for a ride from a user, wherein the request includes GPS information for the user. The processor is to determine compatibility between the typical route information and the request for the ride; determine a ranked list based at least in part on the compatibility; and provide a ride offer to a driver of the one or more casual drivers based at least in part on the ranked list.

Abstract: A system for casual driver ride sharing includes an interface and processor. The interface is to receive a request for a ride from a user, wherein the request includes GPS information for the user. The processor is to determine compatibility between the typical route information and the request for the ride; determine a ranked list based at least in part on the compatibility; and provide a ride offer to a driver of the one or more casual drivers based at least in part on the ranked list.

Abstract: Embodiments provide techniques, including systems and methods, for determining matches of requestors and providers based on a dynamic provider eligibility model. For example, a request matching model uses an estimated arrival time for a requestor and estimated travel times for available providers to a pickup location to determine eligible providers for matching to a ride request. The matching model determines those providers that are far enough away from the request location to allow the requestor time to arrive at the pickup location without matching providers that are too far away, causing delay for the requestor and lowering the efficiency of the system by taking provider system resources from other service areas and increasing provider downtime upon matching. Additionally, embodiments provide more efficient matching processing leading to fewer canceled matched requests, fewer requests for a successful match, and fewer system resources necessary to meet requestor demand.

Abstract: Embodiments provide techniques, including systems and methods, for determining matches of requestors and providers based on a dynamic provider eligibility model. For example, a request matching model uses an estimated arrival time for a requestor and estimated travel times for available providers to a pickup location to determine eligible providers for matching to a ride request. The matching model determines those providers that are far enough away from the request location to allow the requestor time to arrive at the pickup location without matching providers that are too far away, causing delay for the requestor and lowering the efficiency of the system by taking provider system resources from other service areas and increasing provider downtime upon matching. Additionally, embodiments provide more efficient matching processing leading to fewer canceled matched requests, fewer requests for a successful match, and fewer system resources necessary to meet requestor demand.

Abstract: Embodiments provide techniques, including systems and methods, for determining matches of requestors and providers based on a dynamic provider eligibility model. For example, a request matching model uses an estimated arrival time for a requestor and estimated travel times for available providers to a pickup location to determine eligible providers for matching to a ride request. The matching model determines those providers that are far enough away from the request location to allow the requestor time to arrive at the pickup location without matching providers that are too far away, causing delay for the requestor and lowering the efficiency of the system by taking provider system resources from other service areas and increasing provider downtime upon matching. Additionally, embodiments provide more efficient matching processing leading to fewer canceled matched requests, fewer requests for a successful match, and fewer system resources necessary to meet requestor demand.

Abstract: A system for casual driver ride sharing includes an interface and processor. The interface is to receive a request for a ride from a user, wherein the request includes GPS information for the user. The processor is to determine compatibility between the typical route information and the request for the ride; determine a ranked list based at least in part on the compatibility; and provide a ride offer to a driver of the one or more casual drivers based at least in part on the ranked list.

Abstract: A system for casual driver ride sharing includes an interface and processor. The interface is to receive a request for a ride from a user, wherein the request includes GPS information for the user. The processor is to determine compatibility between the typical route information and the request for the ride; determine a ranked list based at least in part on the compatibility; and provide a ride offer to a driver of the one or more casual drivers based at least in part on the ranked list.

Abstract: A system for casual driver ride sharing includes an interface and processor. The interface is to receive a request for a ride from a user, wherein the request includes GPS information for the user. The processor is to determine compatibility between the typical route information and the request for the ride; determine a ranked list based at least in part on the compatibility; and provide a ride offer to a driver of the one or more casual drivers based at least in part on the ranked list.

Abstract: Methods, systems, and apparatus, including computer programs encoded on computer storage media, for processing payment events. One of the systems includes one or more processing engines configured to periodically retrieve information from a payment event feed that comprises a list of payment events in an order, and a server configured to perform a sequence of steps for a payment transaction, the sequence of steps including receiving a request for authorization of the payment transaction from a merchant, receiving an indication that the payment transaction has been authorized, and sending authorization to the merchant for the payment transaction without receiving acknowledgment that the one or more transaction processing engines have received the request for authorization, wherein the server is configured to record completion of each step in the sequence of steps as a payment event in the list of payment events to generate the payment event feed.

Abstract: Method, systems, and apparatus for receiving the email message from a sender device; identifying, using data processing apparatus of a payment service system, a sender email address, a service email address, and one or more recipient email addresses from the email message; identifying, for the sender email address, a sender financial account associated with the payment service system and, for each of the one or more recipient email addresses, a respective recipient financial account associated with the payment service system; identifying a payment amount from a subject or body of the email message; submitting a request to transfer, using the payment service system, the payment amount from the respective sender financial account to the respective recipient financial account.

Abstract: Method, systems, and apparatus for receiving the email message from a sender device; identifying, using data processing apparatus of a payment service system, a sender email address, a service email address, and one or more recipient email addresses from the email message; identifying, for the sender email address, a sender financial account associated with the payment service system and, for each of the one or more recipient email addresses, a respective recipient financial account associated with the payment service system; identifying a payment amount from a subject or body of the email message; submitting a request to transfer, using the payment service system, the payment amount from the respective sender financial account to the respective recipient financial account.

Abstract: Method, systems, and apparatus for receiving the email message from a sender device; identifying, using data processing apparatus of a payment service system, a sender email address, a service email address, and one or more recipient email addresses from the email message; identifying, for the sender email address, a sender financial account associated with the payment service system and, for each of the one or more recipient email addresses, a respective recipient financial account associated with the payment service system; identifying a payment amount from a subject or body of the email message; submitting a request to transfer, using the payment service system, the payment amount from the respective sender financial account to the respective recipient financial account.