---
title: "Authorization adjustment"
description: "Learn the differences between pre-authorization and final authorization, asynchronous and synchronous adjustment, and when authorization adjustment is available."
url: "https://docs.adyen.com/online-payments/adjust-authorisation"
source_url: "https://docs.adyen.com/online-payments/adjust-authorisation.md"
canonical: "https://docs.adyen.com/online-payments/adjust-authorisation"
last_modified: "2023-08-02T22:12:00+02:00"
language: "en"
---

# Authorization adjustment

Learn the differences between pre-authorization and final authorization, asynchronous and synchronous adjustment, and when authorization adjustment is available.

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

In a basic payment flow, the payable amount from your payment request is [authorized](/get-started-with-adyen/adyen-glossary/#authorization?target=_blank) and then [captured](/get-started-with-adyen/adyen-glossary/#capture-or-clearing-and-settlement?target=_blank). But sometimes you want to change the amount or extend the length of the authorization. Using the [authorization type](#authorisation-types?target=_blank) **pre-authorization** for your payment request, you can increase or decrease the authorized amount at a later stage, and then capture the payment manually. Changes to a pre-authorized payment are called "authorization adjustments".

## Requirements

Before you begin, consider the following requirements, limitations, and preparations:

| Requirements                                    | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
| ----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Integration type**                            | An [online payments integration](/online-payments/build-your-integration).                                                                                                                                                                                                                                                                                                                                                                                                                                                     |
| **[Webhooks](/development-resources/webhooks)** | Listen for [Standard webhook messages](/development-resources/webhooks/webhook-types#default-event-codes) with the following `eventCode` values:- **AUTHORISATION\_ADJUSTMENT**
- **CAPTURE**
- **CAPTURE\_FAILED**                                                                                                                                                                                                                                                                                                            |
| **Limitations**                                 | Note the following limitations:- [Support for authorization adjustment](/online-payments/adjust-authorisation/#availability) is limited to specific payment methods and Merchant Category Codes (MCC). It is ultimately up to the issuing bank whether they allow it.
- Pre-authorizations and authorizations [eventually expire](/online-payments/adjust-authorisation/#validity). The length of an authorization's validity depends on the card scheme.
- You can only adjust authorizations for payments acquired by Adyen. |

## Use cases

There are several use cases for adjusting a pre-authorized amount:

* Hospitality. For example, in a hotel:

  1. Just before the guest checks in, or when the guest checks in using an app or in person, the hotel pre-authorizes payment of the guest's room. 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-authorized amount by adjusting the authorization.
  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:

  1. A shopper pre-orders a video game that will be released three months later.
  2. The video game seller pre-authorizes the payment.
  3. The video game seller extends the validity period of the pre-authorization, because they must wait three months to ship the video game.

- Orders with a high Average Transaction Value (ATV) and long delivery times, where the basket composition and amount has changed by the time the payment is ready for capture.

## Authorization type

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

* **Pre-authorization**: this authorization type verifies that the shopper's account is valid and has sufficient funds to cover a transaction, but does not debit the account. It 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 authorized amount at a later point in time.

* **Final authorization**: the final amount is agreed up front and the transaction will be captured in full. This is the default authorization type, and it doesn't allow you to adjust the authorized amount later.

By default, Adyen handles all card payment requests as final authorizations. You can manually specify the authorization type as `additionalData.authorisationType`:**PreAuth** or `additionalData.authorisationType`:**FinalAuth** in each payment request. See [Pre-authorize a payment](/online-payments/adjust-authorisation/adjust-with-preauth#pre-authorize).

## Asynchronous or synchronous adjustment

There are two ways to implement pre-authorization:

* **Asynchronous authorization adjustment**: you refer to a payment using the PSP reference that you received in the response to your pre-authorization request. In each authorization adjustment request, and in the final capture request, you specify this first PSP reference.

  Asynchronous adjustment is easier to implement, but it is not immediately clear if the adjustment succeeded. You must [set up webhooks](/development-resources/webhooks) to receive updates and to know if the final amount was authorized before you capture the payment.

* **Synchronous authorization adjustment**: you pass an `adjustAuthorisationData` blob from one request to the next, to enable us to keep track of the latest amount. You receive the first blob in the response to your pre-authorization request. In your first authorization adjustment request, you specify the blob you received for the pre-authorization, 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 more effort to implement, because you need to keep track of the latest blob. The advantage is that you receive the adjustment result synchronously. In this way you immediately know if the final amount was authorized before you capture the payment.

  If at any point 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.

## 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.                                                                                                                                                                                                                                |   |
| Klarna         | Authorization adjustment is available for payments that have not been cancelled, expired, or fully captured. We only support asynchronous authorization adjustment.                                                                                                                                                                                               |   |

### 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 pre-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).

## Next steps

[required](/online-payments/adjust-authorisation/adjust-with-preauth)

[Adjust an authorization](/online-payments/adjust-authorisation/adjust-with-preauth)

[Implement pre-authorization and authorization adjustment.](/online-payments/adjust-authorisation/adjust-with-preauth)
