{"title":"Adyen for Platforms","category":"default","creationDate":1776961627,"content":"<p>If you are a platform or a marketplace and your users take payments that are processed through Adyen, the other pages in this peak season readiness guide apply to you and your users. So be sure to review the rest of this guide.<\/p>\n<p>This page discusses a few topics that are only relevant in the context of Adyen for Platforms.<\/p>\n<h2>Review the chargeback split logic<\/h2>\n<p>A peak season increase in the number of transactions usually leads to an increase in the number of chargebacks. If you have not set up chargeback logic, Adyen withdraws the full disputed amount from the liable balance account of your platform or marketplace whenever a chargeback occurs.<\/p>\n<p>Chargeback logic refers to billing rules for how to split (or not split) debits and credits related to the chargeback process between your platform or marketplace and your user. Splits you can define are:<\/p>\n<ul>\n<li>Book the full disputed amount to the liable balance account of your platform or marketplace.<\/li>\n<li>Book the full disputed amount to the liable balance account of the user involved.<\/li>\n<li>Split the disputed amount over various balance accounts according to the splits defined in the original payment request. For example, if the payment booked a commission to the platform\/marketplace and a chargeback occurs, the commission is charged back from the liable balance account of the platform\/marketplace.<\/li>\n<\/ul>\n<p>You can define all these chargeback splits on the balance platform level, and on the level of individual payments. Chargeback splits defined for a payment override those defined for the balance platform. If you are a platform, we recommended defining <a href=\"\/pt\/platforms\/automatic-split-configuration\">split configuration profiles<\/a> to apply splits automatically according to your preferences for splitting payments, captures, refunds, and chargebacks.<\/p>\n<p>For details, see <em>Split chargebacks<\/em> for <a href=\"\/pt\/platforms\/online-payments\/split-transactions\/split-chargebacks\">platforms<\/a> or <a href=\"\/pt\/marketplaces\/split-transactions\/split-chargebacks\">marketplaces<\/a>.<\/p>\n<h2>Handle outstanding KYC checks<\/h2>\n<p>After the users of your platform or marketplace have been onboarded, Adyen needs to re-verify them sometimes, for example, when a provided ID document is about to expire. When this happens, users get some time to respond. During that time, they can still use the capabilities needed to operate on your platform or marketplace.<\/p>\n<p>However, if they do not provide information in time, capabilities may expire and payouts may be blocked. Especially during peak season it is important to prevent this from happening. As a platform or marketplace, you should keep an eye on the webhook event messages that Adyen sends about outstanding data reviews, so that you can alert your users to the need to respond to KYC checks.<\/p>\n<ol>\n<li>Listen to  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/balanceplatform-webhooks\/latest\/post\/balancePlatform.accountHolder.updated\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">balancePlatform.accountHolder.updated<\/a> webhook events.<\/li>\n<li>If the webhook event includes a verification error, ask the account holder to fix the issue.<br \/>\nVerification errors have a <code>code<\/code> and a <code>message<\/code> that explains what the problem is and\/or what to do to fix the problem. For example, error code <strong>3_10<\/strong> with the message \"Review of data is required\".<\/li>\n<\/ol>\n<h2>See also<\/h2>\n<p><strong>Platforms<\/strong><\/p>\n<div class=\"see-also-links output-inline\" id=\"see-also\">\n<ul><li><a href=\"\/platforms\/online-payments\/split-transactions\/split-chargebacks\"\n                        target=\"_self\"\n                        >\n                    Split chargebacks\n                <\/a><\/li><li><a href=\"\/platforms\/automatic-split-configuration\"\n                        target=\"_self\"\n                        >\n                    Split configuration profiles\n                <\/a><\/li><li><a href=\"\/platforms\/verification-overview\/capabilities\"\n                        target=\"_self\"\n                        >\n                    Capabilities\n                <\/a><\/li><li><a href=\"\/platforms\/verification-overview\"\n                        target=\"_self\"\n                        >\n                    Verification process\n                <\/a><\/li><\/ul><\/div>\n\n<p><strong>Marketplaces<\/strong><\/p>\n<div class=\"see-also-links output-inline\" id=\"see-also\">\n<ul><li><a href=\"\/marketplaces\/split-transactions\/split-chargebacks\"\n                        target=\"_self\"\n                        >\n                    Split chargebacks\n                <\/a><\/li><li><a href=\"\/marketplaces\/verification-overview\/capabilities\"\n                        target=\"_self\"\n                        >\n                    Capabilities\n                <\/a><\/li><li><a href=\"\/marketplaces\/verification-overview\"\n                        target=\"_self\"\n                        >\n                    Verification process\n                <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/industries\/peak-season\/afp","articleFields":{"description":"Be aware of topics to address specifically on your platform or marketplace.","type":"page"},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/industries\/peak-season\/afp","title":"Adyen for Platforms","content":"If you are a platform or a marketplace and your users take payments that are processed through Adyen, the other pages in this peak season readiness guide apply to you and your users. So be sure to review the rest of this guide.\nThis page discusses a few topics that are only relevant in the context of Adyen for Platforms.\nReview the chargeback split logic\nA peak season increase in the number of transactions usually leads to an increase in the number of chargebacks. If you have not set up chargeback logic, Adyen withdraws the full disputed amount from the liable balance account of your platform or marketplace whenever a chargeback occurs.\nChargeback logic refers to billing rules for how to split (or not split) debits and credits related to the chargeback process between your platform or marketplace and your user. Splits you can define are:\n\nBook the full disputed amount to the liable balance account of your platform or marketplace.\nBook the full disputed amount to the liable balance account of the user involved.\nSplit the disputed amount over various balance accounts according to the splits defined in the original payment request. For example, if the payment booked a commission to the platform\/marketplace and a chargeback occurs, the commission is charged back from the liable balance account of the platform\/marketplace.\n\nYou can define all these chargeback splits on the balance platform level, and on the level of individual payments. Chargeback splits defined for a payment override those defined for the balance platform. If you are a platform, we recommended defining split configuration profiles to apply splits automatically according to your preferences for splitting payments, captures, refunds, and chargebacks.\nFor details, see Split chargebacks for platforms or marketplaces.\nHandle outstanding KYC checks\nAfter the users of your platform or marketplace have been onboarded, Adyen needs to re-verify them sometimes, for example, when a provided ID document is about to expire. When this happens, users get some time to respond. During that time, they can still use the capabilities needed to operate on your platform or marketplace.\nHowever, if they do not provide information in time, capabilities may expire and payouts may be blocked. Especially during peak season it is important to prevent this from happening. As a platform or marketplace, you should keep an eye on the webhook event messages that Adyen sends about outstanding data reviews, so that you can alert your users to the need to respond to KYC checks.\n\nListen to  balancePlatform.accountHolder.updated webhook events.\nIf the webhook event includes a verification error, ask the account holder to fix the issue.\nVerification errors have a code and a message that explains what the problem is and\/or what to do to fix the problem. For example, error code 3_10 with the message \"Review of data is required\".\n\nSee also\nPlatforms\n\n\n                    Split chargebacks\n                \n                    Split configuration profiles\n                \n                    Capabilities\n                \n                    Verification process\n                \n\nMarketplaces\n\n\n                    Split chargebacks\n                \n                    Capabilities\n                \n                    Verification process\n                \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Industries and markets","lvl2":"Peak season readiness","lvl3":"Adyen for Platforms"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/industries","lvl2":"https:\/\/docs.adyen.com\/pt\/industries\/peak-season","lvl3":"\/pt\/industries\/peak-season\/afp"},"levels":4,"category":"","category_color":"","tags":["Adyen","Platforms"]}}