Abstract: An online concierge system facilitates a checkout bypass process for shoppers. The online concierge system detects when the shopper procuring an order for a customer is ready to exit the warehouse after obtaining the items in the order. The online concierge system applies a trained risk model to automatically determining whether to initiate an audit of the shopper. Responsive to determining to initiate the audit, the online concierge system invokes an auditing process. The online concierge system receives, via an auditor application, verification of the order from the auditor mobile application. Responsive to the verification, the online concierge system completes the order and generates routing instructions via the shopper mobile application for facilitating delivery by the shopper to the customer.

Abstract: An online concierge system requests an image of a receipt of an order from a picker after the picker fulfills the order at a store. The online concierge system performs image processing on the image of the receipt and uses machine learning and optical character recognition to determine a tax amount paid for the order and a confidence score associated with the tax amount. The online concierge system may use the machine learning model for segmenting extracted text in the image of the receipt into tokens. The online concierge system may then determine at least one token associated with a tax item and the tax amount associated with the tax item. The online concierge system communicates the tax amount to the store for reimbursement based on the tax amount and the confidence score.

Abstract: An integration platform provides a third party channel products from a merchant, so that the third party channel may cause an opportunity to be presented to a user to purchase one of the products. In response to an indication of a user purchase, the integration platform transmits a purchase request to the electronic commerce platform to create an order for the purchase. The integration platform may create a payment for the purchase with the merchant's payment processor and transmit the payment to the payment processor, update the order with the merchant's electronic commerce platform with the payment information, update the status of the order to shipped, and capture payment information by communicating with the payment provider. The merchant's electronic commerce platform may then update the order with the integration platform, which may notify the third party channel of the update so that update may be communicated to the user.

Abstract: An integration platform provides a third party channel products from a merchant, so that the third party channel may cause an opportunity to be presented to a user to purchase one of the products. In response to an indication of a user purchase, the integration platform transmits a purchase request to the electronic commerce platform to create an order for the purchase. The integration platform may create a payment for the purchase with the merchant's payment processor and transmit the payment to the payment processor, update the order with the merchant's electronic commerce platform with the payment information, update the status of the order to shipped, and capture payment information by communicating with the payment provider. The merchant's electronic commerce platform may then update the order with the integration platform, which may notify the third party channel of the update so that update may be communicated to the user.

Abstract: Systems and methods providing, by a third party, input form fields for sensitive data on a web page provided by an organization. A user may request a web page from an organization, such as a merchant's checkout web page, that requires entry of sensitive data. The merchant's checkout web page may include reference to a script file that provides hosted sensitive data form fields. In response to rendering the merchant web page in a web browser of the user, a request to provide sensitive data form fields on the merchant web page may be received. The request may include a call to a function in a scripting file provided by the third party, and the provided file may cause one or more inline frames to be rendered in the web browser, each inline frame including a sensitive data form field. Data entered by the user in the sensitive data form fields may be received by a third party payment processor device.

Abstract: Techniques for providing access to scope-delimited sensitive data are disclosed. A user provides sensitive data to a first party associated with a payment service provider. The first party stores the sensitive data with the payment service provider, and the payment service provider provides the first party merchant with an encoding of the payment data. The first party provides a purchasing opportunity to the user for goods offered by a third party also associated with the payment service provider. The first party transmits a sensitive data grant request to the payment service provider. In response, the payment service provides a scope-delimited encoding of the sensitive data. The first party provides the scope-delimited encoding of the payment data to the third party. The third party merchant creates a transaction using the scope-delimited encoding of the sensitive data. At some time later, access to the scope-delimited encoding of the sensitive data is revoked.

Abstract: Techniques for providing access to scope-delimited sensitive data are disclosed. A user provides sensitive data to a first party associated with a payment service provider. The first party stores the sensitive data with the payment service provider, and the payment service provider provides the first party merchant with an encoding of the payment data. The first party provides a purchasing opportunity to the user for goods offered by a third party also associated with the payment service provider. The first party transmits a sensitive data grant request to the payment service provider. In response, the payment service provides a scope-delimited encoding of the sensitive data. The first party provides the scope-delimited encoding of the payment data to the third party. The third party merchant creates a transaction using the scope-delimited encoding of the sensitive data. At some time later, access to the scope-delimited encoding of the sensitive data is revoked.

