> For the complete documentation index, see [llms.txt](https://docs.number.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.number.tech/documentation/getting-started/integration-options/payform/incremental-authorizations.md).

# Incremental Authorizations

You may wish to configure your PayForm to collect an Initial *Authorization Only*.

This Authorization can be Reversed or Incrementally increased during your workflow and eventually finalized and sent for settlement.  In order to Specify *Authorization Only* adjust your [request](/api-reference/rest-api/payform.md) as follows

{% code overflow="wrap" %}

```jsonc
"eFeatures": "0008",
```

{% endcode %}

This tells the PayForm that any dollar amount authorized will stay in a PENDING state awaiting any changes or Incremental increases you specify using our API.

{% hint style="warning" %}
Be VERY CAREFUL when setting this feature value; transactions collected here will rely on you to FINALIZE them using the API. If you do an Authorization Only for a dollar value, the merchant WILL NOT collect the funds until you FINALIZE the transaction.
{% endhint %}

Use this REST API call to execute incremental authorizations or finalize the transaction:

{% content-ref url="/pages/mIUOkLIdbQGmBaUi7xmi" %}
[Incremental Auth](/api-reference/rest-api/card-operations/authentication.md)
{% endcontent-ref %}


---

# 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.number.tech/documentation/getting-started/integration-options/payform/incremental-authorizations.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.