Payments, deposits, and refunds

Record and capture payments, hold deposits, assess claims, and refund.

Route: /dashboard/platform/payments, /[id]. Needs canManagePayments.

Payments

Payment.status: pending, processing, succeeded, failed, cancelled, partially_refunded, refunded. Methods: card, bank_transfer, cash, check, manual.

ActionCommand
Record money already receivedpayment_record_manual (the operator attests receipt)
Start or capture a card paymentinitiateStayPayment, captureStayPayment
Cancel an attemptpayment_cancel_attempt

A cancelled or no-show reservation cannot newly capture a payment. Another payment awaiting confirmation blocks a second attempt.

Deposits and claims

SecurityDeposit: required → authorized → held → partially_captured, captured, or released; failed. Use transitionSecurityDeposit.

DamageClaim: draft → submitted → guest_response → approved, partially_approved, declined, settled. A partial approval must be above zero and below the claimed amount. Use createStayDamageClaim and transitionDamageClaim.

Refunds

Reasons: guest_cancellation, host_cancellation, stay_issue, stay_amendment, overpayment, goodwill, other. Status: review, pending, processing, succeeded, failed, cancelled.

Assess

refund_assess decides the amount (at least 3 characters of explanation) or declines with refund_decline. A refund can be reduced under the cancellation policy, not increased.

Create

refund_create with a description of 3 to 1000 characters.

Process

refund_process sends a card refund; refund_record_manual records one already completed in cash or elsewhere.

On this page