Guile returns this only when a client-created appointment is inside the
authorization window, the service group requires a saved-card hold, and the
provider fails the authorize synchronously before the appointment is created.
Guile does not create the appointment in that case, so no booking and no hold
exist. After an appointment exists, later hold failures appear on the appointment
payment instead.
{ "type": "https://docs.guile.app/problems/paymentAuthorizationFailed", "title": "Payment Authorization Failed", "status": 422, "detail": "Guile returns this only when a client-created appointment is inside the authorization window, the service group requires a saved-card hold, and the provider fails the authorize synchronously before the appointment is created."}
