2026-10-21

This update adds a full set of payment endpoints and a guide for financial webhooks. We also updated the GuestyPay tokenization guide, and several financial pages now use clearer wording.

What's New

• Payments: Sixteen new endpoints manage payments and saved payment methods on a reservation. They replace the older per-reservation payment endpoints and the guest payment-methods endpoints.
  • Manage payments: list a reservation's payments, including authorization holds and the payments that capture them. You can also view one, create one, or edit its amount, payment method, scheduled date, or note.
  • Act on a payment: charge a pending or failed payment right away, cancel it, refund it in full or in part, capture funds from an authorization hold, or record a chargeback.
  • Record offline activity without charging a processor: record a payment or a refund, and later update the payment or the refund.
  • Saved payment methods: list them for a guest or a reservation, add one, or view one.
• Financial webhooks guide: The new Financial webhooks guide explains the "guest folio created" and "guest folio updated" events, which were added to the subscribable events last period. It covers when each event is sent, what the payload includes and leaves out, and an example payload. It also explains that updates within 30 seconds are grouped together and that events can arrive out of order.

Improvements

• GuestyPay tokenization guide updated: The guide now matches the article on the publishing platform. The GuestyPay tokenization guide no longer includes the direct-API instructions for creating a card token. Step 1 now covers only the payment form SDK. A new note asks anyone with a direct GuestyPay API integration to move to the latest SDK and to contact Customer Experience for help. The API itself is unchanged.
• Clearer basic fees and channel commission pages: We replaced incorrect terminology with clearer descriptions. The basic fees pages now say that listings with no basic fees configured are left out of the results. The channel commission pages now say that using a parent unit type ID reads and updates the same listing-level commissions.
• Docs corrected, price adjustments:
  • The manual total amount page now says the parent invoice item ID is optional. When it's left out, the system finds the invoice item from the reservation's folio. The old page described it as the invoice item the adjustment applies to, without saying it could be omitted.
  • The total amount lookup page now lists that ID as always present on each returned item. It wasn't listed as required before.