---
title: "Provision"
method: POST
path: "/cards/{card_id}/network-tokens"
tags: ["Network Tokens"]
---

# Provision

`POST /cards/{card_id}/network-tokens`

When Network Tokens are enabled for an account, VGS automatically provisions a token for each card stored. This provisioned token is mapped to the Card ID and kept in sync with the card’s network lifecycle.
As the card is updated or reissued, network token metadata is refreshed, enabling businesses to maintain valid and up-to-date payment credentials with no extra effort. Provisioning Network Tokens offers merchants a future-proof, secure foundation for handling customer payments. The provisioning is skipped if there is an active network token already exists for the card. This provisioning process is applicable regardless of the network token type - Card on File or Ecommerce Network Token.

## Path parameters

- `card_id` string, required

## Response `200`

Card's network token

## Other responses

- `201` — Card's network token
- `400` — The request was invalid.
- `401` — No credentials were provided, or the provided credentials were expired.
- `403` — Valid credentials were provided, but they do not permit access to this resource.
- `404` — Resource not found.
- `500` — Internal Server Error
- `503` — Service Unavailable

---

[API](https://skmtc.net/verygoodsecurity/apis/vgs-card-management-platform-cmp-api.md) · [All operations](https://skmtc.net/verygoodsecurity/apis/vgs-card-management-platform-cmp-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/verygoodsecurity/vgs-card-management-platform-cmp-api/revisions/71471c6a84af/schema)