Property settings

Identity, stay times, taxes, fees, card payments, venues, amenities, and photos.

Operations·Owner·Updated 2026-09-28·Open in console

Property settings is hotel-wide config, not inventory. Rooms and room types stay on /rooms.

The page is stacked cards, not tabs. Identity sits beside stay times; taxes, venues, amenities, photos, and Card payments are full-width so tables and keys stay readable. Jump links at the top scroll to a card.

Save property writes identity, stay times, venues, amenities, and photos. Payment keys use Save payment account on Card payments—the sticky bar does not persist processor secrets.

Stay times (check-in / check-out) default arrival and departure times on new reservations.

Taxes and fees: add or edit codes, percentages or amounts, and whether they apply to room. They post on quotes and folios.

Card payments: for most countries use this hotel’s Stripe keys or Stripe Connect. Hotel Razorpay and Agamnos Pay appear for INR / India hotels. Agamnos Pay is the no-gateway INR path.

Currency on the property is the base for rates, folios, and checkout. Guests on Direct may optionally view an approximate converted amount.

Event venues feed the Events form. Amenities and photos appear on Agamnos Direct and the property profile.

How to

  1. Open Card payments. Prefer Stripe or Stripe Connect outside India. For INR hotels, choose Razorpay, Agamnos Pay (bank + PAN), or Stripe.
  2. For Agamnos Pay, use the property’s Indian address and PIN, then the contact, PAN, and settlement account. For Stripe Connect, finish the Stripe-hosted form; charges stay disabled until Stripe enables them.
  3. Leave a saved secret blank on a later save to keep it. For this hotel’s own processor, paste the webhook signing secret and point the processor at the webhook URL shown under Card payments.

Technical

  • Webhook URLs (same origin as the console, proxied to the API): POST /api/v1/payments/webhooks/stripe and POST /api/v1/payments/webhooks/razorpay.
  • Stripe sends header stripe-signature; Razorpay sends x-razorpay-signature. The API verifies against the webhook secret saved for that hotel.
  • Staff payment capture uses Authorization: Bearer <accessToken> with payment:process. Guest Direct confirm uses public POST /api/v1/payments/confirm (no staff JWT).
  • Processor secrets are stored encrypted on the property payment account. Blank secret fields on save leave the existing value.

See also: Onboard a property · Hotel events · New reservation · Agamnos Pay · Agamnos API

All topics← RatesRoom service →