Popular wallet service MetaMask has partnered with Mastercard to launch MetaMask Card, allowing users to spend cryptocurrency from their MetaMask wallet at any location where Mastercard is accepted.
Available to select users in the UK and EU, the card allows users to spend $USDC, $USDT, $WETH and more directly, without needing to convert to fiat currency.
If the pilot is successful, MetaMask plan to expand the rollout of MetaMask Card to further jurisdictions across the globe.
Source: MetaMask
Everyday Crypto Finance with MetaMask Card
“We are so delighted to partner with web3’s leading wallet, MetaMask, to power the financial revolution by enabling users to be their own bank,” said Simon Jones, Chief Commercial Officer at Baanx.
MetaMask Card integrates seamlessly with Apple Pay and Google Pay, allowing for convenient contactless mobile payments. The card leverages Linea to facilitate fast and secure transactions.
“MetaMask Card gives people more freedom to spend their crypto,” says Lorenzo Santos, Senior Product Manager at Consensys. “MetaMask Card represents a major step to removing the friction that has traditionally existed between the blockchain and real-world commerce. This is a paradigm shift that offers the best of both worlds.”
How do I acquire a MetaMask Card?
The MetaMask Card is initially available to a select group of users in the EU and the UK.
To check if you’re eligible to apply for MetaMask Card, visit your MetaMask Portfolio. A new “Card” tab will appear for particular users, guiding you to set up an account on the Crypto Life platform (by Baanx) which powers MetaMask Card.
If the pilot is successful, MetaMask plans to expand the rollout of MetaMask card to other regions.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
This marker is Chrome Shitiness Mitigation mechanism for Ultrawidify. It turns out that as of 2025-01, Chrome does not correctly respect allowTransparency property on certain iframes, and will force white or black background across the entire element. It is unclear what’s causing the issue — so far, it seems to appear randomly.
