Those are not the same thing, and conflating them would be misleading.
So the platform now communicates cancellation in terms of service status: the booking is cancelled, and any applicable credit or adjustment is handled through the billing arrangement. It no longer implies a direct traveler refund where that is not actually the right commercial interpretation.
Small wording change. Matters a lot for trust.
How we know it actually works
The thing I am most satisfied with this week is not just the feature list.
It is that we did not stop at "it works locally."
We exercised the full booking lifecycle — booking, changing, cancelling, and handling airline-driven changes — against live provider responses, step by step, until we had confirmed outcomes for every scenario.
That shifted the project from "we think this works" to "we know these core flows work."
There is a meaningful difference between code that looks correct and a system that has been proven to behave correctly under real conditions. This week we crossed that line for the servicing layer.
What is next
The immediate next track is operator tooling: giving the people running travel programs visibility into booking settlement, billing data, and the ability to manage their travelers' bookings with confidence.
The AI agent layer is now in a healthy place.
Now the work is turning that foundation into a full product for the humans operating on top of it.
More soon.
Almin Zolotic is the founder of Zologic and building ucp.travel — an agentic travel stack that lets AI agents search, book, change, and cancel flights autonomously. Follow the build here on dev.to.