Kaptio Edge Documentation
Edge is the customer-facing layer of the Kaptio platform. It turns the bookings, itineraries, and pricing in your Salesforce org into branded documents your guests can view and payments they can complete — driven by configuration, not code.
Edge Docs
Branded travel documents — proposals, confirmations, invoices, commission documents, travel packs — generated from your Salesforce data and delivered through a secure online viewer.
Edge Journeys
Configurable booking experiences — trip selection, cabin choice with deck plans, activities, payment, and confirmation — driven by tenant YAML and a React UI you own.
Edge Portal
Pre-departure guest portal — readiness tracking, live itinerary with progressive release, forms and on-device passport capture, payments, and extras, with a travel-agent workspace and an operations console.
Edge Pay
Payment collection from guests and agents through configurable payment pages — payment links, call-center flows, deposits and schedules, multi-currency and multi-brand routing.
Edge Webforms
Website enquiry intake — turn form submissions into scored, deduplicated Trips in Salesforce, with configurable field mapping, dedup rules, and priority routing.
Kaptio Experiences
Trip-scoped optional experiences and gratuities sales — guests buy excursions for their booked tour, Tour Directors sell on tour, and finance runs settlement, export, and reporting. Every capability is a documented REST API.
Edge Connect
One connection, growing catalog. Reach established supplier services today and add native connectors through a faster, fixture-first delivery path.
Architecture & Security
How Edge is hosted and secured — services, data flow, authentication, encryption, tenant isolation, and payment security. Start here for a technical or security review.
How this documentation works
Everything here is anchored on a single worked example: Meridian Travel Co., a fictional tour operator with UK and US brands. Meridian is the reference implementation every real tenant starts from — when you onboard, your configuration begins as a copy of Meridian's, and you customize it from there. Every configuration snippet, schema, and template excerpt in these pages comes from that reference implementation. What you read here is what you fork.
Where to start
How tenants work The configuration model behind every implementation
Owning your configuration Everything is editable — manage it yourself in your own repo
Fork playbook Turn the reference baseline into your tenant
Rebranding Swap the brand layer without touching templates
QA & verification The test contract every change must pass
Security FAQ Quick answers for a security or IT questionnaire
Document data reference The data contract for each document type
payment.yaml reference Every payment capability, block by block
journey.yaml reference Every booking-experience parameter, block by block
Experiences API reference Every optional-sales capability as a documented REST endpoint