Sub-Agent Wallet and Credit Limit Management for B2B Travel Portals

On a B2B travel portal, each sub-agent usually books against either a prepaid wallet (a deposit they top up in advance) or a credit limit (an amount you allow them to owe and settle later). Managing the sub-agent credit limit on a travel portal properly means the system checks available balance before every booking, blocks or holds bookings that exceed it, records every debit and credit in a clear ledger, and gives your finance team control over who gets credit and how much. For UAE consolidators and B2B agencies serving hundreds of sub-agents across the GCC and South Asia, this is where cash flow is protected or lost.

This guide explains how wallets and credit limits should work, the controls that prevent bad debt, and the reconciliation that keeps finance and the portal in agreement.

Wallets versus credit limits: which model to use

Most B2B travel portals in the UAE support both models, and many sub-agents use a combination: a wallet for day-to-day bookings with a modest credit facility on top for trusted partners.

• Prepaid wallet — the sub-agent deposits funds by bank transfer, card or payment link, and bookings are deducted from the balance. Your risk is low because you hold the money before you issue anything.
• Credit limit — the sub-agent can book up to an agreed amount and pays on a schedule, weekly, fortnightly or monthly. This helps volume but exposes you to non-payment.
• Hybrid — the wallet balance is used first, with credit available beyond it up to a limit. This is common for established partners.
• Pay per booking — the sub-agent pays each booking by card at checkout. Simple, but card fees eat into thin flight margins.

Newer partners typically start on wallets, and credit is extended as trust builds. The software should make that progression simple and auditable.

Setting a sub-agent credit limit: travel portal controls that matter

Credit control in travel is unforgiving because many products, especially airline tickets, commit you to paying suppliers quickly. When an IATA-accredited agency issues a ticket, it becomes liable to settle it through the BSP cycle regardless of whether the sub-agent pays. The portal's controls have to reflect that reality.

Controls to build in

• Real-time balance check — before any booking is confirmed or ticketed, the system checks wallet plus available credit against the total, including fees.
• Hold on insufficient funds — where suppliers allow, bookings can be held without ticketing until funds arrive, with clear expiry times.
• Product-level limits — you might allow credit for hotels with free cancellation but require funds upfront for non-refundable tickets.
• Temporary limit increases — finance can raise a limit for a peak period or a large group, with an end date and an approval record.
• Overdue blocking — if an invoice passes its due date, new bookings are blocked or restricted automatically until the account is settled.
• Approval workflows — limit changes above a threshold require a second approver, and every change is logged with user and time.

These controls only work if the whole team trusts the numbers. If sales staff can quietly override a block to keep a big partner happy, the control is decoration.

Top-ups, deposits and payment reconciliation

Wallet top-ups are a constant source of admin. A sub-agent transfers money, sends a screenshot on WhatsApp, and someone in finance has to match it to a bank statement and credit the wallet. Multiply that by hundreds of partners and it becomes a job in itself.

A better process reduces manual steps:

1. Online top-up — sub-agents can top up by card or payment link inside the portal, with the wallet credited automatically when payment is confirmed, net of any agreed fees.
2. Unique references for transfers — each sub-agent gets a reference to use on bank transfers, so incoming payments can be matched to the right account.
3. Bank statement import — finance imports or connects bank statements, and the system suggests matches for review.
4. Approval and credit — once matched, the deposit is approved and the wallet updated, with a notification to the sub-agent.
5. Exceptions queue — unmatched payments go to a queue rather than sitting in someone's inbox.

Card top-up fees and chargeback risk need thought. A sub-agent topping up a large amount by card and later disputing it can cause real losses, so limits on card top-ups and checks on unusual activity are sensible. Our article on fraud prevention for online travel bookings in the UAE covers the warning signs.

The sub-agent ledger and statements

Every movement on a sub-agent account should appear in a ledger: top-ups, bookings, cancellations, refunds, amendments, fees, commissions and manual adjustments. Each line should link back to its booking or payment. Sub-agents should be able to see their own statement and download it, which cuts down on "please send our statement" requests considerably.

Refunds are the area most likely to cause disputes. When a ticket is cancelled, the refund to the sub-agent's wallet should reflect the airline's refund rules, any cancellation fees and your own service charges. If refunds are credited before the supplier refund is confirmed, you carry the risk. The commission and markup side also matters; see our article on markup and commission management for UAE travel portals for how those amounts should be recorded so ledgers stay correct when bookings change.

Linking the portal to accounting

The portal ledger and the accounting system must agree. Ideally, sub-agent balances in the portal are the receivables in your accounts, synced automatically rather than re-entered. VAT on service fees and the treatment of deposits held should be agreed with your accountant and tax adviser, and the system configured to follow that advice consistently.

Reports and alerts for credit control

To keep every sub-agent credit limit on your travel portal under control, finance teams and owners need a small set of views they can check daily:

• Exposure by sub-agent — current balance, credit used, overdue amounts and recent booking volume.
• Ageing report — amounts outstanding by 0–15, 16–30, 31–60 and over 60 days.
• Low balance alerts — automatic emails or WhatsApp messages to sub-agents when wallets fall below a set level, before bookings fail.
• Limit utilisation — partners consistently near their limit may deserve an increase, or a conversation.
• Unusual activity — sudden spikes in bookings, especially non-refundable tickets, from accounts with low history.

Peak periods such as Eid and the summer holidays deserve special attention. Booking volumes rise, sub-agents ask for temporary limit increases, and exposure can grow quickly. Reviewing limits ahead of each peak is good practice.

Buying a portal versus building wallet and credit features

Most white-label B2B travel portals include basic wallet and credit functions, and for many agencies they are enough. Where they fall short is usually in approval workflows, product-level rules, bank reconciliation and accounting integration. Those gaps can often be closed by building the missing pieces around the existing portal rather than replacing it. If credit control is a recurring source of losses or manual work, it is worth reviewing as part of your wider travel and tourism technology setup.

Zellarc approaches wallet and credit projects by sitting with the finance team first. The controls that matter are the ones finance actually uses, and the best system is one where the portal balance, the bank and the accounts all show the same number.