# Conflict

The request conflicts with the current state of a resource. The action cannot be completed because a related resource already exists or is in an incompatible state.

**HTTP Status:** `409 Conflict`

## Error Codes

| Code | Description |
|  --- | --- |
| `customer_already_exists` | A customer with this CPF exists but with a different `external_id` |
| `offer_already_accepted` | This credit offer already has a loan associated with it |
| `session_already_active` | A biometrics session is already in progress for this customer |


## Example Response


```json
{
  "type": "https://api.dinie.com.br/errors/customer_already_exists",
  "title": "Conflict",
  "status": 409,
  "detail": "A customer with CPF 12345678901 already exists with a different external_id.",
  "code": "customer_already_exists"
}
```

## How to Resolve

- **`customer_already_exists`** -- Look up the existing customer by CPF and use their ID instead of creating a new record.
- **`offer_already_accepted`** -- Each credit offer can only be accepted once. Request a new offer if the customer needs another loan.
- **`session_already_active`** -- Wait for the current biometrics session to complete or expire before starting a new one.


## See Also

- [Error Handling guide](/apis/concepts/errors) -- Full error handling patterns and code examples