Read summarized version with:

Virtual cards for insurance agencies let you issue a capped virtual Visa card per adjuster or per claim, named for the claim number, locked to the right spend where supported. Every charge ties back to the claim, the card closes at settlement, and the leftover funds return to your wallet. There is no credit check. This is expense control for the agency's and adjuster's own and firm-authorized vendor expenses, not claim payments to insureds, and not premium, trust, or fiduciary funds.

If you run an agency or a restoration firm, you already know the pattern. An independent adjuster gets deployed to a catastrophe, and they pay for the hotel, the fuel, and the meals out of their own pocket. Then they wait. Property claims take longer to settle than auto claims, and field staff can sit from one season to the next before they are made whole. As one adjuster put it, many are lucky to break even on their first few storms.

This article is about the mechanism that stops that. Below we cover how to put a hard cap on every adjuster and claim card, how to lock a card to the right spend, how every charge ties back to a claim or policy number, how field staff and vendors use the card without your banking details, what happens to the money when a claim settles, and how to roll out a whole catastrophe roster at once.

Can I set a per-adjuster or per-claim limit that cannot be exceeded?

Yes. Every card you issue carries an approved spend amount, and that cap is a hard limit. A charge over the cap is declined at authorization, so the card can never charge a cent past it. You can set the cap per transaction, per day, per month, or per year, which means a deployment card can run on a monthly budget with a daily ceiling on top.

This is the control that ends the fronting problem. When the card itself carries the spend, the adjuster does not put a hotel on a personal card and chase reimbursement. The firm sets the number up front, and field staff spend inside it.

Can I lock a card to the right spend and block the rest?

Yes, where supported. On top of the cap, you can lock a card to certain kinds of merchant or to a single vendor. A deployment card can be restricted to restoration, hardware, and equipment-rental merchants, lodging, travel, or fuel, so it stays on tarps, a water extractor, and a hotel and declines a charge that does not belong on the claim. A mitigation card can be tied to one authorized supplier.

ControlWhat you setHow it behaves
Per-adjuster or per-claim capA fixed approved spend amount per transaction, day, month, or year.Hard limit. A charge cannot go over the cap.
Card naming = claim numberName it CLM-20418 or the policy number.Every charge maps to one claim, so reconciliation is built in.
Category lockRestoration, hardware, and equipment-rental merchants, lodging, travel, or fuel.Declines off-category charges, where supported.
Merchant lockA specific vendor or store.Ties a mitigation card to one supplier, where supported.
Location and timeBy country or city, or active hours.Holds a deployment card to the loss state and claim period, where supported.
Freeze or closeOne-tap freeze or revoke from any device.Close at settlement. Leftover funds return to your wallet.

The cap is a hard limit. The locks are strong guardrails, not guarantees. Category, merchant, location, and time locks work based on supported controls and the merchant data the card network passes. A mis-coded merchant can let an off-list charge slip through, so treat the locks as a strong filter on top of the cap, where supported.

Can I tie each charge back to a claim or policy number?

Yes, and this is where the model earns its keep. Name each card for the claim or policy number, for example CLM-20418 / Mitigation, and every transaction on that card lands under that name. Instead of one statement line that reads "agency Visa $4,280" with no idea which claim it belongs to, you get a per-claim record that is already grouped by the time you look at it.

Each card has a live transaction feed with categorized receipts. You export per card, which means per claim, so the claims desk gets a clean record and the books reconcile against the claim number without anyone untangling a shared statement by hand. Restoration crews are told to keep receipts for tarps, water extractors, fans, and equipment rentals; here the receipt is captured against the claim as the charge posts. For the full workflow, see how to reconcile virtual card payments.

How do I issue a card per adjuster or per claim?

Four steps take you from a new claim to a card the adjuster can use the same day.

From a new claim to settlement
1
Fund your wallet
Load operating funds by ACH or wire. No credit check, no personal bank link.
2
Make the card
Create a card per adjuster or claim, named for the claim number, with the approved spend amount as the hard cap.
3
Lock the spend
Restrict to restoration, hardware, and equipment-rental merchants, lodging, travel, or one vendor, where supported.
4
Email it
The card is emailed to the adjuster or vendor and works in Apple Wallet and Google Wallet.
5
Track
Watch every charge in the dashboard, grouped by claim, with receipts you can export.
6
Close
At settlement, close the card in one tap and the leftover funds return to your wallet.
Fund Make Lock Track Close

