{"title":"Pre-authorisation and authorisation adjustment","category":"default","creationDate":1776961627,"content":"<p>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 <a href=\"#authorisation-types\">authorisation type<\/a> <em>pre-authorisation<\/em> 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.<\/p>\n<div class=\"sc-notice note\"><div>\n<p>Authorisation adjustment is currently available for Discover, Mastercard, Visa, and American Express. Support is ultimately up to the issuer. See <a href=\"#availability\">Availability<\/a> for more information.<\/p>\n<\/div><\/div>\n<h3>Use cases<\/h3>\n<p>There are several use cases for adjusting an authorisation:<\/p>\n<ul>\n<li>\n<p>Hospitality. For example, in a hotel:<\/p>\n<ol>\n<li>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 <a href=\"\/pt\/online-payments\/tokenization\">stores the shopper's payment information<\/a>, to be able to apply late charges when necessary.<\/li>\n<li>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.<\/li>\n<li>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.<\/li>\n<li>If necessary, the hotel charges the guest after they have left, using the shopper's stored payment details for a new payment.<\/li>\n<\/ol>\n<\/li>\n<li>\n<p>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.<\/p>\n<\/li>\n<\/ul>\n<h2 id=\"authorisation-types\">Authorisation types<\/h2>\n<p>For some card schemes, you can set card payment requests to be handled as either a pre-authorisation or a final authorisation.<\/p>\n<ul>\n<li><strong>Pre-authorisation<\/strong>: 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 <a href=\"https:\/\/docs.adyen.com\/api-explorer\/#\/Payment\/adjustAuthorisation\" class=\"codeLabel external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/adjustAuthorisation<\/a> endpoint.<\/li>\n<li><strong>Final authorisation<\/strong>: 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.<\/li>\n<\/ul>\n<div class=\"notices blue\">\n<p>By default, Adyen handles all card payment requests as final authorisations.<\/p>\n<\/div>\n<p>To set an authorisation type, you can either:<\/p>\n<ul>\n<li>Define the default authorisation type at the merchant account level for all card transactions. See <a href=\"#configure-account\">Configure your account<\/a>.<\/li>\n<li>Manually specify the authorisation type (<strong>PreAuth<\/strong> or <strong>FinalAuth<\/strong>) in each payment request. See <a href=\"#pre-authorise\">Pre-authorise a payment<\/a>.<\/li>\n<\/ul>\n<h2>Asynchronous or synchronous adjustment<\/h2>\n<p>There are two ways to implement pre-authorisation:<\/p>\n<ul>\n<li>\n<p>With <strong>asynchronous authorisation adjustment<\/strong>, 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.<\/p>\n<p>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.<\/p>\n<\/li>\n<li>\n<p>With <strong>synchronous authorisation adjustment<\/strong>, you pass an <code>adjustAuthorisationData<\/code> 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.<\/p>\n<p>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.<\/p>\n<div class=\"sc-notice note\"><div>\n<p>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.<\/p>\n<\/div><\/div>\n<\/li>\n<\/ul>\n<h2>Requirements<\/h2>\n<p>Before you configure and use pre-authorisation:<\/p>\n<ol>\n<li>Make sure that you have built an integration that can make a payment.<\/li>\n<li><a href=\"\/pt\/development-resources\/webhooks\">Set up webhooks<\/a>. 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.<\/li>\n<\/ol>\n<p>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.<\/p>\n<h2 id=\"configure-account\">(Optional) Configure your account<\/h2>\n<p>There are two aspects of your account that you may want to configure for pre-authorisation and authorisation adjustment:<\/p>\n<ul>\n<li>\n<p><strong>Synchronous authorisation adjustment<\/strong>: To receive the initial <code>adjustAuthorisationData<\/code> blob with your pre-authorisation request and to subsequently receive the authorisation adjustment results synchronously, ask our <a href=\"https:\/\/ca-test.adyen.com\/ca\/ca\/contactUs\/support.shtml?form=other\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Support Team<\/a> to enable this.<\/p>\n<\/li>\n<li>\n<p><strong>Default authorisation type<\/strong>: If you only do pre-authorisation payment requests, you can ask our <a href=\"https:\/\/ca-test.adyen.com\/ca\/ca\/contactUs\/support.shtml?form=other\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Support Team<\/a> to set your default <a href=\"#authorisation-types\">authorisation type<\/a> to <strong>PreAuth<\/strong> so that you do not have to specify it in your payment requests.<\/p>\n<div class=\"sc-notice note\"><div>\n<p>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.<\/p>\n<\/div><\/div>\n<\/li>\n<\/ul>\n<h2 id=\"pre-authorise\">Step 1: Pre-authorise a payment<\/h2>\n<ol>\n<li>\n<p>Make a payment request, and additionally specify:<\/p>\n<ul>\n<li><code>additionalData.authorisationType<\/code>: <code>PreAuth<\/code><\/li>\n<\/ul>\n<div data-component-wrapper=\"code-sample\">\n<code-sample :title=\"''\" :id=\"'preauthorisation'\" :code-data='[{\"language\":\"json\",\"tabTitle\":\"\",\"content\":[{\"name\":\"request\",\"content\":\"{\\n   \\\"reference\\\":\\\"YOUR_ORDER_NUMBER\\\",\\n   \\\"merchantAccount\\\":\\\"YOUR_MERCHANT_ACCOUNT\\\",\\n   \\\"paymentMethod\\\": {\\n      \\\"type\\\": \\\"scheme\\\",\\n      \\\"number\\\":\\\"4111111111111111\\\",\\n      \\\"cvc\\\":\\\"737\\\",\\n      \\\"expiryMonth\\\":\\\"03\\\",\\n      \\\"expiryYear\\\":\\\"2030\\\",\\n      \\\"holderName\\\":\\\"John Smith\\\"\\n   },\\n   \\\"amount\\\":{\\n      \\\"currency\\\":\\\"EUR\\\",\\n      \\\"value\\\":1500\\n   },\\n   \\\"additionalData\\\":{\\n      \\\"authorisationType\\\":\\\"PreAuth\\\"\\n   }\\n}\"},{\"name\":\"response\",\"content\":\"{\\n  \\\"pspReference\\\": \\\"8884689190961333\\\",\\n  \\\"resultCode\\\": \\\"Authorised\\\"\\n}\"}]}]' :enable-copy-link-to-code-block=\"true\" :code-sample-card-size=\"'fullsize'\"><\/code-sample>\n<\/div>\n<\/li>\n<li>\n<p>Store the <code>pspReference<\/code> from the response for later use when adjusting the authorisation or capturing the payment.<\/p>\n<\/li>\n<\/ol>\n<h2 id=\"adjust-authorisation\">Step 2: (Optional) Modify the authorisation<\/h2>\n<div class=\"notices blue\">\n<p>You cannot make a zero-value authorisation when you adjust an authorisation.<\/p>\n<\/div>\n<h3 id=\"adjust-the-amount\">Adjust the pre-authorisation amount<\/h3>\n<p>To modify the pre-authorised amount, make an authorisation adjustment request.<\/p>\n\n<div id=\"tabAlxL6\">\n    <div data-component-wrapper=\"tabs\">\n        <tabs\n                        :items=\"[{&quot;title&quot;:&quot;Asynchronous authorisation adjustment&quot;,&quot;content&quot;:&quot;\\n&lt;ol&gt;\\n&lt;li&gt;\\n&lt;p&gt;Make a POST request to the &lt;a href=\\&quot;https:\\\/\\\/docs.adyen.com\\\/api-explorer\\\/#\\\/Payment\\\/adjustAuthorisation\\&quot; class=\\&quot;codeLabel external-link no-image\\&quot; target=\\&quot;_blank\\&quot; rel=\\&quot;nofollow noopener noreferrer\\&quot;&gt;\\\/adjustAuthorisation&lt;\\\/a&gt; endpoint, specifying:&lt;\\\/p&gt;\\n&lt;table&gt;\\n&lt;thead&gt;\\n&lt;tr&gt;\\n&lt;th style=\\&quot;text-align: left;\\&quot;&gt;Parameter&lt;\\\/th&gt;\\n&lt;th style=\\&quot;text-align: center;\\&quot;&gt;Required&lt;\\\/th&gt;\\n&lt;th style=\\&quot;text-align: left;\\&quot;&gt;Description&lt;\\\/th&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/thead&gt;\\n&lt;tbody&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;originalReference&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: center;\\&quot;&gt;&lt;img title=\\&quot;-white_check_mark-\\&quot; alt=\\&quot;-white_check_mark-\\&quot; class=\\&quot;smileys\\&quot; src=\\&quot;\\\/user\\\/data\\\/smileys\\\/emoji\\\/white_check_mark.png\\&quot; \\\/&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The &lt;code&gt;pspReference&lt;\\\/code&gt; of the pre-authorisation request. You received this in the response to your pre-authorisation request.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;modificationAmount&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: center;\\&quot;&gt;&lt;img title=\\&quot;-white_check_mark-\\&quot; alt=\\&quot;-white_check_mark-\\&quot; class=\\&quot;smileys\\&quot; src=\\&quot;\\\/user\\\/data\\\/smileys\\\/emoji\\\/white_check_mark.png\\&quot; \\\/&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The &lt;code&gt;currency&lt;\\\/code&gt; and &lt;code&gt;value&lt;\\\/code&gt; of the new amount &lt;strong&gt;in minor units&lt;\\\/strong&gt;. This is the sum of the pre-authorised amount and the additional amount. &lt;br&gt; If this is not the first authorisation adjustment, it is the sum of the pre-authorised amount plus all additional amounts.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;additionalData.industryUsage&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: center;\\&quot;&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;strong&gt;DelayedCharge&lt;\\\/strong&gt;&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;reference&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: center;\\&quot;&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;Your reference to this payment modification, for use in your reconciliation process.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;merchantAccount&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: center;\\&quot;&gt;&lt;img title=\\&quot;-white_check_mark-\\&quot; alt=\\&quot;-white_check_mark-\\&quot; class=\\&quot;smileys\\&quot; src=\\&quot;\\\/user\\\/data\\\/smileys\\\/emoji\\\/white_check_mark.png\\&quot; \\\/&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The name of your merchant account that is used to process the payment.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/tbody&gt;\\n&lt;\\\/table&gt;\\n&lt;p&gt;The following example shows how to add a charge of EUR&amp;nbsp;64.15 to a pre-authorised amount of EUR&amp;nbsp;150.00.&lt;\\\/p&gt;\\n&lt;div data-component-wrapper=\\&quot;code-sample\\&quot;&gt;\\n&lt;code-sample :title=\\&quot;&#039;Asynchronous authorisation adjustment request&#039;\\&quot; :id=\\&quot;&#039;&#039;\\&quot; :code-data=&#039;[{\\&quot;language\\&quot;:\\&quot;json\\&quot;,\\&quot;tabTitle\\&quot;:\\&quot;\\&quot;,\\&quot;content\\&quot;:\\&quot;{\\\\n    \\\\\\&quot;originalReference\\\\\\&quot;:\\\\\\&quot;8815754678001083\\\\\\&quot;,\\\\n    \\\\\\&quot;modificationAmount\\\\\\&quot;: {\\\\n        \\\\\\&quot;currency\\\\\\&quot;:\\\\\\&quot;EUR\\\\\\&quot;,\\\\n        \\\\\\&quot;value\\\\\\&quot;:21415\\\\n    },\\\\n    \\\\\\&quot;additionalData\\\\\\&quot;:{\\\\n        \\\\\\&quot;industryUsage\\\\\\&quot;:\\\\\\&quot;DelayedCharge\\\\\\&quot;\\\\n    },\\\\n    \\\\\\&quot;reference\\\\\\&quot;:\\\\\\&quot;YOUR_MODIFICATION_REFERENCE\\\\\\&quot;,\\\\n    \\\\\\&quot;merchantAccount\\\\\\&quot;:\\\\\\&quot;YOUR_MERCHANT_ACCOUNT\\\\\\&quot;\\\\n}\\&quot;}]&#039; :enable-copy-link-to-code-block=\\&quot;true\\&quot; :code-sample-card-size=\\&quot;&#039;fullsize&#039;\\&quot;&gt;&lt;\\\/code-sample&gt;\\n&lt;\\\/div&gt;\\n&lt;p&gt;The &lt;a href=\\&quot;https:\\\/\\\/docs.adyen.com\\\/api-explorer\\\/#\\\/Payment\\\/adjustAuthorisation\\&quot; class=\\&quot;codeLabel external-link no-image\\&quot; target=\\&quot;_blank\\&quot; rel=\\&quot;nofollow noopener noreferrer\\&quot;&gt;\\\/adjustAuthorisation&lt;\\\/a&gt; response contains:&lt;\\\/p&gt;\\n&lt;ul&gt;\\n&lt;li&gt;&lt;code&gt;pspReference&lt;\\\/code&gt;: The PSP reference associated with this &lt;a href=\\&quot;https:\\\/\\\/docs.adyen.com\\\/api-explorer\\\/#\\\/Payment\\\/adjustAuthorisation\\&quot; class=\\&quot;codeLabel external-link no-image\\&quot; target=\\&quot;_blank\\&quot; rel=\\&quot;nofollow noopener noreferrer\\&quot;&gt;\\\/adjustAuthorisation&lt;\\\/a&gt; request. Note that this is different from the PSP reference associated with the pre-authorisation request.&lt;\\\/li&gt;\\n&lt;li&gt;&lt;code&gt;response&lt;\\\/code&gt;: &lt;strong&gt;[adjustAuthorisation-received]&lt;\\\/strong&gt;&lt;\\\/li&gt;\\n&lt;\\\/ul&gt;\\n&lt;div data-component-wrapper=\\&quot;code-sample\\&quot;&gt;\\n&lt;code-sample :title=\\&quot;&#039;Asynchronous authorisation adjustment response&#039;\\&quot; :id=\\&quot;&#039;&#039;\\&quot; :code-data=&#039;[{\\&quot;language\\&quot;:\\&quot;json\\&quot;,\\&quot;tabTitle\\&quot;:\\&quot;\\&quot;,\\&quot;content\\&quot;:\\&quot;{\\\\n  \\\\\\&quot;pspReference\\\\\\&quot;: \\\\\\&quot;881576235454101H\\\\\\&quot;,\\\\n  \\\\\\&quot;response\\\\\\&quot;: \\\\\\&quot;[adjustAuthorisation-received]\\\\\\&quot;\\\\n}\\&quot;}]&#039; :enable-copy-link-to-code-block=\\&quot;true\\&quot; :code-sample-card-size=\\&quot;&#039;fullsize&#039;\\&quot;&gt;&lt;\\\/code-sample&gt;\\n&lt;\\\/div&gt;\\n&lt;\\\/li&gt;\\n&lt;li&gt;\\n&lt;p&gt;Wait for the &lt;a href=\\&quot;\\\/pt\\\/development-resources\\\/webhooks\\&quot;&gt;webhook event&lt;\\\/a&gt;. This informs you whether the new amount has been authorised.&lt;\\\/p&gt;\\n&quot;,&quot;altTitle&quot;:null,&quot;oldTabId&quot;:&quot;asynchronous_authorisation_adjustment_0_1&quot;,&quot;relation&quot;:&quot;&quot;},{&quot;title&quot;:&quot;Synchronous authorisation adjustment&quot;,&quot;content&quot;:&quot;\\n&lt;ol&gt;\\n&lt;li&gt;\\n&lt;p&gt;Make a POST request to the &lt;a href=\\&quot;https:\\\/\\\/docs.adyen.com\\\/api-explorer\\\/#\\\/Payment\\\/adjustAuthorisation\\&quot; class=\\&quot;codeLabel external-link no-image\\&quot; target=\\&quot;_blank\\&quot; rel=\\&quot;nofollow noopener noreferrer\\&quot;&gt;\\\/adjustAuthorisation&lt;\\\/a&gt; endpoint, specifying:&lt;\\\/p&gt;\\n&lt;table&gt;\\n&lt;thead&gt;\\n&lt;tr&gt;\\n&lt;th style=\\&quot;text-align: left;\\&quot;&gt;Parameter&lt;\\\/th&gt;\\n&lt;th style=\\&quot;text-align: center;\\&quot;&gt;Required&lt;\\\/th&gt;\\n&lt;th style=\\&quot;text-align: left;\\&quot;&gt;Description&lt;\\\/th&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/thead&gt;\\n&lt;tbody&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;originalReference&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: center;\\&quot;&gt;&lt;img title=\\&quot;-white_check_mark-\\&quot; alt=\\&quot;-white_check_mark-\\&quot; class=\\&quot;smileys\\&quot; src=\\&quot;\\\/user\\\/data\\\/smileys\\\/emoji\\\/white_check_mark.png\\&quot; \\\/&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The &lt;code&gt;pspReference&lt;\\\/code&gt; of the pre-authorisation request. You received this in the response to your pre-authorisation request.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;modificationAmount&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: center;\\&quot;&gt;&lt;img title=\\&quot;-white_check_mark-\\&quot; alt=\\&quot;-white_check_mark-\\&quot; class=\\&quot;smileys\\&quot; src=\\&quot;\\\/user\\\/data\\\/smileys\\\/emoji\\\/white_check_mark.png\\&quot; \\\/&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The &lt;code&gt;currency&lt;\\\/code&gt; and &lt;code&gt;value&lt;\\\/code&gt; of the new amount &lt;strong&gt;in minor units&lt;\\\/strong&gt;. This is the sum of the pre-authorised amount and the additional amount. &lt;br&gt; If this is not the first authorisation adjustment, it is the sum of the pre-authorised amount plus all additional amounts.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;additionalData.adjustAuthorisationData&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: center;\\&quot;&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The previous &lt;code&gt;adjustAuthorisationData&lt;\\\/code&gt; blob. &lt;br&gt; 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. &lt;br&gt; 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.&lt;br&gt; &lt;div class=\\&quot;sc-notice note\\&quot;&gt;&lt;div&gt; Always use the latest blob. &lt;\\\/div&gt;&lt;\\\/div&gt;&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;reference&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: center;\\&quot;&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;Your reference to this payment modification, for use in your reconciliation process.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;merchantAccount&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: center;\\&quot;&gt;&lt;img title=\\&quot;-white_check_mark-\\&quot; alt=\\&quot;-white_check_mark-\\&quot; class=\\&quot;smileys\\&quot; src=\\&quot;\\\/user\\\/data\\\/smileys\\\/emoji\\\/white_check_mark.png\\&quot; \\\/&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The name of your merchant account that is used to process the payment.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/tbody&gt;\\n&lt;\\\/table&gt;\\n&lt;p&gt;The following examples shows how to add a charge of EUR&amp;nbsp;64.15 to a pre-authorised amount of EUR&amp;nbsp;150.00.&lt;\\\/p&gt;\\n&lt;div data-component-wrapper=\\&quot;code-sample\\&quot;&gt;\\n&lt;code-sample :title=\\&quot;&#039;Synchronous authorisation adjustment request&#039;\\&quot; :id=\\&quot;&#039;&#039;\\&quot; :code-data=&#039;[{\\&quot;language\\&quot;:\\&quot;json\\&quot;,\\&quot;tabTitle\\&quot;:\\&quot;\\&quot;,\\&quot;content\\&quot;:\\&quot;{\\\\n    \\\\\\&quot;originalReference\\\\\\&quot;:\\\\\\&quot;8815754678001083\\\\\\&quot;,\\\\n    \\\\\\&quot;modificationAmount\\\\\\&quot;: {\\\\n        \\\\\\&quot;currency\\\\\\&quot;:\\\\\\&quot;EUR\\\\\\&quot;,\\\\n        \\\\\\&quot;value\\\\\\&quot;:21415\\\\n    },\\\\n    \\\\\\&quot;reference\\\\\\&quot;:\\\\\\&quot;YOUR_MODIFICATION_REFERENCE\\\\\\&quot;,\\\\n    \\\\\\&quot;additionalData\\\\\\&quot;:{\\\\n        \\\\\\&quot;adjustAuthorisationData\\\\\\&quot;:\\\\\\&quot;BQABAQA+fbc==...\\\\\\&quot;\\\\n    },\\\\n    \\\\\\&quot;merchantAccount\\\\\\&quot;:\\\\\\&quot;YOUR_MERCHANT_ACCOUNT\\\\\\&quot;\\\\n}\\&quot;}]&#039; :enable-copy-link-to-code-block=\\&quot;true\\&quot; :code-sample-card-size=\\&quot;&#039;fullsize&#039;\\&quot;&gt;&lt;\\\/code-sample&gt;\\n&lt;\\\/div&gt;\\n&lt;p&gt;The &lt;a href=\\&quot;https:\\\/\\\/docs.adyen.com\\\/api-explorer\\\/#\\\/Payment\\\/adjustAuthorisation\\&quot; class=\\&quot;codeLabel external-link no-image\\&quot; target=\\&quot;_blank\\&quot; rel=\\&quot;nofollow noopener noreferrer\\&quot;&gt;\\\/adjustAuthorisation&lt;\\\/a&gt; response contains:&lt;\\\/p&gt;\\n&lt;ul&gt;\\n&lt;li&gt;&lt;code&gt;additionalData.adjustAuthorisationData&lt;\\\/code&gt;: The new blob, for the new authorised amount. This blob is not URL-encoded.&lt;\\\/li&gt;\\n&lt;li&gt;&lt;code&gt;merchantReference&lt;\\\/code&gt;: Your reference to this payment modification, for use in your reconciliation process.&lt;\\\/li&gt;\\n&lt;li&gt;&lt;code&gt;pspReference&lt;\\\/code&gt;: The PSP reference associated with this &lt;a href=\\&quot;https:\\\/\\\/docs.adyen.com\\\/api-explorer\\\/#\\\/Payment\\\/adjustAuthorisation\\&quot; class=\\&quot;codeLabel external-link no-image\\&quot; target=\\&quot;_blank\\&quot; rel=\\&quot;nofollow noopener noreferrer\\&quot;&gt;\\\/adjustAuthorisation&lt;\\\/a&gt; request. Note that this is different from the PSP reference associated with the pre-authorisation request.&lt;\\\/li&gt;\\n&lt;li&gt;&lt;code&gt;response&lt;\\\/code&gt;: &lt;strong&gt;Authorised&lt;\\\/strong&gt;. Indicates the new amount is authorised.&lt;\\\/li&gt;\\n&lt;\\\/ul&gt;\\n&lt;div data-component-wrapper=\\&quot;code-sample\\&quot;&gt;\\n&lt;code-sample :title=\\&quot;&#039;Synchronous authorisation adjustment response&#039;\\&quot; :id=\\&quot;&#039;&#039;\\&quot; :code-data=&#039;[{\\&quot;language\\&quot;:\\&quot;json\\&quot;,\\&quot;tabTitle\\&quot;:\\&quot;\\&quot;,\\&quot;content\\&quot;:\\&quot;{\\\\n    \\\\\\&quot;additionalData\\\\\\&quot;: {\\\\n        \\\\\\&quot;adjustAuthorisationData\\\\\\&quot;: \\\\\\&quot;BQABAQArqht7L...\\\\\\&quot;,\\\\n        \\\\\\&quot;merchantReference\\\\\\&quot;: \\\\\\&quot;YOUR_MODIFICATION_REFERENCE\\\\\\&quot;\\\\n    },\\\\n    \\\\\\&quot;pspReference\\\\\\&quot;: \\\\\\&quot;8535762347980628\\\\\\&quot;,\\\\n    \\\\\\&quot;response\\\\\\&quot;: \\\\\\&quot;Authorised\\\\\\&quot;\\\\n}\\&quot;}]&#039; :enable-copy-link-to-code-block=\\&quot;true\\&quot; :code-sample-card-size=\\&quot;&#039;fullsize&#039;\\&quot;&gt;&lt;\\\/code-sample&gt;\\n&lt;\\\/div&gt;\\n&lt;\\\/li&gt;\\n&lt;li&gt;\\n&lt;p&gt;Store the &lt;code&gt;adjustAuthorisationData&lt;\\\/code&gt; blob you received in the &lt;a href=\\&quot;https:\\\/\\\/docs.adyen.com\\\/api-explorer\\\/#\\\/Payment\\\/adjustAuthorisation\\&quot; class=\\&quot;codeLabel external-link no-image\\&quot; target=\\&quot;_blank\\&quot; rel=\\&quot;nofollow noopener noreferrer\\&quot;&gt;\\\/adjustAuthorisation&lt;\\\/a&gt; 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.&lt;\\\/p&gt;\\n&quot;,&quot;altTitle&quot;:null,&quot;oldTabId&quot;:&quot;synchronous_authorisation_adjustment_1_2&quot;,&quot;relation&quot;:&quot;&quot;}]\"\n            :should-update-when-url-changes='false'>\n        <\/tabs>\n    <\/div>\n<\/div>\n\n<\/li>\n<\/ol>\n<h3 id=\"extend-authorisation\">Extend the authorisation<\/h3>\n<p>To extend the authorisation period make an <a href=\"https:\/\/docs.adyen.com\/api-explorer\/#\/Payment\/adjustAuthorisation\" class=\"codeLabel external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/adjustAuthorisation<\/a> request with the same amount as the current balance on the authorisation:<\/p>\n<ul>\n<li>If you haven't adjusted the authorisation yet, use the amount from the original pre-authorisation request.<\/li>\n<li>If you did adjust the authorisation, use the amount from the last adjustment.<\/li>\n<\/ul>\n<div class=\"notices blue\">\n<p>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.<\/p>\n<\/div>\n<div class=\"notices yellow\">\n<p>We strongly recommend you to use the asynchronous flow to extend the authorisation. Visa only supports the asynchronous flow.<\/p>\n<\/div>\n<p>See <a href=\"#adjust-the-amount\">Adjust the authorisation<\/a> for instructions. To check the status of the authorisation (the original and the extension), make sure to consume webhooks.<\/p>\n<div class=\"notices yellow\">\n<p>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.<\/p>\n<\/div>\n<h2 id=\"capture-authorisation\">Step 3: Finalize the pre-authorised payment<\/h2>\n<p>When you have made your last authorisation adjustment, you need to <a href=\"\/pt\/online-payments\/classic-integrations\/modify-payments\/capture#manual-capture\">manually capture the payment<\/a> to transfer the reserved funds to your account:<\/p>\n<ol>\n<li>\n<p>Decide whether you are ready to capture the payment:<\/p>\n<ul>\n<li>\n<p>Are there any additional charges to be made?<br \/>\nIf yes, adjust the authorisation first (see <a href=\"#adjust-the-amount\">Adjust the authorisation<\/a>).<\/p>\n<!-- list separator -->\n<\/li>\n<li>\n<p>Does the shopper want to settle the bill using a different payment method than the one used for the pre-authorisation?<br \/>\nIf yes, do not capture the payment. Instead, cancel the pre-authorisation:<\/p>\n<ul>\n<li>\n<p>Make a <a href=\"https:\/\/docs.adyen.com\/api-explorer\/#\/Payment\/cancel\" class=\"codeLabel external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/cancel<\/a> request specifying the <code>pspReference<\/code> of the original pre-authorisation. Refer to <a href=\"\/pt\/online-payments\/classic-integrations\/modify-payments\/cancel\">Cancel authorisation<\/a> for more details.<\/p>\n<!-- list separator -->\n<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/li>\n<li>\n<p>When you are ready to capture the payment, make a POST request to the <a href=\"https:\/\/docs.adyen.com\/api-explorer\/#\/Payment\/capture\" class=\"codeLabel external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/capture<\/a> endpoint, specifying:<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Parameter<\/th>\n<th style=\"text-align: center;\">Required<\/th>\n<th style=\"text-align: left;\">Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><code>originalReference<\/code><\/td>\n<td style=\"text-align: center;\"><img title=\"-white_check_mark-\" alt=\"-white_check_mark-\" class=\"smileys\" src=\"\/user\/data\/smileys\/emoji\/white_check_mark.png\" \/><\/td>\n<td style=\"text-align: left;\">The <code>pspReference<\/code> of the original pre-authorisation. You received this in the response to your pre-authorisation request.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>modificationAmount<\/code><\/td>\n<td style=\"text-align: center;\"><img title=\"-white_check_mark-\" alt=\"-white_check_mark-\" class=\"smileys\" src=\"\/user\/data\/smileys\/emoji\/white_check_mark.png\" \/><\/td>\n<td style=\"text-align: left;\">The <code>currency<\/code> and <code>value<\/code> of the final amount <strong>in minor units<\/strong>. This is the sum of the original, pre-authorised amount and all later adjustments.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>reference<\/code><\/td>\n<td style=\"text-align: center;\"><\/td>\n<td style=\"text-align: left;\">Your reference to this payment modification, for use in your reconciliation process.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>merchantAccount<\/code><\/td>\n<td style=\"text-align: center;\"><img title=\"-white_check_mark-\" alt=\"-white_check_mark-\" class=\"smileys\" src=\"\/user\/data\/smileys\/emoji\/white_check_mark.png\" \/><\/td>\n<td style=\"text-align: left;\">The name of your merchant account that is used to process the payment.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/li>\n<li>\n<p>When you receive the <a href=\"https:\/\/docs.adyen.com\/api-explorer\/#\/Payment\/capture\" class=\"codeLabel external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/capture<\/a> response, note the following:<\/p>\n<ul>\n<li><code>pspReference<\/code>: The PSP reference associated with this <a href=\"https:\/\/docs.adyen.com\/api-explorer\/#\/Payment\/capture\" class=\"codeLabel external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/capture<\/a> request. Note that this is different from the PSP reference associated with the pre-authorisation request.<\/li>\n<li><code>response<\/code>: <strong>[capture-received]<\/strong>.<\/li>\n<li><code>additionalData.merchantReference<\/code>: Your reference to this payment modification, for use in your reconciliation process.<\/li>\n<\/ul>\n<\/li>\n<li>\n<p>Wait for the <a href=\"\/pt\/development-resources\/webhooks\">webhook event<\/a>. This informs you whether the final amount has been captured.<br \/>\nIf the capture is successful, this event contains:<\/p>\n<ul>\n<li><code>eventCode<\/code>: <strong>CAPTURE<\/strong><\/li>\n<li><code>originalReference<\/code>: The <code>pspReference<\/code> of the pre-authorisation.<\/li>\n<li><code>pspReference<\/code>: The PSP reference associated with this <a href=\"https:\/\/docs.adyen.com\/api-explorer\/#\/Payment\/capture\" class=\"codeLabel external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/capture<\/a>` request.<\/li>\n<li><code>success<\/code>: <strong>true<\/strong><\/li>\n<\/ul>\n<div class=\"sc-notice note\"><div>\n<p>If <code>success<\/code> is <strong>false<\/strong> then your capture request failed. Review the <code>reason<\/code> you received in the webhook event, fix the issue, and submit the capture request again.<\/p>\n<\/div><\/div>\n<\/li>\n<\/ol>\n<div class=\"sc-notice info\"><div>\n<p>If you need to charge the guest for an additional amount after they have left, and you <a href=\"\/pt\/online-payments\/tokenization\/make-token-payments\">stored your shopper's payment details (token)<\/a> with your pre-authorisation request, you can apply these late charges in a recurring payment request using the token. See <a href=\"\/pt\/online-payments\/tokenization\/make-token-payments\">Recurring payments<\/a>.<\/p>\n<\/div><\/div>\n<p>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, <a href=\"#pre-authorise\">pre-authorise a payment<\/a>, partially capture the payment, and then <a href=\"#adjust-the-amount\">adjust the authorisation amount<\/a>.<\/p>\n<h2 id=\"availability\">Availability<\/h2>\n<p>Authorization adjustment is available for the following payment methods:<\/p>\n<table>\n<thead>\n<tr>\n<th>Payment method<\/th>\n<th>Availability<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Card<\/td>\n<td>Card schemes set specific rules around which businesses can adjust authorizations. Your eligibility is determined by your <a href=\"\/pt\/get-started-with-adyen\/adyen-glossary\/#merchant-category-code\" target=\"_blank\">Merchant Category Code (MCC)<\/a>. For a business type, each card scheme uses a different MCC. See which <a href=\"#mcc-authorization-adjustment\">schemes support which MCC codes<\/a>.<\/td>\n<\/tr>\n<tr>\n<td>Apple Pay<\/td>\n<td>Available if the card associated with the Apple Pay wallet is from a card scheme for which authorization adjustment is available.<\/td>\n<\/tr>\n<tr>\n<td>Google Pay<\/td>\n<td>Available if the card associated with the Google Pay wallet is from a card scheme for which authorization adjustment is available.<\/td>\n<td><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3 id=\"mcc-authorization-adjustment\">Merchant Category Code (MCC) and authorization adjustment<\/h3>\n<p>To view your MCCs for each payment method:<\/p>\n<ol>\n<li>Log in to your <a href=\"https:\/\/ca-live.adyen.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">live Customer Area<\/a>.<\/li>\n<li>Switch to your merchant account.<\/li>\n<li>Select <strong>Settings<\/strong> &gt; <strong>Payment methods<\/strong>.<\/li>\n<li>Find the line for the specific payment method. The <strong>MCC<\/strong> column shows your MCC for that payment method.<\/li>\n<\/ol>\n<p>The following table shows, for each card scheme, which MCC codes authorization adjustment is available for:<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Card scheme<\/th>\n<th style=\"text-align: left;\">Merchant Category Codes (MCC) for which authorization adjustment is available<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">American Express<\/td>\n<td style=\"text-align: left;\">All MCCs except 5542<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Discover<\/td>\n<td style=\"text-align: left;\">3351-3441, 3501-3999, 4111, 4112, 4121, 4131, 4411, 4457,  5499, 5812, 5813, 7011, 7033, 7996, 7394, 7512, 7513, 7519, 7999<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Mastercard<\/td>\n<td style=\"text-align: left;\">All MCCs except 5542<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Mexico Domestic (Network MX)<\/td>\n<td style=\"text-align: left;\">Card present: 4722, 5541, 5542, 5812, 5813, 8062, multiple MCCs for car rental, entertainment, and hotels <br>Card not present: 4011, 4112, 4121, 4131, 4816, 5300, 5310, 5311, 5331, 5411, 5422, 5814, all air transportation<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Visa<\/td>\n<td style=\"text-align: left;\">All MCCs except 5542 <br\/><div class=\"notices blue\">Authorization adjustment does not work for V Pay cards.<\/div><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">China UnionPay<\/td>\n<td style=\"text-align: left;\">7011, 7512, 4411, 3xxx<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2 id=\"validity\">Expiration of authorizations<\/h2>\n<p>You can only adjust a pre-authorization that has not expired yet. There are two authorization validity periods to take into account:<\/p>\n<ul>\n<li>\n<p>For the global card schemes, Adyen expires (pre-)authorization requests automatically after 28 days from the day the payment is authorized. Contact our <a href=\"https:\/\/ca-test.adyen.com\/ca\/ca\/contactUs\/support.shtml?form=other\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Support Team<\/a> if you want to change this default setting, and configure custom authorization validity periods for specific merchant accounts and card schemes.<\/p>\n<\/li>\n<li>\n<p>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 <a href=\"\/pt\/online-payments\/capture#manual-capture\">manual capture<\/a> 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:<\/p>\n<ul>\n<li>A <a href=\"\/pt\/online-payments\/capture#failed-capture\">failed capture<\/a>.<\/li>\n<li>Increased interchange fees.<\/li>\n<li>Card scheme transaction fees.<\/li>\n<li>A cardholder-initiated <a href=\"\/pt\/risk-management\/understanding-disputes\/dispute-reason-codes\">chargeback<\/a> for 'No Authorization' or 'Late Presentment' reasons.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>The following tables include information on authorization validity periods for major card schemes <strong>that allow authorization adjustment<\/strong>.<\/p>\n<h3>American Express<\/h3>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Scheme<\/th>\n<th style=\"text-align: left;\">Debit\/credit<\/th>\n<th style=\"text-align: left;\">Environment<\/th>\n<th style=\"text-align: left;\"><a href=\"#authorisation-types\">Authorization type<\/a><\/th>\n<th style=\"text-align: left;\">MCC<\/th>\n<th style=\"text-align: left;\">Days<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">Amex<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">7 days<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>Cartes Bancaires<\/h3>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Scheme<\/th>\n<th style=\"text-align: left;\">Debit\/credit<\/th>\n<th style=\"text-align: left;\">Environment<\/th>\n<th style=\"text-align: left;\"><a href=\"#authorisation-types\">Authorization type<\/a><\/th>\n<th style=\"text-align: left;\">MCC<\/th>\n<th style=\"text-align: left;\">Days<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">Carte Bancaires<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">12 days<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>China UnionPay<\/h3>\n<ul>\n<li>30 Days from the initial authorisation.<\/li>\n<li>Authorisation adjustment does not extend the authorisation validity period.<\/li>\n<\/ul>\n<h3>Diners<\/h3>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Scheme<\/th>\n<th style=\"text-align: left;\">Debit\/credit<\/th>\n<th style=\"text-align: left;\">Environment<\/th>\n<th style=\"text-align: left;\"><a href=\"#authorisation-types\">Authorization type<\/a><\/th>\n<th style=\"text-align: left;\">MCC<\/th>\n<th style=\"text-align: left;\">Days<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">Diners<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">MOTO<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">7 days<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Diners<\/td>\n<td style=\"text-align: left;\">Debit<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">7 days<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Diners<\/td>\n<td style=\"text-align: left;\">Credit<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">30 days<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Diners<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">Car Rental, Hotel\/Lodging<\/td>\n<td style=\"text-align: left;\">30 days<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>Discover<\/h3>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Scheme<\/th>\n<th style=\"text-align: left;\">Debit\/credit<\/th>\n<th style=\"text-align: left;\">Environment<\/th>\n<th style=\"text-align: left;\"><a href=\"#authorisation-types\">Authorization type<\/a><\/th>\n<th style=\"text-align: left;\">MCC<\/th>\n<th style=\"text-align: left;\">Days<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">Discover<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">10 days<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Discover<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">Car Rental, Hotel\/Lodging<\/td>\n<td style=\"text-align: left;\">30 days<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>JCB<\/h3>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Scheme<\/th>\n<th style=\"text-align: left;\">Debit\/credit<\/th>\n<th style=\"text-align: left;\">Environment<\/th>\n<th style=\"text-align: left;\"><a href=\"#authorisation-types\">Authorization type<\/a><\/th>\n<th style=\"text-align: left;\">MCC<\/th>\n<th style=\"text-align: left;\">Days<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">JCB<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">1 year<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">JCB<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">Pre-auth<\/td>\n<td style=\"text-align: left;\">Hotel and Car rental<\/td>\n<td style=\"text-align: left;\">Time of stay\/rental<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>Mastercard<\/h3>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Scheme<\/th>\n<th style=\"text-align: left;\">Debit\/credit<\/th>\n<th style=\"text-align: left;\">Environment<\/th>\n<th style=\"text-align: left;\"><a href=\"#authorisation-types\">Authorization type<\/a><\/th>\n<th style=\"text-align: left;\">MCC<\/th>\n<th style=\"text-align: left;\">Days<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">Mastercard<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">Final auth<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">7 days<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Mastercard<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">Pre-auth<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">30 days<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<div class=\"notices blue\">\n<p>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.<\/p>\n<\/div>\n<h3>Mexico Domestic<\/h3>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Scheme<\/th>\n<th style=\"text-align: left;\">Debit\/credit<\/th>\n<th style=\"text-align: left;\">Environment<\/th>\n<th style=\"text-align: left;\"><a href=\"#authorisation-types\">Authorization type<\/a><\/th>\n<th style=\"text-align: left;\">MCC<\/th>\n<th style=\"text-align: left;\">Days<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">Network MX<\/td>\n<td style=\"text-align: left;\">Debit<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">Final auth<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">7 days<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Network MX<\/td>\n<td style=\"text-align: left;\">Credit<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">Final auth<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">30 days<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Network MX<\/td>\n<td style=\"text-align: left;\">Debit<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">Pre-auth<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">30 days<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Network MX<\/td>\n<td style=\"text-align: left;\">Credit<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">Pre-auth<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">120 days<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h3>Visa<\/h3>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Scheme<\/th>\n<th style=\"text-align: left;\">Debit\/credit<\/th>\n<th style=\"text-align: left;\">Environment<\/th>\n<th style=\"text-align: left;\"><a href=\"#authorisation-types\">Authorization type<\/a><\/th>\n<th style=\"text-align: left;\">MCC<\/th>\n<th style=\"text-align: left;\">Days<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">Visa electron<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">5 days<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Visa<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">POS<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">5 days<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Visa<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">Merchant initiated transactions (MIT) <br\/><br\/><u>Applies to:<\/u><br\/><li> ContAuth + Subscription \/ UnscheduledCardOnFile<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">5 days<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Visa<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\"><a href=\"https:\/\/docs.adyen.com\/get-started-with-adyen\/adyen-glossary\/#card-not-present-cnp\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">CNP<\/a> Cardholder-initiated transactions (CIT) <br\/><br\/><u>Applies to:<\/u><br\/><li> Ecommerce \/ ContAuth + CardOnFile <br\/><li> Ecommerce + Subscription \/ UnscheduledCardOnFile<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">10 days<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Visa<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\"><a href=\"https:\/\/docs.adyen.com\/get-started-with-adyen\/adyen-glossary\/#card-not-present-cnp\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">CNP<\/a> Cardholder-initiated transactions (CIT) <br\/><br\/><u>Applies to:<\/u><br\/><li> Ecommerce \/ ContAuth + CardOnFile <br\/><li> Ecommerce + Subscription \/ UnscheduledCardOnFile<\/td>\n<td style=\"text-align: left;\">Extended-Auth<a href=\"#exauth\">\n  <sup>1<\/sup>\n<\/a><\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">30 days<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Visa<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">Pre-Auth<\/td>\n<td style=\"text-align: left;\">Cruise, Lodging, Vehicle Rental<\/td>\n<td style=\"text-align: left;\">30 days<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Visa<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">Pre-Auth<\/td>\n<td style=\"text-align: left;\">7999, 4457, 7296, 7841, 7394, 7519, 7033<\/td>\n<td style=\"text-align: left;\">10 days<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Visa<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">All<\/td>\n<td style=\"text-align: left;\">Pre-Auth<\/td>\n<td style=\"text-align: left;\">5542<\/td>\n<td style=\"text-align: left;\">2 hours<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<div class=\"notices blue\">\n<p>Capturing Visa payments after the authorization validity period may result in <a href=\"https:\/\/docs.adyen.com\/online-payments\/capture\/failure-reasons\/#capture-cant-be-recaptured\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">capture failures<\/a> 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.<\/p>\n<\/div>\n<p><a id=\"exauth\"><\/a> <sup>1<\/sup> 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 <a href=\"https:\/\/ca-test.adyen.com\/ca\/ca\/contactUs\/support.shtml?form=other\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Support Team<\/a>.<\/p>\n<h2>See also<\/h2>\n<div class=\"see-also-links output-inline\" id=\"see-also\">\n<ul><li><a href=\"https:\/\/docs.adyen.com\/api-explorer\/?classes=codeLabel#\/Payment\/adjustAuthorisation\"\n                        target=\"_blank\"\n                         class=\"external\">\n                    API Explorer\n                <\/a><\/li><li><a href=\"\/online-payments\/classic-integrations\/modify-payments\/capture\"\n                        target=\"_self\"\n                        >\n                    Capture\n                <\/a><\/li><li><a href=\"\/development-resources\/webhooks\"\n                        target=\"_self\"\n                        >\n                    Webhooks\n                <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/online-payments\/classic-integrations\/modify-payments\/adjust-authorisation","articleFields":{"description":"Pre-authorise a payment, adjust the authorised amount, and capture the payment.","last_edit_on":"11-11-2020 10:05"},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/online-payments\/classic-integrations\/modify-payments\/adjust-authorisation","title":"Pre-authorisation and authorisation adjustment","content":"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 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.\n\nAuthorisation adjustment is currently available for Discover, Mastercard, Visa, and American Express. Support is ultimately up to the issuer. See Availability for more information.\n\nUse cases\nThere are several use cases for adjusting an authorisation:\n\n\nHospitality. For example, in a hotel:\n\nAt 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, to be able to apply late charges when necessary.\nDuring their stay, the guest incurs expenses at the hotel facilities. The hotel adds these expenses to the pre-authorised amount by adjusting the authorisation.\nWhen 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.\nIf necessary, the hotel charges the guest after they have left, using the shopper's stored payment details for a new payment.\n\n\n\nPre-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.\n\n\nAuthorisation types\nFor some card schemes, you can set card payment requests to be handled as either a pre-authorisation or a final authorisation.\n\nPre-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 endpoint.\nFinal 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.\n\n\nBy default, Adyen handles all card payment requests as final authorisations.\n\nTo set an authorisation type, you can either:\n\nDefine the default authorisation type at the merchant account level for all card transactions. See Configure your account.\nManually specify the authorisation type (PreAuth or FinalAuth) in each payment request. See Pre-authorise a payment.\n\nAsynchronous or synchronous adjustment\nThere are two ways to implement pre-authorisation:\n\n\nWith 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.\nAsynchronous 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.\n\n\nWith 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.\nSynchronous 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.\n\nIf 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.\n\n\n\nRequirements\nBefore you configure and use pre-authorisation:\n\nMake sure that you have built an integration that can make a payment.\nSet up 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.\n\nYou 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.\n(Optional) Configure your account\nThere are two aspects of your account that you may want to configure for pre-authorisation and authorisation adjustment:\n\n\nSynchronous 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 to enable this.\n\n\nDefault authorisation type: If you only do pre-authorisation payment requests, you can ask our Support Team to set your default authorisation type to PreAuth so that you do not have to specify it in your payment requests.\n\nIf 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.\n\n\n\nStep 1: Pre-authorise a payment\n\n\nMake a payment request, and additionally specify:\n\nadditionalData.authorisationType: PreAuth\n\n\n\n\n\n\nStore the pspReference from the response for later use when adjusting the authorisation or capturing the payment.\n\n\nStep 2: (Optional) Modify the authorisation\n\nYou cannot make a zero-value authorisation when you adjust an authorisation.\n\nAdjust the pre-authorisation amount\nTo modify the pre-authorised amount, make an authorisation adjustment request.\n\n\n    \n        \n        \n    \n\n\n\n\nExtend the authorisation\nTo extend the authorisation period make an \/adjustAuthorisation request with the same amount as the current balance on the authorisation:\n\nIf you haven't adjusted the authorisation yet, use the amount from the original pre-authorisation request.\nIf you did adjust the authorisation, use the amount from the last adjustment.\n\n\nFor 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.\n\n\nWe strongly recommend you to use the asynchronous flow to extend the authorisation. Visa only supports the asynchronous flow.\n\nSee Adjust the authorisation for instructions. To check the status of the authorisation (the original and the extension), make sure to consume webhooks.\n\nFor 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.\n\nStep 3: Finalize the pre-authorised payment\nWhen you have made your last authorisation adjustment, you need to manually capture the payment to transfer the reserved funds to your account:\n\n\nDecide whether you are ready to capture the payment:\n\n\nAre there any additional charges to be made?\nIf yes, adjust the authorisation first (see Adjust the authorisation).\n\n\n\nDoes the shopper want to settle the bill using a different payment method than the one used for the pre-authorisation?\nIf yes, do not capture the payment. Instead, cancel the pre-authorisation:\n\n\nMake a \/cancel request specifying the pspReference of the original pre-authorisation. Refer to Cancel authorisation for more details.\n\n\n\n\n\n\n\nWhen you are ready to capture the payment, make a POST request to the \/capture endpoint, specifying:\n\n\n\nParameter\nRequired\nDescription\n\n\n\n\noriginalReference\n\nThe pspReference of the original pre-authorisation. You received this in the response to your pre-authorisation request.\n\n\nmodificationAmount\n\nThe currency and value of the final amount in minor units. This is the sum of the original, pre-authorised amount and all later adjustments.\n\n\nreference\n\nYour reference to this payment modification, for use in your reconciliation process.\n\n\nmerchantAccount\n\nThe name of your merchant account that is used to process the payment.\n\n\n\n\n\nWhen you receive the \/capture response, note the following:\n\npspReference: The PSP reference associated with this \/capture request. Note that this is different from the PSP reference associated with the pre-authorisation request.\nresponse: [capture-received].\nadditionalData.merchantReference: Your reference to this payment modification, for use in your reconciliation process.\n\n\n\nWait for the webhook event. This informs you whether the final amount has been captured.\nIf the capture is successful, this event contains:\n\neventCode: CAPTURE\noriginalReference: The pspReference of the pre-authorisation.\npspReference: The PSP reference associated with this \/capture` request.\nsuccess: true\n\n\nIf 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.\n\n\n\n\nIf you need to charge the guest for an additional amount after they have left, and you stored your shopper's payment details (token) with your pre-authorisation request, you can apply these late charges in a recurring payment request using the token. See Recurring payments.\n\nYou 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, partially capture the payment, and then adjust the authorisation amount.\nAvailability\nAuthorization adjustment is available for the following payment methods:\n\n\n\nPayment method\nAvailability\n\n\n\n\nCard\nCard schemes set specific rules around which businesses can adjust authorizations. Your eligibility is determined by your Merchant Category Code (MCC). For a business type, each card scheme uses a different MCC. See which schemes support which MCC codes.\n\n\nApple Pay\nAvailable if the card associated with the Apple Pay wallet is from a card scheme for which authorization adjustment is available.\n\n\nGoogle Pay\nAvailable if the card associated with the Google Pay wallet is from a card scheme for which authorization adjustment is available.\n\n\n\n\nMerchant Category Code (MCC) and authorization adjustment\nTo view your MCCs for each payment method:\n\nLog in to your live Customer Area.\nSwitch to your merchant account.\nSelect Settings &gt; Payment methods.\nFind the line for the specific payment method. The MCC column shows your MCC for that payment method.\n\nThe following table shows, for each card scheme, which MCC codes authorization adjustment is available for:\n\n\n\nCard scheme\nMerchant Category Codes (MCC) for which authorization adjustment is available\n\n\n\n\nAmerican Express\nAll MCCs except 5542\n\n\nDiscover\n3351-3441, 3501-3999, 4111, 4112, 4121, 4131, 4411, 4457,  5499, 5812, 5813, 7011, 7033, 7996, 7394, 7512, 7513, 7519, 7999\n\n\nMastercard\nAll MCCs except 5542\n\n\nMexico Domestic (Network MX)\nCard 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\n\n\nVisa\nAll MCCs except 5542 Authorization adjustment does not work for V Pay cards.\n\n\nChina UnionPay\n7011, 7512, 4411, 3xxx\n\n\n\nExpiration of authorizations\nYou can only adjust a pre-authorization that has not expired yet. There are two authorization validity periods to take into account:\n\n\nFor the global card schemes, Adyen expires (pre-)authorization requests automatically after 28 days from the day the payment is authorized. Contact our Support Team if you want to change this default setting, and configure custom authorization validity periods for specific merchant accounts and card schemes.\n\n\nCard 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 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:\n\nA failed capture.\nIncreased interchange fees.\nCard scheme transaction fees.\nA cardholder-initiated chargeback for 'No Authorization' or 'Late Presentment' reasons.\n\n\n\nThe following tables include information on authorization validity periods for major card schemes that allow authorization adjustment.\nAmerican Express\n\n\n\nScheme\nDebit\/credit\nEnvironment\nAuthorization type\nMCC\nDays\n\n\n\n\nAmex\nAll\nAll\nAll\nAll\n7 days\n\n\n\nCartes Bancaires\n\n\n\nScheme\nDebit\/credit\nEnvironment\nAuthorization type\nMCC\nDays\n\n\n\n\nCarte Bancaires\nAll\nAll\nAll\nAll\n12 days\n\n\n\nChina UnionPay\n\n30 Days from the initial authorisation.\nAuthorisation adjustment does not extend the authorisation validity period.\n\nDiners\n\n\n\nScheme\nDebit\/credit\nEnvironment\nAuthorization type\nMCC\nDays\n\n\n\n\nDiners\nAll\nMOTO\nAll\nAll\n7 days\n\n\nDiners\nDebit\nAll\nAll\nAll\n7 days\n\n\nDiners\nCredit\nAll\nAll\nAll\n30 days\n\n\nDiners\nAll\nAll\nAll\nCar Rental, Hotel\/Lodging\n30 days\n\n\n\nDiscover\n\n\n\nScheme\nDebit\/credit\nEnvironment\nAuthorization type\nMCC\nDays\n\n\n\n\nDiscover\nAll\nAll\nAll\nAll\n10 days\n\n\nDiscover\nAll\nAll\nAll\nCar Rental, Hotel\/Lodging\n30 days\n\n\n\nJCB\n\n\n\nScheme\nDebit\/credit\nEnvironment\nAuthorization type\nMCC\nDays\n\n\n\n\nJCB\nAll\nAll\nAll\nAll\n1 year\n\n\nJCB\nAll\nAll\nPre-auth\nHotel and Car rental\nTime of stay\/rental\n\n\n\nMastercard\n\n\n\nScheme\nDebit\/credit\nEnvironment\nAuthorization type\nMCC\nDays\n\n\n\n\nMastercard\nAll\nAll\nFinal auth\nAll\n7 days\n\n\nMastercard\nAll\nAll\nPre-auth\nAll\n30 days\n\n\n\n\nCapturing 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.\n\nMexico Domestic\n\n\n\nScheme\nDebit\/credit\nEnvironment\nAuthorization type\nMCC\nDays\n\n\n\n\nNetwork MX\nDebit\nAll\nFinal auth\nAll\n7 days\n\n\nNetwork MX\nCredit\nAll\nFinal auth\nAll\n30 days\n\n\nNetwork MX\nDebit\nAll\nPre-auth\nAll\n30 days\n\n\nNetwork MX\nCredit\nAll\nPre-auth\nAll\n120 days\n\n\n\nVisa\n\n\n\nScheme\nDebit\/credit\nEnvironment\nAuthorization type\nMCC\nDays\n\n\n\n\nVisa electron\nAll\nAll\nAll\nAll\n5 days\n\n\nVisa\nAll\nPOS\nAll\nAll\n5 days\n\n\nVisa\nAll\nMerchant initiated transactions (MIT) Applies to: ContAuth + Subscription \/ UnscheduledCardOnFile\nAll\nAll\n5 days\n\n\nVisa\nAll\nCNP Cardholder-initiated transactions (CIT) Applies to: Ecommerce \/ ContAuth + CardOnFile  Ecommerce + Subscription \/ UnscheduledCardOnFile\nAll\nAll\n10 days\n\n\nVisa\nAll\nCNP Cardholder-initiated transactions (CIT) Applies to: Ecommerce \/ ContAuth + CardOnFile  Ecommerce + Subscription \/ UnscheduledCardOnFile\nExtended-Auth\n  1\n\nAll\n30 days\n\n\nVisa\nAll\nAll\nPre-Auth\nCruise, Lodging, Vehicle Rental\n30 days\n\n\nVisa\nAll\nAll\nPre-Auth\n7999, 4457, 7296, 7841, 7394, 7519, 7033\n10 days\n\n\nVisa\nAll\nAll\nPre-Auth\n5542\n2 hours\n\n\n\n\nCapturing Visa payments after the authorization validity period may result in capture failures 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.\n\n 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.\nSee also\n\n\n                    API Explorer\n                \n                    Capture\n                \n                    Webhooks\n                \n","type":"page","locale":"pt","boost":16,"hierarchy":{"lvl0":"Home","lvl1":"Online payments","lvl2":"Classic integrations for Ecommerce","lvl3":"Modify payments","lvl4":"Pre-authorisation and authorisation adjustment"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/online-payments","lvl2":"https:\/\/docs.adyen.com\/pt\/online-payments\/classic-integrations","lvl3":"https:\/\/docs.adyen.com\/pt\/online-payments\/classic-integrations\/modify-payments","lvl4":"\/pt\/online-payments\/classic-integrations\/modify-payments\/adjust-authorisation"},"levels":5,"category":"Online Payments","category_color":"green","tags":["Pre-authorisation","authorisation","adjustment"]},"articleFiles":{"397652001.json":"<p alt=\"\">397652001.json<\/p>","capture-auth.request.json":"<p alt=\"\">capture-auth.request.json<\/p>","capture-auth.response.json":"<p alt=\"\">capture-auth.response.json<\/p>","modification-auth.request.json":"<p alt=\"\">modification-auth.request.json<\/p>","modification-auth.response.json":"<p alt=\"\">modification-auth.response.json<\/p>","preauthorisation.request.json":"<p alt=\"\">preauthorisation.request.json<\/p>","preauthorisation.response.json":"<p alt=\"\">preauthorisation.response.json<\/p>"}}