Occupancy-tiered pricing
The price sent to the channel can step up with salon occupancy: as it fills, the next tier takes over.
A booking from a sales channel (GetYourGuide is live today; Viator, Klook and Headout are on the roadmap) lands in the panel, an iyzico payment is posted to the account, and the e-Invoice goes out at day-end. Which connection is live, which is in progress and which is on the roadmap — it is stated plainly below.
Agentora01Channels
We built an integration against the GetYourGuide Supplier API: availability, booking, cancellation and pricing flow both ways. A booking from the channel becomes a regular reservation in your own records.
The integration was built against the GetYourGuide Supplier API. Connecting your account is subject to GetYourGuide’s own approval process.
get-availabilitiesreservebookcancel-bookingnotifyThe availability a channel asks for is calculated from salon capacity and existing reservations.
A reservation is held first, then confirmed. The confirmed record appears in the panel as a reservation.
When the channel cancels, the linked reservation in the panel is cancelled automatically too.
Price and availability changes are sent to the channel (notify), so what it shows stays current.
The channel’s retail price is written to the channel account (cari).
The price sent to the channel can step up with salon occupancy: as it fills, the next tier takes over.
GetYourGuide calls a single address. Agentora routes each request to the right business from the supplier code it carries; the multi-supplier setup exists for this.
Outgoing syncs and incoming channel requests are logged. Channel keys are stored encrypted with AES-256-GCM.
Not live yet. Groundwork for these channels is on the roadmap; they are not live yet. If you need another channel, tell us.
02Payments
Two payment providers are live today: iyzico and Garanti BBVA virtual POS. Card details are entered on the payment provider’s own page and are never stored in Agentora at any stage.
Create a payment link for a reservation or an account from the panel and send it to the customer by copying it, via WhatsApp or by email.
A tracked link is tied to a reservation or account and the payment shows up in the panel. An untracked link is a free-form collection link; its payment is followed in the Movements report.
Card payment with 3D Secure; the set-up is separate for each business. On the online booking page, card payments are taken with iyzico or Garanti.
A payment link is created for the reservation.
The guest enters the card on iyzico’s page.
iyzico notifies, Agentora verifies the payment.
webhookVerifiedSemi-automatic: you confirm the collection.
Card data is never stored in Agentora.
The payment layer is provider-agnostic by design: the architecture is open to adding another virtual POS or payment provider. If you use a different one, write to us and we’ll look at it together.
03Invoicing & FX
The two legs of the day-end flow: invoices enter a queue and go out through Nilvera, and central-bank rates are ready at day opening.
Documents sent from the panel enter a queue; failures are retried and the tax-authority status is synced. Incoming invoices can be imported.
Central-bank rates are fetched automatically at day opening. Fetching rates is also part of the day-end steps.
04Maps & location
Transfer operations rest on two map services: Google Maps (Directions) for route and estimated arrival, and OpenStreetMap-based Leaflet for live driver tracking.
Turned on in business settings. Route and duration are calculated for the remaining stops and recalculated as order or status changes. When it is off, the system keeps working; only the ETA is not shown.
Once a driver taps “Start transfer”, their location appears on the map: driver name, plate and the last hour’s trail. Tracking stops when the shift ends.
05Messaging
Email and mobile/web push notifications are live. WhatsApp exists only as a share link; there is no WhatsApp Business API and no SMS integration.
Reservation confirmation, password reset and the day-end report go out by email.
Expo push in the mobile app, Web Push (VAPID) in the web apps. A driver gets “New transfer” when an assignment changes; a waiter gets a kitchen-ready notice.
wa.me links to share the reservation card and driver contact on WhatsApp. The user sends the message from their own WhatsApp; this is not a WhatsApp Business API integration.
06Hardware
A Windows-based print agent drives the bar and kitchen printers on board. Thermal tickets print over ESC/POS with Turkish character support.
Print jobs enter a queue; the agent prints them on the Windows computer the printer is attached to. Reprint and a bulk “Print kitchen” action are included.
Ticket templates are designed for 58 and 80 mm: block layout or free canvas. Turkish characters print with the CP857 code page.
The kitchen screen is separate: it is a page that opens in a browser and needs no special hardware.
07Protection
Cloudflare Turnstile filters out bots on web sign-in and the online booking flow. The other layers — account lockout, rate limiting, screen lock — are on the Security page.
Security & architectureSign-in and online booking forms verify a human; automated malicious attempts are stopped at the door.
08Build on it
Channel integrations sit on a shared layer: channel accounts, product mapping, price resolution, availability and sync logs are the same for every supplier; the supplier-specific part is an adapter. GetYourGuide is the first adapter on it; Viator, Klook and Headout are on the roadmap.
09FAQ
Wondering about something else? All questions are on the FAQ page; we can cover the rest in a demo.
All questionsYes. An integration with the GetYourGuide Supplier API has been built for availability, booking, cancellation and pricing; a booking from the channel lands directly in the panel and its linked reservation is cancelled automatically on cancellation. Connecting your account is subject to GetYourGuide’s own approval process.
The channel architecture is multi-supplier; groundwork for Viator and Klook is on the roadmap but not live yet. Tell us which channel you need.
iyzico (payment links, tracked and untracked links, refunds, posting to the account) and Garanti BBVA virtual POS (3D Secure) are supported. Card details are never stored in Agentora.
e-Invoice and e-Archive are issued through the Nilvera integration, with taxpayer lookup, a sending queue, retries, tax-authority status tracking and incoming invoice management. Invoices can be issued automatically at day-end.
Today email (confirmation, password reset, day-end report) and mobile/web push notifications are used. For WhatsApp there are share links for the reservation card and driver contact; there is no WhatsApp Business API or SMS integration.
Agentora
In a demo we go through the channels and payment methods you use and tell you plainly which connection is live today.