A virtual card per booking for supplier pay

A lot of supplier payment in travel happens one booking at a time, and a lot of it happens by card. You confirm a reservation, you pay the hotel, the ground handler or the DMC, and you move on to the next booking. Done across hundreds of reservations on a shared company card, this quickly turns into a mess: a statement full of charges in mixed currencies that someone then has to match back to individual bookings, with no easy way to control how much was spent against any single reservation.

A cleaner model treats the booking as the unit of spend. You issue a virtual or single-use card number for one reservation, set its limit to that booking's supplier cost, and let it be used only for that payment. Each charge then carries the booking's identity with it. This is business-to-business pay-the-supplier-per-booking, using single-use card numbers and lodge cards, and it is a reconciliation and control story, not a tale about declined cards. This guide explains how it works and why it helps.

The booking as the unit of spend

When the booking is the unit, the card follows the reservation rather than the other way round. Instead of one shared card absorbing every supplier charge, you generate a dedicated card number for each booking. Its limit matches what that booking should cost the supplier, and its life is tied to that single payment. If a supplier tries to charge more than agreed, the limit stops it; once the payment is made, the number has done its job.

That one-to-one link is what makes the difference. Every charge on that card belongs unambiguously to one reservation, so there is never a question of which booking a payment relates to. You can issue numbers per booking at the scale you operate, giving each hotel, ground handler or DMC payment its own controlled instrument rather than routing everything through a single point of exposure that is hard to reason about after the fact.

Control and reconciliation

Two pains ease at once. On control, a per-booking card carries its own spend limit and can be restricted so it works only where it should, which contains what any single supplier can take and limits the damage if a number is mishandled. You decide the ceiling per booking rather than trusting a shared limit that any charge can draw against. On reconciliation, because each card maps to one reservation, matching the charge back to the booking stops being detective work; the payment arrives already labelled.

Currency is the third pain. Paying a destination supplier on a card that converts at the point of sale typically applies a margin above the mid-market rate, so paying in a currency you do not hold leaks cost on every booking. Treat any specific figure as illustrative and check current terms. Being able to pay in the supplier's own currency, from a matching balance, keeps that leakage down and keeps the amount on the card aligned with the cost you actually agreed.

Who can issue and how it scales

Per-booking issuance only works at volume if issuing a card is quick and controlled. You want the people who confirm bookings to be able to spin up a card for a reservation within sensible bounds, without that turning into a free-for-all on company spend. So alongside the cards themselves you need control over who can issue them and within what limits, so issuance scales with your booking volume rather than becoming a bottleneck or a risk.

Not every payment is online, either. Operations staff sometimes need to settle something in person at the destination, so physical cards with the same limits and controls round out the picture. The goal across virtual and physical is consistent: every payment is tied to a purpose, capped at a sensible amount, made in the right currency, and traceable afterwards, whether it was issued for one online booking or carried by a team member on the ground.

How Altery fits

The core tool here is virtual cards with per-card spend limits and merchant controls, issued per booking so each supplier payment is tied to one reservation and capped at its cost. Because you can pay on a multi-currency card in the supplier's own currency, often from a matching balance, you keep the FX leakage that comes from converting at the point of sale to a minimum. Rich transaction data on every card makes booking-level reconciliation straightforward, since each charge already carries the booking it belongs to. The wider travel toolkit is at our travel business account.

For payments that have to happen in person at a destination, physical business cards carry the same limits and merchant controls as the virtual ones. And team roles let you decide who can issue cards and within what bounds, so per-booking issuance scales with your volume without becoming a control gap. Altery is not a bank, and this is general information, not advice; the underlying supplier obligations remain yours, so treat this as help controlling, paying and reconciling per booking, not as changing what you owe.

Frequently asked questions