Version 4.17.0

• ✨ Document the read-only Payouts and Channel Payouts resources, both in beta. /payouts exposes SmilyPay payouts — what Smily paid out and the Smily fees deducted on top of each collected payment, per booking, with each line's contribution to the payout total. /channel_payouts covers the step before it: what an OTA such as Airbnb or Booking.com actually wired, decomposed across each booking's commission, city tax, cleaning fees and deductions, plus account-level movements. Pivot between the two with related_channel_payout_references. Both require the new payouts_read scope.
• 📚 Add the Understanding payouts guide — a walkthrough for going from "the amount I received is not what I expected" to the line that explains it: which of the two endpoints owns each hop, a worked example, an ordered checklist of the five things that shrink a payout (Smily fee, carry-over from an earlier booking, channel deduction, account-level movement, the channel's own arithmetic), carry-over lines and their paired halves, direct bookings and split payment — including OTA bookings that also carry a SmilyPay upsell — and, explicitly, what you can verify independently and what you cannot.
• ⚠️ Note the beta caveats while these endpoints stabilise: /payouts returns one payout per page (per_page is capped at 1, since rows are computed on the fly), payment_gateway_id is required on every /payouts request and omitting it returns 400, and both resources are read-only — payouts are produced internally as OTA wires arrive.