---
title: "Create a Network Token for a Card-on-File."
method: POST
path: "/payment-instruments/{token}/network-token"
tags: ["Payment Instrument Tokenization"]
---

# Create a Network Token for a Card-on-File.

`POST /payment-instruments/{token}/network-token`

Create a Network Token for a Card-on-File.

Network tokens are automatically provisioned when creating a BR-DGE Card-on-File. However, in situation where this didn't happen (for example if network token support was not enabled at the time of Card-on-File creation or a temporary failure to provision network tokens), you can use this endpoint to manually trigger network token provisioning.

## Response `201`

Network Token created.

- NetworkToken — Information about a Network Token.
  - `id` string, required — A unique identifier that represents the token associated with a card enrolled into the Card Network Service
  - `token` string — The unique token for the enrolled PAN which can be used in authorization as per ISO/IEC 7812 format. This will only be available once a cryptogram has been provisioned at least once.
  - `expiryDate` string, required — Expiration date of the token, noted in MM-YY format
  - `issuer` 'MASTERCARD' | 'VISA', required — The issuing card network of the Network Token
  - `status` 'ACTIVE' | 'DISABLED' | 'DELETED', required — The status of the Network Token. - `ACTIVE`: Can be used to provision Cryptograms for payments. - `DISABLED`: This can be due to card suspensions, fraud, or other temporary hold reasons and may be re-activated at a later date. - `DELETED`: The token is no longer valid and cannot be re-activated. This can be due to token expirations, lost card or other non-temporary reasons.
  - `tokenUniqueReference` string, required — Unique identifier for the Network Token provided by the Card Network
  - `paymentAccountReference` string, required — A non-financial reference assigned to each unique funding PAN (FPAN) that's used to link the payment account of that PAN to affiliated payment tokens. See our [dedicated PAR guide](https://docs.br-dge.io/docs/payment-account-reference) for more info.
  - `lastFour` string — Last four digits of the Network Token
  - `cardBin` string — BIN of the associated associated Card
  - `cardLastFour` string — Last four digits of the associated Card
  - `cardExpiryDate` string — Expiration date of the associated Card, noted in MM-YY Format
  - `cardIssuer` string — Name of the issuing bank

## Other responses

- `400` — Unable to provision Network Token - Bad Request
- `401` — Unauthorized request.
- `404` — The specified entity was not found.
- `409` — The network token already exists
- `500` — An internal server error occurred upstream while processing the request. If you have any questions about why you are receiving these responses, please raise a ticket with support on the BR-DGE Support Portal at <https://comcarde.atlassian.net/servicedesk/customer/portals> with the `id` from the response so we track down the individual requests on our end.

---

[API](https://skmtc.net/br-dge/apis/br-dge-transaction-rest-api.md) · [All operations](https://skmtc.net/br-dge/apis/br-dge-transaction-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/br-dge/br-dge-transaction-rest-api/revisions/a9c0feac5523/schema)