Validate Absorbed Charges Route
Answer whether these outstanding charges can be merged into a checkout, without collecting anything.
Checkout needs this the moment staff add a charge, not at payment time. Some blockers — a package redeemed against another charge, a realized inventory drawdown, a membership log — live in tables the client never fetches, so the UI offers a merge it cannot know is refused. Until this endpoint existed the only answer came from payin-config setup, which fires on a debounced effect: the charge would sit in the ticket as a merged line and then convert to a paid-separately charge at some unpredictable later moment, or not until settlement.
Read-only: same rules as archive_absorbed_charges, nothing mutated.
204 means mergeable; 409 carries the blocking reason.
Headers
The tenant you are making this request on behalf of
Your api key
Body
Ask whether outstanding charges can be merged into a checkout.
Used by checkout the moment staff add one, so a charge the server will refuse is routed to "pay it separately" immediately rather than sitting in the ticket as a merged line until payment.
Response
Successful Response