How do field adjusters and vendors use it without our banking details?

The card is emailed to the recipient. The adjuster or vendor adds it to Apple Wallet or Google Wallet and uses it anywhere Visa is accepted, online, in apps, or by tapping a phone at the counter where contactless is taken. They never see your agency banking details, because there is nothing to share. The card draws from your wallet, and the recipient only ever holds the card.

That keeps a deployment card with the adjuster and a mitigation card with the supplier, while your account details stay in your account. It is the same model behind handing spend to accountants or individual departments: one wallet, many cards, no shared number.

What happens to the money when the claim settles or the card is cancelled?

Freeze or revoke any card in one tap from any device. When a claim settles, you close that one card and new charges stop being approved on it. The leftover funds return to your wallet, ready for the next card. The card's history stays as the claim's spend record, so closing the card does not erase the reconciliation.

This is expense control, not a claims-payout product. The card controls the agency's and adjuster's own operating spend and firm-authorized vendor and mitigation spend. It does not issue claim payments to insureds, settle claims, or hold premium, trust, or fiduciary funds.

Can I issue cards in bulk for a whole catastrophe roster?

Yes. You can make one card at a time, or issue cards in bulk from an Excel file or through the API, each with its own cap and locks. For a catastrophe deployment, that means a card per adjuster on the roster goes out at once instead of being built one by one. The same wallet funds the agency operating cards too, so lead-gen and marketing, the errors-and-omissions renewal, agency-management software, and continuing-education and licensing each get their own named card with its own cap, and month-end reconciles itself with no shared agency Visa.

A worked example: Cedar Ridge Insurance and claim CLM-20418

Cedar Ridge Insurance is an independent property and casualty agency. Field adjuster Renee Coleman is working CLM-20418, a residential water loss. The office manager issues two cards from the wallet, one for the adjuster and one for the claim's mitigation.

Worked example
Cedar Ridge Insurance handles claim CLM-20418

How the cards are set

  • R. Coleman / Field. Adjuster field expenses, approved spend amount $1,800 a month with a $450 daily cap, category lock on fuel, lodging, travel, and meals where supported.
  • CLM-20418 / Mitigation. Claim restoration spend, approved spend amount $2,500, merchant and category lock on restoration, hardware, and equipment-rental merchants where supported.

What happens on the field card

  • Approved $96 fuel, $284 for two nights lodging, and $71 on meals, $451 for the week, under the monthly cap.
  • Declined a $470 same-day overrun, blocked by the $450 daily cap until the next day. No personal card, no reimbursement chase.

What happens on the mitigation card

  • Approved $340 tarps and sealing, $1,180 for a water-extraction rental, and $260 for drying fans, $1,780 in total, all inside the cap.

When the claim settles

The office manager closes the mitigation card and the remaining $720 returns to the Cedar Ridge wallet. Both cards export to a single CLM-20418 record, every charge tagged to the claim for the claims desk.

The same wallet funds spend Cedar Ridge hands off elsewhere, from cards for its accountants to individual departments. Every card runs on the mechanics on this page.

People also ask

Can I tie every charge back to a claim or policy number?

Yes. Name each card for the claim or policy number, for example CLM-20418 / Mitigation. Every transaction on that card shows under it on the live dashboard with receipts, so you can export a clean per-claim record for the claims desk and reconcile each charge to the claim. This is for the agency's and adjuster's own and firm-authorized vendor expenses, not claim payments to insureds.

Is there a credit check?

No. Cards are wallet-funded. You load your Zil Money wallet by ACH or wire, then cards draw from that balance. There is no personal bank link and no credit check.

Can I close the card when the claim settles?

Yes. Freeze or revoke any card in one tap from any device. Cancel the card at settlement and the leftover funds return to your wallet.

Can field staff and vendors use it without our agency banking details?

Yes. The card is emailed to the recipient and works in Apple Wallet and Google Wallet anywhere Visa is accepted. The adjuster or vendor never sees your banking details.

Can I export per-claim reports for reconciliation?

Yes. Each card has a live transaction feed with categorized receipts. Export per card, which means per claim, so reconciliation against the claim number is built in.