Why a MetaMask Card Payment Gets Declined

A declined payment on a self-custody card has more possible causes than on a bank card, but they fall into two groups and one of them is boring.

Wallet-side causes

Start here, because these are the ones you can fix. The spending cap may be exhausted or set lower than the purchase. The token with the balance may not be the token you enabled. Your balance may be on a different network than the one the card draws from. Or the wallet may have no gas, which does not block a purchase directly but blocks every fix you might attempt.

Identity verification lapsing is also common across card programmes generally, and it produces declines that look mysterious until you check the account status.

Merchant-side causes

These you cannot fix, only work around. Some merchants block cards issued through crypto programmes by their card range. Some categories — airlines, subscriptions, car rental, gambling — carry stricter fraud rules regardless of issuer. And fraud systems react to novelty: a first purchase in a new country, an unusually large amount, or several rapid attempts.

Recurring subscriptions deserve a separate mention. A card that draws from a spending cap can fail a renewal silently months later, when the cap has run down and nobody was watching.

The order to check

Look at the spending cap first, then the enabled token and its network, then the account status, then the gas balance. That covers most of it in under a minute.

If all four are fine, the problem is on the merchant's side. Retrying through Apple Pay rather than the card number sometimes routes around it, and a slightly smaller amount sometimes clears fraud thresholds. If neither works, use another card and try the merchant again another day.

Card details are tracked on the MetaMask Card page.