Read summarized version with:
ChatGPT Claude Grok Perplexity Gemini

Why the card limit does not move with the contract

A vendor card is a virtual Visa card dedicated to one supplier. It carries the budget you agreed to pay that vendor, set as a cap when the card was created, and it can be restricted so other merchants are typically blocked from charging it, based on your controls. That cap is a fixed number sitting on the card, not a live link to whatever document your finance team keeps the current agreement in.

So when the agreement changes, the card does not know. A landscaping vendor's seasonal rate goes up, a software vendor tacks on a per-seat fee for new hires, a contractor's scope grows to cover an extra site. None of that reaches the card automatically. The cap stays at the number you typed in the day you created it, whether that was set to cover a monthly retainer, a project total, or a recurring service fee.

That is not a flaw in the setup. A card that quietly stretched to match every change a vendor emailed over would defeat the reason you capped it in the first place. The gap only becomes a problem when nobody closes it, and the card sits capped at last quarter's number while this quarter's invoice is already higher.

Signs a vendor's contract amount just changed

A few patterns show up before the card actually declines anything, and catching them early beats reacting to a bounced payment:

  • A renewal notice or updated statement of work. Annual contracts often bake in a rate step-up that is easy to miss in a long renewal email.
  • A new line item on the invoice. A processing fee, a rush charge, or a materials surcharge added to what used to be a flat monthly bill.
  • A scope change you approved separately. Extra hours, an added deliverable, or a second location, agreed to in a conversation that never made it back to whoever set up the card.
  • The vendor mentions a decline. Sometimes the first sign is the vendor asking why their payment did not go through, which means the cap already did its job.

If you already run a periodic check on vendor cards, comparing invoices against limits is worth adding to that review. For the recurring side of that habit, see managing recurring vendor payments with virtual cards.

A decline is not an emergency to fix in the moment. Charges over the agreed amount are not guaranteed to clear; your controls can decline them, which means a request to raise the cap on the spot is exactly the kind of pressure a fraud attempt relies on. Confirm the new figure through a channel you already trust before you touch the card, even if the vendor is asking you to hurry. The Consumer Financial Protection Bureau's fraud and scams resources cover how to verify a request like this before acting on it.

How to update a vendor card when the contract amount changes

The order matters more than the tool. Confirm first, then adjust.

  1. Confirm the new amount in writing.

    Get the updated rate, fee, or scope change in an email or a signed change order before you adjust anything. A blocked charge is not urgent. A card raised on a verbal request with no paper trail is a bigger risk than a late invoice.

  2. Cancel the existing card and issue a new one.

    There is no option to edit the cap on a card that has already been issued. Cancel the existing card and issue a new one under the same vendor name at the updated limit instead.

  3. Set the new cap to match the updated agreement.

    Set the cap on the new card to the new contract amount, matching the figure in the updated agreement. Charges over that agreed amount can still be declined going forward, once your controls flag the difference.

  4. Reapply the merchant and time restrictions.

    If you reissued the card, restrict it to the intended vendor again based on supported controls, and reset the active window so it still covers only the life of the agreement.

  5. Share the updated details and log the change.

    Send the vendor the new card details if a new number was issued, and note the old amount, the new amount, and the date of the change somewhere you will actually find it at the next renewal.

Give every vendor a card that matches the current deal

Issue virtual Visa cards quickly, cap each one to the agreed amount, and update the cap the moment a contract changes.

See vendor cards

Old limit vs. updated limit: what actually changes

The card itself does not look different to the vendor. What changes sits entirely in your controls.

Card still capped at the old amount

The number on the card matches an agreement that no longer applies.

  • The next invoice at the new rate exceeds the cap, and that portion of the charge is not guaranteed to clear under your controls.
  • The vendor sees a decline with no explanation, and asks you what happened.
  • Someone has to stop mid-task to track down the current contract terms before the payment can go through.
  • A price increase you never agreed to could also hit the same cap, so a decline alone does not tell you which case you are in.
