---
title: "Pre-authorisation and authorisation adjustment"
description: "Pre-authorise a payment, adjust the authorised amount, and capture the payment."
url: "https://docs.adyen.com/online-payments/classic-integrations/modify-payments/adjust-authorisation"
source_url: "https://docs.adyen.com/online-payments/classic-integrations/modify-payments/adjust-authorisation.md"
canonical: "https://docs.adyen.com/online-payments/classic-integrations/modify-payments/adjust-authorisation"
last_modified: "2020-11-11T10:05:00+01:00"
language: "en"
---

# Pre-authorisation and authorisation adjustment

Pre-authorise a payment, adjust the authorised amount, and capture the payment.

[View source](/online-payments/classic-integrations/modify-payments/adjust-authorisation.md)

In a basic payment flow, the payable amount from your payment request is authorised and then captured. But sometimes you may want to change the amount or extend the length of the authorisation. You can enable this using the [authorisation type](#authorisation-types) *pre-authorisation* with your payment request. In this payment flow you can increase or decrease the authorised amount at a later stage, and then capture the payment. We refer to these changes to a pre-authorised payment as authorisation adjustments.

Authorisation adjustment is currently available for Discover, Mastercard, Visa, and American Express. Support is ultimately up to the issuer. See [Availability](#availability) for more information.

### Use cases

There are several use cases for adjusting an authorisation:

* Hospitality. For example, in a hotel:

  1. At the checkout page of the hotel's website or app, the hotel pre-authorises payment of the room that the guest booked. At the same time, the hotel [stores the shopper's payment information](/online-payments/tokenization), to be able to apply late charges when necessary.
  2. During their stay, the guest incurs expenses at the hotel facilities. The hotel adds these expenses to the pre-authorised amount by adjusting the authorisation.
  3. When the guest checks out, the hotel captures the final amount, or cancels the payment if the guest prefers to settle their bill with a different payment method.
  4. If necessary, the hotel charges the guest after they have left, using the shopper's stored payment details for a new payment.

* Pre-ordering items. For example, a shopper pre-orders a video game that will be released three months later. The video game seller authorises the payment, but as they can only ship the product three months later, they need to extend the authorisation validity.

## Authorisation types

For some card schemes, you can set card payment requests to be handled as either a pre-authorisation or a final authorisation.

* **Pre-authorisation**: This is intended for use cases as described above, when you do not yet know the amount to be captured. It allows you to increase or decrease the initially authorised amount at a later point in time using the [/adjustAuthorisation](https://docs.adyen.com/api-explorer/#/Payment/adjustAuthorisation) endpoint.
* **Final authorisation**: Use this when the final amount is agreed up front and the transaction will definitely be captured in full. It is not possible to adjust the authorised amount.

By default, Adyen handles all card payment requests as final authorisations.

To set an authorisation type, you can either:

* Define the default authorisation type at the merchant account level for all card transactions. See [Configure your account](#configure-account).
* Manually specify the authorisation type (**PreAuth** or **FinalAuth**) in each payment request. See [Pre-authorise a payment](#pre-authorise).

## Asynchronous or synchronous adjustment

There are two ways to implement pre-authorisation:

* With **asynchronous authorisation adjustment**, you refer to a payment using the PSP reference that you received in the response to your pre-authorisation request. In each authorisation adjustment request as well as in the final capture request, you only need to specify this first PSP reference.

  Asynchronous adjustment is easier to implement, but it is not immediately clear if the adjustment succeeded. You need to set up webhooks to receive updates and to know if the final amount was authorised before you capture the payment.

* With **synchronous authorisation adjustment**, you pass an `adjustAuthorisationData` blob from one authorisation adjustment to the next, to enable us to keep track of the latest amount. You receive the first blob in the response to your pre-authorisation request. In your first authorisation adjustment request, you specify the blob you received for the pre-authorisation, and you receive a new blob in the response. In your next adjustment, you specify the blob that you received in the response for the previous adjustment, and so on.

  Synchronous adjustment requires an additional step to implement, because you need to keep track of the latest blob to submit it in the subsequent adjust authorisation request. The advantage is that you receive the adjustment result synchronously. In this way you immediately know if the final amount was authorised before you capture the payment.

  If at some stage you fail to pass the blob, the flow falls back to asynchronous adjustment and it is no longer possible to return to synchronous adjustment for that payment.

## Requirements

Before you configure and use pre-authorisation:

1. Make sure that you have built an integration that can make a payment.
2. [Set up webhooks](/development-resources/webhooks). You'll need to rely on webhooks to know whether the capture succeeded. If you use asynchronous authorisation adjustment, you'll also need to rely on webhooks for the authorisation adjustment result.

You also need to implement logic on your end, for example to decide when to use the pre-authorisation flow, and to calculate the amount when you make an authorisation adjustment.

## (Optional) Configure your account

There are two aspects of your account that you may want to configure for pre-authorisation and authorisation adjustment:

* **Synchronous authorisation adjustment**: To receive the initial `adjustAuthorisationData` blob with your pre-authorisation request and to subsequently receive the authorisation adjustment results synchronously, ask our [Support Team](https://ca-test.adyen.com/ca/ca/contactUs/support.shtml?form=other) to enable this.

* **Default authorisation type**: If you only do pre-authorisation payment requests, you can ask our [Support Team](https://ca-test.adyen.com/ca/ca/contactUs/support.shtml?form=other) to set your default [authorisation type](#authorisation-types) to **PreAuth** so that you do not have to specify it in your payment requests.

  If you want to do both pre-authorisation payment requests and regular payment requests, we recommend you specify the authorisation type in all payment requests. Pre-authorised transactions incur scheme fees.

## Step 1: Pre-authorise a payment

1. Make a payment request, and additionally specify:

   * `additionalData.authorisationType`: `PreAuth`

   ##### request

   ```json
   {
      "reference":"YOUR_ORDER_NUMBER",
      "merchantAccount":"YOUR_MERCHANT_ACCOUNT",
      "paymentMethod": {
         "type": "scheme",
         "number":"4111111111111111",
         "cvc":"737",
         "expiryMonth":"03",
         "expiryYear":"2030",
         "holderName":"John Smith"
      },
      "amount":{
         "currency":"EUR",
         "value":1500
      },
      "additionalData":{
         "authorisationType":"PreAuth"
      }
   }
   ```

   ##### response

   ```json
   {
     "pspReference": "8884689190961333",
     "resultCode": "Authorised"
   }
   ```

2. Store the `pspReference` from the response for later use when adjusting the authorisation or capturing the payment.

## Step 2: (Optional) Modify the authorisation

You cannot make a zero-value authorisation when you adjust an authorisation.

### Adjust the pre-authorisation amount

To modify the pre-authorised amount, make an authorisation adjustment request.

### Tab: Asynchronous authorisation adjustment

1. Make a POST request to the [/adjustAuthorisation](https://docs.adyen.com/api-explorer/#/Payment/adjustAuthorisation) endpoint, specifying:

   | Parameter                      | Required                                                                                    | Description                                                                                                                                                                                                                                                         |
   | ------------------------------ | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   | `originalReference`            | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | The `pspReference` of the pre-authorisation request. You received this in the response to your pre-authorisation request.                                                                                                                                           |
   | `modificationAmount`           | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | The `currency` and `value` of the new amount **in minor units**. This is the sum of the pre-authorised amount and the additional amount. If this is not the first authorisation adjustment, it is the sum of the pre-authorised amount plus all additional amounts. |
   | `additionalData.industryUsage` |                                                                                             | **DelayedCharge**                                                                                                                                                                                                                                                   |
   | `reference`                    |                                                                                             | Your reference to this payment modification, for use in your reconciliation process.                                                                                                                                                                                |
   | `merchantAccount`              | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | The name of your merchant account that is used to process the payment.                                                                                                                                                                                              |

   The following example shows how to add a charge of EUR 64.15 to a pre-authorised amount of EUR 150.00.

   **Asynchronous authorisation adjustment request**

   ```json
   {
       "originalReference":"8815754678001083",
       "modificationAmount": {
           "currency":"EUR",
           "value":21415
       },
       "additionalData":{
           "industryUsage":"DelayedCharge"
       },
       "reference":"YOUR_MODIFICATION_REFERENCE",
       "merchantAccount":"YOUR_MERCHANT_ACCOUNT"
   }
   ```

   The [/adjustAuthorisation](https://docs.adyen.com/api-explorer/#/Payment/adjustAuthorisation) response contains:

   * `pspReference`: The PSP reference associated with this [/adjustAuthorisation](https://docs.adyen.com/api-explorer/#/Payment/adjustAuthorisation) request. Note that this is different from the PSP reference associated with the pre-authorisation request.
   * `response`: **\[adjustAuthorisation-received]**

   **Asynchronous authorisation adjustment response**

   ```json
   {
     "pspReference": "881576235454101H",
     "response": "[adjustAuthorisation-received]"
   }
   ```

2. Wait for the [webhook event](/development-resources/webhooks). This informs you whether the new amount has been authorised.

### Tab: Synchronous authorisation adjustment

1. Make a POST request to the [/adjustAuthorisation](https://docs.adyen.com/api-explorer/#/Payment/adjustAuthorisation) endpoint, specifying:

   | Parameter                                | Required                                                                                    | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                          |
   | ---------------------------------------- | ------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
   | `originalReference`                      | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | The `pspReference` of the pre-authorisation request. You received this in the response to your pre-authorisation request.                                                                                                                                                                                                                                                                                                                                                            |
   | `modificationAmount`                     | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | The `currency` and `value` of the new amount **in minor units**. This is the sum of the pre-authorised amount and the additional amount. If this is not the first authorisation adjustment, it is the sum of the pre-authorised amount plus all additional amounts.                                                                                                                                                                                                                  |
   | `additionalData.adjustAuthorisationData` |                                                                                             | The previous `adjustAuthorisationData` blob. For the first adjustment, that is the blob you received in the response to the pre-authorisation request. You may need to URL-decode that before you can use it. For the second adjustment, it is the blob you received in the response to the first adjustment, and so on. The blob you receive for an authorisation adjustment is not URL-encoded, so you do not need to decode it before you can use it. Always use the latest blob. |
   | `reference`                              |                                                                                             | Your reference to this payment modification, for use in your reconciliation process.                                                                                                                                                                                                                                                                                                                                                                                                 |
   | `merchantAccount`                        | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | The name of your merchant account that is used to process the payment.                                                                                                                                                                                                                                                                                                                                                                                                               |

   The following examples shows how to add a charge of EUR 64.15 to a pre-authorised amount of EUR 150.00.

   **Synchronous authorisation adjustment request**

   ```json
   {
       "originalReference":"8815754678001083",
       "modificationAmount": {
           "currency":"EUR",
           "value":21415
       },
       "reference":"YOUR_MODIFICATION_REFERENCE",
       "additionalData":{
           "adjustAuthorisationData":"BQABAQA+fbc==..."
       },
       "merchantAccount":"YOUR_MERCHANT_ACCOUNT"
   }
   ```

   The [/adjustAuthorisation](https://docs.adyen.com/api-explorer/#/Payment/adjustAuthorisation) response contains:

   * `additionalData.adjustAuthorisationData`: The new blob, for the new authorised amount. This blob is not URL-encoded.
   * `merchantReference`: Your reference to this payment modification, for use in your reconciliation process.
   * `pspReference`: The PSP reference associated with this [/adjustAuthorisation](https://docs.adyen.com/api-explorer/#/Payment/adjustAuthorisation) request. Note that this is different from the PSP reference associated with the pre-authorisation request.
   * `response`: **Authorised**. Indicates the new amount is authorised.

   **Synchronous authorisation adjustment response**

   ```json
   {
       "additionalData": {
           "adjustAuthorisationData": "BQABAQArqht7L...",
           "merchantReference": "YOUR_MODIFICATION_REFERENCE"
       },
       "pspReference": "8535762347980628",
       "response": "Authorised"
   }
   ```

2. Store the `adjustAuthorisationData` blob you received in the [/adjustAuthorisation](https://docs.adyen.com/api-explorer/#/Payment/adjustAuthorisation) response. You will need this if you later adjust the authorisation again. This blob is not URL-encoded, so you can use it as it is.

### Extend the authorisation

To extend the authorisation period make an [/adjustAuthorisation](https://docs.adyen.com/api-explorer/#/Payment/adjustAuthorisation) request with the same amount as the current balance on the authorisation:

* If you haven't adjusted the authorisation yet, use the amount from the original pre-authorisation request.
* If you did adjust the authorisation, use the amount from the last adjustment.

For Mastercard, the request made to adjust the pre-authorised amount automatically extends the validity period of the authorisation. So, if you have adjusted an authorisation, you do not immediately have to extend its validity.

We strongly recommend you to use the asynchronous flow to extend the authorisation. Visa only supports the asynchronous flow.

See [Adjust the authorisation](#adjust-the-amount) for instructions. To check the status of the authorisation (the original and the extension), make sure to consume webhooks.

For Visa and American Express, the issuer can refuse the request to extend the authorisation period. This refusal terminates the initially authorised payment. Check that you consume the webhook event to handle this situation by either withholding shipment or authorising the card again at a later time.

## Step 3: Finalize the pre-authorised payment

When you have made your last authorisation adjustment, you need to [manually capture the payment](/online-payments/classic-integrations/modify-payments/capture#manual-capture) to transfer the reserved funds to your account:

1. Decide whether you are ready to capture the payment:

   * Are there any additional charges to be made?\
     If yes, adjust the authorisation first (see [Adjust the authorisation](#adjust-the-amount)).

   * Does the shopper want to settle the bill using a different payment method than the one used for the pre-authorisation?\
     If yes, do not capture the payment. Instead, cancel the pre-authorisation:

     * Make a [/cancel](https://docs.adyen.com/api-explorer/#/Payment/cancel) request specifying the `pspReference` of the original pre-authorisation. Refer to [Cancel authorisation](/online-payments/classic-integrations/modify-payments/cancel) for more details.

2. When you are ready to capture the payment, make a POST request to the [/capture](https://docs.adyen.com/api-explorer/#/Payment/capture) endpoint, specifying:

   | Parameter            | Required                                                                                    | Description                                                                                                                                          |
   | -------------------- | ------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
   | `originalReference`  | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | The `pspReference` of the original pre-authorisation. You received this in the response to your pre-authorisation request.                           |
   | `modificationAmount` | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | The `currency` and `value` of the final amount **in minor units**. This is the sum of the original, pre-authorised amount and all later adjustments. |
   | `reference`          |                                                                                             | Your reference to this payment modification, for use in your reconciliation process.                                                                 |
   | `merchantAccount`    | ![-white\_check\_mark-](/user/data/smileys/emoji/white_check_mark.png "-white_check_mark-") | The name of your merchant account that is used to process the payment.                                                                               |

3. When you receive the [/capture](https://docs.adyen.com/api-explorer/#/Payment/capture) response, note the following:

   * `pspReference`: The PSP reference associated with this [/capture](https://docs.adyen.com/api-explorer/#/Payment/capture) request. Note that this is different from the PSP reference associated with the pre-authorisation request.
   * `response`: **\[capture-received]**.
   * `additionalData.merchantReference`: Your reference to this payment modification, for use in your reconciliation process.

4. Wait for the [webhook event](/development-resources/webhooks). This informs you whether the final amount has been captured.\
   If the capture is successful, this event contains:

   * `eventCode`: **CAPTURE**
   * `originalReference`: The `pspReference` of the pre-authorisation.
   * `pspReference`: The PSP reference associated with this [/capture](https://docs.adyen.com/api-explorer/#/Payment/capture)\` request.
   * `success`: **true**

   If `success` is **false** then your capture request failed. Review the `reason` you received in the webhook event, fix the issue, and submit the capture request again.

If you need to charge the guest for an additional amount after they have left, and you [stored your shopper's payment details (token)](/online-payments/tokenization/make-token-payments) with your pre-authorisation request, you can apply these late charges in a recurring payment request using the token. See [Recurring payments](/online-payments/tokenization/make-token-payments).

You can combine the steps listed before to fulfill your use case. For example, if you want to do multiple partial captures, modify the amount authorised after the first partial capture. To do so, [pre-authorise a payment](#pre-authorise), partially capture the payment, and then [adjust the authorisation amount](#adjust-the-amount).

## Availability

Authorization adjustment is available for the following payment methods:

| Payment method | Availability                                                                                                                                                                                                                                                                                                                                                      |   |
| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | - |
| Card           | Card schemes set specific rules around which businesses can adjust authorizations. Your eligibility is determined by your [Merchant Category Code (MCC)](/get-started-with-adyen/adyen-glossary/#merchant-category-code). For a business type, each card scheme uses a different MCC. See which [schemes support which MCC codes](#mcc-authorization-adjustment). |   |
| Apple Pay      | Available if the card associated with the Apple Pay wallet is from a card scheme for which authorization adjustment is available.                                                                                                                                                                                                                                 |   |
| Google Pay     | Available if the card associated with the Google Pay wallet is from a card scheme for which authorization adjustment is available.                                                                                                                                                                                                                                |   |

### Merchant Category Code (MCC) and authorization adjustment

To view your MCCs for each payment method:

1. Log in to your [live Customer Area](https://ca-live.adyen.com/).
2. Switch to your merchant account.
3. Select **Settings** > **Payment methods**.
4. Find the line for the specific payment method. The **MCC** column shows your MCC for that payment method.

The following table shows, for each card scheme, which MCC codes authorization adjustment is available for:

| Card scheme                  | Merchant Category Codes (MCC) for which authorization adjustment is available                                                                                                                                              |
| ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| American Express             | All MCCs except 5542                                                                                                                                                                                                       |
| Discover                     | 3351-3441, 3501-3999, 4111, 4112, 4121, 4131, 4411, 4457, 5499, 5812, 5813, 7011, 7033, 7996, 7394, 7512, 7513, 7519, 7999                                                                                                 |
| Mastercard                   | All MCCs except 5542                                                                                                                                                                                                       |
| Mexico Domestic (Network MX) | Card present: 4722, 5541, 5542, 5812, 5813, 8062, multiple MCCs for car rental, entertainment, and hotels Card not present: 4011, 4112, 4121, 4131, 4816, 5300, 5310, 5311, 5331, 5411, 5422, 5814, all air transportation |
| Visa                         | All MCCs except 5542 Authorization adjustment does not work for V Pay cards.                                                                                                                                               |
| China UnionPay               | 7011, 7512, 4411, 3xxx                                                                                                                                                                                                     |

## Expiration of authorizations

You can only adjust a pre-authorization that has not expired yet. There are two authorization validity periods to take into account:

* For the global card schemes, Adyen expires (pre-)authorization requests automatically after 28 days from the day the payment is authorized. Contact our [Support Team](https://ca-test.adyen.com/ca/ca/contactUs/support.shtml?form=other) if you want to change this default setting, and configure custom authorization validity periods for specific merchant accounts and card schemes.

  The maximum allowable partial captures against a single pre-authorization is determined by the issuer.

* Card schemes have their own rules on authorization validity, and can expire a pre-authorization before or after the scheme's official authorization validity period. Using [manual capture](/online-payments/capture#manual-capture) it is possible to capture remaining balance on a payment after an authorization has already expired on the card scheme's side, but this practice increases the risk of:

  * A [failed capture](/online-payments/capture#failed-capture).
  * Increased interchange fees.
  * Card scheme transaction fees.
  * A cardholder-initiated [chargeback](/risk-management/understanding-disputes/dispute-reason-codes) for 'No Authorization' or 'Late Presentment' reasons.

The following tables include information on authorization validity periods for major card schemes **that allow authorization adjustment**.

### American Express

| Scheme | Debit/credit | Environment | [Authorization type](#authorisation-types) | MCC | Days   |
| ------ | ------------ | ----------- | ------------------------------------------ | --- | ------ |
| Amex   | All          | All         | All                                        | All | 7 days |

### Cartes Bancaires

| Scheme          | Debit/credit | Environment | [Authorization type](#authorisation-types) | MCC | Days    |
| --------------- | ------------ | ----------- | ------------------------------------------ | --- | ------- |
| Carte Bancaires | All          | All         | All                                        | All | 12 days |

### China UnionPay

* 30 Days from the initial authorisation.
* Authorisation adjustment does not extend the authorisation validity period.

### Diners

| Scheme | Debit/credit | Environment | [Authorization type](#authorisation-types) | MCC                       | Days    |
| ------ | ------------ | ----------- | ------------------------------------------ | ------------------------- | ------- |
| Diners | All          | MOTO        | All                                        | All                       | 7 days  |
| Diners | Debit        | All         | All                                        | All                       | 7 days  |
| Diners | Credit       | All         | All                                        | All                       | 30 days |
| Diners | All          | All         | All                                        | Car Rental, Hotel/Lodging | 30 days |

### Discover

| Scheme   | Debit/credit | Environment | [Authorization type](#authorisation-types) | MCC                       | Days    |
| -------- | ------------ | ----------- | ------------------------------------------ | ------------------------- | ------- |
| Discover | All          | All         | All                                        | All                       | 10 days |
| Discover | All          | All         | All                                        | Car Rental, Hotel/Lodging | 30 days |

### JCB

| Scheme | Debit/credit | Environment | [Authorization type](#authorisation-types) | MCC                  | Days                |
| ------ | ------------ | ----------- | ------------------------------------------ | -------------------- | ------------------- |
| JCB    | All          | All         | All                                        | All                  | 1 year              |
| JCB    | All          | All         | Pre-auth                                   | Hotel and Car rental | Time of stay/rental |

### Mastercard

| Scheme     | Debit/credit | Environment | [Authorization type](#authorisation-types) | MCC | Days    |
| ---------- | ------------ | ----------- | ------------------------------------------ | --- | ------- |
| Mastercard | All          | All         | Final auth                                 | All | 7 days  |
| Mastercard | All          | All         | Pre-auth                                   | All | 30 days |

Capturing Mastercard payments can be successful even when the authorization has expired after seven or 30 days. For domestic transactions in the US and Canada, there is a late capture fee.

### Mexico Domestic

| Scheme     | Debit/credit | Environment | [Authorization type](#authorisation-types) | MCC | Days     |
| ---------- | ------------ | ----------- | ------------------------------------------ | --- | -------- |
| Network MX | Debit        | All         | Final auth                                 | All | 7 days   |
| Network MX | Credit       | All         | Final auth                                 | All | 30 days  |
| Network MX | Debit        | All         | Pre-auth                                   | All | 30 days  |
| Network MX | Credit       | All         | Pre-auth                                   | All | 120 days |

### Visa

| Scheme        | Debit/credit | Environment                                                                                                                                                                                                                           | [Authorization type](#authorisation-types) | MCC                                      | Days    |
| ------------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------ | ---------------------------------------- | ------- |
| Visa electron | All          | All                                                                                                                                                                                                                                   | All                                        | All                                      | 5 days  |
| Visa          | All          | POS                                                                                                                                                                                                                                   | All                                        | All                                      | 5 days  |
| Visa          | All          | Merchant initiated transactions (MIT) *Applies to:* * ContAuth + Subscription / UnscheduledCardOnFile                                                                                                                                 | All                                        | All                                      | 5 days  |
| Visa          | All          | [CNP](https://docs.adyen.com/get-started-with-adyen/adyen-glossary/#card-not-present-cnp) Cardholder-initiated transactions (CIT) *Applies to:* * Ecommerce / ContAuth + CardOnFile* Ecommerce + Subscription / UnscheduledCardOnFile | All                                        | All                                      | 10 days |
| Visa          | All          | [CNP](https://docs.adyen.com/get-started-with-adyen/adyen-glossary/#card-not-present-cnp) Cardholder-initiated transactions (CIT) *Applies to:* * Ecommerce / ContAuth + CardOnFile* Ecommerce + Subscription / UnscheduledCardOnFile | Extended-Auth[ 1](#exauth)                 | All                                      | 30 days |
| Visa          | All          | All                                                                                                                                                                                                                                   | Pre-Auth                                   | Cruise, Lodging, Vehicle Rental          | 30 days |
| Visa          | All          | All                                                                                                                                                                                                                                   | Pre-Auth                                   | 7999, 4457, 7296, 7841, 7394, 7519, 7033 | 10 days |
| Visa          | All          | All                                                                                                                                                                                                                                   | Pre-Auth                                   | 5542                                     | 2 hours |

Capturing Visa payments after the authorization validity period may result in [capture failures](https://docs.adyen.com/online-payments/capture/failure-reasons/#capture-cant-be-recaptured) and processing integrity fees. Capturing Visa cardholder-initiated card-not-present transactions (CIT CnP) after the 10-day validity period may also incur an additional Extended Authorisation scheme fee, depending on regional requirements.

[]()1 Visa's "Extended-Auth" feature is currently available only in pilot. If you would like to pilot this feature and provide feedback, reach out to your Adyen point of contact our [Support Team](https://ca-test.adyen.com/ca/ca/contactUs/support.shtml?form=other).

## See also

* [API Explorer](https://docs.adyen.com/api-explorer/?classes=codeLabel#/Payment/adjustAuthorisation)
* [Capture](/online-payments/classic-integrations/modify-payments/capture)
* [Webhooks](/development-resources/webhooks)
