---
title: "Card-on-file network tokens"
description: "Learn the process of creating a network token through card-on-file tokenization."
url: "https://docs.adyen.com/issuing/card-on-file-tokens"
source_url: "https://docs.adyen.com/issuing/card-on-file-tokens.md"
canonical: "https://docs.adyen.com/issuing/card-on-file-tokens"
last_modified: "2026-06-01T15:33:15+02:00"
language: "en"
---

# Card-on-file network tokens

Learn the process of creating a network token through card-on-file tokenization.

[View source](/issuing/card-on-file-tokens.md)

Card-on-file network tokens, also called merchant network tokens, occurs when your cardholder saves the card details with a merchant. For example, consider the case when a cardholder enters the card details on a website to complete a purchase or subscribe to a service with recurring payments.

Unless the merchant is PCI compliant, the merchant does not store the raw card details. Instead, the merchant makes a network token request that is forwarded to Adyen.

## Requirements

Before you begin, make sure that you fulfill the following requirements:

| Requirement          | Description                                                                                     |
| -------------------- | ----------------------------------------------------------------------------------------------- |
| **Integration type** | You must have an integration that supports Issuing.                                             |
| **Webhooks**         | In your Customer Area, subscribe to the following webhook:- **Network token webhook**           |
| **Setup steps**      | Reach out to your Adyen contact to make sure that you have set up a card manufacturing profile. |

## Overview

The process to create and activate card-on-file network tokens is as follows:

1. Your cardholder provides the card details to the merchant.
2. The merchant sends a network token request to the card scheme.
3. The card scheme sends the network token request to Adyen.
4. Adyen analyzes and approves the request if all the information in the request is correct.
5. Adyen sends the network token and the corresponding card details to the card scheme.
6. The card scheme stores the network token and the corresponding card details.
7. The card scheme sends the network token to the merchant.
8. The merchant stores the network token.

The following diagram shows the process to create and activate card-on-file network tokens.

[![](/user/pages/docs/07.issuing/19.card-on-file-tokens/card-on-file-flow.svg)](/user/pages/docs/07.issuing/19.card-on-file-tokens/card-on-file-flow.svg)

When your cardholder tries to make a purchase using the stored card details, the process is as follows:

1. Your cardholder selects the stored card as a payment method.
2. The merchant sends the network token to the card scheme.
3. The card scheme sends a request to Adyen to validate the status of the network token.
4. Adyen validates the status of the network token.
5. Adyen sends the result of the validation to the card scheme.
6. If the network token is valid, the card scheme approves the transaction.
7. The card scheme sends the approval to the merchant.

The following diagram shows the payment flow using a card-on-file network token.

[![](/user/pages/docs/07.issuing/19.card-on-file-tokens/card-on-file-payment.svg)](/user/pages/docs/07.issuing/19.card-on-file-tokens/card-on-file-payment.svg)

## Provisioning for card-on-file network tokens

Provisioning is the process of creating a network token. Provisioning is initiated when a merchant tries to save your cardholder's data for card-on-file payments.

The initial part of the provisioning flow is as follows:

1. Your user provides the card details to the merchant.
2. The merchant sends a request to the card scheme to create a network token for the card.
3. The card scheme forwards the network token request to Adyen.

After receiving the request, Adyen creates a network token with status **inactive**. Adyen then verify the merchant's information with the card scheme. Based on the outcome of the verification, Adyen decides whether to activate the network token.

After receiving the request, Adyen creates an inactive network token. To decide whether to activate the network token, Adyen verify the merchant's information with the card scheme.

### Verification process for provisioning

Card schemes maintain allowlists of approved merchants that are authorized to use card-on-file network tokens. When Adyen receives a network token request, Adyen verifies that the merchant is on the allowlist of the corresponding card scheme.

The verification results in one of the following outcomes:

* If the merchant is on the allowlist, Adyen automatically approves the network token.
* If the merchant is **not** on the allowlist, Adyen automatically closes the network token and ends the provisioning process.

The outcome of the verification process determines the flow of the provisioning process. The following tabs describe the possible flows.

### Tab: Token approved automatically

When Adyen approves the network token automatically, the provisioning flow is as follows:

1. The provisioning process is initiated.
2. Adyen creates the network token with an **inactive** status.
3. Adyen sends a webhook to inform your server that a network token was created.
4. Adyen verifies that the merchant is on the allowlist of the card scheme.
5. If the merchant is on the allowlist, Adyen activates the network token.
6. Adyen sends a webhook to inform you about the outcome.
7. Adyen sends the network token and the card details to the card scheme.
8. The card scheme stores the network token and the card details.
9. The card scheme sends the network token to the merchant.
10. The merchant stores the network token.

The following diagram shows the provisioning flow:

[![](/user/pages/docs/07.issuing/19.card-on-file-tokens/cof-token-approved-automatically.svg)](/user/pages/docs/07.issuing/19.card-on-file-tokens/cof-token-approved-automatically.svg)

### Tab: Token closed automatically

When Adyen closes the network token automatically, the provisioning flow is as follows:

1. The provisioning process is initiated.
2. Adyen creates the network token with an **inactive** status.
3. Adyen sends a webhook to inform your server that a network token was created.
4. Adyen verifies that the merchant is on the allowlist of the card scheme.
5. If the merchant is not on the allowlist, Adyen closes the network token.
6. Adyen sends a webhook to inform you about the outcome.

The following diagram shows a provisioning flow that ends after closing a network token.

[![](/user/pages/docs/07.issuing/19.card-on-file-tokens/cof-token-closed-automatically.svg)](/user/pages/docs/07.issuing/19.card-on-file-tokens/cof-token-closed-automatically.svg)

## Next steps

[required](/issuing/manage-network-tokens)

[Manage network tokens](/issuing/manage-network-tokens)

[Learn how to manage network tokens for cards added to digital wallets.](/issuing/manage-network-tokens)
