A “Visa Provisioning Service” charge on your bank statement is almost always a temporary verification hold, not a real charge. It appears for $0.00 or $1.00 when your Visa card gets added to a digital wallet or saved with an online merchant, and it drops off your statement within a few days without any money leaving your account. If you recently set up Apple Pay, Google Pay, Samsung Pay, or linked your card to a new app or subscription, that’s what you’re looking at.
What Triggers the Entry
Whenever you register a Visa card for later use, Visa contacts your bank to confirm the card is active and valid. Your bank may approve immediately or ask for extra verification, like a one-time passcode by text or email. To test that the payment pipeline actually works, your bank places a tiny authorization hold. That hold is what shows up on your statement as “Visa Provisioning Service.”
The most frequent cause is adding your card to a mobile payment app. Each device you register produces a separate check, so adding the same card to your phone and your smartwatch can generate two provisioning entries. Other common triggers:
- Linking your card to a streaming service or new subscription
- Saving it as a payment method on a new online store
- Signing up for anything that stores your credentials for future billing
The common thread is storing the card for later, not paying for something right now.
Does Any Money Actually Leave Your Account?
No. The $0.00 or $1.00 entry is a temporary authorization hold, not a fee from Visa, your bank, or the wallet provider. Once the verification succeeds, the hold is released and your balance returns to exactly where it was.
On a credit card, the hold briefly reduces your available credit by a dollar or less. Barely noticeable. On a debit card, the situation is worth watching. A pending hold gets subtracted from your available checking balance right away. If your account is already running low, even a $1.00 hold can push your available balance below what’s needed to cover other transactions clearing that evening. If those post against an insufficient available balance, your bank may charge an overdraft or non-sufficient-funds fee, which typically runs $5 to $35 depending on the bank.
The risk is small for most people. But if you’re managing a tight balance and suddenly see one or two provisioning holds, keep an eye on your available balance until they clear. Using a credit card for digital wallet registration sidesteps this entirely.
When the Hold Disappears
Most provisioning holds drop off within one to five business days. Visa’s authorization framework sets outer limits: card-not-present transactions, which include digital wallet provisioning, can be held up to 10 calendar days, while standard card-present authorizations must clear within five calendar days.
In practice these holds usually vanish faster than the maximums because there’s no actual transaction to settle. Your bank simply lets the authorization expire once verification succeeds. If a hold lingers past 10 days, call your bank and ask them to release it manually. They can see on their end that no settlement was ever submitted against it.
How to Confirm the Charge Is Yours
Match the timestamp first. Pull up the charge details in your banking app and compare the date and time against when you added a card to a wallet, signed up for a new service, or saved your payment info somewhere. If the timing lines up within a few minutes, the entry is routine.
Then check the amount. Legitimate provisioning holds are almost always $0.00 or $1.00. A “Visa Provisioning Service” line paired with a larger dollar amount is unusual and worth investigating. A genuine provisioning check has no reason to hold more than a nominal amount.
Finally, count the entries. One per device or service you recently set up is normal. Multiple entries you can’t account for are not.
What to Do If You Didn’t Authorize It
An unexplained provisioning charge can mean someone obtained your card number and registered it on their device or account. Even though the hold itself is small, the token created during provisioning could be used for real purchases later, so take it seriously.
Report It Fast, Especially on a Debit Card
Timing controls how much you can be held liable for. Under federal law, if you notify your bank within two business days of learning about unauthorized activity on a debit card, your maximum liability is $50. Wait longer than two business days and the ceiling jumps to $500. If unauthorized transfers appear on your statement and you don’t report them within 60 days, you could be liable for the full amount of any transfers that occur after that 60-day window.
For credit cards, Visa’s Zero Liability Policy generally means you won’t be held responsible for unauthorized charges processed through the Visa network, provided you report the problem promptly.
What Happens After You Report
Once you notify your bank, it must investigate and reach a determination within 10 business days. The bank can extend the investigation to 45 days, but only if it provisionally credits your account within the first 10 business days so you aren’t left short while the review runs. If the bank confirms the error, it must correct it within one business day and report the results to you within three business days of finishing the investigation.
You don’t need a police report or any special documentation to file the dispute. The law focuses on timeliness, not form. You can report by phone, in person, or in writing. Keeping a written record still helps if there’s ever a question about when you reported the problem. If the bank asks for written confirmation of your initial report and you don’t provide it within 10 business days, the bank may not be obligated to give you that provisional credit, so follow up in writing even if you first reported by phone.
Ask for a New Card
Beyond filing the dispute, ask your bank to cancel and reissue the compromised card. That invalidates any tokens created from the old card number. You’ll need to re-add the new card to your legitimate wallets afterward, which will generate fresh provisioning entries. Those are expected.