# claim_transferred

> The claim has been sold

- Status: 400 Bad Request
- Returned by: /api/public
- Operations: [refundOrder](https://developers.rivr.io/reference/api-public/refundOrder.md)
- Retry (`retryWhen`): `never`
- 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_transferred
- Try it: `GET https://developers.rivr.io/errors/simulate/claim_transferred` answers with the code's exact wire form; `?succeedAfter=N&attempt=K` gives a 200 once `attempt` passes `N`

## What it means

The order's claim has been sold and transferred to a buyer, or the payment was made on such a claim. The payment isn't refunded through the API.

## What your system does

Contact Rivr. A new call gets the same answer.

## Is it worth retrying?

No, not without changing the call.

`retryWhen`: `never`. Don't send it again. The answer is final for this request: read the current state, the order for example, and act on that.

## 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.

The same code and text also come when the whole payment was excess and has already been refunded to the patient outside the API. No read shows that, since the order stays Completed; contact Rivr.

## Example: /api/public

```http
HTTP/1.1 400 Bad Request
Content-Type: application/json

{
  "propertyName": "ClaimTransferredAt",
  "message": "The payment was made on a claim that has been sold and transferred to a buyer, and it belongs to the buyer up to what remained of the claim. It cannot be refunded through the API. Contact Rivr.",
  "errorCode": "claim_transferred",
  "code": "claim_transferred",
  "type": "https://developers.rivr.io/errors/claim_transferred"
}
```

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