Kazawallet Card Basic: adding it to Apple Pay, step by step

I watched the creator's walkthrough of adding the Kazawallet Card Basic to Apple Pay, published on June 25, 2026, and the step that decides whether it works happens back on the card page, not on the phone. A Details icon there asks for a payment password before it gives up the card number, expiry date and security code. The clip runs a little over two minutes with no narration, just a cursor and a phone screen, and it ends with a UPay Visa card sitting in Apple Wallet.

What the card is

On screen, the platform describes itself as multi-currency, with four figures behind the claim: 100+ payment methods, 100+ supported nations, 15+ cryptocurrencies and 20+ international currencies. Those are marketing numbers until someone tests them in one country with one currency, and I would want to see a fee page and a transaction history before taking them seriously.

The figures shown at the start of the recording:

The card itself is virtual. There is no plastic, only a panel on the website with a balance and a status. When the recording was made, that panel showed a card balance of $0.00 USD and a status of Active. An empty card can be added to Apple Wallet and Wallet will accept it, but a tap in a shop needs money behind it.

The card that lands in Wallet is labelled UPay Visa. Visa tells you where it can be spent, since most card terminals and online checkouts take it. UPay is the name the wallet attaches to the card, which points to the issuer or programme manager behind the brand. That two-name arrangement matters later, when something goes wrong and you need to know who is holding the money.

Crypto cards in general work like this: a platform holds a balance for you, issues a card on a traditional card network, and converts your balance into the currency the merchant wants at the moment of the sale. You get the convenience of tapping a phone; the platform and the issuer get a cut through fees and conversion spreads. The card is the visible part of a stack of arrangements you cannot see.

What you need before you start

• An account on the platform with the card already issued and showing Active.
• Your payment password or Google Authenticator, for the Details pop-up.
• An iPhone with the Wallet app and an Apple Account signed in.
• A phone number or email address that can receive a verification code.
• A phone region set to a country where Apple Pay is supported.

Linking the card to Apple Pay, step by step

These are the taps and clicks, in order.

1. Sign in and open the dashboard.
2. Click the green Go to Card button.
3. Check the card panel: the status should read Active.
4. Open the Wallet app on your iPhone.
5. Tap the plus icon in the top right to open Add to Wallet.
6. Choose Debit or Credit Card.
7. Tap Continue on the information screen.
8. Tap Enter Card Details Manually under the camera frame. A virtual card has no plastic to photograph, so the scanner has nothing to read.
9. Type Kazawallet in the Name field.
10. Go back to the card page, click the Details icon next to the balance and enter your 2FA code to reveal the card number, expiry date and security code.
11. Paste the card number into the phone and tap Continue.
12. Enter the Expiration Date and Security Code from the same window, then tap Continue.
13. Wait while the phone contacts the card issuer.
14. Read the Terms and Conditions, tap Agree, and tap Continue once the screen says your card has been added to Wallet.
15. On the Card Verification screen, choose Text Message and tap Continue. The code that arrives is an email, so check both.
16. Enter the verification code, tap Next, and look for the confirmation that the card is activated and ready for Apple Pay.

The last screen is the one to remember: the card appears in Wallet under the UPay name and the setup is done. Nothing else needs configuring. The work is in having the credentials ready before you start, so you are not jumping between a laptop and a phone with a timer running.

Why the card details sit behind a 2FA code

A card number, an expiry date and a three-digit security code are enough to buy something online. That is why the card page hides them. Clicking Details brings up a box asking for a payment password, and the note beside it says the code can be that password or a code from Google Authenticator. Enter a six-digit code and the credentials appear in a small window.

I prefer this to a dashboard that prints the full card number for anyone who walks past your screen. It also means the details are not stored on your phone until you type them into Wallet, which is a small security gain.

The pop-up sets a trap for the careless too. Anyone with your login and your authenticator can read the card and spend it, so the authenticator app is doing real work here. Codes from an app are harder to intercept than text messages, which can be diverted through a SIM swap, a scam where someone persuades your mobile operator to move your number to a new SIM. If you use the payment password instead, make it something you do not reuse on other sites.

A few habits help. Do not screenshot the credentials window, because screenshots sync to cloud photo libraries. Do not paste the number into a notes app that syncs across devices. Treat any message asking for your payment password or authenticator code as a scam, whoever it claims to be from. No issuer and no support desk needs that code.

The card balance is not your account balance

