Customers increasingly want to book travel where they already pay. For a wallet or bank, travel is a feature — not a business it wants to build from scratch. Avunzo puts flights and hotels behind one API, in the partner's own brand and checkout.
01 · The problem
The problem
Building travel in-house means supplier contracts, GDS and NDC integrations, ticketing arrangements and a servicing operation for changes and refunds — far from the core business.
- Many suppliers to contract and integrate
- Ticketing and servicing expertise required
- Payment risk on high-value bookings
- No view of the revenue travel generates
02 · Why it's hard to fix
Why it's hard to fix
Travel is operationally heavy
Changes, refunds and disruptions need a servicing operation behind the app.
The brand must stay yours
Customers should never feel they've left the app.
Two payment worlds
The partner's checkout has to settle cleanly with the travel supply side.
03 · What we built
What we built
The partner integrates once with Avunzo: search, price, book and manage, with webhooks for anything that changes after booking. Payment stays in the partner's checkout; Voraal handles supplier connections, ticketing and servicing. Folio6 reports the channel's bookings, revenue and margin.
- One API and one commercial agreement
- Partner's own UI, brand and payments
- Webhooks for ticketing, changes and refunds
04 · How it works
How it works
- 1
Search in the app
The partner's app calls Avunzo for live offers.
- 2
Pay in the partner checkout
Wallet, card or other methods on the partner's rails.
- 3
Ticket and confirm
Voraal issues and confirms through the right supplier.
- 4
Service and report
Changes arrive by webhook; revenue appears in Folio6.
05 · What changes for the team
What changes for the team
| Before | With Voraal |
|---|---|
| Many supplier contracts and integrations | One API, one agreement |
| A servicing team to build | Ticketing and servicing on the Voraal core |
| Customers leave the app to book travel | Travel inside the app's own checkout |
| Travel revenue invisible | Bookings, revenue and margin per channel |
06 · What it does not do
What it does not do
- Licensing requirements depend on the partner's market and model; options are reviewed during discovery.
- Who speaks to the customer for servicing is agreed during set-up.
- Supplier coverage is confirmed for the partner's markets before launch.
See it on your own bookings.
