## TL;DR

The virtual card has a capped limit and the purchase would exceed the remaining balance, so the network declines it. In Mesh, increase the card's limit or issue a new virtual card with a sufficient limit for the purchase. The card is fine; the limit is the constraint.

## Error

```text
Mesh: virtual card declined  -  spend limit reached
```

## Steps

1. Open the virtual card in Mesh and check its limit versus spent amount. Expected: the remaining balance is less than the attempted purchase.
2. If the purchase is approved spend, raise the card's limit to cover it (requires the card owner's or admin's permission). Expected: the new limit exceeds the purchase amount.
3. Alternatively, issue a new virtual card with an adequate limit and use it for the purchase. Expected: the new card authorizes the charge.
4. Retry the purchase. Expected: the transaction authorizes and appears in Mesh.
5. Reconcile the card: attach the receipt and code the transaction. Expected: the transaction is documented and reconcilable.

## When to use

- A Mesh virtual card declines with "spend limit reached".
- A subscription charge exceeds the card's remaining limit.
- A one-time vendor card needs a higher cap for a large invoice.

## When not to use

- The card is expired or frozen (a card-state problem, not a limit problem).
- The decline names a blocked merchant category.
- The merchant is attempting an authorization hold larger than the purchase.

## Tool compatibility

Mesh Payments virtual cards (current 2026 releases). Applies to single-use and multi-use virtual cards.

### Variant phrasings

### mesh card "insufficient limit" at checkout

Same decline in network wording. Raise the limit or issue a fresh card.

### subscription failed on a mesh virtual card

The recurring charge hit the cap. Raise the limit or move the subscription to a card with a higher limit.

### one-time vendor card declined in mesh

The card was issued for an estimate below the final invoice. Issue a new card for the actual amount.

## Why it happens

Virtual cards are issued with explicit spend limits as a control: the blast radius of a compromised card number is capped. When legitimate spend grows past the cap (invoice higher than estimated, subscription price increase), the same control declines it. Raising the limit or reissuing is the intended workflow, not a workaround.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_tgMYdUci4BxWXGDbQF1eCg