---
title: "Create Card Account"
method: POST
path: "/tokenizer/ve1_2/token/create"
tags: ["Card Account"]
---

# Create Card Account

`POST /tokenizer/ve1_2/token/create`

A card account (or card token) can be created by providing the card details and a customer reference. 

The API will provide a cardaccount object as a response, with a unique cardaccountid, that can be used to initiate a transaction.

## Headers

- `BD-Traceid` string, required
- `BD-Timestamp` string, required
- `Content-Type` string, required
- `Accept` string, required

## Request body

- object
  - `mercid` string, required — Unique identifier as defined by BillDesk for each merchant
  - `orderid` string, required — Unique ID generated by the merchant for each request
  - `customer_refid` string, required — Unique reference of the customer in the merchant system, and can be linked to different subscriptions of the same customer Required for mandate and tokenization
  - `card` PayUsingCardNumberPan, required
    - `number` string, required — Card number
    - `expiry_month` string, required — Card expiry month in MM format
    - `expiry_year` string, required — Card expiry year in YYYY format
    - `holder_name` string — Cardholder name
    - `cvv` string, required — Card cvv value
    - `tokenize` 'true' — If the card is required to be tokenized then, the value is true
    - `coft_consent` 'true' — Fixed value as true, confirming the card holder consent to tokenize the card
  - `coft_consent` string, required
  - `authentication_data` CardaccidAuthData, required
    - `transactionid` string — Unique transactionid created by BillDesk
    - `authenticationid` string — Unique authenticationid created by BillDesk
    - `rupay_auth_ref_no` string — Refers to the specific transaction reference provided by NPCI (for R cards)
    - `eci` string — Authentication ECI indicator, as per the 3ds protocol (for V, M, D, A cards)
    - `cavv` string — CAVV value generated by issuer (for V, M, D, A cards)
    - `threeds_version` '2.1.0' | '2.2.0' — Protocol of the 3ds2.0 version used for authentication
    - `ds_transaction_id` string — Directory server transaction id for 3ds2.0

## Response `200`

OK

- object
  - `objectid` 'transaction' | 'authentication' | 'mandate' | 'invoice' | 'cardaccount' | 'validatevpa' | 'dispute' | 'settlement' | 'altid' | 'mandate_token' | 'accountvalidation' — String representing the object's type. Objects of the same type share the same value.
  - `mercid` string — Unique identifier as defined by BillDesk for each merchant
  - `customer_refid` string — Unique reference of the customer in the merchant system, and can be linked to different subscriptions of the same customer Required for mandate and tokenization
  - `cardaccountid` string — Unique ID created by BillDesk for the combination of card number, mercid and customer_refid
  - `orderid` string — Unique ID generated by the merchant for each request
  - `masked_value` string — Masked card number, with the last four digits
  - `holder_name` string — Cardholder name
  - `issuer` string — Card issuer
  - `network` string — Card Network
  - `cardaccount_status` string
  - `coft_consent` string
  - `createdon` string, date-time — object creation timestamp
  - `network_token` CardaccNetworkIssuerToken
    - `token_ref_no` string — Token Reference Number – as received from TSP
    - `status` string — Token Status – as received from TSP
    - `token_expiry_month` string — Token Expiry Month – as received from TSP in the MM format
    - `token_expiry_year` string — Token Expiry Year – as received from TSP in the YYYY format
    - `createdon` string
  - `issuer token` CardaccNetworkIssuerToken
    - `token_ref_no` string — Token Reference Number – as received from TSP
    - `status` string — Token Status – as received from TSP
    - `token_expiry_month` string — Token Expiry Month – as received from TSP in the MM format
    - `token_expiry_year` string — Token Expiry Year – as received from TSP in the YYYY format
    - `createdon` string
  - `cardaccount_error_code` string — Represents the error code for the response
  - `cardaccount_error_type` string — Represents the error type for the response
  - `cardaccount_error_desc` string — Represents the error description for the response

## Other responses

- `403` — Forbidden
- `500` — Internal Server Error
- `default` — Any bad or invalid request will lead to following error object

---

[API](https://skmtc.net/billdesk/apis/payments.md) · [All operations](https://skmtc.net/billdesk/apis/payments/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/billdesk/payments/revisions/43f021fc467f/schema)