> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/online-payments/advanced-payment-methods-apms/paypal/your-first-transaction-with-paypal/paypal-void-authorization.md).

# PayPal Void authorization

You can void authorizations for various reasons, including non-availability of some items in cart and partial order cancelled by the payer. You have flexibility to void an authorization and ensure further fund captures are cancelled.

**Void, or cancel an authorized payment by ID:**

You cannot void an authorized payment that has been fully captured. Voiding an authorization cancels the entire open amount. You can initiate a void if:

* the authorization is pending
* the authorized amount was captured at less than 100%

{% hint style="info" %}
A valid JWT Token is required to make the API call.
{% endhint %}

## Required fields

There are no required fields for the Void Authorization API.

## Optional fields

There are no optional fields for the Void Authorization API.

## Request

To void an authorization, make a request with an empty body.

* **POST** `/transactions/{id}/void`

## **Response**

The successful response will be of status code 204, with no content.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.verifone.com/online-payments/advanced-payment-methods-apms/paypal/your-first-transaction-with-paypal/paypal-void-authorization.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.