{"title":"Network tokenization","category":"default","creationDate":1568794800,"content":"<p>Card networks, like Visa, Mastercard, and American Express, offer services that create a network token for a card. A network token is 16-digit alternative for the Primary Account Number (PAN), and is unique per combination of shopper and merchant. When making a payment, the card details can be swapped for the network token.<\/p>\n<p>Making payments with network tokens has important benefits:<\/p>\n<ul>\n<li>Reduced shopper friction and declines because card networks maintain network tokens to ensure tokens remain valid when the card details change. For example, if the shopper receives a new card because the old one expired or was lost, the network token remains the same.<\/li>\n<li>Higher authorization rates compared to payments made without network tokens.<\/li>\n<li>Minimal integration efforts for adopting <a href=\"https:\/\/www.emvco.com\/emv-technologies\/payment-tokenisation\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">EMVCo's network token standards<\/a>.<\/li>\n<li>Better payment security because each transaction is protected with a single-use cryptogram.<\/li>\n<\/ul>\n<p>This page describes how you can implement network tokenization.<\/p>\n<h2>Requirements<\/h2>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Requirement<\/th>\n<th style=\"text-align: left;\">Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><strong>Integration type<\/strong><\/td>\n<td style=\"text-align: left;\">An <a href=\"\/pt\/online-payments\/build-your-integration\/\">online payments integration<\/a> that supports <a href=\"\/pt\/payment-methods\/cards\/\">card payments<\/a>.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong><a href=\"\/pt\/development-resources\/api-credentials\/roles\/\">API credential roles<\/a><\/strong><\/td>\n<td style=\"text-align: left;\">Make sure that you have the following role(s): <ul><li markdown=\"1\"><strong>Checkout webservice role<\/strong><\/li> <li markdown=\"1\"><strong>Merchant Recurring role<\/strong><\/li><\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong><a href=\"\/pt\/development-resources\/webhooks\">Webhooks<\/a><\/strong><\/td>\n<td style=\"text-align: left;\">Subscribe to the Standard webhooks.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><strong>Limitations<\/strong><\/td>\n<td style=\"text-align: left;\">Network tokenization is only applicable for payments acquired by Adyen. It cannot be used with external acquirer connections.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>How it works<\/h2>\n<p>Network tokenization is different from <a href=\"\/pt\/online-payments\/tokenization\">Adyen tokenization<\/a>. With <strong>tokenization<\/strong>, Adyen swaps the shopper's card details from your payment request for a token. You receive this token in a webhook so that you can use the token instead of the card details in later recurring payment requests for that same shopper.<\/p>\n<p>With <strong>network tokenization<\/strong>, the shopper's card details are swapped for a network token. How this is done, depends on the implementation option you choose:<\/p>\n<ul>\n<li>\n<p><strong><a href=\"#network-tokens-collected-by-Adyen\">Let Adyen manage network tokens<\/a> on your behalf.<\/strong><br \/>\nThis option does not require any additional integration. We collect and store network tokens from the card schemes. When you send a payment request, we automatically swap the card details from your payment request for the network token and then forward the payment for authorization.<br \/>\nYou can use our tokenization feature together with network tokenization. When your payment request contains a <code>storedPaymentMethodId<\/code> token, we automatically swap that for a network token. We recommend combining these features because that limits your PCI scope and further increases authorization rates.<\/p>\n<\/li>\n<li>\n<p><strong><a href=\"#existing-network-tokens\">Manage network tokens yourself<\/a>.<\/strong><br \/>\nThis requires additional steps, but you can keep your existing network tokens and use them in the payment requests that you send to Adyen. It is not possible to combine this with our tokenization feature.<\/p>\n<\/li>\n<\/ul>\n<h3>Sharing network tokens<\/h3>\n<p>If you use multiple merchant accounts, you can share network tokens between them. This allows a shopper to use their saved card seamlessly across all of your websites or apps. To enable this feature, 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<h3>Forward network tokens<\/h3>\n<p>You can <a href=\"\/pt\/online-payments\/tokenization\/forward-payment-details\">forward network tokens<\/a> to a PCI-compliant third party, such as another payment service provider.<\/p>\n<h2 id=\"co-badged-in-us\">Co-badged network tokens in the US<\/h2>\n<p>Regardless of the <a href=\"#how-it-works\">implementation option<\/a> you choose, you can benefit from routing <a href=\"#co-badged-in-us\">co-badged network tokens<\/a> to the optimal network in the US.<\/p>\n<p>In the US, some Visa, Mastercard, and Discover network tokens are co-badged with one or more US Debit networks: Accel, Maestro&nbsp;USA, NYCE, PULSE, or STAR. This means that it is possible to route the payment over the network with the lowest costs and\/or the best authorization rate.<\/p>\n<p>To enable routing co-badged network tokens, you need to add the US Debit payment methods to your merchant account.<\/p>\n<p>Payment routing is based on:<\/p>\n<ul>\n<li>Any routing priorities set for your merchant account. For example, 1: PULSE and 2: Visa.<\/li>\n<li>Optimized routing determined by Adyen, provided this does not contradict any routing priorities for your account.<\/li>\n<\/ul>\n<h3>Force the route for an individual payment<\/h3>\n<p>You can force the route for an individual payment:<\/p>\n<ol>\n<li>Make a POST  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/cardDetails\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/cardDetails<\/a> request for a list of brands on the network token or card.<\/li>\n<li>In your  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/payments<\/a> request, use the <code>paymentMethod.brand<\/code> parameter to specify the network over which you want to route the payment.<\/li>\n<\/ol>\n<h2 id=\"network-tokens-collected-by-Adyen\">Let Adyen manage network tokens<\/h2>\n<p>To manage network tokens yourself, 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 payments with network tokens.<\/p>\n<p>If Adyen manages your network tokens, you can benefit from network tokenization without changing anything in your <a href=\"\/pt\/payment-methods\/cards\">card payment integration<\/a>. You continue using your regular payment flow, and Adyen swaps card details or the <code>storedPaymentMethodId<\/code> token for a network token.<\/p>\n<p>Optionally, you can set up receiving the following additional data in your payment responses:<\/p>\n<ul>\n<li><a href=\"#attempts-data\">Data about attempts to use a network token<\/a>.<\/li>\n<li><a href=\"#optional-collect-bin-and-summary-of-the-network-token\">Data about the network token itself<\/a>.<\/li>\n<\/ul>\n<h3 id=\"attempts-data\">Collect attempts data<\/h3>\n<p>If you want to analyze network token usage, you can set up receiving additional information in your  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/payments<\/a> response about attempts to get a payment authorized with or without a network token.<\/p>\n<p>To set up receiving attempts data:<\/p>\n<ol>\n<li>Log in to your <a href=\"https:\/\/ca-test.adyen.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Customer Area<\/a>.<\/li>\n<li>Go to <strong>Developers<\/strong> &gt; <strong>Additional data<\/strong>.<\/li>\n<li>In the <strong>Acquirer<\/strong> section, select <strong>Include the retry attempts<\/strong>.<\/li>\n<li>Select <strong>Save configuration<\/strong>.<\/li>\n<\/ol>\n<p>The <code>additionalData<\/code> object in the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/payments<\/a> response will then contain the following parameters:<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Parameter name<\/th>\n<th style=\"text-align: left;\">Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><code>retry.attempt.acquirer<\/code><\/td>\n<td style=\"text-align: left;\">The  name of the acquirer that processed the payment.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>retry.attempt.acquirerAccount<\/code><\/td>\n<td style=\"text-align: left;\">The acquirer account that was used for the transaction.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>retry.attempt.responseCode<\/code><\/td>\n<td style=\"text-align: left;\">The <a href=\"\/pt\/development-resources\/raw-acquirer-responses#visa-and-mastercard-raw-responses\">numeric acquirer response code<\/a> from the card network.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>retry.attempt.rawResponse<\/code><\/td>\n<td style=\"text-align: left;\">The details of the <a href=\"\/pt\/development-resources\/raw-acquirer-responses\">raw unmodified response from the acquirer<\/a>.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>retry.attempt.networkTokenOffered<\/code><\/td>\n<td style=\"text-align: left;\">Indicates if the transaction was attempted with or without a network token.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>In the following example, the <code>additionalData<\/code> object shows that the payment was approved on the first attempt (<code>attempt1<\/code>) and that a network token was used.<\/p>\n<div data-component-wrapper=\"code-sample\">\n    <code-sample :title=\"'Successful first attempt with a network token'\" :id=\"''\" :code-data='[{\"language\":\"json\",\"tabTitle\":\"\",\"content\":\"{\\n   ...\\n   \\\"additionalData\\\": {\\n      \\\"retry.attempt1.acquirer\\\": \\\"Acquirer\\\",\\n      \\\"retry.attempt1.acquirerAccount\\\": \\\"AcquirerAccount\\\",\\n      \\\"retry.attempt1.responseCode\\\": \\\"00\\\",\\n      \\\"retry.attempt1.rawResponse\\\": \\\"Approved or completed successfully\\\",\\n      \\\"retry.attempt1.networkTokenOffered\\\": \\\"true\\\"\\n   }\\n}\"}]' :enable-copy-link-to-code-block=\"true\" :code-sample-card-size=\"'fullsize'\"><\/code-sample>\n<\/div>\n<p>If a payment attempt with a network token fails (<code>attempt1<\/code>), we automatically retry the payment. In the second attempt (<code>attempt2<\/code>), we do not swap the card details or the <code>storedPaymentMethodId<\/code> token for a network token.<\/p>\n<div data-component-wrapper=\"code-sample\">\n    <code-sample :title=\"'First attempt with network token failed, second attempt without network token succeeded'\" :id=\"''\" :code-data='[{\"language\":\"json\",\"tabTitle\":\"\",\"content\":\"{\\n   ...\\n   \\\"additionalData\\\": {\\n      \\\"retry.attempt2.acquirer\\\": \\\"Acquirer\\\",\\n      \\\"retry.attempt2.acquirerAccount\\\": \\\"AcquirerAccount\\\",\\n      \\\"retry.attempt2.responseCode\\\": \\\"00\\\",\\n      \\\"retry.attempt2.rawResponse\\\": \\\"Approved or completed successfully\\\",\\n      \\\"retry.attempt2.networkTokenOffered\\\": \\\"false\\\",\\n      \\\"retry.attempt1.acquirer\\\": \\\"Acquirer\\\",\\n      \\\"retry.attempt1.acquirerAccount\\\": \\\"AcquirerAccount\\\",\\n      \\\"retry.attempt1.responseCode\\\": \\\"05\\\",\\n      \\\"retry.attempt1.rawResponse\\\": \\\"Refused\\\",\\n      \\\"retry.attempt1.networkTokenOffered\\\": \\\"true\\\"\\n   }\\n}\"}]' :enable-copy-link-to-code-block=\"true\" :code-sample-card-size=\"'fullsize'\"><\/code-sample>\n<\/div>\n<p>The <strong>AUTHORISATION<\/strong> webhook contains the same additional information as the <code>additionalData<\/code> object from the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/payments<\/a> response.<\/p>\n<h3 id=\"optional-collect-bin-and-summary-of-the-network-token\">Collect data about network tokens<\/h3>\n<p>You can set up receiving the following additional information in your  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/payments<\/a> response:<\/p>\n<ul>\n<li>The BIN and last four digits of the network token used.<\/li>\n<li>The BIN, last four digits, and expiry date of the card associated with the network token.<\/li>\n<\/ul>\n<p>To set up receiving data about the network token:<\/p>\n<ol>\n<li>Log in to your <a href=\"https:\/\/ca-test.adyen.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Customer Area<\/a> and switch to your merchant account.<\/li>\n<li>Go to <strong>Developers<\/strong> &gt; <strong>Additional data<\/strong>.<\/li>\n<li>In the <strong>Card<\/strong> section, select <strong>Network token bin and summary for tokenised payments<\/strong>.<\/li>\n<li>Select <strong>Save configuration<\/strong>.<\/li>\n<\/ol>\n<p>The <code>additionalData<\/code> object in the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/payments<\/a> response will then contain the following parameters:<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Parameter name<\/th>\n<th style=\"text-align: left;\">Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><code>networkToken.bin<\/code><\/td>\n<td style=\"text-align: left;\">The BIN of the network token.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>networkToken.tokenSummary<\/code><\/td>\n<td style=\"text-align: left;\">The last four digits of the network token.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>latestCard.bin<\/code><\/td>\n<td style=\"text-align: left;\">The BIN of the card. This is only returned for Mastercard tokens.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>latestCard.summary<\/code><\/td>\n<td style=\"text-align: left;\">The last four digits of the card.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>latestCard.expiryDate<\/code><\/td>\n<td style=\"text-align: left;\">The expiry month and year of the card.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<div data-component-wrapper=\"code-sample\">\n    <code-sample :title=\"'Additional data for the BIN and summary of the network token'\" :id=\"''\" :code-data='[{\"language\":\"json\",\"tabTitle\":\"\",\"content\":\"{\\n  ...\\n  \\\"additionalData\\\": {\\n    \\\"latestCard.bin\\\": \\\"557703\\\",\\n    \\\"latestCard.summary\\\": \\\"4309\\\",\\n    \\\"latestCard.expiryDate\\\": \\\"03\\\/2030\\\",\\n    \\\"networkToken.available\\\": \\\"true\\\",\\n    \\\"networkToken.bin\\\": \\\"489537\\\",\\n    \\\"networkToken.tokenSummary\\\": \\\"3500\\\"\\n  }\\n}\"}]' :enable-copy-link-to-code-block=\"true\" :code-sample-card-size=\"'fullsize'\"><\/code-sample>\n<\/div>\n<h2 id=\"existing-network-tokens\">Manage network tokens yourself<\/h2>\n<p>Because network tokens are non-sensitive, you can also choose to collect and store them yourself. If you are already collecting network tokens from card networks like Visa, Mastercard and American Express, you can use those network tokens to make payments with Adyen.<\/p>\n<p>To manage network tokens yourself:<\/p>\n<ol>\n<li><a href=\"#enable-receiving-relevant-data\">Enable receiving relevant data<\/a> in your Customer Area to receive card details and network token information in the payment response.<\/li>\n<li><a href=\"#make-the-initial-payment-with-a-network-token\">Make the initial payment with a network token<\/a>, using the network token you collect from the card network.<\/li>\n<li>You receive the <code>networkTxReference<\/code> that you need to use for subsequent payments in the payment response. Save this value.<\/li>\n<li><a href=\"#make-a-subsequent-payment-with-a-network-token\">Make a subsequent payment using the same network token<\/a>.<\/li>\n<\/ol>\n<h3>Enable receiving relevant data<\/h3>\n<p>To enable the relevant fields:<\/p>\n<ol>\n<li>Log in to your <a href=\"https:\/\/ca-test.adyen.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">Customer Area<\/a>.<\/li>\n<li>Go to <strong>Developers<\/strong> &gt; <strong>Additional data<\/strong>.<\/li>\n<li>Select the following fields:\n<ul>\n<li>In the <strong>Acquirer<\/strong> section: <strong>Network Transaction Reference<\/strong><\/li>\n<li>In the <strong>Card<\/strong> section: <strong>Card bin<\/strong> and <strong>Card summary<\/strong><\/li>\n<\/ul><\/li>\n<li>Select <strong>Save configuration<\/strong>.<\/li>\n<\/ol>\n<h3>Make the initial payment with a network token<\/h3>\n<p>Make a one-off payment, the first payment in a subscription, or the first payment for automatic top-ups.<\/p>\n<ol>\n<li>\n<p>Make a POST  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/payments<\/a> request, specifying:<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Parameter name<\/th>\n<th style=\"text-align: left;\">Description<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\"><code>paymentMethod.type<\/code><\/td>\n<td style=\"text-align: left;\"><strong>networkToken<\/strong><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>paymentMethod.expiryMonth<\/code><\/td>\n<td style=\"text-align: left;\">The expiry month of the network token.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>paymentMethod.expiryYear<\/code><\/td>\n<td style=\"text-align: left;\">The expiry year of the network token.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>paymentMethod.cvc<\/code><\/td>\n<td style=\"text-align: left;\">Optional. The card verification code or security code.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>paymentMethod.holderName<\/code><\/td>\n<td style=\"text-align: left;\">The name of the cardholder associated with the network token.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>paymentMethod.number<\/code><\/td>\n<td style=\"text-align: left;\">The network token you get from the card networks.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>paymentMethod.brand<\/code><\/td>\n<td style=\"text-align: left;\">Optional. For <a href=\"#co-badged-in-us\">co-badged network tokens in the US<\/a>, this is the card network that you want to route the transaction to. Allowed values: <ul><li markdown=\"1\"><strong>visa<\/strong><\/li> <li markdown=\"1\"><strong>mc<\/strong><\/li> <li markdown=\"1\"><strong>amex<\/strong><\/li> <li markdown=\"1\"><strong>discover<\/strong><\/li> <li markdown=\"1\"><strong>accel<\/strong><\/li> <li markdown=\"1\"><strong>maestro_usa<\/strong><\/li> <li markdown=\"1\"><strong>nyce<\/strong><\/li> <li markdown=\"1\"><strong>pulse<\/strong><\/li> <li markdown=\"1\"><strong>star<\/strong><\/li> <\/ul><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>mpiData.directoryResponse<\/code><\/td>\n<td style=\"text-align: left;\"><strong>Y<\/strong><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>mpiData.authenticationResponse<\/code><\/td>\n<td style=\"text-align: left;\"><strong>Y<\/strong><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>mpiData.tokenAuthenticationVerificationValue<\/code><\/td>\n<td style=\"text-align: left;\">The network token authentication verification value (TAVV). This is the network token cryptogram. <br> If using Checkout API v67 and earlier, use the parameter <code>mpiData.cavv<\/code> instead. This is the cardholder authentication value (CAVV) received from the issuer.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>mpiData.eci<\/code><\/td>\n<td style=\"text-align: left;\">The electronic commerce indicator you get from the issuer.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>recurringProcessingModel<\/code><\/td>\n<td style=\"text-align: left;\"><strong>CardOnFile<\/strong>, <strong>Subscription<\/strong>, or <strong>UnscheduledCardOnFile<\/strong>, depending on your <a href=\"\/pt\/online-payments\/tokenization#recurring-payment-types\">business model<\/a>.<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\"><code>shopperInteraction<\/code><\/td>\n<td style=\"text-align: left;\"><strong>Ecommerce<\/strong><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<div data-component-wrapper=\"code-sample\">\n<code-sample :title=\"'Initial one-off \/payments request with a network token'\" :id=\"''\" :code-data='[{\"language\":\"json\",\"tabTitle\":\"\",\"content\":\"{\\n   \\\"merchantAccount\\\": \\\"YOUR_MERCHANT_ACCOUNT\\\",\\n   \\\"reference\\\": \\\"YOUR_PAYMENT_REFERENCE\\\",\\n   \\\"amount\\\": {\\n      \\\"currency\\\": \\\"USD\\\",\\n      \\\"value\\\": 1000\\n   },\\n   \\\"paymentMethod\\\": {\\n      \\\"type\\\": \\\"networkToken\\\",\\n      \\\"brand\\\": \\\"visa\\\",\\n      \\\"expiryMonth\\\": \\\"08\\\",\\n      \\\"expiryYear\\\": \\\"2028\\\",\\n      \\\"cvc\\\": \\\"737\\\",\\n      \\\"holderName\\\": \\\"CARDHOLDER_NAME\\\",\\n      \\\"number\\\": \\\"666666xxxxxx6666\\\"\\n   },\\n   \\\"mpiData\\\":{\\n      \\\"directoryResponse\\\":\\\"Y\\\",\\n      \\\"authenticationResponse\\\":\\\"Y\\\",\\n      \\\"tokenAuthenticationVerificationValue\\\":\\\"AAEBAwQjSQAAXXXXXXXJYe0BbQA=\\\",\\n      \\\"eci\\\":\\\"07\\\"\\n   },\\n   \\\"returnUrl\\\": \\\"https:\\\/\\\/your-company.example.com\\\/\\\",\\n   \\\"shopperReference\\\": \\\"YOUR_SHOPPER_REFERENCE\\\",\\n   \\\"recurringProcessingModel\\\":\\\"CardOnFile\\\",\\n   \\\"shopperInteraction\\\": \\\"Ecommerce\\\"\\n}\"}]' :enable-copy-link-to-code-block=\"true\" :code-sample-card-size=\"'fullsize'\"><\/code-sample>\n<\/div>\n<\/li>\n<li>\n<p>In the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/payments<\/a> response, note the <code>networkTxReference<\/code> field. You need this value to make subsequent subscription or automatic top-up payments.<\/p>\n<\/li>\n<\/ol>\n<h3>Make a subsequent payment with a network token<\/h3>\n<p>Make a subsequent payment, using the <code>networkTxReference<\/code> you received in the payment response.<\/p>\n\n<div id=\"tabhvVMT\">\n    <div data-component-wrapper=\"tabs\">\n        <tabs\n                        :items=\"[{&quot;title&quot;:&quot;One-off payments&quot;,&quot;content&quot;:&quot;\\n&lt;ol&gt;\\n&lt;li&gt;\\n&lt;p&gt;Make a POST  &lt;a href=\\&quot;https:\\\/\\\/docs.adyen.com\\\/api-explorer\\\/Checkout\\\/latest\\\/post\\\/payments\\&quot; class=\\&quot;codeLabel  external-link no-image\\&quot; target=\\&quot;_blank\\&quot; rel=\\&quot;nofollow noopener noreferrer\\&quot;&gt;\\\/payments&lt;\\\/a&gt; request 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 name&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;paymentMethod.type&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;strong&gt;networkToken&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;paymentMethod.expiryMonth&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The expiry month of the network token.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;paymentMethod.expiryYear&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The expiry year of the network token.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;paymentMethod.cvc&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;Optional. The card verification code or security code.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;paymentMethod.holderName&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The name of the cardholder associated with the network token.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;paymentMethod.number&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The network token you get from the card networks.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;paymentMethod.brand&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;Optional. For &lt;a href=\\&quot;#co-badged-in-us\\&quot;&gt;co-badged network tokens in the US&lt;\\\/a&gt;, this is the card network that you want to route the transaction to. This may be different compared to the initial payment. Allowed values: &lt;ul&gt;&lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;visa&lt;\\\/strong&gt;&lt;\\\/li&gt; &lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;mc&lt;\\\/strong&gt;&lt;\\\/li&gt; &lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;amex&lt;\\\/strong&gt;&lt;\\\/li&gt; &lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;discover&lt;\\\/strong&gt;&lt;\\\/li&gt; &lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;accel&lt;\\\/strong&gt;&lt;\\\/li&gt; &lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;maestro_usa&lt;\\\/strong&gt;&lt;\\\/li&gt; &lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;nyce&lt;\\\/strong&gt;&lt;\\\/li&gt; &lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;pulse&lt;\\\/strong&gt;&lt;\\\/li&gt; &lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;star&lt;\\\/strong&gt;&lt;\\\/li&gt; &lt;\\\/ul&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;mpiData.directoryResponse&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;strong&gt;Y&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;mpiData.authenticationResponse&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;strong&gt;Y&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;mpiData.tokenAuthenticationVerificationValue&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The network token authentication verification value (TAVV). This is the network token cryptogram. &lt;br&gt; If using Checkout API v67 and earlier, use the parameter &lt;code&gt;mpiData.cavv&lt;\\\/code&gt; instead. This is the cardholder authentication value (CAVV) received from the issuer.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;mpiData.eci&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The electronic commerce indicator you get from the issuer.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;recurringProcessingModel&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The value must match the value of the &lt;code&gt;recurringProcessingModel&lt;\\\/code&gt; from the initial payment. For a one-off payment, that is &lt;strong&gt;CardOnFile&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;shopperInteraction&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;strong&gt;ContAuth&lt;\\\/strong&gt;&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/tbody&gt;\\n&lt;\\\/table&gt;\\n&lt;div data-component-wrapper=\\&quot;code-sample\\&quot;&gt;\\n&lt;code-sample :title=\\&quot;&#039;Recurring one-off \\\/payments request with a network token&#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;merchantAccount\\\\\\&quot;: \\\\\\&quot;YOUR_MERCHANT_ACCOUNT\\\\\\&quot;,\\\\n   \\\\\\&quot;reference\\\\\\&quot;: \\\\\\&quot;YOUR_PAYMENT_REFERENCE\\\\\\&quot;,\\\\n   \\\\\\&quot;amount\\\\\\&quot;: {\\\\n      \\\\\\&quot;currency\\\\\\&quot;: \\\\\\&quot;USD\\\\\\&quot;,\\\\n      \\\\\\&quot;value\\\\\\&quot;: 1000\\\\n   },\\\\n   \\\\\\&quot;paymentMethod\\\\\\&quot;: {\\\\n      \\\\\\&quot;type\\\\\\&quot;: \\\\\\&quot;networkToken\\\\\\&quot;,\\\\n      \\\\\\&quot;brand\\\\\\&quot;: \\\\\\&quot;visa\\\\\\&quot;,\\\\n      \\\\\\&quot;expiryMonth\\\\\\&quot;: \\\\\\&quot;08\\\\\\&quot;,\\\\n      \\\\\\&quot;expiryYear\\\\\\&quot;: \\\\\\&quot;2028\\\\\\&quot;,\\\\n      \\\\\\&quot;cvc\\\\\\&quot;: \\\\\\&quot;737\\\\\\&quot;,\\\\n      \\\\\\&quot;holderName\\\\\\&quot;: \\\\\\&quot;CARDHOLDER_NAME\\\\\\&quot;,\\\\n      \\\\\\&quot;number\\\\\\&quot;: \\\\\\&quot;666666xxxxxx6666\\\\\\&quot;,\\\\n   },\\\\n   \\\\\\&quot;mpiData\\\\\\&quot;:{\\\\n      \\\\\\&quot;directoryResponse\\\\\\&quot;:\\\\\\&quot;Y\\\\\\&quot;,\\\\n      \\\\\\&quot;authenticationResponse\\\\\\&quot;:\\\\\\&quot;Y\\\\\\&quot;,\\\\n      \\\\\\&quot;tokenAuthenticationVerificationValue\\\\\\&quot;:\\\\\\&quot;AAEBAwQjSQAAXXXXXXXJYe0BbQA=\\\\\\&quot;,\\\\n      \\\\\\&quot;eci\\\\\\&quot;:\\\\\\&quot;07\\\\\\&quot;\\\\n   },\\\\n   \\\\\\&quot;returnUrl\\\\\\&quot;: \\\\\\&quot;https:\\\\\\\/\\\\\\\/your-company.example.com\\\\\\\/\\\\\\&quot;,\\\\n   \\\\\\&quot;shopperReference\\\\\\&quot;: \\\\\\&quot;YOUR_SHOPPER_REFERENCE\\\\\\&quot;,\\\\n   \\\\\\&quot;recurringProcessingModel\\\\\\&quot;: \\\\\\&quot;CardOnFile\\\\\\&quot;,\\\\n   \\\\\\&quot;shopperInteraction\\\\\\&quot;: \\\\\\&quot;ContAuth\\\\\\&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;In the response, note the &lt;code&gt;additionalData&lt;\\\/code&gt; object. This has information such as the BIN and summary of the card that was charged.&lt;\\\/p&gt;\\n&lt;div data-component-wrapper=\\&quot;code-sample\\&quot;&gt;\\n&lt;code-sample :title=\\&quot;&#039;Additional data object in \\\/payments 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   ...\\\\n   \\\\\\&quot;additionalData\\\\\\&quot;:{\\\\n      \\\\\\&quot;cardBin\\\\\\&quot;:\\\\\\&quot;541333\\\\\\&quot;,\\\\n      \\\\\\&quot;cardSummary\\\\\\&quot;:\\\\\\&quot;1111\\\\\\&quot;,\\\\n      \\\\\\&quot;networkTxReference\\\\\\&quot;:\\\\\\&quot;MCC123456789012\\\\\\&quot;,\\\\n      ...\\\\n   }\\\\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;\\\/ol&gt;\\n&quot;,&quot;altTitle&quot;:null,&quot;oldTabId&quot;:&quot;one-off_payments_0_1&quot;,&quot;relation&quot;:&quot;&quot;},{&quot;title&quot;:&quot;Subscriptions or automatic top-offs&quot;,&quot;content&quot;:&quot;\\n&lt;ol&gt;\\n&lt;li&gt;\\n&lt;p&gt;Make a POST  &lt;a href=\\&quot;https:\\\/\\\/docs.adyen.com\\\/api-explorer\\\/Checkout\\\/latest\\\/post\\\/payments\\&quot; class=\\&quot;codeLabel  external-link no-image\\&quot; target=\\&quot;_blank\\&quot; rel=\\&quot;nofollow noopener noreferrer\\&quot;&gt;\\\/payments&lt;\\\/a&gt; request, 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 name&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;paymentMethod.type&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;strong&gt;networkToken&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;paymentMethod.expiryMonth&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The expiry month of the network token.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;paymentMethod.expiryYear&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The expiry year of the network token.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;paymentMethod.cvc&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;Optional. The card verification code or security code.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;paymentMethod.holderName&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The name of the cardholder associated with the network token.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;paymentMethod.number&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The network token you get from the card networks.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;paymentMethod.brand&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;Optional. For &lt;a href=\\&quot;#co-badged-in-us\\&quot;&gt;co-badged network tokens in the US&lt;\\\/a&gt;, this is the card network that you want to route the transaction to. This may be different compared to the initial payment. Allowed values: &lt;ul&gt;&lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;visa&lt;\\\/strong&gt;&lt;\\\/li&gt; &lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;mc&lt;\\\/strong&gt;&lt;\\\/li&gt; &lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;amex&lt;\\\/strong&gt;&lt;\\\/li&gt; &lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;discover&lt;\\\/strong&gt;&lt;\\\/li&gt; &lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;accel&lt;\\\/strong&gt;&lt;\\\/li&gt; &lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;maestro_usa&lt;\\\/strong&gt;&lt;\\\/li&gt; &lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;nyce&lt;\\\/strong&gt;&lt;\\\/li&gt; &lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;pulse&lt;\\\/strong&gt;&lt;\\\/li&gt; &lt;li markdown=\\&quot;1\\&quot;&gt;&lt;strong&gt;star&lt;\\\/strong&gt;&lt;\\\/li&gt; &lt;\\\/ul&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;paymentMethod.networkPaymentReference&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;The network transaction reference. This is the value of the &lt;code&gt;networkTxReference&lt;\\\/code&gt; field that you received in the response of the initial payment.&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;tr&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;code&gt;recurringProcessingModel&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;This value must match the value of the &lt;code&gt;recurringProcessingModel&lt;\\\/code&gt; from the first payment, either  &lt;strong&gt;Subscription&lt;\\\/strong&gt;, or &lt;strong&gt;UnscheduledCardOnFile&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;shopperInteraction&lt;\\\/code&gt;&lt;\\\/td&gt;\\n&lt;td style=\\&quot;text-align: left;\\&quot;&gt;&lt;strong&gt;ContAuth&lt;\\\/strong&gt;&lt;\\\/td&gt;\\n&lt;\\\/tr&gt;\\n&lt;\\\/tbody&gt;\\n&lt;\\\/table&gt;\\n&lt;div data-component-wrapper=\\&quot;code-sample\\&quot;&gt;\\n&lt;code-sample :title=\\&quot;&#039;Recurring subscription \\\/payments request with a network token&#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;merchantAccount\\\\\\&quot;: \\\\\\&quot;YOUR_MERCHANT_ACCOUNT\\\\\\&quot;,\\\\n   \\\\\\&quot;reference\\\\\\&quot;: \\\\\\&quot;YOUR_PAYMENT_REFERENCE\\\\\\&quot;,\\\\n   \\\\\\&quot;amount\\\\\\&quot;: {\\\\n      \\\\\\&quot;currency\\\\\\&quot;: \\\\\\&quot;USD\\\\\\&quot;,\\\\n      \\\\\\&quot;value\\\\\\&quot;: 1000\\\\n   },\\\\n   \\\\\\&quot;paymentMethod\\\\\\&quot;: {\\\\n      \\\\\\&quot;type\\\\\\&quot;: \\\\\\&quot;networkToken\\\\\\&quot;,\\\\n      \\\\\\&quot;brand\\\\\\&quot;: \\\\\\&quot;visa\\\\\\&quot;,\\\\n      \\\\\\&quot;expiryMonth\\\\\\&quot;: \\\\\\&quot;08\\\\\\&quot;,\\\\n      \\\\\\&quot;expiryYear\\\\\\&quot;: \\\\\\&quot;2028\\\\\\&quot;,\\\\n      \\\\\\&quot;holderName\\\\\\&quot;: \\\\\\&quot;CARDHOLDER_NAME\\\\\\&quot;,\\\\n      \\\\\\&quot;number\\\\\\&quot;: \\\\\\&quot;666666xxxxxx6666\\\\\\&quot;,\\\\n      \\\\\\&quot;networkPaymentReference\\\\\\&quot;: \\\\\\&quot;MCC123456789012\\\\\\&quot;\\\\n   },\\\\n   \\\\\\&quot;returnUrl\\\\\\&quot;: \\\\\\&quot;https:\\\\\\\/\\\\\\\/your-company.example.com\\\\\\\/\\\\\\&quot;,\\\\n   \\\\\\&quot;shopperReference\\\\\\&quot;: \\\\\\&quot;YOUR_SHOPPER_REFERENCE\\\\\\&quot;,\\\\n   \\\\\\&quot;recurringProcessingModel\\\\\\&quot;: \\\\\\&quot;Subscription\\\\\\&quot;,\\\\n   \\\\\\&quot;shopperInteraction\\\\\\&quot;: \\\\\\&quot;ContAuth\\\\\\&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;In the response, note the &lt;code&gt;additionalData&lt;\\\/code&gt; object. This has information such as the BIN and summary of the card that was charged.&lt;\\\/p&gt;\\n&lt;div data-component-wrapper=\\&quot;code-sample\\&quot;&gt;\\n&lt;code-sample :title=\\&quot;&#039;Additional data object in \\\/payments 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   ...\\\\n   \\\\\\&quot;additionalData\\\\\\&quot;:{\\\\n      \\\\\\&quot;cardBin\\\\\\&quot;:\\\\\\&quot;541333\\\\\\&quot;,\\\\n      \\\\\\&quot;cardSummary\\\\\\&quot;:\\\\\\&quot;1111\\\\\\&quot;,\\\\n      \\\\\\&quot;networkTxReference\\\\\\&quot;:\\\\\\&quot;MCC123456789012\\\\\\&quot;,\\\\n      ...\\\\n   }\\\\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&quot;,&quot;altTitle&quot;:null,&quot;oldTabId&quot;:&quot;subscriptions_or_automatic_top-offs_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<h2 id=\"troubleshooting\">Troubleshooting<\/h2>\n<p>When you make a request to create or pay with a network token, the API response informs you of the outcome of the request. If an error occurs, the response includes the <code>status<\/code>, <code>errorCode<\/code>, and <code>errorMessage<\/code> parameters.<\/p>\n<div data-component-wrapper=\"code-sample\">\n    <code-sample :title=\"'Example response for a network token failure'\" :id=\"'example-response-network-token-failure'\" :code-data='[{\"language\":\"json\",\"tabTitle\":\"\",\"content\":\"{\\n    \\\"status\\\": 500,\\n    \\\"errorCode\\\": \\\"26_002\\\",\\n    \\\"message\\\": \\\"The network token is suspended\\\/deactivated\\\",\\n    \\\"errorType\\\": \\\"internal\\\"\\n}\"}]' :enable-copy-link-to-code-block=\"true\" :code-sample-card-size=\"'fullsize'\"><\/code-sample>\n<\/div>\n<p>Use the <a href=\"\/pt\/development-resources\/error-codes#network-token-error-codes\">error code and message<\/a> to learn about the issue and troubleshoot.<\/p>\n<h2 id=\"see-also\">See also<\/h2>\n<div class=\"see-also-links output-inline\" id=\"see-also\">\n<ul><li><a href=\"\/online-payments\/tokenization\"\n                        target=\"_self\"\n                        >\n                    Tokenization\n                <\/a><\/li><li><a href=\"https:\/\/www.emvco.com\/emv-technologies\/payment-tokenisation\/\"\n                        target=\"_blank\"\n                         class=\"external\">\n                    EMVCo's Payment Tokenization Specification\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\/network-tokenization","articleFields":{"description":"Use network tokens to process payments with Adyen for better authorization rates.","feedback_component":true,"last_edit_on":"21-06-2023 22:37","filters_component":false,"page_id":"636b0f7b-771d-4d42-94fe-33a78d3b690b","decision_tree":"[]"},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/online-payments\/network-tokenization","title":"Network tokenization","content":"Card networks, like Visa, Mastercard, and American Express, offer services that create a network token for a card. A network token is 16-digit alternative for the Primary Account Number (PAN), and is unique per combination of shopper and merchant. When making a payment, the card details can be swapped for the network token.\nMaking payments with network tokens has important benefits:\n\nReduced shopper friction and declines because card networks maintain network tokens to ensure tokens remain valid when the card details change. For example, if the shopper receives a new card because the old one expired or was lost, the network token remains the same.\nHigher authorization rates compared to payments made without network tokens.\nMinimal integration efforts for adopting EMVCo's network token standards.\nBetter payment security because each transaction is protected with a single-use cryptogram.\n\nThis page describes how you can implement network tokenization.\nRequirements\n\n\n\nRequirement\nDescription\n\n\n\n\nIntegration type\nAn online payments integration that supports card payments.\n\n\nAPI credential roles\nMake sure that you have the following role(s): Checkout webservice role Merchant Recurring role\n\n\nWebhooks\nSubscribe to the Standard webhooks.\n\n\nLimitations\nNetwork tokenization is only applicable for payments acquired by Adyen. It cannot be used with external acquirer connections.\n\n\n\nHow it works\nNetwork tokenization is different from Adyen tokenization. With tokenization, Adyen swaps the shopper's card details from your payment request for a token. You receive this token in a webhook so that you can use the token instead of the card details in later recurring payment requests for that same shopper.\nWith network tokenization, the shopper's card details are swapped for a network token. How this is done, depends on the implementation option you choose:\n\n\nLet Adyen manage network tokens on your behalf.\nThis option does not require any additional integration. We collect and store network tokens from the card schemes. When you send a payment request, we automatically swap the card details from your payment request for the network token and then forward the payment for authorization.\nYou can use our tokenization feature together with network tokenization. When your payment request contains a storedPaymentMethodId token, we automatically swap that for a network token. We recommend combining these features because that limits your PCI scope and further increases authorization rates.\n\n\nManage network tokens yourself.\nThis requires additional steps, but you can keep your existing network tokens and use them in the payment requests that you send to Adyen. It is not possible to combine this with our tokenization feature.\n\n\nSharing network tokens\nIf you use multiple merchant accounts, you can share network tokens between them. This allows a shopper to use their saved card seamlessly across all of your websites or apps. To enable this feature, contact our Support Team.\nForward network tokens\nYou can forward network tokens to a PCI-compliant third party, such as another payment service provider.\nCo-badged network tokens in the US\nRegardless of the implementation option you choose, you can benefit from routing co-badged network tokens to the optimal network in the US.\nIn the US, some Visa, Mastercard, and Discover network tokens are co-badged with one or more US Debit networks: Accel, Maestro&nbsp;USA, NYCE, PULSE, or STAR. This means that it is possible to route the payment over the network with the lowest costs and\/or the best authorization rate.\nTo enable routing co-badged network tokens, you need to add the US Debit payment methods to your merchant account.\nPayment routing is based on:\n\nAny routing priorities set for your merchant account. For example, 1: PULSE and 2: Visa.\nOptimized routing determined by Adyen, provided this does not contradict any routing priorities for your account.\n\nForce the route for an individual payment\nYou can force the route for an individual payment:\n\nMake a POST  \/cardDetails request for a list of brands on the network token or card.\nIn your  \/payments request, use the paymentMethod.brand parameter to specify the network over which you want to route the payment.\n\nLet Adyen manage network tokens\nTo manage network tokens yourself, ask our Support Team to enable payments with network tokens.\nIf Adyen manages your network tokens, you can benefit from network tokenization without changing anything in your card payment integration. You continue using your regular payment flow, and Adyen swaps card details or the storedPaymentMethodId token for a network token.\nOptionally, you can set up receiving the following additional data in your payment responses:\n\nData about attempts to use a network token.\nData about the network token itself.\n\nCollect attempts data\nIf you want to analyze network token usage, you can set up receiving additional information in your  \/payments response about attempts to get a payment authorized with or without a network token.\nTo set up receiving attempts data:\n\nLog in to your Customer Area.\nGo to Developers &gt; Additional data.\nIn the Acquirer section, select Include the retry attempts.\nSelect Save configuration.\n\nThe additionalData object in the  \/payments response will then contain the following parameters:\n\n\n\nParameter name\nDescription\n\n\n\n\nretry.attempt.acquirer\nThe  name of the acquirer that processed the payment.\n\n\nretry.attempt.acquirerAccount\nThe acquirer account that was used for the transaction.\n\n\nretry.attempt.responseCode\nThe numeric acquirer response code from the card network.\n\n\nretry.attempt.rawResponse\nThe details of the raw unmodified response from the acquirer.\n\n\nretry.attempt.networkTokenOffered\nIndicates if the transaction was attempted with or without a network token.\n\n\n\nIn the following example, the additionalData object shows that the payment was approved on the first attempt (attempt1) and that a network token was used.\n\n    \n\nIf a payment attempt with a network token fails (attempt1), we automatically retry the payment. In the second attempt (attempt2), we do not swap the card details or the storedPaymentMethodId token for a network token.\n\n    \n\nThe AUTHORISATION webhook contains the same additional information as the additionalData object from the  \/payments response.\nCollect data about network tokens\nYou can set up receiving the following additional information in your  \/payments response:\n\nThe BIN and last four digits of the network token used.\nThe BIN, last four digits, and expiry date of the card associated with the network token.\n\nTo set up receiving data about the network token:\n\nLog in to your Customer Area and switch to your merchant account.\nGo to Developers &gt; Additional data.\nIn the Card section, select Network token bin and summary for tokenised payments.\nSelect Save configuration.\n\nThe additionalData object in the  \/payments response will then contain the following parameters:\n\n\n\nParameter name\nDescription\n\n\n\n\nnetworkToken.bin\nThe BIN of the network token.\n\n\nnetworkToken.tokenSummary\nThe last four digits of the network token.\n\n\nlatestCard.bin\nThe BIN of the card. This is only returned for Mastercard tokens.\n\n\nlatestCard.summary\nThe last four digits of the card.\n\n\nlatestCard.expiryDate\nThe expiry month and year of the card.\n\n\n\n\n    \n\nManage network tokens yourself\nBecause network tokens are non-sensitive, you can also choose to collect and store them yourself. If you are already collecting network tokens from card networks like Visa, Mastercard and American Express, you can use those network tokens to make payments with Adyen.\nTo manage network tokens yourself:\n\nEnable receiving relevant data in your Customer Area to receive card details and network token information in the payment response.\nMake the initial payment with a network token, using the network token you collect from the card network.\nYou receive the networkTxReference that you need to use for subsequent payments in the payment response. Save this value.\nMake a subsequent payment using the same network token.\n\nEnable receiving relevant data\nTo enable the relevant fields:\n\nLog in to your Customer Area.\nGo to Developers &gt; Additional data.\nSelect the following fields:\n\nIn the Acquirer section: Network Transaction Reference\nIn the Card section: Card bin and Card summary\n\nSelect Save configuration.\n\nMake the initial payment with a network token\nMake a one-off payment, the first payment in a subscription, or the first payment for automatic top-ups.\n\n\nMake a POST  \/payments request, specifying:\n\n\n\nParameter name\nDescription\n\n\n\n\npaymentMethod.type\nnetworkToken\n\n\npaymentMethod.expiryMonth\nThe expiry month of the network token.\n\n\npaymentMethod.expiryYear\nThe expiry year of the network token.\n\n\npaymentMethod.cvc\nOptional. The card verification code or security code.\n\n\npaymentMethod.holderName\nThe name of the cardholder associated with the network token.\n\n\npaymentMethod.number\nThe network token you get from the card networks.\n\n\npaymentMethod.brand\nOptional. For co-badged network tokens in the US, this is the card network that you want to route the transaction to. Allowed values: visa mc amex discover accel maestro_usa nyce pulse star \n\n\nmpiData.directoryResponse\nY\n\n\nmpiData.authenticationResponse\nY\n\n\nmpiData.tokenAuthenticationVerificationValue\nThe network token authentication verification value (TAVV). This is the network token cryptogram.  If using Checkout API v67 and earlier, use the parameter mpiData.cavv instead. This is the cardholder authentication value (CAVV) received from the issuer.\n\n\nmpiData.eci\nThe electronic commerce indicator you get from the issuer.\n\n\nrecurringProcessingModel\nCardOnFile, Subscription, or UnscheduledCardOnFile, depending on your business model.\n\n\nshopperInteraction\nEcommerce\n\n\n\n\n\n\n\n\nIn the  \/payments response, note the networkTxReference field. You need this value to make subsequent subscription or automatic top-up payments.\n\n\nMake a subsequent payment with a network token\nMake a subsequent payment, using the networkTxReference you received in the payment response.\n\n\n    \n        \n        \n    \n\n\n\n\nTroubleshooting\nWhen you make a request to create or pay with a network token, the API response informs you of the outcome of the request. If an error occurs, the response includes the status, errorCode, and errorMessage parameters.\n\n    \n\nUse the error code and message to learn about the issue and troubleshoot.\nSee also\n\n\n                    Tokenization\n                \n                    EMVCo's Payment Tokenization Specification\n                \n                    Webhooks\n                \n","type":"page","locale":"pt","boost":18,"hierarchy":{"lvl0":"Home","lvl1":"Online payments","lvl2":"Network tokenization"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/online-payments","lvl2":"\/pt\/online-payments\/network-tokenization"},"levels":3,"category":"Online Payments","category_color":"green","tags":["Network","tokenization"]},"articleFiles":{"pay-with-our-nt.js":"<p alt=\"\">pay-with-our-nt.js<\/p>"}}