Agamnos Pay
Folios, deposits, refunds—card data stays with processors.
Agamnos Pay is the payment layer for Direct deposits, front-desk stay folios, and hotel event folios. Amounts are always in the property base currency.
Outside India / non-INR hotels: use this hotel’s Stripe keys or Stripe Connect under Property settings → Card payments.
Hotel Razorpay is available when the property is INR or country IN. Agamnos Pay is the INR path for a hotel with no gateway: the guest pays through Agamnos’s Razorpay account; Route transfers the hotel’s share. PAN and the full account number are sent to Razorpay and are not stored here.
Stripe Connect is the path for a hotel that should be the merchant on Stripe. The guest is charged on that hotel’s connected account, and Agamnos keeps the same commission as an application fee. The platform Stripe account must have Connect turned on. Stripe hosts onboarding. Charges start after Stripe enables the account.
A hotel with neither stays in practice capture for that property only. Cash and other manual folio payments never go to the processor.
In the reservation folio, record cash or capture card. A captured Agamnos Pay or Stripe Connect payment shows the hotel share and the Agamnos fee. Refunds use the same hotel account that took the payment.
If the guest closes the browser after paying, the processor webhook still marks the folio payment captured. Stripe Connect also updates when Stripe reports that charges are enabled.
Generate invoice opens a printable stay statement. Room number appears on the invoice only after check-in or check-out.
Banquet and conference money lives on the event folio at /events — same cash and card capture, billed to the event name, not a stay reservation.
Technical
- Public: GET /api/v1/payments/config; POST /api/v1/payments/confirm (Direct / guest checkout completion).
- Webhooks: POST /api/v1/payments/webhooks/stripe (stripe-signature); POST /api/v1/payments/webhooks/razorpay (x-razorpay-signature). Raw body required for signature verify.
- Staff (JWT + payment:process): POST /api/v1/payments with Idempotency-Key recommended; POST /api/v1/payments/:id/refund with amount.
- Card PANs never enter these JSON bodies—the browser talks to Razorpay/Stripe Checkout; agamnos stores payment ids and folio lines.