How to Give Sub-Agents Credit Without Getting Burned

You remember telling him the limit was 50,000 taka. He remembers you saying it could go a bit higher during Umrah season. Neither of you wrote it down, because he's been booking through you for two years and you trusted him — and now there's a booking that shouldn't have gone through, a customer waiting on a ticket, and an argument neither of you can actually win because there's no record to point to.

If you've built any kind of sub-agent network, some version of this has happened to you. It's not because you picked the wrong agents. It's because "credit" that lives in memory and notebook entries was never going to hold up once the network got big enough to matter.

This article looks at why informal credit arrangements fail in a predictable way, how the industry actually solves this with a prepaid wallet model, what that changes about your day-to-day relationship with agents, and how to grow a network city by city without it turning into a debt-collection job.

Quick answer: The way to give sub-agents credit without getting burned is to stop extending credit at all in the traditional sense — instead, agents top up a prepaid wallet, book against that balance, and bookings simply block when the balance hits zero, so there's never a debt to chase in the first place.

Why informal credit ledgers blow up

Every informal system has the same three cracks, and they all show up eventually.

Limits live in memory, not in a system. You told an agent their cap once, maybe months ago, maybe verbally. Nothing actually stops a booking from exceeding it — the fare gets issued and only afterward does anyone notice the agent is 30,000 taka over what they were supposed to have. By then the ticket is already in the customer's hand.

Entries get disputed because nothing is timestamped or confirmed by both sides. A notebook entry says an agent owes you for three bookings. The agent remembers paying for two of them in cash last month. Without a shared record both sides trust, this becomes a "he said, she said" argument that damages the relationship regardless of who's actually right.

There's no real cut-off. Even agents you like will occasionally push past what they can actually cover, especially during a rush — Eid travel, Umrah season, a sudden fare drop everyone's chasing. Without a hard stop built into the booking process itself, the only cut-off is you noticing and intervening manually, which means you're always reacting after the damage instead of preventing it.

Put together, these cracks mean the bigger your sub-agent network grows, the more exposed you are — not less. More agents means more entries to track, more disputes waiting to happen, and more chances that a limit gets missed at exactly the wrong moment.

The prepaid wallet model — the industry's actual answer

Most B2B travel portals that manage sub-agents at any scale converge on the same pattern, and it's worth understanding why it works rather than just adopting it blindly.

An agent funds their wallet in advance — by bank transfer, by depositing cash with you, through whatever payment method you accept, which is the same territory covered in payment gateway options for travel agencies. That balance is now real money, sitting in the system, not a number someone promised to honor later.

When the agent books, the fare comes out of that balance automatically. If the balance can't cover the booking, the booking simply doesn't go through. There's no judgment call in the moment, no awkward phone call asking whether it's okay just this once — the system enforces the limit because the limit is the balance, not a number someone has to remember and apply consistently.

This flips the entire emotional register of the relationship. You're no longer the person calling to ask for money that's overdue. You're the person an agent calls to top up, because they want to keep booking. The conversation changes from "you owe me" to "your balance is low" — one of those damages a relationship over time, and the other doesn't.

Per-agent margins and visibility

A wallet system does more than stop overexposure — it's also where your margin control actually lives. Each agent can have their own markup or margin structure rather than one blanket rate for the whole network, so your best-performing or highest-volume agents can get sharper pricing without you manually adjusting every quote.

Visibility matters just as much as the number itself. An agent should be able to see their own balance, their booking history, and what they've paid without calling you to ask — and you should be able to see, at a glance, which agents are close to zero, which are dormant, and which are driving most of your B2B volume. Without that visibility on both sides, you're back to phone calls and guesswork even with a wallet in place.

It's worth being upfront about something here: per-agent margin control isn't a feature every platform includes at every tier, and it's often gated to higher plans because it requires more granular pricing infrastructure than a flat markup does. If you're comparing platforms, ask specifically whether per-agent margins are included at the plan you're actually looking at, not just mentioned somewhere in the feature list.

From chasing debts to topping up wallets

The practical shift here is worth spelling out because it's the whole point. In the old model, your job as the "host" agency includes debt collection whether you wanted that job or not — calling agents, tracking who's behind, deciding when to cut someone off and how to say it without losing the relationship entirely.

In the wallet model, none of that is your job anymore. The system cuts off automatically, at zero, every time, without you having to be the bad guy. Your job becomes making it easy for agents to top up — clear balance visibility, fast deposit processing, maybe a low-balance notification — because a funded agent is a booking agent, and an agent who can't book isn't generating anything for either of you.

This also removes a source of resentment that informal credit quietly builds over time. Agents who paid on time used to subsidize, in a sense, the risk you carried on agents who didn't. A wallet model treats every agent identically — funded means you can book, not funded means you can't — which agents generally respect even when it means their own limit is stricter than the loose verbal arrangement they used to have.

Growing your network city by city, safely

Once credit risk stops being the bottleneck, expanding your sub-agent network becomes mostly a sales and onboarding question rather than a risk question. You can bring on a new agent in a new city without the exposure that used to come with extending them informal credit sight-unseen.

A few things make the expansion smoother:

• Onboard with a required minimum top-up, so every new agent has skin in the game from booking one.
• Watch early booking patterns, not just balance — an agent who tops up once and never books is different from one who's actively growing.
• Set margins deliberately per agent or per tier, rather than negotiating each one from scratch, so new agents in new markets get consistent, defensible pricing.
• Keep the top-up process as frictionless as the booking process — an agent who has to jump through hoops to add funds will book less, not because they don't want to, but because the friction discourages it.

None of this eliminates every risk of working with sub-agents. It removes the specific risk that used to blow up relationships — the disputed ledger, the memory-based limit, the moment someone finds out they're owed more than they thought.

FAQ

What's the difference between a sub-agent wallet system and traditional credit terms? Traditional credit means the agent books first and pays later, up to a limit you have to track and enforce manually. A wallet system reverses this — the agent funds a balance first, books against it, and the booking simply can't happen past zero, so there's no debt to track or chase.

Can I still offer different pricing to different sub-agents with a wallet system? Yes — per-agent margin control is usually part of a proper B2B travel portal, letting you set different markups or margins per agent rather than one rate for everyone. Note this is typically a feature on higher platform tiers, so confirm it's included before assuming it's there.

What happens if a sub-agent's wallet balance runs out mid-booking? The booking simply doesn't process past what the balance can cover — there's no partial booking or manual override needed. The agent sees their balance is insufficient and tops up before trying again, which removes the need for you to intervene case by case.

Is a wallet system only useful for large sub-agent networks? No — even two or three sub-agents benefit, because the value isn't scale, it's removing ambiguity. A funded balance with a hard cut-off protects the relationship whether you're managing three agents or thirty.

The honest way out of this

Building this yourself with spreadsheets and manual top-up tracking is possible, but it's the same fragile system with extra steps. OTAPress ships with wallet-based B2B agent accounts and per-agent margins on Enterprise and above, so agents top up, book against their balance, and get blocked automatically at zero — with full visibility for you and for them. If you're weighing whether this fits how your network actually works, the live demo at demo.otapress.com shows the agent wallet flow directly, and otapress.com has the full breakdown of what's included at each plan.