- From: Andrew Paliga <notifications@github.com>
- Date: Mon, 25 Apr 2016 07:48:23 -0700
- To: w3c/browser-payment-api <browser-payment-api@noreply.github.com>
- Cc:
- Message-ID: <w3c/browser-payment-api/issues/155/214369842@github.com>
> Andrew, can you say more about how useful you think the "suggested app" featured would be to merchants? - It can be beneficial for a payee to showcase the payment methods they support to increase conversation rates. Take financing options like [Klarna](https://www.klarna.com/international) and [Affirm](https://www.affirm.com/) for example. They support "pay later" or "pay in instillments" functionality. These are payment options you'd always want to suggest or offer as options in your checkout as a merchant. It's easy to signup during checkout with the options. - Same goes for digital wallets like such as [Mollie](https://www.mollie.com/en/) or or [MOLPay](http://www.molpay.com/v3/). They support a [slew of payment types](https://www.mollie.com/en/pricing). Always suggesting Mollie as a payment app in checkout would ensure user's are aware that they have many options to pay with. - Ditto for cash-on-delivery methods that are very popular in South America and India. [ComproPago](https://www.compropago.com/) comes to mind. In general I think it's best to assume that _no prior configuration_ will be done by the end user. Many countries have much lower cc penetration rates (<20%) than we see in North America. Most online payments are done via bank transfer or digitals wallets. Ensuring the buyer is aware of these payment options at all times would be of benefit to the merchant. > I would prefer the choice of alwaysShow to be left to the user agent. It would be difficult for the user-agent to manage payment app recommendations as these are very country specific. Almost every country in Europe has a different primary payment provider. Ie. ideal in Netherlands, Bancontact in Belgium etc. I think it should be up to the Payee to determine which payment apps are showcased. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/browser-payment-api/issues/155#issuecomment-214369842
Received on Monday, 25 April 2016 14:49:36 UTC