Two numbers appear on two screens, and the gap between them explains how the card works. The dashboard shows a total balance of $136.31. The card page shows a card balance of $0.00 USD. For a prepaid card that separation is normal: you move money onto the card, and taps draw down that pot while the rest of your holdings stay where they are.

It also means the card is only as useful as the top-up step behind it, and that step is where the costs usually hide. The video does not show a top-up, a fee schedule, a spending limit or an identity check, so read the card terms and the issuer's fee list before you move money onto the card.

Then there is tax. In many countries, spending crypto counts as a taxable sale, even when the purchase is a coffee. The tax office generally treats the moment of payment as a disposal at market value, so if the coins have risen since you bought them, the gain can be taxable while the thing you bought is already gone. Keep a record of what you spent, when, and what the coin was worth that day. The platform may produce a statement, but the record is your problem, not theirs.

When the Debit or Credit Card option is missing

A note appears on screen at exactly the point where the flow can fail: if the Debit or Credit Card options do not appear, change your phone region to one of the countries where Apple Pay is supported. Wallet only offers the add-card flow in regions Apple supports, so a phone set to the wrong country shows a shorter menu with no way forward.

The setting lives in Settings, under General and then Language & Region. Changing it is not free of side effects. Your App Store account, subscriptions and any cards already in Wallet can be affected, and some apps behave differently. On a phone you rely on, note what the region was before you change it.

The region is an Apple Pay condition, not proof that the card itself is available where you live. Those are two different checks, and passing one does not settle the other.

What Apple Pay changes, and what it doesn't

Apple Pay does not move your money. When you add a card, Apple assigns it a device account number and stores that on the phone, and the merchant receives the device number rather than your real card number. That is the security benefit: a compromised terminal, or a shop assistant who writes things down, does not end up with credentials that work online.

What Apple Pay does not change is everything else about the card. The fees, the conversion rate, the limits and the issuer's terms all stay the same, because the transaction still settles with the card issuer through Visa. A decline in Wallet comes from the card, not from Apple. If your card balance is empty, the phone will look set up and the payment will still fail.

Losing the phone deserves a thought too. Apple lets you remove cards remotely through Find My or iCloud, and you should know how to do that before you need it. The virtual card itself stays on the platform, so a replacement phone can be set up with the same details and the same 2FA code.

The risks I would weigh before funding the card

The money on the card is a claim on the issuer. That is true of any prepaid card, and it is the risk people forget, because the app looks like a wallet and feels like a bank account. If the programme is frozen, restricted in your country or wound up, the balance does not follow you around; you join a queue. So I would keep the card balance small and top up as I go rather than park a month of spending on it.

There are two names on this product, one on the dashboard and UPay in Wallet, and that split matters when you need help. A failed payment can be the app, the issuer or the merchant, and knowing which one to call saves days. The card terms will say who is responsible for what.

Conversion is the second cost to watch. If the card balance is in US dollars and you spend in another currency, a conversion happens at a rate you do not set, and the spread can be wider than the headline fee. Crypto adds a second layer, because the coin you top up with can move between the moment you convert and the moment you spend. A card that feels free can cost several percent across those two steps.

Rewards deserve their own caution. Crypto cards often advertise cashback paid in the platform's own token, and the conditions are where the value lives: a lock-up period, a holding tier you must maintain, a monthly cap, or a token price that falls while you wait to claim. I would not count any reward as income until I had read those conditions and worked out what it is worth if the token drops. A reward paid in a token you cannot sell at yesterday's price is not income yet.

Account security is the last item. The verification code in this flow arrives by email, which makes your email account part of the card's security. Two-factor authentication on the email, a password manager and a check of logged-in devices are basic hygiene before you attach a payment card to anything.

What to check before you add the card

Before I attached a card like this to Apple Pay, I would find five numbers on the issuer's fee page: what it costs to issue the card, the monthly fee if there is one, the top-up fee, the currency conversion markup and the ATM withdrawal charge. Those five decide whether the card is cheap or expensive, and none of them appear in the setup flow.

Then the limits: how much you can load, how much you can spend in a day, and whether ATM withdrawals have a separate cap. A card with a low daily limit is fine for groceries and useless for a hotel deposit.

Next, the currency of the card balance and the rate used when you top up with crypto. If the answer is vague, that is your answer. Ask support in writing and keep the reply.

Finally, test it small. Add the card, buy something inexpensive, and check the balance and the fee that actually posted. The setup takes two minutes; the fee schedule takes longer to read, and it is the part that decides whether the card stays in your wallet.