Integrations
UnityTrip sits above the systems you already run. It pulls commercial and private travel content, syncs finance, HR, fleet and accommodation data, and brokers payments — all through an event-sourced integration layer that connects without brittle, tightly-coupled point-to-point links.
Source the cheapest fares and richest commercial content through the industry-standard GDS and NDC channels, and show it alongside your own private and chartered schedules — so bookers see owned, leased, and commercial options side by side in one search. The content source is selected to fit each client.
Send data to — and receive data back from — SAP for financial, HR, and identity information, over SAP RFC (Remote Function Call). RFC function calls are personalised with each client. How SAP integration works ↓
Connect vehicle and asset data so ground transport and fleet capacity are planned in the same place as air and sea — not managed in a disconnected spreadsheet.
Coordinate guesthouse and remote-site accommodation alongside travel, so a rotation's flights, transfers, and lodging live on a single itinerary.
Multiple payment gateways, brokered intelligently. Different bookers can choose their preferred gateway for a smoother experience and greater resilience — and a self-correcting broker prevents the double-charge and double-book problems that plague last-seat bookings. How the payment broker works ↓
Payments
UnityTrip brokers payments across multiple gateways — Stripe and Paystack — and lets each booker use the one they prefer. That means a better experience for travellers and a fallback if a single provider has a bad day.
When two people race for the last seat, the broker self-corrects: it silently reverses the losing charge instead of leaving someone paid but seatless. One operator cut roughly ten support escalations and manual reconciliations a month — each of which had been taking three to four hours.
Each booker selects a preferred gateway — Stripe and/or Paystack — improving conversion and giving you provider-level resilience.
Race conditions on the last seat are resolved automatically. The losing charge is reversed without a support ticket or a manual reconciliation.
Every payment event is recorded on the event-sourced core, so reconciliation is a query — not a forensic exercise across two systems.
How it works
Integrations use a change-feed pattern on an event-sourced core. UnityTrip reacts to changes in connected systems rather than constantly polling them, and avoids the tightly-coupled point-to-point links that make integrations fragile when a source system changes. New connections — across GDS, ERP, HR, finance, fleet, and accommodation — can be added as needs grow.
See the architecture for how the event-sourced core works, or the webhook reference to build your own receiving integration.
FAQ
UnityTrip integrates with commercial travel content over GDS and NDC, SAP for financial, HR and identity information, Chevin FleetWave for fleet management, Elina PMS for accommodation, and the payment gateways Stripe and Paystack. Connections are built on an event-sourced change-feed pattern, and new systems can be added as needs grow.
The SAP integration uses SAP RFC (Remote Function Call). RFC function calls are personalised with each client, because each organisation's SAP configuration differs. It is fully bidirectional — sending data to SAP and receiving data back across financial, HR, and identity information. It's a tailored integration rather than a single turnkey connector.
UnityTrip sources commercial fares and content through the industry-standard GDS and NDC channels, integrated against their standardised specifications. The specific content source is selected to fit each client. Bookers see commercial options alongside owned, leased, and chartered schedules in a single search.
Yes. UnityTrip brokers payments across Stripe and Paystack and lets each booker choose their preferred gateway, improving conversion and giving provider-level resilience. A self-correcting broker reverses the losing charge when two people race for the last seat, preventing double-charges and double-bookings. One operator cut roughly ten support escalations and manual reconciliations a month, each taking three to four hours.
Yes. The integration layer uses an event-sourced change-feed pattern designed to extend to new GDS, ERP, HR, finance, fleet, and accommodation systems without brittle point-to-point coupling. Tell us what you run and new connections can be added as needs grow.
The integration layer is built to extend. Tell us what you run, and we'll talk through how UnityTrip connects to it.