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

# Retrieve Card Account

`POST /tokenizer/ve1_2/token/retrieve`

Retrieve details of a cardaccount either by using the mercid and cardaccountid or the mercid, orderid and customer_refid as inputs.

## 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
  - `cardaccountid` string — Unique ID created by BillDesk for the combination of card number, mercid and customer_refid
  - `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
  - `orderid` string — Unique ID generated by the merchant for each request

## 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
  - `status` string
  - `coft_consent` string
  - `createdon` string, date-time — object creation timestamp
  - `network_token` NetworkIssuerToken
    - `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
    - `token_cryptogram` string — Token Cryptogram – as received from TSP in the ‘Detokenize’ response
    - `token_value` string — Token Value – as received from TSP in the ‘Detokenize’ response
  - `issuer_token` NetworkIssuerToken
    - `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
    - `token_cryptogram` string — Token Cryptogram – as received from TSP in the ‘Detokenize’ response
    - `token_value` string — Token Value – as received from TSP in the ‘Detokenize’ 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)