# claim_check_unavailable

> The claim could not be checked

- Status: 409 Conflict
- Returned by: /api/public
- Operations: [refundOrder](https://developers.rivr.io/reference/api-public/refundOrder.md)
- Retry (`retryWhen`): `same_request`
- Did anything happen? (`outcome`): `none` (It did not happen)
- Cancelling and refunding in /api/public
- Page in the portal: https://developers.rivr.io/errors/claim_check_unavailable
- Try it: `GET https://developers.rivr.io/errors/simulate/claim_check_unavailable` answers with the code's exact wire form; `?succeedAfter=N&attempt=K` gives a 200 once `attempt` passes `N`

## What it means

Rivr couldn't check right now whether the payment belongs to the buyer of a sold claim, so nothing was refunded.

## What your system does

Try again shortly. The answer may then be `claim_transferred`.

## Is it worth retrying?

Yes. The same call can succeed in a while.

`retryWhen`: `same_request`. Send the very same request again, unchanged: the same `Idempotency-Key` and the same order id. Wait `Retry-After` seconds when the answer has the header, otherwise a short while that grows with each attempt.

## Did anything happen?

`outcome`: `none`. **It did not happen.** This call did not do what you asked for and changed nothing else that you can see or that concerns money. Where the code has an `outcomeNote`, it takes precedence.

## Example: /api/public

```http
HTTP/1.1 409 Conflict
Content-Type: application/json

{
  "propertyName": "ClaimTransferredAt",
  "message": "Whether the payment belongs to the buyer of a sold claim could not be checked right now, so nothing was refunded. Retry the request.",
  "errorCode": "claim_check_unavailable",
  "code": "claim_check_unavailable",
  "type": "https://developers.rivr.io/errors/claim_check_unavailable"
}
```

The `title`, `detail`, `message` and `error_description` texts are exactly as the API writes them today.