### 1. The wallet is added but not fully verified
A payment method can appear inside a wallet and still fail on a live transaction. This is common when the setup was completed in a hurry before travel, or when the app accepted the card but the first real charge triggers extra checks.
Typical signs:
- the app lets you choose the payment method, then rejects the ride request
- the wallet shows the card, but transport or service payments fail
- the app asks for more confirmation after you try to pay
### 2. The card works online, but not for this payment flow
Some foreign cards work for certain merchant types and fail for transport-related authorizations. A coffee purchase and a ride-hailing charge do not always pass through the same way.
Typical signs:
- you paid for a small retail purchase earlier, but the ride still fails
- one card fails while another card may work
- the error appears only at the final payment step
### 3. The app account and the payment account do not match cleanly
A newly created account, incomplete name format, or inconsistent region settings can create friction during the first attempted charge.
Typical signs:
- account setup looks complete, but booking never reaches confirmed payment
- the app loops back to payment selection
- you are repeatedly asked to verify identity or payment details
### 4. You are trying to solve it only when you already need the car
This is the most common failure pattern for first-time visitors. Payment troubleshooting at the hotel entrance, airport pickup zone, or train station forecourt creates time pressure and forces you into repeated blind retries.
Typical signs:
- you have never tested the wallet before arrival
- you are depending on one app and one card only
- you do not know your backup route to the station, hotel, or scenic area