Adds Wyre Widget

[danjm]

fixes #5260

This PR adds the Wyre widget debit card widget to metamask for use as a crypto onramp.

Some notable aspects to this PR:

• when a signature request is made by the wyre widget, metamask will show a new "Signature Request Modal", this will be layered above the widget

• when we attempt to open the widget from the popup view, the extension is opened in full screen on the new DEPOSIT_ROUTE, which triggers an opening of the widget of the widget

• This PR still needs a QA that goes all the way through wyre onboarding process. The following test data can be used:

101 Mission Street
San Francisco, CA 94105
Test Debit Card number:
Card: 9401113999999995
Exp: 10/2020

• I guess we also need to load the script at run time, instead of copying the script code into our codebase... really I just wish it was an npm module

[whymarrh]

@danjm if we're going to keep the Wyre script, we might be best to move it from ui/lib/wyre.js to ui/vendor/wyre.js as vendor/ is a bit more explicit than lib/. Thoughts?

[metamaskbot]

Builds ready [9409afe]: chrome, firefox, edge, opera

[danjm]

@whymarrh Good suggestion, I will do that, if we decide to keep the code in our codebase

Any thoughts on whether we should? My concern is that if we do we are subject to surprise breaking changes or subject our users to using outdated features/api/UX

I don't really want to load the code from a remote host at runtime either though...

[danjm]

@whymarrh In the latest commit I moved the wyre code to a vendor directory as you suggested.

[metamaskbot]

Builds ready [fa7ee02]: chrome, firefox, edge, opera

[tmashuang]

Couldn't finish the flow, since the phone verification wasn't working.

[metamaskbot]

Builds ready [f57d4a6]: chrome, firefox, edge, opera

[danjm]

Here is a demo video: https://streamable.com/k66vl

[metamaskbot]

Builds ready [4476a17]: chrome, firefox, edge, opera

[bdresser]

Sorry for the delay.

When I got to the end of the flow, I saw this error

I never saw the "connect" screen at the beginning of the flow, I clicked "connect with MetaMask" and was immediately brought to the next step.

After clearing privacy data and trying again, I saw the connect popup and did not see this error on the final screen.

[metamaskbot]

Builds ready [5108750]: chrome, firefox, edge, opera

[kumavis]

@danjm seems this has gone stale -- mostly ready?

[metamaskbot]

Builds ready [d6623a9]

• builds: chrome, firefox, opera, edge
• bundle viz: background, ui, inpage, contentscript, ui-libs, bg-libs, phishing-detect
• dep viz: background
• all artifacts

[metamaskbot]

Builds ready [00db455]

• builds: chrome, firefox, opera, edge
• bundle viz: background, ui, inpage, contentscript, ui-libs, bg-libs, phishing-detect
• dep viz: background
• all artifacts

[metamaskbot]

Builds ready [9142f6c]

• builds: chrome, firefox, opera, edge
• bundle viz: background, ui, inpage, contentscript, ui-libs, bg-libs, phishing-detect
• dep viz: background
• all artifacts

[whymarrh]

LGTM