# clinic_connect_no_consent

> The connection wasn't made here

- Status: 409 Conflict
- Returned by: The account connection (/oauth)
- Retry (`retryWhen`): `never`
- Did anything happen? (`outcome`): `none` (It did not happen)
- The account connection
- Page in the portal: https://developers.rivr.io/errors/clinic_connect_no_consent
- Try it: `GET https://developers.rivr.io/errors/simulate/clinic_connect_no_consent` answers with the code's exact wire form; `?succeedAfter=N&attempt=K` gives a 200 once `attempt` passes `N`

## What it means

`POST /oauth/deauthorize`: the clinic is on your platform, but the account connection didn't connect it, for example because it came through the funnel or a Rivr admin. An approval when the clinic was already on the platform isn't enough. A disconnection moves the clinic from the platform's values to Rivr's, also payment methods and payout schedule, so it can't be done with a key alone. Nothing has changed.

## What your system does

Contact Rivr to end the connection. Send the clinic's `merchant_id`.

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

## Example: The account connection (/oauth)

```http
HTTP/1.1 409 Conflict
Content-Type: application/json
Cache-Control: no-store

{
  "error": "clinic_connect_no_consent",
  "error_description": "The merchant was not connected through the account connection. Contact Rivr to end it."
}
```

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