According to the draft of the w3c standard the canMakePayment method can be used to determinate if the user can perform the checkout with the current PaymentRequest.
For some integration scenarios it would make sense to query upfront if the user is kind of ready to use the payment request api for a simplified checkout. If the user doesn't have e.g. a single address stored in the browser vendors implementation of the address book, the checkout itself could be faster without the payment request api, e.g. due having autocompletion of the user address either via the autofill option or via a google maps auto completion.
According to the draft of the w3c standard the canMakePayment method can be used to determinate if the user can perform the checkout with the current
PaymentRequest
.For some integration scenarios it would make sense to query upfront if the user is kind of ready to use the payment request api for a simplified checkout. If the user doesn't have e.g. a single address stored in the browser vendors implementation of the address book, the checkout itself could be faster without the payment request api, e.g. due having autocompletion of the user address either via the autofill option or via a google maps auto completion.