How to create and reload a virtual card with crypto
Create a virtual Visa or Mastercard in uSwap with supported crypto, then return to the same card bridge to add funds to that card later.
The useful distinction is simple: a virtual card is not a disposable crypto checkout receipt. On uSwap, the first completed funding operation creates a card on its own bridge. When you come back to that bridge later and complete another funding operation, the system reloads the same card.
That makes the bridge the place to return to. It connects the card’s balance, history, credentials, and controls rather than treating every crypto deposit as a new card purchase.
Open the card picker → Virtual Cards on uSwap
Before you start
You need to be at least 18 and have a supported crypto funding route available in the app. The card picker can show Visa or Mastercard products when they are available. Product availability, funding assets, limits, and fees are live route facts, so the quote in front of you matters more than a stale screenshot or an old amount.
Choose the card network deliberately. Once a card bridge is set up, its selected card product is fixed. That is what lets the same bridge keep reloading the same card instead of changing its identity on a later deposit.
1. Open Virtual Cards
In the uSwap destination picker, choose Virtual Cards. Select one of the card products currently displayed. You are choosing the destination for the crypto route; the source asset can be selected separately from the assets the app currently supports for that route.
The card screen begins as a funding flow. It is not a place to paste a merchant checkout link or another person’s card information.
2. Choose a card value and read the quote
Set the card value you want to fund, then read the whole quote before sending anything. A card quote can include more than the value you want added to the card:
- the intended card value;
- an applicable card-creation charge for the first funding operation;
- an applicable top-up charge;
- routing or provider pricing; and
- the network cost for the crypto route.
The app presents these as part of the quote because the crypto amount sent and the amount intended for the card are different numbers. They should not be treated as interchangeable.
The route also tells you whether its funding payment is fixed or allows a range. Follow the active route’s amount and timing instructions. A new quote can have different conditions from the one you saw earlier.
3. Confirm eligibility and fund the route
Before the first card is created, uSwap asks you to confirm that you are at least 18. Then send the crypto amount to the route shown by the app.
Funding can move through a few states before the card operation runs: deposit confirmation, conversion where required, and settled credit. The first successful card operation uses that credit to issue the selected card and load its initial value.
If a final settled amount does not cover a locked card value or the product’s current minimum, the flow can need review rather than being silently completed for less. Keep the original bridge available so you can see the actual state.
4. Open the protected card view
When the first funding operation completes, open the card’s settings from the original bridge. This is where the card is managed.
The protected view can show:
- card number, expiry, CVV, and PIN when provided;
- available balance;
- transaction history;
- payment-verification state when a merchant challenge is active; and
- freeze and unfreeze controls.
Those details are deliberately not part of a public bridge view. The interface conceals sensitive credentials again when browser focus or authorization changes, so treat the card view like any other place where payment details are visible.
5. Reload the same card
When you want to add more funds, return to the same bridge and begin another card funding operation. The system recognizes the card already attached to that bridge and creates a reload request for it.
That is the reloadable part: one bridge, one card identity, multiple completed funding operations over time. The new quote is still authoritative for fees, funding limits, and source requirements, so review it again before each deposit.
What stays the same, and what can change
The card product on an existing bridge stays the same. The market around it does not. Funding assets, conversion pricing, network costs, product limits, and route availability can all change between deposits.
If you want a different available card product, use a separate card bridge. If you want to add value to the card you already have, return to its original bridge.
More card guides
- How virtual-card funding fees and settlement work
- Reloadable virtual card vs. gift card
- What to check when a virtual-card payment is declined
The live route is always the source of truth. Start at Virtual Cards on uSwap when you are ready to see the currently available products.
Common questions
No. The first completed funding operation on a card bridge issues the card. Later completed funding operations on that same bridge reload it.
More from the blog
How to protect a virtual card: details, balance, history, and controls
A practical checklist for keeping a uSwap virtual card's credentials private, checking its balance and history, and using its protected controls.
Read
Virtual card payment declined? Check these six things first
A practical order for troubleshooting a declined virtual-card payment: card state, balance, controls, history, verification, and the merchant checkout.
Read
After you buy a gift card with crypto: delivery, redemption, and support
What to check after funding a uSwap gift-card route: route state, the redemption artifact, issuer rules, and the safest way to ask for help.
Read