receptionist_connections_charge_declined
The prepaid first month of the connections being added could not be collected, definitely: the tenant has no saved payment method on the Stripe customer, the instrument refused, or the PaymentIntent came back in a terminal non-success state. Raised by PUT /v1/subscription/receptionist-connections on an increase only - a connection is prepaid a full month and is not reserved until that charge succeeds (ADR-0025 as amended 2026-08-18; 11-billing.md owns the mechanics). Nothing at all changed: the purchased count, both Stripe subscription items and the reserved receptionist lane are exactly as they were, and no money moved. 402 rather than the 502 its siblings carry - this is the customer's own instrument saying no, not Stripe refusing a request the platform built wrong, and only the customer can clear it: add or update the card under Billing, then send the same absolute target again. A decrease is never gated on payment and never raises this. Delinquency on connections a tenant already holds is a different question with a different answer - capacity.ENTITLED_STATUSES keeps past_due entitled through the documented dunning grace (11-billing.md §Dunning), so a working receptionist is not switched off over a failed payment; what this refuses is new reserved capacity on credit.
Problem shape
Every non-2xx response is an RFC 9457 application/problem+json body. The type URI below is stable and machine-matchable, so branch on the final path segment (the code) and treat the status as redundant confirmation. See the error-handling guide.
{
"type": "https://docs.vocapable.com/errors/receptionist_connections_charge_declined",
"title": "…",
"status": 402,
"detail": "…",
"instance": "/v1/…"
}