Skip to content
Hostelivo
Menu

Payments

Money goes straight to your property's account

Hostelivo never holds reservation money. Each property connects its own account with a licensed payment provider. The platform only creates the payment request, verifies it and records it.

Payment path

  1. Guest

    Pays from the guest portal or the kiosk.

  2. Payment provider

    Your property's account with the provider you choose.

  3. Your account

    Settlement happens between the provider and your property under your agreement.

What Hostelivo does

  • Creates the payment request or link
  • Verifies the result with the provider's server
  • Records the movement in the reservation ledger

Payment status is separate from reservation status

A reservation can be confirmed while payment is partial. So each status is stored on its own and you see it as it is.

  • Unpaid
  • Partially paid
  • Paid
  • Refunded
  • Partially refunded
  • A payment never counts as paid from a browser redirect. We check with the provider
  • Amount and currency must match the request
  • A repeated notification never doubles the amount
  • Unsigned notifications are rechecked against the provider API
  • After the stay folio closes, no new charges are added to the guest
  • Every refund has a due date and an alert if it is late
  • Provider credentials are encrypted and never sent back to the browser

Invoices without claims

E-invoicing has requirements set by the Zakat, Tax and Customs Authority. The platform does not claim to be approved for it.

  • Current documents are drafts clearly marked as not a tax invoice
  • The property issues the official invoice from its compliant system
  • A receipt for every payment in Arabic and English
  • Properties not registered for VAT get receipts only, with no tax line
  • An issued invoice is never edited. Corrections use credit or debit notes
  • Any link with the FATOORA platform stays off until requirements are met

Payment providers

Providers whose docs we reviewed

No provider has been tested in its sandbox yet. The status here comes from reading official documentation only.

  • Moyasar

    Documentation available
    Requirements
    The property onboards as its own Moyasar merchant with its own keys.
    Documented capabilities
    Embedded form and hosted invoices. Server verification. Full or partial refunds. Idempotency through our own ID. mada, Apple Pay, STC Pay.
    Notes
    Webhooks carry a shared secret, not a signature, so we refetch the payment before any change. Test keys available.
    Official source(Moyasar)
  • MyFatoorah

    Documentation available
    Requirements
    A merchant account and a key per country. Saudi Arabia has its own host.
    Documented capabilities
    Embedded payment, hosted page and payment links. Server verification. Full or partial refunds. Idempotency. mada, Apple Pay, STC Pay.
    Notes
    Webhooks are signed. Sandbox with a public test token. Multi-vendor needs approval.
    Official source(MyFatoorah)
  • Tap Payments

    Documentation available
    Requirements
    A merchant account with test and live keys.
    Documented capabilities
    Hosted checkout. Full or partial refunds. Idempotency valid for 24 hours. mada, STC Pay, Apple Pay.
    Notes
    Webhooks are signed. The marketplace model needs eligibility confirmed by Tap.
    Official source(Tap Payments)
  • PayTabs

    Documentation available
    Requirements
    A merchant account. Test keys are generated automatically. A Saudi-specific domain.
    Documented capabilities
    Hosted page, payment links and invoices. Refunds on successful transactions.
    Notes
    Signed IPN. Partial refunds, idempotency and sandbox host not verified.
    Official source(PayTabs)
  • HyperPay

    Documentation available
    Requirements
    Credentials are issued at merchant onboarding.
    Documented capabilities
    Payment widget and server-to-server. Verification after redirect. Refunds.
    Notes
    Webhooks are encrypted. The docs portal must be confirmed as official. mada and STC Pay not verified.
    Official source(HyperPay)
  • Geidea

    Documentation available
    Requirements
    Credentials from the enablement team or the merchant portal.
    Documented capabilities
    Hosted checkout and wallets. Signed session creation. Full or partial refunds. Test cards include mada.
    Notes
    Callbacks are signed. Idempotency not verified.
    Official source(Geidea)
Aggregated collection through a platform account is off. It would only be enabled after an agreement with a licensed provider and a regulatory review.

See Hostelivo on a ready hostel

Properties with rooms, beds and bookings already in. Open one and walk through a day from booking to cleaning.