Virtual card spend controls compared by platform

Most companies issue corporate cards and set a monthly limit, which caps how much gets spent but not where it goes.

Virtual card spend controls fix that by locking rules to the card itself, not just a dollar amount. The right controls depend on what you're trying to manage: SaaS subscriptions, travel spend, departmental budgets, or expense volume. Platforms build for these differently.

What are virtual card spend controls?

Virtual card spend controls are pre-set authorization rules programmed into a virtual card that restrict how, when, and where funds can be spent. Any transaction that falls outside those rules gets declined automatically, before it ever reaches your books.

That's a different model than a single card limit. A $5,000 card that works at any merchant isn't meaningfully controlled: you find out what it was used for when the statement arrives. A card locked to one vendor is controlled by design. Ramp's per-vendor virtual cards work this way: a card created for Figma can only charge Figma, and any other attempt is declined automatically.

Finance teams use these controls to manage SaaS subscriptions, vendor payments, travel spend, and departmental budgets, wherever they need spend to match a policy without manually reviewing every transaction.

Types of virtual card spend controls

Most platforms combine several of these control types on a single card rather than forcing you to pick one:

Spending caps

A spending cap sets a maximum per-transaction amount or a total budget that depletes as it's used. This works well for recurring subscriptions where you want to allow charges up to a known ceiling without approving each one.

Merchant and category restrictions

Merchant restrictions lock a card to a single vendor, so a card issued for one SaaS subscription can't be used anywhere else. Category restrictions use a merchant category code (MCC) to approve spend only within a defined category, and charges outside it get declined everywhere else.

Time and expiration limits

Time-based controls set an active-until date or a specific window when the card can be used. Single-use cards take this further: they invalidate automatically after the first authorized purchase.

Frequency controls

Frequency controls reset a card's limit on a recurring schedule, daily, monthly, or yearly, so it supports ongoing spend like a subscription without needing a new card each cycle.

What to look for in virtual card spend controls

These five criteria separate platforms that treat virtual cards as a real control mechanism from ones that treat them as a card-level limit with extra steps.

Merchant level controls, not just card limits

A virtual card with a $500 limit that works at any merchant isn't meaningfully more controlled than a physical card. Look for platforms that let you lock a virtual card to a specific merchant, so a card created for a SaaS subscription can only charge at that vendor. Any other attempt gets declined automatically.

This kind of enforcement happens at the point of swipe, not after the fact. Ramp blocks 3.5% of transactions that would otherwise violate policy before they ever create reconciliation work, which is the practical payoff of authorization-time enforcement over after-the-spend review.

Card creation that scales with vendor count

Per-vendor virtual cards lose their value if you have to manually create one for every new vendor. Look for platforms that automatically generate a virtual card when you approve a new vendor, since that's what makes this model practical at scale.

Real time spend visibility

Virtual cards generate transaction data the moment a charge occurs. Platforms that surface this data in real time let you see vendor spend as it happens, instead of discovering a surprise renewal on your monthly statement. This visibility is what makes frequency and expiration controls useful—you can only act on a renewal window or a single-use card invalidation if you see the transaction when it happens.

Accounting sync per card

Each virtual card should map to a GL code, cost center, and department at creation. That way, every charge is automatically assigned to the correct category, eliminating manual coding.

Auto renewal and subscription tracking

Issuing a virtual card for each SaaS vendor makes it easy to see which subscriptions are active, what they cost, and when renewals are due. Look for platforms that surface renewal timing and flag unused subscriptions, since merchant restrictions and expiration controls work together to manage a subscription's full lifecycle.

How virtual card spend controls work across platforms

These four platforms take different approaches to virtual card controls, ranging from per-vendor merchant-locking built for SaaS management to budget-based card programs and T&E-integrated spend policies. Here's how they compare across the criteria that matter most.

Ramp

Ramp's corporate cards are built around the per-vendor virtual card model. You create a virtual card for each SaaS vendor, locked to that specific merchant. Your Figma card can only charge Figma: any other attempt gets declined automatically.

Creating cards is fast, even at scale. Ramp pulls vendor payment history, existing contracts, and card spend into one record, so you can approve new cards with full context.

Because Ramp integrates expense management and accounts payable, you see virtual card spend and invoice payments in the same vendor record. If you pay a vendor partly by card and partly by invoice, you get a single payment history, not two separate reconciliation workflows.

Cards sync two-way with QuickBooks, NetSuite, Sage Intacct, and other accounting systems, and Ramp auto-codes 90% of transactions on receipt, so you don't have to manually categorize or reconcile charges.

Ramp also tracks subscription activity and renewal timing, so you know which subscriptions are coming up for renewal before they auto-charge.

BILL Spend & Expense

BILL Spend & Expense (formerly Divvy) takes a budget-first approach to virtual card controls. Rather than setting limits on individual cards, you allocate budgets to teams and let employees request cards against those budgets. This gives finance control at the budget level rather than the transaction level. Virtual card creation is straightforward and supports physical and virtual cards from the same account.

Where BILL Spend & Expense is more limited is in the per-vendor merchant-locking model and depth of SaaS subscription management. BILL's core AP platform is a separate product from BILL Spend & Expense. Teams that want unified card and invoice management will need to use both.

Navan

Navan issues general corporate cards with built-in spend controls and policy enforcement for both travel and non-travel expenses. Its biggest strength is that it brings card spend, T&E policy, and travel booking into one system. Your employees book and pay within policy, and the platform automatically flags out-of-policy transactions, rather than catching them after the fact. Cards earn up to 1.5% cashback and sync with NetSuite, QuickBooks, Xero, and Sage.

If your main goal is SaaS vendor management with per-vendor merchant-locking, Navan's card program isn't built for that use case.

Expensify

Expensify offers the Expensify Card as part of its expense management platform. SmartLimit automatically adjusts card limits based on available budget, so you don't have to manually update limits as budgets shift. SmartScan processes receipts automatically and matches card transactions to expense reports without manual entry. The Expensify Card also earns cashback on purchases.

Expensify's strength is in the receipt capture and expense report workflow. It doesn't offer per-vendor merchant-locking or dedicated SaaS vendor management tools.

Which platform fits your team?

SaaS vendor management, travel spend, departmental budgets, and expense volume each point to a different platform below. The right fit depends on where your biggest control gaps are today.

If your primary virtual card use case is SaaS vendor management, locking individual cards to individual vendors, tracking subscription renewals, and reconciling vendor spend without manual coding, Ramp's per-vendor merchant-locking model is the most purpose-built for that workflow.

If your team spends more on travel than on software subscriptions, Navan's card program integrates T&E policy enforcement with booking to reduce manual work across the entire workflow.

If your primary challenge is managing departmental spend budgets and you want a free platform, BILL Spend & Expense's budget-first model fits that workflow.

If expense report volume and receipt processing are your main pain points, alongside card spend, Expensify's integrated card and SmartScan workflow reduces manual work in those processes.

Control vendor spend with Ramp virtual cards

Ramp's per-vendor virtual card model gives you control at the level that matters: each vendor gets its own card, locked to that merchant, with spend visible in real time. If you're managing dozens or hundreds of SaaS subscriptions, that's the difference between knowing what you're spending and finding out at month-end.

See how you can control vendor spend with Ramp's virtual cards.