rsolomakhin

Minimal UI Payment Handlers

Objective

Provide a golden path, low friction experience for users that are enrolled with payment handlers that support a minimal UI.

Overview

The following conditions must be satisfied to trigger the flow.

rsolomakhin

More restrictive hasEnrolledInstrument() for autofill data

Motivation

The implementation of hasEnrolledInstrument() in Chrome 78 and earlier is relaxed in terms of checking for autofill data completeness and validity. For example, if a user's only autofill data is a credit card that has a number and a name on card, then hasEnrolledInstrument() will return true for basic-card, even if the merchant specifies requestShipping: true and requestPayerEmail: true. This results in poor user experience, which may deter merchant adoption.

Goal

The goal of the project is to reduce the usage of the unhappy path for autofill data, so that users see the happy path more often. A happy path shold require only a couple of clicks to authorize a transaction.

rsolomakhin

if (!checkoutDetails.finished)
  checkout.continue().then(finishCheckout);
else
  checkout.finish(...);
  

var checkout = new Checkout();
checkout
    .onEvent('shippingOptionChange', recalculateLineItems)

rsolomakhin

xterm*termName: xterm-256color
xterm*locale: true
xterm*metaSendsEscape: true
xterm*faceName: Monospace:size=10:antialias=true