{"title":"Modifications not processed","category":"default","creationDate":1776961629,"content":"<div class=\"additional-info-block output-inline\">\n<h5 class=\"article__heading additional-info-block__title\">Time zones<\/h5><div class=\"additional-info-block__body\"><p>Your <a href=\"\/pt\/reporting\/time-zone-setting\">time zone setting<\/a> affects the data in this report.<\/p><\/div><\/div>\n\n<p>The Modifications not processed report includes all modification attempts that couldn't be processed. Modification attempts such as <a href=\"\/pt\/online-payments\/capture\">captures<\/a>, <a href=\"\/pt\/online-payments\/cancel\">cancels<\/a>, and <a href=\"\/pt\/online-payments\/refund\">refunds<\/a> are all actions that can be performed on an original payment and attempt to modify the authorised <a href=\"\/pt\/account\/payments-lifecycle\">payment status<\/a>.<\/p>\n<p>For each unprocessed modification in this report, the transaction status of its original authorised payment in your <a href=\"https:\/\/ca-test.adyen.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Customer Area<\/a> doesn't change. For example, if a refund request couldn't be processed due to insufficient balance, the original transaction will still have a Settled status in the list of transactions in your Customer Area.<\/p>\n<p>A failed modification attempt also triggers a <a href=\"\/pt\/development-resources\/webhooks\">webhook<\/a> with information about the failure.<\/p>\n<h2>Sample<\/h2>\n<p><a href=\"\/pt\/reporting\/modifications-not-processed\/SAMPLE_modifications_not_processed_report.csv\">Download a sample Modifications not processed report<\/a> for examples of the included data.<\/p>\n<h2>Structure<\/h2>\n<h3 id=\"entries\">Entries<\/h3>\n<p>Under the header line, each line in the report is a separate entry.<\/p>\n<h3 id=\"columns\">Columns<\/h3>\n<p>Each column shows specific information about the entries.<\/p>\n<div class=\"sticky-table-container\">\n    \n<table>\n<thead>\n<tr>\n<th>Columns<\/th>\n<th>Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Company Account<\/td>\n<td>Name of your company account as registered in the plataforma de pagamentos da Adyen.<\/td>\n<\/tr>\n<tr>\n<td>Merchant Account<\/td>\n<td>Name of your merchant account used to process the original payment request.<\/td>\n<\/tr>\n<tr>\n<td>Psp Reference<\/td>\n<td>Adyen's 16-character unique reference associated with the transaction\/the request. You can find it in the <a href=\"https:\/\/docs.adyen.com\/api-explorer\/#\/CheckoutService\/v67\/post\/payments__resParam_pspReference\" class=\"codeLabel external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">response to the original payment request<\/a>.<\/td>\n<\/tr>\n<tr>\n<td>Merchant Reference<\/td>\n<td>Reference number provided when initiating the payment request.<\/td>\n<\/tr>\n<tr>\n<td>Currency<\/td>\n<td>Three character ISO code for the currency which was used for processing the payment (transaction currency).<\/td>\n<\/tr>\n<tr>\n<td>Amount<\/td>\n<td>The amount of the original transaction.<\/td>\n<\/tr>\n<tr>\n<td>Creation Date<\/td>\n<td>Time stamp indicating when the capture was received by Adyen. <br>Format: <code>YYYY-MM-DD HH:MM:SS<\/code>. <br>For example: <em>2020-07-26 19:58:55<\/em>.<\/td>\n<\/tr>\n<tr>\n<td>Modification Reference<\/td>\n<td>Adyen's unique identifier (PSP reference) for the modification request. Maximum length: 16 characters.<\/td>\n<\/tr>\n<tr>\n<td>Modification Merchant Reference<\/td>\n<td>Optional modification reference for modifications like capture or refund.<\/td>\n<\/tr>\n<tr>\n<td>Modification Currency<\/td>\n<td>Three character ISO code for the currency which was used for processing the modification.<\/td>\n<\/tr>\n<tr>\n<td>Modification Amount<\/td>\n<td>The amount of the modification.<\/td>\n<\/tr>\n<tr>\n<td>Modification Date<\/td>\n<td>The time stamp indicating when the modification was received by Adyen. <br>Format: <code>YYYY-MM-DD HH:MM:SS<\/code>. <br>For example: <em>2020-07-29 12:15:23<\/em>.<\/td>\n<\/tr>\n<tr>\n<td>Modificationevent<\/td>\n<td>The code of the modification event. Possible values: <strong>RefundNotProcessed<\/strong>, <strong>CaptureNotProcessed<\/strong>, and <strong>CancelNotProcessed<\/strong>.<\/td>\n<\/tr>\n<tr>\n<td>Eventdescription<\/td>\n<td>The reason why the modification was not processed.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\n<\/div>\n\n<h2>See also<\/h2>\n<div class=\"see-also-links output-inline\" id=\"see-also\">\n<ul><li><a href=\"\/online-payments\/capture\"\n                        target=\"_self\"\n                        >\n                    Capture\n                <\/a><\/li><li><a href=\"\/online-payments\/cancel\"\n                        target=\"_self\"\n                        >\n                    Cancel\n                <\/a><\/li><li><a href=\"\/online-payments\/refund\"\n                        target=\"_self\"\n                        >\n                    Refund\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\/reporting\/modifications-not-processed","articleFields":{"description":"Find the modifications that were not processed.","parameters":{"report_name":"Modifications not processed report","file_name":"\/reporting\/modifications-not-processed\/SAMPLE_modifications_not_processed_report.csv","additional_columns":"false","time_zone":"na","ca_type":"ca"},"feedback_component":true},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/reporting\/modifications-not-processed","title":"Modifications not processed","content":"\nTime zonesYour time zone setting affects the data in this report.\n\nThe Modifications not processed report includes all modification attempts that couldn't be processed. Modification attempts such as captures, cancels, and refunds are all actions that can be performed on an original payment and attempt to modify the authorised payment status.\nFor each unprocessed modification in this report, the transaction status of its original authorised payment in your Customer Area doesn't change. For example, if a refund request couldn't be processed due to insufficient balance, the original transaction will still have a Settled status in the list of transactions in your Customer Area.\nA failed modification attempt also triggers a webhook with information about the failure.\nSample\nDownload a sample Modifications not processed report for examples of the included data.\nStructure\nEntries\nUnder the header line, each line in the report is a separate entry.\nColumns\nEach column shows specific information about the entries.\n\n    \n\n\n\nColumns\nDescription\n\n\n\n\nCompany Account\nName of your company account as registered in the plataforma de pagamentos da Adyen.\n\n\nMerchant Account\nName of your merchant account used to process the original payment request.\n\n\nPsp Reference\nAdyen's 16-character unique reference associated with the transaction\/the request. You can find it in the response to the original payment request.\n\n\nMerchant Reference\nReference number provided when initiating the payment request.\n\n\nCurrency\nThree character ISO code for the currency which was used for processing the payment (transaction currency).\n\n\nAmount\nThe amount of the original transaction.\n\n\nCreation Date\nTime stamp indicating when the capture was received by Adyen. Format: YYYY-MM-DD HH:MM:SS. For example: 2020-07-26 19:58:55.\n\n\nModification Reference\nAdyen's unique identifier (PSP reference) for the modification request. Maximum length: 16 characters.\n\n\nModification Merchant Reference\nOptional modification reference for modifications like capture or refund.\n\n\nModification Currency\nThree character ISO code for the currency which was used for processing the modification.\n\n\nModification Amount\nThe amount of the modification.\n\n\nModification Date\nThe time stamp indicating when the modification was received by Adyen. Format: YYYY-MM-DD HH:MM:SS. For example: 2020-07-29 12:15:23.\n\n\nModificationevent\nThe code of the modification event. Possible values: RefundNotProcessed, CaptureNotProcessed, and CancelNotProcessed.\n\n\nEventdescription\nThe reason why the modification was not processed.\n\n\n\n\n\n\nSee also\n\n\n                    Capture\n                \n                    Cancel\n                \n                    Refund\n                \n                    Webhooks\n                \n","type":"page","locale":"pt","boost":18,"hierarchy":{"lvl0":"Home","lvl1":"Reporting","lvl2":"Modifications not processed"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/reporting","lvl2":"\/pt\/reporting\/modifications-not-processed"},"levels":3,"category":"Reporting","category_color":"green","tags":["Modifications","processed"]},"articleFiles":{"SAMPLE_modifications_not_processed_report.csv":"<p alt=\"\">SAMPLE_modifications_not_processed_report.csv<\/p>"}}
