When customers click any of the component's buttons, they're redirected to that payment provider's interface. There they designate a shipping and/or billing address, select a payment method and then authorize it. If payment is successfully authorized, customers are sent back to your site, and Digital River adds the customer's payment sources, shipTo, and/or billTo to the checkout-session.
Certain browsers don't support some express payment methods. For example, the wallet component doesn't render Apple Pay in Chrome.
If customers initiate an express checkout, and items in the checkout-session contains physical products, then the customer's shipping method selection is collected within the payment component. As a result, if the transaction involves physical products and you're using the wallet component, your application needs to implement the payment component.