Travel
What Corporate Travel Platforms Need From a Payments Stack
Let's compare business travel payment models, from lodge cards to virtual cards, and what each one demands of the booking layer.
TL;DR
Travel platforms should evaluate payment providers on four things general comparisons ignore: when settled funds become usable, what specifically triggers a reserve or payout hold, who carries dispute liability after the trip, and whether supplier payouts run through the same integration as acceptance. Rate matters least of these, because reserve drag, absorbed disputes, and declined bookings typically cost more in aggregate than the difference in basis points. Get every answer in writing before signing.
A sales cycle answers every question you ask
That is the trap. Providers are good at their jobs, the demo is sharp, the rate is competitive, and every question on your list gets a confident answer.
The damage in travel comes from the questions nobody thought to ask, because they are not on any general evaluation checklist.
Nobody asks what happens to settlement when a supplier goes insolvent mid-season. Nobody asks at what internal ratio a risk review starts, as distinct from the published network threshold. Nobody asks whether a record booking month reads as growth or as an anomaly.
Those answers exist. They are sitting in a risk policy somewhere, and they will govern your business far more than the basis points you spent three weeks negotiating. You just have to ask before you sign, because afterwards the answers arrive as events rather than as conversations.
The four criteria that actually separate providers
1. When your money becomes usable
Most processors settle on a T+2 rolling schedule, with weekends and holidays extending it further. For a platform paying suppliers, your settlement timing sets the floor on their payment timing. You cannot pay suppliers faster than you get paid.
2. What triggers a reserve
Travel operators commonly see reserves of 5% to 15% held for 90 to 180 days. At full accumulation that reaches one to two months of settled volume permanently outside the business, and it grows as you grow.
3. Who carries dispute liability
Merchant liability is the default almost everywhere. In a category where disputes have been growing around 30% year over year and the average dispute value is the highest of any sector, that default is expensive in a way the rate card never shows.
4. Whether pay-in and payout are one system
An acquirer plus a separate payout vendor means two integrations, two compliance relationships, two reconciliation feeds, and a foreign exchange spread that is rarely itemized.
Price the leaks, not the basis points
See what settlement timing, reserves, and absorbed disputes cost against your booking volume.
Try our savings calculatorThe questions you should be asking
Get these answered in writing. Verbal reassurance during a sales cycle has a way of not surviving your first disrupted season.
On settlement and reserves
- What is your standard settlement schedule, and what does accelerating it cost? An instant payout option carrying a percentage fee is a different product from settlement timing you control at no premium.
- Under what specific conditions would you apply a reserve or hold payouts? Ask for thresholds and percentages, not philosophy.
- If a reserve is applied, what is the review process and who initiates it?
- Does a strong booking season count as a volume anomaly in your risk model?
On disputes
- Who absorbs the loss on a disputed transaction, and what exactly does any coverage exclude? Chargeback protection and chargeback indemnification are different products. Ask which one is on offer.
- What dispute tooling is included, and does it require a third-party vendor?
- How do you handle the seasonal dispute clustering that follows peak travel periods?
On offboarding
- What is your offboarding process and what notice do I get? Merchants terminated for excessive disputes can end up on the Mastercard MATCH list, which makes finding a replacement acquirer materially harder.
- At what internal ratio do you begin a risk review, as distinct from the network threshold?
On payouts and reach
- Which countries can you pay suppliers in, on which local rails, and how fast? International wire is coverage on paper; local rails are coverage in practice.
- How is foreign exchange priced, and is the rate visible to me before conversion?
- Can I run virtual card issuance and direct settlement through the same integration?
Where the money actually leaks
Rank the costs by size for a platform booking $3M a month and the ordering is counterintuitive.
Twenty basis points of rate difference comes to $6,000 a month. Genuinely worth negotiating, and it is where most evaluations spend their energy.
Five points of cross-border authorization rate on $14M of annual international volume is around $700,000 in bookings that never converted. A 10% reserve on a 120-day hold ties up roughly $1.2M in working capital indefinitely. A 1% dispute rate absorbed rather than indemnified runs into six figures a year once fees and labor are counted.
So the line everyone compares carefully is roughly a tenth the size of the lines nobody models. Total cost of processing is the frame that fixes this: rate plus declines plus disputes plus reserve drag plus float plus the overhead of every additional vendor. A provider that undercuts on rate while performing worse on the other five is more expensive, usually by a wide margin.
Where Coinflow fits
Coinflow fits platforms where money movement is the product rather than a checkout feature.
- You choose when each supplier gets paid: at booking, at check-in, or on net terms, set per supplier, without pre-funding it yourself.
- Chargeback indemnification covers fraud and chargebacks on approved card-not-present transactions.
- Pricing is transparent interchange-plus with no rolling reserve, so a strong season does not build a withheld balance.
- Pay-ins, payouts, and foreign exchange run through one API, with payouts reaching more than 170 countries.
How a provider treats the category matters as much as the product. A strong booking season doesn't trigger a hold or a reserve here, and merchants get a named contact reachable before a metric becomes a problem rather than a notification after the decision is made.
Get the answers you need before signing
If you're running an evaluation now, talk to our team and put us against these same questions.
Talk to our team →Frequently asked questions
Can a travel platform run two payment providers at once?
Yes, and at scale it is often the right structure. A primary acquirer with a secondary path gives you redundancy, lets you compare authorization rates on real traffic rather than on sales claims, and reduces the damage if one provider changes your terms. The cost is additional reconciliation, so most platforms route by source market or card type rather than splitting traffic randomly.
Does switching providers reset my dispute history?
No. Network monitoring ratios are calculated per merchant identifier, and any new acquirer will request your processing and dispute history during underwriting. A provider suggesting otherwise is worth a second look. What switching can change is who absorbs future losses and what terms you operate under going forward.
How long does it take to migrate a travel platform to a new provider?
For straightforward card acceptance, days to a few weeks. Travel platforms with supplier payouts, multi-currency settlement, and virtual card issuance take longer, typically several weeks to a couple of months depending on engineering capacity. Avoid cutting over immediately before peak booking season, and ask whether the provider assigns a named integration engineer, since that changes timelines more than API quality does.
This content is for informational purposes only and does not constitute financial, legal, or investment advice.
