# Payments failing? Check if it's your provider

> When calls to an outside service (payments, email, an AI API) start failing, see that the error comes from the provider, not your code, and what to check.

Section: Find and fix real problems · Page: https://tryrelia.com/docs/payment-provider-failing · Last checked against the product: 2026-11-01
Video walkthrough: https://youtu.be/Xbx2NFRn4dg

Your app depends on outside services: a payment provider, an email API, a model provider, a maps API. When one of them fails, your own requests fail too, and it can look like a bug in your code. Relia shows which side the error starts on.

The example is Relia's demo shop: at 18:00 shoppers press **Pay now** and get an error, because the payment provider answers most charges with an error.

## What you'll see

- **Home** says something needs you, for example *Calls from api to payments.example-pay.com are failing*.
- The incident's chip says **Dependencies**: a service your app calls.
- Your own API that makes those calls usually fails at the same rate, and it is part of the same incident.

Relia watches every outgoing call your services make, grouped by the address they call. A dependency is flagged when its calls fail at least 3 times, at least 5% of the time and at least twice as often as usual, or when at least 2 calls fail and half or more of all calls fail. It also flags a dependency that gets much slower (p95 over 1 second and 3 times its usual).

> **Note:** On the Free plan an incident shows its headline and numbers. The evidence, the cause chain and **Do this next** are on Growth and Pro (and during the 14-day Pro trial).

## Find the cause

1. **Open the incident.** **What happened** gives the numbers, for example *failed 25 of 42 times (60%), normally 0%*.
2. **Read Why Relia thinks so.** It explains why the dependency and your failing API belong together: *this service calls that dependency*.
3. **Open a failed request** from the evidence. In the trace, find the outgoing call (for example `POST /v1/charges`). If that call returned an error (a 502 after more than two seconds, say) and your code only passed the error on, the problem starts at the provider.
4. **Open Map** in the menu to see every outside service your app calls, with its calls, errors and speed.

> **Tip:** watch [How to read a production incident](https://youtu.be/5PDrogf7ZJU) (2 min).

## Fix it

**Do this next** tells you what to check:

- **The provider's status page.** If they report an outage, there is nothing to fix in your code. Wait, and tell your customers if it lasts. See [Status page](https://tryrelia.com/docs/status-page.md).
- **Your API key and credentials.** An expired key, a revoked key or a test key in production gives errors that look like an outage.
- **The error the provider returns.** Open the failing call in a trace: the status code and error tell you whether it's a limit (429), bad input (400) or their server (5xx).

To make your app handle the next outage better:

- Put a timeout on calls to the provider, so users don't wait for seconds before seeing an error.
- Show a clear message ("Payment didn't go through, please try again") instead of a generic error, so people don't press the button again and again.
- Retry only where it is safe. A payment retry needs an idempotency key so a card is never charged twice.

## Check the fix worked

- **If the provider recovers on its own:** the calls start working again and the incident goes quiet by itself. Home's **This week** lists it as *Went quiet*.
- **If you changed something** (a new key, a timeout, a retry): deploy it. Relia picks up the new version by itself, or click **I fixed it** on the incident. Once the problem stays away for at least 15 minutes with enough traffic, the incident says **Fix confirmed** and you get *Your fix worked*.

## Next

- [Why is my API slow?](https://tryrelia.com/docs/slow-api.md)
- [Read an incident](https://tryrelia.com/docs/incidents.md)
- [Status page](https://tryrelia.com/docs/status-page.md)

---
All Relia docs for AI assistants: https://tryrelia.com/llms.txt (index) · https://tryrelia.com/llms-full.txt (everything in one file)
