# Delete a payment term

```http
DELETE https://secure.yoprint.com/v1/api/store/{team_slug}/setting/payment_term/{hash_id}
```

- API version: v1
- Operation ID: `v1_public_payment_term_destroy`
- Section: Team settings › [Payment terms](https://developer.yoprint.com/reference/payment-terms.md)
- Web page: https://developer.yoprint.com/reference/payment-terms/v1-payment-term-destroy/
- Authentication: `Authorization: Bearer YOUR_API_KEY`

Deletes a payment term. It stays in the list with `trashed: true` and can be restored. Orders that used it keep their deposit and due dates.

## Permission

Needs the Manage Settings permission.

## Business rules

- The default payment term cannot be deleted.

## Path parameters

- `team_slug` (string, required): Your team slug, shown as Team ID next to your API key in Profile. Example `your-team`.
- `hash_id` (string, required): The payment term's `id`: a hash id from an earlier answer. Only hash ids work here; anything else answers 404 `page_not_found`. Example `H3J5exdciYshbk`.

## Request body

This operation takes no request body.

### Example request

```bash
curl -X DELETE 'https://secure.yoprint.com/v1/api/store/your-team/setting/payment_term/H3J5exdciYshbk' \
  -H 'Authorization: Bearer YOUR_API_KEY' \
  -H 'Accept: application/json' \
  -H 'X-Yoprint-Decimal-Format: exact-v1'
```

## Response

`200` Successful response.

Fields:

- `data` (null, required)
- `status` (integer, required)
- `success` (boolean, required)

Example response:

```json
{
  "data": null,
  "status": 200,
  "success": true
}
```

## Errors

- `401` The API key is missing or wrong (`unauthenticated`).
  - When: The API key is missing or wrong. Fix: Send your personal API key as `Authorization: Bearer YOUR_API_KEY`.
- `403` You are not allowed to do this. `api_access_not_in_plan`: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only `{"message": "Insufficient Permission"}`. Other refusals use the error envelope, with `unauthorized` or `user_is_not_authorized`.
  - When: Your permission group lacks Manage Settings. This 403 has a short body, `{"message": "Insufficient Permission"}`, without `success` or `error`. Fix: Ask the team owner to give your permission group Manage Settings.
- `404` Not found. `page_not_found`: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's. `code: null`, with a message that starts "No query results for": there is no record with that id.
  - When: No payment term with that id on this team (`error.code` is null and `error.message` starts "No query results"), the id is not one of this team's hash ids, or you are not a member of the team (both `page_not_found`). Fix: Use an `id` from the list operation and check the team slug.
- `500` A business rule refused the request (see the operation's errors), or something failed inside YoPrint. Refusals use the error envelope with a code such as `action_not_allowed`; an unexpected failure answers `{"message": "Server Error"}`. Repeating a refusal gets the same answer; after an unexpected failure, read the record back before you retry a change.
  - When: The payment term is the team default. YoPrint refuses with HTTP 500 and `{"status": 500, "success": false, "error": {"code": "delete_fail", "message": null}}`; nothing is deleted. Don't retry it. Fix: Make another one the default first, then delete this one.

## Notes

- YoPrint doesn't check whether customers use it as their default payment term.

## Related

- [Restore a payment term](https://developer.yoprint.com/reference/payment-terms/v1-payment-term-restore.md): `PATCH /v1/api/store/{team_slug}/setting/payment_term/{id}/restore`
- [Set the default payment term](https://developer.yoprint.com/reference/payment-terms/v1-payment-term-default.md): `PATCH /v1/api/store/{team_slug}/setting/payment_term/{id}/default`