> ## Documentation Index
> Fetch the complete documentation index at: https://docs.guile.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Payment Authorization Failed

> The saved-card authorization failed

## Cause

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.

## Fix

Have the customer update or replace the saved card, then
[create an appointment](/api-reference/appointments/create-an-appointment) again
with a new idempotency key.

## Retry safety

Not retryable

## Raised by

These operations can return this problem:

* [Create an appointment](/api-reference/appointments/create-an-appointment)
* [Authorize an appointment payment](/api-reference/appointments/authorize-an-appointment-payment)
* [Capture an appointment payment](/api-reference/appointments/capture-an-appointment-payment)

## Example

```json theme={null}
{
  "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."
}
```