Abstract: An integration platform provides a third party channel products from a merchant, so that the third party channel may cause an opportunity to be presented to a user to purchase one of the products. In response to an indication of a user purchase, the integration platform transmits a purchase request to the electronic commerce platform to create an order for the purchase. The integration platform may create a payment for the purchase with the merchant's payment processor and transmit the payment to the payment processor, update the order with the merchant's electronic commerce platform with the payment information, update the status of the order to shipped, and capture payment information by communicating with the payment provider. The merchant's electronic commerce platform may then update the order with the integration platform, which may notify the third party channel of the update so that update may be communicated to the user.

Abstract: An integration platform provides a third party channel products from a merchant, so that the third party channel may cause an opportunity to be presented to a user to purchase one of the products. In response to an indication of a user purchase, the integration platform transmits a purchase request to the electronic commerce platform to create an order for the purchase. The integration platform may create a payment for the purchase with the merchant's payment processor and transmit the payment to the payment processor, update the order with the merchant's electronic commerce platform with the payment information, update the status of the order to shipped, and capture payment information by communicating with the payment provider. The merchant's electronic commerce platform may then update the order with the integration platform, which may notify the third party channel of the update so that update may be communicated to the user.

Abstract: Systems and methods providing, by a third party, input form fields for sensitive data on a web page provided by an organization. A user may request a web page from an organization, such as a merchant's checkout web page, that requires entry of sensitive data. The merchant's checkout web page may include reference to a script file that provides hosted sensitive data form fields. In response to rendering the merchant web page in a web browser of the user, a request to provide sensitive data form fields on the merchant web page may be received. The request may include a call to a function in a scripting file provided by the third party, and the provided file may cause one or more inline frames to be rendered in the web browser, each inline frame including a sensitive data form field. Data entered by the user in the sensitive data form fields may be received by a third party payment processor device.

Abstract: Techniques for providing access to scope-delimited sensitive data are disclosed. A user provides sensitive data to a first party associated with a payment service provider. The first party stores the sensitive data with the payment service provider, and the payment service provider provides the first party merchant with an encoding of the payment data. The first party provides a purchasing opportunity to the user for goods offered by a third party also associated with the payment service provider. The first party transmits a sensitive data grant request to the payment service provider. In response, the payment service provides a scope-delimited encoding of the sensitive data. The first party provides the scope-delimited encoding of the payment data to the third party. The third party merchant creates a transaction using the scope-delimited encoding of the sensitive data. At some time later, access to the scope-delimited encoding of the sensitive data is revoked.

Abstract: Systems and methods providing, by a third party, input form fields for sensitive data on a web page provided by an organization. A user may request a web page from an organization, such as a merchant's checkout web page, that requires entry of sensitive data. The merchant's checkout web page may include reference to a script file that provides hosted sensitive data form fields. In response to rendering the merchant web page in a web browser of the user, a request to provide sensitive data form fields on the merchant web page may be received. The request may include a call to a function in a scripting file provided by the third party, and the provided file may cause one or more inline frames to be rendered in the web browser, each inline frame including a sensitive data form field. Data entered by the user in the sensitive data form fields may be received by a third party payment processor device.

Abstract: An integration platform provides a third party channel products from a merchant, so that the third party channel may cause an opportunity to be presented to a user to purchase one of the products. In response to an indication of a user purchase, the integration platform transmits a purchase request to the electronic commerce platform to create an order for the purchase. The integration platform may create a payment for the purchase with the merchant's payment processor and transmit the payment to the payment processor, update the order with the merchant's electronic commerce platform with the payment information, update the status of the order to shipped, and capture payment information by communicating with the payment provider. The merchant's electronic commerce platform may then update the order with the integration platform, which may notify the third party channel of the update so that update may be communicated to the user.

Abstract: Systems and methods providing, by a third party, input form fields for sensitive data on a web page provided by an organization. A user may request a web page from an organization, such as a merchant's checkout web page, that requires entry of sensitive data. The merchant's checkout web page may include reference to a script file that provides hosted sensitive data form fields. In response to rendering the merchant web page in a web browser of the user, a request to provide sensitive data form fields on the merchant web page may be received. The request may include a call to a function in a scripting file provided by the third party, and the provided file may cause one or more inline frames to be rendered in the web browser, each inline frame including a sensitive data form field. Data entered by the user in the sensitive data form fields may be received by a third party payment processor device.