Virtual cards for travel agencies: pay suppliers per booking.

Read summarized version with:

ChatGPT Claude Grok Perplexity Gemini

A virtual card for a travel agency is a Visa card you create for one booking, fund from your Zil Money wallet, and hand to the supplier so the hotel, airline, or DMC charges that card and nothing else. You set a spend cap equal to the supplier's quoted net cost, so a charge inside the cap is approved and an overcharge is declined. Where supported, you can also lock the card to the travel or lodging merchant category so it only works at that kind of supplier. Each card carries the booking reference, so when the supplier settles you match the charge to the booking instead of chasing one shared agency card across hundreds of trips. There is no credit check and no personal bank link. You can email the card to the supplier or add it to a wallet, issue cards one at a time, in bulk from an Excel sheet, or through the API, and keep a receipt on every charge for clean reconciliation and commission tracking.

If you run an agency, a tour operation, or a back office that pays travel suppliers, the hard part was never selling the trip. It is the payout side. You front the net rate to a hotel or an airline before the client has paid you in full, then you wait for the charge to land, and then you try to remember which of the forty charges on one company card belongs to which booking. A virtual card moves the control to the moment of payment, where it belongs.

This guide is about that specific job: paying your suppliers per booking, capping what they can take, and reconciling each card against the trip. It is the supplier-payout companion to virtual cards for business travel, which covers funding your own employees when they travel on company trips. Here, the cardholder is your supplier, not your traveler.

What a virtual card for a travel agency is, and how paying a supplier works

A virtual card is a real Visa card you create on screen instead of carrying as plastic. For a travel agency, the workflow is short. You create a card for the booking, fund it from your wallet, set the cap to what the supplier quoted, and send the card to the supplier for the reservation. When the supplier runs the card, the charge clears against the cap, posts with the booking reference, and waits for you to match it.

The reason this fits travel so well is the hotel flow most agencies already know. The hotel runs an authorization when the guest checks in, and the charge settles at checkout. That gap between authorization and settlement is exactly where a capped card earns its keep: the authorized amount is the amount you agreed to, and anything the property tries to tack on at checkout runs into the cap.

Why agencies move supplier payouts off one shared card

The shared agency card feels efficient until you are the one reading merchant names off a statement at month-end. Agency owners describe the same handful of problems, in their own words:

• "The supplier charged more than the quote." A property adds resort fees, a mini-bar, or an upgrade nobody approved, and you only see it after it lands.
• "One company card and I cannot tell which booking is which." Forty charges, one account, and a reconciliation that turns into statement archaeology.
• "Fronting cash to airlines before the client pays." The BSP and IATA cycle pulls funds on its schedule, not yours, and cash flow tightens.
• "FX markup eats our margin." Commission is already thin, and a card with no per-booking discipline makes it thinner.

None of this means anyone is doing the job badly. It means a single card with no per-booking rules cannot give you control or a clean record. A card per booking does both, because the rules travel with the card.

How to set a spend cap so overcharges and add-ons get declined

The cap is the one control that always holds, so it is the one to get right. Set it to the supplier's net cost, the number on the supplier's quote, not the gross price your client pays. If the hotel quoted you $840 for three nights, the cap is $840. The client price and your commission live in your booking system, not on the card.

When the cap equals the net cost, the math does the policing for you. The agreed charge clears. The surprise charge that pushes the total higher is declined at authorization, which means you find out at the counter instead of at month-end. Top up the card if a change order is legitimate, the same way you would approve any real cost.

Locking a card to the hotel, airline, or tour category

Where supported, you can also lock a card to a merchant category such as lodging or airlines, so the card only works at that kind of supplier. This is useful when you want a card that can pay the hotel but not a random merchant if the number leaks.

Be honest with yourself about what these locks do. The spend cap is deterministic: a charge over the cap is declined, full stop. Merchant, category, location, and time locks are probabilistic. They are checked at authorization using the data the supplier's acquirer passes through the network, and that data is not always complete or correctly coded. So treat the category lock as a strong second layer, not a guarantee, and let the cap be your primary control.

Reconciling each card against its booking and tracking commission

This is the part that gives owners their evenings back. Because each card is named for one booking and every charge posts with that reference, reconciliation becomes a one-to-one match: one card, one booking, one settled charge, one receipt. You are no longer splitting a pooled statement across every trip you ran that month.

It also keeps commission tracking clean. When the supplier payout is isolated on its own card, you can confirm the net rate you actually paid against the price the client paid, and your commission ties out without guesswork. If reconciling supplier payments is a recurring pain across your back office, the same one-to-one discipline is what powers virtual cards for accounts payable.

Paying international suppliers in their currency

Plenty of agencies pay overseas hotels, DMCs, and ground operators. You can issue cards to pay international suppliers, and the card works wherever that supplier accepts Visa. Currency handling and any conversion terms follow the Zil Money platform, so review the current multi-currency support in-platform before you lean on it for a corridor that matters to your margin. The point for reconciliation is the same in any currency: one card, one booking, one matched charge.

Issuing cards in bulk for high-volume agencies

If you book at volume, creating cards one at a time is not the workflow. You can create many cards at once from an Excel or CSV upload, one row per booking with its own cap, or issue them programmatically through the API so a card is generated as each booking is confirmed. Each card still carries its own cap, its own booking reference, and its own receipts. See how to issue virtual cards in bulk for the spreadsheet and API workflow.

For a single recurring supplier you pay over and over, a reloadable card with a standing cap can make more sense than a fresh card per booking. The trade-off between a one-time card per booking and a reusable card for a recurring supplier is covered in single-use vs reloadable virtual cards.

How per-booking cards compare to a shared card and BSP cash

Most agencies are choosing between a few real options, not reading a feature list. Here is how they stack up on the things that actually bite.

A real example: one hotel booking, one capped card

Here is a booking walked end to end. A client books a three-night stay. The hotel quoted a net rate of $840, which is $280 a night for three nights. Your commission is built into the client price and never touches this card.

Chargebacks, refunds, and cancellations: what a virtual card changes

A virtual card does not replace your dispute rights, and it does not make refunds disappear. If a supplier needs to refund, they refund to the same card and the money returns to your wallet balance. If a booking is cancelled, cancel the card so no new charge can land, while remembering that a charge already authorized can still settle.

What the card does change is your exposure. Because each card is capped to one booking, a single disputed or duplicated charge is bounded by that card's limit, not by the credit line on a shared account. You contain the problem to one booking instead of one card number that touches every trip you run.

Mistakes to avoid

People also ask