Card updated to the new amount

The cap, the merchant restriction, and the active window all match the current deal.

  • The invoice at the new rate clears without a decline, because the cap already reflects the agreed change.
  • The vendor restriction is reapplied on the new card as part of setup, so it still only works for the one supplier it was issued to. That does not happen automatically, it has to be set again on the reissued card.
  • The change is logged, so the next renewal review starts from the current number instead of the original one.
  • A charge outside the new agreed amount still gets flagged, since the cap keeps doing its job at the updated figure.

Example: a bookkeeping vendor's added fee

Hypothetical example, for illustration only.

A small business pays its bookkeeping vendor through a card capped at the monthly retainer agreed at signup. Six months in, the vendor adds a payroll-processing fee to the plan after the business asks them to start handling payroll filings too. The vendor emails the updated monthly total along with the new service. The business owner cancels the existing card and creates a new card under the vendor's name at the new monthly total, with the same merchant restriction reapplied as before. The vendor gets the new card number, the next invoice clears without a decline, and the owner notes the old and new amounts in the vendor file for the next annual review.

When to cancel the relationship instead of raising the cap

Not every requested increase is one you should approve just because the vendor asked. A cap that keeps climbing with every renewal, a fee added without an explanation you can follow, or a change request that arrives with pressure to act immediately are all reasons to pause before updating the card. Verifying who is actually asking matters here too. If you have not dealt with a particular vendor contact before, or the request has any of the markers common in vetting a new vendor before the first payment, treat it the same way: confirm independently before the card changes at all.

If the relationship itself is ending, the simpler move is to stop the increase question altogether. Cancel the card to stop future charges from clearing, on your schedule, anytime the contract wraps up. Closing the card is a firm line the vendor cannot argue around, unlike a limit that can be pushed higher one email at a time. For the full setup this card sits inside, see how to pay vendors with virtual cards.

Frequently asked questions

Does a vendor card's spending limit update automatically when a contract changes?+
No. The card carries the limit you set when you created it, and it holds that limit until you change it. A rate increase or a new fee in the contract does not move the cap on its own, someone has to update the card to match.
What happens if a vendor's invoice is higher than the card's limit?+
The overage on that invoice is not guaranteed to clear; your account's controls can decline it, which is the card working as designed, not a glitch. Treat the decline as a signal to check what changed before you raise the cap.
How do I raise a vendor card's limit for a new contract amount?+
Cancel the existing card and create a new one under the same vendor with the updated limit. There is no option to edit the cap on a card that has already been issued, cancelling and reissuing is the only way to change the amount.
Will the vendor need a new card number when the limit changes?+
Yes. Since there is no in-place edit for a card's cap, changing the limit always means cancelling the current card and issuing a new one, which carries a new card number. Send the vendor the updated details so their billing file matches the new card.
What if the contract amount goes down instead of up?+
Bring the cap down using the identical cancel-and-reissue steps you would use to raise it. A card still capped at the old, higher amount after a scope reduction leaves room for a charge that no longer matches what you agreed to pay, so there is no reason to leave the old limit in place.
Can a vendor charge more than the card limit without my knowledge?+
The cap is meant to stop that. A charge past the agreed amount is not guaranteed to clear; your controls can decline it, so an attempt over the limit typically shows up as a decline on the vendor's end rather than a surprise charge on yours.
How do I know a rate increase request is legitimate and not a scam?+
Confirm it through a channel you already trust, a phone call to a known contact or your existing email thread, before you touch the card. Fraud attempts often arrive as an urgent request to raise a limit or change payment details. A card restricted to the intended vendor limits the damage if a card number ever leaks, but it does not verify who is asking for a change, that step is still on you.
Does updating the limit affect the vendor restriction on the card?+
No, the merchant restriction and the spending cap are separate controls. If you reissue the card, reapply the restriction to the intended vendor as part of setup rather than assuming it carries over automatically from the old card.