collection_method_update_failed
PUT /admin/tenants/{id}/collection-method saved the authorized change, but fresh Stripe reads do not yet prove completion. A provider write may already have applied. The response includes the saved operation ID and request key; retry the same target and key to recover that operation. Dispatch ownership and a pending audit commit before provider I/O. Completed audit evidence is written only after both required phases are confirmed. Stable per-phase keys are replayed only within 23 hours of first dispatch; after that, fresh correlated provider evidence can confirm an applied write, but a new provider write is refused. A replaced payment method or uncorrelated external edit remains pending for review.
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/collection_method_update_failed",
"title": "…",
"status": 502,
"detail": "…",
"instance": "/v1/…"
}