{"title":"KYC action required snapshot report","category":"Classic Platforms","creationDate":1776961628,"content":"<div class=\"sc-notice info\"><div>\n<p>This page is for classic Adyen for Platforms integrations. If you are just starting your implementation, refer to our <a href=\"\/pt\/adyen-for-platforms-model\">new integration guide<\/a> instead.<\/p>\n<\/div><\/div>\n<p>The KYC action required snapshot report contains all sub-merchants that have processed a payment or received a fund transfer in the last 3 months and have not yet completed KYC. The report is generated in .csv format on a schedule that is configured from the Customer Area. The schedule for this report is: daily, weekly or monthly. This report can help you to identify if users are having issues with KYC verification.<\/p>\n<div class=\"sc-notice note\"><div>\n<p>We recommend you use <a href=\"\/pt\/classic-platforms\/notifications\">notifications<\/a> to identify these users rather than reports, as they are real time and allow for quicker resolution of issues.<\/p>\n<\/div><\/div>\n<p><strong>Report name format:\u00a0<\/strong>kyc_snapshot_report_YYY-MM-DD.csv\u00a0<br \/>\n<strong>Subscription<\/strong>: Default\u00a0<br \/>\n<strong>Frequency<\/strong>: Daily, weekly or monthly.<\/p>\n<h2 id=\"report-structure\">Report structure<\/h2>\n<table>\n<thead>\n<tr>\n<th>#<\/th>\n<th>Column<\/th>\n<th>Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>1<\/td>\n<td>Marketplace<\/td>\n<td>Name of the marketplace.<\/td>\n<\/tr>\n<tr>\n<td>2<\/td>\n<td>Account Holder Code<\/td>\n<td>Unique account holder code defined by the Marketplace upon creation.<\/td>\n<\/tr>\n<tr>\n<td>3<\/td>\n<td>Account holder Country Code<\/td>\n<td>Account holder country code (address).<\/td>\n<\/tr>\n<tr>\n<td>4<\/td>\n<td>Creation date (UTC)<\/td>\n<td>Timestamp (UTC) the account holder was created.<\/td>\n<\/tr>\n<tr>\n<td>5<\/td>\n<td>Entity type<\/td>\n<td>Either Business or Individual.<\/td>\n<\/tr>\n<tr>\n<td>6<\/td>\n<td>Tier number<\/td>\n<td>Processing tier is calculated based on the amount processed by the account holder. Depending on the tier configuration the tier number is determined. Possible values are: 0, 1, 2 and 3.<\/td>\n<\/tr>\n<tr>\n<td>7<\/td>\n<td>Account status<\/td>\n<td>Account holder status (active, inactive, suspended, or closed).<\/td>\n<\/tr>\n<tr>\n<td>8<\/td>\n<td>Next deadline (UTC)<\/td>\n<td>Timestamp (UTC) of the deadline for the account holder to finish the KYC requirements for their tier.<\/td>\n<\/tr>\n<tr>\n<td>9<\/td>\n<td>Payment instrument code<\/td>\n<td>Unique identifier for the bank account. Note that a account holder can have multiple bank accounts.<\/td>\n<\/tr>\n<tr>\n<td>10<\/td>\n<td>Shareholder Code<\/td>\n<td>Unique identifier for the shareholder. Note that a account holder can have multiple shareholders.<\/td>\n<\/tr>\n<tr>\n<td>11<\/td>\n<td>Identity Verification<\/td>\n<td>Status for the Identity Verification check. See <a href=\"\/pt\/classic-platforms\/verification-process\">verification process<\/a> for possible KYC status check values.<\/td>\n<\/tr>\n<tr>\n<td>12<\/td>\n<td>Company Verification<\/td>\n<td>Status for the Company Verification check. See <a href=\"\/pt\/classic-platforms\/verification-process\">verification process<\/a>\u00a0 for possible KYC status check values.<\/td>\n<\/tr>\n<tr>\n<td>13<\/td>\n<td>Bank Account Verification<\/td>\n<td>Status for the Bank Account Verification check. See <a href=\"\/pt\/classic-platforms\/verification-process\">verification process<\/a>\u00a0 for possible KYC status check values.<\/td>\n<\/tr>\n<tr>\n<td>14<\/td>\n<td>Document Verification<\/td>\n<td>Status for the Document Verification check. See <a href=\"\/pt\/classic-platforms\/verification-process\">verification process<\/a>\u00a0 for possible KYC status check values.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>","url":"https:\/\/docs.adyen.com\/pt\/classic-platforms\/kyc-action-required-snapshot-report","articleFields":{"search_category":"Classic Platforms","id":"47485882","type":"page","_expandable":{"operations":""},"status":"current","last_edit_on":"17-05-2019 15:19","parameters":{"directoryPath":"\/classic-platforms"}},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/classic-platforms\/kyc-action-required-snapshot-report","title":"KYC action required snapshot report","content":"\nThis page is for classic Adyen for Platforms integrations. If you are just starting your implementation, refer to our new integration guide instead.\n\nThe KYC action required snapshot report contains all sub-merchants that have processed a payment or received a fund transfer in the last 3 months and have not yet completed KYC. The report is generated in .csv format on a schedule that is configured from the Customer Area. The schedule for this report is: daily, weekly or monthly. This report can help you to identify if users are having issues with KYC verification.\n\nWe recommend you use notifications to identify these users rather than reports, as they are real time and allow for quicker resolution of issues.\n\nReport name format:\u00a0kyc_snapshot_report_YYY-MM-DD.csv\u00a0\nSubscription: Default\u00a0\nFrequency: Daily, weekly or monthly.\nReport structure\n\n\n\n#\nColumn\nDescription\n\n\n\n\n1\nMarketplace\nName of the marketplace.\n\n\n2\nAccount Holder Code\nUnique account holder code defined by the Marketplace upon creation.\n\n\n3\nAccount holder Country Code\nAccount holder country code (address).\n\n\n4\nCreation date (UTC)\nTimestamp (UTC) the account holder was created.\n\n\n5\nEntity type\nEither Business or Individual.\n\n\n6\nTier number\nProcessing tier is calculated based on the amount processed by the account holder. Depending on the tier configuration the tier number is determined. Possible values are: 0, 1, 2 and 3.\n\n\n7\nAccount status\nAccount holder status (active, inactive, suspended, or closed).\n\n\n8\nNext deadline (UTC)\nTimestamp (UTC) of the deadline for the account holder to finish the KYC requirements for their tier.\n\n\n9\nPayment instrument code\nUnique identifier for the bank account. Note that a account holder can have multiple bank accounts.\n\n\n10\nShareholder Code\nUnique identifier for the shareholder. Note that a account holder can have multiple shareholders.\n\n\n11\nIdentity Verification\nStatus for the Identity Verification check. See verification process for possible KYC status check values.\n\n\n12\nCompany Verification\nStatus for the Company Verification check. See verification process\u00a0 for possible KYC status check values.\n\n\n13\nBank Account Verification\nStatus for the Bank Account Verification check. See verification process\u00a0 for possible KYC status check values.\n\n\n14\nDocument Verification\nStatus for the Document Verification check. See verification process\u00a0 for possible KYC status check values.\n\n\n","type":"page","locale":"pt","boost":18,"hierarchy":{"lvl0":"Home","lvl1":"Classic integration","lvl2":"KYC action required snapshot report"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/classic-platforms","lvl2":"\/pt\/classic-platforms\/kyc-action-required-snapshot-report"},"levels":3,"category":"Classic Platforms","category_color":"green","tags":["action","required","snapshot","report"]}}
