# Contract Cancellation

POST /partner/v3/shops/:shopUuid/contracts/:contractUuid/cancel

If the flow includes merchant approval, the merchant checks if the status of the contract is signed using the GET /partner/v3/shops/:shopUuid/contracts/:contractUuid request. When the contract is in the signed status, the merchant needs to approve or cancel the contract. As processing customer signing might take some time, the endpoint may need to be polled once every second for a maximum of 15 seconds.

To cancel the contract, the e-shop needs to know the credit contract UUID, which is in the response to the POST/:applicationUuid/accept request.

The request does not require any parameters to be passed in its body.

Note that you can also cancel contracts in the Partner Portal.

Endpoint: POST /partner/v3/shops/{shopUuid}/contracts/{contractUuid}/cancel
Security: bearerAuth

## Path parameters:

  - `shopUuid` (string, required)
    The unique identifier of the shop.
    Example: "a93f1f44-d5dd-4469-bfcc-c1de9e969213"

  - `contractUuid` (string, required)
    The unique identifier of the contract.
    Example: "788ec8c4-c497-470b-8505-2303f151d427"

## Response 401 fields (application/json):

  - `message` (string)
    Unauthorized
    Example: "unauthorized"

## Response 403 fields (application/json):

  - `message` (string)
    Unauthorized access
    Example: "User is not authorized to access this resource with an explicit deny"

## Response 404 fields (application/json):

  - `message` (string)
    Not Found
    Example: "not_found"

## Response 422 fields (application/json):

  - `message` (string)
    Unprocessable Entity

## Response 500 fields (application/json):

  - `message` (string)
    Internal server error
    Example: "internal_server_error"


## Response 204 fields