{"title":"Webhooks for network tokens","category":"default","creationDate":1773655740,"content":"<p>Adyen sends webhooks for events in network token lifecycles. When your cardholders add their Adyen-issued cards to digital wallets like Apple Pay or Google Pay, Adyen replaces the card data with a network token. Learn more about network tokens in <a href=\"\/pt\/issuing\/tokens-digital-wallet\">Tokens for digital wallets<\/a>.<\/p>\n<p>These webhooks help you monitor and control tokenized cards. This page covers the following events:<\/p>\n<ul>\n<li><strong><a href=\"#network-token-created\">Network token created<\/a><\/strong>: When a cardholder initially adds their card to a digital wallet<\/li>\n<li><strong><a href=\"#network-token-updated\">Network token updated<\/a><\/strong>: When the token status changes during or after provisioning<\/li>\n<\/ul>\n<p>In your Customer Area, subscribe to <a href=\"\/pt\/development-resources\/webhooks#configuration-webhooks\">Configuration webhooks<\/a> to get these events. They help you track where your cards are tokenized, respond to provisioning decisions, and audit network token activity.<\/p>\n<h2>Webhook types<\/h2>\n<p>Webhook messages inform you when Adyen creates or updates a network token, and whether the cardholder must complete authentication before Adyen activates the token.<\/p>\n<p>You can identify the webhooks triggered by network token events by using the following values:<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Parameter<\/th>\n<th style=\"text-align: left;\">Description<\/th>\n<th style=\"text-align: left;\">Value<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><code>type<\/code><\/td>\n<td style=\"text-align: left;\">The webhook type.<\/td>\n<td style=\"text-align: left;\"><strong>balancePlatform.networkToken.created<\/strong> or <strong>balancePlatform.networkToken.updated<\/strong><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>data.status<\/code><\/td>\n<td style=\"text-align: left;\">The status of the network token.<\/td>\n<td style=\"text-align: left;\"><ul><li><strong>inactive<\/strong>: Not yet activated.<\/li><li><strong>active<\/strong>: Ready for payments.<\/li><li><strong>suspended<\/strong>: Temporarily disabled.<\/li><li><strong>closed<\/strong>: Permanently closed.<\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>data.decision<\/code><\/td>\n<td style=\"text-align: left;\">The decision for the network token request.<\/td>\n<td style=\"text-align: left;\"><strong>approved<\/strong>, <strong>requireAuthentication<\/strong>, <strong>declined<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Network token created<\/h2>\n<p>Adyen sends a  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/balanceplatform-webhooks\/latest\/post\/balancePlatform.networkToken.created\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">balancePlatform.networkToken.created<\/a> webhook message when a cardholder adds their Adyen-issued card to a digital wallet. At this point in the <a href=\"\/pt\/issuing\/tokens-digital-wallet#provisioning-for-a-digital-wallet\">provisioning flow<\/a>, Adyen has received the network token request from the card scheme, created a network token with status <strong>inactive<\/strong>, and completed the risk analysis.<\/p>\n<p>The <code>decision<\/code> field specifies the outcome of the risk analysis and determines what happens next in the wallet:<\/p>\n<ul>\n<li><strong>requireAuthentication<\/strong>: The digital wallet shows the cardholder a verification screen. Adyen requires <a href=\"\/pt\/issuing\/tokens-digital-wallet\/authentication-data\">two-factor authentication<\/a> (OTP through SMS or email) or phone call verification before activating the token.<\/li>\n<li><strong>approved<\/strong>: The risk analysis passed. Adyen activates the token automatically without further cardholder action.<\/li>\n<\/ul>\n<h3 id=\"created-auth-required\">Network token created with authentication required<\/h3>\n<p>Adyen sends this webhook message when the risk analysis requires identity verification before activating the token. At this point in the provisioning flow, the cardholder sees a verification screen in their wallet app, or a prompt to contact your call center.<\/p>\n<p>Use this webhook message to show a \"pending verification\" status for this card in your app.<\/p>\n<p>The webhook message contains:<\/p>\n<ul>\n<li><code>type<\/code>: <strong>balancePlatform.networkToken.created<\/strong><\/li>\n<li><code>status<\/code>: <strong>inactive<\/strong><\/li>\n<li><code>decision<\/code>: <strong>requireAuthentication<\/strong><\/li>\n<\/ul>\n<div data-component-wrapper=\"code-sample\">\n    <code-sample :title=\"'Example networkToken.created webhook with authentication required'\" :id=\"''\" :code-data='[{\"language\":\"json\",\"tabTitle\":\"\",\"content\":\"{\\n    \\\"data\\\" : {\\n        \\\"balancePlatform\\\" : \\\"YOUR_BALANCE_PLATFORM\\\",\\n        \\\"id\\\" : \\\"NWTK00000000000000000000000001\\\",\\n        \\\"authenticationApplied\\\" : false,\\n        \\\"decision\\\" : \\\"requireAuthentication\\\",\\n        \\\"paymentInstrumentId\\\" : \\\"PI00000000000000000000000001\\\",\\n        \\\"status\\\" : \\\"inactive\\\",\\n        \\\"type\\\" : \\\"wallet\\\",\\n        \\\"validationFacts\\\" : {\\n            \\\"avsAddress\\\" : \\\"invalid\\\",\\n            \\\"paymentInstrumentActive\\\" : \\\"valid\\\",\\n            \\\"avsPostalCode\\\" : \\\"invalid\\\",\\n            \\\"inputExpiryDateCheck\\\" : \\\"valid\\\",\\n            \\\"paymentInstrumentExpirationCheck\\\" : \\\"valid\\\",\\n            \\\"transactionRules\\\" : \\\"valid\\\",\\n            \\\"accountLookup\\\" : \\\"valid\\\",\\n            \\\"walletValidation\\\" : \\\"valid\\\",\\n            \\\"paymentInstrumentFound\\\" : \\\"valid\\\",\\n            \\\"paymentInstrument\\\" : \\\"valid\\\",\\n            \\\"cvc2\\\" : \\\"*****\\\"\\n        },\\n        \\\"wallet\\\" : {\\n            \\\"device\\\" : {\\n                \\\"formFactor\\\" : \\\"phone\\\",\\n                \\\"osName\\\" : \\\"android\\\"\\n            },\\n            \\\"provisioningMethod\\\" : \\\"manual\\\",\\n            \\\"type\\\" : \\\"wallet\\\"\\n        }\\n    },\\n    \\\"environment\\\" : \\\"test\\\",\\n    \\\"timestamp\\\" : \\\"2022-10-25T10:43:53+02:00\\\",\\n    \\\"type\\\" : \\\"balancePlatform.networkToken.created\\\"\\n}\"}]' :enable-copy-link-to-code-block=\"true\" :code-sample-card-size=\"'fullsize'\"><\/code-sample>\n<\/div>\n<h3 id=\"created-no-auth\">Network token created without authentication required<\/h3>\n<p>Adyen sends this webhook message when the risk analysis determines low risk and no cardholder verification is required. At this point in the <a href=\"\/pt\/issuing\/tokens-digital-wallet?tab=token-activated-automatically\">provisioning flow<\/a>, Adyen activates the token automatically. After receiving this webhook message, expect a  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/balanceplatform-webhooks\/latest\/post\/balancePlatform.networkToken.updated\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">balancePlatform.networkToken.updated<\/a> webhook message that confirms the token is active.<\/p>\n<p>The webhook message contains:<\/p>\n<ul>\n<li><code>type<\/code>: <strong>balancePlatform.networkToken.created<\/strong><\/li>\n<li><code>status<\/code>: <strong>inactive<\/strong><\/li>\n<li><code>decision<\/code>: <strong>approved<\/strong><\/li>\n<\/ul>\n<div data-component-wrapper=\"code-sample\">\n    <code-sample :title=\"'Example networkToken.created webhook without authentication required'\" :id=\"''\" :code-data='[{\"language\":\"json\",\"tabTitle\":\"\",\"content\":\"{\\n    \\\"data\\\" : {\\n        \\\"balancePlatform\\\" : \\\"YOUR_BALANCE_PLATFORM\\\",\\n        \\\"id\\\" : \\\"NWTK00000000000000000000000002\\\",\\n        \\\"authenticationApplied\\\" : false,\\n        \\\"decision\\\" : \\\"approved\\\",\\n        \\\"paymentInstrumentId\\\" : \\\"PI00000000000000000000000002\\\",\\n        \\\"status\\\" : \\\"inactive\\\",\\n        \\\"tokenRequestor\\\" : {\\n            \\\"id\\\" : \\\"40010030273\\\",\\n            \\\"name\\\" : \\\"applePay\\\"\\n        },\\n        \\\"transactionRulesResult\\\" : {\\n            \\\"allHardBlockRulesPassed\\\" : true,\\n            \\\"score\\\" : 0\\n        },\\n        \\\"type\\\" : \\\"wallet\\\",\\n        \\\"validationFacts\\\" : [\\n            {\\n                \\\"result\\\" : \\\"valid\\\",\\n                \\\"type\\\" : \\\"paymentInstrumentFound\\\"\\n            },\\n            {\\n                \\\"result\\\" : \\\"valid\\\",\\n                \\\"type\\\" : \\\"accountLookup\\\"\\n            },\\n            {\\n                \\\"result\\\" : \\\"invalid\\\",\\n                \\\"type\\\" : \\\"avsAddress\\\"\\n            },\\n            {\\n                \\\"result\\\" : \\\"valid\\\",\\n                \\\"type\\\" : \\\"paymentInstrumentActive\\\"\\n            },\\n            {\\n                \\\"result\\\" : \\\"valid\\\",\\n                \\\"type\\\" : \\\"transactionRules\\\"\\n            },\\n            {\\n                \\\"result\\\" : \\\"valid\\\",\\n                \\\"type\\\" : \\\"paymentInstrument\\\"\\n            },\\n            {\\n                \\\"result\\\" : \\\"valid\\\",\\n                \\\"type\\\" : \\\"paymentInstrumentExpirationCheck\\\"\\n            },\\n            {\\n                \\\"result\\\" : \\\"valid\\\",\\n                \\\"type\\\" : \\\"walletValidation\\\"\\n            },\\n            {\\n                \\\"result\\\" : \\\"invalid\\\",\\n                \\\"type\\\" : \\\"avsPostalCode\\\"\\n            },\\n            {\\n                \\\"result\\\" : \\\"valid\\\",\\n                \\\"type\\\" : \\\"inputExpiryDateCheck\\\"\\n            }\\n        ],\\n        \\\"wallet\\\" : {\\n            \\\"accountScore\\\" : \\\"5\\\",\\n            \\\"device\\\" : {\\n                \\\"deviceId\\\" : \\\"DEVICE_ID\\\"\\n            },\\n            \\\"deviceScore\\\" : \\\"3\\\",\\n            \\\"provisioningMethod\\\" : \\\"unknown\\\",\\n            \\\"recommendationReasons\\\" : [\\n                ],\\n            \\\"type\\\" : \\\"applePay\\\"\\n        }\\n    },\\n    \\\"environment\\\" : \\\"test\\\",\\n    \\\"timestamp\\\" : \\\"2026-03-03T19:14:09.779Z\\\",\\n    \\\"type\\\" : \\\"balancePlatform.networkToken.created\\\"\\n}\"}]' :enable-copy-link-to-code-block=\"true\" :code-sample-card-size=\"'fullsize'\"><\/code-sample>\n<\/div>\n<h2>Network token updated<\/h2>\n<p>Adyen sends a  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/balanceplatform-webhooks\/latest\/post\/balancePlatform.networkToken.updated\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">balancePlatform.networkToken.updated<\/a> webhook message when the status of a network token changes. These webhook messages correspond to the later stages of the <a href=\"\/pt\/issuing\/tokens-digital-wallet#provisioning-for-a-digital-wallet\">provisioning flow<\/a>, after Adyen has completed the risk analysis and the cardholder has completed any required verification.<\/p>\n<h3 id=\"provisioned-no-auth\">Provisioned without authentication<\/h3>\n<p>Adyen sends this webhook message after <a href=\"\/pt\/issuing\/tokens-digital-wallet?tab=token-activated-automatically\">activating a network token automatically<\/a> without cardholder verification. At this point in the provisioning flow, the card is available in the cardholder's digital wallet and ready for payments.<\/p>\n<p>Use this webhook message to update your app UI to show the card is active in the wallet.<\/p>\n<p>The webhook message contains:<\/p>\n<ul>\n<li><code>type<\/code>: <strong>balancePlatform.networkToken.updated<\/strong><\/li>\n<li><code>status<\/code>: <strong>active<\/strong><\/li>\n<li><code>authenticationApplied<\/code>: <strong>false<\/strong><\/li>\n<\/ul>\n<div data-component-wrapper=\"code-sample\">\n    <code-sample :title=\"'Example networkToken.updated webhook for provisioning without authentication'\" :id=\"''\" :code-data='[{\"language\":\"json\",\"tabTitle\":\"\",\"content\":\"{\\n    \\\"data\\\" : {\\n        \\\"balancePlatform\\\" : \\\"YOUR_BALANCE_PLATFORM\\\",\\n        \\\"id\\\" : \\\"NWTK00000000000000000000000001\\\",\\n        \\\"authenticationApplied\\\" : false,\\n        \\\"paymentInstrumentId\\\" : \\\"PI00000000000000000000000001\\\",\\n        \\\"status\\\" : \\\"active\\\",\\n        \\\"tokenRequestor\\\" : {\\n            \\\"id\\\" : \\\"40010075001\\\",\\n            \\\"name\\\" : \\\"googlePay\\\"\\n        },\\n        \\\"type\\\" : \\\"wallet\\\",\\n        \\\"wallet\\\" : {\\n            \\\"device\\\" : {\\n                \\\"deviceId\\\" : \\\"DEVICE_ID\\\",\\n                \\\"formFactor\\\" : \\\"mobilephone_or_tablet\\\",\\n                \\\"osName\\\" : \\\"android\\\"\\n            },\\n            \\\"provisioningMethod\\\" : \\\"push\\\",\\n            \\\"type\\\" : \\\"googlePay\\\"\\n        }\\n    },\\n    \\\"environment\\\" : \\\"test\\\",\\n    \\\"timestamp\\\" : \\\"2022-10-25T10:45:00+02:00\\\",\\n    \\\"type\\\" : \\\"balancePlatform.networkToken.updated\\\"\\n}\"}]' :enable-copy-link-to-code-block=\"true\" :code-sample-card-size=\"'fullsize'\"><\/code-sample>\n<\/div>\n<h3 id=\"provisioned-with-auth\">Provisioned with authentication<\/h3>\n<p>Adyen sends this webhook message after activating a network token that required identity verification. At this point in the provisioning flow, the cardholder has completed either <a href=\"\/pt\/issuing\/tokens-digital-wallet?tab=two-factor-authentication-required_2\">two-factor authentication<\/a> (OTP through SMS or email) or <a href=\"\/pt\/issuing\/tokens-digital-wallet?tab=phone-call-authentication-required_3\">phone call authentication<\/a>. The card is available in the cardholder's digital wallet and ready for payments.<\/p>\n<p>Use this webhook message to update the card status in your app from \"pending verification\" to active.<\/p>\n<p>The webhook message contains:<\/p>\n<ul>\n<li><code>type<\/code>: <strong>balancePlatform.networkToken.updated<\/strong><\/li>\n<li><code>status<\/code>: <strong>active<\/strong><\/li>\n<li><code>authenticationApplied<\/code>: <strong>true<\/strong><\/li>\n<\/ul>\n<div data-component-wrapper=\"code-sample\">\n    <code-sample :title=\"'Example networkToken.updated webhook for provisioning with authentication'\" :id=\"''\" :code-data='[{\"language\":\"json\",\"tabTitle\":\"\",\"content\":\"{\\n    \\\"data\\\" : {\\n        \\\"balancePlatform\\\" : \\\"YOUR_BALANCE_PLATFORM\\\",\\n        \\\"id\\\" : \\\"NWTK00000000000000000000000001\\\",\\n        \\\"authenticationApplied\\\" : true,\\n        \\\"paymentInstrumentId\\\" : \\\"PI00000000000000000000000001\\\",\\n        \\\"status\\\" : \\\"active\\\",\\n        \\\"tokenRequestor\\\" : {\\n            \\\"id\\\" : \\\"40010030273\\\",\\n            \\\"name\\\" : \\\"applePay\\\"\\n        },\\n        \\\"type\\\" : \\\"wallet\\\",\\n        \\\"wallet\\\" : {\\n            \\\"device\\\" : {\\n                \\\"deviceId\\\" : \\\"DEVICE_ID\\\",\\n                \\\"formFactor\\\" : \\\"phone\\\"\\n            },\\n            \\\"provisioningMethod\\\" : \\\"manual\\\",\\n            \\\"type\\\" : \\\"applePay\\\"\\n        }\\n    },\\n    \\\"environment\\\" : \\\"test\\\",\\n    \\\"timestamp\\\" : \\\"2022-10-25T10:50:00+02:00\\\",\\n    \\\"type\\\" : \\\"balancePlatform.networkToken.updated\\\"\\n}\"}]' :enable-copy-link-to-code-block=\"true\" :code-sample-card-size=\"'fullsize'\"><\/code-sample>\n<\/div>\n<h3 id=\"token-closed\">Network token closed<\/h3>\n<p>Adyen sends this webhook message when a network token is permanently closed. This happens in the following scenarios:<\/p>\n<ul>\n<li><strong>Provisioning declined<\/strong>: The <a href=\"\/pt\/issuing\/tokens-digital-wallet?tab=token-closed-automatically_4\">risk analysis failed<\/a> and Adyen closed the token automatically. The cardholder cannot add the card to the wallet.<\/li>\n<li><strong>Cardholder removed the card<\/strong>: The cardholder removed the card from their digital wallet.<\/li>\n<li><strong>Token revoked with the API<\/strong>: You closed the token by making a PATCH  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/balanceplatform\/latest\/patch\/networkTokens\/(networkTokenId)\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/networkTokens\/{networkTokenId}<\/a> request.<\/li>\n<li><strong>Payment instrument closed<\/strong>: The underlying <a href=\"\/pt\/issuing\/account-structure-resources#your-balance-platform\">payment instrument<\/a> was closed.<\/li>\n<\/ul>\n<p>Use this webhook message to update your app UI to reflect that the card is no longer available in the wallet.<\/p>\n<p>The webhook message contains:<\/p>\n<ul>\n<li><code>type<\/code>: <strong>balancePlatform.networkToken.updated<\/strong><\/li>\n<li><code>status<\/code>: <strong>closed<\/strong><\/li>\n<\/ul>\n<div data-component-wrapper=\"code-sample\">\n    <code-sample :title=\"'Example networkToken.updated webhook for a closed token'\" :id=\"''\" :code-data='[{\"language\":\"json\",\"tabTitle\":\"\",\"content\":\"{\\n    \\\"data\\\" : {\\n        \\\"balancePlatform\\\" : \\\"YOUR_BALANCE_PLATFORM\\\",\\n        \\\"id\\\" : \\\"NWTK00000000000000000000000001\\\",\\n        \\\"paymentInstrumentId\\\" : \\\"PI00000000000000000000000001\\\",\\n        \\\"status\\\" : \\\"closed\\\",\\n        \\\"tokenRequestor\\\" : {\\n            \\\"id\\\" : \\\"40010075001\\\",\\n            \\\"name\\\" : \\\"googlePay\\\"\\n        },\\n        \\\"type\\\" : \\\"wallet\\\",\\n        \\\"wallet\\\" : {\\n            \\\"device\\\" : {\\n                \\\"deviceId\\\" : \\\"DEVICE_ID\\\",\\n                \\\"formFactor\\\" : \\\"mobilephone_or_tablet\\\",\\n                \\\"osName\\\" : \\\"android\\\"\\n            },\\n            \\\"type\\\" : \\\"googlePay\\\"\\n        }\\n    },\\n    \\\"environment\\\" : \\\"test\\\",\\n    \\\"timestamp\\\" : \\\"2022-11-15T14:30:00+02:00\\\",\\n    \\\"type\\\" : \\\"balancePlatform.networkToken.updated\\\"\\n}\"}]' :enable-copy-link-to-code-block=\"true\" :code-sample-card-size=\"'fullsize'\"><\/code-sample>\n<\/div>\n<h2>See also<\/h2>\n<div class=\"see-also-links output-inline\" id=\"see-also\">\n<ul><li><a href=\"\/development-resources\/webhooks\/configure-and-manage\"\n                        target=\"_self\"\n                        >\n                    Set up webhooks\n                <\/a><\/li><li><a href=\"\/issuing\/network-tokens\"\n                        target=\"_self\"\n                        >\n                    Network tokens\n                <\/a><\/li><\/ul><\/div>\n","url":"https:\/\/docs.adyen.com\/pt\/issuing\/webhook-types\/network-tokens-events","articleFields":{"description":"Learn which webhooks Adyen sends when your cardholders add Adyen-issued cards to digital wallets.","last_edit_on":"16-03-2026 11:09","feedback_component":true,"parameters":{"directoryPath":"\/issuing"}},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/issuing\/webhook-types\/network-tokens-events","title":"Webhooks for network tokens","content":"Adyen sends webhooks for events in network token lifecycles. When your cardholders add their Adyen-issued cards to digital wallets like Apple Pay or Google Pay, Adyen replaces the card data with a network token. Learn more about network tokens in Tokens for digital wallets.\nThese webhooks help you monitor and control tokenized cards. This page covers the following events:\n\nNetwork token created: When a cardholder initially adds their card to a digital wallet\nNetwork token updated: When the token status changes during or after provisioning\n\nIn your Customer Area, subscribe to Configuration webhooks to get these events. They help you track where your cards are tokenized, respond to provisioning decisions, and audit network token activity.\nWebhook types\nWebhook messages inform you when Adyen creates or updates a network token, and whether the cardholder must complete authentication before Adyen activates the token.\nYou can identify the webhooks triggered by network token events by using the following values:\n\n\n\nParameter\nDescription\nValue\n\n\n\n\ntype\nThe webhook type.\nbalancePlatform.networkToken.created or balancePlatform.networkToken.updated\n\n\ndata.status\nThe status of the network token.\ninactive: Not yet activated.active: Ready for payments.suspended: Temporarily disabled.closed: Permanently closed.\n\n\ndata.decision\nThe decision for the network token request.\napproved, requireAuthentication, declined\n\n\n\nNetwork token created\nAdyen sends a  balancePlatform.networkToken.created webhook message when a cardholder adds their Adyen-issued card to a digital wallet. At this point in the provisioning flow, Adyen has received the network token request from the card scheme, created a network token with status inactive, and completed the risk analysis.\nThe decision field specifies the outcome of the risk analysis and determines what happens next in the wallet:\n\nrequireAuthentication: The digital wallet shows the cardholder a verification screen. Adyen requires two-factor authentication (OTP through SMS or email) or phone call verification before activating the token.\napproved: The risk analysis passed. Adyen activates the token automatically without further cardholder action.\n\nNetwork token created with authentication required\nAdyen sends this webhook message when the risk analysis requires identity verification before activating the token. At this point in the provisioning flow, the cardholder sees a verification screen in their wallet app, or a prompt to contact your call center.\nUse this webhook message to show a \"pending verification\" status for this card in your app.\nThe webhook message contains:\n\ntype: balancePlatform.networkToken.created\nstatus: inactive\ndecision: requireAuthentication\n\n\n    \n\nNetwork token created without authentication required\nAdyen sends this webhook message when the risk analysis determines low risk and no cardholder verification is required. At this point in the provisioning flow, Adyen activates the token automatically. After receiving this webhook message, expect a  balancePlatform.networkToken.updated webhook message that confirms the token is active.\nThe webhook message contains:\n\ntype: balancePlatform.networkToken.created\nstatus: inactive\ndecision: approved\n\n\n    \n\nNetwork token updated\nAdyen sends a  balancePlatform.networkToken.updated webhook message when the status of a network token changes. These webhook messages correspond to the later stages of the provisioning flow, after Adyen has completed the risk analysis and the cardholder has completed any required verification.\nProvisioned without authentication\nAdyen sends this webhook message after activating a network token automatically without cardholder verification. At this point in the provisioning flow, the card is available in the cardholder's digital wallet and ready for payments.\nUse this webhook message to update your app UI to show the card is active in the wallet.\nThe webhook message contains:\n\ntype: balancePlatform.networkToken.updated\nstatus: active\nauthenticationApplied: false\n\n\n    \n\nProvisioned with authentication\nAdyen sends this webhook message after activating a network token that required identity verification. At this point in the provisioning flow, the cardholder has completed either two-factor authentication (OTP through SMS or email) or phone call authentication. The card is available in the cardholder's digital wallet and ready for payments.\nUse this webhook message to update the card status in your app from \"pending verification\" to active.\nThe webhook message contains:\n\ntype: balancePlatform.networkToken.updated\nstatus: active\nauthenticationApplied: true\n\n\n    \n\nNetwork token closed\nAdyen sends this webhook message when a network token is permanently closed. This happens in the following scenarios:\n\nProvisioning declined: The risk analysis failed and Adyen closed the token automatically. The cardholder cannot add the card to the wallet.\nCardholder removed the card: The cardholder removed the card from their digital wallet.\nToken revoked with the API: You closed the token by making a PATCH  \/networkTokens\/{networkTokenId} request.\nPayment instrument closed: The underlying payment instrument was closed.\n\nUse this webhook message to update your app UI to reflect that the card is no longer available in the wallet.\nThe webhook message contains:\n\ntype: balancePlatform.networkToken.updated\nstatus: closed\n\n\n    \n\nSee also\n\n\n                    Set up webhooks\n                \n                    Network tokens\n                \n","type":"page","locale":"pt","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Adyen Issuing","lvl2":"Issuing webhook types","lvl3":"Webhooks for network tokens"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/issuing","lvl2":"https:\/\/docs.adyen.com\/pt\/issuing\/webhook-types","lvl3":"\/pt\/issuing\/webhook-types\/network-tokens-events"},"levels":4,"category":"Issuing","category_color":"green","tags":["Webhooks","network","tokens"]}}