-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable / disable continuous payments #238
Comments
We have been discussing a possible issue: what is the difference or relationship between the functionality of enable/disable continuous payments compared to the functionality of enable/disable WM globally. One of the questions is: does this enable/disable continuous payments apply only the current website or does it apply to any website I visit? (probably not a right/wrong way, just an implementation decision for us to make) Current decision for the alpha release: disable continuous payments will apply to any website that the user visits, and so it does not only apply to the current website. |
Agreed to put this ticket on-hold until we (or Tseli) have a full conversation with Alex about what the distinction is between en/disabling WM globally or the use of continuous payments when the Exceptions List functionality is implemented. |
Issue unblocked by decision agreed with Alex today (14 May):
|
When the extension is connected to a wallet:
A user can enable the extension to make continuous WM payments to any website by setting the toggle like this, this will apply the configured hourly rate of WM payments:
A user can disable the extension from making any continuous WM payments to all WM websites by setting the toggle like this:
The text was updated successfully, but these errors were encountered: