Payment integrations

Payments, calendar & bookings

How The Receptionist connects payments, Google Calendar, and your booking flow—without storing card numbers on our servers when you use your own providers.

Payment integrations

Merchants can connect their own payment accounts for customer checkout (POS and online booking). Money goes to the merchant’s provider; we send customers to the provider’s hosted flow or show a wallet QR where supported. Platform subscription billing may use separate platform-level settings.

Stripe

Card and wallet payments via Stripe Checkout. The merchant adds their Stripe secret key in Sales settings; customers complete payment on Stripe’s page. Successful payments are confirmed via Stripe’s session status and webhooks where configured.

Paytrail

Popular in Finland for cards and bank payments. Merchants use their Paytrail merchant ID and secret; customers pay on Paytrail’s hosted page. Return URLs bring the customer back while the gateway confirms the payment.

PayPal

Customers approve payment in PayPal; the app captures the order after return. Merchants configure PayPal REST credentials (sandbox or live) in Sales settings.

Fapshi

Mobile money and local methods where Fapshi operates. Merchants provide API credentials; customers follow the payment link. Webhooks help mark orders as paid reliably—do not rely on the browser alone.

Vipps MobilePay

Nordic wallet payments (ePayment API). Customers can open a payment link on their phone or scan a one-time QR for the same payment. Merchants use their sales unit keys; currency must match the Vipps sales unit. Register webhook URLs so payments are confirmed server-side.

Always treat webhooks and server-side verification as the source of truth for paid status. Return URLs improve UX but can be interrupted.

Google Calendar

Users can connect Google Calendar from their profile. We request read access so the system can see when you are busy and when you are free.

  • Busy times from Google Calendar are respected when suggesting appointment slots, so customers are not offered times that clash with your existing events.
  • Staff and booking flows can combine merchant availability with customer free time—for example when finding a slot that works for both sides.
  • You can disconnect Google Calendar at any time from your account settings.

Connection uses Google’s secure OAuth flow. Tokens are stored securely and refreshed as needed.

Bookings & your calendar

When a booking is confirmed, you can add it to any calendar that supports standard calendar files.

  • Download a signed .ics file for a booking to import into Google Calendar, Apple Calendar, Outlook, and other apps.
  • The booking time, title, and details are included so your personal schedule stays in sync.
  • This is separate from the live Google Calendar connection: .ics is a one-off file per booking; the Google connection helps availability when scheduling.

Building a custom app or website? Use our Partner API for search, slots, and bookings.

Partner API integration Contact us