# PAYMENT_PROVIDER_ERROR

Canonical page: https://docs.ovok.com/errors/payment-provider-error

**HTTP 502.** Problem type: [`https://docs.ovok.com/errors/payment-provider-error`](https://docs.ovok.com/errors/payment-provider-error).

## What this means [#what-this-means]

The payment provider refused Ovok's request or did not answer, so Ovok could not finish the checkout or cancel the subscription. Ovok keeps the provider's own answer out of the response.

## Troubleshooting [#troubleshooting]

1. Wait and retry. Most provider outages and slow answers pass quickly. If `retryAfterSec` or `Retry-After` is present, wait that long first.
2. Ask the deployment administrator to check the payment provider's credentials and status if it keeps failing. A rejected or wrong-mode credential fails every call.
3. Check the billing details if only checkout fails. Correct the name, address or VAT ID, then try once more.

## Retry safely [#retry-safely]

Retrying a cancel is safe: nothing changed. Each retried checkout starts a new payment page, and nothing is charged until you pay on it, so complete only one. The same code can also arrive with `status` 503 or 504 when the provider is busy or slow.

## If the problem persists [#if-the-problem-persists]

Share the HTTP status, problem `type`, request path, response timestamp and `traceId` with your administrator or support contact. Remove access tokens, provider secrets and patient data first. The [Error responses guide](/errors) explains the response fields, and the [machine-code registry](/errors/machine-codes) lists every endpoint-specific type.
