- From: Danyao Wang <notifications@github.com>
- Date: Tue, 14 May 2019 15:46:50 +0000 (UTC)
- To: w3c/payment-handler <payment-handler@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 14 May 2019 15:47:14 UTC
Should we add an "other" category to PaymentItemCategory? @adrianhopebailie mentioned in IRC re: Klarna use case: > The general label for the use cases is 'dynamic credit' which is niot unique to Klarna > MobiCred in South Africa, PayLater in Australia etc all assess credit based on what is being bought > Imprtant use case for economies where credit card penetration is low I understand that the latest proposal is geared to address a different problem, i.e. allow payment handlers to provide a better user experience by more clearly delineate the different types of high level components of the Total. It seems to me that the latest proposal can still support the "dynamic credit" use case if merchant *chooses* to share per-item details with the payment app using the `shareWithPaymentApp` flag and an appropriate `label`. The only hiccup is what PaymentItemCategory would this use? The "other" options would solve this problem. -- 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/payment-handler/issues/91#issuecomment-492295252
Received on Tuesday, 14 May 2019 15:47:14 UTC