Billing & Payments

Navigate to Property Management → Transactions for the transaction audit view. The billing domain also includes folios, coupons, and payment-provider configuration behind the API.

What the system tracks

• Folios are the reservation-level ledgers.
• Transactions record charges, payments, refunds, and coupon adjustments.
• Coupons apply discounts to reservations and create negative adjustment entries on the folio.
• Stripe is the platform payment gateway. Tenants can optionally supply a Stripe Connect account ID so that funds are routed to their connected account with a configurable platform fee.

Operational guarantees

• Capturing a payment intent completes the pending payment transaction and immediately updates the folio balance.
• Stripe webhooks finalize asynchronous payment outcomes and ignore events whose metadata.app does not equal napx-pms.
• Refunds create separate refund transactions and increase the folio balance due accordingly.
• Coupon application is atomic: redemption, usage-count increment, adjustment transaction, and folio recalculation succeed or fail together.
• Property-scoped coupons can only be redeemed against reservations for the same property.

Security

• The transaction audit page does not expose raw gateway secrets.
• Stripe webhook signature verification requires STRIPE_WEBHOOK_SECRET in the API environment.

Support notes

• If a reservation still shows an outstanding balance after a payment attempt, check whether the transaction is still pending or already completed.
• If a coupon cannot be applied, confirm the reservation property, coupon active window, and usage limits.