784769 - [WebPayment] Allow users to select a prefered currency

Status: RESOLVED INCOMPLETE

(Core :: DOM: Device Interfaces, defect)

Description

[Fernando Jiménez Moreno [:ferjm]]

We need to create a setting to let the users select their prefered currency, so it appears as default one when showing the payment request information.

Comment 1

[Jason Smith [:jsmith]]

This sounds important if we're dealing with multiple countries. Is this worth noming to block ship?

Comment 2

[Fernando Jiménez Moreno [:ferjm]]

(In reply to Jason Smith [:jsmith] from comment #1)
> This sounds important if we're dealing with multiple countries. Is this
> worth noming to block ship?

IMHO, this is just a nice to have. It must not block basecamp.
Currently we can just show the first currency or add a 'defaultCurrency' extra parameter in the JWT. The user will see his prefered currency in the payment provider flow.

Comment 3

[Mounir Lamouri (:mounir)]

We shouldn't show another currency if the payment will not be done in that currency. Otherwise, what the user will see will not be what the user will actually pay!

Comment 4

[Fernando Jiménez Moreno [:ferjm]]

(In reply to Mounir Lamouri (:mounir) from comment #3)
> We shouldn't show another currency if the payment will not be done in that
> currency. Otherwise, what the user will see will not be what the user will
> actually pay!

We are returning the full list of prices to content, so we can show the whole list (in a dropdown menu or whatever, it's up to UX to decide how to show it). I am just suggesting that until we have a setting for the prefered one, we can show the first one as default or maybe use the 'defaultCurrency' parameter if available.

Comment 5

[Kumar McMillan [:kumar]]

How is this a relevant client side issue? In the current design, currency selection will be handled by the payment provider https://wiki.mozilla.org/WebAPI/WebPaymentProvider

Comment 6

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

Doesn't it still apply when we have multiple payment providers and so the client displays UI to allow selecting payment provider?

Comment 7

[Jonas Sicking (:sicking) No longer reading bugmail consistently]

This might not be something we worry about for v1 if we only whitelist one payment provider there. But this bug isn't marked as a basecamp blocker...

Comment 8

[Fernando Jiménez Moreno [:ferjm]]

(In reply to Jonas Sicking (:sicking) from comment #6)
> Doesn't it still apply when we have multiple payment providers and so the
> client displays UI to allow selecting payment provider?

Yes, we still need this on the client side. But, indeed, not for v1.

Comment 9

[Jason Smith [:jsmith]]

Removing tracking bug - this isn't a v1 blocker.

Comment 10

[Kumar McMillan [:kumar]]

Ah, I misunderstood this at first. A user preference that the device can "broadcast" to payment providers makes sense. I get it now.

Comment 11

[Kyle Machulis [:qdot] [:kmachulis] (INACTIVE)]

More mass-incompleting of FxOS bugs in the Device Interfaces component.

Please update and let me know if any of these are still valid.