Skip to content

Close high-ticket trips, no reserve call

Bill each stage over a payment link and take it in stablecoins — the client signs the deposit and every installment, the funds are credited in minutes, and you wire the lodge deposit the same day instead of waiting out an acquirer's hold.

Close high-ticket trips, no reserve call

Where bespoke agency margin disappears on card rails

Why does closing a high-ticket trip put your cash and margin at risk?

Four ways card rails and legacy systems thin out bespoke travel margin — the fee on a big ticket, account-level reserves, stacked GDS segment fees, and cross-currency on international clients.

The card fee scales unkindly on a high-ticket trip

Bespoke trips run from a few thousand into six figures, and a percentage-plus-fixed card fee scales straight up with them. On a standard 2.9% + $0.30, a $25,000 safari costs about $725 to accept; an $80,000 cruise costs roughly $2,320. For a luxury agency closing a hundred such trips a year, that's the budget for a senior trip designer — and high-risk travel acquirers often charge more. (Side-by-side in Pricing.)

Acquirers apply reserves account by account on agency volume

Card acquirers price travel agencies into elevated-risk categories and hold back a reserve per merchant — neither the percentage nor the duration published in advance. On new accounts and high-ticket volume, those decisions tend to land when working capital matters most: paying deposits to lodges, charter operators, and on-the-ground guides. ARC-accredited US agencies hit additional BSP cash-settlement timing on top.

GDS segment fees stack on every flight leg

For the flight component of bespoke trips booked through Sabre, Amadeus, or Travelport, GDS segment fees add a per-leg cost that compounds across a multi-segment itinerary. That GDS cost itself doesn't move with how you take payment — but the card-processing fee stacked on top of it is the leak that disappears on the wallet rail.

Cross-currency margin on international clients

The London agency selling a six-figure Tanzania safari to a US client gets hit with 1–2% in cross-currency margin on the conversion — real money per booking the agency never sees, at a rate the processor sets. The same agency selling an Antarctic expedition to a German client takes the same hit. The international clientele that justifies the agency is also where the rate markup compounds.

How bespoke agencies work in stablecoins

What changes when the trip settles in stablecoins?

Run the bespoke trip's payments on a wallet, and four card-rail drags on cash and margin lift.

Your money settles in minutes, with no reserve held back

A bespoke booking confirms on Paymos and is credited to your Paymos balance balance in minutes on most networks — no acquirer reserve, no per-account holdback, no working-capital trap during peak booking season. You can pay lodge deposits the same day the client pays, which is how bespoke agencies actually want to operate.

Deposit plus balance, paid over a sequence of links

A bespoke cruise usually splits into a deposit at booking and a balance closer to departure. Paymos handles it as a sequence of payment links — one per stage, each with its own deadline and external_order_id. The client signs the deposit today and each installment as it falls due, with no card on file holding the balance hostage to expiry or a reissued number.

No cross-currency markup — the agency keeps the difference

The London agency selling to a US client receives a dollar stablecoin and pays out the same stablecoin to lodges that accept it — no cross-currency conversion margin. For lodges that don't, you manage the conversion in your own treasury, at your own rate, capturing the markup that used to live in the processor's margin.

Roughly $250 to accept a $25,000 safari, not $725

That same $25,000 safari costs about $250 to accept on Paymos instead of roughly $725 on a card processor — and you keep the difference on every booking, with no per-transaction minimum, no high-risk surcharge, and no separate currency-conversion charge. Full rate card in Pricing below.

Bespoke agency flows on stablecoins today

What agency patterns run cleanly on a wallet?

Four flows from working bespoke agencies — safari, luxury cruise, corporate retreat, and loyalty.

Africa safari deposit — Payment Link from CRM

The classic luxury bespoke: a private safari with a deposit at booking. The trip designer generates a payment link from inside the CRM and sends it to the client, who pays from their wallet. The designer gets a webhook, and the lodge deposit is wired the same day from the agency's treasury — no acquirer reserve sitting between the client's payment and the supplier's.

Luxury world cruise — multi-stage Payment Links

A premium cruise booking paid over several installments from booking through to departure. Each stage is its own payment link, and the client signs each as it falls due. The whole schedule clears without a card on file expiring mid-process, and every stage is final the moment it confirms.

Corporate retreat — Hosted Checkout

The accessible-tier bespoke: a corporate offsite for a small team, more transactional than a full custom trip. Procurement gets a Hosted Checkout link and pays from a corporate wallet. The receivable closes on confirmation, with a real invoice attached and the money in your treasury the same day.

Loyalty membership — annual renewal invoice

An agency running a paid loyalty program for priority booking and partner-rate access. Each year your system issues a renewal invoice the member pays from their wallet — no card on file to expire and no involuntary churn. The membership just renews on its own cycle.

