> ## Documentation Index
> Fetch the complete documentation index at: https://nayax-44d6e37b-fis-cortina.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Void

> How the Void call un-registers a previously fiscalized transaction from the tax authority.

# Void

The `Void` call un-registers a previously fiscalized transaction from the tax authority. Nayax triggers it when a transaction cancels after authorization or sale, typically because the product or service was not delivered to the customer.

## When Void is triggered

Nayax Engine sends a Void fiscal call when it initiates a cancellation command. This occurs when:

* The transaction was cancelled at the customer's request
* A technical issue prevented the product or service from being supplied

## Void flow

Nayax sends the Void call after authorization or sale approval. This removes the fiscal registration created by the original `Register` call from the tax authority.

The following sequence shows how the Void call works:

1. Transaction has been authorized or sale approved; fiscal registration already sent via `Register`. Product or service has not yet been dispensed.
2. The customer or a technical failure triggers cancellation.
3. Nayax Engine sends a `POST /FisCortina/Void` request to your server.
4. Your server un-registers the transaction with the Tax Authority and returns a response (must include `Verdict`).
5. Nayax Engine completes the void and returns the result to the Nayax Device.
6. Nayax Device informs the Operator that Nayax cancelled the transaction.

### Exception handling

The payment cancellation always completes even if fiscal un-registration fails:

| Scenario      | Step | Resolution                                                                                                               |
| ------------- | ---- | ------------------------------------------------------------------------------------------------------------------------ |
| Void declined | 3–4  | Payment void completes. If retry is enabled, the un-registration is queued for async retry within the configured window. |
| Void timeout  | 3–4  | Payment void completes. Handled according to your timeout configuration.                                                 |

## Next steps

<CardGroup cols={2}>
  <Card title="Request & Response Reference" href="/docs/fis-cortina/response-reference">
    Full field definitions and response codes for all endpoints.
  </Card>

  <Card title="Retry & Timeout Handling" href="/docs/fis-cortina/reliability">
    Configure retry behavior and timeout handling for failed registrations.
  </Card>
</CardGroup>