Travel agency bookings on stablecoins

Frequently asked questions

How does the deposit-plus-balance sequence work for bespoke trips?
You generate a payment link per stage, each with a stage-specific reference (deposit, milestone-1, milestone-2, balance) and your own external_order_id tied to the trip. The client pays each link as it falls due — they don't need to authorise the full amount upfront, unlike a card-on-file approach. You can adjust the schedule (move a milestone earlier or later) by issuing a new link and voiding the old one. No card-on-file expiry on long-lead bookings.
What about ARC commission splits and IATA BSP for the flight component?
The flight component of bespoke trips usually runs through GDS plus IATA BSP, or ARC for ARC-accredited US agencies. Paymos doesn't touch that — the BSP/ARC settlement is separate. The land component (lodges, ground operators, charter operators) settles through the agency's treasury wallet. For agencies that pay BSP/ARC from a fiat bank account, the stablecoin-to-fiat conversion is a treasury step; for agencies operating where suppliers accept stablecoins directly, the conversion is unnecessary.
How do partial refunds work when a bespoke client cancels mid-schedule?
Bespoke cancellations are rarely clean. A client may cancel after the deposit clears but before the next milestone, or two installments may already have settled with non-refundable supplier deposits behind them. Your bespoke cancellation policy (typically tiered by days-to-departure plus carved-out non-refundables) determines the refundable amount per stage. From your side, you initiate outbound transfers from your Paymos balance to the client's wallet for each refundable stage independently — full, partial, or zero per the contract. Paymos only charges its percentage on a settled stage; there's no extra platform fee layered onto a refunded stage. Travel-insurance proceeds for force-majeure cancellations settle outside the Paymos flow as today.
Can corporate clients pay net-30 with proper invoice attachments?
Yes. Generate a payment link with the trip total and send it with your own PDF invoice (from your CRM or prepared manually). The corporate buyer's AP team has the invoice for their books, pays the link from a corporate wallet on their net-30 cycle, and you receive the settlement event over webhook. This is the bespoke-corporate equivalent of net-30 invoicing without an ACH fee layered on top.
How does Paymos compare to wire transfers, which most bespoke agencies use?
International wires take one to five business days, cost the agency a fixed inbound fee, and require the client to chase bank details before each payment. Paymos settles in minutes, lives in a self-service link the client uses without back-office friction, and the inbound bank fee you used to absorb stays with you. For clients accustomed to "send a wire to this account," the Paymos flow is faster and cleaner on both sides.
What's the audit trail for bespoke transactions for accounting?
Every Paymos invoice is keyed to your order reference and client ID, so your system maps each settlement to its trip metadata (trip ID, stage ID, agency cost center). The HMAC-SHA256-signed webhook on confirmation includes the on-chain transaction hash, and the agency dashboard and API surface each settlement for accountant review. Tax handling (sales tax, VAT, travel-agency-specific levies) is the agency's responsibility — Paymos provides the data; the agency or its tax engine applies the right treatment.

Honest disqualifier

When NOT to use Paymos for travel agencies

Four agency setups where wires or card rails still fit better.

Client funds must be collected as fiat under your accreditation

Certain IATA arrangements require client money to arrive through BSP cash channels from a regulated bank account. Paymos credits a stablecoin balance and has no bank-payout leg, so meeting that mandate would mean converting every collection yourself before it counts. Where the accreditation dictates the rail, the accreditation wins.

Your suppliers invoice in fiat and you won't convert it yourself

Lodges, cruise lines, and DMCs mostly want wires in dollars or euros, while Paymos leaves you holding stablecoins in a wallet — the conversion between the two is a treasury process you own, on an exchange or OTC desk you choose. For an agency that doesn't want to operate that step, collecting by card or wire keeps the chain simpler end to end.

Your clients' money moves only through their AP department

Corporate travel paid through procurement platforms follows whatever those platforms automate — today that means cards, ACH, and wires. You can hand a payment link to a willing finance team, but you can't make an ERP grow a wallet. Quote the wallet rail to founders and family offices; bill the enterprise accounts the way their software insists.

Budget group tours sold to clients who've never held a wallet

A $900 coach-tour client who has never touched stablecoins needs onboarding before they can even pay you, and at group-tour margins that hand-holding costs more than the processing it saves. The bespoke clientele already moving money on-chain is where this rail shines; for the coach-tour book, the card form stays the shortest path to yes.

Pricing

1.0% per settled booking. No reserve calls, no rate markup

Same rate for the $5,000 corporate retreat and the $100,000 bespoke world tour — about $250 on a $25,000 safari versus roughly $725 on a 2.9% + $0.30 card processor, before any exchange-rate loss. High-volume tier at 0.3% on request.

See pricing

Close the high-ticket trip and keep the cash working that day